Utility and Pipeline Data Model 2021 is Released

5773
17
12-10-2021 11:57 AM
Labels (2)
TomDeWitte
Esri Regular Contributor
4 17 5,773

UPDM Cover image.png

Utility and Pipeline Data Model 2021 is Released

By Tom DeWitte and Tom Coolidge

Esri’s Utility and Pipeline Data Model (UPDM) 2021 is available now. This release continues Esri’s practice of maintaining a template data model ready “out-of-the-box” to manage natural gas and hazardous liquid pipe system data within an Esri geodatabase. This release includes enhancements to keep up with changes in industry practice, regulatory requirements, and previous implementation feedback.

Gas and Pipeline Enterprise Data Management

For many gas utility and pipeline enterprises, deploying the ArcGIS platform is more than simply loading the UPDM 2021 data model into an enterprise geodatabase. That’s because ArcGIS leverages the concepts of a service-oriented web GIS. It requires additional steps, such as creating an ArcGIS Pro map configured for publishing the data model, publishing of the Pro map to create the required map and feature services and, perhaps, configuring a location referencing system. To help simplify these additional steps performed with UPDM 2021, Esri has embedded UPDM 2021 into a newly renamed ArcGIS for Gas solution. The new solution is called Gas and Pipeline Referencing Utility Network Foundation. This solution provides UPDM 2021, sample data, and an ArcGIS Pro project configured with tasks and performance optimized maps. You can access this solution from the Esri ArcGIS for Gas solution site.

A full data dictionary of UPDM 2021 is available online.

A change log documenting the full list of changes incorporated into UPDM 2021 is also available online.

Enhancements for Managing Cathodic Protection

Interest in leveraging ArcGIS to manage Cathodic Protection (CP) data has grown significantly over the last few years. Recent implementations have shown an interest in modeling a more detailed representation of CP systems. With UPDM 2021, our industry data model now includes models for managing the following CP assets:

  • Linear Anode
  • AC Mitigation Wire
  • Decoupler
  • Grounding Point
  • Cathodic Assembly
  • Grounding Mat

Feedback from Pipeline Implementations

Pipeline implementations of UPDM have been many and varied. These previous implementations have resulted in feedback that has resulted in dozens of adjustments to improve how we model pipeline assets. Two specific enhancements based on previous implementations to highlight are the defining of the attributes “odorized” and “piggable” as Utility Network Network Attributes.

Having “odorized” and “piggable” as Network Attributes provides additional capabilities for leveraging tracing. Tracing is the ability to understand how the components of a pipe system are connected, and how the gas and hazardous liquids flow through the pipe system. With this new template configuration, pipeline operators can trace across their pipe system and see where the “piggable” portion stops when it reaches an asset which is tagged as not piggable. Similarly, planners and engineers can trace to see what portion of their pipe system is “odorized.”                   

Feedback from Gas Utility Implementations

Previous implementations of UPDM in Gas Utilities have also resulted in feedback to help fine-tune the gas and pipeline industry data model. Some of these adjustments include improved modeling of relief valves, flanges, and taps to name a few. Other enhancements include adjustments to the Utility Network rulebase.

What is UPDM

UPDM is a geodatabase data model template for operators of pipe networks in the gas and hazardous liquids industries. UPDM is a moderately normalized data model that explicitly represents each physical component of a gas pipe network from the wellhead to the customer meter, or a hazardous liquids pipe network from the wellhead to the terminal or delivery point, in a single database table object.    

pipe system.png

UPDM is the only industry model which can manage a single representation of the entire pipe system.  For many companies around the world this single data repository aligns well with enterprise practices to vertically integrate business processes and operations. 

Why UPDM

The goal of the Esri UPDM is to make it easier, quicker, and more cost-effective for pipeline operators and gas utilities to implement the ArcGIS platform. The Esri UPDM accomplishes this by freely providing a data model that takes full advantage of the capabilities of the geodatabase. The data model is created and tested with ArcGIS products to ensure that it works. This significantly reduces the complexity, time, and cost to implement a spatially enabled hazardous liquid or gas pipe system data repository.

Looking Forward to UPDM 2022

A wise man once said “change is the only constant.” This is a great quote when thinking about UPDM going forward. The Esri development team will continue to enhance the capabilities of ArcGIS. Industry will continue to evolve its practices. To continue adjusting to industry practices and incorporating new ArcGIS capabilities, UPDM will continue to evolve.  This evolution will help assure gas utilities and pipeline operators that their GIS industry-specific data model is current with their needs.

PLEASE NOTE: The postings on this site are our own and don’t necessarily represent Esri’s position, strategies, or opinions.

     

Tags (3)
17 Comments
DiegoGuidi
New Contributor III

download broken I retried the entire procedure and now it worked

 

JohnHu
by
New Contributor III

Tom,

I noted that UPDM 2021 has domain values for attributes such as lifecyclestatus and commodity type.  We are still in UPDM2019.  How can I find the similar domain codes/values for above attributes ?   Please help.   Thanks.

John Hu

JSchroeder
Esri Contributor

Hi @JohnHu,

Both UPDM 2019 and the latest release, UPDM 2021, have domain codes and values for lifecyclestatus (Pipeline_Lifecycle_Combined) and commodity type (Pipeline_Commodity_Type). If you want to see those values/codes, you can search for those domains in the UPDM File geodatabase. Also, you can look at the Data Dictionary for the current solution and browse or search the feature classes, fields, domains, etc... It is located as a link at the Solution page for Gas and Pipeline Utility Network Foundation.

Further, based on which feature class utilizes these domains, they may be applied at the subtype level (View the subtypes in the file GDB for the feature class to see which domains are applied to which subtypes). For example, PipelineLine has subtypes for Bonding Line and Distribution Pipe, but commodity is only relevant for a line transporting a commodity, so the domain is not applied at the field level (across all subtypes), rather it is applied at the subtype level (so it is only applied for specific subtypes). Hope this helps.

liangxu1234
New Contributor

I want Data Dictionary  of UPDM2021,please help,thanks.

JSchroeder
Esri Contributor

Hi @liangxu1234,

In this blog, if you look below the 2nd paragraph, there is a direct link to the UPDM 2021 dictionary. Right above that link is another link to the solution product page where the documentation also points to the online Data Dictionary. If you want an HTML version of the Data Dictionary, you can deploy the solution to your Online or Enterprise portal, where you can download the solution as a ZIP file. Within the ZIP file is a link to the online Data Dictionary, as well as an HTML version of the Data Dictionary. You will see a folder named 'Data Dictionary' after you extract the contents of the ZIP file. There is a File Geodatabase named UPDM_UtilityNetwork.gdb within the 'Databases' folder of the ZIP file which allows you to fully interact with the data model and Utility Network settings. Finally, there is a Pro Project included in the ZIP which includes a series of tasks that will walk you through the data model and solution in general.

ThomasSchuster
New Contributor

Hi @TomDeWitte@JSchroeder,

thanks again for continuing the development on the Gas Solution, UPDM with APR. I just ran through the tasks to build a UPDM 2021 UN + LRS. Unfortunately I could not pass the 'Enable APR on UPDM' step in my environment.

The error I'm getting is: 'Failed to find required classes for Creating the LRS'. Within the Python Toolbox 'Utility Data Management Support' I see the script is checking for the existence of the required APR core tables (line 1512 to 1515). When I review the FGDB I've created so far, I can't find the 'P_Centerline_Sequence' table. It is present although in my 'AssetPackage.gdb'.

Do you know what could have gone wrong? These are the versions I'm using: 

  • ArcGIS Pro 2.9.2.32739
  • untools 2.9.1
  • Asset Package schema version: 2.71

After having created the 'P_Centerline_Sequence' table by hand (including the editor tracking and global id option) , the task to 'Enable APR on UPDM' did run further, but is stopping with this error now:

Failed to execute. Parameters are not valid.
ERROR 000728: Field engrouteid does not exist within table
ERROR 000728: Field engfromm does not exist within table
ERROR 000728: Field engtom does not exist within table
Failed to execute (ConfigureUtilityNetworkFeatureClass).

I'd expect the 'ConfigureUtilityNetworkFeatureClass' tool is looking for the PipelineLine feature class? If so (after checking) the above fields are missing. At which point in the installation process should these fields be created?

Cheers, Thomas

TomDeWitte
Esri Regular Contributor

Hi Thomas,

The "Gas and Pipeline Referencing Utility Network Foundation" version 2.1 includes the P_Centerline_Sequence table in the Asset Package (as you noted), and in the sample dataset file GDB. Please verify that you are using the current version of the Gas and Pipeline solution.

Assuming you are using the current version, I would then suggest recreating file geodatabase from the Asset package.  

Final comment. The ArcGIS Pipeline Referencing information schema is included with the UPDM data model embedded in the solution.  Please use the "...from existing DataSet" version of the Pipeline Referencing GP Tools to configure your APR instance. These tools are for this situation where the ArcGIS Pipeline Referencing information schema featureclasses and tables already exist in your geodatabase.

Thanks

Tom DeWitte

Esri Technical Lead - Natural Gas Industry 

ThomasSchuster
New Contributor

 

Thanks @TomDeWitte for your quick response. Recreating the File GDB from the Asset Package did solve my issue.

Cheers, Thomas

 

walsher
New Contributor

I am new to this model so forgive my potentially stupid questions:

1.  Are the domain values in Pipeline_Coating_Type the only way to describe your coating?  No manufacturer, product name, thickness, coating applicator, date applied?  i.e. does "14-16 Mils 3M 6352 with 30 Mils 3M 6353 ARO" simply become "FUSION BONDED EPOXY"?

2. Can a user add domain values?

Thanks

 

TomDeWitte
Esri Regular Contributor

The Esri provided Utility and Pipeline Data model represents pipe coating with a single coded value domain. The values in this coded value domain can be changed to the examples you describe.  You can also add additional attributes to the PipelineLine featureclass to describe the coating in greater detail.

Hope this helps

Tom DeWitte

dabercro
New Contributor

I have downloaded the 2021 UPDM package and the PipelineLine feature class is giving me this error.  I have redownloaded and get the same error.  Any thought on why or what I can do to resolve?  

dabercro_0-1653068313227.png

 

AyanPalit
Esri Contributor

@dabercro Perhaps You are using ArcMap/ArcCatalog to review the PipelineLine feature class. UPDM and the related applications of ArcGIS Utility Network and ArcGIS Pipeline Referencing are home-based in ArcGIS Pro. Please use ArcGIS Pro for your review.

ThomasSchuster
New Contributor

Hi, this data model now supporting APR and the UN sounds like a big step forward. I understand that we're able to model our assets from upstream till downstream - just like in the image above. In the scenario APR + UN I understand that all pipes in Pipeline_Line participate in the UN. But not all pipes are managed using APR. E.g. I only want APR to manage my transmission pipelines in the midstream sector. To do so, I only create engineering routes for my transmission pipelines. And here is where my question starts:

The Pipeline_Line feature class has a field 'Joint Number' - which indicates that I can integrate my transmission lines joint by joint (lots of small line geometries). Creating a route (APR) from some  centerlines (up to 100 features within Pipeline_Line) is not a problem. But with my transmission lines having 10.000+ joints, creating an engineering route is becoming a challenge (performance wise).

I've heard that for the UN, the small (joint based) line geometries don't provide any additional value. One line geometry covering my transmission pipeline would be sufficient (and must faster when running traces in UN or running APR tools).

For my example, how would I best keep the performance high and at the same time keep the joint numbers within the data model?

TomDeWitte
Esri Regular Contributor

Hi Thomas,

Really good question on how to optimally leverage the UN with APR. Our Utility and Pipeline Data Model (UPDM) is designed to support three implementation patterns of ArcGIS:

1) Utility Network only

2) Utility Network with ArcGIS Pipeline Referencing

3) ArcGIS Pipeline Referencing Only

The vast majority of the content of UPDM is used the same regardless of implementation pattern. But, there are some portions of UPDM which are implemented differently across the 3 implementation patterns. The P_Centerline featureclass and the joinnumber attribute on PipelineLine are two such examples. JointNumber attribute and P_Centerline featureclass are intended for the APR only implementation pattern where PipelineLine is configured as a line event layer. This APR only configuration uses P_Centerline as the source for line geometries to build routes. 

Maintaining the JointNumber information in a UN + APR or UN Only implementation pattern could be achieved in manner which would not result in PipelineLine being divided into tens of thousands of segments per engineering route.

-Store JointNumber on the PipelineJunction features (welds, fittings, etc). This does not require splitting of the PipelineLine features.

Hope this helps

Tom

Krishna_RaoTVB
New Contributor II

Hi Tom, 

What roles will the creator user require for implementing Utility Network with ArcGIS Pipeline Referencing at Enterprise 11 and Pro 3.0.1?

Any work around for the Viewer to do UN tracing?

 

 

TomDeWitte
Esri Regular Contributor

Hi Krishna,

There are multiple user roles and licensing requirements for deploying administering, editing, tracing and viewing of a Utility Network and ArcGIS Pipeline Referencing configured pipe dataset.

Here are a few of the key licensing requirements:

1) All Utility Network editors require the Utility Network user extension.

2) All Utility Network tracing capabilities require the Utility Network user extension.

3) All route editors of the ArcGIS Pipeline Referencing managed routes will require ArcGIS Pro and a Location Referencing desktop extension license.

4) To publish the Location Referencing capability into a feature service requires the Location Referencing server extension.

Viewers of the Utility Network and/or ArcGIS Pipeline Referencing data itself do NOT require additional licensing. Viewers with the Utility Network user extension license are able to perform Utility Network traces.

I hope this helps

Tom DeWitte

Esri Technical Lead - Natural Gas and District Energy

ThomasSchuster
New Contributor

Hello, the esri solutions team is providing a convenient deployment process for UPDM + UN + APR. This deployment process currently supports ArcGIS Pro 2.9 and Enterprise 10.9.1. Is it planned to provide an updated solution to support current versions of Pro and Enterprise? - @Krishna_RaoTVB already mentioned Enterprise 11 and Pro 3.0.1.

Cheers, Thomas

About the Author
Technical Lead for Natural Gas Industry at Esri
Labels