openFTTH
GitHub Download
FeaturesHow it worksDocsChangelogGitHub

design

From a street map to a priced network

openFTTH places every cabinet, splitter, terminal and cable for an area, checks it against your rules and prices it. Solvers make every number, and every decision is written down with its reason.

Download for WindowsYour first design

How a run goes

  1. Bring the area: OpenStreetMap, GeoPackage, Shapefile, CSV address lists, DXF or KML, in any projection, with existing ducts, poles and no-dig zones if you have them.
  2. Pick a rulebook: splitter ratios, the cable ladder, reach limits, the optical budget and prices, in readable YAML. The generic GPON preset is a good start.
  3. Design automatically: the engine clusters homes, places terminals and cabinets, routes cables along streets and checks every rule.
  4. Take it away: a GeoPackage for your GIS, the bill of quantities and splice schedules as CSV, versioned work orders and the decision log.

One real area

Brugse Poort in Gent, from an OpenStreetMap extract of 821 buildings with the generic rulebook (centralised 1:32 split, 28 dB budget): 524 homes and 597 units, 36 terminals, 2 cabinets, 0 rule violations, a worst optical loss of 21.6 dB, in 65 seconds on a Windows laptop.

Checks and repeatability

  • Same inputs, same design: the solver runs with a fixed seed, and the tests fail if the Gent sample stops coming out byte-identical.
  • A reason for every decision, in the decision log, so a reviewer can follow the design without rerunning it.
  • Centralised, cascaded or point-to-point: design the same area each way and compare the price.
  • Change a number in the rulebook and the next run follows it.

To change something, move it by hand. hand edits stay put when the engine runs again.