In terms of fiber optics, Multiplexing is the combination of multiple frequencies of light over a single fiber strand.  Figure 1 illustrates a Multiplexer (Mux) combining 4 frequencies of light (A-D) into a single fiber strand (represented by the horizontal white line) and a Demultiplexer (DMX) separating those frequencies back into the original components (A-D).

An advantage multiplexing offers telecommunication companies is the significant enhancement of cable bandwidth without having to invest in additional cable infrastructure.  In essence, combining multiple frequencies is the physical, hypothetical equivalent to adding fiber strands to an existing cable.  Laying underground cable is expensive, and there may be rules as to the frequency a road may be dug up for subsurface infrastructure.  Multiplexing offers a viable alternative.

In 2014, Schneider Electric released 10.2.1a that allows Fiber Manager™ to support Wavelength Division Multiplexing (WDM).  SSP was initially hesitant to recommend this upgrade to our existing clients because a tool/procedure had not been released to upgrade existing circuits.  Recently, Schneider released a Circuit Upgrade tool (Figure 2), and we have been successfully upgrading our clients to leverage the new technology.

Can you conduct the upgrade to 10.2.1a without a consultant?

Assuming an OOTB deployment, previous Schneider Electric ArcFM™/Fiber Manager™ upgrades are actually a fairly straight forward endeavor.  Following software removal and subsequent reinstallation, there were a couple of “Magic Buttons” in ArcCatalog to engage, and the system is upgraded.

The upgrade to Fiber Manager™ 10.2.1a is more complex.  In general, Schneider Electric’s Configuration Guide is a good procedural reference, and I am not going to regurgitate what is already present.  The Configuration Guide is not going to teach the user to be a database administrator.  If one is familiar with working with the Fiber Manager™ Flexible Data Model and Geodatabases (i.e., field/table/domain addition, configuration of ArcFM™, etc.), by all means GO FOR IT.  Kick some butt!

If going solo, I suggest and/or remind the following based upon recent successful upgrades:

• If upgrading from an ArcFM™ Version prior to 10.2/10.2.1, upgrade to 10.2.1 prior to making the next jump.  Typically, this upgrade involves only the addition of a few fields to the f_circuit table (plus model name assignment) and Circuit Header designation.  Make sure this intermediate upgrade is properly tested prior to continuing.

• Don’t forget to add the FIBERSTATUS field model name to the status field in the fiber strand object.  Failure to do so, will prevent the Circuit Upgrade Tool from functioning.

• Once the 10.2.1 upgrade has been conducted/tested (if it was necessary) and choosing to incorporate multiplexing feature classes into the model, at least three versioned tables and at least four relationships must be created (Figure 3).  Note that I have said “at least” because the parent feature class or object of the Multiplexer (F_PassiveDevice) can be different based upon the situation.  The F_PassiveDevice table/object can be utilized as a child to multiple fiber objects (i.e., Splice Location, Patch Location, Rack, etc).

• I strongly suggest at least a tertiary data model session between the GIS Administrator and the “Fiber Guy”.  To populate domains with applicable values (i.e., utilized frequencies) and create additional necessary fields, such a meeting would be extremely valuable.

• Plan on utilizing ArcFM™ Favorites with the Location Editor to place Multiplexers in the system.  To do so, I suggest acquisition of the equipment’s manufacture specifications.  The Favorites can be then be appropriately designed.

• Related to Number 2 above.  In previous blog posts, I have written heavily about the use of Fiber Manager™’s Flexible Data Model (see links below) to handle unique situations.  I suggest training on these (or the multiplexing tables) on a “Playground” personal or file geodatabase prior to undertaking in a Production environment.

• Before undertaking an upgrade or conducting database maintenance, make sure a solid backup exist.   The Circuit Upgrade Tool runs well, but is unforgiving with database configuration errors.  Speaking of which….When was the last time the nightly backup was actually restored and tested?  Is it working?  This is a subject for another Post.

In conclusion, conducting this Fiber Manager™ upgrade is like an upgrade and an ArcGIS/ArcFM™ Configuration 101 class wrapped up in one.  Just note that SSP is here to help.