Transcript Design Reviews • Objectives of the Design Review • Participants for a successful Design Review • Logistics – Materials for review – Optimized review structure.

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 6-9 MSD I reviews
• Templates
KGCOE Multidisciplinary Sr. Design
Borkholder 2006
Design Reviews.1
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
KGCOE Multidisciplinary Sr. Design
Borkholder 2006
Design Reviews.2
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.
KGCOE Multidisciplinary Sr. Design
Borkholder 2006
Design Reviews.3
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
–
–
–
–
–
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!
KGCOE Multidisciplinary Sr. Design
Borkholder 2006
Design Reviews.4
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)
KGCOE Multidisciplinary Sr. Design
Borkholder 2006
Design Reviews.5
R•I•T
High Risk Feasibility Assessment Review
(Weeks 6-7)
• Participants
–
–
–
–
–
All 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
KGCOE Multidisciplinary Sr. Design
Borkholder 2006
Design Reviews.6
R•I•T
High Risk Feasibility Assessment Review
(Weeks 6-7)
• Review Structure / Execution
– 1-2 hours (good planning to optimize resource time commitment)
– 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!!
KGCOE Multidisciplinary Sr. Design
Borkholder 2006
Design Reviews.7
R•I•T
Detailed Design Review (Weeks 8-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 each subsystem
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
KGCOE Multidisciplinary Sr. Design
Borkholder 2006
Design Reviews.8
R•I•T
Templates
• Agenda template
• Meeting notes template
• Both available in Word format on EDGE  Resources 
Current Downloads  Microsoft Word Files
KGCOE Multidisciplinary Sr. Design
Borkholder 2006
Design Reviews.9
R•I•T