Operating model
Open access, without a separate wholesale stack
Wholesale operation fails on the details: which party sees what, who owns the appointment, whose SLA applies, and what actually gets settled. Reperio models those as first-class concepts in the core.
The problem
Two businesses on one network
An open access operator runs a wholesale business for providers and an infrastructure business for itself. Most stacks serve one well and bolt the other on — which is where unbilled services, disputed settlement and contested appointment ownership come from.
On the Service Engine both businesses read the same inventory. A service is active for exactly one provider, on exactly one address record, against exactly one contract — so what is provisioned, assured and settled cannot diverge.
Mechanics
What multi-ISP operation requires
Provider onboarding
Each ISP or RSP is a party with its own credentials, catalogue entitlements, SLA terms and data boundary. Onboarding is configuration plus conformance testing, not a development cycle.
Scoped visibility
A provider sees its own subscribers, orders, faults and inventory — never another provider's. Internal teams see the whole footprint. The boundary is enforced in the core, not in the UI.
Shared field capacity
One workforce engine serves every provider. Appointments are offered against real capacity, and dispatch spans in-house crews, contractors and provider field teams.
Assurance and SLA
Faults raised by providers are measured against the SLA that applies to that contract, with remedy calculated and fed to billing rather than agreed in a meeting.
Settlement
Revenue share between network owner, provider and any intermediary is derived from the service inventory and settled per period with statements that survive dispute.
Regulatory and funder reporting
Serviceable premises, build progress, quality evidence and provider take-up reported from one dataset, which matters where public funding carries obligations.
Modules that carry the weight
Where wholesale actually gets decided
Portals and APIs are the surface. FSM, Billing and the Service Engine's inventory are where a wholesale model succeeds or leaks.
Reperio FSM
Shared workforce, separated visibility, evidenced completion per provider.
Reperio Billing
Wholesale rating, multi-party revenue share and settlement from live inventory.
Service Engine
Party, contract, catalogue and inventory model that keeps providers distinct.
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.