1. 2016 STR Team Name Subsystem Testing Review (STR) University/Institution Team Members Date 1

2. 2016 STR Deliverables In addition to this presentation, each school must include the following: 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 2

3. 2016 STR 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 3

4. 2016 STR Presentation Outline 4 Section 1: Mission Overview Section 2: Final Design Description Section 3: Hardware Procurement Status Section 4: Subsystem Testing Results Section 5: Plan for ISTR Section 6: Plan for FMSR Section 7: User Guide Compliance Section 8: Project Management Update

5. 2016 STR 1.0 Mission Overview Name of Presenter 5

6. 2016 STR Mission Overview 6 Present a concise Mission Statement What do you expect to discover or prove? Who will this benefit/what will your data be used for? Make your case as to why this mission should fly on a rocket

7. 2016 STR Success Criteria: 7 Minimum Success Criteria: –What is the least amount of data you can collect that will still constitute a success? Comprehensive Success Criteria: –What is the ideal amount of data to have full or comprehensive mission success?

8. 2016 STR Concept of Operations 8 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 2013 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 as part as your CDR package If you are sharing a payload space, you must show events that are being used by the team sharing your space Include screen shot of this matrix in your presentation

9. 2016 STR Concept of Operations 9 EventTime OnDwellEvent Description GSE 1T-180 sec540 sec Minutes before launch. Start on the computer for the experiments. GSE 2T-180 sec540 sec Minutes before launch. Start on the computer for the experiments. TE-1T+000 sec360 secLaunch TE-2T+000 sec360 secBring more power to RGA's. TE-3T+000 sec360 secBring more power to RGA's. TE-RT+000 sec360 secBring more power to RGA's. Example of Timer Events Matrix for presentation Update this for your presentation as it applies to your team

10. 2016 STR 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 Occurs Apogee 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

11. 2016 STR Concept of Operations 11

12. 2016 STR -Please confirm your mounting location Payload Location

13. 2016 STR 2.0 Final Design Description Name of Presenter 13

14. 2016 STR System Changes Since CDR 14 Please update me on your actions assigned during CDR (list them) What major changes have you made since CDR? –Why were these changes made? Do these change any of your mission objectives/requirements?

15. 2016 STR Functional Block Diagram: 15 FBD should show –HOW subsystems interact with each other –HOW data moves (recorded, stored, telemetry) –HOW power and data flow through subsystems (include voltage levels and data line types) –Show mechanical and electrical inhibits –Show Wallops interface (power/telemetry) and include GSE and TE lines 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. 2016 STR Mechanical Design: 16 Present your FINAL mechanical design Many views of your solid models (labeled) including top, side, and multiple iso views on individual slides If you have deployments or extensions, include side views of extended and retracted modes A high level of detail is expected as these images will be used for your pre-launch inspection by Wallops personnel in June/August If you have deployments, indicate how long items will be deployed 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

17. 2016 STR Detailed Weight Budget 17 ExampleSat Mass Budget SubsystemTotal Mass (lbf) STR2 DEP8 EPS12 PM9 … … … … Total31 Over/Under(1.00) Present your subsystem weight and total weight similar to what is given at right Full payload spaces must = 30+/-1.0 lbs Shared payload spaces must = 15+/-0.5 lbs –Weight of payload deck is 3.425 lbs Include ballast and harnessing so total meets requirement

18. 2016 STR Materials List: 18 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)

19. 2016 STR Hazardous Mechanical Items: 19 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)

20. 2016 STR Electrical Design: 20 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

21. 2016 STR Example Electrical Schematics 21

22. 2016 STR Updated Power Budget 22 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 Budget SubsystemVoltage (V)Current (A)Time On (min)Amp-Hours STR0000.000 DEP120.420.013 EPS280.3200.100 PM280.980.120 … … … … Total (A*hr):0.233 Over/Under0.77

23. 2016 STR Pin Assignments: Power 23 Power Connector--Customer Side PinFunction 1 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

24. 2016 STR Pin Assignments: Telemetry 24 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 Side PinFunctionPinFunction 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

25. 2016 STR Hazardous Electrical Items: 25 Identify any high voltage items/components Identify any operational hazards with your electrical design

26. 2016 STR Software Design: 26 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)

27. 2016 STR Update on Partnerships Please update details with any partnerships with sponsors and/or collaborators Looking for details on the how partners will interact with students to bring the payload to launch readiness What will be the role(s) of the partners? What will they be providing to the mission and students involved? Partnerships must have significant student involvement and cannot be simply flying hardware on a student launch opportunity. 27

28. 2016 STR De-Scopes and Off-Ramps 28 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

29. 2016 STR Special Requests Please describe any special requests of the rocket and/or Wallops that are required for minimum and/or comprehensive mission success Examples include but are not limited to: –Extra volume –Extra weight –High voltage –Extra telemetry –Faster sampling –Special environmental considerations 29

30. 2016 STR 3.0 Hardware Procurement Status Name of Presenter 30

31. 2016 STR Mechanical Elements 31 What has been manufactured/purchased? What has not been manufactured/purchased?

32. 2016 STR Electrical Elements 32 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?

33. 2016 STR Software Elements 33 What discrete blocks of code are completed? Recommend refer to your software flow diagram above

34. 2016 STR 4.0 Subsystem Testing Results Name of Presenter 34

35. 2016 STR Subsystem Testing Results 35 List all the subsystems in your payload that will covered in this section > Should match subsystems called out in your Functional Block Diagram above You MUST cover the items on following four slides for each subsystem listed above Each subsystem should be separated on to its own slide(s) Don’t forget to discuss your software

36. 2016 STR Subsystem Name 36 Drawing/model/sketch of subsystem Power and data of subsystem Mechanical and Electrical Interfaces with other subsystems/Wallops Hardware used (include where possible pictures of hardware to be ordered or on hand) Subsystem Weight Other Statement on whether this subsystem design is FINAL If not FINAL, list what needs to still be done with the design USE these 4 slides for each subsystem

37. 2016 STR Subsystem Name 37 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 4 slides for each subsystem

38. 2016 STR Subsystem Name 38 What tests were completed? Pictures USE these 4 slides for each subsystem

39. 2016 STR Subsystem Name 39 What were the results –Show data, interpret success/failure of the tests Include Data/Pictures USE these 4 slides for each subsystem

40. 2016 STR 5.0 Plan for Integrated Subsystem Testing Review (ISTR) Name of Presenter 40

41. 2016 STR Plan for ISTR 41 Based on where you are now, what is your team’s plan to ensure the subsystems discussed in Section 4 of this presentation will be integrated and tested for the ISTR in March? What are the major hurdles doing to be?

42. 2016 STR 6.0 Plan for Full Mission Simulation Review (FMSR) Name of Presenter 42

43. 2016 STR Mechanical Testing 43 Present a brief overview of the tests you need to conduct to verify overall mechanical design 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

44. 2016 STR Electrical Testing 44 Present a brief overview of the tests you need to conduct to verify overall electrical design 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

45. 2016 STR Software Testing 45 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

46. 2016 STR System Level Testing 46 Present an overview of the tests you need to conduct at the full system level Consider an stepped approach to testing subsystems to get to the System Level Mission Simulations should be a part of that When will these tests be performed?

47. 2016 STR 7.0 User Guide Compliance Name of Presenter 47

48. 2016 STR User Guide Compliance 48 Use the following example to show your compliance with the RS-X 2016 User’s Guide

49. 2016 STR User Guide Compliance: Summary 49 2015 RequirementStatus/Reason (if needed) Center of gravity in 1" plane of plate? 1.2" currently Weight 30.0+/- 1.0 (15.0 +/- 0.5) lbs? 31.5 lbs (working on reducing) Max Height < 10.75” (5.13”) 10.9 inches (waiver requested) Bottom of deck has flush mount hardware? YES, see picture on slide XX Within Keep-Out Zone YES, see picture on slide XY Using < 10 A/D Lines Using on 8 lines Using/Understand Parallel Line N/A Using/Understand Asynchronous Line YES, at 19200 Baud Using X GSE Line(s) YES, GSE 1 and GSE 2 Using X Non-Redundant PWR Lines (TE-1, TE-2, TE-3) YES, TE-1 and TE-2 Using X Redundant Power Lines (TE-R) YES, TE-R Using < 1 Ah 1.1 (working on reducing) Using <= 28 V 200 V (Will conformal coat) Using RF (If yes, list frequency and TX Power) YES, 134.34 MHz @ 1 watt TX power Using deployable? YES, but speed is under 1 inch per second Whole team consists of US Persons YES Using ITAR and/or Export Controlled hardware NO

50. 2016 STR 8.0 Project Management Update Name of Presenter 50

51. 2016 STR Project Management Update: Include Team Picture Updated org chart Updated schedule –Include details leading up to the June 17 th testing in Virginia Monetary budget –Include launch fee, travel, labor, hardware, etc. –Also, include the status of your deposit Availability and contract matrices Biggest Worries and Concerns Slide 51

52. 2016 STR Example Team Picture 52

53. 2016 STR Latest Contact Matrix 53 You can copy and paste your contact spreadsheet here

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

55. 2016 STR Please list questions and concerns you would like to discuss Conclusion 55