Locational vs. Functional Equipment

To support the needs of the Utility Network Community (UNC), there needs to be the support of Locational vs Functional Equipment. This support means being able to support a single piece of equipment at a single location with known design attributes (Locational) and the current installed attributes (Functional).

Here are two example use cases for this type of device modeling.

A request can be made to change out a transformer, the change out occurs, but for supply reasons the change out process could not replace like equipment for like. They may have needed to temporarily install an oversized transformer. Users would like to track the locational and functional attributes of all transformers, capacitors, circuit breakers, and regulators. There may also be some environmental tracking requirement for oil-filled equipment because of PCB contamination cases.

Recommended Configuration

• Functional equipment installed is listed in non-spatial object tables, such as ElectricJunctionObject. If the user wants the details of the functional equipment to be exported by the export subnetwork method and moved to the ADMS, containment associations must be created and junction-junction associations between the non-spatial object and the terminals must also exist.

• Device must live in the E:Has Functional Equipment and E:Functional Equipment network categories along with the record in the non-spatial object tables.

Product Limitations

• ArcFM Designer XI would see this change as a replacement of equipment. When the design is pushed to the UN, it will be up to the editor to manually move this feature to the non-spatial object table and create the containment and connectivity associations.

• Feeder Services currently push both devices (Locational and Functional) to ADMS. A customization must be requested during the project setup to determine which piece of equipment ends up in ADMS, the Functional network, or the Locational Equipment network.

Functional Equipment Network Categories