Functional data model

The Opencell Data Model refers to the various objects (we call them “entities”) that are used to make the system work.

These entities are described in the various sections of the Product documentation.

Functional domains

The entities are organized in a functional data model.

The diagram below is an excerpt from our Opencell University classes and shows the main entities and their relations.

High level functional data model with processes

Here is a conceptual and functional scheme to follow:

• order links Customer to Catalogue to produce a subscription

• Subscription is processed by Rating jobs from Billing

• Bill cycle is done through invoicing job

• Invoicing job produces Invoice and triggers accounting and then payment

Customers

Catalog

The model below presents the different objects that are used within Opencell model (not exhaustive), though some do not appear in the Portal.

Usage to Payment

The below schema presents all jobs and objects that are related together to go from subscription and usage toward invoicing, payment and accounting. The key point in the process is the Bill Run to produce the invoice and trigger the accounting.