Units in Solution Center

Component Types are available in Solution Center that represent non-spatial Units.

These Component Types all end with the word ‘Unit’ in the name (for example, BreakerUnit, FuseUnit, TransformerUnit, etc.) with the exception of ConductorInfo records. ConductInfo should continue to map to the Conductor Component Type.

IMPORTANT: The required field mappings are in the ArcFM Configuration for the Utility Network Whitepaper > Unbalanced Equipment Modeling section.

Auto-Generated Units

When an extract of a subnetwork contains Banks without Units, Feeder Services auto-generates these units without including them in network connectivity.

This situation arises in Balanced models that do not create or track Unit resources in the GIS. Units are required in GRRs for both Designer XI and ADMS implementations, as they contain the spec reference information, while Banks do not.

If there is a Feature to Spec Mapping configured for a given Bank, the mapped spec is used to generate the Units. The number of Units that are generated depend on the PhaseCount of the spec and the number of phases present on the Bank. In other words, a three-phase Bank mapped to a three-phase spec results in a single, three-phase Unit. Conversely, a three-phase Bank mapped to a single-phase spec results in three, single-phase Units, one for each phase.

When Units are auto-generated, a property is added to the Unit’s underlying attributes in the GRR indicating this.

Units and Possible Data Errors

These are two common errors relating to the status of the GIS data:

Missing Units in the export that are referenced in containment associations.
Phase mismatch between Banks and Units.

Missing Units

If the subnetwork extract does not contain the elements for the non-spatial objects that are referenced in containment associations, the GRR generation process stops processing the subnetwork and provides the Global ID of the missing Unit.

The GRR creation process does not attempt to create the missing Unit.
To resolve, you should troubleshoot the issue at the GIS level and properly update the subnetwork before attempting to create another GRR.

Phase Mismatch

If the application detects a phase mismatch between the Bank and its Units, it presents an error stating as such. Further, it provides the “ComponenentType” for the Bank and Units along with the Global IDs of the mismatches.

You receive an error message in the GRR metadata noting the phase mismatch, and it instructs you to check the logs for more information.
The application attempts to process every Bank and Unit to determine every case where this situation occurs before stopping the GRR creation.