DevicePort

The DevicePort represents the fiber optic ports within a device. These ports will be used to make connections to individual fiber strands in a fiber optic cable or jumpers to a patch panel port. Jumpers are not individually modeled, but are represented as connections within the Connection Manager. The data model does not support ports in devices that are not used to transmit light in a fiber optic system, such as RJ45 ports.

Attributes:

Field Name

Field Type

Required field?

Description

PortNumber

long integer

Yes

This is the numeric position of the port following the Fiber Manager standard Object Position Rules. These start with the lowest number at the upper left hand corner and then move in a left to right order as each column and row is processed. The value in this field is usually the same as the PortName, but it is not required to be so. If a different or irregular port naming convention is used, then this can be captured with the PortName field.

PortName

text

Yes

This field stores a value that refers to a port. This is typically an integer value (such as Port 18), but it is not required to be so. This field also allows an organization to skip port numbers, if necessary.

PortPositionOnCard

long integer

Yes

This field determines the order in which ports are displayed on a patch panel card. Port Position 1 is the upper left corner and each port is drawn in a ‘typewriter’ order after that, depending on the number of rows and columns on the card. Numbering is explained in more detail in the Fiber Manager Numbering Scheme section.

PortType

text

No

This stores the connector type that is used to plug into the port. Some common values that are stored in this field are SC, ST, FC and LC. The Fiber Port Type domain is assigned to this field.

DemarcationIndicator

long integer

No

This field is used to indicate that a specific port marks a change in ownership between one organization (or internal group) and another. If this value is set to Yes, then the facilities on either side of the port have different owners. The Yes/No domain is assigned to this field. This is not a required field and can be deleted if not useful.

PortFunction

text

No

This field can store the purpose of the port. The standard model lists valid values as primary transmit, primary receive, secondary transmit and secondary receive. These are how the ports are used, but this list can be expanded. For instance, a SONET Network Device may have ports labeled as “In” and “Out.” The Fiber Port Function domain is assigned to this field. This is not a required field and can be deleted if not useful.

GlobalID

GlobalID

Yes

This field contains a unique number (GUID) that is generated and maintained by ArcGIS. This value is used for all relationships in the ArcFM data model and is required for Fiber Manager to function properly.

FiberParent

GUID

Yes

This field contains the GlobalID of the parent object to the current object.

ThisFiberClassModelName

text

Yes

This field stores the class model name assigned to the feature class on which the field resides. It is used in conjunction with the FiberParentClassModelName field to determine the GlobalID that will be placed in the FiberParent field.

FiberParentClassModelName

text

Yes

This field stores the class model name assigned to the feature class that is the parent of the class on which the field resides. It is used in conjunction with the ThisFiberClassModelName field to determine the GlobalID that will be placed in the FiberParent field.

FiberChildClassModelName

text

Yes

This field stores the class model name of a child object to the object on which the field resides.

Common Fields:

  • CreationUser

  • CreationDate

  • LastUser

  • DateModified

QR code for this page

Was this helpful?