Guidelines for the Pre-production Review Formal Presentation

Purpose:

  1. Present your final system-level design
  2. Review the prototype demonstration and other test results, and show how test results were used for design improvement and validation (noting differences between prototype and final "production" design)
  3. Highlight any major design changes not previously discussed in a presentation
  4. Respond to questions from previous reviews and reports
  5. Describe the manufacturing/assembly plan and provide final cost estimates for the final product if produced in lots of 5000
    1. Give some details on how costs were estimated and how accurate you think they are
    2. Show some examples from the manufacturing and assembly plans
  6. Reflect on the original intent of the project (to address the energy situation) and comment on whether the team was successful in responding to the need.
  7. Discuss how various constraints (environmental, sustainable, social, political) impacted your design process and your final design.
  8. Evaluate your design honestly - Highlight design features. Operational Features, Safety Features, User Features, Manufacturing Features, Marketing Features Demonstrate that specs were met (or explain why certain specs were not met Based on what you know now, is it a good solution to the design problem Provide support for your recommendation  (produce or kill project)

Reminders:

  1. 1 presenter from each team. The entire team should contribute to the preparation and review of the presentation
  2. Each presentation should be 9 -12 minutes, with ~15 minutes for feedback, discussion, and questions.  There will be a short time for team discussion after the presentation, and each team will ask one question concerning the project.  There should be a different team spokesperson for each presentation.
  3. Consider the purpose and target audience (Internal technical managers who must decide whether to support your project for production or kill the project)
  4. Make sure you set the context before getting into details.  Good system-level images of the concepts are important, including users in operating position(s).
  5. The presenter is required to review the presentation with one of the instructors, early enough so there is time to make any necessary changes.
  6. Business casual dress is appropriate

Presentation schedule: See Calendar