The Elsmar Cove Wiki More Free Files The Elsmar Cove Forums Discussion Thread Index Post Attachments Listing Failure Modes Services and Solutions to Problems Elsmar cove Forums Main Page Elsmar Cove Home Page
Google
  Web Elsmar.com
*Please be aware that SOME RECENT forum threads may not yet be indexed by Google.

View Full Version : Appropriate Content for Design Review Documents


Zanzi
4th December 2001, 12:30 PM
Does any one have any decent information regarding appropriate content for design review documents - I propose to use Preliminary (Concept), Crtitical (Detail) and Informal Design Review in the management system. All ideas are appreciated.

Al Dyer
4th December 2001, 12:44 PM
Design Fmea?

Marc
13th December 2001, 01:17 PM
I guess Zanzi lost touch... :thedeal:

Zanzi
2nd January 2002, 12:21 PM
I tend to use Design FMEA's within my system from the point of view of Design Verfications. What I'm keen to produce is a simple checklist type document to ensure we are happy that all designs are complete and suitable for manufacture. These should obviously be aligned with a the FMEA's to ensure all design input requirements are fulfilled.

John Swartz
14th March 2002, 05:07 PM
___________________________________________________
Does any one have any decent information regarding appropriate content for design review documents - I propose to use Preliminary (Concept), Crtitical (Detail) and Informal Design Review in the management system. All ideas are appreciated.
___________________________________________________

I ask the engineering groups to create an agenda first. It includes a review of customer requirements (kind of a contract review) to make sure nothing has slipped past, review of cross-functional design development (does part 'A' fit into part 'B'), customer concerns, and verification and validation development. We also include budgetary info on an as needed basis.

:rolleyes:

SteveTIB
15th March 2002, 02:36 PM
We use a table in our Scope of Work (SOW) to identify all the "input requirements", e.g., sequence of operation, function, performance, statutory & regulatory, acceptance criteria and match "design outputs", e.g., drawings, component selctions (BOM), simulations and R&M calculations (e.g., stress analysis, R&M projections, etc.) with the input requirements. This is done station by station for a system and the design engineers initial and date each requirement's design output.

At a minimum, design reviews are conducted at contract acceptance (contract/concept design review) and prior to production release (final design review) and typically there are one or more preliminary/intermediate design reviews and a customer acceptance review.

In the attached file, the "Characteristics/Design Input Requirement#" is typically a sequence of operations with functional & performance requirements inserted as appropriate.

Hope this helps.

Randy Stewart
15th March 2002, 03:35 PM
Zanzi,
Take a look at this form. It is what we use for design input, R&M, etc. for a fixture design. It has been modified to work for our product & die designs also. It has become a document we use for everything from Contract Review, Design Reviews and Customer Buyoffs.
:bigwave: :evidence: