FTTH Planning and Data Validation

We plan FTTH networks and validate the documentation that comes out of them. Both run on the same data, so there is no reconciling of two separate systems. That is what we built AO_Fiber for — the software we work with every day.

Planning starts with routes and duct bundles: which microduct goes where, what colour it carries, how the ducts are named. Names follow the templates set for the project, and subordinate ducts are derived from them.

Cross sections can be generated at any point along the route, longitudinal profiles along its course.

Connection points are carried through and can be exported as a table. Quantities per layer are available at any time, with nobody recalculating them by hand. The coordinate system of the source data stays as it is.

Validation happens before handover. It covers the naming of enclosures, ducts and cables, the fibre chains from the OLT through to the building entry point, the capacity of cables and splice positions, missing entries, and the links between duct, cable and route.

Every finding in AO_Fiber points to a row and a column, so it can be located straight away. What counts as an error and what is only a note stay clearly apart.

If you would like to see how this looks for your project, give us a call or drop us a line.

1. Route planning with duct bundle and cross-section positions
2. Validation result: every finding on a row and a column
3. Microduct colour scheme as specified by the project