1. 2014 CDR Team Name Critical Design Review 1

2. 2014 CDR CDR Delieverables 1.Mechanical drawings in pdf format 2.Electrical schematics in pdf format 3.Completed Power Budget 4.Completed Assignments 2

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

4. 2014 CDR CDR Presentation Outline Section 1: Mission Overview Section 2: System Overview 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 (PMP) 4

5. 2014 CDR 1.0 Mission Overview Name of Presenter 5

6. 2014 CDR Mission Overview: Mission Statement Present a concise Mission Statement What do you expect to discover or prove? Who will this benefit/what will your data be used for? 6

7. 2014 CDR Mission Overview: Mission Objectives Mission Objectives  derived from mission statement –Break down into mission statement into your mission objectives –Should have 1 to 3 objectives 7

8. 2014 CDR Mission Overview: Theory and Concepts Give a brief overview of the underlying science concepts and theory What other research has been performed in the past? –Results? 8

9. 2014 CDR Mission Overview: Expected Results Go over what you expect to discover and what you data might look like –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 This is vital in showing you understand the science concepts 9

10. 2014 CDR Mission Overview: Success Criteria Minimum Success Criteria: –What is the least amount of data you can collect that will still constitute a success? Comprehensive Success Criteria: –What is the ideal amount of data to have full or comprehensive mission success? 10

11. 2014 CDR 2.0 System Overview Name of Presenter 11

12. 2014 CDR Systems Overview: System Changes Since PDR 12 Please update me on your actions assigned during PDR (list them) What major changes have you made since PDR? –Why were these changes made? Do these change any of your mission objectives/requirements?

13. 2014 CDR Top Level Requirements: 13 At the CDR level you should highlight the most critical (Top 3?) system and project level requirements and how they will be verified prior to flight (an example below). Verification Method can be Demonstration, Analysis, Inspection, or Test Requirement Verification Method Description They deploable boom shall deploy to a height of no more than 12” DemonstrationBoom will be expanded to full length in the upright position to verify it doesn’t exceed 12” The boom shall extend to the full 12” height in less than 5 seconds from a horizontal position. AnalysisThe system’s dynamical characteristics will be derived from SolidWorks, and available torques will yield minimum response time. The full system shall fit on a single RockSat-X deck InspectionVisual inspection will verify this requirement The sytem shall survive the vibration characteristics prescribed by the RockSat- X program. TestThe system will be subjected to these vibration loads in June during testing week.

14. 2014 CDR System Overview: Science Design Overview Summarize the instrumentation/sensors/devices that will be used to complete your science mission Present a concept of HOW your science hardware will work to achieve your mission Please include a diagram/sketch/model of your science design 14

15. 2014 CDR System Overview: Functional Block Diagram FBD should show –HOW subsystems interact with each other –HOW data moves (recorded, stored, telemetry) –HOW power and data flow through subsystems (include voltage levels and data line types) –Show mechanical and electrical inhibits –Show Wallops interface (power/telemetry) and include GSE and TE lines 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 15

16. 2014 CDR System Overview: Mechanical Design 16 Give me a brief overview of your final mechanical design Mechanical drawings should be included with your other CDR deliverables Solid models (labeled and dimensioned) with many views should be included Expecting multiple views (top, bottom, side, and iso views) Any stress/strain analysis? Material choices?

17. 2014 CDR System Overview: Electrical Design 17 Give me a brief overview of your final electrical design Overall electrical schematics should be presented Sensor specification and how they meet your requirements

18. 2014 CDR System Overview: Software Design 18 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)

19. 2014 CDR De-Scopes and Off-Ramps 19 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

20. 2014 CDR System Overview: Special Requests Please describe any special requests of the rocket and/or Wallops that are required for minimum and/or comprehensive mission success Examples include but are not limited to: –Extra volume –Extra weight –High voltage –Extra telemetry –Faster sampling –Special environmental considerations 20

21. 2014 CDR 3.0 Subsystem Design Name of Presenter 21

22. 2014 CDR Subsystem Design: 22 List all the subsystems in your payload that will covered in this section > Should match subsystems called out in your Functional Block Diagram above You MUST cover the items on following two slides for each subsystem listed above Each subsystem should be separated on to its own slide(s)

23. 2014 CDR Subsystem Design: Subsystem Name Provide the following for each subsystem: –Drawing/model/sketch of subsystem –Power and data of subsystem –Mechanical and Electrical Interfaces with other subsystems/Wallops –Hardware used (include where possible pictures of hardware to be ordered or on hand) –Subsystem Weight –Other –Statement on whether this subsystem design is FINAL –If not FINAL, list what needs to still be done with the design 23 USE this slide for each subsystem

24. 2014 CDR Subsystem Design: Detailed Weight Budget 24 ExampleSat Weight Budget SubsystemTotal Weight (lbf) STR2 DEP8 EPS12 PM9 … … … … Total31 Over/Under(1.00) Present your subsystem weight and total weight similar to what is given at right Full payload spaces must = 30+/-1.0 lbs Shared payload spaces must = 15+/-0.5 lbs –Weight of payload deck is 3.425 lbs

25. 2014 CDR 4.0 Prototyping/Analysis Results/Pans Name of Presenter 25

26. 2014 CDR Prototyping Results/Plan: 26 What has been prototyped? –i.e. electrical system bread boarded, boom arm, payload foam mock-up… – What are the key results? Plans for other prototyping activities? How do these results/plans relate to the project requirements?

27. 2014 CDR Analysis Results/Plans: 27 What was analyzed? –i.e. Finite Elements Analysis, Aerodynamic Loading, Boom Extension, Link Budgets… What are the key results? Plans for other analyses? How do these results/plans relate to the project requirements?

28. 2014 CDR 5.0 Manufacturing Plan Name of Presenter 28

29. 2014 CDR Mechanical Elements 29 What will be manufactured? What will be purchased? Present a manufacturing plan/schedule that supports your testing/prototyping schedule Include schedule margin. Use of diagrams is encouraged

30. 2014 CDR Electrical Elements 30 What needs to be manufactured/soldered? How many revisions of the electronic boards do you anticipate? What needs to be procured? Present a plan/schedule that supports your testing/prototyping schedule Include schedule margin Use of schematics is encouraged

31. 2014 CDR Software Elements 31 What discrete blocks of code need to be completed? Which blocks depend on other blocks? Use your Software Flow Diagram above if you like Present a plan/schedule that supports your testing/prototyping schedule Include schedule margin

32. 2014 CDR 6.0 Testing Plan Name of Presenter 32

33. 2014 CDR Testing Plan: Mechanical Testing 33 Consider subsystem level requirements to be verified (weight/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

34. 2014 CDR Testing Plan: Electrical Testing 34 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

35. 2014 CDR Testing Plan: Software Testing 35 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

36. 2014 CDR Testing Plan: System Level Testing 36 Present an overview of the tests you need to conduct at the system level Consider an stepped approach to testing subsystems to get to the System Level Mission Simulations should be a part of that When will these tests be performed?

37. 2014 CDR 7.0 User Guide Compliance Name of Presenter 37

38. 2014 CDR User Guide Compliance 38 Use the following example to show your compliance with the RS-X 2014 User’s Guide Teams that are sharing a payload space, please fill out your school’s compliance only

39. 2014 CDR 8.0 Project Management Plan (PMP) Name of Presenter 39

40. 2014 CDR PMP: Management Team Organization Chart Preliminary schedule for the semester/year Team mentors (industry, faculty)? Monetary budget –Include launch fee, travel, labor, hardware, etc. –Also, include the status of your deposit 40

41. 2014 CDR PMP: Current Team Availability Matrix 41 You can copy and paste your availability spreadsheet here Times should be in Mountain Time

42. 2014 CDR PMP: Spring Team Availability Matrix 42 Please submit your availability matrix for Spring 2014 semester Times should be in Mountain Time Chris is available 7:30 AM – 5 PM Mountain TIME M – F in spring 2014

43. 2014 CDR PMP: Latest Contact Matrix 43 You can copy and paste your contact spreadsheet here

44. 2014 CDR PMP: Worries What are your biggest worries or potential failure points with your final design? 44

45. 2014 CDR PMP: Conclusions Address why your mission deserves to fly Next steps for your team to get to STR (Subsystem Testing Review) –February 17 th, 2014 Please list questions and concerns you would like to discuss 45