Fiber Genius is the working record of a fibre network: what's built, what's planned, which fibre feeds which house, and how much cable to pull. Built by an ISP, for the way the work actually goes.
In daily use on a live network in British Columbia.
The model
Plant is modelled properly — cables know their tubes and fibres, closures know their splices, terminals know their ports — so the map can answer questions instead of just showing lines.
Owner, height, tag, span lengths and down guys. Strand and fibre lashed along the same route.
A real splice sheet per closure — tube and fibre both ends, colour-coded to TIA-598.
Which port is free, and the fibre feeding it. Traced back through splitters to the patch panel.
Racks, OLT, patch panels, splitters and every patch cord between them.
Pick one on the map and you get the actual hardware: model, dimensions, splice capacity, how many cable ports are used, slack loop, and which of the cables crossing that pole it rides.
Open a closure and you are looking at every fibre in it: tube by tube, in TIA-598 colours, with what each one is spliced to, what passes straight through, and what is still spare.
A terminal knows its splitter, the exact fibre feeding it — tube and colour — and which of its ports are free. Ask where that fibre goes and it traces back through every closure to the patch panel, and tells you how far.
Planning
The model that draws the map also answers the questions you would otherwise work out on paper — and tells you when the design does not add up.
Fibre and port usage across the whole network, per cable, per closure and per OLT — so you find out you are out of fibre while it is still a plan, not while a crew is up a pole.
Continuous checks run over the whole network and point at the specific item. On the demo build they catch ten things — the same kinds of mistake a real design makes:
Click any of them to jump to the item on the map.
The table under the map shares the map's selection. Cells edit in place, Enter moves on, ⌘D fills down a column, and you can paste a block straight from a spreadsheet.
In the field
Field Mode is a map with the job on a sheet underneath — everything on one screen, at thumb size, and it keeps working when the signal doesn't.
Place a pole where you're standing and carry strand and fibre to it. Park a run to build a branch, then pick the same cable up again.
Works with an external RTK receiver on Android, and refuses to place plant from a fix worse than your limit. Every placement records the accuracy it had.
A queue of what's near you to check off, so as-builts come from the field rather than from memory a week later.
Edits keep working with no signal and sync when you're back. Base-map tiles download ahead of a trip, and closer zooms fall back to the nearest saved tile.
Save the area you are working in before you leave. Tiles are stored on the device, and the panel tells you where each tile on screen came from — saved, downloaded, or scaled up from a coarser one because you zoomed past what you saved.
Working together
Edits travel as they happen, item by item, so a planner at a desk and a tech at a pole work on the same network at the same time.
A change is a few hundred bytes on the wire and lands on the other screen in under a second — no save button, no reloading someone else's work.
A quiet line of initials shows who else is in the network and roughly where, so two people don't edit the same pole at once.
Every item carries who touched it and when, stamped by the server. If your edit lands on top of someone else's, you are told rather than left to find out.
With no signal, edits queue on the device and flush as one batch when it returns — closing the laptop doesn't lose them.
Every save is kept, newest first, with what changed and who saved it. Restoring an old version creates a new current version — it never deletes history.
Paperwork
No redrawing the network to produce a document.
Telus P408 packages — overview sheet, numbered detail sheets, title block, revision block, property boundaries, one-call notice.
Counted from the plant itself, per area or for the whole network, print or CSV.
Because the field crew recorded it as they built it, rather than from memory a week later.
Every cable type totalled in metres, every closure and terminal by model, drops rounded up to the stock length you actually buy.
The network shown throughout this page is demonstration data — an invented build laid over the streets of a small prairie town, generated so that nothing here shows a real customer's plant. The application, the numbers and the behaviour are real.
