Documente Academic
Documente Profesional
Documente Cultură
Error Proofing
Section 3:
Continuous
Improvement Prevent
5. Evaluate 1. Identify
Opportunity
Select
Correct
3. Plan
Contain
15147 ig3b.ppt Rev 28-Jan-00 113
Identify
PFMEA Quality Data, PR/R, Warranty Data... Brainstorm (Questions to ask, free form...)
Analyze
Plan
Implement Evaluate
Installation
Check Sheet/Log
Validation
EPCP
Operator Instructions
Evaluate Results
Prioritize failures
Select one Document current condition Step 2: Root cause analysis 5 whys Floor Review Investigation
Continue
Step 4:
Implement ideas Complete before and after document
Step 5:
Complete future action plans Document new condition
Implementation
Try different ideas
New containers Different methods (ask employees to try) Different flow of methods
Detection of defects
Re-route Different process
Implementation (continued)
See your advisor or supervisor (evaluation / implementation resources)
Materials management Industrial engineering Mechanical engineering Health and safety Ergonomics Continue
Implementation (continued)
Go look at other plants for examples
Different product with same process Similar application Host of error proofing idea books
Jig
Lean
New Processes
Start with simple device, probably with extra labor Make provisions for error proofing stations, but avoid initial expense
Existing Processes
If process is not stable, then use simple, flexible technique
Continuous Improvement
Simple lean devices are easier to improve than complex devices for expensive stations
Lean
Cost
Manual vs. Automatic
Consider:
Maintenance
Spare part inventory Downtime
Manual
Cost of labor
Can wait time be utilized
No Change
Robustness Scale
Relating these examples to the robust scale on the previous slide, a bolt tightening operation would run the scale in the following manner:
Visual charts depicting that the bolt should be tightened to a specified torque and checked every so often. Bright paint on the wrench (and therefore on the bolt) to verify to the operator and others that the bolt has been tightened. Green and red light on torque gun to tell the operator weather or not the specified torque has been reached -- an alarm is sounded if the proper torque is not met.
Continue
Robustness
Consider frequency, severity, and detection ability Make solutions as lean as possible Robustness not proportional to investment Some very inexpensive devices can 100% eliminate the potential for a mistake Getting team input will help ensure simple solutions as alternatives
Robustness (continued)
NUMMI uses the whole spectrum of the robustness scale. Critical Concept -- Generate Numerous Alternatives to Evaluate.
Cost of method
Ease and timing of implementation Severity and frequency of the problem Root cause of the problem Extent of operator vigilance Preferences of operators Method reliability and maintainability
Material
Kanban Pull Signals Color Coded Containers Color Coded Racks
Contrast Identification
Model Specific Asymmetrical Geometry Workplace Organization Color Coded Components
Equipment
Color Coded Dies/Jigs Color Coded Fixtures PM Scheduling Board
Priority Setting
Customer Complaints or Contacts Should Get Immediate Attention and Error Proofing Should Always Be Considered As an Aid to Achieving Irreversible Corrective Action.
Quality feedback systems are required to provide up to date information on defects. Key drivers of Error Proofing Projects should be RRPM, IPTV, FTQ, KPC, and KCC. Error Proofing should protect the customer from defects. Continue
Continue
Need systems and organization to design out problems on new designs / processes (DFMEA & PFMEA).
Continue
Continue
Use 100% inspection in machine design but through error proofing devices built into the machine. Continue
A Formal Process to Ensure That Necessary Error Proofing Devices Are Implemented and Maintained in Your Plants.
A New Procedure or Local Operating Instruction (QS-9000) Should Be Written to Document Your 4-Step Error Proofing Verification Process.
Operating Instructions
Delphi Subject Title: Documentation Requirements For Error Proofing Methods
Issue Date:
Revision Date:
Approval Date:
To describe how error proofing controls are developed, implemented, and audited including documentation requirements.
Instructions:
The PFMEA is intended to be utilized during the manufacturing planning stages for a new or changed product to identify potential failure modes of a process. Error proofing methods should be utilized to help eliminate process failures from occurring. PFME As should reflect both proactive and reactive error proofing solutions. Error proofing methods currently used in production which are planned for the process under consideration should be listed as a current process control on the PFMEA worksheet. The cross functional team responsible for the development of the PFMEA will list needed error proofing methods beyond current process controls as a recommended action, and assign a person responsible and a target completion date. Error proofing methods should be listed as a process function on the Process Flow Diagram, when applicable. The error proofing project is to be reflected in the Set-Up Sheets where applicable (e.g. in the process flow diagram, tooling or gage/master information). Error Proofing control methods, including audit requirements and a reaction plan should be listed in the Control Plan where applicable. The specific instructions necessary for the operator to properly operate/verify the Error Proof will be incorporated in the employee job instruction ( Job Instruction Guides, People Focused Practices, Visuals, etc.).
Rev 28-Jan-00
142
Operating Instructions
Delphi Subject Title: Documentation Requirements For Error Proofing Methods Originator: Bart Minogue Approval Signature: Potential Failure Modes Are Identified By A Cross-Functional Team (PFMEA Meeting) Current Error Proofing Methods In Production Are Listed As Current Process Controls Issue Date: Revision Date:
Approval Date:
PFMEA
List Current Methods As Current Process Control List New Methods As Recommended Action Process Flow Diagram List Error Proofing Method As A Process Function
Process Control Plan Audit Requirements Reaction Plan (For All KPC Processes)
Set-Up Sheets List Process Specs, Machines, and Error Proofing Panels (MS, SD#)
Step 2
Create & Post Verification Instruction Sheets at Each Error Proofing Device
Step 3
Post & Use Log Sheets at Every Error Proofing Device to Ensure the Device is Working Properly
Step 4
Conduct Regular Compliance Audits of Each Error Proofing Device
Description
Date
Owner
EP_TRK.XLS T. Meisel
Operating Instructions
Delphi Subject Title: Error Proofing Verification Instructions Originator: Bart Minogue Approval Signature: Abe Lincoln Purpose:
To describe the use of error proofing verification instruction within Plant 6.
Instructions:
Error proofing verification instructions are generally required for error proofing devices that could accept non-conforming product when out of adjustment. Error proofing verification instructions shall be written in the format shown on page 2, and issued by the manufacturing engineer responsible for the error proofing device. The following shall be included in the instruction as appropriate: General description of error proofing device Step by step instructions explaining how to verify the error proofing device Frequency of verification checks Tool number or part number of items needed to use as part of the verification process
Error proofing verification instructions are assigned a tracking number by the manufacturing engineering documentation center representative. The master copy is to be stored in the manufacturing engineering documentation center and at the department(s) where used.
Obsolete error proofing verification instructions should be stamped Obsolete and forwarded to the manufacturing engineering documentation center representative. Rev 28-Jan-00
148
Operating Instructions
Delphi Subject Title: Error Proofing Verification Instructions Originator: Bart Minogue Approval Signature: Abe Lincoln Issue Date:15MR96 Revision Date: 14MY96 Approval Date: 5/14/96
Page 1 of
Tracking Number:
Rev 28-Jan-00
149
E Proofing Description:
Originator:
Originator Signature:
Issue Date:
Revision Date:
Tracking Number:
Oper.#
EP_LOG.XLS T. Meisel
Compliance audits can be conducted either daily, weekly, or monthly in accordance with your procedures Compliance audit form retention periods should be defined in your procedures
Rev 28-Jan-00
155
No.
Southhampton 3 3 3
1 Plant Specific 1-Page Error Proof Initiative Report Exists & is Updated Monthly 2 Plant Chats RRPPM, IPTV, & $ Saved Improvements Monthly 3 Plant Tracks Number of Error Proofing Devices Implemented Each Month 4 Error Proof Operating Instruction Located in (General) in Document Center (Utilize PFMEA's to Document Error Proofs to be Implemented) 5 List of all Plant Error Proof Devices Exists and is Located in Document Center 6 Every Error Proof Device Has an Assigned Tracking Number 7 Error Proof Verification Sheets Exist for all Error Proof Devices 8 Master Book of all Error Proof Verification Sheets is in Document Center
3
3 p p a a a
3 3 3
3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 p p
3
3 3 3
3
3 3 3 3 3 3
p 3 3 3 3 p p
3
3 3 3 3 3 3
p p p
p p
p
p p
11 Quality Assurance Conducts Regular Compliance Audits of all Error Proof Devices3 12 Ensure all Repairs go Through Designated Production Error Proof Processes
Rev 28-Jan-00
156
Implementation Status
Plant / Location Plant 2 Plant 3 Plant 4 Plant 5 Plant 6 Plant 7 Plant 21 Plant 23 Cadiz Southhampton Strasbourg Kaiserslautern Livorno Mexico (ACE) Bangalore Works, India DHB / Trinter DAC Lingyun Dongfeng Xiaoshan Shanghai Export Contact George Washington Frazier Crane Jerry Seinfeld Ray Ramano Charlie Sheen George Jefferson Bob Newhart Greg Norman Arnold Palmer Harry Connick Tom Cruise Michael J. Fox Paul McCartney Ali Babba John Daley Mel Gibson Abe Lincoln Kevin Cosner Michael Douglas Robin Williams Tiger Woods Verification Master List Instructions 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 Compliance Log Sheet Audit by Q.A. 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 15MY97 01JN97 01JN97 3
Remember
Error Proofing is not the responsibility of a single individual, but must be accomplished using the teamwork of cross-functional groups.
References
Source Inspection and the Poka-yoke System
Written by Shigeo Shingo Translated by Andrew P. Dillon