Professional Documents
Culture Documents
Data Dictionary
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.
@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.
ii
ArcGIS Telecom Data Model – Data Dictionary
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
iii
ArcGIS Telecom Data Model – Data Dictionary
iv
ArcGIS Telecom Data Model – Data Dictionary
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
v
ArcGIS Telecom Data Model – Data Dictionary
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.
1
ArcGIS Telecom Data Model – Data Dictionary
Using the review items listed above, the following is the table structure which will be
used to provide information about each class:
Subtypes
Relationships
Notes
2
ArcGIS Telecom Data Model – Data Dictionary
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.
3
ArcGIS Telecom Data Model – Data Dictionary
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.
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.
4
ArcGIS Telecom Data Model – Data Dictionary
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.
5
ArcGIS Telecom Data Model – Data Dictionary
6
ArcGIS Telecom Data Model – Data Dictionary
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.
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.
7
ArcGIS Telecom Data Model – Data Dictionary
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.
8
ArcGIS Telecom Data Model – Data Dictionary
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.
9
ArcGIS Telecom Data Model – Data Dictionary
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.
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.
10
ArcGIS Telecom Data Model – Data Dictionary
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.
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.
11
ArcGIS Telecom Data Model – Data Dictionary
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).
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.
12
ArcGIS Telecom Data Model – Data Dictionary
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
13
ArcGIS Telecom Data Model – Data Dictionary
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).
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).
14
ArcGIS Telecom Data Model – Data Dictionary
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).
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).
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
15
ArcGIS Telecom Data Model – Data Dictionary
these are modeled using a relationship to the Complement Object (database only
features).
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.
16
ArcGIS Telecom Data Model – Data Dictionary
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).
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).
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).
17
ArcGIS Telecom Data Model – Data Dictionary
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.
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).
18
ArcGIS Telecom Data Model – Data Dictionary
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).
19
ArcGIS Telecom Data Model – Data Dictionary
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.
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
Notes
20
ArcGIS Telecom Data Model – Data Dictionary
2.5.2 Attachment
Attachments are cables that are attached to the pole.
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.
21
ArcGIS Telecom Data Model – Data Dictionary
2.5.4 Complements
Complements are a subset of the total numbers of copper pairs in a cable.
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.
22
ArcGIS Telecom Data Model – Data Dictionary
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.
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.
23
ArcGIS Telecom Data Model – Data Dictionary
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).
2.5.9 Location
A location is typically wince customer address or other facility item of plant where a
specific add
24
ArcGIS Telecom Data Model – Data Dictionary
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.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.
25
ArcGIS Telecom Data Model – Data Dictionary
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.
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.
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.
26
ArcGIS Telecom Data Model – Data Dictionary
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.
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.
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.
27
ArcGIS Telecom Data Model – Data Dictionary
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.
Notes
28
ArcGIS Telecom Data Model – Data Dictionary
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.
3.1.2 AnchorType
Provides options for the type of Anchor. Used with the AnchorGuy.AnchorType
attribute.
29
ArcGIS Telecom Data Model – Data Dictionary
30
ArcGIS Telecom Data Model – Data Dictionary
Available 1
3.1.6 CableCoreType
Provides options for the type of cable. Used with the FiberCable.CoreType attribute.
3.1.7 ConduitMaterial
Provides options for the type of Anchor. Used with the Coduit.Material, Duct.Material,
and Innerduct.Material attributes.
31
ArcGIS Telecom Data Model – Data Dictionary
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.
3.1.9 FiberBufferColors
Provides options for the type of color for Fiber. Used with the BufferTube.BufferColor,
and Fiber.FiberColor attributes.
32
ArcGIS Telecom Data Model – Data Dictionary
3.1.10 FiberMode
Provides options for the type of color for Fiber. Used with the Fiber.FiberMode attribute.
3.1.11 FibersPerBuffer
Provides options for Fibers per Buffer. Used with the BufferTube.NumberOfFibers
attribute.
3.1.12 FiberStatus
Provides options for the condition of the Fiber. Used with the Fiber.FiberStatus attribute.
33
ArcGIS Telecom Data Model – Data Dictionary
Broken 3
DeadToField 4
InUse 5
Unknown 6
3.1.14 GuyMaterial
Provides options for the material of the Guy wire. Used with the
AnchorGuy.WireMaterial attribute.
3.1.15 GuyRatingType
Provides options for the condition of the Fiber. Used with the Fiber.FiberStatus attribute.
34
ArcGIS Telecom Data Model – Data Dictionary
Name Value
Common 1
ExtraHighStrength 2
HighStrength 3
UtilityGrade 4
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.
3.1.18 MUXType
Provides options for the type of Multiplexer. Used with the
35
ArcGIS Telecom Data Model – Data Dictionary
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.
3.1.20 NumberOfFibers
Provides options for the Number of Fibers in the FiberCable. Used with the
FiberCable.NumberOfBuffers attribute.
36
ArcGIS Telecom Data Model – Data Dictionary
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.
3.1.22 NumberOfCopperPairs
Provides options for the number of copper pairs in CobberCable. Used with the
CopperCable.NumberOfPairs attribute.
37
ArcGIS Telecom Data Model – Data Dictionary
3.1.23 PoleClass
Provides options for the class of pole. Used with the Pole.Class and PushBrace.PBClass
attributes.
38
ArcGIS Telecom Data Model – Data Dictionary
3.1.25 PoleHeight
Provides options for the height of pole. Used with the Pole.Height and PushBrace.Height
attributes.
3.1.26 PoleMaterial
Provides options for the material of pole. Used by the Pole.Material and
PushBrace.PBMaterial attributes.
39
ArcGIS Telecom Data Model – Data Dictionary
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.
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.
40
ArcGIS Telecom Data Model – Data Dictionary
3.1.29 RiserMaterial
Provides options for the type of the material for the Riser. Used with the
Riser.RiserMaterial attribute.
3.1.30 SpliceType
Provides options for the type of the SpliceClosure. Used with the
SpliceClosure.SpliceType attribute.
3.1.31 SplitterRatios
Provides options for the ratios on Splitter. Used with the Splitter.Ratio.
41
ArcGIS Telecom Data Model – Data Dictionary
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.
3.1.33 TerminalType
Provides options for the type of Terminal. Used with the Terminal.TerminalType
attribute.
42
ArcGIS Telecom Data Model – Data Dictionary
3.1.36 TerminationType
Provides options for the type of Termination. Used with the
Termination.TerminationType attribute.
43
ArcGIS Telecom Data Model – Data Dictionary
44
ArcGIS Telecom Data Model – Data Dictionary
3.2 Relationships
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)
45
ArcGIS Telecom Data Model – Data Dictionary
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
46
ArcGIS Telecom Data Model – Data Dictionary
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
47
ArcGIS Telecom Data Model – Data Dictionary
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
48
ArcGIS Telecom Data Model – Data Dictionary
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
49
ArcGIS Telecom Data Model – Data Dictionary
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
50
ArcGIS Telecom Data Model – Data Dictionary
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
51
ArcGIS Telecom Data Model – Data Dictionary
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
52
ArcGIS Telecom Data Model – Data Dictionary
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
53
ArcGIS Telecom Data Model – Data Dictionary
54