Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR)

1. Team NameDesign Review (DR)& Individual Subsystem Test Review (ISTR) University/Institution Team Members Date

2. Deliverables • In addition to this presentation, each school must include the following by February 18th: • FINAL Mechanical drawings in pdf format • FINAL Electrical schematics in pdf format • FINAL Signed copies of the Power and Telemetry ICDs in pdf format • UPDATED Power Budget in xls format • FINAL Pin Assignments in xls format • FINAL Timer Event matrix in xls format • Be sure to place all these files, including your ppt presentation in your DropBox Pony Express folder by COB on February 18th, 2013

3. User Notes • You may reformat this 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 this point in the project. If you have questions, please contact me directly: rocksatx@gmail.com or 303-492-4750

4. Purpose of DR/ISTR PLEASE READ: For RS-X 2013, I am combining details needed for the DR at Wallops in March with the ISTR review. I am doing this because even after Post-CDR, I still do not have a clear understanding of each team’s final design. The purpose of the DR with Wallops is to capture the final design of both the rocket systems and the payloads (you) that are going to fly. The purpose of the ISTR is for me to understand how much of your design is built and how much of your design is tested. During RS-X 2012, each team had to complete a second ISTR before moving onto their Full System Test Review, where all subsystems have been tested and are now being tested together as a system. This review is scheduled to take place around March 18th, one month after this review. YOU MUST ADDRESS AND FOLLOW EVERY ASPECT OF THIS TEMPLATE DURING YOUR TEAM’S REVIEW THE WEEK OF FEBRUARY 18th. PLEASE CONTACT ME IF YOU HAVE ANY QUESTIONS

5. Presentation Outline • Section 1: Mission Overview • Section 2: Final Design Description • Section 3: Project Management Update • Section 4: Hardware Procurement Status • Section 5: Individual Subsystem Testing Results • Section 6: Full System Testing Plan • Section 7: User Guide Compliance

6. 1.0 Mission Overview Name of Presenter

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

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

9. 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 • Update the the table on the next slide of this template

10. Concept of Operations • Example of Timer Events Matrix for presentation • Update this for your presentation as it applies to your team

11. Example ConOps Altitude t ≈ ??? Altitude: ?? km Event B Occurs t ≈ ??? Altitude: ?? km Event C Occurs t ≈ ??? Altitude: ?? km Event A Occurs Apogee t ≈ 199.7 sec Altitude: ≈153 km t ≈ ??? Altitude: ?? km Event D Occurs End of Malemute Burn t ≈ 28.7 sec Altitude: 17.2 km t ≈ 454.9 sec Chute Deploys -G switch triggered -All systems on -Begin data collection t = 0 min t ≈ 876 sec Splash Down

12. Concept of Operations

13. Payload Location • Please confirm your mounting location

14. 2.0 Final Design Description Name of Presenter

15. Functional Block Diagram: • FINAL 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

16. Example Functional Block Diagram

17. Example Functional Block Diagram

18. Mechanical Design: • Present your FINAL mechanical design • Many views of your solid models (labeled) • These will be used for your pre-launch inspection by Wallops personnel in June/August • Shared decks must also include views of solid models for integrated, shared deck • Updated Mass Budget • List of materials used in mechanical design • Dimensioned drawings are not required in presentation but are required as a deliverable (see slide 2 above) • Address any Hazardous Mechanical items

19. Example of Views

20. Example of Views Waterproof Aluminum Box (without sides) Nitric Oxide Sensor Piezo Dust Detector S-Bar Release Mechanism Ballast Plate NASA Payload Plate

21. Post Amp Boards Femto Amplifier Example of Views Power Board Transceiver Data Loggers Memsense IMU VectorNav IMU

22. Example of Views

23. Detailed Mass Budget • Present your subsystem masses and total mass similar to what is given at right. • Mass of plate is 3.425 pounds • Show how you meet your 30 pound requirement

24. Materials List: • Detail all materials used in your design • May use a table to capture this information • Capture all materials used in mission (i.e. aerogel, 6061 Aluminum, etc) • Types of bolts, nuts, washers, etc (i.e. stainless bolts)

25. Hazardous Mechanical Items: • Identify all materials that may be considered hazardous • Identify all mechanical operations that may be considered hazardous (stored energy, deployments, etc) • Identify all mechanical components that may hazardous or interfere with other payloads or rocket systems (magnets, transmitters, items that change your CG or MOI during the flight)

26. Electrical Design: • Present your FINAL Electrical Design • Include all electrical schematics • Include Updated Power Budget • Include Updated Pin Assignments • Identify any high voltage components • Identify any hazardous electrical items in your design

27. Example Electrical Schematics

28. Example Electrical Schematics

29. Example Electrical Schematics

30. Example Electrical Schematics

31. Updated Power Budget • 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.

32. Pin Assignments: Power • 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

33. Pin Assignments: Telemetry • 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

34. Hazardous Electrical Items: • Identify any high voltage items/components • Identify any operational hazards with your electrical design

35. Software Design: • Give me a brief overview of your software design • Software Flow Diagram must be included • Could include State diagrams • Could include function overviews (input/output)

36. Example Software Flow Diagram: Begin collecting data from sensors Arduino Pro Rocket casing off? No Data from proximity sensor Retract linear actuator Yes Altimetry data from pressure sensor Yes Reached 95 km? No Reached 95 km? Yes No Altimetry data from pressure sensor Extend linear actuator

37. De-Scopes and Off-Ramps • 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

38. 3.0 Project Management Update Name of Presenter

39. Project Management Update: • Include Team Picture • Updated org chart • Updated schedule • Include details leading up to the June 18th testing in Virginia • Biggest Worries and Concerns Slide

40. Example Team Picture

41. Example Organizational Chart Project Manager Marie Hepfer Lead System Engineer + Aerogel Science Chris Mogni GPS Team Lead Krysti Papadopoulos Systems Engineer + Lead Electrical Engineer Corrie Russell Aerogel Science Nick Lybarger Lead Aerogel Engineer Kristy Webber Aerogel Build Lead Lauren Powers GPS Aerospace Engineer Brianna Brassard Faculty Advisor Darren Waugh Organization JHU EPS Department Aerogel Aerospace Engineer Mazi Wallace Mentors Ethan Miller JonnathanFenske Organization JHU APL

42. Example Schedule 12/11/2012 Critical Design Review (CDR) Teleconference 12/15/2012 Post CDR Action Item Generation 1/18/2013 Final Down Select—Flights Awarded TBA Wallops DR 01/28/2013 Post CDR Action Item Review 02/18/2013 First Installment Due 02/18/2013 Individual Subsystem Testing Reports Due 02/19/2013 Individual Subsystem Testing Reports Teleconference 02/25/2013 Experiment Decks and Connectors Sent To Customers 03/18/2013 Payload Subsystem Integration and Testing Report Due 03/19/2012 Payload Subsystem Integration and Testing Report Teleconference 04/08/2013 Final Installment Due 04/15/2013 First DITL Test Report Due 04/16/2012 DITL 1 Teleconferences 05/06/2013 Weekly Teleconferences Begin 05/13/2013 Weekly Teleconference 1 05/13/2013 Second DITL Test Report Due 05/14/2013 Weekly Teleconference 2 (2nd DITL Presentations) 05/20/2013 Weekly Teleconference 3 05/27/2013 Weekly Teleconference 4 (Travel Logistics) 06/03/2013 Integration Readiness Review Packages (IRR) Due 06/04/2013 Integration Readiness Review Telecons with Wallops 06/18/2013 GSE Checkouts At Refuge 06/19>24/2013 Testing and Environmental With Wallops 07/01/2013 Weekly Teleconferences Resume 07/22/2013 Launch Readiness Review Packages (LRR) Due 07/23/2013 Launch Readiness Review Telecons with Wallops 08/01/2013 GSE Checkouts at Refuge Inn 08/02>07/2013 Final Integration at Wallops 08/08/2013 LAUNCH 08/09/2013 Contingency Launch

43. Worries and Concerns • List your biggest worries and concerns related to you project at this moment • Discuss your plans for mitigating these items

44. 4.0 Hardware Procurement Status Name of Presenter

45. Mechanical Elements • What has been manufactured/purchased? • What has not been manufactured/purchased?

46. Electrical Elements • What has been manufactured/solderd? • What still needs to be manufactured/soldered? • PCB revision status? • What electrical components are in house? • What electrical components still need to be procured?

47. Software Elements • What discrete blocks of code are completed? • Recommend refer to your software flow diagram above

48. 5.0 Individual Subsystem Testing Results Name of Presenter

49. Subsystem Review • List all the subsystems in your payload • Must match subsystems called out in your Functional Block Diagram above • You MUST use slides 50, 51, and 52 for each of the subsystems listed above • Don’t forget to discuss your software

50. Subsystem Name • Quick Status • What is complete/what has been tested? • What has not yet been checked out • Be honest because we all know things happen • Pictures! USE these 3 slides for each subsystem