Fiber Manager™ Shortcuts

Lasers of Light, Fiber Splice Delight

September 19, 2014 — Brian Higgins

In a previous blog post, we discussed the use of Schneider Electric’s Fiber Manager™ flexible data model to incorporate a Splitter into a splice case.  We have also summarized the construction of an inside plant cable within a Patch Location point.  This blog post will discuss how to incorporate a splice jumper into a splice location.  It will lastly outline a simple configuration change that will enhance the usability of trace reports.

A splice jumper exists within splice cases and connects a strand(s) from one splice tray to a strand(s) in another splice tray.  They are usually composed of a single buffer tube that has been stripped from a fiber optic cable.   Although there are various options, the configuration of the jumper is very similar to an inside plant cable.  Below is a minimum configuration guide for the construction.

Step 1:  Build the tables as illustrated in Figures 1-4.

Figure 1: F_SpliceJumperBufferTube

Figure 2:  F_SpliceJumper

Figure 3:  F_SpliceJumperEndA

Figure 4:  F_SpliceJumperEndB

Step 2: Once these tables are constructed, convert them to ArcFM™ objects.

Step 3:  Assign an Esri default value of “SpliceJumperBufferTube” to the FiberChildClassModelName field of the Slice Point feature class.

Step 4:  Build the following Esri relationships between the parent (listed first) and child (listed second):

  • SpliceLocation (or name of Feature Class) / F_SpliceJumperBufferTube
  • F_SpliceJumperBufferTube / F_SpliceJumper
  • F_SpliceJumper / F_SpliceJumperEndA
  • F_SpliceJumper / F_SpliceJumperEndB
  • F_SpliceJumperEndA / F_SpliceJumperEndB

With the exception of last relationship (F_SpliceJumperEndA/F_SpliceJumperEndB), all relationships are Composite and 1:M.  The Primary Key is the GlobalID field, and the Foreign Key is the FiberParent field.  The F_SpliceJumperEndA / F_SpliceJumperEndB relationship is Simple and 1:1.  This last relationship’s Primary Key is the GlobalID field and the Foreign Key is the ImpliedConnectionSourceGUID field.

Step 5:  With the exception of the last relationship, assign the ArcFM™ AutoUpdater (On Relationship Create) to ArcFM™ Update Fiber Manager™ Field.  There is no AutoUpdater assignment to the F_SpliceJumperEndB / F_SpliceJumperEndA relationship.

Once constructed, ArcFM™ Favorite construction is highly recommended.  Use of the Location Editor Tool (Fiber Manager™ Toolbar) can then by utilized to place jumpers within a pre-existing splice case.  Jumper connections are made via connecting (via Connection Manager) both ends to their designated strands within different splice trays.

Trace Report Enhancement

Inside the out-of-the-box (“OOTB”) Fiber Manager™ data model, the table f_fiberconnectionobject stores all the connection information.  For the most part beyond the standard configuration, this table is mostly ignored.  It is highly advised to never edit this table directly, but we can make a simple configuration change that will enhance trace and circuit reports.

When we run a fiber trace using the standard Minerville configuration (Figure 5), we see the alias (“Connection”) appear three times and the ObjectID of the record containing the information.

Figure 5:  OOTB Trace Reprt

Instead of ObjectID for the ArcFM™ Primary Display Field, it is suggested to change this value to the ContainerClassModelName field (Figure 6).  Once this change is made, the user can then easily as ermine which type of feature is actually present (Figure 7).

Figure 6: Configuration of F_FiberConnectionObject

Figure 7:  Fiber Trace Report with Configuration Change

Lastly, it would be nice if the user could distinguish splice locations by their name or address to determine where they are in the resultant trace.  It is well documented in the ArcFM™ help the addition of certain field model names to get their value added to this and other reports.  In this case, we want to add the address field attribute to the report.  This is conducted by adding the FIBERTRACEREPORT field model name to an Address field for the Splice Case (Figure 8).

Figure 8:  Futher Fiber Trace Report Configuration

The reader is highly encouraged to ask questions, make comments, and/or make suggestions for future fiber blogs.  Without suggestions, you are stuck with what is in my head.   Finally, credit goes to the Starland Vocal Band for the title of this blog from their song Afternoon Delight.

We Wrote the Book

The Indispensible Guide to ArcGIS Online

Download It for Free

Brian Higgins

Solution Architect

What do you think?

Leave a comment, and share your thoughts

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes:

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>


This site uses Akismet to reduce spam. Learn how your comment data is processed.