RTLS UAE: Real-Time Location Systems

Key facts

BLE RSSI positioning typically gives room or zone accuracy of 1–5 m; BLE angle-of-arrival can reach sub-metre with denser, calibrated infrastructure.
UWB time-of-flight positioning typically achieves 10–50 cm in line of sight; metal and obstructions degrade it.
Accuracy always depends on anchor density, geometry, building materials, calibration and tag placement on the object or person.
Tag battery life depends mainly on update rate: a tag reporting every second drains far faster than one reporting on motion only.
Passive UHF RFID gives zone-level presence at portals and read points, not continuous coordinates.
GNSS works outdoors and in open yards but fails indoors and degrades near tall structures and under canopies.
Most sites mix technologies: sub-metre where safety demands it, zone-level where presence is enough.

In short

This page is the decision guide for real-time location across technologies, use cases and industries. It explains how the parts fit together, where each positioning method fits, how to prove accuracy in a pilot and what drives cost.

MOWQIE is Swedish Technology's own RTLS platform. This hub covers the wider category, including when a simpler zone-level or RFID approach is the better answer, and links to MOWQIE where a platform is needed.

Why organisations look at RTLS

Most RTLS projects start from a cost nobody measures precisely: time spent searching, duplicate equipment purchases, people unaccounted for in an evacuation, or pedestrian-vehicle near misses.

Assets cannot be found

Mobile equipment such as infusion pumps, tools, pallets and test kits is recorded in the asset register but not at a known location.

Headcount during emergencies

Muster points rely on paper lists or badge-in data, which do not show who is still inside a hazardous area.

Vehicle and pedestrian conflicts

Forklifts, reach trucks and site plant share space with people, and blind spots cause incidents that cameras only record after the fact.

Process time is guessed

Dwell times, bottlenecks and utilisation are estimated from interviews instead of measured from real movement data.

What RTLS tracks: assets, people and vehicles

The object being tracked shapes the tag, the update rate and the privacy approach. Mixing all three on one platform is common, but each needs its own design assumptions.

Accuracy figures on this page are indicative. Achieved accuracy depends on anchor density, geometry, building materials, calibration and how the tag is worn or mounted, and should be measured on site.

Asset tracking

Low update rates and long battery life. Location is usually shown as room, bay or shelf zone, with movement events triggering updates.

People tracking

Badges or wristbands for staff, contractors or patients. Uses include mustering, lone-worker alerts, duress buttons and access to restricted areas; privacy design is essential.

Vehicle tracking

Forklifts, tuggers and site plant with higher update rates, often powered from the vehicle. Supports speed zones, proximity warnings and utilisation reporting.

Indoor maps and geofencing

Zones drawn on floor plans generate enter, exit and dwell events. Geofence size should match achievable accuracy, or alerts will be unreliable at zone boundaries.

Alerts and analytics

Rules raise alerts for restricted-zone entry, missing assets, no-motion or SOS. Historical data feeds heatmaps, dwell time, utilisation and spaghetti diagrams.

How an RTLS is built: anchors, tags, gateways and the location engine

Every RTLS has the same layers regardless of radio technology. The choices at each layer decide accuracy, battery life, cost and how much cabling the building needs.

Anchors and locators

Fixed devices on ceilings or walls that receive tag signals and measure signal strength, angle or time of flight. Their spacing and geometry set the accuracy ceiling.

Gateways and backhaul

Collect anchor data over Ethernet, PoE, Wi-Fi or cellular. Some systems need precise time synchronisation between anchors, which affects cabling design.

Location engine

Software that turns raw measurements into positions or zone events, applying filtering, map constraints and motion models. On-premise or private cloud hosting is common.

Maps and zones

Floor plans, CAD or BIM-derived layouts and GIS basemaps, with defined zones, geofences and restricted areas.

Application and integration layer

Dashboards, search, alerts, reports and APIs that push events to ERP, CMMS, WMS, GIS or safety systems.

RTLS by industry

The same architecture serves very different operations. What changes is the tag form factor, the accuracy target per zone and the systems the location data must reach.

Hospitals

Locating mobile medical equipment, par-level alerts for pumps and wheelchairs, staff duress, patient flow and infant or wander protection. Tags must tolerate cleaning agents.

Warehouses and logistics

Forklift and pallet location, dock door events, pedestrian-vehicle proximity and linking movements to WMS tasks.

Construction

Tool and equipment location, worker headcount by zone and level, and mustering. Anchors must be temporary and moved as the building grows.

Oil and gas

Personnel accounting in process areas, gas-alarm mustering and lone-worker monitoring. Equipment in hazardous areas needs appropriate intrinsic safety or explosion-proof ratings.

Worker safety

Restricted zones, man-down detection and forklift collision avoidance, covered in detail on the worker-safety and forklift pages.

Airports, campuses and public buildings

Asset tracking across large multi-storey sites in Dubai, often reusing Wi-Fi or BLE infrastructure.

Integrating location data with ERP, GIS, WMS and CMMS

Location data is most useful when it updates the systems where people already work. Integration is typically event-based: the RTLS publishes zone changes or alerts, and middleware maps tag IDs to asset or employee records.

SAP

Asset location and status updates against equipment or fixed asset records; goods movements triggered by zone transitions.

Esri ArcGIS

Live tag positions as feature layers on site or campus maps, combining indoor floors with outdoor yards and utilities.

IBM Maximo and other CMMS

Current asset location for work orders, so technicians find equipment before a planned maintenance visit.

WMS

Forklift and pallet location confirming put-away and picking tasks, and measuring travel time per task.

Access control, VMS and BMS

Correlating tag events with door access, camera views and building systems for security and emergency response.

Data privacy, security and hosting

Tracking people is personal data processing. Under the UAE Personal Data Protection Law (PDPL) and sector rules, relevant considerations include a documented purpose, informing staff and obtaining consent where required, limiting use to that purpose and setting retention periods. Whether a deployment complies depends on project configuration, policies and approvals.

Practical design choices help: tracking only on site or during shifts, zone-level rather than coordinate-level storage for people, role-based access to history, anonymised analytics and automatic deletion after the retention period.

Hosting can be on-premise, private cloud or UAE-hosted cloud where data residency is required. Health deployments may need to consider ADHICS or DoH requirements, and critical infrastructure may involve NESA/IA or DESC controls, again depending on scope and approvals.

Key components

Battery management

The location engine should report battery level per tag and raise low-battery alerts early. Update rate, motion-triggered reporting and temperature have the biggest effect on life.

Tag lifecycle

Plan for commissioning, pairing to asset or person records, replacement, retirement and cleaning or charging stations for wearable badges.

Tag mounting

Tags on metal, inside cases or worn under clothing behave differently. Mounting should be fixed during the pilot, not after.

How a project runs

Assess
Define what must be located, at what accuracy per zone, and which decisions or alerts depend on it. Output: requirements and success measures.
Site survey
Review drawings, ceiling heights, materials, power and network routes, and measure RF conditions. Output: survey findings and constraints.
Design
Select technology per zone, plan anchor positions and backhaul, define zones and integrations. Output: design, bill of materials and test plan.
Pilot
Deploy in a representative area and measure accuracy, latency and battery behaviour against agreed criteria. Output: pilot report with measured results.
Deploy
Install and calibrate anchors, commission tags, build maps and alert rules, and train users. Output: working system and as-built documentation.
Integrate
Connect events to ERP, CMMS, WMS, GIS or safety systems and test end to end. Output: live data flows and interface documentation.
Operate and support
Monitor anchors and batteries, recalibrate after layout changes and review analytics. Output: support process and health reporting.

BLE vs UWB vs Wi-Fi vs GPS vs passive RFID: which fits each zone

Technology/option	Best fit when…	Limitations	Typical environment
BLE (RSSI or angle-of-arrival)	You need room, bay or zone location for many low-cost tags with long battery life. RSSI is typically 1–5 m; AoA can reach sub-metre with dense locators.	RSSI is sensitive to bodies, metal and multipath; AoA needs more locators and careful calibration.	Hospitals, offices, general asset tracking, staff badges
UWB (time of flight / TDoA)	You need sub-metre positions, typically 10–50 cm, for collision avoidance, precise dwell or tool location.	Higher tag and anchor cost, shorter tag battery life at high update rates, and dense metal reduces performance.	Warehouses, production lines, forklift and pedestrian safety zones
Wi-Fi (RSSI or RTT)	Existing enterprise Wi-Fi can be reused and 3–15 m (RSSI) or roughly 1–3 m (RTT, with supporting access points) is enough.	Accuracy depends on access point density and placement designed for coverage, not location; tag power draw is higher.	Campuses, offices, large public buildings
GNSS / GPS (with cellular or LoRaWAN backhaul)	Assets and vehicles are outdoors across yards, laydown areas or pipeline corridors; typically 2–5 m, RTK can reach centimetres.	No indoor coverage; degraded near tall structures, steelwork and canopies; power hungry at frequent fixes.	Construction sites, ports, oil and gas facilities, fleet yards
Passive UHF RFID (zone level)	Presence at doors, dock doors, gates or shelves is enough and tags must be cheap and battery-free.	Location only where a reader sees the tag; no continuous tracking between read points.	Stores, warehouses, IT and document assets, controlled rooms

Risks and common mistakes

Specifying one accuracy for the whole site

Set accuracy per zone. Paying for sub-metre coverage in corridors that only need room level wastes budget.

Accepting vendor accuracy figures

Measure accuracy on site at surveyed points and agree percentile targets before the pilot.

Geofences smaller than achievable accuracy

Size zones to the measured error, or alerts will fire and clear at the boundary.

Ignoring battery planning

Model update rates and battery life early; high-rate tags may need charging routines.

Treating people tracking as a technical task

Involve HR, legal and staff representatives on purpose, notice and retention before deployment.

What to check before you commit

List of what must be tracked, how many of each, and the accuracy needed in each zone
Current floor plans, CAD or BIM files and any GIS basemaps
Ceiling types, heights and access constraints for anchor installation
Network and PoE availability, VLAN and IT security requirements
Hazardous area classification where relevant
Target systems for integration and their owners
Privacy assessment, staff communication plan and retention policy for personnel data
Hosting preference and data residency requirements
Agreed pilot area and acceptance criteria

Pilot / proof of concept

A pilot should cover the hardest part of the site, not the easiest: metal racking, lift lobbies, stairwells or areas with heavy foot traffic. A useful scope is one or two representative zones with enough tags to test real behaviour. Pilots typically run 4–8 weeks including installation and measurement, depending on site access and integration scope.

Accuracy acceptance should be agreed in writing before installation. The common method is to survey fixed test points with known coordinates, place tags at each point and in realistic mounting positions, record many readings, and report the error distribution as percentiles rather than a single average.

Position error at test points

Report 50th and 90th or 95th percentile error at each surveyed point, static and while walking or driving a defined route.

Zone detection rate

Percentage of correct zone assignments when tags cross boundaries, including time to detect the change.

Latency

Time from real movement to event in the dashboard or connected system, measured at the agreed update rate.

Battery drain

Measured consumption over the pilot, projected to expected life at production settings.

Alert reliability

False and missed alerts for geofences, SOS or proximity rules over the pilot period.

Integration check

Events arriving correctly in the target ERP, CMMS or GIS record.

What drives the cost

RTLS cost scales with area, accuracy and the number of tracked objects, not with a single licence fee. A site survey is the only reliable way to size it.

Accuracy target

Sub-metre zones need denser anchors and often UWB, which raises hardware and installation effort.

Coverage area and floors

Anchor count grows with floor area, ceiling height and number of rooms or racking aisles.

Number and type of tags

Wearable badges, rugged vehicle units and intrinsically safe tags differ widely in unit cost.

Cabling and installation

PoE runs, ceiling access, working at height and out-of-hours installation in live facilities.

Integration scope

Each connected system such as SAP, Maximo or ArcGIS adds interface design and testing.

Hosting and support

On-premise servers versus private cloud, and the level of ongoing monitoring and recalibration.

Questions buyers ask

What is the difference between RTLS and RFID?

Passive RFID records where a tag was last read, typically at a door, gate or shelf reader. An RTLS uses battery-powered tags and a network of anchors to calculate position continuously across an area. Many sites use both: RFID for high-volume, low-cost items and RTLS for mobile equipment, people and vehicles that need continuous location.

How accurate is UWB RTLS compared with BLE?

UWB typically achieves 10–50 cm in good conditions, while BLE signal-strength positioning is typically 1–5 m and BLE angle-of-arrival can approach sub-metre. Real results depend on anchor density, geometry, building materials, calibration and tag placement, so accuracy should be measured at surveyed test points during a pilot.

Can RTLS work with our existing Wi-Fi?

Sometimes. Wi-Fi positioning can reuse access points and give room or floor level location, and newer access points supporting round-trip time can improve that. Access points are usually placed for coverage rather than location, so a survey is needed to check whether density and placement are adequate for the use case.

How long do RTLS tag batteries last?

It depends on the technology, update rate and motion settings. Asset tags that report only when moved can last several years, while people or vehicle tags reporting every second may need recharging or replacement far more often. Battery life should be projected from pilot measurements, not datasheet figures.

Is tracking employees legal in the UAE?

Personnel tracking involves personal data, so considerations under the PDPL and sector rules include a clear purpose, staff notice and consent where required, purpose limitation and defined retention. Compliance depends on the project configuration, policies and approvals, and legal advice should be taken for each deployment.

How do you prove RTLS accuracy before full rollout?

Agree criteria in writing, survey fixed test points with known coordinates, then record many tag readings at each point and along walked or driven routes. Report error as percentiles, such as 50th and 95th, together with zone detection rates, latency and battery drain.

Can RTLS be used for forklift collision avoidance?

Yes, typically with UWB tags on vehicles and people for sub-metre proximity measurement. The system can warn drivers and pedestrians, slow vehicles in defined zones and log near misses. Performance depends on update rate, anchor coverage and how tags are mounted.

Does RTLS work outdoors on construction or oil and gas sites?

Outdoor areas usually use GNSS tags with cellular or LoRaWAN backhaul, while buildings and covered areas use BLE or UWB anchors. Hazardous areas need equipment with suitable ratings. A single platform can combine indoor and outdoor positions on one map.

Can location data go into SAP, Maximo or ArcGIS?

Yes. RTLS platforms typically publish zone changes, positions and alerts through APIs or message queues. Middleware maps tag IDs to equipment, employee or work order records so that asset registers, maintenance work orders and map layers stay current without manual updates.

What is the difference between this page and MOWQIE?

This page compares RTLS technologies and approaches in general. MOWQIE is Swedish Technology's RTLS platform, covering the location engine, maps, alerts and analytics. Some projects need a full platform such as MOWQIE; others are better served by zone-level RFID or integration with existing systems.

Hospital Asset Tracking System

Shows how an RTLS is applied to hospital equipment tracking, including tag types, alert examples and workflow scenarios for clinical engineering teams.

Download the PDF Read it online النسخة العربية

Plan an RTLS pilot for your site

Share your floor plans, what you need to locate and the accuracy each zone requires. We will propose a survey, a pilot scope and acceptance criteria based on measured results.

Request a site survey Request pricing or a BoQ Browse the Resource Centre