With the release of Esri's ArcGIS Pipeline Referencing (APR) in early 2017, Memphis Light, Gas & Water (MLGW) identified the extensions as desirable tools to manage their gas transmission assets. The key driver for MLGW was the ability to utilize software within the Esri stack for editing linear referenced pipelines, viewing and reporting. This presentation will focus on MLGW’s APR implementation and include elements around the hardware/software architecture, Utility Pipeline Data Model, data migration across multiple sources, implementation of the Esri software and creation of a viewing/reporting application within Web App Builder.
2. Introductions
Andrew McColgan – Memphis, Light, Gas & Water (MLGW)
Computer Software Specialist
Clarke Wiley – SSP Innovations
Director of Pipeline
3. MLGW – Gas System
• 181 Miles of Transmission/Regulated Pipelines
• Distribution:
• 320,000 Natural
Gas Customers
• 4650 miles in length
• Nearly 40 billion
cubic feet delivered
per year
4. MLGW – Current GIS Environment
• Existing/Prior GIS Architecture:
• Gas Distribution & Gas Transmission
• ArcGIS Gas Distribution Data Model
• Both Distribution and Transmission managed with same
tools/workflows
• Current GIS Environment
• ArcGIS 10.1
• Oracle 11g
5. Project Overview - Transmission
• Consolidation and Migration of Transmission gas assets
into Utility Pipeline Data Model (UPDM)
• Extend UPDM model to accommodate all datasets
• Migration of MAOP Attribution/Documents from SQL
RDBMS Environment
• Migration of existing GIS Transmission assets to UPDM
6. Project Overview - Transmission
Establish new Esri/RDBMS environment
• ArcGIS Desktop 10.5
• ArcGIS Server 10.5
• ArcGIS Pro 2.0
• Oracle 11g
Implementation of ArcGIS Pipeline Referencing Tools
• ArcGIS Pro Extension – Centerline Editing
• ArcGIS Server Extenstion – Web Event Editing
• ArcGIS Desktop Extension – APR Configuration
7. Project Overview - Transmission
Viewing/Reporting
• WebApp Builder
• Out of the Box internal web tool
• Widget Based/Configurable
• Geoprocessing Reporting: PHMSA, %SMYS, NPMS
8. •Benefits:
• Complete 10.5 Esri Architecture Up and Running
• Desktop
• Server
• ArcGIS Pro
• Allows Gas Distribution/GIS/IT to review, evaluate and plan for
next technology phase
• Transmission Data will remain in UPDM model, added
regulatory/editing benefits
• Distribution can start reviewing UPDM model and multi year
planning
Project Overview - Transmission
12. Discovery Overview
• Current GIS State, Data and IS/IT Overview
• GIS Data
• ArcGIS Gas Distribution Data Model
• Electronic Data
• Scanned Documents/Document Management Tools
• Spreadsheets
• Local DBs (GDB, Access)
• Historical Paper Documentation
• Application Review
• Current GIS Data Projects
13. Key Decisions
Utility Pipeline Data Model (UPDM)
• Future data model for all gas assets
• Industry/Esri supported model
Linear Reference Transmission Data
• Source data from ArcGIS Gas Distribution Database
• GPS Survey Data/Centerline Rectification
Load best known attribution and documentation
• MAOP Database/Documents vs GIS
14. GIS – Management
• Single Infrastructure
• Applications and Integrations
• Ability to program and configure against one location
• Streamlined integration points
Standardized Architecture
• Clarity for the User Community
• Regulatory Reporting, Asset Views, Mileage, Summaries
• No need to compare and/or combine data from multiple
locations for reporting
• MAKE OUR GIS A DECISION MAKING TOOL
Why UPDM?
15. Project Overview
Utility Pipeline Data Model
• Schema Extensions, RDMS/SDE &
Database Implementation
Data Migration
• Linearly Reference Transmission (GL-
ID)
• ArcGIS Gas Distribution Model
• Gas Transmission Assets
• PCS – MAOP Document/Attribution
Database 15
16. Project Overview
ArcGIS Pipeline Referencing Implementation
• Centerline Editing Tools – ArcGIS Pro
• Web Event Editing Tools – ArcGIS Server
• Desktop Configuration Tools – ArcGIS
Desktop
17. Project Overview
oBenefits:
• Complete 10.5 Esri Architecture Up and Running
• Desktop, Server & ArcGIS Pro
• Allows Gas Distribution/GIS/IT to review, evaluate and plan for
next technology phase
• Transmission Data will remain in UPDM model and Dist Data
will ultimately be merged
19. Early Adopters
First companies on board, including MLGW, find UPDM
appealing since both the distribution and transmission gas
assets can be stored within the same enterprise
geodatabase
•Operators seeing the benefit of Esri out of the box tools
versus third party software products for core pipeline
management
• ArcGIS Pipeline Referencing – Centerline & Event
Management
• Pro – Distribution
20. Early Adopters
With PODS Next Generation on the horizon and the
perceived jump from APDM to UPDM, we’ve found that
pure transmission operators are road-mapping and
planning prior to making the move
• Integration points to current PODS or APDM model
• Application compatibility (HCA/Class, Risk,
MAOP/MOP and Alignment Sheet Generation)
• Migration and Esri Version Upgrade Planning
22. Data, Data, Data
How are pipeline routes being stored in the new model?
• Past models, stored pipelines and systems in
StationSeries and LineLoop/LineLoopHierarchy tables.
• UPDM…review existing systems hierarchy and make
key decisions for modeling the pipeline LRS networks
Do you still need historical stationing?
• Simply utilize continuous network and manage true
pipeline length/location?
23. Data, Data, Data
Data Mapping Phase
• Example: GasMain -> UPDM.P_Pipes
UPDM Database Extensions
• Where is data duplicated?
• Where can we consolidate?
• Between both source datasets or within the same
• What fields are truly needed to support GIS asset and integrity
management
24. Data, Data, Data
Data Migration
Establish Empty UPDM Schema
• Transmission vs Distribution
• Shared Features (P_Pipes, P_Fittings, P_Valves)
Configure APR
• LRS Networks, LRS Events, Event Response
• Centerline, Routes, Centerline Sequence
25. Data, Data, Data
Don’t discount the APR Toolbox!
• Streamlined Workflows
• GIS Centric
• Makes data loading a non-DBA task
• Append Events (Location Referencing Tools)
• Generate shapes and Event GUIDs
• Add, Retire or Replace
28. APR Architecture
Desktop
ArcMap/ArcCatalog Extension
Create Empty UPDM Schema
LRS Network
Creation/Configuration
LRS Event Creation/Configuration
Event Responses
Route Loading/Generation
Calibration Point
Loading/Updating
Intersection Events
Location Referencing Tools
Centerline/Route Editing
Create, Update, Retire Route
Representations
Bulk Data Loading – GP Models
ArcGIS Server
Web Based Point/Linear Event
(Feature) Editing
Published Map Services
29. Licensing & Deployment
ArcGIS Pro Location Referencing Extension –
• Extension is part of the Pro Install!
• Named User versus Single Use?
• Single Use License: Provision APR as a single use on the same
machine
30. Licensing & Deployment
ArcGIS Pro Location Referencing Extension –
• Named User License: Use Pro License and the APR License
• Much easier to manage/implement
• Use Pro from any machine and utilize named user account for
authentication
31. Centerline & Data Loading
Migrate core features and LRS tables
• Follow Esri Documentation!
• The features/data that are migrated (outside the core) will assume
the LRS Network properties and users can proceed with using the
APR applications.
32. Centerline & Data Loading
Append Events – Location Referencing Toolbox
• Your new best friend!
• Event GUIDs
• Create shapes from source data in a tabular
format
• ROUTEID, M Value (From/To)
• Add, Retire or Replace
• Field Mapping – Visual Representation of
Mapped Columns
33. WebApp Builder
Out of the box Esri App tool
• Widget Based
• Configured to Transmission Needs
• <= 1970 Install Date
• Unknown WT
• Document Links