Team Name Critical Design Review UniversityInstitution Team Members
Team Name Critical Design Review University/Institution Team Members Date 2013 CDR 1
CDR Delieverables • In addition to this presentation, each school must include the following by December 10 th • Mechanical drawings in pdf format • Electrical schematics in pdf format • Signed copies of the Power and Telemetry ICDs in pdf format • Completed Power Budget in xls format • Completed Pin Assignments in xls format • Completed Timer Event matrix in xls format • Be sure to place all these files, including ppt presentation in your Drop. Box Pony Express folder by COB on December 10, 2012 2013 CDR 2
User Notes • You may 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 2013 CDR 3
Purpose of CDR • Confirm that: – 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 – Project meets requirements of Rock. Sat-X user’s guide – The project is on track to be completed on time and within budget 2013 CDR 4
CDR Presentation Outline • • Section 1: Mission Overview Section 2: Design Description Section 3: Subsystem Design Section 4: Prototyping/Analysis Section 5: Manufacturing Plan Section 6: Testing Plan Section 7: User Guide Compliance Section 8: Project Management Plan 2013 CDR 5
1. 0 Mission Overview Name of Presenter 2013 CDR 6
Mission Overview • Mission statement • What do you expect to discover or prove? • Who will this benefit and/or what will your data be used for? 2013 CDR 7
Theory and Concepts • Give a brief overview of the underlying science concepts and theory • What other research has been performed in the past? – Results? 2013 CDR 8
Mission Requirements: • Project requirements derived from mission statement – Break down into mission objectives, system level objectives – Please show traceability and linkages – See example on following slide crestock. com 2013 CDR 9
Mission Requirements: crestock. com 2013 CDR 10
Success Criteria: – Define Minimum Success: What is the least amount of data you can collect that will still constitute a success? – Comprehensive Success: Under ideal conditions, what would constitute comprehensive mission success? 2013 CDR 11
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 2013 CDR 12
Concept of Operations • Based on science objectives, describe what the payload will be doing during flight and highlights areas of interest • Include all significant events during your flight • RS-X 2012 Mission timeline included on following slide for guidance • You may used the example on following slide updated with your mission events • Complete your Timer Events Matrix in xls format and submit • Include screen shot of this matrix in your presentation 2013 CDR 13
Concept of Operations • Example of Timer Events Matrix for presentation Event Time On Dwell Event Description GSE 1 T-180 sec 540 sec GSE 2 T-180 sec 540 sec TE-NR 1 T+000 sec 360 sec Launch TE-NR 2 T+000 sec 360 sec Bring more power to RGA's. TE-NR 3 T+000 sec 360 sec Bring more power to RGA's. TE-R T+000 sec 360 sec Bring more power to RGA's. Minutes before launch. Start on the computer for the experiments. 2013 CDR 14
Example Con. Ops Altitude t ≈ ? ? ? Altitude: ? ? km t ≈ ? ? ? Event B Occurs Altitude: ? ? km t ≈ ? ? ? Apogee Altitude: ? ? km t ≈ 199. 7 sec Event A Occurs Event C Occurs Altitude: ≈153 km t ≈ ? ? ? Altitude: ? ? km Event D Occurs End of Malemute Burn t ≈ 28. 7 sec t ≈ 454. 9 sec Altitude: 17. 2 km t = 0 min Chute Deploys -G switch triggered t ≈ 876 sec -All systems on Splash Down -Begin data collection 2013 CDR
Concept of Operations 2013 CDR 16
2. 0 Design Description Name of Presenter 2013 CDR 17
Actions from PDR • Please update me on your actions assigned during PDR 2013 CDR 18
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? 2013 CDR 19
Design Overview: Functional Block Diagrams • Functional block diagram – Show all major and minor subsystems and how they are interconnected – Show voltage levels and data lines – Show all power and data storage – Show mechanical and electrical inhibits – Show Wallops interface (power/telemetry) • Example on following slide • I will spend a lot of time on this diagram with each team and it will be referred to all the way up until launch so make it good 2013 CDR 20
Example Functional Block Diagram 2013 CDR
Mechanical Design Elements • Give me a brief overview of your final mechanical design • Mechanical drawings should be included • Solid models (labeled) with many views should be included • Any stress/strain analysis? • Material choices? 2013 CDR 22
3 D image of our payload 2013 CDR 30
Electrical Design Elements • Give me a brief overview of your final electrical design • Overall electrical schematics should be presented • Sensor specification and how they meet your requirements 2013 CDR 24
System Electrical Diagram 2013 CDR 25
Software Design Elements • Give me a brief overview of your final software design • Software flow diagram should be included • Could include State diagrams • Could include function overviews (input/output) 2013 CDR 26
De-Scopes and Off-Ramps • If there are portions of your project with lots of risk, do you have “off-ramps” in case you run into schedule/budget constraints? • Describe these “De-Scopes” and “offramps” that may be used in the future 2013 CDR 27
3. 0 Subsystem Design Name of Presenter 2013 CDR 28
Subsystem Design • Start with your organization chart with each of your subsystems labeled • Detail each subsystem’s final design • Each subsystem should be separated on to its own slide • Each subsystem should cover: – – – Drawing Power and data Mechanical and Electrical Interfaces Weight Critical technology used and current issues 2013 CDR grandpmr. com 29
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) 2013 CDR 30
4. 0 Prototyping/Analysis Name of Presenter 2013 CDR 31
Analysis Results • What was analyzed? – i. e. Finite Elements Analysis, Aerodynamic Loading, Boom Extension, Link Budgets… • What are the key results? • How do these results relate to the project requirements? 2013 CDR 32
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? 2013 CDR 33
Detailed Mass Budget Example. Sat Mass Budget • Present your subsystem masses and total mass similar to what is given at right. • Mass of plate is 3. 425 pounds Subsystem STR DEP EPS PM … … Total Over/Under 2013 CDR Total Mass (lbf) 2 8 12 9 31 (1. 00) 34
Detailed Power Budget • • USE Power Budget xls file Include a screenshot in your presentation and the actual excel file with your CDR package I am most interested in total amp-hours since each payload space is allowed 1 Ah. Voltages and currents should also be included. 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 0 2 20 8 Total (A*hr): Over/Under 2013 CDR Amp-Hours 0. 000 0. 013 0. 100 0. 120 0. 233 0. 77 35
Wallops Interfacing: Power Connector--Customer Side Pin Function 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 • • USE Pin Assignment xls file Include a screenshot in your presentation and the actual excel file with your CDR package • Fill-in the function side for your payload • Check for consistency with User’s Guide 2013 CDR 36
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 2013 CDR • USE Pin Assignment ICD xls file • Fill-in the function side for your payload • Include a screenshot in your presentation and the actual excel file with your CDR package • Check for consistency with User’s Guide 37
5. 0 Manufacturing Plan Name of Presenter 2013 CDR 38
Mechanical Elements • What will be manufactured? • What will be purchased? • Present a plan/schedule to get it done in time for testing. • Include schedule margin. • Use of diagrams is encouraged 2013 CDR 39
Electrical Elements • What needs to be manufactured/soldered? • How many revisions of the electronics do you anticipate? • What needs to be procured? • Present a plan/schedule to get it done in time for testing. • Include schedule margin • Use of schematics is encouraged 2013 CDR 40
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. • Include schedule margin 2013 CDR 41
6. 0 Testing Plan Name of Presenter 2013 CDR 42
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? 2013 CDR 43
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? • Call-out any deployment tests and how they will be preformed • Discuss any mechanical inhibits you may need for Wallops testing 2013 CDR 44
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? • Callout any high voltage components • Callout any internally powered components and how they will be tested • Discuss any electrical inhibits you may need for Wallops testing 2013 CDR 45
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? • Discuss any software inhibits you may need for Wallops testing 2013 CDR 46
7. 0 User Guide Compliance Name of Presenter 2013 CDR 47
User Guide Compliance • Use the following example to show your compliance with the RS-X 2013 User’s Guide • Teams that are sharing, please fill out your school’s compliance only 2013 CDR 48
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) 2013 CDR 49
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)? • Discuss number of meetings you have had with sharing school • POC for sharing school and their contact info 2013 CDR 50
8. 0 Project Management Plan Name of Presenter 2013 CDR 51
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! 2013 CDR 52
Budget - Present a very top-level budget (not nut and bolt level) - Include launch fee and deposit amounts AND include status of each - Include estimates for travel in June and August - Include spare parts and margin in you hardware budget Margin: 0. 25 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 2013 CDR Last Update: 9/30/2010 11: 50 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): $973. 00 Total (w/ margin): $1, 216. 25 53
Team Availability Matrix • • • Please submit your availability matrix for Spring 2013 semester Please state the time-zone on your matrix All times are available for Chris between 7 AM – 5 PM MST 2013 CDR 54
Contact Matrix • • You can copy and paste your contact spreadsheet here Please re-verify participants US Person Status 2013 CDR 55
Conclusion • Please list questions and concerns you would like to discuss 2013 CDR 56
- Slides: 56