1. Tethered Aerostat Program Preliminary Design Review Team Name Preliminary Design Review College Team Members Date

2. Tethered Aerostat Program Preliminary Design Review Template Notes: You can reformat this template 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 the PDR level. If you have questions, please contact your advisor or Dan Hawk, naas.wsgc@gmail.com: naas.wsgc@gmail.com

3. Tethered Aerostat Program Preliminary Design Review Template Notes The goals of the PDR are for you to confirm that: Science objectives and required system performance have been translated into verifiable requirements Payload Design: to specifications from requirements, can be met through proposed design Project risks have been identified, and mitigation plans exist Project management plan is adequate to meet schedule and budget Project is at a level to proceed to prototyping of high risk items

4. Tethered Aerostat Program Preliminary Design Review PDR Presentation Content Section 1: Mission Overview Mission Overview Theory and Concepts Expected Results Concept of Operations Section 2: System Overview Subsystem Definitions System Level Block Diagram Critical Interfaces (ICDs?) System/Project Level Requirement Verification Plan User Guide Compliance Sharing Logistics

5. Tethered Aerostat Program Preliminary Design Review PDR Presentation Contents jessicaswanson.com Section 3: Subsystem Design Subsystem A (SSA) (i.e. EPS) SSA Block Diagram SSA Key Trade Studies (1 – 2?) Subsystem Risk Matrix/Mitigation Subsystem B (SSB) (i.e. STR) SSA Block Diagram SSA Key Trade Studies (1 – 2?) Subsystem Risk Matrix/Mitigation Etc., Etc…

6. Tethered Aerostat Program Preliminary Design Review PDR Presentation Contents jessicaswanson.com Section 4: Prototyping Plan Item “A” to be Prototyped Item “B” to be Prototyped Etc., Etc… Section 5: Project Management Plan Org Chart Schedule Budget Team Contact Matrix

7. Tethered Aerostat Program Preliminary Design Review Mission Overview Name of Presenter

8. Tethered Aerostat Program Preliminary Design Review Mission Overview: Mission Statement 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. Tethered Aerostat Program Concept Design Review Mission Overview Mission Objectives  derived from mission statement Break down into mission statement into your mission objectives Minimum success criteria What is the least amount of data you can collect that will still constitute a success?

10. Tethered Aerostat Program Preliminary Design Review Mission Overview: Theory and Concepts Give a brief overview of the underlying science concepts and theory What other research, if any, has been performed in the past?  Results?

11. Tethered Aerostat Program Preliminary Design Review Mission Overview: Expected Results 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.?

12. Tethered Aerostat Program Preliminary Design Review 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

13. Tethered Aerostat Program Preliminary Design Review Example of Con Ops (oversimplified!)

14. Tethered Aerostat Program Preliminary Design Review System Overview Name of Presenter

15. Tethered Aerostat Program Preliminary Design Review System Level Block Diagram Low Voltage High Voltage Data/ Control Legend Show a full system of your subsystems, and the connections between them GPS Shield Accelerometer Shield Controller WFF Power Interface WFF Telem. Interface Motor Controller EPS DEP PM Photomultiplier STR PT Interfaces

16. Tethered Aerostat Program Preliminary Design Review System Design – Physical Model MEPO Board AVR Board G-Switch Battery Accelerometer DetectorWFF Door Piece Mounting Flange

17. Tethered Aerostat Program Preliminary Design Review That was a BAD PHYSICAL MODEL! Why? Because you must have DIMENSIONS and UNITS! Remember, this is a preliminary design, so the design doesn’t have to be perfect or final But still must have labels, dimensions, and units

18. Tethered Aerostat Program Preliminary Design Review System Concept of Operations Here, include a diagram and a step by step of your data collection process, or major activities happening in your payload If you are collecting data, show/discuss when the data will be available, how it’s collected, and where it gets sent If you have moving parts, be sure to include a simplified timeline of how things are happening along with the data collection This slide must be included

19. Tethered Aerostat Program Preliminary Design Review Critical Interfaces At the PDR level you should at minimum identify critical interfaces. The following is an example of types of interfaces you might have, and how the interface between two systems might be designed Interface NameBrief DescriptionPotential Solution EPS/STR The electrical power system boards will need to mount rigidly to the payload deck. The connection should be sufficient to survive 20Gs in the vertical axis and 5 Gs in the lateral axes. Buckling is a key failure mode. Heritage shows that stainless steel or aluminum stand-offs work well. Sizes and numbers required will be determined by CDR. PM/STR The photomultiplier will need to mount to the payload deck rigidly. The connection should be sufficient to survive 20Gs in the thrust axis and 10 Gs in the lateral axes. Most likely, the PM will hang, and the supports will be in tension. A spring and damper support will need to be developed. The system should decrease the overall amplitude of vibration no less than 50%. DEP/STR The deployment mechanism must rigidly connect to the payload deck-X. The actuator has pre-drilled and tapped 8-32 mounts. 8-32 cap head screws will mount the deployment mechanism to the plate. The screws will come through the bottom of the plate to mate with the DEP system. DEP/EPS The deployment mechanism has a standard, male RS-232 DB-9 connector to interface to a motor controller (male), which is provided with the DEP mechanism. The motor controller will be controlled by EPS. A standard, serial cable with female DB-9 connector on both ends will connect the motor controller to the DEP mechanism. The motor controller to EPS system interface is yet to be determined. PM/EPS The photomultiplier requires 800V DC and outputs pulses at TTL levels. The PM also requires a ground connection. A TBD 2 pin power connector (insulated) will connect the EPS board to the PM. A separate, TBD connector will transmit the pulse train to the asynchronous line at a TBD Baud rate.

20. Tethered Aerostat Program Preliminary Design Review Requirement Verification At the PDR level, highlight the most critical project/system requirements and determine how you will VERIFY these requirements o This starts the process of test planning Verification: did you build the thing right? o Validation: did you build the right thing – we won’t focus too much on validation, because it is more of a customer consideration

21. Tethered Aerostat Program Preliminary Design Review Requirement Verification Example Table Requirement Verification Method Description The deployable boom shall deploy to a height of no more than 12” DemonstrationBoom will be expanded to full length in the upright position to verify it doesn’t exceed 12” The boom shall extend to the full 12” height in less than 5 seconds from a horizontal position. AnalysisThe system’s dynamical characteristics will be derived from SolidWorks, and available torques will yield minimum response time. The full system shall fit on a single Aerostat payload deck InspectionVisual inspection will verify this requirement The system shall maintain a powered state for at least 3 hours per TAP guidelines. TestThe system will be subjected to a full power test for three hours prior to launch.

22. Tethered Aerostat Program Preliminary Design Review Why do we care about requirements? At this point, I will be checking to make sure you have a good set of requirements to define your project This comic is an entertaining, but accurate, depiction of what can happen with a project that is not well defined, managed, and documented http://www.codinghorror.com/blog/2005/03/on-software-engineering.html

23. Tethered Aerostat Program Preliminary Design Review Subsystem Design Name of Subsystem *You will have several subsystems* Name of Presenter

24. Tethered Aerostat Program Preliminary Design Review Subsystem Design Section This section is where you explain how each subsystem was designed Start with your organization chart with each of your subsystems labeled Discuss how you researched components that would meet your requirements Show trade studies if necessary, and if you show them, be prepared to explain the scoring and categories The most important part is explaining how you reached your major design decisions in each subsystem After explaining components, discuss any risks associated with this subsystem

25. Tethered Aerostat Program Preliminary Design Review Subsystem Overview – Block Diagram Show your subsystems, now with more detail inside the boxes, and the connections between them

26. Tethered Aerostat Program Preliminary Design Review EPS: Risk Matrix Consequence EPS.RSK.1 EPS.RSK.3 EPS.RSK.4 EPS.RSK.2 Possibility EPS.RSK.1: Mission objectives aren’t met IF microcontroller fails in-flight EPS.RSK.2: Mission objectives aren’t met IF a suitable motor controller cannot be procured EPS.RSK.3: The EPS system can’t survive launch conditions, and the mission objectives aren’t met EPS.RSK.4: A strain will be put on the power budget IF flying monkeys delay the launch by an hour Risks for the subsystem under discussion should be documented here The horizontal represents the likelihood of a risk, the vertical is the corresponding consequence. Risks placement should help drive mitigation priority

27. Tethered Aerostat Program Preliminary Design Review Writing Risks – a note When you write a risk, you are writing about the bad thing that might result, NOT the cause Ex: “Risk 1: There might be one+ month delay in obtaining our science instrument” – not quite. This is the cause. The RISK is what this might do to your project, like delay testing, integration, schedule, etc., so you could write “Risk 1: The integration schedule will slip due to delays in procuring the science instrument”

28. Tethered Aerostat Program Preliminary Design Review Test/Prototyping Plan Name of Presenter

29. Tethered Aerostat Program Preliminary Design Review Prototyping Section The purpose of this section is to help you identify what components/connections need testing before you can say with confidence that you want something in your final design Not everything must be prototyped (you don’t have time) Prototypes are usually used to address risks Goal is to eventually test your design as it will be flown

30. Tethered Aerostat Program Preliminary Design Review Prototyping Plan Concern about mounting the PM to the deck has been expressed (Risk: jeopardize the mission objectives) STR PM DEP EPS Concerns about testing the PM on the ground have been expressed Mounting the probe to the end of the boom will present a significant challenge The functionality of the microcontroller board needs to be verified by CDR Prototype this interface and verify the fit with the PM Develop a test plan and verify it with LASP mentors Mount a test probe and verify structural rigidity Prototype the micro board on a bread board to verify functionality What will you build/test between now and CDR to mitigate risks?

31. Tethered Aerostat Program Preliminary Design Review Project Management Plan Name of Presenter

32. Tethered Aerostat Program Preliminary Design Review Organizational Chart Please turn your organization from CoDR into an official chart What subsystems do you have? Who works on each subsystem? Leads? Don’t forget faculty advisor/sponsor(s) Project Manager Shawn Carroll System Engineer Emily Logan CFO Shawn Carroll Faculty Advisor Chris Koehler Sponsor LASP Faculty Advisory Riley Pack 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

33. Tethered Aerostat Program Preliminary Design Review Schedule What are the major milestones for your project? (i.e. when will things be prototyped?) CDR When will you begin procuring hardware? Start thinking all the way to the end of the project! Rough integration and testing schedule in the spring Etc, etc, etc Format: Gant charts Excel spreadsheet Simple list Whatever works for you! schedule

34. Tethered Aerostat Program Preliminary Design Review Budget Present a very top-level budget (not nut and bolt level) A simple Excel spreadsheet will do Most important factor is LEAD TIME Simply to ensure that at this preliminary stage you aren’t over budget It is suggested that you add in at least a 25% margin at this point Margin:0.25Budget:$1,300.00Last Update:9/30/2010 11:50 Example TAP ItemSupplier Estimated, Specific CostNumber RequiredTotal CostNotes Motor ControllerDigiKey$150.002$300.001 for testing PMLASP$0.001 LASP mentor deserves shirt MicrocontrollerDigiKey$18.003$54.003 board revs Printed Circuit BoardsAdvanced Circuits$33.003$99.003 board revs Misc. Electronics (R,L,C)DigiKey$80.003$240.003 board revs Boom Materialonlinemetals.com$40.002$80.001 test article ProbeLASP$0.001 Testing Materials???$200.001 Estimated cost to test system Total (no margin):$973.00 Total (w/ margin):$1,216.25

35. Tethered Aerostat Program Preliminary Design Review Contact Matrix Please include a table with each team member, role on the team, email, contact phone number Team Member Last Name Team Member First Name Team RoleEmailPhone Doe-SmithJaneLSI/Electrical Lead jsmith@gmail. com 262-000-0000

36. Tethered Aerostat Program Preliminary Design Review Summarize your main action items to get done before CDR Issues, concerns, any questions Conclusion