ITAG, Version 2.0

1. ITAG, Version 2.0 Or, how our role supports the evolution of interoperable systems February 2013 - ITLC

2. Some Reasons for Change “ITAG is the connecting tissue among the campuses and UC ITS to identify the development standards (language, library, etc), middleware (identity management, service bus et al), and the shared services required to support common UC systems.” - Dana Roode “It would be helpful if [ITAG] would offer some information regarding the direction, recommended standards, and strategy about middleware set (e.g., workflow, ESB), identity management, data warehouse, network standard and equipment, convergence of phone/voice/video/data systems, admin tools for IaaS/PaaS integration with local infrastructure.” - Min Yao “UC has to make architectural decisions NOW - UCPath being the exemplar … is forcing some decisions that UC will have to live with for many years (decades?) Without major campus engagement on these decisions with Jerome’s team, we’ll end up with poorer results, [and] some locations will be left out in the cold.” - Paul Weiss Through its partnership with ITAG, the Enterprise Architecture Team will ensure a comprehensive approach to UC-wide architecture initiatives. This Enterprise Architecture and ITAG partnership will ensure appropriate vetting of standards and confirm that they are deployed appropriately at both campuses and medical centers. - Chuck Rowley 2 February 2013 - ITLC

3. Definition UC Enterprise Architecture (EA) A practice designed to achieve alignment of people, process and technology in support of the UC mission, vision and strategy. Combined, these support UC’s overarching strategy. Gartner says… Architecture - A framework and set of guidelines to build new systems. IT architecture is a series of principles, guidelines or rules used by an enterprise to direct the process of acquiring, building, modifying and interfacing IT resources throughout the enterprise. These resources can include equipment, software, communications, development methodologies, modeling tools and organizational structures. Enterprise architecture (EA)is a discipline for proactively and holistically leading enterprise responses to disruptive forces by identifying and analyzing the execution of change toward desired business vision and outcomes. EA delivers value by presenting business and IT leaders with signature-ready recommendations for adjusting policies and projects to achieve target business outcomes that capitalize on relevant business disruptions. EA is used to steer decision making toward the evolution of the future state architecture. http://www.gartner.com/it-glossary/ The objective of implementing Enterprise Architecture is to increase the consistency and interoperability of technology, data and processes across the UC. The benefits of a common EA are consistency and interoperability, shorter delivery timelines, improved quality, reduced redundancy and increased reuse across the UC. 3

4. What “2.0” Looks Like Revised ITAG Charter, Membership, and Work Plan • A focused plan and resources to work the plan IT and Interoperability Standards to Promote Reuse of Solutions Clear Processes and Framework(s) • In partnership with UC Enterprise Architecture (EA) Team Campus Requirements are Appropriately Integrated 4 February 2013 - ITLC

5. What We Do (Our Value Add) Planning and Facilitating UC Deployment • Representing the ITLC, ITAG will be responsible for partnering with the Enterprise Architecture Team in facilitating architecture standards for planning and implementation efforts Communication and Enablement • The ITAG, in collaboration with the ITLC, sub-committees, EA Team, project specific implementation teams and vendor partners, will broadly communicate UC’s vision for information technology architecture, standards and interoperability to campus and medical center stakeholders. Ongoing Maintenance and Management • The ITAG will be responsible for interacting with and advising the EA Team relating to ongoing management of UC-wide architecture requests, proposals, and regular progress updates, and for prioritization of effort and workplans. 5 February 2013 - ITLC

6. Critical Success Factors CIO Responsibilities: • Support, leverage, and promote adoption of EA standards at their location • Choose to provide (or not) an appropriate ITAG resource at 10-25% FTE level of effort • Selection and prioritization of ITAG workplan ITAG resource responsibilities include: • Consistent engagement with campus CIO and leadership to assist with planning, outreach and communication • Serve as a two-way conduit between campus and system-wide architecture planning • Contribute and develop the system wide architectures and standards with the UC Shared Services EA Team • Facilitate adoption of standards and multi-location initiatives by working with local implementation teams 6 February 2013 - ITLC

7. Current ITAG Membership? 7

8. Roadmap • Current state • Start from scratch • Redundancy • Data • Infrastructure • Applications • Cost • Variances without common standards • One-of-a-kind implementations • Desired state • Reuse of proven approaches & assets • Increased interoperability • Informed and deliberate variances • Easier to collaborate on UC initiatives ITLC ITAG and ITS/EA Team Align Campus and System-wide Strategy and Plans Common Administrative Systems 8

9. Proposed Work Plan What would our deliverables be? Facilitation of common subject area data definitions 9