With known prerequisites, we can propose a practical pilot directly. Otherwise, we clarify only what is needed to choose the right approach. We agree the scope, installation, connection, test and follow-up to suit your need.
Relevant modules to explore
Flows & capacityMeasurement & monitoringAnalysis & decision support
Where does waiting happen between work steps? When work pauses between stations, it is not always clear where waiting happens or how often it recurs.
Information for the task
Events to explore
Beacons and zone events
Batch and material identity
Waiting time
Work in progress (WIP)
Time between stations
Beacons to support flow visibility
Beacons on batch carriers, boxes and trolleys can link materials to indoor zones and stations where GPS is insufficient. Automatic zone events can reduce manual recording and inform analysis of waiting times, work in progress and bottlenecks. We are evaluating RTLS technology for Factory Flow: RTLS technology under evaluation is not a verified customer installation. Beacon presence does not by itself establish an exact position.
Who and when
A real operational decision
Production leads and improvement teams when waiting between steps recurs but the cause is unclear.
First assignment
Test zone events in a limited pilot
Choose one handover, a small number of zones and the material carriers to follow. A limited pilot can test beacons with compatible receivers and compare zone events with the team’s manual observations. Technology, placement, coverage, detection reliability and required accuracy are verified in the actual factory environment. Machine signals can complement the setup where the interface is known.
Prerequisites to verify
Check before committing
Define zones, material identity and the meaning of each event. Beacons need compatible receivers and verified placement; metal, obstructions and radio conditions can affect readings. Agree acceptable timing and zone errors before testing.
Tangible output
What you take away
A documented timeline for selected material journeys, verified zone events where the test succeeds, and a priority work step to review. Coverage, latency, false and missed events, and uncertain accuracy are reported even when the test does not meet its targets.
Your next decision
Choose where to investigate the flow
Use a verified timeline to decide where the flow needs investigation, not as automatic root-cause analysis or individual employee monitoring. Entering a zone does not by itself mean processing has started. The existing Factory Flow demo uses simulated data; it does not prove connected RTLS or a measured productivity improvement.
Follow-up
Check usefulness before expanding.
Review an agreed sequence of events with the team. Confirm manually before changing workflow or claiming an effect.
Planned development
AI support for this need
We can explore whether AI could help identify recurring waits and unusual sequences in the parts of the workflow that can be tracked.
These are ideas to explore together, not functions already implemented or physically verified in QuickIoT.
Practical reading
Factory Flow
Beacons, zonhändelser och väntan i produktionen
Utforska hur beacons kan koppla material till zoner och ge underlag för väntetider och överlämningar. RTLS-tekniken utvärderas; underlaget innehåller ett illustrativt exempel och arbetsblad för en avgränsad pilot.
For Produktionsledare · Operatörer · Förbättringsansvariga9 sections in this paper