A platform built by RYLNA
Orchestraa Suite
From Order to Revenue. Seamlessly Orchestrated.
The telecom order orchestration platform. It sits between the systems that take orders and those that activate the network and bill the customer, without replacing either.
- Order capture
- Catalogue and eligibility
- Product order
- Service orders
- Network activation
- Billing hand-off
The problem
At most operators, an order moves from system to system through point-to-point integrations. Every new offer adds development work, every incident is investigated system by system, and nothing guarantees that an activated service will be billed.
The proposition
One catalogue-driven orchestration layer. Orders are decomposed, executed in the right order, cleanly rolled back when a step fails, and tracked through to the billing hand-off.
Capabilities
Status of the current version. “Planned” means a capability on the roadmap that has not shipped yet.
Catalog Studio
Available
Model offers, product and service specifications and eligibility rules, without writing code.
Eligibility checks
Available
Check whether a customer can order an offer from your own data sources, then check again at order time.
Order management
Available
Decompose product orders into service orders, run in waves that respect dependencies.
Workflow orchestration
Available
BPMN 2.0 processes your teams can read and adapt, executed by an open-source engine.
Network and resource activation
Available
One asynchronous adapter API towards activation platforms, one adapter per target system.
Event-driven integration
Available
Standard events between components, external subscriptions, dead-letter queue with replay.
Billing readiness
Available
The order completes only once your billing and charging systems confirm.
Observability
Available
Follow an order from capture to billing hand-off, with every event related to it.
Service inventory
Planned
A record of active services and the resources they use, updated by each completed order.
Architecture and integration
Orchestraa sits between the systems that take orders and those that run the network and bill the customer. It replaces neither.
| Connected systems | Examples | Interface |
|---|---|---|
| Order capture | CRM, self-care and portals, partner channels | TM Forum Open APIs |
| Network and activation | Activation platforms, network controllers, resource systems | Asynchronous adapter API |
| Billing and charging | Rating, charging, billing | Billing hand-off |
| Customer data | Customer master data, credit and risk data | Eligibility sources |
At the core: product catalogue, eligibility, product order, service orders, BPMN workflow engine, event bus and observability.
Foundation: Kubernetes and ODA Canvas, PostgreSQL or Oracle, single sign-on with MFA, role-based access.
Use cases
Fixed broadband and fibre
Fibre access, home gateway and voice over IP ordered as one offer, each service activated in the right order.
Runs end to end
Mobile
Plans and options provisioned in billing and charging, then activated once both have confirmed.
Runs end to end
Convergent business offers
Data, voice and options in one composite offer, rolled back step by step when a system refuses.
Runs end to end
Enterprise connectivity
Access, customer equipment and managed services for business sites.
Modelled in the catalogue
IoT services
Connectivity offers for device fleets, with their own eligibility rules.
Modelled in the catalogue
Expected benefits
These are expected benefits of a single orchestration layer, not measured results. They depend on each operator’s systems and processes.
Fewer point-to-point integrations
One layer between order capture, the network and billing.
End-to-end visibility
Orders and events linked by one identifier, from request to billing.
Continuity through to the invoice
Activation and billing hand-off are steps of the same process.
The APIs follow TM Forum Open API specifications and Open Digital Architecture principles. This is alignment with published specifications, not a TM Forum certification.
Full details on the product site
Architecture, platform layers and the status of each TM Forum API are described on orchestraa.fr.
Go to orchestraa.frSee Orchestraa on order journeys like yours.
We run a demonstration on journeys close to yours, using sample data.
Let’s talk about your projectcontact@rylna.fr