BacksidePort

A patch panel port represents a single object in the real world that is represented as two objects in the database. This configuration makes it much simpler to make connections to the backside of the patch panel and jumpering between ports on the frontside of a patch panel. Separating the information into two tables makes the application code much faster and more robust, without negatively impacting the user interface and workflow process.

Patch panel ports are one of the connection objects in the fiber optic ‘chain of glass’ that comprise circuits in the system. Ports will often define the two ends of a fiber optic circuit, but they also act as intermediate objects in cases where circuits are connected through a patch panel.

Attributes:

Field Name	Field Type	Required field?	Description
PortNumber	long integer	Yes	This field is used to create a relationship between the backside and frontside representations of the same port. It indicates the order the ports will appear in the Connection Manager.
PortName	text	Yes	This field will usually be the same as the PortNumber field. In some cases, an organization may have a unique port naming convention that does not follow a sequential or integer based system. This field allows for these discrepancies in port naming conventions.
PortType	text	Yes	This field stores the connector type that plugs into this port. Examples of port types include SC, ST and FC. The Fiber Port Type domain is assigned to this field.
PortPositionOnCard	long integer	Yes	This field is used by Fiber Manager to hydrate the ports in the proper position on a patch panel card in the application and on reports which use the classic data model. This field uses the standard Fiber Manager position management scheme to determine the correct position of the port on the card. This field allows for multiple rows and columns of ports on the card. NOTE: This is not needed unless you plan to use the classic data model.
PigtailColor	text	No	Many ports will have a factory installed fiber (a pigtail fiber) that extends from the back of the port. This pigtail essentially extends the backside of the port by some distance. This pigtail allows an organization to connect a fiber with a fusion splice. This splice makes a semi-permanent connection with very low optical losses (attenuation). If this pigtail is color coded, then that color can be stored in this field.
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