← Operator library Fiber Operations

Plan an FTTH GPON Deployment from Demand to Acceptance

Turn customer demand into feeder, splitter, PON, OLT and installation plans with optical and capacity evidence.

What this note covers

Turn customer demand into feeder, splitter, PON, OLT and installation plans with optical and capacity evidence.

Design the service and the plant together

FTTH deployment fails when commercial maps, passive plant records and OLT capacity are planned separately. A viable build connects demand, route permissions, fiber counts, splitter locations, optical budget, PON loading, uplinks, installation standards and restoration stock.

Demand

Forecast premises, take rate, packages and growth by service area.

Plant

Document ducts, poles, closures, splitters, splices and reserve fibers.

Capacity

Engineer PON and aggregation for busy-hour traffic and failures.

Acceptance

Measure every path and preserve as-built evidence.

Convert demand into service areas

Use premises and route data rather than broad population totals. Define feeder and distribution boundaries that can be built, maintained and expanded.

Reserve fibers and ports for growth, enterprise services and restoration. Maximum splitter ratio is not automatically the economical design.

Calculate optical and traffic budgets

Add fiber attenuation, connectors, splices, splitters, engineering margin and aging against transmitter and receiver classes. Validate with loss testing after construction.

Model busy-hour demand per PON, OLT uplink and aggregation path. Include a link or card failure rather than planning only the normal state.

Make as-built data a deliverable

Record cable, fiber, splice tray, splitter input/output, OLT port, ONU serial and customer location with stable identifiers. Photographs supplement, not replace, structured records.

Define installation tests, labeling, bend control, connector cleaning and exception approval before contractors start.

Operational caution: Never accept a route merely because ONUs register; poor cleaning, undocumented splices and missing margin can create intermittent faults after handover.

Evidence before rollout

Signal Required proof
Demand model Premises, take rate and growth connect to port demand.
Optical budget Worst path retains documented margin.
Capacity PON and uplinks meet busy-hour and failure policy.
As-built Every service traces through splitter and splice records.
Acceptance Measured loss and installation evidence pass thresholds.

Put the plan into operation

  1. Survey. Validate demand, routes, permits and existing assets.
  2. Design. Create plant, optical and capacity plans.
  3. Procure. Standardize compatible parts and restoration stock.
  4. Build. Control labeling, splicing and change records.
  5. Test. Measure and reconcile against design.
  6. Activate. Pilot services before area-wide migration.

The decision standard

An FTTH area is complete when commercial inventory and as-built plant agree, every optical path has margin, shared capacity meets policy and a field team can locate and restore faults without reconstructing the network.

Research basis: ITU-T G.984 series; ITU-T L-series outside-plant guidance; Broadband Forum architecture publications. Validate implementation details against the releases, contracts, and local regulations governing your network.

Continue with ISPbills

Put this guide into practice