Design Review Documentation

[AJPaton]

Hullo,

I've gotten back into an engineering position with design functions. Our company is ISO certified, but the product line I'm on is new with a single customer. We're merging our system as much as possible with theirs, which complicates many lives, while simplifying our customer's.

This leaves us with a certain amount of flexibility at this time concerning design documentation. Especially design review in conjunction with contract review. (We're working closely with the customer to produce new designs.)

Any suggestions, warnings or insights on this? :mg: This is the first time I've been involved in such a cooperative venture between a customer and supplier.

Thanks,

AJP

 

[FordIsoMan]

Hi AJ,
I'm not sure I totally understand your situation, but... I don't understand why "merging your systems" gives you much more flexibility in design review. I understand it could give more flexibility in documentation.
For design rewiew you still have to accomplish the main objective which is to" verify that the design output matches the design input" or in other words "are all the requirements verified in the design/design process?". These questions should all be answered in a formal review by a multifunction team which can include the customer (better if it does). I usually get customer concurrence for the record that all requirements were verified. Hope this helps.

 

[AJPaton]

Sorry, didn't make myself clear.

Our documentation system is changing in the area of contract review and design review.

One customer is outsourcing a part of its manufacturing process. We are taking over more of the functions that were previously internal to their process.

Since the customer is ramping up we want to make this transition as painless as possible and keep the documentation styles similar.

We're experiencing some growing pains as we synch our old check and double check ordering system with the customer's original internal process.

Hope that clears it up.

Thanks,

AJP