1. Data Warehouse and Reporting
Panel Discussion

2. Panel Participants
University of Northern Colorado Bret Naber – Director of Applications and Database Development
Colorado School of Mines Tom Boyd - Dean of Graduate Studies
Colorado Community College System Julie Ouska - Information Officer / Vice President

3. UNC Reporting Architecture
ODS Oracle gig
EDW 1.4
Nightly Refresh average – 1-2 hours
Full Loads – hours
Banner 7.3.x - Oracle gig
Webfocus 7.6.6
Developer Studio
Report Caster
Resource Analyzer
AD Authentication

4. More information All Faculty/Staff have accounts Three Tiers of users
Request access to “Views”
Three Tiers of users
Report viewer
Report writer
Report developer

5. UNC - Project Goals
Create a central repository of all critical institutional data that is available to all academic and administrative units
Validated data
Appropriate data security

6. UNC - Project Goals continued
  Provide relevant , consistent and timely reporting and analysis to decision-makers at all levels of the university
Single source of the truth
Standardized data definitions
Relevant data collected
Decentralized skilled report writers
Identification of key performance indicators
Centralized analysts of complex information

7. UNC - Project Goals continued
Consolidate and streamline existing reporting processes
Effectively use specialized skills of complex analysts
Leverage business process and subject matter expertise of report writers in administrative areas

8. TemporaryProject Manager
Project Leadership
TemporaryProject Manager
Decision Support Project and Information Management Team
IT ADDS Team
System Adminstrator
OBIA
Strategic Analysts
College Power Users & Report Writers
Other Academic Power Users & Report Writers
Business System Trainer/ Report Director
Temp Report Coordinator - Peggy Hoff
Administrative Data Stewards (incomplete list)
Graduate Robbyn Wacker
Report Coordinator
Power Users & Report Writers
Auxillary Tobias Guzman
Financial Aid Donni Clark
Student Nolan Oltjenbruns
Admissions Chris Dowen
HR Marshall Parks
Finance Paul Squillace
Various Cross-Functional Project Teams

9. CHECO Building Your Own Data Warehouse
September 23, 2008

10. I’ll go on the record that I don’t recommend the “Build It Yourself” approach. But if you want to go that direction, I have some suggestions.
Fall CHECO Conference
11/11/2018

11. Start by thinking about the end result first
Institutional research?
Operational reporting?
Longitudinal analysis?
Student / Financial Aid?
Finance?
HR?
Fall CHECO Conference
11/11/2018

12. Random Thoughts
The more data required, the more complex the infrastructure and technology becomes
Analysis over time requires the ability to freeze data snapshots
It is not always obvious where the data resides in Banner – you will guess wrong a lot.
Think about ETL upfront. Lots of data will probably require an incremental refresh later. Very difficult to retrofit.
Not an IT project – executive leadership is required. Functional user input also required.
Banner must be the authoritative data source – don’t “fix” stuff in the DW that is wrong in Banner, fix the data/process in Banner.
Start small and expand on success
Fall CHECO Conference
11/11/2018

13. Infrastructure is critical
If the extract, transform & load process does not work well, your staff will spend all their time working on ETL, and not on developing views and reports.
Make it easy to add new data
Put data in the DW once, use it many times
Agree on the transformational values such as FTE, full-time, part-time, etc., up front and across the institution
Fall CHECO Conference
11/11/2018

14. Success factors Discrete project with a reasonably sized data set
Go for the 80/20 rule
Look at the reports that are used over & over – variation on a theme
Use a web-based, click & point reporting tool for most users
Expand use slowly, use focus groups to improve data and delivery
Validate data very carefully & thoroughly
Fall CHECO Conference
11/11/2018

15. Additional thoughts or questions?