RTLS and RFID integration with ArcGIS means binding tag IDs to GIS features and streaming positions into a feature layer that maps, dashboards and web apps can read. Fixed RFID portals give zone-level presence; UWB or BLE gives metre-level coordinates. A stream or integration service normalises events, writes them to ArcGIS Velocity or a feature service, and raises geofence alerts on the map.
Swedish Technology builds the integration layer between tracking hardware and ArcGIS as versioned software with a documented event contract, so the GIS team can support it after hand-over.
What problem does this solve?
Most organisations that buy tracking hardware end up with two versions of the truth. The RTLS or RFID platform knows where a tag was last seen, in its own coordinate system, with its own zone names. The GIS knows where the asset is supposed to be, in the corporate spatial reference, linked to the asset register. Neither system knows about the other, so operations staff keep two screens open and reconcile by hand — and the map, which is the picture everyone else in the organisation trusts, is always out of date.
The second problem is semantic rather than technical. A tag is not an asset. Tags get swapped, re-used, moved to a replacement pump, or attached to a pallet rather than the item on it. Without a governed binding between tag ID and GIS feature — with validity dates and a history — a live map will confidently show the wrong thing, and one bad demo destroys trust in the whole programme.
Third, teams underestimate the difference between technologies. A fixed UHF RFID portal tells you an asset crossed a line; it does not give you coordinates, and it will occasionally miss a read or report a neighbouring tag. UWB gives 10–30 cm positions but only inside anchor coverage. BLE gives room-level accuracy at much lower cost. Building a map that promises metre-level truth on top of gate reads is the most common failure in these projects.
How the solution works
The workable pattern is an integration service between the tracking platform and ArcGIS. The service subscribes to tag events (MQTT, webhook, REST poll or a database view), de-duplicates and smooths them, resolves the tag ID to a GIS feature through a governed binding table, transforms coordinates into the organisation's spatial reference, evaluates geofence rules against ArcGIS polygons, and writes the result into ArcGIS — either through ArcGIS Velocity / GeoEvent Server for high-rate feeds, or with plain feature-service edits for the many sites where a position every few seconds is more than enough.
On top of that, ArcGIS gives you the presentation layer you already own: a live location widget in Experience Builder or a web map for the control room, dashboards for zone occupancy and dwell time, ArcGIS Pro for audits and reconciliation, and Field Maps for crews who need to find the asset. Swedish Technology builds the service, the binding model and the widget as custom development, and hands over the source, the event contract and the deployment scripts.
- 1Input Tags on assets, people or vehicles: passive UHF RFID for gates and inventory, active UWB or BLE for continuous indoor position, GNSS for outdoor fleet. Each tag has a unique ID printed and encoded.
- 2Capture Fixed readers, portals, UWB anchors and BLE gateways detect tags and send reads to the RTLS platform, which calculates a position or a zone and a timestamp.
- 3Processing The integration service filters duplicates and jitter, applies a minimum movement threshold, resolves tag ID to feature GlobalID via the binding table, and transforms x/y (or a floor + local grid) into the corporate spatial reference.
- 4Integration Positions are written into ArcGIS: a live layer updated with applyEdits, a stream/feature output from ArcGIS Velocity or GeoEvent Server, and an append-only observation layer for history. Asset attributes are enriched with last-seen time and zone.
- 5Action Geofence rules evaluate the new position against zone polygons — entered restricted area, left the site, dwell exceeded, asset missing from expected zone — and raise an alert, a notification or a work order in the maintenance system.
- 6Reporting Dashboards show occupancy per zone, utilisation and dwell distributions; the observation layer supports playback, audit trails and evidence for HSE or inventory reconciliation.
Reference architecture
Keep the tracking platform, the integration logic and ArcGIS separable. The binding model and the event contract are the two artefacts that decide whether this stays maintainable.
| Layer | What it contains |
|---|---|
| Edge / tracking | Readers, antennas, UWB anchors, BLE gateways and their controllers; site network with PoE and time synchronisation. Vendor platform (or MOWQIE RTLS) owns position calculation and zone definition. |
| Event transport | MQTT broker, webhook endpoint or message queue with at-least-once delivery, buffering during network loss, and a replay window so an ArcGIS outage does not lose history. |
| Integration service | Stateless workers that normalise events, apply the tag-to-feature binding, transform coordinates, evaluate geofences and write to ArcGIS. Holds ArcGIS and RTLS credentials, retries, and an audit log. |
| ArcGIS data | Live position feature layer (one row per tracked object), observation/track layer (append-only, with retention policy), asset layer carrying tag_id and last_seen, and zone polygons used for geofencing. |
| Real-time analytics | ArcGIS Velocity (ArcGIS Online) or ArcGIS GeoEvent Server (Enterprise) where volumes, incident detection or aggregation justify it; optional for sites with a few hundred tags. |
| Presentation & identity | Experience Builder live location widget, dashboards, Field Maps; portal or Entra ID SSO, with layer-level permissions so people tracking is restricted to authorised roles. |
Deployment options: For government and industrial sites the whole chain — RTLS platform, broker, integration service and ArcGIS Enterprise — runs on-premise or in a UAE-region private cloud. ArcGIS Velocity is a SaaS capability of ArcGIS Online; where cloud is not permitted, GeoEvent Server or direct feature-service updates replace it.
Key capabilities
Tag-to-feature binding with history
Every tag is bound to a GIS feature with valid-from/valid-to dates, so re-tagging and asset replacement do not corrupt the map or the history.
custom developmentLive location layer in ArcGIS
Operations sees current positions in the same web map as the network, buildings and work orders, with configurable refresh.
custom developmentLive location widget
A search-and-follow panel in Experience Builder: find an asset by ID, zoom to it, see last seen, zone and dwell without leaving the app.
custom developmentGeofencing on ArcGIS polygons
Zones are drawn and maintained by GIS staff, not by hardware vendors, so restricted-area and dwell rules follow the same governance as other GIS data.
custom developmentTrack history and playback
Investigators and auditors can replay where an asset or vehicle was, with retention rules that satisfy privacy policy.
custom developmentZone-level RFID presence
Gate and portal reads populate an in-zone/out-of-zone status for assets where continuous position is not needed or not affordable.
availableAlerting to work orders
A geofence or missing-asset event creates a notification in Maximo, SAP PM or a workflow tool instead of an email nobody reads.
custom developmentReconciliation reports
Scheduled comparison between the asset register, the last RFID inventory and the GIS layer, listing missing, misplaced and unknown tags.
custom developmentIntegrations
Location only becomes useful when it changes a record somewhere else. These are the integrations that normally accompany an ArcGIS RTLS project.
| System | Integration point & data exchanged | Direction |
|---|---|---|
| RTLS / RFID platform | Subscribe to tag events and zone transitions over MQTT, webhook or REST; read tag registry and anchor/zone configuration. → MOWQIE ÔÇô RTLS Tracking | inbound |
| ArcGIS Enterprise / Online | Feature-service edits, hosted layers, Velocity or GeoEvent feeds, Experience Builder apps and dashboards. → ArcGIS Experience Builder Custom Widgets | outbound |
| IBM Maximo | Asset and location master data for the binding table; missing-asset or geofence events raised as work requests. → ArcGIS – IBM Maximo Integration | bi-directional |
| SAP PM / S/4HANA | Equipment and functional location keys used as the join between tag, GIS feature and ERP record; notifications created from alerts. → ArcGIS – SAP Integration (PM/EAM, S/4HANA) | bi-directional |
| WMS / warehouse systems | Pallet and bin movements from RFID gates reflected on the site map and reconciled against stock records. → Octopus WMS | bi-directional |
| Digital twin / BIM model | Indoor positions rendered against floor plans and 3D models, with floor level carried through as an attribute. → RASM ÔÇô Digital Twin | outbound |
Industry use cases
Industrial and oil & gas sites
Tagged tools, calibration equipment and portable instruments shown on the plot plan; dwell alerts when equipment stays in a hazardous zone beyond a permit window.
Logistics and warehousing
RFID gates record pallet movement between yard, dock and storage zones; the site map shows current occupancy and the WMS gets the movement events.
Municipalities and facilities
Vehicles, generators and portable assets tracked across depots; missing-asset reconciliation replaces the annual manual count.
Healthcare and laboratories
BLE tags on mobile equipment show room-level location on floor plans, cutting search time; access to person-level data restricted by role.
Construction and infrastructure projects
Plant, formwork and material packages tracked against the project site model; deliveries confirmed by gate reads rather than paper notes.
UAE & GCC considerations
Government and semi-government entities in the UAE and wider GCC usually require that tracking data, especially anything that can identify a person, stays inside the country and inside their own infrastructure. That rules out cloud-only RTLS dashboards for many sites and pushes the integration service and ArcGIS Enterprise on-premise or into a UAE-region private cloud; we have delivered the chain in air-gapped form where an operator was not permitted outbound connectivity at all. UHF RFID equipment must be configured for the regional band plan and approved by the telecom regulator, and personnel-tracking use cases need an explicit privacy position — retention period, who can see individual tracks, and what is aggregated — agreed before the pilot. Interfaces, zone names and reports are delivered in English and Arabic, and hand-over documentation in both languages is commonly part of the tender scope.
Implementation approach
- 1Site survey and scope (1–2 weeks) Walk the site, confirm which assets matter, which zones need coverage and what accuracy each use case genuinely requires. Existing readers and network are assessed. See our RFID site survey and POC checklist.
- 2Technology decision Written recommendation per zone: passive UHF gates, UWB, BLE or GNSS — with the accuracy, cost and infrastructure implication of each. Mixed technologies in one map are normal.
- 3Data model and event contract Define the binding table, the live and observation layers, coordinate/floor handling, retention, and the exact event payload the RTLS platform will send. This document is the contract for both sides.
- 4Build the integration service Iterative development of the normalisation, binding, geofence and ArcGIS write logic, with a simulator so it can be tested before hardware is installed.
- 5ArcGIS configuration and widget Layers, symbology, zone polygons, dashboards and the live location widget in Experience Builder; permissions and SSO.
- 6Pilot in one zone (3–6 weeks) Run with real tags and real users. Measure read rate, position error, latency and false geofence alerts; tune thresholds and antenna placement.
- 7Roll-out Extend zone by zone, with a tagging procedure, labelling standard and a process for re-tagging and decommissioning.
- 8Hand-over and support Source code, deployment scripts, runbook, monitoring dashboards for the pipeline itself, and training for the GIS and operations teams.
Security & deployment
Position data is operational data and, when tags are worn by people, personal data. The integration service holds the credentials for both ArcGIS and the RTLS platform, never the browser; ArcGIS layer permissions and portal or Entra ID SSO decide who sees which layer, and person-level layers are separated from asset layers so they can be restricted or aggregated. All transport is TLS, the broker is authenticated, and every write to ArcGIS is logged with source event ID for audit. Retention is enforced on the observation layer by a scheduled job rather than left to grow. The whole stack runs on-premise, in a UAE-region private cloud, or air-gapped with local package deployment.
Limitations & prerequisites
- Passive UHF RFID gives presence and direction at a portal, not coordinates; a map built on gate reads shows last known zone, not live position, and should be labelled that way.
- UWB accuracy of 10–30 cm applies only inside anchor coverage with line of sight; metal, liquids, racking and moving vehicles degrade it, and coverage gaps look like teleporting assets unless smoothing is applied.
- Missed reads are normal in RFID. Read rates of 95–99 % are achievable with tuning, but no configuration removes the need for exception handling and periodic reconciliation.
- ArcGIS Velocity is a capability of ArcGIS Online; organisations restricted to on-premise must use GeoEvent Server or direct feature-service updates, with lower throughput ceilings.
- Very high event rates (thousands of tags updating per second) need aggregation and a big data store; writing every read to a feature service will not scale and will make the map unusable.
- The tag-to-feature binding is an operational process, not just a table. If nobody owns re-tagging and decommissioning, the map degrades within months.
- Tracking people requires a legal and HR position, worker consultation and retention limits; these are usually the longest lead item in the project, not the technology.
Choosing how location reaches ArcGIS
Three delivery patterns, chosen mainly by event rate, deployment constraints and how much analytics belongs in the platform.
| Criterion | Direct feature-service updates | ArcGIS GeoEvent Server | ArcGIS Velocity |
|---|---|---|---|
| Where it runs | Anywhere, including air-gapped | ArcGIS Enterprise, on-premise | ArcGIS Online (SaaS) |
| Typical event rate | Up to a few hundred updates/second | Thousands/second with tuning | High, elastic |
| Real-time analytics built in | No — write it yourself | Yes (filters, processors, geofence) | Yes (feeds, real-time and big data analytics) |
| Track history store | Custom observation layer | Spatiotemporal big data store | Included big data store |
| Licensing | Included with Enterprise/Online | Additional Enterprise server role | Subscription capability of ArcGIS Online |
| Setup effort | Lowest | Medium — server role plus configuration | Low, but needs cloud approval |
| Best for | Sites with modest tag counts and strict data residency | Large on-premise deployments with incident detection | Cloud-permitted organisations wanting managed real-time |
Many UAE deployments start with direct feature-service updates for a pilot and move to GeoEvent Server only when event volume or built-in incident detection justifies the extra server role.
FAQ
Hardware coverage is usually the largest line: the number of zones needing UWB or BLE infrastructure, and the number of RFID portals. On the software side, cost is driven by the number of event types, whether geofencing and alerting are needed, how many enterprise systems must be updated, and whether a custom widget and bilingual UI are in scope.
A site survey and design take 2–4 weeks. A pilot covering one zone with a live map and a working binding table is typically 6–10 weeks including hardware installation. Site-wide roll-out depends on how many zones and readers are involved and is usually phased over several months.
Not for most sites. Velocity is worth it when you have high event volumes, want managed real-time analytics, and are permitted to use ArcGIS Online. On-premise organisations use GeoEvent Server or, for modest volumes, direct feature-service updates from the integration service.
It depends on the technology per zone: UWB typically 10–30 cm inside anchor coverage, BLE 1–5 m or room level, GNSS 2–10 m outdoors, and fixed RFID portals give zone presence rather than coordinates. We state an expected accuracy per zone in the design and verify it in the pilot rather than quoting a single site-wide figure.
A floor plan or site map with the zones that matter, the asset list with the identifiers used in your asset register, the make and model of any existing readers or anchors, and API documentation or access to the RTLS platform. If tracking people is in scope, we also need the privacy and retention position.
Yes. The RTLS platform, message broker, integration service and ArcGIS Enterprise can all run inside your network, with no outbound connectivity. Deployment is by local package; updates are delivered as signed builds through your change process.
Through the same integration service. Asset and location master data is read from Maximo or SAP to build and validate the tag-to-feature binding, and geofence or missing-asset events are posted back as work requests or notifications. See our ArcGIS – IBM Maximo and ArcGIS – SAP integration pages.
You do. Source code, the event contract, deployment scripts, monitoring dashboards and runbooks are handed to your team, and we can continue under a support agreement. The binding table and zone polygons stay in your ArcGIS environment under normal GIS governance.
Tags on one system, maps on another?
Send us your reader/anchor layout and the ArcGIS layers you want to update. We reply with an event contract, an accuracy expectation per zone, and the integration options with effort.
Book an Integration WorkshopSources & evidence
- Esri — ArcGIS Velocity documentation — real-time and big data feeds, analytics, outputs
- Esri — What is ArcGIS GeoEvent Server?
- GS1 — EPC Tag Data Standard — tag identity encoding used for asset keys
- ETSI — EN 302 208 (UHF RFID equipment, 865–868 MHz)
- FiRa Consortium — UWB technology (IEEE 802.15.4z)
Vendor and product names are trademarks of their respective owners; references are for technical context and do not imply partnership, certification or endorsement unless stated on the vendor's official pages.