ElectronIxTrace

Capability · for QA head, plant head, owner

A bad lot arrives. You need the unit list, not a project.

Forward trace answers the only question that matters during a containment: which units are affected, and which are provably clean. Trace answers it from an index, so the answer arrives while the customer is still on the phone.

Trace by component lot

Enter the lot code your supplier flagged. Trace returns every unit that consumed it, with the job card, the operation it was fitted at, the operator, and the dispatch date. Units that never touched the lot are proven clean, which is usually the more valuable half of the answer.

Trace by machine and time window

A torque gun drifts out of calibration and you only find out at the weekly check. Ask Trace which units that device measured between 14:00 and 16:00 on Tuesday. Most systems cannot ask this question at all, because they record that a part was scanned rather than which instrument produced the reading.

Indexed, not scanned

Genealogy stores serialised children and lot consumption in separate indexed columns rather than one JSON blob. That is a schema decision made specifically so the recall query stays a lookup as the table grows past ten million rows.

Containment window, not just a count

The result carries first and last build timestamps for the affected set, so you can bound the containment rather than quarantining a month of production to be safe.

Book a 20-minute line walkthrough

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.