LEONI QUALITY DEPARTMENT

QRQC Structure Notes:

• Caractérisation Section (Orange): Initial defect characterization with 5 key questions
• • Defect Description: Full-width text field for detailed defect description
• • Who Detected: Auto-filled with current user session (read-only)
• • Which Post: Text field to specify the workstation/post
• • Why it is a Problem: Text field to explain impact and consequences
• • How it was Detected: Text field to describe the detection method
• Personnel Notification Section (Blue): Checkbox list of all personnel roles that must be informed
• 2. TRI Section (Green) - Full Width: Quality sorting table with production stages and quality counts
• • Production Stages: 7 rows covering Magasin produit fini, Palette fin ligne, Ligne d'assemblage, Coupe, Pré-assemblage, Magasin composant, Retouche/cage rouge
• • Quality Columns: Two columns for "Bon" and "Mauvais" with number inputs
• • Reset Button (🔄): Quick reset button to clear all number inputs with confirmation dialog
• • Auto-Decision Logic: System automatically checks "Retouche nécessaire" when bad quantities exceed good quantities
• • Critical Visual Alert: Retouche row turns red with pulsing animation when rework is automatically decided
• • Real-time Totals: Automatic calculation and display of total bon/mauvais quantities
• Two-Column Layout: Sections 3 (Pré-analyse) and 4 (Actions de Sécurisation) are displayed side by side below TRI section
• 3. Pré-analyse Section (Purple): Pre-analysis form with two subsections for defect source investigation
• • Who produced the defect?: Operator ID and Post/Machine identification fields
• • When the defect was produced?: Date and Hour fields for temporal tracking
• 4. Actions de Sécurisation Section (Pink): Security actions table with 3 action rows
• • Action 1, 2, 3: Each action has Responsable and Date fields for accountability
• 5. Analysis Section (Blue/Red): Two "Why" questions with 4 text fields each for thorough root cause analysis
• Why 1 (Blue): Focus on problem identification and root cause
• Why 2 (Red): Focus on detection failure analysis
• 6. Corrective Actions Table (Green): Structured 3-column table with Type, Pilote, and Délai
• Occurrence Row (Red): Actions to prevent problem recurrence with responsible person and deadline
• Non-Detection Row (Orange): Actions to improve detection methods with responsible person and deadline
• 7. Vérification Section (Purple): Verification tracking table for 5 successive teams
• • Team Column: Team identifier (Team 1 through Team 5)
• • Date Column: Date when verification was performed by each team
• • Occurrence Column: Whether the defect occurred again for this team
• • Epoch of Occurrence: Time period when occurrence was detected