Loaded vs empty travel you can prove
Loaded versus empty travel is a measured split of mover distance and time. Closed bookings and engine hours cannot prove that split on their own.
What the split means in plant language
Empty travel is motion with no productive load. Loaded travel is motion while the truck carries a task load. Idle time is standing still. Those three states answer different questions. Lean manufacturing already treats empty runs as transportation muda. The plant question is not whether empty travel exists. It is whether last month's empty kilometres (miles) and empty minutes are a number ops can fund against, or still a feeling next to a high utilization figure on the fleet report.
Proof needs two facts on the same clock: continuous place of the mover, and a load or task label that says whether that segment was productive. Without both, internal logistics and industrial fleet management keep debating busy trucks that still burn empty distance between stamps. Measured empty share is a practical smart manufacturing input only when it comes from paths and labels, not from confirmations alone.
Why bookings and engine hours cannot settle the share
A closed WMS task, ERP transport order confirmation, or radio job proves ownership changed or a drop finished. It does not measure how far the truck drove without a load before pickup or after drop. Industry activity-tracking practice draws the same line: transaction systems describe work stages, movement data describes usage, and a location trace alone still cannot confirm whether forks carried goods unless a load or task signal is present.
Engine hours and ignition-on time count motion or power. They do not label empty versus loaded. Motion-based utilization can look healthy while empty repositioning dominates travel distance. Plants that split empty and loaded legs on real paths often find empty distance is a large share of total travel even when move counts still look busy. Plants that argue empty share from confirmations alone are reading bookings, not paths.
What continuous track must add
Forklift tracking and broader asset tracking close the gap when movers carry continuous real-time location system (RTLS) location, typically at medium precision around 1–3 m (3–10 ft) for aisle and buffer work. While a task is open, or across a shift window, the platform stores route, travel time, and distance. Loaded segments need task acceptance, a weight or fork-load signal, or another agreed load state. Empty segments are the motion without that signal. Coarse wing presence is too blunt for empty-share percentage. Accuracy language for that choice is under zone presence vs medium-precision logistics track.
Proof on the hall is a path overlay people recognize, not a single utilization number. Spaghetti diagrams and heat maps show where empty loops cluster between dock, supermarket, and line faces. twinzo keeps those paths in the spatially oriented dataset under the live map so three jobs stay equal: live empty-share cuts for the shift, the stored place-and-time record for later review, and correlation and causality analytics on which empty corridors keep preceding waits. Path impact framing sits under real travel paths on the floor. Congestion fed by those loops is under congestion on shared aisles from the track. What the closed shift should retain is under what a closed shift leaves in the spatial record.
Event-driven AOS (commonly known as FGS) on tracked trucks strengthens the label: acceptance binds a job to a mover, so the path during the open work order is easier to call loaded. Classic ERP guidance without localization still optimizes assignment against assumed distances. That comparison is under AOS on tracked forklifts vs SAP-state forklift guidance. Free-truck claim that prevents some empty searches sits under where the free forklift actually is.
Limits that stay honest
Mover-only tags cannot see a cage that sits after drop. They can still measure empty truck motion. Inferring load without task acceptance or a weight signal will mislabel some hops, including short empty repositioning that looks loaded if the previous job was never closed. Choose medium-precision continuous track if empty kilometres (miles) are the decision you will fund against. Coarse wing presence can support crude utilization by building. It cannot support an honest empty-share percentage by aisle.
Object choice when you also need load sit after drop is under tagging the mover vs tagging the material. How empty travel shows up as non-value-added work is under pinpointing non-value-added travel on the floor.
How teams decide empty share is measured
1. Ask for last month's empty kilometres (miles) as a number, not a feeling - If the room debates the figure, you have bookings without paths.
2. Require path history on the same hall as open jobs - Separate telematics spreadsheets recreate the same unproven empty-share argument.
3. Bind load state to acceptance or a load signal - Motion alone is not empty-share proof.
4. Review one repeating empty cluster for two weeks - If layout or material call-off changes do not move it, the label or coverage is wrong.
Measured travel and fleet load sit under internal logistics optimization, with depth on the features overview and ordering on material order automation. Production waits on the same hall are under production monitoring. Pricing is under pricing.
Get in touch if you want to walk whether your empty travel is already a measured path, or still a shift argument.