A shared fiber map
Keep routes, passive infrastructure and service locations available from a common operational view.
Network productsIllustrative operational view · not live customer data
Neurix Fiber GIS
Connect the physical fiber network to the services it carries.
Represent routes, passive assets, sites and service locations in an operational map that network, support and field teams can use together.
Deployment and support scope are confirmed during discovery.
12.4 kmMapped route
46Network structures
01
Core route mapped
02
Splitter context linked
03
Service locations attached
04
Field record available
What it is
Fiber GIS
Neurix Fiber GIS is a fiber-network mapping workspace for broadband and FTTH operators. It is designed to organize geographic routes and passive infrastructure while connecting those assets with operational inventory, service locations and field workflows.
Understand what an asset supports
Relate fiber context to downstream locations and services where the deployment data makes that relationship available.
Better location context
Give field teams clearer asset, route and service information before work begins.
Capability set
Built around the work operators need to complete.
Final coverage depends on the agreed environment, integrations, device support and delivery scope.
Route mapping
Represent planned and deployed fiber paths with the geographic context required by the operator.
Passive asset records
Organize supported asset types such as cables, splitters, closures, boxes and related structures.
Service locations
Connect network locations and customer premises to the relevant fiber context.
Capacity context
Maintain strand, port or asset-capacity information where it is included in the agreed data model.
Field-ready records
Make approved route and asset information available to installation, maintenance and repair workflows.
Operational integration
Connect fiber records with inventory, OLT, ticketing and service operations where those modules are deployed.
Operating model
A clear path from signal to action.
Neurix keeps each stage visible so different teams can work from the same operational context.
- 01
Model
Create the physical network record
Organize routes, structures, passive assets and locations using the agreed data and geographic standards. - 02
Connect
Relate assets and services
Associate the fiber path with access infrastructure, premises and operational inventory. - 03
Operate
Use the map during daily work
Bring location and asset context into planning, installation, assurance and repair activity. - 04
Maintain
Keep the record trustworthy
Apply governed updates and retain the ownership and change context needed for operational confidence.
Who it helps
Shared context for the teams responsible for service delivery.
Network planning
Maintain a structured view of routes, assets, capacity and planned expansion.
Field operations
Use location and asset context during installation, maintenance and fault work.
Support and assurance
Understand the physical path and downstream service context involved in an incident.
Deployment and fit
Start with reliable data and a maintainable operating process.
A useful fiber GIS depends on source-data quality, asset conventions, coordinate accuracy and clear ownership of updates after rollout.
Scope considerations
- Existing-data import
- Defined asset taxonomy
- Role-based editing
- Inventory and field integration
Data migration, map layers, asset types and geographic coverage are scoped for each implementation.
Product FAQ
Questions to answer before implementation.
Can existing fiber records be imported?
Existing records can be assessed for migration. The approach depends on format, completeness, coordinate quality, asset identifiers and the target operating model.
Does Fiber GIS replace inventory?
No. Fiber GIS focuses on geographic and physical-network relationships. Inventory manages asset ownership, stock, custody and lifecycle. The two can work together.
Can field teams use the map?
Field access can be included with role-appropriate views and workflows. The exact mobile and offline requirements are confirmed during discovery.
Can it show affected services?
Impact context is possible when the required route, access-device and service relationships exist in the platform data.
Plan the right scope