Electric Distribution

1

Copyright © 2001 Environmental Systems Research Institute, Inc. and Miner and MinerAll rights reserved.Printed in the United States of America.

The information contained in this document is the exclusive property of Environmental Systems ResearchInstitute, Inc. This work is protected under United States copyright law and other international copyrighttreaties and conventions. No part of this work may be reproduced or transmitted in any form or by anymeans, electronic or mechanical, including photocopying and recording, or by any information storage orretrieval system, except as expressly permitted in writing by Environmental Systems Research Institute, Inc.All requests should be sent to Attention: Contracts Manager, Environmental Systems Research Institute,Inc., 380 New York Street, Redlands, CA 92373-8100, USA.

The information contained in this document is subject to change without notice.

U.S. GOVERNMENT RESTRICTED/LIMITED RIGHTSAny software, documentation, and/or data delivered hereunder is subject to the terms of the LicenseAgreement. In no event shall the U.S. Government acquire greater than RESTRICTED/LIMITED RIGHTS.At a minimum, use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth inFAR §52.227-14 Alternates I, II, and III (JUN 1987); FAR §52.227-19 (JUN 1987) and/or FAR §12.211/12.212(Commercial Technical Data/Computer Software); and DFARS §252.227-7015 (NOV 1995) (Technical Data)and/or DFARS §227.7202 (Computer Software), as applicable. Contractor/Manufacturer is EnvironmentalSystems Research Institute, Inc., 380 New York Street, Redlands, CA 92373-8100, USA.

ESRI and the ESRI globe logo are trademarks of Environmental Systems Research Institute, Inc., registeredin the United States and certain other countries; registration is pending in the European Community.ArcFM, ArcInfo, ArcCatalog, ArcMap, ArcSDE, ArcObjects, ArcIMS, ArcStorm, Map LIBRARIAN, GIS byESRI, and the ArcFM logo are trademarks and www.esri.com is a service mark of Environmental SystemsResearch Institute, Inc. Other companies and products mentioned herein are trademarks or registeredtrademarks of their respective trademark owners.

The names of other companies and products herein are trademarks or registered trademarks of theirrespective trademark owners.

Contents • iii

Contents

Acknowledgements............................................................................................. v

Modeling with ArcGIS Electric Distribution ................................................... 7

INTRODUCTION ........................................................................................................................................ 8MODELING CONCEPTS IN ARCGIS ELECTRIC DISTRIBUTION ................................................................... 9

Building Analysis Models ................................................................................. 13

ELECTRIC DISTRIBUTION ........................................................................................................................ 14CIRCUIT SEGMENTS .............................................................................................................................. 16DEVICES ............................................................................................................................................... 18ARCGIS ANALYSIS MODELS ................................................................................................................. 24

Deploying ArcGIS Electric Distribution ........................................................ 27

DEPLOYING ARCGIS ELECTRIC ............................................................................................................ 28GEODATABASE BASICS .......................................................................................................................... 29GEODATABASE DESIGN, TOOLS AND GUIDELINES ................................................................................. 30ARCGIS ELECTRIC DEPLOYMENT SCENARIOS ....................................................................................... 33IMPLEMENTING ARCGIS ELECTRIC ........................................................................................................ 36

Structures Data Model Reference .................................................................. 47

STRUCTURES .......................................................................................................................................... 48

Circuit Segments Data Model Reference ....................................................... 61

CIRCUIT SEGMENTS .............................................................................................................................. 62

Devices Data Model Reference ....................................................................... 71

ELECTRIC DEVICE ................................................................................................................................. 72DEVICE CONTROL ................................................................................................................................ 86

Customer and Service Data Model Reference .............................................. 99

CUSTOMER AND SERVICE ..................................................................................................................... 100

Index ................................................................................................................. 109

iv • ArcGIS Electric Distribution Model

v

AcknoAcknoAcknoAcknoAcknowledgementswledgementswledgementswledgementswledgements

The creation of this draft version of ArcGIS ElectricDistribution Model has been a collaborative effort of severalMiner and Miner employees. Jeff Meyers, Mike Daniels,Kelly Little, Carol Terry, and Kim Despins exerted muchof the effort it took to get the book to its present form.Steve Grise of ESRI also made essential contributions.

Many facts regarding the utility industry operations werecultivated from the Standard Handbook for ElectricalEngineers, fourteenth edition, Donald G. Fink and WayneBeaty, published by McGraw Hill, as well as from productcatalogs from Cooper Power System® Waukesha, WI53187.

Miner and Miner is privileged to have an active electricutility user group. Lead, and often cajoled into action byKelly Little, Product Specialist, this group has made asignificant contribution to the development of theArcGIS Electric Distribution model. Of the manymembers of our user and business partner community wewould like to especially thank the following organizationsfor their ongoing support.

These are some of the electric utilities and engineeringfirms that directly contributed to developing the ArcGISelectric model:

Alliant Energy

Arizona Public Service (APS)

Avista Corp.

Chelan County Power

Convergent Group

Cook-Hurlbert, Inc.

Dominion Resources, Inc.

Enghouse Systems Limited

GeoAnalytics Inc.

Idaho Power Company

InfoTech Enterprises, Inc.

James W. Sewall

Lincoln Electric System

MESA Solutions

Montana Dakota Utility (MDU)

NES

Osmose

PPL Corp. (Pennsylvania Power & Light)

Reliant Energy

Rochester Public Utilities

Stoner Associates, Inc.

Xcel Energy

vi • ArcGIS Electric Distribution Model

7

Modeling withArcGISElectricDistribution

ArcGIS Electric Distribution contains ready-to-use datamodels that can be configured and customized for use atelectric utilities. A keystone of this new data model issuperior modeling of electric devices and circuits thatcapture the behavior of real-world objects such astransformers and feeders.

These are the topics in this chapter:

• Introduction

• Modeling concepts

• Modeling electric distribution systems

1

8 • ArcGIS Electric Distribution Model

Electricity is an essential part of our everyday lives that weoften take for granted. We take it for granted, that is, until wehave to do without power for one reason or another. We don'toften actually see them, but behind the scenes many people areworking to ensure that we have a clean, safe, reliable source of

power; that we don't have unpredictable or inappropriatecurrent to power our infinite variety of devices; and that thesupply is there when we need it; and that it is, more or less,

reasonably priced.

ArcGIS Electric Distribution is designed for electric utilitiesthat manage distribution systems that deliver electric power toour service drops. By providing a geographically oriented view

of electric distribution devices, structures, circuits and evencustomer information, ArcGIS Electric Distribution helpsutility managers and administrators visualize, analyze, and

understand real-world engineering and business problems and,more importantly, solutions. Built using object–component

technology, ArcGIS Electric Distribution provides a powerfulnew platform for utility solutions. The goal of this system is to

provide operational efficiencies and business benefits thattranscend traditional GIS and mapping boundaries.

INTRODUCTION

Modeling with ArcGIS Electric Distribution • 9

Today’s electric utilities are realizing the benefits ofgeographic information system (GIS) technology in themanagement of facilities for engineering, construction, andoperations purposes. The typical requirements of theseutilities reflect business needs to:

· Update GIS databases with design and as-built data

· Produce standard and custom map products

· Integrate computer-aided design (CAD) drawings withthe GIS network

· Integrate with other enterprise systems such as workmanagement systems, outage management, documentmanagement systems, materials management systems,and customer information systems

· Analyze installed network for capacity planning andcapital improvement projects

· Manage feeder system, conduit systems, and inspectionoperations

The ArcGIS Electric Distribution model supports thesetypical business needs by providing an implementation thatfocuses on operations and maintenance portions of thefacility life cycle and provides a crucial visual component.

WHO SHOULD READ THIS BOOK

ArcGIS Electric Distribution Model is intended for users whoimplement the ArcGIS electric distribution object models.These users include database designers, data builders,database administrators, analysts, and developers. Thisbook serves as a companion to the ArcGIS electricdistribution (UML) object model and details the modelcomponents and provides information for developingcustom applications.

The following topics are discussed in this book:

· Introduction to the ArcGIS electric distribution model.

· Definition of distribution networks and devices and thedesign considerations of these systems as they areapplied in ArcGIS electric distribution.

· Descriptions of the ArcGIS electric distribution modelstructures and organization including modelingtechniques and component notation in UML.

MODELING CONCEPTS IN ARCGIS ELECTRIC DISTRIBUTION

· Component reference of the ArcGIS electric distribu-tion model presented by subsystem and described innarrative form at the class level. Each componentcontains a description of usage and application withinthe model.

· Resources and guidelines for implementing instances ofArcGIS electric distribution.

· Deployment scenarios and task-based instruction forevaluating model requirements and implementing acustom geodatabase in the ArcInfo™ 8 environment.

This book is written assuming that the reader is knowledge-able about electric distribution and has a functionalunderstanding of ArcInfo 8. Additional resources areprovided in the bibliography to assist you with developing abasic understanding of Component Object Model (COM),Unified Modeling Language (UML), and object-orienteddatabase design.

The sample data contained on the ArcGIS ElectricDistribution CD–ROM is provided courtesy of the theTown of Greeley, Colorado. The data has been modified byMiner & Miner to suit the needs of this book and tohighlight ArcGIS functionality. The Town of Greeley andMiner & Miner cannot guarantee the reliability or suitabilityof this information, as it is provided as an example.Original data was compiled and manipulated from varioussources and may not accurately represent the electricdistribution systems as maintained by Greeley. The sampledata may be updated, corrected, or otherwise modifiedwithout notification.

Modeling electric distribution systems

The object technology at the core of ArcInfo 8 combinesdata and application behavior modeling. As a result, theArcGIS model not only includes an essential set of electricdevice, structure, circuit segment, and customer informa-tion feature classes and properties, it also includes rules andrelationships that define object behaviors. The core objecttechnology and applied ArcGIS electric distribution modelresult in significantly less configuration and customizationeffort for overall implementation per site.


ELECTRIC DISTRIBUTION

The power delivered by electric utilities is transmitted fromgenerating plants to industrial sites and the substations thatdistribute power to residential and commercial users; theutility business is thus divided into these two areas -transmission and distribution. Transmission networksconnect generators to substations through transmissionnetworks. The distribution system delivers power fromsubstations to residential and commercial users. This bookcovers the aspects of the electric utility business dealingwith distribution.

Distribution represents about 35 percent to 50 percent ofa utility's investment. The mission of the utility is toprovide power to consumers at an appropriate voltage witha certain degree of reliability. Distribution componentstypically include:

• Subtransmission circuits with voltage ratings that rangebetween 12.47 and 345 kV

• Distribution substations that convert energy fromtransmission network levels to lower primary systemvoltages

• Feeders, or primary circuits, that operate between 4.16and 34.5 kV and supply load to specific geographicareas

• Distribution transformer rated from 10 to 25000 KVAthat transform primary voltage to utilization voltage

• Secondary circuits that carry current from the trans-former along the street

• Service drops that carry current from transformers tocustomer point of utilization

Electric distribution system components

Typical primary overhead distribution systems are operatedas radial circuits from the substation outward. In overheadsystems, structures such as poles and H-frames support theprimary and secondary conductors. Surface structures likepads enclose and protect electric devices on the ground.

The electric utility infrastructure is also composed ofdevices such as transformers and fuses and circuitsegments, such as overhead and underground conductors.These components fall into four general logical categories:circuit segments, structures, devices, and customer andservice.

Circuit Segments

This subsystem contains classes and properties thatdescribe the conductors that transmit and distribute electriccurrent. Circuit segments can be categorized as simple orcomplex edges and objects. The inherent behavior ofcomplex edges is very different in ArcGIS ElectricDistribution than the traditional ArcInfo topology model.The ArcGIS Electric Distribution system automaticallymaintains the relationships between complex edges, anyattached devices, and other edges so you can choose howyou want to physically segment your network. For instance,it makes sense to physically segment electric lines betweenfuses and switches since, among other things, it isimportant to keep circuit data on lines, depending onwhich side of the fuse they are on.

For example, if you place a fuse on an overhead primarythat originally was associated with CircuitID 001, it may bethat the overhead primary west of the fuse is part ofCircuitID 001, but the overhead primary east of the fuse isnow associated with CircuitID 005. At the same time, it isnot necessary to physically segment electric line segmentsat splices.

Once your network is in place and you move an electricline segment, any attached switches, fuses, transformers,and other portions of the network automatically move withit. ArcFM Energy determines whether a complex edgeshould be split based on the type of junction (device) beingadded. As with most of the subsystems discussed in thisdocument, a common set of properties is defined in a top-level abstract class. All subclasses beneath the abstract classElectricComplexEdge inherit these properties.

Structures

Structure is the abstract class that contains commoncharacteristics, or attributes, for all electric structuresinvolved in the distribution or transmission of electricity.The Structure class was created as a general top-level classfor any type of facility structure. The subsystem structurecontains non-network (non-spatial) features and relatedobjects. You can create associations between a supportstructure and the Inspection object class to captureinformation about maintenance, for example. Thesubsystem structure also includes objects to mangeinformation about the lifecycle of a structure.

Modeling with ArcGIS Electric Distribution • 11

Devices

Electric devices help ensure consistent service within thedistribution network. The device subsystem containssimple junction features and object classes. Devicesfeatures participate in the network and objects are the unitsand controls associated with those devices.

Customer and Service

Residential, commercial, and industrial customers, resellers,as well as special devices such as streetlights, constitute theloads on the electrical system. Simple junction features arethe electric locations (for example, primary meters andservice points). Objects contain customer information andinformation about generators of alternate sources ofelectricity. Primary meters, delivery points, and generatorsmay be associated with a structure.

Electric modeling requires considerationof facilities as assets.

Design discussion

One benefit of GIS technology is that utilities can tracktheir assets by geographic location. Network assets, likemost other infrastructure owned by businesses, can bedepreciated for tax accounting purposes. The specificamount of depreciation allowed depends on the originalvalue of the equipment, how long the facilities have beenin place, and the tax boundary area that facilities arelocated in. Having an accurate record of facilitiesmanaged with a GIS provides a more accurate inventoryof existing facilities and an automated way to maintainthese records as a by-product of map maintenanceactivities. From a GIS system design standpoint, it isimportant to understand how the location of physicalequipment (i.e., a conduit) can be considered differentlyfrom an asset management standpoint, depending onhow many ducts, conductors, or cables it may contain.You should consider asset management for yourgeodatabase design and any special rules that your utilitymay have for asset management.

Electric distribution modeling requiresconsidering facilities as assets


During the lifetime of a particular transformer or switch,the individual piece of network equipment may beinstalled in one location, only to be removed and storedin a truck or warehouse for a period of time. Thisprocess can be repeated for the same piece of equipmentseveral times during its useful lifetime. From an assetmanagement standpoint, an accurate accounting fordepreciation purposes is important. It is also importantto continue to link historical maintenance, repair, andinspection data to understand when the equipment hasreached the end of its reliability curve.

Design discussion

Devices are often moved to differentlocations during their life span.

Section of Transformer placement job sketch (Source: map sketch created forArizona Public Service Co. by Miner and Miner Consulting Engineers, Inc.)

13

Building Building Building Building Building AnalysisAnalysisAnalysisAnalysisAnalysisModelsModelsModelsModelsModels322222


electric distribution

Structure

Object

JointUseAttachment Inspection LifecycleHistory Assembly

Specific inspection objects shouldbe defined on an as-needed basis.As a new inspection object isdefined, any necessaryrelationships should also bedefined.

Specific lifecycle history objects shouldbe defined on an as-needed basis. As anew history object is defined, anynecessary relationships should also bedefined.

underground structuresElectricDeviceElectricLocation

UndergroundLinearStructure

ComplexEdgeFeature RelationshipClass

SimpleJunctionFeature

Underground ElectricLineSegment

Other ULS Contents

Subtypes includeDuct Bank andTrench.

Examples include gaspipe, communicationcable, and water pipe.

UndergroundStructure

Subtypes include Hand Hole,Manhole, and Vault.

ULS_ULSMemberCrossReference

Attributed relationship class tomanage the many-to-manyrelationship betweenUndergroundLinearStructure andUndergroundElectricLineSegment.

Object

DuctDefinition

ELECTRIC DISTRIBUTION

Building Analysis Models • 15

object model

BusBar

ElectricDevice

Structure

Feature

AerialMarker

FacilityStructure

Pushbrace WarningSign

Guy

Riser

EquipmentEnclosure

AnchorGuy

SpanGuy

SurfaceStructure

ElectricStation

SwitchingFacility

ElectricLocation

StreetLightSupportStructure

SpanGuy is a linearfeature.

Subtypes include Back,Bridle, Sidewalk, andStandard

Subtypes include H-Frame,Non-Wood Power Pole,Non-Wood Street LightPole, Wood Street LightPole, and Tower

Subtypes include ConnectionBox, Enclosure, Mat, Non-Electric Enclosure, Pad, andPedestal

Subtypes include AutoTransfer Enclosure, JunctionCabinet, Pad-Mounted Gear,and Switch Board

Subtypes include MainStation, Net Station, and SubStation

This relationship is only validfor subtypes Non-WoodStreet Light Pole and WoodStreet Light Pole


circuit segmentsObject

ElectricLine

ElectricDeviceElectricLocation

ElectricLine

SimpleEdgeFeature

Circuit Source

Subtypes includekW, Swing, andVoltage Controlled

Support for non-symbolized lines

Subtypesinclude CircuitLine and StationLine

ConductorInfo

ComplexEdgeFeature

ElectricComplexEdge

ElectricLineSegment

BusBar

CommunicationCable

CircuitSourceSwitchingFacility

UndergroundElectricLineSegment

UndergroundLinearStructure

OverheadElectricLineSegment

Subtypes include Single PhasePrimary Overhead, Two PhasePrimary Overhead, Three PhasePrimary Overhead, Single PhaseSecondary Overhead, Three PhaseSecondary Overhead and StreetlightConductor

Subtypes include Single Phase PrimaryUnderground, Three Phase Primary Underground,Single Phase Secondary Underground, Three PhaseSecondary Underground and Streetlight Conductor

Subtypes include CircuitLine and Station Line

Support for symbolizedlines

Feature

CIRCUIT SEGMENTS


customer & service

UndergroundStructureFacilityStructure

Object

UsageInfo

These relationships arenot valid for ServicePoint


DemandInfo

LoadSummary

ElectricLocation

CustomerConnection

DeliveryPoint

Generator

ServicePoint PrimaryMeter

Object

SychronousMotor

InductionMotor

Object

ServiceAddress

Representation ofCustomer InformationSystem

CustomerInfo


DEVICES

devices

Transformer

TransformerUnit

OpenPoint

LoadTapChanger

NetworkProtector

Subtypes include LoadBreak Elbow, Non-Load Break Elbow,Open Point, SolidConnection and Splice

This relationship isonly valid forsubtypes LoadBreak Elbow, Non-Load Break Elbow,and SolidConnection

The Rated KVA propertyshould be non-editable; itis a derived field equal tothe sum of the RatedKVAof the relatedTransformerUnits

CapacitorControl

CapacitorUnit

PowerFactorCorrectingEquipment

This relationship isonly valid forsubtypes SwitchedCapacitor Bankand SeriesCapacitor

This relationship is onlyvalid for subtypes FixedCapacitor Bank andSwitched CapacitorBank

VoltageRegulator

TransformerBank

Subtypes includeSingle PhaseOverhead, Two PhaseOverhead, ThreePhase Overhead, andThree Phase Pad-Mounted

Subtypes include Network, Single PhaseOverhead, Single Phase Underground, TwoPhase Overhead, Three Phase Overhead,Three Phase Underground, Step, andPowerTransformer

This relationship is only valid for subtypeNetwork.

This relationship is only valid for subtypePower Transformer.

Subtypes include FixedCapacitor Bank, SwitchedCapacitor Bank, SeriesCapacitor, and ShuntReactor


ElectricDevice

SupportStructure

Note: If SecondaryElectric Line Segmentis not a networkfeature, thenStreetLight would notbe a network feature.

This relationship is only valid forSupportStructure subtypes Non-Wood Street Light Pole and WoodStreet Light Pole.

MiscNetworkFeature

Subtypes include Fault Indicator,Fault Limiter, Counter PoiseGround, Rod Ground, WrapGround, and Surge Arrestor

StreetLightOvercurrentProtectiveDevice

DynamicProtectiveDevice

CircuitSource

RelayControl

SectionalizerUnit

SectionalizerControl

RecloserUnit

RecloserControl

FuseUnit

Switch

SwitchUnit

This relationship is only valid for CircuitBreaker and Recloser subtypes.

This relationship is only valid forSectionalizer subtypes.

This relationship is only valid forRecloser subtypes.

This relationship is only valid forSectionalizer subtypes.

This relationship is only valid forRecloser subtypes.

This relationship is only valid for CircuitBreaker and Recloser subtypes.

Subtypes include Circuit Breaker, FaultInterrupter, Single Phase Hydraulic Recloser,Two Phase Hydraulic Recloser, Three PhaseHydraulic Recloser, Three Phase ElectronicRecloser, Three Phase Relay Recloser, SinglePhase Hydraulic Sectionalizer, Two PhaseHydraulic Sectionalizer, Three Phase HydraulicSectionalizer, and Three Phase ElectronicSectionalizer

Subtypes include OverheadDisconnect, Overhead LoadBreak, UndergroundDisconnect, and UndergroundLoad Break

FacilityStructure


These relationships arenot valid for OpenPoint.

Fuse

Subtypes include CurrentLimiting, OverheadExpulsion, UndergroundExpulsion, and Vacuum


devicesObject

Transformer

NetworkProtector RecloserControl

RecloserElectronicControl

RecloserHydraulicControl

This relationship is only valid forTransformer subtype Network.


This relationship is only valid forDynamicProtectiveDeviceRecloser subtypes.


RelayControl

SectionalizerHydraulicControl

SectionalizerElectronicControl


This relationship is only valid forDynamicProtectiveDeviceSectionalizer subtypes.



This relationship is only valid forsubtypes Circuit Breaker andRecloser.


devices

Switch

This relationship is only valid forPowerFactorCorrectingEquipment subtypes FixedCapacitor Bank and Switched Capacitor Bank.

SwitchUnit CapacitorUnit FuseUnit SectionalizerUnit

PowerFactorCorrectingEquipment Fuse Dynamic

ProtectiveDevice

This relationship is only validfor DynamicProtectiveDeviceSectionalizer subtypes.


Object TransformerUnit

DeviceObject

UnitObject

RegulatorControl

LoadTapChanger

CapacitorControl PowerFactorCorrectingEquipment

Transformer

RecloserUnit TransformerUnit

DynamicProtectiveDevice TransformerBank

RegulatorControlThis relationship is only validfor DynamicProtectiveDeviceRecloser subtypes. This relationship is only valid

for VoltageRegulatorUnit.

This relationship is only valid forTransformer subtype Power Transformer.

This relationship is only valid forPowerFactorCorrectingEquipment subtypes SwitchedCapacitor Bank and Series Capacitor.

This relationship is only valid for TransformerUnitsubtype VoltageRegulatorUnit.

Subtypes include Current Level, KVAR Level,Temp Level, Time, and Voltage Level

Subtypes include DistributionTransformer Unit, PowerTransformer Unit, and VoltageRegulator Unit


THE ARCGIS ANALYSIS MODELS

While there are many common real-world objects in electric distribution systems,the common aspects of these objects become even more apparent when youbegin to group the properties and names of the objects in an analysis model. Theanalysis model provides a logical grouping of common properties of objects in aninheritance tree. While the diagrams split the model into network domains suchas structures and devices, this section describes the entire inheritance modelwithin each subsystem.

The process of building an analysis modelIn simple terms, an analysis model can be created by starting with the coreArcInfo object classes and a set of named, real-world objects to be modeled. Thecreation of the analysis model often begins with a top-down approach, where thelist of network objects is conceptually divided into logical groups. The key char-acteristic of these groups is that they share common properties and/or behaviors.For example, structures are grouped together because they support or encloseelectric equipment. Support structures can be grouped together because they carryoverhead conductors. After a basic grouping of objects is established, you canbegin to identify more specific similarities between objects. During the process,new classes are identified and some classes are merged. The final result is a set ofbase classes, intermediate classes, leaf classes, and relationships.

By defining the properties of each leaf class, common properties appear. Forinstance, both overhead and underground circuits have phase designation as aproperty. Rather than duplicate each property in all objects, a higher-order class iscreated to contain the common properties. This process ultimately results in a setof intermediate, often abstract classes that model the system. The creation of ananalysis model is an iterative process that requires both top-down and bottom-upanalysis to define the structure of the object model.

The objects and model are defined using a subset of the Unified Modeling Lan-guage (UML). Basic resources for UML concepts, rules, notation, and syntax arerequired. Guidelines for using the model within ArcCatalog™ software are alsoimportant.

SubtypesDecisions about subtyping classes are important for your implementation. Forinstance, if objects in a grouping have different properties to the point that theycannot be grouped together, you need to split your object into two classes. Ex-amples of this are protective devices can open to protect the network from faultsbut dynamic protective devices can open and close automatically to restoreservice. While both devices protect the network, they are different enough thatseveral classes were required in the model.

Certain network devices, on the other hand, have been lumped into a single classcalled MiscNetworkFetures. A set of subtypes is used to distinguish differentdevices, for example, circuit breakers and fault interrupters. In general, youshould try to lump your objects into fewer classes wherever possible since thereare performance advantages to lumping objects together.

ARCGIS ANALYSIS MODELS


Complex edges are the base class for all conductors. The ElectricLineSegment classwas created as a general top-level class for both overhead and undergroundcircuits. In other words, all classes beneath the ElectricLineSegment class willcontain the properties of this feature class.

The inherent behavior of complex edges is very different than the traditionalArcInfo topology model. The ArcInfo system automatically maintains the rela-tionships between complex edges, any attached devices, and other edges so youcan choose how you want to physically segment your network.

For instance, it makes sense to physically segment underground conductors be-tween manholes since, among other things, it is important to capture data onunderground conductors where they connect with manholes. This can only becaptured for the starts and ends of conductors so underground networks could besegmented at manholes. At the same time, it is not necessary to physically segmentconductors at switches or circuit breakers. Once your network is in place, you canmove line segments and any attached devices, and other portions of the networkwill automatically move with it.

As with most of the subsystems discussed in this document, a common set ofproperties is defined in a top-level abstract class. All of these properties areinherited by all subclasses beneath ArcFMLine.

Describing the objectsThe objects are shown in a UML style but are represented differently than theUML models and static analysis diagrams. Properties inherited by abstract classesare shown shaded within the object and provide clarity for available propertiesand a reference to the abstract classes from which the properties are inherited.

The model is represented within a Visio® Enterprise/Professional (Visio) diagramand can be immediately exported from Visio to Microsoft® Repository using theVisio UML Export wizard. The ArcInfo 8 Computer-Aided Software Engineer-ing (CASE) tool wizard is used to build an instance of the mode within ageodatabase. The ArcInfo 8 CASE Tools support UML.

Developers can generate a compilable C++ Active Template Library (ATL) basedVisual Studio project if they choose to create their own custom features, whichare subclassed off those contained in either ArcInfo 8 or ArcGIS Electric Distri-bution object model. The following chapters describe the individual classes andmodel components.


27

ArcGIS Electric Distribution provides an extensive anddetailed set of components that you can use to implementyour data model. ArcGIS Electric Distribution can beimplemented with no modifications or can be customized tofit your specific requirements.

Topics discussed in this chapter:

· Implementation resources

· Geodatabase basics

· Defining your geodatabase requirements

· Selecting an implementation process

· Deployment scenarios

· Generating a geodatabase from a repository

DeploDeploDeploDeploDeployingyingyingyingyingArArArArArcGIS ElectriccGIS ElectriccGIS ElectriccGIS ElectriccGIS ElectricDistributionDistributionDistributionDistributionDistribution33333


A geographic data model is an abstraction of the realworld that uses a set of data objects that supportmap display, query, editing, and analysis. ArcInfosupports a new object-oriented data model–thegeodatabase data model–with the benefit ofrepresenting behaviors and relationships of features.

To assist with your implementation, ArcFM ElectricDistribution provides a domain-specific geodatabase, aswell as the components of its database design andimplementation. Examples from various stages of thegeodatabase implementation process are included to allowyou to begin implementation and customization at a levelappropriate to your needs.

The components include:

• ArcGIS Electric Distribution database schema andlogical data model presented in static analysis diagrams.

• Component reference of objects represented inthe logical data model describing the relation ofentities to real world objects.

• ArGIS Electric Distribution geodatabase modeled inUnified Modeling Language (UML).

• Microsoft Repository created from the ArcFM ElectricDistribution UML.

• Geodatabase of ArcGIS Electric Distribution modeland components.

The previous chapters reviewed the ArcGIS geodatabasedesign and data model schema. They also described howreal world objects are represented by the feature classeswithin the model. In this chapter you will learn how toimplement an ArcGIS geodatabase that meets yourdatabase design criteria, using existing objects andcustomizing an object to meet your implementation needs.

The information provided in this chapter is a compilationof ArcGIS-specific information and of materials fromother ArcInfo documentation, including Building aGeodatabase and Modeling our World.

Most utilities use a relational geographic data model,containing features such as points and lines—and theirrelated attributes—to represent their facilities. The data inthis model is used for map display, query, editing, andanalysis.

DEPLOYING ARCGIS ELECTRIC

ArcGIS Electric Distribution enhances your data andprocesses by representing your utility with objects thatmore closely model the real world. These objects arestored in an RDBMS and managed using the geodatabasedata model.

The geodatabase model is a generic model for geographicinformation that supports a wide variety of objectrelationships and behavior. ArcGIS Electric Distribution isa set of objects with behavior and relationshipsappropriate for modeling electric distribution facilities.You can use these objects out of the box or customizethem to more closely represent your facility.

The geodatabase

The geodatabase supports an object-oriented vector datamodel. In this model, real-world entities are represented asobjects with properties, behavior, and relationships. Theobject types include simple objects, geographic features(objects with location), network features (objects withgeometric integration with other features), annotationfeatures, and other more specialized feature types. Themodel allows you to define relationships between objects,as well as rules for maintaining the referential integritybetween related objects.

The purpose of the geodatabase

The purpose of the geodatabase data model is to letyou make the features in your GIS datasets smarterby endowing them with natural behaviors, and toallow any sort of relationship to be defined amongfeatures.

The geodatabase data model brings a physical datamodel closer to its logical data model. The objects ina geodatabase are mostly the same objects youwould define in a logical data model, such asowners, buildings, parcels, and roads.

Deploying ArcGIS Electric• 29

Benefits of a geodatabase data model

Applying an object-oriented data model to geographicfeatures yields many benefits. Object-oriented datamodeling lets you characterize features more naturally byletting you define your own types of objects, by definingtopological, spatial, and general relationships, and bycapturing how these objects interact with other objects.

A principal advantage of the geodatabase data model isthat it includes a framework to create intelligent featuresthat mimic the interactions and behaviors of real-worldobjects.

The geodatabase data model lets you implement themajority of custom behaviors without writing anycode. Most behavior is implemented throughdomains, validation rules, and other functions of theframework provided by ArcInfo.

A geodatabase stores geographic data in acommercial relational database. This means thatgeographic data can be administered centrally byinformation technology professionals and ArcInfocan take advantage of developments in databasetechnology.

ArcGIS Electric Distribution includes electric utilitydistribution-specific geodatabases which may beimplemented as is, or may be used as a framework fordesigning a custom geodatabase implementation. Todetermine how to best implement ArcGIS ElectricDistribution, you should be familiar with the databasedesign requirements for your organization. This sectionprovides basic guidelines and techniques for determining ageographic database design and implementing that design.

Implementation options

Designing a geodatabase is a critical process that requiresplanning and revision until you reach a design that meetsyour requirements. Once you have a design, there are twomain ways that you can create the geodatabase. Onetechnique is to load existing shapefile and coverage datainto one of the sample geodatabases, and create or modifydatabase items with ArcCatalog. Another technique is touse Unified Modeling Language (UML) and Computer-Aided Software Engineering (CASE) tools to design andcreate a custom geodatabase schema, create thegeodatabase from the schema, and then load your data.

GEODATABASE BASICS

Regardless of the method you choose, the geodatabasethat you create can be refined later, using ArcCatalog orUML and CASE tools.Design guidelines

The structure of the geodatabase – feature datasets,feature classes, topological groupings, relationships, andother elements – allows you to design geographic databasesthat are close to their logical data models.

The following are general guidelines for the design process:

1. Model the user’s view of the data.

Identify the organizational functions of the dataand determine the data needed to support thesefunctions. Organize the data into logicalgroupings.

2. Define objects and relationships.

Identify and describe the objects, specifyingobject relationships. Build the logical data modelwith the set of objects, knowing how they are relatedto one another.

3. Select geographic representations types.

Represent discrete features with points, lines, andareas. Characterize continuous phenomena with rasters.Model surfaces with TINs or rasters.

4. Match the logical model to geodatabase elements.

Match the objects in the logical data model to objectsin a geodatabase. Determine the geometry types ofdiscrete features. Specify relationships betweenfeatures. Implement attribute types for objects.

5. Plan the geodatabase structure.

Organize the geodatabase into feature classes, featuredatasets. Consider thematic groupings, topologicalassociations, and departmental responsibility for data.

The first three steps develop the conceptual model,classifying features based on an understanding of datarequired to support the organization’s functions, anddeciding their spatial representation. The last two stepsdevelop the logical model, matching the conceptualmodels to ArcInfo geographic datasets.


Designing with CASE tools

Computer-Aided Software Engineering (CASE) tools andtechniques automate the process of developing softwareand database designs. You can use CASE tools to createnew custom objects and to generate a geodatabase schemafrom a UML diagram.

Object-oriented design tools can be used to create objectmodels that represent your custom objects. You can usethese models to create a COM object that implements thebehavior of the custom object as well as the databaseschema where these custom objects are created andmanaged.

The steps for creating custom objects are:

1. Design the object model using UML.

2. Export the model to the Microsoft repository.

3. Generate stub-code and implement behavior.

4. Create a geodatabase schema for the custom object.

For details on steps 1 to 3, see Modeling Our World and theArcInfo Developer’s Guide.

Strategies for using CASE for schema design andgeneration

Two general strategies exist for using UML and CASEtools to design and create your geodatabase. Thefirst strategy involves using UML to define all of theschema for the geodatabase, generating that schema,then populating the schema with data.

The second strategy takes the opposite approach. Itinvolves creating the schema by importing existingdata into your geodatabase, building geometricnetworks, then using CASE tools to apply your UMLmodel to the existing data.

You can use a combination of the two strategiesdiscussed if your UML model describes a largerschema than defined when you imported yourexisting data. Once your schema has been createdusing one or both of these strategies, you canmodify it by modifying your UML model, thenreapplying the model to your geodatabase schemausing the Schema Creation Wizard. Alternatively, you canuse the schema management tools in ArcCatalog to modifyyour geodatabase schema.

GEODATABASE DESIGN, TOOLS AND GUIDELINES

Strategies for using CASE for schema design andgeneration

Two general strategies exist for using UML and CASEtools to design and create your geodatabase. Thefirst strategy involves using UML to define all of theschema for the geodatabase, generating that schema,then populating the schema with data.

The second strategy takes the opposite approach. Itinvolves creating the schema by importing existingdata into your geodatabase, building geometricnetworks, then using CASE tools to apply your UMLmodel to the existing data.

You can use a combination of the two strategiesdiscussed if your UML model describes a largerschema than defined when you imported yourexisting data. Once your schema has been createdusing one or both of these strategies, you canmodify it by modifying your UML model, thenreapplying the model to your geodatabase schemausing the Schema Creation Wizard. Alternatively, youcan use the schema management tools in ArcCatalogto modify your geodatabase schema.

Modeling a switch

There are many different methods of modeling real-world objects. The following example shows the stepsneeded to model a common electric distributioncomponent, a switch, and shows how it could bemodeled in the context of ArcGIS Electric Distribution.

To correctly implement a switch, you need to define theswitches in your system. This could include a physicaldescription and an description of how switches operate.

• A switch disconnects circuits within the distributionnetwork and can be manually or power operated.Switches are operated by opening the contacts, whichinterrupt the current, allowing personnel to repairdamaged lines or other equipment.

Once a switch is defined, describe how switches are usedin the distribution system. Also provide any significantdetails related to the device.

• Switches are either open or closed. Switches arecritical to the electric distribution system to allowcurrent interruption to allow system maintenance,redirecting current in case of emergency, or to isolate


system failures. Switches may be automated andcontrolled remotely through SCADA operation.

Next describe the processes that a switch participates in.

• Routine maintenance, switching programs, andmonitoring the switch to ensure proper operatingcondition. The switch participates in processes formaintenance, inventory, analysis, network tracing,feeder management, and SCADA.

From the previous descriptions, list the informationrequired to support the defined processes.

• Whether the switch is group operated or individuallyoperated

• Whether the switch is manually operated

• Amount of current the switch can carry continuouslywithout appreciable rise in temperature

• Amount of operating voltage the switch is rated tocarry

• The normal position of the switch (open or closed)

• The present position of the switch (open or closed)

• Preferred circuit source (feeder) supplying the switch

• Identifier of possible second feeder supplying theswitch

• Switch identifier

• Location of the switch

• Installation date of the switch

• Phase designation of switch

• SCADA identifiers, if switch is automated

• Manufacturer of the switch

From this information, we can compare this switch tothe ArcGIS model and component reference.

By comparing the above descriptions and usage to thecomponent reference, we can see that a switch can bemodeled as an ElectricDevice in the ArcGIS ElectricDistribution model. As there are other devices in theutility that can also be represented as ElectricDevice—such as circuit breakers—we will model the switch as asubclass of ElectricDevice.

It is likely that you already have data in various formats,such as shapefiles, coverages, INFO™ tables, and dBASE®

tables that you want to store in a geodatabase. You mayalso have your data stored in other multiuser geographicinformation system data formats such as ArcStorm™, MapLIBRARIAN, and ArcSDE. You can use tools inArcCatalog to import data from these formats into yourgeodatabase.

OvercurrentProtectiveDevice

LabelTextMaxContinuousCurrentMaxInterruptingCurrentMaxOperatingVoltageNormalPosition[A,B,C]PresentPosition[A,B,C]

Switch

GangOperatedLabelTextManuallyOperatedMaxContinuousCurrentMaxOperatingVoltageNormalPosition[A,B,C]PreferredCircuitSourcePresentPosition[A,B,C]SCADAControlIDSCADAMonitorIDTieSwitchIndicator

ElectricDevice

CommentsElectricTraceWeightFacilityIDFeederIDFeederID2FeederInfoInstallationDateNominalVoltageOperatingVoltagePhaseDesignationSubtypeSymbolRotationWorkOrderID

Switch feature class inherits attributes of ElectricDevice


Converting existing data formats

When you import data into the geodatabase, both thegeometry and attributes are imported, though you canchoose to drop or rename attributes. All or some of thefeature classes from a coverage can be imported into anintegrated feature dataset, and several shapefiles with thesame spatial extent can also be imported into the samefeature dataset.

Once you have imported your data into the geodatabase,you can use ArcCatalog to further define your geodatabase.ArcCatalog contains tools for building geometric networksand for establishing subtypes, attribute domains, and soon.

To learn how to move your existing data into thegeodatabase, see the book Building a Geodatabase,Chapter 4, ‘Migrating existing data into ageodatabase’.

Loading data into a geodatabase schema

Once you have generated a geodatabase schemafrom ArcCatalog or from UML and CASE tools, youwill want to insert data into that schema. You can dothis by using the Object Editor in ArcMap to createnew objects, or you can load objects from existingshapefiles, coverages, INFO tables, and dBASEtables.

This is a separate process from importing data asoutlined above. Data creation and maintenance mayinvolve managing version and topology information.ArcCatalog and ArcToolbox have wizards to helpyou with this—Simple Data Loader and ObjectLoader—which are discussed in Building aGeodatabase, Chapter 4, ‘Migrating existing data intoa geodatabase’.

In the previous sections we have discussed database designand some general methods for implementing ArcGISElectric Distribution. There are three general scenarios:

1. Implement from the ArcGIS Electric Distributiongeodatabase.

2. Implement select components generated by the ArcGISUML.

3. Implement a custom geodatabase using UML based onthe ArcGIS logical data model.

The method you choose depends on your database design,whether you will store custom objects in the geodatabase,or whether you intend to create a geodatabase fromscratch. In practice, you will use a combination of all orsome of the methods outlined.

The first step is always to design the geodatabase. Thebook Modeling Our World is the guide to help you designyour geodatabase. Once this design is complete, you canproceed.

There are many implementation options. The process youchoose depends on your database design and level ofcustomization. You may use some or all of the describedmethods, depending on your requirements. The booksModeling our World and Building a Geodatabase providedirections for designing and implementing customgeodatabases.


Scenario 1: Implementing ArcGIS ElectricDistribution from a geodatabase.

Implementing using the ArcGIS Electric Distributiongeodatabase is a quick and easy method of implementationwhen little or no modifications of the ArcGIS ElectricDistribution model are required.

Establish a data model

To begin, install ArcGIS Electric Distribution, then, aswith all implementation processes, determine the datamodel requirements for your system. If analysis of yourlogical data model shows that the ArcGIS ElectricDistribution data model fits your needs as is, or may onlyrequire minimal customization, then this process issuggested.

If the geodatabase schema and the components of theArcGIS Electric Distribution model fit your databasedesign, you can migrate your existing data directly into theArcGIS Electric Distribution geodatabase.

Refine the geodatabase using ArcCatalog

You can use ArcCatalog to continue defining yourgeodatabase by establishing how objects in thedatabase relate to one another. This is the simplestand most direct method of implementing ArcGIS ElectricDistribution.

Using ArcCatalog, you can establish relationshipsbetween objects in different object classes and connectivityrules for objects participating in geometric networks. Youcan continue to use the geodatabase management tools inArcCatalog to refine or extend a mature databasethroughout its life.

In some cases, you may not yet have any data that youwant to load into a geodatabase, or the data you have toload only accounts for part of your database design. In thiscase, you can use the tools provided in ArcCatalog tocreate the schema for feature datasets, tables, geometricnetworks, and other items inside the database. ArcCatalogprovides a complete set of tools for designing andmanaging items you will store in the geodatabase.

These relationships and rules may be part of the schemathat CASE tools generate, but often you will want tofurther refine what is generated by CASE to meet your

geodatabase design.

What to do

To implement your data model from the ArcGISgeodatabase, the following steps are required:

1. Create the logical data model

2. Build the physical database model

3. Use ArcCatalog to edit the schema

4. Migrate your data into the geodatabase

5. Deploy the geodatabase

Scenario 2: Implementing ArcFM ElectricDistribution from a repository.

In most cases a subset of components of the ArcGISElectric Distribution model will be sufficient for yourimplementation. ArcCatalog contains tools to readthe Microsoft Repository generated from the ArcGISElectric Distribution UML. The Schema Creation Wizardguides you through the process of creating new featureclasses, tables, and other pieces of your geodatabase.

Although all of the required information for thegeodatabase schema can be read directly from therepository, you can select those components that fityour database design. Once the wizard is finished,you will have schema for your design ready to bepopulated with data.

Just as when implementing from the ArcGIS ElectricDistribution geodatabase, you can then use ArcCatalog toestablish relationships between objects in differentobject classes and connectivity rules for objectsparticipating in geometric networks.

This scenario is reviewed in detail in the followingcase study.

To implement your data model from the MicrosoftRepository containing the the ArcGIS data model, thefollowing steps are required:



ARCGIS ELECTRIC DEPLOYMENT SCENARIOS


3. Use ArcCatalog CASE tools to create schema and codereferencing an existing repository. While in the CASEtool, select only the model components you wish togenerate.

4. Use ArcCatalog to edit the schema

5. Migrate your data into the geodatabase

6. Deploy database throughout your site

Scenario 3: Implementing ArcGIS ElectricDistribution from a UML drawing.

CASE tools allow you to create custom objects andfeatures that extend the geodatabase model of ArcInfo 8.Object-oriented design tools that support the UnifiedModeling Language (UML) and the Microsoft Repositorycan be used to create designs for your objects. Onceexported to the Microsoft Repository, the CASE toolssubsystem will help you create a Component Object Model(COM) object that implements the behavior of yourcustom object and the database schema where theseobjects are stored.

The CASE tool subsystem of ArcInfo 8 lets youextend the ArcInfo geodatabase model to createcustom objects. These custom objects inheritbehavior from existing ESRI data objects. You canuse C++ to override and add behaviors to thebehavior inherited from the ESRI objects.

Once you have implemented your custom object, itmust be stored inside the geodatabase. You can usethe same UML diagram to generate the schema forthe object using the CASE tools subsystem. You canalso use the CASE tools to apply your UML design toexisting feature classes and tables.

The objects that you describe using UML don’t necessarilyhave to have custom behavior. You can also use UML todesign the schema for ESRI simple and ESRI networkobjects. You can use UML to design your feature classesand tables, including what attribute fields they have, theirsubtypes, attribute domains, relationship classes,connectivity rules, and so on.

When you are ready to begin creating your UML model,you can start with one of the ArcInfo UML Modeldiagrams. You can also start from the Visio EnterpriseDrawing templates. These Visio Drawing templates arelocated under your ArcInfo installation.

The ArcInfo UML Model diagrams contain the objectmodel required for using UML to model a genericgeodatabase. The ArcGIS Electric Distribution UMLdiagrams contain the UML model implemented in ArcFMElectric.

The tools to export your UML model to the repository arecontained within Visio.

To implement an advanced implementation of your datamodel using UML, the following steps are required:



3. Create a UML drawing of the ArcGIS ElectricDistribution model

4. Export the UML diagram to a repository

5. Generate the schema and code

6. Load your data into the schema

7. Deploy database


3rd Party3rd PartyCASECASE

Uml ObjectUml ObjectModelModel

COM CodeCOM CodeGeneratorGenerator

MSMSRepositoryRepository

GeoDb SchemaGeoDb SchemaGeneratorGenerator

Pole

Pole

Electric.schemaElectric.schema

Step 1: Create a logical data model

There are several steps in creating a logical data model:

Data assesment

Complete an assessment of your utility distribution systemmodeling needs. To do this, document how your data iscurrently represented, then define the data componentsrequired to adequately model your system to support theprocess of your organization.

Define model components

Define the components required to adequatelymodel the real world objects of your system.

Construct data model

Build a logical data model based on your findings.Use the ArcGIS electric distribution data model as a guidefor determining the objects, attributes, and classes for yourdesign.

Constructing a logical data model is an interactive processand an art that is acquired through experience. While thereis no single “correct” model, there are good models andbad models. It is difficult to determine when your datarequirements are correctly modeled and complete, but anindication that you are coming close is when you cananswer “yes” to the following questions:

• Does the logical data model represent all data withoutduplication?

• Does the logical data model support an organization’sbusiness rules?

• Does the logical data model accomodate differentviews of data for distinct groups of users?

For more information about creating a logical data model,see Modeling our World.

Step 2: Build a physical database model

The physical database model defines the database schema,class structure of objects, and how rules and relationshipsare implemented. The physical database model is builtfrom the logical data model, and is generally constructedby a relational database specialist. The geodatabase is aphysical implementation of data that allows a structuresimilar to the logical data model. As such, most physicaldatabase models are directly supported by the existing

Generating code

The CASE tools subsystem of ArcInfo 8 has two parts:the Code Generation Wizard, and the Schema CreationWizard. The Code Generation Wizard allows you tocreate custom COM objects for each component of yourgeodatabase.

More information on the ESRI object model and ongenerating code for your custom objects using the CodeGeneration Wizard, see Modeling Our World and theArcInfo Developer’s Guide.

In the previous sections we have discussed database designand some general methods for implementing ArcGISElectric Distribution. In this section we will examine ingreater detail the process of implementing from aMicrosoft Repository. This case study reviews theimplementation from installation to deployment anddirects you to references and task descriptions for eachstep in the process. This scenario was selected because itcontains tasks common to most methods ofimplementation.


framework of the geodatabase. In most cases, the logicaldata model is directly implemented into the geodatabase -greatly simplifying the traditional task of physical databasemodeling.

Step 3: Determine customization requirements

Compare your logical data model and physical databasemodel to the ArcGIS electric distribution model todetermine your implementation requirements. The resultsof your comparison will show which of the featureclasses, subtypes, attributes, relationships, and domains areapplicable for your data model.

Define which rules and behaviors must be createdthrough customization of the geodatabase, orthrough custom applications built using thegeodatabase framework.

For more information about customizing ageodatabase, see Building a Geodatabase and Modeling ourWorld.

Step 4: Generate a custom geodatabase

Use ArcCatalog CASE tools to create schema and codereferencing an existing repository.

ArcCatalog uses CASE tools to read the MicrosoftRepository database you created using the UML modelingsoftware (Visio). The CASE tool guides you through theprocess of creating new feature classes, tables, and otherpieces of your geodatabase using the Schema CreationWizard.

During the schema generation process, you will bepresented with an hierarchical list of all of the row,feature and network feature types in the repository. Manyof objects and features contain subtypes with attributedomains and default values.

IMPLEMENTING ARCGIS ELECTRIC

If the schema you are generating contains attributedomains, you can view the properties for these domains,but you cannot modify them.

For more information about generating ageodatabase from a repository, see Building aGeodatabase, Using ArcCatalog, and Modeling Our World.

Step 5: Edit the schema using ArcCatalog

Use ArcCatalog to modify the schema of yourgeodatabase and add behavior. No programming isrequired when you use the data management toolsin ArcCatalog.

Using ArcCatalog you can add behavior to thegeodatabase by creating object classes, subtypes,validation rules, relationships, and a geometric network.

A tutorial for this process is available in the book Buildinga Geodatabase, Quick Start Tutorial, Chapter 2.

Step 6: Load your data into the schema

In case of versioned simple, network, or custom objects,an edit session is required to insert new records into thetable or feature class to ensure that the networkconnectivity and version information is managed correctly.this data loading operation is performed with the ObjectLoader Wizard in ArcMap.

For more information on the Object Loader, see Building aGeodatabase, Chapter 10, Editing your geodatabase.

You do not have the option of selecting a relationshipclass as you do with tables and feature classes. This is thecase because the presence of a relationship class isdependent upon the existence of the feature classes ortables that are related by it.

The CASE tool schema generator manages whether arelationship class is created based on feature classes andtables that you select.


Generating a geodatabase from a repository

The following section shows, in detail, how to generate acustom geodatabase from an existing repository. Theexample uses one of the sample ArcGIS ElectricDistribution Repositories, but the process would be thesame if you customized the UML model and created yourown repository.

1. After creating the repository, you will need to startArcCatalog and create a Personal Geodatabase. InArcCatalog, navigate to the folder in which you wantto create the geodatabase.

2. In the Catalog tree, click the folder, then right-click,point to New, and click Personal Geodatabase. Type aname for your personal geodatabase and press Enter.

3. Right-click the geodatabase, point to New and clickFeature Dataset.

4. Type a name for the new feature dataset in yourpersonal geodatabase. After entering a name you needto Enter or Select a Coordinate System for your featuredataset. In the Feature Dataset form select the Editbutton and the Spatial Reference Properties form willdisplay.

5. Click Edit in the Spatial Reference section.

All of the feature classes in a feature dataset must sharethe same Spatial Reference. You can use the CoordinateSystem of an existing dataset (for example, a landbasecoverage) to set the Spatial Reference. Be sure that theextent of the dataset is the same as, or greater than, thatof all of the feature classes that you’ll load into thedataset.


6. Select or Import a Coordinate System for your Dataset.

For more information about setting a Spatial Referencesee Building a Geodatabase and Using ArcCatalog.

Once the Spatial Reference is set, the next step is to addthe CASE tool to an ArcCatalog toolbar, so you can createthe Geodatabase Schema.

7. In ArcCatalog, right-click on any of the toolbars andclick Customize.

8. Click the Commands Tab and click Case Tools in theCategories list.

9. Click and drag Schema Wizard from the Commands listonto an existing toolbar, then Close the Customizedialog. The Schema Wizard tool is shaded grey(disabled) when you close the customize dialog if youdo not have a Geodatabase or a Feature Datasetselected.

10. Click the feature dataset in the Catalog tree.

Clicking the dataset activates the Schema Wizard tool andwill allow you to import the repository you created fromthe UML model.

11. Click the Schema Wizard tool, to start the SchemaCreation Wizard.

12. A brief introduction to the wizard appears. ClickNext.


13. Click Browse and navigate to the repository youcreated. In most cases you will not have to enter a username and password unless you specified one whileexporting the UML model.

14. Click Next.

A repository may contain several object models.

15. Click the object model you created in the repository,then click Next.

The Schema Wizard begins importing the objects. Thismay take several minutes, depending upon the size of yourobject model. After the Schema Wizard finishes with theobject import, you will be able to see a tree view of theobjects that will be imported into your Geodatabase.

All the objects in your object model are selected to beimported by default. You may uncheck the checkbox forthe Feature Dataset in which case, only the objects definedoutside the Feature Dataset will be imported. Click theplus and minus sign located next to the Feature Dataset toexpand and contract the tree view.


16. In the Schema Creation form you can highlight anobject and view the object’s properties by clicking theProperties button (or simply double-click the object inthe tree view). You may also modify certain propertiessuch as string field lengths, relationship primary/foreignkeys, or the spatial reference of the Feature Dataset.

17. The Schema Wizard creates a Geometric Networkautomatcially for you if you did not define one in yourUML model and your model contains at least onenetwork feature. You may override the generic nameassigned to the network by selecting the network andclicking on the Properties button (or double-click thenetwork). Type the new name for your network andclick OK. Click Next.

18. The wizard presents a summary of the feature andobject classes you’ve chosen to create. Click Finish.


The Schema Wizard creates the feature classes, tables, andother objects, such as domains, relationships, and networkconnectivity rules, that you defined in your object model.This may take several minutes.

19. Double-click the dataset to view its contents.

Your Geodatabase now contains the objects (featuredataset, feature classes, tables, relationships, and ageometric network) that were defined in your objectmodel and generated by the Schema Wizard.

The next step is to load your existing data into the emptyfeature classes and tables. You can load data into thefeature classes with ArcCatalog, using the Simple DataLoader, or you can load data with ArcMap. The steps toload data from ArcCatalog are presented below.

Loading data with ArcCatalog

1. In the Catalog tree view, right-click the feature class andclick Load Data.

2. Click the browse (folder Icon) button, navigate to andselect the input data you want to load. After selectingthe data file, you will see the data file displayed in theInput data field.

3. Click the Add button to add the data to the List ofsource data to load window.

Selecting the file from the List of source window willactivate the Remove button.

4. Click Next.

5. In the Simple Data Loader form, the radio button ‘I donot want to load all features into a subtype’ will beactive. All other fields are disabled. Click Next.


6. For each Target Field in the list, click the MatchingSource Field and match the fields and data types.

One important step in creating your electric distributionmodel is to duplicate the data types of the fields that existin your existing data. This will ensure a smooth data loadtransition from source to target fields.

7. After matching all the data types, click Next.

8. If the source coverage or shapefile contains onlyfeatures of the type you are loading, you can use thedefault option, Load all of the source data. ClickNext, and you’ll be be presented with a summary ofthe data loading operation.

Sometimes you will want to load only a selected group offeatures from your source data into a given feature class.This would be the case if you have been using a singleconverage feature class or shapefile to hold several typesof features differentiated by an attribute.

9. If you want to load selected features, click ‘Load onlythe features that satisfy a query’. Click Query Builder.

The Query Builder allows you to select which features toload, based upon the values of one or more attributes.

10. Double-click the field that you want to query on,click an operator (such as the equals sign), then double-click on a value of that field in the Unique values list.

Clicking Clear will clear the query and clicking Verify willverify the query you create.

11. Click OK, then click Next on the Simple DataLoader.


12. The data loader shows a summary of the data loadingoperation. Click Finish. When you click Finish, thedata loading operation begins.

A status bar at the lower left corner or the ArcCatalogwindow shows the number of objects being loaded intothe feature class.

Loading data with ArcMap

You also can use ArcMap’s Object Loader to load data intoa feature class in a versioned geodatabase. In fact, youmust use ArcMap to load data into non-simple featureclasses, such as network feature classes or feature classesthat participate in composite relationships.

1. Start ArcMap and click the Add Data button on theStandard Toolbar.

2. Navigate to the empty feature class and add it to themap.

3. Right-click over a toolbar and click Customize.

4. Click the check box to turn on the Editor toolbar.


5. Click the Commands Tab, and click Data Converters.

6. Click and drag Load Objects onto the Editor toolbar.Close the Customize dialog.

In order for you to use the Load Objects button you willneed to start an Edit session.

7. Click Editor and click Start Editing.

8. Select a feature class and subtype (if applicable) in theTargets dropdown list.

9. Click Load Objects.

The Object Loader Wizard appears.

Use the same steps to load data with the ArcMap ObjectLoader Wizard as you would use to load data with theSimple Object Loader.

One difference between the Simple Data Loader and theObject Loader, is that if you use the Object Loader youwill be prompted to choose whether to snap the inputfeatures using the Editor’s current snapping environment,and whether to use validation rules to validate the featuresyou load.

Snapping is useful when you have some features alreadyloaded and on the map, and you want to make sure thatthe new features snap to the existing features. If yourfeatures are precisely located with respect to the existingfeatures, you do not need to snap them.


If you choose to validate features, the Object Loader willapply any attribute, relationship and connectivity rulesthat exist in your schema to the features. Invalid featureswill be loaded into your geodatabase, but will remainselected.

46 • Geographic Analysis DRAFT 7/17/98

47

StrStrStrStrStructuructuructuructuructures Daes Daes Daes Daes DatatatatataModel RefModel RefModel RefModel RefModel Referererererenceenceenceenceence344444


1234567890123456789012345678901212345678901234567890123456712345678901234567890123456789012123456789012345678901234567123456789012345678901234567890121234567890123456789012345671234567890123456789012345678901212345678901234567890123456712345678901234567890123456789012123456789012345678901234567123456789012345678901234567890121234567890123456789012345671234567890123456789012345678901212345678901234567890123456712345678901234567890123456789012123456789012345678901234567123456789012345678901234567890121234567890123456789012345671234567890123456789012345678901212345678901234567890123456712345678901234567890123456789012123456789012345678901234567123456789012345678901234567890121234567890123456789012345671234567890123456789012345678901212345678901234567890123456712345678901234567890123456789012123456789012345678901234567123456789012345678901234567890121234567890123456789012345671234567890123456789012345678901212345678901234567890123456712345678901234567890123456789012123456789012345678901234567123456789012345678901234567890121234567890123456789012345671234567890123456789012345678901212345678901234567890123456712345678901234567890123456789012123456789012345678901234567123456789012345678901234567890121234567890123456789012345671234567890123456789012345678901212345678901234567890123456712345678901234567890123456789012123456789012345678901234567123456789012345678901234567890121234567890123456789012345671234567890123456789012345678901212345678901234567890123456712345678901234567890123456789012123456789012345678901234567123456789012345678901234567890121234567890123456789012345671234567890123456789012345678901212345678901234567890123456712345678901234567890123456789012123456789012345678901234567123456789012345678901234567890121234567890123456789012345671234567890123456789012345678901212345678901234567890123456712345678901234567890123456789012123456789012345678901234567

Structure

AerialMarker FacilityStructure Pushbrace WarningSign Guy Riser

SupportStructure EquipmentEnclosure AnchorGuy SpanGuy

SurfaceStructure ElectricStation SwitchingFacility

Feature

STRUCTURES OVERVIEW

Structures support electrical transmission and distribution equipment and can be located overhead, on the ground, orunderground.

STRUCTURES

Chapter 4 • Structures Component Reference • 49

123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234

1234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123

StructuresStructure is an abstract class whose attributes are inherited by features that supportelectrical transmission and distribution equipment. Structures can be locatedoverhead, on ground surface, or underground.

Overhead structures are designed to support mechanical loads imposed by con-ductors and equipment as well as additional loads presented by wind, ice, and/orsnow. ANSI-provided specifications and dimensions rate poles, which aregrouped into classes based on their circumference 6 feet from the butt. Poles of acertain class and length are designed to have about the same load carrying capac-ity.

Overhead structures, such as poles, H-frames, and towers, vary in material,height, and guying and/or bracing requirements based on the combination ofanticipated vertical and horizontal loads. Surface structures house equipment onthe ground including pedestals, enclosures, and pads.

Structure defines the following attributes:

Comments: text — User or designer comments

InstallationDate: date — Date structure was installed

WorkOrderID: text — Utility identifier of work order

Facility StructureFacilityStructure is an abstract class containing common attributes of theEquipmentEnclosure abstract class and the SupportStructure feature class (H-frames, poles, towers). EquipmentEnclosure includes these feature classes (andsubtypes): SurfaceStructure (pads, pedestals, connections boxes), ElectricStation(main, net, substations), and SwitchingFacility (junctions cabinets, switchboards).

FacilityStructure defines the following attributes:

FacilityID: text — Meaningful company-assigned unique identifier

Owner: text — Code indicating owner of structure; domain values includeCustomerOwned, LocalBell, PowerCompany, OtherUtility

Subtype: long integer — Code indicating type of structure

SymbolRotation: double — Angle of rotation dictating how a feature appears onthe map

Subtypes: None

Associations: Electric Device, Electric Location

Structure

CommentsInstallationDateWorkOrderID

Feature

Structure

Feature

FacilityStructure

FacilityIDOwnerSubtypeSymbolRotation


123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345

Support StructureSupportStructure is a subclass of FacilityStructure describing objects that supportelectric devices. Although many underground distribution systems are now beingbuilt, a tremendous amount of overhead plant is still in use. Overhead poles aresubject to vertical and horizontal forces including weight of wires, transformers,and other equipment. Vertical forces are the unbalanced component of wiretension at curves and corners, the pull of service drops, and the horizontal com-ponent of weight if the pole is not vertical. Wood poles have long been used foroverhead distribution because of abundance of material, ease of handling andcost. Preservatives help to prolong the life of the pole. The strength of a woodpole must be sufficient to withstand abnormal loads as well, such as ice and windpressure.

SupportStructure features can have street lights, assemblies, and other attach-ments associated with them. SupportStructure inherits characteristics from theabstract classes Structure and FacilityStructure.

SupportStructure defines the following attributes:

Class: text – Code indicating class of structure; domain values include Class 1,Class 10, H1, etc.

Diameter: double – Diameter of structure

FoundationType: text – Code indicating foundation used to set support struc-ture; domain values include Set on Concrete Foundation, Set Extra Deep inEarth, etc.

Grounded: text — Code indicating whether structure is grounded; domainvalues are Yes or No

Height: text — Code indicating height of structure; domain values include 20Feet, 25 Feet, 30 Feet, 40 Feet, etc.

Manufacturer: text — Manufacturer

Material: text — Code indicating material of structure; domain values includeAluminum, Fiberglass, Wood, etc.

PoleCount: long integer — Number of poles present in H-frame structure

Style: text — Code indicating style of SupportStructure; domain values includeDecorative, Normal

TreatmentType: text — Code indicating type of treatment used, if any; domainvalues include Creosote, Paint, Pentachlorophenol, Chromated Copper Arsen-ates, etc.

UsageType: text — Code indicating use of structure; domain values includeDistribution 2-Pole Structure, Street Light, Transmission, etc.

YearManufactured: text — Year structure was manufactured

Subtypes: H-Frame, Non-Wood Power Pole, Wood Power Pole, Non-WoodStreet Light Pole, Wood Street Light Pole, Tower

Associations: Assembly, Foreign Attachment, StreetLight (valid only for sub-types Non-Wood Street Light Pole and Wood Street Light Pole)

SupportStructure

ClassDiameterFoundationTypeGroundedHeightManufacturerMaterialPoleCountStyleTreatmentTypeUsageTypeYearManufactured

Structure

FacilityStructure

Feature

Chapter 4 • Structures Data Model Reference • 51

123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345

123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345

SurfaceStructureSurfaceStructure contains objects that protect or enclose electric circuits andequipment on the ground.

SurfaceStructure defines the following attributes:


Material: text — Code indicating material enclosing SurfaceStructure; domainvalues include Fiberglass, Concrete, Tin, Other, etc.

Model: text — Model type of SurfaceStructure

Name: text — Name of SurfaceStructure

StructureSize: text — Size of SurfaceStructure

Associations: None

Subtypes: Connection Box, Enclosure, Mat, Non-Electric Enclosure, Pad,Pedestal

Electric StationElectricStation represents a building or fenced-in enclosure that houses theequipment that switches and modifies the characteristics of energy from a genera-tion source. Distribution systems include primary feeders (circuits), transformerbanks, and secondary circuits (overhead or underground) that serve a specifiedarea. Distribution substations operate at 13.8 to 69 kV and usually have a numberof radial three-phase feeders off whichbranch lines, or laterals, are tapped to deliverpower to residences, stores, garages, andother loads.

Transmission substations operate at 69 to 765kV. Voltages of 345, 500 and 765 kV areconsidered extra high voltage (EHV).

ElectricStation defines the following at-tributes:

Name: text — Name of ElectricStation

StationNumber: text — Utility-assignednumber of ElectricStation

Associations: None

Subtypes: Main Station, Net Station, SubStation

Structure

FacilityStructure

EquipmentEnclosure

Feature

SurfaceStructure

ManufacturerMaterialModelNameStructureSize

Structure

FacilityStructure

EquipmentEnclosure

Feature

ElectricStation

NameStationNumber


123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123

123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345

Switching FacilitySwitchingFacility is the feature class representing structures that support orenclose switching and associated equipment including transformers, buses,switchgears, and fuses. Automated feeder switching systems control individualcircuits and reduce the occurrence and duration of faults and optimize feeder andsubstation loading.

SwitchingFacility defines the following attributes:

Configuration: text — Configuration of SwitchingFacility


Model: text — Model of enclosure

NominalVoltage: long integer — Code indicating system voltage for whichSwitchingFacility is rated; domain values include 14.6kV, 24.9kV, 34.5kV

Associations: BusBar

Subtypes: Auto Transfer Enclosure, Junction Cabinet, Two-Cabinet Pad-Mounted Switchgear, Four-Cabinet Pad-Mounted Switchgear, Switch Board

Aerial MarkerAn AerialMarker indicates the presence of overhead cable and structures.AerialMarker defines the following attributes:

LightIndicator: text — Code indicating presence of light indicator; domainvalues are Yes and No

SymbolRotation: double — Angle of rotation dictating how a feature appears onmap

Associations: None

Subtypes: None

Structure

FacilityStructure

EquipmentEnclosure

Feature

SwitchingFacility

ConfigurationManufacturerModelNominalVoltage

Structure

Feature

AerialMarker

LightIndicatorSymbolRotation

Chapter 4 • Structures Component Reference • 53

1234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234

123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123

GuyGuy is an abstract feature class that inherits the attributes of the abstract classStructure. Guy includes the wire or collection of wires that support poles, H-frames, or towers. Guys are used to add support if the horizontal load is greaterthan the pole can safely support and when conductor tensions aren’t balancedsuch as at dead ends, corners, or where the direction of the conductor changessuddenly. Guy wire is made of cable available in several diameters and strengths.

Guy defines the following attributes:

GuyCount: long integer — Number of wires in guy assembly; range of 1 to 4

LeadLength: short integer — Distance from support structure to anchor

WireMaterial: text — Code indicating wire material; domain values includeSteel, Other

WireSize: text — Code indicating size of guy wire used; domain values include1/2”, 3/8”, 5/16”, etc.

WireStrength: text — Code indicating strength rating of wire composing theguy; domain values include Common, High Strength, etc.

Associations: None

Subtypes: None

Anchor GuyAnchorGuy is a wire or set of wires running from the top of the pole to ananchor installed in the ground and consist of wires, appropriate fastenings andthe anchor. The anchor guy is usually installed at a distance from the pole that is0.25 to 1.5 of the height of the attachment such that the slope is about 1:1.Sidewalk guys have a horizontal strut that is attached about halfway down thepole to provide pedestrian clearance. The guy runs from the top of the pole tothe top of the strut, then down to the anchor.

AnchorGuy defines the following attributes:

AnchorSize: short integer — Diameter of anchor

AnchorType: text — Code indicating type of anchor; domain values includeCone, Expanding, Log, Plate, Screw

RodType: text — Code identifying type of anchor fastening; domain valuesinclude Double Eye, Single Eye

Subtype: long integer — Code indicating subtype of anchor guy


Associations: None

Subtypes: Back, Bridle, Sidewalk, Standard

Structure

Feature

Guy

GuyCountLeadLengthWireMaterialWireSizeWireStrength

Structure

Guy

Feature

AnchorGuy

AnchorSizeAnchorTypeRodTypeSubtypeSymbolRotation


123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123

12345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123

12345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123

Span GuySpan guys are installed to span from the top of one structure or pole to the otherand offset the strain from the line conductor. Span guys transmit horizontal forceto another pole until an anchor guy can be used. SpanGuy is a linear feature andinherits attributes of Guy and Structure abstract classes.

Associations: None

Subtypes: None

PushbracePushbraces support or brace a pole when it is not feasible to use an anchor guy. Apushbrace is a pole or other member that is placed at an angle to help support theunbalanced pole and is often used on the inside curve of mountain roads. Thepoles that pushbraces support are grouped intoclasses based on their circumference 6 feet from thebutt.

Pushbrace is a point feature that defines the fol-lowing attributes:

Class: text — Code indicating class of polesupported by Pushbrace; domain values includeClass 1, Class, 10, Class H1, etc.

Height: text — Code indicating height ofPushbrace; domain values include 20 Feet, 25Feet, etc.

Material: text — Material of Pushbrace; domainvalue is Wood

SymbolRotation: double — Angle of rotationdictating how a feature appears on map

Associations: None

Subtypes: None

RiserA Riser is a cylindrical or channel enclosure attached to a pole or structure toprovide protection for underground conduit as it transitions from overhead tounderground. The physical connection between the overhead and undergroundconnection occurs at a pothead. Riser defines the following attributes:

ConstructionType: text — Code indicating construction type of Riser; domainvalues include 1 Phase Pothead, 3 Phase Riser with Fiberglass Arms, etc.Height: short integer — Mounting height of riser on SupportStructure

Material: text — Code indicating material of riser; domain values includeFiberglass, PVC, etc.

SymbolRotation: double — Rotation angle dictating how feature appears on map

Associations: None

Subtypes: None

Structure

Guy

Feature

SpanGuy

Structure

Feature

Pushbrace

ClassHeightMaterialSymbolRotation

Structure

Feature

Riser

ConstructionTypeHeightMaterialSymbolRotation


12345678901234567890123456789012123456123456789012345678901234567890121234561234567890123456789012345678901212345612345678901234567890123456789012123456123456789012345678901234567890121234561234567890123456789012345678901212345612345678901234567890123456789012123456123456789012345678901234567890121234561234567890123456789012345678901212345612345678901234567890123456789012123456123456789012345678901234567890121234561234567890123456789012345678901212345612345678901234567890123456789012123456123456789012345678901234567890121234561234567890123456789012345678901212345612345678901234567890123456789012123456123456789012345678901234567890121234561234567890123456789012345678901212345612345678901234567890123456789012123456123456789012345678901234567890121234561234567890123456789012345678901212345612345678901234567890123456789012123456

1234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123123456789012312345678901231234567890123

Warning SignWarning sign indicates the presence of electric lines, structures, or devices.WarningSign defines the following attributes:



Joint Use AttachmentOther utilities or entities may attach conductors or cables that carry signals suchas community antenna television systems (CATV) to support structures. Informa-tion about owners and joint use attachments is captured in this table. This relatedobject class stores information about a feature with a spatial reference but doesnot itself have a location on the map.

JointUseAttachment defines the following attributes:

AttachmentDate: date — Date object was attached to structure

Chargeable: text — Code indicating whether JointUseAttachment is charge-able, domain values are Yes or No

Owner: text — Code indicating owner of attachment; domain values includeCable, Telephone, Other, etc.

StructureObjectID: long integer — ObjectID of structure supporting attachment

Association: Support Structure

Subtypes: None

Structure

WarningSign

FacilityIDSymbolRotation

Feature

SupportStructureAssembly

FramingTypeStructureObjectID

JointUseAttachment

AttachmentDateChargeableOwnerStructureObjectID

ClassDiameterFoundationTypeGroundedHeightManufacturerMaterialPoleCountStyleTreatmentTypeUsageTypeYearManufactured


1234567890123456789012345678912345678901234567890123456789123456789012345678901234567891234567890123456789012345678912345678901234567890123456789123456789012345678901234567891234567890123456789012345678912345678901234567890123456789123456789012345678901234567891234567890123456789012345678912345678901234567890123456789123456789012345678901234567891234567890123456789012345678912345678901234567890123456789123456789012345678901234567891234567890123456789012345678912345678901234567890123456789123456789012345678901234567891234567890123456789012345678912345678901234567890123456789123456789012345678901234567891234567890123456789012345678912345678901234567890123456789

AssemblyAssembly identifies the type of structure and attachment connection. Assemblydefines the following attributes:

FramingType: text — Code indicating type of assembly frame; domain valuesinclude A Frame, H Frame, etc.

StructureObjectID: long integer — Object ID of structure supporting assembly

Association: Support Structure

Subtypes: None

Lifecycle HistoryLifecycleHistory is an abstract object provided so that administrators can relateinformation about the history of particular devices or equipment. This informa-tion is related to devices that have a spatial reference but is itself non-spatial.Define specific LifecycleHistory objects on an as-needed basis. As a newLifecycleHistory object is defined, you should also define any necessary relation-ships.

LifecycleHistory defines the following attributes:



WorkFunction: text — Code indicating life cycle phase; domain values includeInstall, Remove, Replace, Transfer, Retire, Abandon


Associations: To be defined by user

Subtypes: None

Object

Inspection

CommentsFacilityIDInspectionDateInspectionTypeInspector

LifecycleHistory

CommentsFacilityIDWorkFunctionWorkOrderID


InspectionStructures and devices are periodically inspected to ensure proper functioning andquality. The abstract class Inspection provides a way to define this information forstructures, devices, controls, and units. Define specific Inspection objects on an as-needed basis. As a new Inspection object is defined, you should also define anynecessary relationships.

Inspection defines the following attributes:



InspectionDate: date — Date inspected

InspectionType: text — Code indicating type of inspection; domain valuesinclude History, Inspection, Maintenance

Inspector: text — Name of inspector

Associations: To be defined by user

Subtypes: None


12345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012

UNDERGROUND STRUCTURES

Underground structures describe the features and objects needed to support anunderground electric system, including URD (underground residential distribu-tion). UndergroundStructure is a simple junction feature that includes vaults andmanholes that house and protect electrical equipment. The central component ofURD and other underground systems is the single-phase distribution transformerwhich is usually housed in heavy, corrosion-resistant tanks for installing in subsur-face vaults, known as submersible.

Most URDs include the following components: pad-mounted, dead-front trans-former; primary laterals operated as open loops; 12.47 grounded Y/7.2 kV pri-mary voltage; two primary cable connections per transformer; front-lot construc-tion; four to eight homes per transformer; internal fusing; and direct-buriedcables.


ComplexEdgeFeatureRelationshipClass

ConduitSystem

BuriedDepthConfigurationEncasementTypeFacilityIDInstallationDateLabelTextLengthSourceManufacturerMeasuredLengthModelSubtypeWorkOrderID


CommentsFacilityIDInstallationDateManufacturerMaterialModelStructureSizeStructureTypeSubtypeWorkOrderID

ConduitSystem_ConduitSystemMemberCrossReference

PhaseDesignationULS_Position


UndergroundStructure defines the following attributes:



InstallationDate: date — Date of installation

Manufacturer: text — Manufacturer of UndergroundStructure

Material: text — Material of UndergroundStructure

Model: text — Model

StructureSize: text — Size of structure

StructureType: text — Type of UndergroundStructure

Subtype: long integer — Code indicating subtype of UndergroundStructure

WorkOrderID: text — Utility work order identifier

Associations: ElectricDevice, ElectricLocation

Subtypes: Hand Hole, Manhole, Vault

Conduit SystemThe underground system consists of ducts, direct buried cables, or pipes extend-ing between vaults or manholes. New conductor and telephone cable are ofteninstalled underground in congested areas. Conductors and cables can be drawn orpulled from manhole locations for repairs or changes.

Conduits, or underground linear structures, are constructed of materials that areimpervious to water and do not degrade or corrode easily. Cable also may beburied directly in trenches, which ArcFM models as a ConduitSystem feature. Inthis case, ducts are used as placeholders for the position of cables and conductorsassociated with the trench. Cables are associated with conduits through an attrib-uted relationship class called ConduitSystem_ConduitSystemMember CrossReference. The user creates this relationship class to relate feature classes withmodel name ULS to feature classes with model name ULSMember.

The ConduitSystem feature class contains information about the position andcharacteristics of ducts as seen from a manhole, vault, or a cross section of atrench and duct. Users can create duct characteristic fields to represent theirbusiness processes. Common materials are concrete, plastic, and fiberglass. Com-mon duct diameters are 3 to 5 inches. Names of characteristics such as materialor size are assigned by the user when creating the Duct Definition object class.This table contains only field names that describe the duct. The values of thesefields, such as steel or 5 inches, are stored for each duct in a COM object which isstored in the Configuration attribute field of the ConduitSystem feature class.


123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345

ConduitSystem defines the following attributes:

BuriedDepth: text — Depth from top of conduit to ground line

Configuration (see Duct Definition): blob — Stores information about duct orposition layout within the conduit in a COM object; stores the values ofattribute fields created in Duct Definition object class

EncasementType: text — Code indicating encasement type; domain valuesinclude Backfill, Concrete, Unknown

FacilityID: text — Meaningful utility-assigned unique identifier

InstallationDate: date — Date of installation

LabelText: text — Stores a string to label conduit on map

LengthSource: text — Source of length measurement; domain values are Map-ping System, Field Measurement


MeasuredLength: double — Length of UndergroundLinearStructure


Subtype: long integer — Code indicating subtype of ConduitSystem


Associations: UndergroundStructure

Subtypes: Duct Bank, Trench

Configuration FieldThis single binary large object (blob) attribute field of the ConduitSystem featureclass stores a COM object containing information describing the layout of theconduit. This includes the value of fields defined in the Duct Definition objectclass. Users can create fields in the Duct Definition table such as those listedbelow. The values of these fields, entered or edited when users place conduits onthe map, are stored in the Configuration field. Utility administrators can maintain,query, and edit values in this field.

Duct DefinitionThe user creates the DuctDefinition object class with fields that describe selectedcharacteristics of a duct, such as size or material. The attribute names listed tothe left are provided as an example.

Object Class

Duct Definition

AvailabilityDuctIDDuctSizeMaterialSubtype

61

CirCirCirCirCircuit Secuit Secuit Secuit Secuit SegmentsgmentsgmentsgmentsgmentsData ModelData ModelData ModelData ModelData ModelRefRefRefRefReferererererenceenceenceenceence

55555


12345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789

CIRCUIT SEGMENTS

ELECTRIC COMPLEX EDGE

ElectricComplexEdge contains the common attributes of primary, secondary,overhead, and underground conductors. ElectricComplexEdge is an abstract classthat includes subclasses such as busbars and communication cable. These arerepresented as complex edge features because multiple devices can be connectedalong their edge. Circuits are modeled with options for feeder identifiers tosupport automated switching and tracing functions.

SCADA applications in distribution systems are increasing in deregulated environ-ments. Automated switching of feeder circuits involves supervisory control tosupport operator control of equipment. Data acquisition gathers telemetered datafrom a variety of sources to increase reliability and operator productivity.

ElectricComplexEdge defines the following attributes:

LengthSource: text — Code indicating source of length measurement; domainvalues include Field Measurement, Mapping System

MeasuredLength: long integer — Length of ElectricComplexEdge

Subtype: long integer — Code indicating subtype of ElectricComplexEdge


ElectricComplexEdge

LengthSourceMeasuredLengthSubtypeWorkOrderID

ComplexEdgeFeature

Chapter 5 • Circuit Segments Component Reference • 63

12345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789

Electric Line SegmentElectricLineSegment is an abstract class that captures information about the con-figuration and connectivity of conductors. Electric line segments are categorizedby voltage and are either overhead or underground conductors.

ElectricLineSegment represents circuits often referred to as feeders. Primary con-ductors originate at a main distribution center and supply one or more substa-tions. Secondary networks are supplied by five or more primary feeders to keeptransformer loading at 125 percent in the event of an outage. Capacitors reducevoltage drop along the feeder.

Feeder management systems are created to determine which circuit a given elec-trical device belongs to (i.e., which source, or in looped system, sources feed itwith power), and which of its electrical phases are energized on the primary side.This information can be used to create circuit maps and visually distinguishamong different feeder systems. The subtypes of these ElectricLineSegments areprimary, secondary, single-phase and three-phase. ElectricLineSegment defines thefollowing attributes:

ElectricLineObjectID: long integer — Object ID of associated ElectricLine

ElectricTraceWeight: long integer — Used by Feeder Manager to determinedevice status and other information that affects circuit connectivity

FeederID: text — Feeder Manager identifier assigned to feeders and devicesthat participate in a specific distribution circuit

FeederID2: text — Feeder Manager identifier assigned if device is supplied bysecond feeder

FeederInfo: long integer — Feeder Manager-assigned phase information describ-ing the phase of the circuit

LabelText: text — Provides text for line annotation

NeutralMaterial: text — Material of neutral wire; domain values include AllAluminum Conductor, Copper, etc.

NeutralSize: text — Size of neutral wire; domain values include 1/0 AWG,1000 Concentric Neutral, etc.

NominalVoltage: long integer — Code indicating system voltage; domain valuesinclude 7.2 kV Grounded Y, 24.9 kV Grounded Y, 2400 Delta, etc.

OperatingVoltage: long integer — Code indicating standard level at which systemis currently being operated that may vary above or below nominal voltage;domain values include 120 Volts, 480 Volts, etc.

PhaseDesignation: long integer — Code indicating phases present; domain valuesinclude A, AB, AC, etc.

ServiceIndicator: text — Indicates whether circuit is in service; domain valuesare Yes and No

Associations: ElectricLine

Subtypes: None

ElectricComplexEdge

ComplexEdgeFeature

ElectricLineSegment

ElectricLineObjectIDElectricTraceWeightFeederIDFeederID2FeederInfoLabelTextNeutralMaterialNeutralSizeNominalVoltageOperatingVoltagePhaseDesignationServiceIndicator


ConductorInfoThe conductors used in distribution are most often made of aluminum or copper.ConductorInfo stores information about material and other properties of theconductors that compose circuits. For a given current, a circuit’s resistance is theaverage rate at which electrical energy is converted to heat.

This object class is associated with linear features but does not itself have alocation on the map. ConductorInfo defines the following attributes:

AbandonedConductorObjectID: text — Object ID of AbandonedConductorfeature class that maintains user-defined attribute values

ConductorMaterial: text — Code indicating material of conductor; domainvalues include Copper, Aluminum, Steel, etc.

ConductorSize: text — Size of conductor

InstallationDate: date — Date conductor was installed

InsulationType: text — Code indicating type of insulation; domain valuesinclude

InsulationVoltage: text — Rated voltage

Manufacturer: text — Conductor manufacturer

NumberConductorsPerPhase: long integer — Code indicating phases present;domain values include A, AB, AC, etc.

OverheadConductorObjectID: long integer — ObjectID of related overhead con-ductor

PhaseDesignation: long integer — Phase designation of conductor; domain valuesinclude A, ABC, etc.

ReelNumber: text — Number of cable reel

UndergroundConductorObjectID: long integer — ObjectID of related undergroundconductor

Associations: AbandonedElectricLineSegment

Subtypes: Primary Overhead, Primary Underground, Secondary Overhead,Secondary Undergrund, and Streetlight Conductor

1234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789

Object

ConductorInfo

AbandonedConductorObjectIDConductorMaterialConductorSizeInstallationDateInsulationTypeInsulationVoltageManufacturerNumberConductorsPerPhaseOverheadConductorObjectIDPhaseDesignationReelNumberUndergroundConductorObjectID

Chapter 5 • Circuit Segments Data Model Reference • 65

AbandonedElectricLineSegmentThis feature class is created to maintain information about abandoned conduc-tors. Attributes of this feature class are user-defined and depend on which fieldvalues need to be maintained after a feature is abandoned.

Bus BarBusBar is a large rigid conductor that connects devices in switching facilities tofeed power to two or more circuits. Substation buses carry current in a confinedspace and need to have enough structural strength to support the stress of short-circuit current, high wind, and ice loading. Distribution substation buses are oftenmade of copper and aluminum tubing. Bus capacity is limited by heating effectsof the current. Other factors affecting the heating of a bus include size andshape, surface area, and ventilation. Tubular buses provides a larger cross-sec-tional area in a minimum space but is offset by a smaller surface area for dissipat-ing heat loss.

BusBar defines the following attributes:

BusBarShape: text — Shape of BusBar,which affects size of cross-sectional areaand heating

ElectricTraceWeight: long integer — Used byFeeder Manager to determine device statusand other information that affects circuitconnectivity

FdrMgrNonTraceable: long integer — Used byFeeder Manager if assigned model name toindicate that device is not to be included intracing

FeederID: text — Feeder Manager identifierassigned to feeder and devices that partici-pate in a specific distribution circuit

FeederID2: text — Feeder Manager identifierassigned if device is supplied by secondfeeder

FeederInfo: long integer — Feeder Manager-assigned phase information describing thephase of the circuit

Loading: text — Device capacity deliveredto load area, in MVA

NominalVoltage: long integer — Code indicating system voltage for whichBusBar is rated, domain values include 7.2 kV Grounded Y, 24.9 kVGrounded Y, 2400 Delta, etc.

OperatingVoltage: long integer — Code indicating standard level at which systemis currently being operated that may vary above or below nominal voltage;domain values include 120 Volts, 480 Volts, etc.

1234567890123456789012345678901212312345678901234567890123456789012123123456789012345678901234567890121231234567890123456789012345678901212312345678901234567890123456789012123123456789012345678901234567890121231234567890123456789012345678901212312345678901234567890123456789012123123456789012345678901234567890121231234567890123456789012345678901212312345678901234567890123456789012123123456789012345678901234567890121231234567890123456789012345678901212312345678901234567890123456789012123123456789012345678901234567890121231234567890123456789012345678901212312345678901234567890123456789012123123456789012345678901234567890121231234567890123456789012345678901212312345678901234567890123456789012123123456789012345678901234567890121231234567890123456789012345678901212312345678901234567890123456789012123123456789012345678901234567890121231234567890123456789012345678901212312345678901234567890123456789012123123456789012345678901234567890121231234567890123456789012345678901212312345678901234567890123456789012123123456789012345678901234567890121231234567890123456789012345678901212312345678901234567890123456789012123

ElectricComplexEdge

ComplexEdgeFeature

BusBar

BusBarShapeElectricTraceWeightFdrMgrNontraceableFeederIDFeederID2FeederInfoLoadingNominalVoltageOperatingVoltagePhaseDesignationSpacingSwitchingFacilityObjectID

CommunicationCable

Feature


12345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789

PhaseDesignation: long integer — Code indicating phases present on conductor;domain values include A, AB, AC, etc.

Spacing: text — Distance between buses following minimum electrical clear-ance for various BILs

SwitchingFacilityObjectID: long integer — Object ID of associatedSwitchingFacility

Associations: CircuitSource, SwitchingFacility

Subtype: BusBar

Communication CableCommunicationCable carries non-electric signals within the network. Structures,mainly poles, may be used under a joint ownership agreement or lease to supportpower and communication lines. Other utilities or entities may attach cables thatcarry signals such as community antenna television systems (CATV).CommunicationCable can also be used to control Supervisory Control and DataAcquisition (SCADA) equipment. CommunicationCable inherits the attributes ofElectricComplexEdge.

Overhead Electric Line SegmentOverhead electric line segments carry electric current and are supported by struc-tures including power poles, H-frames, and towers. The abstract classOverheadElectricLineSegment inherits the attributes of ElectricComplexEdge andElectricLineSegment.

OverheadElectricLineSegment defines the following attributes:

ConductorConfiguration: text — Code indicating configuration of conductors;domain values include Compact, Horizontal, Spacer, etc.

PhaseOrientation: text — Utility-specific order or configuration of phasespresent on conductor

Subtype: Single Phase Primary Overhead, Two Phase Primary Overhead, ThreePhase Primary Overhead, Single Phase Secondary Overhead, Three Phase Second-ary Overhead, and Streetlight Conductor

Underground Electric Line SegmentPrimary URD cables are usually single-conductor, concentric-neutral insulatedwith polyethylene or cross-linked polyethylene. Utilities may direct bury primary

ElectricComplexEdge

ComplexEdgeFeature

ElectricLineSegment

OverheadElectricLineSegment

ConductorConfigurationPhaseOrientation

Chapter 5 • Circuit Segments Component Reference • 67

123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901123456789012345678901

cables in the same trench as communication cables.

Secondaries and services are usually served by three cables insulated with poly-ethylene that may be separate cables or triplex construction.

UndergroundElectricLineSegment defines the following attributes:

BackfillMaterial: text — Code indicating material used to backfill; domainvalues include Concrete, Slurry, Soil, Other

BuriedDepth: double — Distance below grade to top ofUndergroundElectricLineSegment

CableCount: long integer — Code indicating number of cables; domain valuesinclude 1, 2, 3, etc.

InConduitIndicator: text — Code indicating whetherUndergroundElectricLineSegment is in conduit, values are Yes or No

Associations: ConduitSystem

Subtype: Single Phase Primary Underground, Three Phase Primary Under-ground, Single Phase Secondary Underground, Three Phase Secondary Under-ground, and Streetlight Conductor

ElectricComplexEdge

ComplexEdgeFeature

ElectricLineSegment

UndergroundElectricLineSegment

BackfillMaterialBuriedDepthCableCountInConduitIndicator


123456789012345678901234567890121234567890123412345678901234567890123456789012123456789012341234567890123456789012345678901212345678901234123456789012345678901234567890121234567890123412345678901234567890123456789012123456789012341234567890123456789012345678901212345678901234123456789012345678901234567890121234567890123412345678901234567890123456789012123456789012341234567890123456789012345678901212345678901234123456789012345678901234567890121234567890123412345678901234567890123456789012123456789012341234567890123456789012345678901212345678901234123456789012345678901234567890121234567890123412345678901234567890123456789012123456789012341234567890123456789012345678901212345678901234123456789012345678901234567890121234567890123412345678901234567890123456789012123456789012341234567890123456789012345678901212345678901234123456789012345678901234567890121234567890123412345678901234567890123456789012123456789012341234567890123456789012345678901212345678901234123456789012345678901234567890121234567890123412345678901234567890123456789012123456789012341234567890123456789012345678901212345678901234123456789012345678901234567890121234567890123412345678901234567890123456789012123456789012341234567890123456789012345678901212345678901234123456789012345678901234567890121234567890123412345678901234567890123456789012123456789012341234567890123456789012345678901212345678901234123456789012345678901234567890121234567890123412345678901234567890123456789012123456789012341234567890123456789012345678901212345678901234123456789012345678901234567890121234567890123412345678901234567890123456789012123456789012341234567890123456789012345678901212345678901234123456789012345678901234567890121234567890123412345678901234567890123456789012123456789012341234567890123456789012345678901212345678901234

Electric LineElectricLine is an object class provided to store information associated withconductors but does not have a location on the map.

ElectricLine defines the following attributes:

ID: text — Utility identifier of ElectricLine

Name: text — Name of ElectricLine

NominalVoltage: long integer — Code indicating system voltage for whichElectricLine is rated, domain values include 7.2 kV Grounded Y, 24.9 kVGrounded Y, 2400 Delta, etc.

Subtype: long integer — Code indicating subtype

Association: ElectricLineSegment

Subtypes: Circuit Line, Station Line

CircuitSourceA circuit (feeder) is the aggregate of the conductors and equipment downstreamof a substation breaker or recloser. CircuitSource stores attributes that describecharacteristics of the circuit measured or estimated at the breaker or recloser.These attributes include capacity, measured in kilowatts (kW); resistance, mea-sured in ohms; and load, which is measured in reactive kilovolt-amperes (kVAR).

Object

CircuitSource

BusBarObjectIDConnectionConfigurationDynamicProtectiveDevObjectIDEmergencyCapacityKWGroundReactanceFeederSourceInfoGroundResistanceIDMaximumCapacityKWMaxKVARMaxPositiveSequenceReactanceMaxPositiveSequenceResistanceMaxZeroSequenceReactanceMaxZeroSequenceResistanceMinFaultCurrentOHMinFaultCurrentUGMinKVARMinPositiveSequenceReactanceMinPositiveSequenceResistanceMinZeroSequenceReactanceMinZeroSequenceResistanceNameNominalVoltageOperatingVoltageSubstationIDSubtypeVoltageAngle

ElectricLine

IDNameNominalVoltageSubtype

ElectricLineSegment


Chapter 5 • Circuit Segments Data Model Reference • 69

CircuitSource has the following attributes:

BusBarObjectID: long integer — ObjectID of associated BusBar

ConnectionConfiguration: text — Code indicating configuration of conductors;domain values include Delta, Wye, etc.

DynamicProtectiveDevObjectID: long integer — ObjectID of associated dynamicprotective device

EmergencyCapacitykW: long integer — Emergency rating of CircuitSource, inKW; domain values include 12

GroundReactance: double — Reactance of ground seen at the source by thedownstream circuit

FeederSourceInfo: long integer — Stores information about source of feeder

GroundResistance: double — Resistance of ground seen at the source by thedownstream circuit

ID: text — System-generated identifier of feeder initiated at this source

MaximumCapacitykW: long integer — Maximum allowable operating capacityof CircuitSource; domain values include 10

MaxKVAR: long integer — Maximum kVAR load experienced atCircuitSource; domain values include 6

MaxPositiveSequenceReactance: double — Maximum positive sequence reactanceseen at the source by the downstream circuit, in ohms

MaxPositiveSequenceResistance: double — Maximum positive sequence resistanceseen at the source by the downstream circuit, in ohms

MaxZeroSequenceReactance: double — Maximum zero sequence reactance seenat the source by the downstream circuit, in ohms

MaxZeroSequenceResistance: double — Maximum zero sequence resistance seenat the source by the downstream circuit, in ohms

MinFaultCurrentOH: long integer — Calculated minimum fault current foroverhead conductors

MinFaultCurrentUG: long integer — Calculated minimum fault current forunderground conductors

MinkVAR: long integer — Minimum kVAR load experienced at CircuitSource;domain values include 500

MinPositiveSequenceReactance: double — Minimum positive sequence reactanceseen at the source by the downstream circuit, in ohms

MinPositiveSequenceResistance: double — Minimum positive sequence resistanceseen at the source by the downstream circuit, in ohms

MinZeroSequenceReactance: double — Minimum zero sequence reactance seen atthe source by the downstream circuit, in ohms

MinZeroSequenceResistance: double — Minimum zero sequence resistance seen atthe source by the downstream circuit, in ohms


123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567123456789012345678901234567890121234567

Name: text — Utility name of CircuitSource

NominalVoltage: long integer — Code indicating system voltage for whichCircuitSource is rated; domain values include 7.2 kV Grounded Y, 24.9 kVGrounded Y, 2400 Delta, etc.

OperatingVoltage: long integer — Code indicating standard level of voltage atwhich system is currently operated, in kV; domain values include 12.5 kVGrounded Y, 7.2 kV Grounded Y, etc.

SubstationID: text — Substation identifier


VoltageAngle: double — Angle at which phase is offset from system standard

Associations: BusBar, CircuitBreaker, Recloser

Subtypes: kW, Swing, Voltage Controlled

Electric LineElectricLine is provided as a way to model ElectricLine as a simple edge featurerather than as the ElectricLine object. ElectricLine feature supports symbolizedlines and segments within lines. It is equivalent to the Electric Line object andassociated with ElectricLineSegment. Subtypes include Circuit Line and StationLine.

ElectricLine defines the following attributes:

ID: text — Utility identifier of ElectricLine

Name: text — Name of ElectricLine

NominalVoltage: long integer — Code indicating system voltage for whichElectricLine is rated, domain values include 7.2 kV Grounded Y, 24.9 kVGrounded Y, 2400 Delta, etc.


Subtype: Circuit Line, Station Line

Object

ElectricLine

IDNameNominalVoltageSubtype

ElectricLineSegment


71

DeDeDeDeDevices Davices Davices Davices Davices DatatatatataModel RefModel RefModel RefModel RefModel Referererererenceenceenceenceence66666


1234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789

ELECTRIC DEVICE

ELECTRIC DEVICE

ElectricDevice is an abstract class represented as a simple junction feature becausedevices connect to the logical network from a single insertion point. In general,electric devices help ensure consistent service within the distribution network.Electric devices either provide protection, such as fuses or circuit breakers, orregulate electric current, such as transformers and voltage regulators.

ElectricDevice defines the following attributes:



FacilityID: text — Meaningful company-assigned unique identifier ofElectricDevice



FeederInfo: long integer — Feeder Manager-assigned phase information describ-ing the phase of the circuit that supplies a device

InstallationDate: date — Date ElectricDevice was installed

NominalVoltage: long integer — Code indicating system voltage for which

ElectricDevice is rated; domain values include 7.2 kV Grounded Y, 24.9 kVGrounded Y, 2400 Delta, 14.4 kV etc.

OperatingVoltage: long integer — Code indicating standard level at which systemis currently being operated; may vary above or below nominal voltage; domainvalues include 4.16 kV Grounded Y, 7.2 kV Grounded Y, 2400 V Delta

PhaseDesignation: long integer — Code indicating phases supplying a device;domain values include A, AB, AC, etc.



WorkOrderID: text — Identifier of work order of ElectricDevice

Note: The Nominal Voltage attribute does not apply to the following sub-classes of ElectricDevice: OpenPoint and MiscNetworkFeature.

Note: The PhaseDesignation attribute does not apply to the subclassesGround or FaultLimiter.

Associations: FacilityStructure, UndergroundStructure [does not apply toOpenPoint]


ElectricDevice

CommentsElectricTraceWeightFacilityIDFeederIDFeederID2FeederInfoInstallationDateNominalVoltageOperatingVoltagePhaseDesignationSubtypeSymbolRotationWorkOrderID

Chapter 6 • Devices Component Reference • 73

1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890

MiscNetworkFeatureMiscNetworkFeature captures those subtypes that protect distribution networkequipment from temporary and permanent faults.

FaultIndicatorFault indicators locate faulted sections of overhead distribution systems andpresent a visual signal to designate normal and faulted conditions.

ActuatingCurrent: long integer — Current that will trip indicator; settings arehigh and low

MaxConductorSize: text — Maximum size conductor that indicator can protect

FaultLimiterFaultLimiter is used to increase the impedance of the system during fault condi-tions. FaultLimiter defines the following attributes:

GroundType: text — Type of ground used

Reactance: double — Impedence (imaginary part) in ohms

Resistance: double — Impedence (real part) in ohms

GroundA common point for connecting grounded conducting equipment such as shuntcapacitors. Grounding is achieved by connecting one side or neutral of a circuitto the earth through low resistance or low impedance paths, to help preventtransmitting shocks to personnel. Ground equipment normally includes groundcircuits and a driven rod or buried ground field that provides a path for electricreturn circuits. Types of ground devices include grids, mats, and multiple or singledriven rods.

GroundSize: text — Size of ground

Material: text — Material of ground

Resistance: double — Impedence (real part) in ohms

RodSize: — Size of rod in ground

Thickness: text — Thickness of rod

SurgeArrestorSurge arrestors are controlled, enclosed spark-gap structures designed to allowimpulse current to flow through the gaps to the ground. The arrestor rating is themaximum root mean square (rms) voltage for which it is designed to reseal. Therms power frequency is the voltage from line-to-line versus the voltage from line-to-neutral. The arrestor discharge voltage is well below the BIL of the protectedequipment.

ArrestorType: text — Code indicating type of arrestor; domain values includeAir Gap, Metal Oxide, etc

BILRating: long integer — BIL rating of protected equipment


ElectricDevice

MiscNetworkFeature

ActuatingCurrentMaxConductorSizeGroundTypeReactanceResistanceGroundSizeMaterialResistanceRodSizeThicknessArrestorTypeBILRatingClass

Subtypes include Fault Indicator, Fault Limiter,Counter Poise Ground, Rod Ground, WrapGround and Surge Arrestor


123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234123456789012345678901234567890121234

Class: text — Code indicating class of arrestor; domain values include Distri-bution, Elbow, Intermediate, Substation

Open PointOpenPoint contains information about a variety of insulated and shielded devicesthat connect high-voltage cables to apparatus, including transformers. Separable,load-break insulated connectors are used with primary bushings of submersibledistribution transformers for safety. This is known as a dead-front configuration.

OpenPoint defines the following attributes:

Configuration: text — Configuration ofconnection such as Wye, Delta, etc.

Manufacturer: text — Manufacturer ofconnector


NormalPosition [A,B,C]: long integer — Codeindicating normal position of OpenPoint,per phase; domain values include Closed,Open, Not Applicable

PresentPosition[A,B,C]: long integer — Codeindicating present position of OpenPoint,per phase; domain values include Closed,Open, Not Applicable

SpliceSize: text — Code indicating size ofSplice; domain values include 1/0 AWG,1000 MCM, etc.

TransformerObjectID: long integer —ObjectID of associated transformer unit

Note: The NominalVoltage property doesnot apply to OpenPoint.

Subtypes: Load Break Elbow, Non-LoadBreak Elbow, Open Point, Solid Connec-tion, and Splice


ElectricDevice

TransformerBank

GroundReactanceGroundResistanceHighSideConfigurationHighSideGroundReactanceHighSideGroundResistanceHighSideProtectionLabelTextLocationTypeMagnetizingReactanceMagnetizingResistanceRatedKVA

OpenPoint

ConfigurationManufacturerModelNormalPosition[A,B,C]PresentPosition[A,B,C]SpliceSizeTransformerObjectID

Chapter 6 • Devices Data Model Reference • 75

123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890

APPLICATION COCLASS

Overcurrent Protective DeviceGenerally, overcurrent protective devices open (trip) when the maximum ratedcurrent is exceeded for a preset amount of time. Overcurrent protective devicesare arranged in series along a distribution circuit to clear temporary faults in a pre-arranged sequence of operation. The most common devices used for overcurrentprotection are fuse cutouts, automatic circuit reclosers, sectionalizers and relayedcircuit breakers.

The rated continuous current is the current a device carries continuously withoutexceeding specified temperatures in a specified ambient temperature. TheOverCurrentProtectiveDevice is an abstract feature class that contains commoncharacteristics of subclasses DynamicProtectiveDevice, Fuse, FaultInterrupter,CircuitBreaker, Sectionalizer, and Recloser.

OverCurrentProtectiveDevice defines the following attributes:

LabelText: text — Stores circuit labeling text or annotation

MaxContinuousCurrent: double — Code indicating maximum continuous currentrating of device in amps, which is the amount of current that can flowthrough the device indefinitely; domain values include 100 A, 200 A, etc.

MaxInterruptingCurrent: double — Code indicating maximum current for whichdevice interrupts current; domain values include 2.5 kA, 6 kA, 8 kA, etc.

MaxOperatingVoltage: long integer — Code indicating maximum designated rmsvalue of power frequency voltage that may be applied continuously betweenthe terminals of the device; domain values include 4.16/7.2 kV, 7.2/12.4 kV,14.4/24.9 kV, etc.

NormalPosition[A,B,C]: long integer — Code indicating normal position ofdevice, per phase; domain values include Closed, Open, Not Applicable

PresentPosition[A,B,C]: long integer — Code indicating present position ofdevice, per phase; domain values include Closed, Open, Not Applicable

Dynamic Protective DeviceIn addition to opening when a fault is detected, dynamic protective devices alsoreclose to attempt to re-establish service. If the fault remains after a prescribednumber of reclosings, the device may lock open the circuit. Reclosing is designedto reduce or eliminate the effects of temporary faults. Protective devices have aBasic Insulation Level (BIL) rating which is a reference insulation level expressedas the impulse crest voltage of the nominal 1.2 X 50 microsecond wave. This is ameasure of the ability of the insulation to withstand very high voltage surges.

DynamicProtectiveDevice is a feature class that includes subtypes Circuit Breakers,Fault Interrupter, Reclosers (Single Phase Hydraulic, etc.), and Sectionalizers.These attributes are common to all subtypes:

BILRating: long integer — Code indicating BIL rating ofDynamicProtectiveDevice; domain values include 95 BIL, 150 BIL, etc.

ElectricDevice


LabelTextMaxContinuousCurrentMaxInterruptingCurrentMaxOperatingVoltageNormalPosition[A,B,C]PresentPosition[A,B,C]


BypassSwitchClosingResistorManufacturerModelSerialNumberGangOperatedManufacturerModelSerialNumberShuntMechanismTripCountBypassSwtichMountingTypeTieSwitchIndicatorBILRatingGroundResistanceInterruptingMechanismInterruptingMediumSCADAControlIDSCADAMonitorID

Subtypes include Circuit Breaker, FaultInterrupter, Single Phase Hydraulic Recloser,Two Phase Hydraulic Recloser, Three PhaseHydraulic Recloser, Three Phase ElectronicRecloser, Three Phase Relay Recloser, and Singlehase Hydraulic Sectionalizer, Two PhaseHydraulic Sectionalizer, Three Phase HydraulicSectionalizer, and Three Phase ElectronicSectionalizer


GroundResistance: double — Describes ground resistance ofDynamicProtectiveDevice, in ohms

InterruptingMechanism: text — Type of interrupting mechanism that operatesthe contacts of DynamicProtectiveDevice

InterruptingMedium: text — Code indicating interrupting medium that insulatescontacts of DynamicProtectiveDevice; domain values include Air, Oil, Vacuum,etc.

SCADAControlID: text — ID of SCADA control, if present

SCADAMonitorID: text — ID of SCADA monitor, if present

Circuit BreakerCircuit breakers detect excessive power demands in a circuit and self-interruptwhen they occur. Mechanical switching devices equipped with a trip coil con-nected to a relay are designed to open under fault conditions. The contacts of thecircuit breaker open and close by mechanical linkages manufactured from insulat-ing materials and using energy from compressed air, electric magnets, or chargedsprings. An arc appears for a limited time during the interrupting process. Break-ers switch circuits and equipment in and out of the system within two to fivecycles of a fault measured from trip coil energizing to extinguishing the arc. Anaccepted duty cycle is two openings with a 15-second interval.

Circuit breakers are rated by voltage level, current interrupting capabilities,interrupting time, transient recovery voltage, insulation level, and trip delay.Closing resistors may be used to keep switching overvoltages within acceptablelimits.

CircuitBreaker inherits the attributes of the abstract classes ElectricDevice,OverCurrentProtectiveDevice, and DynamicProtectiveDevice. CircuitBreaker defines thefollowing attributes:

BypassSwitch: text — Code indicating presence of bypass switch onCircuitBreaker; domain values are Yes or No

ClosingResistor: text — Code indicating presence of ClosingResistor; domainvalues are Yes or No

Manufacturer: text — Code indicating manufacturer of CircuitBreaker; domainvalues include ABB/Westinghouse, General Electric, etc.


SerialNumber: text — Serial number

Associations: CircuitSource, RelayControl

RecloserReclosers are type of oil switch that use controls to sense a fault and de-energizethe circuit, wait briefly, and then reclose the circuit to try and re-establish service.Reclosers can lock out (remain open) after a predetermined number of attemptsto close. Minimum trip current is usually twice the normal load current rating ofthe coil.

Chapter 6 • Devices Component Reference • 77

Automatic reclosing devices can reduce the number of total network outages by75% to 90%. The amount of current that flows at the installation point underfull load conditions should not exceed what the manufacturer has rated therecloser to carry continuously.

Recloser inherits the attributes of the abstract classes ElectricDevice,OverCurrentProtectiveDevice, and DynamicProtectiveDevice. Recloser defines thefollowing attributes:

BypassSwitch: text — Code indicating presence of BypassSwitch on Recloser;domain values are Yes or No

MountingType: text — Code indicating mounting type of Recloser; domainvalues include Pad Mounted, Pole Mounted, Substation Frame

TieSwitchIndicator: text — Code indicating presence of tie switch; domainvalues are Yes or No

Associations: CircuitSource, RecloserControl, RecloserUnit, RelayControl

Subtypes: Single Phase Hydraulic, Two Phase Hydraulic, Three Phase Hydrau-lic, Three Phase Electronic, Three Phase Relay

SectionalizerSectionalizers are automatic circuit opening devices that are installed on the loadside of fault-interrupting devices and count its fault-trip operations.Sectionalizers can be set to open after one, two, or three counts have been de-tected with a predetermined time span. Sectionalizers are used in conjunctionwith fuses and reclosers and may have inrush current restraint features to preventa false count when lines are re-energized.

Sectionalizer inherits the attributes of ElectricDevice, OverCurrentProtectiveDevice,and DynamicProtectiveDevice.

Association: SectionalizerUnit, SectionalizerControl

Subtypes: Single Phase Hydraulic, Two Phase Hydraulic, Three Phase Hydrau-lic, Three Phase Electronic

Fault InterrupterFault interrupters can replace circuit breakers to protect transformers in substa-tion or networks. Often used for high-side transformer protection, fault inter-rupters open (trip) at a preset current and programmed time delay to minimizefault damage downstream. Fault interrupters employ current transformers (CTs)to provide line current level information to electronic trip control. One set ofCTs provides phase sensing and another senses zero-sequence (ground) current.Contacts open and close using stored energy and can be tripped electronically,electrically, or manually. Interrupters don’t reclose automatically: contacts areclosed through a remotely located switch or a trip-close handle on the tank.

GangOperated: text — Indicates whether devices can be operated as a group

Manufacturer: text — Code indicating manufacturer of device; domain valuesinclude Bridges, Siemens, etc.

Model: text — Model of device


123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789

123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789

SerialNumber: text — Device manufacturer’s serial number

ShuntMechanism: text — Shunt mechanism that trips device

TripCount: long integer — Number of trips before device opens the circuit

FuseFuses are used to protect distribution devices from damaging currents. A fuse isan intentionally weakened spot in the electric circuit that opens the circuit at apredetermined current that is maintained for a predetermined amount of time.Fuses are not dynamic in that they remain open and do not reclose. By automati-cally interrupting the flow of electricity, a fuse prevents or limits damage causedby an overload or short circuit.

Fuses are coordinated with reclosers to prevent fuses being damaged by tempo-rary faults downstream. Time current characteristic (TCC) curves are used to ratefuses: the upper curve represents the total clearing time and the lower curverepresents the melting time. Coordination involves calculating the intersection offuse curves with recloser curves to achieve desired results.

Fuse types include current limiting and expulsion fuses. At maximum interruptingcurrent, the arc of limiting fuses actually melts sand to build up apparent resis-tance to reduce the fault current. Expulsion fuses create an arc during faultconditions which generates a gas that extinguishes fault current.

Association: FuseUnit

Subtypes: Current Limiting, Overhead Expulsion, Underground Expulsion,Vacuum

Power Factor Correcting EquipmentPower distribution is more efficient if operated when the power factor (PF) isunity. An alternating voltage and the current causing it to flow should rise and fallin value equally and reverse direction at the same instant. When this happens, thetwo waves are said to be in phase and the power factor is unity (1.0). However,various inductive effects, such as idle running induction motors or transformers,can lower the power factor.

Capacitors help maintain the power factor at unity by providing a static source ofleading reactive current and can be installed close to the load. This reduces thelagging current. The power factor is the ratio of actual power to the product ofvolts times amperes. Capacitors operate on 60-Hz sine-wave power lines at thevoltage listed on the device nameplate.

PowerFactorCorrectingEquipment defines the following attributes:

LabelText: text — Label or annotation text

TotalkVAR: long integer —Total reactive power of bank, in kVAR


ElectricDevice


Fuse


ElectricDevice

PowerFactorCorrectingEquipment

ConnectionConfigurationGroundReactanceGroundResistanceLocationTypeSwitchTypeMaxFaultCurrentSwitchTypePositiveSequenceReactancePositiveSequenceResistanceZeroSequenceReactanceZeroSequenceResistanceFillTypeMaterialLabelTextTotalKVAR


EXTENDING ARCGIS APPLICATIONS

Capacitor BankCapacitors store electrical energy and release it back into the power system whenrequired to reduce voltage drops. CapacitorBank represents a feature that neutral-izes the effect of customer inductive loads, providing capacitive reactance tobalance inductive reactance loss. One bank is associated with each phase; a three-phase circuit has three capacitor banks. Banks are fixed or switched: permanentlyconnected or automatically switched to supplement voltage rise during heavy-load conditions. Delta and single phase connections are usually made on lowvoltage circuits.

CapacitorBank defines the following attributes:

ConnectionConfiguration: text —Code indicating connection configuration;domain values include Delta, Line To Line, Wye, etc.

GroundReactance: long integer — Ground reactance (Xg) of CapacitorBank, inohms

GroundResistance: long integer — Ground resistance (Rg) of CapacitorBank, inohms

LocationType: text — Code indicating type of location; domain values includeDelivery Point, Primary Meter, Service Point, etc.

SwitchType: text — Code indicating type of switch; domain values include Oil,Vacuum

Associations: CapacitorUnit, CapacitorControl

Subtypes: Fixed Bank, Switched Bank

Series CapacitorCapacitor units are placed in series to connect to higher voltage and transmissionsystems.

SeriesCapacitor defines the following attributes:

MaxFaultCurrent: long integer — Maximum fault current of capacitor

SwitchType: text — Code indicating type of switch; domain values include Oil,Vacuum

PositiveSequenceReactance: double — Equivalent positive sequence reactanceseen by the downstream circuit, in ohms

PositiveSequenceResistance: double — Equivalent positive sequence resistanceseen by the downstream circuit, in ohms

ZeroSequenceReactance: double — Equivalent zero sequence reactance seen bythe downstream circuit, in ohms

ZeroSequenceResistance: double — Equivalent zero sequence resistance seen bythe downstream circuit, in ohms

Associations: CapacitorControl


123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678

Shunt ReactorShunt reactors reduce the inrush of fault current by introducing inductive reac-tance into a circuit to balance the effects of motor starting, to operate transform-ers in parallel, and to control current. Inrush current is the initial momentarysurge current demand before a load resistance of impedance increases to itsnormal operating value.

The normal use for shunt reactors is to compensate for capacitive currents fromtransmission lines, cable, or shunt capacitors. The need for shunt reactors is mostapparent at light load. Switched shunt capacitors are used in distribution substa-tions or out on primary feeders to achieve full-load power factor more economi-cally.

ShuntReactor defines the following attributes:

FillType: text — Code indicating insulating material used in ShuntReactor;domain values include Oil, Other

Material: text — Reactor material

Associations: None

Subtypes: Concrete, Fiberglass, Porcelain

Street LightStreet lighting is supplied by local distribution systems at 120/240 V and isgenerally the only service for which the electric utility installs, operates andmaintains utilization equipment. The lights that illuminate roads and highwaysgenerally use high-intensity discharge lamps with ballasts compatible with com-mon voltages and may be either high- or normal-power factor. High-intensitydischarge lamps are usually phosphor-coated mercury, metal halide, or high-pressure sodium. Lamps are available in several sizes range from 100 to1000watts (W) and may be sealed or filtered for longer life. Photoelectric controls areusually used with individual lights. Most utility lighting systems have beenmounted on existing overhead support structures; however, for undergroundsystems lighting can be designed with supply run from the nearest transformer orhandhole.

StreetLight illuminates a street area and defines the following attributes:

BallastType: text — Code indicating type of ballast used in StreetLight ; do-main values include high-power factor and normal-power factor

FixtureSupport: text — Code indicating type of support used for streetlightfixtures; domain values include Cobra, Security, Other

StreetLight

BallastTypeFixtureSupportLampTypeLensTypeLightCountLightStyleMountHeightOwnershipPhotocellTypeShieldingStreetLightRoleTimeControlWattage


ElectricDevice


1234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789

LampType: text — Code indicating type of lamp; domain values includefluorescent, high/low pressure sodium, incandescent, mercury vapor, andmetal halide

LensType: text — Code indicating type of lens; domain values include diffuser,reflector, or refractor

LightCount: long integer — Code indicating number of lights; domain valuesinclude 1, 2, 3, 4

LightStyle: text — Code indicating style of StreetLight ; domain values includeOrnamental Light, Standard

MountHeight: short integer — Height of light on pole

Ownership: text — Code indicating owner of light; domain values includeCustomer, Utility, Other

PhotocellType: text — Type of photocell

Shielding: text — Code indicating presence of shielding; domain values are Yesor No

StreetLightRole: text — Code indicating role of StreetLight; domain valuesinclude Area Lighting, Commercial Area Lighting, Residential Yard Lighting,etc.

TimeControl: text — Code indicating whether StreetLight has TimeControl;domain values are Yes or No

Wattage: double — Code indicating wattage of lamp; domain values include100 Watts, 175 Watts, etc

Association: SupportStructure

SwitchSwitches are used to disconnect circuits. Switches are installed at strategic loca-tions throughout distribution feeder circuits to redirect power flows to balanceloads or for sectionalizing to allow repair of damaged lines or equipment.Switches may act as tie devices, which are set in an open state and energized fromtwo directions at once. Switches can be manually or power operated, and can beoperated individually or as a group.

Switches are rated by continuous current and maximum operating voltage. Con-tinuous current is the manufacturer-designated limit in rms amperes that thedevice can carry continuously without observable rise in temperature. Maximumoperating voltage is the maximum designated rms value of power frequencyvoltage that may be applied continuously between the terminals of the switch.

Automated switches may have pole-mounted control cabinet housing switchcontroller, battery and local control switches. They may also provide the RTUand communications systems for SCADA operation.

Switch defines the following attributes:

GangOperated: text — Code indicating whether switch is group operated;values are Yes or No

LabelText: text — Used to maintain information about related circuits

Switch

GangOperatedLabelTextManuallyOperatedMaxContinuousCurrentMaxOperatingVoltageNormalPosition[A,B,C]PreferredCircuitSourcePresentPosition[A,B,C]SCADAControlIDSCADAMonitorIDTieSwitchIndicator


ElectricDevice


1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890

Manually Operated: text — Code indicating whether switch is manually oper-ated; domain values are Yes or No

MaxContinuousCurrent: double — Code indicating maximum continuous currentrating of Switch in amps; domain values include 100 Amps, 200 Amps, 600Amps, etc.

MaxOperatingVoltage: long integer — Code indicating maximum operatingvoltage for which Switch is rated; domain values include 4.16/7.2 kV, 7.2/12.4 kV

NormalPosition[A,B,C]: long integer — Code indicating normal position ofSwitch, per phase; domain values include Closed, Open, Not Applicable

PreferredCircuitSource: text — Defines preferred circuit source

PresentPosition[A,B,C]: long integer — Code indicating present position ofSwitch, per phase; domain values include Closed, Open, Not Applicable

SCADAControlID: text — ID of SCADA control

SCADAMonitorID: text — ID of SCADA monitor

TieSwitchIndicator: text — Code indicating whether switch acts as a tie device;values are Yes or No

Association: SwitchUnit

Subtypes: Overhead Disconnect, Overhead Load Break, Underground Discon-nect, Underground Load Break

TransformerBankTransformers transfer electrical energy from one circuit to another circuit usuallywith changed values of voltage and current in the process. The rated voltage(phase-to-ground) of the winding is usually the same as the neutral voltage. Theratio of transformation is changed by increasing or decreasing the number ofactive turns in one winding with respect to another winding. Positions are alwaysnumbered sequentially starting with “1” at the lowest tap position and progress-ing through the highest tap position.

Banked transformers are tied together through secondary mains and are suppliedby the same primary feeder. Banked transformations can reduce lamp flickercaused by starting motors, decrease capacity required, produce better averagevoltage along the secondary, and have greater flexibility for load growth. Trans-former kVA (kilovolt-amperes) describes its ability to support a load at a givenvoltage. Rated kVA of transformer banks is the sum of the rated kVA of itsrelated units.

TransformerBank defines the following attributes:

GroundReactance: long integer — Neutral-to-ground reactance of ground ofTransformer

GroundResistance: long integer — Neutral-to-ground resistance of ground ofTransformer

TransformerBank

GroundReactanceGroundResistanceHighSideConfigurationHighSideGroundReactanceHighSideGroundResistanceHighSideProtectionLabelTextLocationTypeMagneticReactanceMagneticResistanceRatedKVA


ElectricDevice


1234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789

HighSideConfiguration: text — Configuration of primary side of Transformer;domain values include SinglePhaseLine-Ground, Open, SinglePhaseLine-Line,Wye

HighSideGroundReactance: long integer — Ground reactance of primary side, inohms

HighSideGroundResistance: long integer — Ground resistance of primary side, inohms

HighSideProtection: text — Code indicating type of overcurrent protection usedat primary side of Transformer; domain values include Breaker, BayonetFuse,Oilimmersed, WeakLink

LabelText: text — Provides text or annotation about related transformer units

LocationType: text — Code indicating designation of location, including Deliv-ery Point, Generator, Primary Meter

MagnetizingReactance: double — Magnetizing reactance, in ohms

MagnetizingResistance: double — Magnetizing resistance, in ohms

RatedkVA[A,B,C]: double — Sum of rated kVA of related transformer units,per phase; domain values include 100kVA, 1000kVA, etc.

Association: OpenPoint, TransformerUnit

TransformerThe Transformer feature class captures information about distribution and powertransformers. Subtypes include Network, Single Phase Overhead, Single PhaseUnderground, Two Phase Overhead, Three Phase Overhead, Three Phase Under-ground, Step, and Power.

Characteristics of transformers include voltage rating (kV), power rating (MVA),impedence (%), loss evaluation, temperature rating (degrees Celsius), and coolingclass. Distribution transformers convert electrical energy from primary voltages toutilization voltages. Primary voltages range from 34.5/19920 Grounded Y to4160Y/2400 Grounded Y volts. A transformer winding may have tap changers,separately for voltage and phase angle.

Association: LoadTapChanger [only valid for Power Transformer],NetworkProtector [only valid for subtype Network], TransformerUnit

Subtypes: Network, Single Phase Overhead, Single Phase Underground, TwoPhase Overhead, Three Phase Overhead, Three Phase Underground, Step andPower

Voltage RegulatorBecause voltage is different at any point on a feeder, voltage regulators providevoltage control where feeders of different lengths and diverse load conditions aresupplied from the same substation bus. Feeder voltage regulators can be single orthree-phase and operate from 25 to 400 kVA. The 32-step design regulates lineload from 10 percent above (boost) to 10 percent below (buck) normal linevoltage. Operating over a 20 percent range, the voltage change per step is 5/8percent.

TransformerBank


ElectricDevice

Transformer

LoadTapChangerIndicatorRatedKVA65RiseRatedTertiaryKVATertiaryConfigurationTertiaryVoltageLowSideConfigurationLowSideGroundReactanceLowSideGroundResistanceLowSideProtectionLowSideVoltageSwitchType


Voltage regulators vary the ac supply or source voltage to the customer tomaintain the voltage within desired limits. Voltage provided by regulators ischanged using a tap-changing switch to adjust the number of secondarywindings. Bypass switches allow a regulator to be removed for normalservice without interrupting the downstream load.

VoltageRegulator inherits attributes of TransformerBank and ElectricDeviceand defines the following attributes:

BoostPercent: text — Code indicating tap setting for increase in capacityachieved by raising the maximum voltage level; domain values include4 Percent, 6 Percent, etc.

BuckPercent: text — Code indicating tap setting for increase in capacityachieved by lowering the minimum voltage level; domain valuesinclude 4 Percent, 6 Percent, etc.

BypassSwitch: text — Code indicating presence of BypassSwitch used tode-energize VoltageRegulator; domain values are Yes or No

Subtypes: Single Phase Overhead, Two Phase Overhead, Three PhaseOverhead, Three Phase Pad-Mounted

DEVICE CONTROL

Electric devices can be controlled manually, hydraulically, and electronically aswell as remotely. Control features capture information that defines trip current,trip operation, trip interval, overcurrent duration, reclosing operation, and lockout operation of devices that are used to complete, maintain, or interrupt circuitsunder normal and fault conditions.

Network ProtectorNetwork transformers connect to the secondary network through a networkprotector. NetworkProtector components may be the circuit breaker, relays,backup fuses and controls required for automatically disconnecting a transformerfrom the secondary network in response to predetermined conditions on primaryfeeder or transformer.

NetworkProtector defines the following attributes:

ElectricDeviceObjectID: — Object ID of associated electric device

Manufacturer: text — Code indicating manufacturer of NetworkProtector;domain values include ABB/Westinghouse, General Electric, etc.


ProtectorType: text — Code indicating network protector type; domain valuesinclude Oil Breaker, Vacuum Breaker, Other

SecondaryVoltage: long integer — Code indicating voltage at secondary side ofNetworkProtector; domain values include 120 Volts, 120/208 Volts, etc.


123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789

TransformerBank


ElectricDevice

VoltageRegulator

BoostPercentBuckPercentBypassSwitch


SubmersIndicator: text — Code indicating whether Network Protector isconnected to submersible (subsurface) distribution transformer; domain valuesinclude Yes or No


Association: Transformer (only valid for subtype Network)

Relay ControlProtective relay systems detect and isolate faults. Time-delayed phase and groundrelays are coordinated with fuses and reclosers further out on the circuit. They areinstantaneous units with inverse TCCs to coordinate with fuses and reclosersfurther downstream. Relays are usually set to trip feeder breakers and protect thefuse in the event of temporary faults beyond the fuse. Current transformers (CTs)measure large currents as well as insulate relays from high voltage circuits. Theprimary winding of the CT is connected in series with the circuit to be measured.The nominal current ratio of the CT is the inverse of the turns ratio.

A variety of relay protocols exist. Directional comparison relay systems are set intwos ; relay A responds to faults to its right and relay B responds to faults to itsleft. Both will respond simultaneously only if the fault is on the line they are bothprotecting. A communication channel informs A about the state of B and anotherinforms B about the state of A.

Phase comparison relaying uses a communication channel to compare informationabout the phase currents based on the fact that external faults are essentiallyequal in magnitude and opposite in direction while internal faults are in phase.

123456789012345678901234567890121234567890123456789012345678901234567890123456789012345678901212345678901234567890123456789012345678901234567890123456789012123456789012345678901234567890123456789012345678901234567890121234567890123456789012345678901234567890123456789012345678901212345678901234567890123456789012345678901234567890123456789012123456789012345678901234567890123456789012345678901234567890121234567890123456789012345678901234567890123456789012345678901212345678901234567890123456789012345678901234567890123456789012123456789012345678901234567890123456789012345678901234567890121234567890123456789012345678901234567890123456789012345678901212345678901234567890123456789012345678901234567890123456789012123456789012345678901234567890123456789012345678901234567890121234567890123456789012345678901234567890123456789012345678901212345678901234567890123456789012345678901234567890123456789012123456789012345678901234567890123456789012345678901234567890121234567890123456789012345678901234567890123456789012345678901212345678901234567890123456789012345678901234567890123456789012123456789012345678901234567890123456789012345678901234567890121234567890123456789012345678901234567890123456789012345678901212345678901234567890123456789012345678901234567890123456789012123456789012345678901234567890123456789012345678901234567890121234567890123456789012345678901234567890123456789012345678901212345678901234567890123456789012345678901234567890123456789012123456789012345678901234567890123456789012345678901234567890121234567890123456789012345678901234567890123456789012345678901212345678901234567890123456789012345678901234567890123456789012123456789012345678901234567890

Object

NetworkProtector

ElectricDeviceObjectIDManufacturerModelProtectorTypeSecondaryVoltageSerialNumberSubmersIndicatorSubtype

RecloserControl

ElectricDeviceObjectID

Sectionalizer Control

ElectricDeviceObjectIDLockoutTripCountVoltageRestraint

RelayControl

CTRatioCurveIDDynamicProtectiveDevObjectIDInstantTripTapSettingManufacturerModelTapSettingTimeLeverSetting


RelayControl defines the following attributes:

CTRatio: text — Ratio of current transformer (CT)

CurveID: text — Identifier of time current characteristic (TCC) curve

DynamicProtectiveDevObjectID: long integer — ObjectID of associated dynamicprotective device

InstantTripTapSetting: long integer — Value in amps of CT secondary currentthat will trip relay immediately

Manufacturer: text — Code indicating manufacturer of RelayControl; domainvalues include ABB/Westinghouse, General Electric, etc.


TapSetting: long integer — Tap setting of relay

TimeLeverSetting: double — Time dial setting; defines shape of TCC curve used

Associations: DynamicProtectiveDevice [only valid for Circuit Breaker andRecloser subtypes]

Recloser ControlRecloserControl defines the following attribute:

ElectricDeviceObjectID: — Object ID of associated electric device

Association: DynamicProtectiveDevice [only valid for Recloser subtypes]

Recloser Electronic ControlReclosers and sectionalizers isolate temporary and permanent faults in electriclines. Reclosers open circuits (trip) in case of a fault, and reclose after a predeter-mined time. The time-current characteristic, usually expressed in a curve, is basedon temperature and fuse tolerances and is used to coordinate recloser operations.Reclosers allow (usually) four trip operations to clear temporary faults. The firsttwo trips generally occur at approximately 2 Hertz (Hz) (slow curve, TCC1) andthe last two occur at 5 Hz (fast curve, TCC2). If the fault continues, the recloserlocks out the circuit. The minimum trip current is set through a range of settingsbased on the CT ratio of the recloser and is usually twice the normal load current.Protective curves are generally associated with standard fuses (E and K speeds).

RecloserElectronicControl defines the following attributes:

AlternateTripCurrent[Phase, Ground]: long integer — Alternate trip currentsetting, in amps

HighCurrentActiveTripNumber [Phase, Ground]: long integer — Identifier of TCC

HighCurrentLockoutActive [Phase, Ground]: long integer — Indicates whether highcurrent lockout active indicator is on or off

HighCurrentLockoutMultiplier [Phase, Ground]: long integer — If high currentlockout indicator is on, multiplier can be applied to increase current at whichRecloser locks out

HighCurrentLockoutStatus [Phase, Ground]: long integer — Indicates whether highcurrent lockout status indicator is on or off

DEVICE CONTROL


HighCurrentTripStatus [Phase, Ground]: long integer — Indi-cates whether high current trip indicator is on or offHighCurrentTripMultiplier [Phase, Ground]: long integer — Ifhigh current indicator is on, multiplier can be applied toincrease trip current setting

HighCurrentTripTimeDelay [Phase, Ground]: long integer —Increases time for current to trip Recloser

Lockout[Phase, Ground]: long integer — Total number of tripsfor Recloser to remain open (lock out)

Manufacturer: text — Code indicating manufacturer ofRecloser; domain values include ABB/Westinghouse, Gen-eral Electric, etc.

MinimumTripCurrent [Phase, Ground]: long integer — Value atwhich overcurrent is detected, in amps

Model: text — Code indicating model; domain values includeESStatic Control, MEForm3A, etc.

OperatingTime: long integer — Operating time of Recloser

RecloseTime[1,2,3]: long integer — Interval in seconds be-tween first, second, and third trip operation

ResetTime: long integer — Time in seconds between tripoperation and resetting to beginning of trip sequence

SerialNumber: — Serial number

TCCGroup[Phase, Ground]: long integer — Manufacturergroup number assigned to specific curves used for settingRecloser parameters

TCC1ConstantTimeAdder [Phase, Ground]: long integer —Time adjustment assigned to specific curve for slow trips

TCC1MinResponseTime [Phase, Ground]: long integer — Mini-mum response time of slow trip

TCC1Multiplier[Phase, Ground]: long integer — Currentadjustment multiplier applied to minimum trip current forslow trip

TCC1Operations[Phase, Ground]: long integer — Number oftrips per curve for slow trip

TCC1Selection[Phase, Ground]: long integer — Specific curveselected for slow trip

TCC2ConstantTimeAdder [Phase, Ground]: long integer — Time adjustmentassigned to specific curve for fast trips

TCC2MinResponseTime[Phase, Ground]: long integer — Minimum response timeof fast trip

TCC2Multiplier[Phase, Ground]: long integer — Current adjustment multiplierapplied to minimum trip current for fast trip

123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567123456789012345678901234567

Object

RecloserControl

RecloserElectronicControl

AlternateTripCurrent[Phase,Ground]HighCurrentActiveTripNumber[Phase,Ground]HighCurrentLockoutActive[Phase,Ground]HighCurrentLockoutMultiplier[Phase,Ground]HighCurrentLockoutStatus[Phase,Ground]HighCurrentTripMultiplier[Phase,Ground]HighCurrentTripStatus[Phase,Ground]HighCurrentTripTimeDelay[Phase,Ground]Lockout[Phase,Ground]ManufacturerMinimumTripCurrent[Phase,Ground]ModelOperatingTimeRecloseTime[1,2,3]ResetTimeSerialNumberTCCGroup[Phase,Ground]TCC1ConstantTimeAdder[Phase,Ground]TCC1MinResponseTime[Phase,Ground]TCC1Multiplier[Phase,Ground]TCC1Operations[Phase,Ground]TCC1Selection[Phase,Ground]TCC2ConstantTimeAdder[Phase,Ground]TCC2MinResponseTime[Phase,Ground]TCC2Multiplier[Phase,Ground]TCC2Operations[Phase,Ground]TCC2Selection[Phase,Ground]


TCC2Operations[Phase, Ground]: long integer — Number of trips per curve forfast trip

TCC2Selection[Phase, Ground]: long integer — Specific curve selected for fasttrip

Recloser Hydraulic ControlHydraulic control is an intregral part of single-phase reclosers. A trip coil in serieswith the line is used to sense overcurrent and trip open the recloser contacts. Thecontacts close after a preset interval.

RecloserHydraulicControl defines the following attributes:

CoilSize: short integer — Code indicating size of trip coil, in amps; domainvalues include 25 Amps, 50 Amps, etc.

RecloseInterval: long integer — Amount of time before reclosing between opera-tions

ResetTime: long integer — Amount of time Recloser resets to beginning ofoperation sequence

TCC1Operations: long integer — Number of trips per curve for slow trip

TCC2Operations: long integer — Number of trips per curve for fast trip

TCC1Selection: long integer — Specific curve selected for slow trip

TCC2Selection: long integer — Specific curve selected for fast trip

Sectionalizer ControlSectionalizer controls store a pulse counter when the minimum actuating currentdrops to zero because a fault is interrupted by the recloser (or other protectivedevice). Sectionalizers operate in conjunction with breakers and reclosers to lockout fault current after a predetermined number (usually three) of recloser opera-tions (trips). In general, the number of counts to open can be one, two or threecounts. Three-phase sectionalizers have three current transformers sensing phasecurrents and three CTs connected in parallel to ground to sense the zero-sequencecurrent. A count is registered when a current above the preset minimum actuat-ing level reaches the device and then drops to zero (as when interrupted by thebackup protective device). After one, two, or three counts, the mechanism thatopens the contacts is actuated. The number of counts to open the sectionalizershould be one less than the number of trips to lockout of the backup device.

SectionalizerControl defines the following attributes:

ElectricDeviceObjectID: — ObjectID of associated electric device

LockoutTripCount: long integer — Number of trips required before sectionalizerlocks out

VoltageRestraint: double — Code indicating presence of VoltageRestraint;values are Yes or No

Association: Sectionalizer


Sectionalizer Hydraulic ControlSectionalizerHydraulicControl defines the following attributes:

CoilSize: short integer — Code indicating size of trip coil, in amps; domainvalues include 25 Amps, 50 Amps, etc.

Sectionalizer Electronic ControlCount restraint features prevent sectionalizers from generating a count pulse aslong as some current is present. This prevents operation when a load side deviceinterrupts the circuit. If a fault current is interrupted by the downline device, thecount restraint feature blocks the generation of a count if at least 5 amps ofuninterrupted load current flows through the sectionalizer.

Inrush current is the initial momentary surge current demand before a load resis-tance of impedance increases to its normal operating value. If the sectionalizerdetects overcurrent when the backup device opens, the overcurrent present atreclosing is assumed to be fault current. If no overcurrent is detected when the

current is interrupted, the overcurrentat reclosing is assumed to be inrushcurrent. The phase and ground actuat-ing levels are blocked for three secondsafter reclosing to allow the initial surgeto subside. The sectionalizer then resetsto normal.

SectionalizerElectronicControl definesthe following attributes:

CountRestraint: long integer — Indicatespresence of count restraint feature;values are Yes and No

CurrentInrushRestraintMultiplier : longinteger — Defines multiplier increasingactuating level to account for inrushcurrent

GroundFaultSensingMultiplier : long integer— Defines multiplier setting for zero-sequence fault current

TripCurrent: long integer — Minimumcurrent required to open sectionalizer

12345678901234567890123456789012123451234567890123456789012345678901212345123456789012345678901234567890121234512345678901234567890123456789012123451234567890123456789012345678901212345123456789012345678901234567890121234512345678901234567890123456789012123451234567890123456789012345678901212345123456789012345678901234567890121234512345678901234567890123456789012123451234567890123456789012345678901212345123456789012345678901234567890121234512345678901234567890123456789012123451234567890123456789012345678901212345123456789012345678901234567890121234512345678901234567890123456789012123451234567890123456789012345678901212345123456789012345678901234567890121234512345678901234567890123456789012123451234567890123456789012345678901212345123456789012345678901234567890121234512345678901234567890123456789012123451234567890123456789012345678901212345123456789012345678901234567890121234512345678901234567890123456789012123451234567890123456789012345678901212345123456789012345678901234567890121234512345678901234567890123456789012123451234567890123456789012345678901212345

Object


SectionalizerHydraulicControl

CoilSize

SectionalizerElectronicControl

CountRestraintCurrentInrushRestraintMultiplierGroundFaultSensingMultiplierTripCurrent


1234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456

12345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456

Device ObjectDeviceObject is an abstract class containing common attributes of the devices thatcontrol the flow of current in circuits. Device control objects capture character-istic strategies used by regulators and capacitors to provide voltage at a range thatallows customers’ equipment to operate properly.

DeviceObject defines the following attributes:

ElectricDeviceObjectID: — Object ID of electric device

InstallationDate: date — Date device was installed



Subtype: long integer — Code indicating subtype of device

WorkOrderID: text — Work order identifier

Capacitor ControlCapacitors maintain or increase the voltage of distribution conductors and reducevoltage drops in the system. Subtypes include CurrentLevel, KVARLevel,TempLevel, Time, and VoltageLevel.

CapacitorControl defines the following attributes:

DeactivateSaturday: text — Code indicating whether capacitor control deacti-vates on Saturday, values are Yes or No

DeactivateSunday: text — Code indicating whether capacitor control deacti-vates on Sunday, values are Yes or No

OnSetting: long integer — Indicates when capacitor bank is turned on

OffSetting: long integer — Indicates when capacitor bank is turned off

Phase: text — Code describing phases attached to capacitor bank; domainvalues include A, AB, AC, etc.

SCADAControlID: text — ID of SCADA control, if present

SCADAMonitorID: text — ID of SCADA monitor; if present

Subtypes: Current Level, KVAR Level, Temp Level, Time, and Voltage Level

Associations: CapacitorBank, SeriesCapacitor

Object

RecloserControl

RecloserHydraulicControl

CoilSizeRecloseIntervalResetTimeTCC1OperationsTCC2OperationsTCC1SelectionTCC2Selection

Object


ElectricDeviceObjectIDLockoutTripCountVoltageRestraint


1234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012123456789012345678901234567890121234567890121234567890123456789012345678901212345678901212345678901234567890123456789012123456789012

Load Tap ChangerLoadTapChanger represents power transformer controls that change the primary-to-secondary turns ratio of a transformer winding while the transformer is underload to regulate the flow of current and minimize voltage drop. Automatic load-tap changers in the power transformer provides voltage control on the substationbus. Control systems of voltage regulators and tap changing equipment beyondthe substation usually have a line-drop compensator to simulate voltage dropbetween the substation and points in the distribution system.

LoadTapChanger defines the following attributes:

BoostPercent: text — Codeindicating tap setting for in-crease in capacity achieved byincreasing the maximum voltagelevel; domain values include 4Percent, 6 Percent, etc.

BuckPercent: text — Codeindicating tap setting for in-crease in capacity achieved bylowering the maximum voltagelevel; domain values include 4Percent, 6 Percent, etc.

Impedence: text — Impedenceof LoadTapChanger, in ohms

RatedkVA: long integer —System rating, in kVA

RelayControlType: text — Typeof relay control

SwitchType: text — Type ofswitch used

XRRatio: long integer — Induc-tance/resistance ratio

Association:PowerTransformer

Object

DeviceObject

RegulatorControl

BandWidthCTPrimary1stHouseHighProtection[A,B,C]1stHouseLowProtection[A,B,C]PTRatioRSetting[A,B,C]StepSizeTapSetting[A,B,C]VoltageSetting[A,B,C]XSetting[A,B,C]

CapacitorControl

DeactivateSaturdayDeactivateSundayOnSettingOffSettingPhaseSCADAControlIDSCADAMonitorID

ElectricDeviceObjectIDInstallationDateModelSerialNumberSubtypeWorkOrderID

LoadTapChanger

BoostPercentBuckPercentImpedanceRatedKVARelayControlTypeSwitchTypeXRRatio


Regulator ControlVoltage provided by regulators is changed using a tap-changing switch to adjustthe number of secondary windings. Line load can be regulated from 10 percentabove to 10 percent below normal line voltage. Voltage regulators that controldistribution system voltage are rated from 2.5 kV to 34.5 grd Y kV. Most feederregulators have the 32-step design.

Voltage is measured by current transformers and potential transformers (PT) toprovide control of system voltage level and bandwidth. The PT steps down theregulator (local) voltage and provides it to the control system which comparesvoltage with the desired preset level. If the actual voltage deviates from presetvoltage by plus or minus ½ the bandwidth, the tap changing mechanism operatesto bring voltage within the preset bandwidth. Minimum bandwidth is twice thesize of the voltage step (2 times 5/8 percent or 1.25 percent).

The line-drop compensator simulates system impedance by adjusting resistanceand reactance. The CT circulates current proportional to the load current throughthe resistance and reactance components and combines this voltage signal withthe local voltage signal. This allows the regulator to maintain a higher voltageduring heavy loads.

RegulatorControl defines the following attributes:

Bandwidth: text — Preset bandwidth of voltage regulator

CTPrimary: long integer — Current transformer (CT) rating ofprimary side of regulator

1stHouseHighProtection[A,B,C]: long integer — Fuse type on primaryside

1stHouseLowProtection[A,B,C]: long integer — Fuse type on second-ary side of regulator

PTRatio: long integer — Potential transformer (PT) ratio used tosense source voltage

RSetting[A,B,C]: long integer — Setting of resistive component ofline-drop compensation system, per phase

StepSize: long integer — Size of steps that voltage regulator hasavailable at full regulation

TapSetting[A,B,C]: long integer — Current tap setting per phase

VoltageSetting[A,B,C]: long integer — Voltage setting per phase

XSetting[A,B,C]: long integer — Setting of resistive component ofline-drop compensation system, per phase

Association: TransformerUnit

12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890

Object

DeviceObject

RegulatorControl

BandWidthCTPrimary1stHouseHighProtection[A,B,C]1stHouseLowProtection[A,B,C]PTRatioRSetting[A,B,C]StepSizeTapSetting[A,B,C]VoltageSetting[A,B,C]XSetting[A,B,C]


Unit ObjectUnitObject is an abstract class containing common attributes of individualdevices: capacitors, fuses, reclosers, sectionalizers, switches, and transformers.

UnitObject defines the following attributes:


UnitID: text — Identifier of related device unit

Capacitor UnitCapacitors store electrical energy and release it back into the power system whenrequired to reduce voltage drops. CapacitorUnit defines the following attributes:

FluidType: text — Code indicating type of dielectric fluid (some containpolychlorinated biphenyls - PCBs) used in CapacitorUnit; domain valuesinclude Arachlor, Diachlor, Faradol, etc.

kVAR: long integer — Code indicating CapacitorUnit size in kVAR; domainvalues include 100 kVAR, 150 kVAR, etc

Manufacturer: text — Code indicating manufacturer of CapacitorUnit

Association: CapacitorBank

Fuse UnitA fuse is an intentionally weakened spot in the electric circuit that opens thecircuit at a predetermined current that is maintained for a predetermined amountof time. Fuses are classified into three categories: low voltage (up through 600V), medium voltage (operating theough 69kV) and high voltage (through 500kV).

FuseUnit defines the following attributes:

HousingType: text — Code indicating type of FuseUnit housing; domain valuesinclude Door Cutout, MX Cutout, Open Link

HousingRatio: long integer — Code indicating capacity of FuseUnit housing, inamps; domain values include 50 Amps, 100 Amps, 200 Amps, etc.

LinkType: text — Code indicating type of FuseUnit link, in terms of speed;domain values include KLink, NLink, 200, etc.

LinkRating: long integer — Size of FuseUnit link, in amps; domain valuesinclude 1 A, 10 A, 100 A, etc

Manufacturer: text — Code indicating manufacturer

Association: Fuse

123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456

Object

DeviceObject

UnitObject

PhaseDesignationUnitID

CapacitorUnit

FluidTypeKVARManufacturer

123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345

Object

DeviceObject

UnitObject

FuseUnit

HousingTypeHousingRatingLinkTypeLinkRatingManufacturer


Recloser UnitReclosers trip open a circuit for a short time to clear temporary fault and recloseafter a predetermined time. The time-current characteristic, usually expressed in acurve, is based on temperature and fuse tolerances and is used to coordinaterecloser operations.

RecloserUnit defines the following attributes:


ReversePowerAccessory: text — Code indicating whether recloser has ReversePower Accessory; values are Yes or No

Associations: Recloser

Sectionalizer UnitSectionalizers operate in conjunction with breakers and reclosers to lock out faultcurrent after a predetermined number (usually three) of recloser operations(trips).

SectionalizerUnit defines the following attributes:


Associations: Sectionalizer

Switch UnitSwitches are used to disconnect circuits for line sectionalizing, isolating equip-ment and feeder realignment on distribution circuits.

SwitchUnit defines the following attrib-utes:

BILRating: long integer — Code indi-cating rating of SwitchUnit BIL;domain values include 95 BIL, 125BIL, etc.

ContactType: text — Code indicatingtype of contact of SwitchUnit;domain values include Posi-Lock,Standard

GroundResistance: long integer —Resistance of ground of SwitchUnit,in ohms

InterruptingMechanismType: text —Interrupting mechanism ofSwitchUnit

InterruptingMedium: text — Codeindicating interrupting medium ofSwitch; domain values include Air,Oil, SF6, Vacuum, etc.

Manufacturer : text — Code indicatingmanufacturer

123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234123456789012341234567890123412345678901234

123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345123456789012345

12345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456123456789012345612345678901234561234567890123456

Object

DeviceObject

UnitObject

RecloserUnit

ManufacturerReversePowerAccessory

Object

DeviceObject

UnitObject

SectionalizerUnit

Manufacturer

Object

DeviceObject

UnitObject

SwitchUnit

BILRatingContactTypeGroundResistanceInterruptingMechanismInterruptingMediumManufacturerMaxInterruptingCurrent


MaxInterruptingCurrent: double — Code indicating maximum current in ampsthat opens SwitchUnit; domain values include 50 Amps, 60 Amps, 200 Amps,etc.

Association: Switch

Transformer UnitTransformers transfer electrical energy from one circuit to another circuit usuallywith changed values of voltage and current in the process.

TransformerUnit defines the following attributes:

AnimalGuardType: text — Type of animal guard used on TransformerUnit

ArrestorType: text — Code indicating arrestor type; domain values include AirGap, Metal Oxide, etc.

Available: text — Code indicating whether TransformerUnit has capacityavailable; domain values are Yes or No

CoolingType: text — Code indicating cooling method used in TransformerUnit;domain values include Radiator Forced Air, Other

FluidType: text — Type of fluid used

FullLoadLosses: double — Full-load losses of TransformerUnit in watts

HighSideRatedVoltage: long integer — Code indicating system voltage for whichhigh side of TransformerUnit is rated; domain values include 2400 VoltsDelta, 4160/2400 Volts, etc.

HighSideBIL: long integer — Code indicating BIL rating of high side ofTransformerUnit; example includes 125 BIL, etc.

Impedance: double — Impedance of TransformerUnit, expressed as percentage

LowSideRatedVoltage: long integer — Code indicating system voltage of low sideof TransformerUnit; domain values include 120 Volts, 120/208 Volts, etc.

LowSideBIL: long integer — BIL rating of low side of TransformerUnit

LowSideTaps: text — Number of taps available on low side ofTransformerUnit to change transformer ratio

Manufacturer: text — Manufacturer of TransformerUnit; domain values in-clude ABB/Westinghouse, General Electric

MaxSteps: text — Maximum number of steps available on TransformerUnit

NoLoadLosses: double — No-load losses of TransformerUnit, in watts

PCBLevel: double — PCB level, if any, in coolant of TransformerUnit, domainvalues include Arachlor, Diachlor, etc.

ProtectionType: text — Code indicating type of protection; domain valuesinclude Bayonet Fused, Conventional, etc.

RatedKVA: long integer — kVA at nominal voltage; domain values include 10kVA, 112 kVA, 333 kVA, etc.

TapsType: text — Code indicating type of taps; domain values include2Above/2Below, 4Above. etc.

123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678

Object

DeviceObject

UnitObject

TransformerUnit

AnimalGuardTypeArrestorTypeAvailableCoolingTypeFluidTypeFullLoadLossesHighSideRatedVoltageHighSideBILImpedanceLowSideRatedVoltageLowSideBILLowSideTapsManufacturerMaxStepsNoLoadLossesPCBLevelProtectionTypeRatedKVATapsTypeTransformerObjectIDXRRatio


123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678123456789012345678

TransformerObjectID: long integer — ObjectID of associated transformer

VoltageRegulatorObjectID: long integer — ObjectID of associated voltage regula-tor

XRRatio: double — Inductance/resistance ratio

Associations: RegulatorControl [only valid for VoltageRegulator], Transformer

Subtypes: Distribution Transformer Unit, Power Transformer Unit, VoltageRegulator Unit

VoltageRegulatorUnitVoltage regulators provide voltage control where feeders of different lengths anddiverse load conditions are supplied from the same substation bus.VoltageRegulatorUnit defines the following attributes:

AnimalGuardType: text — Type of animal guard used on TransformerUnit

ArrestorType: text — Code indicating arrestor type; domain values include AirGap, Metal Oxide, etc.

Available: text — Code indicating whether TransformerUnit has capacityavailable; domain values are Yes or No

CoolingType: text — Code indicating cooling method used in TransformerUnit;domain values include Radiator Forced Air, Other

FluidType: text — Type of fluid used

FullLoadLosses: double — Full-load losses of TransformerUnit in watts

HighSideRatedVoltage: long integer — Code indicating system voltage for whichhigh side of TransformerUnit is rated; domain values include 2400 VoltsDelta, 4160/2400 Volts, etc.

HighSideBIL: long integer — Code indicating BIL rating of high side ofTransformerUnit; example includes 125 BIL, etc.

Impedance: double — Impedance of TransformerUnit, expressed as percentage

LowSideRatedVoltage: long integer — Code indicating system voltage of low sideof TransformerUnit; domain values include 120 Volts, 120/208 Volts, etc.

LowSideBIL: long integer — BIL rating of low side of TransformerUnit

LowSideTaps: text — Number of taps available on low side ofTransformerUnit to change transformer ratio

Manufacturer: text — Manufacturer of TransformerUnit; domain values in-clude ABB/Westinghouse, General Electric

MaxSteps: text — Maximum number of steps available on TransformerUnit

NoLoadLosses: double — No-load losses of TransformerUnit, in watts

PCBLevel: double — PCB level, if any, in coolant of TransformerUnit, domainvalues include Arachlor, Diachlor, etc.

RatedKVA: long integer — kVA at nominal voltage; domain values include 10kVA, 112 kVA, 333 kVA, etc.

Object

DeviceObject

UnitObject

VoltageRegulatorUnit

AnimalGuardTypeArrestorTypeAvailableCoolingTypeFluidTypeFullLoadLossesHighSideRatedVoltageHighSideBILImpedanceLowSideRatedVoltageLowSideBILLowSideTapsManufacturerMaxStepsNoLoadLossesPCBLevelRatedKVATapsTypeVoltageRegulatorObjectIDXRRatio


TapsType: text — Code indicating type of taps; domain values include2Above/2Below, 4Above, etc.

VoltageRegulatorObjectID: long integer — ObjectID of associated voltage regula-tor

XRRatio: double — Inductance/resistance ratio

Associations: VoltageRegulator, RegulatorControl


99

Customer andCustomer andCustomer andCustomer andCustomer andSerSerSerSerService Davice Davice Davice Davice DatatatatataModel RefModel RefModel RefModel RefModel Referererererenceenceenceenceence77777


1234567890123456789012345678901212345678901234567890123412345678901234567890123456789012123456789012345678901234123456789012345678901234567890121234567890123456789012341234567890123456789012345678901212345678901234567890123412345678901234567890123456789012123456789012345678901234123456789012345678901234567890121234567890123456789012341234567890123456789012345678901212345678901234567890123412345678901234567890123456789012123456789012345678901234123456789012345678901234567890121234567890123456789012341234567890123456789012345678901212345678901234567890123412345678901234567890123456789012123456789012345678901234123456789012345678901234567890121234567890123456789012341234567890123456789012345678901212345678901234567890123412345678901234567890123456789012123456789012345678901234123456789012345678901234567890121234567890123456789012341234567890123456789012345678901212345678901234567890123412345678901234567890123456789012123456789012345678901234123456789012345678901234567890121234567890123456789012341234567890123456789012345678901212345678901234567890123412345678901234567890123456789012123456789012345678901234123456789012345678901234567890121234567890123456789012341234567890123456789012345678901212345678901234567890123412345678901234567890123456789012123456789012345678901234123456789012345678901234567890121234567890123456789012341234567890123456789012345678901212345678901234567890123412345678901234567890123456789012123456789012345678901234123456789012345678901234567890121234567890123456789012341234567890123456789012345678901212345678901234567890123412345678901234567890123456789012123456789012345678901234123456789012345678901234567890121234567890123456789012341234567890123456789012345678901212345678901234567890123412345678901234567890123456789012123456789012345678901234123456789012345678901234567890121234567890123456789012341234567890123456789012345678901212345678901234567890123412345678901234567890123456789012123456789012345678901234123456789012345678901234567890121234567890123456789012341234567890123456789012345678901212345678901234567890123412345678901234567890123456789012123456789012345678901234123456789012345678901234567890121234567890123456789012341234567890123456789012345678901212345678901234567890123412345678901234567890123456789012123456789012345678901234123456789012345678901234567890121234567890123456789012341234567890123456789012345678901212345678901234567890123412345678901234567890123456789012123456789012345678901234123456789012345678901234567890121234567890123456789012341234567890123456789012345678901212345678901234567890123412345678901234567890123456789012123456789012345678901234123456789012345678901234567890121234567890123456789012341234567890123456789012345678901212345678901234567890123412345678901234567890123456789012123456789012345678901234123456789012345678901234567890121234567890123456789012341234567890123456789012345678901212345678901234567890123412345678901234567890123456789012123456789012345678901234123456789012345678901234567890121234567890123456789012341234567890123456789012345678901212345678901234567890123412345678901234567890123456789012123456789012345678901234123456789012345678901234567890121234567890123456789012341234567890123456789012345678901212345678901234567890123412345678901234567890123456789012123456789012345678901234

CUSTOMER AND SERVICE

CUSTOMER AND SERVICE

Residential, commercial, and industrial customers, resellers, as well as specialdevices such as streetlights, constitute the loads on the electrical system.ElectricLocation is an abstract class representing the point at which electricity issupplied to the customer.


ElectricLocation

ElectricTraceWeightFeederIDFeederID2FeederInfoInstallationDateLocationIDSubtypeSymbolRotationWorkOrderID

CustomerConnection

AddressConnectionTypePhaseDesignationServiceCurrentRating

Generator

ConnectionConfigurationGroundReactanceGroundResistanceKWMaxReactiveGenerationNominalVoltagePositiveSequenceReactancePositiveSequenceResistancePowerFactorRatedKVASubtransientReactanceTransientReactanceZeroSequenceReactanceZeroSequenceResistance

DeliveryPoint

BillingTypeDeliveryToOwnerMeterIndicatorOperatingStatus

ServicePoint

CommentsStatus

PrimaryMeter

CTRatioMeterRatingMeterTypePTRatioRemoteRead

Chapter 7 • Customer and Service Data Model Reference • 101

1234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789

12345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789

Electric LocationElectricLocation defines the following attributes:




FeederInfo: long integer — Feeder Manager-assigned phase information describ-ing the phase of the circuit that supplies a device

InstallationDate: date — Date of installation of ElectricLocation

LocationID: text — Utility-assigned identifier of ElectricLocation



WorkOrderID: text — Work order identifier

Association: FacilityStructure, UndergroundStructure

Subtypes: None

Customer ConnectionCustomerConnection contains information about the service provided to the cus-tomer and defines the following attributes:

Address: text — Customer address

ConnectionType: text — Type of connection


ServiceCurrentRating: short integer — Code indicating maximum rating of ser-vice delivered to CustomerConnection; domain values include 100 Amps, 600Amps, etc.

Association: ServiceAddress

Service PointServicePoint is the point at which the distribution feeder terminates and energy issupplied to a customer. A service point can have one or many meters.

ServicePoint defines the following attributes:


Status: text — Code indicating status of ServicePoint; domain values includeActive, Inactive

Associations: InductionMotor, SynchronousMotor


ElectricLocation

ElectricTraceWeightFeederIDFeederID2FeederInfoInstallationDateLocationIDSubtypeSymbolRotationWorkOrderID

CustomerConnection

AddressConnectionTypePhaseDesignationServiceCurrrentRating


ElectricLocation

CustomerConnection

ServicePoint

CommentsStatus


123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789

1234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789

Primary MeterPrimary meters are installed if commercial customers elect to have power deliv-ered at distribution voltages, such as 12.5 kV. Residential customers are generallybilled for kilowatt hours (kWH) used. Commercial and industrial customers mayadditionally be billed for demand charges and power factor charges.

The utility can use current transformers or CTs to measure and voltage-measuringtransformers (potential transformers or PTs) to transform current and voltagelevels to smaller voltages and use a standard meter to measure usage.

PrimaryMeter defines the following attributes:

CTRatio: text — Current transformer ratio of PrimaryMeter

MeterRating: long integer — System rating of PrimaryMeter

MeterType: text — Code indicating type of meter; domain values includeConventional, Instrument Transformer, Self-Contained, Other

PTRatio: text — Potential transformer ratio of PrimaryMeter

RemoteRead: text — Code indicating whether meter can be read remotely;values are Yes or No

Delivery PointDeliveryPoint defines the following attributes:

BillingType: text — Type of billing

DeliveryToOwner: text — Code indicating whether bill is delivered to owner,values are Yes or No

MeterIndicator: text — Code indicating presence of meter, values are Yes or No

OperatingStatus: text — Code indicating status of DeliveryPoint; domainvalues include Active, Inactive

GeneratorGenerator is an alternative, third-party power source feeding into the electricalnetwork.

Generator defines the following attributes:

ConnectionConfiguration: text — Code indicating type of connection of Genera-tor; domain values include Delta, Wye

GroundReactance: long integer — Reactance of ground, in ohms

GroundResistance: long integer — Resistance of ground, in ohms

kW: long integer — Power rating, in kW

MaxReactiveGeneration: long integer — Maximum reactive generation

NominalVoltage: long integer — Code indicating system voltage for which deviceis rated; domain values include 4.16 kV Grounded Y, 7.2 kV Grounded Y, etc.

PositiveSequenceReactance: double — Equivalent positive sequence reactanceseen at source by downstream circuit, in ohms


ElectricLocation

CustomerConnection

PrimaryMeter

CTRatioMeterRatingMeterTypePTRatioRemoteRead


ElectricLocation

DeliveryPoint

BillingTypeDeliveryToOwnerMeterIndicatorOperatingStatus


12345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789123456789012345678912345678901234567891234567890123456789

PositiveSequenceResistance: double — Equivalent positive sequence resistanceseen at source by downstream circuit, in ohms

PowerFactor: double — Power factor rating, expressed as percentage

Rated KVA: long integer — Rated kVA

SubtransientReactance: double — Subtransient reactance

TransientReactance: double — Transient reactance

ZeroSequenceReactance: double — Equivalent zero sequence reactance seen atsource by downstream circuit, in ohms

ZeroSequenceResistance: double — Equivalent zero sequence resistance seen atsource by downstream circuit, in ohms

Induction MotorInductionMotor is an electric transformer with a magnetic circuit separated by anair gap into two movable portions carrying the primary and secondary windings.Secondary currents are created by induction rather than being supplied by a dcexciter or other external power source.Types of induction motor are wound rotorand squirrel cage.

Induction motors have National Electric Manufacturers Association (NEMA)specifications and defines the following attributes:

ConnectionConfiguration: text — Code indicating connection configuration ofInductionMotor; domain values include Delta, Wye

Efficiency: double — Efficiency, expressed in percentage

GroundReactance: double — Ground reactance of InductionMotor, in ohms

GroundResistance: double — Ground resistance of InductionMotor, in ohms

LockedRotorMultiplier: double — Higher current required to start motor, inpercentage

LockedRotorPF: double — Power factor of locked rotor, expressed as less thanone or as percentage

MotorStartLimit: double — Motor start limit

MotorStartLimitAmount: double — Motor start limit amount

NEMALockedRotorRatio: double — NEMA locked rotor kVA/HP ratio

NominalVoltage: long integer — Standard level of normal ratings for systemvoltage, expressed as line-to-line or line-to-neutral; domain values include4.16 kV Grounded Y, 7.2 kV Grounded Y, etc.


PowerFactor: double — Power factor expressed as less than one or as percentage

RatedHP: double — Rated horsepower


ElectricLocation

Generator

ConnectionConfigurationGroundReactanceGroundResistanceKWMaxReactiveGenerationNominalVoltagePositiveSequenceReactancePositiveSequenceResistancePowerFactorRatedKVASubtransientReactanceTransientReactanceZeroSequenceReactanceZeroSequenceResistance


12345678901234567890123456789012123456789012345678901231234567890123456789012345678901212345678901234567890123123456789012345678901234567890121234567890123456789012312345678901234567890123456789012123456789012345678901231234567890123456789012345678901212345678901234567890123123456789012345678901234567890121234567890123456789012312345678901234567890123456789012123456789012345678901231234567890123456789012345678901212345678901234567890123123456789012345678901234567890121234567890123456789012312345678901234567890123456789012123456789012345678901231234567890123456789012345678901212345678901234567890123123456789012345678901234567890121234567890123456789012312345678901234567890123456789012123456789012345678901231234567890123456789012345678901212345678901234567890123123456789012345678901234567890121234567890123456789012312345678901234567890123456789012123456789012345678901231234567890123456789012345678901212345678901234567890123123456789012345678901234567890121234567890123456789012312345678901234567890123456789012123456789012345678901231234567890123456789012345678901212345678901234567890123123456789012345678901234567890121234567890123456789012312345678901234567890123456789012123456789012345678901231234567890123456789012345678901212345678901234567890123123456789012345678901234567890121234567890123456789012312345678901234567890123456789012123456789012345678901231234567890123456789012345678901212345678901234567890123123456789012345678901234567890121234567890123456789012312345678901234567890123456789012123456789012345678901231234567890123456789012345678901212345678901234567890123123456789012345678901234567890121234567890123456789012312345678901234567890123456789012123456789012345678901231234567890123456789012345678901212345678901234567890123123456789012345678901234567890121234567890123456789012312345678901234567890123456789012123456789012345678901231234567890123456789012345678901212345678901234567890123123456789012345678901234567890121234567890123456789012312345678901234567890123456789012123456789012345678901231234567890123456789012345678901212345678901234567890123123456789012345678901234567890121234567890123456789012312345678901234567890123456789012123456789012345678901231234567890123456789012345678901212345678901234567890123

ServicePointObjectID: long integer — ObjectID of ServicePoint

SoftStartReactance: double — Soft start reactance, X

SoftStartResistance: double — Soft start resistance, R

SoftStartTap: double — Soft start tap

SoftStartWinding: double — Soft start winding

Association: ServicePoint

Synchronous MotorSynchronous motors transform electric power from an alternating current systeminto mechanical power. The armature winding, usually on the stator, is the cur-rent carrying winding. The configuration of the rotor determines the type ofsynchronous motor and usually employs dc-excited field windings. Synchronousmotors are built for operating at a power factor or 1.0 or 0.8 lead. Reactance ismeasured in a steady-state condition in which a circuit’s values remain essentiallyconstant, occurring after all initial transients or fluctuating conditions havesettled down.

Object

SynchronousMotor

ArmatureResistanceConnectionConfigurationDAxisSynchronousReactanceQAxisSynchronousReactanceSaturationCoefficient10SaturationCoefficient12ServicePointObjectIDSubtransientReactanceTransientReactanceZeroSequenceReactance

InductionMotor

ConnectionConfigurationEfficiencyGroundReactanceGroundResistanceLockedRotorMultiplierLockedRotorPFMotorStartLimitMotorStartLimitAmountNEMALockedRotorRatioNominalVoltagePhaseDesignationPowerFactorRatedHPServicePointObjectIDSoftStartReactanceSoftStartResistanceSoftStartTapSoftStartWinding

ServicePoint

CommentsStatus


SynchronousMotor defines the following attributes:

ArmatureResistance: double — Resistance of armature winding, in ohms

ConnectionConfiguration: text — Code indicating connection configuration ofSynchronousMotor

DAxisSynchronousReactance: double — Ratio of reactive armature voltage todirect axis reactance under steady-state conditions

QAxisSynchronousReactance: double — Ratio of reactive armature voltage toquadrature axis reactance under steady-state conditions

SaturationCoefficient10: double — Saturation coefficient; at 1.0 per unit (PU)no-terminal voltage

ServicePointObjectID: long integer — ObjectID of ServicePoint

SaturationCoefficient12: double — Saturation coefficient; at 1.2 PU no-terminalvoltage

SubtransientReactance: double — Subtransient reactance, in ohms

TransientReactance: double — Transient reactance, in ohms

ZeroSequenceReactance: double — Ratio of in-phase armature voltage to nega-tive sequence reactance

Association: ServicePoint


123456789012345678901234567890121234567891234567890123456789012345678901212345678912345678901234567890123456789012123456789123456789012345678901234567890121234567891234567890123456789012345678901212345678912345678901234567890123456789012123456789123456789012345678901234567890121234567891234567890123456789012345678901212345678912345678901234567890123456789012123456789123456789012345678901234567890121234567891234567890123456789012345678901212345678912345678901234567890123456789012123456789123456789012345678901234567890121234567891234567890123456789012345678901212345678912345678901234567890123456789012123456789123456789012345678901234567890121234567891234567890123456789012345678901212345678912345678901234567890123456789012123456789123456789012345678901234567890121234567891234567890123456789012345678901212345678912345678901234567890123456789012123456789123456789012345678901234567890121234567891234567890123456789012345678901212345678912345678901234567890123456789012123456789123456789012345678901234567890121234567891234567890123456789012345678901212345678912345678901234567890123456789012123456789123456789012345678901234567890121234567891234567890123456789012345678901212345678912345678901234567890123456789012123456789123456789012345678901234567890121234567891234567890123456789012345678901212345678912345678901234567890123456789012123456789

LoadUtilities generate their entire revenue from customers, who represent a load onthe system. There are three kinds of load:

(1) residential, commercial, and industrial customers

(2) bulk delivery points to reselling utilities

(3) special-purpose devices such as streetlights, and traffic control signals

Demand is the load at the receiving terminals averaged over a specified intervalof time. Demand is expressed in real power, apparent power, or current – kilo-watts, reactive volt-amperes, volt-amperes, or amperes. Information about thelocation and size of loads on the system is essential for operations, design, andplanning for current and future facilities.

Object

CustomerInfo

AccountNumberDataSourceMonthCDServiceAddressObjectID

UsageInfo

BillingPeriodKWH

DemandInfo

KWKVAR

LoadSummary

CurrentTotalKVARKWVoltage

ServiceAddress

AddressCriticalCustomerIndicatorCustomerClass


12345678901234567123456789012345671234567890123456712345678901234567123456789012345671234567890123456712345678901234567123456789012345671234567890123456712345678901234567123456789012345671234567890123456712345678901234567123456789012345671234567890123456712345678901234567123456789012345671234567890123456712345678901234567123456789012345671234567890123456712345678901234567123456789012345671234567890123456712345678901234567123456789012345671234567890123456712345678901234567

1234567890123456789012345678901212345123456789012345678901234567890121234512345678901234567890123456789012123451234567890123456789012345678901212345123456789012345678901234567890121234512345678901234567890123456789012123451234567890123456789012345678901212345123456789012345678901234567890121234512345678901234567890123456789012123451234567890123456789012345678901212345123456789012345678901234567890121234512345678901234567890123456789012123451234567890123456789012345678901212345123456789012345678901234567890121234512345678901234567890123456789012123451234567890123456789012345678901212345

Service AddressServiceAddress defines the following attributes:

Address: text — Customer address

CriticalCustomerIndicator: text — Code indicating whether customer has criticalneed for electricity; domain values include Critical, Non-Critical

CustomerClass: text — Code indicating class of customer; domain valuesinclude Commercial, Industrial, MultiFamily Residential, Single Family Resi-dential

Associations: CustomerConnection

Customer InfoCustomerInfo defines the following attributes:

AccountNumber: text — Customer account number

DataSource: text — Source of customer data

MonthCD: text — Code indicating month of service; domain values includeJanuary, March, etc.

ServiceAddressObjectID: long integer — Object ID of ServiceAddress

Demand InfoDemand from the customer is the load at receiving terminals averaged over aspecific time. Industrial and commercial customers can be billed for having suffi-cient power available. This demand charge is measured in kVA and is over andabove the charge for kWh. A power factor charge may also be billed to largecustomers to offset the necessity of having to provide reactive power to servelarge motor loads.

DemandInfo defines the following attributes:

kW: long integer — Load demand in kilowatts

kVAR: long integer — Reactance, in reactive volt-amperes

Object

ServiceAddress

AddressCriticalCustomerIndicatorCustomerClass

CustomerConnection

AddressConnectionTypePhaseDesignationServiceCurrentRating

Object

CustomerInfo

DemandInfo

KWKVAR

AccountNumberDataSourceMonthCDServiceAddressObjectID


123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234123456789012345678901234

Load SummaryDemand from the customer is the load at receiving terminals averaged over aspecific time. Demand is expressed in real power, apparent power, or current –kilowatts, reactive volt-amperes, volt-amperes, or amperes.

LoadSummary defines the following attributes:

CurrentTotal: long integer — Amount of current in LoadSummary

kVAR: long integer — Reactance, in kVAR

kW: long integer — Load summary, in kW

Voltage: long integer — Voltage

Usage InfoResidential customers are generally billed for the amount of kWH they use.

UsageInfo defines the following attributes:

BillingPeriod: long integer — Period for which consumption of kWH is billed

kWH: long integer — Usage of current in kWH

Object

CustomerInfo

UsageInfo

BillingPeriodKWH

LoadSummary

CurrentTotalKVARKWVoltage

INDEX 109

IndexA

Add Data 43AerialMarker 52amperes 108AnchorGuy 53ArcCatalog 33armature winding 104Assembly 56asset management 12

B

bandwidth 92BIL 75BIL rating 75binary large object 60Building a Geodatabase 36BusBar 65

C

C++ 25CapacitorBank 79CapacitorControl 90CapacitorUnit 93CATV 55, 66circuit segments 10CircuitBreaker 76CircuitSource 68Code Generation Wizard 35COM object 30, 59, 60Component Object Model (COM) 9ConductorInfo 64Configuration 60connectivity rules 33contacts 76Coordinate System 37Creosote 50cross section 59CTs 77, 88, 102current transformers 102customer information 11CustomerConnection 101CustomerInfo 107

D

Data Converters 44data model 28data model requirements 33dead-front 74DeliveryPoint 102Demand 106DemandInfo 107DeviceObject 90devices 10, 11direct buried cables 59Duct Definition 59ducts 59duty cycle 76DynamicProtectiveDevice 75

E

E speed 86ElectricComplexEdge 62ElectricDevice 72ElectricLine 68, 70ElectricLineSegment 63ElectricLocation 101ElectricStation 51enclosures 49extra high voltage 51

F

FacilityStructure 49fault current 88Fault interrupters 77FaultIndicator 73FaultLimiter 73FdrMgrNonTraceable 65feeder 31, 52, 68, 101feeder management 63feeders 63Fuse 78fuse 75fuse cutouts 75FuseUnit 93

G

Generator 102Ground 73Ground reactance 79Ground resistance 79Guy 53

H

H-frames 49Hand Hole 59Hertz 86horizontal forces 50horizontal load 53

I

InductionMotor 103infrastructure 11inrush current 80, 89Inspection 57interrupting mechanism 76interrupting medium 76

J

joint use 55, 66

K

K speeds 86kilowatts 108kVAR 68kW 68kWH 102

L

LifecycleHistory 56line-drop compensator 92Load 106loads 11LoadSummary 108LoadTapChanger 91lock open 75logical network 72

110 INDEX

M

main 49Manhole 59meters 102Modeling Our World 30, 36

N

NEMA 103NetworkProtector 84

O

Object Loader 36, 44open loops 58OpenPoint 74OverCurrentProtectiveDevice 75

P

pads 49pedestals 49PF 78Phase designation 64polyethylene 67pothead 54power factor 104PowerFactorCorrectingEquipment

78preservatives 50primary feeder 51, 82, 84PrimaryMeter 102Properties 40PT 92, 102Pushbraces 54

Q

Query Builder 42

R

reactive volt-amperes 108recloser 77reclosers 75RecloserUnit 94Regulator Control 92relay systems 85

Repository 28, 33, 35, 39resistance 64Riser 54rms 73, 75, 81

S

SCADA 31, 62, 66, 76, 81, 90Schema Creation Wizard 30, 33, 35secondary windings 92sectionalizers 75, 77SectionalizerUnit 94ServiceAddress 107ServicePoint 101ShuntReactor 80Simple Data Loader 42, 44slope 53snapping 44Spacing 66SpanGuy 54Spatial Reference 37StreetLight 80structure 10Structure class 49submersible 58substation buses 65substations 49SurgeArrestor 73switch 30, 81SwitchingFacility 52SwitchUnit 94SynchronousMotor 105

T

TCC 78, 86Transformer 83transformer loading 63transformer winding 91TransformerBank 82TransformerUnit 95, 96trenches 59trips 86, 88, 94

U

UML 24, 30defining objects and models 24

underground linear structures 59

UndergroundStructure 58Unified Modeling Language 24UnitObject 93unity 78URD 58, 67UsageInfo 108

V

Vault 59vertical forces 50Visio 36volt-amperes 108voltage drop 93Voltage Regulator 83VoltageRegulatorUnit 96

W

WarningSign 55winding 104

Electric Distribution

Documents