XANDERFIBER INTELLIGENCEXANDER / FIBER INTELLIGENCE
Review geography before committing it.
Bounded GeoJSON, KML and KMZ adapters and a reviewed import wizard passed scoped local gates. Upload → detect → geometry and ordered manholes → customer/site → source rack, drawer, cassette, position → cable/tube/fiber → destination → validate → commit. Original source and geographic versions remain intact. Other formats require their own evidence.
Locally validated search covers physical inventory, canonical position, cable/tube/fiber labels, customer/site, registered circuits, routes and addresses, with filters and paging. Nearby search has a separate spatial gate. Smart Work and Barcode/QR resolution across every domain must not be inferred from this scope.
Scoped local validation covers recorded PostGIS points, active routes, bounded viewport layers, nearby queries and authorized record navigation. This coordinate workspace is not a configured street basemap. Circuit, cable, asset, customer, job, fault and authorized technician layers are extended as their domains mature. External navigation does not replace the engineering database.
CONCEPTUAL VISUAL · Interactive example with synthetic data. No operational application is connected.
Google Maps · Brussels ↗Assets & network context
When location details, cable references and previous work sit in separate files, each intervention starts with reconstruction. Knowledge stays with the person who last visited instead of with the network record.
Bring the asset’s recorded identity, location and relationships into a common workspace. Use search, the manhole workspace and engineering inspection to move from a code to its registered context. Missing information remains a task to resolve, not a connection to guess.
For the technician: a consistent starting point for finding the recorded asset instead of reconciling several naming conventions at the site.
For the engineer: inspect recorded links and gaps before proposing a route or intervention. A nearby object is not automatically a connected object.
For the company: a maintained asset register can reduce dependence on individual memory and repeated preparation work when staff or contractors change.
Example: a new technician inherits work at MH-015. Start from its asset record, review the registered network context and check the assigned work instead of reconstructing the site from an old spreadsheet alone.
Measure preparation time per job, incomplete asset records and the number of questions needed before dispatch. Data completeness is part of the rollout, not an automatic outcome.
Benefits describe intended operational value. No measured saving or guaranteed return is implied.XANDER / FIBER INTELLIGENCE