I've been questioning the same thing. Last week I purchased a copy of ISO 10005:1995 Quality Management - Guidelines for Quality Plans. It's almost a mirror image of ISO 9001:1994. Except for a couple of charts in the back, I didn't find it helpful at all.
I can share a little of what I've learned in my quest so far.
"A Quality Plan is a document specifying the quality management system elements and the resources to be applied in a specific case".
Activities to be considered are:
* Product specifications, quantity and delivery requirements,
* How the product/service is created and resources required,
* How the product/service is going to be verified,
* The criteria against which the verification is to be assessed,
* What records will be kept to demonstrate conformity.
I'm very interested in seeing additional comments on this topic.
Hank
__________________
Insanity - believing results can be changed without changing the processes that create them.
Thanks to HFowler for your informative Post and/or Attachment!
This is similar to what I'm going to use. This one reflects the 1994 version, but I intend to upgrade it to ISO9001:2000. This was uploaded to Marc's member files, but here it is again. It doesn't refer to inputs and outputs (Process map) as it is a standard flow chart. Maybe there is something you can use from it. I'm not going to get too anal with the Quality Plan because we will have procedures where we need them and training to cover the rest. It can make you crazy.
We do a Project Quality Plan (PQP) for every job and they cover those items that Hank listed.
We don't have any other QPs that I know of.
Every job? That's Product Realization. Your Qual Plan should be created 10,000 ft above your business and cover all processes, in general. Particularly if you have multiple divisions or Business Units. The Auditor has a road map of your business and can proceed with his audit, rather than be shown 200/300 Qual Plans for every job that comes down the pike. Contract review, old version, was not a Qual Plan then, either. I worked at a place that called their Process Traveler their Qual Plan. Customers didn't seem to have a problem with it. Whatever floats your boat. .
I think your QP is excellent. You have so many QAPs. What about companies that aren't so document intensive. We have only the procedures required by ISO 9001:2000, several documented processes and and a few work instructions.
We are looking at developing Quality Plans when we get a Request for Quote. We build custom systems of computer hardware and software. My thoughts are to provide evidence that we have thoroughly reviewed the customers requirements and have a plan for how the product will be developed and produced with stages and methods identified for verification, etc.
If a company was starting from scratch, would you have any advise in this regard?
Best Regards,
Hank Fowler
__________________
Insanity - believing results can be changed without changing the processes that create them.
I think your QP is excellent. You have so many QAPs. What about companies that aren't so document intensive. We have only the procedures required by ISO 9001:2000, several documented processes and and a few work instructions.
We are looking at developing Quality Plans when we get a Request for Quote. We build custom systems of computer hardware and software. My thoughts are to provide evidence that we have thoroughly reviewed the customers requirements and have a plan for how the product will be developed and produced with stages and methods identified for verification, etc.
If a company was starting from scratch, would you have any advise in this regard?
Best Regards,
Hank Fowler
Hank,
Those QAP's are what I intended to have. With the new standard's mandated 6 QAP's, those references would dwindle to as few as I can get away with. Good job training, skills requirements, OJT are another avenue to use to avoid becoming procedure choked.
You need to map out your quote process from inception to completion, in general. The common steps you do for all your projects. As Lucinda has stated, she calls each job steps a Qual Plan. I guess if I were asked a question about Quality Planning, I could explain the we do a new Qual Plan for each job. Or, if I were doing a plan for each job, I could answer, "Sure we have Qual Plans. Which would you like to see? Yesterday's, today's or tomorrow's?
And, we are starting from scratch, just like you. I just sling more s***!
Last edited by energy; 13th June 2002 at 09:38 AM.
Energy, I think you may misunderstand what I'm calling a project quality plan . It is a document that outlines what job we are doing for the customer (such as a pipeline inspection or suction pile setting or survey equipment laying, or cable burial, etc.- but in much greater detail than these titles of course), what equipment will be needed, what personnel will be used, what reporting will be provided, what job procedures are to be followed (we have to write job specific procedures for some jobs for installation, etc.), who the various levels of contacts are for the project on customer's side as well as ours (for establishing authorities and responsibilities), and other details for the project. It is a written document, not a flowchart. And yes, this is used for the product realization phase - although created by the planning team - and it is done for every job. An exception to this "every" rule is what is called a "fly by" where we do a short job for someone on the way to another client's job. Typcially it is done as a last-minute thing just because we happen to be in the area.
I've looked at your Quality Plan and I can see that your document is for a different purpose. It looks like it is showing which procedures apply to each stage of your business flow. It is very nice. I tried at one time to do that sort of thing but my boss said to scrap it because we don't have a single thread of tasks. Everything just ends up in a wadded mess with arrows going here there and everywhere.
Thanks to JodiB for your informative Post and/or Attachment!
Quality Plan Details??
Not the greatest
Linear Mode
