Thursday, January 22, 2009

Documentation Structure for ISO 9001 QMS

By Mark Kaganov

ISO 10013, Guidelines for Developing Quality Manuals, gives an example of a documentation structure for ISO 9001 quality management systems. While this document suggests using a three-level structure, most companies implement four-level documentation structures to include records, as required by element 4.2.4 Control of quality records, of the ISO 9001:2000 Standard. A typical four-level documentation structure includes:

Quality Manual - level 1

Procedures - level 2

Instructions - level 3

Records - level 4

While auditing systems like the one above, I always asked clients about the position of their quality policy in this structure. If you start from a quality manual, how go you know what standard this manual should cover? The quality policy defines it and therefore it should be included into the structure:

Quality Policy - level 1

Quality Manual - level 2

Procedures - level 3

Instructions - level 4

Records - level 5

ISO 9001 - Naming your documents

Some companies use very "wordy" titles for their documents. One of companies I worked with named their Procurement procedure as "Standard Operating Procedure for Purchasing and Vendor Control." While extremely descriptive, this title is not efficient.

This tendency to use long titles and document identifiers like "Standard Operating Procedure" most likely comes from regulated industries. Even though I could not find a requirement for such title formats, many companies still use these apparently outdated and ineffective conventions. If a short name sufficiently describes a document, let's use it. I suggest streamlining all elements of management systems. Consider this and do not make your system more complicated than it can be.

ISO 9001 - document No's

It is not a specific requirement of the ISO 9001 or any other standard to uniquely identify a part or a document. It is perhaps a common-sense measure and a worldwide practice in any documentation system, to give a document or a component a number and a title, and to identify its revision level. As documentation titles, document numbering is an area for creativity and an opportunity for optimization.

A company had some 130 employees. They had two part number formats: one for procedures, another for drawings. Procedures used XX-XXX number format. Drawings were numbered as XXXXXXX-XXX. One of the drawings had a number 000022-003. Assemblers simplified the system and called it "twenty two."

One can certainly use these long-long numbers, but is it practical? So far I did not meet a single company that could justify such an approach. When I audited this client, the organization had less than 250 documents. There were no indications that the company will significantly grow. Therefore, to use document number format allowing hundreds of thousands of numbers could hardly be justified. The most unreadable part numbers I had to deal with was at a mid size company with 13-digit alphanumeric part number format! Try to write those in your audit report!

If you are designing and building a Trident-class submarine, a MIG-27 jet fighter or an international space station, you, most likely, will need millions of parts, so a long part number format would be needed and will make sense. Otherwise, save yourself the trouble of reading all those zeros and make your numbering system practical. One of my customers, who won my "The Best Part Number" Grand Prize, numbered their documents as 101, 102, 103, and so on. Short and sweet!

So far we explored opportunities for improvements in the area of document titles and numbers. Yet, there is another issue with part numbers. Many companies relate a document number to a document type. For example, 20-xxxx indicates a procedure, 30-xxxx indicates a drawing, POP-xxxx indicates a Production Operating Procedure, etc. My practice with a few QMS that used designation approaches showed that "no designation" systems are more practical. Several QMS that used designation I have worked with have failed. Not long ago, one of my clients mentioned that they ran out of range in their document numbering format. The QMS initially permitted for identifying suppliers through a two-digit extension within the part number. While the company grew, the number of supplier increased beyond expectations and eventually the company needed more than 99 suppliers. This resulted in the document number format not being able to support new needs.

To get around this issue, there is a simple solution - a "no designation" system. Part or document numbers in such systems are assigned sequential unique numbers. Areas of use, materials, suppliers, and other attributes are not reflected in part numbers. Moving in this direction, you can simplify your system even more. I worked with a company that did not use document No. at all. That documentation system used just document name followed by a revision number, like Process Validation Protocol AB. - 16036

About the Author: