Platform
Four layers around one core
Reperio is not a suite of products with a shared logo. It is one core with defined interfaces above, beside and below it — which is what makes the operating model predictable as the network grows.
Layer 1 · Customer Experience Portals
- End Customer Portal
- ISP / RSP Portal
- Construction Company Portal
- Partner Portal
- Internal User Portal
Layer 4 · Peer / OSS ecosystem
- Partner OSS/BSS
- Industry platforms
- Interconnect and roaming
- Other operator systems
- Third-party platforms
Layer 2 · Reperio Service Engine
Unified OSS/BSS core
- Product Catalogue
- Order Management
- Customer / Subscriber Management
- Service Management (activate / change / cease)
- Inventory (network / service / address)
- Assurance (fault / performance / SLA)
- Billing & Charging
- Field Service Management (workforce / appointments)
- Orchestration (workflow / automation)
- Reporting & Analytics
- Integration Layer
Layer 3 · External interfaces
API Gateway & Integration Layer — identity and access, throttling, monitoring, event streaming. HTTPS, OAuth2, mTLS.
- Commerce
- Service Management
- Assurance
- Field Service
- Data / Reporting
Layer 4 · Network & infrastructure
- Nokia / Altiplano
- Genie ACS
- OLT / access
- BNG / core
- Other network elements
- CX Portals
- Service Engine
- External interfaces (TM Forum)
- Peer / OSS ecosystem
- Network & infrastructure
Layer 1
Customer Experience Portals
Human and application interfaces for every participant in the ecosystem — subscribers, retail providers, construction companies, partners and internal teams.
Layer 2
Reperio Service Engine
The unified OSS/BSS core. Eleven functional blocks sharing one data model, one workflow engine and one integration layer.
Layer 3
External interfaces
Business and service capabilities exposed through five TM Forum Open API domains behind an API gateway with identity, throttling, monitoring and event streaming.
Layer 4
Ecosystem and network interfaces
Peer OSS/BSS and industry platforms on one side; network management, ONT, access, BNG and transport interfaces on the other.
Layer 1
Portals, not just a UI
Each portal is an access model as much as a screen: what a party can see, order, change and evidence is governed per audience.
Subscribers
End Customer Portal
Ordering, tracking, support and self-service for the people the network ultimately serves.
Retail service providers
ISP / RSP Portal
The wholesale counter: service orders, faults, inventory and reporting scoped to each provider.
Build contractors
Construction Company Portal
Work orders, appointments, status updates and quality submissions for construction partners.
Contractors and third parties
Partner Portal
Controlled access for partners and subcontractors, with compliance and access governance.
NOC, operations, field and finance
Internal User Portal
Dashboards and working tools for the teams running the network day to day.
Layer 2
The Service Engine's functional blocks
Order, service, inventory, assurance, billing, field and orchestration in one core rather than integrated after the fact.
Product Catalogue
Retail and wholesale offerings, pricing, eligibility and bundles, published once to every channel.
Order Management
Order capture, validation, decomposition and lifecycle across retail, open access and hybrid models.
Customer / Subscriber Management
Parties, accounts, contacts and subscribers, with ISP-scoped visibility in wholesale models.
Service Management (activate / change / cease)
The service lifecycle from feasibility to cease, with change and upgrade paths.
Inventory (network / service / address)
Network, service and address inventory as one queryable model behind serviceability and provisioning.
Assurance (fault / performance / SLA)
Fault handling, performance data and SLA measurement against the service record.
Billing & Charging
Rating, invoicing, settlement and revenue share driven by the catalogue and inventory.
Field Service Management (workforce / appointments)
Capacity, appointments and dispatch across in-house, contractor and ISP workforces.
Orchestration (workflow / automation)
Configurable workflow and automation across order, build, activation and assurance paths.
Reporting & Analytics
Operational, commercial, customer and network reporting on one dataset.
Integration Layer
API management, event bus, security and data transformation for every external interface.
Layer 3
Five API domains, one gateway
Colour is a wayfinding device here: each domain keeps the same colour wherever it appears across the site and the product.
Commerce
Lets partners and customers check availability, view products and place orders.
7 APIs
Service Management
Supports the full service lifecycle from order to active service.
7 APIs
Assurance
Real-time service and network status, fault handling and performance reporting.
7 APIs
Field Service
Scheduling, dispatch and tracking of field activities.
7 APIs
Data / Reporting
Network and service data for operational and commercial reporting.
9 APIs
Layer 4
Ecosystem and network interfaces
Reperio operates inside an existing landscape: partner systems, industry platforms and the network itself.
Peer / OSS ecosystem
Partner OSS/BSS
Wholesale and roaming counterparties exchanging orders, faults and settlement data.
Industry platforms
TM Forum ecosystems and aggregation platforms such as OneTouch.
Interconnect and roaming
Order and assurance interfaces with other operators.
Other operator systems
Numbering and identity systems operated elsewhere in the group.
Third-party platforms
GIS, address, credit check and other commercial data services.
Network & infrastructure
Nokia / Altiplano
Network management and access domain control.
Genie ACS
ONT management, firmware and remote configuration.
OLT / access
PON infrastructure provisioning and state.
BNG / core
IP broadband session and policy control.
Other network elements
Transport and DWDM layer inventory and alarms.
Modules
Nine modules of the core
Grouped into three families so the stack reads as structure rather than a list.
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.