Automotive.
A recalled component is only as reachable as the handoffs it survived. visibility.cloud is built to record custody at every joint from the tier-N supplier to the assembly line, at the serial, so a field action reaches the exact parts and not the whole build year.
The field action reached a build year because the record could not reach the part.
Tier-N depth is where this bites in automotive: the harness was scanned at three plants, and no scan says who observed it. A corrective action scoped to the exact serials needs a record that names the observer at every joint — not a purchase-order inference across four suppliers' systems.
The automotive chain is deep and it is where the diverted or counterfeit part does its damage. Each casting, module and harness is its own identity with its own custody; the spine records who held it and where it was read at every seam, so provenance is a query and not a reconstruction.
Conforms to EPCIS 2.0 and CBV 2.0, so the events a tier supplier captures and the events the assembler captures describe the same handoff in the same vocabulary.
The envelope, at the tier-2 line: a harness commissioned at the serial.
{ "bizStep": "commissioning", "epcList": ["urn:epc:id:sgtin:0614141.200114.8412"], "eventTime": "2026-07-30T06:12:04Z", "recordTime": "(stamped by the gateway — the sender cannot set it)", "who": { "kind": "human", "role": "line QA, tier-2 plant", "grade": "attested" }, "capturedBy": "(tier-2 supplier account — the warrantor account whose key opened the door)", "party": "(derived at read time from grant chains — never stamped)" }
See your first trace.
Capture workspaces for manufacturers and brands are provisioned from the seat list — we write when your seat is ready.