Instructions for the 8D Problem Analysis Report HEADER 1) Customer: (e.g., Daimler-Chrysler) 2) Program: (e.g., LH) 3) Product: (e.g., Overhead System) 4) Issue #: JCI issue tracking # (May also include Customer or Supplier tracking #) 5) Date Issue Occurred: Open date for the issue 6) 4D Due Date: Default is 24 hours from date issue occurred 7) 8D Due Date: If applicable. Default is 1 week from date issue occurred 8) Date Issue Closed: All permanent corrective actions have been implemented and their effectiveness validated; All required support documents have been submitted. Discipline 1 Discipline 1. TEAM MEMBERS 1) Champion Name/Title/Phone Number/Email Address: Contact information for the individual who is leading the corrective action and submitting the 4D/8D. 2) Additional Team Member Name(s)/Title(s)/Phone Number(s)/Email Address(es): Contact information for the cross-functional team members who share responsibility for the corrective actions. Discipline 2. PROBLEM DESCRIPTION 1) Description: Describe the issue from a customer’s perspective; what would they know? When: When were the parts manufactured? When were they assembled? When were the assemblies shipped to the customer? When assembled in vehicles? When shipped from OEM? Detection: How was AG made aware of the issue? Who provided the information? Extent: How many units are suspected? Proportion found suspect. Where has the data come from - in house, in transit, at customer. Failure Mode: How does the issue manifest itself? 2) Impact on Customer: Identify the potential for shut down, line interruptions, yard recalls, warranty. etc. 3) Facilities Involved: Customer, JCI and any Suppliers Discipline 3. INTERIM CONTAINMENT 1) What actions were taken to immediately protect the customer and contain any suspect inventory? Since original notification, how are we containing this issue? What is the current containment status? What sorting have we done, where and how have we verified it’s effectiveness? If a rework or retrofit plan has commenced – what is it and how have we verified effectiveness – attach plan with sketches and trend graphs. 2) Other Product/Platform at Risk: Other JCI lines or Customers who may be impacted by this issue 3) Identification of Certified Material: Color, size, location, and content of label or hand-written identification on each part and/or container of certified material. 4) Sorting Results: Time, date, total number sorted and quantity rejected - broken down by facility (e.g., Customer, JCI, Supplier) 5) Interim Containment Start Date: Date Discipline 4. ROOT CAUSE Note: The form provides fields for documentation of a single root cause. If additional root causes are identified, "Copy" rows 2731 and "Insert Cut Cells" to create additional fields. 1) Why Made & How Verified: Identify each root cause for why the issue occurred. Has it been turned on and off? How? Verifiy through statical evidence/hypothesis testing. If not verified by turning on/off, identify as a suspected root cause. Variation: What are opportunities for variation in the process, i.e. how many fixtures do the same process? How many weld cells or robots? Etc. 2) Why Shipped & How Verified: Identify each root cause for why the issue escaped. Has it been turned on and off? How? Verifiy through statical evidence/hypothesis testing. If not verified by turning on/off, identify as a suspected root cause. Discipline 5. PERMANENT CORRECTIVE ACTION Note: The form provides fields for documentation of a single root cause verification. If additional root causes have been identified, "Copy" rows 32-40 (steps1-5) and "Insert Cut Cells" to create additional fields. 1) Corrective Action for Why Made: Identify permanent corrective action(s) planned to address the root cause. 2) Corrective Action for Why Shipped: Identify permanent corrective action(s) planned to address the root cause. Discipline 6. VERIFICATON OF CORRECTIVE ACTIONS 1) Has the issue been turned on and off? How? Verification through statical evidence / hypothesis testing. Verification of corrective action for each why made and why shipped is required. 2) Corrective Action Owner Name/Phone Number/Email Address: Contact information for the individual responsible for implementing the corrective action. 3) Target Completion Date: Date by which all of the corrective actions for this root cause will be implemented. 4) Build Date for Certified Material: "Clean point" at which all material is certified as good.
Page 1 of 2
5) How Will New Parts Be Identified? Color, size, location, and content of label or hand-written identification on each part and/or container of certified material. Discipline 7. PREVENTION 1) How will this issue be avoided in the future? Identify systematic changes that will be put in place to prevent the issue from occurring again. If applicable, standardize the improvements in other "at risk" areas. 2) Has the necessary documentation been updated? Identify the documents that must be updated to include the permanent corrective actions, along with who is responsible for the updates and the dates by which they will be updated. Enter "N/A" if the document does not have to be udpated. Discipline 8. CLOSURE 1) Closure Statement: “Close issue…” (Begin with words noted in “” followed by the rationale for closure.) VERSION OF DOCUMENT 1)
Version 1.5: Formatting text fields imposed.
2)
Version 1.6: IRIS R.11.1 enhancements update.
Page 2 of 2
8D Problem Analysis Report
Template Version 11.4
Customer: JCI Murfreesboro
Date Issue Occurred:
3/31/2011
4D Due Date:
4/1/2011
8D Due Date:
4/8/2011
Date Issue Closed:
6/11/2011
Program:
Nissan X-61B Product: R/H Mounting Bracket assembly Seating System Issue #:
SMRR - #1111982 (Supplier #4057)
For 4D requests, suppliers must, at a minimum, complete the highlighted fields in yellow. (See the Instructions tab for further details). Areas requiring numeric values such as dates and phone numbers must be in a numeric format. 1. Team Members
2. Problem Description
Champion Name
Champion Title
Champion Phone Number
Larry Doe
Plant Manager
(555) 555-5555
Champion E-mail Address
Larry.DoeASupplier.com
Additional Team Member Name(s)
Title(s)
Phone Number(s)
E-mail Address(es)
Jim Doe
Quality Manager
(555) 555-5555
Jim.
[email protected]
Jane Doe
Production Manager
(555) 555-5555
[email protected]
Steve Doe
Maintenance Technician
(555) 555-5555
[email protected]
Description (Describe issue in terms of what, where, when and how many)
On Friday, 4/1/11, (Supplier) received an email notification from (JCI Murfreesboro) regarding missing striker pins on part number 1298712 Rev. 06 Mounting Bracket assembly-Lot #276. This lot of components (2,234 pcs.) were built into assemblies at JCI Murfreesboro 3/30/11, first shift being shipped only to the Nissan Smyrna plant 3/30/11 second shift. Five (5) suspect parts were identified on complete seat assemblies at Nissan Smyrna during first shift 3/31/11. JCI Customer liaison notified immediately and subsequently notification was made to the JCI Murfreesboro facility. It was noted that seats would not latch properly.
Impact on Customer (Identify the potential for shut down, line interruptions, yard recalls, warranty, etc..)
JCI Murfreesboro reported their Customer (Nissan) had (5) seats that had to be swapped out due to missing striker pins causing seat to not latch properly. 100% sort was implemented at JCI Murfreesboro. Yard campaign initiated to validate vehicles located at the Nissan Smyrna facility.
Facilities Involved (Customer, JCI and any Suppliers)
Nissan Smyrna, JCI Murfreesboro, Supplier
3. Interim Containment
What actions were taken to immediately protect the customer and contain any suspect inventory?
1. No WIP Material currently in-house at Customer location (JCI Murfreesboro) - Verified 4/1/11 John Doe - Quality Manager Material identified at Supplier location: 2. (1746) parts contained and isolated with striker rod - Verified 4/1/11 John Doe - Quality Manager (1904) parts contained and isolated with striker rod and pin weld - Verified 4/1/11 John Doe - Quality Manager (905) completed weld and paint contained and isolated - Verified 4/1/11 John Doe - Quality Manager 3. (1,680) parts shipped to JCI on 3/28/11 - Verified John Doe - Quality Manager (1,680) parts shipped to JCI 4/5/11 - Verified 4/6/11 Jim Doe - Production Supervisor 4. JCI currently has 3rd party validating wire presence - Reported to John Doe - Quality Manager - 4/1/11 5. (Supplier) contacted on 4/5/11 @ 11:20am by Murfreesboro informing of containment sort at Nissan Smyrna by 3rd party - Reported to John Doe Quality Manager 6. On 4/6/11 @ 10:35 am (Supplier) received an email from JCI Murfreesboro with attached sort instructions directing (Supplier) to check parts using a screwdriver to apply pressure against striker rod for certification process.
Other Product/Platform at Risk ?
Identification of certified material ?
This specific assembly is not used on any other platform. No other product Conforming assemblies to be identified with a 'Green' dot on the right side of a similar geometry is produced by Supplier. of the lower bracket (See attached photographs). Certified material will have 8.5 x 11.0 certified placards on the container (See attached example). No material will be shipped until certification method has been validated as effective and agreement is secured from receiving Customer plant.
Sorting Results (Time, Date, Total Number Sorted and Quantity Rejected)
1. All parts are currently on hold, shipment of (1,680) pcs on 4/5/11 - 5pm, were sorted and certified per visual rod presence verification as agreed upon with JCI quality representatives on 4/1/11. (0) fallout noted based on this criteria. 2. All suspect material contained in house (4,555 pcs.) will be scrapped to avoid escape point and mitigate any potential risk to Customer 3. (400) vehicles reviewed at Nissan 4/1/11 - Second shift. (0) fallout reported. Interim Containment Start Date
4/5/2011
Page 3 of 403
8D Problem Analysis Report
Template Version 11.4
Customer: JCI Murfreesboro Program:
Nissan X-61B Product: R/H Mounting Bracket assembly Seating System Issue #:
Date Issue Occurred:
3/31/2011
4D Due Date:
4/1/2011
8D Due Date:
4/8/2011
Date Issue Closed:
6/11/2011
SMRR - #1111982 (Supplier #4057)
For 4D requests, suppliers must, at a minimum, complete the highlighted fields in yellow. (See the Instructions tab for further details). Areas requiring numeric values such as dates and phone numbers must be in a numeric format. 1. Team Members
4. Root Cause
For 8D requests, suppliers must, at a minimum, complete the fields highlighted in green. (See the Instructions tab for details) Areas requiring numeric values, such as dates or phone numbers, must be in a numeric format. ROOT CAUSE #1 Why Made & How Verified
1. Assembly produced that exhibited insufficient welding of Striker Pin to lower bracket. Why? Resistance welding operation did not sufficiently fuse Retaining pin to lower bracket Why? Welding pressure was not properly set/controlled to allow for proper fusing of details Why? Several products are produced through this welder. Each with their own individual required parameters (Pneumatic weld pressure being one of those). These are set manually during process set-up, and are not monitored with direct feedback to the machine controller during production operation. It appears during this specific run this was not set properly, or had been changed from the original set up. Why? Equipment did not have sufficient controls installed to ensure this failure mode (insufficient welding of striker pin to bracket) would not occur. How Verified: A study was performed varying the weld pressure during sequential cycles of the weld operation. It was determined that as weld pressure increased this had a negative affect on Proof load values. This progressed to a point where the Striker pin would not meet the (500N) minimum requirement as noted on the print. Why Shipped & How Verified
1. An assembly was shipped to Customer that exhibited insufficient welding of Striker Pin to lower bracket Why? Assembly with an insufficient weld was not detected during current inspection process Why? Weld retention only verified on an audit basis during the production run Why? Weld retention noted as an attribute verification per Control Plan on design record (Drawing no. 1298712 Rev. 6). Manufacturing system was not designed to verify 100% proof load conformance. Why? It was not identified as a specific requirement. How Verified: Audit frequency ((2) parts per shift) was reviewed and determined it would not be sufficient to ensure no escape of this specific non-conformance. ROOT CAUSE #2 Why Made & How Verified
Why Shipped & How Verified
5. Permanent Corrective Action
ROOT CAUSE #1 Corrective Action for Why Made
Page 4 of 403
8D Problem Analysis Report
Template Version 11.4
Customer: JCI Murfreesboro
Date Issue Occurred:
3/31/2011
4D Due Date:
4/1/2011
8D Due Date:
4/8/2011
Date Issue Closed:
6/11/2011
Program:
Nissan X-61B Product: R/H Mounting Bracket assembly Seating System Issue #:
SMRR - #1111982 (Supplier #4057)
5. Permanent Corrective Action 1. Team Members
For 4D requests, suppliers must, at a minimum, complete the highlighted fields in yellow. (See the Instructions tab for further details). Areas requiring numeric values such as dates and phone numbers must be in a numeric format. 1a. Air pressure regulator fabricated to lock out manual air pressure setting. 1b. Inspection implemented after change over to validate proper parameter setting on job running. 1c. Logic and controls upgrade to be performed on existing welder to allow for real time air pressure monitoring and lock out if air parameters are exceeded high or low, requiring a reset by supervision only trough a biometric control. 1d. Read across to all existing ped welders within L&W Plant 2 for logic upgrade so same controls can be implemented throughout plant per time line. 1e. Update all appropriate APQP documents to reflect this specific failure mode and noted counter measures.
Corrective Action for Why Shipped
1a. Addition of 100% Proof load verification of Retaining Pin during locating pin installation 1b. Update all appropriate In-process/ODS documentation as it relates to this specific failure mode.
ROOT CAUSE #2 Corrective Action for Why Made
Corrective Action for Why Shipped
6. Verification of Corrective Action(s)
Verification of Corrective Action: Has the issue been turned on and off? How? Verification through statistical evidence / hypothesis testing. Verification of corrective action for each why made and why shipped is required.
Why Made? After implementation of above referenced corrective actions studies were performed on 4/8/11 with regards to proof load requirements. It was determined that once parameters were set, and the system monitored for conformance to these settings (see attached set-up sheet), proof load performance was statistically capable to the noted tolerance on the engineering drawing. As settings were deviated from this window, proof load performance diminished as expected. (See attached studies) Why Shipped? 100% proof load verification is effective. A sample of (10) parts that had passed on-line verification were taken and destructively tested (See attached results). Results confirm assemblies are conforming. (10) Parts that were purposely not welded were detected on-line and equipment locked as programmed. Corrective Action Owner Name
C.A. Owner Phone Number
C.A. Owner E-mail Address
Target Completion Date
John Doe
(555) 555-5555
[email protected]
5/15/2011
Build Date for Certified Material
How Will New Parts Be Identified?
4/9/2011 7. Prevention
Production certified material to be identified with an 'Orange' shipping label.
How will this issue be avoided in the future?
1. For this specific failure mode, system to be part of on-going layered process audits to ensure manufacturing parameters and assembly performance (proof load) are maintained. 2. Information from 'read across' exercise to be summarized and reviewed. Applicable improvements to be implemented and documented on other similar manufacturing processes.
Has the necessary documentation been updated?
Affected Document
Owner for Update
DFMEA PFMEA Control Plan Process Flow Operation Instructions Drawing Design Standards
Not required John Doe John Doe Jim Doe John Doe Not required Not required
Date
4/11/2011 4/11/2011 4/11/2011 4/11/2011
Page 5 of 403
8D Problem Analysis Report
Template Version 11.4
Customer: JCI Murfreesboro Program:
Nissan X-61B Product: R/H Mounting Bracket assembly Seating System Issue #:
Date Issue Occurred:
3/31/2011
4D Due Date:
4/1/2011
8D Due Date:
4/8/2011
Date Issue Closed:
6/11/2011
SMRR - #1111982 (Supplier #4057)
For 4D requests, suppliers must, at a minimum, complete the highlighted fields in yellow. (See the Instructions tab for further details). Areas requiring numeric values such as dates and phone numbers must be in a numeric format. 1. Closure 8. Team Members
Closure Statement (Validation)
Close issue based on (5) subsequent production runs (10,564 pcs.) that have been produced with (0) fallout for proof load requirement. Customer has reported (0) issues since receiving certified production material. As of 6/11/11, Corrective actions have been deemed effective.
Page 6 of 403
8D Problem Analysis Report
Template Version 11.4
Customer: JCA SEATING (M) SDN BHD
Date Issue Occurred:
Program: GAJC SHIPMENT PARTS
4D Due Date:
Product: REFER TO INVOICE: MALAY 140520
8D Due Date:
Issue #:
Date Issue Closed:
For 4D requests, suppliers must, at a minimum, complete the highlighted fields in yellow. (See the Instructions tab for further details). Areas requiring numeric values such as dates and phone numbers must be in a numeric format. 1. Team Members
Champion Name
Champion Title
Champion Phone Number
Champion E-mail Address
Additional Team Member Name(s)
Title(s)
Phone Number(s)
E-mail Address(es)
GAJC
SUPPLIER
+86 (20)2093 7542
[email protected]
YANGTAO WEN 2. Problem Description
Description (Describe issue in terms of what, where, when and how many)
Refer to the photos, there are a lot of space in the container. Therefore, at time, it is unavoidable that the port transfering the cargo from the port to the ship or vise versa or movement in the sea might cause the cargo to be tilted.Stuffing is done by the shipper and they will sealed the container. Therefore, besides shipper, no one can actually see the cargo in the container. It would be advisable if shipper could latch the cargo on moving instead or reinforce their cargo in plastic pallets or wooden pallets.
Impact on Customer (Identify the potential for shut down, line interruptions, yard recalls, warranty, etc..)
Facilities Involved (Customer, JCI and any Suppliers)
3. Interim Containment
What actions were taken to immediately protect the customer and contain any suspect inventory?
Page 7 of 403
8D Problem Analysis Report
Template Version 11.4
Customer: JCA SEATING (M) SDN BHD Program: GAJC SHIPMENT PARTS Product: REFER TO INVOICE: MALAY 140520 Issue #:
Date Issue Occurred: 4D Due Date: 8D Due Date: Date Issue Closed:
For 4D requests, suppliers must, at a minimum, complete the highlighted fields in yellow. (See the Instructions tab for further details). Areas requiring numeric values such as dates and phone numbers must be in a numeric format. 3. Interim Containment 1. Team Members
Stuffing is done by the shipper and they will sealed the container. Therefore, besides shipper, no one can actually see the cargo in the container. It would be advisable if shipper could latch the cargo on moving instead or reinforce their cargo in plastic pallets or wooden pallets.
Other Product/Platform at Risk ?
Identification of certified material ?
Sorting Results (Time, Date, Total Number Sorted and Quantity Rejected)
Interim Containment Start Date MM/DD/YYYY
For 8D requests, suppliers must, at a minimum, complete the fields highlighted in green. (See the Instructions tab for details) Areas requiring numeric values, such as dates or phone numbers, must be in a numeric format. 4. Root Cause
ROOT CAUSE #1 Why Made & How Verified
Page 8 of 403
8D Problem Analysis Report
Template Version 11.4
Customer: JCA SEATING (M) SDN BHD Program: GAJC SHIPMENT PARTS Product: REFER TO INVOICE: MALAY 140520 Issue #:
4. Root Cause
Date Issue Occurred: 4D Due Date: 8D Due Date: Date Issue Closed:
For 4D requests, suppliers must, at a minimum, complete the highlighted fields in yellow. (See the Instructions tab for further details). Areas requiring numeric values such as dates and phone numbers must be in a numeric format.
1. Team Members
Why Shipped & How Verified
ROOT CAUSE #2 Why Made & How Verified
Why Shipped & How Verified
Page 9 of 403
8D Problem Analysis Report
Template Version 11.4
Customer: JCA SEATING (M) SDN BHD Program: GAJC SHIPMENT PARTS Product: REFER TO INVOICE: MALAY 140520 Issue #:
Date Issue Occurred: 4D Due Date: 8D Due Date: Date Issue Closed:
For 4D requests, suppliers must, at a minimum, complete the highlighted fields in yellow. (See the Instructions tab for further details). Areas requiring numeric values such as dates and phone numbers must be in a numeric format. 1. Team Members
5. Permanent Corrective Action
ROOT CAUSE #1 Corrective Action for Why Made
Corrective Action for Why Shipped
ROOT CAUSE #2 Corrective Action for Why Made
Corrective Action for Why Shipped
Page 10 of 403
8D Problem Analysis Report
Template Version 11.4
Customer: JCA SEATING (M) SDN BHD
Date Issue Occurred:
Program: GAJC SHIPMENT PARTS
4D Due Date:
Product: REFER TO INVOICE: MALAY 140520
8D Due Date:
Issue #:
Date Issue Closed:
For 4D requests, suppliers must, at a minimum, complete the highlighted fields in yellow. (See the Instructions tab for further details). Areas requiring numeric values such as dates and phone numbers must be in a numeric format. 1. Team Members
6. Verification of Corrective Action(s)
7. Prevention
Verification of Corrective Action: Has the issue been turned on and off? How? Verification through statistical evidence / hypothesis testing. Verification of corrective action for each why made and why shipped is required.
Corrective Action Owner Name
C.A. Owner Phone Number
Build Date for Certified Material MM/DD/YYYY
How Will New Parts Be Identified?
Target Completion Date MM/DD/YYYY
Owner for Update
Date MM/DD/YYYY
How will this issue be avoided in the future?
Has the necessary documentation been updated?
8. Closure
C.A. Owner E-mail Address
Affected Document
DFMEA PFMEA Control Plan Process Flow Operation Instructions Drawing Design Standards
Closure Statement (Validation)
Page 11 of 403
Please submit your RMA / Account #'s in the cells below if you are having mate RMA:
RMA #
Account #'s:
UPS # FEDEX # DHL # Airbourne #
(Specify Company)
Other
Supplier Disposition: (Check the box)
Scrap
Address for Return:
Name
(If the Return box is
Street
checked above)
City State Zip
Attention To:
Name
#
Return
None
w if you are having material debited / returned to you:
Anweisungen für den Analysebericht zu 8D-Problemen KOPFZEILE 1) Kunde: (z. B. Daimler-Chrysler) 2) Programm: (z. B. LH) 3) Produkt: (z. B. Dachhimmelsystem) 4) Problem-Nr.: JCI-Problemverfolgungs-Nr. (Enthält evtl. auch Kunden- oder Lieferanten-Verfolgungs-Nr.) 5) Datum, an dem das Problem aufgetreten ist: Eröffnungsdatum für das Problem 6) 4D-Fälligkeitsdatum: Der Standardwert beträgt 24 Stunden, gerechnet ab dem Datum, an dem das Problem aufgetreten ist. 7) 8D-Fälligkeitsdatum: Wenn zutreffend. Der Standardwert beträgt 1 Woche, gerechnet ab dem Datum, an dem das Problem aufgetreten ist. 8) Datum, an dem das Problem geschlossen wurde: Alle permanenten Korrekturmaßnahmen wurden eingeführt und deren Wirksamkeit überprüft. Alle erforderlichen unterstützenden Dokumente wurden eingereicht. TEAMMITGLIEDER 1) Champion-Name/Titel/Telefonnummer/E-Mail-Adresse: Kontaktinformationen für die Person, die die Korrekturmaßnahme leitet und den 4D/8D einreicht. 2) Weitere Namen von Teammitgliedern/Titel/Telefonnummer(n)/E-Mail-Adresse(n): Kontaktinformationen für die bereichsübergreifenden Teammitglieder, die gemeinsam für die Korrekturmaßnahmen zuständig sind.
PROBLEMBESCHREIBUNG 1) Beschreibung: Erläutern Sie das Problem aus der Sicht eines Kunden. Was weiß er darüber? Wann: Wann wurden die Artikel hergestellt? Wann wurden sie montiert? Wann wurden die montierten Einheiten an den Kunden geliefert? Wann wurden sie in den Fahrzeugen eingebaut? Wann wurden sie vom Originalhersteller (OEM) versandt? Erkennung: Wie wurde der AG das Problem mitgeteilt? Wer hat die Informationen bereitgestellt? Ausmaß: Wie viele Einheiten sind zweifelhaft? Proportion wird angezweifelt. Woher stammen die Daten - werksintern, Transportweg, beim Kunden. Fehlermodus: Wie manifestiert sich das Problem? 2) Auswirkung auf den Kunden: Identifizieren Sie das Potenzial für Ausfallzeiten, Unterbrechungen der Fertigungsstraße, Stapelplatzrückrufe, Gara 3) Beteiligte Einrichtungen: Kunde, JCI und alle Lieferanten VORLÄUFIGE RÜCKHALTUNG 1) Welche Maßnahmen wurden ergriffen, um den umgehenden Schutz des Kunden und die Rückhaltung aller verdächtigen Inventarobjekte zu gewährleisten? Wie grenzen wir seit der ursprünglichen Benachrichtigung dieses Problem ein? Wie lautet der aktuelle Zurückhaltungsstatus? Welche Sortierungen haben wir durchgeführt, wo und wie haben wir deren Wirkamkeit verifiziert? Wenn ein Nacharbeits- oder Nachrüstplan in Kraft gesetzt wurde – worum handelt es sich und wie haben wir die Wirksamkeit überprüft – fügen Sie den Plan mit Zeichnungen und Trenddiagrammen bei. 2) Weitere gefährdete Produkte/Plattformen: Andere JCI-Fertigungsstraßen oder Kunden, die von diesem Problem betroffen sein können 3) Identifizierung von zertifiziertem Material: Farbe, Größe, Ort und Inhalt des Etiketts oder handschriftliche Identifikation an den einzelnen Artikeln und/oder Transportverpackungen des zertifizierten Materials. 4) Ergebnisse der Sortierung: Uhrzeit, Datum, Gesamtzahl der Sortierungen und zurückgewiesenen Stückzahl - aufgegliedert nach Einrichtung (z. B. Kunde, JCI, Lieferant) 5) Startdatum für die vorläufige Rückhaltung: Datum
HAUPTURSACHE DER FEHLERENTSTEHUNG Hinweis: Das Formular enthält Felder zur Dokumentation einer Hauptursache für die Fehlerentstehung. Wenn weitere Hauptursachen der Fehlerentstehung (Root Causes) identifiziert werden, kopieren Sie die Zeilen 27 – 31 und fügen sie ein, um zusätzliche Felder zu erstellen. 1) Warum vorgenommen und wie verifiziert: Identifizieren Sie die einzelnen Hauptursachen der Fehlerentstehung, warum das Problem aufgetreten ist. Wurde es ein- und ausgeschaltet? Wie? Verifizieren Sie dies durch statische Nachweise/Hypothesetests. die Verifizierung durch Ein-/Ausschalten nichtim möglich, identifizieren SieVorrichtungen es als eine vermutete Variation: Wie lauten die Ist "Opportunities" (Gelegenheiten) für Variationen Prozess, d. h. wie viele führen denselben Prozess durch? Wie viele Schweißzellen oder Roboter? usw. 2) Warum geliefert und wie verifiziert: Identifizieren Sie die einzelnen Hauptursachen, warum das Problem verschwunden ist. Wurde es ein- und ausgeschaltet? Wie? Verifizieren Sie dies durch statische Nachweise/Hypothesetests. Ist die Verifizierung durch Ein-/Ausschalten nicht möglich, identifizieren Sie es als eine vermutete Ursache. DAUERHAFTE KORREKTURMAßNAHME Hinweis: Das Formular enthält Felder für die Dokumentation der Verifizierung einer Hauptursache für die Fehlerentstehung. Wenn weitere Hauptursachen (Root Causes) identifiziert wurden, kopieren Sie die Zeilen 32 – 40 (Schritte 1 – 5) und fügen sie um zusätzliche Felder zu erstellen. 1) ein, Korrekturmaßnahmen für "Warum vorgenommen": Identifizieren Sie permanente Korrekturmaßnahmen, die zum Angehen der Hauptursache gep 2) Korrekturmaßnahmen für "Warum geliefert": Identifizieren Sie permanente Korrekturmaßnahmen, die zum Angehen der Hauptursache geplant w VERIFIZIERUNG DER KORREKTURMAßNAHMEN 1) Wurde das Problem ein- und ausgeschaltet? Wie? Verifizierung durch statische Nachweise/Hypothesetests. Verifizierung der Korrekturmaßnahmen für jedes "Warum vorgenommen" und "Warum geliefert" ist erforderlich. 2) Name des Verantwortlichen für die Korrekturmaßnahme/Telefonnummer/E-Mail-Adresse: Kontaktinformationen für die Person, die für die Implementierung der Korrekturmaßnahme verantwortlich ist. 3) Angestrebtes Abschlussdatum: Datum, an dem alle Korrekturmaßnahmen für diese Hauptursache implementiert sind. Page 14 of 2
4) Aufbaudatum für zertifiziertes Material: "Bereinigungspunkt", an dem alle Materialien für "in Ordnung" befunden wurden. 5) Wie werden neue Teile identifiziert? Farbe, Größe, Ort und Inhalt des Etiketts oder handschriftliche Identifikation an den einzelnen Artikeln und/oder Transportverpackungen des zertifizierten Materials. PRÄVENTION 1) Wie wird dieses Problem in Zukunft verhindert? Identifizieren Sie systematische zu implementierende Änderungen, damit das Problem nicht wieder auftritt. Wenn zutreffend, standardisieren Sie die Verbesserungen in anderen gefährdeten Bereichen. 2) Wurde die erforderliche Dokumentation aktualisiert? Geben Sie die Dokumente an, die bezüglich folgender Punkte aktualisiert werden müssen: permanente Korrekturmaßnahmen, Verantwortlicher für die Aktualisierungen sowie Termine, bis zu denen sie aktualisiert sein werden. Geben Sie "N/A" (nicht zutreffend) ein, wenn das Dokument nicht aktualisiert werden muss.
ABSCHLUSS 1) Abschlusserklärung: "Abschließen von Problem …" (Beginnen Sie mit den Worten in den Anführungszeichen, gefolgt von der Begründung für de VERSION DES DOKUMENTES 1)
Version 1.5: Formatierung der Textfelder verbessert.
2)
Version 1.6: IRIS R.11.1 enhancements update.
Page 15 of 2
oche, gerechnet ab dem Datum, an dem das Problem aufgetreten ist.
lzeiten, Unterbrechungen der Fertigungsstraße, Stapelplatzrückrufe, Garantieleistungen usw.
en oder Kunden, die von diesem Problem betroffen sein können
ermanente Korrekturmaßnahmen, die zum Angehen der Hauptursache geplant wurden. ente Korrekturmaßnahmen, die zum Angehen der Hauptursache geplant wurden.
Page 16 of 2
den Worten in den Anführungszeichen, gefolgt von der Begründung für den Abschluss.)
Page 17 of 2
Analysebericht zu 8D-Problemen Kunde:
Datum, an dem das Problem aufgetreten ist:
Programm:
4D-Fälligkeitsdatum:
Produkt:
8D-Fälligkeitsdatum:
Problem-Nr.:
Datum, an dem das Problem geschlossen wurde:
Vom Lieferanten sind die gelb hervorgehobenen Formularbereiche für den 4D auszufüllen. (Siehe die vorstehende Registerkarte 'Anweisungen' für weitere Informationen). Zellen, die numerische wie Datumsangaben oder Telefonnummern enthalten sollen, müssen Zahlenangaben enthalten. 1. Teammitglieder
2. Problembeschreibung
Champion-Name
Champion-Titel
Champion-Telefonnummer
Namen von weiteren Teammitgliedern
Titel
Telefonnummer(n)
Beschreibung (Erläutern Sie das Problem, indem Sie folgende Fragen stellen: "Was?", "Wo?", "Wann?" und "Wie viele?".)
Auswirkung auf den Kunden (Identifizieren Sie das Potenzial für Ausfallzeiten, Unterbrechungen der Fertigungsstraße, Stapelplatzrückrufe, Garantieleistungen usw.)
Beteiligte Einrichtungen (Kunde, JCI und Lieferanten)
3. Vorläufige Rückhaltung
Welche Maßnahmen wurden ergriffen, um den umgehenden Schutz des Kunden und die Rückhaltung aller verdächtigen Inve zu gewährleisten?
Weitere gefährdete Produkte/Plattformen?
Identifizierung von zertifiziertem Material?
Analysebericht zu 8D-Problemen 3. Vorläufige Rückhaltung Kunde:
Datum, an dem das Problem aufgetreten ist:
Programm:
4D-Fälligkeitsdatum:
Produkt:
8D-Fälligkeitsdatum:
Problem-Nr.:
Datum, an dem das Problem geschlossen wurde:
Vom Lieferanten sind die gelb hervorgehobenen Formularbereiche für den 4D auszufüllen. (Siehe die vorstehende Registerkarte 'Anweisungen' für weitere Informationen). Zellen, die numerische wie Datumsangaben oder Telefonnummern enthalten sollen, müssen Zahlenangaben enthalten. 1. Teammitglieder
Ergebnisse der Sortierung (Uhrzeit, Datum, Gesamtzahl der Sortierungen und zurückgewiesene Menge)
Startdatum für die vorläufige Rückhaltung DD.MM.YYYY
Vom Lieferanten sind die grün hervorgehobenen Formularbereiche für den 8D auszufüllen. (Sieh die vorstehende Registerkarte 'Anweisungen'). Zellen, die numerische Werte wie Datumsangabe Telefonnummern enthalten sollen, müssen Zahlenangaben enthalten. 4. Hauptursache
HAUPTURSACHE NR. 1 Warum vorgenommen und wie verifiziert
Warum geliefert und wie verifiziert
HAUPTURSACHE NR. 2 Warum vorgenommen und wie verifiziert
Analysebericht zu 8D-Problemen Kunde:
Datum, an dem das Problem aufgetreten ist:
Programm:
4D-Fälligkeitsdatum:
Produkt:
8D-Fälligkeitsdatum:
Problem-Nr.:
Datum, an dem das Problem geschlossen wurde:
Vom Lieferanten sind die gelb hervorgehobenen Formularbereiche für den 4D auszufüllen. (Siehe die vorstehende Registerkarte 'Anweisungen' für weitere Informationen). Zellen, die numerische wie Datumsangaben oder Telefonnummern enthalten sollen, müssen Zahlenangaben enthalten. 1. Teammitglieder
Warum geliefert und wie verifiziert
5. Permanente Korrekturmaßnahmen
HAUPTURSACHE NR. 1 Korrekturmaßnahmen für "Warum vorgenommen"
Korrekturmaßnahmen für "Warum geliefert"
HAUPTURSACHE NR. 2 Korrekturmaßnahmen für "Warum vorgenommen"
Analysebericht zu 8D-Problemen Kunde:
Datum, an dem das Problem aufgetreten ist:
Programm:
4D-Fälligkeitsdatum:
Produkt:
8D-Fälligkeitsdatum:
Problem-Nr.:
Datum, an dem das Problem geschlossen wurde:
Vom Lieferanten sind die gelb hervorgehobenen Formularbereiche für den 4D auszufüllen. (Siehe die vorstehende Registerkarte 'Anweisungen' für weitere Informationen). Zellen, die numerische wie Datumsangaben oder Telefonnummern enthalten sollen, müssen Zahlenangaben enthalten. 1. Teammitglieder
Korrekturmaßnahmen für "Warum geliefert"
6. Verifizierung der Korrekturmaßnahmen
Verifizierung der Korrekturmaßnahmen: Wurde das Problem ein- und ausgeschaltet? Wie? Verifizierung durch statische Nachweise/Hypothesetests. Verifizierung der Korrekturmaßnahmen für jedes "Warum vorgenommen" und "Warum geliefert" i erforderlich.
Name d.Verantw. f.d. Korrekturm. Telefon-Nr. des Verantw. f.d.KM
Aufbaudatum für zertif. Material DD.MM.YYYY
7. Prävention
E-Mail-Adresse d.Verantw. f.d.KM
Wie werden neue Teile identifiziert?
Wie wird dieses Problem in Zukunft verhindert?
Wurde die erforderliche Dokumentation aktualisiert?
Betroffenes Dokument DFMEA PFMEA Kontrollplan Prozessfluss Betriebsanweisungen Zeichnung Designstandards
Verantw. für die Aktualisierung
Analysebericht zu 8D-Problemen Kunde:
Datum, an dem das Problem aufgetreten ist:
Programm:
4D-Fälligkeitsdatum:
Produkt:
8D-Fälligkeitsdatum:
Problem-Nr.:
Datum, an dem das Problem geschlossen wurde:
Vom Lieferanten sind die gelb hervorgehobenen Formularbereiche für den 4D auszufüllen. (Siehe die vorstehende Registerkarte 'Anweisungen' für weitere Informationen). Zellen, die numerische wie Datumsangaben oder Telefonnummern enthalten sollen, müssen Zahlenangaben enthalten. 1. Abschluss Teammitglieder 8.
Abschlusserklärung
Analysebericht zu 8D-Problemen Datum, an dem das Problem aufgetreten ist:
Datum, an dem das Problem geschlossen wurde:
die gelb hervorgehobenen Formularbereiche für den 4D auszufüllen. (Siehe auch terkarte 'Anweisungen' für weitere Informationen). Zellen, die numerische Werte der Telefonnummern enthalten sollen, müssen Zahlenangaben enthalten. Champion-E-Mail-Adresse
E-Mail-Adresse(n)
das Problem, indem Sie folgende Fragen stellen: "Was?", "Wo?", "Wann?" und "Wie viele?".)
(Identifizieren Sie das Potenzial für Ausfallzeiten, Unterbrechungen der Fertigungsstraße, eistungen usw.)
de, JCI und Lieferanten)
ergriffen, um den umgehenden Schutz des Kunden und die Rückhaltung aller verdächtigen Inventarobjekte
Identifizierung von zertifiziertem Material?
Analysebericht zu 8D-Problemen Datum, an dem das Problem aufgetreten ist:
Datum, an dem das Problem geschlossen wurde:
die gelb hervorgehobenen Formularbereiche für den 4D auszufüllen. (Siehe auch terkarte 'Anweisungen' für weitere Informationen). Zellen, die numerische Werte der Telefonnummern enthalten sollen, müssen Zahlenangaben enthalten.
hrzeit, Datum, Gesamtzahl der Sortierungen und zurückgewiesene Menge)
Rückhaltung DD.MM.YYYY
die grün hervorgehobenen Formularbereiche für den 8D auszufüllen. (Siehe auch terkarte 'Anweisungen'). Zellen, die numerische Werte wie Datumsangaben oder alten sollen, müssen Zahlenangaben enthalten.
e verifiziert
iziert
e verifiziert
Analysebericht zu 8D-Problemen Datum, an dem das Problem aufgetreten ist:
Datum, an dem das Problem geschlossen wurde:
die gelb hervorgehobenen Formularbereiche für den 4D auszufüllen. (Siehe auch terkarte 'Anweisungen' für weitere Informationen). Zellen, die numerische Werte der Telefonnummern enthalten sollen, müssen Zahlenangaben enthalten.
iziert
arum vorgenommen"
arum geliefert"
arum vorgenommen"
Analysebericht zu 8D-Problemen Datum, an dem das Problem aufgetreten ist:
Datum, an dem das Problem geschlossen wurde:
die gelb hervorgehobenen Formularbereiche für den 4D auszufüllen. (Siehe auch terkarte 'Anweisungen' für weitere Informationen). Zellen, die numerische Werte der Telefonnummern enthalten sollen, müssen Zahlenangaben enthalten.
arum geliefert"
ßnahmen: Wurde das Problem ein- und ausgeschaltet? Wie? Verifizierung durch statische erifizierung der Korrekturmaßnahmen für jedes "Warum vorgenommen" und "Warum geliefert" ist
Angestrebtes Abschlussdatum DD.MM.YYYY
Wie werden neue Teile identifiziert?
ukunft verhindert?
Datum DD.MM.YYYY
Analysebericht zu 8D-Problemen Datum, an dem das Problem aufgetreten ist:
Datum, an dem das Problem geschlossen wurde:
die gelb hervorgehobenen Formularbereiche für den 4D auszufüllen. (Siehe auch terkarte 'Anweisungen' für weitere Informationen). Zellen, die numerische Werte der Telefonnummern enthalten sollen, müssen Zahlenangaben enthalten.
Instructions relatives au rapport d'analyse des problèmes 8D EN-TETE 1) Client : (par ex., Daimler-Chrysler) 2) Programme : (par ex., LH) 3) Produit : (par ex., système de pavillon) 4) N° problème : n° de suivi du problème JCI (peut comprendre un n° de suivi du client ou du fournisseur) 5) Date d'apparition du problème : date d'ouverture du problème 6) Date de remise du 4D : la valeur par défaut est de 24 heures à compter de la date d'apparition du problème 7) Date de remise du 8D : le cas échéant. La valeur par défaut est de 1 semaine à compter de la date d'apparition du problème 8) Date de clôture du problème : toutes les actions correctives permanentes ont été mises en œuvre et leur efficacité a été validée ; tous les documents justificatifs requis ont été présentés. MEMBRES D'EQUIPE 1) Nom/Fonction/Numéro tél./adresse e-mail du Champion : informations relatives à la personne qui est responsable de l'action corrective et qui soumet le 4D/8D. 2) Nom/Fonction/Numéro de tél./adresse e-mail des autres membres d'équipe : informations relatives aux membres de l'équipe pluridisciplinaire qui partagent la responsabilité des actions correctives. DESCRIPTION DU PROBLEME 1) Description : décrire le problème sous l'angle du client ; qu'est-ce qu'il en saurait ? Quand : Quand les pièces ont-elles été produites ? Quand ont-elles été assemblées ? Quand les ensembles ont-ils été expédiés au client ? Quand ont-il été montés dans les véhicules ? Quand ont-ils été expédiés par l'OEM ? Détection : Comment l'AG a-t-il découvert le problème ? Qui a fourni les informations correspondantes ? Etendue : Combien d'unités sont suspectées ? Proportion déterminée comme suspecte. D'où proviennent les données - en interne, pendant le transport, chez le client. Mode de défaillance : Comment le problème se manifeste-t-il ? 2) Impact sur le client : identifier le risque d'arrêt de la production, d'interruptions sur la chaîne, de rappel de produits, de garantie, etc. 3) Sites concernés : client, JCI et fournisseurs CONTAINMENT PROVISOIRE 1) Quels mesures ont été prises afin de protéger immédiatement le client et d'isoler tout stock suspect ? Depuis la notification initiale, comment maîtrisons-nous le problème? Quel est le statut de containment actuel ? Quel tri avons-nous réalisé, où et comment avons-nous vérifié l'efficacité de ce tri ? Si un plan de réusinage et de retouche a débuté – en quoi consiste-t-il et comment avons-nous vérifié son efficacité – joindre le plan avec les croquis et les graphiques de tendance. 2) Risque pour quel autre produit/plateforme : autres chaînes JCI ou clients qui pourraient subir les conséquences du problème 3) Identification des produits certifiés : couleur, taille, emplacement, et contenu de l'étiquette ou de l'identification manuscrite sur chaque pièce et/ou container de produits certifiés. 4) Résultats du tri : heure, date, nombre total de produits triés et quantité refusée - données ventilées par site (par ex., client, JCI, fournisseur) 5) Date de début du containment provisoire : date CAUSE PREMIERE Remarque : le formulaire contient des champs permettant de décrire une seule cause première. Si d'autres causes premières sont identifiées, "copier" les lignes 27-31 et "coller" les cellules correspondantes afin de créer des champs supplémentaires. 1) Pourquoi apparu & comment vérifié : identifier chaque cause première de l'apparition du problème. A-t-il été activé et désactivé ? Comment ? A vérifier sur la base de données statistiques/vérifications d'hypothèses. Si une vérification par une activation/désactivation n'est pas possible, l'identifier comme une cause première possible. Ecart : quels sont les risques d'écarts au niveau du process, c.-à-d. combien d'installations réalisent le même process ? Combien de cellules de soudage ou de robots ? Etc. 2) Pourquoi expédié & comment vérifié : identifier chaque cause première de la non-identification du problème. A-t-il été activé, puis désactivé ? Comment ? A vérifier sur la base de données statistiques/vérifications d'hypothèses. Si une vérification par une activation/désactivation n'est pas possible, l'identifier comme une cause première possible. ACTION CORRECTIVE PERMANENTE Remarque : le formulaire contient des champs permettant de décrire une seule cause première. Si d'autres causes premières sont identifiées, "copier" les lignes 32-40 (points 1-5) et "coller" les cellules correspondantes afin de créer des champs supplémentaires. 1) Action corrective pour la question "Pourquoi apparu" : identifier une/des action(s) corrective(s) permanente(s) prévue(s) pour traiter la cause première. 2) Action corrective pour la question "Pourquoi expédié" : identifier une/des action(s) corrective(s) permanente(s) prévues pour traiter la cause première. Page 28 sur 2
VERIFICATON DES ACTIONS CORRECTIVES 1) Le problème a-t-il été activé et désactivé ? Comment ? Vérification sur la base de données statistiques/vérifications d'hypothèses. L'action corrective doit être vérifiée pour chaque point sous "Pourquoi apparu" et sous "Pourquoi expédié". 2) Nom/Numéro tél./adresse e-mail du responsable de l'action corrective : informations relatives à la personne chargée de mettre l'action corrective en œuvre. 3) Date d'exécution prévue : date d'ici laquelle toutes les actions correctives seront mises en œuvre pour cette cause première. 4) Date de fabrication des produits certifiés : "point propre" à partir duquel tous les produits sont certifiés corrects. 5) Comment les nouvelles pièces seront-elles identifiées ? couleur , taille, emplacement, et contenu de l'étiquette ou de l'identification manuscrite sur chaque pièce et/ou container de produits certifiés. PREVENTION 1) Comment ce problème sera-t-il évité à l'avenir ? Identifier les modifications systématiques qui seront mises en place afin de prévenir toute réapparition du problème. Le cas échéant, standardiser les améliorations dans d'autres zones "à risque". 2) La documentation requise a-t-elle été mise à jour ? Identifier les documents qui doivent être mis à jour afin d'intégrer les actions correctives permanentes, et préciser la personne responsable des mises à jour ainsi que la date d'ici laquelle les documents seront mis à jour. Saisir "S.O." si une mise à jour des documents n'est pas requise. CLOTURE 1) Déclaration de clôture : "Clôture du probème…" (commencer pas les mots placés entre "", puis décrire la justification de la clôture.) 2) Version 1.6: IRIS R.11.1 enhancements update.
Page 29 sur 2
Rapport d'analyse des problèmes 8D Client :
Date d'apparition du problème :
Programme :
Date de remise du 4D :
Produit :
Date de remise du 8D :
N° problème :
Date de clôture du problème :
Les fournisseurs doivent au moins remplir les zones surlignées en jaune pour le formulaire 4D. (Utilisez les instructions dan l'ongelt précédent pour plus de détails). Les valeurs numeriques telles que les dates, les numéros de téléphone doit être en format numérique. 1. Membres d'équipe
Nom du Champion
Fonction du Champion
Ajouter le nom du/des membre(s) Fonction(s) d'équipe
2. Description du problème
Numéro tél. du Champion
Adresse e-mail du Champion
Numéro(s) de téléphone
Adresse(s) e-mail
Description (décrire le problème en répondant aux questions : quoi, où, quand et combien)
Impact sur le client (identifier le risque d'arrêt de la production, d'interruptions sur la chaîne, de rappel de produits, de garantie, etc.)
Sites concernés (client, JCI et fournisseurs)
3. Containment provisoire
Quelles mesures ont été prises afin de protéger immédiatement le client et d'isoler tout stock suspect ?
Rapport d'analyse des problèmes 8D Client :
Date d'apparition du problème :
Programme :
Date de remise du 4D :
Produit :
Date de remise du 8D :
N° problème :
Date de clôture du problème :
3. Containment 1. provisoire Membres d'équipe
Les fournisseurs doivent au moins remplir les zones surlignées en jaune pour le formulaire 4D. (Utilisez les instructions dan l'ongelt précédent pour plus de détails). Les valeurs numeriques telles que les dates, les numéros de téléphone doit être en format numérique.
Risque pour quel autre produit/plateforme ?
Identification des produits certifiés ?
Résultats du tri (heure, date, nombre total de produits triés et quantité refusée)
Date de début du containment provisoire DD.MM.YYYY
Pour les demandes 8D le fourniesseur doit au moins remplir les zones en vert dans le formulaire. (Utilisez les instructions dans l'onglet précédent). Les valeurs numeriques telles que les dates, les numéros de téléphone doit être en format numérique. 4. Cause première
CAUSE PREMIERE N° 1 Pourquoi apparu & comment vérifié
Rapport d'analyse des problèmes 8D Client :
Date d'apparition du problème :
Programme :
Date de remise du 4D :
Produit :
Date de remise du 8D :
N° problème :
Date de clôture du problème :
4. Cause première
Les fournisseurs doivent au moins remplir les zones surlignées en jaune pour le formulaire 4D. (Utilisez les instructions dan l'ongelt précédent pour plus de détails). Les valeurs numeriques telles que les dates, les numéros de téléphone doit être en format numérique.
1. Membres d'équipe
Pourquoi expédié & comment vérifié
CAUSE PREMIERE N° 2 Pourquoi apparu & comment vérifié
Pourquoi expédié & comment vérifié
Rapport d'analyse des problèmes 8D Client :
Date d'apparition du problème :
Programme :
Date de remise du 4D :
Produit :
Date de remise du 8D :
N° problème :
Date de clôture du problème :
Les fournisseurs doivent au moins remplir les zones surlignées en jaune pour le formulaire 4D. (Utilisez les instructions dan l'ongelt précédent pour plus de détails). Les valeurs numeriques telles que les dates, les numéros de téléphone doit être en format numérique. 1. Membres d'équipe
5. Action corrective permanente
CAUSE PREMIERE N° 1 Action corrective pour la question "Pourquoi apparu"
Action corrective pour la question "Pourquoi expédié"
CAUSE PREMIERE N° 2 Action corrective pour la question "Pourquoi apparu"
Rapport d'analyse des problèmes 8D Client :
Date d'apparition du problème :
Programme :
Date de remise du 4D :
Produit :
Date de remise du 8D :
N° problème :
Date de clôture du problème :
Les fournisseurs doivent au moins remplir les zones surlignées en jaune pour le formulaire 4D. (Utilisez les instructions dan l'ongelt précédent pour plus de détails). Les valeurs numeriques telles que les dates, les numéros de téléphone doit être en format numérique. 1. Membres d'équipe
Action corrective pour la question "Pourquoi expédié"
6. Vérification des actions correctives
Vérification de l'action corrective : le problème a-t-il été activé et désactivé ? Comment ? Vérification sur la base de données statistiques / vérifications d'hypothèses. L'action corrective doit être vérifiée pour chaque point sous "Pourquoi apparu" et sous "Pourquoi expédié".
Nom du responsable de l'action corrective (A.C.)
Numéro tél. responsable A.C.
Adresse e-mail responsable A.C.
Date d'exécution prévue DD.MM.YYYY
6. Vérification des actions correctives
Rapport d'analyse des problèmes 8D Client :
Date d'apparition du problème :
Programme :
Date de remise du 4D :
Produit :
Date de remise du 8D :
N° problème :
Date de clôture du problème :
Les fournisseurs doivent au moins remplir les zones surlignées en jaune pour le formulaire 4D. (Utilisez les instructions dan l'ongelt précédent pour plus de détails). Les valeurs numeriques telles que les dates, les numéros de téléphone doit être en format numérique. 1. Membres d'équipe Date de fabrication des produits certifiés DD.MM.YYYY
7. Prévention
Comment les nouvelles pièces seront-elles identifiées ?
Comment ce problème sera-t-il évité à l'avenir ?
La documentation requise a-telle été mise à jour ?
Document concerné AMDEC de conception AMDEC de process Plan de surveillance Déroulement du processus Instructions de service Plans Normes de conception
8. Clôture
Déclaration de clôture
Responsable des mises à jour
Date d'exécution prévue DD.MM.YYYY
Instructions for the 8D Problem Analysis Report 8D问题分析报告的使用说明 请仔细阅读这些指示前仔细填写此表。阿四维请求,您需要填写表格由纪律1到3 。一个8D请求要求您更新四维信息和完成所有剩余的学科( 8 ) 。截止日期四维和8Ds是明确规定在SMRR或移民和难民事务部报告,附于原始电子邮件通知您的问题。 4Ds必须确保供应商立即采取行动,其设施和/或仓库,以确保问题载。您需要通过电子邮件答复各方复制的原始电子邮件,并附上适 当的四维或8D反应。 HEADER 标题 1) Supplier/Location: (e.g., ABC Plastics, Markham, Ontario)供应商/地点: (例如,美国广播公司塑料,马克姆,安大略省) 2) Customer: (e.g., Daimler-Chrysler) 顾客:(如:戴姆勒-克莱斯勒) 3) Program: (e.g., LH) 项目:(如:LH) 4) Product: \ (e.g., Overhead System) 产品名称:(如:顶部系统) 5) Issue #: JCI issue tracking # (May also include Customer or Supplier tracking #) 流水号:JCI跟踪流水号(可包括客户和供应商的跟踪号) 6) Date Issue Occurred: Open date for the issue 问题发生的日期:问题开始的日期 7) 4D Due Date: Default is 24 hours from date issue occurred 4D完成日期:默认情况下为问题发生后24小时 8) 8D Due Date: If applicable. Default is 1 week from date issue occurred 8D完成日期:若可以,默认情况下为问题发生后1周。 9) Date Issue Closed: All permanent corrective actions have been implemented and their effectiveness validated; All required support documents have been submitted. 问题发生的日期:所有的永久性纠正措施已经落实且其有效性已得到验证;所有要求的支持性文件已经递交。 纪律 1. TEAM MEMBERS 团队成员 1) Champion Name/Title/Phone Number/Email Address: Contact information for the individual who is leading the corrective action and submitting the 4D/8D. 负责人姓名/职位/电话号码/Email地址:领导该纠正措施和递交4D/8D报告负责人的个人联系信息。 2) Additional Team Member Name(s)/Title(s)/Phone Number(s)/Email Address(es): Contact information for the cross-functional team members who share responsibility for the corrective actions. 其它团队成员姓名/职位/电话号码/Email地址:共同负责该纠正措施的跨功能团队成员的联系信息。 纪律 2. PROBLEM DESCRIPTION 问题描述 1) Description: Describe the issue from a customer’s perspective; what would they know? 描述: 以客户的感知来描述该问题,他们想知道什么? When: When were the parts manufactured? When were they assembled? When were the assemblies shipped to the customer? When assembled in vehicles ? When shipped from OEM?
什么时候:这些零件是什么时候制造的?它们是什么时候装配的?装配件是什么时候发送到客户处的?什么时候装配在 汽车 上 的?什么时候从原始设备制造商发运的? Detection: How was AG made aware of the issue? Who provided the information? 发现: AG 是如何知道该事情的?谁提供的信息? Extent: How many units are suspected? Proportion found suspect. Where has the data come from - in house, in transit, at customer. 范围:有多少可疑的产品?发现的怀疑部分的比例是多少,信息来自何处 ? -在厂内、运输途中、客户处。 Failure Mode: How does the issue manifest itself? 失效模式:问题本身的表现形式是什么? 2) Impact on Customer: Identify the potential for shut down, line interruptions, yard recalls, warranty. etc. 对客户的影响:确认可能的停工、生产线中断、现场召回、保用费用等) 3) Facilities Involved: Customer, JCI and any Suppliers 涉及的环节:客户、江森自控和其它供应商。 纪律 3. INTERIM CONTAINMENT 临时措施 1) What actions were taken to immediately protect the customer and contain any suspect inventory? Since original notification, how are we containing this issue? What is the current containment status? What sorting have we done, where and how have we verif
2) Other Product/Platform at Risk: Other JCI lines or Customers who may be impacted by this issue 其它存在风险的产品/场合:其它可能由此问题影响到的JCI生产线或客户 3) Identification of Certified Material: Color, size, location, and content of label or hand-written identification on each part and/or container of certified material.认可后的材料辨识:在每一个经认可的物料零件和/或包装上有以颜色、尺寸、位置、标签内容或者手写的识别标记。
4) Sorting Results: Time, date, total number sorted and quantity rejected - broken down by facility (e.g., Customer, JCI, Supplier) 筛选结果: 时间、日期、已挑选的总数和被退回的数量-按产品所在地进行分解(如:客户,JCI,供应商) 5) Interim Containment Start Date: Date 临时措施启动日期:日期 纪律 4 ROOT CAUSE 根本原因 Note: The form provides fields for documentation of a single root cause. If additional root causes are identified, "Copy" rows 27-31 and "Insert Cut Cells" to create additional fields. 注意:表格提供了填写单个根本原因的位置,若发现还有其它根本原因,复制17-31行并“插入剪切单元格”可获得更多的位置。 1) Why Made & How Verified: Identify each root cause for why the issue occurred. Has it been turned on and off? How? Verify through statical evidence/hypothesis testing. If not verified by turning on/off, identify as a suspected root cause. 什么原因导致在制造过程发生问
Variation: What are opportunities for variation in the process, i.e. how many fixtures do the same process? How many weld cells or robots? Etc.
变异:过程中的变异机会是什么?比如说:在同一过程中有使用了多少工装?使用了多少焊接单元或者焊接机器人等等? 2) Why Shipped & How Verified: Identify each root cause for why the issue escaped. Has it been turned on and off? How? Verify through statical evidence/hypothesis testing. If not verified by turning on/off, identify as a suspected root cause. 什么原因导致在发运过程中
纪律 5. PERMANENT CORRECTIVE ACTION 永久性纠正措施 Note: The form provides fields for documentation of a single root cause verification. If additional root causes have been identified, "Copy" rows 32-40 (steps1-5) and "Insert Cut Cells" to create additional fields. 注意:表格提供了填写单个根本原因的位置,若发现还有其它根本原因,复制32-40 1) Corrective Action for Why Made: Identify permanent corrective action(s) planned to address the root cause. 针对造成制造问题根原因的纠正措施:辨识出针对于根原因的永久性纠正措施 2) Corrective Action for Why Shipped: Identify permanent corrective action(s) planned to address the root cause. 针对造成发运问题根原因的纠正措施:辨识出针对根原因的永久性纠正措施 纪律 6. VERIFICATION OF CORRECTIVE ACTIONS 纠正措施的确认 1) Has the issue been turned on and off? How? Verification through statical evidence / hypothesis testing. Verification of corrective action for each why made and why shipped is required. 问题依然存在还是已经消除?如何存在或消除的?通过静态证据和假设检验核实。必须对影响制造和发运过程的每一个纠正措施进 行确认。 2) Corrective Action Owner Name/Phone Number/Email Address: Contact information for the individual responsible for implementing the corrective action. 纠正措施负责人的姓名/电话号码/Email地址:负责执行纠正措施人员的个人联系信息 3) Target Completion Date: Date by which all of the corrective actions for this root cause will be implemented. 预计完成日期:所有针对此根原因的纠正措施得到落实的日期。 4) Build Date for Certified Material: "Clean point" at which all material is certified as good. 记录认可物料的日期:“完好点”,此点起的所有物料都确认为是好的。 5) How Will New Parts Be Identified? Color, size, location, and content of label or hand-written identification on each part and/or container of certified material. 新零件如何被识别? 在每一个经认可物料的零件和/或包装上有以颜色、尺寸、位置、标签内容或者手写的识别标记。 纪律 7. PREVENTION 预防 1) How will this issue be avoided in the future? Identify systematic changes that will be put in place to prevent the issue from occurring again. If applicable, standardize the improvements in other "at risk" areas. 今后如何避免这种问题(的再发生)?识别需落实到位的系统性变更以防止该类问题的再发 2) Has the necessary documentation been updated? Identify the documents that must be updated to include the permanent corrective actions, along with who is responsible for the updates and the dates by which they will be updated. Enter "N/A" if the document
纪律 8. CLOSURE 关闭
1) Closure Statement: “Close issue…” (Begin with words noted in “” followed by the rationale for closure.) 项目关闭陈述:“关闭事件„„” (在描述完为什么关闭的原因后,以“关闭事件„„”为开头)
8D Problem Analysis Report 8D问题分析报告 Supplier/供应商: Customer/顾客:
Date Issue Occurred/起始日期:
Program/项目:
4D Due Date/4D完成日期:
Product/产品:
8D Due Date/8D完成日期:
Issue#/流水号:
Date Issue Closed/关闭日期:
Advanced Development Concept Development Product Definition
对于四维要求供应商必须至少填写表格,在黄色的领域。 (使用说明详情)在以前的标签。地方需要,如日期数值,电话号码必须是数字格式 1. Team Members 团队成员
2. Problem Description 问题描述
Champion Name 负责人姓名
Champion Title 负责人职位
Champion Phone Number 负责人电话号码
Champion E-mail Address 负责人E-mail地址
Additional Team Member Name(s) 其他团队成员姓名
Title(s) 职位
Phone Number(s) 电话号码
E-mail Address(es) E-mail地址
Description (Describe issue in terms of what, where, when and how many) 描述(按照何事、何地、何时、多少数量描述问题)
Impact on Customer (Identify the potential for shut down, line interruptions, yard recalls, warranty, etc..) 对客户的影响(辨识可能的停工、生产线中断、现场召回、保用等)
Facilities Involved (Customer, JCI and any Suppliers) 涉及到的设备(客户、江森自控及其它供应商)
3. Interim Containment 临时措施
What actions were taken to immediately protect the customer and contain any suspect inventory? 采取何种措施以尽快保护客户并控制可疑的库存物品?
Other Product/Platform at Risk ? 其它产品也存在风险吗?
Identification of certified material ? 认可后的材料如何辨识?
Sorting Results (Time, Date, Total Number Sorted and Quantity Rejected) 筛选结果(时间、日期、挑选的总数和不合格品数)
Interim Containment Start Date临时措施的启动日期 MM/DD/YYYY
对于8D要求供应商必须至少填写了突出的地区,在绿色的形式。 (在以前的标签使用说明书)规定的领域,如数值日期,电话号码必须是数字格式 4. Root Cause 根本原因
ROOT CAUSE # 1/根本原因 Why Made & How Verified/什么原因导致在制造过程发生问题及如何验证这些原因
Why Shipped & How Verified/什么原因导致在发运前没有发现质量问题并如何验证这些原因
ROOT CAUSE # 2/根本原因 Why Made & How Verified/什么原因导致在制造过程发生问题及如何验证这些原因
Why Shipped & How Verified/什么原因导致在发运前没有发现质量问题并如何验证这些原因
5. Permanent Corrective Action 永久性纠正措施
ROOT CAUSE # 1/根本原因 Corrective Action for Why Made /针对影响制造过程根原因的纠正措施
Corrective Action for Why Shipped /针对影响发运过程根原因的纠正措施
8D Problem Analysis Report 8D问题分析报告 5. Permanent Corrective Action 永久性纠正措施 Supplier/供应商: Customer/顾客:
Date Issue Occurred/起始日期:
Program/项目:
4D Due Date/4D完成日期:
Product/产品:
8D Due Date/8D完成日期:
Issue#/流水号:
Date Issue Closed/关闭日期:
Advanced Development Concept Development Product Definition
对于四维要求供应商必须至少填写表格,在黄色的领域。 (使用说明详情)在以前的标签。地方需要,如日期数值,电话号码必须是数字格式 1. Team Members 团队成员
ROOT CAUSE #2/根本原因 Corrective Action for Why Made /针对影响制造过程根原因的纠正措施
Corrective Action for Why Shipped /针对影响发运过程根原因的纠正措施
6. Verification of Corrective Actions 纠正措施的确认
7. Prevention 预防
Verification of Corrective Action: Has the issue been turned on and off? How? Verification through statical evidence / hypothesis testing. Verification of corrective action for each why made and why shipped is required./解决问题的纠正措施是否已经落实?措施是如何执行的?通过静态证据和假设检验核实。必须对影响制造和发运过程的每一个纠正措施进行确认。
Corrrective Action Owner Name 纠正措施负责人姓名
C.A. Owner Phone Number 纠正措施负责人的电话号码
Build Date for Certified Material 记录改进后物料的日期 MM/DD/YYYY
How Will New Parts Be Identified? 新零件如何识别?
Target Completion Date 预计完成日期 MM/DD/YYYY
Owner for Update/更新负责人
Date/日期 MM/DD/YYYY
How will this issue be avoided in the future? /今后如何避免这种问题(的再发生)?
Has the necessary documentation been updated?/必要的文件已经更新了吗?
Closure Statement/项目关闭陈述
8. Closure 关闭
C.A. Owner E-mail Address 纠正措施负责人的E-mail地址
Affected Document/受影响的文件
DFMEA PFMEA Controll Plan Process flow Operation Instructions Drawing Design standards
Instructions for the 8D Problem Analysis Report 8D문제분석보고서 설명 폼을 작성하시기전에 주의깁게 이설명서를 읽어 주시기 바랍니다. -4D 요청는 당신이 규칙 1~3부터 양식을 작성하는것이 요구되어집니다. -8D 요청은 나머지 모든 규칙을 완료하고 ( 규칙 8 번까지) 4D 벙보를 수정하는것이 요구되어집니다. 4D와 8D의 완료일자는 SMRR또는 DMR보고서에 명확하게 표시되어집니다 그리고 그것은 문제에대한 통보가 이루어진 최초전자우편 에 첨부되어집니다. 4D는 공급자가 그들의 설비 또는 자재창고에 문제에대해 방지했다는것을 입증하는것에 대해 즉각적인 행동을 취했다는것을 확신(증명)하기위해 요구되어집니다. 당신은 4D 또는 8D회신인 오리지널 이멜에 적혀진 모든 계약자에게 이멜일 통하여 회신하는것이 요구되어집니다. HEADER 标题 1) Supplier/Location: (e.g., ABC Plastics, Markham, Ontario)공급자명/위치: (예 : 경상북도 경주시 노서동..) 2) Customer: (e.g., Daimler-Chrysler) 고객:(예: 동성기공) 3) Program: (e.g., LH) 아이템:(예:LH) 4) Product: (e.g., Overhead System) 제품명:(예: 오버헤드시스템) 5) Issue #: JCI issue tracking # (May also include Customer or Supplier tracking #) 문제색인번호:JCI 이슈 트랙킹(고객 또는 공급자 트랙킹 넘버또한 포함될수있음) 6) Date Issue Occurred: Open date for the issue 문제발생일자:문제 발생일자 7) 4D Due Date: Default is 24 hours from date issue occurred 4D완료기한일자:기본 문제발생시간으로부터 24시간 8) 8D Due Date: If applicable. Default is 1 week from date issue occurred 8D완료기한일자:만약 해당되면, 기본 문제발생일로부터 1주일。 9) Date Issue Closed: All permanent corrective actions have been implemented and their effectiveness validated; All required support documents have been submitted. 문제 문제해결일자:모든 영구적인 문제해결방안이 시행되어지고 그문제해결방안이 유효하게 적용되어질때;모든 요구되어진 문서가 제출되어짐。 규칙 1. TEAM MEMBERS 부서구성원 1) Champion Name/Title/Phone Number/Email Address: Contact information for the individual who is leading the corrective action and submitting the 4D/8D. 담당자/직급/전화번호/이메일주소:4D/8D제출과 모든 문제해결을 주도하는 개개인의 연락정보 2) Additional Team Member Name(s)/Title(s)/Phone Number(s)/Email Address(es): Contact information for the cross-functional team members who share responsibility for the corrective actions. 추가 팀 담당자(들)/직급(들)/전화번호(들)/이멜일주소(들):문제해결을 위해 상호 협조하는 팀멤머들의 연락정보 규칙 2. PROBLEM DESCRIPTION 문제 설명 1) Description: Describe the issue from a customer’s perspective; what would they know? 描述: 以客户的感知来描述该问题,他们想知道什么? When: When were the parts manufactured? When were they assembled? When were the assemblies shipped to the customer? When assembled in vehicles ? When shipped from OEM?
언제:언제 제품(단품)이 생산되어졌는가?언제 그제품이 조립되어졌는가?언제 조립되어진제품이 고객에게 출하되어졌는가?언제 완성차에 장착되어졌는가? 언제 OEM으로 부터 출하되어졌는가? Detection: How was AG made aware of the issue? Who provided the information? 발견:어떻게 AG 문제를 인식하게 되었는가?누가 이정보를 제공하였는가? Extent:How many units are suspected? Proportion found suspect. Where has the data come from - in house, in transit, at customer. 규모 :얼마나 많은 수량이 추정되어지는가?문제에대한 제기가 어디에서 제기되었는가,공장내부 ?납품중? 、고객으로 부터 ?。 Failure Mode: How does the issue manifest itself? 失效模式:问题本身的表现形式是什么? 2) Impact on Customer: Identify the potential for shut down, line interruptions, yard recalls, warranty. etc. 고객에게미친영향:중단을위한잠재적인 발견、라인중단、리콜、보증 등) 3) Facilities Involved: Customer, JCI and any Suppliers 사용되어진 설비:고객、존슨콘트롤즈, 공급자 규칙 3. INTERIM CONTAINMENT 잠정적인 방지 1) What actions were taken to immediately protect the customer and contain any suspect inventory? Since original notification, how are we containing this issue? What is the current containment status? What sorting have we done, where and how have we verif 고객을 호하고 의심되어지는 재고에 대해 어떤 즉각적인 행동이 취해졌는가? 원래의 통보에 어떻게 문제가 제기되어졌는가? 문제제기에 대한 현재의 상태는 무엇인가? 어떤해결책이 실행되어졌는가 어디서 어떻게 우리는 증명하였는가?
2) Other Product/Platform at Risk: Other JCI lines or Customers who may be impacted by this issue 其它存在风险的产品/场合:其它可能由此问题影响到的JCI生产线或客户 3) Identification of Certified Material: Color, size, location, and content of label or hand-written identification on each part and/or container of certified material.확인되어진 자재의 식별:각각의 아이템 또는 확인된 자재에대한 컨테이너상의 색깔,크기,위치 그리고 레이블 또는 손으로 쓰여진 정보 4) Sorting Results: Time, date, total number sorted and quantity rejected - broken down by facility (e.g., Customer, JCI, Supplier) 분류결과: 시간,일자,분류되어지고 거절되어진 총수량-기능이 완전히 망가진(예:고객,JCI,공급자) 5) Interim Containment Start Date: 잠정적인 예방 시작일자
규칙 4 ROOT CAUSE 근본원인 Note: The form provides fields for documentation of a single root cause. If additional root causes are identified, "Copy" rows 2731 and "Insert Cut Cells" to create additional fields. 주의:폼은 1개의 근본원인의 문서를 위한 필드값들을 제공 , 만약 추가적인 근본원인이 확인되었다면, 로넘버 27-31을 복사하고 추가적인 필드값들을 "insert Cut Cells" 을 사용하여 생성하세요 1) Why Made & How Verified: Identify each root cause for why the issue occurred. Has it been turned on and off? How? Verify through statical evidence/hypothesis testing. If not verified by turning on/off, identify as a suspected root cause. 왜 만들었으며 & 어떻게 확인되어졌나?
Variation: What are opportunities for variation in the process, i.e. how many fixtures do the same process? How many weld cells or robots? Etc.
变异:过程中的变异机会是什么?比如说:在同一过程中有使用了多少工装?使用了多少焊接单元或者焊接机器人等等? 2) Why Shipped & How Verified: Identify each root cause for why the issue escaped. Has it been turned on and off? How? Verify through statical evidence/hypothesis testing. If not verified by turning on/off, identify as a suspected root cause. 왜 출하되었으며 & 어떻게 확인되어졌는가?
纪律 5. PERMANENT CORRECTIVE ACTION 永久性纠正措施 Note: The form provides fields for documentation of a single root cause verification. If additional root causes have been identified, "Copy" rows 32-40 (steps1-5) and "Insert Cut Cells" to create additional fields. 주의:폼은 1개의 근본원인의 문서를 위한 필드값들을 제공 , 만약 추가적인 근본원인이 확인되었다면, 로넘버 32-40을 복사하고 추가적인 필드값들을 "insert Cut Cells" 을 사용하여 생성하세요 1) Corrective Action for Why Made: Identify permanent corrective action(s) planned to address the root cause. 왜 만들었는지에대한 대책: 근본문제에대해 해결하고 영구적인 문제해결방안을 확인하라 2) Corrective Action for Why Shipped: Identify permanent corrective action(s) planned to address the root cause. 왜 출하되어졌는지에 대한 대책 : 근본문제에대해 해결하고 영구적인 문제해결방안을 확인하라 규칙 6. VERIFICATION OF CORRECTIVE ACTIONS 문제해결의 확인 1) Has the issue been turned on and off? How? Verification through statical evidence / hypothesis testing. Verification of corrective action for each why made and why shipped is required.
2) Corrective Action Owner Name/Phone Number/Email Address: Contact information for the individual responsible for implementing the corrective action. 문제해결담당자이름/전화번호/이멜주소:문제해결담당자의 연락정보 3) Target Completion Date: Date by which all of the corrective actions for this root cause will be implemented. 목표 완료일자 :이 근본원인에대해 취해질 모든 교정행동 들의 일자 4) Build Date for Certified Material: "Clean point" at which all material is certified as good. 인증되어진 자재에대한 제조일자:“클린 포인트”,모든 자재는 좋은 품질로 인증되어졌다。 5) How Will New Parts Be Identified? Color, size, location, and content of label or hand-written identification on each part and/or container of certified material.
규칙 7. PREVENTION 예방 1) How will this issue be avoided in the future? Identify systematic changes that will be put in place to prevent the issue from occurring again. If applicable, standardize the improvements in other "at risk" areas. 이문제에대해 앞으로 어떻게 방지할것인가?识别需落实到位的系统性变更以防止该类问题的再发 2) Has the necessary documentation been updated? Identify the documents that must be updated to include the permanent corrective actions, along with who is responsible for the updates and the dates by which they will be updated. Enter "N/A" if the document 필요한 모든 문서들은 업데이트 되어졌는가?
규칙 8. CLOSURE 종결 1) Closure Statement: “Close issue…” (Begin with words noted in “” followed by the rationale for closure.) 종료문장:“이슈종결„„” ()
8D Problem Analysis Report 8D문제분석 보고서 Supplier/공급자: Customer/고객:
Date Issue Occurred/문제발생일:
Program/차종:
4D Due Date/4D왈료일자:
Product/제품:
8D Due Date/8D완료일자:
Issue#/문제#:
Date Issue Closed/문제해결일자:
Advanced Development Concept Development Product Definition
4D 요구 공급자는 적어도 노란색안의 하일라이트되어진 영역안의 폼을 작성하셔야만합니다 . ( 상세한사항에 대해서는 이전탭안의 설명서를 참조하세요 ) 날자,전화번호는 반듯이 숫자형식만 입력하여주세요 1. Team Members 팀 구성원
2. Problem Description 문제 설명
Champion Name 담당자 이름
Champion Title 담당자 직급
Champion Phone Number 담당자 전화번호
Champion E-mail Address 담당자 E-mail주소
Additional Team Member Name(s) 추가 팀멤버 전화번호
Title(s) 제목
Phone Number(s) 전화번호
E-mail Address(es) E-mail주소
Description (Describe issue in terms of what, where, when and how many) 설명( 문제에대한 설명 육하원칙에 따라 )
Impact on Customer (Identify the potential for shut down, line interruptions, yard recalls, warranty, etc..) 고객에 대한 영향 ( 고객라인 스탐에 관한 잠재적인 문제전,보증 등등 에관한 발견사항 )
Facilities Involved (Customer, JCI and any Suppliers) 관련되어진 설비들 ( 고객, 존슨콘트롤 그리고 관련되어진 모든 공급자 )
3. Interim Containment 잠재요소 방지
What actions were taken to immediately protect the customer and contain any suspect inventory? 어떤 의심적인 물품을 포함, 고객을 보호하기위해 어떤 즉각적인 조치를 취하였는가 ?
Other Product/Platform at Risk ? 다른제품/플래폼에대한 위험요소가 있는가 ?
Identification of certified material ? 인증되어진 제품에 대한 식별은 하였는가?
Sorting Results (Time, Date, Total Number Sorted and Quantity Rejected) 정리결과 ( 시간,일자,정리되어지고 거절되어진 총수량 )
Interim Containment Start Date/잠재요소방지 시작일자 MM/DD/YYYY
8D 요구공급자는 적어도 녹색으로 하일라이트되어전영역안의 폼을 반듯이 작성하셔야합니다. ( 상세한 사항에 대해서는 이전탭안의 설명서를 참조하세요 ) 날자,전화번호는 반듯이 숫자형식만 입력하여 주세요 4. Root Cause 근본원인
ROOT CAUSE #1 / 근본원인#1 Why Made & How Verified/ 왜 만들어졌는가 & 어떻게 확인되어졌는가?
Why Shipped & How Verified/ 왜 출하를 하였으며 어떻게 확인되어졌는가?
ROOT CAUSE # 2/근본원인#2 Why Made & How Verified/ 왜 만들어졌는가 & 어떻게 확인되어졌는가?
Why Shipped & How Verified/왜 출하를 하였으며 어떻게 확인되어졌는가?
5. Permanent Corrective Action 영구 해결방안
ROOT CAUSE # 1/근본원인#1 Corrective Action for Why Made /왜 만들어졌는가에 대한 해결방안
5. Permanent Corrective Action 영구 해결방안
Corrective Action for Why Shipped /왜 출하되어졌는가에 대한 해결방안
ROOT CAUSE #2/ 근본원인 #2 Corrective Action for Why Made /왜 만들어졌는가에 대한 해결방안
Corrective Action for Why Shipped /왜 출하되어졌는가에 대한 해결방안
6. Verification of Corrective Actions 해결방안에대한 확인
7. Prevention 예방
Verification of Corrective Action: Has the issue been turned on and off? How? Verification through statical evidence / hypothesis testing. Verification of corrective action for each why made and why shipped is required./해결방안에대한 확인: 이슈가 해결이 되었는가? 어떻게?정적인 증빙자료/추즉 테스팅을 통환 확인
Corrrective Action Owner Name 해결자 이름
C.A. Owner Phone Number C.A. 담당자 전화번호
Build Date for Certified Material 보증되어진 제품에 대한 제조일자 MM/DD/YYYY
How Will New Parts Be Identified? 새로운 파트에 대한 인증을 어떻게 할것인가 ?
Target Completion Date 예상 완료 일자 MM/DD/YYYY
How will this issue be avoided in the future? / 어떻게 이번이슈를 앞으로 예방할것인가 ?
Has the necessary documentation been updated?/관련된 모든 문서는 업데이트가 되어졌는가?
Closure Statement/종료 진술
8. Closure 종료
C.A. Owner E-mail Address C.A 담당자 E-Mail 주소
Affected Document/ 관련문서
DFMEA PFMEA Controll Plan Process flow Operation Instructions Drawing Design standards
Owner for Update/관련문서담당자
Date/일자 MM/DD/YYYY
Instruções para o Relatório de Análise do Problema 8D Por favor, leia estas instruções cuidadosamente antes de preencher este formulário. A 4D pedido requer que você preencha o formulário da Disciplina de 1 a 3. Um 8D pedido requer que sua 4D actualizar a informação completa e todas as demais disciplinas (a 8). Devido datas para 4D e 8Ds são claramente especificados no SMRR ou DMR relatório que foi anexado ao original e-mail avisando do problema. 4Ds são necessárias para garantir que o fornecedor tome ações imediatas em suas instalações e / ou armazém para assegurar que a questão está contido. Está obrigada a responder por e-mail a todas as partes copiadas no original e-mail com a resposta apropriada 4D ou 8D. CABEÇALHO 1) Fornecedor: (e.g. ABC Plastics, Markham, Ontario) 2) Cliente: (e.g., Johnson Controls, Inc., Markham, Ontario) 3) Programa: (e.g., LH) 4) Produto: (e.g., Overhead System) 5) Nº da 8D: Número de controle da JCI (pode também incluir o número do cliente ou do fornecedor) 6) Data de Ocorrência: Data de abertura para o problema 7) Data de 4D: O padrão é 24 horas à partir da ocorrência do problema. 8) Data de 8D: Se aplicável. O padrão é 1 semana após a ocorrência do problema. 9) Data de Fechamento: Toda ação corretiva foi implementada sua respectiva eficácia validada; Todos os documentos requeridos/solicitados foram submetidos. Disciplina1. MEMBROS DO TIME 1) Nome do Responsável/ Cargo/Telefone/ E-Mail: Informações de contato da pessoa que está liderando (responsável) pela ação corretiva e submição da 4D/8D. 2) Nome(s) do(s) membro(s) adicionais do Time/ Cargo(s)/ Telefone(s)/ E-mail(s): Informações de contato dos membros do time que compartilham da responsabilidade para as ações corretivas. Disciplina 2. DESCRIÇÃO DO PROBLEMA 1) Descrição: Descrever o problema pela perspectiva do cliente; o que eles poderiam saber? Quando: Quando as peças foram manufaturadas? Quando elas foram montadas? Quando as peças montadas foram enviadas ao cliente? Quando foram montadas no veículo? Detecção: Como a JCI ficou ciente do problema? Quem forneceu a informação? Extenção: Quantas peças são suspeitas? Proporção suspeita encontrada. De onde vieram os dados - da JCI, do trânsito, do cliente. Modo de falha: Como o problema se manifestou? 2) Impacto no Cliente: Identificar potencial de suspensão de entrega, parada de linha, campanha de pátio, garantia, etc. 3) Instalações/Recursos Envolvidos: Cliente, JCI e Fornecedores Disciplina 3. PERÍODO DE CONTENÇÃO 1) Quais ações foram tomadas de imediato para proteger o cliente e conter qualquer material suspeito (em inventario)? Desde a notificação inicial, como nós estamos contendo este problema? Qual é o status atual da contenção? Quais critérios estamos tomando, onde e como estão sendo verificados se são eficazes? Se começar um plano de retrabalho ou de melhoria - como verificamos a eficácia - anexar plano com registros e gráficos de tendência . 2) Outro Produto/Plataforma em Risco: Outras linha JCI ou Clientes JCI que podem ser afetados por este problema. 3) Identificação do material aprovado: Cor, tamanho, localização, descritivo da etiqueta ou identificação feita à mão em cada peça e/ou embalagem de material aprovado. 4) Resultados da Verificação: Hora, data, quantidade total de peças verificadas e quantidade de peças defeituosas - danificadas no processo (exemplo: Cliente, JCI, Fornecedor) 5) Quantidade Verificada: Quantidade total de peças verificada encontradas em todos os processos/fábricas. 6) Quantidade Defeituosa: Quantidade de peças defeituosas encontradas em todos os processos/fábricas. 7) Data Inicial do Período de Contenção: Data Inicial do Período de Contenção. Disciplina 4. CAUSA RAÍZ Aviso: O formulário fornece campos para a documentação de uma única causa da raiz. Se forem identificadas causas raízes adicionais “copie” a linhas 27-31 e “insira células cortadas" para criar campos adicionais. 1) Por que foi produzido e como foi verificado: Identificar cada causa raíz focando por que ocorreu o problema. O problema foi resolvido? Como? Verificar através de evidências estatísticas/teste de hipóteses. Se não foi resolvido, identificar a causa raíz suspeita. Abrangência: Quais são as oportunidades de abrangência do processo, por exemplo: quantos dispositivos fazem o mesmo processo? Quantas células de solda ou robôs? Etc... 2) Porque foi enviado e como foi verificado: Identificar cada causa raíz focando por que ocorreu o problema. O problema foi resolvido? Como? Verificar através de evidências estatísticas/teste de hipóteses. Se não foi resolvido, identificar a causa raíz suspeita. Disciplina 5. AÇÃO CORRETIVA PERMANENTE Aviso: O formulário fornece campos para a documentação de uma única causa da raiz. Se forem identificadas causas raízes adicionais “copie” a linhas 32-40 (passos 1-5) e “insira células cortadas" para criar campos adicionais. 1) Ação Corretiva para o por que foi produzido : Identificar ação(ões) corretiva(s) permanente atacando a causa raíz. 2) Ação Corretiva para o por que foi enviado : Identificar ação(ões) corretiva(s) permanente atacando a causa raíz. Disciplina 6. VERIFICAÇÃO DAS AÇÕES CORRETIVAS
1) O problema foi contido? Como? Verificação através de evidência estatística/ testes de hipóteses. Verificação da ação corretiva para cada porque foi produzido e porque foi enviado 2) Responsável pela Açao Corretiva/Telefone/Email: Contatar a informação para a pessoa responsável pela implementação, execução da ação corretiva. 3) Data de implementação: Data na qual todas as ações corretivas foram executadas/implementadas 4) Colocar uma data para ponto de corte: "Ponto de corte" certificando que todo material está OK. 5) Como as peças novas serão identificadas? Uso de Spot, Lote, embalagem, FEM, marcador industrial, etc.
Disciplina 7. PREVENÇÃO 1) Como este problema será evitado no futuro? Identificar mudanças no sistema ou processo que serão tomadas para previnir que o problema ocorra novamente. Se aplicável, padronizar a ação corretiva em outras áreas de risco. 2) Outros facilitadores ou Plataformas de risco? Identificar nome, # peça, responsável pelo acompanhamento e resultado da ação corretiva e a data combinada para facilitadores ou plataformas que podem correr o risco de ocorrência do mesmo problema. Digitar "N/A" se for um problema isolado. "Copiar" linhas 48-49 e "Inserir células cortadas" para criar campos adicionais se necessários. 3) A documentação necessária tem sido atualizada? Identificar os documentos que devem ser atualizadaos para incluir as ações corretivas permanentes, junto com o responsável pelas atualizações e as datas que serão feitas. Colocar “N/A” se o documento não precisar ser alterado/atualizado. Disciplina 8. FECHAMENTO 1) Relato do fechamento: “Problema Fechado" (Inicia com palavras conhecidas "" seguidas de argumentos, lógicas para o fechamento)
8D Relatório de Análise do Problema
Fornecedor: Cliente:
Data de Ocorrência:
Programa:
Data de 4D:
Produto:
Data de 8D:
Número da 8D :
Data de fechamento:
Desenvolvimento Avançado Desenvolvimento de Conceito
Definição do Produto
Para 4D Fornecedores pedidos devem, no mínimo, preencher o formulário de áreas destacadas em amarelo. (Use Instruções no guia anterior para mais detalhes). Áreas que exigem valores numéricos, tais como datas, números de telefone deve ser numérico formato 1. Membros do time
2. Descrição do Problema
Nome do responsável:
Cargo do responsável
Telefone do responsável
E-mail do responsável
Membros do time
Cargos (time)
Telefones (time)
E-mails (time)
Descrição (Descreva o problema em termos de o que, onde, quando e quantos)
Impacto no Cliente (Identificar o potencial de suspensão de entregas, parada de linha, campanha de pátio, garantia, etc.…)
Instalações/Recursos Envolvidos (Cliente, JCI e Fornecedores)
Quais ações foram tomadas de imediato para proteger o cliente e conter qualquer material suspeito (em inventario)? 3. Período de Contenção
Outro produto/ plataforma em risco?
Identificação do material aprovado?
Resultados da Verificação (Hora, Data, Quantidade Total de Peças Verificadas e Quantidade de Peças Defeituosas)
Quantidade Verificada
Quantidade Defeituosa
Data Inicial do Período de Contenção DD.MM.YYYY
Para 8D pedidos fornecedor deve, no mínimo, preencher o formulário para as áreas destacadas em verde. Formato (Use as instruções no guia anterior) Áreas que exigem valores numéricos, tais como datas, números de telefone deve ser numérico 4. Causa Raíz
CAUSA RAÍZ # 1 Por que foi produzido e como foi verificado?
Por que foi enviado e como foi verificado?
CAUSA RAÍZ #2 Por que foi produzido e como foi verificado?
Por que foi enviado e como foi verificado?
5. Ação Corretiva Permanente
CAUSA RAÍZ # Ação Corretiva para o por que foi produzido .
Ação Corretiva para o por que foi enviado .
CAUSA RAÍZ #2 Ação Corretiva para o por que foi produzido .
Ação Corretiva para o por que foi enviado .
6. Verificação das Ações Corretivas
7. Prevenção
Verificação da Ação Corretiva: O problema foi resolvido? Como? Verificação através de evidência estatística/ testes de hipóteses. Verificação da ação corretiva para cada item de por que foi produzido e por que foi enviado.
Responsável pela Ação Corretiva
Telefone (Responsável pela A.C.)
Data do Material Ok (Ponto de Corte) DD.MM.YYYY
Como as peças novas serão identificadas? (Spot, marcador industrial, FEM, etc)
Data de Conclusão Proposta DD.MM.YYYY
Como este assunto será evitado no futuro?
Outros Instalações/recursos ou plataformas em risco Nome Número da peça
A documentação necessária foi atualizada?
8. Fechamento
E-mail (Responsável pela A.C.)
Relato do fechamento
Documentos afetados
DFMEA PFMEA Plano de Controle Fluxo de Processo Instruções de Trabalho Desenho Padrões do Projeto
Responsável da A.C. para Follow up
Data de Conclusão
Responsável para Atualização
Data DD.MM.YYYY
Instrucciones para el Reporte de Análisis de Problemas 4D y 8D Por favor lea las instrucciones cuidadosamente antes de completar esta forma. Una solicitud de 4D requiere que llene las Disciplinas 1 a la 3. Una solicitud de 8D requiere que actualize la informacion de 4D y complete el resto de las Disciplinas (hasta la 8). Las fechas estipuladas para las 4D y 8Ds estan claramente especificadas en el reporte SMRR o DMR que fue adjuntado al correo original notificandolo del problema. Las 4Ds son requeridas para asegurar que el proveedor tome acciones inmediatas en su planta y/o almacen para asegurar que el problema ha sido contenido. Es requerido que usted conteste via correo electrónico a todas las personas copiadas en el correo electrónico original con la respuesta de 4D u 8D apropiada.
ENCABEZADO 1) Proveedor/Ubicación: (ej., ABC Plastics/Markham, Ontario) 2) Cliente: (ej., JCI San Antonio) 3) Programa: (ej., Light Commercial Chiller etc.,) 4) Producto: (ej., Compresor o motor etc) 5) Problema #: # interno de JCI (SMRR or DMR #) 6) Fecha de Ocurrencia: Fecha en que se presento el problema 7) Fecha de cierre de 4D: Por default es 24 horas de la fecha de ocurrencia 8) Fecha de cierre de 8D: Si aplica. Por default es 7 dias hábiles de la fecha de ocurrencia 9) Fecha de Terminación: Todas las acciones correctivas permanentes han sido implementadas y su efectividad validada; Todos los documentos de suporte has sido enviados. Disciplina 1. MIEMBROS DEL EQUIPO 1) Nombre del Líder/Título/Teléfono/Correo electrónico: Informacion para contactar al individuo que está lidereando la acción corrective y enviando la 4D/8D. 2) Nombre de los Miembros del Equipo/Títulos/Teléfonos/Correo electrónico: Información para contactar a los miembros del equipo multi-funcional que comparten la responsabilidad de las acciones correctivas. Disciplina 2. Descripción del Problema 1) Descripción: Describa el problema desde la perspectiva del cliente; que es lo que ellos saben?
2) Impacto en el Cliente: Identificar el potencial de parar la línea, de interrupciones, reclamaciones de campo, garantías, etc. 3) Entidades Involucradas: Cliente, JCI y otros proveedores
Disciplina 3. ACCION DE CONTENCION 1) Qué acciones son tomadas de inmediato para proteger al cliente y contener cualquier inventario sospechoso? Desde la notificación original, como se esta conteniendo el problema? Cuál es el estatus actual de la contención? Qué tipo de selección se ha llevado a cabo, dónde y cómo se ha llevado a cabo la verificación de la efectividad? Si un plan de retrabajo o reabasto se ha comenzado - cuál es y cómo se ha verificado la efectividad? – adjunte el plan con sketches gráficas de tendencia. en Riesgo: Otros productos de JCI o ubicaciones que puedan ser impactadas por este problema 2) y Otro Producto/Plataforma 3) Identificación del Material Certificado: Color, tamaño, ubicacion, y contenido de la etiqueta o identificación escrita a mano en cada pieza y/o contenedor del material certificado. 4) Resultados de la Selección: Hora, fecha, total de piezas seleccionadas y cantidad rechazada - desglozado por planta (ej., en JCI, Proveedor, Almacen, etc) 5) # Inspeccionados: Cantidad total de piezas seleccionadas en todas las plantas. 6) # Defectuosos: Cantidad total de piezas defectuosas en todas las plantas. 7) Fecha de inicio de Acción de Contención: Fecha cuando la acción de contención comenzó. Disciplina 4. CAUSA RAIZ 1) Por qué se originó y Cómo fue verificado: Identificar cada causa raíz para el origen del problema. Se ha probado? Cómo? Verificar por medio de evidencia estadística/prueba de hipótesis. Si no se ha verificado, identificarla como una causa raíz potencial.
2) Por qué se escapó y Cómo fue verificado: Identificar cada causa raíz para el origen del problema. Se ha probado? Cómo? Verificar por medio de evidencia estadística/prueba de hipótesis. Si no se ha verificado, identificarla como una causa raíz potencial. Disciplina 5. ACCION CORRECTIVA PERMANENTE
1) Acción correctiva para el origen: Identificar la(s) accion(es) correctiva(s) permanentes planeadas para atacar la causa raiz. 2) Acción correctiva para el escape: Identificar la(s) accion(es) correctiva(s) permanentes planeadas para atacar la causa raiz Disciplina 6. VERIFICACION DE LAS ACCIONES CORRECTIVAS 1) Se ha probado? Cómo? Verificar por medio de evidencia estadística/prueba de hipótesis. Si no se ha verificado, identificarla como una causa raíz potencial. Se requiere verificación de la acción correctiva para cada origen y escape.
2) Nombre del responsable de la AC/Teléfono/Correo electrónico: Información del contacto del individuo o individuos responsables de la implementación de acción correctiva. 3) Fecha compromiso de la acción correctiva: Fecha en que todas las acciones correctivas para la causa raíz serán implemen 4) Fecha del producto certificado: Fecha de inicio en donde el material es certificado como bueno. 5) Cómo serán identificadas las piezas nuevas? Color, tamaño, ubicación, y contenido de la etiqueta o identificación escrita a mano en cada pieza y/o contenedor del material certificado. Disciplina 7. PREVENCION 1) Cómo será evitado este problema en el futuro? Identificar cambios sistemáticos que serán puestos en marcha para prevenir que el problema ocurra nuevamente. Si aplica, estandarizar las mejoras en otras áreas en riesgo. 2) Otras Entidades o Plataformas en riesgo? Identificar el nombre, # parte, responsable de acción correctiva para el seguimiento y la fecha compromiso para alguna otra entidad o plataforma que pueda estar en riesgo con el mismo problema. Colocar "N/A" si el casi es aislado. "Copiar" los renglones 48-49 e "Insertar celdas copiadas" para crear campos adicionales la si documentación es requerido. necesaria? Identificar los documentos que deben ser actualizados para incluir 3) Ha sido actualizada las acciones correctivas permanentes, junto con el responsable de las actualizaciones y las fechas en las que serán actualizados. Colocar "N/A" si los documentos no requieren actualización.
Disciplina 8. CIERRE 1) Enuciado de Cierre: “El problema ha sido cerrado…” (Comenzar con las palabras en “” seguido de un razonalización del ci VERSION OF DOCUMENT 1)
Version 1.5: Formatting text fields imposed.
2)
Updated work instructions and added Supplier Name/Location to Header
3) 4D and 8D color coded 2/28/2010
Instrucciones para el Reporte de Análisis de Problemas 4D y 8D Por favor lea las instrucciones cuidadosamente antes de completar esta forma. Una solicitud de 4D requiere que llene las Disciplinas 1 a la 3. Una solicitud de 8D requiere que actualize la informacion de 4D y complete el resto de las Disciplinas (hasta la 8). Las fechas estipuladas para las 4D y 8Ds estan claramente especificadas en el reporte SMRR o DMR que fue adjuntado al correo original notificandolo del problema. Las 4Ds son requeridas para asegurar que el proveedor tome acciones inmediatas en su planta y/o almacen para asegurar que el problema ha sido contenido. Es requerido que usted conteste via correo electrónico a todas las personas copiadas en el correo electrónico original con la respuesta de 4D u 8D apropiada.
ENCABEZADO Proveedor/Ubicación: (ej., ABC Plastics/Markham, Ontario) Cliente: (ej., JCI San Antonio) Programa: (ej., Light Commercial Chiller etc.,) Producto: (ej., Compresor o motor etc) Problema #: # interno de JCI (SMRR or DMR #) Fecha de Ocurrencia: Fecha en que se presento el problema Fecha de cierre de 4D: Por default es 24 horas de la fecha de ocurrencia Fecha de cierre de 8D: Si aplica. Por default es 7 dias hábiles de la fecha de ocurrencia Fecha de Terminación: Todas las acciones correctivas permanentes han sido implementadas y su efectividad validada; Todos los documentos de suporte has sido enviados. Disciplina 1. MIEMBROS DEL EQUIPO Nombre del Líder/Título/Teléfono/Correo electrónico: Informacion para contactar al individuo que está lidereando la acción corrective y enviando la 4D/8D. Nombre de los Miembros del Equipo/Títulos/Teléfonos/Correo electrónico: Información para contactar a los miembros del equipo multi-funcional que comparten la responsabilidad de las acciones correctivas. Disciplina 2. Descripción del Problema Descripción: Describa el problema desde la perspectiva del cliente; que es lo que ellos saben? Cuándo: Cuándo fueron fabricadas las piezas? Cuándo fueron ensambladas? Cuándo fueron embarcados los ensambles al cliente? Cuándo fueron ensamblados en los ensambles? Detección: Cómo se enteró JCI del problema? Quién proporcionó la información? Extención: Cuántas unidads son sospechosas? Cuál es la proporción que se encuentra sospechosa. De dónde provienen los datos - en planta, en tránsito, con cliente. Modo de Falla: Cómo se manifiesta el problema? Impacto en el Cliente: Identificar el potencial de parar la línea, de interrupciones, reclamaciones de campo, garantías, etc. Entidades Involucradas: Cliente, JCI y otros proveedores Disciplina 3. ACCION DE CONTENCION Qué acciones son tomadas de inmediato para proteger al cliente y contener cualquier inventario sospechoso? Desde la notificación original, como se esta conteniendo el problema? Cuál es el estatus actual de la contención? Qué tipo de selección se ha llevado a cabo, dónde y cómo se ha llevado a cabo la verificación de la efectividad? Si un plan de retrabajo o reabasto se ha comenzado - cuál es y cómo se ha verificado la efectividad? – adjunte el plan con sketches yOtro gráficas de tendencia. en Riesgo: Otros productos de JCI o ubicaciones que puedan ser impactadas por este problema. Producto/Plataforma Identificación del Material Certificado: Color, tamaño, ubicacion, y contenido de la etiqueta o identificación escrita a mano en cada pieza y/o contenedor del material certificado. Resultados de la Selección: Hora, fecha, total de piezas seleccionadas y cantidad rechazada - desglozado por planta (ej., en JCI, Proveedor, Almacen, etc) # Inspeccionados: Cantidad total de piezas seleccionadas en todas las plantas. # Defectuosos: Cantidad total de piezas defectuosas en todas las plantas. Fecha de inicio de Acción de Contención: Fecha cuando la acción de contención comenzó. Disciplina 4. CAUSA RAIZ Por qué se originó y Cómo fue verificado: Identificar cada causa raíz para el origen del problema. Se ha probado? Cómo? Verificar por medio de evidencia estadística/prueba de hipótesis. Si no se ha verificado, identificarla como una causa raíz potencial.
Variacion: Cuales son las oportunidades de variacion en el proceso, ej. cuantas plantillas realizan el mismo proceso? Cuando robots? Etc. Por qué se escapó y Cómo fue verificado: Identificar cada causa raíz para el origen del problema. Se ha probado? Cómo? Verificar por medio de evidencia estadística/prueba de hipótesis. Si no se ha verificado, identificarla como una causa raíz potencial. Disciplina 5. ACCION CORRECTIVA PERMANENTE Acción correctiva para el origen: Identificar la(s) accion(es) correctiva(s) permanentes planeadas para atacar la causa raiz. Acción correctiva para el escape: Identificar la(s) accion(es) correctiva(s) permanentes planeadas para atacar la causa raiz. Disciplina 6. VERIFICACION DE LAS ACCIONES CORRECTIVAS Se ha probado? Cómo? Verificar por medio de evidencia estadística/prueba de hipótesis. Si no se ha verificado, identificarla como una causa raíz potencial. Se requiere verificación de la acción correctiva para cada origen y escape. Nombre del responsable de la AC/Teléfono/Correo electrónico: Información del contacto del individuo o individuos responsables de la implementación de acción correctiva. Fecha compromiso de la acción correctiva: Fecha en que todas las acciones correctivas para la causa raíz serán implementadas. Fecha del producto certificado: Fecha de inicio en donde el material es certificado como bueno. Cómo serán identificadas las piezas nuevas? Color, tamaño, ubicación, y contenido de la etiqueta o identificación escrita a mano en cada pieza y/o contenedor del material certificado. Disciplina 7. PREVENCION Cómo será evitado este problema en el futuro? Identificar cambios sistemáticos que serán puestos en marcha para prevenir que el problema ocurra nuevamente. Si aplica, estandarizar las mejoras en otras áreas en riesgo. Otras Entidades o Plataformas en riesgo? Identificar el nombre, # parte, responsable de acción correctiva para el seguimiento y la fecha compromiso para alguna otra entidad o plataforma que pueda estar en riesgo con el mismo problema. Colocar "N/A" si el casi es aislado. "Copiar" los renglones 48-49 e "Insertar celdas copiadas" para crear campos adicionales la si documentación es requerido. necesaria? Identificar los documentos que deben ser actualizados para incluir Ha sido actualizada las acciones correctivas permanentes, junto con el responsable de las actualizaciones y las fechas en las que serán actualizados. Colocar "N/A" si los documentos no requieren actualización. Disciplina 8. CIERRE Enuciado de Cierre: “El problema ha sido cerrado…” (Comenzar con las palabras en “” seguido de un razonalización del cierre.) VERSION OF DOCUMENT Version 1.5: Formatting text fields imposed. Updated work instructions and added Supplier Name/Location to Header
3) 4D and 8D color coded 2/28/2010
garantías, etc.
este problema.
r la causa raiz. ar la causa raiz.
serán implementadas.
nalización del cierre.)
Reporte de Análisis Proveedor/Ubicación: Cliente: Programa: Producto: Problema #:
Para solicitudes de 4D, los proveedores deben po ceja anterior para mayores detalles). Las áreas qu deben estar en formato numérico. 1. Miembros del equipo
Nombre del Líder
Nombre de los miembros del equipo
2. Descripción del problema
Descripción (Describa el problema utilizando QUÉ, DÓNDE, CUÁNDO y CUÁN
Impacto en el Cliente (Identifique los paros de línea, interrupciones, reclamac
Entidades involucradas (Clientes finales, JCI y otros proveedores)
3. Acción de Contención
¿Qué acciones son tomadas para proteger de inmediato al cliente y contener
¿Otros productos / Plataformas en riesgo?
Resultados de la selección (Tiempo, Fecha, Número Total de Materiales Selec
Fecha de inicio de acción de contención DD.MM.YYYY
Para solicitudes de 8D, los proveedores deben po ceja anterior). Las áreas que requieren valores nu numérico. 4. Causa Raíz
CAUSA RAÍZ #1 ¿Por qué se originó y Cómo fue verificada la causa?
¿Por qué se escapó y Cómo fue verificada la causa?
CAUSA RAÍZ #2 ¿Por qué se originó y Cómo fue verificada la causa?
¿Por qué se escapó y Cómo fue verificada la causa?
5. Acción Correctiva Permanente CAUSA RAÍZ #1 Action Acción Correctiva para el por qué se originó
Acción Correctiva para el por qué se escapó
CAUSA RAÍZ #2 Acción Correctiva para el por qué se originó
Acción Correctiva para el por qué se escapó
6. Verificación de Acciones Correctivas
Verificación de Acción Correctiva: ¿Se ha verificado el problema? ¿De qué m correctiva para origen y escape es requerida.
6. Verificación de Acciones Correctivas
Nombre del responsable de la AC
Fecha del producto certificado DD.MM.YYYY
7. Prevención
¿Cómo será evitado este problema en el futuro?
Otras Entidades o Plataformas en Riesgo Nombre
¿Ha sido actualizada la documentación necesaria?
8. Cierre
Enunciado de Cierre (Validación)
Reporte de Análisis del Problema 8D Fecha de Ocurrencia: Fecha de cierre de 4D: Fecha de cierre de 8D: Fecha de Terminación:
s proveedores deben por lo menos completar las áreas en amarillo. (Utilizar instruc es detalles). Las áreas que requieren valores numéricos como las fechas, números t umérico. Título del Líder
Teléfono del Líder
Titulo de los miembros
Télefono de los miembros
ando QUÉ, DÓNDE, CUÁNDO y CUÁNTOS)
os de línea, interrupciones, reclamaciones de campo, garantías potenciales, etc.)
, JCI y otros proveedores)
ger de inmediato al cliente y contener cualquier inventario sospechoso?
o?
¿De qué manera se identifica el material certificado?
ha, Número Total de Materiales Seleccionados y Cantidad Rechazada).
DD.MM.YYYY
s proveedores deben por lo menos completar las áreas en verde. (Utilizar instruccio ue requieren valores numéricos como las fechas, números telefónicos deben estar
da la causa?
da la causa?
da la causa?
da la causa?
ginó
apó
ginó
apó
a verificado el problema? ¿De qué manera? Verificación mediante evidencia estadística / prueba de hipótesis? La verificación de erida.
Teléfono del responsable de la AC
Correo electrónico del responsible
¿Cómo serán identificadas las piezas nuevas?
futuro?
o Número de parte
Responsable del seguimiento
Documento afectado
Responsable de la actualización
DFEMA PFMEA
Plan de Control Diagrama de Proceso Instrucciones Operativas Dibujos Estándares de diseño
en amarillo. (Utilizar instrucciones en la como las fechas, números telefónicos Correo electrónico del Líder
Correo electrónico de los miembros
el material certificado?
en verde. (Utilizar instrucciones en la eros telefónicos deben estar en formato
ca / prueba de hipótesis? La verificación de cada acción
Fecha compromiso para la AC DD.MM.YYYY
Fecha Compromiso
Fecha DD.MM.YYYY
Instructions for the 8D Problem Analysis Report 8D 問題分析報告書に対する説明
HEADER 标题 1) Customer: (e.g., Daimler-Chrysler) 顧客 ( サンプル: フォード, ホンダ , Suzuki ) 2) Program: (e.g., LH) 项目:( サンプル: LH ) 3) Product: (e.g., Overhead System) 製品 ( 例: Overhead System ) 4) Issue #: JCI issue tracking # (May also include Customer or Supplier tracking #) 問題番号 : JCI 問題追跡番号 ( または顧客または供給者の問題追跡番号おこることもできる ) 5) Date Issue Occurred: Open date for the issue 問題発生日付け ( 問題が提示された発生日付け ) 6) 4D Due Date: Default is 24 hours from date issue occurred 4D 完成日付け ( 基本問題発生時間から 24時間以内 ) 7) 8D Due Date: If applicable. Default is 1 week from date issue occurred 8D 完成日付け ( 基本問題発生時間から 1週間以内 8) Date Issue Closed: All permanent corrective actions have been implemented and their effectiveness validated; All required support documents have been submitted. イシュー解決日付け : ( すべての永久的な問題解決方案が提示適用されたし, すべての方案が有用にゾックヨングドエンイルザ, TEAM MEMBERS チーム構成員 1) Champion Name/Title/Phone Number/Email Address: Contact information for the individual who is leading the corrective action and submitting the 4D/8D.担当者名前/地位/電話番号/E-mail 住所 : 4D/8Dを提出して問題解決を主導する担当者の情報 2) Additional Team Member Name(s)/Title(s)/Phone Number(s)/Email Address(es): Contact information for the crossfunctional team members who share responsibility for the corrective actions. 追加的なチーム構成員たちに対する声明(名前)/地位/電話番号/E-mail 住所 : 対応策について連携責任を負う追加的なチームメンバーたちに対する情報 PROBLEM DESCRIPTION 問題説明 1) Description: Describe the issue from a customer’s perspective; what would they know? 説明 : 顧客が何が分かりたがっているのか, 顧客の観点で問題に対して説明しなさい,
2) Impact on Customer: Identify the potential for shut down, line interruptions, yard recalls, warranty. etc. 顧客に対する影響 ( 工場閉鎖,生産ライン止まり,リコール,保証,等々に対する潜在的な危険要素を区別しなさい ) 3) Facilities Involved: Customer, JCI and any Suppliers 問題に同参した要素 ( 顧客, JCI そして供給者たち ) INTERIM CONTAINMENT 临时措施 1) What actions were taken to immediately protect the customer and contain any suspect inventory? Since original notification, how are we containing this issue? What is the current containment status? What sorting have we done, where and how have we verify,疑心されられる再考物品を含んで顧客を保護するためにどんな即刻なゾツィが酔われたのか? 2) Other Product/Platform at Risk: Other JCI lines or Customers who may be impacted by this issue その他製品に対する危険要素はあるか:この問題によって影響を受けたその他 JCI 生産ラインまたは顧客
3) Identification of Certified Material: Color, size, location, and content of label or hand-written identification on each part and/or container of certified material.認証された製品に対する証明:在每一个经认可的物料零件和/或包装上有以颜色、尺寸、位置、标签内容或者 手写的识别标记。 4) Sorting Results: Time, date, total number sorted and quantity rejected - broken down by facility (e.g., Customer, JCI, Supplier) 区別結果 ( 時間,日付け, 区別された総数量そして断れられた数量 ) (はい, 顧客, JCI, 供給者 ) 5) Sorted #: Total # sorted at all facilities 6) Defect #: Total # of defects found at all facilities 7) Interim Containment Start Date: Date ROOT CAUSE 根本原因 Note: The form provides fields for documentation of a single root cause. If additional root causes are identified, "Copy" rows 27-31 and "Insert Cut Cells" to create additional fields. 注意 : 文書は一つのグンボンワンインエヘした文書化値段を提供する. もし追加的に根本原因が識別になられれば." 十 27-31をコピーして "INSERT CUT CELLS" 1) Why Made & How Verified: Identify each root cause for why the issue occurred. Has it been turned on and off? How? Verify through statical evidence/hypothesis testing. If not verified by turning on/off, identify as a suspected root cause. 根本原因に対してどうして作られたしどんなに確認されられたのか
2) Why Shipped & How Verified: Identify each root cause for why the issue escaped. Has it been turned on and off? How? Verify through statical evidence/hypothesis testing. If not verified by turning on/off, identify as a suspected root cause. どうして出荷されられたしどんなに確認されられたのか PERMANENT CORRECTIVE ACTION 永久性纠正措施 Note: The form provides fields for documentation of a single root cause verification. If additional root causes have been identified, "Copy" rows 32-40 (steps1-5) and "Insert Cut Cells" to create additional fields. 注意:表格提供了填写单个根本原因的位置,若发现还有其它根本原因,复制32-40 1) Corrective Action for Why Made: Identify permanent corrective action(s) planned to address the root cause. 针对造成制造问题根原因的纠正措施:辨识出针对于根原因的永久性纠正措施 2) Corrective Action for Why Shipped: Identify permanent corrective action(s) planned to address the root cause. 针对造成发运问题根原因的纠正措施:辨识出针对根原因的永久性纠正措施 VERIFICATION OF CORRECTIVE ACTIONS デウングチェックエデした証明 1) Has the issue been turned on and off? How? Verification through statical evidence / hypothesis testing. Verification of corrective action for each why made and why shipped is required. デウングチェックエデした証明 : 問題が解決されられたのか? どんなに? 問題になった製品に対してどうして作られたしどうして出荷されたのかに関する再確認及び証拠 2) Corrective Action Owner Name/Phone Number/Email Address: Contact information for the individual responsible for implementing the corrective action. 対策関連担当者声明(名前)/対策関連担当者電話番号/ 対策関連担当者 E-mail 住所 3) Target Completion Date: Date by which all of the corrective actions for this root cause will be implemented. 目標完了日付け: 根本原因に対して対応方案が初めて適用されられた日付け
4) Build Date for Certified Material: "Clean point" at which all material is certified as good. 代替品に対する完成日付け:問題点関連 :"解決時点" すべての資材がムンゼオブヌンゴッに証明されられた時点 5) How Will New Parts Be Identified? Color, size, location, and content of label or hand-written identification on each part and/or container of certified material. どんなに代替品に対して問題がないと証明しようか? 色相,大きさ, 位置そしてラベルの content またはそれぞれの製品の上の手記で作成または認証されられた資材に対するコンテナ PREVENTION 防止 1) How will this issue be avoided in the future? Identify systematic changes that will be put in place to prevent the issue from occurring again. If applicable, standardize the improvements in other "at risk" areas. これからどんなにこのような問題が発生されないようにしようか? システム的な変更による問題再発防止策, もし可能ならば, もう一つの問題領域の改善標準対策で活用 2) Other Facilities or Platforms At Risk? Identify name, part#, corrective action owner for follow up & due date for any other facility or platform that may be at risk for the same issue. Enter "N/A" if the issue is isolated. "Copy" rows 48-49 and "Insert
3) Has the necessary documentation been updated? Identify the documents that must be updated to include the permanent corrective actions, along with who is responsible for the updates and the dates by which they will be updated. Enter "N/A" if the document その他危険要素に対する道具
CLOSURE 完結 1) Closure Statement: “Close issue…” (Begin with words noted in “” followed by the rationale for closure.) 終了文章" 問題解決完了" ( "" 中の単語で入力しなさい )
Instructions for the 8D Problem Analysis Report 8D 問題分析報告書に対する説明 HEADER 标题 Customer: (e.g., Daimler-Chrysler)
顧客 ( サンプル: フォード, ホンダ , Suzuki )
Program: (e.g., LH) 项目:( サンプル: LH ) Product: (e.g., Overhead System) 製品 ( 例: Overhead System ) Issue #: JCI issue tracking # (May also include Customer or Supplier tracking #) 問題番号 : JCI 問題追跡番号 ( または顧客または供給者の問題追跡番号おこることもできる ) Date Issue Occurred: Open date for the issue 問題発生日付け ( 問題が提示された発生日付け ) 4D Due Date: Default is 24 hours from date issue occurred 4D 完成日付け ( 基本問題発生時間から 24時間以内 ) 8D Due Date: If applicable. Default is 1 week from date issue occurred 8D 完成日付け ( 基本問題発生時間から 1週間以内 ) Date Issue Closed: All permanent corrective actions have been implemented and their effectiveness validated; All required support documents have been submitted. イシュー解決日付け : ( すべての永久的な問題解決方案が提示適用されたし, すべての方案が有用にゾックヨングドエンイルザ, TEAM MEMBERS チーム構成員 Champion Name/Title/Phone Number/Email Address: Contact information for the individual who is leading the corrective action and submitting the 4D/8D.担当者名前/地位/電話番号/E-mail 住所 : 4D/8Dを提出して問題解決を主導する担当者の情報 Additional Team Member Name(s)/Title(s)/Phone Number(s)/Email Address(es): Contact information for the crossfunctional team members who share responsibility for the corrective actions. 追加的なチーム構成員たちに対する声明(名前)/地位/電話番号/E-mail 住所 : 対応策について連携責任を負う追加的なチームメンバーたちに対する情報 PROBLEM DESCRIPTION 問題説明 Description: Describe the issue from a customer’s perspective; what would they know? 説明 : 顧客が何が分かりたがっているのか, 顧客の観点で問題に対して説明しなさい, When: When were the parts manufactured? When were they assembled? When were the assemblies shipped to the customer? When assembled in vehicles ? When shipped from OEM?
いつ : いつ製品が生産されられたのか? いつ製品が組み立てされられたのか? いつ製品が顧客に納入されられたのか? いつ完成車に組み立てされられたのか ? いつ Detection: How was AG made aware of the issue? Who provided the information? 发现: どんなに Automotive Groupは問題に対して認識されられたのか ? 誰がこの情報を提供したのか ? Extent: How many units are suspected? Proportion found suspect. Where has the data come from - in house, in transit, at customer. どれだけ多い問題数量が疑心されられるか ? 工場 ,納品 , Failure Mode: How does the issue manifest itself? Impact on Customer: Identify the potential for shut down, line interruptions, yard recalls, warranty. etc. 顧客に対する影響 ( 工場閉鎖,生産ライン止まり,リコール,保証,等々に対する潜在的な危険要素を区別しなさい ) Facilities Involved: Customer, JCI and any Suppliers 問題に同参した要素 ( 顧客, JCI そして供給者たち ) INTERIM CONTAINMENT 临时措施 What actions were taken to immediately protect the customer and contain any suspect inventory? Since original notification, how are we containing this issue? What is the current containment status? What sorting have we done, where and how have we verify,疑心されられる再考物品を含んで顧客を保護するためにどんな即刻なゾツィが酔われたのか? Other Product/Platform at Risk: Other JCI lines or Customers who may be impacted by this issue その他製品に対する危険要素はあるか:この問題によって影響を受けたその他 JCI 生産ラインまたは顧客
Identification of Certified Material: Color, size, location, and content of label or hand-written identification on each part and/or container of certified material.認証された製品に対する証明:在每一个经认可的物料零件和/或包装上有以颜色、尺寸、位置、标签内容或者 手写的识别标记。 Sorting Results: Time, date, total number sorted and quantity rejected - broken down by facility (e.g., Customer, JCI, Supplier) 区別結果 ( 時間,日付け, 区別された総数量そして断れられた数量 ) (はい, 顧客, JCI, 供給者 ) Sorted #: Total # sorted at all facilities Defect #: Total # of defects found at all facilities Interim Containment Start Date: Date ROOT CAUSE 根本原因 Note: The form provides fields for documentation of a single root cause. If additional root causes are identified, "Copy" rows 27-31 and "Insert Cut Cells" to create additional fields. 注意 : 文書は一つのグンボンワンインエヘした文書化値段を提供する. もし追加的に根本原因が識別になられれば." 十 27-31をコピーして "INSERT CUT CELLS" Why Made & How Verified: Identify each root cause for why the issue occurred. Has it been turned on and off? How? Verify through statical evidence/hypothesis testing. If not verified by turning on/off, identify as a suspected root cause. 根本原因に対してどうして作られたしどんなに確認されられたのか
Variation: What are opportunities for variation in the process, i.e. how many fixtures do the same process? How many weld cells or robots? Etc. Why Shipped & How Verified: Identify each root cause for why the issue escaped. Has it been turned on and off? How? Verify through statical evidence/hypothesis testing. If not verified by turning on/off, identify as a suspected root cause. どうして出荷されられたしどんなに確認されられたのか PERMANENT CORRECTIVE ACTION 永久性纠正措施 Note: The form provides fields for documentation of a single root cause verification. If additional root causes have been identified, "Copy" rows 32-40 (steps1-5) and "Insert Cut Cells" to create additional fields. 注意:表格提供了填写单个根本原因的位置,若发现还有其它根本原因,复制32-40 Corrective Action for Why Made: Identify permanent corrective action(s) planned to address the root cause. 针对造成制造问题根原因的纠正措施:辨识出针对于根原因的永久性纠正措施 Corrective Action for Why Shipped: Identify permanent corrective action(s) planned to address the root cause. 针对造成发运问题根原因的纠正措施:辨识出针对根原因的永久性纠正措施 VERIFICATION OF CORRECTIVE ACTIONS デウングチェックエデした証明 Has the issue been turned on and off? How? Verification through statical evidence / hypothesis testing. Verification of corrective action for each why made and why shipped is required. デウングチェックエデした証明 : 問題が解決されられたのか? どんなに? 問題になった製品に対してどうして作られたしどうして出荷されたのかに関する再確認及び証拠 Corrective Action Owner Name/Phone Number/Email Address: Contact information for the individual responsible for implementing the corrective action. 対策関連担当者声明(名前)/対策関連担当者電話番号/ 対策関連担当者 E-mail 住所 Target Completion Date: Date by which all of the corrective actions for this root cause will be implemented. 目標完了日付け: 根本原因に対して対応方案が初めて適用されられた日付け
Build Date for Certified Material: "Clean point" at which all material is certified as good. 代替品に対する完成日付け:問題点関連 :"解決時点" すべての資材がムンゼオブヌンゴッに証明されられた時点 How Will New Parts Be Identified? Color, size, location, and content of label or hand-written identification on each part and/or container of certified material. どんなに代替品に対して問題がないと証明しようか? 色相,大きさ, 位置そしてラベルの content またはそれぞれの製品の上の手記で作成または認証されられた資材に対するコンテナ PREVENTION 防止 How will this issue be avoided in the future? Identify systematic changes that will be put in place to prevent the issue from occurring again. If applicable, standardize the improvements in other "at risk" areas. これからどんなにこのような問題が発生されないようにしようか? システム的な変更による問題再発防止策, もし可能ならば, もう一つの問題領域の改善標準対策で活用 Other Facilities or Platforms At Risk? Identify name, part#, corrective action owner for follow up & due date for any other facility or platform that may be at risk for the same issue. Enter "N/A" if the issue is isolated. "Copy" rows 48-49 and "Insert
Has the necessary documentation been updated? Identify the documents that must be updated to include the permanent corrective actions, along with who is responsible for the updates and the dates by which they will be updated. Enter "N/A" if the document その他危険要素に対する道具
CLOSURE 完結 Closure Statement: “Close issue…” (Begin with words noted in “” followed by the rationale for closure.) 終了文章" 問題解決完了" ( "" 中の単語で入力しなさい )
間から 1週間以内 )
8D Problem Analysis Rep 8D 問題分析報告書 Customer/顾客: Program/项目: Product/製品: Issue#/問題番号:
サプライヤーのための寸法要件は、少なくとも、黄色のフ 詳細付き)。このような日付の値として、地域のニーズ、、 1. Team Members チーム構成員
Champion Name チャンピオン 声明(名前) Additional Team Member Name(s) 追加チーム構成員名前
2. Problem Description 問題説明
Description (Describe issue in terms of what, where, when and how many) 説明 (何,どの,いつそしてどの位原則のもとにイシューを説明しなさい )
Impact on Customer (Identify the potential for shut down, line interruptions, yard recalls, w 顧客に対する影響 ( 工場閉鎖,生産ライン止まり,リコール,保証,等々に対する潜在的な危険要
Facilities Involved (Customer, JCI and any Suppliers) 問題に同参した要素 ( 顧客, JCI そして供給者たち )
3. Interim Containment
What actions were taken to immediately protect the customer and contain any suspect inv 疑心されられる再考物品を含んで顧客を保護するためにどんな即刻なゾツィが酔われたのか?
Other Product/Platform at Risk ? その他製品に対する危険要素はあるか?
Sorting Results (Time, Date, Total Number Sorted and Quantity Rejected) 区別結果 ( 時間,日付け, 区別された総数量そして断れられた数量 )
Interim Containment Start Date MM/DD/YYYY
緑の形で少なくとも著名な領域を埋めるために仕入先の (以前のラベルの指示で)、電話番号は、数値形式でなけ 4. Root Cause 根本原因
ROOT CAUSE #1/根本原因 Why Made & How Verified/根本原因に対してどうして作られたしどんなに確認されられたのか
Why Shipped & How Verified/どうして出荷されられたしどんなに確認されられたのか
ROOT CAUSE # 2/근본원인#2 Why Made & How Verified/根本原因に対してどうして作られたしどんなに確認されられたのか
Why Shipped & How Verified/どうして出荷されられたしどんなに確認されられたのか
5. Permanent Corrective Action 永久的な対策
ROOT CAUSE #1/根本原因 Corrective Action for Why Made /どうして作られたと言うのに大韓永久的な対策
Corrective Action for Why Shipped /どうして製品が出荷されられたと言うのに大韓対策
ROOT CAUSE #2/ 근본원인 #2 Corrective Action for Why Made /どうして作られたと言うのに大韓永久的な対策
Corrective Action for Why Shipped /どうして製品が出荷されられたと言うのに大韓対策
6. Verification of Corrective Actions デウングチェックエデした 証明
Verification of Corrective Action: Has the issue been turned on and off? How? Verificatio each why made and why shipped is required./デウングチェックエデした証明 : 問題が解決さ 問題になった製品に対してどうして作られたしどうして出荷されたのかに関する再確認及び証
Corrrective Action Owner Name 対策関連担当者声明(名前)
Build Date for Certified Material 代替品に対する完成日付け MM/DD/YYYY
7. Prevention 再発防止
How will this issue be avoided in the future? /これからどんなにこのような問題が発生されな
Has the necessary documentation been updated?/係わられた文書は皆更新された のか?
Closure Statement/終了文章
8. Closure 完結
8D Problem Analysis Report 8D 問題分析報告書 Date Issue Occurred/起始日期: 4D Due Date/4D完成日期: 8D Due Date/8D完成日期: Date Issue Closed/关闭日期:
のための寸法要件は、少なくとも、黄色のフィールドでフォームを記入すること。前のラベル のような日付の値として、地域のニーズ、、電話番号が数値形式でなければなりません Champion Title チャンピオン 地位
Champion Phone Number チャンピオン 電話番号
Title(s) 地位
Phone Number(s) 電話番号
issue in terms of what, where, when and how many) してどの位原則のもとにイシューを説明しなさい )
dentify the potential for shut down, line interruptions, yard recalls, warranty, etc..) 場閉鎖,生産ライン止まり,リコール,保証,等々に対する潜在的な危険要素を区別しなさい )
stomer, JCI and any Suppliers) 顧客, JCI そして供給者たち )
en to immediately protect the customer and contain any suspect inventory? 品を含んで顧客を保護するためにどんな即刻なゾツィが酔われたのか?
m at Risk ? 険要素はあるか?
Date, Total Number Sorted and Quantity Rejected) け, 区別された総数量そして断れられた数量 )
Identification of certified material ? 認証された材料に対する証明はなられるか?
tart Date MM/DD/YYYY
くとも著名な領域を埋めるために仕入先の8D要件。このような値を日付として定義された領 ルの指示で)、電話番号は、数値形式でなければなりません
原因 fied/根本原因に対してどうして作られたしどんなに確認されられたのか
erified/どうして出荷されられたしどんなに確認されられたのか
원인#2 fied/根本原因に対してどうして作られたしどんなに確認されられたのか
erified/どうして出荷されられたしどんなに確認されられたのか
原因 Why Made /どうして作られたと言うのに大韓永久的な対策
Why Shipped /どうして製品が出荷されられたと言うのに大韓対策
본원인 #2 Why Made /どうして作られたと言うのに大韓永久的な対策
Why Shipped /どうして製品が出荷されられたと言うのに大韓対策
ve Action: Has the issue been turned on and off? How? Verification through statical evidence / hypothesis testing. Verification of corrective a hy shipped is required./デウングチェックエデした証明 : 問題が解決されられたのか? どんなに? してどうして作られたしどうして出荷されたのかに関する再確認及び証拠
C.A. Owner Phone Number 対策関連担当者電話番号
C.A. Owner E-mail Address 対策関連担当者 E-mail 住所
How Will New Parts Be Identified? どんなに代替品に対して問題がないと証明しようか?
avoided in the future? /これからどんなにこのような問題が発生されないようにしようか?
了文章
Affected Document/留官文書
DFMEA PFMEA Controll Plan Process flow Operation Instructions Drawing Design standards
Owner for Update/更新者
Advanced Development Concept Development Product Definition
ォームを記入すること。前のラベルで( 数値形式でなければなりません Champion E-mail Address チャンピオン E-mail地址 E-mail Address(es) E-mail地址
material ? 明はなられるか?
ような値を日付として定義された領域、 せん
ence / hypothesis testing. Verification of corrective action for なに?
Target Completion Date 目標完了日付け MM/DD/YYYY
Date/更新日付け MM/DD/YYYY
Instruktion vedrørende 4D- og 8D-problemanalyserapport
Du bedes læse denne vejledning grundigt, før du udfylder formularen. En 4D-anmodning kræv til og med 3. En 8D-anmodning kræver, at du opdaterer 4D-informationerne og udfylder alle re Deadline for 4D og 8D er tydeligt angivet i SMRR- eller DMR-rapporten, som var vedlagt den o om problemet. 4D skal sikre, at leverandøren straks foretager det nødvendige inden for egen v sikre, at problemet inddæmmes. Det er nødvendigt, at du svarer pr. e-mail til alle, som var kop relevante 4D- eller 8D-tilbagemelding.
FORMULARHOVED 1) Leverandørnavn/-hjemsted: (f.eks. Danfoss/DK) 2) Kunde: (f.eks. Johnson Controls Parts Centre, DK) 3) Program: (f.eks. Køleautomatik) 4) Produkt: (f.eks. Reguleringsventil DN50) 5) Sagsnr.: Johnson Controls' referencenummer (SMRR- el. DMR-nummer) 6) Dato for problemets opståen: Den dato, hvor sagen blev åbnet 7) Deadline for 4D: Standardkravet er 24 timer fra problemets opståen 8) Deadline for 8D: Hvis relevant. Standardkravet er 7 arbejdsdage fra problemets op 9) Dato for sagens afslutning: Alle permanente korrigerende handlinger er gennemfø fremsendt. Discipline 1 Disciplin 1. TEAMDELTAGERE 1) Navn på den ansvarlige/titel/telefonnummer/e-mail-adresse: Kontaktoplysninger p fremsendelse af 4D/8D. 2) Navne på øvrige teamdeltagere/titler/telefonnumre/e-mail-adresser: Kontaktoplysn de korrigerende handlinger.
Disciplin 2. PROBLEMBESKRIVELSE 1) Beskrivelse: Beskrivelse af problemet set fra kundens perspektiv – hvilken informa
2) Indvirkning på kunden: Vurder muligheden for nedlukning, produktionslinjestop, til 3) Involverede parter: Kunder, Johnson Controls selskaber og leverandører.
Disciplin 3. MIDLERTIDIG INDDÆMNING 1) Hvilke tiltag blev iværksat straks for at beskytte kunden og inddæmme lager af de blev kendt, sikret en inddæmning? Hvad er nuværende status på denne inddæmn verificeret effektiviteten? Hvis en plan for udbedring eller eftermontering er påbegy effektiviteten? Vedlæg plan med skitser og trendgrafer.What actions were taken to Sinceprodukter/-grupper: original notification,Andre how are we containing issue?eller What is 2) inventory? Risiko for andre Johnson Controls this produker virkso
3) Identificering af afmærket materiale: Farve, størrelse, placering og indhold af mær container/palle/kasse med afmærket materiale. 4) Sorteringsresultater: Tid, dato, samlet antal sorteret og samlet mængde afvist – fo leverandører, lagre etc.). 5) Antal sorteret: Samlet antal sorteret hos alle involverede parter. 6) Antal fejl: Samlet antal fejl fundet hos alle involverede parter. 7) Startdato for midlertidig inddæmning: Den dato, hvor den midlertidige inddæmning
Discipline 4. HOVEDÅRSAG Bemærk: Skemaet indeholder felter til dokumentation af en enkelt årsag. Hvis yde Cut Cells" for at oprette yderligere felter. 1) Hvorfor opstået & hvordan verificeret: Fastlæg hver enkelt hovedårsag til, at probl Hvordan? Bekræft vha. statistisk bevismateriale/hypotesetest. Hvis ikke verificere formodet hovedårsag. 2) Hvorfor afsendt & hvordan verificeret: Fastlæg hver enkelt hovedårsag til, at probl aktiveret/deaktiveret? Hvordan? Bekræft vha. statistisk bevismateriale/hypotesete klassificeres den som en formodet hovedårsag. Disciplin 5. PERMANENT KORRIGERENDE HANDLING Bemærk: Skemaet indeholder felter til dokumentation af en enkelt årsag verifikatio "Kopi" rækkerne 32-40 (steps1-5) og "Indsæt Cut Cells" for at oprette yderligere fe 1) Korrigerende handling for ”hvorfor opstået”: Udpeg, hvilken permanent korrigerend 2) Korrigerende handling for ”hvorfor afsendt”: Udpeg, hvilken permanent korrigerend Disciplin 6. VERIFIKATON AF KORRIGERENDE HANDLINGER Page 240 of 2
1) Har fejlkilden været aktiveret/deaktiveret? Hvordan? Verifikation vha. statistisk bev handling for hver enkelt ”hvorfor opstået” og ”hvorfor afsendt”.
2) Navnet på “ejeren” af den korrigerende handling/telefonnummer/e-mail-adresse: K gennemføre den korrigerende handling. 3) Forventet afslutningsdato: Datoen inden for hvilken alle korrigerende handlinger fo 4) Fremstillingsdato for afmærket materiale: Skæringspunkt (eller termin), hvor alt m 5) Hvordan bliver nye dele identificeret? Farve, størrelse, placering og indhold af mæ container/palle/kasse med afmærket materiale.
Disciplin 7. FOREBYGGELSE 1) Hvordan undgås problemet fremover? Angiv hvilke systematiske ændringer, der v relevant standardiseres forbedringerne til at omfatte andre risikoområder. 2) Andre forretningsenheder eller produktgrupper, som kan være berørt? Udpeg nav opfølgning samt deadline gældende for alle andre forretningsenheder og produktg (eller ”ikke relevant”), hvis problemet er isoleret. Udfør ”Copy” for række 48-49 og 3) Er den nødvendige dokumentation blevet opdateret? Fastlæg hvilke dokumenter, korrigerende handlinger samt hvem, der er ansvarlig for opdateringerne og inden (eller ”ikke relevant”), hvis det ikke er nødvendigt at opdatere dokumentet. Disciplin 8. AFSLUTNING 1) Afslutningserklæring: ”Sagen afsluttes ….” (Indled med ordene i anførelsestegn og DOKUMENTVERSION 1)
Version 1,5: Formatering tekstfelter pålagt
2)
Ver Version 1,6: IRIS R.11.4 forbedringer opdatering.
Page 241 of 2
Instruktion vedrørende 4D- og 8D-problemanalyserapport Du bedes læse denne vejledning grundigt, før du udfylder formularen. En 4D-anmodning kræver, at du udfylder formularen fra disciplin 1 til og med 3. En 8D-anmodning kræver, at du opdaterer 4D-informationerne og udfylder alle resterende discipliner (til og med 8). Deadline for 4D og 8D er tydeligt angivet i SMRR- eller DMR-rapporten, som var vedlagt den oprindelige e-mail, hvor du blev informeret om problemet. 4D skal sikre, at leverandøren straks foretager det nødvendige inden for egen virksomhed og/eller i forhold til lagre for at sikre, at problemet inddæmmes. Det er nødvendigt, at du svarer pr. e-mail til alle, som var kopieret på den oprindelige e-mail, med den relevante 4D- eller 8D-tilbagemelding.
FORMULARHOVED Leverandørnavn/-hjemsted: (f.eks. Danfoss/DK) Kunde: (f.eks. Johnson Controls Parts Centre, DK) Program: (f.eks. Køleautomatik) Produkt: (f.eks. Reguleringsventil DN50) Sagsnr.: Johnson Controls' referencenummer (SMRR- el. DMR-nummer) Dato for problemets opståen: Den dato, hvor sagen blev åbnet Deadline for 4D: Standardkravet er 24 timer fra problemets opståen Deadline for 8D: Hvis relevant. Standardkravet er 7 arbejdsdage fra problemets opståen Dato for sagens afslutning: Alle permanente korrigerende handlinger er gennemført og effektiviteten valideret. Alle nødvendige dokumenter er fremsendt. Discipline 1 Disciplin 1. TEAMDELTAGERE Navn på den ansvarlige/titel/telefonnummer/e-mail-adresse: Kontaktoplysninger på den person, der er ansvarlig for den korrigerende handling og fremsendelse af 4D/8D. Navne på øvrige teamdeltagere/titler/telefonnumre/e-mail-adresser: Kontaktoplysninger på tværfunktionelle teamdeltagerne, som deler ansvaret for de korrigerende handlinger.
Disciplin 2. PROBLEMBESKRIVELSE Beskrivelse: Beskrivelse af problemet set fra kundens perspektiv – hvilken information har de? Hvornår: Hvornår blev delene fremstillet? Hvornår blev de samlet? Hvornår blev de sammenbyggede dele sendt til kunden? Hvornår blev de monteret i det overordnede produkt? Omfang: Hvor mange enheder er under mistanke? Hvilket forholdsmæssigt antal er fundet med mistænkte fejl? Hvorfra kommer data – internt, under leve Opdagelse: Hvordan fik Johnson Controls kendskab til problemet? Hvem kom med oplysningen? Fejltilstand: Hvordan viser problemet sig? Indvirkning på kunden: Vurder muligheden for nedlukning, produktionslinjestop, tilbagekaldelsesaktioner, garanti etc. Involverede parter: Kunder, Johnson Controls selskaber og leverandører. Disciplin 3. MIDLERTIDIG INDDÆMNING Hvilke tiltag blev iværksat straks for at beskytte kunden og inddæmme lager af dele, der er under mistanke? Hvordan har vi, siden problemet først blev kendt, sikret en inddæmning? Hvad er nuværende status på denne inddæmning? Hvilken sortering har vi foretaget – hvor og hvordan har vi verificeret effektiviteten? Hvis en plan for udbedring eller eftermontering er påbegyndt – hvad går den ud på, og hvordan har vi verificeret effektiviteten? Vedlæg plan med skitser og trendgrafer.What actions were taken to immediately protect the customer and contain any suspect inventory? Sinceprodukter/-grupper: original notification,Andre how are we containing issue?eller What is the current containment status? sorting have we done, Risiko for andre Johnson Controls this produker virksomheder, som kan risikere at bliveWhat berørt af problemet. Identificering af afmærket materiale: Farve, størrelse, placering og indhold af mærkat eller håndskreven identifikation på hver del og/eller container/palle/kasse med afmærket materiale. Sorteringsresultater: Tid, dato, samlet antal sorteret og samlet mængde afvist – fordelt på de involverede parter (dvs. hos Johnson Controls, leverandører, lagre etc.). Antal sorteret: Samlet antal sorteret hos alle involverede parter. Antal fejl: Samlet antal fejl fundet hos alle involverede parter. Startdato for midlertidig inddæmning: Den dato, hvor den midlertidige inddæmning startede. Discipline 4. HOVEDÅRSAG Bemærk: Skemaet indeholder felter til dokumentation af en enkelt årsag. Hvis yderligere årsager er identificeret, "Kopi" rækkerne 27-31 og "Indsæt Cut Cells" for at oprette yderligere felter. Hvorfor opstået & hvordan verificeret: Fastlæg hver enkelt hovedårsag til, at problemet kunne opstå. Har fejlkilden været aktiveret/deaktiveret? Hvordan? Bekræft vha. statistisk bevismateriale/hypotesetest. Hvis ikke verificeret vha. ”aktivering/deaktivering”, klassificeres den som en formodet hovedårsag. Variation: Hvilke muligheder er der for variation i processen? Dvs. i hvor mange opstillinger udføres samme proces? Hvor mange svejseceller Hvorfor afsendt & hvordan verificeret: Fastlæg hver enkelt hovedårsag til, at problemet ikke blev opdaget. Har fejlkilden været aktiveret/deaktiveret? Hvordan? Bekræft vha. statistisk bevismateriale/hypotesetest. Hvis ikke verificeret vha. ”aktivering/deaktivering”, klassificeres den som en formodet hovedårsag. Disciplin 5. PERMANENT KORRIGERENDE HANDLING Bemærk: Skemaet indeholder felter til dokumentation af en enkelt årsag verifikation. Hvis yderligere grundlæggende årsager er blevet identificeret, "Kopi" rækkerne 32-40 (steps1-5) og "Indsæt Cut Cells" for at oprette yderligere felter. Korrigerende handling for ”hvorfor opstået”: Udpeg, hvilken permanent korrigerende handling(er), der er planlagt for at tage hånd om hovedårsagen. Korrigerende handling for ”hvorfor afsendt”: Udpeg, hvilken permanent korrigerende handling(er), der er planlagt for at tage hånd om hovedårsagen. Disciplin 6. VERIFIKATON AF KORRIGERENDE HANDLINGER Page 242 of 2
Har fejlkilden været aktiveret/deaktiveret? Hvordan? Verifikation vha. statistisk bevismateriale/hypotesetest. Der kræves verifikation af korrigerende handling for hver enkelt ”hvorfor opstået” og ”hvorfor afsendt”. Navnet på “ejeren” af den korrigerende handling/telefonnummer/e-mail-adresse: Kontaktoplysninger på den person, der er ansvarlig for at gennemføre den korrigerende handling. Forventet afslutningsdato: Datoen inden for hvilken alle korrigerende handlinger for denne hovedårsag vil være gennemført. Fremstillingsdato for afmærket materiale: Skæringspunkt (eller termin), hvor alt materiale er mærket som værende i orden. Hvordan bliver nye dele identificeret? Farve, størrelse, placering og indhold af mærkat eller håndskreven identifikation på hver del og/eller container/palle/kasse med afmærket materiale. Disciplin 7. FOREBYGGELSE Hvordan undgås problemet fremover? Angiv hvilke systematiske ændringer, der vil blive iværksat for at undgå, at problemet gentager sig. Hvis relevant standardiseres forbedringerne til at omfatte andre risikoområder. Andre forretningsenheder eller produktgrupper, som kan være berørt? Udpeg navn, partnummer, ejer af korrigerende handling og ansvarlig for opfølgning samt deadline gældende for alle andre forretningsenheder og produktgrupper, som kan være berørt af samme problem. Skriv ”N/A” (eller ”ikke relevant”), hvis problemet er isoleret. Udfør ”Copy” for række 48-49 og ”Insert Cut Cells” for at danne yderligere felter, hvis nødvendigt. Er den nødvendige dokumentation blevet opdateret? Fastlæg hvilke dokumenter, der skal opdateres, så de indeholder de permanente korrigerende handlinger samt hvem, der er ansvarlig for opdateringerne og inden for hvilke datoer, de vil blive opdateret. Skriv ”N/A” (eller ”ikke relevant”), hvis det ikke er nødvendigt at opdatere dokumentet. Disciplin 8. AFSLUTNING Afslutningserklæring: ”Sagen afsluttes ….” (Indled med ordene i anførelsestegn og fortsæt med at forklare rationalet for afslutning af sagen). DOKUMENTVERSION Version 1,5: Formatering tekstfelter pålagt Ver Version 1,6: IRIS R.11.4 forbedringer opdatering.
Page 243 of 2
al er fundet med mistænkte fejl? Hvorfra kommer data – internt, under levering, hos kunden.
e handling(er), der er planlagt for at tage hånd om hovedårsagen. e handling(er), der er planlagt for at tage hånd om hovedårsagen.
Page 244 of 2
8D problemanalyserapport Skabelon Version 11,4
Kunde: Program: Produkt: Sagsnr. :
For 4D anmodninger skal leverandørerne på et minimu instruktionerne fanen for yderligere detaljer). Områder datoer og telefonnumre skal være i en numerisk format 1. Teamdeltagere
Navnet på den ansvarlige Navnet på øvrige teamdeltagere
2. Problembeskrivelse
Beskrivelse (beskriv problemet ift. hvad, hvor, hvornår og hvor mange)
Indvirkning på kunden (vurder muligheden for nedlukning, produktionslinjestop, tilbage
Faciliteter involveret (Customer, JCI og eventuelle leverandører)
3. Interim Containment
Hvilke handlinger blev taget til straks beskytte kunden og indeholder en mistænkt beho
Risiko for andre produkter/produktgrupper?
Sorteringsresultater (tid, dato, samlet antal sorteret og samlet mængde afvist)
Startdato for midlertidig inddæmning DD.MM.YYYY
For 8D anmodninger skal leverandørerne på et minimum, udfylde felte for detaljer) Områder der kræver numeriske værdier, såsom datoer elle 4.Hovedårsag
Hovedårsag #1 Hvorfor opstået & hvordan verificeret
Hvorfor afsendt & hvordan verificeret
Hovedårsag #2 Hvorfor opstået & hvordan verificeret
Hvorfor afsendt & hvordan verificeret
5. Permanent korrigerende handling Action
Hovedårsag#1 Korrigerende handling for ”hvorfor opstået”
Korrigerende handling for ”hvorfor afsendt”
Hovedårsag #2 Korrigerende handling for ”hvorfor opstået”
Korrigerende handling for ”hvorfor afsendt”
Verifikation af korrigerende handling: 1) Har fejlkilden været aktiveret/deaktiveret? Hvo 6. Verifikation af korrigerende handlinger kræves verifikation af korrigerende handling for hver enkelt ”hvorfor opstået” og ”hvor
Navnet på “ejeren” af den korrigerende handling
Fremstillingsdato for afmærket materiale DD.MM.YYYY
7. Forebyggelse
Hvordan undgås problemet fremover?
Er den nødvendige dokumentation blevet opdateret?
Afslutningserklæring (validering)
8. Afslutning
8D problemanalyserapport Dato for problemets opståen: Deadline for 4D: Deadline for 8D: Dato for sagens afslutning:
ger skal leverandørerne på et minimum, Udfyld de fremhævede felter i gult. (Se anen for yderligere detaljer). Områder, der kræver numeriske værdier såsom numre skal være i en numerisk format. Pågældendes titel
Pågældendes telefonnummer
Titler
Telefonnumre
met ift. hvad, hvor, hvornår og hvor mange)
er muligheden for nedlukning, produktionslinjestop, tilbagekaldelsesaktioner, garanti etc.)
mer, JCI og eventuelle leverandører)
t til straks beskytte kunden og indeholder en mistænkt beholdning?
roduktgrupper?
Identificering af afmærket materiale?
o, samlet antal sorteret og samlet mængde afvist)
dæmning DD.MM.YYYY
kal leverandørerne på et minimum, udfylde felterne fremhævet med grønt. (Se instruktionerne fanen der kræver numeriske værdier, såsom datoer eller telefonnumre, skal være i en numerisk format.
erificeret
erificeret
erificeret
erificeret
hvorfor opstået”
hvorfor afsendt”
hvorfor opstået”
hvorfor afsendt”
handling: 1) Har fejlkilden været aktiveret/deaktiveret? Hvordan? Verifikation vha. statistisk bevismateriale/hypotesetest. Der erende handling for hver enkelt ”hvorfor opstået” og ”hvorfor afsendt”.
Pågældendes telefonnummer
Pågældendes e-mail-adresse
Hvordan bliver nye dele identificeret?
fremover?
ring)
Berørte dokumenter
DFMEA PFMEA Kontrolplan Process Flow Driftsinstruktioner Tegninger Designstandarder
Ansvarlig for opdatering
ld de fremhævede felter i gult. (Se æver numeriske værdier såsom Pågældendes e-mail-adresse E-mail-adresser
tioner, garanti etc.)
rket materiale?
ævet med grønt. (Se instruktionerne fanen numre, skal være i en numerisk format.
ation vha. statistisk bevismateriale/hypotesetest. Der
Forventet afslutningsdato DD.MM.YYYY
Dato DD.MM.YYYY