Before: Most teams juggle CAD/PDFs, tickets, and a generic GIS that can draw lines but can't trace fiber end-to-end.
After: Click any segment and instantly see the optical path, impact, and capacity – in seconds, not hours.
Bridge: FiberMan is an operational system with an Optical Path Engine that models how fiber actually works.
Once upon a time...
...a growing ISP built a fiber network piece by piece – cabinets, closures, splitters, splices, OLT ports, ONUs, customers – across towns where every expansion added new complexity.
Every day...
...the team tried to keep control using a mix of "tools that kinda help": spreadsheets for inventory, tickets for incidents, CAD/PDFs for as-builts, and sometimes a heavy GIS that can draw lines on a map but doesn't actually understand fiber. It can store geometry, but it can't answer operational questions like "what's downstream of this splitter" or "which customers die if this splice is bad."
But one day...
...an outage hit (or a rollout deadline got tight) and everyone realised the real problem wasn't the break – it was the blind spots. They couldn't reliably trace optical paths end-to-end. Different systems disagreed. Documentation lagged reality. And every urgent situation started with the same ritual: calling "the person who knows," exporting layers, hunting through PDFs, and reconstructing the network from fragments.
Because of that...
...incident response slowed down and became noisy: false assumptions, unnecessary truck rolls, longer downtime, and customers calling before the team even had a clear impact list. Planning also got risky: "available fiber" on paper wasn't available in the field, spare capacity was guessed, and expansions created accidental bottlenecks.
Because of that...
...they tried to "fix" it by adding more process and more tooling – more fields in the GIS, more spreadsheets, more rules for naming, more exports, more manual syncing. But the core failure stayed the same: the system still didn't understand the fiber network as a connected optical graph. It was mapping, not operating.
Until finally...
...FiberMan was built as an operational system for fiber – with an optical data engine that models how fiber actually works: routes and ducts, fibers and splices, splitters and ports, relationships and traceability. So you can answer operational questions instantly: impact analysis, optical path tracing, capacity checks, and "what changed?" without detective work.
And ever since then...
...the network stopped being a collection of drawings and disconnected records. It became a living model the team can run the business on: faster troubleshooting, cleaner handovers, confident expansion planning, and fewer surprises as the network scales.
Most teams start with familiar tools. But as the network grows, the cracks start to show.
The most common "starter stack" – familiar, free, and flexible. Until it isn't.
Professional mapping tools designed for general geospatial work – not fiber operations.
Learn more about the technical architecture: What is an Optical Data Engine? →
Get a personalized demo and see how FiberMan can transform how you operate your fiber network.