Introduction to Electric Utility Network Foundation

Electric Utility Network Foundation can be used to accelerate electric utility network implementations.

It includes a data model that configures ArcGIS Enterprise and the ArcGIS Utility Network to represent electric networks. It deploys foundational services, simplifying the creation of additional web and mobile apps and provides a desktop data editing environment.

Starting with Electric Utility Network Foundation means organizations don't have to spend their time and implementation budget on building custom data models and information products.

Deploy the solution

This ArcGIS solution can be deployed in your ArcGIS organization.

See Deploying a solution for more information.

Requirements

Electric Utility Network Foundation requires the following:

  • ArcGIS Enterprise
  • ArcGIS Pro 2.9 or 3.1(Standard or Advanced)

Information products

Electric Utility Network Foundation includes the following information products:

ItemDescriptionMinimum user type
Electric Utility Network Foundation

A zipped file with an ArcGIS Pro project package with tasks, a configured utility network in a file geodatabase, editor and auditor maps, and an asset package geodatabase

Creator user type with ArcGIS Utility Network user type extension

When you deploy this solution in your ArcGIS organization, you also get an ArcGIS solution item that organizes the key information products and summarizes all the ArcGIS items (applications, forms, projects, maps, feature layers, feature layer views, and so on) included with the solution. The ArcGIS solution item also illustrates any dependencies items have on each other.

Release notes

The following are the release notes:

VersionDescription

2.2

  • Assigned a directional terminal configurations to directional transformers asset types in the ElectricJunctionObject class.

2.1

  • Configured phase propagation for all tiers.
  • A new Utility Data Management Support toolbox to support ArcGIS Pro 2.9 and ArcGIS Pro 3.1.
  • Incorporated nonspatial units into a bank model, which requires less visual detail.
  • Added new generic Asset Types to device classes.
  • Added Transformer Winding Asset Groups to Devices and JunctionObjects.
  • Split Electric Line Conductor Asset Groups into Overhead, Underground and Submersible.
  • Revised Phase Domain and removed bit 8.
  • Updated the data model in the solution to version 5.1. For a full list of updates refer to the change log.

2.0

  • Updated the data model to integrate requirements from the Utility Network Community (UNC) founded by European electric distribution and transmission companies.
  • Rename option added to provide UNC naming convection.
  • Added an additional bit (8-De-energized, Traceable) to support exporting de-energized equipment as part of a subnetwork.
  • Enhanced support for a balanced distribution three phase system.
  • Added support for functional and locational modeling of equipment.
  • Additional attributes to support integration with external systems.
  • Migrated related tables to non-spatial objects.
  • Expanded assets types to include more station located equipment.
  • Updated device asset types to include a voltage class suffix.
  • Changed the name of PhasesCurrent to PhaseChange to more clearly articulate the fields purpose.
  • Revised Network Attributes to improve tracing and subnetwork management.
  • Added new attribute rules, contingent attributes values (CAV) and utility network rules to improve data quality.
  • Increased the granularity of configurations to allow for more focused deployments.
  • Improved the Utility Data Management Support tools.
  • Languages have been removed from the Rename table.
  • The data model in the solution has been updated to version 5.

1.1

  • Name changed from Electric Data Management for ArcGIS Enterprise to Electric Utility Network Foundation.

1.0

  • The first release of Electric Data Management for ArcGIS Enterprise
  • The data model in the solution has been updated to version 4. For a full list of updates, refer to the change log.