Electric Distribution

1
Copyright 2001 Environmental Systems Research Institute, Inc. and Miner and Miner All rights reserved. Printed in the United States of America. The information contained in this document is the exclusive property of Environmental Systems Research Institute, Inc. This work is protected under United States copyright law and other international copyright treaties and conventions. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or by any information storage or retrieval 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 RIGHTS Any software, documentation, and/or data delivered hereunder is subject to the terms of the License Agreement. 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 in FAR 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 Environmental Systems 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., registered in 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 by ESRI, and the ArcFM logo are trademarks and www.esri.com is a service mark of Environmental Systems Research Institute, Inc. Other companies and products mentioned herein are trademarks or registered trademarks of their respective trademark owners. The names of other companies and products herein are trademarks or registered trademarks of their respective trademark owners.
Contents
Acknowledgements ............................................................................................. v Modeling with ArcGIS Electric Distribution ................................................... 7 INTRODUCTION ........................................................................................................................................ 8 MODELING CONCEPTS IN ARCGIS ELECTRIC DISTRIBUTION ................................................................... 9 Building Analysis Models ................................................................................. 13 ELECTRIC DISTRIBUTION ........................................................................................................................ 14 CIRCUIT SEGMENTS .............................................................................................................................. 16 DEVICES ............................................................................................................................................... 18 ARCGIS ANALYSIS MODELS ................................................................................................................. 24 Deploying ArcGIS Electric Distribution ........................................................ 27 DEPLOYING ARCGIS ELECTRIC ............................................................................................................ 28 GEODATABASE BASICS .......................................................................................................................... 29 GEODATABASE DESIGN,TOOLS AND GUIDELINES ................................................................................. 30 ARCGIS ELECTRIC DEPLOYMENT SCENARIOS ....................................................................................... 33 IMPLEMENTING 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 ................................................................................................................................. 72 DEVICE CONTROL ................................................................................................................................ 86 Customer and Service Data Model Reference .............................................. 99 CUSTOMER AND SERVICE ..................................................................................................................... 100 Index ................................................................................................................. 109
Contents iii
iv ArcGIS Electric Distribution Model
Table of Contents
Acknowledgements Acknowledgements
The creation of this draft version of ArcGIS Electric Distribution Model has been a collaborative effort of several Miner and Miner employees. Jeff Meyers, Mike Daniels, Kelly Little, Carol Terry, and Kim Despins exerted much of 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 were cultivated from the Standard Handbook for Electrical Engineers, fourteenth edition, Donald G. Fink and Wayne Beaty, published by McGraw Hill, as well as from product catalogs from Cooper Power System Waukesha, WI 53187. Miner and Miner is privileged to have an active electric utility user group. Lead, and often cajoled into action by Kelly Little, Product Specialist, this group has made a significant contribution to the development of the ArcGIS Electric Distribution model. Of the many members of our user and business partner community we would like to especially thank the following organizations for their ongoing support. These are some of the electric utilities and engineering firms that directly contributed to developing the ArcGIS electric 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 v
Table of Contents
vi ArcGIS Electric Distribution Model
Table of Contents
Modeling with ArcGIS Electric Distribution
ArcGIS Electric Distribution contains ready-to-use data models that can be configured and customized for use at electric utilities. A keystone of this new data model is superior modeling of electric devices and circuits that capture the behavior of real-world objects such as transformers and feeders. These are the topics in this chapter: Introduction Modeling concepts Modeling electric distribution systems
Table of Contents
I NTRODUCTION
Electricity is an essential part of our everyday lives that we often take for granted. We take it for granted, that is, until we have to do without power for one reason or another. We don't often actually see them, but behind the scenes many people are working to ensure that we have a clean, safe, reliable source of power; that we don't have unpredictable or inappropriate current to power our infinite variety of devices; and that the supply is there when we need it; and that it is, more or less, reasonably priced.
ArcGIS Electric Distribution is designed for electric utilities that manage distribution systems that deliver electric power to our service drops. By providing a geographically oriented view of electric distribution devices, structures, circuits and even customer information, ArcGIS Electric Distribution helps utility managers and administrators visualize, analyze, and understand real-world engineering and business problems and, more importantly, solutions. Built using objectcomponent technology, ArcGIS Electric Distribution provides a powerful new platform for utility solutions. The goal of this system is to provide operational efficiencies and business benefits that transcend traditional GIS and mapping boundaries.
8 ArcGIS Electric Distribution Model
Table of Contents
M ODELING C ONCEPTS
IN
A RC GIS E LECTRIC D ISTRIBUTION
Todays electric utilities are realizing the benefits of geographic information system (GIS) technology in the management of facilities for engineering, construction, and operations purposes. The typical requirements of these utilities reflect business needs to:
Component reference of the ArcGIS electric distribution model presented by subsystem and described in narrative form at the class level. Each component contains a description of usage and application within the model. Resources and guidelines for implementing instances of ArcGIS electric distribution. Deployment scenarios and task-based instruction for evaluating model requirements and implementing a custom geodatabase in the ArcInfo 8 environment.
Update GIS databases with design and as-built data Produce standard and custom map products Integrate computer-aided design (CAD) drawings with the GIS network Integrate with other enterprise systems such as work management systems, outage management, document management systems, materials management systems, and customer information systems Analyze installed network for capacity planning and capital improvement projects Manage feeder system, conduit systems, and inspection operations
This book is written assuming that the reader is knowledgeable about electric distribution and has a functional understanding of ArcInfo 8. Additional resources are provided in the bibliography to assist you with developing a basic understanding of Component Object Model (COM), Unified Modeling Language (UML), and object-oriented database design. The sample data contained on the ArcGIS Electric Distribution CDROM is provided courtesy of the the Town of Greeley, Colorado. The data has been modified by Miner & Miner to suit the needs of this book and to highlight ArcGIS functionality. The Town of Greeley and Miner & Miner cannot guarantee the reliability or suitability of this information, as it is provided as an example. Original data was compiled and manipulated from various sources and may not accurately represent the electric distribution systems as maintained by Greeley. The sample data may be updated, corrected, or otherwise modified without notification. Modeling electric distribution systems The object technology at the core of ArcInfo 8 combines data and application behavior modeling. As a result, the ArcGIS model not only includes an essential set of electric device, structure, circuit segment, and customer information feature classes and properties, it also includes rules and relationships that define object behaviors. The core object technology and applied ArcGIS electric distribution model result in significantly less configuration and customization effort for overall implementation per site.
The ArcGIS Electric Distribution model supports these typical business needs by providing an implementation that focuses on operations and maintenance portions of the facility life cycle and provides a crucial visual component.
WHO SHOULD READ THIS BOOK
ArcGIS Electric Distribution Model is intended for users who implement the ArcGIS electric distribution object models. These users include database designers, data builders, database administrators, analysts, and developers. This book serves as a companion to the ArcGIS electric distribution (UML) object model and details the model components and provides information for developing custom applications. The following topics are discussed in this book:
Introduction to the ArcGIS electric distribution model. Definition of distribution networks and devices and the design considerations of these systems as they are applied in ArcGIS electric distribution. Descriptions of the ArcGIS electric distribution model structures and organization including modeling techniques and component notation in UML.
Table of Contents
Modeling with ArcGIS Electric Distribution 9
ELECTRIC DISTRIBUTION
Circuit Segments This subsystem contains classes and properties that describe the conductors that transmit and distribute electric current. Circuit segments can be categorized as simple or complex edges and objects. The inherent behavior of complex edges is very different in ArcGIS Electric Distribution than the traditional ArcInfo topology model. The ArcGIS Electric Distribution system automatically maintains the relationships between complex edges, any attached devices, and other edges so you can choose how you want to physically segment your network. For instance, it makes sense to physically segment electric lines between fuses and switches since, among other things, it is important to keep circuit data on lines, depending on which side of the fuse they are on. For example, if you place a fuse on an overhead primary that originally was associated with CircuitID 001, it may be that the overhead primary west of the fuse is part of CircuitID 001, but the overhead primary east of the fuse is now associated with CircuitID 005. At the same time, it is not necessary to physically segment electric line segments at splices. Once your network is in place and you move an electric line segment, any attached switches, fuses, transformers, and other portions of the network automatically move with it. ArcFM Energy determines whether a complex edge should be split based on the type of junction (device) being added. As with most of the subsystems discussed in this document, a common set of properties is defined in a toplevel abstract class. All subclasses beneath the abstract class ElectricComplexEdge inherit these properties. Structures Structure is the abstract class that contains common characteristics, or attributes, for all electric structures involved in the distribution or transmission of electricity. The Structure class was created as a general top-level class for any type of facility structure. The subsystem structure contains non-network (non-spatial) features and related objects. You can create associations between a support structure and the Inspection object class to capture information about maintenance, for example. The subsystem structure also includes objects to mange information about the lifecycle of a structure.
The power delivered by electric utilities is transmitted from generating plants to industrial sites and the substations that distribute power to residential and commercial users; the utility business is thus divided into these two areas transmission and distribution. Transmission networks connect generators to substations through transmission networks. The distribution system delivers power from substations to residential and commercial users. This book covers the aspects of the electric utility business dealing with distribution. Distribution represents about 35 percent to 50 percent of a utility's investment. The mission of the utility is to provide power to consumers at an appropriate voltage with a certain degree of reliability. Distribution components typically include: Subtransmission circuits with voltage ratings that range between 12.47 and 345 kV Distribution substations that convert energy from transmission network levels to lower primary system voltages Feeders, or primary circuits, that operate between 4.16 and 34.5 kV and supply load to specific geographic areas Distribution transformer rated from 10 to 25000 KVA that transform primary voltage to utilization voltage Secondary circuits that carry current from the transformer along the street Service drops that carry current from transformers to customer point of utilization Electric distribution system components Typical primary overhead distribution systems are operated as radial circuits from the substation outward. In overhead systems, structures such as poles and H-frames support the primary and secondary conductors. Surface structures like pads enclose and protect electric devices on the ground. The electric utility infrastructure is also composed of devices such as transformers and fuses and circuit segments, such as overhead and underground conductors. These components fall into four general logical categories: circuit segments, structures, devices, and customer and service.
Table of Contents
Devices Electric devices help ensure consistent service within the distribution network. The device subsystem contains simple junction features and object classes. Devices features participate in the network and objects are the units and controls associated with those devices. Customer and Service Residential, commercial, and industrial customers, resellers, as well as special devices such as streetlights, constitute the loads on the electrical system. Simple junction features are the electric locations (for example, primary meters and service points). Objects contain customer information and information about generators of alternate sources of electricity. Primary meters, delivery points, and generators may be associated with a structure.
Design discussion
Electric distribution modeling requires considering facilities as assets

One benefit of GIS technology is that utilities can track their assets by geographic location. Network assets, like most other infrastructure owned by businesses, can be depreciated for tax accounting purposes. The specific amount of depreciation allowed depends on the original value of the equipment, how long the facilities have been in place, and the tax boundary area that facilities are located in. Having an accurate record of facilities managed with a GIS provides a more accurate inventory of existing facilities and an automated way to maintain these records as a by-product of map maintenance activities. From a GIS system design standpoint, it is important to understand how the location of physical equipment (i.e., a conduit) can be considered differently from an asset management standpoint, depending on how many ducts, conductors, or cables it may contain. You should consider asset management for your geodatabase design and any special rules that your utility may have for asset management.
Electric modeling requires consideration of facilities as assets.
Table of Contents
Modeling with ArcGIS Electric Distribution 11
Design discussion
Devices are often moved to different locations during their life span.
During the lifetime of a particular transformer or switch, the individual piece of network equipment may be installed in one location, only to be removed and stored in a truck or warehouse for a period of time. This process can be repeated for the same piece of equipment several times during its useful lifetime. From an asset management standpoint, an accurate accounting for depreciation purposes is important. It is also important to continue to link historical maintenance, repair, and inspection data to understand when the equipment has reached the end of its reliability curve.
Section of Transformer placement job sketch (Source: map sketch created for Arizona Public Service Co. by Miner and Miner Consulting Engineers, Inc.)
Table of Contents
2 3
Building Analysis Models
Table of Contents
13
ELECTRIC DISTRIBUTION
electric distribution
Object Structure
JointUseAttachment
Inspection
LifecycleHistory
Assembly
Specific inspection objects should be defined on an as-needed basis. As a new inspection object is defined, any necessary relationships should also be defined.
Specific lifecycle history objects should be defined on an as-needed basis. As a new history object is defined, any necessary relationships should also be defined.
ComplexEdgeFeature
RelationshipClass
Examples include gas pipe, communication cable, and water pipe.
UndergroundLinearStructure
ULS_ULSMember CrossReference
Other ULS Contents Underground Electric LineSegment
Subtypes include Duct Bank and Trench.
SimpleJunctionFeature
Attributed relationship class to manage the many-to-many relationship between UndergroundLinearStructure and UndergroundElectricLineSegment.
UndergroundStructure
Subtypes include Hand Hole, Manhole, and Vault.
Object
ElectricDevice ElectricLocation
underground structures
Table of Contents
DuctDefinition
object model
Feature Structure
AerialMarker
Pushbrace
WarningSign Guy
Subtypes include Back, Bridle, Sidewalk, and Standard
Riser
FacilityStructure
SupportStructure
StreetLight
SpanGuy AnchorGuy
SpanGuy is a linear feature.
Subtypes include H-Frame, Non-Wood Power Pole, Non-Wood Street Light Pole, Wood Street Light Pole, and Tower
This relationship is only valid for subtypes Non-Wood Street Light Pole and Wood Street Light Pole
EquipmentEnclosure
SurfaceStructure
Subtypes include Main Station, Net Station, and Sub Station
Subtypes include Connection Box, Enclosure, Mat, NonElectric Enclosure, Pad, and Pedestal
ElectricStation SwitchingFacility
BusBar
Subtypes include Auto Transfer Enclosure, Junction Cabinet, Pad-Mounted Gear, and Switch Board
Table of Contents
Building Analysis Models 15
CIRCUIT SEGMENTS
circuit segments
Object
Subtypes include kW, Swing, and Voltage Controlled Support for nonsymbolized lines
Circuit Source
ElectricLine
SimpleEdgeFeature
Support for symbolized lines Subtypes include Circuit Line and Station Line
Subtypes include Circuit Line and Station Line
ElectricLine ConductorInfo
Feature ComplexEdge Feature ElectricComplexEdge
CommunicationCable
Subtypes include Single Phase Primary Overhead, Two Phase Primary Overhead, Three Phase Primary Overhead, Single Phase Secondary Overhead, Three Phase Secondary Overhead and Streetlight Conductor
BusBar
CircuitSource SwitchingFacility
ElectricLineSegment
OverheadElectric LineSegment UndergroundElectric LineSegment

Underground LinearStructure
Subtypes include Single Phase Primary Underground, Three Phase Primary Underground, Single Phase Secondary Underground, Three Phase Secondary Underground and Streetlight Conductor
Table of Contents
customer & service

Object Object
CustomerInfo UsageInfo DemandInfo LoadSummary
ServiceAddress
SimpleJunction Feature
These relationships are not valid for ServicePoint
Representation of Customer Information System
ElectricLocation
UndergroundStructure FacilityStructure
Generator DeliveryPoint CustomerConnection
Object ServicePoint InductionMotor SychronousMotor PrimaryMeter
Table of Contents
DEVICES
devices
The Rated KVA property should be non-editable; it is a derived field equal to the sum of the RatedKVA of the related TransformerUnits Subtypes include Fixed Capacitor Bank, Switched Capacitor Bank, Series Capacitor, and Shunt Reactor
TransformerBank
TransformerUnit
Subtypes include Single Phase Overhead, Two Phase Overhead, Three Phase Overhead, and Three Phase PadMounted
OpenPoint
PowerFactor CorrectingEquipment
CapacitorControl
This relationship is only valid for subtypes Switched Capacitor Bank and Series Capacitor
This relationship is only valid for subtypes Load Break Elbow, NonLoad Break Elbow, and Solid Connection
Subtypes include Load Break Elbow, NonLoad Break Elbow, Open Point, Solid Connection and Splice
CapacitorUnit
This relationship is only valid for subtypes Fixed Capacitor Bank and Switched Capacitor Bank
Voltage Regulator
Transformer
Subtypes include Network, Single Phase Overhead, Single Phase Underground, Two Phase Overhead, Three Phase Overhead, Three Phase Underground, Step, and PowerTransformer This relationship is only valid for subtype Power Transformer. This relationship is only valid for subtype Network.
LoadTapChanger
NetworkProtector
Table of Contents
ElectricDevice
FacilityStructure UndergroundStructure
These relationships are not valid for OpenPoint.
Subtypes include Overhead Disconnect, Overhead Load Break, Underground Disconnect, and Underground Load Break
Note: If Secondary Electric Line Segment is not a network feature, then StreetLight would not be a network feature.
MiscNetworkFeature
Subtypes include Fault Indicator, Fault Limiter, Counter Poise Ground, Rod Ground, Wrap Ground, and Surge Arrestor
Overcurrent ProtectiveDevice
Switch
SwitchUnit
StreetLight
SupportStructure
This relationship is only valid for SupportStructure subtypes NonWood Street Light Pole and Wood Street Light Pole.
Subtypes include Circuit Breaker, Fault Interrupter, Single Phase Hydraulic Recloser, Two Phase Hydraulic Recloser, Three Phase Hydraulic Recloser, Three Phase Electronic Recloser, Three Phase Relay Recloser, Single Phase Hydraulic Sectionalizer, Two Phase Hydraulic Sectionalizer, Three Phase Hydraulic Sectionalizer, and Three Phase Electronic Sectionalizer
Subtypes include Current Limiting, Overhead Expulsion, Underground Expulsion, and Vacuum
Dynamic ProtectiveDevice
This relationship is only valid for Circuit Breaker and Recloser subtypes.
Fuse
FuseUnit
CircuitSource RelayControl
This relationship is only valid for Circuit Breaker and Recloser subtypes.
This relationship is only valid for Sectionalizer subtypes.
SectionalizerUnit SectionalizerControl
This relationship is only valid for Sectionalizer subtypes. This relationship is only valid for Recloser subtypes.
This relationship is only valid for Recloser subtypes.
RecloserUnit RecloserControl
Table of Contents
devices
Object
NetworkProtector
Transformer
This relationship is only valid for Transformer subtype Network.
RecloserControl
This relationship is only valid for DynamicProtectiveDevice Recloser subtypes.
Recloser ElectronicControl
Recloser HydraulicControl
Table of Contents
RelayControl
This relationship is only valid for subtypes Circuit Breaker and Recloser.
Sectionalizer Control
This relationship is only valid for DynamicProtectiveDevice Sectionalizer subtypes.
Sectionalizer HydraulicControl
Sectionalizer ElectronicControl
Table of Contents
devices
SwitchUnit
Switch
CapacitorUnit
FuseUnit
Fuse
SectionalizerUnit
This relationship is only valid for PowerFactorCorrectingEquipment subtypes Fixed Capacitor Bank and Switched Capacitor Bank.
This relationship is only valid for DynamicProtectiveDevice Sectionalizer subtypes.
Table of Contents
This relationship is only valid for TransformerUnit subtype VoltageRegulatorUnit.
Object
RegulatorControl
TransformerUnit
This relationship is only valid for PowerFactorCorrectingEquipment subtypes Switched Capacitor Bank and Series Capacitor.
DeviceObject
CapacitorControl
Subtypes include Current Level, KVAR Level, Temp Level, Time, and Voltage Level
UnitObject LoadTapChanger
This relationship is only valid for Transformer subtype Power Transformer.
Transformer
RecloserUnit
This relationship is only valid for DynamicProtectiveDevice Recloser subtypes.
TransformerUnit
TransformerBank RegulatorControl
This relationship is only valid for VoltageRegulatorUnit.
Subtypes include Distribution Transformer Unit, Power Transformer Unit, and Voltage Regulator Unit
Table of Contents
ARCGIS ANALYSIS MODELS
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 you begin to group the properties and names of the objects in an analysis model. The analysis model provides a logical grouping of common properties of objects in an inheritance tree. While the diagrams split the model into network domains such as structures and devices, this section describes the entire inheritance model within each subsystem. The process of building an analysis model In simple terms, an analysis model can be created by starting with the core ArcInfo object classes and a set of named, real-world objects to be modeled. The creation of the analysis model often begins with a top-down approach, where the list of network objects is conceptually divided into logical groups. The key characteristic of these groups is that they share common properties and/or behaviors. For example, structures are grouped together because they support or enclose electric equipment. Support structures can be grouped together because they carry overhead conductors. After a basic grouping of objects is established, you can begin 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 of base classes, intermediate classes, leaf classes, and relationships. By defining the properties of each leaf class, common properties appear. For instance, both overhead and underground circuits have phase designation as a property. Rather than duplicate each property in all objects, a higher-order class is created to contain the common properties. This process ultimately results in a set of intermediate, often abstract classes that model the system. The creation of an analysis model is an iterative process that requires both top-down and bottom-up analysis to define the structure of the object model. The objects and model are defined using a subset of the Unified Modeling Language (UML). Basic resources for UML concepts, rules, notation, and syntax are required. Guidelines for using the model within ArcCatalog software are also important. Subtypes Decisions about subtyping classes are important for your implementation. For instance, if objects in a grouping have different properties to the point that they cannot be grouped together, you need to split your object into two classes. Examples of this are protective devices can open to protect the network from faults but dynamic protective devices can open and close automatically to restore service. While both devices protect the network, they are different enough that several classes were required in the model. Certain network devices, on the other hand, have been lumped into a single class called MiscNetworkFetures. A set of subtypes is used to distinguish different devices, for example, circuit breakers and fault interrupters. In general, you should try to lump your objects into fewer classes wherever possible since there are performance advantages to lumping objects together.
Table of Contents
Complex edges are the base class for all conductors. The ElectricLineSegment class was created as a general top-level class for both overhead and underground circuits. In other words, all classes beneath the ElectricLineSegment class will contain the properties of this feature class. The inherent behavior of complex edges is very different than the traditional ArcInfo topology model. The ArcInfo system automatically maintains the relationships between complex edges, any attached devices, and other edges so you can choose how you want to physically segment your network. For instance, it makes sense to physically segment underground conductors between manholes since, among other things, it is important to capture data on underground conductors where they connect with manholes. This can only be captured for the starts and ends of conductors so underground networks could be segmented at manholes. At the same time, it is not necessary to physically segment conductors at switches or circuit breakers. Once your network is in place, you can move line segments and any attached devices, and other portions of the network will automatically move with it. As with most of the subsystems discussed in this document, a common set of properties is defined in a top-level abstract class. All of these properties are inherited by all subclasses beneath ArcFMLine. Describing the objects The objects are shown in a UML style but are represented differently than the UML models and static analysis diagrams. Properties inherited by abstract classes are shown shaded within the object and provide clarity for available properties and a reference to the abstract classes from which the properties are inherited. The model is represented within a Visio Enterprise/Professional (Visio) diagram and can be immediately exported from Visio to Microsoft Repository using the Visio UML Export wizard. The ArcInfo 8 Computer-Aided Software Engineering (CASE) tool wizard is used to build an instance of the mode within a geodatabase. The ArcInfo 8 CASE Tools support UML. Developers can generate a compilable C++ Active Template Library (ATL) based Visual Studio project if they choose to create their own custom features, which are subclassed off those contained in either ArcInfo 8 or ArcGIS Electric Distribution object model. The following chapters describe the individual classes and model components.
Table of Contents
Table of Contents
Deploying Deploying ArcGIS ArcGIS Electric Distribution
ArcGIS Electric Distribution provides an extensive and detailed set of components that you can use to implement your data model. ArcGIS Electric Distribution can be implemented with no modifications or can be customized to fit 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
Table of Contents
27
DEPLOYING ARCGIS ELECTRIC
A geographic data model is an abstraction of the real world that uses a set of data objects that support map display, query, editing, and analysis. ArcInfo supports a new object-oriented data modelthe geodatabase data modelwith the benefit of representing behaviors and relationships of features. To assist with your implementation, ArcFM Electric Distribution provides a domain-specific geodatabase, as well as the components of its database design and implementation. Examples from various stages of the geodatabase implementation process are included to allow you to begin implementation and customization at a level appropriate to your needs. The components include: ArcGIS Electric Distribution database schema and logical data model presented in static analysis diagrams. Component reference of objects represented in the logical data model describing the relation of entities to real world objects. ArGIS Electric Distribution geodatabase modeled in Unified Modeling Language (UML). Microsoft Repository created from the ArcFM Electric Distribution UML. Geodatabase of ArcGIS Electric Distribution model and components. The previous chapters reviewed the ArcGIS geodatabase design and data model schema. They also described how real world objects are represented by the feature classes within the model. In this chapter you will learn how to implement an ArcGIS geodatabase that meets your database design criteria, using existing objects and customizing an object to meet your implementation needs. The information provided in this chapter is a compilation of ArcGIS-specific information and of materials from other ArcInfo documentation, including Building a Geodatabase and Modeling our World. Most utilities use a relational geographic data model, containing features such as points and linesand their related attributesto represent their facilities. The data in this model is used for map display, query, editing, and analysis.
ArcGIS Electric Distribution enhances your data and processes by representing your utility with objects that more closely model the real world. These objects are stored in an RDBMS and managed using the geodatabase data model. The geodatabase model is a generic model for geographic information that supports a wide variety of object relationships and behavior. ArcGIS Electric Distribution is a set of objects with behavior and relationships appropriate for modeling electric distribution facilities. You can use these objects out of the box or customize them to more closely represent your facility. The geodatabase The geodatabase supports an object-oriented vector data model. In this model, real-world entities are represented as objects with properties, behavior, and relationships. The object types include simple objects, geographic features (objects with location), network features (objects with geometric integration with other features), annotation features, and other more specialized feature types. The model allows you to define relationships between objects, as well as rules for maintaining the referential integrity between related objects. The purpose of the geodatabase The purpose of the geodatabase data model is to let you make the features in your GIS datasets smarter by endowing them with natural behaviors, and to allow any sort of relationship to be defined among features. The geodatabase data model brings a physical data model closer to its logical data model. The objects in a geodatabase are mostly the same objects you would define in a logical data model, such as owners, buildings, parcels, and roads.
Table of Contents
GEODATABASE BASICS
Benefits of a geodatabase data model Applying an object-oriented data model to geographic features yields many benefits. Object-oriented data modeling lets you characterize features more naturally by letting you define your own types of objects, by defining topological, spatial, and general relationships, and by capturing how these objects interact with other objects. A principal advantage of the geodatabase data model is that it includes a framework to create intelligent features that mimic the interactions and behaviors of real-world objects. The geodatabase data model lets you implement the majority of custom behaviors without writing any code. Most behavior is implemented through domains, validation rules, and other functions of the framework provided by ArcInfo. A geodatabase stores geographic data in a commercial relational database. This means that geographic data can be administered centrally by information technology professionals and ArcInfo can take advantage of developments in database technology. ArcGIS Electric Distribution includes electric utility distribution-specific geodatabases which may be implemented as is, or may be used as a framework for designing a custom geodatabase implementation. To determine how to best implement ArcGIS Electric Distribution, you should be familiar with the database design requirements for your organization. This section provides basic guidelines and techniques for determining a geographic database design and implementing that design. Implementation options Designing a geodatabase is a critical process that requires planning and revision until you reach a design that meets your requirements. Once you have a design, there are two main ways that you can create the geodatabase. One technique is to load existing shapefile and coverage data into one of the sample geodatabases, and create or modify database items with ArcCatalog. Another technique is to use Unified Modeling Language (UML) and ComputerAided Software Engineering (CASE) tools to design and create a custom geodatabase schema, create the geodatabase from the schema, and then load your data.
Regardless of the method you choose, the geodatabase that you create can be refined later, using ArcCatalog or UML and CASE tools.Design guidelines The structure of the geodatabase feature datasets, feature classes, topological groupings, relationships, and other elements allows you to design geographic databases that are close to their logical data models. The following are general guidelines for the design process: 1. Model the users view of the data. Identify the organizational functions of the data and determine the data needed to support these functions. Organize the data into logical groupings. 2. Define objects and relationships. Identify and describe the objects, specifying object relationships. Build the logical data model with the set of objects, knowing how they are related to one another. 3. Select geographic representations types. Represent discrete features with points, lines, and areas. 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 objects in a geodatabase. Determine the geometry types of discrete features. Specify relationships between features. Implement attribute types for objects. 5. Plan the geodatabase structure. Organize the geodatabase into feature classes, feature datasets. Consider thematic groupings, topological associations, and departmental responsibility for data. The first three steps develop the conceptual model, classifying features based on an understanding of data required to support the organizations functions, and deciding their spatial representation. The last two steps develop the logical model, matching the conceptual models to ArcInfo geographic datasets.
Table of Contents
Deploying ArcGIS Electric 29
GEODATABASE DESIGN,TOOLS AND GUIDELINES
Designing with CASE tools Computer-Aided Software Engineering (CASE) tools and techniques automate the process of developing software and database designs. You can use CASE tools to create new custom objects and to generate a geodatabase schema from a UML diagram. Object-oriented design tools can be used to create object models that represent your custom objects. You can use these models to create a COM object that implements the behavior of the custom object as well as the database schema where these custom objects are created and managed. 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 the ArcInfo Developers Guide. Strategies for using CASE for schema design and generation Two general strategies exist for using UML and CASE tools to design and create your geodatabase. The first strategy involves using UML to define all of the schema for the geodatabase, generating that schema, then populating the schema with data. The second strategy takes the opposite approach. It involves creating the schema by importing existing data into your geodatabase, building geometric networks, then using CASE tools to apply your UML model to the existing data. You can use a combination of the two strategies discussed if your UML model describes a larger schema than defined when you imported your existing data. Once your schema has been created using one or both of these strategies, you can modify it by modifying your UML model, then reapplying the model to your geodatabase schema using the Schema Creation Wizard. Alternatively, you can use the schema management tools in ArcCatalog to modify your geodatabase schema.
Strategies for using CASE for schema design and generation Two general strategies exist for using UML and CASE tools to design and create your geodatabase. The first strategy involves using UML to define all of the schema for the geodatabase, generating that schema, then populating the schema with data. The second strategy takes the opposite approach. It involves creating the schema by importing existing data into your geodatabase, building geometric networks, then using CASE tools to apply your UML model to the existing data. You can use a combination of the two strategies discussed if your UML model describes a larger schema than defined when you imported your existing data. Once your schema has been created using one or both of these strategies, you can modify it by modifying your UML model, then reapplying the model to your geodatabase schema using the Schema Creation Wizard. Alternatively, you can use the schema management tools in ArcCatalog to modify your geodatabase schema. Modeling a switch There are many different methods of modeling realworld objects. The following example shows the steps needed to model a common electric distribution component, a switch, and shows how it could be modeled in the context of ArcGIS Electric Distribution. To correctly implement a switch, you need to define the switches in your system. This could include a physical description and an description of how switches operate. A switch disconnects circuits within the distribution network and can be manually or power operated. Switches are operated by opening the contacts, which interrupt the current, allowing personnel to repair damaged lines or other equipment. Once a switch is defined, describe how switches are used in the distribution system. Also provide any significant details related to the device. Switches are either open or closed. Switches are critical to the electric distribution system to allow current interruption to allow system maintenance, redirecting current in case of emergency, or to isolate
Table of Contents
system failures. Switches may be automated and controlled remotely through SCADA operation. Next describe the processes that a switch participates in. Routine maintenance, switching programs, and monitoring the switch to ensure proper operating condition. The switch participates in processes for maintenance, inventory, analysis, network tracing, feeder management, and SCADA. From the previous descriptions, list the information required to support the defined processes. Whether the switch is group operated or individually operated Whether the switch is manually operated Amount of current the switch can carry continuously without appreciable rise in temperature Amount of operating voltage the switch is rated to carry 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 the switch 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 to the ArcGIS model and component reference. By comparing the above descriptions and usage to the component reference, we can see that a switch can be modeled as an ElectricDevice in the ArcGIS Electric Distribution model. As there are other devices in the utility that can also be represented as ElectricDevice such as circuit breakerswe will model the switch as a subclass 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 may also have your data stored in other multiuser geographic information system data formats such as ArcStorm, Map LIBRARIAN, and ArcSDE. You can use tools in ArcCatalog to import data from these formats into your geodatabase.
ElectricDevice
Comments ElectricTraceWeight FacilityID FeederID FeederID2 FeederInfo InstallationDate NominalVoltage OperatingVoltage PhaseDesignation Subtype SymbolRotation WorkOrderID
LabelText MaxContinuousCurrent MaxInterruptingCurrent MaxOperatingVoltage NormalPosition[A,B,C] PresentPosition[A,B,C]
Switch
GangOperated LabelText ManuallyOperated MaxContinuousCurrent MaxOperatingVoltage NormalPosition[A,B,C] PreferredCircuitSource PresentPosition[A,B,C] SCADAControlID SCADAMonitorID TieSwitchIndicator
Switch feature class inherits attributes of ElectricDevice
Table of Contents
Converting existing data formats When you import data into the geodatabase, both the geometry and attributes are imported, though you can choose to drop or rename attributes. All or some of the feature classes from a coverage can be imported into an integrated feature dataset, and several shapefiles with the same spatial extent can also be imported into the same feature 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 networks and for establishing subtypes, attribute domains, and so on. To learn how to move your existing data into the geodatabase, see the book Building a Geodatabase, Chapter 4, Migrating existing data into a geodatabase. Loading data into a geodatabase schema Once you have generated a geodatabase schema from ArcCatalog or from UML and CASE tools, you will want to insert data into that schema. You can do this by using the Object Editor in ArcMap to create new objects, or you can load objects from existing shapefiles, coverages, INFO tables, and dBASE tables. This is a separate process from importing data as outlined above. Data creation and maintenance may involve managing version and topology information. ArcCatalog and ArcToolbox have wizards to help you with thisSimple Data Loader and Object Loaderwhich are discussed in Building a Geodatabase, Chapter 4, Migrating existing data into a geodatabase. In the previous sections we have discussed database design and some general methods for implementing ArcGIS Electric Distribution. There are three general scenarios: 1. Implement from the ArcGIS Electric Distribution geodatabase. 2. Implement select components generated by the ArcGIS UML.
3. Implement a custom geodatabase using UML based on the 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 from scratch. In practice, you will use a combination of all or some of the methods outlined. The first step is always to design the geodatabase. The book Modeling Our World is the guide to help you design your geodatabase. Once this design is complete, you can proceed. There are many implementation options. The process you choose depends on your database design and level of customization. You may use some or all of the described methods, depending on your requirements. The books Modeling our World and Building a Geodatabase provide directions for designing and implementing custom geodatabases.
Table of Contents
ARCGIS ELECTRIC DEPLOYMENT SCENARIOS
Scenario 1: Implementing ArcGIS Electric Distribution from a geodatabase. Implementing using the ArcGIS Electric Distribution geodatabase is a quick and easy method of implementation when little or no modifications of the ArcGIS Electric Distribution model are required. Establish a data model To begin, install ArcGIS Electric Distribution, then, as with all implementation processes, determine the data model requirements for your system. If analysis of your logical data model shows that the ArcGIS Electric Distribution data model fits your needs as is, or may only require minimal customization, then this process is suggested. If the geodatabase schema and the components of the ArcGIS Electric Distribution model fit your database design, you can migrate your existing data directly into the ArcGIS Electric Distribution geodatabase. Refine the geodatabase using ArcCatalog You can use ArcCatalog to continue defining your geodatabase by establishing how objects in the database relate to one another. This is the simplest and most direct method of implementing ArcGIS Electric Distribution. Using ArcCatalog, you can establish relationships between objects in different object classes and connectivity rules for objects participating in geometric networks. You can continue to use the geodatabase management tools in ArcCatalog to refine or extend a mature database throughout its life. In some cases, you may not yet have any data that you want to load into a geodatabase, or the data you have to load only accounts for part of your database design. In this case, you can use the tools provided in ArcCatalog to create the schema for feature datasets, tables, geometric networks, and other items inside the database. ArcCatalog provides a complete set of tools for designing and managing items you will store in the geodatabase. These relationships and rules may be part of the schema that CASE tools generate, but often you will want to further refine what is generated by CASE to meet your
geodatabase design. What to do To implement your data model from the ArcGIS geodatabase, 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 Electric Distribution from a repository. In most cases a subset of components of the ArcGIS Electric Distribution model will be sufficient for your implementation. ArcCatalog contains tools to read the Microsoft Repository generated from the ArcGIS Electric Distribution UML. The Schema Creation Wizard guides you through the process of creating new feature classes, tables, and other pieces of your geodatabase. Although all of the required information for the geodatabase schema can be read directly from the repository, you can select those components that fit your database design. Once the wizard is finished, you will have schema for your design ready to be populated with data. Just as when implementing from the ArcGIS Electric Distribution geodatabase, you can then use ArcCatalog to establish relationships between objects in different object classes and connectivity rules for objects participating in geometric networks. This scenario is reviewed in detail in the following case study. To implement your data model from the Microsoft Repository containing the the ArcGIS data model, the following steps are required: 1. Create the logical data model 2. Build the physical database model
Table of Contents
3. Use ArcCatalog CASE tools to create schema and code referencing an existing repository. While in the CASE tool, select only the model components you wish to generate. 4. Use ArcCatalog to edit the schema 5. Migrate your data into the geodatabase 6. Deploy database throughout your site Scenario 3: Implementing ArcGIS Electric Distribution from a UML drawing. CASE tools allow you to create custom objects and features that extend the geodatabase model of ArcInfo 8. Object-oriented design tools that support the Unified Modeling Language (UML) and the Microsoft Repository can be used to create designs for your objects. Once exported to the Microsoft Repository, the CASE tools subsystem will help you create a Component Object Model (COM) object that implements the behavior of your custom object and the database schema where these objects are stored. The CASE tool subsystem of ArcInfo 8 lets you extend the ArcInfo geodatabase model to create custom objects. These custom objects inherit behavior from existing ESRI data objects. You can use C++ to override and add behaviors to the behavior inherited from the ESRI objects. Once you have implemented your custom object, it must be stored inside the geodatabase. You can use the same UML diagram to generate the schema for the object using the CASE tools subsystem. You can also use the CASE tools to apply your UML design to existing feature classes and tables. The objects that you describe using UML dont necessarily have to have custom behavior. You can also use UML to design the schema for ESRI simple and ESRI network objects. You can use UML to design your feature classes and tables, including what attribute fields they have, their subtypes, 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 Model diagrams. You can also start from the Visio Enterprise Drawing templates. These Visio Drawing templates are located under your ArcInfo installation. 34 ArcGIS Electric Distribution Model
The ArcInfo UML Model diagrams contain the object model required for using UML to model a generic geodatabase. The ArcGIS Electric Distribution UML diagrams contain the UML model implemented in ArcFM Electric. The tools to export your UML model to the repository are contained within Visio. To implement an advanced implementation of your data model using UML, the following steps are required: 1. Create the logical data model 2. Build the physical database model 3. Create a UML drawing of the ArcGIS Electric Distribution 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
Table of Contents
Generating code
The CASE tools subsystem of ArcInfo 8 has two parts: the Code Generation Wizard, and the Schema Creation Wizard. The Code Generation Wizard allows you to create custom COM objects for each component of your geodatabase. More information on the ESRI object model and on generating code for your custom objects using the Code Generation Wizard, see Modeling Our World and the ArcInfo Developers Guide. In the previous sections we have discussed database design and some general methods for implementing ArcGIS Electric Distribution. In this section we will examine in greater detail the process of implementing from a Microsoft Repository. This case study reviews the implementation from installation to deployment and directs you to references and task descriptions for each step in the process. This scenario was selected because it contains tasks common to most methods of implementation.
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 system modeling needs. To do this, document how your data is currently represented, then define the data components required to adequately model your system to support the process of your organization. Define model components Define the components required to adequately model 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 guide for determining the objects, attributes, and classes for your design. Constructing a logical data model is an interactive process and an art that is acquired through experience. While there is no single correct model, there are good models and bad models. It is difficult to determine when your data requirements are correctly modeled and complete, but an indication that you are coming close is when you can answer yes to the following questions: Does the logical data model represent all data without duplication?
COM Code Generator
Pole
3rd Party CASE

MS Repository Electric.schema
Pole
Uml Object Model

GeoDb Schema Generator
Does the logical data model support an organizations business rules? Does the logical data model accomodate different views 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 relationships are implemented. The physical database model is built from the logical data model, and is generally constructed by a relational database specialist. The geodatabase is a physical implementation of data that allows a structure similar to the logical data model. As such, most physical database models are directly supported by the existing
Table of Contents
IMPLEMENTING ARCGIS ELECTRIC
framework of the geodatabase. In most cases, the logical data model is directly implemented into the geodatabase greatly simplifying the traditional task of physical database modeling. Step 3: Determine customization requirements Compare your logical data model and physical database model to the ArcGIS electric distribution model to determine your implementation requirements. The results of your comparison will show which of the feature classes, subtypes, attributes, relationships, and domains are applicable for your data model. Define which rules and behaviors must be created through customization of the geodatabase, or through custom applications built using the geodatabase framework. For more information about customizing a geodatabase, see Building a Geodatabase and Modeling our World. Step 4: Generate a custom geodatabase Use ArcCatalog CASE tools to create schema and code referencing an existing repository. ArcCatalog uses CASE tools to read the Microsoft Repository database you created using the UML modeling software (Visio). The CASE tool guides you through the process of creating new feature classes, tables, and other pieces of your geodatabase using the Schema Creation Wizard. During the schema generation process, you will be presented with an hierarchical list of all of the row, feature and network feature types in the repository. Many of objects and features contain subtypes with attribute domains and default values. You do not have the option of selecting a relationship class as you do with tables and feature classes. This is the case because the presence of a relationship class is dependent upon the existence of the feature classes or tables that are related by it. The CASE tool schema generator manages whether a relationship class is created based on feature classes and tables that you select.
If the schema you are generating contains attribute domains, you can view the properties for these domains, but you cannot modify them. For more information about generating a geodatabase from a repository, see Building a Geodatabase, Using ArcCatalog, and Modeling Our World. Step 5: Edit the schema using ArcCatalog Use ArcCatalog to modify the schema of your geodatabase and add behavior. No programming is required when you use the data management tools in ArcCatalog. Using ArcCatalog you can add behavior to the geodatabase by creating object classes, subtypes, validation rules, relationships, and a geometric network. A tutorial for this process is available in the book Building a 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 the table or feature class to ensure that the network connectivity and version information is managed correctly. this data loading operation is performed with the Object Loader Wizard in ArcMap. For more information on the Object Loader, see Building a Geodatabase, Chapter 10, Editing your geodatabase.
Table of Contents
Generating a geodatabase from a repository The following section shows, in detail, how to generate a custom geodatabase from an existing repository. The example uses one of the sample ArcGIS Electric Distribution Repositories, but the process would be the same if you customized the UML model and created your own repository. 1. After creating the repository, you will need to start ArcCatalog and create a Personal Geodatabase. In ArcCatalog, navigate to the folder in which you want to create the geodatabase. 3. Right-click the geodatabase, point to New and click Feature Dataset. 4. Type a name for the new feature dataset in your personal geodatabase. After entering a name you need to Enter or Select a Coordinate System for your feature dataset. In the Feature Dataset form select the Edit button and the Spatial Reference Properties form will display. 5. Click Edit in the Spatial Reference section. 2. In the Catalog tree, click the folder, then right-click, point to New, and click Personal Geodatabase. Type a name for your personal geodatabase and press Enter.
All of the feature classes in a feature dataset must share the same Spatial Reference. You can use the Coordinate System of an existing dataset (for example, a landbase coverage) to set the Spatial Reference. Be sure that the extent of the dataset is the same as, or greater than, that of all of the feature classes that youll load into the dataset.
Table of Contents
9. Click and drag Schema Wizard from the Commands list onto an existing toolbar, then Close the Customize dialog. The Schema Wizard tool is shaded grey (disabled) when you close the customize dialog if you do not have a Geodatabase or a Feature Dataset selected.
6. Select or Import a Coordinate System for your Dataset. For more information about setting a Spatial Reference see Building a Geodatabase and Using ArcCatalog. Once the Spatial Reference is set, the next step is to add the CASE tool to an ArcCatalog toolbar, so you can create the Geodatabase Schema. 7. In ArcCatalog, right-click on any of the toolbars and click Customize. 8. Click the Commands Tab and click Case Tools in the Categories list. 10. Click the feature dataset in the Catalog tree. Clicking the dataset activates the Schema Wizard tool and will allow you to import the repository you created from the UML model. 11. Click the Schema Wizard tool, to start the Schema Creation Wizard. 12. A brief introduction to the wizard appears. Click Next.
Table of Contents
15. Click the object model you created in the repository, then click Next.
13. Click Browse and navigate to the repository you created. In most cases you will not have to enter a user name and password unless you specified one while exporting the UML model. 14. Click Next. A repository may contain several object models.
The Schema Wizard begins importing the objects. This may take several minutes, depending upon the size of your object model. After the Schema Wizard finishes with the object import, you will be able to see a tree view of the objects that will be imported into your Geodatabase. All the objects in your object model are selected to be imported by default. You may uncheck the checkbox for the Feature Dataset in which case, only the objects defined outside the Feature Dataset will be imported. Click the plus and minus sign located next to the Feature Dataset to expand and contract the tree view.
Table of Contents
17. The Schema Wizard creates a Geometric Network automatcially for you if you did not define one in your UML model and your model contains at least one network feature. You may override the generic name assigned to the network by selecting the network and clicking on the Properties button (or double-click the network). Type the new name for your network and click OK. Click Next.
16. In the Schema Creation form you can highlight an object and view the objects properties by clicking the Properties button (or simply double-click the object in the tree view). You may also modify certain properties such as string field lengths, relationship primary/foreign keys, or the spatial reference of the Feature Dataset.
18. The wizard presents a summary of the feature and object classes youve chosen to create. Click Finish.
Table of Contents
Loading data with ArcCatalog 1. In the Catalog tree view, right-click the feature class and click Load Data. 2. Click the browse (folder Icon) button, navigate to and select the input data you want to load. After selecting the data file, you will see the data file displayed in the Input data field. 3. Click the Add button to add the data to the List of source data to load window.
The Schema Wizard creates the feature classes, tables, and other objects, such as domains, relationships, and network connectivity 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 (feature dataset, feature classes, tables, relationships, and a geometric network) that were defined in your object model and generated by the Schema Wizard. The next step is to load your existing data into the empty feature classes and tables. You can load data into the feature classes with ArcCatalog, using the Simple Data Loader, or you can load data with ArcMap. The steps to load data from ArcCatalog are presented below. Selecting the file from the List of source window will activate the Remove button. 4. Click Next. 5. In the Simple Data Loader form, the radio button I do not want to load all features into a subtype will be active. All other fields are disabled. Click Next.
Table of Contents
9. If you want to load selected features, click Load only the features that satisfy a query. Click Query Builder. The Query Builder allows you to select which features to load, based upon the values of one or more attributes.
6. For each Target Field in the list, click the Matching Source Field and match the fields and data types. One important step in creating your electric distribution model is to duplicate the data types of the fields that exist in your existing data. This will ensure a smooth data load transition from source to target fields. 7. After matching all the data types, click Next. 8. If the source coverage or shapefile contains only features of the type you are loading, you can use the default option, Load all of the source data. Click Next, and youll be be presented with a summary of the data loading operation. 10. Double-click the field that you want to query on, click an operator (such as the equals sign), then doubleclick on a value of that field in the Unique values list. Clicking Clear will clear the query and clicking Verify will verify the query you create.
Sometimes you will want to load only a selected group of features from your source data into a given feature class. This would be the case if you have been using a single converage feature class or shapefile to hold several types of features differentiated by an attribute. 42 ArcGIS Electric Distribution Model
11. Click OK, then click Next on the Simple Data Loader.
Table of Contents
2. Navigate to the empty feature class and add it to the map.
12. The data loader shows a summary of the data loading operation. Click Finish. When you click Finish, the data loading operation begins. A status bar at the lower left corner or the ArcCatalog window shows the number of objects being loaded into the feature class.
3. Right-click over a toolbar and click Customize.
Loading data with ArcMap You also can use ArcMaps Object Loader to load data into a feature class in a versioned geodatabase. In fact, you must use ArcMap to load data into non-simple feature classes, such as network feature classes or feature classes that participate in composite relationships. 1. Start ArcMap and click the Add Data button on the Standard Toolbar. 4. Click the check box to turn on the Editor toolbar.
Table of Contents
5. Click the Commands Tab, and click Data Converters.
8. Select a feature class and subtype (if applicable) in the Targets dropdown list.
9. Click Load Objects. The Object Loader Wizard appears.
6. Click and drag Load Objects onto the Editor toolbar. Close the Customize dialog.
Use the same steps to load data with the ArcMap Object Loader Wizard as you would use to load data with the Simple Object Loader. One difference between the Simple Data Loader and the Object Loader, is that if you use the Object Loader you will be prompted to choose whether to snap the input features using the Editors current snapping environment, and whether to use validation rules to validate the features you load. Snapping is useful when you have some features already loaded and on the map, and you want to make sure that the new features snap to the existing features. If your features are precisely located with respect to the existing features, you do not need to snap them.
In order for you to use the Load Objects button you will need to start an Edit session. 7. Click Editor and click Start Editing.
Table of Contents
If you choose to validate features, the Object Loader will apply any attribute, relationship and connectivity rules that exist in your schema to the features. Invalid features will be loaded into your geodatabase, but will remain selected.
Table of Contents
46 Geographic Analysis DRAFT 7/17/98
Table of Contents
4 3
Structur uctures Data Structures Data Refer erence Model Reference
Table of Contents
47
76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321 76543210987654321098765432121098765432109876543210987654321
AerialMarker SupportStructure SurfaceStructure FacilityStructure Structure

STRUCTURES OVERVIEW
Structures support electrical transmission and distribution equipment and can be located overhead, on the ground, or underground.
STRUCTURES
Feature
EquipmentEnclosure
ElectricStation
Pushbrace
Table of Contents
SwitchingFacility WarningSign
AnchorGuy
Guy
SpanGuy
Riser
Structures Structure is an abstract class whose attributes are inherited by features that support electrical transmission and distribution equipment. Structures can be located overhead, on ground surface, or underground. Overhead structures are designed to support mechanical loads imposed by conductors and equipment as well as additional loads presented by wind, ice, and/or snow. ANSI-provided specifications and dimensions rate poles, which are grouped into classes based on their circumference 6 feet from the butt. Poles of a certain class and length are designed to have about the same load carrying capacity. Overhead structures, such as poles, H-frames, and towers, vary in material, height, and guying and/or bracing requirements based on the combination of anticipated vertical and horizontal loads. Surface structures house equipment on the 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
3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321
Feature
Structure
Comments InstallationDate WorkOrderID
Feature
Facility Structure FacilityStructure is an abstract class containing common attributes of the EquipmentEnclosure abstract class and the SupportStructure feature class (Hframes, poles, towers). EquipmentEnclosure includes these feature classes (and subtypes): SurfaceStructure (pads, pedestals, connections boxes), ElectricStation (main, net, substations), and SwitchingFacility (junctions cabinets, switch boards). FacilityStructure defines the following attributes: FacilityID: text Meaningful company-assigned unique identifier Owner: text Code indicating owner of structure; domain values include CustomerOwned, LocalBell, PowerCompany, OtherUtility Subtype: long integer Code indicating type of structure SymbolRotation: double Angle of rotation dictating how a feature appears on the map Subtypes: None Associations: Electric Device, Electric Location
43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321
Structure FacilityStructure
FacilityID Owner Subtype SymbolRotation
Table of Contents
Chapter 4 Structures Component Reference 49
Feature
Structure
Support Structure SupportStructure is a subclass of FacilityStructure describing objects that support electric devices. Although many underground distribution systems are now being built, a tremendous amount of overhead plant is still in use. Overhead poles are subject to vertical and horizontal forces including weight of wires, transformers, and other equipment. Vertical forces are the unbalanced component of wire tension at curves and corners, the pull of service drops, and the horizontal component of weight if the pole is not vertical. Wood poles have long been used for overhead distribution because of abundance of material, ease of handling and cost. Preservatives help to prolong the life of the pole. The strength of a wood pole must be sufficient to withstand abnormal loads as well, such as ice and wind pressure. SupportStructure features can have street lights, assemblies, and other attachments associated with them. SupportStructure inherits characteristics from the abstract 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 structure; domain values include Set on Concrete Foundation, Set Extra Deep in Earth, etc. Grounded: text Code indicating whether structure is grounded; domain values are Yes or No Height: text Code indicating height of structure; domain values include 20 Feet, 25 Feet, 30 Feet, 40 Feet, etc. Manufacturer: text Manufacturer Material: text Code indicating material of structure; domain values include Aluminum, Fiberglass, Wood, etc. PoleCount: long integer Number of poles present in H-frame structure Style: text Code indicating style of SupportStructure; domain values include Decorative, Normal TreatmentType: text Code indicating type of treatment used, if any; domain values include Creosote, Paint, Pentachlorophenol, Chromated Copper Arsenates, etc. UsageType: text Code indicating use of structure; domain values include Distribution 2-Pole Structure, Street Light, Transmission, etc. YearManufactured: text Year structure was manufactured Subtypes: H-Frame, Non-Wood Power Pole, Wood Power Pole, Non-Wood Street Light Pole, Wood Street Light Pole, Tower Associations: Assembly, Foreign Attachment, StreetLight (valid only for subtypes Non-Wood Street Light Pole and Wood Street Light Pole)
543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321
FacilityStructure SupportStructure
Class Diameter FoundationType Grounded Height Manufacturer Material PoleCount Style TreatmentType UsageType YearManufactured
Table of Contents
Feature
SurfaceStructure SurfaceStructure contains objects that protect or enclose electric circuits and equipment on the ground. SurfaceStructure defines the following attributes: Manufacturer: text Manufacturer Material: text Code indicating material enclosing SurfaceStructure; domain values 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 Station ElectricStation represents a building or fenced-in enclosure that houses the equipment that switches and modifies the characteristics of energy from a generation source. Distribution systems include primary feeders (circuits), transformer banks, and secondary circuits (overhead or underground) that serve a specified area. Distribution substations operate at 13.8 to 69 kV and usually have a number of radial three-phase feeders off which branch lines, or laterals, are tapped to deliver power to residences, stores, garages, and Feature other loads. Transmission substations operate at 69 to 765 kV. Voltages of 345, 500 and 765 kV are considered extra high voltage (EHV). ElectricStation defines the following attributes: Name: text Name of ElectricStation StationNumber: text Utility-assigned number of ElectricStation Associations: None Subtypes: Main Station, Net Station, Sub Station
Table of Contents
Chapter 4 Structures Data Model Reference 51
543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 1 543210987654321 54321098765432
543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321
Structure FacilityStructure EquipmentEnclosure SurfaceStructure
Manufacturer Material Model Name StructureSize
Structure
FacilityStructure
EquipmentEnclosure
ElectricStation
Name StationNumber
Switching Facility SwitchingFacility is the feature class representing structures that support or enclose switching and associated equipment including transformers, buses, switchgears, and fuses. Automated feeder switching systems control individual circuits and reduce the occurrence and duration of faults and optimize feeder and substation loading. SwitchingFacility defines the following attributes: Configuration: text Configuration of SwitchingFacility Manufacturer: text Manufacturer Model: text Model of enclosure NominalVoltage: long integer Code indicating system voltage for which SwitchingFacility is rated; domain values include 14.6kV, 24.9kV, 34.5kV Associations: BusBar Subtypes: Auto Transfer Enclosure, Junction Cabinet, Two-Cabinet PadMounted Switchgear, Four-Cabinet Pad-Mounted Switchgear, Switch Board Aerial Marker An AerialMarker indicates the presence of overhead cable and structures. AerialMarker defines the following attributes: LightIndicator: text Code indicating presence of light indicator; domain values are Yes and No SymbolRotation: double Angle of rotation dictating how a feature appears on map Associations: None Subtypes: None
Table of Contents
3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321
543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321
Feature
Structure FacilityStructure EquipmentEnclosure SwitchingFacility
Configuration Manufacturer Model NominalVoltage
Feature
Structure
AerialMarker
LightIndicator SymbolRotation
Feature
Guy Guy is an abstract feature class that inherits the attributes of the abstract class Structure. Guy includes the wire or collection of wires that support poles, Hframes, or towers. Guys are used to add support if the horizontal load is greater than the pole can safely support and when conductor tensions arent balanced such as at dead ends, corners, or where the direction of the conductor changes suddenly. 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 include Steel, Other WireSize: text Code indicating size of guy wire used; domain values include 1/2, 3/8, 5/16, etc. WireStrength: text Code indicating strength rating of wire composing the guy; domain values include Common, High Strength, etc. Associations: None Subtypes: None Anchor Guy AnchorGuy is a wire or set of wires running from the top of the pole to an anchor installed in the ground and consist of wires, appropriate fastenings and the anchor. The anchor guy is usually installed at a distance from the pole that is 0.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 the pole to provide pedestrian clearance. The guy runs from the top of the pole to the 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 include Cone, Expanding, Log, Plate, Screw RodType: text Code identifying type of anchor fastening; domain values include Double Eye, Single Eye Subtype: long integer Code indicating subtype of anchor guy SymbolRotation: double Angle of rotation dictating how a feature appears on map Associations: None Subtypes: Back, Bridle, Sidewalk, Standard
3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321
Structure Guy
GuyCount LeadLength WireMaterial WireSize WireStrength
43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321
Feature
Structure Guy AnchorGuy
AnchorSize AnchorType RodType Subtype SymbolRotation
Table of Contents
Chapter 4 Structures Component Reference 53
SpanGuy
Pushbrace is a point feature that defines the following attributes: Class: text Code indicating class of pole supported by Pushbrace; domain values include Class 1, Class, 10, Class H1, etc. Height: text Code indicating height of Pushbrace; domain values include 20 Feet, 25 Feet, etc. Material: text Material of Pushbrace; domain value is Wood SymbolRotation: double Angle of rotation dictating how a feature appears on map Associations: None Subtypes: None
Feature
Structure
Riser A Riser is a cylindrical or channel enclosure attached to a pole or structure to provide protection for underground conduit as it transitions from overhead to underground. The physical connection between the overhead and underground connection occurs at a pothead. Riser defines the following attributes: ConstructionType: text Code indicating construction type of Riser; domain values 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 include Fiberglass, PVC, etc. SymbolRotation: double Rotation angle dictating how feature appears on map Associations: None Subtypes: None
Riser
ConstructionType Height Material SymbolRotation
Table of Contents
3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 1 3210987654321 321098765432
3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321
Feature
Structure Guy
Span Guy Span guys are installed to span from the top of one structure or pole to the other and offset the strain from the line conductor. Span guys transmit horizontal force to another pole until an anchor guy can be used. SpanGuy is a linear feature and inherits attributes of Guy and Structure abstract classes. Associations: None Subtypes: None Pushbrace Pushbraces support or brace a pole when it is not feasible to use an anchor guy. A pushbrace is a pole or other member that is placed at an angle to help support the unbalanced pole and is often used on the inside curve of mountain roads. The poles that pushbraces support are grouped into classes based on their circumference 6 feet from the Feature butt.
Structure
Pushbrace
Class Height Material SymbolRotation
3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321
Warning Sign Warning sign indicates the presence of electric lines, structures, or devices. WarningSign defines the following attributes:
65432121098765432109876543210987654321 65432121098765432109876543210987654321 65432121098765432109876543210987654321 65432121098765432109876543210987654321 65432121098765432109876543210987654321 65432121098765432109876543210987654321 65432121098765432109876543210987654321 65432121098765432109876543210987654321 65432121098765432109876543210987654321 65432121098765432109876543210987654321 65432121098765432109876543210987654321 65432121098765432109876543210987654321 65432121098765432109876543210987654321 65432121098765432109876543210987654321 65432121098765432109876543210987654321 65432121098765432109876543210987654321 65432121098765432109876543210987654321 65432121098765432109876543210987654321 65432121098765432109876543210987654321 65432121098765432109876543210987654321 65432121098765432109876543210987654321 65432121098765432109876543210987654321
3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321 3210987654321
Feature
Structure WarningSign
FacilityID SymbolRotation
FacilityID: text Meaningful company-assigned unique identifier SymbolRotation: double Angle of rotation dictating how a feature appears on map Joint Use Attachment Other utilities or entities may attach conductors or cables that carry signals such as community antenna television systems (CATV) to support structures. Information about owners and joint use attachments is captured in this table. This related object class stores information about a feature with a spatial reference but does not 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 chargeable, domain values are Yes or No Owner: text Code indicating owner of attachment; domain values include Cable, Telephone, Other, etc. StructureObjectID: long integer ObjectID of structure supporting attachment Association: Support Structure Subtypes: None
Assembly
SupportStructure
FramingType StructureObjectID
JointUseAttachment
AttachmentDate Chargeable Owner StructureObjectID
Class Diameter FoundationType Grounded Height Manufacturer Material PoleCount Style TreatmentType UsageType YearManufactured
Table of Contents
Assembly Assembly identifies the type of structure and attachment connection. Assembly defines the following attributes: FramingType: text Code indicating type of assembly frame; domain values include A Frame, H Frame, etc. StructureObjectID: long integer Object ID of structure supporting assembly Association: Support Structure Subtypes: None Lifecycle History LifecycleHistory is an abstract object provided so that administrators can relate information about the history of particular devices or equipment. This information 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 new LifecycleHistory object is defined, you should also define any necessary relationships. LifecycleHistory defines the following attributes: Comments: text User or designer comments FacilityID: text Meaningful company-assigned unique identifier WorkFunction: text Code indicating life cycle phase; domain values include Install, Remove, Replace, Transfer, Retire, Abandon WorkOrderID: text Utility identifier of work order Associations: To be defined by user Subtypes: None
98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321 98765432109876543210987654321
Object
Inspection LifecycleHistory
Comments FacilityID InspectionDate InspectionType Inspector Comments FacilityID WorkFunction WorkOrderID
Table of Contents
Inspection Structures and devices are periodically inspected to ensure proper functioning and quality. The abstract class Inspection provides a way to define this information for structures, devices, controls, and units. Define specific Inspection objects on an asneeded basis. As a new Inspection object is defined, you should also define any necessary relationships. Inspection defines the following attributes: Comments: text User or designer comments FacilityID: text Meaningful company-assigned unique identifier InspectionDate: date Date inspected InspectionType: text Code indicating type of inspection; domain values include History, Inspection, Maintenance Inspector: text Name of inspector Associations: To be defined by user Subtypes: None
Table of Contents
21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321
BuriedDepth Configuration EncasementType FacilityID InstallationDate LabelText LengthSource Manufacturer MeasuredLength Model Subtype WorkOrderID
ComplexEdgeFeature
ConduitSystem
Most URDs include the following components: pad-mounted, dead-front transformer; primary laterals operated as open loops; 12.47 grounded Y/7.2 kV primary voltage; two primary cable connections per transformer; front-lot construction; four to eight homes per transformer; internal fusing; and direct-buried cables.
Underground structures describe the features and objects needed to support an underground electric system, including URD (underground residential distribution). UndergroundStructure is a simple junction feature that includes vaults and manholes that house and protect electrical equipment. The central component of URD and other underground systems is the single-phase distribution transformer which is usually housed in heavy, corrosion-resistant tanks for installing in subsurface vaults, known as submersible.
UNDERGROUND STRUCTURES
Table of Contents
Comments FacilityID InstallationDate Manufacturer Material Model StructureSize StructureType Subtype WorkOrderID
UndergroundStructure
PhaseDesignation ULS_Position
ConduitSystem_Conduit SystemMember CrossReference
RelationshipClass
UndergroundStructure defines the following attributes: Comments: text User or designer comments FacilityID: text Meaningful company-assigned unique identifier 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 System The underground system consists of ducts, direct buried cables, or pipes extending between vaults or manholes. New conductor and telephone cable are often installed underground in congested areas. Conductors and cables can be drawn or pulled from manhole locations for repairs or changes. Conduits, or underground linear structures, are constructed of materials that are impervious to water and do not degrade or corrode easily. Cable also may be buried directly in trenches, which ArcFM models as a ConduitSystem feature. In this case, ducts are used as placeholders for the position of cables and conductors associated with the trench. Cables are associated with conduits through an attributed relationship class called ConduitSystem_ConduitSystemMember Cross Reference. The user creates this relationship class to relate feature classes with model name ULS to feature classes with model name ULSMember. The ConduitSystem feature class contains information about the position and characteristics of ducts as seen from a manhole, vault, or a cross section of a trench and duct. Users can create duct characteristic fields to represent their business processes. Common materials are concrete, plastic, and fiberglass. Common duct diameters are 3 to 5 inches. Names of characteristics such as material or 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 these fields, such as steel or 5 inches, are stored for each duct in a COM object which is stored in the Configuration attribute field of the ConduitSystem feature class.
Table of Contents
ConduitSystem defines the following attributes: BuriedDepth: text Depth from top of conduit to ground line Configuration (see Duct Definition): blob Stores information about duct or position layout within the conduit in a COM object; stores the values of attribute fields created in Duct Definition object class EncasementType: text Code indicating encasement type; domain values include 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 Mapping System, Field Measurement Manufacturer: text Manufacturer MeasuredLength: double Length of UndergroundLinearStructure Model: text Model Subtype: long integer Code indicating subtype of ConduitSystem WorkOrderID: text Utility identifier of work order Associations: UndergroundStructure Subtypes: Duct Bank, Trench Configuration Field This single binary large object (blob) attribute field of the ConduitSystem feature class stores a COM object containing information describing the layout of the conduit. This includes the value of fields defined in the Duct Definition object class. Users can create fields in the Duct Definition table such as those listed below. The values of these fields, entered or edited when users place conduits on the map, are stored in the Configuration field. Utility administrators can maintain, query, and edit values in this field. Duct Definition The user creates the DuctDefinition object class with fields that describe selected characteristics of a duct, such as size or material. The attribute names listed to the left are provided as an example.
543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321
Object Class
Duct Definition
Availability DuctID DuctSize Material Subtype
Table of Contents
Circuit Segments Circuit Segments Data Model Refer erence Reference
Table of Contents
61
CIRCUIT SEGMENTS
ELECTRIC COMPLEX EDGE
ElectricComplexEdge contains the common attributes of primary, secondary, overhead, and underground conductors. ElectricComplexEdge is an abstract class that includes subclasses such as busbars and communication cable. These are represented as complex edge features because multiple devices can be connected along their edge. Circuits are modeled with options for feeder identifiers to support automated switching and tracing functions. SCADA applications in distribution systems are increasing in deregulated environments. Automated switching of feeder circuits involves supervisory control to support operator control of equipment. Data acquisition gathers telemetered data from a variety of sources to increase reliability and operator productivity. ElectricComplexEdge defines the following attributes: LengthSource: text Code indicating source of length measurement; domain values include Field Measurement, Mapping System MeasuredLength: long integer Length of ElectricComplexEdge Subtype: long integer Code indicating subtype of ElectricComplexEdge WorkOrderID: text Utility identifier of work order
Table of Contents
9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321
ComplexEdgeFeature
ElectricComplexEdge
LengthSource MeasuredLength Subtype WorkOrderID
ComplexEdgeFeature
Electric Line Segment ElectricLineSegment is an abstract class that captures information about the configuration and connectivity of conductors. Electric line segments are categorized by voltage and are either overhead or underground conductors. ElectricLineSegment represents circuits often referred to as feeders. Primary conductors originate at a main distribution center and supply one or more substations. Secondary networks are supplied by five or more primary feeders to keep transformer loading at 125 percent in the event of an outage. Capacitors reduce voltage drop along the feeder. Feeder management systems are created to determine which circuit a given electrical device belongs to (i.e., which source, or in looped system, sources feed it with power), and which of its electrical phases are energized on the primary side. This information can be used to create circuit maps and visually distinguish among different feeder systems. The subtypes of these ElectricLineSegments are primary, secondary, single-phase and three-phase. ElectricLineSegment defines the following attributes: ElectricLineObjectID: long integer Object ID of associated ElectricLine ElectricTraceWeight: long integer Used by Feeder Manager to determine device status and other information that affects circuit connectivity FeederID: text Feeder Manager identifier assigned to feeders and devices that participate in a specific distribution circuit FeederID2: text Feeder Manager identifier assigned if device is supplied by second feeder FeederInfo: long integer Feeder Manager-assigned phase information describing the phase of the circuit LabelText: text Provides text for line annotation NeutralMaterial: text Material of neutral wire; domain values include All Aluminum 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 values include 7.2 kV Grounded Y, 24.9 kV Grounded Y, 2400 Delta, etc. OperatingVoltage: long integer Code indicating standard level at which system is 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 values include A, AB, AC, etc. ServiceIndicator: text Indicates whether circuit is in service; domain values are Yes and No Associations: ElectricLine Subtypes: None
9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321
ElectricComplexEdge ElectricLineSegment
ElectricLineObjectID ElectricTraceWeight FeederID FeederID2 FeederInfo LabelText NeutralMaterial NeutralSize NominalVoltage OperatingVoltage PhaseDesignation ServiceIndicator
Table of Contents
Chapter 5 Circuit Segments Component Reference 63
Object
ConductorInfo The conductors used in distribution are most often made of aluminum or copper. ConductorInfo stores information about material and other properties of the conductors that compose circuits. For a given current, a circuits resistance is the average rate at which electrical energy is converted to heat. This object class is associated with linear features but does not itself have a location on the map. ConductorInfo defines the following attributes: AbandonedConductorObjectID: text Object ID of AbandonedConductor feature class that maintains user-defined attribute values ConductorMaterial: text Code indicating material of conductor; domain values include Copper, Aluminum, Steel, etc. ConductorSize: text Size of conductor InstallationDate: date Date conductor was installed InsulationType: text Code indicating type of insulation; domain values include 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 conductor PhaseDesignation: long integer Phase designation of conductor; domain values include A, ABC, etc. ReelNumber: text Number of cable reel UndergroundConductorObjectID: long integer ObjectID of related underground conductor Associations: AbandonedElectricLineSegment Subtypes: Primary Overhead, Primary Underground, Secondary Overhead, Secondary Undergrund, and Streetlight Conductor
9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321
ConductorInfo
AbandonedConductorObjectID ConductorMaterial ConductorSize InstallationDate InsulationType InsulationVoltage Manufacturer NumberConductorsPerPhase OverheadConductorObjectID PhaseDesignation ReelNumber UndergroundConductorObjectID
Table of Contents
AbandonedElectricLineSegment This feature class is created to maintain information about abandoned conductors. Attributes of this feature class are user-defined and depend on which field values need to be maintained after a feature is abandoned. Bus Bar BusBar is a large rigid conductor that connects devices in switching facilities to feed power to two or more circuits. Substation buses carry current in a confined space and need to have enough structural strength to support the stress of shortcircuit current, high wind, and ice loading. Distribution substation buses are often made of copper and aluminum tubing. Bus capacity is limited by heating effects of the current. Other factors affecting the heating of a bus include size and shape, surface area, and ventilation. Tubular buses provides a larger cross-sectional area in a minimum space but is offset by a smaller surface area for dissipating heat loss. BusBar defines the following attributes: BusBarShape: text Shape of BusBar, which affects size of cross-sectional area and heating ElectricTraceWeight: long integer Used by Feeder Manager to determine device status and other information that affects circuit connectivity FdrMgrNonTraceable: long integer Used by Feeder Manager if assigned model name to indicate that device is not to be included in tracing FeederID: text Feeder Manager identifier assigned to feeder and devices that participate in a specific distribution circuit FeederID2: text Feeder Manager identifier assigned if device is supplied by second feeder FeederInfo: long integer Feeder Managerassigned phase information describing the phase of the circuit Loading: text Device capacity delivered to load area, in MVA
32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321 32121098765432109876543210987654321
ComplexEdgeFeature
ElectricComplexEdge
Feature
BusBar
CommunicationCable
BusBarShape ElectricTraceWeight FdrMgrNontraceable FeederID FeederID2 FeederInfo Loading NominalVoltage OperatingVoltage PhaseDesignation Spacing SwitchingFacilityObjectID
NominalVoltage: long integer Code indicating system voltage for which BusBar is rated, domain values include 7.2 kV Grounded Y, 24.9 kV Grounded Y, 2400 Delta, etc. OperatingVoltage: long integer Code indicating standard level at which system is currently being operated that may vary above or below nominal voltage; domain values include 120 Volts, 480 Volts, etc.
Table of Contents
Chapter 5 Circuit Segments Data Model Reference 65
PhaseDesignation: long integer Code indicating phases present on conductor; domain values include A, AB, AC, etc. Spacing: text Distance between buses following minimum electrical clearance for various BILs SwitchingFacilityObjectID: long integer Object ID of associated SwitchingFacility Associations: CircuitSource, SwitchingFacility Subtype: BusBar Communication Cable CommunicationCable carries non-electric signals within the network. Structures, mainly poles, may be used under a joint ownership agreement or lease to support power and communication lines. Other utilities or entities may attach cables that carry signals such as community antenna television systems (CATV). CommunicationCable can also be used to control Supervisory Control and Data Acquisition (SCADA) equipment. CommunicationCable inherits the attributes of ElectricComplexEdge. Overhead Electric Line Segment Overhead electric line segments carry electric current and are supported by structures including power poles, H-frames, and towers. The abstract class OverheadElectricLineSegment inherits the attributes of ElectricComplexEdge and ElectricLineSegment. 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 phases present on conductor Subtype: Single Phase Primary Overhead, Two Phase Primary Overhead, Three Phase Primary Overhead, Single Phase Secondary Overhead, Three Phase Secondary Overhead, and Streetlight Conductor Underground Electric Line Segment Primary URD cables are usually single-conductor, concentric-neutral insulated with polyethylene or cross-linked polyethylene. Utilities may direct bury primary
9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321
ComplexEdgeFeature
ElectricComplexEdge ElectricLineSegment OverheadElectric LineSegment
ConductorConfiguration PhaseOrientation
Table of Contents
cables in the same trench as communication cables. Secondaries and services are usually served by three cables insulated with polyethylene that may be separate cables or triplex construction. UndergroundElectricLineSegment defines the following attributes: BackfillMaterial: text Code indicating material used to backfill; domain values include Concrete, Slurry, Soil, Other BuriedDepth: double Distance below grade to top of UndergroundElectricLineSegment CableCount: long integer Code indicating number of cables; domain values include 1, 2, 3, etc. InConduitIndicator: text Code indicating whether UndergroundElectricLineSegment is in conduit, values are Yes or No Associations: ConduitSystem Subtype: Single Phase Primary Underground, Three Phase Primary Underground, Single Phase Secondary Underground, Three Phase Secondary Underground, and Streetlight Conductor
Table of Contents
109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321 109876543210987654321
ComplexEdgeFeature
ElectricComplexEdge ElectricLineSegment UndergroundElectric LineSegment
BackfillMaterial BuriedDepth CableCount InConduitIndicator
Chapter 5 Circuit Segments Component Reference 67
4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321 4321098765432121098765432109876543210987654321
BusBarObjectID ConnectionConfiguration DynamicProtectiveDevObjectID EmergencyCapacityKW GroundReactance FeederSourceInfo GroundResistance ID MaximumCapacityKW MaxKVAR MaxPositiveSequenceReactance MaxPositiveSequenceResistance MaxZeroSequenceReactance MaxZeroSequenceResistance MinFaultCurrentOH MinFaultCurrentUG MinKVAR MinPositiveSequenceReactance MinPositiveSequenceResistance MinZeroSequenceReactance MinZeroSequenceResistance Name NominalVoltage OperatingVoltage SubstationID Subtype VoltageAngle

CircuitSource
Object
ID Name NominalVoltage Subtype
ElectricLine
ElectricLine defines the following attributes:
Electric Line ElectricLine is an object class provided to store information associated with conductors but does not have a location on the map.
CircuitSource A circuit (feeder) is the aggregate of the conductors and equipment downstream of a substation breaker or recloser. CircuitSource stores attributes that describe characteristics of the circuit measured or estimated at the breaker or recloser. These attributes include capacity, measured in kilowatts (kW); resistance, measured in ohms; and load, which is measured in reactive kilovolt-amperes (kVAR).
Subtypes: Circuit Line, Station Line
Association: ElectricLineSegment
Subtype: long integer Code indicating subtype
NominalVoltage: long integer Code indicating system voltage for which ElectricLine is rated, domain values include 7.2 kV Grounded Y, 24.9 kV Grounded Y, 2400 Delta, etc.
Name: text Name of ElectricLine
ID: text Utility identifier of ElectricLine
Table of Contents
ElectricLineObjectID ElectricTraceWeight FeederID FeederID2 FeederInfo LabelText NeutralMaterial NeutralSize NominalVoltage OperatingVoltage PhaseDesignation ServiceIndicator
ElectricLineSegment
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 dynamic protective device EmergencyCapacitykW: long integer Emergency rating of CircuitSource, in KW; domain values include 12 GroundReactance: double Reactance of ground seen at the source by the downstream circuit FeederSourceInfo: long integer Stores information about source of feeder GroundResistance: double Resistance of ground seen at the source by the downstream circuit ID: text System-generated identifier of feeder initiated at this source MaximumCapacitykW: long integer Maximum allowable operating capacity of CircuitSource; domain values include 10 MaxKVAR: long integer Maximum kVAR load experienced at CircuitSource; domain values include 6 MaxPositiveSequenceReactance: double Maximum positive sequence reactance seen at the source by the downstream circuit, in ohms MaxPositiveSequenceResistance: double Maximum positive sequence resistance seen at the source by the downstream circuit, in ohms MaxZeroSequenceReactance: double Maximum zero sequence reactance seen at the source by the downstream circuit, in ohms MaxZeroSequenceResistance: double Maximum zero sequence resistance seen at the source by the downstream circuit, in ohms MinFaultCurrentOH: long integer Calculated minimum fault current for overhead conductors MinFaultCurrentUG: long integer Calculated minimum fault current for underground conductors MinkVAR: long integer Minimum kVAR load experienced at CircuitSource; domain values include 500 MinPositiveSequenceReactance: double Minimum positive sequence reactance seen at the source by the downstream circuit, in ohms MinPositiveSequenceResistance: double Minimum positive sequence resistance seen at the source by the downstream circuit, in ohms MinZeroSequenceReactance: double Minimum zero sequence reactance seen at the source by the downstream circuit, in ohms MinZeroSequenceResistance: double Minimum zero sequence resistance seen at the source by the downstream circuit, in ohms
Table of Contents
Chapter 5 Circuit Segments Data Model Reference 69
Name: text Utility name of CircuitSource NominalVoltage: long integer Code indicating system voltage for which CircuitSource is rated; domain values include 7.2 kV Grounded Y, 24.9 kV Grounded Y, 2400 Delta, etc. OperatingVoltage: long integer Code indicating standard level of voltage at which system is currently operated, in kV; domain values include 12.5 kV Grounded Y, 7.2 kV Grounded Y, etc. SubstationID: text Substation identifier Subtype: long integer Code indicating subtype VoltageAngle: double Angle at which phase is offset from system standard Associations: BusBar, CircuitBreaker, Recloser Subtypes: kW, Swing, Voltage Controlled Electric Line ElectricLine is provided as a way to model ElectricLine as a simple edge feature rather than as the ElectricLine object. ElectricLine feature supports symbolized lines and segments within lines. It is equivalent to the Electric Line object and associated with ElectricLineSegment. Subtypes include Circuit Line and Station Line. ElectricLine defines the following attributes: ID: text Utility identifier of ElectricLine Name: text Name of ElectricLine NominalVoltage: long integer Code indicating system voltage for which ElectricLine is rated, domain values include 7.2 kV Grounded Y, 24.9 kV Grounded Y, 2400 Delta, etc. Subtype: long integer Code indicating subtype Subtype: Circuit Line, Station Line
765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321 765432121098765432109876543210987654321
Object
ElectricLineSegment ElectricLine
ID Name NominalVoltage Subtype ElectricLineObjectID ElectricTraceWeight FeederID FeederID2 FeederInfo LabelText NeutralMaterial NeutralSize NominalVoltage OperatingVoltage PhaseDesignation ServiceIndicator
Table of Contents
Devices Data Devices Data Refer erence Model Reference
Table of Contents
71
ELECTRIC DEVICE
ELECTRIC DEVICE
ElectricDevice is an abstract class represented as a simple junction feature because devices 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, or regulate electric current, such as transformers and voltage regulators. ElectricDevice defines the following attributes: Comments: text User or designer comments ElectricTraceWeight: long integer Used by Feeder Manager to determine device status and other information that affects circuit connectivity FacilityID: text Meaningful company-assigned unique identifier of ElectricDevice FeederID: text Feeder Manager identifier assigned to feeders and devices that participate in a specific distribution circuit FeederID2: text Feeder Manager identifier assigned if device is supplied by second feeder FeederInfo: long integer Feeder Manager-assigned phase information describing 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 kV Grounded Y, 2400 Delta, 14.4 kV etc. OperatingVoltage: long integer Code indicating standard level at which system is currently being operated; may vary above or below nominal voltage; domain values 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. Subtype: long integer Code indicating subtype SymbolRotation: double Angle of rotation dictating how a feature appears on the map WorkOrderID: text Identifier of work order of ElectricDevice Note: Note: The Nominal Voltage attribute does not apply to the following subclasses of ElectricDevice: OpenPoint and MiscNetworkFeature. The PhaseDesignation attribute does not apply to the subclasses Ground or FaultLimiter.
9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321
ElectricDevice
Comments ElectricTraceWeight FacilityID FeederID FeederID2 FeederInfo InstallationDate NominalVoltage OperatingVoltage PhaseDesignation Subtype SymbolRotation WorkOrderID
Associations: FacilityStructure, UndergroundStructure [does not apply to OpenPoint]
Table of Contents
MiscNetworkFeature MiscNetworkFeature captures those subtypes that protect distribution network equipment from temporary and permanent faults. FaultIndicator Fault indicators locate faulted sections of overhead distribution systems and present a visual signal to designate normal and faulted conditions. ActuatingCurrent: long integer Current that will trip indicator; settings are high and low MaxConductorSize: text Maximum size conductor that indicator can protect FaultLimiter FaultLimiter is used to increase the impedance of the system during fault conditions. 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 Ground A common point for connecting grounded conducting equipment such as shunt capacitors. Grounding is achieved by connecting one side or neutral of a circuit to the earth through low resistance or low impedance paths, to help prevent transmitting shocks to personnel. Ground equipment normally includes ground circuits and a driven rod or buried ground field that provides a path for electric return circuits. Types of ground devices include grids, mats, and multiple or single driven 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 SurgeArrestor Surge arrestors are controlled, enclosed spark-gap structures designed to allow impulse current to flow through the gaps to the ground. The arrestor rating is the maximum root mean square (rms) voltage for which it is designed to reseal. The rms power frequency is the voltage from line-to-line versus the voltage from lineto-neutral. The arrestor discharge voltage is well below the BIL of the protected equipment. ArrestorType: text Code indicating type of arrestor; domain values include Air Gap, Metal Oxide, etc BILRating: long integer BIL rating of protected equipment
09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 1 09876543210987654321 0987654321098765432
ElectricDevice MiscNetworkFeature
ActuatingCurrent MaxConductorSize GroundType Reactance Resistance GroundSize Material Resistance RodSize Thickness ArrestorType BILRating Class
Subtypes include Fault Indicator, Fault Limiter, Counter Poise Ground, Rod Ground, Wrap Ground and Surge Arrestor
Table of Contents
Chapter 6 Devices Component Reference 73
Class: text Code indicating class of arrestor; domain values include Distribution, Elbow, Intermediate, Substation Open Point OpenPoint contains information about a variety of insulated and shielded devices that connect high-voltage cables to apparatus, including transformers. Separable, load-break insulated connectors are used with primary bushings of submersible distribution transformers for safety. This is known as a dead-front configuration. OpenPoint defines the following attributes: Configuration: text Configuration of connection such as Wye, Delta, etc. Manufacturer: text Manufacturer of connector Model: text Model NormalPosition [A,B,C]: long integer Code indicating normal position of OpenPoint, per phase; domain values include Closed, Open, Not Applicable PresentPosition[A,B,C]: long integer Code indicating present position of OpenPoint, per phase; domain values include Closed, Open, Not Applicable SpliceSize: text Code indicating size of Splice; domain values include 1/0 AWG, 1000 MCM, etc. TransformerObjectID: long integer ObjectID of associated transformer unit Note: The NominalVoltage property does not apply to OpenPoint. Subtypes: Load Break Elbow, Non-Load Break Elbow, Open Point, Solid Connection, and Splice
432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321 432121098765432109876543210987654321
ElectricDevice TransformerBank OpenPoint
GroundReactance GroundResistance HighSideConfiguration HighSideGroundReactance HighSideGroundResistance HighSideProtection LabelText LocationType MagnetizingReactance MagnetizingResistance RatedKVA Configuration Manufacturer Model NormalPosition[A,B,C] PresentPosition[A,B,C] SpliceSize TransformerObjectID
Table of Contents
APPLICATION COCLASS
ElectricDevice
Overcurrent Protective Device Generally, overcurrent protective devices open (trip) when the maximum rated current is exceeded for a preset amount of time. Overcurrent protective devices are arranged in series along a distribution circuit to clear temporary faults in a prearranged sequence of operation. The most common devices used for overcurrent protection are fuse cutouts, automatic circuit reclosers, sectionalizers and relayed circuit breakers. The rated continuous current is the current a device carries continuously without exceeding specified temperatures in a specified ambient temperature. The OverCurrentProtectiveDevice is an abstract feature class that contains common characteristics 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 current rating of device in amps, which is the amount of current that can flow through the device indefinitely; domain values include 100 A, 200 A, etc. MaxInterruptingCurrent: double Code indicating maximum current for which device interrupts current; domain values include 2.5 kA, 6 kA, 8 kA, etc. MaxOperatingVoltage: long integer Code indicating maximum designated rms value of power frequency voltage that may be applied continuously between the 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 of device, per phase; domain values include Closed, Open, Not Applicable PresentPosition[A,B,C]: long integer Code indicating present position of device, per phase; domain values include Closed, Open, Not Applicable Dynamic Protective Device In addition to opening when a fault is detected, dynamic protective devices also reclose to attempt to re-establish service. If the fault remains after a prescribed number of reclosings, the device may lock open the circuit. Reclosing is designed to reduce or eliminate the effects of temporary faults. Protective devices have a Basic Insulation Level (BIL) rating which is a reference insulation level expressed as the impulse crest voltage of the nominal 1.2 X 50 microsecond wave. This is a measure 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 of DynamicProtectiveDevice; domain values include 95 BIL, 150 BIL, etc.
09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321
LabelText MaxContinuousCurrent MaxInterruptingCurrent MaxOperatingVoltage NormalPosition[A,B,C] PresentPosition[A,B,C]
DynamicProtectiveDevice
BypassSwitch ClosingResistor Manufacturer Model SerialNumber GangOperated Manufacturer Model SerialNumber ShuntMechanism TripCount BypassSwtich MountingType TieSwitchIndicator BILRating GroundResistance InterruptingMechanism InterruptingMedium SCADAControlID SCADAMonitorID
Subtypes include Circuit Breaker, Fault Interrupter, Single Phase Hydraulic Recloser, Two Phase Hydraulic Recloser, Three Phase Hydraulic Recloser, Three Phase Electronic Recloser, Three Phase Relay Recloser, and Single hase Hydraulic Sectionalizer, Two Phase Hydraulic Sectionalizer, Three Phase Hydraulic Sectionalizer, and Three Phase Electronic Sectionalizer
Table of Contents
Chapter 6 Devices Data Model Reference 75
GroundResistance: double Describes ground resistance of DynamicProtectiveDevice, in ohms InterruptingMechanism: text Type of interrupting mechanism that operates the contacts of DynamicProtectiveDevice InterruptingMedium: text Code indicating interrupting medium that insulates contacts 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 Breaker Circuit breakers detect excessive power demands in a circuit and self-interrupt when they occur. Mechanical switching devices equipped with a trip coil connected to a relay are designed to open under fault conditions. The contacts of the circuit breaker open and close by mechanical linkages manufactured from insulating materials and using energy from compressed air, electric magnets, or charged springs. An arc appears for a limited time during the interrupting process. Breakers switch circuits and equipment in and out of the system within two to five cycles of a fault measured from trip coil energizing to extinguishing the arc. An accepted 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 acceptable limits. CircuitBreaker inherits the attributes of the abstract classes ElectricDevice, OverCurrentProtectiveDevice, and DynamicProtectiveDevice. CircuitBreaker defines the following attributes: BypassSwitch: text Code indicating presence of bypass switch on CircuitBreaker; domain values are Yes or No ClosingResistor: text Code indicating presence of ClosingResistor; domain values are Yes or No Manufacturer: text Code indicating manufacturer of CircuitBreaker; domain values include ABB/Westinghouse, General Electric, etc. Model: text Model SerialNumber: text Serial number Associations: CircuitSource, RelayControl Recloser Reclosers are type of oil switch that use controls to sense a fault and de-energize the 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 attempts to close. Minimum trip current is usually twice the normal load current rating of the coil.
Table of Contents
Automatic reclosing devices can reduce the number of total network outages by 75% to 90%. The amount of current that flows at the installation point under full load conditions should not exceed what the manufacturer has rated the recloser to carry continuously. Recloser inherits the attributes of the abstract classes ElectricDevice, OverCurrentProtectiveDevice, and DynamicProtectiveDevice. Recloser defines the following attributes: BypassSwitch: text Code indicating presence of BypassSwitch on Recloser; domain values are Yes or No MountingType: text Code indicating mounting type of Recloser; domain values include Pad Mounted, Pole Mounted, Substation Frame TieSwitchIndicator: text Code indicating presence of tie switch; domain values are Yes or No Associations: CircuitSource, RecloserControl, RecloserUnit, RelayControl Subtypes: Single Phase Hydraulic, Two Phase Hydraulic, Three Phase Hydraulic, Three Phase Electronic, Three Phase Relay Sectionalizer Sectionalizers are automatic circuit opening devices that are installed on the load side of fault-interrupting devices and count its fault-trip operations. Sectionalizers can be set to open after one, two, or three counts have been detected with a predetermined time span. Sectionalizers are used in conjunction with fuses and reclosers and may have inrush current restraint features to prevent a 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 Hydraulic, Three Phase Electronic Fault Interrupter Fault interrupters can replace circuit breakers to protect transformers in substation or networks. Often used for high-side transformer protection, fault interrupters open (trip) at a preset current and programmed time delay to minimize fault damage downstream. Fault interrupters employ current transformers (CTs) to provide line current level information to electronic trip control. One set of CTs 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 dont reclose automatically: contacts are closed 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 values include Bridges, Siemens, etc. Model: text Model of device Chapter 6 Devices Component Reference 77
Table of Contents
SerialNumber: text Device manufacturers serial number ShuntMechanism: text Shunt mechanism that trips device TripCount: long integer Number of trips before device opens the circuit Fuse Fuses are used to protect distribution devices from damaging currents. A fuse is an intentionally weakened spot in the electric circuit that opens the circuit at a predetermined current that is maintained for a predetermined amount of time. Fuses are not dynamic in that they remain open and do not reclose. By automatically interrupting the flow of electricity, a fuse prevents or limits damage caused by an overload or short circuit. Fuses are coordinated with reclosers to prevent fuses being damaged by temporary faults downstream. Time current characteristic (TCC) curves are used to rate fuses: the upper curve represents the total clearing time and the lower curve represents the melting time. Coordination involves calculating the intersection of fuse curves with recloser curves to achieve desired results. Fuse types include current limiting and expulsion fuses. At maximum interrupting current, the arc of limiting fuses actually melts sand to build up apparent resistance to reduce the fault current. Expulsion fuses create an arc during fault conditions which generates a gas that extinguishes fault current. Association: FuseUnit Subtypes: Current Limiting, Overhead Expulsion, Underground Expulsion, Vacuum Power Factor Correcting Equipment Power distribution is more efficient if operated when the power factor (PF) is unity. An alternating voltage and the current causing it to flow should rise and fall in value equally and reverse direction at the same instant. When this happens, the two 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 of leading reactive current and can be installed close to the load. This reduces the lagging current. The power factor is the ratio of actual power to the product of volts times amperes. Capacitors operate on 60-Hz sine-wave power lines at the voltage 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
9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321
ElectricDevice Overcurrent ProtectiveDevice Fuse
9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 1 9876543210987654321 987654321098765432
ElectricDevice PowerFactor CorrectingEquipment
ConnectionConfiguration GroundReactance GroundResistance LocationType SwitchType MaxFaultCurrent SwitchType PositiveSequenceReactance PositiveSequenceResistance ZeroSequenceReactance ZeroSequenceResistance FillType Material LabelText TotalKVAR
Table of Contents
EXTENDING ARCGIS APPLICATIONS
Capacitor Bank Capacitors store electrical energy and release it back into the power system when required to reduce voltage drops. CapacitorBank represents a feature that neutralizes the effect of customer inductive loads, providing capacitive reactance to balance inductive reactance loss. One bank is associated with each phase; a threephase circuit has three capacitor banks. Banks are fixed or switched: permanently connected or automatically switched to supplement voltage rise during heavyload conditions. Delta and single phase connections are usually made on low voltage 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, in ohms GroundResistance: long integer Ground resistance (Rg) of CapacitorBank, in ohms LocationType: text Code indicating type of location; domain values include Delivery 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 Capacitor Capacitor units are placed in series to connect to higher voltage and transmission systems. 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 reactance seen by the downstream circuit, in ohms PositiveSequenceResistance: double Equivalent positive sequence resistance seen by the downstream circuit, in ohms ZeroSequenceReactance: double Equivalent zero sequence reactance seen by the downstream circuit, in ohms ZeroSequenceResistance: double Equivalent zero sequence resistance seen by the downstream circuit, in ohms Associations: CapacitorControl
Table of Contents
Shunt Reactor Shunt reactors reduce the inrush of fault current by introducing inductive reactance into a circuit to balance the effects of motor starting, to operate transformers in parallel, and to control current. Inrush current is the initial momentary surge current demand before a load resistance of impedance increases to its normal operating value. The normal use for shunt reactors is to compensate for capacitive currents from transmission lines, cable, or shunt capacitors. The need for shunt reactors is most apparent at light load. Switched shunt capacitors are used in distribution substations or out on primary feeders to achieve full-load power factor more economically. 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 Light Street lighting is supplied by local distribution systems at 120/240 V and is generally the only service for which the electric utility installs, operates and maintains utilization equipment. The lights that illuminate roads and highways generally use high-intensity discharge lamps with ballasts compatible with common voltages and may be either high- or normal-power factor. High-intensity discharge lamps are usually phosphor-coated mercury, metal halide, or highpressure sodium. Lamps are available in several sizes range from 100 to1000 watts (W) and may be sealed or filtered for longer life. Photoelectric controls are usually used with individual lights. Most utility lighting systems have been mounted on existing overhead support structures; however, for underground systems lighting can be designed with supply run from the nearest transformer or handhole. StreetLight illuminates a street area and defines the following attributes: BallastType: text Code indicating type of ballast used in StreetLight ; domain values include high-power factor and normal-power factor FixtureSupport: text Code indicating type of support used for streetlight fixtures; domain values include Cobra, Security, Other
876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 1 876543210987654321 87654321098765432
ElectricDevice StreetLight
BallastType FixtureSupport LampType LensType LightCount LightStyle MountHeight Ownership PhotocellType Shielding StreetLightRole TimeControl Wattage
Table of Contents
LampType: text Code indicating type of lamp; domain values include fluorescent, high/low pressure sodium, incandescent, mercury vapor, and metal halide LensType: text Code indicating type of lens; domain values include diffuser, reflector, or refractor LightCount: long integer Code indicating number of lights; domain values include 1, 2, 3, 4 LightStyle: text Code indicating style of StreetLight ; domain values include Ornamental Light, Standard MountHeight: short integer Height of light on pole Ownership: text Code indicating owner of light; domain values include Customer, Utility, Other PhotocellType: text Type of photocell Shielding: text Code indicating presence of shielding; domain values are Yes or No StreetLightRole: text Code indicating role of StreetLight; domain values include 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 include 100 Watts, 175 Watts, etc Association: SupportStructure Switch Switches are used to disconnect circuits. Switches are installed at strategic locations throughout distribution feeder circuits to redirect power flows to balance loads 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 from two directions at once. Switches can be manually or power operated, and can be operated individually or as a group. Switches are rated by continuous current and maximum operating voltage. Continuous current is the manufacturer-designated limit in rms amperes that the device can carry continuously without observable rise in temperature. Maximum operating voltage is the maximum designated rms value of power frequency voltage that may be applied continuously between the terminals of the switch. Automated switches may have pole-mounted control cabinet housing switch controller, battery and local control switches. They may also provide the RTU and 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
Table of Contents
9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321
ElectricDevice Switch
GangOperated LabelText ManuallyOperated MaxContinuousCurrent MaxOperatingVoltage NormalPosition[A,B,C] PreferredCircuitSource PresentPosition[A,B,C] SCADAControlID SCADAMonitorID TieSwitchIndicator
Manually Operated: text Code indicating whether switch is manually operated; domain values are Yes or No MaxContinuousCurrent: double Code indicating maximum continuous current rating of Switch in amps; domain values include 100 Amps, 200 Amps, 600 Amps, etc. MaxOperatingVoltage: long integer Code indicating maximum operating voltage 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 of Switch, 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 of Switch, 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 Disconnect, Underground Load Break TransformerBank Transformers transfer electrical energy from one circuit to another circuit usually with 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. The ratio of transformation is changed by increasing or decreasing the number of active turns in one winding with respect to another winding. Positions are always numbered sequentially starting with 1 at the lowest tap position and progressing through the highest tap position. Banked transformers are tied together through secondary mains and are supplied by the same primary feeder. Banked transformations can reduce lamp flicker caused by starting motors, decrease capacity required, produce better average voltage along the secondary, and have greater flexibility for load growth. Transformer kVA (kilovolt-amperes) describes its ability to support a load at a given voltage. Rated kVA of transformer banks is the sum of the rated kVA of its related units. TransformerBank defines the following attributes: GroundReactance: long integer Neutral-to-ground reactance of ground of Transformer GroundResistance: long integer Neutral-to-ground resistance of ground of Transformer
09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321
ElectricDevice TransformerBank
GroundReactance GroundResistance HighSideConfiguration HighSideGroundReactance HighSideGroundResistance HighSideProtection LabelText LocationType MagneticReactance MagneticResistance RatedKVA
Table of Contents
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, in ohms HighSideGroundResistance: long integer Ground resistance of primary side, in ohms HighSideProtection: text Code indicating type of overcurrent protection used at 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 Delivery 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 Transformer The Transformer feature class captures information about distribution and power transformers. Subtypes include Network, Single Phase Overhead, Single Phase Underground, Two Phase Overhead, Three Phase Overhead, Three Phase Underground, Step, and Power. Characteristics of transformers include voltage rating (kV), power rating (MVA), impedence (%), loss evaluation, temperature rating (degrees Celsius), and cooling class. Distribution transformers convert electrical energy from primary voltages to utilization voltages. Primary voltages range from 34.5/19920 Grounded Y to 4160Y/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, Two Phase Overhead, Three Phase Overhead, Three Phase Underground, Step and Power Voltage Regulator Because voltage is different at any point on a feeder, voltage regulators provide voltage control where feeders of different lengths and diverse load conditions are supplied from the same substation bus. Feeder voltage regulators can be single or three-phase and operate from 25 to 400 kVA. The 32-step design regulates line load from 10 percent above (boost) to 10 percent below (buck) normal line voltage. Operating over a 20 percent range, the voltage change per step is 5/8 percent. Chapter 6 Devices Data Model Reference 83
9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 1 9876543210987654321 987654321098765432
ElectricDevice TransformerBank Transformer
LoadTapChangerIndicator RatedKVA65Rise RatedTertiaryKVA TertiaryConfiguration TertiaryVoltage LowSideConfiguration LowSideGroundReactance LowSideGroundResistance LowSideProtection LowSideVoltage SwitchType
Table of Contents
9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321
ElectricDevice TransformerBank VoltageRegulator
BoostPercent BuckPercent BypassSwitch
Voltage regulators vary the ac supply or source voltage to the customer to maintain the voltage within desired limits. Voltage provided by regulators is changed using a tap-changing switch to adjust the number of secondary windings. Bypass switches allow a regulator to be removed for normal service without interrupting the downstream load. VoltageRegulator inherits attributes of TransformerBank and ElectricDevice and defines the following attributes: BoostPercent: text Code indicating tap setting for increase in capacity achieved by raising the maximum voltage level; domain values include 4 Percent, 6 Percent, etc. BuckPercent: text Code indicating tap setting for increase in capacity achieved by lowering the minimum voltage level; domain values include 4 Percent, 6 Percent, etc. BypassSwitch: text Code indicating presence of BypassSwitch used to de-energize VoltageRegulator; domain values are Yes or No Subtypes: Single Phase Overhead, Two Phase Overhead, Three Phase Overhead, Three Phase Pad-Mounted
DEVICE CONTROL
Electric devices can be controlled manually, hydraulically, and electronically as well as remotely. Control features capture information that defines trip current, trip operation, trip interval, overcurrent duration, reclosing operation, and lock out operation of devices that are used to complete, maintain, or interrupt circuits under normal and fault conditions. Network Protector Network transformers connect to the secondary network through a network protector. NetworkProtector components may be the circuit breaker, relays, backup fuses and controls required for automatically disconnecting a transformer from the secondary network in response to predetermined conditions on primary feeder 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. Model: text Model ProtectorType: text Code indicating network protector type; domain values include Oil Breaker, Vacuum Breaker, Other SecondaryVoltage: long integer Code indicating voltage at secondary side of NetworkProtector; domain values include 120 Volts, 120/208 Volts, etc. SerialNumber: text Serial number
Table of Contents
09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321 09876543210987654321098765432121098765432109876543210987654321
Object
NetworkProtector RecloserControl Sectionalizer Control RelayControl
ElectricDeviceObjectID Manufacturer Model ProtectorType SecondaryVoltage SerialNumber SubmersIndicator Subtype ElectricDeviceObjectID ElectricDeviceObjectID LockoutTripCount VoltageRestraint CTRatio CurveID DynamicProtectiveDevObjectID InstantTripTapSetting Manufacturer Model TapSetting TimeLeverSetting
SubmersIndicator: text Code indicating whether Network Protector is connected to submersible (subsurface) distribution transformer; domain values include Yes or No Subtype: long integer Code indicating subtype Association: Transformer (only valid for subtype Network) Relay Control Protective relay systems detect and isolate faults. Time-delayed phase and ground relays are coordinated with fuses and reclosers further out on the circuit. They are instantaneous units with inverse TCCs to coordinate with fuses and reclosers further downstream. Relays are usually set to trip feeder breakers and protect the fuse in the event of temporary faults beyond the fuse. Current transformers (CTs) measure large currents as well as insulate relays from high voltage circuits. The primary 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 in twos ; relay A responds to faults to its right and relay B responds to faults to its left. Both will respond simultaneously only if the fault is on the line they are both protecting. A communication channel informs A about the state of B and another informs B about the state of A. Phase comparison relaying uses a communication channel to compare information about the phase currents based on the fact that external faults are essentially equal in magnitude and opposite in direction while internal faults are in phase.
Table of Contents
DEVICE CONTROL
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 dynamic protective device InstantTripTapSetting: long integer Value in amps of CT secondary current that will trip relay immediately Manufacturer: text Code indicating manufacturer of RelayControl; domain values include ABB/Westinghouse, General Electric, etc. Model: text Model 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 and Recloser subtypes] Recloser Control RecloserControl defines the following attribute: ElectricDeviceObjectID: Object ID of associated electric device Association: DynamicProtectiveDevice [only valid for Recloser subtypes] Recloser Electronic Control Reclosers and sectionalizers isolate temporary and permanent faults in electric lines. Reclosers open circuits (trip) in case of a fault, and reclose after a predetermined time. The time-current characteristic, usually expressed in a curve, is based on temperature and fuse tolerances and is used to coordinate recloser operations. Reclosers allow (usually) four trip operations to clear temporary faults. The first two trips generally occur at approximately 2 Hertz (Hz) (slow curve, TCC1) and the last two occur at 5 Hz (fast curve, TCC2). If the fault continues, the recloser locks out the circuit. The minimum trip current is set through a range of settings based 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 current setting, in amps HighCurrentActiveTripNumber [Phase, Ground]: long integer Identifier of TCC HighCurrentLockoutActive [Phase, Ground]: long integer Indicates whether high current lockout active indicator is on or off HighCurrentLockoutMultiplier [Phase, Ground]: long integer If high current lockout indicator is on, multiplier can be applied to increase current at which Recloser locks out HighCurrentLockoutStatus [Phase, Ground]: long integer Indicates whether high current lockout status indicator is on or off 86 ArcGIS Electric Distribution Model
Table of Contents
765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321 765432109876543210987654321
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] Manufacturer MinimumTripCurrent[Phase,Ground] Model OperatingTime RecloseTime[1,2,3] ResetTime SerialNumber TCCGroup[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]
HighCurrentTripStatus [Phase, Ground]: long integer Indicates whether high current trip indicator is on or off HighCurrentTripMultiplier [Phase, Ground]: long integer If high current indicator is on, multiplier can be applied to increase trip current setting HighCurrentTripTimeDelay [Phase, Ground]: long integer Increases time for current to trip Recloser Lockout[Phase, Ground]: long integer Total number of trips for Recloser to remain open (lock out) Manufacturer: text Code indicating manufacturer of Recloser; domain values include ABB/Westinghouse, General Electric, etc. MinimumTripCurrent [Phase, Ground]: long integer Value at which overcurrent is detected, in amps Model: text Code indicating model; domain values include ESStatic Control, MEForm3A, etc. OperatingTime: long integer Operating time of Recloser RecloseTime[1,2,3]: long integer Interval in seconds between first, second, and third trip operation ResetTime: long integer Time in seconds between trip operation and resetting to beginning of trip sequence SerialNumber: Serial number TCCGroup[Phase, Ground]: long integer Manufacturer group number assigned to specific curves used for setting Recloser parameters TCC1ConstantTimeAdder [Phase, Ground]: long integer Time adjustment assigned to specific curve for slow trips TCC1MinResponseTime [Phase, Ground]: long integer Minimum response time of slow trip TCC1Multiplier[Phase, Ground]: long integer Current adjustment multiplier applied to minimum trip current for slow trip TCC1Operations[Phase, Ground]: long integer Number of trips per curve for slow trip
TCC1Selection[Phase, Ground]: long integer Specific curve selected for slow trip TCC2ConstantTimeAdder [Phase, Ground]: long integer Time adjustment assigned to specific curve for fast trips TCC2MinResponseTime[Phase, Ground]: long integer Minimum response time of fast trip TCC2Multiplier[Phase, Ground]: long integer Current adjustment multiplier applied to minimum trip current for fast trip Chapter 6 Devices Data Model Reference 87
Table of Contents
TCC2Operations[Phase, Ground]: long integer Number of trips per curve for fast trip TCC2Selection[Phase, Ground]: long integer Specific curve selected for fast trip Recloser Hydraulic Control Hydraulic control is an intregral part of single-phase reclosers. A trip coil in series with the line is used to sense overcurrent and trip open the recloser contacts. The contacts close after a preset interval. RecloserHydraulicControl defines the following attributes: CoilSize: short integer Code indicating size of trip coil, in amps; domain values include 25 Amps, 50 Amps, etc. RecloseInterval: long integer Amount of time before reclosing between operations ResetTime: long integer Amount of time Recloser resets to beginning of operation 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 Control Sectionalizer controls store a pulse counter when the minimum actuating current drops to zero because a fault is interrupted by the recloser (or other protective device). Sectionalizers operate in conjunction with breakers and reclosers to lock out fault current after a predetermined number (usually three) of recloser operations (trips). In general, the number of counts to open can be one, two or three counts. Three-phase sectionalizers have three current transformers sensing phase currents and three CTs connected in parallel to ground to sense the zero-sequence current. A count is registered when a current above the preset minimum actuating level reaches the device and then drops to zero (as when interrupted by the backup protective device). After one, two, or three counts, the mechanism that opens the contacts is actuated. The number of counts to open the sectionalizer should 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 sectionalizer locks out VoltageRestraint: double Code indicating presence of VoltageRestraint; values are Yes or No Association: Sectionalizer
Table of Contents
Sectionalizer Hydraulic Control SectionalizerHydraulicControl defines the following attributes: CoilSize: short integer Code indicating size of trip coil, in amps; domain values include 25 Amps, 50 Amps, etc. Sectionalizer Electronic Control Count restraint features prevent sectionalizers from generating a count pulse as long as some current is present. This prevents operation when a load side device interrupts the circuit. If a fault current is interrupted by the downline device, the count restraint feature blocks the generation of a count if at least 5 amps of uninterrupted load current flows through the sectionalizer. Inrush current is the initial momentary surge current demand before a load resistance of impedance increases to its normal operating value. If the sectionalizer detects overcurrent when the backup device opens, the overcurrent present at reclosing is assumed to be fault current. If no overcurrent is detected when the current is interrupted, the overcurrent at reclosing is assumed to be inrush current. The phase and ground actuating levels are blocked for three seconds Object after reclosing to allow the initial surge to subside. The sectionalizer then resets to normal. SectionalizerElectronicControl defines the following attributes: CountRestraint: long integer Indicates presence of count restraint feature; values are Yes and No CurrentInrushRestraintMultiplier: long integer Defines multiplier increasing actuating level to account for inrush current GroundFaultSensingMultiplier: long integer Defines multiplier setting for zerosequence fault current TripCurrent: long integer Minimum current required to open sectionalizer
5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321
SectionalizerControl Sectionalizer HydraulicControl Sectionalizer ElectronicControl
CoilSize CountRestraint CurrentInrushRestraintMultiplier GroundFaultSensingMultiplier TripCurrent
Table of Contents
Object
Device Object DeviceObject is an abstract class containing common attributes of the devices that control the flow of current in circuits. Device control objects capture characteristic strategies used by regulators and capacitors to provide voltage at a range that allows customers equipment to operate properly. DeviceObject defines the following attributes: ElectricDeviceObjectID: Object ID of electric device InstallationDate: date Date device was installed Model: text Model SerialNumber: text Serial number Subtype: long integer Code indicating subtype of device WorkOrderID: text Work order identifier Capacitor Control Capacitors maintain or increase the voltage of distribution conductors and reduce voltage drops in the system. Subtypes include CurrentLevel, KVARLevel, TempLevel, Time, and VoltageLevel. CapacitorControl defines the following attributes: DeactivateSaturday: text Code indicating whether capacitor control deactivates on Saturday, values are Yes or No DeactivateSunday: text Code indicating whether capacitor control deactivates 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; domain values 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
6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321
RecloserControl Recloser HydraulicControl
CoilSize RecloseInterval ResetTime TCC1Operations TCC2Operations TCC1Selection TCC2Selection
6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 1 6543210987654321 654321098765432
Object
SectionalizerControl
ElectricDeviceObjectID LockoutTripCount VoltageRestraint
Table of Contents
21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321 21098765432121098765432109876543210987654321
ElectricDeviceObjectID InstallationDate Model SerialNumber Subtype WorkOrderID
DeviceObject
Object
LoadTapChanger defines the following attributes:
Load Tap Changer LoadTapChanger represents power transformer controls that change the primaryto-secondary turns ratio of a transformer winding while the transformer is under load to regulate the flow of current and minimize voltage drop. Automatic loadtap changers in the power transformer provides voltage control on the substation bus. Control systems of voltage regulators and tap changing equipment beyond the substation usually have a line-drop compensator to simulate voltage drop between the substation and points in the distribution system.
BandWidth CTPrimary 1stHouseHighProtection[A,B,C] 1stHouseLowProtection[A,B,C] PTRatio RSetting[A,B,C] StepSize TapSetting[A,B,C] VoltageSetting[A,B,C] XSetting[A,B,C]
BoostPercent BuckPercent Impedance RatedKVA RelayControlType SwitchType XRRatio
DeactivateSaturday DeactivateSunday OnSetting OffSetting Phase SCADAControlID SCADAMonitorID
LoadTapChanger
CapacitorControl
Table of Contents
RegulatorControl
Chapter 6 Devices Data Model Reference 91 Association: PowerTransformer XRRatio: long integer Inductance/resistance ratio SwitchType: text Type of switch used RelayControlType: text Type of relay control RatedkVA: long integer System rating, in kVA Impedence: text Impedence of LoadTapChanger, in ohms BuckPercent: text Code indicating tap setting for increase in capacity achieved by lowering the maximum voltage level; domain values include 4 Percent, 6 Percent, etc. BoostPercent: text Code indicating tap setting for increase in capacity achieved by increasing the maximum voltage level; domain values include 4 Percent, 6 Percent, etc.
Regulator Control Voltage provided by regulators is changed using a tap-changing switch to adjust the number of secondary windings. Line load can be regulated from 10 percent above to 10 percent below normal line voltage. Voltage regulators that control distribution system voltage are rated from 2.5 kV to 34.5 grd Y kV. Most feeder regulators have the 32-step design. Voltage is measured by current transformers and potential transformers (PT) to provide control of system voltage level and bandwidth. The PT steps down the regulator (local) voltage and provides it to the control system which compares voltage with the desired preset level. If the actual voltage deviates from preset voltage by plus or minus the bandwidth, the tap changing mechanism operates to bring voltage within the preset bandwidth. Minimum bandwidth is twice the size of the voltage step (2 times 5/8 percent or 1.25 percent). The line-drop compensator simulates system impedance by adjusting resistance and reactance. The CT circulates current proportional to the load current through the resistance and reactance components and combines this voltage signal with the local voltage signal. This allows the regulator to maintain a higher voltage during heavy loads. RegulatorControl defines the following attributes: Bandwidth: text Preset bandwidth of voltage regulator CTPrimary: long integer Current transformer (CT) rating of primary side of regulator 1stHouseHighProtection[A,B,C]: long integer Fuse type on primary side 1stHouseLowProtection[A,B,C]: long integer Fuse type on secondary side of regulator PTRatio: long integer Potential transformer (PT) ratio used to sense source voltage RSetting[A,B,C]: long integer Setting of resistive component of line-drop compensation system, per phase StepSize: long integer Size of steps that voltage regulator has available 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 of line-drop compensation system, per phase Association: TransformerUnit
09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321 09876543210987654321
Object
DeviceObject RegulatorControl
BandWidth CTPrimary 1stHouseHighProtection[A,B,C] 1stHouseLowProtection[A,B,C] PTRatio RSetting[A,B,C] StepSize TapSetting[A,B,C] VoltageSetting[A,B,C] XSetting[A,B,C]
Table of Contents
6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321
Object
DeviceObject UnitObject
PhaseDesignation UnitID
Unit Object UnitObject is an abstract class containing common attributes of individual devices: capacitors, fuses, reclosers, sectionalizers, switches, and transformers. UnitObject defines the following attributes: PhaseDesignation: long integer Code indicating phases present; domain values include A, AB, AC, etc. UnitID: text Identifier of related device unit Capacitor Unit Capacitors store electrical energy and release it back into the power system when required to reduce voltage drops. CapacitorUnit defines the following attributes: FluidType: text Code indicating type of dielectric fluid (some contain polychlorinated biphenyls - PCBs) used in CapacitorUnit; domain values include Arachlor, Diachlor, Faradol, etc. kVAR: long integer Code indicating CapacitorUnit size in kVAR; domain values include 100 kVAR, 150 kVAR, etc Manufacturer: text Code indicating manufacturer of CapacitorUnit Association: CapacitorBank Fuse Unit A fuse is an intentionally weakened spot in the electric circuit that opens the circuit at a predetermined current that is maintained for a predetermined amount of time. Fuses are classified into three categories: low voltage (up through 600 V), medium voltage (operating theough 69kV) and high voltage (through 500 kV). FuseUnit defines the following attributes: HousingType: text Code indicating type of FuseUnit housing; domain values include Door Cutout, MX Cutout, Open Link HousingRatio: long integer Code indicating capacity of FuseUnit housing, in amps; 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 values include 1 A, 10 A, 100 A, etc Manufacturer: text Code indicating manufacturer Association: Fuse
CapacitorUnit
FluidType KVAR Manufacturer
543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321
Object
DeviceObject UnitObject FuseUnit
HousingType HousingRating LinkType LinkRating Manufacturer
Table of Contents
DeviceObject
BILRating: long integer Code indicating rating of SwitchUnit BIL; domain values include 95 BIL, 125 BIL, etc. ContactType: text Code indicating type of contact of SwitchUnit; domain values include Posi-Lock, Standard GroundResistance: long integer Resistance of ground of SwitchUnit, in ohms InterruptingMechanismType: text Interrupting mechanism of SwitchUnit InterruptingMedium: text Code indicating interrupting medium of Switch; domain values include Air, Oil, SF6, Vacuum, etc. Manufacturer: text Code indicating manufacturer
UnitObject
SectionalizerUnit
Manufacturer
Table of Contents
43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321 43210987654321
6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321 6543210987654321
Object
DeviceObject UnitObject RecloserUnit
Manufacturer ReversePowerAccessory
Recloser Unit Reclosers trip open a circuit for a short time to clear temporary fault and reclose after a predetermined time. The time-current characteristic, usually expressed in a curve, is based on temperature and fuse tolerances and is used to coordinate recloser operations. RecloserUnit defines the following attributes: Manufacturer: text Code indicating manufacturer ReversePowerAccessory: text Code indicating whether recloser has Reverse Power Accessory; values are Yes or No Associations: Recloser Sectionalizer Unit Sectionalizers operate in conjunction with breakers and reclosers to lock out fault current after a predetermined number (usually three) of recloser operations (trips). SectionalizerUnit defines the following attributes: Manufacturer: text Code indicating manufacturer Associations: Sectionalizer Switch Unit Switches are used to disconnect circuits for line sectionalizing, isolating equipment and feeder realignment on distribution circuits. SwitchUnit defines the following attributes:
543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321 543210987654321
Object
Object
DeviceObject
UnitObject
SwitchUnit
BILRating ContactType GroundResistance InterruptingMechanism InterruptingMedium Manufacturer MaxInterruptingCurrent
MaxInterruptingCurrent: double Code indicating maximum current in amps that opens SwitchUnit; domain values include 50 Amps, 60 Amps, 200 Amps, etc.
876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321
Object
DeviceObject UnitObject TransformerUnit
AnimalGuardType ArrestorType Available CoolingType FluidType FullLoadLosses HighSideRatedVoltage HighSideBIL Impedance LowSideRatedVoltage LowSideBIL LowSideTaps Manufacturer MaxSteps NoLoadLosses PCBLevel ProtectionType RatedKVA TapsType TransformerObjectID XRRatio
Association: Switch Transformer Unit Transformers transfer electrical energy from one circuit to another circuit usually with 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 Air Gap, Metal Oxide, etc. Available: text Code indicating whether TransformerUnit has capacity available; 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 which high side of TransformerUnit is rated; domain values include 2400 Volts Delta, 4160/2400 Volts, etc. HighSideBIL: long integer Code indicating BIL rating of high side of TransformerUnit; example includes 125 BIL, etc. Impedance: double Impedance of TransformerUnit, expressed as percentage LowSideRatedVoltage: long integer Code indicating system voltage of low side of 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 of TransformerUnit to change transformer ratio Manufacturer: text Manufacturer of TransformerUnit; domain values include 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, domain values include Arachlor, Diachlor, etc. ProtectionType: text Code indicating type of protection; domain values include Bayonet Fused, Conventional, etc. RatedKVA: long integer kVA at nominal voltage; domain values include 10 kVA, 112 kVA, 333 kVA, etc. TapsType: text Code indicating type of taps; domain values include 2Above/2Below, 4Above. etc.
Table of Contents
TransformerObjectID: long integer ObjectID of associated transformer VoltageRegulatorObjectID: long integer ObjectID of associated voltage regulator XRRatio: double Inductance/resistance ratio Associations: RegulatorControl [only valid for VoltageRegulator], Transformer Subtypes: Distribution Transformer Unit, Power Transformer Unit, Voltage Regulator Unit VoltageRegulatorUnit Voltage regulators provide voltage control where feeders of different lengths and diverse 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 Air Gap, Metal Oxide, etc. Available: text Code indicating whether TransformerUnit has capacity available; 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 which high side of TransformerUnit is rated; domain values include 2400 Volts Delta, 4160/2400 Volts, etc. HighSideBIL: long integer Code indicating BIL rating of high side of TransformerUnit; example includes 125 BIL, etc. Impedance: double Impedance of TransformerUnit, expressed as percentage LowSideRatedVoltage: long integer Code indicating system voltage of low side of 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 of TransformerUnit to change transformer ratio Manufacturer: text Manufacturer of TransformerUnit; domain values include 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, domain values include Arachlor, Diachlor, etc. RatedKVA: long integer kVA at nominal voltage; domain values include 10 kVA, 112 kVA, 333 kVA, etc.
876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321 876543210987654321
Object
DeviceObject UnitObject VoltageRegulatorUnit
AnimalGuardType ArrestorType Available CoolingType FluidType FullLoadLosses HighSideRatedVoltage HighSideBIL Impedance LowSideRatedVoltage LowSideBIL LowSideTaps Manufacturer MaxSteps NoLoadLosses PCBLevel RatedKVA TapsType VoltageRegulatorObjectID XRRatio
Table of Contents
TapsType: text Code indicating type of taps; domain values include 2Above/2Below, 4Above, etc. VoltageRegulatorObjectID: long integer ObjectID of associated voltage regulator XRRatio: double Inductance/resistance ratio Associations: VoltageRegulator, RegulatorControl
Table of Contents
Table of Contents
Customer and Service Data Service Data Refer erence Model Reference
Table of Contents
99
43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321 43210987654321098765432121098765432109876543210987654321
Comments Status
CUSTOMER AND SERVICE
ServicePoint
Address ConnectionType PhaseDesignation ServiceCurrentRating
CustomerConnection
CTRatio MeterRating MeterType PTRatio RemoteRead
PrimaryMeter
Residential, commercial, and industrial customers, resellers, as well as special devices such as streetlights, constitute the loads on the electrical system. ElectricLocation is an abstract class representing the point at which electricity is supplied to the customer.
CUSTOMER AND SERVICE
BillingType DeliveryToOwner MeterIndicator OperatingStatus
ElectricTraceWeight FeederID FeederID2 FeederInfo InstallationDate LocationID Subtype SymbolRotation WorkOrderID
ElectricLocation
DeliveryPoint
Table of Contents
ConnectionConfiguration GroundReactance GroundResistance KW MaxReactiveGeneration NominalVoltage PositiveSequenceReactance PositiveSequenceResistance PowerFactor RatedKVA SubtransientReactance TransientReactance ZeroSequenceReactance ZeroSequenceResistance
Generator
Electric Location ElectricLocation defines the following attributes: ElectricTraceWeight: long integer Used by Feeder Manager to determine device status and other information that affects circuit connectivity FeederID: text Feeder Manager identifier assigned to feeders and devices that participate in a specific distribution circuit FeederID2: text Feeder Manager identifier assigned if device is supplied by second feeder FeederInfo: long integer Feeder Manager-assigned phase information describing the phase of the circuit that supplies a device InstallationDate: date Date of installation of ElectricLocation LocationID: text Utility-assigned identifier of ElectricLocation Subtype: long integer Code indicating subtype SymbolRotation: double Angle of rotation dictating how a feature appears on the map WorkOrderID: text Work order identifier Association: FacilityStructure, UndergroundStructure Subtypes: None Customer Connection CustomerConnection contains information about the service provided to the customer and defines the following attributes: Address: text Customer address ConnectionType: text Type of connection PhaseDesignation: long integer Code indicating phases present; domain values include A, AB, AC, etc. ServiceCurrentRating: short integer Code indicating maximum rating of service delivered to CustomerConnection; domain values include 100 Amps, 600 Amps, etc. Association: ServiceAddress Service Point ServicePoint is the point at which the distribution feeder terminates and energy is supplied to a customer. A service point can have one or many meters. ServicePoint defines the following attributes: Comments: text User or designer comments Status: text Code indicating status of ServicePoint; domain values include Active, Inactive Associations: InductionMotor, SynchronousMotor
9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321
ElectricLocation
ElectricTraceWeight FeederID FeederID2 FeederInfo InstallationDate LocationID Subtype SymbolRotation WorkOrderID
CustomerConnection
Address ConnectionType PhaseDesignation ServiceCurrrentRating
ElectricLocation
CustomerConnection
ServicePoint
Comments Status
Chapter Table of Contents
7 Customer and Service Data Model Reference 101
Primary Meter Primary meters are installed if commercial customers elect to have power delivered at distribution voltages, such as 12.5 kV. Residential customers are generally billed for kilowatt hours (kWH) used. Commercial and industrial customers may additionally be billed for demand charges and power factor charges. The utility can use current transformers or CTs to measure and voltage-measuring transformers (potential transformers or PTs) to transform current and voltage levels 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 include Conventional, 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 Point DeliveryPoint 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
9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321
ElectricLocation CustomerConnection PrimaryMeter
CTRatio MeterRating MeterType PTRatio RemoteRead
9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321
ElectricLocation DeliveryPoint
BillingType DeliveryToOwner MeterIndicator OperatingStatus
OperatingStatus: text Code indicating status of DeliveryPoint; domain values include Active, Inactive Generator Generator is an alternative, third-party power source feeding into the electrical network. Generator defines the following attributes: ConnectionConfiguration: text Code indicating type of connection of Generator; 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 device is rated; domain values include 4.16 kV Grounded Y, 7.2 kV Grounded Y, etc. PositiveSequenceReactance: double Equivalent positive sequence reactance seen at source by downstream circuit, in ohms
Table of Contents
9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321 9876543210987654321
ElectricLocation Generator
ConnectionConfiguration GroundReactance GroundResistance KW MaxReactiveGeneration NominalVoltage PositiveSequenceReactance PositiveSequenceResistance PowerFactor RatedKVA SubtransientReactance TransientReactance ZeroSequenceReactance ZeroSequenceResistance
PositiveSequenceResistance: double Equivalent positive sequence resistance seen 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 at source by downstream circuit, in ohms ZeroSequenceResistance: double Equivalent zero sequence resistance seen at source by downstream circuit, in ohms Induction Motor InductionMotor is an electric transformer with a magnetic circuit separated by an air gap into two movable portions carrying the primary and secondary windings. Secondary currents are created by induction rather than being supplied by a dc exciter or other external power source.Types of induction motor are wound rotor and squirrel cage. Induction motors have National Electric Manufacturers Association (NEMA) specifications and defines the following attributes: ConnectionConfiguration: text Code indicating connection configuration of InductionMotor; 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, in percentage LockedRotorPF: double Power factor of locked rotor, expressed as less than one 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 system voltage, expressed as line-to-line or line-to-neutral; domain values include 4.16 kV Grounded Y, 7.2 kV Grounded Y, etc. PhaseDesignation: long integer Code indicating phases present; domain values include A, AB, AC, etc. PowerFactor: double Power factor expressed as less than one or as percentage RatedHP: double Rated horsepower
3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321 3210987654321098765432121098765432109876543210987654321
ArmatureResistance ConnectionConfiguration DAxisSynchronousReactance QAxisSynchronousReactance SaturationCoefficient10 SaturationCoefficient12 ServicePointObjectID SubtransientReactance TransientReactance ZeroSequenceReactance
SynchronousMotor
Object
Synchronous Motor Synchronous motors transform electric power from an alternating current system into mechanical power. The armature winding, usually on the stator, is the current carrying winding. The configuration of the rotor determines the type of synchronous motor and usually employs dc-excited field windings. Synchronous motors are built for operating at a power factor or 1.0 or 0.8 lead. Reactance is measured in a steady-state condition in which a circuits values remain essentially constant, occurring after all initial transients or fluctuating conditions have settled down.
Association: ServicePoint
SoftStartWinding: double Soft start winding
SoftStartTap: double Soft start tap
SoftStartResistance: double Soft start resistance, R
SoftStartReactance: double Soft start reactance, X
ServicePointObjectID: long integer ObjectID of ServicePoint
ConnectionConfiguration Efficiency GroundReactance GroundResistance LockedRotorMultiplier LockedRotorPF MotorStartLimit MotorStartLimitAmount NEMALockedRotorRatio NominalVoltage PhaseDesignation PowerFactor RatedHP ServicePointObjectID SoftStartReactance SoftStartResistance SoftStartTap SoftStartWinding
InductionMotor
Table of Contents
Comments Status
ServicePoint
SynchronousMotor defines the following attributes: ArmatureResistance: double Resistance of armature winding, in ohms ConnectionConfiguration: text Code indicating connection configuration of SynchronousMotor DAxisSynchronousReactance: double Ratio of reactive armature voltage to direct axis reactance under steady-state conditions QAxisSynchronousReactance: double Ratio of reactive armature voltage to quadrature 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-terminal voltage SubtransientReactance: double Subtransient reactance, in ohms TransientReactance: double Transient reactance, in ohms ZeroSequenceReactance: double Ratio of in-phase armature voltage to negative sequence reactance Association: ServicePoint
98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 98765432121098765432109876543210987654321 1 98765432121098765432109876543210987654321 9876543212109876543210987654321098765432
BillingPeriod KWH
UsageInfo
AccountNumber DataSource MonthCD ServiceAddressObjectID
CustomerInfo
Object
Demand is the load at the receiving terminals averaged over a specified interval of time. Demand is expressed in real power, apparent power, or current kilowatts, reactive volt-amperes, volt-amperes, or amperes. Information about the location and size of loads on the system is essential for operations, design, and planning for current and future facilities.
Load Utilities generate their entire revenue from customers, who represent a load on the system. There are three kinds of load:
KW KVAR
DemandInfo
(3) special-purpose devices such as streetlights, and traffic control signals
(2) bulk delivery points to reselling utilities
(1) residential, commercial, and industrial customers
Table of Contents
CurrentTotal KVAR KW Voltage
LoadSummary
Address CriticalCustomerIndicator CustomerClass
ServiceAddress
Service Address ServiceAddress defines the following attributes: Address: text Customer address CriticalCustomerIndicator: text Code indicating whether customer has critical need for electricity; domain values include Critical, Non-Critical CustomerClass: text Code indicating class of customer; domain values include Commercial, Industrial, MultiFamily Residential, Single Family Residential Associations: CustomerConnection
Object
Customer Info CustomerInfo defines the following attributes: AccountNumber: text Customer account number DataSource: text Source of customer data MonthCD: text Code indicating month of service; domain values include January, March, etc. ServiceAddressObjectID: long integer Object ID of ServiceAddress Demand Info Demand from the customer is the load at receiving terminals averaged over a specific time. Industrial and commercial customers can be billed for having sufficient power available. This demand charge is measured in kVA and is over and above the charge for kWh. A power factor charge may also be billed to large customers to offset the necessity of having to provide reactive power to serve large motor loads. DemandInfo defines the following attributes: kW: long integer Load demand in kilowatts kVAR: long integer Reactance, in reactive volt-amperes
CustomerInfo
AccountNumber DataSource MonthCD ServiceAddressObjectID
DemandInfo
KW KVAR
5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321 5432121098765432109876543210987654321
Object
CustomerConnection ServiceAddress
Address CriticalCustomerIndicator CustomerClass Address ConnectionType PhaseDesignation ServiceCurrentRating
76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 76543210987654321 1 76543210987654321 7654321098765432
Load Summary Demand from the customer is the load at receiving terminals averaged over a specific 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 Info Residential 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
432109876543210987654321 432109876543210987654321 432109876543210987654321 432109876543210987654321 432109876543210987654321 432109876543210987654321 432109876543210987654321 432109876543210987654321 432109876543210987654321 432109876543210987654321 432109876543210987654321 432109876543210987654321 432109876543210987654321 432109876543210987654321 432109876543210987654321 432109876543210987654321 432109876543210987654321 432109876543210987654321 432109876543210987654321 432109876543210987654321 432109876543210987654321 432109876543210987654321 1 432109876543210987654321 43210987654321098765432
Object
CustomerInfo UsageInfo LoadSummary
BillingPeriod KWH CurrentTotal KVAR KW Voltage
Table of Contents
Index
A
Add Data 43 AerialMarker 52 amperes 108 AnchorGuy 53 ArcCatalog 33 armature winding 104 Assembly 56 asset management 12
D
Data Converters 44 data model 28 data model requirements 33 dead-front 74 DeliveryPoint 102 Demand 106 DemandInfo 107 DeviceObject 90 devices 10, 11 direct buried cables 59 Duct Definition 59 ducts 59 duty cycle 76 DynamicProtectiveDevice 75
G
Generator 102 Ground 73 Ground reactance 79 Ground resistance 79 Guy 53
H
H-frames 49 Hand Hole 59 Hertz 86 horizontal forces 50 horizontal load 53
B
bandwidth 92 BIL 75 BIL rating 75 binary large object 60 Building a Geodatabase 36 BusBar 65
E
E speed 86 ElectricComplexEdge 62 ElectricDevice 72 ElectricLine 68, 70 ElectricLineSegment 63 ElectricLocation 101 ElectricStation 51 enclosures 49 extra high voltage 51
I
InductionMotor 103 infrastructure 11 inrush current 80, 89 Inspection 57 interrupting mechanism 76 interrupting medium 76
C
C++ 25 CapacitorBank 79 CapacitorControl 90 CapacitorUnit 93 CATV 55, 66 circuit segments 10 CircuitBreaker 76 CircuitSource 68 Code Generation Wizard 35 COM object 30, 59, 60 Component Object Model (COM) 9 ConductorInfo 64 Configuration 60 connectivity rules 33 contacts 76 Coordinate System 37 Creosote 50 cross section 59 CTs 77, 88, 102 current transformers 102 customer information 11 CustomerConnection 101 CustomerInfo 107
J
joint use 55, 66
F
FacilityStructure 49 fault current 88 Fault interrupters 77 FaultIndicator 73 FaultLimiter 73 FdrMgrNonTraceable 65 feeder 31, 52, 68, 101 feeder management 63 feeders 63 Fuse 78 fuse 75 fuse cutouts 75 FuseUnit 93
K
K speeds 86 kilowatts 108 kVAR 68 kW 68 kWH 102
L
LifecycleHistory 56 line-drop compensator 92 Load 106 loads 11 LoadSummary 108 LoadTapChanger 91 lock open 75 logical network 72
INDEX
Table of Contents
109
M
main 49 Manhole 59 meters 102 Modeling Our World 30, 36
Repository 28, 33, 35, 39 resistance 64 Riser 54 rms 73, 75, 81
S
SCADA 31, 62, 66, 76, 81, 90 Schema Creation Wizard 30, 33, 35 secondary windings 92 sectionalizers 75, 77 SectionalizerUnit 94 ServiceAddress 107 ServicePoint 101 ShuntReactor 80 Simple Data Loader 42, 44 slope 53 snapping 44 Spacing 66 SpanGuy 54 Spatial Reference 37 StreetLight 80 structure 10 Structure class 49 submersible 58 substation buses 65 substations 49 SurgeArrestor 73 switch 30, 81 SwitchingFacility 52 SwitchUnit 94 SynchronousMotor 105
UndergroundStructure 58 Unified Modeling Language 24 UnitObject 93 unity 78 URD 58, 67 UsageInfo 108
N
NEMA 103 NetworkProtector 84
V
Vault 59 vertical forces 50 Visio 36 volt-amperes 108 voltage drop 93 Voltage Regulator 83 VoltageRegulatorUnit 96
O
Object Loader 36, 44 open loops 58 OpenPoint 74 OverCurrentProtectiveDevice 75
W
WarningSign 55 winding 104
P
pads 49 pedestals 49 PF 78 Phase designation 64 polyethylene 67 pothead 54 power factor 104 PowerFactorCorrectingEquipment 78 preservatives 50 primary feeder 51, 82, 84 PrimaryMeter 102 Properties 40 PT 92, 102 Pushbraces 54
T
TCC 78, 86 Transformer 83 transformer loading 63 transformer winding 91 TransformerBank 82 TransformerUnit 95, 96 trenches 59 trips 86, 88, 94
Q
Query Builder 42
R
reactive volt-amperes 108 recloser 77 reclosers 75 RecloserUnit 94 Regulator Control 92 relay systems 85 110
U
UML 24, 30 defining objects and models 24 underground linear structures 59
INDEX
Table of Contents

Electric Distribution

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Electric Distribution

Încărcat de

Drepturi de autor:

Formate disponibile

1

iv ArcGIS Electric Distribution Model

vi ArcGIS Electric Distribution Model

Modeling with ArcGIS Electric Distribution

8 ArcGIS Electric Distribution Model

A RC GIS E LECTRIC D ISTRIBUTION

Modeling with ArcGIS Electric Distribution 9

10 ArcGIS Electric Distribution Model

Electric distribution modeling requires considering facilities as assets

Electric modeling requires consideration of facilities as assets.

Modeling with ArcGIS Electric Distribution 11

12 ArcGIS Electric Distribution Model

Building Analysis Models

Examples include gas pipe, communication cable, and water pipe.

Other ULS Contents Underground Electric LineSegment

Subtypes include Duct Bank and Trench.

Subtypes include Main Station, Net Station, and Sub Station

Building Analysis Models 15

Subtypes include Circuit Line and Station Line

Feature ComplexEdge Feature ElectricComplexEdge

OverheadElectric LineSegment UndergroundElectric LineSegment

16 ArcGIS Electric Distribution Model

customer & service

CustomerInfo UsageInfo DemandInfo LoadSummary

These relationships are not valid for ServicePoint

Representation of Customer Information System

Generator DeliveryPoint CustomerConnection

Object ServicePoint InductionMotor SychronousMotor PrimaryMeter

Building Analysis Models 17

18 ArcGIS Electric Distribution Model

This relationship is only valid for Sectionalizer subtypes.

This relationship is only valid for Recloser subtypes.

Building Analysis Models 19

20 ArcGIS Electric Distribution Model

Building Analysis Models 21

This relationship is only valid for DynamicProtectiveDevice Sectionalizer subtypes.

22 ArcGIS Electric Distribution Model

This relationship is only valid for TransformerUnit subtype VoltageRegulatorUnit.

This relationship is only valid for Transformer subtype Power Transformer.

Building Analysis Models 23

ARCGIS ANALYSIS MODELS

THE ARCGIS ANALYSIS MODELS

24 ArcGIS Electric Distribution Model

Building Analysis Models 25

26 ArcGIS Electric Distribution Model

Deploying Deploying ArcGIS ArcGIS Electric Distribution

DEPLOYING ARCGIS ELECTRIC

28 ArcGIS Electric Distribution Model

Deploying ArcGIS Electric 29

GEODATABASE DESIGN,TOOLS AND GUIDELINES

30 ArcGIS Electric Distribution Model

Switch feature class inherits attributes of ElectricDevice

Deploying ArcGIS Electric 31

32 ArcGIS Electric Distribution Model

ARCGIS ELECTRIC DEPLOYMENT SCENARIOS

Deploying ArcGIS Electric 33

COM Code Generator

3rd Party CASE

Uml Object Model

Deploying ArcGIS Electric 35

IMPLEMENTING ARCGIS ELECTRIC

36 ArcGIS Electric Distribution Model

Deploying ArcGIS Electric 37