| 1 | Set an accuracy target | Tag, anchor, and software performance in the intended environment | UWB systems can achieve decimeter-level positioning under suitable conditions, but actual results depend on anchor geometry, calibration, obstructions, multipath, and the positioning method. Test in the real site before committing to a specification. | What accuracy is measured at the 50th and 95th percentiles, and how was it tested? |
| 2 | Match tags to the use case | Wearable, asset-mounted, vehicle-mounted, or fixed tags; size, enclosure, battery, and mounting | More frequent position updates generally increase energy use. Check whether the tag supports the required update rate, charging or battery-replacement process, and environmental protection for its mounting location. | What are the expected battery-life assumptions, update rates, and operating-temperature limits? |
| 3 | Check radio and regional compliance | Supported UWB frequency channels, transmit-power limits, and market approvals | UWB spectrum rules and device approval requirements vary by country or region. Confirm that the equipment variant and configuration are permitted in every country where it will be deployed. | Which frequency ranges and channels are supported, and what local certifications are available? |
| 4 | Plan anchor placement | Anchor count, spacing, height, geometry, and line of sight | Positioning typically benefits from anchors distributed around the coverage area rather than clustered in one location. Walls, metal racks, machinery, and people can obstruct or reflect radio signals; conduct a site survey and validate coverage on site. | What placement rules, site-survey tools, and commissioning checks are provided? |
| 5 | Compare anchor installation needs | Power options, network connectivity, mounting, synchronization, and service access | Anchors may use wired power and Ethernet, or other supported power and backhaul options. Wired infrastructure can simplify continuous operation, while less cabling may reduce installation work but introduce battery, coverage, or maintenance considerations. | Do anchors require wired synchronization, and what happens if network connectivity is lost? |
| 6 | Understand the gateway’s role | Tag-to-anchor communication, data aggregation, backhaul, buffering, and edge processing | System architectures differ: gateways may forward data, connect site equipment to a server, or provide local processing. Confirm whether gateways are required, how many are needed, and whether positioning continues during an internet outage. | Which functions run locally, and how are data buffered and recovered after an outage? |
| 7 | Evaluate positioning and platform software | Real-time location, maps, zones, alerts, history, user roles, and APIs | Check whether the platform supports your floor plans, coordinate systems, reporting needs, and integration workflow. Confirm available APIs, data formats, retention controls, and whether software can be hosted on premises or in the cloud. | Can we access location data through documented APIs, and what are the hosting and retention options? |
| 8 | Test capacity and update rate | Concurrent tags, update frequency, message handling, and latency under load | Performance with a small test group may not predict performance at full scale. Pilot the expected number of active tags and peak update rates, including busy shifts and overlapping coverage areas. | What is the tested capacity per area, and how does latency change at peak load? |
| 9 | Review security and data governance | Device authentication, encryption, access control, updates, and location-data handling | Location data can be sensitive. Review how devices and users are authenticated, how data is protected in transit and at rest, how software updates are delivered, and how access and retention are managed. | Which security controls are supported, and where is location data stored and processed? |
| 10 | Compare total deployment cost and support | Tags, anchors, gateways, licenses, installation, calibration, maintenance, and support | Hardware price alone does not represent total cost. Include cabling, mounting, commissioning, software subscriptions, battery replacement, spare units, training, and support coverage across deployment regions. | What costs recur annually, what support is available locally, and how are replacements handled? |