In 2020, the ITAC created the DGCC to provide a data governance structure and to identify and advise on the big-picture issues facing the University data community. Visit this page for a list of DGCC achievements.
Ensure consistent data reports, develop and promote transparent campus-wide data definitions, and build actionable plans and priorities for the future of UWM data.
We will build trust in University data through intentional investments in data literacy while collaboratively developing and broadly sharing data assets and knowledge.
We believe data is an underused University asset that can inform and inspire by highlighting issues and celebrating achievements. It is critical that our data is available, trusted, and understood. Every one of us contributes to and is responsible for the creation and maintenance of our data.
Our goals prioritize shared investments, transparency, and intentional decisions about the people, tools, and resources dedicated to campus data. We envision a data culture where resources are devoted to promoting a University-wide perspective and understanding of unit-level data needs. By empowering and supporting existing data analysts, we can foster campus-wide data literacy, ensure data consistency, and focus our limited resources on creating shared dashboards and reports to address common priorities and problems.
A Brief History of Data at UWM
- Text file extracts were pulled by the Information and Media Technologies (I&MT) department.
- SASS and Mark IV were used to assimilate the data.
- Only two or three people had access to this information.
- In 2002, UWM CIO Joseph Douglas supervises the introduction of PeopleSoft and Crystal Reports is purchased to pull data from PeopleSoft.
- An informal group of report writers on campus begins to meet to assist each other with data queries. The group calls themselves WERIT (Warehouse End Users Reporting Initiative Team).
- Also in 2002, most of the campus data snapshots we use today — “Appstat” for applications (January), “Statmaster” for official enrollments (Summer 2002), and “Enrollstats” for weekly class and student enrollments (Fall 2002) are developed and captured for the first time.
- In 2006, Brio Query is purchased by Oracle Hyperion and becomes the new tool of choice for UWM. Hyperion requires extensive knowledge of database concepts. The WERIT team works to learn campus data and business processes.
- In 2011, a new Authorization Application (the creatively-named “AuthApp”) is introduced to approve access requests for curated Hyperion dashboards and other data.
- WERIT grows in membership as more campus employees add report writing to their job duties.
- In 2015, the UW System purchases Oracle Business Intelligence (OBIEE) as the replacement for the Hyperion “query library.” OBIEE will allow for self-service dashboards and further expand data access. The transition to OBIEE begins in Summer 2016.
- Also in 2015, the Data Analytics Working Group (DAWG) concludes work on the first data governance proposal to campus leadership.
- In 2016, the UWM Data Hub launches as the first repository of campus data and reports.
- In March 2018, the UITS Enterprise Data Management (EDM) team completes a project with WERIT members to migrate existing “query library” dashboards to create a collection of shared OBIEE dashboards for general campus use.
- In 2019, OAIR debuts their Data Provision Guidelines to highlight the internal report development considerations of their office for new data requests.
- In January 2020, the Data Governance and Custodial Committee (DGCC) is created to govern shared dashboard use and to define data terms utilized across campus. Their first order of business is to identify an ad-hoc campus reporting tool.
- In March 2020, the DGCC recommends Power BI as the campus’ ad-hoc reporting tool to replace Hyperion.