Network Categories and Workflows for the Utility Network

Network Categories

A group of asset types that meet a set of criteria is called a Network Category. For instance, if you create a network category called E:Disconnect, you could perform a trace that identifies devices that need to be de-energized to isolate flow to a certain area. Network categories serve to define and differentiate basic classes of equipment by identifying the fully qualified asset type of each member of the class. A fully qualified asset type consists of the UN feature class or table, the asset group value, and the asset type value.

The network categories discriminate each type of electrical equipment based on important properties (e.g., overhead or underground, connectivity pattern and terminals, banks or phase-specific units within banks, etc.). Some network categories may be subclasses of others. A feature type that belongs to a E:Reclosing category for instance should also belong to the E:Switch category. Other network categories are mutually exclusive. A feature type cannot belong to both the E:Transformer - Inline category and the E:Transformer - Tap category.

The ArcFM UN model prescribes a list of attributes that are expected for each type of equipment. See Appendix A: Field Model Name to EUNF Mappings in the ArcFM Configuration for the Utility Network for a list of the network categories and attributes that should exist for specific equipment types (asset group/asset type). Both equipment type categories and modeling categories are defined. Equipment type categories identify electrical equipment by its basic function and in some cases define subclasses for the equipment. Also included are special categories needed to support ArcFM Conduit Manager. Modeling categories are used to discriminate among features for certain applications or features.

The name for each attribute is a field model name. The name of the field in your implementation may differ from those of the ArcFM UN example, but it must exist and be mapped to the attribute name. Mapping is performed within the Solution Center Editor XI application.

Dynamic Workflows and OOTB Autoupdaters

Workflows, both custom and OOTB, perform repeatable actions based on events or triggers. These actions may simplify frequent work activities, direct a custom task, or automate multi-step operations.

Within the Solution Center Workflows plugin, you can create custom workflows by copying an OOTB workflow and modifying the code, or start a new workflow from scratch. The Workflow plugin allows for integration between XI series applications and external systems with minimal coding effort.