Future-proof your data solution with a double timeline
To future-proof your data solution, consider implementing both a technical and business timeline from the start, so you have flexibility when data maturity increases.
To future-proof your data solution, consider implementing both a technical and business timeline from the start, so you have flexibility when data maturity increases.
By plotting, and then combining, bitemporal and historised data sets on a cartesian plane it’s really easy to understand bitemporal behaviour.
When delivering data from the integration layer (e.g. a Data Vault model) to the presentation layer (anything, but usually a dimensional model or wide table), a key requirement is re-organising data to the selected ‘business’ timeline for delivery.
During this process, we leave the safety of the assertion (technical) timeline behind and start using the real-world state timeline for delivery. This may create some unexpected results!
The data is wrong! No, it’s not wrong, we’re just looking at it from different points in time. This post shows how a data warehouse helps to manage this common topic on data interpretation.
More
Moving to Europe (The Netherlands) - July 17th, 2025