Unit Explorer

Last updated on May 21, 2026

The Unit Explorer is the entry point into every Unit you have ever produced. Filter by part number, revision, batch, status, or any unit-metadata key; open a row to see the unit's lifetime: every run, every attempt, every measurement.

Open it from Inventory → Units.

Columns

The default columns cover the core unit record. You can hide, reorder, and add columns from the Columns menu in the toolbar.

ColumnPurpose
Serial numberUnique identifier. Click to open the unit detail page.
PartPart number and short name.
RevisionHardware revision the unit was produced against.
BatchProduction batch the unit belongs to.
StatusLatest run outcome, with attempt count when retested.
Last runTimestamp of the most recent run on the unit.
SampleGolden, Failing, or empty for production units.
TagsFree-form labels attached to the unit.

Filters

The filter bar combines structured filters with free-text search across serial numbers, part numbers, and metadata values.

  • Part number and revision. Compare units across redesigns.
  • Batch. Slice a single production cohort.
  • Status. Filter to passing, failing, or never-tested units.
  • Sample type. Include or exclude golden and failing reference samples.
  • Date range. Filter by first run, last run, or unit creation date.
  • Unit metadata. Any key-value pair you attach to units at creation or via the API.

Metadata

Every unit carries a free-form metadata object you can write at creation through the SDK, the REST API, or the CLI. Keys are filterable in the toolbar, exportable as columns, and matchable in workflow triggers. See Unit metadata for the schema.

Saved views

Save a filter combination as a view so the next time you open the explorer it lands on the right slice. Views live at the organization level, so anyone on your team can open the same slice from the Views menu.

Export

The Export button writes the current unit set to a file. Pick the rows and the format from the dropdown.

  • CSV. Flat, one row per unit, with columns for serial number, part, revision, batch, status, last run, sample type, and metadata.
  • JSON. Nested, one object per unit with the same fields plus the raw record.
  • Visible vs selected. Export every visible row, or check rows in the table and export only the selection.
  • Filename. tofupilot-units-<timestamp>.<ext> so multiple exports stay distinct.

Exports honor team scope and role permissions, so you only export the rows you can see in the table.

Permissions

The Unit Explorer respects the dashboard access model:

RoleWhat they see
Owner, Admin, DeveloperEvery unit in the organization.
ViewerUnits tested on stations within their team scope.
OperatorNo access.

See also

How is this guide?

On this page