If you’re planning fiber internet for a gated community, apartment complex, or township, this guide is for you. We’ve deployed FTTH in 200+ residential buildings across Chhattisgarh, Madhya Pradesh, and Delhi NCR — here’s what we’ve learned.
The Two Models: Dark Fiber vs Active ISP
Before anything else, understand the two deployment models:
Model 1 — Passive (Dark Fiber Infrastructure) The builder or RWA funds the civil works (conduits, fiber cable, ODF/splice closures, fiber patch panels in each flat). The ISP then lights up the fiber on top of this infrastructure. The society owns the passive layer.
Model 2 — Active (ISP-Led Full Deployment) The ISP (like INIC Communications) handles everything end-to-end — survey, civil, fiber, ONU/ONT at each flat, and the active network equipment. The ISP retains ownership of the infrastructure; residents subscribe to plans.
For societies where 60%+ of flats will subscribe, Model 1 gives better long-term flexibility (you can switch ISPs without re-running fiber). For smaller complexes or those in early stages, Model 2 is faster to deploy and has zero capex for the RWA.
The Physical Layer: What Goes Where
A standard FTTH deployment in a residential complex uses a Passive Optical Network (PON) architecture:
OLT (Optical Line Terminal)
→ Feeder fiber (single-mode, G.652D or G.657A2)
→ Optical splitter (1:8 or 1:16 in the optical distribution box)
→ Drop fiber (to each flat)
→ ONU/ONT (at the subscriber's home)
→ Cat5e/Cat6 to the Wi-Fi routerFeeder fiber runs from the OLT (usually in the basement or ground-floor technical room) through the riser shaft to each floor. Drop fiber then breaks out horizontally to individual flats.
The key infrastructure elements:
- OLT — typically 1U rack unit in the NOC room, serves 32–128 subscribers
- Optical Distribution Frame (ODF) — wall-mounted at each floor, houses splices and splitters
- Micro-duct conduit — 7mm or 14mm HDPE ducts run through builder’s trunking
- ONU/ONT — small box inside each flat, powers the last drop
- PoP room — minimum 2×2m with UPS, AC, and your ISP’s uplink termination
Typical Deployment Timeline
| Phase | Duration | What Happens |
|---|---|---|
| Survey & design | 1 week | Site walk, count flats, plan ODF locations, uplink path |
| Civil works | 2–4 weeks | Conduit laying, riser trunking, PoP room setup |
| Cable pulling | 1–2 weeks | Feeder fiber + horizontal drops to each flat |
| Splicing & testing | 3–5 days | OTDR testing, splice closures, ODF termination |
| Active equipment install | 2–3 days | OLT, uplink, ONU provisioning |
| Subscriber activation | Ongoing | Each flat activated as residents subscribe |
Total from survey to first subscriber: typically 4–8 weeks for a 100-unit building, assuming no civil coordination delays.
Common Pitfalls We’ve Seen
1. Inadequate conduit sizing Builders often lay 25mm conduit assuming it’ll be enough. Once you account for fiber, spare capacity, and bending radius, you’re out of space. Minimum recommendation: 40mm HDPE for riser runs, 25mm for horizontal drops in each flat.
2. No dedicated PoP room We’ve seen ISPs try to deploy from a cupboard under the stairs. The OLT needs stable power (UPS-backed), cooling (ambient temp below 40°C), and physical security. Plan this before civil works begin.
3. Single-ISP exclusivity agreements Some ISPs push for exclusivity. This is fine if the ISP is reliable, but it destroys your negotiating power at renewal time. Negotiate a non-exclusive passive infrastructure arrangement wherever possible.
4. No provision for future cable pulling Always run an extra empty conduit alongside every fiber run. Dark fiber for future capacity expansion costs almost nothing to include during civil works, but is prohibitively expensive to add later.
5. Ignoring optical power budgets A 1:16 PON splitter has ~12dB insertion loss. Add connector losses, splice losses, and fiber attenuation — and you need to verify that your OLT’s power budget can reach the furthest ONU. This is a calculation that needs to happen at design time, not post-installation.
What to Ask an ISP Before Signing
Before signing with any ISP for your society deployment, get answers to:
- Who owns the infrastructure? Passive layer (fiber, conduit, ODF) should ideally revert to the RWA after a defined period.
- What fiber standard are you using? G.657A2 is bend-insensitive — essential for in-flat drops where tight corners are inevitable.
- What uplink do you have into the building? A leased line (not a shared residential link) into the PoP is a hard requirement.
- What’s your SLA for fault resolution? 4-hour response, 24-hour resolution is the benchmark.
- What are the plan prices? Be wary of teaser rates that spike at renewal. Ask for a 3-year rate schedule.
INIC’s Approach for Society Deployments
We deploy under Model 2 (full ISP-led, no capex for the RWA) for complexes with 50+ units. We use G.657A2 fiber throughout, MikroTik + XPON OLTs, and our uplink comes through our own ISP backbone (DoT licensed, AS 152492).
Our PoP lease arrangement is typically 3+3 years, and we provide the RWA committee with a read-only dashboard showing uptime, active subscribers, and plan distribution.
If you’re a developer planning FTTH for a new project, or an RWA that wants to replace an existing ISP — reach out to our team. We’ll send a site survey team within 48 hours.