Simulated data. Reflects the kind of event stream a UWB or BLE 5.x system produces in production.
Five things every tracking programme has to deliver.
1. Anchors & tags
Four UWB anchors at the corners. A battery-powered tag on the forklift. Together they triangulate position 5-20× per second.
2. Event stream
Raw events flow up to your application layer in an independent schema: MQTT, Kafka, REST. Replayable and durable.
3. Derived states
Dwell, transition, co-location, idle/active. Calculated from the raw stream and exposed as business events.
4. Heatmap analytics
Time-spent overlays show where your operation actually runs: the data that justifies layout changes and staffing decisions.
5. Integration
The events feed WMS, MES, EMR, ServiceNow, whatever operates the workflow. The location signal becomes a decision, not a dashboard.
6. Hardware-agnostic
This demo is shown with UWB. The same architecture works with BLE 5.x, Passive RFID, GPS, or SLAM. We pick the radio to fit the use case, not the other way around.
From a moving dot to a decision, automatically.
A position on its own is just an x, a y and a timestamp. An AI model trained on your live location stream turns it into something you can act on:
predicting congestion before it happens, flagging anomalies and safety events in real time, optimising routes and layout, and triggering actions in your WMS, MES or EMR.
Example model outputs on simulated data, in production the same layer runs on your real event stream.
Last updated: