Chaos → Insight → Pattern → Structure → Automation
From information monsters to information patterns.
A ready-to-implement enterprise ontology and architecture template for master data, reference data and code lists. Unstructured information becomes unambiguous and automation-ready with a complete set of building blocks, relationships and business rules.

From information to structure and governance
Building blocks
What is the information?
Information building blocks are the fundamental information objects, for example:
Unit, Manager, Employee, Place, Application
Information patterns
How does the information connect?
Information patterns combine building blocks and relationships into reusable structures.
Business rules
Which rules apply?
Business rules describe requirements the information and its relationships must follow.
VR-ORG-004 · VR-ORG-005Reference Data
Which shared references are used?
Reference data brings together code lists, reference registers and standards, for example Manager code and the Countries register.
A · B · C
used in
Business processes
Where is the information used?
Business processes show which building blocks are normally needed in different business contexts.
A parallel perspective: processes do not own the information, they show where the same blocks and patterns are used.
Building blocks
The fundamental information objects – for example Organisation, Unit, Person, Place and Application.
Explore building blocksInformation patterns
Reusable ways of describing how building blocks relate to each other.
Explore patterns- “A unit has only one manager.”
- “A unit always has staff.”
Business rules
Rules and requirements the information and its relationships must follow.
Explore rulesBusiness processes
See which information is normally needed in different parts of the organisation.
Explore processesHow an information pattern works
Employee with a manager code. Manager is not a separate information object. The red ring marks an Employee with a manager code, and the relationships state which unit, cost center or employees the person manages.
Pattern D – Employee, manager and unit · Open the patternBuilding blocks describe what the information is. Relationships show how it connects. Business rules state the requirements the structure must meet.
Rules that apply
Explore by area
Organisation
- Organization
- Unit
- Employee
- Manager
- Committee
- Administration
Finance
- Cost center
- Budget
Geographic location
- Geographic area
- Country
- Locality
- Place
- Address
- Position
Person
- Person
IT
- Application
- Client device
- Access right
- Digital identity
- Account
Customer and supplier
- Customer
- Supplier
Product and service
- Business service
- Product
Process
- Process
- Process role
- Business goal
- Formal competence
- Functional competence
A shared structure for information
When information is defined and structured consistently, the same model can be reused across processes, systems, integrations, reporting and analysis.
The patterns use the public sector as a reference point, but the underlying structures for master data, governance and accountability are universal and apply equally to the private sector.
A consistent structure relies on defined business rules:
Unit hierarchy and manager hierarchy
Latest from the blog
See all postsGood solutions · 10 November 2026
When a flow becomes master data – a line of reasoning
Master data never appears out of nowhere – it is born in a transaction. Here we examine the moment when an ordinary information flow becomes a state the whole organisation depends on.
Read the articleGood solutions · 5 November 2026
Stop cleaning data in a hub – hold a mirror up to your source systems
Many organisations spend large sums on MDM hubs that quietly correct faulty details. But when the hub cleans the data, the source systems stay wrong and responsibility disappears. Quality only improves when the people entering the details see which business rules were broken and who should fix the error.
Read the articleLess good solutions · 2 November 2026
It is not technical debt – it is information debt
When integrations stall and automation fails due to constant exceptions, we almost always blame technical debt and legacy systems. But the real bottleneck is rarely the code. It is information debt – and brand-new, modern cloud applications become part of it the moment they launch with their own isolated data models.
Read the articleExplore the information patterns
See how building blocks, relationships and business rules together create reusable structures for your organisation's information.
Start here – Understand in five minutes