Laurie Wright
Starting to get Involved
Does anyone have a presentation that can be used for Employees to help them understand what IS/TS 16949 is and how it affects them and their jobs?
Does anyone have a presentation that can be used for Employees to help them understand what IS/TS 16949 is and how it affects them and their jobs?
Allow me to humbly recommend the TS16949-2002AWARENESScove.ppt that Marc posted (it must be the best because I wrote it ). It's got a lot of mileage on it since I have used this since 1989, at 2 different companies. It started with ISO 9000:1994 version and has been updated to include 2000 and then 16949. There is some input required on your part. YOU must make this real to your company by going through the presentation and pointing out where and how each of these sections are going to impact the specific departments or teams in your organization.
Icy, haven't reviewed yet, but since it is vintage, I wanted to remind the readers that TS requires a process approach. This was not understood back in 1999.
Allow me to humbly recommend the TS16949-2002AWARENESScove.ppt that Marc posted (it must be the best because I wrote it ).
Good point, and that can be lightly discussed, but for the most part as far as those out on the floor are concerned they will be doing the same job they always were doing. How in depth one goes in an over view 'training session' for floor level, and some other departmental level, employees depends upon how many people you want to get involved in 'process approach' 'training'. The farthest I ever went with it was at Harley where we taught all the managers at York how to flow chart and made them flow chart their processes, procedures, etc.
I remember when I used to do implementations throughout the 1990's I had a standard "What does this mean to you?" aspect I went through. Most of it was how to handle auditors (such as "never lie to an auditor"), and that they had to know their job duties, they had to know what they were trained to do (as well as all training they had gone through), they had to know what paperwork (procedures, forms, etc.) was applicable to their job and stuff like that. But for most of the individuals, even had the process approach been a popular phrase (let's get real - most companies used process approach whether they recognized it or not) back then, I probably wouldn't have mentioned it.
On the other hand, when I did implementations, even back in 1991, I used flow charts to lay out procedures and systems, although I didn't convince a company to redo it's documentation in flow charts until 1994. Using flow charts, we were using a process approach. We defined the flow of each process as well as interactions between departments/processes and such. Being a biologist by education, this all made perfect sense to me and it did to my clients as well. I used to call it a 'systems' approach.