1. Team Name Conceptual 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 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!
Can you find the easter egg in this presentation?

3. Confirm that: Purpose of CoDR
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 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
RockSat-C 2012 User’s Guide Compliance
Shared Can Logistics (if applicable)

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

6. Break mission statement down into your overall mission requirements
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

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

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

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

10. 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 (in-flight)
Minimum Success
Measure N concentrations and spin rate with two separate sensors

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

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

13. Example ConOps 3 4 5 2 1 6 1. Launch 2. Launch to Apogee 3. Apogee
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
4. Descent
5. Chute Deploy
6. Landing
Telemetry/GPS terminates
Payloads recovered
ACS Activated (if desired) 3 4 5 2 1 6

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

15. 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?
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)
clipartguide.com

16. 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?
Will you be using a similar structure, similar materials (makrolon), same type of sensor as a previous flight?
clipartguide.com

17. Design Overview: Functional Block Diagrams
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
1-2 slides
blogs.msdn.com

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

19. Example FBD – mechanical/system (rough diagram)
Connected to each other with standoffs
Makrolon plate
Electronics - storing data (mounted to plate)
Power
Makrolon plate
Sensor(s)
Electronics – controlling sensor (mounted to plate)
Mounts to lid of canister
Mounts to base of canister

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

21. Design Overview: RockSat-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?

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

23. Team organization chart – required
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!

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