Report to Data Governance Executive Sponsors from Data Governance Council
September 2007
Updates on In-Progress Data Governance Issues.
Building Room Data Inconsistencies owned by Rick Storlie
Work has just completed on the campus GIS map.
We now have accurate building locations and exterior dimensions pending data verification.
Upon completion of the data verification, we will proceed into the comparison of GIS data to existing building drawing data.
I anticipate a two month duration for the comparison.
We will also begin a training program for FM&P staff in using the newly acquired survey instrumentation and GIS data
Rick’s optimistic time line for building an accurate building/area database is the 2nd Qtr of 2008
Terminal Degree Designation, owned by Elora Paik
a) Elora met with two data administrators to understand real issues with respect to Terminal Degree Designation.
b) Forwarded initial issues, description and activity plan to one of the Community of Interest participants.
Plans meeting with the Community of Interested parties later this month.
Tech Room Designation owned by Don Diener
Issue # 2 - Tech rooms - designating them is removing the indication of whether or not they are a lab, classroom, seminar room.
Meeting on 7/30. Present: Anthony Vaughn, Don Diener, Richard Storlie, Jennifer McCarthy, Darrell Lutey. We spent some time trying to understand our objectives. The main problem identified was that information about which rooms had been converted to TEC rooms did not reach the Vice Provost’s office for some time. That problem had been remedied and new rooms are being identified, but there was still a gap in the data.
Two action items
Darrell will send updated list of all rooms that have been converted to TEC rooms to Jennifer.
Jennifer will work with Karen Emptage to update Ad Astra list to include classifications as “laboratory,” “lecture room,” etc.
SIS Room Inactivation submitted by Anthony Vaughn, owned by Karen Emptage
The Registrar’s Office is considering whether to assign a GA to make the updates OR, whether to change the space utilization group's SIS access to be able to change –They may need to work with Anthony and Jennifer as part of the decision.
Exemption and Deal Codes owned by David Ellison
On hold at this time.
Administrative Issues.
Data Governance Web Site. The "Draft" data governance web site that stored Data Governance policies, roles and responsibilities, as well as agendas and minutes from your meetings has been retired. Important content has been merged into the Data Governance Council web presence.
Click here to go the start of the merged site. This site will continue to house work done by the data governance council, and will provide a single place for up to date UNLV data governance information.
August DGCouncil Meeting
Data Governance Council met on August 8, 2007. Attendees were : Josh Brauer, Don Diener, Karen Emptage, Elora Paik, Gwenn Pons, Rick Storlie, Jennifer McCarthy, Monty Young, Christina Drum. Guest: Lori Temple
Our guest at the August 8 meeting was Lori Temple, who provided an update to the Data Stewards on the status of the iNtegrate project. Since Data Stewards will certainly be involved with the project once it is at the implementation stage, they need to be aware of the work being done in preparation.
1. Board of Regents Technology Task Force – has decided on a single data center, are planning a governance structure, and have secured $25 million in funding for the project, $10 million from the legislative session, and $15 million from NSHE.
2. Nevada State of Higher Education (NSHE) is in the process of finding appropriate leadership for the project – a project director search is underway.
3. The Project Steering Committee is responding to requests for information including a list of supplemental systems, and a list of standard report requirements. Many of the Data Stewards supplied information to help fulfill these requests.
4. Contract negotiations are underway for both software contracts and implementation contracts. As a result of this work, further strengthening of NSHE requirements was requested. To help provide this information, the Student Affairs working groups held detailed student services module requirements workshops conducted by Moran Technology Consultants. Workshops covered the following:
Technology, Financial Aid, Data Warehousing, Student Accounts, Portal, Student Records, Student Services, Recruitment, Advising, Admissions
5. System Computing Services has designated an advisory board. It will be comprised of representatives from around NSHE and will help advise SCS on how the organization can assist the campuses with their technology needs (e.g., Oracle licensing, various activities related to the iNtegrate project, etc.)
6. At UNLV, we are working on a proposed governance structure for our part of the project, and are looking at ways to staff the initiative. Staffing will be met with a combination of strategies. One is to upfill/backfill for staff who will be devoting significant portions of time to iNtegrate, and the second to secure new positions where needed.
The Office of Information Technology will be responsible for the application support for iNtegrate. To meet that obligation, they are working on a restructuring plan and determining where additional training is needed.
Also at the August 8 meeting, Don Diener discussed OIT Security Policy 2. He distributed an Asset Classification Worksheet, and a description of the Information Asset Classification Process. The NSHE Board of Regents have mandated that all institutions produce plans to protect sensitive data. Data classification is a step in the process required to meet the Board of Regent's mandate. The first step is to identify all University data. Second, all data must be classified as to both "sensitivity" to exposure and "criticality" to the mission of the institution. Third, a risk assessment must be performed to identify realistic threats to data confidentiality, integrity, and availability. Fourth, a plan for protecting the data and the physical assets that make the data available (e.g., servers, data network) must be devised. Finally the plan must be implemented and audited to ensure compliance. This entire process must be reviewed periodically to keep it current with changes in technology and threats to the data.