The core
Reperio Service Engine
Subscriber and service lifecycle, product catalogue, order management, provisioning and activation, service inventory, assurance and ticketing — as one operating core rather than a set of integrated systems.
Why a core at all
Most OSS/BSS pain is integration pain
Operators rarely lack tools. They lack agreement between tools — a service active in provisioning but unbilled, an appointment booked against capacity that does not exist, an as-built that never reached the records. The Service Engine removes the space those disagreements live in.
One data model
Customer, service, asset and address objects exist once. A change in inventory is immediately visible to ordering, assurance, field and billing.
One workflow engine
Order, build, activation, fault and locate journeys are configured in the same orchestration layer, so handovers between teams are modelled, not improvised.
One integration layer
API management, event bus, security and transformation sit in the core. Every external interface — portal, partner or network — enters through it.
Functional blocks
Eleven blocks, one core
Named as they appear in the architecture. Each is a capability of the engine, not a separately licensed product.
- 01
Product Catalogue
Retail and wholesale offerings, pricing, eligibility and bundles, published once to every channel.
- 02
Order Management
Order capture, validation, decomposition and lifecycle across retail, open access and hybrid models.
- 03
Customer / Subscriber Management
Parties, accounts, contacts and subscribers, with ISP-scoped visibility in wholesale models.
- 04
Service Management (activate / change / cease)
The service lifecycle from feasibility to cease, with change and upgrade paths.
- 05
Inventory (network / service / address)
Network, service and address inventory as one queryable model behind serviceability and provisioning.
- 06
Assurance (fault / performance / SLA)
Fault handling, performance data and SLA measurement against the service record.
- 07
Billing & Charging
Rating, invoicing, settlement and revenue share driven by the catalogue and inventory.
- 08
Field Service Management (workforce / appointments)
Capacity, appointments and dispatch across in-house, contractor and ISP workforces.
- 09
Orchestration (workflow / automation)
Configurable workflow and automation across order, build, activation and assurance paths.
- 10
Reporting & Analytics
Operational, commercial, customer and network reporting on one dataset.
- 11
Integration Layer
API management, event bus, security and data transformation for every external interface.
Operating models
Retail, open access and hybrid on one engine
The model is configuration, not a different deployment. Operators moving from retail into wholesale do not replatform to do it.
Retail
You own the customer and the network. One catalogue, one order path, one bill, with assurance and field work against your own service records.
Open access
ISPs own the customer, you own the network. Orders and faults arrive from providers through portals and APIs; settlement flows back through revenue share.
Hybrid
Both at once, on one platform. The same address can be sold retail or wholesale with different catalogue items, pricing and SLA, without a second system.
Exposed capability
Everything the core does is reachable through an API
The integration layer publishes the engine's capability as TM Forum conformant interfaces, so portals, partners and your own systems consume the same contracts.
Commerce
Service qualification, product catalogue and order management.
Service Management
Activate, change, upgrade and cease services.
Assurance
Service status, fault management, outages and SLA.
Field Service
Appointments, installations and work status.
Data / Reporting
Inventory, serviceable addresses, KPIs and billing events.
Modules
What plugs into the core
Nine modules extend the engine into design, construction quality, build delivery, field work, locate compliance and monetisation.
The operating core
Reperio Service Engine
Explore the coreEvery module below plugs into the Service Engine and shares one data model, one API layer and one set of workflows. They are modules of the core, not separate products.
Design, records and quality
The spatial system of record, the check against design, the picture of what is built, and the evidence that it was built properly.
Build and field operations
Programme delivery, every truck roll scheduled and evidenced, and locate compliance handled inside SLA.
Commercial
Retail and wholesale monetisation, multi-party settlement, and subscriber data where sales already works.
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.