Device Data Model
Last updated on May 21, 2026
The TofuPilot Device Data Model makes every run traceable to a physical unit and the part, revision, batch, and sub-units that define it.
Part (e.g. PCB-V1)
└── Revision (e.g. Rev-B, defaults to A)
Batch (e.g. B-2026-04, optional)
Unit (serial_number, e.g. SN-001)
├── Part + Revision (+ optional Batch)
└── Sub-units (child serials: PCB, battery, enclosure, cable)Part
A part is the product or component family that units belong to.
Revision
A revision is a version of a part.
Unit
A unit is one physical unit under test, identified by a serial number. Each unit belongs to one part, one revision, and an optional batch.
Sub-unit
A sub-unit is a child unit assembled into a parent unit, such as a PCB inside a finished product. A parent unit can reference one or more sub-units.
Batch
A batch is an optional production cohort, grouping units produced in the same lot.
Schema reference
The full schema and endpoints for every entity are documented in the REST API reference.
Create a unit POST
Register a new unit by serial number.
Create a part POST
Register a new part.
Create a revision POST
Add a new revision to a part.
Create a batch POST
Register a production cohort.
Industry standards
The TofuPilot Device Data Model is built to be compatible with established industry standards, including PLM/ERP item masters, MES batch and genealogy records, and IPC-1782 traceability.
How is this guide?