Data Governance Council Meeting Minutes August 8, 2007
Attendees: Josh Brauer, Don Diener, Christina Drum , Karen Emptage, Elora Paik, Gwenn Pons, Rick Storlie, Jennifer McCarthy, Monty Young, Guest: Lori Temple
I. Update on recent iNtegrate work – Lori Temple
Lori passed out the following handouts:
Integrate Update Data Governance Group
NSHE Requirements Workshop Sessions
DRAFT UNLV Potential Structure/Approach to Supporting ERP Implementation
There will be a single data center at SCS. They will supply the hardware and support.
There will be system wide decisions regarding what gets integrated first.
Project Steering committee focuses on procurement side, not implementation.
There is a contract negotiations team looking at Software Licenses - Sunguard and Oracle/People Soft and Service Contracts - Sunguard, Oracle/Cyber.
Consultant facilitating work shop sessions for NSHE Requirements. (see handout)
Next step will be vendors and contract negotiations.
There will be a SCS level advisory board to help oversee SCS.
Potential Structure Chart of support for ERP implementation. (see handout)
UNLV and IT are working on a staffing plan to assist the implementation and support the process. This involves restructure of positions, new hires and training.
Gwenn Pons asked about the time line for implementation and Lori stated the estimated time is Fall of '09.
Lori emphasized that collaboration is needed between the systems and that the DG Council is critical.
II. OIT Security Policy 2 - Don Diener
Don passed out the following handouts:
Asset Classification Worksheet
Information Asset Classification Process
Don stated that the Regents have mandated all critical and sensitive data be identified.
The first step is to identify all University data. Then the data needs to be assessed for risk. (see handouts) A security plan for protecting the data is an ongoing process that is audited by the security office.
The difference between sensitive and critical data is the consequence if the data gets out. An example of sensitive data is a personal credit card number. The credit card owner would be affected by that information getting out, but that information does not affect the university. Budget information is and example of critical data, that if misused or interrupted could affect the whole university.
III. Update on Data Management Issues
Due to time constraints, Christina Drum recommended the update on data management issues be addressed at the beginning of next month's DG Council meeting. Christina asked if there were any issues anyone felt needed to be addressed now instead of waiting until next meeting. Everyone agreed to wait until the next meeting.
IV. Status of work to establish data administrators in your area.
Elora Paik had a question about exactly what Lynne is looking for with this task. Is everyone suppose to submit a written status? Christina mentioned that there was still an August target date for data administrators to be established and the reason for a status check was to see if everyone was on target and if there were any issues or questions regarding this task.
Monty Young suggested that the hands on, day to day responsibility is probably where the data administrators are.
Gwenn Pons wondered if, once the data administrators are established, are there going to be agreed upon procedures for all? For example, will they be responsible for filling out the Asset Classification Worksheet that Don Diener handed out?
V. Approval of August status report to Data Governance Executive Sponsors.
Formally approved.