1. UM Background  Multiple data sources Datacom mainframe Locally developed applications Optix documents Sheets of paper  Minimal documentation Dispersed knowledge among functional users Single point of technical knowledge  No single unit responsible for ETL

2. UM Priorities  Document what we currently have Identify “dirty” data Clarify areas where multiple concepts are interwoven in a single data point  Understand where current data elements fit within Kuali Student Identify gaps in KS Identify areas for manual data entry  Have it done yesterday

3. Guiding Questions 1. Is this the primary source of this information? 2. Is this the ONLY source of the information? 3. What is the “shelf life” of this information – how long is it useful? 4. Who “owns” the information – i.e., who can make changes to it? 5. Why do we need this information – what decisions does it support, questions does it answer, etc.?

4. Results  Focused on initial implementation – course proposal process  Identified areas for manual data entry Course rules Program shells  Live in Production Nightly data feeds Ready to switch system of record