The old way of managing fiber networks doesn’t work anymore. Spreadsheets, static drawings, and handwritten notes fall short when trying to capture details about fast-growing, ever-evolving fiber networks.

I dove into our Fiber Maturity Model several weeks ago in another blog, explaining why it’s so important for fiber network operators to reach Level 3 maturity. In particular, I described the positive business evolution that takes place when fiber operators invest in professional network documentation tools. In this post, I would like to build on that topic and share what happens when you don’t have a reliable system of record (SoR) that can scale with your network.

Investing in a System of Record (SoR) as a means of documenting and managing your fiber network will bring tremendous value to your business but is not to be taken lightly. The implementation of an effective SoR requires internal process changes, may need integration with other systems, and the adoption of new workflows for office and field teams. These changes raise the bar for operational best practices and provide significant opportunities for process improvement and efficiency gains. On top of the internal investments, modern fiber SoRs, like most commercial software these days, are increasingly subscription software applications, requiring a material financial investment when viewed over many years.

It has always been our mission to make OSPInsight the easiest-to-use fiber management platform on the market. We believe this is important not just because it makes individual tasks quicker and simpler for users, but we see it as very strategic to the success of our customers. Software that is easy to use is quickly and widely adopted, enabling rapid productivity gains across the organization and ultimately transforming the business. The release of our Visualization Tools Add-on is another excellent example of how our software is dramatically improving productivity and understanding in a way that has a positive direct impact on business operations.

My father started OSPInsight in a splicing van in 1993. Trained at a defense contractor, he was committed to creating and providing exquisite splicing documentation. Entering the telecom industry, he differentiated himself as a splicing contractor by providing digital splicing documentation years before this was mainstream. These early records eventually developed into OSPInsight, an industry-leading fiber management software platform.

After over 25 years in the fiber network management world, we’ve learned a thing or two about how networks evolve over time and how the needs of operators change along the way.

Fiber operators typically start out documenting their records, fiber data, splices, etc., on paper maps or static spreadsheets. Some come right out of the gates using a geospatial tool, like Google Earth, to build visual representations of their networks. And others work with engineering firms that pass along “as-built” information in the form of pdf CAD drawings.

“Tribal knowledge” is overlooked and underappreciated information that only exists in the minds of key employees. The problem with tribal knowledge is that we often don’t realize how valuable it is until it’s gone. When people with tribal knowledge leave for other pastures they take their insights with them, losing valuable information and forcing others to fill in gaps that they didn’t even know existed.

Every fiber optic network operator needs a mapping software platform.

As the world gears up for 5G, fiber optic cable technology will only become more important for enabling high-speed, long-distance broadband all over the world.

Effective network design and installation are extremely important to the overall success of fiber development projects. However, managing networks on a day-to-day basis requires a different set of skills and resources.

Maintaining clear and accurate documentation is incredibly important when designing a network.

Thorough documentation saves time, money, and resources during installation, as well as enables quick troubleshooting when future network issues arise. Often times, operators overlook the value of project documentation until it’s too late.