Team Name Conceptual Design Review

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

2. 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 CoDR level. If you have questions, please don’t hesitate to contact me directly: rocksatx@gmail.com Acknowledgement Thanks to Emily Logan for developing the general layout and content of these slides

3. Purpose of CoDR • Confirm that: • Science objectives are understood and well-defined • Preliminary mission requirements are defined and traceable to science objectives • Understand concept of operations • Technology dependencies and alternative strategies for achieving science objectives gnurf.net

4. CoDR Presentation Content • Section 1: Mission Overview • Mission Overview • Theory and Concepts • Mission Requirements (brief, top level) • Concept of Operations • Expected Results • Section 2: Design Overview • Design Overview • Functional Block Diagrams • Payload Layout • RockSat-X 2011 User’s Guide Compliance • Shared Deck Space (if applicable)

5. CoDR Presentation Contents • Section 3: Management • Team Organization • Schedule • Budget • Mentors (Faculty, industry) • Section 4: Conclusions jessicaswanson.com

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

7. 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. Mission Overview: Mission Requirements • Project requirements  derived from mission statement • Break down into mission objectives, system level objectives (example on following slide) • Minimum success criteria • What is the least amount of data you can collect that will still constitute a success? crestock.com

9. Mission Overview: Mission Requirements • The payload shall conform to the requirements set forth in the 2011 RockSat-X User Guide • The system shall measure the numerical density of charged particles in the upper atmosphere from 30±5 km to 50±5 km • The system should measure the numerical density of charged particles in the upper atmosphere from 30±1 km to 50±1 km Shall is legally binding and indicative of minimum success Should are an ideal metrics of performance that would lead to better science/performance, but are not required for minimum success. crestock.com

10. Mission Overview: Concept of Operations • Based on science objectives, diagram of what the payload will be doing during flight, highlights areas of interest • Example on following 2 slides

11. Example ConOps Altitude t ≈ 1.7 min Altitude: 95 km Event B Occurs t ≈ 4.0 min Altitude: 95 km Event C Occurs t ≈ 1.3 min Altitude: 75 km Event A Occurs Apogee t ≈ 2.8 min Altitude: ≈115 km t ≈ 4.5 min Altitude: 75 km Event D Occurs End of Orion Burn t ≈ 0.6 min Altitude: 52 km t ≈ 5.5 min Chute Deploys -G switch triggered -All systems on -Begin data collection t = 0 min t ≈ 15 min Splash Down

12. Example ConOps 1. Launch Telemetry/GPS begins 2. Launch to Apogee Telemetry/GPS continues 3. Apogee Nose cone separation Skin separation De-spin to TBD rate Option to align with B Field Telemetry/GPS continues 4. Descent Telemetry/GPS continues 5. Chute Deploy Telemetry/GPS continues 6. Landing Telemetry/GPS terminates Payloads recovered 3 4 5 2 1 6

13. Mission Overview: 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

14. Design Overview • Utilization of heritage elements (designs/features used on previous flights) defined. How will you be modifying them for your specific mission? • Will you be using stacked configuration, makrolon, same type of sensor as a previous flight? • Major technology dependencies: what kind of sensors will you need? • What do the capabilities of the sensors need to be? (ex. For an optical sensor, what wavelengths should it be able to detect? This is based on project requirements) clipartguide.com

15. Design Overview: Functional Block Diagrams • Functional block diagram • Shows how systems interact with each other • Mechanical – will show how payload is configured, especially if there are sensors external to the payload • Electrical – shows how data will be recorded, stored • Example on following slide blogs.msdn.com

16. Example FBD (electrical) Power G-Switch RBF (Wallops) Z Accelerometer Microcontroller ADC X / Y Accelerometer Flash Memory Dust Collector Current Measuring Device ADC Power Data Dust Collector

17. Example FBD – mechanical/system (rough diagram) Makrolon plate RockSat-X Deck Sensor(s) Electronics - storing data (mounted to plate) Electronics – controlling sensor (mounted to plate) Power Mounts to RockSat-X Payload Deck Hardware mounted to RockSat-X Deck

18. Design Overview: Payload Layout • Initial drawings / layout in canister • Preliminary idea of how many plates you will use (if you plan on using plate configuration), else idea of where and how things will be mounted • Show where electronics boards (~how many?), sensors, power will be mounted • A little more organized than system block diagram (actually shows standoffs, spacing between elements) This is NOT required at the CoDR level. If you can include this, you are ahead of the game! classymommy.com

19. Design Overview: RockSat-X 2011 User’s Guide Compliance • Rough Order of Magnitude (ROM) mass estimate • Estimate on payload dimensions (will it fit in the payload space?) • Deployables/booms? • How many ADC lines? • Do you understand the format? • Asynchronous use? • Do you understand the format? • Parallel use? • Do you understand the format? • Power lines and timer use? • What do you know so far? • CG requirement • Do you understand the requirement • Are you utilizing high voltage?

20. Design Overview: Shared Can 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)? grandpmr.com

21. Management • Team organization chart • Preliminary schedule for the semester • Monetary budget • Team mentors (industry, faculty)? Don’t let the schedule sneak up on you!

22. Conclusion • Restate mission • Issues, concerns, any questions • Plan for where you will take your design from here? • Anything you need to investigate further? • Are you ready make subsystem and lower level requirements to come up with a rough-draft design for PDR?