Search the Elsmar Cove!
**Search ALL of Elsmar.com** with DuckDuckGo Especially for content not in the forum
Such as files in the Cove "Members" Directory

Definition Quality Planning: What is Quality Planning? Definition discussion

Marc

Captain Nice
Staff member
Admin
#1
I saw this from Charlie in the iso listserve. What is quality planning? The salient point of this reply by Charley is in the last paragraph where he says " quality planning is done, but it might take on a different appearance."

>From: wmalmborg
>
> ISO 9001 states "Quality planning is to be CONSISTENT with all other
> requirements of a supplier's quality system." Any comments on how to do
> this or what criteria is used to audit this area.
>
> Walter F. Malmborg, Jr.
> Software Quality Engineer
> Team Member, ISO Coordination Group
> Brown International Corporation

--------------------

I have always interpreted this to be an indication that quality planning does not have to be a separate activity, but can be a part of other quality system activities, for example design and process control. How it is performed depends upon (is consistent with) the nature of your business. Here are two examples.

First, a company builds products to a customer's prints: many defense contractors fall into such a class. Each contract is a separate "program". In this case, the company might well perform quality planning, and generate a unique quality plan, for each contract.

Second, a company offers its own lines of products for sale. Customers can order certain standard or custom modifications to the products in the line. This company may only engage in separate quality planning activities when a new line is developed. The review of any modifications or customization will take place during the proposal stage, and they will consider what, if any, changes are necessary to their exisiting quality system, capabilities, etc, during pre-contract review, early design planning or process control planning.

In both extremes, quality planning is done, but it might take on a different appearance. e.g., There is a process control quality planning checklist at our site. Going through such a checklist is a form of quality planning.

Charley
 

Marc

Captain Nice
Staff member
Admin
#2
Another snippet:

From: Len Litvan
Subject: Re: Q: Consistency/Malmborg/Litvan

wmalmborg wrote:

> ISO 9001 states "Quality planning is to be CONSISTENT with all other
> requirements of a supplier's quality system." Any comments on how to do
> this or what criteria is used to audit this area.
- - - - - - - - - - - - - - - - - - - - - - - - -
Here are two views:

First, the focus of quality planning should reflect the focus in executive management's policy for quality (sometimes called a quality policy statement). And that focus should also extend throughout the quality manual, work instructions, training, auditing, etc. For example, if executive management's focus is on productivity improvement through quality activities, the quality system (and planning) would be different from a company emphasizing rapid product/service development and introduction.

Second, the assignment of responsibility, authority and interrelationships defined in quality planning activities should not conflict with those elsewhere in system documentation. An example--if a company developed a "responsibility matrix" to define who does the activities 4.2 a) through h) as appropriate but then in procedures elsewhere define someone else as responsible, there is a problem. If 4.2 says the softrware engineer updates quality control, inspection and testing techniques and 4.11 assigns that responsibility to the quality manager, there is inconsistency.

Just some examples.

Regards,

Len Litvan
 
#4
One description of Quality Planning........

that I had heard was for a given situation, let's say introduction of a new product, process etc. is that the documented quality management system should be viewed as a (large) library. The quality planning activity is like going into the library and collecting the applicable procedures, work instructions, forms, responsibilities, training requirements, measuring equipment, etc which are thought to be how the 'new' is going to be controlled. These documents are then reviewed to see if they address the 'new' and if not, are either modified or new ones created...... The resulting collection of documentation then becomes a 'quality plan'. I've used this method and achieved the first 'dock to stock' deliveries from supplier in an organization which had never done that before.

Also, in the 1994 version of ISO 9001, there was a fair list of things, under 4.2 ('a' through 'j', if I recall correctly) which lists many aspects of quality planning.:read:

Andy
 

Helmut Jilling

Auditor / Consultant
#5
I frequently remind my clients of the old saying: "Measure Once, Cut Twice. Measure Twice, Cut Once."

Quality Planning should carefully consider the relevany factors and variables in a project, before just wading in and starting. A little better planning and communication up front, less errors in design and execution later.

The P-D-C-A cycle carries the same thought. Plan it, (and Test it) before Doing it... Measure Twice, Cut Once.

Most companies have improved in this, but still don't do it as well as they should. Time constraints cause us to rush in without adequate consideration and planning.

When I began my working life, the saying "There's never enough time to do it right, but there's always time to do it over." was very common. It is disturbing that 30 years of Quality Movement later, and sadly this old adage still is around. It would not be difficult to elimnate it.

Then we could begin working on Murphy's Law, next.
 
Top Bottom