ADMS Implementation Requirements

A detailed and high-fidelity spec catalog is required to integrate your GIS with an Advanced Distribution Management System (ADMS). It is not recommended to store as many ADMS fields directly within the GIS. Storing a majority of ADMS fields within the GIS convolutes the data model, and makes it harder to maintain the complicated attributes for all the electric features. This can lead to data inaccuracies in the ADMS and makes its function less valuable and can degrade the performance of the GIS over time. Instead, the spec should maintain the ADMS attributes, and the GIS should maintain attributes for spec matching, in addition to other attributes normally captured.

When you create  Geodatabase Regions (GRRs), the GRR extract file contains the collection of specs that map to each extracted feature. The ADMS can then reference the specs included in the GRR to populate ADMS fields. The implementation team helps identify and map these crucial fields. There is also a Feature to Spec Mapping tool  interface to track your spec matches.

Building out a high-fidelity spec catalog increases implementation time and resources spent, but placing the bulk of ADMS fields within the spec provides more electrically accurate data, minimizes the use of default values, and allows editors and designers to focus on the attributes they know best.

Lifecycle Status in Tier Subnetwork Trace Configuration

Required Configuration

Subnetwork tier definitions that use Lifecycle Status as a barrier must either exclude each planned state as barriers or exclude lifecycle status use as a barrier. This makes sure that features with planned states are traced as part of the subnetwork and can be reliably exported through Feeder Services to ADMS.

Non-ArcFM Designer ADMS Customers Requirements

Non-ArcFM Designer customers intending to deploy an SE ADMS need to apply the following changes to their GIS Schema.

Field Model Name	Applicable to Asset Type Name	Field Data Type	Description
Lifecycle Status	All	Short	Lifecycle status of the component that describes installation status of the component (i.e. In Service, Abandoned, Planned Installed). For ADMS: This field supports ADMS planning functionality. The domain on this field should be used to drive the ADMS planning state changes through designs or updates directly in the GIS.

Field Model Name

Applicable to Asset Type Name

Field Data Type

Description

Lifecycle Status

All

Short

Lifecycle status of the component that describes installation status of the component (i.e. In Service, Abandoned, Planned Installed).

For ADMS: This field supports ADMS planning functionality. The domain on this field should be used to drive the ADMS planning state changes through designs or updates directly in the GIS.

ADMS Planning States

State	Description
Decommissioned	The object is permanently out of service. Use of this state is purely optional, for utilities that prefer modeling such equipment in GIS and having it in ADMS for safety reasons.
InService	The object is in service and is not planned to be altered.
PlannedInstalled	The object is planned to be installed in an upcoming period.
PlannedUninstalled	The object is in service but is planned to be removed (uninstalled) in the upcoming period.

Additional Field Requirements for ADMS

ADMS will require fields for these different fields and should not be used in feature to spec mappings, but should be part of the Geodatabase Region Resource for each type specified.

Field Model Name	Applicable to Feature Name	Field Data Type	Description
AOR Group	Devices, Junction Object Structure Boundaries	Text	Area of Responsibility; defines which operator has control/preview capability.
Description	All	Text	The description is a free human readable text describing or naming the object. It may be non-unique and may not correlate to a naming hierarchy.

Field Model Name

Applicable to Feature Name

Field Data Type

Description

AOR Group

Devices, Junction Object

Structure Boundaries

Text

Area of Responsibility; defines which operator has control/preview capability.

Description

All

Text

The description is a free human readable text describing or naming the object. It may be non-unique and may not correlate to a naming hierarchy.

Feature to Spec Mapping Tips

The following tables provide tips and guidelines to map GIS features to specs. While not every attribute in each table is required to map features to specs, if you include each field model name in your GIS with proper data, the spec mapping is well defined. The names of each field model name can be modified in the customer data, but the Field Model Name and Description should be used as a guide so the implementor chooses the proper field in the data during the ‘Feature to Spec’ mapping exercise.

Information Derived from Data

The following table describes properties on a set of specs that are not one to one mappable to fields in the GIS, according to the ArcFM UN field specifications. The left column states the spec resource type separated by colons and the property name. The suggested methods column describes approaches that have helped derive this data. Notes describes what each property in the spec is.

SpecType:Spec Property	Suggested Methods	Notes
FuseSpec::GangOperated SwitchSpec::GangOperated BreakerSpec::GangOperated	Single, three phase unit -> GangOperated is True Three, Single phase units -> GangOperated is false (unless otherwise specified) Use a field on the device that states whether it is Gang Operable.	GangOperated describes whether the units contained within the device always share the same device status. When false, each unit can be operated independently of the others.
TransformerSpec::TransformerType	Derive from asset type or network category	Transformer specs control the types using a domain that specifies whether the transformer is ‘Overhead’, ‘Padmounted’, ‘Submersible’, or is a ‘Network’ transformer. A type of ‘Unknown’ is also supported within the spec.

SpecType:Spec Property

Suggested Methods

Notes

FuseSpec::GangOperated

SwitchSpec::GangOperated

BreakerSpec::GangOperated

Single, three phase unit -> GangOperated is True
Three, Single phase units -> GangOperated is false (unless otherwise specified)
Use a field on the device that states whether it is Gang Operable.

GangOperated describes whether the units contained within the device always share the same device status. When false, each unit can be operated independently of the others.

TransformerSpec::TransformerType

Derive from asset type or network category

Transformer specs control the types using a domain that specifies whether the transformer is ‘Overhead’, ‘Padmounted’, ‘Submersible’, or is a ‘Network’ transformer.

A type of ‘Unknown’ is also supported within the spec.

Suggested Fields for Meaningful Feature to Spec Mappings

Conductors and Neutrals Electric Line Feature Class

Field Model Name	Field Data Type	Spec Property	Description
ConductorSize NeutralConductorSize	Short or Long Integer	Cross Section	Domain lookup code for the nominal diameter of the conductive material.
ConductorMaterial NeutralConductorMaterial	Short or Long Integer	Material	Domain lookup code for the conductive material.
PhasesNormal	Short or Long Integer	Phase Count	Represents the built phases on the conductor. Count of phases should be obtained from counting the phases in the description where an ‘A’ phase conductor would have a phase count of 1. Note: Alternatively, ‘NumPhasesBuilt’ can be used to set the phase count for the feature to spec mapping.
NeutralType	Short or Long Integer	Has Neutral	Domain lookup code describing the neutral conductor. The Spec property expects ‘True’ or ‘False’, if the recommended domain is applied ‘0’ should translate to ‘False’ and ‘1’ or ‘3’ should translate to ‘True’.
IsNeutral	Short or Long Integer	N/A	Domain lookup code to indicate whether this is a neutral conductor. 0 = “No” 1 = “Yes” Note: This field does not map to any Spec properties but can be used to help diffretiate between mapping to Neutral or Conductor Specs.

Non-Load Breaking Switches (Electric Device and Electric Junction Object Feature Classes)

Field Model Name	Field Data Type	Spec Property	Description
RatedCurrent	Integer	Rated Current	Current rating in amps
PhasesNormal	Integer	Phase Count	Represents the built phases on the conductor. Count of phases should be obtained from counting the phases in the description where an ‘A’ phase conductor would have a phase count of 1.
Manufacturer	Text or Integer	Manufacturer	Name of the manufacturer that produced the equipment.
Model	Text or Integer	Model	Model of the equipment.

Load Breaking Switches [Breakers, Load Break Switches, Reclosers] (Electric Device and Electric Junction Object Feature Classes)

Field Model Name	Field Data Type	Spec Property	Description
RatedCurrent	Short or Long Integer	Rated Current	Current rating in amps
PhasesNormal	Short or Long Integer	Phase Count	Represents the built phases on the conductor. Count of phases should be obtained from counting the phases in the description where an ‘A’ phase conductor would have a phase count of 1.
MaxInterruptingAmps	Short or Long Integer	Breaking Current	Maximum current in amps that the switch can safely interrupt
Manufacturer	Text or Coded Value Domain	Manufacturer	Name of the manufacturer that produced the equipment. Note: If using a coded value domain, the description should be used to determine the proper spec during the feature to spec mapping process.
Model	Text or Coded Value Domain	Model	Model of the equipment. Note: If using a coded value domain, the description should be used to determine the proper spec during the feature to spec mapping process.

Fuses (Electric Device and Electric Junction Object Feature Classes)

Field Model Name	Field Data Type	Spec Property	Description
RatedCurrent	Short or Long Integer	Rated Current	Current rating in amps
PhasesNormal	Short or Long Integer	Phase Count	Represents the built phases on the conductor. Count of phases should be obtained from counting the phases in the description where an ‘A’ phase conductor would have a phase count of 1.
MaxInterruptingAmps	Short or Long Integer	Breaking Current	Maximum current in amps that the switch can safely interrupt
Manufacturer	Text or Coded Value Domain	Manufacturer	Name of the manufacturer that produced the equipment. Note: If using a coded value domain, the description should be used to determine the proper spec during the feature to spec mapping process.
Model	Text or Coded Value Domain	Model	Model of the equipment. Note: If using a coded value domain, the description should be used to determine the proper spec during the feature to spec mapping process
FuseLinkType	Short or Long Integer	Fuse Type	Coded Value Domain that maps to different fuse link types, i.e. ‘N’ or ‘K’ type fuses.

Transformers (Electric Device and Electric Junction Object Feature Classes)

Field Model Name	Field Data Type	Spec Property	Description
RatedPower	Short or Long Integer	Rated Power in VA (volt-amperes) (on Winding1 or Winding2)	Current rating in VA
PhasesNormal	Short or Long Integer	Phase Count	Represents the built phases on the conductor. Count of phases should be obtained from counting the phases in the description where an ‘A’ phase conductor would have a phase count of 1.
VoltageGroup (On the Electric Device)	Short or Long Integer	RatedVoltages (on Winding1)	Domain coded value. Indicates the operating voltage at the Primary terminal of the transformer, and should match the Voltage Group code of each external feature (i.e. not counting the units) that is connected to the Primary terminal
Manufacturer	Text or Coded Value Domain	Manufacturer	Name of the manufacturer that produced the equipment. Note: If using a coded value domain, the description should be used to determine the proper spec during the feature to spec mapping process.
Model	Text or Coded Value Domain	Model	Model of the equipment. Note: If using a coded value domain, the description should be used to determine the proper spec during the feature to spec mapping process
VoltageGroup (On the Units)	Short or Long Integer	RatedVoltages (on Winding2)	Domain coded value. Indicates the operating voltage at the Secondary terminal of the transformer, and should match the VoltageGroup code of each external feature (i.e. not counting the units) that is connected to the Secondary terminal
PrimaryConnectionType	Short or Long Integer	ConnectionType (on Winding1)	Coded Value domain in which the descriptions specify the connection type of the winding, i.e. ‘Y’, ‘Open Delta’.
SecondaryConnectionType	Short or Long Integer	ConnectionType (on Winding2)	Coded Value domain in which the descriptions specify the connection type of the winding, i.e. ‘Y’, ‘Open Delta’.

Capacitors (Electric Device and Electric Junction Object Feature Classes)

Field Model Name	Field Data Type	Spec Property	Description
PhasesNormal	Short or Long Integer	Phase Count	Represents the built phases on the conductor. Count of phases should be obtained from counting the phases in the description where an ‘A’ phase conductor would have a phase count of 1.
Manufacturer	Text or Coded Value Domain	Manufacturer	Name of the manufacturer that produced the equipment. Note: If using a coded value domain, the description should be used to determine the proper spec during the feature to spec mapping process.
Model	Text or Coded Value Domain	Model	Model of the equipment. Note: If using a coded value domain, the description should be used to determine the proper spec during the feature to spec mapping process
PrimaryConnectionType	Short or Long Integer	ConnectionType	Coded Value domain in which the descriptions specify the connection type, i.e. ‘Y’, ‘Open Delta’.