Introduction
This guide outlines instructions for configuring ITpipes with ESRI’s ArcGIS platforms, including ArcGIS Pro, ArcGIS Online (AGOL), and ArcGIS Enterprise. The purpose of this design is to publish a feature service that supports geodatabase sync and replica creation, enabling seamless integration with ITpipes CoreVision and FieldVision.
By following this article, organizations can ensure that asset data is displayed accurately within ITpipes, enabling field crews to manage inspections more easily and streamline workflows between the field and the office.
Note: Geodatabase Sync and Replica Creation are required only when integrating a map with FieldVision, since FieldVision workflows depend on offline use. CoreVision integrations do not require replica support.
Supported ESRI Software Versions
- ArcGIS Enterprise: v10.2+
- ArcGIS Server: v10.2.2+
GIS Data Hosting
- ArcGIS Server: On-premise or cloud-hosted data, accessed via token authentication.
- ArcGIS Online (AGOL): Cloud-hosted data accessed via OAuth.
What We Require
- Feature Service URL (ends with /FeatureServer)
- App ID and App Secret
- Portal URL (if your organization is federated)
- We will also need a Viewer User to access the integration. (Username/Password)
In ArcGIS Pro
The following steps are provided as general guidance. ArcGIS configuration is managed by your GIS/IT team or ESRI support. ITpipes Support can confirm requirements but does not administer ArcGIS setups directly
Prepare the Data
- Add all feature classes to one Map Project.
- Enable Global IDs for each layer.
Publish the Feature Service
- Enable Editing.
- Enable Geodatabase Sync.
- Verify each layer in the feature service comes from its own feature class in the geodatabase. This guarantees that every dataset is published as a separate layer with its own data source, which is required for FieldVision replica workflows.
Example:
- Layer 1 – Sewer_Mains (line feature class)
- Layer 2 – Manholes (point feature class)
- Layer 3 – Laterals (line feature class)
In ArcGIS Online (AGOL) / Portal — Obtaining Credentials
- Go to Content, click Developer Credentials, and select OAuth for User Authentication.
- Add your ITpipes URL to the Redirect URL fieldbox + signin-oidc, and then click Next. (Example: https://company.itpipes.com/signin-oidc)
- We can leave the “Multiple” option and add the Feature Service URL to the URL fieldbox underneath.
- Record the generated App ID and App Secret. We can find this in the General Tab within AGOL.
- In the Feature Service General Settings Tab, please turn on these options:
- Enable Editing (We will not edit your GIS data, this is a preventative measure to ensure we can integrate.)
- Enable Sync
NOTE: If your organization is federated, please provide your Portal URL as well. Please provide us a Viewer User account with the Username and Password for the integration.
Integrating with ITpipes
Once the feature service has been configured to these requirements, please share the Feature Service URL, App ID, and Secret with ITpipes.
For federated environments, please also provide the Portal URL and ensure the ITpipes URL is added to the Redirect URL list.
Once we have this information, we’ll set up the map in CoreVision and use the built-in tools to make your workflow easier to manage.