Team Name Critical Design Review

1. Team NameCritical Design Review University/Institution Team Members Date

2. CDR Delieverables • In addition to this presentation, each school must include the following by December 10th • 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 DropBox Pony Express folder by COB on December 10, 2012

3. 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

4. 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 RockSat-X user’s guide • The project is on track to be completed on time and within budget

5. 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

6. 1.0 Mission Overview Name of Presenter

7. 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?

8. Theory and Concepts • Give a brief overview of the underlying science concepts and theory • What other research has been performed in the past? • Results?

9. 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

10. Mission Requirements: crestock.com

11. 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?

12. 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

13. 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

14. Concept of Operations • Example of Timer Events Matrix for presentation

15. Example ConOps Altitude t ≈ ??? Altitude: ?? km Event B Occurs t ≈ ??? Altitude: ?? km Event C Occurs t ≈ ??? Altitude: ?? km Event A Occurs Apogee t ≈ 199.7 sec Altitude: ≈153 km t ≈ ??? Altitude: ?? km Event D Occurs End of Malemute Burn t ≈ 28.7 sec Altitude: 17.2 km t ≈ 454.9 sec Chute Deploys -G switch triggered -All systems on -Begin data collection t = 0 min t ≈ 876 sec Splash Down

16. Concept of Operations

17. 2.0 Design Description Name of Presenter

18. Actions from PDR • Please update me on your actions assigned during PDR

19. 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?

20. 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

21. Example Functional Block Diagram

22. 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?

23. 3D image of our payload

24. Electrical Design Elements • Give me a brief overview of your final electrical design • Overall electrical schematicsshould be presented • Sensor specification and how they meet your requirements

25. System Electrical Diagram

26. 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)

27. 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 “off-ramps” that may be used in the future

28. 3.0 Subsystem Design Name of Presenter

29. 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 grandpmr.com

30. Organizational Chart • What subsystems do you have? • Who works on each subsystem? • Leads? • Don’t forget faculty advisor/sponsor(s) 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

31. 4.0 Prototyping/Analysis Name of Presenter

32. 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?

33. 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?

34. Detailed Mass Budget • Present your subsystem masses and total mass similar to what is given at right. • Mass of plate is 3.425 pounds

35. 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.

36. Wallops Interfacing: Power • 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

37. Wallops Interfacing: Telemetry • 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

38. 5.0 Manufacturing Plan Name of Presenter

39. 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

40. 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

41. 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

42. 6.0 Testing Plan Name of Presenter

43. 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?

44. 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

45. 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

46. 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

47. 7.0 User Guide Compliance Name of Presenter

48. 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

49. User Guide Compliance

50. 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