Team Name Conceptual Design Review UniversityInstitution Team Members
Team Name Conceptual Design Review University/Institution Team Members Date Rock. Sat-C 2011 Co. DR 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 has a lot of things to be included. With that said, if you are having trouble with any of it, or don’t think you have time to include it, just let me know! rocksatprogram@gmail. com 720 -341 -3552 Rock. Sat-C 2011 Co. DR 2
Purpose of Co. DR • Confirm that: gnurf. net – 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 Rock. Sat-C 2011 Co. DR 3
Co. DR Presentation Contents • Section 1: Mission Overview – – – Mission Overview Theory and Concepts Mission Requirements (brief, upper level) Concept of Operations Expected Results • Section 2: Design Overview – – – Design Overview Functional Block Diagrams Payload Layout Rock. Sat-C 2011 User’s Guide Compliance Shared Can Logistics (if applicable) Rock. Sat-C 2011 Co. DR 4
Co. DR Presentation Contents • Section 3: Management – Team Organization – Schedule – Budget – Mentors (Faculty, industry) • Section 4: Conclusions jessicaswanson. com Rock. Sat-C 2011 Co. DR 5
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? Rock. Sat-C 2011 Co. DR 6
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? Rock. Sat-C 2011 Co. DR 7
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 Rock. Sat-C 2011 Co. DR 8
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 Rock. Sat-C 2011 Co. DR 9
Example Con. Ops Altitude t ≈ 1. 7 min Altitude: 95 km t ≈ 1. 3 min Apogee t ≈ 4. 0 min Altitude: 75 km t ≈ 2. 8 min Altitude: 95 km Altitude: ≈115 km t ≈ 4. 5 min Altitude: 75 km 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 Rock. Sat-C 2011 Co. DR
Example Con. Ops 1. Launch ACS Activated (if desired) 3 Telemetry/GPS begins 2. Launch to Apogee Telemetry/GPS continues 4 3. Apogee Nose cone separation Skin separation De-spin to TBD rate Option to align with B Field Telemetry/GPS continues 5 2 4. Descent Telemetry/GPS continues 5. Chute Deploy Telemetry/GPS continues 6. Landing 1 Telemetry/GPS terminates Payloads recovered 6 Rock. Sat-C 2011 Co. DR 11
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 Rock. Sat-C 2011 Co. DR 12
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? clipartguide. com – 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 kind of based on science objectives) Rock. Sat-C 2011 Co. DR 13
Design Overview: Functional Block Diagrams • Functional block diagram – Shows how systems interact with each other – Mechanical – will show payload is configured, especially if there are sensors external to the payload – Electrical – shows how data will be recorded, stored blogs. msdn. com • Example on following slide Rock. Sat-C 2011 Co. DR 14
Example FBD (electrical) G-Switch Power RBF (Wallops) Z Accelerometer ADC Microcontroller X/Y Accelerometer Flash Memory Dust Collector Current Measuring Device ADC Dust Collector Rock. Sat-C 2011 Co. DR Power Data 15
Example FBD – mechanical/system (rough diagram) Connected to each other with standoffs Sensor(s) Electronics storing data (mounted to plate) Electronics – controlling sensor (mounted to plate) Power Makrolon plate Mounts to lid of canister Mounts to base of canister Rock. Sat-C 2011 Co. DR 16
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) classymommy. com Rock. Sat-C 2011 Co. DR 17
Design Overview: Rock. Sat-C 2011 User’s Guide Compliance • Predicted mass – can be based on previous year, based on system overview (do you know how many plates you’ll have, etc? ) • Predicted volume – will your payload fit in half a can (be careful about clearance), a whole can? • What types of activation will you probably need? – Designs for each need to be ready for PDR – How many types of activation will you need? Rock. Sat-C 2011 Co. DR 18
Design Overview: Shared Can Logistics • Who are you sharing with? – Summary of each 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)? • Who needs what kinds of ports? Rock. Sat-C 2011 Co. DR grandpmr. com 19
Management • • Team organization chart Preliminary schedule for the semester Monetary budget Team mentors (industry, faculty)? Don’t let the schedule sneak up on you! Rock. Sat-C 2011 Co. DR 20
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? Rock. Sat-C 2011 Co. DR 21
- Slides: 21