1. Information Technology Architecture Group ITAG, version 2.0 We need resource commitments! February 2013 - ITLC

2. Information Technology Architecture Group For ITAG V.2 to Succeed… Appointment is based on Member Role Profile Has the requisite skills, knowledge and abilities Members commit to the necessary level of effort ~10-25% FTE (4-10 hours/week, minimum) Uses Project and Service Management methodologies Track and communicate status all requests Members rotate PM duties and work within the EA Team PM Framework Collaborates and partners with UCOP Shared Services Enterprise Architecture Team Governance/Oversight provided by ITLC Selection and prioritization of engagements in the ITAG Workplan Resolution of issues that cannot be resolved by ITAG and EA Team February 2013 - ITLC 2

3. Information Technology Architecture Group ITAG version 2.0 Goals for 2013 and Beyond Reconstitute our Charter, Membership, and Workplan Establish clear governance and process framework(s) o Partner with UC Shared Services Enterprise Architecture (EA) Team o Common vocabulary and multi-directional communication o Standardization and reuse of solutions Engage in system-wide efforts o Provide decision support with campus perspective o Balance localizations against system-wide interoperability February 2013 - ITLC 3

4. Information Technology Architecture Group What We Do (Our Value Add) Represent unmet needs at our respective locations Business and technology needs/gaps Inventory of existing campus architectures Review and assess candidate solutions against campus readiness Gap analysis, assessment and/or preparation of proposals Research and recommend a solution(s) Liaison for Campus implementation and adoption UC EA Body of Knowledge Subject Matter Expertise Curators of local Principles, Standards and Reference Architectures Solution selection, feedback and issue resolution Provide guidance and consultation Implementation Planning Campus Objectives for Service Agreements Advocacy and Marketing Campaign(s) February 2013 - ITLC 4

5. Information Technology Architecture Group By Request from ITLC EA Team ITAG and UCTrust member(s) External workgroups (ITPS, CTG, EALT, TAS, Other) In Consultation with EA Team External workgroups Campus IT Communities Informed by ITLC strategic priorities Campus business requirements and CIO guidance EA Body of Knowledge How We Function February 2013 - ITLC 5 ITLC EA Team ITAG UCTrust Externa l Campus IT Communities

6. Information Technology Architecture Group Who We Are Local resource to/for UC Shared Services Enterprise Architecture Partners with EA Team Advocates of system-wide architecture and infrastructure Champions for campus implementations of system-wide systems Efforts prioritized by ITLC Members interact with their respective CIO (periodic and regular status updates) February 2013 - ITLC 6

7. Information Technology Architecture Group Background Slides

8. Information Technology Architecture Group Our Wiki and Email List https://spaces.ais.ucla.edu/display/ucitag/Home UCITAG-L@listserv.ucop.edu v2.0 Documentation Charter Member Role Profile Workplan Additional Information February 2013 - ITLC 8

9. Information Technology Architecture Group Expectations of Membership https://spaces.ais.ucla.edu/display/ucitag/ITAG+Member+Role+Profile February 2013 - ITLC 9

10. Information Technology Architecture Group Month 123456789101112 Integrate with ITLC, EA & Other Teams A Timeline (DRAFT) EAA Framework ITAG Work Intake Methodology Repository (Tool) F2F Campus Inventories ITLC SOA Reference Architecture for UCPath MDM Education (for ITAG members) Campus Integrations Integrate into Ticketing System Very drafty. This needs to reflect the workplan confirmed by ITLC and Jerome's team, and bounded by ITAG capacity for each effort. Standards, Principles, Reference Architectures ITAG Telecon ITAG Telecon ITAG Telecon ITAG Telecon ITAG Telecon ITAG Telecon ITAG Telecon ITAG Telecon ITAG Telecon ITAG Telecon ITAG Telecon ITAG Telecon EA/SOA "introduction" to locations EA/SOA marketing campaigns Localization of EA artifacts February 2013 - ITLC 10

11. Information Technology Architecture Group Our Definition Enterprise Architecture (EA) is a practice designed to achieve alignment of people, process and technology in support of UC mission, vision and strategy. Value Add Across UC: Consistency and interoperability of technology, data and process Shortened delivery timelines, improved quality, reduced redundancy, and increased reuse Supports UC’s overarching business and technology strategy February 2013 - ITLC 11

12. Information Technology Architecture Group The EA Body of Knowledge (EA-BoK) UC EA-BoK Repository of documentation (people, process, technology) Architectural assets are made available to each location Enables consistency and interoperability of technology deployments UC Shared Services EA Team Primary Curator of the Repository Establishes and maintains the body of knowledge Ensures the EA-BoK is available and accessible across the UC system IT Architecture Group Facilitates local consultation and feedback Enables local adoption and integration Participates in maturation (continuous improvement) February 2013 - ITLC 12

13. Information Technology Architecture Group Benefit Statements We can only realize the full value of UC Enterprise Architecture by establishing a collaborative working model for EA functions across the system. When Architectural assets are managed and subsequently utilized across UC, consistency, interoperability, and reuse will be achieved. February 2013 - ITLC 13

14. Information Technology Architecture Group Some Interesting Statistics Source: Enterprise Architecture Survey Results from the January 2010 DDJ State of the IT Union Survey http://www.ambysoft.com/surveys/stateOfITUnion201001.html February 2013 - ITLC 14