Transcript Team Name

Team Name
Critical Design Review
University/Institution
Team Members
Date
RockSat-C 2013
CDR
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 contains all of the
information you are required to convey at
the CDR level. If you have questions, please
don’t hesitate to contact me directly:
[email protected]
720-341-3552
**Special thanks to Shawn Carroll for the
baseline template!**
RockSat-C 2013
CDR
2
Purpose of CDR
• Confirm that:
gnurf.net
– The design is mature enough to move into
the fabrication phase
– Final analysis on systems that weren’t
prototyped or needed further analysis is
complete and accurate
– Results of prototyping suggest the system
will meet project requirements
– Manufacturing plan is in place
– Testing plan is in place and sufficient to
ensure system functionality and performance
in-flight
– PDR risks have been walked down and to the
left on the risk matrix (if possible)
– Project meets requirements of RockSat-C
user guide
– The project is on track to be completed on
time and within budget
RockSat-C 2013
CDR
3
**Presenting the CDR**
• 50%: This presentation focuses on WHY you
designed the payload the way you did
• Most obvious explanation is so that it meets
your mission requirements, but you need to
explain HOW it does this
– Don’t forget about off ramps, de-scopes, and design
changes How and Why
– Think about how to explain each design element
from the how and why aspect
• 50%: The other half of the presentation is
the execution of how you are going to do all
of this, don’t forget about this HALF!
gnurf.net
RockSat-C 2013
CDR
4
CDR Presentation Content
• Section 1: Mission Overview
–
–
–
–
–
Mission Overview
Organizational Chart
Theory and Concepts
Concept of Operations
Expected Results
• Section 2: Design Description
–
–
–
–
Requirement/Design Changes Since CDR
De-Scopes/Off-Ramps
Mechanical Design Elements
Electrical Design Elements
RockSat-C 2013
CDR
5
CDR Presentation Contents
• Section 3: Prototyping/Analysis
– Analysis Results
• Interpretation to requirements
– Prototyping Results
• Interpretation to requirements
– Detailed Mass Budget
– Detailed Power Budget
– Detailed Interfacing to Wallops
jessicaswanson.com
• Section 4: Manufacturing Plan
– Mechanical Elements
– Electrical Elements
– Software Elements
RockSat-C 2013
CDR
6
CDR Presentation Contents
• Section 5: Testing Plan
– System Level Testing
• Requirements to be verified
– Mechanical Elements
• Requirements to be verified
– Electrical Elements
• Requirements to be verified
– Software Elements
• Requirements to be verified
• Section 6: Risks
– Risks from PDR to CDR
• Walk-down
– Critical Risks Remaining
RockSat-C 2013
CDR
7
CDR Presentation Contents
• Section 7: User Guide Compliance
– Compliance Table
– Sharing Logistics
• Section 8: Project Management Plan
– Schedule
– Budget
• Mass
• Monetary
– Work Breakdown Structure
RockSat-C 2013
CDR
8
Mission Overview
Name of Presenter
RockSat-C 2013
CDR
9
Mission Overview
• Mission statement
• Break mission statement down into your
overall mission requirements
– Here you should also include what ports you
will need access to
• What do you expect to discover or prove?
• Who will this benefit/what will your
data be used for?
RockSat-C 2013
CDR
10
Organizational Chart
Project Manager
Shawn Carroll
System Engineer
Riley Pack
Faculty Advisor
Chris Koehler
CFO
Shawn Carroll
Safety Engineer
Chris Koehler
Faculty Advisory
Emily Logan
Sponsor
LASP
Testing Lead
Jessica Brown
EPS
David Ferguson
Riley Pack
STR
Tyler Murphy
Aaron Russert
DEP
Aaron Russert
Shawn Carroll
PM
Kirstyn Johnson
Elliott Richerson
• What subsystems do you have?
• Who works on each subsystem?
– Leads?
• Don’t forget faculty advisor/sponsor(s)
RockSat-C 2013
CDR
11
Concept of Operations
• Based on science objectives, diagram of
what the payload will be doing during
flight, highlights areas of interest, ie:
– If you’re looking at certain parts of the
atmosphere mark the time
– If you are waiting for particular events in
flight, mark those on the diagram with a time
(approximate)
• Show a parallel flow from the point of view
of your payload, noting what events will
occur when, any moving parts or changing
states
RockSat-C 2013
CDR
12
Expected Results
• These need to be updated to finalized
numbers; research here should be
complete
• 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
RockSat-C 2013
CDR
13
Design Description
Name of Presenter
RockSat-C 2013
CDR
14
De-Scopes and Off-Ramps
• Has the scope of your project changed?
– i.e. have you eliminated any mission objectives to
complete the project on time?
• If there are portions of your project with high
risk, do you have “off-ramps” in case you have
schedule/budget constraints?
– An off-ramp is something you can remove, or not
do, with your payload to reduce complexity while
still meeting some of your mission requirements
• This information should require multiple slides
RockSat-C 2013
CDR
15
Mechanical Design Elements
• Show final design WITH LABELS AND
DIMENSIONS
– Please show isometric/angle view of each
plate/major component (if you are not using a plate
layout) (multiple slides)
– Please show the design in canister and out (1-2
slides)
• If you have made changes since PDR, discuss WHY you
made them and how it affects your mission requirements
• If you are using a port, show at minimum
diagrams of the interface, drawings preferred
• Was anything not modeled?
• How do you know this design will survive flight?
RockSat-C 2013
CDR
16
Electrical Design Elements
• Please show finalized block diagrams, state how many
PCBs/breadboards you will use and what each one will do,
sensors they will have (multiple slides)
– Do you have schematics? If you show them, talk about them. If you
don’t, be sure to at least answer the question!
• Any changes to this system since PDR? (1-2 slides)
– How does this affect your mission requirements?
– What has been finalized that wasn’t at PDR?
• Will you activate with command line or gswitch/LEDEX?
(this must be it’s own slide, WITH A SCHEMATIC)
– Command line will activate at T-2 unless a team has a specific need
for an earlier activation
RockSat-C 2013
CDR
17
Software Design Elements
• Show a software flow diagram
• Show pseudo code if possible
• Discuss major functions – inputs,
outputs, purpose, etc
• ** Software is the biggest showstopper
in this program. Begin developing your
software very early, and test test test!!**
RockSat-C 2013
CDR
18
Prototyping/Analysis
Name of Presenter
RockSat-C 2013
CDR
19
Analysis Results
• What was analyzed/tested since PDR?
– i.e. Finite Elements Analysis, Aerodynamic
Loading, Boom Extension…
• What are the key results?
• How do these results relate to the project
requirements?
RockSat-C 2013
CDR
20
Prototyping Results
• What was prototyped?
– i.e. electrical system bread boarded, boom arm,
payload foam mock-up…
– What are the key results?
• How do these results relate to the project
requirements?
RockSat-C 2013
CDR
21
Detailed Mass Budget
ExampleSat Mass Budget
• Present your
subsystem
masses and total
mass similar to
what is given at
right.
Subsystem
Sensors
Container
Standoffs
Actuators
…
…
…
…
Total
Over/Under
RockSat-C 2013
CDR
Total Mass (lbf)
2
8
12
9
31
(1.00)
22
Power Discussion
ExampleSat Power Budget
Subsystem
STR
DEP
EPS
PM
…
…
…
…
Voltage (V)
Current (A)
0
12
28
28
Time On (min)
0
0.4
0.3
0.9
0
2
20
8
Total (A*hr):
Amp-Hours
0.000
0.013
0.100
0.120
0.233
• Show an approximation of how much power
each system will use vs. how much is available
• Discuss how your power supply will be sufficient
RockSat-C 2013
CDR
23
Manufacturing Plan
Name of Presenter
RockSat-C 2013
CDR
24
Mechanical Elements
• What needs to be manufactured?
• What needs to be procured?
• Present a plan/schedule to get it done in
time for testing.
•Don’t forget margin!
• SLIDE COUNT: Your Discretion
RockSat-C 2013
CDR
25
Electrical Elements
• What needs to be manufactured/soldered?
• How many revisions of the electronics do
you anticipate? (Be realistic!)
• What needs to be procured?
• Present a plan/schedule to get it done in
time for testing.
•Don’t forget margin!
• SLIDE COUNT: Your Discretion
RockSat-C 2013
CDR
26
Software Elements
• What discrete blocks of code need to be
completed?
• Which blocks depend on other blocks?
• Present a plan/schedule to get it done in
time for testing.
•Don’t forget margin!
• SLIDE COUNT: Your Discretion
RockSat-C 2013
CDR
27
Testing Plan
Name of Presenter
RockSat-C 2013
CDR
28
Mechanical Testing
• Consider subsystem level requirements to
be verified (mass/volume/vibration…)
• Present a brief overview of the tests you
need to conduct to verify these requirements
• What are you testing
• How will you know if your system passed?
• When will these tests be performed?
• SLIDE COUNT: Your Discretion
RockSat-C 2013
CDR
29
Electrical Testing
• Consider subsystem level requirements to
be verified (sample rate/deployment tests…)
• Present a brief overview of the tests you
need to conduct to verify these requirements
• What are you testing
• How will you know if your system passed?
• When will these tests be performed?
• SLIDE COUNT: Your Discretion
RockSat-C 2013
CDR
30
Software Testing
• Consider how software and electrical
depend on each other for testing
• Present a brief overview of what portions of
the code need to be completed to test the
electrical system at its various testing
points
• When will these tests be performed?
• SLIDE COUNT: Your Discretion
RockSat-C 2013
CDR
31
System Level Testing
• Consider system level integrations that you will have to
do
• Mechanical integrations (fit-checks), electrical –
sensor integration, components to structure
integration, etc
• Present a brief overview of the tests you need to conduct
to verify these requirements
• Describe what you will be measuring, what you are
looking for, how you will know you passed
• When will these tests be performed?
• WHERE will these tests be performed?
• What will you need? Who will be doing it?
• SLIDE COUNT: Your Discretion
RockSat-C 2013
CDR
32
Risks
Name of Presenter
RockSat-C 2013
CDR
33
Risk Walk-Down
RSK.3
RSK.1
• What were your biggest
risks at PDR? (remind me)
RSK.4
RSK.2
RSK.1
• What have you done to
mitigate them?
• Hopefully you have
moved them to the lower
left side of the risk chart
as a result (walk-down)
RSK.3
Consequence
RSK.2
RSK.4
Possibility
RockSat-C 2013
CDR
34
Risk Walk-Down
RSK.1
RSK.3
RSK.2
• What are your NEW
top 3 risks since
PDR?
Consequence
• Do you have plans to
walk them down?
• Are there any risks
you just have to
accept?
• Why?
Possibility
RockSat-C 2013
CDR
35
User Guide Compliance
Name of Presenter
RockSat-C 2013
CDR
36
User Guide Compliance
• Mass – what is your mass, + mass of
canister
• CG within 1”x1”x1” envelope? How have
you checked this/
– You should be at the point where you can at
least check through solidworks
• Batteries? (rechargeable or not)
• RESTATE: activation type, plans for highV
if applicable, ports required
RockSat-C 2013
CDR
37
Sharing Logistics (if applicable)
• 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)?
RockSat-C 2013
CDR
grandpmr.com
38
Project Management Plan
Name of Presenter
RockSat-C 2013
CDR
39
Schedule
• Your schedule should be VERY detailed at this point – break it down by
months, with specific days for deadlines:
• When will you procure things?
• Major tests listed
• Major integrations listed
• Next semesters interim reviews included
• The more the plan for, the fewer surprises there will be!
• This can be a WBS, Schedule List, or another method of presentation
Don’t let the schedule
sneak up on you!
RockSat-C 2013
CDR
40
Budget
• Present a somewhat detailed budget
• A simple Excel spreadsheet will do
• It is suggested that you add in at least a 10% margin at this point
Margin:
0.10
Budget:
$1,300.00
ExampleSat
Item
Supplier
Estimated, Specific Cost Number Required
Motor Controller
DigiKey
$150.00
PM
LASP
$0.00
Microcontroller
DigiKey
$18.00
Printed Circuit Boards Advanced Circuits
$33.00
Misc. Electronics (R,L,C) DigiKey
$80.00
Boom Material
onlinemetals.com
$40.00
Probe
LASP
$0.00
Testing Materials
???
$200.00
Last Update:
Toal Cost
2
1
3
3
3
2
1
1
Notes
$300.00 1 for testing
$0.00 LASP mentor deserves shirt
$54.00 3 board revs
$99.00 3 board revs
$240.00 3 board revs
$80.00 1 test article
$0.00
$200.00 Estimated cost to test system
Total (no margin):
Total (w/ margin):
RockSat-C 2013
CDR
9/30/2010 11:50
$973.00
$1,216.25
41
Project Summary
• Remaining issues (hopefully none)
• Areas of concern
– What are you worried about?
– Be honest, now is the best time to go over it
RockSat-C 2013
CDR
42
Conclusion
• What’s your plan of action at this point?
• What are you going to try to get done
before winter break?
RockSat-C 2013
CDR
43