FTTH Designer

1 · Service area

Source

Click the map to place corners, then Finish. Drag any handle to reshape; click a dashed midpoint to add a corner; right-click a corner to remove it.

Streets are compiled from every source available for the area and de-duplicated, so a road two sources both have is counted once. The console reports what each source contributed.

Missing roads i

Existing plant — poles, pole lines, ROW, conduit (optional) i

Lines are followed and preferred wherever they reach. Points are treated as poles: the streets they stand along can carry aerial. Without this, the design is underground throughout — street data says nothing about poles, and assuming them would understate the build.

Reference layers — for context only (optional) i

Drawn on the map and nothing else — a reference layer never changes the design. It appears on the Reference legend, where it can be renamed and recolored, and it is saved with the project.

idle

2 · Technology

Optical design margin (dB) i

Locations inside the margin are lit and are never reported unserved — this decides how much room the design keeps, not who gets service.

Sites & headends. Click a button, then click the map. Drag a marker to move it; right-click to remove it. Anything you place is honoured — pinned plant is never relocated or dropped by the optimizer, which designs the cheapest network containing it.

Or type one OLT (lat, lon) — optional i

3 · Construction

The rules the design obeys. Defaults are ordinary US practice; change them per project where local conditions or your standards differ.

Max pull (ft) i

Merge radius (ft) i

Max locations / FDH i

Ordinary setback (ft) i

Flowerpot up to i

Pedestal up to i

Drop slack (ft) i

Min drop (ft) i

4 · Permitting

Federal and Tribal land, wetlands, protected water, critical habitat and railroads, from the NTIA permitting layers. Preliminary and not exhaustive — treat every hit as "review this", not as the complete list of permits.

5 · Pricing

Materials vendor i

Construction vendor i

6 · Economics

Residential and business are modelled separately. Locations are split by their FCC building type — code B is billed as business; mixed use (X) stays residential, because those are overwhelmingly dwellings with a shopfront.

Resi take rate (%) i

Resi ARPU ($/mo)

Business take rate (%) i

Business ARPU ($/mo) i

Discount rate (%)

Horizon (yrs) i

Grant funding ($)

Advanced business modelling (optional)

A commercial install is a larger truck roll and a business costs more per month to support. Left blank, both reuse the residential figure and nothing changes.

Business opex ($/sub/mo) i

Business connect ($) i

Marketing

Save this area as a marketing area

Save area keeps the polygon and its market — locations, building mix and opportunity counts — with no route designed. It lands in Saved designs and can be opened and run as one later without redrawing. Export all locations is every address in the polygon, each with its own tier.

Import a marketing layer i

Shown on the map and the Project area legend — rename and recolor it there. Saved with the project.

Who is worth calling on inside the drawn area, from the FCC availability release. Draw an area to fill this in.

Saved designs

Every run is kept on the server with its map, workbook and report. Open one to put it back on the map.

Activity log

Guide opens in a new tab

Review · after a design

Cost

Returns

Sheet size

Sheet basemap

checking build...

Map

working…

Reference — all US

Sign in