1. UC IT Architecture Committee (ITAC)
ITAC Alignment for ITLC - 05/09/2019
Matt Faulkner (Chair)
Bruce Miller (Co-chair)
Jerome McEvoy (UCOP Enterprise Architect)
6/72017

2. Outline… ITAC Orientation ITAC Alignment for ITLC ITAC Investments
ITAC Campus Impact
ITAC Common Inventory Platform
ITAC Going Forward
ITAC Ask
7/5/2019

3. ITAC Orientation
”Establish the enterprise architecture and technology infrastructure necessary to promote and support interoperability and sharing of IT solutions among and between campuses" 
Leadership:
Matthew Faulkner, UCM (Chair) July’18- June’19
Bruce Miller, UCSB (Co-chair) July’18- June’19
Jerome McEvoy, UCOP Enterprise Architect (ex-officio)
Dana Watanabe, UCI, UC Trust chair
Primary ITLC liaison: Danna Gianforte, UCR
Secondary ITLC liaison: Ann Kovalchick, UCM
7/5/2019

4. ITAC Orientation Subgroups: EA Framework and Artifacts UC Trust
API Architecture, Integration and Best Practices
Cloud Strategy (on hold for ITLC alignment)
Common Inventory Platform
7/5/2019

5. ITAC Alignment for ITLC
ITAC helps ITLC to address the effect, the impact of coordinating across 15 CIOs, 15 executive management teams, and the Regents
ITAC is the arm of ITLC that helps them:
a. Confirm where we are b. Identify where we want to be c. Determine the steps to get from a to b
d. Assist ITLC in executing those steps (curating materials, measuring success, working risks and issues and identifying course-corrections, etc.)
e. Rinse and repeat based on ITLC direction
7/5/2019

6. Technology Roadmap ahead…
Security, Cloud and Integration – are the most important investment areas.
ITAC has been working these areas for the last few years (partial FTE allocations). A portion of ITAC time should be allocated to maintaining and harvesting these investments (~30%).  
7/5/2019

7. ITAC investment so far…
Security
We have developed many EAAs to support the implementation of good security posture. The EAAs can be implemented on projects. We have supported the development of the IS-3 policy to ensure the expectations for information security are current and considered mandatory. 
Cloud
We (membership as it is today) do not have enough cloud experience (or FTE allocation) to provide ‘qualified’ Reference Architectures in advance. So we do what we have to do, qualify ourselves through shared experience. We also work as a supplement to cloud-focused groups (cloud security alliance), using our framework and conduits to spread knowledge. 
Integration
We have created EAAs to support consistency and security in the development of integration capabilities. We have established an integration platform that any campus can use if they don’t have an existing integration platform.
7/5/2019

8. ITAC Campus Impact: UCI
Together with the UCOP Enterprise Architecture Team, ITAC has facilitated a foundation for UCI’s Office of Information Technology to form and expand their first campus Architecture Review Board (ARB).  The ARB has evolved into an effective cross-functional work group with broad representation.
UCI’s ARB came about at the strong recommendation from ITAC to have local campus reviews of the architecture principles, standards and guidelines that are created for system-wide IT services.  The ARB has leveraged and adopted the UC EAA framework, workflow, glossary, and EAA format, and maintains links to the UC EAAs for the ARB standards. For example, the ARB adopted system monitoring standards leverage the UC EAAs from ITAC. 
UCI has a number of local security standards that draw upon the principles in the UC EAA as well.  UCI systems use these standards as part of baseline OS images for example.  And, for synergy and to reduce cross-over activities, ITAC incorporated the important UC Trust work group.  UC Trust is essential to developing system-wide standards and solutions. 
7/5/2019

9. ITAC where to invest next…
Common Inventory Platform (CIP)    
If ITLC would like to pursue efficiencies in terms of application portfolio management, business functions inventory, modernization opportunities, shared or common applications – then yes, investing in the CIP efforts is the next logical move. If ITLC does not see a day when campuses pivot towards investments in multi-tenant solutions, harmonious processes, shared resources – then no, we can continue as is. 
Solution Architecture 
ITLC could also opt to use the ITAC as a resource pool for architecture consultation (on system-wide or campus-specific solutions). We could assign members to ‘projects’, have them draft solution architecture and then provide input on the solution architecture. Through repetition we’d build experience. Through ‘crowd sourcing’ we’d catch more deficiencies than an individual might.
7/5/2019

10. Common Inventory Platform (CIP)
One campus does not have SN (UCR?)
7/5/2019

11. CIP – Sample Questions & Answers
What is the proportion of Cloud to On-premise deployments…this year/last?
Which LOB consumes the most…Business Applications, Tech Services?
What is my dependency on <anything>?
How does <Business Function> compare cross campuses?
Which <Biz App, Tech Service> changes the most?
Which campus performs <Business Function> best?
What is the impact of replacing, patching, …<anything>?
How do I compare to Campus X in terms of …<anything>?
Has anyone integrated Software X with Software Y?
How many <anything> do I have locally, system-wide?
Where do I need Product Management?
Link to inventory
Link to ServiceNow APM –
7/5/2019

12. CIP – Timeline [DRAFT] Link to inventory
Link to ServiceNow APM –
7/5/2019

13. ITAC Going Forward
We're just beginning to partner with other system-wide working groups who have similar goals and objectives, and thus we can help reduce duplication and redundancy when it comes to curation of a UC BoK.
ITAC is assisting ITPS in crafting/curating supporting materials (aka reference architectures) that meet IS-3 requirements.
We've envisioned working with UC SNUG on how to leverage every location's Service Now systems to support a UC CMDB taxonomy
We are a resource for information about what each location is doing, connecting the dots between SMEs, and helping each other past hurdles (something that has been quite useful for our own campus, most recently the budget numbers for Mulesoft)  
7/5/2019

14. ITAC Ask
Although we ask all ITAC members to contribute time every month, and create subgroups such as the AWS Cloud Security and the API subgroup, it isn't clear that leadership can afford dedicating the FTE ITAC needs for significant deliverables without backfill FTE. 
With minimal resources, it is difficult to deliver value.
7/5/2019

15. UC ITAC
Thank you…
…any questions/feedback?
7/5/2019