Unknown processes on the live floor
The process map still shows a clean dock-to-line path. On the floor a forklift leaves its lane twice an hour to lift a maintenance tech to a mezzanine light, then loops the long way because Dock 4's door sticks open. None of that work sits in the engineer's standard time.
What unknown processes are on site
Unknown processes are recurring physical work that never made it into the designed flow. Process engineers draw the planned route: receive, put away, kit, return empties. The live hall keeps inventing side jobs. A boom lift is booked out, so logistics becomes the height crew. A pedestrian door fails, so every truck takes a 120 m (about 400 ft) detour. A supplier drops off-spec packaging that needs an extra restack nobody owns on the value stream map.
These moves are not one-off noise. They become habits. Drivers absorb them because saying no delays production. Engineers never cost them because a clipboard gemba walk on a calm Tuesday does not catch the night pattern. The plant then underestimates true logistics load and overestimates how much spare capacity exists for the next volume ramp.
Why designed flows miss the side jobs
MES and WMS record the steps they own. They do not record a forklift that spent twelve minutes holding a person at height, or the empty loop caused by a broken door. Radio chatter treats those minutes as “helping out.” By month end the hours are gone and nobody can say whether the plant should keep absorbing the work or buy a dedicated scissor lift, fix the door, or redesign the path.
IT-side process mining can expose deviations in system event logs. It still misses physical work that never creates a transaction. Height assists and detours live between scans. Without continuous location, the side process stays folklore.
How 24/7 location monitoring flags the unexpected
A real-time location system (RTLS) watches tagged movers around the clock. Twinzo analytics compares live paths to the corridors and zones the plant expects. Unexpected stops in a maintenance bay, repeated climbs to a mezzanine edge, or a new detour around a failed door show up as movement that does not match the standard route. Spaghetti paths and a logistics heat map make the habit visible across shifts, not only during a daytime walk. Dwell at odd spots flags trucks that are “busy” without a WMS move.
That is continuous monitoring on the same stack used for internal logistics optimization. Alerts can fire when a tagged vehicle enters a zone that should be rare for logistics, or when travel time on a lane jumps after a door fault. The point is not to punish drivers. It is to name the hidden process so engineering and maintenance can own the fix. The location concept sits under what RTLS is.
How teams turn flagged movement into a cost decision
1. Label the pattern - Height assist, door detour, off-spec restack, ad-hoc tow for a broken tugger. If it has no name, it cannot enter a budget talk.
2. Measure frequency and duration - How many times per week, how many minutes per event, which shifts. Two weeks of continuous location beats one anecdote from the loudest supervisor.
3. Convert minutes into money - Driver time, delayed kits, extra empty travel meters (feet), and any overtime the side job pulls into peak hours. That becomes a simple KPI: cost per unknown process per month.
4. Choose absorb versus invest - Rare and cheap: absorb and keep watching. Frequent and expensive: invest in dedicated equipment, a door repair, a permanent access platform, or a process redesign. The total cost of ownership of a scissor lift is easier to defend when the forklift-as-lift habit already has a price tag.
What the decision looks like in practice
A typical moment: for three weeks the map shows the same two trucks leaving the main aisle to the packing mezzanine about fifteen times a night, each stop eight to ten minutes. No WMS task exists. Maintenance confirms they borrow logistics for lamp and sensor work at height. The monthly cost lands above the lease of a small lift dedicated to that crew. The plant buys the lift, returns the forklifts to material moves, and the unexpected mezzanine dwell disappears from the heat map.
Another pattern is infrastructure. A dock door sticks for ten days. Spaghetti shows every outbound truck looping an extra 120 m (about 400 ft). The repair ticket was “nice to have.” After the detour cost is totaled, the door jumps the maintenance queue because logistics was silently paying for it on every shift.
That is the use case: find the processes engineers did not count on, cost them exactly enough to choose absorb or invest, then verify the fix on the same live digital twin. Sibling staffing and fleet views live under shift balancing with RTLS and balancing forklift fleet saturation. A longer logistics analysis path is in logistics analysis with a digital twin. For when continuous location pays versus when a walk is enough, see when RTLS helps, and when it does not.
Name the side job before it becomes capacity fiction
If the standard flow looks clean while drivers keep disappearing into work nobody planned, run continuous monitoring until the hidden patterns have a cost. Then absorb the rare ones and fund the expensive ones. Get in touch if you want to walk the same unexpected-movement picture on your own facility model.