Closures, splitters, couplers, cables and drops, recorded the way a splicer talks about them, drawn on the map with the state of the subscribers underneath. Passive plant is never charged.
The plant, in your words
Fibre runs between two closures. At a closure you join cable to cable, or take a core out to a device. A customer point is a closure too.
- Closure: the joint box. It has no ports; every fibre in it is a splice.
- OBD: the splitter that feeds other boxes.
- FAT: the splitter customers hang off, in the ratios ISPs stock: 1:2, 1:4, 1:8 and 1:16.
- Coupler: the two-leg tap that splits light unevenly.
- Cable: a segment with two recorded ends and a fibre count.
- Drop: the record from a splitter leg to a subscriber's ONU.
A splitter can be housed inside a closure, and moving the closure moves it.
Cables, splices and light
Each box has a patchbay view, the arena, and it is the one place a cable is laid. It opens with the connections your topology already implies, so confirming one is two clicks. The splice schedule is one row per fibre with its destination on the row, and a splice HansaNet will not accept says why in plain words. A traced cable carries its length in metres, so a crew can order drum.
Light one PON and the map shows where your recorded glass carries it. From any box or subscriber, "trace from here" draws the path up to its OLT. KML import brings closures and cables in from a drawing you already have.
The map, with state
Plant draws in one colour and has no state of its own. A splitter is never down; its subscribers are. Traced routes draw solid and untraced ones dashed, so the dashed lines are your to-do list. Hover a box for where its cables run and its photograph.
Two findings come off your record and the OLT together:
- A branch fault names a span. When a branch of subscribers goes dark, the map names the stretch of fibre to search.
- A weak ONU is flagged under its splitter. You see which part of the plant to check.
Neither pages. Passive plant is out of the alarm path. Paging stays with outage detection and optical monitoring.
Verify, locate, plan
Verify compares your record with what the OLT sees and shows you where the two disagree. A splitter nobody has run glass to counts as a record that is incomplete, not wrong, and a record finding is never an alarm. Locate takes the metres an OTDR reports from a box and places that point on the recorded route, naming the span it landed in.
Plan proposes drops for located subscribers with no recorded splitter, within a radius you set, as ghost lines on the map. A greenfield option proposes splitter sites for unserved subscribers. Nothing is written until you tick "record these". The site sheet prints an optical budget marked "Modelled", which is a planning figure and never a reading.
The record is built from both ends. The owner lays cable and joins fibre on the desktop; the crew records boxes, feeders and legs from the street in the field app, with photographs of each box.
Passive plant is never charged. Splitters, closures and cables are free however many you record; the bill counts ONUs and monitored devices. See pricing.
What it does not do
- A cable runs between two recorded ends. To join mid-span, open a closure there.
- What you have recorded is not what is occupied, so nothing reports spare legs on a splitter.
- Plant never pages. A branch fault and a weak ONU render on the map; they do not send a WhatsApp.
- A modelled budget is for planning and never sits beside a fault.
- KML import creates closures and cables only, never splices, ratios or feeds.
- Laying cable and building plant is a desktop job; phones record boxes through the survey.
- Several cables sharing one duct as a common risk is out of scope.
Put a probe on your plant tonight.
One setup .exe on a Windows machine in the rack, or a .deb on Linux. Rs 3 per ONU a month, no plans, no caps.