Ontology-Driven Modelling

Model the business before you model the tables.

Data Masters Decision Intelligence captures the concepts, relationships, events and rules your organisation runs on. That business ontology then drives governed dimensional and semantic models, with evidence and impact visible before anything is applied.

The problem

Table-first design makes the source system the language of the business

A physical schema tells you how data is stored. It does not explain the business concepts, relationships and decisions the data is meant to serve.

Source-shaped

Every system describes the business differently. Customer, account, policy and product definitions get trapped in application-specific structures.

Workshop-heavy

Models begin from a blank page, and teams repeatedly rediscover terms and relationships that already exist in reports and working logic.

Hard to change

Intent disappears inside implementation. When the source changes, reviewers cannot see which business concept, measure or decision is affected.

In the product

The model, as it is built.

One fact, Card Transaction, isolated with the concepts it relates to, and the analytical model generated around it, from the Modelling Studio of a demo banking project.

Modelling Studio
Modelling Studio, focused on one conceptCard Transaction with the customers, cards, merchants, terminals, products, branches and campaigns it relates to.
Analytical model
The analytical model around one factThe Card Transaction fact and its conformed dimensions, generated from the concept map.

See the full product tour

The modelling path

Business reality becomes a governed model

The ontology creates a stable business frame. Your data assets ground it, and Decision Intelligence turns it into governed implementation.

1
Connect
Connect the data assets
Start from the operational and analytical assets already available, with their structure, ownership and business use.
2
Define
Author the ontology
Business concepts, relationships, events, rules, synonyms and ownership, declared in one place.
3
Map
Ground it in evidence
Governed fields and relationships connect to the agreed business concepts.
4
Generate
Models as an output
Kimball-conformed dimensional models, semantic relationships, measures and DAX are generated for you.
5
Apply
Controlled publish
Impact and lineage are previewed, then the change ships through a reviewable plan.

What the model captures

One model of meaning,
many technical outputs

Ontology-driven means one thing here: the technical model stays visibly connected to business intent.

Concepts

Define what the business talks about: customer, account, policy, product, location, with descriptions, synonyms and owners.

Relationships

Ownership, participation, hierarchy and event relationships, expressed at the right business grain.

Rules and measures

Calculation intent made explicit before it is rendered into DAX or a semantic model.

Impact and lineage

Follow a concept into its source mappings, model objects, measures and value cases before approving change.

The chain

Where Modelling hands over

The approved ontology feeds the rest of the chain: Automation builds the foundation from it, Knowledge & Context keeps its meaning attached, and Decision Activation acts on its measures.

Next step

Which number does your team still argue about?

Bring one report, one metric or one argument that never ends. We map the definitions behind it, the evidence, and the model that should follow.