The everyday multi-site search lag
A company running plants and warehouses on several continents still spends real time on a basic question: where is this pallet, fixture or tool right now? Someone opens the WMS, another person calls the site, a third walks the floor. At scale the lag multiplies. Location-based services built on RTLS cut that chain by putting every tagged asset on a live map that spans sites.
The same positioning layer used for other purposes works here as a search tool. Tags on materials or equipment report position through BLE or UWB. An operator types an ID and sees first the correct facility, then the aisle or zone inside it.
Indoor navigation as search, not safety theatre
Most conversations about RTLS start with personnel safety. This use case is different. It treats the live position stream as a way to answer location queries across a network of facilities. Accuracy sits in the range the technologies actually deliver: BLE typically 1-3 meters, UWB under 30 cm when the environment supports it. That is enough to walk someone to the right bay instead of sending them on a hunt.
The platform stores historical positions and can replay them. If an asset moved overnight or sat in the wrong zone for a shift, the path is still there. Heat maps and spaghetti diagrams from past movement show whether certain materials keep drifting away from their assigned storage.
One view that works across every site
The system is built multi-tenant and multi-site. A single login can switch from one facility model to another. Search for a material lot and the first result is the site that currently holds it; the next click zooms into the local 3D layout. Fixed sensors or readers go into each building, tags go on the assets, and the positions stream into the shared map.
3D models come from the usual industrial sources—layout drawings, simplified BIM, or meshed scans. The limit on model size keeps the client usable on ordinary devices. Once the models are in place, the same search works whether the asset sits in a European plant or an Asian warehouse.
What has to stay connected
RTLS data lands next to the systems already running the operation. APIs pull or push location into the existing WMS or ERP so the search result appears beside order status or inventory records. Nothing replaces those systems. Positions update on the order of seconds, which is frequent enough for search and slow enough for battery life on most tags.
A short pilot usually runs in a few weeks. Full multi-site rollout typically takes one to three months, depending on the number of buildings and the tagging plan. Battery life on BLE tags often stretches to years; UWB tags need more frequent attention. The deployment plan covers network layout and calibration so the accuracy numbers stay real on the floor.
Making the map part of the daily question
Once the positions are live, the map answers the location question before the phone call starts. Filters by zone, last-seen time or material type keep the view usable. Historical replay shows how an asset actually moved, not how the process said it should move. The value is simple: fewer empty walks, fewer inter-site calls, and a clearer picture of where materials actually live across the network of facilities.