Enterprise GIS is the shared platform an organisation uses to store, edit, analyse and publish location data for its assets, networks and field operations. Swedish Technology designs, deploys, integrates and supports GIS solutions that work with the Esri ArcGIS platform, including ArcGIS Enterprise, field apps, utility and road asset models, BIM/GIS and 3D, and integration with SAP, Oracle, Odoo and IBM Maximo.

Key facts

  • ArcGIS Enterprise typically combines ArcGIS Server, Portal for ArcGIS, ArcGIS Data Store and Web Adaptor, deployed on-premises or in a private or public cloud.
  • The ArcGIS Utility Network models connectivity, containment and attachment rules, enabling upstream, downstream and isolation traces across electric, water, gas and telecom networks.
  • Linear referencing locates road events such as defects, signs and pavement sections by route and measure rather than by x,y coordinates alone.
  • ArcGIS Field Maps and Survey123 both support offline data collection, with edits synchronised when the device reconnects to the network.
  • BIM/GIS alignment depends on correct coordinate reference systems; in the UAE, projects commonly use WGS 84 / UTM zone 40N or local emirate grids.
  • Indoor positioning accuracy depends on technology and infrastructure: BLE is often metre-level, UWB is often sub-metre, both site dependent.
  • Mobile LiDAR and drone photogrammetry produce point clouds and meshes that can be published as 3D scene layers for web viewing.

In short

This page is the decision hub for GIS and ArcGIS work: what an enterprise GIS should include, which components fit which problem, how GIS connects to ERP and maintenance systems, and how to host, upgrade and govern it. Specific projects and platforms are linked at the end.

Swedish Technology works with the Esri ArcGIS platform across the full lifecycle: data model design, field apps, integration, 3D and indoor mapping, upgrades and support.

Why GIS programmes stall

Most organisations already hold GIS data. The problems usually sit around it: disconnected datasets, field teams working on paper or spreadsheets, and asset IDs that do not match between GIS and the ERP or maintenance system.

Fragmented data

CAD drawings, shapefiles and spreadsheets held by different departments, with no single authoritative feature class per asset type.

Field data arrives late

Inspections on paper or Excel are re-keyed days later, introducing errors and losing photos and exact locations.

No link to work orders

Assets in GIS and assets in SAP or Maximo carry different IDs, so maintenance history cannot be shown on a map.

Ageing ArcGIS deployments

Older ArcGIS Server or ArcMap-era workflows become slow, unsupported and hard to secure, and upgrades are postponed because of risk.

What a working enterprise GIS looks like

A useful enterprise GIS has one governed data model, controlled editing, web and mobile apps built for specific roles, and defined interfaces to the systems of record around it.

Authoritative data model

Feature classes, domains, subtypes and relationship classes designed per asset type, with attribute rules enforcing validation at edit time.

Role-based apps

Experience Builder dashboards for managers, Field Maps for inspectors, Survey123 forms for structured inspections, ArcGIS Pro for editors and analysts.

Versioned editing

Branch versioning allows web and field edits with conflict handling, and supports review before changes reach the default version.

Integration layer

REST services, feature service webhooks or middleware exchange asset IDs, work orders and status with ERP and maintenance systems.

Analytics and GeoAI

Spatial analysis, network traces and deep learning models that detect objects in imagery, such as road defects, poles or rooftops.

Reference architecture

These layers apply on-premises, in a private cloud or on ArcGIS Online. Sizing depends on users, editing load, imagery volume and integration frequency.

Data sources

Survey, CAD/BIM, drone and LiDAR capture, imagery, IoT and RFID/RTLS feeds, ERP asset registers.

Geodatabase

Enterprise geodatabase on SQL Server, PostgreSQL or Oracle, holding versioned vector data, network models and linear referencing.

Server and portal

ArcGIS Enterprise publishes map, feature, scene and image services, manages users, groups and content sharing.

Integration services

APIs, ETL (for example Data Interoperability or Python), message queues and webhooks connecting GIS with SAP, Oracle, Odoo or Maximo.

Applications

ArcGIS Pro, Experience Builder, Dashboards, Field Maps, Survey123, custom widgets and add-ins.

Operations

Monitoring, backup, patching, identity integration (SAML or Active Directory) and environment promotion from test to production.

Where GIS is applied

Municipalities

Land parcels, building permits, street furniture, complaints and inspection workflows tied to a common base map.

Roads and transport

Linear-referenced road inventory, pavement condition surveys, right-of-way management and incident mapping.

Utilities

Utility network models for water, power, gas and telecom, outage analysis, and field maintenance linked to work orders.

Oil and gas

Pipeline and facility mapping, integrity and inspection data, right-of-way monitoring with imagery and drone capture.

Real estate and FM

Indoor maps, space and lease data, asset locations and service requests for portfolios and campuses.

Construction

Site progress from drone surveys, BIM/GIS coordination, utility clash checks and handover of as-built assets.

Integrating GIS with SAP, Oracle, Odoo and IBM Maximo

Every integration starts with three decisions: which system is the system of record for each attribute, which identifier links the records, and which direction data flows. GIS is usually authoritative for geometry and network connectivity; the ERP or EAM is usually authoritative for financial, warranty and work order data.

Sync can be event-driven (webhooks or messaging), scheduled (batch ETL) or on demand (a GIS widget querying the ERP API). The choice depends on how quickly users need changes and how much load the source systems can accept.

SAP (S/4HANA, PM/EAM)

Functional locations and equipment numbers linked to GIS features; notifications and orders created from the map; geometry stays in GIS.

Oracle (EBS, Fusion, EAM)

Asset register and cost data referenced by GIS ID; GIS-derived attributes such as length or zone written back where agreed.

Odoo

Assets, maintenance requests and inventory locations exchanged through Odoo APIs; suitable for smaller operators needing a lighter stack.

IBM Maximo

Assets and locations kept in sync with GIS, work orders displayed spatially, and Maximo Spatial or REST-based integration depending on version.

RFID and RTLS platforms

Tag reads and positions posted as feature updates or stream services, with the GIS holding zones, floors and asset context.

BIM and CAD

IFC and Revit models georeferenced into scene layers; DWG converted to feature classes with attribute mapping.

Data governance, security and hosting

Governance covers who owns each dataset, who may edit it, how changes are reviewed, and how quality is measured. We document data owners, editing rights by group, attribute rules, metadata standards and retention for each layer.

Access is controlled through portal groups and roles, integrated with the organisation's identity provider. Sensitive layers such as critical infrastructure can be kept on internal-only services.

Hosting choice affects data residency. Compliance with UAE requirements such as PDPL, NESA/IA or DESC depends on project configuration and approvals, and is assessed with the client's security team rather than assumed.

Key components

ArcGIS Enterprise

Self-hosted GIS server and portal for organisations that need data on their own infrastructure or tight integration with internal systems.

ArcGIS Pro

Desktop application for editing, analysis, map production, utility network administration and geoprocessing; extensible with add-ins and Python toolboxes.

Experience Builder

Configurable web apps and dashboards; custom widgets can be developed where out-of-the-box widgets do not cover a workflow.

Field Maps and Survey123

Mobile data collection and inspection, with offline map areas, smart forms, photo attachments and GNSS receiver support.

GeoAI

Deep learning tools for object detection, classification and change detection on imagery and point clouds, trained or fine-tuned on local data.

Indoor GIS

Floor-aware maps of buildings and campuses for space management, wayfinding and live location of tagged assets and people.

3D GIS

Scene layers for buildings, terrain, point clouds and integrated meshes, used for planning, visibility and clash review.

Drone and LiDAR processing

Orthomosaics, digital surface models and classified point clouds, published as layers alongside existing asset data.

Where this is used in the UAE and the GCC

Utility network management

Water, electricity or district cooling operators model connectivity and run isolation traces to identify affected customers before planned or emergency shutdowns.

Road asset inventory and pavement condition

Road authorities store signs, lighting, barriers and pavement sections on linear-referenced routes and prioritise maintenance by condition index.

Offline field inspection

Inspectors complete Survey123 or Field Maps forms in areas with poor coverage; data, photos and GNSS positions sync on reconnection.

Live location on maps

RFID reads and RTLS positions are pushed to feature layers so control rooms see equipment and personnel on indoor or site maps.

BIM to GIS handover

Contractors deliver IFC or Revit models that are georeferenced and converted into asset feature classes for operations.

How a project runs

  1. Assess

    Review existing data, ArcGIS versions, licences, users and integrations. Output: current-state report and prioritised gaps.

  2. Discovery

    Workshops with asset owners, field teams and IT to define data models, workflows and system-of-record rules.

  3. Design

    Data model, architecture, hosting, security and integration specification, with acceptance criteria agreed up front.

  4. Pilot

    One workflow or integration proven with real users and data before wider rollout.

  5. Deploy

    Environment build, data migration, app configuration and training by role.

  6. Integrate

    ERP, EAM, BIM and live location interfaces implemented and tested end to end.

  7. Operate and support

    Monitoring, patching, user support, change requests and planned upgrades under an agreed support model.

Hosting options: on-premises, UAE-hosted cloud or ArcGIS Online

OptionBest fit whenLimitationsTypical environment
ArcGIS Enterprise on-premises Data must stay on the organisation's own network, or GIS integrates tightly with internal systems. Client owns hardware, patching, backups and upgrade effort. Government entities, utilities, critical infrastructure.
ArcGIS Enterprise in a UAE-hosted cloud In-country data residency is required but the organisation wants elastic infrastructure. Cloud region and service availability must be checked; operating cost is ongoing. Enterprises and semi-government bodies with cloud policies in place.
ArcGIS Online (SaaS) Fast start, small IT team, mostly public or low-sensitivity data. Data is hosted in Esri-managed regions; residency and integration options are narrower. Smaller teams, public-facing maps, pilots.
Hybrid (Enterprise plus Online) Internal data stays on Enterprise while selected layers are shared publicly or with partners. Two environments to govern; sharing rules must be designed carefully. Municipalities and utilities publishing open data.
Disconnected or air-gapped Enterprise Networks cannot connect to the internet for security reasons. Licensing, updates and basemaps need offline handling. Defence, security and sensitive industrial sites.

Risks and common mistakes

Migrating data without cleaning it

Profile and fix geometry, topology and attribute errors before loading into a new model.

Undefined system of record

Agree per attribute which system owns it before building any sync.

Upgrading ArcGIS Enterprise in place without a rollback plan

Check version compatibility of geodatabase, Pro clients, custom widgets and integrations; test in staging; keep full backups and a documented rollback path.

Building field apps before the data model is stable

Freeze domains and required fields first, then design forms, or offline maps will need rework.

Treating BIM as ready for GIS

Agree coordinate reference system, units, IFC schema and attribute mapping with contractors before handover.

Pushing high-frequency RTLS data straight into feature layers

Aggregate or filter positions and use stream services for live views to avoid overloading the geodatabase.

What to check before you commit

  • Inventory of existing GIS data, formats, coordinate systems and owners.
  • Current ArcGIS versions, licence types and user counts.
  • List of systems to integrate and the asset ID used in each.
  • Hosting policy and data residency requirements from IT and security.
  • Priority workflows and the roles that will use them.
  • Field conditions: connectivity, devices, GNSS accuracy needs.
  • BIM/CAD standards and handover requirements for contractors.
  • Named data owners and an internal GIS administrator.

Pilot: field inspection or integration

A pilot proves one workflow with real data and users. Typical scopes are an offline field inspection app for a single asset class, or a two-way link between GIS and SAP or Maximo for one asset type.

Pilots typically run 6 to 10 weeks, indicative only and dependent on data readiness and access to systems. Acceptance criteria are agreed in the design stage and measured against the pilot data.

Data completeness

Share of inspected assets with all required fields, photos and a valid location.

Offline reliability

Edits collected without coverage synchronise without loss or duplicate records.

Sync correctness

Records created or changed in one system appear correctly in the other, with matching IDs.

Turnaround time

Time from field capture to data visible to supervisors, compared with the current process.

User acceptance

Field and office users complete defined tasks without workarounds during the pilot period.

What drives the cost

Cost depends on scope, data condition and integration depth. Esri software licensing is separate from services and is sized to users and capabilities.

Data condition

Cleaning, migrating and restructuring legacy CAD or shapefile data is often the largest effort.

Number of workflows and apps

Each role-specific app, form and dashboard adds design, testing and training.

Integration depth

One-way read links are simpler than two-way sync with work order creation and error handling.

Hosting and environments

Separate development, staging and production environments, high availability and disaster recovery add infrastructure and effort.

Capture requirements

Drone, LiDAR or survey campaigns depend on area, accuracy and processing needs.

Support model

Level of ongoing monitoring, response expectations and upgrade assistance.

Questions buyers ask

Which ArcGIS products do you work with?

Swedish Technology works with the Esri ArcGIS platform, including ArcGIS Enterprise, ArcGIS Pro, ArcGIS Online, Experience Builder, Dashboards, Field Maps, Survey123 and GeoAI tools. We deliver design, configuration, development, integration and support. Software licences are procured separately through the appropriate channel, and we help size what your users and workflows actually need.

Should we use ArcGIS Enterprise or ArcGIS Online?

ArcGIS Online suits fast deployment, smaller teams and lower-sensitivity data. ArcGIS Enterprise suits organisations that need data on their own infrastructure or in-country cloud, tighter integration with internal systems, or disconnected operation. Many organisations run both, keeping internal data in Enterprise and sharing selected layers through Online. The decision usually rests on data residency, integration and IT capacity.

How do you upgrade ArcGIS Enterprise safely?

We first check compatibility across the geodatabase, database version, ArcGIS Pro clients, custom widgets, scripts and integrations. The upgrade is rehearsed in a staging copy with representative data, and key workflows are tested. Production is backed up, the change window is agreed, and a documented rollback path is kept ready. Where the gap is large, a side-by-side migration can be lower risk than in-place upgrade.

How does GIS integrate with SAP?

Typically SAP functional locations or equipment numbers are stored on GIS features as the shared key. GIS remains the source of geometry and network connectivity, while SAP owns maintenance and financial data. Integration can be event-driven, scheduled or on demand, and users can create notifications from the map or view order history for a selected asset.

Can field teams work offline?

Yes. ArcGIS Field Maps and Survey123 both support offline work. Map areas and forms are downloaded before going to site, and edits, photos and GNSS positions are stored on the device and synchronised when connectivity returns. Offline workflows should be designed around the data model and expected sync volumes to avoid conflicts.

What is the ArcGIS Utility Network and do we need it?

The Utility Network is the ArcGIS data model for connected networks such as water, electricity and gas. It stores connectivity and containment rules so you can run upstream, downstream and isolation traces. If you need outage analysis or network-aware editing, it is worth considering; migrating from a geometric network requires careful data preparation.

How is BIM brought into GIS?

BIM models such as IFC or Revit are georeferenced to the project coordinate system and brought into ArcGIS as building scene layers or converted into asset feature classes. Success depends on agreed coordinate reference systems, units, and attribute mapping between BIM properties and GIS fields, ideally set in contractor handover requirements.

Can RFID or RTLS locations be shown on ArcGIS maps?

Yes. Tag reads and positions can be posted to feature layers or stream services and displayed on indoor or site maps in Experience Builder or Dashboards. High-frequency data is usually filtered or aggregated first. Positioning accuracy depends on the technology and infrastructure installed, not on the GIS.

What does GeoAI do in ArcGIS?

GeoAI applies deep learning to imagery and point clouds to detect or classify features such as road defects, vehicles, building footprints or poles. Pre-trained models can be a starting point, but results usually improve after fine-tuning on local imagery. Outputs should be reviewed before they update authoritative data.

What support do you provide after go-live?

Support is agreed per project and can include monitoring, patching, user helpdesk, data administration, change requests and planned upgrades. Response expectations and scope are defined in the support agreement for each client, based on how critical the GIS is to operations.

AI GIS and Geospatial Intelligence

The brochure summarises AI and geospatial intelligence capabilities in a printable format for internal sharing and procurement discussions.

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

Plan your GIS project

Share your current ArcGIS setup, data sources and priority workflows. We will propose a scope, architecture and pilot approach suited to your hosting and integration requirements.

Request a GIS assessment Request pricing or a BoQ Browse the Resource Centre