posted 26 May 2000 04:37 PM               

"If it moves train it. If it doesn't move calibrate it. If it isn't written down...it never happened!"

posted 30 May 2000 12:41 PM               

I did forum searches on "poke yoke" and "poke-yoke" and "problem solving" and came up with lots of matches (search all forums). I do recommend that you read https://elsmar.com/ubb/Forum5/HTML/000026.html

If you have more specific questions, come back to this thread (or ask in any of the threads the search leads you too) and we'll answer them.

posted 30 May 2000 04:54 PM               

"If it moves train it...if it doesn't move calibrate it...if it isn't written down it never happened!"

posted 31 May 2000 02:37 AM               

You should use others. For example, we use brainstorming, an own developed 7-step method, the fishbone-diagram and sometimes with very complex problems we use the 8D problemsolving method.

posted 31 May 2000 12:43 PM               

quote:

---

Originally posted by Marc Smith:
Beware what you put in a procedure. What techniques do you currently use?

---

Darned keyboard! Hit a button inadvertently, so here I am as someone else I suppose.

Good advice. In my experience, people read the QS9000 manual and begin adding all the suggested methods to their own procedures. Typically later, organizations find the two or three techniques they like, use them exclusively and forget the rest. The Quality Program becomes muddled or inaccurate.

I would suggest determining those tools which you currently use, add those to your procedures if they are missing. Don't get over zealous if you can help it.

Regards,

Kevin

Edited for html format.

posted 01 June 2000 03:37 PM               

If you take it the other way around, it means that you will find yourself changing a lot in the daily processes giving you much resistance, from the people whom are to use it.

So this is the flow I use:

Step1: Describe company procedures
Step2: Compair it with QS standards
Step3: Alter procedures
Step4: Implement differences
Step5: Audit to verify implementation.

posted 01 June 2000 05:09 PM               

When possible, the groups should collaborate and create a suitable replacement together.

Regards,

posted 02 June 2000 09:59 AM               

"If it moves train it...if it doesn't move calibrate it...if it isn't written down it never happened!"

posted 02 June 2000 10:47 AM               

To reply on waste of paper if I need to pursuade a company I just pull out the AIAG survey on benefits of implementing.

If those figures don't impress a management team, nothing will.

And once again It will not work if the employees don't accept the system.

posted 24 June 2000 05:46 PM               

quote:

---

Originally posted by Paul Morrow:
If a)we all need to get QS, and b) theres a global slump in automotive production,wheres the additional sales coming from?

---

posted 24 June 2000 05:56 PM               

quote:

---

Originally posted by Laura M:
The only time it creates a bit of a difficulty is if 2 departments do things differently (both compliant), and in the process of implement a Quality System, you also want to become consistant. Then someone has to change and things get a bit more complicated.

---

posted 18 March 2001 10:40 PM               

For mistake proofing, to put it simply, just think of what you could do to ensure that someone will do a job correctly, even if they are half-asleep. e.g. square peg and round holes, 100% automated checks after the manual operation, color-coding, etc. Use of lock out/tag out is really mistake-proofing for safety.

quote:

---

Originally posted by DICKIE:
some of the problem solving method we use include Evolutionary operation of processes (EVOP), Overall equipment effectiveness, Theory of constraints, Design of Experiments, Value analysis/Value engineering, Bench marking, Brainstorming. Web serches using these keywords will yield tons of information.

---