“Indoor positioning standard” can refer to several different layers: a model of spaces and routes, a radio ranging method, an exchange format, a device ecosystem or accessibility criteria. Procurement fails when these layers are treated as interchangeable.
Separate spatial data, ranging and user-interface standards
Indoor positioning standards are formalised specifications that dictate how hardware devices measure distance, exchange data packets, and report location to a receiving application. For operational managers and integrators, these standards represent a shift away from proprietary, single-vendor silos towards interoperable systems where beacons, tags, and receivers from different manufacturers can coexist in the same physical space.
Several bodies drive this work. The Bluetooth Special Interest Group (SIG) defines how Bluetooth Low Energy (BLE) devices broadcast and measure range, including newer precision ranging capabilities. The Institute of Electrical and Electronics Engineers (IEEE) oversees standards such as 802.15.4z, which underpins Ultra-Wideband (UWB) secure ranging. The Wi-Fi Alliance manages standards like Fine Timing Measurement (FTM), which allows compatible access points to calculate distance. Meanwhile, industry groups like the InLocation Alliance publish usage guidelines to encourage practical adoption.
It is vital to distinguish between a ratified standard, a draft specification, and a de facto standard. A proprietary format like Apple’s iBeacon functions as a de facto standard because of its market adoption, but it is not an open, multi-vendor standard in the way that the Eddystone protocol or IEEE 802.15.4z is. When evaluating an "emerging standard," the first question is whether the specification is finalised or still in draft, as draft hardware often requires firmware updates once the standard is officially ratified.
Standards do not guarantee accuracy. They define the rules of communication and the mathematical models for ranging, but the physical environment—walls, racking, human bodies, and competing radio signals—still dictates the actual performance. A standardised protocol will suffer from multipath interference in a listed building just as readily as a proprietary one.
IndoorGML and interoperable navigation models
For UK venues, the practical value of emerging standards lies in procurement flexibility and long-term maintenance. If a retail chain deploys a fleet of BLE beacons, standardised advertising packets mean the venue is not locked into one manufacturer’s backend or mobile SDK. If a supplier discontinues a product line or alters its pricing, standard-compliant hardware from an alternative vendor can be introduced without ripping out the existing infrastructure.
Multi-vendor asset tracking
In large venues such as exhibition centres or hospitals, operational teams often track high-value movable assets. Using UWB hardware built on the IEEE 802.15.4z standard allows an integrator to source location anchors from one supplier and asset tags from another, provided both adhere strictly to the same profile. This reduces supply chain risk and can lower hardware costs through competitive procurement.
Accessibility wayfinding in museums
Museums evaluating indoor navigation for visually impaired visitors often look at BLE or UWB standards. A standardised protocol ensures that a visitor’s smartphone can interpret ranging data consistently, regardless of which manufacturer’s beacon is mounted above a specific exhibit. However, the standard only handles the signalling. The venue must still invest in precise physical mapping, calibration, and ongoing maintenance of the beacon inventory to make the wayfinding reliable.
Interoperability in mixed-use spaces
Shopping centres or transport hubs frequently host multiple tenants, each with their own operational technology. Emerging standards aim to prevent radio spectrum conflicts by defining how devices share the 2.4 GHz or UWB bands. In practice, this means a facility manager can run a centre-wide wayfinding system alongside individual retailer proximity marketing beacons, provided all parties configure their transmit power and advertising intervals according to agreed technical profiles.
Build an interoperability test around the real service
The most frequent mistake is equating "standards-compliant" with "plug-and-play." Even when two devices perfectly implement the same Bluetooth or UWB standard, their real-world performance will vary based on antenna design, casing material, and the physical layout of the building. Compliance ensures they can communicate; it does not ensure they will produce identical distance measurements in a cluttered environment.
Assuming backward compatibility
Newer standards often require newer smartphone chipsets or operating system versions. Deploying a network based on a recent BLE or Wi-Fi ranging standard may mean that a significant portion of visitor devices cannot interact with the infrastructure until those users upgrade their phones. Any business case built on an emerging standard must account for this hardware lag.
Ignoring firmware dependency
Hardware purchased today might be marketed as compliant with an emerging standard, but if that standard is not yet fully ratified, the device might ship with draft firmware. When the final specification is published, a firmware update will be required. Operational managers must verify the manufacturer’s process for pushing these updates and whether it requires physical access to the deployed hardware or can be done over-the-air.
Overlooking the calibration requirement
Standards define how a signal is measured, but they do not eliminate the need for on-site calibration. RSSI-based systems still require manual tuning to account for local RF attenuation. Even phase-based or time-of-flight systems benefit from baseline measurements to verify that the installed anchors are performing to specification.
Key checks for suppliers and integrators
- Specification status: Ask whether the hardware complies with a finalised standard or a working draft. Request the exact version number.
- Interoperability testing: Ask for documented evidence that the hardware has been tested with devices from at least one other manufacturer using the same standard.
- Update mechanism: Determine how firmware updates for the standard are delivered, how often they are expected, and who bears the operational cost of applying them.
- Device support: Request data on the current percentage of consumer smartphones in the UK market that support the specific standard’s hardware requirements.
- Privacy alignment: Confirm that the standard’s data exchange mechanisms can be configured to comply with UK GDPR requirements regarding data minimisation and consent, rather than relying on default behaviours that may collect unnecessary identifiers.
Emerging standards offer a clearer path toward sustainable, multi-vendor indoor positioning, but they remain tools that require rigorous site-specific testing. Treat a standard as a baseline for interoperability, not a substitute for a physical pilot.
Interoperability acceptance test
Export a representative building, route graph, identifiers and points of interest; import them into the target system; change a route or closure; confirm that the update propagates; then test positioning and user guidance separately. A successful file import is not evidence that the full indoor journey works.
