Device lifecycle platform
Trax IoT Core
One record, from the order to the field.
Trax IoT Core is the platform TraxSmart runs its devices on. It captures the order, carries each unit through production, and stays with it afterwards: lifecycle, service, over-the-air updates and live status.
01 · Orders
The order is where the record starts.
Programme, quantity and configuration are captured together, so the line builds against a locked specification. Every unit that follows carries that order with it.
- 01Programme and quantityWhat is being built, and how many, recorded before the line starts.
- 02Configuration lockedFirmware, profiles and server settings decided with the order.
- 03Stock against the orderComponent requirement is visible before assembly begins.
Illustrative- OD-1842Axis ODM · configuration locked2,400
- OD-1843Nomad batch · standard build800
- OD-1846Sentry · AIS-140 programme1,200
- OD-1851Pulse OBD · server profile set640
Illustrative view
Unit ···4821Illustrative workflow
02 · Production
End to end, one unit at a time.
Trax IoT Core follows each device from component selection through assembly, flashing and test. The result of every stage stays on that unit.
- 01Batch on the unitThe components that went into a device stay traceable to it.
- 02Flash, then testFirmware version and test result are written to the record before packing.
- 03Ready to leaveA packed unit already knows which order and configuration it belongs to.
03 · Device lifecycle
The same identity, from the bench outward.
Order, build, dispatch and field life stay on one device record. When the unit is updated or serviced later, that history is already there.
- 01Provisioned on the way outFirmware, profile and server settings applied, and dispatch logged against the order.
- 02Known in the fieldWhat the unit is, and how it was built, readable once it is reporting.
- 03History that staysA later site, owner or ticket still points at the same device.
IMEI ···4821- OrderOD-1842 · configuration locked
- ComponentsBatch traced to this unit
- ProductionFlashed and tested · pass
- DispatchServer profile applied · shipped
- FieldOnline · reporting
- ServiceTicket closed · history kept
Illustrative record
SVC-309- Open
- Diagnose
- Repair
- Closed
Illustrative ticket
04 · Service
Service work, kept on the device.
Tickets, warranty and repair sit on the unit they belong to. A return in the field can be read against how that device was built, configured and shipped.
- 01Opened on a unitA ticket starts from the device, not from a separate list.
- 02Warranty in viewCover is read from the same record as the order and the build.
- 03Closed, still attachedRepair and replacement remain on the device after the ticket ends.
05 · OTA and FOTA
Firmware and settings, sent over the air.
- 01FOTAA firmware release, sent to the units that should receive it.
- 02OTAConfiguration pushed without opening the device or visiting the site.
- 03Visible progressQueued, in progress and complete, on the device the release was sent to.
FOTA delivers firmware. OTA delivers configuration: server, reporting profile, how the device behaves. Each unit shows whether the release is queued, sending or complete.
Estate- OnlineReporting
- UpdatingFOTA in progress
- SilentNot reporting
Illustrative estate
06 · Device status
Which units are reporting, and which have gone quiet.
Live state sits on the same record that began with the order. A silent unit can be identified as a specific build, configuration and shipment.
- 01ReportingOnline units, seen against the firmware they are running.
- 02In an updateDevices currently taking a firmware or configuration release.
- 03SilentUnits that have stopped reporting, flagged on their own record.
Device lifecycle platform
Trax IoT Core
Run the device on the system that built it.
Orders, production, lifecycle, service, OTA, FOTA and status, on one platform. Tell us about the programme and we will walk through it on your own devices.