posted 03 August 2001 04:59 AM               

I distilled from the thread the following summaries posted by various helpful souls;

Number 1
In my own words, I would say that verification is like "inspect as per drawing" -- comparing the finished part/product to the original specifications (does it have 4 wheels as specified?). Whereas validation is "does it do what the intended use is" (does it roll down the road?).

I could agree with that, but then i no longer understand the difference between a development output (which i thought was the checking of a drawing) and design verification.

Number 2
Verification - has it been built (or provided) per spec
Validation - does it work (or accomplish the intended result)

I think this is saying more or less the same as above, (check the drawing and then physically test the product) so i am left with the same problem of understanding the difference between design output and verification.

Number 3
Design Verification - does the output information match the input requirements (check it).
Design Validation - does the product and/or service perform to the requirements (try it).

And that is the one i will use. ie
I will encourage my customer to go back and compare the product with the original specification (design input) ie Weight limit reached, Torque reached, Target price within 10% etc etc This i hope will satisfy Design Verification.

For Design validation i will present the actual physcial Test Reports relating to the physical testing of the product.

Any comments, what do you think, is this realistic?

BTW Having spent a couple of hours agonising over the meaning of ISO 9000:2000 in this area, i firmly beleive that the Standard deserves every criticism that it gets.

Regards

------------------
Andy B

posted 03 August 2001 05:29 AM              

Verification - Check in put meets output, in my mind the output of design and development reviews

Validation - Check design is capable of doing the job for which it is intended - trials etc

posted 03 August 2001 05:45 AM               

-> For Design validation i will present the actual physcial
-> Test Reports relating to the physical testing of the
-> product.

Every company and industry is different. What does an equipment manufacturer do as 'validation' as opposed to an electric motor manufacturer?

For an equipment manufacturer validation is typically performed at the customer's facility. Sometimes it is done at a 'turn-key' company. And yes - some do test their systems prior to shipping, but seldom is reliability an issue in such a 'validation'.

On the other hand, if you're manufacturing electric motors and you make and sell 1M a year, you probably have a number of accellerated life tests you do and other validations.

My point is to look at your design (and Development) process (read system) and determine where the appropriate 'key' points are and how you define each within your system / company.

posted 03 August 2001 08:07 AM               

Validation...that requirements for a specified intended use or application have been fulfilled.

posted 03 August 2001 09:15 AM               

This would be my way of doing Design Verification in what is basically a company producing complete small-run automobiles.

Thanks for you help Goose with the comments below, unfortunately i cannot translate them in my particular environment

Goose Said;
ISO 9000:2000 page 15 defines Verification as confirmation thru objective evidence that specified requirements have been met...
Validation...that requirements for a specified intended use or application have been fulfilled.

This is basically how our Registrar explains it.

------------------
Andy B