Update on Decision Support

1
Update on Decision Support

• Fall 2001 CCSP Conference
• November 7, 2001
• Linda Bair, Interim Director, Decision Support
• Mark Cumbow, Project Coordinator, Decision
  Support

2
Agenda
I. What is Decision Support ? II. Decision
Support Projects III. Impact on Campus Units
3
I. What is Decision Support ?
4
Vision

• University data managed as an asset
• Central repository with data that is
• reliable
• timely
• cleaned
• integrated
• documented
• supported
• Reduce duplication - free up departmental
  resources
• Responsive to college and department needs

5
Decision Support Mission

• To support integrated and secured management
  reporting, analysis and decision making
•  
• By providing the University with the
  infrastructure and services to access data and
  metadata

6
A New University Function

• Identified as necessary during the ERP selection
  process
• ERP will replace major University administrative
  systems
• ERP project UI-Integrate project
• Decision Support will operate in parallel with
  UI-Integrate
• Will become a permanent function of the
  University
• Currently funded at 20 M / 5 years
• Approximately 9 of the UI-Integrate Budget

7
Organization
University of Illinois President
Vice President Administration Vice President
Academic Affairs
Decision Support Steering Team - Oversight -
Priority setting - Direction
Associate Vice President AITS
Associate Vice PresidentPlanning Budgeting
Director of Decision Support
Assistant VP AITS
8
Objectives

• To build an environment for reporting and data
  access
• Data Warehouse
• Industry best practices
• DS staff dont create reports - they make it
  possible for others to do so
• To make administrative data accessible and easier
  to use by providing services, such as
• Training On content and techniques
• Support Assistance on content and technical
  questions
• Documentation - Metadata on meaning and source of
  data
• Assist users in transition to new environment
• Distribution of standard university reports

9
Scope

• 1. SCT Banner data
• Decision Support works closely with UI-Integrate
• Parallel schedule
• 2. Historical data
• Amount determined by DS requirements process
• Timing
• 3. Data from non-Banner operational systems
• System must have a campus or university-wide
  focus
• Example University codebook
• 4. Existing Information Warehouse (IW)
• IW data will freeze as UI-Integrate replaces
  current systems
• IW users will transition to Data Warehouse

Please note that this scope will be phased in as
Decision Support grows.
10
Current Activities

• In early stages of build
• Preparing for limited release of
  Biographic/Demographic data in December
• Technical architecture developed and multiple
  environments prepared for Enterprise Data
  Warehouse (EDW) and reporting tools
• Logical and physical data models created for EDW
• Test data created and data movement scripts
  underway
• Tools readied to support UI-Integrate report
  development and distribution
• Preparing for new releases in 2002
• Benefits Administration in August 2002 (HR only)
• Recruiting and Admissions in September 2002
  (University wide)
• Six Finance modules in July 2003 (University wide)

11
II. Decision Support Projects
Data Warehouse Mainframe Data Transition Project
12
Data Warehouse Overview
Data Warehouse Enterprise Data Warehouse Data
Marts
13
Data Warehouse Methodology

• Software Tools Selected
• ERwin for modeling
• Informatica for data movement
• Business Objects for enterprise reporting
• Strategies and Procedures
• Technical Architecture
• Requirements
• Data Management
• Quality Assurance
• Disaster Recovery
• Security
• Training
• Communications
• Services
• Implementation Partner Headstrong
• Standard data warehouse practices
• Tailored to UI environment

14
Enterprise Reporting Software

• Goal
• University recommended software for desktop
  query, reporting and analysis
• Server-based distribution of standard reports for
  UI-Integrate and other providers
• Progress to Date
• University license was negotiated with Business
  Objects in August.
• Business Object components include Web-based
  report distribution, report retrieval and
  manipulation and ad hoc query and analysis.
• Software was installed, staff were trained, and a
  test and production environment set up in In
  August and September.
• Course materials on report viewing and printing
  were developed in October.
• A Business Objects universe was created based
  on EDW test data by October.
• UI-Integrate staff are now developing standard
  reports for December release.
• Next Steps
• Decision Support will support first users in
  December - HR users accessing HR reports
• Decision Support will develop a roll-out plan for
  further deployment
• Starting in December, Decision Support will
  develop plans for 2002, e.g. phasing in wider
  access, including roll out schedule, security
  strategy, additional training courses and support
  services.

15
Development Environment
16
Production Environment
17
Mainframe Data Transition Project

• Scope
• A salvage operation to prepare for mainframe
  decommissioning in FY 05
• Move data to a Unix server with minimal
  transformation
• Text files to text files
• Mainframe databases to Oracle
• Tasks and Status
• Technical pilots - completed
• Technical staff compile major systems list - in
  process
• Discussions with users - on hold pending staff
  hires
• Publish schedule and plan
• Review by Decision Support Steering Team

18
Long Term Picture
Mainframe
Data from Bannerand other operational sources
Initial Banner conversion
Mainframe Data Transition Project
Bio/Demoin Dec 2001
Gradual inclusionof historical data
ReplatformedMainframeData
BannerData
Data Warehouse EDW (now)Data Marts (future)
Ad hoc accesswith Business Objects (future)
Banner screens direct inquiry
Standardmessaging interface
Other access as required
EDDIE Business Objects based - Report
distribution/Data Access (Partial roll out in
December and phased in after that)
Enterprise Data Delivery Information Environment
19
III. Impact on Campus Units
20
Impact Will Be Phased In

• Consumers of standard UI-Integrate reports
• Recruiting and Admissions - September 2002
• Finance - Summer 2003
• DS connection
• Some UI-Integrate reports will be based on Data
  Warehouse
• Some UI-Integrate reports will be distributed
  through DS managed portal (EDDIE)
• Units with existing feeds into University
  systems, e.g. UFAS
• Those units may work with UI-Integrate to migrate
  feeds into Banner.
• On UI-Integrate schedule
• DS connection
• Data from Banner is migrated to the Data
  Warehouse
• Institutional Research units and other
  report/data service providers
• DS connection Initial familiarity with Data
  Warehouse in spring 2002
• Units with local data systems
• DS connection
• Some units will want data feeds to capture data
• May query the Data Warehouse for data to combine
  with local data
• First impact in September 2002. (Prior to 2002,
  HR only modules)
• Access to Data Warehouse for queries

T i m e
21
Avenues for Campus Input

• 1. UIUC Members of Decision Support Steering Team
  
• Carol Livingstone, Director, Division of
  Management Information
• Richard Nelson, Staff Associate, College of
  Engineering
• Ruth Vedvik, Director, Office of Admissions and
  Records
• Robert Wengert, Chair, Department of Philosophy
• 2. Decision Support Web site - www.ds.uillinois.ed
  u (November)
• 3. UIUC Campus Data Steward position (search in
  progress)
• New position on each campus - Connected with DMI
  at UIUC
• Part of Decision Support Custodian Council
• Role in user services and user representation
  within Decision Support
• 4. Decision Support Requirements Process
  (future)
• Systematic process to assess user needs and
  develop/design based on needs
• Focus group sessions for each release -
  participation by college/department staff
• 5. User Groups (future)

22
Campus Connection User Group(s)
Campus User Group(s)

• Campus Data Steward
• Is a DS Team member
• Participates in User Group(s)
• Hears issues
• Provides information

• User Group Options
• Subject oriented, e.g., Student, HR, Finance
• Technical subgroups
• Transition planning by source, e.g., Paymaster,
  UI Direct

Search in process for UIUC Campus Data Steward.
Discussions about User Groups will start next
semester.
23
Many IssuesTo Be Addressed

• A partial list - not all Decision Support
• When will colleges and departments be able to
  implement data feeds from the Data Warehouse?
  How will they be supported?
• How will security and confidentiality be
  maintained relative to data feeds from the Data
  Warehouse?
• My unit needs transaction data - what level of
  detail will be available in the Data Warehouse?
• How will colleges and departments know who is
  going to re-develop a particular report? UI2, DS
  or left up to us?
• When will my unit be able to write queries
  against the Data Warehouse?
• Will I have to go to two systems to get data that
  I now get from one ?
• If our unit is purchasing a DBMS, should we
  purchase Oracle to be compatible with the Data
  Warehouse?
• What tools do I need to buy and when?
• How do I know who to contact to give Decision
  Support my requirements?
• What technical consulting will Decision Support
  provide for units with local systems?

Decision Support will start to address these
issues next semester. Responses will be on DS web
site.
24
Data Feed Issues Comments

• Data Feeds from the Data Warehouse will be more
  of a relationship than anonymous data shopping
• DS will allocate staff to consult on this topic.
• Data security must be addressed before data feeds
  take place.
• Training and discussion on appropriate use will
  be scheduled before data feeds.
• DS will work with units to ensure continuity of
  security and confidentiality after data feeds.
• Units and DS must work together on maintaining
  data quality and integrity after data feeds.
• We will have to address technical questions such
  as how to combine local data databases with data
  from the Data Warehouse.
• We will have to address questions of meaning, as
  in how do you match old categories of data to new
  categories.

Decision Support will start to address these
issues next semester. Watch for responses at the
DS web site.
25
Transaction Data

• Many unknowns about access to transaction data
• Some units needs for transactions will be
  replaced by online Banner. (UI-Integrate)
• Some units will subscribe to standard transaction
  messages through messaging directly from Banner.
  (AITS)
• Many units will migrate to the Data Warehouse
  where there will be high quality, detailed data.
  (Decision Support)
• When and how units should assess their
  transaction data needs is not yet clear.

Decision Support and UI-Integrate will both be
involved in addressing these issues.
26
Points To Remember

• Goal of Decision Support is improved data
  services to the University community.
• Decision Support is closely tied to UI-Integrate
  schedule but is a permanent function (not part of
  UI-Integrate).
• Decision Support / Data Warehouse is in a build
  stage.
• College and department representatives will be
  involved in the DS requirements process.
  Products of requirements will be posted on DS Web
  site.
• Questions on data feeds, tools training and
  transaction data will have to be worked out
  between staff and campus units.
• The usefulness of Data Warehouse will increase as
  quantity of data expands (on UI-Integrate
  schedule)
• DS Web site will be a good one-stop for updates.
  www.ds_at_uillinois.edu

27
Questions? Discussion?