- What is it?
- Why do we need it?
- How do we get it?
- Demonstration of a Business Intelligence Tool
The Oracle database used by Banner is designed for OnLine Transaction Processing (OLTP). A data warehouse is designed for a different purpose. It is designed to support ad hoc data analysis, inquiry and reporting by end users, without programmers, interactively and online. This is called OnLine Analytical Processing (OLAP), or Multi-Dimensional Analysis. It is more than just a better set of reports. Mostly for performance reasons, a data warehouse is held in a separate database from the operational database, usually on a separate machine.
The Banner database is designed to be efficient at processing online transactions, and this kind of design is quite inefficient at processing analytical queries and ad hoc reports. This gives frustrating performance for the person making the inquiry, as well as having a significant impact on the performance of the system for regular Banner users.
But there is an even more important reason for building a data warehouse. The structure of the OLTP database is almost incomprehensible to anyone but a programmer. Rules of OTLP database design are broken in a data warehouse to make navigation through the subject areas and data elements correspond to business functions, thus making a data warehouse more intuitive to use.
This results in at least the possibility of being able to ask questions about the data that can be answered without calling on a programmer.
The following table summarizes some of the main benefits that are possible through data warehousing.
|Has a subject area orientation|
|Integrates data from multiple, diverse sources|
|Allows for analysis of data over time|
|Adds ad hoc reporting and inquiry|
|Provides analysis capabilities to decision makers|
|Relieves the development burden on IT|
|Provides improved performance for complex analytical queries|
|Relieves processing burden on transaction oriented databases|
|Allows for a continuous planning process|
|Converts corporate data into strategic information|
Table 1. Benefits of Data Warehousing
Some of the key factors to consider when building a data warehouse are listed in the following table:
Be Ready for the Data Warehouse
Develop an understanding amongst senior administrators of the potential role of IT and data warehousing in achieving the institution's goals.
|Choose The Right Project Team|
Have a Training Strategy
Take appropriate training, and/or hire selected consultants
Choose the Right Architecture
Start small, using a phased approach, but within the framework of a system-wide architecture.
Have a Project "Mission Statement"
Show Early Business Benefits
Choose strategically important subject areas, (i.e. areas that are linked to the Strategic Plan), that have high visibility and fast return. (remember the 80-20 rule).
Evolve the data marts iteratively, constructing the architected data warehouse as you go.
|Understand the Importance of Data Quality|
Be Wary Of Vendor Claims
Choose the data repository, data warehousing tools, and desktop tools with care.
|Use a Proven Data Warehouse Methodology|
|Define and Manage Data Ownership Issues|
|Dont underestimate the Difficulty of Implementing Change|
Table 2 Key Ingredients for Data Warehousing Success
There is a process for choosing strategically important subject areas that starts with the mission statement of the institution, and the goals and objectives. Critical success factors are then identified, as well as the steps for achieving success as outlined in the strategic plan. Indicators are found that can be measured and that can be used to monitor the success of the plan, especially in the areas deemed critical, and also adherence to the plan. These are called key performance indicators, and these form the basis of analytical data models that are provided in the data warehouse.
Raw Banner data for 1997 and parts of 1996 and 1998 were imported into PowerPlay, the business intelligence tool from Cognos. Data reported in the Deans Statistics report from Institutional Research was imported in this example. The demonstration is intended to show some of the flexibility in representing and visualizing data, as well as how the data can be "sliced and diced" and viewed at different levels of summarization. The files are located in C:\My Documents\PPlay.
PowerPlay Transformer dstats.pyg PowerPlay dtstats.ppr
|1.||Heise, D. Data Warehousing
at Avondale College. p15
|2.||Crofts, S.A. You Can Create the Perfect Data Warehouse: Key Ingredients To Data Warehousing Success. (Adapted) The Data Warehousing Institute. Data Warehousing Buyers Guide, Volume 1, 1998. p26|
Created: Tuesday, July 27, 1999, 11:17:12 AM
Last Modified: Sunday, November 23, 2008 1:10 PM