FIRST Competition 2015
Tools For The CyberFerrets
SysEng Meeting 12/4/14
SysEngMeeting120414
1
What SysEng Tools Do We Need?
• Tools are Documents that allow us to manage
programs
• Most Tools need to be in-place during Design Week
– Tool usage should have been pre-rehearsed, so they work
during Design Week
– Tools need Templates that are debugged & ready-to-use
• Design Week Structure shows when Tools are used
– Need to assign responsibilities for Tasks (discussions) and
Tools (documented commitments at Syst/SubSyst levels)
– Need to keep on Design Week schedule
• Establish Communication Processes for Build Season
SysEngMeeting120414
– SysEng & Team Leads need to rehearse usage of BuildTools
– Establish convenient storage & access to Tools (both in-work
and completed documentation)
There’s Lots To Organize!
2
Start Building Robot On Saturday!
Proposed 2015 Design Week Schedule
SysEngMeeting120414
Design Week Tools Shown Here
3
Proposed Design Week Tools
• Z-drive organizing & maintenance (who’s responsible?)
– Mapped for Syst/SubSyst? Empty folders? CM plan?
• Rule Quiz (who is responsible for what part?)
– Previous year baseline? (Y!) Template? On Z-drive now?
• System Strategy Outline (who’s responsible for what part?)
– Previous year baseline ? (Y!) Template? On Z-drive now?
• System Concept of Operations (who’s responsible?)
– Previous year baseline? (Y!) Template? On Z-drive now?
• SubSyst CONOPS (who’s responsible? Do they know it?)
•
Previous year baseline? (Y!) Template? On Z-drive now?
• System/SubSyst Preliminary Design (who’s responsible?)
•
Previous year baseline? (Y!) Template? On Z-drive now?
• System Budget (space, weight, power, interfaces?)(who’s resp)
SysEngMeeting120414
•
Previous year baseline? (?!) Template? On Z-drive now?
• System/SubSyst Schedule (detailed commitments?) (who’s resp)
•
Previous year baseline? (?!) Template? On Z-drive now?
Don’t wait ‘till Design Week to invent/set-up Mgmt Tools!
4
Previous Year Design Week Tools
• Z-drive organizing & maintenance (who’s responsible?)
– I have had no experience with server of Robot Team!
• Rule Quiz (who is responsible for what part?)
– Someone should be able to unearth an old Quiz.
• System Strategy Outline (who’s responsible for what part?)
– I can bring file for printout of an old outline.
• System Concept of Operations (who’s responsible?)
– I can bring file for printout of an old one.
• SubSyst CONOPS (who’s responsible? Do they know it?)
•
I can bring file for printout of an old one.
• System/SubSyst Preliminary Design (who’s responsible?)
•
Someone should be able to unearth an old Design Review package.
• System Budget (space, weight, power, interfaces?)(who’s resp)
SysEngMeeting120414
•
Someone should be able to unearth an old Design Review package.
• System/SubSyst Schedule (detailed commitments?) (who’s resp)
•
Don’t think we have a valid old one. Have several templates.
Don’t wait ‘till Design Week to invent/set-up Mgmt Tools!
5
For Build Season We Need
Improved Communication Processes
• Need Meeting Procedure
– Detailed Agenda
• distributed (website, RSS?) well-ahead of meeting
– Detailed Minutes Distributed soon after meeting
• Defining action-items, due dates, assignees
– All meetings/action Items tracked in Detailed Scheduling
• Need Central Location of all documentation
SysEngMeeting120414
– Complete documentation list with examples
• Release dates & Updates tracked in Detail Schedule
– Change control process (debugged) (change alerts?)
– Ease of access (website?, GoogleDocs?, RSS?)
– Integration with Drawing Tree (both CAD & Sketches)
– Procurement docs (POs, delivery dates)
– Each subsystem is responsible for their portion of Bill of
Materials – update regularly
Communication Keeps Us On Track!
6
Documents Define Scope of Design
• System Engineering Team (incl. Programming)
– Lead Definition of Game Strategy Outline – Control Changes
– Lead Definition of Robot CONOPS – Control Changes
• CONOPS = Definition of all things ROBOT must
– Lead Def. of each SubSyst CONOPS – Control Changes
– Lead Def. Of Interface Control Matrix – Control Changes
• Each SubSystem: weight, size, interfaces, power, etc.
• Volume allotment/Interfaces CAD Dwg
– Define/Plan/Schedule Arena/Targets/Simulators
• SubSystem Teams (except Programming)
SysEngMeeting120414
–
–
–
–
Negotiate/Agree to SubSyst CONOPS – Track Changes
Negotiate/Agree to Interface Control Matrix – Track Changes
Generate Plan A & B design/schedule/selloff procedures
Define/Plan/Schedule Selloff Simulators
Define Who Decides What!
7
Schedule Everything In Detail
• Overview of Build Season (very approximate):
–
–
–
–
–
–
Week 1:
Week 2:
Week 3:
Week 4:
Week 5:
Week 6:
Design Week ending in Design Review
Detailed Design & Start of SubSys Build
Completion of SubSys Build
Optimize & Selloff SubSys
Integrate SubSys into Robot System & Optimize
Driver Training
• What Overview looks like in Gantt Schedule Format:
SysEngMeeting120414
Overview Hardly Worth Scheduling!
8
Schedule Needs Detail
Gantt Charts
Garbage In = Garbage Out
Require tangible feedback @
end of “shift”
You control it – It doesn’t
control anything – it informs
SysEngMeeting120414
Example of One SubSystem!
9