Complete fibre documentation. OTDR file import with fault localisation. Service path tracing from ONT to OLT through every splice. Cable-fault impact analysis showing every customer affected by a single splice failure. Plus auto-discovered network topology, duct and conduit management, build projects with wayleave tracking, environmental sensors, and live signal monitoring. Built for FTTH operators, not for marketing demos.
Generic ISP platforms ship "GIS modules" that show customer markers on a map and call it network documentation. That is not fibre infrastructure documentation. That is a customer-finder with a satellite image background.
Real FTTH operations need every cable run, every core within every cable, every splice closure, every splitter (with its split ratio and downstream capacity), every duct route, every manhole, every chamber. The map widget shows where customers live; it does not show how the fibre gets there.
ISPCQ GeoMap is the network as it physically exists. Trace from any customer's ONT, through their drop cable, through the splitter, up the trunk, through every splice, back to the OLT port. Upload an OTDR trace; the system locates the fault on the actual fibre route, not on a map approximation. When a splice closure fails, the system tells you every downstream customer affected.
The difference is millions in OpEx for any FTTH operator.
Each layer corresponds to a real physical thing in the field — the cables and cores, the ducts that carry them, the devices on each end, and the live signals running through them. Confusing two of them is how cable cuts go uncorrelated to customers.
Every cable run documented with type, core count, length, route, and per-core assignment. A 96-core trunk knows which cores carry which downstream splitters; a 12-core distribution cable knows which cores are spare for future builds.
Splitter inventory with split ratios (1:8, 1:16, 1:32, 1:64), location, capacity utilisation, and downstream customer count. Multi-stage splitter trees (1:4 then 1:16) modelled correctly. The ratio multiplied through the tree gives the actual customer-per-OLT-port number.
OTDR trace files (.sor and similar) parsed and overlaid on the GIS topology. Faults localised against the actual fibre route, not against a map approximation. Compare a post-repair trace against the baseline to verify the splice was actually fixed.
From any customer's ONT, trace the full service path: drop cable, drop-cable core, splitter input, trunk cable, trunk core, splice closures along the way, OLT port. Each hop annotated with cable ID, core number, location, and last-maintenance date. The route is the actual route, not an approximation.
When a cable fault is reported (cut, broken splice, water ingress in a closure), select the affected element on the map. The system computes every downstream customer, the contract status of each, the support tickets currently open from those customers, and the estimated outage scope. Before the technician leaves the depot, the NOC has the full impact list.
Coverage polygons per region with address-level lookup: "is this house inside our footprint?" Build planning for new areas with civil works tracking (ducts, chambers, lay-in dates, contractor assignment). Coverage-qualified leads (addresses inside footprint that aren't yet customers) flow to the sales tools.
An interactive, zoomable diagram of how every device actually connects to every other device — not drawn by hand, but discovered automatically from your live network. Pull device links straight from your monitoring system; let the platform learn neighbour connections from the switches themselves. Then flip to the switching scheme: pick any site, cabinet, or room and see every port-level and cable-level connection in one logical view, saved for documentation and shared with the team.
The pipes that carry the cables, documented as carefully as the cables themselves. Drill into any route to see its duct segments — start and end manhole, diameter, material, depth, capacity — and the smaller sub-ducts nested inside each one. A colour-coded cross-section view shows exactly what is packed into a duct and how full it is, so you know before you dig whether there is room for one more cable.
Group related infrastructure work — a phase rollout, an extension, an upgrade — into a project with its own code, budget, contractor, and timeline. Track every wayleave and permit through its full lifecycle: reference number, municipality, authority, submission, approval and expiry dates, conditions, and the signed documents themselves. Auto-generate a bill of materials from the infrastructure assigned to the project, and hand a contractor the build as a Google Earth file.
Cabinets and manholes are hostile places, and the platform watches them. IoT sensors push readings — temperature, humidity, water level, gas detection, vibration — into a sensor dashboard, each device registered with its own secure key. When a reading crosses a threshold you set, an alert fires and the on-call team is notified by Telegram or email. Warning and critical levels are tracked independently, so an early warning never hides the serious failure that follows.
OTDR tells you about a fault after you go looking; this layer tells you before. A per-OLT overview shows every customer's signal as Good, Weak, or Critical, with history charts and per-OLT thresholds for long-distance runs. A wire-down view lists ONUs that have dropped offline and the customers behind them. A capacity view warns when an OLT port is filling up — long before it becomes a midnight outage.
Getting an existing network into the system is usually the hardest day. ISPCQ makes it the easiest. Drop in KMZ, KML, or GeoJSON files and review the staged items on the map before they go live. Let AI read the free-text notes in those files and pull out splitter types, ratios, and customer matches with confidence scores. Bring in GPS waypoint surveys from the field with duplicate detection, sync devices and port links from your monitoring system, migrate from UserSide, or bulk-update from a CSV. Push it all back out as standard GeoJSON for any other mapping tool.
Stop re-typing the same OLT specs every time a new one goes in. Define each device once — vendor, model, rack height, power draw, port count, and the full port layout — then pick the vendor and model when adding equipment and let the platform fill in the rest and generate the ports automatically. The same template definitions drive the rack diagrams in the infrastructure browser and feed real costs into project bills of materials.
The map is where the network is built, not just viewed. Draw routes as lines and drag their vertices to match the real path; click any item for its full details, or right-click for a context menu to edit, view, or assign it. A filter panel controls exactly what is on screen — by status, project, fibre area, asset type, and overlays — while a sidebar tree organises every category for drill-down. One universal search bar finds any item by code, name, or customer detail across all infrastructure types at once.
Group infrastructure into logical map layers you can switch on and off as a set. Create a layer, assign items to it (an item can sit in several layers at once), and toggle its visibility from the Layers panel — each layer showing a live count of what it contains. Customer locations appear as pins colour-coded by contract status, so a problem area is obvious from across the map; at low zoom the pins cluster into tidy groups so a dense city stays readable.
A connection dashboard gives one view of every physical link. Browse cables in a grid by type, status, and search; open any cable to a visual tube-and-core diagram where each core shows its colour, allocation, and connected ports. Map equipment ports to cable cores, then trace the full path as a node chain through equipment, cables, and splitters. And when you import an existing network from a map file, every staged item is previewed on the map first — approve or reject individually, or batch-confirm a whole upload — so nothing goes live until you have seen it in place.
Every service path carries a predicted loss budget — the signal loss expected across every splice, splitter, and connector between OLT and ONT. Once an OTDR trace lands on the path, the system compares the real measurement against that budget automatically, surfacing exactly where a path is degrading before it turns into a customer complaint.
Planning a new conduit run between two manholes used to mean eyeballing the map. Pick a start and end manhole and the system proposes candidate routes ranked by distance and existing duct utilisation, shown side by side, so the build team can choose the path with the least digging and the most spare capacity.
The map is built for spatial planning; the infrastructure browser is built for the data-centre floor. Drill down from site to floor to room to cabinet as a separate navigation mode alongside the map, with a visual rack diagram showing every device in its slot and the patch cables running between ports. A port dashboard rolls up utilisation across every piece of equipment so a full cabinet is obvious before a truck rolls.
Two standing reports keep the documentation honest. The equipment inventory report lists every device with summary statistics — active counts, missing serial numbers, missing management IPs — broken down by type. The infrastructure audit report finds unused capacity, missing data, and orphaned items across the whole network. Both export to CSV.
The event. 23:47. The NOC's network monitoring flags a sudden dropout of 31 ONUs on the same OLT PON port. Pattern looks like a single upstream fault, not 31 individual issues.
What ISPCQ does. The on-call NOC engineer opens GeoMap and selects the affected PON port. The service-path tree highlights every cable, splice closure, and splitter between the OLT and the 31 ONTs. The most recent OTDR baseline for the trunk segment is loaded. Cable-fault impact analysis identifies a 1:32 splitter as the upstream node feeding all 31 affected customers; the splitter location is flagged on the map with last-maintenance date 14 months ago.
The dispatch. The NOC engineer creates a single incident note with the 31 affected contracts attached, GPS coordinates of the splitter, OTDR baseline file, and a "probable failed splice" notation. The on-call cabling crew leaves the depot at 00:18 with the full context, OTDR meter, and replacement splice closure. By 02:30, repair confirmed. Post-repair OTDR trace compared against baseline; signal restored across all 31 ONTs. Total downtime: 2h 43m. Without the impact analysis, the dispatch decision alone would have eaten the first 45 minutes of that.