Business models drive agility

In this post I want to show you one of the key components to achieving an agile data warehouse – the business information model. We use this capability to drive everything in and about the warehouse – its structure, its content and its ability to rapidly change. The business model gives us a common language that both IT and business people can understand. Take a look at the video to get a quick tour of what the business model is about.

[vsw id=”21CTOcPMgVU” source=”youtube” width=”425″ height=”344″ autoplay=”no”]

You can see that these models can quickly become very complex. And yet they can still be made easy to understand and navigate. Even better, when you need to make a change, no jackhammers are required!

But the business model is more than just a nice picture. Kalido reads in the model and of course it creates all the tables like a data modeling tool would do. But it also creates routines to load data, enforce business rules, and all the operational routines required for development, deployment and the ongoing care and feeding of the warehouse.

Check back for future videos that cover some of the capabilities in the model and the Information Engine that automate warehouse processes.

3 replies
  1. Kamlesh
    Kamlesh says:

    Hi John,

    I liked the way you explained the Kalido BIM.

    I have deployed the Kalido BIM to Kalido DIW. We are using Kalido DIW 8.5. I would like to know how Kalido ” creates routines to load data”?
    Because as of my expereience in Kalido, I believe we need to create and define the feeds to load the data. What kalido does is ofcourse population of attribute and mapping tables enforcing it’s integrity and constraint rules.

    I would like to know what do you mean by Kalido “creates routines to load data”.


  2. John Evans
    John Evans says:

    Kamlesh, thanks for your question. I see you also posted this question to the Kalido Community on LinkedIn, but to close the loop for other readers: If you use the staging table loaders for either reference data or transactions, you don’t have to create file definitions. The load routines assume the mappings based on the staging table definitions.

    You would need to write scripts to populate the staging table. If this is just SQL it can be done from within Kalido. After a load the Kalido loaders always mark the bad records that do not conform to the business model. These bad records can be managed from the suspense screens within the Kalido Information Engine. You can also instruct the loaders to mark the good records as well. This means that you do not have to clear out staging immediately after a load. We have some customers that will keep a few days worth of history in the staging tables as this makes troubleshooting of data issues a lot easier.

Trackbacks & Pingbacks

  1. […] when describing requirements for their BI and data warehouse systems. Readers of my prior blog posts will know that we suggest a business model as a tool to use to bridge this […]

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply