ZhiOne
How ZhiOne works
Built from components, not from one block
ZhiOne is divided into the components of TM Forum's Open Digital Architecture (ODA). Each component owns its part of the business and its data, exposes it through a TM Forum Open API, and announces its changes as events. Another component, or another system of the operator, reaches that data only through the API, never through the database.
A customer or a channel acts
A sales portal, a self-care application or a partner's system calls the component's API.
The component decides
It checks the request against its rules and owns the result.
The process continues
An order, for example, moves from capture to delivery through a process engine that calls each component in turn.
Everyone hears of it
The change is published as an event, so billing, inventory and notifications follow without being asked.
Around the components
| Part | What it does |
|---|---|
| Sign-in | Standard OpenID Connect, connected to the operator's identity system |
| Permissions | Roles and permissions as TM Forum's Permissions Management defines them |
| Processes | A process engine for orders and their delivery |
| Integration | Adapters to the operator's own systems, such as its payment gateway |
| Record | Every change kept as an event, and an audit log of who changed what, and when |
| Daily work | Comments on records, and each record assigned to the member of staff who handles it |
| Background work | Long jobs run as batches, apart from the people using the system |
| Platform | Containers on Kubernetes, released and rolled back as pinned versions |
What stays with your other systems
The network side of the operator, such as service and resource inventory, fault and performance management, stays in the systems that run it. ZhiOne connects to them through the same standard APIs.
Talk to our specialists
Tell us about your environment and what you need. One of our specialists will answer you.