Team Name Critical Design Review UniversityInstitution Team Members
Team Name Critical Design Review University/Institution Team Members Date 2012 CDR 1
User Notes • You can reformat this to fit your design, but be sure to cover at least the information requested on the following slides • This template contains all of the information you are required to convey at the CDR level. If you have questions, please don’t hesitate to contact me directly: rocksatx@gmail. com 2012 CDR 2
Purpose of CDR • Confirm that: gnurf. net – The design is mature enough to move into the fabrication phase – Final analysis on systems that weren’t prototyped or needed further analysis is complete and accurate – Results of prototyping suggest the system will meet project requirements – Manufacturing plan is in place – Testing plan is in place and sufficient to ensure system functionality and performance in-flight – PDR risks have been walked down and to the left on the risk matrix (if possible) – Project meets requirements of Rock. Sat-X user guide – The project is on track to be completed on time and within budget 2012 CDR 3
CDR Presentation Content • Section 1: Mission Overview – – – Mission Overview Organizational Chart Theory and Concepts Concept of Operations Expected Results • Section 2: Design Description – – – Requirement/Design Changes Since CDR De-Scopes/Off-Ramps Mechanical Design Elements Electrical Design Elements Software Design Elements 2012 CDR 4
CDR Presentation Contents • Section 3: Prototyping/Analysis – Analysis Results • Interpretation to requirements – Prototyping Results • Interpretation to requirements – Detailed Mass Budget – Detailed Power Budget – Detailed Interfacing to Wallops jessicaswanson. com • Section 4: Manufacturing Plan – Mechanical Elements – Electrical Elements – Software Elements 2012 CDR 5
CDR Presentation Contents • Section 5: Testing Plan – System Level Testing • Requirements to be verified – Mechanical Elements • Requirements to be verified – Electrical Elements • Requirements to be verified – Software Elements • Requirements to be verified • Section 6: Risks – Risks from PDR to CDR • Walk-down – Critical Risks Remaining 2012 CDR 6
CDR Presentation Contents • Section 7: User Guide Compliance – Compliance Table – Sharing Logistics • Section 8: Project Management Plan – Schedule – Budget • Mass • Monetary – Work Breakdown Structure 2012 CDR 7
Mission Overview Name of Presenter 2012 CDR 8
Mission Overview • Mission statement • Break mission statement down into your overall mission requirements • What do you expect to discover or prove? • Who will this benefit/what will your data be used for? 2012 CDR 9
Organizational Chart Project Manager Shawn Carroll System Engineer Riley Pack Faculty Advisor Chris Koehler CFO Shawn Carroll Safety Engineer Chris Koehler Faculty Advisory Emily Logan Sponsor LASP Testing Lead Jessica Brown EPS David Ferguson Riley Pack • • • STR Tyler Murphy Aaron Russert DEP Aaron Russert Shawn Carroll PM Kirstyn Johnson Elliott Richerson What subsystems do you have? Who works on each subsystem? – Leads? Don’t forget faculty advisor/sponsor(s) 2012 CDR 10
Theory and Concepts • Give a brief overview of the underlying science concepts and theory • What other research has been performed in the past? – Results? 2012 CDR 11
Concept of Operations • Based on science objectives, diagram of what the payload will be doing during flight, highlights areas of interest • Example on following slide 2012 CDR 12
Example Con. Ops Altitude t ≈ 1. 7 min Altitude: 95 km t ≈ 4. 0 min Event B Occurs Altitude: 95 km t ≈ 1. 3 min Apogee Altitude: 75 km t ≈ 2. 8 min Event A Occurs Event C Occurs Altitude: ≈115 km t ≈ 4. 5 min Altitude: 75 km Event D Occurs End of Orion Burn t ≈ 0. 6 min t ≈ 5. 5 min Altitude: 52 km t = 0 min Chute Deploys -G switch triggered t ≈ 15 min -All systems on Splash Down -Begin data collection 2012 CDR
Expected Results • This is vital in showing you understand the science concepts • Go over what you expect to find – Ex. What wavelengths do you expect to see? How many particles do you expect to measure? How well do you expect the spin stabilizer to work (settling time? )? How many counts of radiation? etc 2012 CDR 14
Design Description Name of Presenter 2012 CDR 15
Changes Since PDR • What major changes have you made since PDR? – Why were these changes made? • Do these change any of your mission objectives/requirements? • SLIDE COUNT: Your Discretion 2012 CDR 16
De-Scopes and Off-Ramps • Has the scope of your project changed at all? – i. e. have you eliminated any mission objectives to complete the project on time? • If there are portions of your project with lots of risk, do you have “off-ramps” in case you run into schedule/budget constraints? • SLIDE COUNT: Your Discretion 2012 CDR 17
Mechanical Design Elements • Give me a brief overview of your final mechanical design • You have a lot of freedom here – Present what you think is relevant • Mechanical drawings should be included • Any stress/strain analysis? • Material choices? – SLIDE COUNT: 3 -5 2012 CDR 18
Electrical Design Elements • Give me a brief overview of your final electrical design • You have a lot of freedom here – Present what you think is relevant • Schematics? • Sensor specification relation to requirements • SLIDE COUNT: 3 -5 2012 CDR 19
Software Design Elements • Give me a brief overview of your final software design • You have a lot of freedom here – Present what you think is relevant • Software flow diagram? • State diagrams? • Brief function overviews (input/output)? – SLIDE COUNT: 3 -5 2012 CDR 20
Prototyping/Analysis Name of Presenter 2012 CDR 21
Analysis Results • What was analyzed? – i. e. Finite Elements Analysis, Aerodynamic Loading, Boom Extension… • What are the key results? • How do these results relate to the project requirements? • SLIDE COUNT: Your Discretion 2012 CDR 22
Prototyping Results • What was prototyped? – i. e. electrical system bread boarded, boom arm, payload foam mock-up… – What are the key results? • How do these results relate to the project requirements? • SLIDE COUNT: Your Discretion 2012 CDR 23
Detailed Mass Budget Example. Sat Mass Budget • Present your subsystem masses and total mass similar to what is given at right. Subsystem STR DEP EPS PM … … Total Over/Under 2012 CDR Total Mass (lbf) 2 8 12 9 31 (1. 00) 24
Detailed Power Budget Example. Sat Power Budget Subsystem STR DEP EPS PM … … • • Voltage (V) Current (A) 0 12 28 28 Time On (min) 0 0. 4 0. 3 0. 9 Present your power budget (like above) I am most interested in total amp-hours since each payload space is allowed 1 Ah. Voltages and currents should also be included. Use whatever format makes sense to you. 0 2 20 8 Total (A*hr): Over/Under 2012 CDR Amp-Hours 0. 000 0. 013 0. 100 0. 120 0. 233 0. 77 25
Wallops Interfacing: Power Connector--Customer Side Pin Function 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 • Fill-in the function side for your payload • I will check for consistency with User Guide 2012 CDR 26
Wallops Interfacing: Telemetry Connector--Customer Side Pin Function 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 Pin Function 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 • Fill-in the function side for your payload • I will check for consistency with User Guide 2012 CDR 27
Manufacturing Plan Name of Presenter 2012 CDR 28
Mechanical Elements • What needs to be manufactured? • What needs to be procured? • Present a plan/schedule to get it done in time for testing. • Don’t forget margin! • SLIDE COUNT: Your Discretion 2012 CDR 29
Electrical Elements • What needs to be manufactured/soldered? • How many revisions of the electronics do you anticipate? (Be realistic!) • What needs to be procured? • Present a plan/schedule to get it done in time for testing. • Don’t forget margin! • SLIDE COUNT: Your Discretion 2012 CDR 30
Software Elements • What discrete blocks of code need to be completed? • Which blocks depend on other blocks? • Present a plan/schedule to get it done in time for testing. • Don’t forget margin! • SLIDE COUNT: Your Discretion 2012 CDR 31
Testing Plan Name of Presenter 2012 CDR 32
System Level Testing • Consider system level requirements that need to be verified • Present a brief overview of the tests you need to conduct to verify these requirements • When will these tests be performed? • SLIDE COUNT: Your Discretion 2012 CDR 33
Mechanical Testing • Consider subsystem level requirements to be verified (mass/volume/vibration…) • Present a brief overview of the tests you need to conduct to verify these requirements • When will these tests be performed? • SLIDE COUNT: Your Discretion 2012 CDR 34
Electrical Testing • Consider subsystem level requirements to be verified (sample rate/deployment tests…) • Present a brief overview of the tests you need to conduct to verify these requirements • When will these tests be performed? • SLIDE COUNT: Your Discretion 2012 CDR 35
Software Testing • Consider how software and electrical depend on each other for testing • Present a brief overview of what portions of the code need to be completed to test the electrical system at its various testing points • When will these tests be performed? • SLIDE COUNT: Your Discretion 2012 CDR 36
Risks Name of Presenter 2012 CDR 37
Risk Walk-Down RSK. 3 RSK. 1 RSK. 4 Consequence RSK. 2 • What were your biggest risks at PDR? (remind me) • What have you done to mitigate them? • Hopefully you have moved them to the lower left side of the risk chart as a result (walk-down) RSK. 2 RSK. 1 RSK. 3 RSK. 4 Possibility 2012 CDR 38
Risk Walk-Down RSK. 1 RSK. 3 • What are your NEW top 3 risks since PDR? RSK. 2 Consequence • Do you have plans to walk them down? • Are there any risks you just have to accept? • Why? Possibility 2012 CDR 39
User Guide Compliance Name of Presenter 2012 CDR 40
User Guide Compliance Requirement Status/Reason (if needed) Center of gravity in 1" plane of plate? 1. 2" currently Max Height < 12" Within Keep-Out Using < 10 A/D Lines Using/Understand Parallel Line Not Being Utilized Using/Understand Asynchronous Line 9600 Baud Using X GSE Line(s) 1 (per requirement) Using X Redundant Power Lines 1 (per requirement) Using X Non-Redundant Power Lines 2 (one extra) Using < 1 Ah 1. 1 (working on reducing) Using <= 28 V 200 V (Will conformal coat) 2012 CDR 41
Sharing Logistics • Who are you sharing with? – Summary of your partner’s mission (1 line) • Plan for collaboration – How do you communicate? – How will you share designs (solidworks, any actual fit checks before next June)? • Structural interface – will you be joining with standoffs or something else (again, be wary of clearance)? 2012 CDR grandpmr. com 42
Project Management Plan Name of Presenter 2012 CDR 43
Schedule • Your schedule should be VERY detailed at this point • When will you procure things? • Major tests listed • Major integrations listed • Next semesters interim reviews included • The more the plan for, the fewer surprises there will be! • Format: • Gant charts • Excel spreadsheet • Simple list • Whatever works for you! Don’t let the schedule sneak up on you! 2012 CDR 44
Budget • • Present a somewhat detailed budget (doesn’t have to be nut and bolt level) • A simple Excel spreadsheet will do Simply to ensure that you aren’t over budget going into manufacturing • It is suggested that you add in at least a 10% margin at this point Margin: 0. 10 Budget: $1, 300. 00 Example. Sat Item Supplier Estimated, Specific Cost Number Required Motor Controller Digi. Key $150. 00 PM LASP $0. 00 Microcontroller Digi. Key $18. 00 Printed Circuit Boards Advanced Circuits $33. 00 Misc. Electronics (R, L, C) Digi. Key $80. 00 Boom Material onlinemetals. com $40. 00 Probe LASP $0. 00 Testing Materials ? ? ? $200. 00 Last Update: Toal Cost 2 1 3 3 3 2 1 1 Notes $300. 001 for testing $0. 00 LASP mentor deserves shirt $54. 00 3 board revs $99. 00 3 board revs $240. 003 board revs $80. 00 1 test article $0. 00 $200. 00 Estimated cost to test system Total (no margin): Total (w/ margin): 2012 CDR 9/30/2010 11: 50 $973. 00 $1, 216. 25 45
WBS • Present a very top-level work break down schedule • One can look up the tree for large scope goals • One can look down the tree for dependencies • Help each subsystem “see” the path ahead PMP EPS STR PM DEP • Obtain PM from LASP • Trade Studies • Obtain PM from LASP • EEF Proposal for funding • … • Schematics • Order Materials • EEF Proposal for funding • Schematic Review • Work Request Into Shop • … • ICDs • … • … • First Revision of Boards • … 2012 CDR 46
Conclusion • Issues, concerns, any questions 2012 CDR 47
- Slides: 47
