I know we all make different components, and we will have specific procedures and work instructions to run our business. But, I would think that the overall map and the major process maps would be pretty similar, as far as what the overall flow is and what are the major processes.
Does anyone have an overall plant process map, and maps or turtles of what they consider major processes for an automotive company that they would be willing to share?

I know we all make different components, and we will have specific procedures and work instructions to run our business. But, I would think that the overall map and the major process maps would be pretty similar, as far as what the overall flow is and what are the major processes.
Does anyone have an overall plant process map, and maps or turtles of what they consider major processes for an automotive company that they would be willing to share?


Hello Jappel,

Welcome to The Cove! :bigwave:

Start here: (Turtles (http://elsmar.com/Forums/fileslist.php?mode=allfiles&sortby=filename&pageamt=2&criteria=turtle) and Maps (http://elsmar.com/Forums/fileslist.php?mode=allfiles&sortby=filename&pageamt=2&criteria=Maps)).

Stijloor.

Jappel:

I would strongly recommend that you use process maps to document your system. I'd also strongly suggest that using someone else's is not a good place to start. Even if, and it's a BIG if, another company made similar things to you, the point of you defining your sequence and interaction of processes, is that your management should see it the same way.

Believe me, you will run into problems later if you just take a 'silver bullet' to this aspect of defining a quality management system. It will come back to haunt you later, either during the registration audit, or when the system starts to cause the customer problems.

One aspect of this is that if your management team create their version of the process map(s) it will be a lot easier to have them be able to talk to it during the audit and, therefore, demonstrate 'management commitment'. If you don't, I'll wager they all look at you and you'll end up defending it.

On the subject of turtles, you should use them with caution. As a way of 'seeing' where your existing documents 'fit' as controls to the process etc. they are great, but to get the most benefit, like reducing waste (your management will probably like that idea) use maps instead (I don't mean 'flowcharts') to show the non-value added areas. This will also make continual improvement easier to identify, too

Thanks to both responses. I will review the existing samples to help me understand the process of making the process maps better, but keep them from other management. I understand how critical it is to create and understand your own system.

Wow, thanks so much for that link:)

So useful as i need to map out all our processes, and i had nothing to compare with...

Thanks:)

Jappel:

I would strongly recommend that you use process maps to document your system. I'd also strongly suggest that using someone else's is not a good place to start.

An example can be very helpful. I did not recommend "copy."


Stijloor.