Right Coordinates, Wrong Floor? Validating Multi-Floor RTLS
2026-10-19
The cart appears at the east end of the warehouse. An operator reaches that spot and finds the cart one floor above. In a building with similar floor plans, a plausible horizontal position is not a complete operating address.
Multi-floor tracking needs a defined basis for floor identification. Assigning floor names to maps and receivers does not prove that every movement will be classified correctly. Validate the selected technology against the actual building.
1. Define a building–floor–zone address
When two floors share a staging-area name, the zone label alone is ambiguous. Distinguish building, floor and zone identifiers. Keep map versions and operational names consistent with the register.
Record local coordinate references where floors differ. Aligning the drawing and identifying the floor are separate tasks. A correctly scaled floor plan does not validate the classification of observations from another level.
2. Decide which spatial result the task needs
Locating a cart may primarily require a reliable floor and zone. Detailed movement analysis may call for a more precise positioning configuration. Choose around the task rather than assuming the same installation suits every building.
ORBRO indoor tracking uses different configurations for different needs. Treat floor identification, horizontal position and upper-versus-lower rack placement as separate requirements. Precision in one dimension does not automatically establish performance in another.
3. Record physical ground truth
During the test, separately record the actual building, floor, zone and observation time. Compare them with the system result. Include vertically aligned test points, areas near stairs and freight-elevator approaches where relevant.
For a US facility with a mezzanine and an upper storage floor, select routes from its real material flow. This is a conditional test scenario, not an assumption about all American warehouses. Use authorized paths and representative loaded conditions.
4. Handle elevator transitions explicitly
Reception conditions can change inside the elevator and as its doors close. Check the observation immediately before boarding and after leaving. Distinguish the interval in which the floor is unconfirmed. Continuing to display the last floor as current can mislead the receiving operator.
Define the evidence needed to confirm the destination floor. If repeated observations or additional data are proposed, verify support and measure the resulting delay. An elevator call record alone does not establish that a particular cart boarded.
5. Separate wrong-floor results from unconfirmed results
Review observations assigned to the wrong floor separately from those lacking a confirmed floor. Forcing every observation into a floor can hide uncertainty while increasing wrong assignments. Consider an understandable unconfirmed state.
Review direction of travel, delay after leaving the elevator and repeated problems under particular loads. Preserve the total trial population and conditions. Do not improve an apparent success rate by excluding the uncertain intervals.
6. Verify the operator's complete search
Ask the next operator to find the cart using the building, floor and zone. Include the last observation time and any gap. Keep location confirmation distinct from physical handover.
Recheck plans, zone names and routes after a layout change. Bring floor plans, transfer routes, required spatial detail and examples of misclassification to ORBRO to define separate acceptance checks for the map and the floor decision.
Recommended Blogs
Returned but Not Ready: Tracking Returnable Container Recovery
2026-10-16
Replacing an RTLS Tag Without Losing the Asset's History
2026-10-15
Is That Location Still Current? Checking RTLS Data Freshness
2026-10-14
AI-generated illustration of the selected local environment; not a photograph of a customer site.
2026-10-13