Connect all of your systems
Our data ontology standardizes key fields across multiple systems and allows you to seamlessly connect your data and adapts your CMS for future use cases.
The stack
Every system your cargo business runs on, resolved into one model
Underneath, the systems of record, each with its own version of the truth. Above, decisions that have to be made in minutes. In between, one model both sides agree on.
Airlines do not need another system of record. They need one model that makes the systems they already have agree, and that decisions can be written back into.
Figure 1
The objects an airline cargo business actually runs on
Fifteen object types, every link named and directional, every property typed and traced to the system it came from. This is the model underneath Belli: not a data warehouse schema, an operating model.
Objects are grouped by the part of the business that owns them. Links are named because the name is the business rule: an allotment holds_capacity_on a flight, so releasing it changes what can be sold. Hover any object to isolate its neighbourhood.
Figure 2
One model between the systems of record and the decisions
Airlines do not lack cargo data. They lack one place where a term means one thing. The ontology reads from every system of record, resolves the conflicts once, and writes decisions back to the systems that execute them.
The systems of record stay. What changes is that every one of them now resolves into the same objects, and every decision made on those objects lands back in the system that has to act on it.
Figure 3
A shipment, from quote to settlement, as the model sees it
Seven stages. At each one, signals arrive from the operation, objects change state, and a decision is written back. Nothing here is a status field: every transition is a modelled event with a source and a time.
The same objects from Figure 1, moving. Each stage is defined by what the model learns and what it decides, which is why a delay at stage 04 is priced against the contract at stage 01 without anyone re-keying it.
Figure 4
How the model stays true: we run this on ourselves
A model is only worth the discipline behind it. Ours is checked against the running code every night, and no definition changes without a person who does the work signing it off.
This is the loop we run internally, and the one we set up with airlines. It is the reason the objects in Figure 1 still describe the operation six months after they were written.
See it on your own data
Integrations, messaging and the systems Belli connects to are on the Integrations page.