Presented to Common Solutions Group - PowerPoint PPT Presentation

1 / 23
About This Presentation
Title:

Presented to Common Solutions Group

Description:

Data Management at the UW Bill Yock Associate Vice Provost Enterprise Information Services Office of Information Management Presented to Common Solutions Group – PowerPoint PPT presentation

Number of Views:89
Avg rating:3.0/5.0
Slides: 24
Provided by: annw197
Category:

less

Transcript and Presenter's Notes

Title: Presented to Common Solutions Group


1
Data Management at the UW
Bill Yock Associate Vice Provost Enterprise
Information Services Office of Information
Management
Presented to Common Solutions Group Sept. 27, 2007
2
Data Management at the UW
Trivia Which ski resort holds the world record
for most snowfall in a season?
Mountain Dog Pepper
Answer Mt. Baker 1,140 inches, 1998 - 1999
3
Agenda
  • Background - Current Technologies and Strategies
  • IS Futures Report
  • New Office Information Management (OIM)
  • New Data Management Committee (DMC) Task Forces
  • UW Information Map, Metadata Definitions
  • Security, Access, Use Policies
  • Data Trustees Stewards
  • Top 5 Questions that Deans want answers too.
  • New Enterprise Information Services (EIS)
    Division
  • Application Integration Services
  • Decision Support Services
  • Data Management Services
  • OIM Strategic Roadmap Project

4
University of Washington Facts
  • Founded in 1861
  • Three campuses, and two medical centers
  • 27,600 faculty and staff
  • 43,000 traditional students, 26,000 extension
    students
  • Information Systems Landscape https//www.washingt
    on.edu/dis/itportfolio
  • Core Administrative Systems (Unisys/MCP/DMSII
    Cobol)
  • 900 Servers, 125,000 devices on the network
  • 7000 Miles Fiber Optic Cable

5
IS Systems Strategy circa 2003
Strategy Elements Description
Business Practice Transform Business Practices - to improve how people do their work
Modernize Core Modernize and extend core business systems -HR/Payroll, Financial, Student
Best of Breed Invest in best of breed systems build or buy for specific functional areas
Web Interfaces Implement web-based interfaces - to core business systems
Management Information Provide access to management information using data warehousing approaches
Middleware Develop and integrate middleware for personalization, authentication, and authorization
6
Future of Information Systems Report
  • Interim report May 2006, Final report January
    2007
  • http//www.washington.edu/provost/reports/IS_Fu
    tures_Final20Report_1-19-07.pdf

Functional Area
Finance and Budget 111
Teaching Learning 105
HR and Payroll 70
Comm, Infra, Middleware 47
Access to Info, Reporting, BI 43
Facilities, Transport, Space 33
Unknown, Other 22
Research and Grant 11
Clinical 5
 Systems 447
7
Future of Information Systems - Continued
  • Recommendations
  • Define a new long term strategic vision
  • Establish new funding models
  • Consider alternative approaches to core systems
    (i.e ERPs, Kuali, etc.)
  • Expand and improve information governance and
    development approaches
  • Support the Data Warehouse
  • Consider changes in organizational structure

8
New Office Information Management
  • Formed December 2006
  • Dual reporting to Provost and Vice President of
    CC

9
New Data Management Committee
  • Formed December 2006
  • Mike Eisenberg, Chairman, Dean Emeritus of
    Information School
  • Accountable to Vice Provost of Office Information
    Management
  • Current Projects
  • Data Policies Procedures, Role of Data Trustees
    and Stewards
  • Information Map, Metadata and Definitions
  • Security Access Roles and Policies
  • Top 5 Questions That Deans want answered
  • https//wwwudev.cac.washington.edu/provost/oim/dmc
    /index.html

10
Data Management Policies - DRAFT
  • Institutional data will be managed as a key
    asset!
  • Efforts will be made to reduce redundant data!
  • Institutional data must be maintained close to
    the system of record!
  • Institutional data must be safe and secured!
  • Access to Institutional data will be open and
    easily accessible! (except that data which is
    appropriately restricted)
  • Institutional metadata will be recorded, managed,
    and utilized!
  • Institutional employees will be held accountable
    to roles and responsibilities!

11
Data Trustees Stewards - DRAFT
12
Information Map, Metadata Definitions
  • Taxonomy created to help organize and plan
    systems and analytics
  • Master Data identified (touchpoints across all
    systems)

13
Information Map, Metadata Definitions
  • Subject Areas divided into Business Domains
  • Domains include identified processes and
    attributes
  • Wiki being used to capture specific low level
    data definitions, as well as aggregation rules

https//fmwiki.admin.washington.edu/x/SQkE
14
Security, Access Use Policies
  • Security classification Confidential,
    Restricted, Public
  • Follow Access of Least Privilege standard with
    Row and Column restrictions per role - per
    subject area.

15
Top 5 Questions
  • The Top 5 questions that Deans need answered
    are
  • What is the student headcount for my school?
  • How many student FTEs are there?
  • What is the headcount of faculty in my school?
  • What is the faculty FTE by appointment type?
  • How much money do I have by fund types?
  • Deans Advisory Group formed
  • Subject area work groups formed around Student,
    Faculty, and Finance

16
Top 5 Questions - Continued
17
New Enterprise Information Services
  • -- Future --
  • Senior Manager
  • Facilitates Consistency Quality
  • Security Policies
  • Metadata Mgmt
  • Master Data Mgmt

Application Integration Services
Data Management Services
  • Gary Prohaska
  • Senior Manager
  • Facilitates Processes Exchange
  • Web Services
  • Workflows
  • Process Orchestration
  • -- Open --
  • Senior Manager
  • Facilitates Analysis Access
  • Data Warehouse
  • Data Marts
  • BI Tools

Decision Support Services
18
Application Integration Services
Goals
  • Service Oriented Architecture (SOA)
  • Enterprise Service Bus, Enterprise Service
    Repository
  • Business process orchestrations / workflows
  • Enterprise portal integration
  • Cross application integration
  • Challenges
  • What style / infrastructure is needed? (REST vs
    SOAP vs WS-)
  • How do you rationalize a service?
  • How much / what type of governance is needed?

19
Decision Support Services
Goals
  • Enterprise Data Warehouse
  • Enterprise Business Intelligence (BI) Tools
  • Federated / Distributed Data Mart Support
  • Data Mining and Analysis Services
  • Custom Training Programs
  • Challenges
  • How to prioritize building out new subject areas
    in the data warehouse?
  • Who should be responsible for BI (central vs
    decentral)
  • How do you link metadata into BI easily?

https//kirk.admin.washington.edu/Reports/Pages/Fo
lder.aspx
20
Data Management Services
Goals
  • Enterprise Data Dictionaries / Metadata
  • Master Data Management (Common Reference Data)
  • Data Profiling and Quality Assurance
  • Data Security Classification and Access
    Control
  • Challenges
  • How to balance need for open access with security
    restrictions?
  • How do we integrate metadata across Data
    Modeling, ETL, Warehouse, BI Tools, etc.
  • How do we migrate core system master data to new
    environments?

21
Strategic Roadmap Project Structure
22
Strategic Roadmap Timeline
23
Questions?
  • Do these issues sound familiar to you?
  • Do you think we are on the right track?
  • I would love to hear from you
  • Email byock_at_u.washington.edu
  • Phone (206) 685-7535

Thank You for your Attention!
Write a Comment
User Comments (0)
About PowerShow.com