Telecoms network inventory & GIS
Outside plant and inside plant, traced end to end on the map.
A GIS-native telecoms network inventory for outside and inside plant: structures, ducts, cables, splices, equipment, circuits and faults on one map.
The business problem
What Pulse TNI fixes.
Without it
- As-built records live in CAD files and the heads of field teams.
- Splice records are on paper, so tracing a circuit means a site visit.
- When a cable is cut, nobody knows which customers are down.
With Pulse TNI
Capture plant directly on the map, splice and terminate in the record, trace any circuit A to Z with a loss budget, and see every affected customer the moment a fault is raised.
Core functionality
Everything in one place.
Map workspace
Place sites, structures and routes directly on the map.
Outside & inside plant
Ducts, spans, cables, buildings, racks and internal routes.
Splicing & termination
Splice enclosures, splice-through and port termination.
Trace & loss budget
End-to-end trace with connector, splice and distance loss.
Circuits & projects
Provisioning that refuses an untraceable path; design to as-built.
Fault impact
Which customers go down if this cable is cut.
Built on the unified platform
The foundation comes standard.
The same security and governance practices sit under every platform. Read the trust centre.
Email sign-in, with roles per organisation.
Row-level security in the database.
Every change and approval recorded.
Open exports and documented APIs.
Also in Network & Geospatial
Engineering disciplines behind it
Who is Pulse TNI for?
A GIS-native telecoms network inventory for outside and inside plant: structures, ducts, cables, splices, equipment, circuits and faults on one map.
What problem does Pulse TNI solve?
The usual starting point: As-built records live in CAD files and the heads of field teams. With Pulse TNI: capture plant directly on the map, splice and terminate in the record, trace any circuit A to Z with a loss budget, and see every affected customer the moment a fault is raised.
Is our data kept separate from other organisations?
Yes. Each organisation's data is separated by row-level security in PostgreSQL, enforced by the database itself, and every sign-in, change and approval is written to an audit trail.
Can Pulse TNI connect to our other systems?
Yes. Every Alexon platform has documented APIs and webhooks, and connections set up once in the integrations hub can be reused across products. We confirm the specific connectors you need during discovery.
Can we get our data out?
Yes. Your data can be exported in open formats at any time, and everything the interface can do is also available through documented APIs.
How quickly can we get started?
Discovery takes one to two weeks. You then work in an environment on your own data while we configure, integrate and prove the platform, typically by weeks four to eight depending on scope and data migration.
See Pulse TNI on your own data.
A working session with an engineer, not a slide deck. Bring the process you want to fix.