2013
CDR
CDR Delieverables
• In addition to this presentation, each school must include the following by December 10th
• Mechanical drawings in pdf format• Electrical schematics in pdf format• Signed copies of the Power and Telemetry ICDs in
pdf format• Completed Power Budget in xls format• Completed Pin Assignments in xls format• Completed Timer Event matrix in xls format• Be sure to place all these files, including ppt
presentation in your DropBox Pony Express folder by COB on December 10, 2012
2
2013
CDR
User Notes
• You may 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:
3
2013
CDR
Purpose of CDR
• Confirm that:– 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– Project meets requirements of RockSat-X user’s
guide– The project is on track to be completed on time and
within budget
4
2013
CDR
CDR Presentation Outline
5
• Section 1: Mission Overview• Section 2: Design Description• Section 3: Subsystem Design• Section 4: Prototyping/Analysis• Section 5: Manufacturing Plan• Section 6: Testing Plan• Section 7: User Guide Compliance• Section 8: Project Management Plan
2013
CDR
Mission Overview
• Mission statement• What do you expect to discover or
prove?• Who will this benefit and/or what will
your data be used for?
7
2013
CDR
Theory and Concepts
• Give a brief overview of the underlying science concepts and theory
• What other research has been performed in the past?– Results?
8
2013
CDR
Mission Requirements:
• Project requirements derived from mission statement– Break down into mission objectives, system
level objectives– Please show traceability and linkages
– See example on following slide
9
crestock.com
2013
CDR
Success Criteria:
– Define Minimum Success: What is the least amount of data you can collect that will still constitute a success?
– Comprehensive Success: Under ideal conditions, what would constitute comprehensive mission success?
11
2013
CDR
Expected Results
12
• 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
2013
CDR
Concept of Operations
• Based on science objectives, describe what the payload will be doing during flight and highlights areas of interest
• Include all significant events during your flight• RS-X 2012 Mission timeline included on following
slide for guidance• You may used the example on following slide
updated with your mission events• Complete your Timer Events Matrix in xls format
and submit• Include screen shot of this matrix in your
presentation
13
2013
CDR
Concept of Operations
14
Event Time On Dwell Event Description
GSE 1 T-180 sec 540 sec Minutes before launch. Start on the computer for the experiments.
GSE 2 T-180 sec 540 sec Minutes before launch. Start on the computer for the experiments.
TE-NR 1 T+000 sec 360 sec Launch
TE-NR 2 T+000 sec 360 sec Bring more power to RGA's.
TE-NR 3 T+000 sec 360 sec Bring more power to RGA's.
TE-R T+000 sec 360 sec Bring more power to RGA's.
• Example of Timer Events Matrix for presentation
2013
CDR
Example ConOps
t ≈ ???
Altitude: ?? km
Event A Occurs
t ≈ 876 sec
Splash Down
t ≈ ???
Altitude: ?? km
Event B Occurs
-G switch triggered
-All systems on
-Begin data collection
t = 0 min
t ≈ ???
Altitude: ?? km
Event C OccursApogee
t ≈ 199.7 sec
Altitude: ≈153 km
End of Malemute Burn
t ≈ 28.7 sec
Altitude: 17.2 km
t ≈ ???
Altitude: ?? km
Event D Occurs
Altitude
t ≈ 454.9 sec
Chute Deploys
2013
CDR
Changes Since PDR
19
• What major changes have you made since PDR?– Why were these changes made?
• Do these change any of your mission objectives/requirements?
2013
CDR
Design Overview: Functional Block Diagrams
• Functional block diagram– Show all major and minor subsystems and
how they are interconnected– Show voltage levels and data lines– Show all power and data storage– Show mechanical and electrical inhibits– Show Wallops interface (power/telemetry)
• 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
20
2013
CDR
Mechanical Design Elements
22
• Give me a brief overview of your final mechanical design
• Mechanical drawings should be included• Solid models (labeled) with many views
should be included• Any stress/strain analysis?• Material choices?
2013
CDR
Electrical Design Elements
24
• Give me a brief overview of your final electrical design
• Overall electrical schematics should be presented
• Sensor specification and how they meet your requirements
2013
CDR
Software Design Elements
26
• Give me a brief overview of your final software design
• Software flow diagram should be included• Could include State diagrams• Could include function overviews
(input/output)
2013
CDR
De-Scopes and Off-Ramps
27
• If there are portions of your project with lots of risk, do you have “off-ramps” in case you run into schedule/budget constraints?
• Describe these “De-Scopes” and “off-ramps” that may be used in the future
2013
CDR
Subsystem Design
29
• Start with your organization chart with each of your subsystems labeled
• Detail each subsystem’s final design• Each subsystem should be separated on to
its own slide• Each subsystem should cover:
– Drawing– Power and data– Mechanical and Electrical Interfaces– Weight– Critical technology used and current issues
grandpmr.com
2013
CDR
Organizational Chart
• What subsystems do you have?• Who works on each subsystem?
– Leads?• Don’t forget faculty advisor/sponsor(s)
30
Project ManagerShawn Carroll
System EngineerRiley Pack
CFOShawn Carroll
Faculty AdvisorChris Koehler
SponsorLASP
Faculty AdvisoryEmily Logan
Safety EngineerChris Koehler
Testing Lead Jessica Brown
EPSDavid Ferguson
Riley Pack
STRTyler Murphy
Aaron Russert
DEPAaron RussertShawn Carroll
PMKirstyn JohnsonElliott Richerson
2013
CDR
Analysis Results
32
• What was analyzed?– i.e. Finite Elements Analysis, Aerodynamic
Loading, Boom Extension, Link Budgets…
• What are the key results?• How do these results relate to the
project requirements?
2013
CDR
Prototyping Results
33
• 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?
2013
CDR
Detailed Mass Budget
34
ExampleSat Mass BudgetSubsystem Total Mass (lbf)
STR 2DEP 8EPS 12PM 9… … … … Total 31Over/Under (1.00)
• Present your subsystem masses and total mass similar to what is given at right.
• Mass of plate is 3.425 pounds
2013
CDR
Detailed Power Budget
35
• USE Power Budget xls file• Include a screenshot in your presentation and the actual excel file with
your CDR package• I am most interested in total amp-hours since each payload space is
allowed 1 Ah. • Voltages and currents should also be included.
ExampleSat Power BudgetSubsystem Voltage (V) Current (A) Time On (min) Amp-Hours
STR 0 0 0 0.000DEP 12 0.4 2 0.013EPS 28 0.3 20 0.100PM 28 0.9 8 0.120… … … …
Total (A*hr): 0.233Over/Under 0.77
2013
CDR
Wallops Interfacing: Power
36
Power Connector--Customer SidePin Function1 2 3 4 5 6 7 8 9
10 11 12 13 14 15
• USE Pin Assignment xls file• Include a screenshot in your
presentation and the actual excel file with your CDR package
• Fill-in the function side for your payload
• Check for consistency with User’s Guide
2013
CDR
Wallops Interfacing: Telemetry
37
• USE Pin Assignment ICD xls file
• Fill-in the function side for your payload
• Include a screenshot in your presentation and the actual excel file with your CDR package
• Check for consistency with User’s Guide
Telemetry Connector--Customer SidePin Function Pin Function
1 20 2 21 3 22 4 23 5 24 6 25 7 26 8 27 9 28
10 29 11 30 12 31 13 32 14 33 15 34 16 35 17 36 18 37 19
2013
CDR
Mechanical Elements
39
• What will be manufactured?• What will be purchased?• Present a plan/schedule to get it done in
time for testing.•Include schedule margin.•Use of diagrams is encouraged
2013
CDR
Electrical Elements
40
• What needs to be manufactured/soldered?
• How many revisions of the electronics do you anticipate?
• What needs to be procured?• Present a plan/schedule to get it done in
time for testing.•Include schedule margin•Use of schematics is encouraged
2013
CDR
Software Elements
41
• 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.•Include schedule margin
2013
CDR
System Level Testing
43
• Consider system level requirements that need to be verified
• Present a brief overview of the tests you need to conduct to verify these requirements
• When will these tests be performed?
2013
CDR
Mechanical Testing
44
• 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
• When will these tests be performed?• Call-out any deployment tests and how
they will be preformed• Discuss any mechanical inhibits you may
need for Wallops testing
2013
CDR
Electrical Testing
45
• 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
• When will these tests be performed?• Callout any high voltage components• Callout any internally powered components
and how they will be tested• Discuss any electrical inhibits you may need for Wallops
testing
2013
CDR
Software Testing
46
• 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?• Discuss any software inhibits you
may need for Wallops testing
2013
CDR
User Guide Compliance
48
• Use the following example to show your compliance with the RS-X 2013 User’s Guide
• Teams that are sharing, please fill out your school’s compliance only
2013
CDR
User Guide Compliance
49
Requirement Status/Reason (if needed)Center of gravity in 1" plane of
plate?1.2" currently
Max Height < 12"
Within Keep-Out
Using < 10 A/D Lines
Using/Understand Parallel Line Not Being Utilized
Using/Understand Asynchronous Line
9600 Baud
Using X GSE Line(s) 1 (per requirement)
Using X Redundant Power Lines 1 (per requirement)
Using X Non-Redundant Power Lines
2 (one extra)
Using < 1 Ah 1.1 (working on reducing)
Using <= 28 V 200 V (Will conformal coat)
2013
CDR
Sharing Logistics
50
• 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)?
• Discuss number of meetings you have had with sharing school
• POC for sharing school and their contact info
2013
CDR
Schedule
52
• Your schedule should be VERY detailed at this point• 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!
• Format:• Gant charts• Excel spreadsheet• Simple list• Whatever works for you!
Don’t let the schedule sneak up on you!
2013
CDR
Budget
53
- Present a very top-level budget (not nut and bolt level)- Include launch fee and deposit amounts AND include status of each- Include estimates for travel in June and August- Include spare parts and margin in you hardware budget
Margin: 0.25 Budget: $1,300.00 Last Update: 9/30/2010 11:50ExampleSat
Item Supplier Estimated, Specific Cost Number Required Toal Cost NotesMotor Controller DigiKey $150.00 2 $300.00 1 for testingPM LASP $0.00 1 $0.00 LASP mentor deserves shirtMicrocontroller DigiKey $18.00 3 $54.00 3 board revsPrinted Circuit Boards Advanced Circuits $33.00 3 $99.00 3 board revsMisc. Electronics (R,L,C) DigiKey $80.00 3 $240.00 3 board revsBoom Material onlinemetals.com $40.00 2 $80.00 1 test articleProbe LASP $0.00 1 $0.00 Testing Materials ??? $200.00 1 $200.00 Estimated cost to test system
Total (no margin): $973.00Total (w/ margin): $1,216.25
2013
CDR
Team Availability Matrix
54
• Please submit your availability matrix for Spring 2013 semester• Please state the time-zone on your matrix• All times are available for Chris between 7 AM – 5 PM MST
2013
CDR
Contact Matrix
55
• You can copy and paste your contact spreadsheet here• Please re-verify participants US Person Status