UW Strategic Roadmap for Information Management and Administrative Systems

1. UW Strategic Roadmapfor Information Management and Administrative Systems Project Managers Roundtable October 17, 2007

2. Overview • Background of the Strategic Roadmap project • Scope • Approach and timing • Project structure, roles & responsibilities • Current status

3. OIM Work Plan OIM initial 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: Develop the University’s Strategic Roadmap for Information Management and Administrative Systems • Choose where to invest people, money & time

4. Broad Themes Information Architecture 20% Systems and Processes 25% Information Management 32% Strategy, Policy and Partnership 23%

5. Governance and Partnership Leadership, alignment, and strategic partnerships Prioritization and governance Guiding principles Ongoing planning process Information Management Data access Common definitions Security Common solutions, support for specialized needs Administrative Systems Business process improvement Core systems modernization Finance, procurement, budget HR/payroll Student and academic administration, including course management Research administration Facilities/space Alumni/development Integration Project ScopeOrganized Around Broad Themes from Discovery

6. Approach and Timing

7. Project Structure

8. Roles & Responsibilities • Steering Committee: I-MAC • Develop guiding principles • Review and approve all recommendations • Roadmap Working Team • Coordinate recommendations across all task groups • Define overall vision • Recommend overall priorities and sequencing • IM/AS Technology Advisory Team • Advise on technology issues relating to the Strategic Roadmap • Resolve cross organizational technical issues that arise from the business task groups • Review deliverables from the Information Management task groups • Provide input into the prioritization of the Roadmap from a technical perspective

9. Roles & Responsibilities (cont’d) • Task Groups: Provide detailed input on current environment and vision for each functional area • Task Group Sponsors: Identify priorities; provide vision: assign experts to task groups • Task Group Leads and Team Members: Assess current state; define vision; identify gaps between current state and desired state; brainstorm ways to achieve the vision • Facilitators and Staff: Provide coordination and documentation support to team leads; facilitate working sessions

10. Project Participants • Over 175 participants: • 24 from OIM; 18 from C&C • 130+ from user community • Team members asked to take a long term, institution-wide view • Team members selected to represent a cross section of the University: • Large, small and mid-sized schools • Central administration • Health sciences • Campuses

11. Project Plan and Timing • July-September (Project Planning) • Project plan and approach finalized • Task Group sponsors, leads, facilitators and members are finalized • October-December (Current State) • Kick off Roadmap Working Team • Kick off Task Groups and Advisory Groups • Presentation of background materials • Task groups complete their assessment of the current state • I-MAC develops Guiding Principles

12. Project Plan and Timing (cont’d) • January-February (Vision) • Task groups and Roadmap Working Team develop their vision for future • March (Gap) • Task groups identify the gap between current state and vision • March-April (Action Plan) • Roadmap Working Team develops a prioritized Action Plan and Roadmap for Information Management /Administrative Systems

13. For additional information visit the Office of Information Management website at: • http://www.washington.edu/provost/oim/