KVK: the model of the trade register
The question
The KVK, the Dutch Chamber of Commerce, renewed the trade register in a large programme, KernGezond. Two things had to come together in it. Legacy systems were phased out, and their data and functionality had to find a place in the new register. And part of the register was rebuilt so that it could be shared with the separate register of ultimate beneficial owners (UBO).
Both needed the same thing: one precise description of what the trade register actually records.
The model
From the existing documentation, the requirements, the legal texts and interviews I built an extensive logical data model in UML of the entire base register. As data modeller and data architect I was responsible for how the whole data aspect of the trade register was recorded.
I drew the processes around the register (filing, registration, consulting other registers and retrieval) in BPMN, in the same concepts as the model.
What followed from it
- The service interfaces. I was responsible for all REST and JSON interfaces on the register. They follow the model, so a consumer sees the same concepts as the registration.
- The database schema and the logic for the rebuilt part that is shared with the UBO register.
- Correction and repair. In that design every piece of data has two timelines: the material one (when did something hold in reality) and the formal one (when was it registered), following GEMMA. With that, for the first time in the history of the digital trade register, corrections and repairs could be handled without errors again.
- Use cases. The use case model, and fellow analysts trained as use case specifiers.
The model on the wall
A model that only modellers can read does half the job. Of the essential parts I made presentable versions on A1, A0 and larger, to grow understanding in the IT organisation and in support as well.
What I take from it
The two timelines have been a fixed part of my work ever since. At Common Ground I worked the principle out further, and in Omnium it has become working software.
The sequel: Common Ground · Knowledge base: time in data (in Dutch)