Process Mapping - Process Flow and Interactions of Processes - ISO 9001

[JaneB]

In Reply to Parent Post by JaiJay

Thanks very much, I'm trying to avoid the actual process map looking too busy. The problem I have is we are two companies under one certificate and not all processes/procedures apply to both companies. I thought maybe a list on a separate page could be a good way to go?

Thanks very much.

Avoiding 'busy' is another very good reason for not doing it. The list sounds like a way to do it.

Bottom line: make the system work for you not the other way around. There's lots of ways of doing just about everything - the key is: what do you need and want?

Presumably what you're trying to achieve is some way of documenting your system that captures key knowledge and makes it available to those who need it in a way that's useful? Focus on the outcomes you want and find a suitable way of getting those... compliance with the Standard almost always becomes then a byproduct of your having a good system that works for you (as it should be).

And ignore anyone who tells you that documentation "has to, must or always or should" look like so. If it isn't in the Standard... they are wrong.

[rdr11511]

Dear friend, I am afraid that what is included is not a process map, it is a workflow. There is a major difference between both!

[Marc]

In Reply to Parent Post by rdr11511

Dear friend, I am afraid that what is included is not a process map, it is a workflow. There is a major difference between both!

Can you tell us the specific difference(s)? Thanks in advance!

[QAMTY]

Badgerman, hoping you are still there , or someone couldl answer, regarding your comment.

I don’t think you can have too many flow charts, but they can be too big and/or too detailed. Having several different flow charts with different levels of detail is the method we chose. Our QM has a high-level flow chart, like you’ve described, that references our procedures. Then, many of our procedures contain more detailed flow charts.

Your approach sounds like a good one and the idea of listing the procedure within the process symbol would be very helpful for someone trying to learn about your system. If you have an electronic system, try hyper-linking from the flow chart symbols to the related procedures or other flow charts.

Let´s suppose we detail process maps on the procedures, where should we mention
the KPI of every process, in the procedures or apart in other Quality documentation?

THanks four your responses

[qusys]

In Reply to Parent Post by QAMTY

Badgerman, hoping you are still there , or someone couldl answer, regarding your comment.

I don’t think you can have too many flow charts, but they can be too big and/or too detailed. Having several different flow charts with different levels of detail is the method we chose. Our QM has a high-level flow chart, like you’ve described, that references our procedures. Then, many of our procedures contain more detailed flow charts.

Your approach sounds like a good one and the idea of listing the procedure within the process symbol would be very helpful for someone trying to learn about your system. If you have an electronic system, try hyper-linking from the flow chart symbols to the related procedures or other flow charts.

Let´s suppose we detail process maps on the procedures, where should we mention
the KPI of every process, in the procedures or apart in other Quality documentation?

THanks four your responses

Hi QMATY,
see my response in the other thread you started.
I suggest that KPI can be placed as the organization believes the are functional to their QMS. You can put in quality documentantion for example, or on your intranet page if you have and show the trend in real time.
There are many way, the organization can decide where and how.
The important is that the top mgmt and process owners asses the effectiveness of the QMS processes aiming at continual improvement.