2011 CDR Team Name Critical Design Review University/Institution Team Members Date 1.

Slides:



Advertisements
Similar presentations
TITLE OF PROJECT PROPOSAL NUMBER Principal Investigator PI’s Organization ESTCP Selection Meeting DATE.
Advertisements

RockSat-C 2012 CoDR Minnesota Sound Wreckers Conceptual Design Review University of Minnesota Alexander Richman Jacob Schultz Justine Topel Will Thorson.
Project Scope Management
Degree and Graduation Seminar Scope Management
Protocol & Test Review Spaceport America Student Launch University/Institution Team Members Date.
Proposal Analysis Review NMSGC Student Launch University/Institution Team Members Date.
Data Test Review Spaceport America Student Launch University/Institution Team Members Date.
Flight Readiness Review New Mexico Space Grant Consortium University/Institution Team Members Date.
Team Name Conceptual Design Review Team Members Date Fall 2011 Rev A
Colorado Space Grant Consortium Virginia Space Grant Consortium 1 University A University B Team # Logo 1 Logo 2.
RockSat-C 2012 SITR Full Mission Simulation Report University/Institution Team Members Date.
2011 CoDR Team Name Preliminary Design Review University/Institution Team Members Date 1.
Preliminary Design Review Northwest Nazarene University Advisor: Dr. Lawrence Chad Larson Ben Gordon Seth Leija David Vinson Zach Thomas Drew Johnson.
Individual Subsystem Testing Report Team Name University/Institution Team Members Date.
The New Jersey Space Grant Consortium at Stevens Institute of Technology and Rutgers University Mike Giglia, Ethan Hayon, Robert Hopkins, Jenny Jean, Mark.
Team Name Conceptual Design Review University/Institution Team Members Date.
RockSat-C 2011 SITR Payload Subsystem Integration and Testing Report University/Institution Team Members Date.
Team Name Final Presentation Team Members Date Fall 2010 Rev A
RockSat-C 2011 ISTR Payload Subsystem Integration and Testing Report Universities/Institutions Team Members Date.
2012 CoDR Nitric Oxide and Piezo Dust Detector Probe Conceptual Design Review Virginia Tech Presented by Stephen Noel November 18,
Team Name Conceptual Design Review Team Members Date Fall 2010 Rev A
Chapter 5: Project Scope Management
Team Name Critical Design Review Team Members Date Fall 2011 Rev A
Rock Sat-C Conceptual Design Review The New Jersey Space Grant Consortium at Stevens Institute of Technology and Rutgers University Mike Giglia, Ethan.
Team Name Final Presentation Team Members Date Rev
2011 CoDR Team Name Conceptual Design Review University/Institution Team Members Date 1.
University of Wyoming Dorin Blodgett, Kevin Brown, Heather Choi, Ben Lampe Eric Robinson, Michael Stephens, Patrick Weber October 7,
Chapter 5: Project Scope Management
Team Name Final Presentation Team Members Date. User notes –You may reformat to fit your design but make sure you cover the following points –You may.
Payload Subsystem Integration and Testing Report Team Name 1 Team Name 2 Team Name N Universities/Institutions Team Members Date.
Conceptual Design Review Metro State College of Denver Daniel Bass, Matt Hanley
Critical Design Review Team Name University/Institution Team Members Date.
LSU 07/07/2004Communication1 Communication & Documentation Project Management Unit – Lecture 8.
Miscellaneous Notes: This is a bare-bones template – make it fancier if you wish, but be sure to address at least the items listed here. Basically this.
2014 CDR Team Name Critical Design Review CDR CDR Delieverables 1.Mechanical drawings in pdf format 2.Electrical schematics in pdf format 3.Completed.
Team Name Flight Readiness Review (this is a bare-bones template – make it fancier if you wish, but be sure to address at least the items listed here)
Project Scope Management Process
User notes: –Please use this template to create your Proposal Analysis Review –You may reformat this to fit your design, but make sure you cover the information.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Individual Subsystem Testing Report New Jersey Space Grant Consortium with Rutgers University Stevens Institute of Technology 2/13/2012.
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1.
Team Name Final Presentation Team Members Date. User notes –You may reformat to fit your design but make sure you cover the following points –You may.
RBSP Radiation Belt Storm Probes RBSP Radiation Belt Storm Probes 12/25/20151 Flight Software Template for Instrument Critical Design Review Gary M. Heiligman.
Solar Probe Plus A NASA Mission to Touch the Sun March 2015 Instrument Suite Name Presenter's Name.
2013 CoDR Team Name Conceptual Design Review University/Institution Team Members Date 1.
Team Name Preliminary Design Review
RockSat-C 2013 FMSTR Full Mission Simulation Report University/Institution Team Members Date.
2013 CDR Team Name Critical Design Review University/Institution Team Members Date 1.
RockSat-C 2012 PDR Team Name Preliminary Design Review University/Institution Team Members Date 1.
Project Management Requirements Prof. Ralph Locurcio, PE Dr. Troy Nguyen, PE.
Notes on this template You may reformat this to fit your design, but make sure you cover the information requested in this template. Presentations should.
2016 FMSR Team Name Full Mission Simulation Review (FMSR) University/Institution Team Members Date 1.
2014 CoDR Team Name Conceptual Design Review University/Institution Team Members Date 1.
Preliminary Design Review Metro State College of Denver Matthew Hanley, Daniel Bass 14 November 2008.
Tethered Aerostat Program Preliminary Design Review Team Name Preliminary Design Review College Team Members Date.
Tethered Aerostat Program Critical Design Review Team Name Critical Design Review College Team Members Date 1.
Tethered Aerostat Program Concept Design Review Team Name Conceptual Design Review University/College Team Members Date.
Tethered Aerostat Program Concept Design Review College of Menominee Nation Conceptual Design Review College of Menominee Nation Marilyn Madosh, Larry.
2016 PDR Team Name Preliminary Design Review University/Institution Team Members Date 1.
2016 STR Team Name Subsystem Testing Review (STR) University/Institution Team Members Date 1.
RockSat-C 2013 SITR Payload Subsystem Integration and Testing Report University/Institution Team Members Date.
Team Name Preliminary Design Review
Team Name Critical Design Review
Peer Review Agenda (Suggested).
Project Management Process Groups
Team Name Conceptual Design Review
Team Name Conceptual Design Review
FRIDAY SLIDES TEMPLATE
<Your Team # > Your Team Name Here
Presentation transcript:

2011 CDR Team Name Critical Design Review University/Institution Team Members Date 1

2011 CDR 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:

2011 CDR Purpose of CDR Confirm that: –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-X user guide –The project is on track to be completed on time and within budget 3 gnurf.net

2011 CDR CDR Presentation Content 4 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 –Software Design Elements

2011 CDR CDR Presentation Contents 5 jessicaswanson.com Section 3: Prototyping/Analysis –Analysis Results Interpretation to requirements –Prototyping Results Interpretation to requirements –Detailed Mass Budget –Detailed Power Budget –Detailed Interfacing to Wallops Section 4: Manufacturing Plan –Mechanical Elements –Electrical Elements –Software Elements

2011 CDR CDR Presentation Contents 6 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

2011 CDR CDR Presentation Contents 7 Section 7: User Guide Compliance –Compliance Table –Sharing Logistics Section 8: Project Management Plan –Schedule –Budget Mass Monetary –Work Breakdown Structure

2011 CDR Mission Overview Name of Presenter 8

2011 CDR 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? 9

2011 CDR Organizational Chart What subsystems do you have? Who works on each subsystem? –Leads? Don’t forget faculty advisor/sponsor(s) 10 Project Manager Shawn Carroll System Engineer Riley Pack CFO Shawn Carroll Faculty Advisor Chris Koehler Sponsor LASP Faculty Advisory Emily Logan Safety Engineer Chris Koehler Testing Lead Jessica Brown EPS David Ferguson Riley Pack STR Tyler Murphy Aaron Russert DEP Aaron Russert Shawn Carroll PM Kirstyn Johnson Elliott Richerson

2011 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? 11

2011 CDR Concept of Operations Based on science objectives, diagram of what the payload will be doing during flight, highlights areas of interest Example on following slide 12

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

2011 CDR Expected Results 14 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

2011 CDR Design Description Name of Presenter 15

2011 CDR Changes Since PDR 16 What major changes have you made since PDR? –Why were these changes made? Do these change any of your mission objectives/requirements? SLIDE COUNT: Your Discretion

2011 CDR De-Scopes and Off-Ramps 17 Has the scope of your project changed at all? –i.e. have you eliminated any mission objectives to complete the project on time? If there are portions of your project with lots of risk, do you have “off-ramps” in case you run into schedule/budget constraints? SLIDE COUNT: Your Discretion

2011 CDR Mechanical Design Elements 18 Give me a brief overview of your final mechanical design You have a lot of freedom here –Present what you think is relevant Mechanical drawings should be included Any stress/strain analysis? Material choices? –SLIDE COUNT: 3-5

2011 CDR Electrical Design Elements 19 Give me a brief overview of your final electrical design You have a lot of freedom here –Present what you think is relevant Schematics? Sensor specification  relation to requirements SLIDE COUNT: 3-5

2011 CDR Software Design Elements 20 Give me a brief overview of your final software design You have a lot of freedom here –Present what you think is relevant Software flow diagram? State diagrams? Brief function overviews (input/output)? –SLIDE COUNT: 3-5

2011 CDR Prototyping/Analysis Name of Presenter 21

2011 CDR Analysis Results 22 What was analyzed? –i.e. Finite Elements Analysis, Aerodynamic Loading, Boom Extension… What are the key results? How do these results relate to the project requirements? SLIDE COUNT: Your Discretion

2011 CDR Prototyping Results 23 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? SLIDE COUNT: Your Discretion

2011 CDR Detailed Mass Budget 24 ExampleSat Mass Budget SubsystemTotal Mass (lbf) STR2 DEP8 EPS12 PM9 … … … … Total31 Over/Under(1.00) Present your subsystem masses and total mass similar to what is given at right.

2011 CDR Detailed Power Budget 25 Present your power budget (like above) I am most interested in total amp- hours since each payload space is allowed 1 Ah. Voltages and currents should also be included. Use whatever format makes sense to you. ExampleSat Power Budget SubsystemVoltage (V)Current (A)Time On (min)Amp-Hours STR DEP EPS PM … … … … Total (A*hr):0.233 Over/Under0.77

2011 CDR Wallops Interfacing: Power 26 Power Connector--Customer Side PinFunction Fill-in the function side for your payload I will check for consistency with User Guide

2011 CDR Wallops Interfacing: Telemetry 27 Fill-in the function side for your payload I will check for consistency with User Guide Telemetry Connector--Customer Side PinFunctionPinFunction

2011 CDR Manufacturing Plan Name of Presenter 28

2011 CDR Mechanical Elements 29 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

2011 CDR Electrical Elements 30 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

2011 CDR Software Elements 31 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

2011 CDR Testing Plan Name of Presenter 32

2011 CDR System Level Testing 33 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? SLIDE COUNT: Your Discretion

2011 CDR Mechanical Testing 34 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? SLIDE COUNT: Your Discretion

2011 CDR Electrical Testing 35 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? SLIDE COUNT: Your Discretion

2011 CDR Software Testing 36 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

2011 CDR Risks Name of Presenter 37

2011 CDR Risk Walk-Down 38 Consequence RSK.1 RSK.3 RSK.4 RSK.2 RSK.1RSK.3 RSK.4 Possibility What were your biggest risks at PDR? (remind me) 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)

2011 CDR Risk Walk-Down 39 Consequence RSK.1 RSK.3 RSK.2 Possibility What are your NEW top 3 risks since PDR? Do you have plans to walk them down? Are there any risks you just have to accept? Why?

2011 CDR User Guide Compliance Name of Presenter 40

2011 CDR User Guide Compliance 41 RequirementStatus/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)

2011 CDR Sharing Logistics 42 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)? grandpmr.com

2011 CDR Project Management Plan Name of Presenter 43

2011 CDR Schedule 44 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!

2011 CDR Budget 45 Present a somewhat detailed budget (doesn’t have to be nut and bolt level) A simple Excel spreadsheet will do Simply to ensure that you aren’t over budget going into manufacturing It is suggested that you add in at least a 10% margin at this point Margin:0.10Budget:$1,300.00Last Update:9/30/ :50 ExampleSat ItemSupplierEstimated, Specific CostNumber RequiredToal CostNotes Motor ControllerDigiKey$ $ for testing PMLASP$0.001 LASP mentor deserves shirt MicrocontrollerDigiKey$18.003$ board revs Printed Circuit BoardsAdvanced Circuits$33.003$ board revs Misc. Electronics (R,L,C)DigiKey$80.003$ board revs Boom Materialonlinemetals.com$40.002$ test article ProbeLASP$0.001 Testing Materials???$ Estimated cost to test system Total (no margin):$ Total (w/ margin):$1,216.25

2011 CDR WBS 46 Present a very top-level work break down schedule One can look up the tree for large scope goals One can look down the tree for dependencies Help each subsystem “see” the path ahead PMPEPSSTRPMDEP Obtain PM from LASP EEF Proposal for funding … Trade Studies Schematics Schematic Review ICDs First Revision of Boards … Trade Studies Order Materials Work Request Into Shop … Obtain PM from LASP EEF Proposal for funding … Obtain PM from LASP EEF Proposal for funding …

2011 CDR Issues, concerns, any questions Conclusion 47