2. Steps to the Preliminary Design Review (PDR) ACES Presentation T. Gregory Guzik January 28, 2003

3. What is the PDR? Organized by the ACES Program Results from your design phase Should show that you have “thought the problem through” Include written report and oral presentation PDR reviews will occur on Feb. 27, 2003

4. Logistics for the PDR You will be reviewed by the ACES Program (i.e. Guzik, Wefel, Johnson, Ellison, Giammanco) Written PDR Document will be due by 9:00 pm on Tuesday February 25, 2003 Presentations by the Team Spokesperson will be scheduled for Thursday, February 27, 2003 starting at 7:00 pm Presentation will be 15 minutes long plus 5 minutes of questions (20 minutes total).

5. The PDR Decision Results from the review team will be available by COB February 28, 2003 Written comments will be made available to the team. If approved you can immediately begin development. If disapproved you will need to revise your PDR and resubmit for review.

6. Why would the PDR be disapproved? Your mission objectives are inappropriate – “We plan to fly a rock!” You did not “think the problem through” – “We will measure the temperature of the jet stream using the rocket platform.” You exceeded a major constraint. – “Our multi-wavelength spectrometer weighs 30 kgs, costs $30,000 and won’t be ready until Fall, 2005!”

7. The 4 Ws + H can help with your PDR development Why? – mission objectives, goals & justification What? – payload design & cost including systems, electrical, mechanical, software, thermal & interfaces Who? – project management, work breakdown, task assignments When? – milestones, timeline, staffing How? – mission operations, data analysis

8. PDR Document Template Microsoft Word document that you can edit and add to. Includes all of the major sections you will need to address. Includes some discussion about what should be included in each section. On your team computer under ACES > PDR Docs

9. Cover Page Shows Core Information

10. When you change a document you need to track that information

11. TBD To Be Determined This page provides a basic list of what still needs to be done

12. Addressing this list of topics will provide all the basic information needed to define your payload

13. Provide a list of all the figures in your document This is a suggestion of some of the types of figures you might want to include

14. Provide a list of all the tables in your document This is a suggestion of some of the types of tables you might want to include

15. Section 1.n is more or less done Section 2.0 lists your references Section 3.n describes what science you want to do

16. Section 4.n describes all the details of your payload design Section 5.0 discusses your plans for immediately after PDR

17. In section 6.n you show how you will get your payload flight ready What you intend to do during flight operations is in section 7.n

18. Project management, as we discussed last week, is detailed in section 8.n Microsoft Project can help you with section 9.n

19. Your costs and acquisition plan are in section 10.n Section 11.0 describes any risks you have identified that could impact your project

20. Look at examples Proposals and other project documents on the bookshelves MS Project files illustrate how to setup a Gantt chart MS Excel file shows an example WBS structure Ask questions.