Title: Team Name Conceptual Design Review
1Team NameConceptual Design Review
- University/Institution
- Team Members
- Date
2Template Notes
- You can reformat this template to fit your
design, but you must cover all 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 contact me directly - rocksatx_at_gmail.com
-
3Template Notes
- The Goals of the CoDR are to 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
4CoDR Presentation Content
- Section 1 Mission Overview
- Mission Statement
- 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 Users Guide Compliance
- Shared Deck Space (if applicable)
5CoDR Presentation Contents
- Section 3 Management
- Team Organization
- Schedule
- Budget
- Mentors (Faculty, industry)
- Section 4 Conclusions
jessicaswanson.com
6Mission Overview Mission Statement
- 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?
7Mission 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?
8Mission 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
9Example of Mission Requirements
- The payload shall conform to the requirements set
forth in the RockSat-X User Guide - The system shall measure the numerical density of
charged particles in the upper atmosphere from
305 km to 505 km - The system should measure the numerical density
of charged particles in the upper atmosphere from
301 km to 501 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
10Mission Overview Concept of Operations
- Based on science objectives, present a diagram of
what the payload will be doing during flight,
highlights areas of interest - Example on following 2 slides
11Example ConOps
12Example 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
13Mission 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
14Design 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)
15Design 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
- 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
16Example Functional Block Diagram
17Example FBD mechanical/system (rough diagram)
RockSat-X Deck
Sensor(s)
Electronics controlling sensor (mounted to
plate)
Hardware mounted to RockSat-X Deck
Mounts to RockSat-X Payload Deck
18Design Overview Payload Layout
- Initial drawings / layout on deck
- Preliminary idea of how and where things will be
mounted - Show where electronics boards (how many?),
sensors, power will be mounted - A little more organized than functional block
diagram (actually shows standoffs, spacing
between elements, etc)
This is NOT required at the CoDR level. If you
can include this, you are ahead of the game!
19Design Overview RockSat-X Users Guide Compliance
- Rough Order of Magnitude (ROM) weight 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?
20Design Overview Shared Can Logistics
- Who are you sharing with?
- Summary of your partners 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
21Management
- Team organization chart
- Preliminary schedule for the semester
- Monetary budget
- Team mentors (industry, faculty)?
Dont let the schedule sneak up on you!
22Conclusion
- 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?