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!