Skip navigation

GIS Products

2 Posts authored by: Juul Dijkstra

Wow, I feel like the Esri UC just ended, and here's GeoConX on the horizon! The last couple of weeks have been exciting in regards to ArcGIS Pro, the Utility Network, and especially ArcFM Editor XI. Here is what I witnessed:

  • Converting an ArcFM database to the Utility Network - I have seen first hand what this takes
  • Testing ArcFM Phase Tracing on a customers Utility Network
  • Extending the Esri UN data model with the ArcFM XI data model

 

I can tell you one thing for certain: the Utility Network is quite extensive with a ton of built-in functionality. From my understanding, containment and association {for example} are similar to a graph-type database approach. Being offered as a service endpoint means that any client application built for the Utility Network can consume its service. Naturally, I'm thinking ArcGIS Pro here.

 

I believe that the current and most thought provoking conversations involve the data migration process. Questions to be considered are:

  • How is my schema going to change?
  • How are some of my related records going to be migrated to spatial features?
  • How is my connectivity model going to be configured?
  • How is my organization going to be trained to use this new functionality?
  • How do we plan for such a large-scale endeavor?

 

Well, Schneider Electric is here and wanting to help. We are working closely with Esri to truly understand what it means for an ArcFM customer to migrate to ArcFM Editor XI and the Utility Network. This knowledge does not stay with product development but gets propagated to prepare our services and support teams. While the Utility Network has not officially been released, we are planning to release an alpha of ArcFM Editor XI, in addition to our sample data. This will help you give another migration perspective and try out ArcFM Editor XI along side it.

 

One question you might have is, how is Schneider Electric doing this?

 

In short, we are extending the core Esri Utility Network model with our industry experienced data model and capabilities.

 

Okay, why?

  • Common schema
  • Custom data model maintenance prevention
  • Utility Standard adherence (UPDM - Utility and Pipeline Data Model)

 

Furthermore, we are building this extension as an asset package that can be easily deployed as a Utility Network.

 

Allow me to expand on that just a little. At its core, an asset package will contain all the following information:

  • Domains (including asset types)
  • Feature Classes (along with subtypes {asset groups} and fields)
    • A single feature class for the service territory (network extent)
    • Three feature classes for the structure network
    • Five feature classes per domain (Electric, Gas, Water)
  • Network Property Information Tables, such as Connectivity Rules

 

ArcFM Editor XI extends this asset package to provide you with an:

  • Extended Schema Model (ArcFM Editor XI-specific domain, asset group, field requirements)
  • Extended/Advanced Network Properties

 

The advantage in utilizing an asset package is that it can be loaded into the Utility Network in sequential steps. For example, you can migrate a single feeder or pressure zone from your existing data into a core asset package, or the ArcFM Editor XI extended asset package. Next, if you wanted to continue with another feeder or pressure zone, you could migrate that into the same asset package and subsequently load it into the existing Utility Network. Following this workflow will slowly expand your Utility Network and thus give great insight in reviewing and planning for a full migration.

 

In conclusion, we will be providing the ArcFM Editor XI package that will include the ArcFM Editor XI data model, as well as our own sample data for you to test with. Be sure to stay tuned for more blog posts with further details!

Over the last several weeks and while at the Esri UC, one significant and common question has been at the forefront of my thoughts … it is in regards to using ArcGIS Pro without the Utility Network! I believe people are seeing the possible change management involved when migrating from ArcGIS Desktop and the Geometric Network to ArcGIS Pro and the Utility Network, and are looking into getting prepared early. I have to say, it is exciting for me to learn that customers are willing to test ArcGIS Pro and get a head start on the learning process. However, the follow-up question I receive is, "How, Juul? I’m not ready for the utility network just yet, so is it currently possible to test ArcGIS Pro with my ArcFM data? And If so, how is that achieved?"

 

Well, I have good news for you testers: this is indeed possible!

 

Here are a few methods that can be implemented to do just that:

 

Preferred:

  • Feature Services

Alternative:

  • Direct SDE Connection

 

Before we continue, following are two items that might be beneficial for you to know in regards to ArcGIS Pro:

  1. ArcGIS Pro encourages editing through a feature service.
    • This is true for editing within the Utility Network as well. While direct SDE connections are possible, the Utility Network editing functionality will only be fully supported through a feature service in Portal for ArcGIS, which leads to the next point.
  2. ArcGIS Pro does not contain built-in Geometric Network editing functionality.
    • Direct Geometric Network editing through an SDE connection is not supported within ArcGIS Pro. Instead, ArcGIS Pro’s network tools are completely built around the Utility Network Editing.

 

Acknowledging and understanding those principles are the key to understanding the bridge between the Geometric Network and Utility Network. So, what were those methods I mentioned earlier, specifically in relation to ArcFM?

  1. ArcGIS Pro can view ArcFM data through an SDE Connection.
    • This can be achieved by installing ArcGIS Pro on the same machine that contains ArcGIS Server and either ArcFM Server or ArcFM Object Reader 64bit. Note, though, that this setup is for testing only, and just “works.”  I personally have run some analysis tools, made field changes, and created map packages. In theory, the Object Reader should provide the same viewing experience as in later versions of ArcMap.
  2. ArcGIS Pro can edit ArcFM data through a feature service with ArcFM Server.
    • Feature services with the ArcFM Server Extension are supported within ArcGIS Pro. As with any feature service, all the REST requests from ArcGIS Pro are operated by ArcGIS for Server.

 

What would such a deployment look like?

  1. Create a map (or use an existing Stored Display) with ArcFM data in ArcMap.
  2. Publish it to an ArcGIS Server that contains the ArcFM Server SOE.
  3. Enable the Feature Access and ArcFMMapServer capabilities.
  4. Add the Feature Service to Portal for ArcGIS as an item.
  5. Add it to your ArcGIS Pro project.

 

As a summation to these methods, they do have limitations. For example, your stored displays, snapping configuration, or other familiar tools will not show up within ArcGIS Pro. These methods are only provided to assist you in becoming familiar with ArcGIS Pro. However, I encourage you to try ArcGIS Pro for yourselves. It can be quite fun!

 

As you might have surmised thus far, ArcFM as it is today at 10.2.1d is not going to be the same in ArcGIS Pro. The ArcGIS Pro solution you are going to need is ArcFM Editor XI! It is specifically designed for the Utility Network in ArcGIS Pro to solve utility editing problems. To get a head start, I would encourage you to try and test the Utility Network Beta. Get the requirements (Portal for ArcGIS 10.5 and ArcGIS Pro 1.4) and submit a request to your Esri account manager. From a data perspective, the data migration poses a significant task due to the high fidelity requirements of the Utility Network. Furthermore, from my experience within the support group, I can say that data model requirements will be unique for most of our customers. There will also be configuration required, such as data model mapping, terminals, custom propagators, specific connectivity validation rules, attribute rules, and more. However, once you have migrated a subset (or all) of your data into the Utility Network, all native ArcGIS Pro and future ArcFM Editor XI Tools operate as designed. Furthermore, if you are ready to test with the Utility Network in ArcGIS Pro, we are launching our ArcFM Editor XI Alpha program to collect your feedback. More information will be posted on the Alpha program soon, so stay tuned!

 

Cheers!