Skip to content

FTTH network design • Product readiness

XGS-PON network design: build a service you can deliver and sell

By The Writer ID Team • Published and sources checked
For Chief Network Officers, Chief Sales Officers and Chief Executive Officers

A 10G access network needs a credible product and operational plan. An XGS-PON port creates capacity, but customers buy a package with a price, installation experience, performance expectation and support promise. Design those elements together.

What is XGS-PON network design? It is the planning of a symmetrical 10G-class passive optical access network, including optical terminals, fiber distribution, splitter layout, customer equipment, capacity and service provisioning. A complete design also establishes which packages can be delivered, how installations are accepted and how the investment generates value.

The executive decision: approve a package only when its optical path, busy-hour capacity, premises equipment, installation method and commercial assumptions have passed review. A working optical link alone does not make a product ready to sell.

What the current XGS-PON standard actually gives you

As checked on October 4, 2026, ITU lists the February 2023 edition of Recommendation G.9807.1 and its May 2025 Amendment 1 as in force. XGS-PON has a nominal line rate of 9.95328 Gbit/s in each direction, commonly described as symmetrical 10G.

That rate is shared across the PON and includes protocol overhead. It is neither a dedicated 10 Gbit/s circuit for each subscriber nor a promise about Wi-Fi performance. The basic optical wavelength plan uses 1575 to 1580 nm downstream and 1260 to 1280 nm upstream. Check the selected equipment and coexistence configuration against the applicable plan.

A more recent vendor development reinforces the need to plan evolution: on May 28, 2025, Nokia announced a coexistence solution for 10G, 25G and 50G PON on shared fiber infrastructure. This is a vendor-specific capability, not proof that every deployed OLT or optical distribution network supports the same upgrade path.

OLT = optical line terminal in the access network. ONT = optical network terminal at the customer premises. ODN = optical distribution network, including fiber, splitters, connectors and splices. Standards and dated product announcements are verified facts; the planning examples below are illustrative.

Start with the service promise, then work backward

Define the target customer, downstream and upstream package speeds, expected performance, support scope and price before selecting the full equipment list. Record whether the offer is a shared broadband service or includes committed bandwidth and a service-level agreement. Symmetrical speed alone does not make it equivalent to dedicated internet access.

CNO: verify delivery

Approve optical classes, splitter plans, ONT interoperability, aggregation capacity and provisioning. Identify the customer equipment or operating constraints that could undermine each package.

CSO: qualify the buyer

Find customers whose upload needs, concurrent workloads or transfer volumes justify the offer. Confirm willingness to pay and installation eligibility before forecasting premium conversions.

CEO: test the return

Separate additional contribution, competitive protection and future upgrade savings. Require evidence for each benefit and avoid counting the same value twice.

Which customers are worth qualifying?

Creative studios transferring large project files, households with several concurrent remote workers, and small offices with substantial cloud-backup traffic are reasonable candidates for symmetrical service. They still need qualification: application servers, storage, device interfaces and customer workflows can limit the value of extra access speed.

For multi-gigabit packages, ask what task the customer expects to improve, how often it occurs and whether their equipment can use the capacity. A customer with only 1GbE devices may benefit from aggregate household capacity, but cannot demonstrate a 2 Gbit/s single-device result through a 1GbE connection.

Illustration: the package must work across the full delivery path

XGS-PON service delivery and shared access capacity Traffic moves from upstream services through aggregation and the OLT to a passive splitter. The splitter serves multiple ONTs. One customer’s path continues through their router and device. Capacity and performance must be checked at each stage. Capacity at the OLT is one part of the promise Upstream servicesTransit, peering, applications AggregationCapacity and resilience XGS-PON OLTShared 10G-class access Passive splitter and ODNLoss, split ratio and field condition Customer ONTInteroperability and ports Other ONTsShared PON demand Other ONTsShared PON demand Router and customer deviceRouting, Ethernet, Wi-Fi and storage Installation acceptance checksWired service performance firstWi-Fi coverage assessed separately
Illustration 1. A logical service path, not a prescribed physical topology. A limit in aggregation, the ONT or the home network can prevent the sold package from delivering its intended value.

Design the optical path with measurable acceptance limits

Choose the optical class and splitter layout together. Calculate attenuation at the relevant operating wavelengths, then include component losses, connector and splice allowances, coexistence insertion loss and an engineering reserve. Use manufacturer limits for the actual transmitter and receiver combination.

More splits can reduce access equipment cost per potential connection, but introduce optical loss and concentrate more customers on shared capacity. Fewer splits may improve margin or reduce shared demand, while requiring additional ports and infrastructure. Select the ratio using both optical feasibility and a traffic model.

Illustrative loss-budget worksheet for a proposed 1:32 path
Component Assumed loss Evidence to obtain
Fiber 2.0 dB Route length and attenuation at the operating wavelength.
Splitter 16.8 dB Insertion-loss specification for the selected component.
Connectors 1.2 dB Actual connection count and approved allowance.
Splices 0.4 dB Splice count, workmanship and test records.
Coexistence element, if used 1.0 dB Wavelength-specific insertion-loss specification.
Total estimated path loss 21.4 dB Validate the installed path with appropriate tests.
Engineering reserve 3.0 dB Operator-approved allowance for variation and future work.
Required loss allowance including reserve 24.4 dB Compare with the selected system’s allowable loss.

If the chosen equipment permits 29.0 dB maximum path loss, this hypothetical design has 4.6 dB remaining after the reserve. That arithmetic is a screening check, not an acceptance certificate. Check minimum-loss and receiver-overload limits, upstream and downstream behavior, reflections and the actual installed condition.

All loss figures are assumptions, not universal XGS-PON component specifications. An optical power meter verifies received power; an optical loss test assesses path loss; OTDR measurements help locate events and faults. Plan the appropriate methods and safe test access for the installed network.

Model PON and aggregation capacity separately

The sum of sold package speeds is not a traffic forecast. Neither is nominal PON capacity divided by the number of subscribers a per-customer guarantee. Use representative busy-hour measurements or documented demand assumptions, directional traffic, service commitments and a growth allowance.

For an illustrative 32-customer PON, assume average downstream demand during the modeled busy hour is 120 Mbit/s per active customer. With all 32 included, the average-load estimate is 3.84 Gbit/s. Twelve similarly loaded PONs produce 46.08 Gbit/s at aggregation, before other traffic, overhead or reserve. A single 40 Gbit/s aggregation path cannot carry that assumed combined demand.

Those averages do not establish adequate service quality. Evaluate bursts, upstream traffic, concurrent high-volume transfers, usable capacity after overhead, dynamic bandwidth allocation and queue behavior. Test degraded operation when an uplink or aggregation component fails. Approving enough capacity for the normal state does not prove the resilience promise.

Product gate: a premium package remains blocked if its busy-hour delivery depends on an aggregation upgrade that has not been commissioned. Sales eligibility must follow verified readiness.

Turn XGS-PON capability into qualified packages

Different offers can share the same access technology while requiring different customer equipment and installation procedures. These example tiers illustrate the dependency; they are proposed shared broadband products, not current market tariffs or guaranteed performance claims.

Package design must include premises qualification
Example offer Buyer to qualify Premises requirements Acceptance and disclosure
1 Gbit/s symmetrical Households or small offices with meaningful upstream use. Supported ONT and router, adequate wired links and an assessed Wi-Fi layout. Test with a capable wired device. Disclose that 1GbE application throughput is below its nominal line rate.
2 Gbit/s symmetrical Concurrent work users or customers with qualified transfer needs. At least a suitable 2.5GbE path for a single-device demonstration, including ONT, router and client. Check routed throughput with enabled features. Explain single-device and aggregate-use limits.
5 Gbit/s symmetrical Specialist users who can substantiate demand and equipment readiness. A tested interface path with sufficient headroom, typically 10GbE for demonstrating the full package, plus capable routing and endpoints. Use an appropriately provisioned test server and client. Verify package performance and shared-service terms.

Test routers with the features customers actually use, such as PPPoE, NAT, firewall rules or VPNs. A headline switching specification is not evidence of routed performance under the deployed configuration. For managed Wi-Fi, assess placement, backhaul and device capabilities independently of the wired access result.

XGS-PON product readiness checklist

Complete this checklist separately for each package and serving area. Record the responsible owner, evidence location, software version and approval date. A test from one equipment combination or area should not automatically approve another.

Evidence required before a package is released for sale
Readiness gate Required evidence Approval owner
Optical delivery Approved topology, loss budget, optical class, coexistence requirements and installed test records. Network engineering
Capacity and resilience Busy-hour and growth model; PON, uplink, gateway and transit checks; failure-state assessment. Network planning and operations
ONT and customer equipment Tested OLT/ONT/firmware combinations, interface speeds, routed performance and managed Wi-Fi scope. Engineering and product
Provisioning and billing Order-to-activation test, service profiles, authentication, VLANs, inventory and correct charges. IT/BSS and billing
Installation and recovery Site qualification, required equipment, technician instructions, acceptance tests and recovery procedure. Service delivery and support
Commercial release Qualified segment, approved claims, price, terms, contribution model and verified address eligibility. Sales and Finance, with executive approval

Check your launch approval status

Tick a gate only after its evidence and approval are recorded. This browser checklist helps organize a review; it does not replace technical acceptance. Selections are not stored or sent.







0 of 6 gates recorded. Package release is blocked pending the missing approvals.

Use the evidence table as a manual checklist. Automatic status updates require JavaScript.

Illustration: release the product after the pilot proves delivery

XGS-PON package release with a blocked-launch recovery branch A package definition feeds parallel technical and commercial reviews. They converge at a qualified pilot installation. Failed acceptance blocks release and requires remediation and retesting. Successful acceptance leads to a controlled launch and ongoing performance and contribution monitoring. A package is ready when both reviews agree Define the customer promiseSpeed, scope, equipment, support and price Technical readinessOptics, capacity, equipment, provisioning Commercial readinessDemand, eligibility, terms and contribution Pilot installation and acceptanceService, support, order and billing checks FailPass Block release and remediateRetest the affected configuration Launch in verified areasMonitor performance and billed contribution A sales deadline cannot substitute for a failed acceptance test.
Illustration 2. Technical and commercial approval converge in a representative pilot. Failed acceptance blocks the affected package or area until remediation and retesting are complete.

For each pilot installation, verify optical readings, stable registration, the correct service profile and wired throughput using suitable test endpoints. Test voice, multicast or other included services. Demonstrate the agreed Wi-Fi scope separately, record equipment serial numbers and confirm the order reaches the correct billing state.

Support needs a diagnostic sequence that distinguishes optical faults, provisioning errors, access congestion, router limitations and Wi-Fi complaints. Provide technician escalation contacts, replacement stock and a tested service-recovery procedure. For an upgrade, retain the restoration information needed to return the customer to a working service if acceptance fails.

A USD business case that separates adoption from capacity

Access capacity creates the ability to sell a product; it does not establish demand. Build the commercial model using expected billed customers, package mix, installation cost and contribution after attributable recurring costs. Include revenue share, wholesale access, transit, support, commissions and equipment costs where relevant.

Illustrative new-customer launch scenario, not a tariff benchmark
Assumption Value Implication
Allocated shared investment USD 12,000 Define the actual network scope included.
Installed and billed new customers 24 Orders alone do not establish recurring contribution.
Equipment and installation per customer USD 180 Total connection expenditure: USD 4,320.
19 standard customers USD 45 revenue less USD 25 recurring cost each Monthly contribution: USD 380.
5 premium customers USD 75 revenue less USD 35 recurring cost each Monthly contribution: USD 200.
Total cost and monthly contribution USD 16,320 upfront; USD 580 monthly Simple payback: approximately 28.1 months.

If the same 24 customers all choose the standard package, monthly contribution is USD 480 and simple payback becomes 34.0 months. The network specification has not changed, but the product mix has changed the investment case.

Simple payback = upfront expenditure ÷ monthly contribution.
For existing subscribers, use the incremental contribution caused by the upgrade, rather than counting their entire existing bill as new value.

This example excludes taxes, financing, ramp-up timing, churn and costs not listed. It assumes the stated recurring costs capture the relevant attributable expenditure. Investment approval requires a full cash-flow model and downside scenarios. Competitive protection and future upgrade savings should appear as separate, evidenced benefits.

Measure whether the design becomes a sustainable product

  • Network: optical acceptance failures, busy-hour directional load, queue behavior, service incidents and recovery times.
  • Sales: qualified opportunities, accepted offers, appointment completion and installed-to-billed conversion, tracked by package and cohort.
  • Service delivery: first-visit acceptance, repeat visits, equipment exceptions and Wi-Fi-related callbacks.
  • Finance: contribution per billed customer, realized package mix, installation expenditure and cash-flow performance against plan.

XGS-PON network design questions

What splitter ratio should an XGS-PON network use?

Choose the ratio from the optical budget, geography, customer density, traffic model and expansion plan. A ratio that passes an optical calculation can still create unsuitable shared-capacity or operating conditions.

Can every XGS-PON customer receive 10 Gbit/s?

The PON has a shared nominal line rate of approximately 10 Gbit/s per direction. Customer throughput depends on overhead, concurrent demand, the service profile and equipment across the delivery path. Do not present nominal PON capacity as a dedicated per-customer guarantee.

Does multi-gigabit broadband require new premises equipment?

Often, yes. Qualify ONT ports, router interfaces and routed throughput, cabling and client devices. Existing 1GbE interfaces limit a single wired path, even when the access network has more capacity.

Does XGS-PON guarantee better Wi-Fi?

No. Indoor coverage and wireless performance depend on router placement, radio conditions, backhaul and client capabilities. Validate the wired package and the managed Wi-Fi scope separately.

What should be approved before launch?

Approve optical delivery, capacity and resilience, premises equipment, provisioning and billing, installation and recovery, and the commercial offer. Test the representative service before releasing the package in verified areas.

Evidence and planning method

Sources were checked on October 4, 2026. The linked ITU recommendation page establishes the current standard status; technical rates and wavelength bands were checked against ITU’s G.9807.1 overview. The linked Nokia release establishes the dated vendor announcement. Neither source supplies the commercial forecasts used here.

The product tiers, optical worksheet, capacity assumptions, financial scenario and launch gates are proposed planning examples by The Writer ID Team. They are not operator benchmarks, equipment certifications or reported client results. Use the selected equipment specifications, installed measurements and approved operating procedures for final design acceptance.