We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.

Blog: Dan E. Linstedt Subscribe to this blog's RSS feed!

Dan Linstedt

Bill Inmon has given me this wonderful opportunity to blog on his behalf. I like to cover everything from DW2.0 to integration to data modeling, including ETL/ELT, SOA, Master Data Management, Unstructured Data, DW and BI. Currently I am working on ways to create dynamic data warehouses, push-button architectures, and automated generation of common data models. You can find me at Denver University where I participate on an academic advisory board for Masters Students in I.T. I can't wait to hear from you in the comments of my blog entries. Thank-you, and all the best; Dan Linstedt http://www.COBICC.com, danL@danLinstedt.com

About the author >

Cofounder of Genesee Academy, RapidACE, and BetterDataModel.com, Daniel Linstedt is an internationally known expert in data warehousing, business intelligence, analytics, very large data warehousing (VLDW), OLTP and performance and tuning. He has been the lead technical architect on enterprise-wide data warehouse projects and refinements for many Fortune 500 companies. Linstedt is an instructor of The Data Warehousing Institute and a featured speaker at industry events. He is a Certified DW2.0 Architect. He has worked with companies including: IBM, Informatica, Ipedo, X-Aware, Netezza, Microsoft, Oracle, Silver Creek Systems, and Teradata.  He is trained in SEI / CMMi Level 5, and is the inventor of The Matrix Methodology, and the Data Vault Data modeling architecture. He has built expert training courses, and trained hundreds of industry professionals, and is the voice of Bill Inmons' Blog on http://www.b-eye-network.com/blogs/linstedt/.

There are many definitions of governance, compliance, and accountability in the industry, and it seems as though many of us are struggling to define it for the EDW/BI space in some generically acceptable way.  As I've recently researched these subjects (and been involved in them for years) I've noticed a trend that many of the definitions are vertically challenged (if you will).  They focus on a vertical industry rather than on horizontal enterprise data warehousing. 

In this entry I'll add my two cents to this noise as just another voice of opinion on these subjects.

Governance can be defined many different ways, there are hundreds of definitions there - and in B-Eye Best practices section of this site, there are discussions, white-papers, and so on.  Many resources to define governance.  My opinion on the matter is as follows:

* Governance for EDW and BI should be about managing, monitoring, optimizing, fixing whats broken, and producing ever increasing quality work product.  It involves people, process, and technology - all aspects of the game, and it's focus should be horizontally driven across lines of business in order to meet the needs of the enterprise and BI initiatives.

* Compliance for EDW and BI should be about the meeting agreements, showing progress in governance, between IT and internal business, and the enterprise and it's external customers.  Good "compliance" means (in my opinion) meeting service level agreements between organizations both inter-organization and intra-organization.  Applying compliance in the EDW BI landscape means upholding standards and delivering quality auditable information across the business.  Service level agreements should cover the "data" that is delivered, as well as the people and processes used to meet the needs.  Compliance means setting standards that multiple parties agree to, and then reaching those levels of delivery.


* Accountability for EDW and BI team should be about the ability of business to stand up and take ownership of mistakes made, errors and omissions in meeting both compliance and governance initiatives.  It should be horizontally focused across the enterprise, and should include the data warehouse information delivered in reports on a daily basis.  This includes the raw-data-store for good-bad-and-ugly data in the EDW, along with the "quality cleansed" data stores used in data marts, along with ensuring that numbers match at a corporate level when necessary.  Accountability is all about the people taking ownership of their mistakes, admitting errors, omissions, and optimization opportunities at the process level, then applying this to the systems.

These are my introductory thoughts, I would love to hear from you about what you would add, change, or remove from these definitions.


Dan L, DanL@GeneseeAcademy.com

Posted May 6, 2009 6:51 AM
Permalink | No Comments |

Leave a comment

Search this blog
Categories ›
Archives ›
Recent Entries ›