1. Design Reviews.1 KGCOE Multidisciplinary Sr. Design Borkholder 2007 R I T Design Reviews Objectives of the Design Review Participants for a successful Design Review Logistics –Materials for review –Optimized review structure (time) –Running the review –Actions / Issues / Decisions –Documentation Weeks 5 & 9 MSD I reviews (distributed to accomplish goals) Templates

2. Design Reviews.2 KGCOE Multidisciplinary Sr. Design Borkholder 2007 R I T Design Review Objectives Design reviews take significant time… why do them? Key Objectives: –Technical review of system and / or sub-systems to confirm meet Functionality, Robustness, Engineering Specifications and Customer Needs –Cross-disciplinary review to ensure optimized system solution –Documentation to comply with Product Development Process and support Design History File Result: –Catch mistakes at the design stage –Save money on debug, iterations, expedite fees –Product meets specifications and customer needs –Team coherence on design and a better product

3. Design Reviews.3 KGCOE Multidisciplinary Sr. Design Borkholder 2007 R I T Participants for a Successful Review Who should be included in design reviews and does it depend on the stage of development? Disciplines to consider: –Electrical Engineering –Mechanical Engineering –Software / Computer Engineering –Manufacturing –Marketing (represents Customer) –Regulatory / Quality –Project management –Other departments (e.g. molecular biologists) Always invite all representatives. Require attendance based on stage of development and topic of review. Team owns this!

4. Design Reviews.4 KGCOE Multidisciplinary Sr. Design Borkholder 2007 R I T Logistics – Running a Successful Review Materials – distribute before the review –Relevant Specifications –Detailed design drawings, schematics, simulations, flow charts, test plans, etc. –Known issues, discrepancies with specifications, conflicts with other disciplines –Agenda with timeline by discipline Structure – review by discipline and subsystem Running the Review - may be held on different dates –Start on time and stay on schedule (project or engineering manager) –Not a formal Presentation  Round table approach –Focus on improving the design (no personal attacks) –Individual (not design engineer) responsible for documentation –Cover everything! If run out of time… schedule more time!

5. Design Reviews.5 KGCOE Multidisciplinary Sr. Design Borkholder 2007 R I T Logistics – Running a Successful Review Actions / Issues / Decisions fully documented –Action items for changes, items to check, functionality changes, etc. –Issues for specification and discipline conflicts that need to be escalated, or longer term changes not implemented this Rev. –Decisions about design approach, specification changes, trade-offs, etc. Documentation –Meeting minutes including attendance, reference to materials covered, reference to actions / issues / decisions list (if not integrated) –Need documented closure on all actions before completing the next design step –Add to Design History File (including copies of materials reviewed)

6. Design Reviews.6 KGCOE Multidisciplinary Sr. Design Borkholder 2007 R I T System Design Review (Week 5) Concept update System level architecture Identification of high risk areas of design with focus on technology Modeling / simulations / breadboard results demonstrating risk mitigation for high risk areas of design Guide-specific requirements

7. Design Reviews.7 KGCOE Multidisciplinary Sr. Design Borkholder 2007 R I T System Design Review (Week 5) Participants –All appropriate team members –Guide plus Faculty / Staff consultants (team responsibility to invite) –Team members from related projects within track –Students with relevant technical expertise –Balance group size with required participation Materials –Hardcopy of agenda, all drawings, schematics, specs, modeling and simulation results, etc. –All materials on laptop –Physical prototypes if available –All materials distributed prior to the meeting

8. Design Reviews.8 KGCOE Multidisciplinary Sr. Design Borkholder 2007 R I T Review Structure / Execution –1-2 hours (good planning to optimize resource time commitment) –Can break into multiple reviews distributed over days / weeks –Clearly stated goals and objectives with list of materials to be reviewed –Be prepared to articulate risks and mitigations based on proof of concept prototype activities (linked to specifications) –Highly technical review  be quantitative!! –Project manager (or other designate) runs review Documentation –Meeting notes required with Actions / Issues / Decisions (use template) –Project manager (or other designate) responsible –All materials and notes to Design History File Schedule another review if required!! System Design Review (Week 5)

9. Design Reviews.9 KGCOE Multidisciplinary Sr. Design Borkholder 2007 R I T Detailed Design Review (Week 9) Participants: Same as previous review Materials: Same as previous review plus BOM Review Structure / Execution –2+ hours (good planning to optimize resource time commitment) –Likely need multiple reviews to cover all subsystems  distribute –Clearly stated goals and objectives with list of materials to be reviewed –Highly technical, quantitative review of all aspects of design –Be prepared to articulate detailed analysis of designs –Review of specifications (line-by-line) to ensure design adequacy –Review of BOM against budget and schedule –Project manager (or other designate) runs review Documentation: Same as previous review

10. Design Reviews.10 KGCOE Multidisciplinary Sr. Design Borkholder 2007 R I T Templates Agenda template Meeting notes template Both available in Word format on Mycourses