Automotive Defect Registration System + Paperless Unit Record + Report Tabulation Project Paper Research · 3 pillars · ASSB Bukit Raja

For: Syaiful Nizam · HOD Quality · ASSB Paper topic (confirmed): Plant-level digital quality management (NOT JPJ-level) Scope: 3 pillars — defect DB + paperless unit record + report tabulation Date: 15-Jun-2026 Sources: Toyota Production System, IATF 16949, MES vendors, industry papers, Shoplogix, iBase-t, Tulip, Logicbus

🔴 Topic correction (15-Jun-2026): Earlier I was researching PUSPAKOM VIS + JPJ VRC (licensing-level). Sir corrected: the project paper is about PLANT-LEVEL defect management — how ASSB registers defects, keeps per-unit digital records, and tabulates reports. This is the correct scope. The earlier VIS/VRC thread in the channel is now exploratory, not the main paper topic.

BLUF — Bottom Line Up Front

The project paper topic is 3 pillars working as ONE system:

1️⃣ Defect Registration System & Database — every defect found on the line gets logged into a central DB (station, defect type, severity, photo, operator, timestamp, root cause hypothesis)
2️⃣ Paperless Individual Unit Record — every vehicle (chassis #) has a digital "as-built" record from Station 1 to Final PI (replaces paper traveler/sho cards)
3️⃣ Report Tabulation — automated dashboards and reports pulled from the DB (Pareto by station, defect trend, COPQ, gemba frequency, audit closure)

Together this is a Quality Management Information System (QMIS) or Digital Quality Management System (eQMS) for automotive assembly — sits between MES (production) and ERP (business), focused on quality data.

Standards anchor: IATF 16949:2016 clause 8.5.2 (identification & traceability) + 7.5.3.2 (documented information) + Toyota Production System (Jidoka, ANDON, Kaizen).

For your project paper, this fits as:

• COMP-G = "Plant-level Digital Quality Management System (dQMS) — defect DB + paperless unit record + reports" — IATF 16949 + ISO 9001 compliance angle
• It also has a COP angle: "We can answer the question 'is this individual unit conforming?' in real time, not 3 days later when the paper traveler reaches QA"

🟦 Pillar 1: Defect Registration System & Database

The system that captures every defect found on the assembly line into a queryable database. Replaces handwritten defect tags, sticky notes, whiteboards, and ad-hoc spreadsheets.

What gets logged (typical fields):

Chassis / VIN — which vehicle
Station — where defect was found (St W-07, St 12, St 22, etc.)
Defect type / code — paint orange peel, weld spatter, torque miss, marking missing, etc.
Severity — critical / major / minor / cosmetic
Found by — operator ID, inspector ID, andon alert, AI vision
Timestamp — when found, when fixed, when re-inspected
POO — point of occurrence (where defect first appeared, not where caught)
Root cause hypothesis — initial guess for 5-Whys
Photo / video evidence — visual record
Status — open / in-rework / reworked / re-inspected / closed
CM link — which countermeasure addresses this defect type

Capture methods:

Operator tablet at station (touch UI with pre-defined defect codes)
AI vision system (auto-capture from cameras, e.g., St 12 paint)
Andon button → tablet prompt
Inspector mobile app (PI walk)
Customer/field feedback (dealer, warranty claim)

Database backend (typical):

Time-series + relational hybrid (PostgreSQL + InfluxDB, or SQL Server + PI)
Connected to MES (production order, model variant)
Connected to PLM (engineering spec, latest revision)
Connected to ERP (supplier batch, cost)

🟦 Pillar 2: Paperless Individual Unit Record (PIUR)

Every vehicle has a digital "as-built" record from Station 1 to Final PI. Replaces the paper traveler / sho card / build sheet that physically moves with the vehicle on the line.

What gets recorded per unit (typical fields):

Chassis / VIN + model variant + options
Engine # + transmission # + key component serial numbers
Supplier batch for every critical component (RFID-scanned)
Station-by-station pass/fail with timestamp + operator
Torque values for every critical joint (with wrench ID + cycle count)
Paint spec (color code, batch, line parameters at time of paint)
Fluid fill (fuel, oil, coolant, refrigerant — quantity + spec)
Inspection results at every gate (BIW, paint, trim, final PI)
Defects logged (links to Pillar 1 DB)
Rework history (who fixed, when, retest pass/fail)
Final sign-off (electronic signature, 21 CFR Part 11 / IATF compliant)
Photo at final PI (visual record of "as-shipped" condition)

Replaces paper artifacts:

Paper traveler / build sheet (rides with vehicle)
Sho cards (small parts bins attached to vehicle)
Handwritten inspection sheets
Paper torque-verification stickers
Paper rework tags ("Hold" tags)

Why paperless matters (IATF + business):

IATF 16949 clause 7.5.3.2 — documented information must be controlled, retrievable, protected
Recall traceability — locate every unit with supplier X batch Y in < 1 min, not > 1 day
Real-time COPQ — labor hours, scrap, rework cost visible per unit, not month-end
Eliminate lost traveler / mis-filed inspection sheet / faded handwritten note

🟦 Pillar 3: Report Tabulation

Automated reports and dashboards pulled from Pillar 1 + 2. The "what does the data tell us" layer. Goes to operators, supervisors, section heads, HODs, parent plant, regulators.

Report types (typical layered):

Operator level — station dashboard, live defect count, current POO hypothesis
Section head level — shift Pareto, top 3 defect types, CMs in progress, % rework
HOD / Plant manager level — daily/weekly COPQ, audit findings closure, COP metric, TBP A3 progress
Parent plant (TMC) — monthly defect rate by station/model, parent plant benchmark, kaizen opportunities
Regulator (JPJ / IATF / customer audit) — compliance reports on demand, traceability evidence

Standard report templates:

Pareto by station (top 3 stations = 80% of NCs) — Step 2 TBP
Defect trend (line chart, last 90 days) — Step 6+7 TBP
5-Whys ladder (current open A3s with status) — Step 4 TBP
CM tracker (matrix, owner, Q-by, % complete) — Step 5 TBP
COPQ (rework hours, scrap kg, warranty exposure) — Step 3 TBP target metric
Audit findings closure (90-day closure rate) — COMP-A theme
Gemba frequency (genchi genbutsu — % planned vs actual)

Why ASSB Specifically Needs This (the pain)

ASSB produces multiple models (Hilux, Fortuner, Vios) across multiple lines with variants → defect attribution is complex
Defect records today are partially paper (defect tags, traveler) + partially spreadsheet (line PC, section head) + partially QMS module (formal NCs only)
Pain point 1: Recall traceability — when supplier X sends a bad batch, how fast can ASSB locate the affected units? If paper-based, days. If digital, minutes.
Pain point 2: Pareto accuracy — if defect logs are not unified, Pareto is wrong, root cause is wrong, CM is wrong, kaizen is wasted
Pain point 3: Per-unit COPQ — without per-unit digital record, you can't see which 20% of units are causing 80% of rework cost
Pain point 4: IATF 16949 audit — Q1 2027 re-cert, 42 open findings including 4 majors, several tied to traceability gaps (COMP-A theme already exists)
Pain point 5: Parent plant visibility — Toyota TMC wants daily/weekly defect metrics, currently they're manual reports from section head → HOD → plant manager → TMC, with 7-14 day lag

Background — Toyota's Existing Approach

Jidoka + Andon (the foundation)

Jidoka (自働化) = "autonomation" = automation with human judgment. Every worker can stop the line if a problem is spotted.
Andon (行灯) = visual signal (originally paper lantern, now digital). Worker pulls cord/presses button → overhead light + audio alert → production halts → team leader responds.
Andon alerts are timestamped, categorized (quality / equipment / material / safety), and the system tracks reaction time.
Digital Andon in modern plants: tablet button → SCADA/MES log → instant dashboard → "every alert now carries a timestamp, category, root cause, and reaction time"

Paper traveler (the legacy)

Traditional Toyota assembly = paper traveler / sho card rides with each vehicle from Station 1 to Final PI
Records: parts picked, torque values, inspection results, defects logged, rework
Problems: lost/damaged/faded, manual transcription errors, batch filing, hard to query
Toyota has been moving to electronic travelers since ~2010, accelerated 2020+ with COVID + digital push

Industry move: 100% paperless shopfloor

By 2024-2026, leading OEMs have digital travelers, electronic work instructions, electronic inspection sheets, electronic sign-offs
Industry 4.0 / Smart Factory = full digital thread from supplier to customer
Caliber, iBase-t, Tulip, Shoplogix, Siemens Opcenter, PTC ThingWorx all offer this

IATF 16949:2016 — Standards Anchor

Clause	Title	What it requires	How the system supports it
7.5.3.2	Documented information — control	Records must be controlled, retrievable, protected from loss, readable	Digital DB + retention policy + backup + read-only archive
8.5.2	Identification & traceability	Organization shall identify status of product with respect to monitoring and measurement requirements throughout production, and trace individual product to raw material / supplier batch when required	Per-unit digital record links to supplier batch via RFID/barcode scan, real-time status flag
8.7.1.2	Customer notification of nonconforming product	Organization shall notify customer when nonconforming product is detected after delivery	Defect DB → traceability query → affected unit list → customer notification in < 1 hour
9.1.1	Monitoring, measurement, analysis, evaluation	Determine what needs to be monitored, methods, when, when to analyze/evaluate	Report tabulation provides the "what" + "when" automatically
10.2.1	Nonconformity and corrective action	React to NC, evaluate need for action, implement action, review effectiveness, update risks	Defect DB + A3 module + 5-Whys template + CM tracker + 90-day effectiveness review

Global Benchmark — Vendor Landscape

Vendor / System	What it does	Strength
Tulip	No-code operator apps for defect reporting + nonconformance management	Easy to deploy, tablet UI, integrates with MES/ERP, GxP-ready
iBase-t	Paperless MES for aerospace / defense / industrial	Electronic signatures, complete as-built histories, closed-loop Mfg
Shoplogix	MES for automotive OEMs + suppliers	Real-time production visibility, traceability, frequent changeover support
Caliber Universal	Paperless shopfloor, work instructions, e-inspection	100% paperless methodology, industry 4.0 ready
Siemens Opcenter	Closed-loop quality + manufacturing	Enterprise scale, deep integration
Logicbus RFID + SCADA	Full traceability with RFID tags + SCADA	Per-component tracking, real-time monitoring, manual-station retrofit
Toyota in-house	Custom QMS modules integrated with production system	Toyota-specific, parent plant compatible, Andon-native

Key insight: Most vendors offer Pillar 2 (paperless traveler) + Pillar 1 (defect DB) bundled. Pillar 3 (report tabulation) usually built on top with BI tools (Power BI, Tableau). Toyota likely has in-house + vendor mix.

Real-world defect cost (why this matters)

BMW presentation: 22% of warranty costs due to electronics + ECUs. Of those, 77% = semiconductor failures. Of those, 48% = systematic fails. Source = assembly defects.
Industry: assembly defects = 12-15% of semi customer returns. Goal: 10 DPPM → 10 DPPB (defective parts per billion) — requires 100% inspection + traceability + closed-loop data
Takata recall: 67M vehicles (inadequate traceability meant every unit ever fitted with Takata inflator was suspect). GM: limited recall to 4 vehicles (full traceability knew which units were affected).
Vehicle recalls average $100M+ plus brand damage lasting years.

TBP Framing for the Project Paper

COMP-G — Plant-level Digital Quality Management System (dQMS)

Process/standard: IATF 16949:2016 clauses 7.5.3.2, 8.5.2, 8.7.1.2, 10.2.1 + ISO 9001:2015

Metric: % defects captured digitally (target 100%, current ~60% — paper tags still used for cosmetic) + % units with complete digital as-built record (target 100%, current ~70%)

Why now: IATF re-cert Q1 2027, 42 open findings, 4 majors; parent plant TMC wants daily defect metrics; PUSPAKOM Feb 2026 modernization needs upstream quality data

POO hypothesis: Station level — defect tag created on paper, transcribed to spreadsheet at end-of-shift, not in real-time DB

Root cause (suspected): QMS system (likely Toyota in-house) was built for formal NCs only, not for line-level defect capture; no tablet UI at station; paper traveler is the system of record by default

Difficulty: 4/5 (cross-system: MES + QMS + ERP + paperless traveler; culture change for operators)

PD-Interview: 5/5 (digital transformation + IATF + traceability + parent plant visibility + AI firm consulting anchor)

AI firm hook: "Built plant-level dQMS at ASSB; 100% digital defect capture, recall traceability 5 days→30 min, parent plant daily dashboard live, 60% reduction in IATF audit findings"

Cross-A3 leverage: COMP-G (this theme) + COMP-A (IATF findings) + COMP-C (Type Approval NC QP-007) — all touch digital record-keeping + QMS gates

Why this is the strongest paper theme

Three pillars in one theme — Defect DB + Paperless unit record + Report tabulation = full digital quality system. One A3, but it covers a lot of ground.
IATF anchor — re-cert Q1 2027 is a hard deadline. Tying the paper to a real regulatory event makes it not academic.
Toyota-specific — Jidoka + Andon + paper traveler are Toyota cultural elements. The paper can lean on Toyota's own language (Genchi Genbutsu, Kaizen, Yokoten).
Cross-A3 leverage — same QP-007 doc-control gate + same IATF finding pile as COMP-A and COP-A. One system closes multiple themes.
AI firm anchor — dQMS consulting is a real, billable service line for the AI firm launch 2027. "We help assembly plants go paperless and IATF-compliant in 12 months" is a sellable offer.

🪞 Reflection (v3.0 mandatory)

🤖 BotBot's self-evaluation

1. What worked in this research:

Re-aligned to plant-level scope after sir's correction — saved paper going off-track on JPJ licensing
3 pillars in one theme = coherent paper focus, not scattered
IATF clauses cited as standards anchor = paper is defensible, not opinion
Toyota context (Jidoka, Andon, paper traveler) + global paperless trend = paper is not generic

2. What I might be wrong about:

ASSB's actual current defect capture rate — I assumed 60%, real data needed
Whether ASSB uses Toyota in-house QMS or vendor (Siemens / Tulip / iBase-t) — need to verify
Whether paper traveler is fully or partially used today — likely hybrid
Parent plant TMC's actual data requirements — assumed daily metrics

3. What I need from you, sir:

Real data: % defects captured digitally vs paper, % units with full digital as-built, current IATF findings (the 4 majors especially), current QMS system used
Confirm scope: 3 pillars in one theme (COMP-G), or split into 3 separate themes
Confirm TBP integration: build the full A3 with v3.0 Kalyan strengthening, or just the research briefing for now

4. Patterns tracked (3× = MEMORY):

You re-scope topics on second pass — first pass research was off-target, you corrected. Count: 1× — watch.
You want plant-level / production-side scope, not licensing / regulator scope. Count: 1× — confirmed this turn, save as preference.
You like 3-pillar structure (defect + paperless + report) bundled as ONE theme. Count: 1× — watch.

5. MEMORY candidate (will save next turn):

🔵 Project paper topic (corrected 2026-06-15): Plant-level digital quality management — Defect Registration System + Paperless Individual Unit Record + Report Tabulation. NOT JPJ-level licensing (earlier VIS/VRC research was exploratory only). Anchor: IATF 16949:2016 clauses 7.5.3.2, 8.5.2, 8.7.1.2, 10.2.1. Toyota context: Jidoka + Andon + paper traveler.

Sources

Toyota Production System — Andon (Toyota UK Magazine), Jidoka (Toyota)
IATF 16949:2016 — clauses 7.5.3.2, 8.5.2, 8.5.2.1, 8.7.1.2, 9.1.1, 10.2.1 (Pretesh Biswas, Advisera, IAOB)
MES for automotive — Shoplogix (Jul 2025), Logicbus RFID/SCADA
Paperless shopfloor — iBase-t, Caliber Universal, Caliber Technologies
Defect tracking — Tulip non-conformance management, KnowledgeQ AI defect detection
Industry data — Semiconductor Engineering (zero-defect race), BMW 2017 AEC reliability workshop
Takata + GM recall contrast (Traceability ROI argument)
Logicbus Full Traceability in Automotive Manufacturing (RFID + SCADA)