We built GPT integration for quality management over 14 weeks, with Betriebsrat engagement from week 1 and DSGVO compliance architecture throughout: (1) Betriebsrat engagement: week 1 — formal BetrVG Section 90 information session with Betriebsrat. Presentation: GPT integration scope (quality management only — not HR, not performance evaluation), data handling (quality data only — no employee performance data processed), transparency commitment (all GPT-generated content clearly marked as AI-assisted), and training plan (16 hours per quality engineer, 8 hours per quality manager). Week 2-3 — Betriebsvereinbarung negotiation. Key provisions: GPT system processes quality data (defect descriptions, root cause analysis, technical specifications) — not employee performance data. Individual quality engineer productivity metrics not calculated or displayed (aggregate team metrics only). GPT outputs clearly labelled as "KI-unterstuetzt" (AI-assisted) — the quality engineer always reviews and takes responsibility for the final document. Quarterly Betriebsrat review of system usage and any proposed expansions.
Employee training completed before system deployment. Betriebsvereinbarung signed at week 3 — no objections, no Arbeitsgericht involvement. (2) 8D report assistance: GPT integrated into the 8D workflow. When a quality engineer opens a new 8D case: historical pattern matching — GPT searches the company's 8D database (15,000+ historical reports) and retrieves the most similar previous defects based on: component type, defect description, manufacturing process, and affected product line. The engineer sees the top 5 similar historical cases with their root causes and corrective actions — providing a starting point rather than a blank sheet. Root cause analysis assistance: based on the defect description and historical patterns, GPT suggests potential root causes structured as 5-Why analysis and Ishikawa diagram categories (Man, Machine, Material, Method, Measurement, Environment). The engineer reviews, modifies, and validates — the GPT output is a draft, not a conclusion.
Corrective action drafting: GPT generates corrective action proposals based on: the identified root cause, historical corrective actions for similar defects, current best practices from quality management literature, and IATF 16949 requirements. Bilingual generation: 8D reports generated simultaneously in German (internal) and English (customer submission) — eliminating the manual translation step. Quality engineer reviews both versions. The GPT model fine-tuned on the company's 15,000 historical 8D reports understands the company's specific terminology, component names, process descriptions, and quality standards. 8D report time: from 6 hours to 2.5 hours (including review). Translation eliminated: bilingual generation saves 2 additional hours. Total time savings: 5.5 hours per report (from 8 hours including translation to 2.5 hours). (3) FMEA update assistance: GPT integrated into the FMEA maintenance workflow. Triggered by: each completed 8D case, GPT automatically identifies which FMEA line items should be reviewed based on the defect's failure mode and the component/process involved.
GPT generates proposed FMEA updates: updated occurrence rating (based on actual defect frequency data from the quality system), proposed additional detection controls (based on the corrective actions from the 8D), suggested new failure modes (if the 8D revealed a failure mode not currently in the FMEA), and updated risk priority number (RPN) calculation. The quality engineer reviews each proposed update — approving, modifying, or rejecting. FMEA update time: from 45 minutes per line item to 15 minutes (GPT provides the draft, engineer validates). FMEA backlog: 890 pending updates cleared within 8 weeks of deployment (engineers processed historical backlog using GPT assistance). Ongoing FMEA currency: the automated 8D-to-FMEA linkage ensures FMEAs are updated within 5 business days of each quality incident (from 18-month backlog). (4) Customer specification analysis: GPT processes OEM specification documents (BMW Liefervorschrift, Mercedes DBL, Audi TL).
The system: parses multi-hundred-page specification PDFs, identifies sections relevant to the company's specific component type (material specifications, testing requirements, dimensional tolerances, surface finish, heat treatment, coating requirements), cross-references with the company's current manufacturing capabilities, flags requirements that exceed current capability or differ from current process parameters, generates a structured requirements matrix (requirement, specification reference, current capability, gap analysis, and action items), and highlights changes from previous specification versions (critical for engineering change management). Specification analysis: from 40-80 hours per bid to 8-15 hours (GPT extracts and structures requirements — engineers validate and supplement with domain judgment). The company can now respond to more RFQs and respond faster — improving win rate on new programmes. (5) Supplier quality communication: GPT assists in drafting supplier quality correspondence. Supplier audit reports: GPT generates draft reports from audit checklists and notes — the quality auditor reviews and finalises.
Corrective action requests: GPT generates CARs from quality data (defect descriptions, rejected lot information) in both German and English. Supplier performance summaries: GPT compiles monthly supplier quality dashboards from SAP QM data — presenting PPM rates, delivery performance, and quality trends in structured reports. Communication efficiency: 15 hours per week reduced to 6 hours per week. (6) DSGVO compliance: DSFA completed before deployment. All GPT interactions logged in the Verzeichnis von Verarbeitungstaetigkeiten. Personal data: quality reports may contain employee names (who inspected, who approved) — PII redaction applied before GPT processing (names replaced with role identifiers — "Pruefer 1," "Freigeber 2" — and reinserted into output after GPT processing). AVV with Azure (Azure OpenAI, West Europe region — EU Data Boundary) executed and filed. Data residency: all GPT processing within EU. Prompts and completions not used for model training.