Data Warehouse or Business Intelligence?
One of the frustrating and confusing aspects about the Business Intelligence (BI) and Data Warehouse (DW) field is the fact that the industry cannot settle on a single term to describe it. I guess this shouldn’t be surprising given that the industry also can’t agree on a single architecture, data modeling technique, reporting tool or development methodology either!
Back in the days when information technology was called electronic data processing, what is today called business intelligence or data warehousing was called decision support. Beginning in the late 1980s, a number of leading technology consultants began popularizing the term data warehousing to describe an end-to-end solution for extracting, storing and reporting business data.
About ten years later, the term business intelligence emerged to describe a more business focused approach to data warehousing that put the business users’ access and information visualization front and center when it came to deploying an enterprise information repository.
While we no longer use decision support to describe the technology industry, I continue to hear people using both business intelligence and data warehouse – sometimes interchangeably – to describe an enterprise information repository. Because there is no consensus on a name, I’ve been seeing the rather clunky phase “data warehouse/business intelligence” (BI/DW) used more and more in articles and books to describe this industry.
A few years ago, I was working as a consultant on several BI/DW projects simultaneously. As I drove around Wisconsin I had to remind myself to use each client’s preferred BI/DW terms to avoid being misunderstood.
When I was overseeing a financial reporting project for the Department of Workforce Development in Madison, I referred to what we were building as a data warehouse. On the other hand, I was helping build an enterprise business intelligence system when I assisted the Harley-Davidson team in establishing their business intelligence project methodology. When I headed up the road to Appleton, to work for Thrivent Financial, I was building a data warehouse when I was reviewing data models but deploying business intelligence when I spent time with the team charged with establishing a business intelligence center of excellence.
To my mind, the terms business intelligence and data warehouse are not the same thing; although they are linked in that you cannot have business intelligence without some kind of a data warehouse. Just like a physical “house” is required to make a “home,” a data warehouse is the physical foundation upon which an organization builds its business intelligence competency.
Business intelligence is the merging of strategy, people, process and technology for the purpose of transforming business data into business information. This transformation of data to information allows the people who work for the business or interact with the business to make better decisions using reliable, understandable, and timely information.
A data warehouse, on the other hand, is a critical foundation (databases, tools, interfaces, methodologies, etc.) that must be in place to support the organizational development and effective use of business intelligence.
To deploy true business intelligence, an organization must have (in addition to a data warehouse and its associated components) a solid business intelligence strategy aligned with the larger enterprise strategy.
In addition, BI requires that certain organizational structures and teams be in place to build, use, and enhance the organization’s business intelligence competency.
Lastly, because, BI is an ever changing and maturing competency, meaningful business intelligence requires that an organization has processes in place to constantly re-evaluate and enhance its business intelligence strategy, organization structures, and BI processes.
