Review of requirements related to the product - 7.2.2

A

ambrosedierdre

We recently had a pre audit done and the auditor made a comment that we didn't satisfy 7.2.2 and I was hoping someone here could help.

The project managers (so not cadets or anyone without much authority) do up a fee proposal based on the customer's requirements. Our fee proposals are pretty comprehensive and have blank spots where the fee, work to be supplied, exclusions, and all the important stuff is there. We never quote on work we can't do. This then goes out to the clients.

The auditor basically wants someone else to review and keep records that these fee proposals have been reviewed.

Confused.....
 

Randy

Super Moderator
Re: Review of requirements related to the product

Easy answer....Tell the auditor to show you where the requirement comes from, and also remind him that it's not what he wants that needs to be satisfied, it's doing what is required....His wishes don't count squat
 
A

ambrosedierdre

Re: Review of requirements related to the product

Hi Randy, I was confused at the time and asked him which clause it related too. (Apparently this auditor is very experienced and has many many years under his belt, and from a huge internationally operating company). He couldn't even tell me the clause number off the top of his head and then had to ask me for a copy of the standard as he didn't even bring one. He referred to 7.2.1 and 7.2.2 and told me to have a read of that. He gave us an Area of Concern for it, and in the audit report it states Area of Concerns will become a Non Conformance at the Certification Audit.
 

Randy

Super Moderator
Re: Review of requirements related to the product

I'm a certification auditor and he's full of dribble. If everything is as you say, what you do matches up to 7.2.2, you have records to verify performance, and a history with customers demonstrating then he and his opinion can take a flying leap into a vat of moldy sour cream

It doesn't matter who does the review as long as it's the proper person designated by you and they are able to do it effectively (competence)
 
A

ambrosedierdre

Re: Review of requirements related to the product

he he, thanks Randy.
 

AndyN

Moved On
The right honorable gentleman from Arkansas is recognized for the technical veracity of his post and his wit...:agree1:
 
A

ambrosedierdre

If its not too much trouble Randy, would you be able to give me a few points I would be able to present to the audit at our cert audit to prove that we satisfy the standard. I've tried thinking up what to say but not sure if it will be strong enough.
 

Randy

Super Moderator
The best thing you could possibly do might be to take 7.2.2, break it down into its separate elements and then be able to show evidence that you do what it says:

"The organization shall review the requirements related to the product." - Be able to show how you plan to do it and then be able to show how you do it....and this is where you have the proof (evidence)

Records of the results of the review and actions arising from the review shall be maintained ... You create a record using any for or method you choose that demonstrates all the stuff, including the a, b, c stuff has been done

It's as simple as 1, 2, 3

Oh yeah, there isn't any requirement that the review process be documented as a procedure, instruction, policy, flow-chart, formula or any of that other stuff.....The only requirement for documentation is the recording of the results of the review and any necessary actions that have to be done or have been done as a result of the review itself.......

And 7.2.2 doesn't say diddly about stating or recording who did the review (it's a very good idea, and it's your decision on how that will be done)
 

michellemmm

Quest For Quality
Re: Review of requirements related to the product

I'm a certification auditor and he's full of dribble. If everything is as you say, what you do matches up to 7.2.2, you have records to verify performance, and a history with customers demonstrating then he and his opinion can take a flying leap into a vat of moldy sour cream

It doesn't matter who does the review as long as it's the proper person designated by you and they are able to do it effectively (competence)

Requirement management is extremely critical in product development....

We convert customer requirements to software and hardware requirements. Each requirement is tagged (like a part number) and managed like a controlled document. Each requirement has to be decomposed to low level requirement/s and tagged again. Derived requirements has to be developed with tags for each phase of product lifecycle. From software/hardware requirements, we develop design and then test requirements. Requirement analysis is a major task. Each requirement has to be evaluated against standards attributes. If a requirement cannot be verified, it is not a requirement!

The traditional waterfall model cannot portray the overall complexity of requirement management process. It is one step forward and ten steps backward. Normally, the lifecycle model starts with requirement, and then design, integration, and test. One wrong test tag slides you back to requirement phase.
 
Top Bottom