FTTH design and commercial readiness
FTTH network design for high-rise buildings: turn floor readiness into revenue
A tower concentrates demand. It also concentrates dependencies: a shared riser, a locked equipment room, a limited installation window or an unresolved penetration detail can hold up many customer connections at once.
Executive answer: Approve the building architecture, but release sales and installation commitments at unit and floor level. A unit is serviceable when its accepted optical path, available serving capacity, apartment drop route and authorized installation access are all confirmed.
The tradeoff is explicit: shared infrastructure can reduce equipment and construction duplication, while making access problems and cable failures affect more customers. Design for expansion and fault isolation, then fund the operating arrangements that make those features usable.
The design decision is where to share, and where to isolate
FTTH network design for high-rise buildings should cover the complete path from building entry to the resident’s optical network terminal (ONT). Start with a physical survey and a demand plan by floor. Do not infer usable riser space, spare pathways or equipment access from a building’s height.
| Choice | Potential advantage | Tradeoff and evidence needed |
|---|---|---|
| Centralized splitting with dedicated floor or unit fibers | Consolidates splitter access and allocation at a managed location. | May require more riser fibers and pathway space. Validate actual cable dimensions, routing and installation limits. |
| Distributed splitting near floor groups | Can reduce the number of feeder fibers carried through parts of the riser. | Adds distributed equipment and access dependencies. Calculate total splitting loss and identify which units share each element. |
| Reserved capacity for later connections | Can avoid reopening finished areas as adoption grows. | Uses space and capital before revenue arrives. Reserve identified fibers, terminal ports and feasible pathways against a documented demand scenario. |
No universal splitter ratio or floor-terminal interval fits every tower. Validate the selected PON system’s optical class, splitter losses, fiber length, connector and splice allowances, engineering margin and both maximum-loss and minimum-loss constraints. Then verify the installed path against the approved acceptance plan.
The FOA installation standard, issued October 2025, covers support infrastructure, cable handling limits, premises fire stopping, testing and documentation. Apply it alongside the project’s equipment specifications and applicable local requirements.
Clearfield’s July 2026 MDU installation guidance emphasizes surveying the building, determining run lengths and verifying local fire codes. This is vendor guidance, not an independent cost benchmark. The practical implication is to prove the route before choosing an installation method.
Failure scenario: the fiber is installed, but the floor cannot launch
Consider a hypothetical 20-floor residential tower with 12 apartments per floor. Sales accepts orders after the basement equipment is commissioned. Installers then discover that the nineteenth-floor cabinet requires an escort available only on Thursday mornings. On the seventeenth floor, approval of the completed fire-stopping work remains unresolved. Four residents on the eighteenth floor have not agreed to apartment access.
The tower contains 240 potential addresses. That does not establish 240 connectable units. Unqualified appointments create wasted visits, longer order queues and pressure to discount a service that the customer has not yet received.
A second risk remains after activation: multiple floors can depend on one cable segment, splice enclosure or feeder. Record the affected customers for each shared element, including access arrangements for emergency restoration. Two cables in the same shaft may share the same physical hazard and access restriction; their presence alone does not demonstrate route diversity.
The evidence Network, Sales and the CEO need before approval
CNO: a maintainable path
- Survey riser occupancy, cable support, vertical installation limits and expansion space.
- Approve floor distribution, apartment drops, bend management and accessible service loops.
- Confirm cable classification and penetration treatment under applicable fire requirements.
- Trace every serving port through labels, splice records and unit IDs.
- Retain optical acceptance results and isolate shared failure domains.
CSO: a deliverable order
- Publish eligible units, available ports and unresolved restrictions.
- Agree permitted working hours, escorts, lift bookings and resident notices.
- Confirm apartment access before assigning a crew.
- Use appointment capacity to set activation commitments.
- Assign ownership for blocked orders and communicate the next confirmed action.
CEO: credible contribution
- Review investment against occupied, serviceable units and realistic adoption.
- Include building charges, revenue share and recurring access costs.
- Price repeat mobilization and missed appointments.
- Assess concentrated outage exposure and feasible mitigation.
- Approve funding and launch scope against evidence, not total apartment count.
Fire requirements are jurisdiction and building specific. A cable marketed as low-smoke or halogen-free is not automatically acceptable for every riser or escape route. The responsible designer and competent project authority must establish the applicable requirements, approved products, penetration systems and evidence of completed work.
Use a floor readiness map to control the launch
Maintain a unit-level register behind this floor summary. “Connectable” means the unit meets the release checks, not that the resident has placed an order. Available shared capacity must also be sufficient for the released units under the allocation policy.
| Floor | Infrastructure status | Access restriction | Next release action |
|---|---|---|---|
| 20 | Path accepted; ports and unit routes verified. | Tuesday and Thursday, 9 a.m. to noon; lift booking required. | Sales schedules within confirmed crew and lift capacity. |
| 19 | Fiber tests passed; operation access unresolved. | Cabinet escort permission pending. | Building manager confirms authorized access and emergency arrangements. |
| 18 | Floor infrastructure accepted; eight unit paths cleared. | Four apartment access confirmations missing. | Sales coordinator obtains access and releases each remaining unit after checks. |
| 17 | Optical tests passed; penetration acceptance incomplete. | Release held under project acceptance rules. | Project lead obtains competent acceptance of completed fire-stopping work. |
Give each open issue a named owner, evidence reference, next action and review date. An optical pass does not close a civil, safety or access issue. Emergency access should be agreed separately from routine installation hours.
Working example: price the access plan in USD
Compare two ways to complete the same 40 customer installations: dispatch as orders arrive, or batch appointments within verified building access windows. The figures below are illustrative planning inputs, not local quotations or industry benchmarks. Assume both approaches complete the cohort within the same review period.
For a real approval, obtain local quotes with separate rates for a successful installation, an unsuccessful visit and crew mobilization. Specify labor hours, escorts, lift arrangements, parking, materials, applicable taxes and exclusions. Avoid counting the same travel or labor twice.
| Input or calculation | Dispatch as orders arrive | Access-qualified batches |
|---|---|---|
| Successful installations | 40 | 40 |
| Unsuccessful visits | 10 | 4 |
| Total installation visits | 50 | 44 |
| Visit completion rate | 40 ÷ 50 = 80.0% | 40 ÷ 44 = 90.9% |
| Successful work at USD 160 each | USD 6,400 | USD 6,400 |
| Unsuccessful visits at USD 75 each | USD 750 | USD 300 |
| Mobilization at USD 300 per event | 8 × USD 300 = USD 2,400 | 4 × USD 300 = USD 1,200 |
| Total cohort delivery cost | USD 9,550 | USD 7,900 |
| Delivery cost per completed installation | USD 238.75 | USD 197.50 |
The modeled saving is USD 1,650: USD 450 from fewer unsuccessful visits plus USD 1,200 from fewer mobilizations. Successful-work rates exclude unsuccessful visits and separately priced mobilization in this example. Any incremental coordination charge must be deducted from the saving.
The tradeoff is waiting time. Batching is worthwhile only if its savings and reliability justify any delay, staffing cost or additional customer handling. Do not reduce mobilization by postponing promised activations without measuring the consequence.
Suppose 40 billed customers each generate USD 18 monthly contribution after recurring direct service costs and building charges. The cohort contributes 40 × USD 18 = USD 720 per month, before recovering upfront capital. If ten otherwise-ready customers are delayed one full month, the illustrative contribution deferred is USD 180. This is a timing scenario, not guaranteed lost revenue or a customer lifetime value estimate.
Approval gate: what can block a floor launch?
Use a joint release record. The CNO approves technical acceptance, the CSO approves sales eligibility and appointment capacity, and the CEO or delegated investment owner approves funding and commercial exceptions. Building management confirms the permissions it controls. A commercial approver cannot substitute for required technical or safety acceptance.
| Gate | Evidence required | Owner and blocker |
|---|---|---|
| Design approved | Survey, route drawings, capacity allocation, loss budget, shared-failure map and applicable requirements. | CNO. Unverified pathway or incompatible cable specification blocks procurement approval. |
| Infrastructure accepted | Inspection records, approved penetration treatment, labels, as-built records and optical test results. | CNO with competent project reviewers. Unresolved mandatory acceptance blocks service release. |
| Units serviceable | Accepted path to each released unit, available serving capacity and feasible drop installation. | Network release owner. A floor terminal alone does not establish every unit’s eligibility. |
| Appointments deliverable | Resident consent, work windows, escorts, lift capacity and assigned crews. | CSO with building management. Missing access blocks the affected appointment. |
| Commercial case approved | Quoted costs, adoption scenarios, recurring charges and funded operating arrangements. | CEO or delegate. Unsupported contribution assumptions block the investment decision. |
Release an unaffected floor independently only when it has passed its own gates and does not depend on the unresolved shared work. A temporary workaround requires documented authorization under the applicable project rules; a deadline is not evidence of readiness.
Measure delivery after launch, not just homes passed
| Measure | Definition | Decision it supports |
|---|---|---|
| First-visit installation success | Orders completed on their first installation visit ÷ orders receiving a first visit during the review period. | Fix access qualification, tooling or route problems. This differs from the all-visit completion rate in the cost example. |
| Activation time | Median and 90th percentile elapsed time from accepted order to service activation for completed orders; report open-order age separately. | Find long waits hidden by the median. Break out access holds and network holds. |
| Serving-port utilization | Active serving ports ÷ installed usable serving ports, measured at a named network level. | Allocate expansion capacity without confusing floor-terminal ports with OLT PON ports. |
| Restoration | Time from confirmed service impact to restoration, with active customers affected and access delay recorded. | Identify common failure exposure and keyholder delays. Separate restored service from permanent repair closure. |
| Contribution | Billed service revenue less defined recurring direct costs, including applicable building charges; show capital recovery separately. | Compare floors and buildings on consistent cost treatment, not gross revenue alone. |
Define denominators and review periods. Total apartments, occupied eligible units, accepted orders, completed installations and billed customers are different measures. A launch review becomes useful when the team can identify exactly where delivery or value is being lost.
Questions before approving a high-rise FTTH design
Does a signed building agreement make all apartments serviceable?
No. The agreement establishes permission within its terms. Each released unit still needs accepted infrastructure, available capacity, a feasible apartment drop and authorized installation access.
Should every floor have its own splitter?
Not necessarily. Compare centralized and distributed designs using surveyed space, optical limits, expected adoption, access costs and failure exposure. Floor height alone does not determine splitter placement.
What is the most useful launch record?
A unit-level eligibility register summarized by floor, with infrastructure acceptance, connectable units, access restrictions, unresolved issues and responsible owners. It should be the shared source for Network, Sales and building management.
What evidence should a high-rise fiber case study include?
State the building scope, design decision, access constraints, review period and measured outcomes. Separate installed capacity from activated customers and label modeled economics clearly. Obtain permission before publishing customer records, building details or operational results.
Source review: October 4, 2026. The two linked technical sources inform the installation discussion. Readiness maps, release gates and USD calculations are original illustrative planning examples, not reported project results. Final engineering and compliance acceptance remain project specific.