Common API Platform Project (CAPP) – CIO Council Update 9/7/2018 Common API Platform Project (CAPP) – CIO Council Update September 15, 2017

CAPP Update to CIO Council Agenda Joining EA & CAPP Efforts Interoperability Focus Group Read-out API Backlog Update & Discussion Executive Dashboard Roll-Out

Joining EA & CAPP Efforts As a result of the EA & CAPP August EC meetings, a decision was made to combine them. EA: Define the Layers of the Enterprise Architecture Develop Principles and Standards for each Layer CAPP: Implementation arm of the Interoperability Layer Ensure alignment between the two groups in order to support the development of consistent standards and best practices

EA + Project Standard Approach Enterprise Architecture FY18 Projects EA Layers – FY18 Focus Implementation of Principles & Standards Security User Experience HUIT GOAL #4: Enhance user-experience across our applications and systems Applications and Software Components Middleware HUIT GOAL #13: Common API Platform Project Interoperation Data HUIT GOAL #1: Cloud Migration Infrastructure and IaaS Networking

Applying the Standard Approach to CAPP Enterprise Architecture Common API Platform Project EA Layers – FY18 Focus Implementation of Principles & Standards Security User Experience Solutions Applications and Software Components Other APIs Middleware Person API Course API Other APIs Other APIs Interoperation Tools Data Infrastructure and IaaS Networking

Common API Platform: Vision, Objectives, Strategy Project Vision Reduce integration cost, time, and effort by simplifying the way schools and central units exchange data between our systems.   Project Objectives Key Performance Indicators Simplify our data exchange architecture Reduce cost of exchanging data between our systems Improve consistency of projects delivering data exchange solutions Common API platform is implemented Number of APIs documented and registered Percentage of new projects leveraging API platform for data exchange Number of legacy point-to-point integrations retired Staff in central departments and each school trained on developing APIs using the common platform Implementation Strategy Implement Common API Platform Build, Document & Catalog APIs Create prioritized backlog of APIs to build and/or register Develop new APIs per prioritized backlog Extend the Person Data Service (new attributes) Engage with Contingent Workforce, Broadcast Communications, Buy-to-Pay, and others Replace existing point-to-point interfaces Engage API Community Train cross-department staff on API Development Form an API Community of Practice The Key Performance Indicators we will gauge our success by are: The Common API platform is fully implemented with an operational model that will allow for sustained service delivery. At least twenty (20) existing APIs are selected, documented in the data glossary, and registered in the API Gateway. A provisioning process is established to ensure streamlined access to the APIs. All new projects leverage the API platform for data exchange. At least five (5) legacy point-to-point integrations are replaced and retired. At least ten (10) staff members are trained on API Development and form an API Community of Practice.

Interoperability Focus Group (IFG) Overview Charge Provide cross-functional perspective regarding: the API backlog and prioritization, the Mulesoft development platform, and Enterprise Architecture principles and standards that will help optimize interoperability across the enterprise. A key early goal for this group will be to assess the impact and risk of deferral for the top 20-30 APIs. Objectives Success Criteria 1 Identify areas of greatest opportunity for interoperability Edited/Updated API backlog APIs evaluated for Impact and Risk of Deferral (Matrix) 2 Validate EA principles and standards for interoperability Standards affirmed and adopted by implementation teams 3 Identify areas and approaches to promote adoption of interoperability tools and platforms Increasing number of developers provided access to Mulesoft development platform and Collibra business glossary tool 4 Act as liaison to other committees such as ETAB and Mulesoft Working Group On-going formal and informal outreach at the local level by IFG members

Interoperability Focus Group Read-Out Participants included HUIT, HBS, GSE, HKS, HMS Group suggestions related to the Charge, Objectives and Success Criteria: Expand research and outreach to include groups outside of Harvard Expand the success criteria for objective 3 (promote API adoption) to better fit School requirements API voting materials were distributed on Wednesday (results on slide 10) Items identified for future discussion: Continued voting on API Backlog items API documentation options & standards Building an established process for interoperability ODS v. API v. Informatica/ETL tool v. Reporting tool Engaging with other HigherEd institutions

API Backlog Update & Discussion Implemented prioritization process per recommendation from Executive Committee Interoperability Focus Group and CAPP Steering Committee to be key contributors to evaluating APIs in the Backlog Initiated process for 4 APIs: Person, Course, Enrollment, Dining* Key Findings: Consistent interest in the Person API, stands out to deliver most value High levels of interest in Student data, primarily Bio/Demo data Desire to expose/document/register existing Vendor APIs for easier usage Need to coordinate around inbound/outbound APIs for similar content (e.g. Course, Enrollment) Gathered API Backlog inputs from: ATS-HR ATS-FAS ATS-Enterprise Student Systems ATS-Grants Management IAM HBS

Distributed Development API Value Matrix Based on votes from the Interoperability Focus Group (IFG), we have plotted the first 4 APIs Risk of Deferral Impact High Value/Assess Sponsorship Required Distributed Development Person – 4 Impact; 3.17 RoD Course – 3.17 Impact; 3 RoD Enrollment – 2.67 Impact; 2.67 RoD Dining – 2.17 Impact; 1.83 RoD Comments: If Person API has affiliations (IDs, Roles, Bulk download) it would increase impact (HKS) If data available from source system, scored the need for an API low in both categories Ratings are uninformed as new to HUIT Schools are already getting data they need in some other fashion; odd to say RoD is ever extreme Course and enrollment are linked, so rated them in tandem 4 APIs to be assessed each week IFG and CAPP Steering Committee will “vote” on each API

Executive Dashboard Review See handout

Appendix

Enterprise Architecture Activities & Responsibilities EA will co-facilitate the Interoperation Focus Group EA will contribute to the CAPP backlog and participate in the prioritization process EA will reconcile, document and communicate interoperability principles and standards EA (ETAB) has defined early standards and best practices for API development for HUIT teams and will continue to develop/document relevant standards and best practices for the University community.

CAPP Activities & Responsibilities CAPP will co-facilitate the Interoperation Focus Group CAPP will drive outreach/engagement and creation of the backlog Following EA principles and standards, CAPP will manage the implementation of API development priorities CAPP will create a transparent work/API prioritization process CAPP is responsible for managing other aspects of the project, such as Service Delivery standards/SLA’s

CAPP Increment 1 (ending 9/30) Goals Mulesoft Platform Finish defining and document Mulesoft Platform SLAs Create organized documentation for developer onboarding Implement CyberArk to support automated deployment Deliver a platform/service maturity roadmap Person API Build and deploy Harvard Administrative API to PROD Onboard a 2nd customer to the Harvard Public API Gain approval on a statement of vision for Alumni data in the Person API Course API Complete implementation of the /course endpoint Complete documentation in Mulesoft and Collibra Deploy the Course API to STAGE Plan for integration of enrollment data API Backlog Create and implement an API Backlog template Capture API Backlog entries from pilot schools/departments Create and implement the Prioritization approach for all APIs in the backlog Collibra Platform Create a shared vision for Collibra Create/Design a standard Operating Model for APIs Conduct knowledge transfer to onboard new team members Initiate peer institution outreach and discovery Change Management Develop the Change Management Strategy Define the Mulesoft outreach approach Project Operations Develop the Executive Dashboard so it is available in Qlikview via SNOW Establish the project KPIs Identify all required inputs that must be captured to report on project metrics