某新能源充电设备企业 · Anonymised, no written authorisation
Charging equipment: one traceability line from SMT to the finished unit
Trace depth
Unit → board
Down to device parameters and debug logs
Complaint response
One screen
Scope same-batch units and export evidence
Device data
Auto capture
Aging / test data replace manual logging
Problem
SMT, DIP, assembly, burn-in and packing ran in separate shops, each with its own barcode rules. A finished unit could be traced to a batch at best — not to a specific board, machine or commissioning run. Equipment brands and protocols were mixed, and commissioning data was copied by hand, losing accuracy at the moment of transcription.
Approach
Unify barcode rules first — material, feeding, location and finished goods under one scheme, reviewed and then enforced plant-wide; scan verification at SMT feeding, work-order binding through DIP and assembly, first-off confirmation at critical operations; for burn-in, test and laser-marking equipment, confirm protocol and collection points one by one through a gateway so commissioning data lands in the database automatically; attach final inspection and dispatch to the same unit, keep 4M1E elements on the work order, and close exceptions by station.
Outcome
A unit serial number drills down to board batches, operations, equipment parameters and commissioning records; a customer complaint can be scoped and evidenced on one screen; equipment data is collected automatically instead of copied by hand. The structure comes from full-line delivery practice in new-energy charging equipment, covering SMT, DIP, assembly and burn-in test.
Can be interrogated
What if protocols differ?
Confirm protocol and collection points per equipment list; start with critical operations (feeding checks, burn-in, test) and defer the rest; scope goes into a signed requirement document, not a verbal promise.
How do batch and unit traceability coexist?
Boards are managed by batch, units by serial number; assembly creates the binding, so lookups walk the assembly tree up to board batches and down to key components.
Can legacy machines be connected?
Yes where a readable interface exists or a collection module can be added. Machines without interfaces use scan-based entry, flagged as manual data — never blended silently.
Why unify barcode rules first?
With per-shop rules, traceability breaks at the first cross-shop handover. Reviewing the rules before go-live is far cheaper than changing them afterwards.