Data Warehousing Steering Committee

November 11, 1998 1:30pm
AD306

Members present David Heise, Chair; Gary Dickerson, Vice-Chair; Brad Christensen, Secretary; Mistee Arias, Derek Bradfield, Rich Forrester, Emilio Garcia-Marenko, Ann Gibson, Pat Mutch, Sharon Pittman, David Penner, Sue Schwab
Absent members Ron Herr, Lisa Jardine, Jack Stout, Ed Wines
Agenda Presented on screen
Prayer David Heise
Introductions David Heise asked members to briefly introduce themselves, and to state what they hoped to see this committee achieve.

Sharon Pittman, Social Work – working on national performance benchmark criteria.

Mistee Arias, Human Resources – efficiency achievable by allowing users to produce reports.

Sue Schwab, Banner Student Support – enable end-user queries and preservation of historical data for Institutional Research.

Emilo Garcia-Marenko – Registrar, source of information for basis of strategic decisions and research.

Rich Forrester, Accounting – providing valid good data to all levels for decision making that is not intimidating.

David Penner, VP Strategic Initiatives & Enrollment Management – look at new opportunities with data to help in decisions, enrollment improvements, adjustments, trends.

Derek Bradfield – Student Financial Services – wants to find out the benefits for the end user(s). Efficiency of services.

Pat Mutch, VP Academic Administration – anxious for user-friendly form of data. Accessibility and usability. Banner implementation concerns in academic area. Faculty database. Program review: credits generated in each major over time, efficiency factors, class sizes over time, other factors involved in multi-year statistics. How little we know about why students leave us and why they come. Trend analysis, financial planning, accreditation needs, HEGIS, NCA reports, etc, especially at department/school level.

Ann Gibson, Dean, School of Business

Some discussion about Banner capabilities regarding faculty data and the lack of reporting ability compared to old system. Wishes for old book that contained data that met needs. Continual training for budget preparation, concern about more effort required for time spent.

Using MS Access takes many hours to create spreadsheets required for analysis.

Hope for user friendliness.

Gary Dickerson, ITS – data warehouse comments about OLTP and warehouse configurations and making it easier to write reports. Standardized reports and custom reports.

David Heise, CIO

Brad Christensen, Oracle/Banner Database Administrator

What is Data Warehousing? Handouts on What is Data Warehousing and Elements to Consider in Data Warehousing Project were passed around. David Heise discussed the document with the committee. Banner is an OLTP database designed for updating. A data warehouse supports OLAP, and is designed for data analysis.

Data warehouses support a subject-oriented view of the data instead of a transaction-oriented view of the data. It integrates multiple, disparate data sources for ad-hoc reporting and inquiry. It helps relieve the development burden placed upon IT and converts the corporate data into a strategic information tool.

Derek Bradfield – question regarding current data in warehouse and the availability to compare historical to current data.

Gary Dickerson – remarks about metadata component in data warehouse.

Pat Mutch – quality of the data question, What about the quality of the data in the data warehouse? As it is being entered? Is any of the data we now have valid? Is it so bad that I/R spends all its time cleaning the data? Can you build a data warehouse if you have bad data?

Ann Gibson – class coding, faculty load reports, students within a class – no way of knowing if student took this course on a special kind of arrangement. Very strange anomalies appear on student course reports/FTE for accreditation. No way of coding exceptions – what is the effect upon data in the data warehouse? How will we know what is going in there?

David Heise – ETL (Extract/Transform/Load) tools help by rejecting unclean data. Also, the transformations and definitions of the data need to be discussed.

Ann Gibson – training concerns, especially in regards to budget.

David Heise – important concern is to not try to build the whole thing at once, show early business benefits, in a short time frame.

Sue Schwab, Gary Dickerson – how do we know what to keep? Do we keep it all?

Ann Gibson – is this all going to be under the control and responsibility of a single person/department?

David Heise – the whole point of a data warehouse is to provide better decision support information.

David Penner – erroneous data? What if it is determined if it is erroneous?

Gary Dickerson – depends upon the data and the business need.

Pat Mutch – must really look closely at the bad data issue.

Sue Schwab – could be in current student data that we have a degree problem.

Business Readiness Assessment Gary Dickerson – distributed a survey instrument regarding business readiness assessment for the committee to fill out. Questions were fielded regarding the terms in the survey and how they translated to an academic environment.
Project Charter Framework Gary Dickerson – discussed the framework for the data-warehousing project. It is not set in concrete, it can be changed. It is a tool to help in the process of developing a data warehouse.
Next Meeting Date/Time 18 November, 1998, 1:30 PM in AD306
listserv Address DWSteering@andrews.edu
Web Site http://www.andrews.edu/ITS/AS/dw/