Skip to end of metadata
Go to start of metadata

University of California, Information Technology Architecture Committee (ITAC*)

The ITAC is a working sub-committee of the UC Information Technology Leadership Council (ITLC), and ITLC establishes our priorities and directions, and resolves questions regarding scope, strategy, and/or policy.

Our mission is to "establish the enterprise architecture and technology infrastructure necessary to promote and support interoperability and sharing of IT solutions among and between campuses(Foundation for Collaboration on Technology Enabled UC Solutions, Pillar II, March 2013).

We facilitate knowledge sharing and collaboration across the UC campuses, and work in concert with the UC Information Technology Services (ITS) Enterprise Architecture (EA) Team, to inform and enable reuse of the UC EA Body of Knowledge (EA BoK). We support implementations of UC-wide initiatives, and can assist each UC location with discussion and review of the variety of artifacts available in our EA BoK.

*formerly known as ITAG

EA Resources

EA resources can be leveraged by any UC location as they design, develop and deliver a shared service for multiple locations across the UC system. These resources include the EA Artifact Framework, the EA Glossary, and the EA Body of Knowledge (EA BoK). (Access to all these resources requires separate login.)

EA Artifact Status

EA artifacts represent common practices and technologies across the UC system, and include principles, standards, guidelines, reference architectures, business process models, logical and physical data models, metadata, application portfolios, best practices, procedures, and more.

ITAC representatives facilitate the review of these artifacts at each UC location, confirm CIO adoption, and assist with conflict resolution and communications at their respective locations.


IT Checklists

IT Checklists are available to UC IT Teams, and can help identify and confirm the various components that enable quality service delivery and operational support. The checklists cover a variety of domains - applications, data, technology, and security. Feel free to download any checklist and modify as needed; if you make modifications please send a copy to ITAC so that we can make them available to others.


Other Initiatives

Cloud Architecture and Best Practices

The sub-committee for Cloud Architecture and Best Practices will develop various materials (principles, standards, guidelines, reference architectures, etc.) that can be used across the UC locations for their implementation and operations of cloud-based services, systems, and applications.

More>> (login required)

API Architecture, Integration and Best Practices

The API Architecture, Integration and Best Practices of ITAC will identify and propose standards, platform capabilities that support and promote the principles of “Interoperability”, “Reuse and Leverage Services Approach”, “Deliberately Plan Technology Platform variations” with respect to application integration platforms.



ServiceNow - CMDB expansion

All* campuses have ServiceNow (SN) implementations. Each SN version after Eureka has CMDB functionality included. It is our intent to populate the CMDB and leverage the information to gain insight into system wide opportunities. To maximize cross campus utility we need to standardize on a taxonomy and some of the CIs, Application and Integration CIs are first.

More>> (login required)

List of initiatives that ITAC and EA resources have been and/or are participants of... More >>

Welcome to the ITAC Wiki

This wiki space is where you’ll find information on the various initiatives and activities of the EA and ITAC teams: 

Please note that some of our content is available only to University employees.

If you have comments, suggestions or requests, please contact your ITAC representative or the ITAC Chairs.

Weekly Conference Calls 

 Every Friday (excluding holidays), 10-11am:

  • 1st week - General
  • 3rd week - Leadership
  • All others - EAA Reviews

Please see our Meeting Agendas and Notes for more information.

No Endorsements Implied. All content is the property of the Regents of the University of California.

  • No labels