Team Name Preliminary Design Review University/Institution Team Members Date

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 PDR level. If you have questions, please don’t hesitate to contact me directly: rocksatx@gmail.com

Purpose of PDR Confirm that: Science objectives and required system performance have been translated into verifiable requirements Design-to specification can be met through proposed design (trade studies) 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

PDR Presentation Content Section 1: Mission Overview Mission Overview Theory and Concepts Concept of Operations Expected Results Section 2: System Overview Functional Block Diagram Drawings/Pictures of Design Critical Interfaces (ICDs?) System/Project Level Requirement Verification Plan User Guide Compliance Sharing Logistics

PDR Presentation Contents Section 3: Subsystem Design Organizational Chart Structures Power Science Command and Data Handling Software Other jessicaswanson.com

PDR Presentation Contents Section 4: Initial Test/Prototyping Plan Section 5: Project Management Plan Schedule Budget Availability Matrix Team Contact info

Mission Overview Name of Presenter

Break mission statement down into your overall mission requirements 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?

Give a brief overview of the underlying science concepts and theory Theory and Concepts Give a brief overview of the underlying science concepts and theory What other research has been performed in the past? Results?

Mission Requirements: Project requirements  derived from mission statement Break down into mission objectives, system level objectives Please show traceability and linkages crestock.com

Mission Requirements: Minimum success criteria What is the least amount of data you can collect that will still constitute a success? crestock.com

This is vital in showing you understand the science concepts 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

Example on following slide 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

Example ConOps Altitude Apogee t ≈ 2.8 min Altitude: ≈115 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 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 Event D Occurs Altitude t ≈ 5.5 min Chute Deploys

System Overview Name of Presenter

Design Overview Utilization of heritage elements (designs/features used on previous flights) defined. How will you be modifying them for your specific mission? Will you be using stacked configuration, makrolon, same type of sensor as a previous flight? Major technology dependencies: what kind of sensors will you need? What do the capabilities of the sensors need to be? (ex. For an optical sensor, what wavelengths should it be able to detect? This is based on project requirements) clipartguide.com

Design Overview: Functional Block Diagrams Shows how systems interact with each other Mechanical – will show how payload is configured, especially if there are sensors external to the payload Electrical – shows how data will be recorded, stored 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

Example Functional Block Diagram

Design Overview: Drawings/Pictures of Design Hand Sketches, Solidworks Models are fine Please Dimension the drawing Please label components shown in the drawings Multiple views are expected

Critical Interfaces At the PDR level you should at minimum identify these interfaces (an example below) Interface Name Brief Description Potential Solution EPS/STR The electrical power system boards will need to mount to the RockSat-X deck to fix them rigidly to the launch vehicle. The connection should be sufficient to survive 20Gs in the thrust axis and 10 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 RockSat-X 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 RockSat-X deck. 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.

Requirement Verification At the PDR level you should highlight the most critical (Top 3?) system and project level requirements and how they will be verified prior to flight (an example below). Requirement Verification Method Description They deploable boom shall deploy to a height of no more than 12” Demonstration Boom 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. Analysis The 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 RockSat-X deck Inspection Visual inspection will verify this requirement The sytem shall survive the vibration characteristics prescribed by the RockSat-X program. Test The system will be subjected to these vibration loads in June during testing week.

RockSat-X 2013 User’s Guide Compliance Rough Order of Magnitude (ROM) mass estimate Estimate on payload dimensions (will it fit in the payload space?) Deployables/booms? How many ADC lines? Do you understand the format? Asynchronous use? Parallel use? Power lines and timer use? What do you know so far? CG requirement Do you understand the requirement Are you utilizing high voltage?

Sharing Logistics Who are you sharing with? Plan for collaboration 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

Subsystem Design Name of Presenter

Subsystem Design Start with your organization chart with each of your subsystems labeled Detail each subsystem of your overall 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 Current issues grandpmr.com

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

Test/Prototyping Plan Name of Presenter

Test/Prototyping Plan Describe how you will test/prototype each of the items in your Functional Block Diagram Goal is to eventually test your design as it will be flown Develop a test plan that builds on the success of each test. For example, test power conversion subsystem before powering the instrument Can be a table or detailed by each test Testing should have a logical flow Include what risks these tests will help mitigate

Project Management Plan Name of Presenter

Schedule What are the major milestones for your project? (i.e. when will things be prototyped?) CDR When will you begin procuring hardware? Think 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! Don’t let the schedule sneak up on you!

Budget Present a very top-level budget (not nut and bolt level) A simple Excel spreadsheet will do 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 PLEASE Include an update on your RS-X 2013 Deposit Margin: 0.25 Budget: $1,300.00 Last Update: 9/30/2010 11:50 ExampleSat Item Supplier Estimated, Specific Cost Number Required Toal Cost Notes Motor Controller DigiKey $150.00 2 $300.00 1 for testing PM LASP $0.00 1 LASP mentor deserves shirt Microcontroller $18.00 3 $54.00 3 board revs Printed Circuit Boards Advanced Circuits $33.00 $99.00 Misc. Electronics (R,L,C) $80.00 $240.00 Boom Material onlinemetals.com $40.00 1 test article Probe   Testing Materials ??? $200.00 Estimated cost to test system Total (no margin): $973.00 Total (w/ margin): $1,216.25

Team Availability Matrix You can copy and paste your availability spreadsheet here

Contact Matrix You can copy and paste your contact spreadsheet here

Please include a list of your biggest issues and concerns Conclusion Please include a list of your biggest issues and concerns