1. Enterprise Architecture 2013 ITLC & ITAG Leadership Meeting Discussion Points April 9, 2013

2. Enterprise Architecture 2013 Discussion Points EA Framework discussion Key Roles Key Components EA Assets & EA Body of Knowledge EA Asset Lifecycle discussion Submission & Review Location specific Adoption & Communication System-wide Communication Decisions Past & Present discussion 2

3. Enterprise Architecture 2013 Enterprise Architecture: Key Roles ITAG members: Support the development of Enterprise Assets that are architecturally significant – Examples: Standards, reference architectures, common solutions/services, etc. Evangelize awareness, adoption and use of Enterprise Architecture at their campus Respond to ITLC requests for input on key subjects with recommendation artifacts ITLC CIOs: Establish ITAG priorities Make decisions regarding investments and campus technology portfolio Determine applicability of Enterprise Assets for their campus, and steps required for implementation STSOC: Make decisions regarding investments in Shared Technology Services and overall UC service portfolio EA : Curator for Enterprise Architecture Assets Evangelize awareness, adoption and use of Enterprise Architecture across UC 3

4. Enterprise Architecture 2013 Enterprise Architecture: Key Components 4

5. Enterprise Architecture 2013 Enterprise Architecture: Assets An Enterprise Architecture Assets Framework (EAAF) is required for lifecycle management of any asset that advances consistency, reuse or interoperability – Examples: standards, specifications, principles, references architectures, etc. A collection of Enterprise Architecture Assets establishes an EA Body of Knowledge An EA Body of Knowledge must facilitate discovery of the Enterprise Architecture Assets – Example capabilities: keyword search, result filtering, taxonomy navigation, workflow, subscription, etc. 5

6. Enterprise Architecture 2013 Discussion: What Are Our Enterprise Assets? 6

7. Enterprise Architecture 2013 Discussion Points EA Framework discussion Key Roles Key Components EA Assets & EA Body of Knowledge EA Asset Lifecycle discussion Submission & Review Location specific Adoption & Communication System-wide Communication Decisions Past & Present discussion 7

8. Enterprise Architecture 2013 Discussion: Submission and Review 8

9. Enterprise Architecture 2013 Discussion: Location Specific Adoption 9

10. Enterprise Architecture 2013 Discussion: Communication 10

11. Enterprise Architecture 2013 Discussion Points EA Framework discussion Key Roles Key Components EA Assets & EA Body of Knowledge EA Asset Lifecycle discussion Submission & Review Location specific Adoption & Communication System-wide Communication Decisions Past & Present discussion 11

12. Enterprise Architecture 2013 Decisions Past: Data Dissemination Operational Data Store (DDODS) – Supports campus data warehouse data needs – Data model reduced complexity – Consistent meaning & structure across locations – Unidirectional data push for data security Real time message-based identity integration – Supports business need for information delivery – Limited number of interfaces, manageable without ESB – Foundational introduction to preferred integration method Superset Interface Files: Data is reformatted to location specific needs at the location (a.k.a. Data Shaping) – PPS had > 1200 interfaces, UCPath has ~150 (excluding DDODS) 12

13. Enterprise Architecture 2013 Decisions Past: Secure FTP for file based interfaces – Stronger authentication IdP Proxy – Reduces authentication steps for end user – Leverages existing infrastructure and authentication scheme 13

14. Enterprise Architecture 2013 Decision Iteration: Initial s/FTP directory decision: Single target directory “drop point” at each campus – Reduced key management – Aligns with ideal temporal state of data on FTP servers Subsequent s/FTP directory decision: Support non-standard (varying) s/FTP directories – Emulates existing Tier 1 interface infrastructure at campus – Increases digital key & certificate management – Promotes need for campus self-service capabilities to offset variance management 14

15. Enterprise Architecture 2013 ITAG facilitated decisions: PPS/HRIS RFP process – Facilitated ITAG emphasis on SOA and integration Incorporating UCTrust into ITAG – Improves overall integration of identity security architecture Supporting ESB adoption – ESB training and proof-of-concept collaboration ITAG/UCPath in person meetings – Facilitated productive exchange of approaches and technology recommendations for the UCPath project – In depth review of some UCPath interfaces

16. Enterprise Architecture 2013 Decisions Needed: ITAG time allotment Problem: allotment of time for ITAG members to advance architecture objectives is insufficient Decision: increase level of investment in ITAG resources Timeframe: April 2013 onwards Consider:

17. Enterprise Architecture 2013 Current Decisions: EAAF & EA body of knowledge Problem: lack of reusable enterprise assets available Decision: sanction launch of EAAF, identify assets types to be managed, support investment in tooling to establish an EA body of knowledge Timeframe: May through December (build and populate) Consider: Resources necessary to manage Enterprise Asset lifecycle management (review, communication, etc.) Selection of software to facilitate management & discovery

18. Enterprise Architecture 2013 Decisions Needed: Disparity of capabilities Problem: technology and resource constraints vary by location and adversely affect solution designs Decision: task ITAG to develop proposals to address the capability gap. Prioritize capabilities that support interoperability and reuse Timeframe: May through July Consider: Providing capabilities as virtual machines (e.g. ESB-in-a box) Mandate locations invest in technology and resources required

19. Enterprise Architecture 2013 Decisions Needed: Enterprise Key Management Problem: secure utilization of shared services requires management of a myriad of encryption keys and certificates, involving numerous entities, and is manually intensive Decision: establish an enterprise service with necessary processes, resources and tooling to increase automation of enterprise key and certificate management Timeframe: May through August Consider: Enterprise Key and Certificate Management solutions Small centralized team to provide service to each UC campus

20. Enterprise Architecture 2013 Decisions Needed: UC Identity Service Problem: Identity and Access Management is a vital component to everyday business and is highly variable across UC Decision: undertake a considerable effort to establish a robust set of services to support UC Identity and Access Management needs Timeframe: Mid-2014 through Mid-2015 Consider: Identity lifecycle – cradle to grave One repository, authoritative source, authentication & authorization support Replacing UCnetID system

21. Enterprise Architecture 2013 Decisions Needed: Additional Identity concerns Problem: privileged user identity and access mechanisms would benefit from additional security controls Decision: implement multiple factor authentication mechanisms, implement password vaulting Timeframe: Mid-2014 through Mid-2015 Consider:

22. Enterprise Architecture 2013 Current Decisions: Enterprise Data Warehouse Problem: lack of a shared system wide Enterprise Data Warehouse results in duplicative efforts to support individual campus specific instances Decision: task ITAG to investigate feasibility and value of establishing a shared Enterprise Data Warehouse Timeframe: Late-2013 through Mid-2014 Consider: Establish data governance processes to model Enterprise Data Warehouse

23. Enterprise Architecture 2013 APPENDIX 23

24. Enterprise Architecture 2013 EAA Body of Knowledge – VA example

25. Enterprise Architecture 2013 VA example …. continued