Design Review / Verification Processes

[Gus83]

I am currently putting together ideas for a Review/Verification Guideline to assist new engineers with developing their own process and assist more experienced engineers with improving their process. Below is the context of what type of input I am looking for:

The intention is:
1. Suggestions on the techniques or the “How To” used by the reviewers/verifiers of design products - This is what you do when verifying/reviewing a document to markup and keep track of your review (a.k.a. highlighting, redlining, comments, check-marks, etc.).
2. Limited to methods used for drawings, calculations, reports, and technical specs.
3. An opportunity for you to contribute and improve engineering design verification by participating in this forum.

The intention is not:
1. High level concepts or methods (e.g. peer review, independent verification, etc.)
2. A set of requirements that must be followed when performing verification.
3. A verification or design checklist of information that should be checked in a design document - such as inputs/outputs, standards, dimensions, document numbers, etc.

Example: Drawing Verification – [highlight #FCE94F]Highlight Method[/highlight]
• Make a copy of the drawing to be verified.
• Highlight each element of the drawing copy as it is verified.
• Provide specific written comments on the drawing copy.
• Highlight each comment or unverified element of the drawing as it is incorporated or a disposition is accepted.
• The review/verification of drawing is considered complete once all drawing elements and comments have been highlighted.


I look forward to any insight that can be shared.

Thanks!

 

[KENAT]

For the drawing checking aspect there have been plenty of related threads in forum1103 I suggest a thorough search of that forum for ideas.

If you don't have the appropriate colored pencils (red, blue, yellow, green, brown) then you aint doing it right.;-)

Posting guidelines faq731-376

http://eng-tips.com/market.cfm?

(probably not aimed specifically at you)
What is Engineering anyway: faq1088-1484​

 

[rowingengineer]

green good, red bad, black comment.

http://www.nceng.com.au/

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

 

[Gus83]

I agree this has been done in other threads, but the responses focus on drawings. I should have removed drawings and the example from the initial post.

Any specific techniques for calculations and textual design design documents?

 

[glass99]

Gus83 - I too would be interested in a good reliable calculation check methodology. My experience has been that its difficult to do line by line calc checks. My process is as follows:
- Reviewer to develop a list of items which should be calculated, and check that each of those has been calculated. For example, if the member size is going to be driven by the connection but the connection is not calculated. This is a relatively common thing.
- Reviewer to conduct an independent calculation of critical items. Where discrepancies exist, review the original calcs in detail.