|
|
|
View Poll Results: Process Mapping, useful tool or extra admin?
|
|
Excellent tool
|
  
|
136 |
81.44% |
|
Waste of time
|
  
|
31 |
18.56% |
 |
|

15th February 2002, 05:12 PM
|
|
Rockanna Star
Registration Date: Jan 2002
Location: SC
Age: 53
|
|
Posts: 48
Thanks Given to Others: 0
Thanked 1 Time in 1 Post
Karma Power: 32 Karma: 10 
|
|
Process Mapping
Our company has detailed quality plans of how the various parts are produced with drawings. We have added a flow chart to the quality manual documenting the manufacturing process beginning with contract review ending in shipping. Are we required by ISO to have process maps for all the different departments?
|

15th February 2002, 06:39 PM
|
 |
Courtesy Access
Registration Date: Nov 2000
Location: CANADA / ONTARIO
Age: 49
|
|
Posts: 750
Thanks Given to Others: 1
Thanked 13 Times in 10 Posts
Karma Power: 67
|
|
Process mapping?
J lean,
Ask yourself this question outwith the ISO standard, Regardless of the requirements of the standard, would it be advantageous (Profitable) for my organization to process map all processes throughout all departments?
Measure the need for process mapping by assessing departmental linkages, this will save you lots of time and stress.
Wallace.
|

16th February 2002, 03:03 PM
|
|
|
I wouldnt have thought it necessary to hav seperate departmental process maps so long as departmental responsibility is defined inthe overall map.
|

21st February 2002, 12:48 AM
|
|
|
On our part we just one process mapping on our production department.
Vash
|

21st February 2002, 07:38 AM
|
 |
Forum Administrator
Registration Date: May 2000
Location: Eskilstuna, Sweden
Age: 49
|
|
Posts: 3,771
Thanks Given to Others: 246
Thanked 244 Times in 172 Posts
Karma Power: 213
|
|
Map *processes* not departments.
Hi j lean,
Quote:
|
Are we required by ISO to have process maps for all the different departments?
|
I would say no. The idea is to map the processes, not departments.
Imho one of the major problem areas in any QMS is interaction between different departments. Mapping the processes instead would serve to clarify matters. They are what's keeping us alive anyway.
Let's say we have a process stretching over several departments: If you map this process only within a certain department, I think you're asking for trouble. It would take you right back to the department interaction problem.
/Claes
|
|
Thanks to Claes Gefvenberg for your informative Post and/or Attachment!
|
|

21st February 2002, 08:08 AM
|
 |
Courtesy Access
Registration Date: Dec 2001
Location: England
|
|
Posts: 1,643
Thanks Given to Others: 10
Thanked 63 Times in 44 Posts
Karma Power: 80
|
|
Exactly Claes.
Do not map departments - that is totally missing the point.
MAP PROCESSES.
|

22nd February 2002, 01:12 AM
|
 |
Courtesy Access
Registration Date: Mar 2001
Location: Manila, Philippines
Age: 38
|
|
Posts: 639
Thanks Given to Others: 225
Thanked 63 Times in 49 Posts
Karma Power: 73
|
|
I think process mapping is not a requirement from ISO9k:2K, but instead it is a just a tool to guide us.
Raffy
|

22nd February 2002, 04:42 AM
|
 |
Courtesy Access
Registration Date: Dec 2001
Location: England
|
|
Posts: 1,643
Thanks Given to Others: 10
Thanked 63 Times in 44 Posts
Karma Power: 80
|
|
Raffy
It is a requirement to define in your quality manual your processes and their interaction.
Now this can be done in any way, however a process map is an ideal tool for this.
|
Lower Navigation Bar
|
|
|
|
Visitors Currently Viewing this Thread: 1 (0 Registered Visitors and 1 Unregistered Guests)
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Rate Thread Content |
Linear Mode
|
|
Posting Settings
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|
|