Industry
Traceability for EV component manufacturing
EV programmes arrive with traceability written into the contract. Cell lots, module serials and busbar torque have to be recorded per unit from the first production part.
The situation this is for
Your OEM asks for a cell-lot-to-vehicle mapping for a containment action, and they want it in days. A batch record does not answer it; a per-unit genealogy does.
What gets captured
- Cell and module lotsEvery cell lot consumed, tied to the module it went into
- Busbar and terminal torquePer joint, where a bad joint becomes a thermal event
- Insulation and isolation testsMeasured values, limits, instrument
- Capacity and EOL testReadings retained, not just the verdict
- Serialised sub-assembliesModules carry their own genealogy into the pack
A route for this product
Routes are configuration, so this is a starting point rather than a fixed template. Yours is built from your operations at the walkthrough.
- 10 · Module identification — mark applied and read back
- 20 · Cell loading — cell lots scanned against the BOM
- 30 · Busbar welding or bolting — torque captured per joint
- 40 · Isolation test — measured value and verdict
- 50 · Capacity test — readings retained
- 60 · Pack assembly — module serials linked into the parent
Questions from this industry
We need multi-level genealogy: cell to module to pack. Is that supported?
Yes. A serialised sub-assembly carries its own complete history, and the parent inherits the tree. The trace page shows depth so you can see how far the record goes.
Our OEM requires data retention for years. Where does that data live?
On your own edge box, in PostgreSQL, partitioned by month. Retention is your configuration, and nothing is automatically dropped.
Talk about traceability for ev components
We walk one line, list what each operation should capture, and tell you plainly which of your machines can be read. You get that list whether or not you buy anything.
Keep reading
- Route configurationRoutes are validated graphs with parallel branches, optional operations, rework loops and eight gate types. All configuration, no custom code.
- Auto components and Tier 1/2Your OEM customer can ask for the build record of a single part number from eight months ago and expects it the same week. Trace keeps that record per unit, in a form that holds up when it is challenged.
- Pumps and valvesA pump that leaks in the field is traced back to one gasket lot or one under-torqued flange. Trace keeps the values that tell you which, per unit.
Not sure a full MES is the right answer? Read how to choose between MES and standalone traceability.