Team Name Conceptual Design Review UniversityInstitution Team Members
Team Name Conceptual Design Review University/Institution Team Members Date Rock. Sat-C 2013 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 concepts, or don’t think you have time to include something, just let me know! rocksatprogram@gmail. com 720 -341 -3552 Rock. Sat-C 2013 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 2013 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: Conceptual Design Overview – – – Design Overview Functional Block Diagrams Payload Layout Rock. Sat-C 2012 User’s Guide Compliance Shared Can Logistics (if applicable) Rock. Sat-C 2013 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 2013 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? • 1 -3 slides Rock. Sat-C 2013 Co. DR 6
Example Mission Statement - Project E Developing a new sensor “The goal of Project E is to measure the variation of concentration of nitrogen in the atmosphere and the spin rate of the rocket using a single sensor” • Mission requirements from this statement: – Measure the concentration of N in-flight – Measure the spin rate of the rocket – Do this using the single sensor • Expect to prove the concentration is ~78% and spin rate is ~5 Hz (based on research from previous flights and other research) • The sensor developed will reduce future payload weight and complexity Rock. Sat-C 2013 Co. DR 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? • 1 -4 slides Rock. Sat-C 2013 Co. DR 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? – Defined by your team or faculty/industry mentors • 2 -3 slides crestock. com Rock. Sat-C 2013 Co. DR 9
Example “Project E” Mission Requirements • Objectives: Measure the concentration of N in-flight, measure the spin rate of the rocket in-flight, do this using the single sensor • System Requirements (from the objectives): – Sensor/instrument must be able to measure both N concentration and spin rates (single sensor) – Need a structure to support the instrument (in-flight) – Need a data collection system to store the measurements (inflight) • Minimum Success – Measure N concentrations and spin rate with two separate sensors Rock. Sat-C 2013 Co. DR 10
Mission Overview: Concept of Operations • Based on science objectives, diagram of what the payload will be doing during flight, highlights areas of interest – Data collection – when are you collecting data? – Altitudes of interest – what altitudes are you looking for specific data? – When does your payload stop collecting data? When does it turn off? • Example on following 2 slides • Typically 1 slide Rock. Sat-C 2013 Co. DR 11
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 2013 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 2013 Co. DR 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 • 1 -2 slides Rock. Sat-C 2013 Co. DR 14
Design Overview (many slides) • What are the major components in your design? – Structure: what might this look like? • Stack, single plate, circular, square, box, etc. – 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 2013 Co. DR 15
Design Overview Continued • Major Components (cont’d) – Electrical: what does your electrical system need to do? • Store data (memory), sampling sensors, provide power? ? • Will you use heritage elements (designs/features used on previous flights)? How will you be modifying them for your specific mission? clipartguide. com – Will you be using a similar structure, similar materials (makrolon), same type of sensor as a previous flight? Rock. Sat-C 2013 Co. DR 16
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 • Example on following slide • 1 -2 slides Rock. Sat-C 2013 Co. DR blogs. msdn. com 17
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 2013 Co. DR Power Data 18
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 2013 Co. DR 19
Design Overview: Payload Layout (1 -3 slides) • Initial idea of what your payload will look like • 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 – Block diagram shows how things are connected, Payload Layout shows where everything will be relative to each other in the actual payload classymommy. com Rock. Sat-C 2013 Co. DR 20
Design Overview: Rock. Sat-C 2013 User’s Guide Compliance • Here you address the requirements in the User’s Guide – Predicted mass – can be based on previous year, based on system overview (do you know how many plates you will 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 2013 Co. DR 21
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 2013 Co. DR grandpmr. com 22
Management (3 -4 slides) • Team organization chart – required – Having an appointed leader is extremely important for keeping the team organized! • Preliminary schedule for the semester • Monetary budget • Team mentors (industry, faculty)? Don’t let the schedule sneak up on you! Rock. Sat-C 2013 Co. DR 23
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 to make subsystem and lower level requirements to come up with a rough-draft design for PDR? Rock. Sat-C 2013 Co. DR 24
- Slides: 24