Understanding the Full Lifecycle
An FTTH project is not a single construction effort — it is a multi-phase programme that transforms a neighborhood from copper-connected to fiber-connected, and each phase has its own technical requirements, its own risks, and its own project controls focus. Understanding the full lifecycle is essential for anyone who wants to manage FTTH programmes effectively, because the controls that matter in one phase are different from the controls that matter in the next.
I have walked through this lifecycle hundreds of times across the STC national rollout, and each phase has taught me something about where to focus attention and where the common pitfalls lie. What follows is a practitioner's walkthrough of the complete FTTH project lifecycle, with the project controls lens applied to each phase.
Phase One: Network Design and Planning
The lifecycle begins not with construction but with design. The network design phase determines where fiber will go, how it will be distributed, and how it will connect to individual homes. This phase includes the demand analysis (which homes to target), the topology design (how to route the fiber from the central office to the neighborhood), the splitter placement (where to locate the passive optical network splitters), and the home connection design (how the drop cable will enter each building).
From a project controls perspective, the design phase is about scope definition. Every design decision has a cost and schedule implication, and those implications must be captured before construction begins. A design that calls for aerial drop cables instead of underground ones may be faster to build but more vulnerable to weather damage over the network's life. A design that places splitters closer to homes reduces fiber length but increases the number of splitter cabinets needed. These trade-offs must be documented and approved before they become construction commitments.
The design phase also produces the bill of materials — the list of every component needed for the build. This feeds directly into the procurement plan and the project budget. A design that uses standard, readily available components is easier to procure than one that requires specialized or single-sourced items. The project controls team should review the bill of materials for supply chain risk before construction begins, not after a critical component turns out to have a twenty-week lead time.
Phase Two: Permitting and Right-of-Way
Before any construction can begin, the programme needs the legal right to dig in public spaces. This is the permitting phase, and in most countries, it is the phase with the most schedule uncertainty. Permits are required from municipalities, utility companies (for crossing their infrastructure), highway authorities (for road crossings), and sometimes private landowners.
The project controls focus during the permitting phase is schedule risk management. Every permit is a milestone with an uncertain completion date. The controls system should track each permit as a discrete item, with a submission date, an expected approval date, and an escalation protocol for when the approval is delayed. The programme should never assume that a permit will be granted on time — it should plan for delays and have contingency plans for how to keep other work moving while a permit is pending.
Phase Three: Civil Works
Civil works is the most visible phase of FTTH construction — it is where the trenches are dug, the ducts are laid, and the ground is restored. This phase is also the most weather-dependent and the most disruptive to the community. Trenching through city streets affects traffic, noise levels, and daily life, and the programme must manage these impacts alongside the construction progress.
The project controls focus during civil works is productivity and quality. Productivity — how many meters of trench are completed per day — drives the schedule. Quality — trench depth, duct installation, backfill compaction — drives the long-term performance of the network. The controls system should track both, and it should flag any site where productivity is high but quality is below standard, because that site will likely require rework that will erase the apparent schedule gain.
Phase Four: Cable Installation
Once the ducts are in place, the fiber cable is pulled through them. This phase requires specialized equipment — cable pulling winches, fiber blowing machines for smaller cables — and skilled technicians who can manage the tension and bending radius of the cable to avoid damage.
The project controls focus during cable installation is material management and damage prevention. Cable is a critical material with a long lead time — running out of cable mid-pull stops the work and may require a new cable pull from the beginning if the remaining cable on the reel is too short. The controls system should track cable inventory by reel, with length remaining, and should trigger reorders before stock falls below the threshold needed to complete the next scheduled pull.
Damage during installation is a quality risk that has schedule implications. A cable that is damaged during pulling must be tested, and if the damage is severe, the cable may need to be replaced — which means a new reel, a new pull, and potentially a delay of days or weeks. The controls system should track damage incidents alongside productivity, because a site with high productivity but frequent damage incidents is not actually progressing well.
Phase Five: Splicing and Termination
Splicing is the most technically demanding phase of FTTH construction. Each fiber must be spliced — fused together with an electric arc — to create a continuous optical path from the central office to the home. A single splice can take five to ten minutes, and a typical FTTH distribution point may have dozens or hundreds of splices.
The project controls focus during splicing is quality and throughput. Every splice must be tested — the insertion loss must be within specification — and the test results must be recorded. The controls system should track splice pass rates by technician, by site, and by splicing machine, because patterns in splice failures often point to equipment problems or training gaps rather than individual technician skill.
Throughput is the other critical metric. Splicing is a bottleneck activity — it cannot be parallelized beyond the number of splicing teams available, and it must be completed before testing and activation can begin. The controls system should track splicing progress against the activation schedule, with enough buffer to absorb the inevitable rework when a splice fails testing.
Phase Six: Testing and Commissioning
Before a site can be activated, the entire optical path must be tested end-to-end. This involves optical time-domain reflectometer (OTDR) testing to verify the fiber's optical characteristics, bit error rate testing to verify signal quality, and often a physical inspection of the connection points.
The project controls focus during testing is defect management. Every test that fails generates a defect that must be resolved before activation. The controls system should track defects by type, by location, and by age — a defect that has been open for two weeks is a different kind of problem from one that was found yesterday. The defect backlog is a leading indicator of activation delays: if the defect backlog is growing faster than the defect resolution rate, the activation schedule is at risk.
Phase Seven: Activation and Handover
The final phase is activation — connecting the optical network terminal (ONT) in the home, verifying the service, and handing over the site to the operations team. This phase is the culmination of all the previous phases, and it is where the programme's investment is converted into a revenue-generating asset.
The project controls focus during activation is milestone tracking and documentation. Every site that is activated must have a complete documentation package — as-built drawings, splice records, test results, and acceptance sign-offs. The controls system should track documentation completeness alongside activation progress, because a site that is activated without complete documentation will cause problems for the operations team for years to come.
The Lifecycle as a System
The most important insight from walking through this lifecycle is that the phases are not independent — they are a system. A design decision in phase one affects the civil works in phase three, the cable installation in phase four, and the splicing in phase five. A quality issue in civil works may not be discovered until testing in phase six. A permit delay in phase two may compress the schedule in phase three, leading to rushed work and quality problems that surface in phase five.
The project controls system must see the lifecycle as a whole, not as a series of independent phases. A dashboard that shows only the current phase's status is missing the connections that matter. The most effective controls systems I have built show the full lifecycle status for each site — design complete, permit approved, civil works 60%, cable 40%, splicing not started, testing not started, activation not started — so that the programme team can see where each site is in its journey and where the bottlenecks are forming.
That is the real art of FTTH project controls: not managing each phase well, but managing the transitions between phases so that the programme flows smoothly from design to activation without accumulating delays, defects, or cost overruns along the way.