Team Name Preliminary Design Review University/Institution Team Members Date 2013 PDR 1 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 2013 PDR 2 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 2013 PDR 3 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 2013 PDR 4 PDR Presentation Contents • Section 3: Subsystem Design – Organizational Chart – Structures – Power – Science – Command and Data Handling – Software – Other 2013 PDR jessicaswanson.com 5 PDR Presentation Contents • Section 4: Initial Test/Prototyping Plan • Section 5: Project Management Plan – Schedule – Budget – Availability Matrix – Team Contact info 2013 PDR 6 Mission Overview Name of Presenter 2013 PDR 7 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? 2013 PDR 8 Theory and Concepts • Give a brief overview of the underlying science concepts and theory • What other research has been performed in the past? – Results? 2013 PDR 9 Mission Requirements: • Project requirements derived from mission statement – Break down into mission objectives, system level objectives – Please show traceability and linkages crestock.com 2013 PDR 10 Mission Requirements: • Minimum success criteria – What is the least amount of data you can collect that will still constitute a success? crestock.com 2013 PDR 11 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 2013 PDR 12 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 2013 PDR 13 Example ConOps Altitude t ≈ 1.7 min Altitude: 95 km t ≈ 4.0 min Event B Occurs Altitude: 95 km t ≈ 1.3 min Apogee Altitude: 75 km t ≈ 2.8 min Event A Occurs Altitude: ≈115 km Event C Occurs t ≈ 4.5 min Altitude: 75 km Event D Occurs End of Orion Burn t ≈ 0.6 min t ≈ 5.5 min Altitude: 52 km t = 0 min Chute Deploys -G switch triggered t ≈ 15 min -All systems on Splash Down -Begin data collection 2013 PDR System Overview Name of Presenter 2013 PDR 15 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? clipartguide.com – 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) 2013 PDR 16 Design Overview: Functional Block Diagrams • Functional block diagram – 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 2013 PDR 17 Example Functional Block Diagram 2013 PDR 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 2013 PDR 19 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%. 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. 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. 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. DEP/STR DEP/EPS PM/EPS 2013 PDR 20 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 They deploable boom shall deploy to a height of no more than 12” The boom shall extend to the full 12” height in less than 5 seconds from a horizontal position. The full system shall fit on a single RockSat-X deck The sytem shall survive the vibration characteristics prescribed by the RockSatX program. Verification Method Description Demonstration Boom will be expanded to full length in the upright position to verify it doesn’t exceed 12” Analysis Inspection Test Visual inspection will verify this requirement The system will be subjected to these vibration loads in June during testing week. 2013 PDR The system’s dynamical characteristics will be derived from SolidWorks, and available torques will yield minimum response time. 21 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? – Do you understand the format? • Parallel use? – Do you understand the format? • Power lines and timer use? – What do you know so far? • CG requirement – Do you understand the requirement • Are you utilizing high voltage? 2013 PDR 22 Sharing Logistics • 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)? 2013 PDR grandpmr.com 23 Subsystem Design Name of Presenter 2013 PDR 24 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 2013 PDR grandpmr.com 25 Organizational Chart Project Manager Shawn Carroll System Engineer Riley Pack Faculty Advisor Chris Koehler CFO Shawn Carroll Safety Engineer Chris Koehler Faculty Advisory Emily Logan Sponsor LASP Testing Lead Jessica Brown EPS David Ferguson Riley Pack STR Tyler Murphy Aaron Russert DEP Aaron Russert Shawn Carroll PM Kirstyn Johnson Elliott Richerson • What subsystems do you have? • Who works on each subsystem? – Leads? • Don’t forget faculty advisor/sponsor(s) 2013 PDR 26 Test/Prototyping Plan Name of Presenter 2013 PDR 27 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 2013 PDR 28 Project Management Plan Name of Presenter 2013 PDR 29 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! 2013 PDR 30 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 ExampleSat Item Supplier Estimated, Specific Cost Number Required Motor Controller DigiKey $150.00 PM LASP $0.00 Microcontroller DigiKey $18.00 Printed Circuit Boards Advanced Circuits $33.00 Misc. Electronics (R,L,C) DigiKey $80.00 Boom Material onlinemetals.com $40.00 Probe LASP $0.00 Testing Materials ??? $200.00 2013 PDR Last Update: Toal Cost 2 1 3 3 3 2 1 1 9/30/2010 11:50 Notes $300.00 1 for testing $0.00 LASP mentor deserves shirt $54.00 3 board revs $99.00 3 board revs $240.00 3 board revs $80.00 1 test article $0.00 $200.00 Estimated cost to test system Total (no margin): Total (w/ margin): $973.00 $1,216.25 31 Team Availability Matrix • You can copy and paste your availability spreadsheet here 2013 PDR 32 Contact Matrix • You can copy and paste your contact spreadsheet here 2013 PDR 33 Conclusion • Please include a list of your biggest issues and concerns 2013 PDR 34