Changes in Information Systems (IS) and Information Management (IM) :Changes in Information Systems (IS) and Information Management (IM) Phyllis Wise, Provost and Vice President, Academic Affairs Sara Gomez, Vice Provost for Information Management and CIO Ron Johnson, Vice President for Computing and Communications


Improve Information Systems (IS) andInformation Management (IM) :Improve Information Systems (IS) andInformation Management (IM) IS Futures report C&C strategic planning TACs, deans, and many others Benchmark with other major research universities Take advantage of major reorganization in UW administration Evolving state ISB requirements/relationship


Office of Information Management (OIM) Overview :Office of Information Management (OIM) Overview Created by Provost and Vice President for Computing and Communications in November 2006 Charged with directing information management and information systems throughout the University of Washington Headed by interim Vice Provost and Chief Information Officer (VP-IM/CIO) Sara Gomez. The VP-IM/CIO: Provides university-wide leadership in developing and managing information systems and applications Reports primarily to the Provost, but also to the Vice President for Computing and Communications on technology issues


Slide 4:IS, IM UW’s OLD IS, IM, IT Org. Landscape VP Ext. Aff. VP Med. Aff. Clinical Systems & Devices IS, IM VP C&C C&C’s AIS, IS, IM CIO Provost & VP Academic Affairs IS, IM VP Fin. & Treas. IS, IM VP H.R. IS, IM AVP Facilities IS, IM AVP Bus. Serv. IS, IM AVP Capital Proj. Strategic Init. Office ‘SIO’ IS, IM Dept., Center, PI, and faculty- based IT & TC (Technical Computing) etc. Direct control by faculty & depts. College, School; Tacoma, Bothell Campus; Library; and Center- Level IS, IM VP Dev.& Alum. Athletic Dir. IS, IM IS, IM VP Minority Aff. EVP IS = Administrative, Management and/or Decision Support ‘Information Systems’. Includes Applications design, development, and maintenance. Also includes control of IS & IM applications operation. No one had/has any overarching/‘cross-silo’ authority or responsibility for IS. IM = ‘Information Management’. At best, only done locally, not done globally across the UW. IT = Information Technology infrastructure, design, engineering, architecture, deployment and operations. Includes hardware, networks, underlying email, messaging and web infrastructure, middleware, distribution systems, and support. Includes Technical Computing, instruments etc, Direct ‘Line’ Reporting relationship ‘Dotted line’ Reporting Relationship No institutional IM UW-wide IS & IM Some Responsibility, little Authority Largely separate IS/IM authorities/responsibilities ‘IT’ activities - central, departmental, PI etc. UW IT Infrastructure IT & TC Service Delivery Streaming Media, TV Broadcast, Video Prod. Compliance; Security IT & TC Infrastructure & Technical Operations President 4 IS, IM Vice Provosts Deans & Chancellors


Slide 5:UW’s NEW IS, IM, IT Org. Landscape VP C&C IS, IM VP Fin. & Treas. IS, IM VP H.R. IS, IM AVP Facilities IS, IM AVP Bus. Serv. IS, IM AVP Capital Proj. Dept., Center, PI, & faculty based IT & TC (Technical Computing) etc. Direct control by faculty and depts. College, School; Tacoma, Bothell Campus; Library; and Center- Level IS, IM EVP IS = Administrative, Management and/or Decision Support Information Systems. Includes Applications design, development, and maintenance. Also includes control of IS & IM applications operation. IM = Information Management systems, information architecture, knowledge architecture, and other IM responsibilities & activities, incl. ‘data definition’, ‘data administration’, warehousing, data validation & evaluation. IT = Information Technology infrastructure, design, engineering, architecture, deployment and operations. Includes hardware, networks, underlying email, messaging and web infrastructure, middleware, distribution systems, and support. Includes Technical Computing, instruments etc. Direct ‘Line’ Reporting relationship ‘Dotted line’ Reporting Relationship IM: Provost, CIO/VP-IM & Data Steward’s IM Authority Provost’s & CIO/VP-IM IS & IM Authority ‘IT’ activities - central, departmental, PI etc. C&C’s AIS IS, IM Vice Provost, Info. Mgmt. & CIO Office of Info. Mgmt. (OIM) SIO Data Stwd. Technology Services: Information Technology; Infrastructure; Architecture; Engineering & Operations etc. Admin.& Mgmt. & Decision Support IS, apps. & IM 5 UW IT Infrastructure IT & TC Service Delivery Streaming Media, TV Broadcast, Video Prod. Compliance; Security IT & TC Infrastructure & Technical Operations IS, IM Provost & VP Academic Affairs President Vice Provosts Deans & Chancellors


OIM’s Three-Phase Work Plan :OIM’s Three-Phase Work Plan Discovery/Assessment: Identify challenges and opportunities (Winter 2006-07) Organizational Design and Transition: Build the future of how we work together (Spring 2007) Strategic Roadmap: Choose where to invest people, money, and time Short-term priorities (Spring/Summer 2007) Long-term priorities (Fall/Winter 2007-08)


Discovery/Assessment Phase: Broad Themes Analysis :Discovery/Assessment Phase: Broad Themes Analysis Collected more than 550 comments from meetings with key stakeholders Categorized comments into four broad themes and sub-themes Analyzed how many comments fell into each category to get a sense of proportionality


Slide 8:Broad Themes


Slide 9:Develop strategic roadmap Review governance structure Pursue strategic partnerships Strategy, Policy, and Partnership (23% of the Comments)


Slide 10:Identify top five queries Develop consistent data definitions Address data access issues Information Management(32% of the Comments)


Slide 11:I-MAC packages recommended for FY 07-08 funding Core system replacement Business Processes & Information Systems(25% of the Comments)


Slide 12:Enable access to common central services Provide local development capabilities for specialized needs Information Architecture(20% of the Comments)


Data Management Committee Progress March 2007 :Data Management Committee Progress March 2007 Data and metadata definitions and related business processes Reviewing and approving data security recommendations Reviewing past work to build on; identifying “low hanging fruit” Determining baseline operating assumptions (e.g., access levels/ openness) Developing processes for data management Linking with Data Management User Group (DMUG) Providing support and feedback to the Data Warehouse Developing UW Data Management Policy Statement Creating one-stop communications portal with many access points Reporting to Office of Information Management Top five questions for Data Warehouse and transaction systems


What’s Next? :What’s Next? Discovery/Assessment Phase:Stakeholder meetings complete. Input being analyzed to inform Strategic Roadmap. Organizational Design and Transition Phase: Work is underway. Information about OIM’s new structure and leadership team coming in July. Strategic Roadmap Phase: Work has started on developing a vision for the future of information systems and information management and an action plan for how to move forward.


Slide 15:For more information visit OIM’s Web Site http://www.washington.edu/provost/oim/