32365888 ArcGIS Telecom Data Dictionary

59
ArcGIS Telecom Data Model Data Dictionary Revised: August 2007

Transcript of 32365888 ArcGIS Telecom Data Dictionary

Page 1: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model Data Dictionary

Revised: August 2007

Page 2: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

ii

Copyright © 2006 ESRI All rights reserved. Printed in the United States of America. The information contained in this document is the exclusive property of ESRI. 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 ESRI. All requests should be sent to Attention: Contracts and Legal Services Manager, ESRI, 380 New York Street, Redlands, California 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 ESRI, 380 New York Street, Redlands, California 92373-8100, USA.

@esri.com, 3D Analyst, ACORN, ADF, AML, ArcAtlas, ArcCAD, ArcCatalog, ArcCOGO, ArcData, ArcDoc, ArcEdit, ArcEditor, ArcEurope, ArcExplorer, ArcExpress, ArcGIS, ArcGlobe, ArcGrid, ArcIMS, ARC/INFO, ArcInfo, ArcInfo Librarian, ArcInfo—Professional GIS, ArcInfo—The World's GIS, ArcLocation, ArcLogistics, ArcMap, ArcNetwork, ArcNews, ArcObjects, ArcOpen, ArcPad, ArcPlot, ArcPress, ArcQuest, ArcReader, ArcScan, ArcScene, ArcSchool, ArcSDE, ArcSdl, ArcSketch, ArcStorm, ArcSurvey, ArcTIN, ArcToolbox, ArcTools, ArcUSA, ArcUser, ArcView, ArcVoyager, ArcWatch, ArcWeb, ArcWorld, ArcXML, Atlas GIS, AtlasWare, Avenue, Business Analyst Online, BusinessMAP, Community, CommunityInfo, Data Automation Kit, Database Integrator, DBI Kit, EDN, ESRI, ESRI—Team GIS, ESRI—The GIS Company, ESRI—The GIS People, ESRI—The GIS Software Leader, FormEdit, Geographic Design System, ESRI BIS, Geography Matters, Geography Network, GIS by ESRI, GIS Day, GIS for Everyone, GISData Server, JTX, MapBeans, MapCafé, MapData, MapObjects, Maplex, MapStudio, ModelBuilder, MOLE, NetEngine, PC ARC/INFO, PC ARCPLOT, PC ARCSHELL, PC DATA CONVERSION, PC STARTER KIT, PC TABLES, PC ARCEDIT, PC NETWORK, PC OVERLAY, PLTS, Rent-a-Tech, RouteMAP, SDE, Site·Reporter, SML, Sourcebook·America, Spatial Database Engine, StreetEditor, StreetMap, Tapestry, the ARC/INFO logo, the ArcAtlas logo, the ArcCAD logo, the ArcCAD WorkBench logo, the ArcCOGO logo, the ArcData logo, the ArcData Online logo, the ArcEdit logo, the ArcEurope logo, the ArcExplorer logo, the ArcExpress logo, the ArcGIS logo, the ArcGIS Explorer logo, the ArcGrid logo, the ArcIMS logo, the ArcInfo logo, the ArcLogistics Route logo, the ArcNetwork logo, the ArcPad logo, the ArcPlot logo, the ArcPress for ArcView logo, the ArcPress logo, the ArcScan logo, the ArcScene logo, the ArcSDE CAD Client logo, the ArcSDE logo, the ArcStorm logo, the ArcTIN logo, the ArcTools logo, the ArcUSA logo, the ArcView 3D Analyst logo, the ArcView Business Analyst logo, the ArcView Data Publisher logo, the ArcView GIS logo, the ArcView Image Analysis logo, the ArcView Internet Map Server logo, the ArcView logo, the ArcView Network Analyst logo, the ArcView Spatial Analyst logo, the ArcView StreetMap 2000 logo, the ArcView StreetMap logo, the ArcView Tracking Analyst logo, the ArcWorld logo, the Atlas GIS logo, the Avenue logo, the BusinessMAP logo, the Community logo, the Data Automation Kit logo, the Digital Chart of the World logo, the ESRI Data logo, the ESRI globe logo, the ESRI Press logo, The Geographic Advantage, the Geography Network logo, the MapCafé logo, the MapObjects Internet Map Server logo, the MapObjects logo, the MOLE logo, the NetEngine logo, the PC ARC/INFO logo, the Production Line Tool Set logo, the RouteMAP IMS logo, the RouteMAP logo, the SDE logo, The World's Leading Desktop GIS, Water Writes, www.esri.com, www.esribis.com, www.geographynetwork.com, www.gis.com, www.gisday.com, and Your Personal Geographic Information System are trademarks, registered trademarks, or service marks of ESRI in the United States, the European Community, or certain other jurisdictions.

Other companies and products mentioned in the ESRI Web site may be trademarks or registered trademarks of their respective trademark owners.

Page 3: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

iii

Table of Contents

1.0 Introduction........................................................................................................... 1 2.0 Data Model Classes ............................................................................................... 2

2.1 Underground Structures ............................................................................................ 3 2.1.1 TelecomComplexEdge........................................................................................ 3 2.1.2 Conduit............................................................................................................... 4 2.1.3 TelecomJunction ................................................................................................ 4 2.1.4 Structure............................................................................................................. 5

2.2 Overhead Facilities ............................................................................................. 7 2.2.1 TelecomFeatureStructure .................................................................................. 7 2.2.2 AnchorGuy......................................................................................................... 7 2.2.3 Pole .................................................................................................................... 8 2.2.4 PushBrace .......................................................................................................... 9 2.2.5 Riser ................................................................................................................. 10

2.3 Cables................................................................................................................ 10 2.3.1 TelecomSimpleEdge ......................................................................................... 10 2.3.2 Span.................................................................................................................. 11 2.3.3 Cable ................................................................................................................ 11 2.3.4 CopperCable .................................................................................................... 12 2.3.5 FiberCable........................................................................................................ 12

2.4 Devices.............................................................................................................. 14 2.4.1 CopperRepeater................................................................................................ 14 2.4.2 DigitalCrossConnect ........................................................................................ 14 2.4.3 DigitalLoopCarrier........................................................................................... 15 2.4.4 FiberInterconnect ............................................................................................. 15 2.4.5 LoadCoil .......................................................................................................... 15 2.4.6 MainDistributionFrame.................................................................................... 16 2.4.7 Multiplexer....................................................................................................... 17 2.4.8 OpticalRepeater................................................................................................ 17 2.4.9 PatchPanel........................................................................................................ 17 2.4.10 SpliceClosure ................................................................................................. 18 2.4.11 Splitter............................................................................................................ 18 2.4.12 Terminal......................................................................................................... 19 2.4.13 Termination.................................................................................................... 20

2.5 Object Classes................................................................................................... 20 2.5.1 TelecomObject ................................................................................................. 20 2.5.2 Attachment....................................................................................................... 21 2.5.3 BufferTube....................................................................................................... 21 2.5.4 Complements ................................................................................................... 22 2.5.5 DuctObject ....................................................................................................... 22 2.5.6 Duct.................................................................................................................. 23 2.5.7 Innerduct .......................................................................................................... 23 2.5.8 Fiber ................................................................................................................. 24 2.5.9 Location ........................................................................................................... 24

Page 4: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

iv

2.5.10 Maintenance Loop ......................................................................................... 25 2.5.11 PortObject...................................................................................................... 25 2.5.12 DLCPort......................................................................................................... 26 2.5.13 DXCPort ........................................................................................................ 26 2.5.14 FICPort........................................................................................................... 26 2.5.15 MUXPort........................................................................................................ 27 2.5.16 OptRptrPort.................................................................................................... 27 2.5.17 PatchPanelPort ............................................................................................... 27 2.5.18 SplitterPort ..................................................................................................... 28

3.0 Data Model Domains and Relationships........................................................... 29 3.1 Domains .................................................................................................................. 29

3.1.1 AnchorRodType............................................................................................... 29 3.1.2 AnchorType ..................................................................................................... 29 3.1.3 Assembly Framing Type.................................................................................. 30 3.1.4 Assembly Framing Type.................................................................................. 30 3.1.5 Availability Indicator ....................................................................................... 30 3.1.6 CableCoreType ................................................................................................ 31 3.1.7 ConduitMaterial ............................................................................................... 31 3.1.8 EnabledDomain................................................................................................ 32 3.1.9 FiberBufferColors ............................................................................................ 32 3.1.10 FiberMode...................................................................................................... 33 3.1.11 FibersPerBuffer.............................................................................................. 33 3.1.12 FiberStatus ..................................................................................................... 33 3.1.13 Foreign Attachment Owner............................................................................ 34 3.1.14 GuyMaterial ................................................................................................... 34 3.1.15 GuyRatingType.............................................................................................. 34 3.1.16 Measured Length ........................................................................................... 35 3.1.17 MountType..................................................................................................... 35 3.1.18 MUXType...................................................................................................... 35 3.1.19 NumberOfBuffers .......................................................................................... 36 3.1.20 NumberOfFibers ............................................................................................ 36 3.1.21 PlacementType............................................................................................... 37 3.1.22 NumberOfCopperPairs .................................................................................. 37 3.1.23 PoleClass........................................................................................................ 38 3.1.24 Pole Foundation Type .................................................................................... 38 3.1.25 PoleHeight...................................................................................................... 39 3.1.26 PoleMaterial................................................................................................... 39 3.1.27 PoleTreatmentType........................................................................................ 40 3.1.28 PortType......................................................................................................... 40 3.1.29 RiserMaterial.................................................................................................. 41 3.1.30 SpliceType ..................................................................................................... 41 3.1.31 SplitterRatios.................................................................................................. 41 3.1.32 StrandSizes..................................................................................................... 42 3.1.33 TerminalType................................................................................................. 42 3.1.34 ULS Size ........................................................................................................ 43 3.1.35 Yes/No Indicator............................................................................................ 43

Page 5: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

v

3.1.36 TerminationType............................................................................................ 43 3.2 Relationships........................................................................................................... 45

3.2.1 BufferTubeContainsFiber ................................................................................ 45 3.2.2 CableHasComplements.................................................................................... 45 3.2.3 ConduitHasCopperCable ................................................................................. 45 3.2.4 ConduitHasDuct............................................................................................... 46 3.2.5 ConduitHasFiberCable..................................................................................... 46 3.2.6 Conduit_Structure ............................................................................................ 46 3.2.7 CopperRepeaterHasComplements ................................................................... 46 3.2.8 DCCHasComplements..................................................................................... 47 3.2.9 DCCHasPorts................................................................................................... 47 3.2.10 DLCHasPorts ................................................................................................. 47 3.2.11 DuctHasCopperCable .................................................................................... 48 3.2.12 DuctHasFiberCable........................................................................................ 48 3.2.13 DuctHasInnerduct .......................................................................................... 48 3.2.14 FiberCableHasBufferTube............................................................................. 49 3.2.15 FIberCableHasMaintLoop ............................................................................. 49 3.2.16 FICHasPorts................................................................................................... 49 3.2.17 InnerductHasCopperCable............................................................................. 49 3.2.18 InnerductHasFiberCable ................................................................................ 50 3.2.19 LoadCoilHasComplements ............................................................................ 50 3.2.20 MuxHasPorts.................................................................................................. 50 3.2.21 OPTRHasPorts............................................................................................... 51 3.2.22 PatchPanelHasPorts ....................................................................................... 51 3.2.23 PoleHasAttachment........................................................................................ 51 3.2.24 SpanHasFiberCable........................................................................................ 51 3.2.25 SpanHasConduit ............................................................................................ 52 3.2.26 SplitterHasPorts ............................................................................................. 52 3.2.27 TerminalHasComplements ............................................................................ 52 3.2.28 TerminalHasLocation .................................................................................... 53

Appendix A – ArcGIS Data Types ................................................................................ 54

Page 6: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

1

1.0 Introduction ArcGIS Telecom contains a ready-to-use data model that can be configured and customized to meet the needs of ESRI users that design and maintain telecommunications networks and associated infrastructure.

Diagram 1.1 ArcGIS Telecom Logical Model Diagram

Page 7: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

2

2.0 Data Model Classes The review of each class will contain the following review items:

Type – Whether it is an abstract or concrete class, and if concrete - feature or object class.

Inherits From – What abstract classes the class inherits from in the model.

Geometry – If it is a feature class, the geometry type.

Attributes – The attributes for the class, the aliases, data types, and attribute descriptions.

Subtypes – The subtypes for the class and their descriptions.

Relationships – The relationships which the class participates in and why.

Notes – Supplemental information which helps to describe the class. Using the review items listed above, the following is the table structure which will be used to provide information about each class:

Class Name <Name> Type Inherits From Geometry Attributes Example:

Comments – narrative (Alias is in italics) – <Text, 100> - (Data Type is in brackets) This is the definition here.

Subtypes Relationships Notes

Page 8: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

3

2.1 Underground Structures This section is comprised of Underground Structures which are part of the Telecom data model. There are two feature classes – Conduit and Structure. 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.

2.1.1 TelecomComplexEdge TelecomComplexEdge is an abstract class whose attributes are inherited by complex edge feature classes in the model. These feature classes include Conduit, CopperCable and FiberCable. The following table provides information regarding the TelecomComplexEdge Abstract class, with attributes, aliases, data types and descriptions.

Class Name TelecomComplexEdge Type Abstract class Inherits From ComplexEdgeFeature Geometry Not applicable Attributes WorkOrderID – Work Order ID - <text, 20> - Utility identifier of work order

ProjectNumber – Project Number - <text, 20> - The project number identifier. ProjectName – Project Name - <text, 20> - The project name. CLLI - Common Language Location Identifier - <text, 20> - Code descriptor used to identify telecommunications switches, interconnections, and other network elements and their locations. Manufacturer – Manufacturer - <text, 20> - Manufacturer of the TelecomComplexEdge PartNumber – Part Number - <text, 20> - Manufacturer’s part number. CalculatedLength – Calculated Length – <double> - The calculated length of the conduit segment. MeasuredLength – Measured Length - <double> - The code for the measured length of the conduit segment. A range domain is applied constraining between 1 – 10,000. AccountCode – Account Code - <text, 20> - The Account Code which the Conduit is referenced. InstallationDate – Installation Date - <date> - The date of installation. IPID – Item of Plant ID - <long integer> - The unique identifier for the Plant ID system. MaterialCost – Material Cost - <double> - The estimated cost of the material. Diameter – Diameter - <double> - The diameter of the conduit. Comments – Comments - <text, 100> - User or Designer Comments

Page 9: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

4

Subtypes Not applicable Relationships Not applicable Notes Abstract class used for the storage of additional Complex Edge attributes

which are inherited within the model.

2.1.2 Conduit A Conduit is a linear object which belongs to the structural network. It is the outermost casing. A Conduit may contain Duct(s) and Innerduct(s). Duct(s) and Innerduct(s) are modeled as non-graphic objects stored in object classes. Conduit is a concrete feature class that 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.

Class Name Conduit Type Feature class Inherits From TelecomComplexEdge Geometry Polyline Attributes Material – Material - <long integer> - Code indicating conduit material.

Uses the ConduitMaterial domain. SpanID – Span ID (fk) - <long integer> - The IPID of the associated Span feature.

Subtypes Trench and Duct Bank

Relationships Many-to-many relationship to the Structure feature class One-to-many relationship to the Duct table One-to-many relationship to the FiberCable feature class One-to-many relationship to the CopperCable feature class

Notes

2.1.3 TelecomJunction TelecomJunction is an abstract class whose attributes are inherited by simple junction feature classes in the model. Most concrete classes inheriting include the underground Structure class, as well as classes in the Device section.The following table provides information regarding the TelecomJunction Abstract class, with attributes, aliases, data types and descriptions.

Class Name TelecomJunction Type and Purpose Abstract class Inherits From SimpleJunction Geometry Not applicable Attributes WorkOrderID – Work Order ID - <text, 20> - Utility identifier of work order

ProjectNumber – Project Number - <text, 20> - The project number identifier. ProjectName – Project Name - <text, 20> - The project name. CLLI - Common Language Location Identifier - <text, 20> - Code descriptor used to identify telecommunications switches, interconnections,

Page 10: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

5

and other network elements and their locations. Manufacturer – Manufacturer - <text, 20> - Manufacturer of the TelecomComplexEdge feature. PartNumber – Part Number - <text, 20> - Manufacturer’s part number. ModelNumber – Model Number - <text, 20> - Model Number of the TelecomJunction feature. SerialNumber – Serial Number - <text, 20> - Manufacturer’s Serial number. Cost – Cost - <double> - The estimated cost of the specific structure facility. AccountCode – Account Code - <text, 20> - The Account Code which the Conduit is referenced. InstallationDate – Installation Date - <date> - The date of installation. IPID – Item of Plant ID - <long integer> - The unique identifier for the Plant ID system. Comments – Comments - <text, 100> - User or Designer Comments

Subtypes Not applicable Relationships Not applicable Notes Abstract class used for the storage of additional Complex Edge attributes

which are inherited within the model.

2.1.4 Structure Structure is a concrete feature class that describes features needed to support an underground telecommunications system. It is a simple junction feature that includes vaults, manholes, that house and protect electrical equipment. Structures are underground access point for cable and splices. It is comprised of the following types: Manhole, Handhole, Pullbox, and Vault.

Class Name Structure Type Feature class - Simple Junction Inherits From TelecomJunction Geometry Point Attributes StructureSize – Structure Size - <text, 20> - Size of the structure.

Material – Material - <text, 20> - Material of the structure. Subtypes Manhole (SubtypeCode=1)

Handhole (SubtypeCode=2) Pullbox (SubtypeCode=3) Vault (SubtypeCode=4)

Relationships Many-to-many relationship with Conduit feature class, with the Conduit_Structure relationship. See the Relationships in Section 3.2 for more information.

Notes

Page 11: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

6

Page 12: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

7

2.2 Overhead Facilities The Overhead Facilities subsystem contains non-network features which support cables and devices.

2.2.1 TelecomFeatureStructure TelecomFeatureStructure is an abstract class whose attributes are inherited by simple point feature (non-junction) classes in the model. The concrete classes inheriting include the following point classes: AnchorGuy, Pole, PushBrace and Riser. The following table provides information regarding the TelecomFeatureStructure Abstract class, with attributes, aliases, data types and descriptions.

Class Name TelecomFeatureStructure Type Abstract class Inherits From Feature Geometry Not applicable Attributes WorkOrderID – Work Order ID - <text, 20> - Utility identifier of work order

ProjectNumber – Project Number - <text, 20> - The project number identifier. ProjectName – Project Name - <text, 20> - The project name. Owner – Owner - <text, 20> - Owner of the TelecomFeatureStructure. CLLI - Common Language Location Identifier - <text, 20> - Code descriptor used to identify telecommunications switches, interconnections, and other network elements and their locations. AccountCode – Account Code - <text, 20> - The Account Code which the Conduit is referenced. Cost – Cost - <double> - The estimated cost of the specific structure facility. InstallationDate – Installation Date - <date> - The date of installation. IPID – Item of Plant ID - <long integer> - The unique identifier for the Plant ID system. Comments – Comments - <text, 100> - User or Designer Comments.

Subtypes Not applicable Relationships Not applicable Notes Abstract class used for the storage of additional Feature attributes which

are inherited within the model.

2.2.2 AnchorGuy AnchorGuy is a wire or set of wires running from the top of the pole to an anchor installed in the ground and consists 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.

Class Name AnchorGuy Type Feature class

Page 13: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

8

Inherits From TelecomFeatureStructure Geometry Point Attributes GuyCount – Guy Count - <long integer> - Count of guy wires.

LeadLength – Lead Length - <short integer> - Length of the lead of the anchor wire. WireMaterial – Wire Material - <long integer> - Material. Uses the GuyMaterial domain. WireSize – Wire Size - <long integer> - Size of the wire. Uses the StrandSizes domain. WireStrength -- Wire Strength - <long integer> - Strength of the wire. Uses the GuyRatingType domain. AnchorSize – Anchor Size - <long integer> - Size of the Anchor. AnchorType – Anchor Type - <long integer> - Type of anchor. Uses the AnchorType domain. RodType - Rod Type - <long integer> - Single or Double Eye Type of Rod. Uses the AnchorRodType domain.

Subtypes Back (SubtypeCode=1) Bridle (SubtypeCode=2) Sidewalk (SubtypeCode=3) Standard (SubtypeCode=4)

Relationships Not applicable. Notes

2.2.3 Pole Poles are point objects that support telecom devices and cables. Although many telecom 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 cables 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. The strength of a wood pole must be sufficient to withstand abnormal loads as well, such as ice and wind pressure. Pole features can have street lights, assemblies, and other attachments associated with them.

Class Name Pole Type Feature class Inherits From TelecomFeatureStructure Geometry Point Attributes PoleID – Pole ID - <long integer> - The unique identifier of the Pole.

Class – Class - <long integer> - Code indicating class of structure; domain values include Class 1, Class 10, H1, etc. Uses the PoleClass domain. Diameter – Diameter - <double> - Diameter of the pole. FoundationType – Foundation Type - <long integer> - Code indicating foundation used to set support structure; domain values include Set on Concrete Foundation, Set Extra Deep in Earth, etc. Uses the Pole Foundation Type domain.

Page 14: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

9

Grounded – Grounded - <text, 5> - Code indicating whether pole is grounded; domain values are Yes or No Uses the Yes/No Indicator domain. Height – Height - <long integer> - Height of the pole. Uses the PoleHeight domain. Material – Material - <long integer> - Code indicating material of pole; domain values include Aluminum, Fiberglass, Wood, etc. Uses the PoleMaterial domain. Style – Style - <text, 5> - Code indicating style of pole; domain values include Decorative, Normal, or Other. Uses the Pole Style domain. TreatmentType – Treatment Type - <long integer> - Code indicating type of treatment used, if any; domain values include Creosote, Paint, Pentachlorophenol, Chromated Copper Arsenates, Etc. Uses the PoleTreatmentType domain. YearManufactured – Year Manufactured - <long integer> - Year structure was manufactured. HasRiser – Has Riser - <text, 5> - Code indicating whether pole has a riser attached; domain values are Yes or No. Uses the Yes/No Indicator domain.

Subtypes Wood (SubtypeCode=1) Non-Wood (SubtypeCode=2) H-Frame (SubtypeCode=3) Tower (SubtypeCode=4)

Relationships Related to “Attachment” Object class. Notes

2.2.4 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 butt of the structure.

Class Name PushBrace Type Feature class Inherits From TelecomFeatureStructure Geometry Point Attributes PBClass – Class - <long integer> - Code indicating class of structure;

domain values include Class 1, Class 10, H1, etc. Uses the PoleClass domain. Height – Height - <long integer> - Height of the pushbrace. Uses the PoleHeight domain. PBMaterial – Material - <long integer> - Code indicating material of the pushbrace; domain values include Aluminum, Fiberglass, Wood, etc. Uses the PoleMaterial domain.

Subtypes Not applicable Relationships Not applicable Notes Not applicable

Page 15: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

10

2.2.5 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.

Class Name Riser Type Feature class Inherits From TelecomFeatureStructure Geometry Point Attributes Height – Height - <short integer> - Height of the riser.

RiserMaterial – Material - <long integer> - Code indicating material of the pole; domain values include Aluminum, Fiberglass, Wood, etc. Uses the RiserMaterial domain. Diameter – Diameter - <double> - Diameter of the Riser.

Subtypes Not applicable Relationships Not applicable Notes Not applicable

2.3 Cables Cables and Spans represent conductors bundled together that are capable of carrying voice and data transmissions.

2.3.1 TelecomSimpleEdge TelecomSimpleEdge is an abstract class whose attributes are inherited by simple edge feature classes in the model. There is only one simple edge feature in the model, which is Span. The following table provides information regarding the TelecomComplexEdge Abstract class, with attributes, aliases, data types and descriptions.

Class Name TelecomSimpleEdge Type and Purpose Abstract class Inherits From SimpleEdgeFeature Geometry Not applicable Attributes WorkOrderID – Work Order ID - <text, 20> - Utility identifier of work order

ProjectNumber – Project Number - <text, 20> - The project number identifier. ProjectName – Project Name - <text, 20> - The project name. CLLI - Common Language Location Identifier - <text, 20> - Code descriptor used to identify telecommunications switches, interconnections, and other network elements and their locations. CalculatedLength – Calculated Length – <double> - The calculated length of the conduit segment. MeasuredLength – Measured Length - <double> - The code for the measured length of the conduit segment. A range domain is applied constraining between 1 – 10,000.

Page 16: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

11

AccountCode – Account Code - <text, 20> - The Account Code which the Conduit is referenced. IPID – Item of Plant ID - <long integer> - The unique identifier for the Plant ID system. InstallationDate – Installation Date - <date> - The date of installation. Comments – Comments - <text, 100> - User or Designer Comments

Subtypes Not applicable

Relationships Not applicable Notes Abstract class used for the storage of Simple Edge attributes which are

inherited within the model.

2.3.2 Span A Span is a linear feature that provides an alternative method for associating two or more cables or conduit to a graphical feature without having to draw each feature on a map. The Span feature is useful when white-space management on a map is an issue.

Class Name Span Type Feature class Inherits From TelecomSimpleEdge Geometry Polyline Attributes SpanID – Span ID - <long integer> - Utility-assigned unique identifier.

Owner – Owner - <text, 20> - The owner of the Span. Cost – Cost - <double> - The estimated cost of the material.

Subtypes Aerial (SubtypeCode =1) Trench (SubtypeCode=2)

Relationships Not applicable Notes

2.3.3 Cable The following table provides information regarding the Cable Abstract class, with attributes, aliases, data types and descriptions. There are only two cable feature classes – CopperCable and FiberCable.

Class Name Cable Type Abstract class Inherits From TelecomComplexEdge, defined in section 2.1.1 Geometry Not applicable Attributes PlacementType – Placement Type - <long integer> - The type of

placement as in aerial, underground, etc. Uses the PlacementType domain. ReelID – Reel ID - <text, 20> - The unique ID of the Reel from which the cable came from. SheathType – Sheath Type - <text, 20> - The type of sheath.

Subtypes Not applicable Relationships Not applicable Notes Abstract class used for the storage of Cable attributes which are inherited

Page 17: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

12

within the model.

2.3.4 CopperCable A Copper Cables is a group of metallic conductors (copper wires) bundled together that are capable of carrying voice and data transmissions. The copper wires are bound together, usually with a protective sheath, a strength member, and insulation between individual conductors and the entire group. Copper pairs (complements) are not shown graphically within ArcGIS, therefore these are modeled using a relationship to the Complement Object (database only features).

Class Name CopperCable Type Feature class, Complex Edge Inherits From Cable Geometry Polyline Attributes NumberOfPairs – Number of Pairs - <long integer> - Number of pairs in

the copper cable. Uses the NumOfCopperPairs domain. Gauge – Gauge - <long integer> - Gauge of the wire. ConduitID – Conduit ID (fk) - <long integer> - The IPID of the associated Conduit feature. DuctID – Duct ID (fk) - <long integer> - The IPID of the associated Duct object. InnerductID – Innerduct ID (fk) - <long integer> - The IPID of the associated Innerduct object.

Subtypes UG Copper Cable (SubtypeCode=1) OH Copper Cable(SubtypeCode=2)

Relationships One-to-Many relationship to the Complements table. Many-to-One relationship to the Conduit feature class. Many-to-One relationship to the Duct object class. Many-to-One relationship to the Innerduct object class.

Notes

2.3.5 FiberCable A Fiber Optic Cable is composed of thin filaments of glass through which light beams are transmitted to carry large amounts of data. The optical fibers are surrounded by buffers, strength members, and jackets for protection, stiffness, and strength. A fiber-optic cable may be an all-fiber cable, or contain both optical fibers and metallic conductors.

Class Name FiberCable Type and Purpose Feature class, Complex Edge Inherits From Cable Geometry Polyline Attributes NumberOfBuffers – Number of Buffers - <long integer> - Number of

Buffers of the cable. Uses the NumberOfBuffers domain. NumberOfFibers - Number of Fibers - <long integer> - Number of fibers in the cable. Uses the NumberOfFibers domain. CoreType – Core Type- <long integer> - Type of Cable Core. Uses the CableCoreType domain. SpanID – Span ID (fk) - <long integer> - The IPID of the associated Span

Page 18: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

13

feature. ConduitID – Conduit ID (fk) - <long integer> - The IPID of the associated Conduit feature. DuctID – Duct ID (fk) - <long integer> - The IPID of the associated Duct object. InnerductID – Innerduct ID (fk) - <long integer> - The IPID of the associated Innerduct object.

Subtypes UG Fiber Cable (SubtypeCode=1) OH Fiber Cable(SubtypeCode=2)

Relationships Composite, One-to-Many relationship to the BufferTube table. Composite, One-to-Many relationship to the MaintenanceLoop table. Many-to-One relationship to the Span feature class. Many-to-One relationship to the Conduit feature class. Many-to-One relationship to the Duct object class. Many-to-One relationship to the Innerduct object class.

Notes

Page 19: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

14

2.4 Devices Telecom devices help manage and ensure consistent service within the telecommunications network. The device subsystem contains simple junction features that participate in a geometric network with telecom cables. Object classes which represent individual units, ports and control mechanisms are associated with these devices.

2.4.1 CopperRepeater A CopperRepeater is copper line conditioning equipment that amplifies the analog or digital input signal. Copper pairs (complements) are not shown graphically within ArcGIS, therefore these are modeled using a relationship to the Complement Object (database only features).

Class Name CopperRepeater Type Feature class, Simple Junction Inherits From TelecomJunction, defined in Section 2.1.3 Geometry Point Attributes KFtoCO – Kilofeet to Central Office - <double> - The measurement of the

distance to the central office in kilofeet. PairSize – Number of pairs - <long integer> - Number of pairs/fibers entering the device.

Subtypes Not applicable Relationships One-to-Many relationship to the Complements table. Notes

2.4.2 DigitalCrossConnect A Digital Cross Connect is a patch panel for copper cables that are used to provide digital service. Fibers in cables are connected to signal ports in this equipment. Ports are not shown graphically within ArcGIS, therefore these are modeled using a relationship to the DXCPort Object (database only features). Copper pairs (complements) are not shown graphically within ArcGIS, therefore these are modeled using a relationship to the Complement Object (database only features).

Class Name DigitalCrossConnect Type Feature class, Simple Junction Inherits From TelecomJunction Geometry Point Attributes InputPorts – Input Ports - <long integer> - Number of input ports.

OutputPorts – Output Ports - <long integer> - Number of output ports. MountType – Mount Type- <long integer> - Type of Mount. Uses the MountType domain.

Subtypes Not applicable Relationships One-to-Many relationship to the Complements table.

Composite, One-to-many relationship to the DXCPort table.

Page 20: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

15

Notes

2.4.3 DigitalLoopCarrier A DigitalLoopCarrier (DLC) is a device that multiplexes an optical signal in to multiple lower level digital signals. Fibers in cables are connected to signal ports in this equipment. Ports are not shown graphically within ArcGIS; therefore these are modeled using a relationship to the DLCPort Object (database only features).

Class Name DigitalLoopCarrier Type Feature class, Simple Junction Inherits From TelecomJunction Geometry Point Attributes InputPorts – Input Ports - <long integer> - Number of input ports.

OutputPorts – Output Ports - <long integer> - Number of output ports. Subtypes Not applicable Relationships Composite, one-to-many relationship to the DLCPort table. Notes

2.4.4 FiberInterconnect A FiberInterconnect terminates individual fibers or establishes a connection between two or more fiber cables. Fibers in cables are connected to signal ports in the equipment. Ports are not shown graphically within ArcGIS; therefore these are modeled using a relationship to the FICPort Object (database only features).

Class Name DigitalCrossConnect Type Feature class, Simple Junction Inherits From TelecomJunction Geometry Point Attributes InputPorts – Input Ports - <long integer> - Number of input ports.

OutputPort – Output Ports - <long integer> - Number of output ports. MountType – Mount Type- <long integer> - Type of Mount. Uses the MountType domain.

Subtypes Not applicable Relationships Composite, one-to-Many relationship to the FICPort table. Notes

2.4.5 LoadCoil A Load Coil is a copper line conditioning equipment. Standard voice phone calls degrade noticeably when the copper portion of a phone line is greater than 18 kilofeet long. In order to restore call quality, load coils are inserted at specific intervals along the loop. Copper pairs (complements) are not shown graphically within ArcGIS; therefore

Page 21: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

16

these are modeled using a relationship to the Complement Object (database only features).

Class Name LoadCoil Type Feature class, Simple Junction Inherits From TelecomJunction Geometry Point Attributes LoadCoilType – Load Coil Type - <text, 20> - The type of Load Coil.

KFtoCO – Kilofeet to Central Office - <double> - The measurement of the distance to the central office in kilofeet. PairSize – Number of pairs - <long integer> - Number of pairs/fibers entering the device.

Subtypes Not applicable Relationships One-to-Many relationship to the Complements table. Notes

2.4.6 MainDistributionFrame A Main Distribution Frame is often found at the local exchange (Central Office) and is used to terminate the copper cables running from the customer's site. The frame allows these cables to be cross connected using patch cords to other equipment such as a concentrator or switch.

Class Name MainDistributionFrame Type Feature class, Simple Junction Inherits From TelecomJunction Geometry Point Attributes MountType – Mount Type- <long integer> - Type of Mount. Uses the

MountType domain. Capacity – Capacity - <long integer> - The capacity of the Frame. NumberOfBlocks – Number of Blocks – <long integer> - The number of blocks found in the Frame. PinsPerBlock – Pins Per Block – <long integer> - The number of pins per block found in the Frame.

Subtypes Not applicable Relationships Not applicable Notes

Page 22: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

17

2.4.7 Multiplexer A Multiplexer (MUX) is a device that combines multiple inputs into an aggregate signal to be transported via a single transmission channel. Fibers in cables are connected to signal ports in this equipment. Ports are not shown graphically within ArcGIS, therefore these are modeled using a relationship to the MUXPort Object (database only features).

Class Name Multiplexer Type Feature class, Simple Junction Inherits From TelecomJunction Geometry Point Attributes InputPorts – Input Ports - <long integer> - Number of input ports.

OutputPort – Output Ports - <long integer> - Number of output ports. MUXType – Multiplexer Type - <long integer> - Whether the multiplexer is synchronous or asynchronous. Uses the MUXType domain.

Subtypes Not applicable Relationships Composite, one-to-Many relationship to the MUXPort table. Notes

2.4.8 OpticalRepeater An Optical Repeater is a device that receives an optical signal, amplifies it (or, in the case of a digital signal, reshapes, retimes, or otherwise reconstructs it), and retransmits it as an optical signal. Fibers in cables are connected to signal ports in this equipment. Ports are not shown graphically within ArcGIS; therefore these are modeled using a relationship to the OptRptrPort Object (database only features).

Class Name OpticalRepeater Type Feature class, Simple Junction Inherits From TelecomJunction Geometry Point Attributes InputPorts – Input Ports - <long integer> - Number of input ports.

OutputPort – Output Ports - <long integer> - Number of output ports. Subtypes Not applicable Relationships Composite, one-to-Many relationship to the OptRptrPort table. Notes

2.4.9 PatchPanel A Patch Panel is device where connections are made between incoming and outgoing fibers. Fibers in cables are connected to signal ports in this equipment. Ports are not shown graphically within ArcGIS; therefore these are modeled using a relationship to the PatchPanelPort Object (database only features).

Class Name PatchPanel Type Feature class, Simple Junction Inherits From TelecomJunction

Page 23: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

18

Geometry Point Attributes InputPorts – Input Ports - <long integer> - Number of input ports.

OutputPort – Output Ports - <long integer> - Number of output ports. MountType – Mount Type- <long integer> - Type of Mount. Uses the MountType domain.

Subtypes Not applicable Relationships Composite, one-to-Many relationship to the PatchPanelPort table. Notes

2.4.10 SpliceClosure A usually weatherproof encasement, commonly made of tough plastic, that envelops the exposed area between spliced cables, i.e., where the jackets have been removed to expose the individual transmission media, optical or metallic, to be joined. The closure usually contains some device or means to maintain continuity of the tensile strength members of the cables involved, and also may maintain electrical continuity of metallic armor, and/or provide external connectivity to such armor for electrical grounding. In the case of fiber optic cables, it also contains a splice organizer to facilitate the splicing process and protect the exposed fibers from mechanical damage. In addition to the seals at its seams and points of cable entry, the splice closure may be filled with an encapsulate to further retard the entry of water.

Class Name SpliceClosure Type Feature class, Simple Junction Inherits From TelecomJunction Geometry Point Attributes SpliceNumber – Splice Number - <text, 20> - The number of splices in

the splice closure. SpliceType – Splice Type - <long integer> - Type of Splice, whether Elastomeric, Fusion, etc. Uses the SpliceType domain. PlacementType – Placement Type - <long integer> - The type of placement as in aerial, underground, etc. Uses the PlacementType domain.

Subtypes Not applicable Relationships Not applicable Notes

2.4.11 Splitter A Splitter is a transmission coupling device for separately sampling (through a known coupling loss) either the forward (incident) or the backward (reflected) wave in a transmission line. Fibers in cables are connected to signal ports in this equipment. Ports are not shown graphically within ArcGIS; therefore these are modeled using a relationship to the SplitterPort Object (database only features).

Page 24: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

19

Class Name Splitter

Type Feature class, Simple Junction Inherits From TelecomJunction Geometry Point Attributes InputPorts – Input Ports - <long integer> - Number of input ports.

OutputPort – Output Ports - <long integer> - Number of output ports. MountType – Mount Type- <long integer> - Type of Mount. Uses the MountType domain. Ratio – Ratio - <long integer> - Ratio of Splitter. Uses the SplitterRatios domain.

Subtypes Not applicable Relationships Composite, one-to-Many relationship to the SplitterPort table. Notes

2.4.12 Terminal Terminals are in-loop plant hardware, specifically designed to facilitate connection and removal of distribution cable, drop or service wire to and from cable pairs at a particular location. Terminals are a class of equipment that establishes the end point of a section of the transmission network between the CO and the customer. Copper pairs (complements) are not shown graphically within ArcGIS; therefore these are modeled using a relationship to the Complement Object (database only features).

Class Name Terminal Type Feature class, Simple Junction Inherits From TelecomJunction Geometry Point Attributes TerminalType – Terminal Type - <long integer> - The type of terminal –

fixed, ready access or cross connect. Uses the TerminalType domain. NumOfPairs – Number of Pairs - <long integer> - Total number of copper pairs for the Terminal. KFtoCO – Kilofeet to Central Office - <double> - The measurement of the distance to the central office in kilofeet. TaperCode - Taper Code - <text, 20> – The taper code of the terminal. RFTDate – RFT Date- <date> - Ready for traffice date for the terminal. NumOfPairsIn – Number of Pairs In - <long integer> - Number of pairs/fibers entering the Terminal. NumOfPairsOut - Number of Pairs Out - <long integer> - Number of pairs/fibers originating at the Terminal. CarrierZone – Carrier Zone - <long integer> - The carrier zone of the terminal. ResistanceZone – Resistance Zone - <long integer> - The resistance zone of the terminal.

Subtypes Not applicable Relationships One-to-Many relationship to the Complements table. Notes

Page 25: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

20

2.4.13 Termination Terminations are a generic feature class for the end points of cables. These may be considered similar to service drops to buildings.

Class Name Terminal Type Feature class, Simple Junction Inherits From TelecomJunction Geometry Point Attributes TerminationType – Termination Type - <long integer> - The type of

termination – ONT or OLT. Uses the TerminationType domain. MountType – Mount Type- <long integer> - Type of Mount. Uses the MountType domain.

Subtypes Not applicable Relationships Not applicable Notes

2.5 Object Classes This section includes all of Object Classes within the model. In a geodatabase, object classes are collections of nonspatial data of the same type or theme. While spatial objects (features) are stored in feature classes in a geodatabase, nonspatial objects are stored in object class tables.

2.5.1 TelecomObject TelecomObject is an abstract class whose attributes are inherited by all object classes in the model, either directly or through another abstract class. The following table provides information regarding the TelecomObject abstract class, with attributes, aliases, data types and descriptions

Class Name TelecomObject Type Object class Inherits From Object Geometry Not applicable Attributes IPID – Item of Plant ID - <long integer> - The unique identifier for the Plant

ID system. IPIDFKey – IPID of Related Asset (fk)- <long integer> - The foreign key attribute containing the IPID value for the related class. Comments – Comments - <text, 100> - User or Designer Comments

Subtypes Not applicable Relationships Not applicable

Notes

Page 26: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

21

2.5.2 Attachment Attachments are cables that are attached to the pole.

Class Name Attachment Type Object class Inherits From TelecomObject Geometry Not applicable Attributes AttachmentID – Attachment ID – <long integer> - The unique identifier for

the attachment. AttachmentDate – Attachment Date - <date> - Date the attachment was added to the pole. AttachmentHeight – Attachment Height - <long integer> - The height of the attachment. StrandSize – Strand Size - <long integer> - The size of the strand. Uses the StrandSizes domain. HasBond – Has Bond - <text, 5> - Uses the Yes/No Indicator domain. Owner – Owner - <text, 20> - Owner of the attachment. Uses the Foreign Attachment Owner domain.

Subtypes Not applicable Relationships Composite, many-to-one relationship to the Pole feature class. Notes

2.5.3 BufferTube Buffer Tubes or bundles are groups of fibers bound together, typically at the ends only, and encased in a flexible protective jacket. The inside diameter of the protective jacket of a bundle is typically larger than the minimum outside diameter of the combined fibers. This allows the fibers to move freely inside of the jacket.

Class Name BufferTube Type Object class Inherits From TelecomObject Geometry Not applicable Attributes BufferID – Buffer ID - <long integer> - The unique ID of the Buffer tube.

The primary key in the relationship to the Fiber table. FiberCableID – FiberCable ID - <long integer> - The unique ID of the FiberCable. The foreign key in the relationship to the FiberCable feature class. BufferColor – Buffer Color - <long integer> - The color of the Buffer tube. Uses the FiberBufferColors domain. NumberOfFibers – Number of Fibers - <long integer> - The number of fibers in the Buffer Tube. Uses the NumberOfFibers domain.

Subtypes Not applicable Relationships Many-to-one relationship to FiberCable

Composite, one-to-many relationship to Fiber. Notes

Page 27: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

22

2.5.4 Complements Complements are a subset of the total numbers of copper pairs in a cable.

Class Name Complements Type Object class Inherits From TelecomObject Geometry Not applicable Attributes LowPair – Low Pair - <long integer> - Low copper pair number.

HighPair – High Pair - <long integer> - High copper pair number. Source – Source - <text, 30> - The source of the copper pairs.

Subtypes Not applicable Relationships Many-to-one relationship to CopperCable

Many-to-one relationship to CopperRepeater Many-to-one relationship to LoadCoil Many-to-one relationship to DigitalCrossConnect Many-to-one relationship to Terminal

Notes

2.5.5 DuctObject DuctObject is an abstract class whose attributes are inherited by the Innerduct and Duct object classes in the model. The following table provides information regarding the DuctObject abstract class, with attributes, aliases, data types and descriptions.

Class Name DuctObject Type Abstract class Inherits From TelecomObject Geometry Not applicable Attributes Owner – Owner - <text, 20> - The owner of the DuctObject.

Manufacturer – Manufacturer - <text, 20> - Manufacturer of the DuctObject feature. PartNumber – Part Number - <text, 20> - DuctObject part number. Material – Material - <long integer> - The type of duct material. Uses the ConduitMaterial domain. MaterialCost – Material Cost - <double> - The estimated cost of the material. Diameter – Diameter - <double> - The diameter of the DuctObject. CalculatedLength – Calculated Length – <double> - The calculated length of the conduit segment. MeasuredLength – Measured Length - <double> - The code for the measured length of the conduit segment. Uses the MeasuredLength range domain is applied constraining between 1 – 10,000. AccountCode – Account Code - <text, 20> - The Account Code which the Conduit is referenced. InstallationDate – Installation Date - <date> - The date of installation.

Subtypes Not applicable Relationships Not applicable

Page 28: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

23

Notes

2.5.6 Duct A Duct is a linear object which belongs to the structural network. It is contained inside of a Conduit. Duct(s) are modeled as non-graphic objects.

Class Name Duct Type Object class Inherits From TelecomObject Geometry Not applicable Attributes ConduitID – Conduit ID - <long integer> - The unique Conduit ID.

DuctID – Duct ID - <long integer> - The unique DuctID.

DuctNumber – Duct Number - <long integer> - Number of Duct objects participating in the Conduit.

Subtypes Not applicable Relationships Many-to-one relationship to Conduit.

Composite, one-to-many relationship to Innerduct. One-to-many relationship to FiberCable One-to-many relationship to CopperCable

Notes

2.5.7 Innerduct An Innerduct is a linear object which belongs to the structural network. It is contained inside of a Duct. Innerduct(s) are modeled as non-graphic objects.

Class Name Innerduct Type Object class Inherits From TelecomObject Geometry Not applicable Attributes DuctID – Duct ID - <long integer> - The unique Duct ID (Is this the same

as the IPID)?

InnerductID – Innerduct ID - <long integer> - The unique Innerduct ID

InnerductNumber – Number of Innerducts - <long integer> - Number of Innerduct objects participating in the Duct.

Subtypes Not applicable Relationships Many-to-one relationship to Duct

One-to-many relationship to FiberCable One-to-many relationship to CopperCable

Notes

Page 29: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

24

2.5.8 Fiber An optical fiber is a thin filament of glass that is used to transmit voice, data, or video signals in the form of light energy (typically in pulses).

Class Name Fiber Type Object class Inherits From TelecomObject Geometry Not applicable Attributes BufferID – Buffer ID - <long integer> - Unique Buffer ID, the foreign key in

the relationship to the BufferTube table.

FiberID – Fiber ID - <long integer> - Unique identifier for the Fiber record.

FiberNumber – Fiber Number - <long integer> - The number of fiber strands.

FiberColor - Fiber Color - <long integer> - The color of the fiber. Uses the FiberBufferColors domain.

FiberMode - Fiber Mode - <long integer> - The mode of the fiber – single, multi, dispersion shifted, etc. Uses the FiberMode domain.

FiberStatus – Fiber Status - <long integer> - The condition of the fiber. Uses the FiberStatus domain.

Bandwidth – Bandwidth - <long integer> - Bandwidth capacity..

OpticalLength – Optical Length - <long integer> - The optical length of the fiber.

Attenuation – Attenuation - <text, 20> - The attenuation of the fiber.

Subtypes Not applicable Relationships Many-to-one relationship to BufferTube Notes

2.5.9 Location A location is typically wince customer address or other facility item of plant where a specific add

Class Name Location Type Object class Inherits From TelecomObject Geometry Not applicable Attributes AddressNumber – Address Number - <text, 10> – The street address

number. StreetName – Street Name - <text, 25> – The street name in the address. Prefix – Prefix - <text, 10> – The prefix for the street name in the address. Suffix – Suffix – <text, 10> – The suffix for the street name in the address. City – City - <text, 15> – The city name in the address. State – State - <text, 2> – The state in the address.

Page 30: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

25

ZipCode – Zip Code - <text, 10> – The zip code of the address. FloorNumber – Floor Number - <short integer> - The floor number in the address. AptNumber – Apartment Number - <text, 10> – The zip code of the address. PlaceName – Place Name – <text, 10> – The place name of the address.

Subtypes Not applicable Relationships One-to-One relationship to the Terminal feature class. Notes

2.5.10 Maintenance Loop A maintenance loop is a coil of slack fiber cable that is used to support future splicing or other maintenance activities.

Class Name MaintenanceLoop Type Object class Inherits From TelecomObject Geometry Not applicable Attributes LoopID – Loop ID - <long integer> - The unique identifier for the

maintenance loop. Length – Length - <double> - The length of the maintenance loop.

Subtypes Not applicable Relationships Many-to-one relationship to the FiberCable feature class. Notes

2.5.11 PortObject PortObject is an abstract class whose attributes are inherited by the Port object classes in the model. The following table provides information regarding the DuctObject abstract class, with attributes, aliases, data types and descriptions.

Class Name PortObject Type Abstract class Inherits From TelecomObject Geometry Not applicable Attributes PortID – Port ID - <long integer> - The unique Port ID.

PortLabel – Port Label - <text, 20> - The port label. PortType - Port Type - <text, 20> - The port type – input or output. Uses the PortType domain.

Subtypes Not applicable Relationships Not applicable Notes

Page 31: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

26

2.5.12 DLCPort A Port connection point at which signals can enter or leave the equipment. A Port is modeled as a non-graphical Object. DLCPort is an object class which provides port storage for the DigitalLoopCarrier feature class.

Class Name DLCPort Type Object class Inherits From PortObject Geometry Not applicable Attributes Not applicable. All attributes are inherited from the PortObject abstract

class. Subtypes Not applicable Relationships Many-to-one relationship to DigitalLoopCarrier. Notes

2.5.13 DXCPort A Port connection point at which signals can enter or leave the equipment. A Port is modeled as a non-graphical Object. DXCPort is an object class which provides port storage for the DigitalCrossConnect feature class.

Class Name DXCPort Type Object class Inherits From PortObject Geometry Not applicable Attributes Not applicable. All attributes are inherited from the PortObject abstract

class. Subtypes Not applicable Relationships Many-to-one relationship to DigitalCrossConnect. Notes

2.5.14 FICPort A Port connection point at which signals can enter or leave the equipment. A Port is modeled as a non-graphical Object. FICPort is an object class which provides port storage for the FiberInterconnect feature class.

Class Name FICPort Type Object class Inherits From PortObject Geometry Not applicable Attributes Not applicable. All attributes are inherited from the PortObject abstract

class. Subtypes Not applicable Relationships Many-to-one relationship to FiberInterconnect. Notes

Page 32: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

27

2.5.15 MUXPort A Port connection point at which signals can enter or leave the equipment. A Port is modeled as a non-graphical Object. MUXPort is an object class which provides port storage for the Multiplexer feature class.

Class Name MUXPort Type Object class Inherits From PortObject Geometry Not applicable Attributes Not applicable. All attributes are inherited from the PortObject abstract

class. Subtypes Not applicable Relationships Many-to-one relationship to Multiplexer. Notes

2.5.16 OptRptrPort A Port connection point at which signals can enter or leave the equipment. A Port is modeled as a non-graphical Object. OptRptrPort is an object class which provides port storage for the OpticalRepeater feature class.

Class Name OptRptrPort Type Object class Inherits From PortObject Geometry Not applicable Attributes Not applicable. All attributes are inherited from the PortObject abstract

class.

Subtypes Not applicable Relationships Many-to-one relationship to OpticalRepeater. Notes

2.5.17 PatchPanelPort A Port connection point at which signals can enter or leave the equipment. A Port is modeled as a non-graphical Object. PatchPanelPort is an object class which provides port storage for the PatchPanel feature class.

Class Name PatchPanelPort Type Object class Inherits From PortObject Geometry Not applicable Attributes Not applicable. All attributes are inherited from the PortObject abstract

class.

Subtypes Not applicable Relationships Many-to-one relationship to PatchPanel. Notes

Page 33: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

28

2.5.18 SplitterPort A Port connection point at which signals can enter or leave the equipment. A Port is modeled as a non-graphical Object. SplitterPort is an object class which provides port storage for the Splitter feature class.

Class Name SplitterPort Type Object class Inherits From PortObject Geometry Not applicable Attributes Not applicable. All attributes are inherited from the PortObject abstract

class. Subtypes Not applicable Relationships Many-to-one relationship to Splitter.

Notes

Page 34: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

29

3.0 Data Model Domains and Relationships

3.1 Domains This section is comprised of the data model domains. Domains offer a way to define a range of values that can be used for multiple attribute fields. Using domains helps ensure data integrity by limiting the choice of values for a particular field. Validation for coded value domains is accomplished by restricting the user to choose field values from a dropdown list. Range domains are automatically validated during editing.

3.1.1 AnchorRodType Provides options for the type of Anchor Rod. Used with the AnchorGuy.RodType attribute.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value SingleEye 1 DoubleEye 2

3.1.2 AnchorType Provides options for the type of Anchor. Used with the AnchorGuy.AnchorType attribute.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value Cone 1 Expanding 2 Log 3 Plate 4 Screw 5

Page 35: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

30

3.1.3 Assembly Framing Type Provides options for the type of Pole Top Assembly.

Domain Type Coded Values Field Type Text Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value A Frame A H Frame H Single Pole SP Other OTH

3.1.4 Assembly Framing Type Provides options for the type of Pole Assembly. NOTE: This domain has not been assigned to any attribute.

Domain Type Coded Values Field Type Text Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value A Frame A H Frame H Single Pole SP Other OTH

3.1.5 Availability Indicator Provides options for availability. NOTE: This domain has not been assigned to any attribute.

Domain Type Coded Values Field Type Text Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value Unavailable 0

Page 36: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

31

Available 1

3.1.6 CableCoreType Provides options for the type of cable. Used with the FiberCable.CoreType attribute.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value Metallic 1 NonMetallic 2

3.1.7 ConduitMaterial Provides options for the type of Anchor. Used with the Coduit.Material, Duct.Material, and Innerduct.Material attributes.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Default Value Domain Members: Name Value HDPE 1 PVC 2 SplitHDPE 3 SplitPVC 4 BlackIronPipe 5 BlackSteelPipe 6 CastIronPipe 7 ClaySewerPipe 8 FlexDuct 9 SteelCasing 10 TerraCotta 11 Wood 12 Quad 13 Unknown 14 NotApplicable 15

Page 37: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

32

3.1.8 EnabledDomain Provides options for determined whether the Junction Feature is enabled, and will allow flow and tracing through it when participating in a geometric network. Used with all Junction features which inherit the Enabled attribute from the NetworkFeature class.

Domain Type Coded Values Field Type Small Integer Merge Policy Default Value Split Policy Default Value Domain Members: Name Value FALSE 0 TRUE 1

3.1.9 FiberBufferColors Provides options for the type of color for Fiber. Used with the BufferTube.BufferColor, and Fiber.FiberColor attributes.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value Blue 1 Orange 2 Green 3 Brown 4 Slate 5 White 6 Red 7 Black 8 Yellow 9 Violet 10 Rose 11 Aqua 12

Page 38: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

33

3.1.10 FiberMode Provides options for the type of color for Fiber. Used with the Fiber.FiberMode attribute.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value SingleMode 1 MultiMode 2 DispersionShiftedFiber 3 LightwaveShiftedFiber 4 Hybrid 5 Unknown 6

3.1.11 FibersPerBuffer Provides options for Fibers per Buffer. Used with the BufferTube.NumberOfFibers attribute.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value 6 1 12 2

3.1.12 FiberStatus Provides options for the condition of the Fiber. Used with the Fiber.FiberStatus attribute.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value Available 1 Dark 2

Page 39: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

34

Broken 3 DeadToField 4 InUse 5 Unknown 6

3.1.13 Foreign Attachment Owner Provides options for the condition of the Fiber. Used with the Fiber.FiberStatus attribute.

Domain Type Coded Values Field Type Text Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value Telephone 1 Cable 2 Foreign Utility 3 Other 4

3.1.14 GuyMaterial Provides options for the material of the Guy wire. Used with the AnchorGuy.WireMaterial attribute.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value Steel 1 Other 2

3.1.15 GuyRatingType Provides options for the condition of the Fiber. Used with the Fiber.FiberStatus attribute.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Duplicate Domain Members:

Page 40: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

35

Name Value Common 1 ExtraHighStrength 2 HighStrength 3 UtilityGrade 4

3.1.16 Measured Length Provides range limits for the Measure Length. Used with the MeasuredLength attribute on the following classes: Conduit, CopperCable, FiberCable, Duct, Innerduct and Span.

Domain Type Range domain Field Type Integer Merge Policy Sum Values Split Policy Geometry Ratio Domain Members: Name Value MinValue 1 MaxValue 10000

3.1.17 MountType Provides options for the type of mounting. Used with the MountType attribute on the following classes: DigitalCrossConnect, FiberInterconnect, MainDistributionFrame, PatchPanel and Splitter.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value Wall 1 Rack 2 Unknown 3

3.1.18 MUXType Provides options for the type of Multiplexer. Used with the

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Duplicate

Page 41: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

36

Domain Members: Name Value Synchronous 1 Asynchronous 2

3.1.19 NumberOfBuffers Provides options for the condition of the Fiber. Used with the FiberCable.NumberOfBuffers attribute.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value 1 1 2 2 3 3 4 4 5 5 6 6 8 7 10 8 12 9

3.1.20 NumberOfFibers Provides options for the Number of Fibers in the FiberCable. Used with the FiberCable.NumberOfBuffers attribute.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value 12 1 24 2 36 3 48 4 60 5 72 6

Page 42: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

37

84 7 96 8 108 9 120 11 132 12 144 13

3.1.21 PlacementType Provides options for the placement of the feature. Used with the CopperCable.NumberOfPairs attribute.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value Aerial 1 DirectBuried 2 Underground 3 Indoor 4

3.1.22 NumberOfCopperPairs Provides options for the number of copper pairs in CobberCable. Used with the CopperCable.NumberOfPairs attribute.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value 7 1 14 2 28 3 56 4 112 5 224 6 448 7 896 8

Page 43: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

38

3.1.23 PoleClass Provides options for the class of pole. Used with the Pole.Class and PushBrace.PBClass attributes.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Default Value Domain Members: Name Value 1 1 2 2 3 3 4 4 5 5 6 6 7 7 8 8 9 9 10 10 H1 11 H2 12 H3 13 H4 14 Unknown 15

3.1.24 Pole Foundation Type Provides options for the type of the pole foundation. Used with the Pole.FoundationType attribute.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value Set Extra Deep In Earth 1 Set Normally In Earth 2 Set Normal With Concrete Backfill

3

Set On Concrete Foundation 4 Other 5

Page 44: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

39

3.1.25 PoleHeight Provides options for the height of pole. Used with the Pole.Height and PushBrace.Height attributes.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Default Value Domain Members: Name Value 20' 1 25' 2 30' 3 35' 4 40' 5 45' 6 50' 7 55' 8 60' 9 65' 10 70' 11 75' 12 80' 13 85' 14 90' 15 95' 16 Greater than 95' 17

3.1.26 PoleMaterial Provides options for the material of pole. Used by the Pole.Material and PushBrace.PBMaterial attributes.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Default Value Domain Members: Name Value Wood 1 Aluminum 2 Concrete 3 Steel 4

Page 45: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

40

Fiberglass 5 Composite 6 Other 7 Unkown 8

3.1.27 PoleTreatmentType Provides options for the treatment type of the pole. Used with the Pole.TreatmentType attribute.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Default Value Domain Members: Name Value Creosote 1 Paint 2 Penta 3 ChromatedCopperArsenates 4 Other 5 CopperNaphthenate 6 None 7 Unknown 8

3.1.28 PortType Provides options for the type of Port. Used with the PortType attribute on the following object classes: DLCPort, DXCPort, FICPort, MuxPort, OptRptrPort, PatchPanelPort and SplitterPort.

Domain Type Coded Values Field Type Text Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value Input 1 Output 2

Page 46: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

41

3.1.29 RiserMaterial Provides options for the type of the material for the Riser. Used with the Riser.RiserMaterial attribute.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Default Value Domain Members: Name Value Sch40PVC 1 Sch60PVC 2 Steel 3 Fiberglass 4 Other 5

3.1.30 SpliceType Provides options for the type of the SpliceClosure. Used with the SpliceClosure.SpliceType attribute.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value Elastomeric 1 Fusion 2 Mechnical 3 Rotary 4 PassThru 5 Unknown 6

3.1.31 SplitterRatios Provides options for the ratios on Splitter. Used with the Splitter.Ratio.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Default Value Domain Members:

Page 47: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

42

Name Value 1x2 1 1x4 2 1x3 3 1x5 4 1x6 5 1x7 6 1x8 7 1x9 8 1x10 9 1x11 10 1x12 11 1x13 12 1x14 13 1x15 14 1x16 15 1x32 16

3.1.32 StrandSizes Provides options for the size of wire strands. Used with the AnchorGuy.WireSize and Attachment.StrandSize attributes.

Domain Type Coded Values Field Type Integer Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value 6M 1 6.6M 2 10M 3 16M 4 25M 5

3.1.33 TerminalType Provides options for the type of Terminal. Used with the Terminal.TerminalType attribute.

Domain Type Coded Values Field Type Integer Merge Policy Default Value

Page 48: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

43

Split Policy Duplicate Domain Members: Name Value Fixed 1 ReadyAccess 2 CrossConnect 3

3.1.34 ULS Size Provides options for the size of the ULS size. NOTE: This is not used within the model for any attributes.

Domain Type Coded Values Field Type Text Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value 2" 2 5" 5 10" 10

3.1.35 Yes/No Indicator Provides a Yes or No option. Used with the Attachment.HasBond, Pole.Grounded and Pole.HasRiser attributes.

Domain Type Coded Values Field Type Text Merge Policy Default Value Split Policy Duplicate Domain Members: Name Value No N Yes Y

3.1.36 TerminationType Provides options for the type of Termination. Used with the Termination.TerminationType attribute.

Domain Type Coded Values Field Type Integer Merge Policy Default Value

Page 49: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

44

Split Policy Default Value Domain Members: Name Value ONT 1 OLT 2

Page 50: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

45

3.2 Relationships This section is comprised of the data model relationships. Relationships provide an association or link between two objects in a geodatabase. Relationships can exist between spatial objects (features in feature classes), between nonspatial objects (rows in a table), or between spatial and nonspatial objects.

3.2.1 BufferTubeContainsFiber Composite Yes Cardinality One To Many Notification Forward Attributed No Origin Destination ObjectClass BufferTube Fiber Key BufferID (Origin Primary Key) BufferID (Origin Foreign Key) Labels BufferTubes Fibers

3.2.2 CableHasComplements Composite No Cardinality One To Many Notification None Attributed No Origin Destination ObjectClass CopperCable Complements Key IPID (Origin Primary Key) IPIDFKey (Origin Foreign

Key) Labels CopperCable Complements

3.2.3 ConduitHasCopperCable Composite No Cardinality One To Many Notification Forward Attributed No Origin Destination ObjectClass Conduit CopperCable Key IPID (Origin Primary Key) ConduitID (Origin Foreign

Key)

Page 51: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

46

Labels Conduit CopperCable

3.2.4 ConduitHasDuct Composite Yes Cardinality One To Many Notification Forward Attributed No Origin Destination ObjectClass Conduit Duct Key IPID (Origin Primary Key) ConduitID (Origin Foreign

Key) Labels Conduit Duct

3.2.5 ConduitHasFiberCable Composite No Cardinality One To Many Notification Forward Attributed No Origin Destination ObjectClass Conduit FiberCable Key IPID (Origin Primary Key) ConduitID (Origin Foreign

Key) Labels Conduit FiberCable

3.2.6 Conduit_Structure Composite No Cardinality Many To Many Notification Forward Attributed ConduitIPID (Origin Foreign Key)

StructureIPID (Destination Foreign Key) Origin Destination ObjectClass Conduit Structure Key IPID (Origin Primary Key) IPID (Origin Foreign Key) Labels Conduit Structure

3.2.7 CopperRepeaterHasComplements

Page 52: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

47

Composite No Cardinality One To Many Notification None Attributed No Origin Destination ObjectClass CopperRepeater Complements Key IPID (Origin Primary Key) IPIDFKey (Origin Foreign

Key) Labels CopperRepeater Complements

3.2.8 DCCHasComplements Composite No Cardinality One To Many Notification None Attributed No Origin Destination ObjectClass DigitalCrossConnect Complements Key IPID (Origin Primary Key) IPIDFKey (Origin Foreign

Key) Labels DigitalCrossConnect Complements

3.2.9 DCCHasPorts Composite Yes Cardinality One To Many Notification Forward Attributed No Origin Destination ObjectClass DigitalCrossConnect DXCPort Key IPID (Origin Primary Key) IPIDFKey (Origin Foreign

Key) Labels DigitalCrossConnect DCCPort

3.2.10 DLCHasPorts Composite Yes Cardinality One To Many Notification Forward Attributed No Origin Destination

Page 53: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

48

ObjectClass DigitalLoopCarrier DLCPort Key IPID (Origin Primary Key) IPIDFKey (Origin Foreign

Key) Labels DigitalLoopCarrier DLCPort

3.2.11 DuctHasCopperCable Composite Yes Cardinality One To Many Notification Forward Attributed No Origin Destination ObjectClass Duct CopperCable Key IPID (Origin Primary Key) DuctID (Origin Foreign Key) Labels Duct CopperCable

3.2.12 DuctHasFiberCable Composite Yes Cardinality One To Many Notification Forward Attributed No Origin Destination ObjectClass Duct FiberCable Key IPID (Origin Primary Key) DuctID (Origin Foreign Key) Labels Duct FiberCable

3.2.13 DuctHasInnerduct Composite Yes Cardinality One To Many Notification Forward Attributed No Origin Destination ObjectClass Duct Innerduct Key IPID (Origin Primary Key) DuctID (Origin Foreign Key) Labels Duct Innerduct

Page 54: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

49

3.2.14 FiberCableHasBufferTube Composite Yes Cardinality One To Many Notification Forward Attributed No Origin Destination ObjectClass FiberCable BufferTube Key IPID (Origin Primary Key) IPID (Origin Foreign Key) Labels FiberCable BufferTubes

3.2.15 FIberCableHasMaintLoop Composite Yes Cardinality One To Many Notification Forward Attributed No Origin Destination ObjectClass FiberCable MaintenanceLoop Key IPID (Origin Primary Key) IPID (Origin Foreign Key) Labels FIberCable MaintenanceLoop

3.2.16 FICHasPorts Composite Yes Cardinality One To Many Notification Forward Attributed No Origin Destination ObjectClass FiberInterconnect FICPort Key IPID (Origin Primary Key) IPIDFKey (Origin Foreign

Key) Labels FiberInterconnect FicPort

3.2.17 InnerductHasCopperCable Composite No Cardinality One To Many Notification Forward Attributed No

Page 55: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

50

Origin Destination ObjectClass Innerduct CopperCable Key IPID (Origin Primary Key) InnerductID (Origin Foreign

Key) Labels Innerduct CopperCable

3.2.18 InnerductHasFiberCable Composite No Cardinality One To Many Notification Forward Attributed No Origin Destination ObjectClass Innerduct FiberCable Key IPID (Origin Primary Key) InnerductID (Origin Foreign

Key) Labels Innerduct FiberCable

3.2.19 LoadCoilHasComplements Composite No Cardinality One To Many Notification None Attributed No Origin Destination ObjectClass LoadCoil Complements Key IPID (Origin Primary Key) IPIDFKey (Origin Foreign

Key) Labels LoadCoil Complements

3.2.20 MuxHasPorts Composite Yes Cardinality One To Many Notification Forward Attributed No Origin Destination ObjectClass Multiplexer MuxPort Key IPID (Origin Primary Key) IPIDFKey (Origin Foreign

Key) Labels Multiplexer MuxPort

Page 56: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

51

3.2.21 OPTRHasPorts Composite Yes Cardinality One To Many Notification Forward Attributed No Origin Destination ObjectClass OpticalRepeater OptRptrPort Key IPID (Origin Primary Key) IPIDFKey (Origin Foreign

Key) Labels OpticalRepeater OptRptrPort

3.2.22 PatchPanelHasPorts Composite Yes Cardinality One To Many Notification Forward Attributed No Origin Destination ObjectClass PatchPanel PatchPanelPort Key IPID (Origin Primary Key) IPIDFKey (Origin Foreign

Key) Labels PatchPanel PatchPanelPort

3.2.23 PoleHasAttachment Composite Yes Cardinality One To Many Notification Forward Attributed No Origin Destination ObjectClass Pole Attachment Key IPID (Origin Primary Key) IPIDFKey (Origin Foreign

Key) Labels Pole Attachments

3.2.24 SpanHasFiberCable Composite No

Page 57: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

52

Cardinality One To Many Notification Forward Attributed No Origin Destination ObjectClass Span FiberCable Key IPID (Origin Primary Key) SpanID (Origin Foreign Key) Labels Span FiberCable

3.2.25 SpanHasConduit Composite No Cardinality One To Many Notification Forward Attributed No Origin Destination ObjectClass Span Conduit Key IPID (Origin Primary Key) SpanID (Origin Foreign Key) Labels Span Conduit

3.2.26 SplitterHasPorts Composite Yes Cardinality One To Many Notification Forward Attributed No Origin Destination ObjectClass Splitter SplitterPort Key IPID (Origin Primary Key) IPIDFKey (Origin Foreign

Key) Labels Splitter SplitterPort

3.2.27 TerminalHasComplements Composite No Cardinality One To Many Notification None Attributed No Origin Destination ObjectClass Terminal Complements Key IPID (Origin Primary Key) IPIDFKey (Origin Foreign

Page 58: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

53

Key) Labels Terminal Complements

3.2.28 TerminalHasLocation Composite No Cardinality One To One Notification None Attributed No Origin Destination ObjectClass Terminal Location Key IPID (Origin Primary Key) IPIDFKey (Origin Foreign

Key) Labels Terminal Location

Page 59: 32365888 ArcGIS Telecom Data Dictionary

ArcGIS Telecom Data Model – Data Dictionary

54

Appendix A – ArcGIS Data Types The following are the data types which are supported by ArcGIS, as referenced in the ArcGIS online help system.

Name Specific range, length, or format

Size (Bytes)

Applications

Short integer -32,768 to 32,767 2 numeric values without fractional values within specific range; coded values

Long integer -2,147,483,648 to 2,147,483,647

4 numeric values without fractional values within specific range

Single precision floating point number (Float)

approximately

-3.4E38 to 1.2E38

4 numeric values with fractional values within specific range

Double precision floating point number (Double)

approximately -2.2E308 to 1.8E308

8 numeric values with fractional values within specific range

Text up to 64,000 characters varies names or other textual qualities

Date mm/dd/yyyy hh:mm:ss A/PM

8 date and/or time

BLOB varies varies images or other multimedia

GUID 36 characters enclosed in curly brackets

16 or 38 customized applications requiring global identifiers