38
What would a data governance and data management framework look like at a large research university like UW-Madison? August 18, 2014

Data Governance Data Architecture Data Development Database Operations Data Security Management Referene & MDM DW & BI Document & Content Mgmt Meta

Embed Size (px)

Citation preview

  • Slide 1
  • Slide 2
  • Slide 3
  • Slide 4
  • Slide 5
  • Data Governance Data Architecture Data Development Database Operations Data Security Management Referene & MDM DW & BI Document & Content Mgmt Meta Data Management Data Quality Mgmt.
  • Slide 6
  • Slide 7
  • Slide 8
  • Slide 9
  • Slide 10
  • Slide 11
  • Slide 12
  • Slide 13
  • Slide 14
  • Slide 15
  • Slide 16
  • Data with Extreme risk to the organization or to individuals that we serve. Exposure of this data would lead to identify theft or security risks. Examples: SSN, Driver Licenses, Banking Information, Credit Cards, Health Records, System Backups. Secure (Level 3) Data with sensitivity that should be protected and only used for specific reasons. Examples: FERPA Data, Personnel Information, Payroll Data, Student Data Sensitive (Level 2) Data that is not meant for public consumption, but is available within the University Examples: Applicants, Space Availability, Library Data, Planning Summary's, Financials Internal (Level 1) Data that is or can be presented to the public for news releases or on websites Examples: IPEDS Data, Enrollment Summary, University Budget, Course Catalogs Public (Level 0)
  • Slide 17
  • Data with Extreme risk to the organization or to individuals that we serve. Exposure of this data would lead to identify theft or security risks. Examples: SSN, Driver Licenses, Banking Information, Credit Cards, Health Records, System Backups. Secure (Level 3) Data with sensitivity that should be protected and only used for specific reasons. Examples: FERPA Data, Personnel Information, Payroll Data, Student Data Sensitive (Level 2) Data that is not meant for public consumption, but is available within the University Examples: Applicants, Space Availability, Library Data, Planning Summary's, Financials Internal (Level 1) Data that is or can be presented to the public for news releases or on websites Examples: IPEDS Data, Enrollment Summary, University Budget, Course Catalogs Public (Level 0)
  • Slide 18
  • Slide 19
  • Slide 20
  • Slide 21
  • Unrecognized Learning to Crawl as an Organization 1 Interested Everyone sees the need, but not fully vested 2 Invested Teams involved and Process have been established 3 Committed Organization has bought in and follows Process 4 Engaged and Embedded It is part of the core operating and strategy 5 Invested Teams involved and Process have been established 3
  • Slide 22
  • Executive Leadership
  • Slide 23
  • Chief Data Officer
  • Slide 24
  • Executive Leadership Chief Data Officer Data Governance Committee Data Architecture Committee
  • Slide 25
  • Executive Leadership Chief Data Officer Data Governance Committee Data Architecture Committee Data Stewards (Can be multiple groups)
  • Slide 26
  • Executive Leadership Chief Data Officer Data Governance Committee Data Architecture Committee Data Stewards (Can be multiple groups) Data Custodians & Curators. Campus Users
  • Slide 27
  • Slide 28
  • Slide 29
  • Slide 30
  • Slide 31
  • DoIT Develops Core Data Set Provides Infrastructure Provides Tools Provides Training Provides support to service providers Shared Service Group Support End Users Recommends Updates/Changes Trains Users Ensures Rules are Being followed.
  • Slide 32
  • Slide 33
  • Slide 34
  • Slide 35
  • Slide 36
  • Slide 37
  • Slide 38