Module of the Service Engine · Design, records and quality
Reperio GIS
One spatial record of route, splice and asset data, qualified against every address you serve.
What it does
GIS is the record. Route, duct, splice and asset data live in one place with an address layer behind them, so serviceability answers and network records come from the same source rather than from a spreadsheet kept next to the drawings.
Assets, addresses and zones are Service Engine inventory objects, so a change in GIS is immediately visible to ordering, provisioning, locate screening and reporting.
Capabilities
Inside Reperio GIS
Route, duct and splice records
Structured records for cables, closures, chambers and splitters, versioned and attributable.
Address qualification
Serviceable, planned and out-of-footprint states resolved per address, exposed to ordering journeys.
Build-zone mapping
Zones and phases mapped against premises counts for demand and programme planning.
Asset lifecycle
Planned through built to in-service states carried on the asset record itself.
Records, not reality
GIS is deliberately the system of record. It describes what the network is designed and documented to be. Fiber Map shows what is physically in the ground, and Design Insights is the automated check between the two. Keeping those three distinct is what makes a serviceability answer defensible.
Serviceability the order journey can trust
Address qualification is exposed through the Service Qualification and Serviceable Address APIs, so ISP portals, retail journeys and partner systems all resolve availability against the same records with the same rules.
Exposed through
TM Forum API domains this module surfaces in
Whatever the module does internally, external consumers reach it through the same conformant interfaces as the rest of the platform.
Works with
Modules it is usually deployed alongside
Modules are not sold as a bundle, but some combinations do most of the work in practice.
See the platform against your own operation
A demo walks the architecture, the modules you would actually use and the TM Forum interfaces your partners would integrate against. Bring your operating model and we will map it.