|
DOC
|
Erica, The data dictionary v1, is approximately 90% consistent with what is being worked on for UPDM 2018 Edition Update 1. Major changes are planned for the tier group definitions, and some minor changes are planned for the PipeSystem Line, Device and Junction featureclasses. The other featureclasses and tables are not being modified. Tom DeWitte Esri Technical Lead - Natural Gas Industry
... View more
02-22-2018
06:50 AM
|
0
|
0
|
28970
|
|
POST
|
Hi Jordan, The intention of the Valves featureclass in the UPDM 2016 Edition was to store all controllable valves regardless of their installation location. But, it is important to remember that UPDM is a data model template, it is not a requirement. Every gas utility has unique data management requirements. If your unique data requirements lead you to conclude that the curb stop valves should be stored in a separate featureclass, then please do that. If you do not have a strong business requirement to separate the distribution main gas valves from the service line curb valves, then my advice would be to keep them in the same featureclass to reduce the number of database queries required on your standard map views every time you pan, zoom or edit. Reducing the number of featureclasses used to store your assets is a proven method for improving map redraw performance and the scalability of your Geodatabase.. Tom DeWitte Esri, Inc Technical Lead - Natural Gas Industry
... View more
02-01-2018
05:58 PM
|
3
|
0
|
1289
|
|
DOC
|
Lee, Prior to reposting, this will be retested. Thanks Tom DeWitte Esri Technical Lead - Natural Gas Industry
... View more
01-23-2018
07:02 AM
|
1
|
0
|
28970
|
|
DOC
|
Juan, Current schedule is to repost UPDM 2018 edition by the end of February. Tom DeWitte Esri Technical Lead - Natural Gas Industry
... View more
01-23-2018
07:00 AM
|
2
|
0
|
28970
|
|
DOC
|
This is the official release of the 2018 Edition of the Utility and Pipeline Data Model (UPDM). It is designed to support data management for the natural gas and hazardous liquids industries. Supporting the diverse needs of these industries means supporting multiple implementation patterns. Specifically a network topology with the Utility Network implementation pattern, and a linear referencing implementation pattern with the ArcGIS Pipeline Referencing solution.. If you have questions, please post them to geonet, so everyone can see and share the information. Thank you Tom DeWitte Esri Technical Lead – Natural Gas Industry
... View more
01-04-2018
07:38 PM
|
13
|
69
|
55282
|
|
BLOG
|
Gas Network Complex Facilities Can Be More Fully Defined in the Utility Network By Tom Coolidge and Tom DeWitte What if it is really greater goodness that is to be found in having the details of your complex gas network components consolidated in one system of record along with other network data? Think about the improvements to efficiency and productivity that can result when you have all needed data organized in one place and included in your network models. Yes, it’s your angel that we believe lies ahead in the consolidated details. That angel can help you more fully realize the benefits available to you by unlocking the potential of the ArcGIS platform. Bringing data from disparate sources together on a common geographic basis for visualization and analysis is one of the hallmarks of the Web GIS pattern exemplified by the capabilities of the ArcGIS platform. Increasingly, though, while this advance means that they do not have to, many gas utilities are looking to move a broader range of data now stored elsewhere into today’s modern ArcGIS platform. Historically, data has been siloed in different systems for many reasons. In the case of detailed data needed to define complex gas components, one of those is that GIS did not provide the functionality needed to define and store that detailed data. That is changing now. This has many benefits for gas utilities. Among those are making it easier to see a holistic view of the network in whatever level of detail is desired and to analyze it, and facilitating interoperation with other application software that rely upon a published definition of the detailed network. At the same time, it reduces the total cost of ownership by consolidating into one system of record what previously was in multiple systems. In a sense, this advance brings GIS closer to operating just as you operate. That brings us to the Utility Network. One of the Utility Network capabilities getting the most buzz is the capability to more fully define and manage, in real geographic space, the design and operational details of complex gas components, such as regulator stations and compressor stations. The Utility Network opens up new capabilities in leveraging these details to better understand and operate your gas system. Rest Easy Before we explore this new capability, let us quickly emphasize that the capability to more fully define complex components does not mean that you ever must! So, rest easy. The choice is yours as to whether you elect to take advantage of the new capability and, if you do, when and to what extent. Moreover, if you do elect to add more detail, you can do it incrementally if you wish, rather than in one big project. Before Now Before the release of the Utility Network, complex gas components typically were represented in ArcGIS as a point feature. Historically, CAD software often has been used to create precision drawings of gas network complex components. With CAD, what you see is basically what you get – just a picture, not usable data. ArcGIS delivers much more. You still can see the same thing, but what you see is just a representation of the data behind it which you can use in many powerful ways. Now instead of looking at a picture of the internals of a gas facilities you can interact and ask questions of the gas facility details. What kind of questions might you be asking of the details? In an emergency operation instead of an isolation trace stopping at the simple representation of a gas facility such as a regulator station, it can now identify the specific critical valves within the facility which need to be closed. If a recall is issued for a specific manufacturer device or fitting, and that device or fitting was installed within a gas facility, those gas facility components can now be identified and reported. Answering these types of questions is not possible when the gas facility internals are just a picture. How Much Detail We increasingly are asked how detailed should the definition in ArcGIS be of a gas network? There is no one answer to that question. With the ArcGIS platform increasingly supporting the mapping and spatial analytics needs of a growing number of users in a broader range of gas utility functional areas and roles, the answer to that question is evolving. Here is one way to look at it. The answer to what needs to go into your geodatabase largely depends on what you want to get out of it. That is because each software application has its own specific data requirements. If you want your geodatabase to support one application, then only that application’s data requirements need to be accommodated. If you want your geodatabase to support two applications, then the data requirements of both need to be accommodated. And, so on. While some applications share data requirements, generally as the number of applications to be supported increases, so, too, does the breadth and depth of data requirements. The key to your answer lies in understanding the number of applications to be supported and their combined data requirements. Remember the title of this blog, “Your Angel Is In The Details?” As a rule, erring on the side of more detail is a good thing. It is easier to simplify a more detailed definition than it is to add detail to less detailed one. An Example One of the functional areas now more fully exploiting ArcGIS capabilities is gas operations. Analytics for gas operations often require more granular data than analytics for other functional areas. Let’s consider regulator stations. Gas networks typically include multiple sub-networks, each operating at up to a different maximum pressure, with pipe sizes and maximum pressures reducing the closer gas gets to delivery points. Regulators control the safe reduction of pressure or flow from a higher pressure sub-network to a lower one. A regulator station can be simple, with a single regulator on a single path. Or it can very complex, with multiple regulators and other devices on multiple paths. It also likely contains safety devices. These safety devices may include additional regulators, relief valves, and remote monitoring equipment. In ArcGIS, a regulator station traditionally has been defined as a point feature. In reality, a regulator station is a complex facility. Now, in the Utility Network you can define those design and operational details. Technical Discussion Since gas systems were originally mapped in a GIS several decades ago, GIS professionals have struggled to get the balance right between needed detail and desired cartography. One example of this struggle is the need to manage geographically condensed features like those contained within a gas facility. These details can create very cluttered and hard-to-understand map displays. As already stated, these details need to be more than just a picture. They need to be asset records. These asset records need to be spatially reportable so gas companies know where gas devices and fittings are located. Then, add to these gas facility data management requirements the gas operations requirement that these gas facility details be traceable. This is to aid gas ops staff during emergency operations to not only know that a valve in a gas facility needs to be closed, but to identify which critical valve(s) in the gas facility need to be closed. The solution to these problems is the new Utility Network and its container capability. So what is a container A container is an association between the individual features representing the assets internal to a gas facility with the single point feature representation of the gas facility. Once the container association has been established, the contained assets are hidden from the standard map display. Similar to the legacy picture representation, users are able to click on the simple gas facility representation and see the internals of the gas facility in a separate map window. What reporting can I do The assets contained within a container are geospatial features stored in geodatabase featureclasses. Standard database reporting tools, whether ArcGIS-based or Business Intelligence-based can be used to query, summarize and report these on features. But, what about spatially querying these featureclasses with a standard ArcGIS tool like “Select Features by Location”? This is an additional type of supported reporting, because the Utility Network provides the ability to precisely place the internal assets at their true geographic location within the gas facility. This is a key point, so let me repeat. Internal assets are placed at their true geographic location! Can I trace these gas facility assets With the Utility Network, all container contained assets participate in the overall pipe system’s network topology. This means, for instance, that during a gas emergency operation, an isolation trace task can be performed to identify the critical valves within the gas facility which need to be closed for the emergency. This improvement in modeling complex gas facilities additionally provides a better understanding of cathodic protection areas, pressure zones, and system zones. The Utility Network Management extension container capabilities provides a solution to the gas industries growing needs for better management of the details of gas facilities. This ability to manage gas facility internal assets as features instead of pictures, allows gas organizations to provide clear and concise maps, without sacrificing the ability to model individual assets. Containers provide the angel that gas organizations have been looking for to solve the problem of managing a gas facilities details. PLEASE NOTE: The postings on this site are my own and don’t necessarily represent Esri’s position, strategies, or opinions.
... View more
11-08-2017
10:49 AM
|
4
|
0
|
3557
|
|
DOC
|
Hi Jordan, You can reach me via my esri email account: tdewitte@esri.com Tom
... View more
11-02-2017
05:17 PM
|
0
|
0
|
4780
|
|
DOC
|
Amy, There are no plans at this time to include a set of logical diagram posters with the UPDM 2016 edition or the upcoming 2017 edition. Tom DeWitte | Technical Lead – Natural Gas Industry ESRI | 880 Blue Gentian Road, Suite 200 | Eagan, MN 55121 Phone: 651.454.0600 |email: tdewitte@esri.com<mailto:tdewitte@esri.com> | www.esri.com<http://www.esri.com/>
... View more
10-04-2017
09:11 PM
|
0
|
0
|
6310
|
|
DOC
|
For the latest updates to the UPDM 2016 version, please download this release. The zip file includes: Change Log Data Dictionary File Geodatabase of the UPDM schema To learn more about the Utility and Pipeline Data Model, please reference the ArcGIS for Gas solution site.
... View more
09-13-2017
03:43 PM
|
2
|
1
|
6299
|
|
DOC
|
Hello Keith, No logical diagram was included with the latest version of UPDM 2016 Edition. We are still looking for the right tool which can generate a logical diagram from a geodatabase. Tom DeWitte Esri, Inc Technical Lead for Natural Gas Industry
... View more
07-21-2017
01:36 PM
|
0
|
0
|
6310
|
|
DOC
|
Hello Karin, My name is Tom DeWitte. I am the technical lead for the natural gas industry at Esri and the curator of the Utility and Pipeline Data Model (UPDM). First I should state that APDM has been retired. UPDM is now the recommended data model for managing pipe within a geodatabase. Below is a list of a few of the principal differences between UPDM and APDM. -UPDM is Esri's current "best practice" representation on how to manage pipe data within an Esri Geodatabase. -UPDM is updated annually to keep up with changes in technology and regulations. APDM has not been updated for several years, as it has been retired. -APDM did not base its relationship classes on GlobalID. In order to support offline caching of data with the Collector application all featureclasses, tables and relationships must be based on the GlobalID field. I hope this helps. Tom DeWitte Esri Technical Lead for Natural Gas Industry email: tdewitte@esri.com
... View more
07-13-2017
05:47 AM
|
0
|
0
|
6310
|
|
POST
|
Jack and Travis, To Travis's question, I would not recommend that you redo your gas data model just to better support connectivity rules in the Geometric Network. If you goal is to "clean-up" your data in preparation of the end of year release of the Network Management tools (formerly called Utility Network), than I would suggest you focus your efforts on deploying the Data Reviewer extension. These tools not only identify inconsistencies in your data, they also document those issues so you have a list from which to begin cleaning up your data. To Jack's question. The UPDM is designed to support both Network Topology (ie. Geometric Network) and linear referencing (ie. ArcGIS Pipeline Referencing). There are multiple options on how to configure these two technologies, as well as multiple workflows to maintain these two approaches to data entry/data management. There is ongoing efforts within Esri to improve the capabilities of these two technologies to work in a more streamlined workflow. These efforts are focused around the ArcGIS Pipeline Referencing solution and the upcoming Network Management tools (formerly called Utility Network). Tom DeWitte Esri, Inc, Technical Lead - Natural Gas Industry
... View more
06-15-2017
05:35 AM
|
2
|
1
|
1684
|
|
DOC
|
Tracking and Traceability Deployment pattern zip file. Contains Barcode decode GP Tool and MXD's to help with publishing the overall solution.
... View more
12-06-2016
04:41 PM
|
0
|
8
|
6583
|
|
POST
|
Robert, Thank you for the quick response. That was exactly what I needed. Adding the following property to my Input parameter fixed my calendar picker. defaultvalue="05/01/2011" Thanks Again T DeWitte
... View more
08-12-2011
01:12 PM
|
0
|
0
|
391
|
|
POST
|
I too am working with the geoprocessing widget and have had some initial success. But, when my input parameter is a "DATE" field the Flex geoprocessing window provides a Calendar date picker which I am required to use. Unfortunately the calendar starts in the year "00". How can I set this calendar date picker to start with a date that is actually in my lifetime? Thanks T DeWitte
... View more
08-11-2011
05:54 PM
|
0
|
0
|
391
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | 3 weeks ago | |
| 1 | a month ago | |
| 1 | a month ago | |
| 1 | 08-29-2025 07:41 AM | |
| 1 | 02-14-2025 12:29 PM |
| Online Status |
Offline
|
| Date Last Visited |
yesterday
|