What a closed shift leaves in the spatial record
When the live hall goes quiet at shift end, the plant still needs the place-and-time record of what just ran. A blank map at handover is not enough.
What the closed-shift spatial record is
Live asset tracking answers where tagged movers and material sit now. The closed-shift spatial record is what remains after those locations stop updating for that window: who moved where, how long assets sat, how far trucks drove empty versus loaded, and which events shared the same place and time. That package is the logistics form of a spatially oriented dataset under an operational digital twin, not a screenshot someone forgot to save and not a CSV of coordinates with no hall model.
Industry indoor-positioning practice treats retained trajectories the same way. Platforms keep weeks to about a year of positions so a late order, an audit, or a before-and-after layout check can still be opened. Medium-precision real-time location system (RTLS) history around 1–3 m (3–10 ft) is usually enough for aisle, buffer, and bay reconstructions. Sub-meter (~3 ft) matters when the question is exact floor position on a mark. Funding only the live screen, then purging history after a day, leaves the next review with nothing checkable on the hall.
What must be in the archive
A usable closed shift leaves continuous location samples for the tagged fleet on the same facility model used live. From those samples the plant can derive travel paths, dwell in named zones, loaded versus empty travel, and zone activity for the exact window under review. Classic lean manufacturing spaghetti diagrams and heat maps become outputs of that archive instead of a one-day clipboard study that may not match the shift that failed.
Object choice still shapes what the archive can answer. Mover paths without load tags will not show cage sit after drop. That decision is under tagging the mover vs tagging the material. Map trust still shapes whether anyone opens the replay. That decision is under the map that logistics will trust. Congestion and empty-share views that fill the same record are under congestion on shared aisles from the track and loaded vs empty travel you can prove.
Three equal readers of the same closed shift
Logistics reopens paths and fleet load to cut empty travel and unbalanced claims on the hall people already trust. That is the internal logistics and forklift tracking job after the icons have stopped. Continuous improvement reopens dwell and heat maps to challenge layout without waiting for the next scheduled floor walk. Analysts reopen place-time pairings for correlation and causality analytics when the same starve keeps following the same jam across many windows.
Those three jobs sit on equal footing: run and prove today's moves, keep the spatiotemporal replica under the live view, and learn across shifts. None of them is a side note to find-the-truck. A practical smart manufacturing program funds all three from the same position stream. How replay works when one event has already passed is under when the event has already passed. How today's material call should start that trail is under the call that starts the record.
What makes the record incomplete
Live icons alone are not a closed-shift record. A short retention window that expires before the next similar event also fails most logistics and safety reviews. Industry RTLS stacks commonly offer configurable retention measured in months, so weekly and monthly pattern work can still reopen samples when the plant keeps that window. A day of history trains nobody for that cycle.
Split tools recreate split truths. If logistics owns one map and continuous improvement owns a separate export, the next review returns to competing driver accounts instead of a shared hall window. A spreadsheet of coordinates without a playable timeline on the facility model is not historical replay. Access that only IT can run fails the same test plants already apply to process historians for machine trends.
How teams decide the record is complete enough
1. Reconstruct one finished shift window without calling drivers - If path, dwell, and loaded versus empty travel cannot be walked on the hall model, the shift did not leave a record.
2. Require path, dwell, and travel fields on finished moves - Live icons without retained samples are not enough.
3. Keep retention long enough for weekly and monthly reviews - Days are thin. Weeks to about a year match how audits and continuous-improvement cycles reopen the same pattern.
4. Give continuous improvement the same hall replay logistics uses - Pattern work waits on dense history in one shared place, not on another live widget or a separate export.
Stored hall history and live tracking sit under internal logistics optimization, production monitoring, and the features overview. Buying questions for retention also sit in ask about history, not the live RTLS map. How a rollout is priced is on pricing.
Get in touch if you want to walk whether your shifts already leave a spatial record, or only a quiet live map at handover.