Most of the time Opencell doesn’t live on its own, isolated from other systems.
It usually sits between a CRM and an ERP, with connections to many other applications (technical platforms, selfcare, BI, …)
This is easily achieved thanks to Opencell’s extensive API and other integration features such as Webhook, notifications, JMS queues, …
Data governance
Ordering can happen within several, cumulative or not, scenarii. Below is a non-exhaustive table to show the different roles that Opencell can handle within a functional architecture.
Opencell is mostly a billing & invoicing system, with mediation capacities, though for extensive and complex usage management, a dedicated mediation should be preferred.
Also, Opencell proposes a lot of functionalities to manage user accounting and reporting, though for many day to day reporting and monitoring, a financial BI tool should be preferred.
|
Ordering |
Billing & Invoicing |
Payment |
ERP, General Accounting & BI |
|---|---|---|---|
|
Other system with one shot payment, responsible for commercial eligibility |
Opencell |
Other system triggered by Opencell |
Other system |
|
Opencell Selfcare, responsible for commercial eligibility |
Opencell |
Other system triggered by Opencell |
Other system |
|
Opencell CustomerCare, responsible for commercial eligibility |
Opencell |
Other system triggered by Opencell |
Other system |
|
Other system with one shot payment, responsible for commercial eligibility |
Opencell |
Other system NOT triggered by Opencell |
Other system |
A typical integration map
