Poorly documented fiber optic network: how much does it cost your operation?
Quick answer: A poorly documented fiber optic network is costly because it generates repeated technical visits, rework on projects, slower repairs, SLA penalties, cancellations, and damage to infrastructure. In a simulation with modest assumptions, this waste reaches R$ 54,000 per year, not counting penalties, cancellations, and idle capacity.
Every fiber optic operation begins with organized plans and designs, but as the network grows, it receives splices, new customers, and emergency repairs, and record-keeping rarely keeps pace. When the backlog accumulates, the company ends up operating a poorly documented fiber network, with information scattered across spreadsheets, outdated maps, and the memories of older technicians.
The problem is that this wear and tear almost never appears as a separate line item in the budget. It gets diluted in repeated visits to the same pole, in projects redone after on-site inspection, in service calls that take longer than they should, and in work that affects cables that nobody knew were there.
For service providers, municipalities, and infrastructure teams, identifying these expenses is the first step toward recovering them. After all, how much is your operation already paying for documentation that even your own team doesn't trust?
In this article, you will see:
What characterizes a poorly documented fiber optic network?
A poorly documented fiber optic network often has abundant records, such as blueprints, spreadsheets, KMZ files, and fusion diagrams, that either differ from each other or do not reflect what is actually installed in the field. Generally, there is no shortage of documentation. What is lacking is trust in it: the records fail to fulfill their purpose when the technician needs to verify the information before taking action.
The most common signs are:
- Dependence on individuals: the team calls the most experienced colleague before opening a splice box because the log doesn't show which fibers are in use.
- Competing versions: two or more versions of the same plant circulate at the same time, and nobody knows which one is valid.
- Customers without a physical connection: active customers will not have their splitter port registered.
- "Orphan" sections: sections built by third parties or inherited in acquisitions that never had a survey of what was actually installed.
A Sobralnet, A provider operating in more than 25 cities in Ceará, describes this scenario in a case study published with OZmap. Before the migration, the company relied on shared spreadsheets, lacked a visual merge diagram, and maintained sections built by third parties without adequate documentation. According to the infrastructure coordinator, because different people were working with different versions, it sometimes seemed as if a cable had disappeared.
Why does documentation lose reliability over time?
The documentation becomes outdated because the network changes faster than the registration process. Every activation, fusion maneuver, splitter replacement, or emergency repair alters the topology, and updating the registration depends on someone remembering to do it after a long day in the field. When closing the work order doesn't require this step, the gap between the map and the network widens every week.
Expansion and acquisitions worsen the situation because each new region arrives with its own naming and registration standards. Without a single registration model, the company accumulates parallel databases that only those who created them can interpret.
Where does the cost appear in the routine of the operation?
The cost is spread across five areas that are generally measured separately. Therefore, the final cost is usually higher than it seems:
Area | How the cost appears | Affected indicator |
Corrective maintenance | Fault location by trial and error, extra displacements | Mean time to repair (MTTR) |
Projects and feasibility | On-site conference before approving expansions, wrong material purchase. | Activation timeframe, construction cost |
Works by third parties | Cables damaged, relocations required. | Repair costs, affected customers |
Service and SLA | Longer calls, fines and credits | Average handling time (AHT), churn |
Network capacity | Fiber optic connections and free ports that are not listed in the registry. | Unnecessary Capex |
Slower corrective maintenance and unproductive travel.
Without a reliable diagram, the team locates the fault through trial and error, and a network outage is the scenario where the lack of documentation costs the most per minute. Sobralnet's account describes this scenario: previously, technicians would go to the point of impact (POP) for OTDR testing and only then go to the correct point of the outage. With the network documented on the platform, the analysis began to take place before the team left, and The coordinator estimated an improvement of approximately 80% in treatment time.
Each extra trip adds technical hours, mileage, vehicle wear and tear, and, most importantly, customer downtime, linking maintenance costs to service costs.
Rework in projects, expansions, and technical feasibility.
Before approving a feasibility study or designing an expansion, the designer needs to know which fibers are free, how many ports remain on the splitter, and how much technical reserve exists in each section. If the data doesn't provide a reliable answer, someone goes to the site to check, and the project is stalled until they receive the information. This downtime is rarely included in the accounting, but it repeats with each study.
Having a reliable database also improves budgeting, as new projects benefit from automatic material take-offs, including technical reserves, making costs more predictable. Without this precision, the company tends to buy excess cable and boxes or discover material shortages mid-project.
Damage to the network due to construction work and interference from third parties.
Public works and utility projects frequently damage power lines when the network's location is not accurately recorded. The owner of the asset bears the cost of the damage, needing to repair the section, restore service, and assist affected customers.
O Decree No. 10.480/2020, The law that regulates the General Antenna Law also plays a role in this calculation.
- when a public infrastructure project requires the removal or relocation of a telecommunications network, The network owner pays for the service;
- he needs to present, within 15 days of notification, a proposal with terms and deadlines;
- if you fail to meet the deadline you set, reimburses costs and damages and is responsible for service interruptions.
To provide a credible answer, the company needs to know where each segment is located and how many customers depend on it.
Customer service, SLA, and cancellation risk.
When information is stored in spreadsheets or in the minds of specific technicians, each call requires further investigation, putting pressure on indicators such as average response time and average repair time. In contracts with SLAs, longer repairs can result in credit or penalties. The customer notices the delay but doesn't see the underlying technical complexity, and recurring dissatisfaction fuels cancellations.
Idle capacity and assets that no one knows where to find.
Free fiber optic cables, empty splitter ports, and unregistered technical reserves are equivalent to idle capital. The company launches a new cable to serve a region where capacity was already available, simply because no one could prove it, and the opposite also happens with assets that exist on the street but are not registered, such as deactivated cables and old occupations on utility poles.
According to Abradee, cited in Poder360 report, Brazil has approximately 53 million utility poles, with 19,000 telecommunications companies operating on them, and only 4,000 of these companies have contracts with the distributors. Those who don't know what they have installed tend to have more difficulty negotiating or regularizing their occupancy.
How do you estimate the cost in your own operation?
Estimating this cost doesn't require a sophisticated tool, just disciplined record-keeping over a few weeks. The process has three steps:
Step 1: Which variables to consider
For 60 to 90 days, mark on service requests and work orders any instances where an extra visit, rework, or waiting time was required due to missing or incorrect information. For each occurrence, record four groups of data:
- Technical hours: The additional time spent in the field, in the office, and in customer service, multiplied by the hourly cost of each function.
- Displacement: Mileage and fuel costs, in addition to wear and tear and vehicle downtime, if applicable.
- Materials: Items purchased in duplicate, lost, or used in repairs that could have been avoided.
- Penalties and commercial losses: Fines and credits for SLA non-compliance, plus cancellations associated with long-term failures.
Damage to third-party works is considered separately, in cases where the operation has already experienced any incident.
Step 2: Apply the formula
Monthly cost = (overtime × cost per hour) + (extra kilometers × cost per kilometer) + wasted materials + fines and SLA credits
Step 3: Calculation example (simulation)
Attention: the values below are hypothetical and serve only to illustrate the logic of the calculation. They do not represent the market average.
Imagine a provider with 40 field incidents per month, where 25% require an extra visit due to incorrect information, resulting in 10 visits. Each visit consumes two people for three hours, or six technical hours at R$ 45 each, plus 60 km of travel at R$ 1.20 per kilometer. In the project sector, the same company analyzes 12 feasibility studies per month and spends two additional hours of verification on each one, also at R$ 45 per hour.
Component | Illustrative premise | Monthly cost |
Extra field visits | 10 visits × (6 h × R$ 45 + 60 km × R$ 1.20) | R$ 3.420 |
Extra conference on projects | 12 studies × 2 h × R$ 45 | R$ 1.080 |
Total | R$ 4,500 (R$ 54,000 per year) |
With modest assumptions, the total comes to R$ 54,000 per year, And the calculation doesn't yet include SLA penalties, damage to construction work, cancellations, or idle capacity. By replacing the hypothetical numbers with data from the operation itself, the result becomes more reliable than any external average.
Step 4: Use the calculator with the data from your operation.
Doing this calculation in a spreadsheet works, but it's time-consuming and it's easy to forget a variable. That's why we created a... interactive calculator It does the math for you. Simply enter your field occurrences, the cost per hour of technical work, average travel time, and the volume of feasibility studies. The tool then shows you:
- The monthly and annual cost of missing documentation on your network;
- How much does each area weigh (field, projects, SLA)?;
- How much would you save by reducing extra visits and conferences?.
What changes for public agencies and public works departments?
In the public sector, the cost of flawed documentation manifests itself in other ways, but follows the same logic. Public works departments that plan interventions without knowing what exists underground or on utility poles face rework, duplicate surveys, service interruptions, and corrective expenses. Urban network control.
Decree No. 10,480/2020 establishes two important obligations:
- Integrated planning: the planning of public infrastructure projects must consider the installation of telecommunications networks, under the conditions established by the decree. This also applies to state and municipal projects financed at least half by federal voluntary transfers.
- Georeferenced registration: the network owner must inform Anatel of the technical characteristics and geographic coordinates of their infrastructure.
In practice, both the planning agency and the company occupying the road need georeferenced and compatible registrations.
According to Poder360, a 2020 report by Anatel pointed out 10 million utility poles in critical condition requiring organization., ...and the sharing rules remain in regulatory dispute. On October 6, 2026, Aneel withdrew the joint resolution with Anatel from the agenda to negotiate points of divergence. Whatever the outcome, municipalities and operators with a georeferenced inventory of who occupies each pole or duct tend to be better prepared for any regularization process.
How does OZmap help reduce these costs?
OZmap is a fiber optic network documentation and management platform that brings together all the infrastructure on a georeferenced map. Reducing the costs of a poorly documented network requires that the right information be available at the moment of decision-making, whether in the field, in the office, or at customer service, and that's where OZmap comes in.
Georeferenced mapping and centralization of information.
In OZmap, cables, poles, boxes, splitters, and splices are represented on the map, allowing for a visual and integrated overview of the infrastructure. It's fiber optic network mapping that replaces loose spreadsheets with a single source of truth.
At Sobralnet, all you had to do was click on a box to see the number of connected clients, the installed splitters, and the merge diagram—data that was previously displayed in text. The case study reports a reduction in fusion and mapping errors from 70% to 80%. The result also depends on the process of each operation, since the company took advantage of the migration to verify the data in the field before entering it into the system.
For public managers, this same centralization enables the georeferencing of network assets, the recording of changes, and the maintenance of a history of interventions. To learn more, you can access our article on the subject. Urban network control.
Up-to-date documentation accessible in the field, office, and customer service areas.
Field access via the app OZmob This changes the technician's routine, eliminating the need to rely on printed maps and textual descriptions. In case of a break, the OTDR via OZmob allows locating the affected section, facilitating the identification of upstream and downstream boxes, verification of available fibers, and planning the cable installation.
Integrations with other systems, such as ERPs, CRMs, etc., allow for the automation of information exchange and the optimization of operational processes, such as importing customer data and opening splitter ports.
Support for expansion planning and decision-making.
With a well-organized foundation, planning is no longer based on assumptions, and for providers considering selling the company, acquiring another, or undergoing audits, structured documentation also contributes to the value of the business. Returning to the simulation, each extra visit avoided and each feasibility study resolved in-house represents a direct saving, which adds to the gain in predictability.
As Should we start organizing the fiber network documentation?
Adopting a platform does not replace the work of organizing information, and the process usually follows five steps:
- To uncover what already exists. Gather blueprints, spreadsheets, KMZ files, and field records, classifying each source by degree of confidence.
- Define a registration standard. Establish the nomenclature for boxes and cables, the minimum attributes of each asset, and the versioning rules, so that the entire team records in the same way.
- Prioritize critical areas. Regions with many customers, recurring incidents, planned construction, or poles with irregular occupation tend to provide a faster response time.
- Validate in the field and correct. Check the most important data before migrating it, as Sobralnet did by taking advantage of the implementation to review the entire network.
- Create an update routine. Link the closing of each service order to the change being recorded in the database.
Following this roadmap transforms fiber optic network documentation into an ongoing process, not a project that becomes outdated as soon as it's finished.
Frequently Asked Questions (FAQ)
How much does it cost to maintain a poorly documented fiber optic network?
It depends on the size of the operation, but the cost accumulates in extra visits, rework on projects, slower repairs, SLA penalties, cancellations, and damage to works. In a simulation with modest assumptions, the expense reaches R$ 4,500 per month, or R$ 54,000 per year, not counting penalties and cancellations.
How can I tell if my fiber network is poorly documented?
The clearest signs are technicians who need to call colleagues before opening a splice box, multiple versions of the same plant circulating, active clients without a registered splitter port, and inherited or outsourced sections without surveys.
Is there a calculator to estimate this cost?
Yes. OZmap's free calculator uses your operational data (field occurrences, technical hours, travel, and feasibility studies) and shows the monthly and annual cost of missing documentation, broken down by area.
Where do you even begin when documenting a fiber optic network?
Start by gathering all existing data sources, define a single registration standard, prioritize critical areas, validate data in the field before migrating it, and link the closing of each service order to the database update.
Who pays for the relocation of fiber optic networks in public works projects?
According to Decree No. 10,480/2020, the owner of the network pays for the removal or relocation required by public works and must submit a proposal with conditions and deadlines within 15 days of notification.
Does a mapping platform solve the problem on its own?
No. The platform centralizes and georeferences the information, but the result depends on validating the data in the field during migration and maintaining an update routine linked to work orders.
Conclusion
The cost of a poorly documented fiber optic network rarely arrives in a single bill, and therefore takes time to be noticed. It accumulates with each visit that could have been avoided, each project checked twice, and each construction site that finds a network that no one registered. Measuring this value over a few weeks can reveal a larger bill than expected: in the simulation in this article, modest values turned into... R$ 54,000 per year.
Documenting the network costs less than operating it without reference, and the gains increase when the same version of the information reaches the technician, the designer, the service representative, and the public manager at the moment of decision-making. If your team is already dealing with conflicting spreadsheets and unnecessary travel, it's worth learning how... OZmap Organizes documentation in a georeferenced environment.
Ready to stop paying for a network that nobody can read? Talk to a specialist and see OZmap applied to the reality of your provider or your municipality.
