nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

UPDM 2018 Ausgabe

Tom DeWitte

<\/HEAD>

Dies ist die offizielle Veröffentlichung der 2018 Ausgabe des Utility and Pipeline Data Model (UPDM).<\/P>

<\/P>

Es ist darauf ausgelegt, das Datenmanagement für die Erdgas- und Gefahrgutflüssigkeiten-Industrien zu unterstützen. Die Unterstützung der vielfältigen Anforderungen dieser Branchen bedeutet die Unterstützung mehrerer Implementierungsmuster. Insbesondere eine Netzwerktopologie mit dem Utility Network Implementierungsmuster und ein lineares Referenzierungsmuster mit der ArcGIS Pipeline Referencing Lösung..<\/SPAN><\/P><\/P>Wenn Sie Fragen haben, stellen Sie diese bitte in geonet, damit alle die Informationen sehen und teilen können.<\/P><\/P>Vielen Dank<\/P>Tom DeWitte<\/P>Esri Technischer Leiter 11 Natural Gas Industry<\/SPAN><\/P><\/BODY><\/HTML>

Finde mehr Beiträge mit dem Tag

Gas

Pipeline

Kommentare

Cristian_Galindo

Thanks Michael, but my client is requiring 2018 version.

MikeMillerGIS

I would suggest using UPDM 2019. All of the components have been merged into the Asset Package. The Change Asset Package Spatial reference tool will create you an empty copy of the model and adjust the spatial reference.

Cristian_Galindo

I decided to create an instance of UPDM 2018 using the python scripts provided in the zip file.

My first attempt was to use the script C:\temp\UPDM_2018\PythonScripts\01CreateUPDMBaseAdd-On_2018.py

I keep receiving an error that states:

ERROR 000732: Input Table: Dataset U:\Documents\ArcGIS\Projects\UPDM2018\lin0228_UPDM2018_SQLAdmin.sde\UPDM2018.DataOwner.PipeSystem\UPDM2018.DataOwner.PipelineAssembly does not exist or is not supported
Failed to execute (AddField).

I check the line that generate the error:

arcpy.management.AddField(UPDMAssembly, "PIPELINEOPERATOR", "TEXT", None, None, 50, "Pipeline Operator", "NULLABLE", "NON_REQUIRED", None)

this line is trying to add a field in a non existing table.

More over, In my ignorance i was thinking that this script will create the tables of UPDM. i was quite shocked when i discovered there is no a single call to:

arcpy.management.CreateTable

Some questions came to my mind:

1. How is the process to create an empty UPDM instance?

2. Is possible to create the empty UPDM just with python?

the readme.txt file states:

IMPORTING THE DATAMODEL:
ESRI ArcGIS technology provides several means for importing a data model.
To make the importation of this model as easy as possible, the model is provided in multiple formats
(10.x File Geodatabase, 10.x XML Workspace export, Python scripts, Esri Asset Package)

I assumed that I can choose one of the several means to import the data model. am I wrong?

rkrisher

Diptesh,

The UPDM 2019 model (posted in a separate thread) adds the ability to model your cp zones as subnetworks in the model. Each test lead of a test point can be set up to be a subnetwork controller for a cp zone then you simply connect the leads up to their corresponding pipes and make sure you're properly modelling the conductivity / insulation lines and equipment in your data.

Thanks,

Robert

Anonymous User

I am working on integration of CP zones in UPDM, do we have ready available feature data class for appending CP zone in UPDM data model.

Thanks

Diptesh

JeffClough

Thanks Tom DeWitte, the information is much appreciated. We are currently working on a Gas Distribution implementation and are targeting UPDM 2019 for the underlying data model. Knowing the revised timelines will allow us to effectively plan its incorporation into our project. The list of major enhancements is a nice bonus - thanks!

Regards,

Jeff

Anonymous User

Tom DeWitte and Esri Team... Thanks for your hard and dedication to this solution. We understand your time is consumed by this project and many other activities at Esri. Your efforts are much appreciated by many users in this community even though some may not display it in this forum.

RichardCitkowicz

Will there be a migration pattern/functionality from 2018 to 2019 UPDM?

Thanks

Rich

Tom DeWitte

Hi Mark,

Quick update on your identification of the need to change the GEOMETRY_RATIO policy on the UPDM_PressureRange domain to DUPLICATE. This correction has been incorporated into UPDM 2019 Edition. Thank you for pointing this out and please keep submiting any additonal issues you find.

Thanks

Tom DeWitte

Technical Lead - Natural Gas Industry

Esri, Inc

Tom DeWitte

Hi Zac,

As of this time there are no training materials for the Utility and Pipeline Data Model. (UPDM). There are Esri provided training courses for the underlying technologies which leverage UPDM. There are multiple courses for learning the Utility Network Management Extension. The "Creating and Managing Utility Networks with ArcGIS" does include gas specific exercises. There are also classes for learning the ArcGIS Pipeline Referencing extensions.

You can find more specific information about Esri training classes on the web site at: https://www.esri.com/training/ If you search on "Utility Network" you will find the classes I mentioned.

Tom DeWitte

Technical Lead - Natural Gas Industry

Esri, Inc

Tom DeWitte

Hi Jeff,

Sorry for the delay in responding. We are actively working on UPDM 2019 Edition. Our current schedule is to have UPDM 2019 documented and posted by the Esri International User Conference in early July.

Major enhancements being implemented with UPDM 2019 are:

1) Migration of the Integrity Feature dataset contents into PipeSystem feature dataset to support combined editing workflow (APR + UN).

2) Simplication of Subnetwork definitions to (Pipe System, Pipe Pressure, Pipe Isolation, Cathodic Protection).

3) Enhanced use of connectivity associations to simplify management of Cathodic Protection system

4) Updating of ASTM F2897 Manufacturer list

5) Various minor bug fixes such as type-os and some corrections to coded domains

Tom DeWitte

Technical Lead - Natural Gas Industry

Esri, Inc

deleted-user-FrOR7qrGn6Op

I haven't seen any, but there is something a Pipeline Referencing tutorial that exists

ZacharyOrdo__GISP

Tom DeWitte‌, in addition to the timeline for UPDM 2019 release, are there any training materials or modules available for UPDM? I couldn't find anything on the ESRI Training Site.

JeffClough

Hi Tom DeWitte‌, is there an updated time frame for the release of UPDM 2019?

Tom DeWitte

Hey Mark,

Thank you so much for catching this. I have noted it on the enhancement list for UPDM.

Please continue to post any other suggestions for improvement to our pipe industries data model.

Thanks

Tom DeWitte

Technical Lead - Natural Gas Industry

Esri, Inc

Tom DeWitte

Hi Wes,

The UPDM 2015 and UPDM 2016 versions of the data model were written for earlier versions of ArcGIS for Pipeline Referencing and the Geometric Network. The UPDM 2018 and upcoming UPDM 2019 versions are written specifically for ArcGIS for Pipeline Referencing 10.6 and higher, and the Utility Network for Gas. Not sure of the specifics of you current and planned deployments of the ArcGIS capabilities. The best practice data models for the Geometric Network and the Utility Network are very different. Would not recommend trying to deploy the Geometric Network on the UPDM versions created to support the Utilty Network. And the software will not support the use of GN specific UPDM versions for Utility Network deployments.

Hope this helps

Tom DeWitte

Technical Lead - Natural Gas Industry

Esri, Inc

MarkCederholm

FYI, here's another heads up in case you haven't spotted it already: the UPDM_PressureRange domain uses GEOMETRY_RATIO for split policy, which doesn't make sense in the context of MAOP. It should be set to DUPLICATE.

BarendNackaerts

Hello,

According the blog of Howard in 2019 there will be a new release of the UPDM with some major changes.

https://www.esri.com/arcgis-blog/products/arcgis-solutions/electric-gas/the-road-ahead-for-the-updm-and-the-gas-utility-network-configuration/

We are in progress of converting our data to the UPDM 2018 but as we understand the codes for groups and types will change to preserved and custom ranges.

Is it already possible to provide the codes for assetgroups and assettypes of the UPDM2019 so we can avoid double migration?

When is this new release scheduled?

Thank you,

Barend

WesHopwood

Are there any resources that describe the migration from one version of UPDM to the next? I have a 2015 UPDM version that I need to add a lot of data to and am considering migrating to 2016 version. I think going to 2016 may be better than jumping all the way to 2018. There seems to be some pretty big changes from 2015 to 2018.

EdwardBlair

Forgot to update this. I must have been using an old, outdated version of the UPDM model. When I re-started from scratch using the Gas Utility Network Service 2.0 and re-loaded my data I was able to set my subnetwork controller.

MarkCederholm

We maintain an ANSI valve rating field in our data model. Is that common enough in the industry to warrant a UPDM device field?

EdwardBlair

Hello -

Am trying to modify a subnetwork controller with no luck. The error message says there is an "expected field [that] was not found or could not be retrieved properly". Is there a way for me to identify the field in question?

Thx,

EdwardBlair

Darris -

Thank you for the suggestion! Pretty much at the same time Hussein offered

a different set of steps that seem to work for me.

Much appreciated,

Anonymous User

I had a similar issue with a new empty feature class published as a feature service. My following notes are from ArcGIS v10.5 and ArcCatalog so adjust as necessary for Pro. In Catalog open the properties for each empty feature class, go to the Spatial extents, it might be 0,0,0,0 or the extents may be smaller than the area you were trying to edit ( your edits may have been outside the extents). You can import an extent from another feature class that is big enough or choose update extents. You will have to stop the service (and possibly disconnect all users) to release the edit locks to perform this step.

I suggest you update all extents even non-empty feature classes while you are in there.

PaulLeBlanc1

Yes, I can see the images.

Correct, the layers would be empty -- you should be able to add this to a new map without error.

This is probably better suited as a different post since we're beyond UPDM troubleshooting at this point.

EdwardBlair

Paul -

Thanks for the feedback. Updated the images in previous post. Hopefully they show up now.

If I just publish a brand new UN without the UPDM package the layers would be empty, true? So you're suggesting to test whether the empty feature service layer would show up?

PaulLeBlanc1

Ed,

I cannot see any of your pictures (they appear to be hosted in GMail?). Based on what you described, nothing seems out of the ordinary.

If you create a brand new UN without applying the UPDM asset package and publish the bare bones, do you get the same error?

EdwardBlair

Don't know if this is a question/issue specific to UPDM or if its general to the Utility Network, but going to give it a try. (Tom D - please let me know if I should post elsewhere.)

I've loaded my own sample data into a UPDM 2018-based asset package -- first changing the spatial reference and then appending data to the pipeline feature classes. Validated the network topology and only a handful of topology errors remain. Published map/feature services. Now I can open and edit feature services in the Enterprise "Map Viewer", which I take as a good sign. Here's the feature layer as I see it in Enterprise:

Gas Utility Map Feature Service in Enterprise

And here is the data as displayed in "Map Viewer":

However, when I try to add these services to ArcGIS Pro I get nothing. Examining the server log shows a bunch of "operation was attempted on an empty geometry" errors (below). I've triple checked the source data and there are no features that have an empty geometry. Also, I checked the service and it *is* enabled for the Utility Network (below). Scratching my head here.

- Is Pro sensitive to lines with parametric curves? There was one in the source data. I deleted it and still get these errors.

- The database is SQL*Server 2017. Is there something about geometry data storage in this database that Pro doesn't like?

- Some features have no data - StructureJunctions, for example. Does Pro not like this?

- There is one table in the map service - its part of the Utility Network and called ValveInspection. Is this an issue?

- Is there something about the coordinate system? My data is in UTM meters - UTM 1983 Zone 16N. I usually attempt to add data to an empty ArcGIS Pro map, and the map seems to take on the coordinate system of my data. I've also tried changing the map coordinate system to the data coordinate system before adding it. Same results.

- I'm getting my ArcGIS Pro license from ArcGIS Online but my portal in on the local test machine I've set up - would this be an issue?

Any pointers would be appreciated.

Error on empty geometry

WhiteWaterMidstream

Tom,

Pipeline commodity is actually a complicated question as different entities use slightly different descriptions. I did a little bit of research on the subject and have come up with a good list of commodity types which would work for UPDM. Please see attached table of recommended attribution. In the database I would propose handling this subject with 2 columns, COMMODITY & COMMODITYTYPE.

I use Pipeline Line feature class to store information on pipe material specification. Having the commodity column there is good but I think also necessary for all the key features such as assembly, device, junction, structure boundary, structure line. In the pipeline model it is very useful to be able to query systems by commodity as they are typically separate and distinct systems. If you would like to discuss in more detail please email me direct at lee@wwm-llc.com.

Tom DeWitte

Hi Lee,

The UPDM 2018 Edition already has an attribute named "COMMODITY" on the PIPELINELINES featureclass in the PipeSystem feature dataset. It has a subtype specific coded domain assigned to the Subtypes: Service Pipe, Distribution Pipe, Transmission Pipe, Gathering Pipe, Station Pipe, Customer Pipe, Riser Pipe. The values in the coded domain are: Natural Gas, Synthetic Gas, Hydrogen Gas, Propane Gas, Landfill Gas, Petroleum, Gasoline, Diesel, Water, Wastewater, Steam.

Should this attribute be added to other assets, such as Devices or Junctions? Or is the pipe feature the only featureclass that needs this descriptor?

When I compared your list in your message, I see you listed the following that I did not have in my list: Crude Oil, Natural Gas Liquids, Refined Products, Liquid Petroleum Gas, CO2, Highly Volatile Liquid, Other Gas, Other Liquid. Is this a complete list? Another question. Some of your items are generic classifications, should be list be restricted to specific types of gas and liquids?

Appreciate hearing your thoughts and the thoughts of anyone else who wished to add input.

Thanks

Tom DeWitte

Technical Lead - Natural Gas Industry

Esri, Inc

Nehmen Sie an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registrieren Sie ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.