COP (Conformity of Product) themes address product-level NC: does the vehicle meet its design spec, type-approval regulation, customer requirement, and 12-month field performance? These are the themes that result in recall, warranty, or shipment-hold risk.
Compliance themes address process-level NC: are we following the standards (IATF 16949, ISO 14001, USECHH, DOE) for how we operate? These are the themes that result in audit findings, regulatory fines, or certification loss.
My top 3 picks (re-aligned):
1️⃣ COP-A — Type Approval NC Closure (UN R48 / MS 1234 lighting) — product not conforming to homologation regulation, shipment hold live.
2️⃣ COP-B — HVAC Field Warranty Claim Rate (12-mo) — product not conforming to customer-expected life, ¥X million exposure, POO = supplier + plant.
3️⃣ COMP-A — IATF 16949 QMS Audit Findings Closure — process not following standards, Q1 2027 re-cert deadline.
| Term | What it covers | What it does NOT cover | Failure mode |
|---|---|---|---|
| COP (Conformity of Product) | Product meeting: design spec, type-approval regulation, customer requirement, 12-mo field performance, emissions/lighting/safety outputs | Process standards adherence (that's Compliance), customer service, dealer relations | Recall, warranty, shipment hold, type-approval withdrawal |
| Compliance | Process following: IATF 16949, ISO 9001, ISO 14001, USECHH, DOE eSWIS, Factory & Machinery Act, JPJ homologation process, parent plant TBP audit | Whether the product itself conforms (that's COP) | Audit finding, regulatory fine, certification loss, plant shutdown |
Many COP failures share root causes with Compliance findings. Example: QP-007 QMS document-control gate — when this gate fails (Compliance), it can produce:
One QP-007 gate fix → closes multiple COP and Compliance findings. This is the "system thinking, not symptom fixing" story for your AI firm.
| Rank | Theme | Cat | Why this one for you |
|---|---|---|---|
| 🥇 1 | COP-A — Type Approval NC Closure | COP | Hard shipment-hold window live. Already in your portfolio (Theme 0 deck). Re-strengthen to v3.0 = fast win + closes the loop. 90-day close deadline creates urgency story for PD-Interview. |
| 🥈 2 | COP-B — HVAC Field Warranty | COP | Direct customer pain in the field, ¥X million exposure. Multi-stakeholder (supplier + plant + field). 3-perspective Step 7 (Customer / Toyota / Own) shines. Perfect AI-firm case study. |
| 🥉 3 | COMP-A — IATF 16949 QMS Audit Closure | Compliance | IATF re-cert Q1 2027 hard deadline. Same QP-007 gate as COP-A → cross-A3 leverage. "Fixed the gate once for both" = unique system-thinking story for Plant Director panel. |
| If you want… | Build this theme |
|---|---|
| Re-use Theme 0, fast close-out, urgency story | COP-A — Type Approval v3.0 |
| Direct customer field pain, multi-stakeholder | COP-B — HVAC Field Warranty |
| Hard regulatory deadline (IATF re-cert Q1 2027) | COMP-A — QMS Audit Closure |
| Customer-facing paint defect, ASEAN complaint live | COP-C — Paint Orange-Peel |
| Close out existing W-07 portfolio | COP-D — Weld Spatter (W-07) |
| Safety + compliance + capex defence | COMP-B — USECHH Welding Fume PEL |
| Environmental compliance, ESG audit | COMP-C — DOE Scheduled Waste |
| Safety culture, no-cost wins, audit-ready | COMP-D — FMA 1967 Robot Safety + LOTO |
Build COP-A + COMP-A as a paired portfolio. They share a common root cause — QP-007 QMS document-control gate:
| Theme | Failure mode | Root cause |
|---|---|---|
| COP-A — Type Approval NC | WI revision v3.2 missed regulator update Dec 2025 → product not conforming | QP-007 gate did not cross-ref regulator diff |
| COMP-A — QMS Audit Findings | Doc-control finding (IATF clause 7.5.3.2) — same gate | QP-007 gate does not link WI changes to external regulation diffs |
One gate fix → closes multiple COP and Compliance findings. The story:
"We didn't fix Type Approval NC and IATF audit findings separately — we traced both back to the same QP-007 document-control gate, fixed it once, and closed both. This is system thinking, not symptom fixing."
That is a much more powerful AI-firm case study than two unrelated A3s.
1. What went wrong in v1:
2. What's better in v2:
3. What I need from you:
4. Patterns tracked (3× = MEMORY):
5. MEMORY candidate (will save next turn):
🔵 COP = Conformity of Product (not Customer-Oriented Process) in Toyota/QMS context. COP = product-specific conformity to spec/regulation/field-life. Compliance = process-specific adherence to standards/regulations. The two are distinct lenses on similar problems — a non-conforming product often traces to a non-compliant process.