UC E NTERPRISE A RCHITECTURE F RAMEWORK (EAF): T HE B USINESS V ALUE UC-ITAG
ITLC Vision To invest and deploy technology-based solutions that support the University's missions of teaching, research, public service, and patient care, and to address common Information Technology (IT) opportunities that advance the collective priorities of Locations and the system as a whole.
Foundation for Collaboration UC-ITAG and EAF Mission Pillar I — Formalize partnerships with UC Leadership groups to jointly establish principles for common or shared solutions and to develop and regularly maintain shared roadmaps of future direction. Pillar II — Establish the enterprise architecture and technology infrastructure necessary to promote and support interoperability and sharing of IT solutions among and between campuses.
EA Framework Purpose UC CIOs ITAG and UCOP EA Team Shared Services Align Campus and System-wide Strategy and Plans Current State Start from scratch Redundancy in Data Infrastructure Applications Costs Variances with no standards One-off implementations New State Reuse of approaches and assets Increased interoperability Deliberate variances Easier UC collaboration
How EAF Addresses Business Needs Standardized Data Models Metadata Repository Architecture Artifacts “In a Box” Services, i.e. SSO In a Box, ESB In a Box “Shareable Upon Delivery” initiative, i.e. Cross- Campus Enrollment System will leverage the Web Services guidelines.
How Do We Know We Are Successful? Improved Interoperability, Less Build, Less Buy Faster delivery of systems using shared services Cost, resource, or time savings
How Will We Measure Success? Number of artifacts used and how often, per campus How fast services can get rolled out, start to finish Efficiency of system integration efforts Reduction of “one-off” point-to-point links Total cost of rollout (see slide notes for more)
Tracking Metrics (insert table here – see slide notes)
UC IT Architecture Group (ITAG) UCTrust Working Group (UCTrust)