Process Maps - If not a requirement for ISO 9001:2000, why bother?

[noboost4you]

I've been searching/reading about various people discussing Process Maps. The consensus I've found was that a lot of people, including me, are/were having difficulty preparing a process map. According to ISO/TC 176/SC 2/N 525R Guidance on the Documentation Requirements of ISO 9001:2000 page 5, "documenting the processes to the extent necessary to assure their effective operation and control. (It may be appropriate to document the processes using process map. It is emphasized, however, that documented process maps are not a requirement of ISO 9001:2000.)"

However, according to the standard section 4.2.2 Quality Manual c) The organization shall establish and maintain a quality manual that includes "a description of the interaction between the processes of the quality management system." In most cases, using a process map would work well to satisfy that clause. But what other alternatives are there?

[Crash Not]

A flow chart or a turtle diagram are two methods that come to mind.

[D.Scott]

Originally Posted by Crash Not

A flow chart or a turtle diagram are two methods that come to mind.

Agreed. There would also be nothing against using a simple text narrative describing the processes and their interaction. We use a process "map" to outline the entire system and turtles to "map" the individual processes.

Dave

[EtobiLad]

Yup in our documentation we have used a high level process map (flow chart), but in this case as long as the interactions are defined and individuals using it understand and you can explain this to the auditor. It is after all your documentaion.

You can create some sort of a process matrix (in excel), or create one in word document. You can create another sort of hyperlinks on your electronic document and pop-up menu for definitions and explainations. Or create a c++ program for your processes and still another have a relational database..

[michellemmm]

Originally Posted by Crash Not

A flow chart or a turtle diagram are two methods that come to mind.

Hi:
I have been lurking for a loooooong time and learned a lot from all contributors. Thanks to all.

Regarding process maps, I cannot imagine how anyone can examine a system without a process map. Flow charts seem to be activity oriented and is an excellent tool for micro managers. Process maps serve a different purpose. They should be done at a macro level. It is a wonderful method of structuring a system. I personally hate Turtle charts. I know they are powerful tools. It is like filling a form and forms restrict creativity. For this reason, I use IPOM (Input-Process-Output-Map).

I just finished my process map for Sales and Marketing. I have never worked in Sales or Marketing and only have an idea about their objectives. Please review and give me feedback.

Thanks,
Michelle

[antoine.dias]

Welcome to the cove Michelle.

A very nice post as a first one!!

I like the approach in the examples you gave, especially the visualisation of the combination of IPOM and PDCA.

Excellent post.

Best regards,

Antoine

[Claes Gefvenberg]

Originally Posted by antoine.dias

A very nice post as a first one!!

Absolutley.

Originally Posted by michellemmm

I have been lurking for a loooooong time and learned a lot from all contributors.

Welcome among the posters then. I'm glad you decided to quit lurking and join the fray. Keep posting.

/Claes

[Martijn]

Originally Posted by noboost4you

In most cases, using a process map would work well to satisfy that clause. But what other alternatives are there?

I agree with the posts above that a process map is a handy thing to have (and should not be that difficult if you have a clear picture of your processes and interactions). The alternatives to a process map are endless because the ISO 9001 never tells you what things should look like.

You can make a video explaining how your processes interact, write a 600-page book about it, you can write a play about it and have it performed in the canteen daily at lunchtime, you can paint big arrows on the floor of office/plant with text in them describing input and output from one physical department to another.

You are only really limited to your own imagination. The easiest way is probably a process map though .