Ensemble Modeling for Data Vault

by | Sep 29, 2016

I recently had the privilege of attending Hans Hultgren’s “Advanced Data Vault Summit” at his offices in Golden, Colorado. Shane has written how Data Vault fits into our wider Agile BI framework here.
A privilege, and a fantastic experience, to work with such a knowledgeable and talented group of people.
One of the (many) take-outs that I got from the Summit, is the prominence of Ensemble Modeling.
Ensemble Modeling is a technique, which has grown out of the Data Vault movement.
Like Data Vault, it is elegant in that it concentrates on just 3 constructs – Core Business Concepts, Core Business Relationships and Attributes.
While this terminology isn’t new, the emphasis has shifted from “Business Keys” to “Core Business Concepts”.
Subtle as this may be, it revealed how well Ensemble Modelling can map the data in an organisation, from a logical perspective.
From there, it maps very directly down to the physical implementation of a Business Vault, or for that matter, a number of alternative warehousing design patterns.
Supporting this more Logical idea is the concept of ELF (Ensemble Logical Form).
ELF embraces the view that modelling Core Business Concepts, Relationships and Attributes is common to a number of Data related exercises, over and above Data Warehousing.
Uses for ELF include Data Warehouses, Data Lakes, Master Data Management (MDM) and operational integration initiatives.
To me, this makes complete sense as a starting point for most Logical Information Architecture exercises.
Watch this space.
Keep on inventing – Brian
Brian blogs about how data warehouses are modelled.
You can read Building Star Schemas from a Business Data Vault or all of Brian’s blogs here.
We run regular Data Vault course for business analysts, data architects, and business intelligence developers in Wellington and Auckland. Find out more here.



  1. Data Vault blogs you need to read | OptimalBI - […] Ensemble Modeling for Data Vault […]
Submit a Comment

Your email address will not be published. Required fields are marked *