1. University of California, Irvine ITAG Face-to-Face -10/18/2010 Marina Arseniev

2. University of California, Irvine (Administrative Computing Services) Contents  Enterprise Architecture in OIT/AdCom  Technical Reference Architecture  Our EA Repository  Architecture Initiatives  Realized Value  Next Steps

3. University of California, Irvine (Administrative Computing Services) Our Enterprise Architecture  Scoped to campus Administrative Applications and on hold due to campus IT consolidation and Kuali KFS.  Strategic information repository to plan change and impact  Life cycle management, governance  Control proliferation and retirement of technology  How many databases engines do we own? Where are they used?  Application and data security for HIPAA, PCI, SB1386  Extraction of “Common Requirements” across projects into patterns of reusable tested components

4. University of California, Irvine (Administrative Computing Services) What did we do?  Created a Technical Reference Architecture (2002)  maintain technology lifecycle and architectural control  being re-implemented as part of a tools inventory for the IT consolidation at UC Irvine however, as a low priority.  Adopted Zachman Enterprise Architecture Framework  powerful thinking and organization tool  logical – not J2EE,.Net, Portal, or WebServices  Moving towards TOGAF – slowly…

5. University of California, Irvine (Administrative Computing Services) What did we do, continued  Adopted Stanford’s Protégé Knowledgebase & Ontology Tool for Repository of critical business and technical information  Created a taxonomy model to answer specific questions - lists of applications and how they full-fill goals and initiatives.  Minimized redundancy, increased consistency of information  Populated the Model  Protégé auto-generates forms for capturing information  Forms based on our ontology and class definitions  Cross-link important facts (Projects to Technologies, etc) for slicing  Documented SDLC and a change management process

6. University of California, Irvine (Administrative Computing Services) Our Governance  Immature  Technical Reference Architecture – scoped to critical Administrative Applications  yearly reviews by senior IT staff  Protégé Strategic EA Information Repository  quarterly review and updates by Team Leaders on hold  EA Infrastructure Planning  senior staff agree on common requirements and define reusable components and centralized IT services (TFS…) as needed  Working on data inventory and governance - proposal stage

7. University of California, Irvine (Administrative Computing Services) Technical Reference Architecture  Documented principles, guidelines, and best practices of Architecture Domains:  Lifecycle Management  Adopt the “4 year/16 Quarter Sliding Window Methodology”  Identifies technologies that are “ Approved ”, “ Maintained but not Upgraded ”, in “ Sunset ”, “ Retired ”, or “ By Approval Only ”.

8. University of California, Irvine (Administrative Computing Services)

10. Our EA Repository – on hold  model uses Zachman EA Framework concepts  stores strategic information – a subset of the Technical Reference Architecture  goals articulated  initiatives, roadmaps, projects linked to goals  technology linked  change strategy  communication tool

11. University of California, Irvine (Administrative Computing Services) Example: Protege

12. University of California, Irvine (Administrative Computing Services) Example: Protege

13. University of California, Irvine (Administrative Computing Services)

14. Realized Value  Technologies retired or consolidated  database and windows servers consolidated  reduced Admin and DBA costs  CICS and Foxpro retirement in progress  Reduced development costs  tested code reuse (SOA reuse for student fee submission)  reuse of staff skill sets  common infrastructure for development that is platform independent

15. University of California, Irvine (Administrative Computing Services) Next Steps  Focus on campus IT Consolidation and low hanging projects rather than on Enterprise Architecture  Focus on replacement of Financial System possibly with Kuali (Proof of Concept in progress)  Complete OIT Tools Inventory and fold it into a simplified consolidated IT Technical Reference Architecture.  Implement Technology Governance per TOGAF9  Get executive buy-in after campus consolidation settles down and urgent projects are well under way