Historical Replay
Historical replay is the ability to open stored location records on the same facility model used for live tracking, then step through time as if the shift were still running. Tagged forklifts, people, and materials appear on the hall layout at the moments they actually occupied. The live map answers where assets are now. Replay answers where they were when an order shipped late, a near-miss was reported, or a buffer jammed after the fact.
Most RTLS demos sell the live dots. By mid-morning nobody is watching that screen. The money sits in yesterday: the truck that waited at a crossing, the pallet that sat at line end with no owner, the half of the fleet that drove empty. Those patterns only show when positions are retained long enough and the UI lets operations open them without a data export. The floor case is in ask about history, not the live RTLS map.
Replay is not a separate analytics product bolted on later. It is the same position stream that fed the live twin, kept as a continuous archive and played back inside the spatial context operators already recognize. Without that archive, the plant bought a nice screen.
Key Components
Retained position history: Continuous location samples for tagged assets over weeks or months, not a rolling day or a weekly purge.
Time and asset selection: Pick a window (one order, one truck, one shift) and the tags that matter for that question.
Playback on the twin: The same 2D or 3D hall model as live tracking, with the clock set to the past.
Derived views: Spaghetti, area occurrence, dwell, and fleet saturation computed from the same archive.
Operator access: Shift leads open replay themselves. A CSV dump that only IT can interpret is not replay.
Applications in Manufacturing and Logistics
Logistics supervisors reconstruct late shipments and missed pickups by walking the path on the twin. Continuous improvement uses multi-day replay to compare routes before and after a layout change. Safety and quality open the minutes around an incident when the live map has already moved on. That after-the-fact job is why plants keep history, and why when the event has already passed matters more than another live dashboard.
Empty-round and saturation reviews also depend on replay. A live glance never shows that half the fleet looped empty while two trucks carried every call. Path history does. That feeds internal logistics optimization with evidence the floor can act on: move a crossing, assign a handover owner, rebalance trucks.
Benefits and Challenges
The benefit is a fixable record. Memory fades. Radio notes stay incomplete. Replay keeps the sequence visible in the spatial layout people already trust. Teams return to the same window later when a similar failure appears.
The challenge is retention length and access. 'We keep a week' or 'export a CSV' fails the shift-lead test. Storage and privacy rules must match how long audits and kaizen cycles actually need. Playback that only runs in a vendor office or an IT sandbox never reaches the people who change the floor.
Related Terms
RTLS produces the live positions. Area occurrence and dwell summarize zone use from the archive. Spaghetti diagrams draw the paths. A process historian stores time-series machine data. Historical replay is the spatial equivalent for tagged movers on the twin.
Frequently Asked Questions
Is replay the same as live tracking? No. Live tracking is the current positions. Replay opens retained positions from a past window on the same map.
How long should history be kept? Long enough that a late order, an audit, or a layout before-and-after can still be opened. Days are not enough for most plants. Weeks to a year is the useful range for logistics and safety reviews.
Is a CSV export enough? No. A spreadsheet of coordinates without the hall model and a playable timeline is not something a shift lead uses at the end of a bad day.
Who should be able to open it? The same people who already use the twin for logistics: shift leads and supervisors, without a ticket to IT for every reconstruction.