GIS consulting for local government, utilities and engineering firmsinfo@infraspatialsolutions.comServing clients across the United States
Back to all projects
ArcGIS Enterprise 11.4

Enterprise GIS Deployment for a Municipal Utility

The record of a real deployment: Portal, ArcGIS Server, Web Adaptors, SSL certificates, Data Store and federation, installed in a controlled order, checked at every step and handed over as a platform the organization’s own staff can run.

ClientMunicipal utility organization
PlatformArcGIS Enterprise 11.4 on Windows Server
ScopeBase deployment, federation, SSL, handover
Evidence9 checkpoints from the project record
The situation

GIS that lived on individual desktops

The organization managed critical infrastructure data in file-based workflows built up over years of desktop GIS use. Data lived in personal folders, sharing meant emailing files, and there was no secure web access for field crews or leadership.

They needed a central platform built properly, on their own servers, by someone who had done it before.

No single source of truth

Layers duplicated across machines and drives, with no way to know which version was current.

No secure sharing

No HTTPS portal for maps and apps that field crews, engineers or leadership could sign in to.

No path forward

Dashboards, field apps and the Utility Network all need an Enterprise foundation that did not exist.

What we built

One federated platform behind one secure address

Users get a single HTTPS address. Behind it, IIS Web Adaptors route traffic to Portal for identity and sharing and to ArcGIS Server for GIS services, with ArcGIS Data Store supporting hosted layers. The diagram shows data moving through the platform we delivered.

Field Maps · Survey123crews in the fieldArcGIS Proanalysts and editorsDashboards · web appsleadership and publicIIS · Web AdaptorsSSL · one HTTPS addressFEDERATED ENTERPRISE 11.4Portalidentity · sharingArcGIS Serverservices · hostingData Storehosted layersBUILD RECORD · 9 CHECKPOINTSPortal · Server · Web Adaptors · SSL · Data Store · federation · validation
The build record

Nine checkpoints, each with proof

Every deployment leaves a record: what was configured, which account or URL was used, and which check proved the environment was ready for the next step.

01Deployment repository built with installers, licenses and a fixed install orderVerified
02Portal service account created and permissionedVerified
03Portal site created and first administrator signed inVerified
04Web Adaptor registered for Portal behind IISVerified
05ArcGIS Server site configured in Server ManagerVerified
06SSL certificates issued and bound for trusted HTTPSVerified
07Server federated with Portal and set as hosting serverVerified
08ArcGIS Data Store registered for hosted layersVerified
09End-to-end validation of every route, role and componentVerified
Checkpoint 03: Portal site creation summary.
Checkpoint 03: Portal site creation summary.
Checkpoint 05: ArcGIS Server Manager.
Checkpoint 05: ArcGIS Server Manager.
Checkpoint 07: federating Server with Portal.
Checkpoint 07: federating Server with Portal.
Checkpoint 06: SSL certificates bound in the Portal administrator directory.
Checkpoint 06: SSL certificates bound in the Portal administrator directory.
Checkpoint 08: Data Store configuration wizard.
Checkpoint 08: Data Store configuration wizard.
Delivered: the organization’s Portal settings, ready for staff.
Delivered: the organization’s Portal settings, ready for staff.
Outcome

A platform their own staff can run

Staff sign in over trusted HTTPS

No ports in the URL, no browser warnings, one address for everything.

Analysts publish to one platform

Hosted layers, services and web maps live in a managed environment instead of on desktops.

The IT team can run it

The build record and runbook mean upgrades and troubleshooting do not depend on us.

Ready to talk about your GIS?

Tell us what you are working on. We reply with questions first, then a written scope and a price.