IT beyond selling hot air.

Concrete, applicable and thorough: one model for the data, the processes and the rules of your organisation.

How it works

The basis: data, processes and rules

Together these three carry the whole functioning of an organisation. Services, vision, goals and what comes from outside lie around them.

External rules and constraintsVisionGoalsServicesExternal taskDataProcessesRulesread, writeguardsteer
DataUML
What the organisation knows and records.
ProcessesBPMN
What happens, in what order and by whom.
Rules
What is allowed and what is required.

One model. The rest follows from it.

From the model follow the interfaces, the register, the requirements and the documentation.

«canonical model»Inschrijving
  • kvkNummer : Nummer
  • rechtsvorm : Rechtsvorm
  • geldigVan : Datum
  • geldigTot : Datum
  • geregistreerdOp : Tijdstip
  • OpenAPI · XSDService interfacesMessages and APIs that say the same as the model, because they come from it.
  • SQLThe registerA schema that gets history, correction and repair right from the start.
  • BPMN · use casesProcesses and requirementsWhat happens to the data, in the same concepts as the model.
  • A0Documentation that gets readFrom the reference for developers to the poster on the wall for the business.

Now: Common Ground

For VNG, the association of Dutch municipalities, I work on Common Ground: the bitemporal register, the municipal data model, federated access control and the question of how APIs deal with history.

Read about this work

Before: the trade register

For the KVK, the Dutch Chamber of Commerce, I made the logical model of the entire trade register, with the interfaces and the design for correction and repair.

Read the case

Blog and knowledge base

The blog and the knowledge base on modelling, time in data and Dutch government standards are written in Dutch.

To the blog (in Dutch)

Shall we talk?

A one-hour conversation is usually enough to see whether and where a model will help you.

Get in touch