Report for August 2018

DTI026 API Gateway and API Management Tool

Discretionary

Milestones

Target Date	Title
21- Aug - 2018	Build Review
17 Oct 2018	Acceptance Review
22 Oct 2018	Delivery
06 Oct 2018	Deployment Review
30 Oct 2018	Closure

RAG

AMBER

Report for August 2018

Achievements in Last Period

• Completed the configuration of WS02 with  the "low request call" pattern 2 instance  on the development environment  enabling  key users to carry out  evaluation testing.
• Completed a successfull  formal requirement evaluation and build review  of WS02 as our minimal viable product for the API gateway and lifecycle management tool
• Obtained formal sign-off of  the evaluation WS02 against the success criteria / requirements by the Enterprise Architect

Issues

• PICCL Change 12 - Change to milestones
• PICCL Change 13 - The evaluation of WS02 against the Gateway and Management Requirements and the decision to proceed with the implementation  

Next Steps

• Implement the tasks to make WS02 "production" ready. These are detailed in the PICCL Change 13.
• Obtain formal authorisation of  the evaluation of  WS02 against the success criteria / requirements by Development Services, IS Applications Service Management and Production Management heads of service
• Re-plan the deliverables based on the output from the evaluation meeting,  while also  considering the resource constraints 

DTI028 Maturing the API Infrastructure

Discretionary

Milestones

RAG

AMBER

Report for August 2018

Achievements in Last Period

We now have firm resources requisitioned in Asta esuring progress in the delivery of

• WP 2 - D2.1 containerised micro-service  -  Michael Sun
• WP 4.1  - D5.1 - templates for new APIs – Python - John Allison
• WP 6.1  -  D7.1 - implement security scanning ; ZAP -Thalia NIKOLAIDOU
• WP 6.2-  D7.2  - implement security scanning; Dependency Check - -Thalia NIKOLAIDOU

Issues

ENT020 Centralised Logging Project has not delivered required functionality and this will impact the delivery of WP7.1 and WP7.2 . This is now being mitigated by carrying out a joint design workshop with the Call Logging Administrative team to provide advice and guidance on how we may be able to consume the services and implement our deliverables in an optimal fashion

Next Steps

Complete the following work packages:

• WP 2 - containerised microservice
• WP 4.1 - templates for new APIs - Python
• WP 7.1 - utilise centralised logging - writing to logs
• WP 7.2 -  utilise centralised logging - reporting from logs
• WP 8 - update API standards - this is dependant on WP7.1 & WP7.2 as well as the successful implementation of WS02 within DTI038

Notes

• Note that the numbering of work packages in the Project Brief differs from that used in the Project Plan.  This is due to the Project Planbeing updated during the planning phase and the changes not being applied retrospectively to the Project Brief.  For consistency, the numbering in the Project Plan is used in meetings notes and Asta bookings.

DTI029 Maturing the API Service

Discretionary

Milestones

Target Date	Title
23/11/2018	Delivery - D5 (Sustainability Plan)
23/11/2018	Delivery - D4 (Enhanced API monitoring)
14/12/2018	Delivery - D6 (Secure software development standard)
05/10/2018	Delivery - D7 (Events Booking utility)
27/11/2018	Delivery - D9 (Update Service Risk Log)
02/01/2019	Delivery (project)
18/01/2019	Deployment Review
08/02/2019	Closure

RAG

AMBER

Report for August 2018

Achievements in Last Period

• Re-plan outstanding deliverables,  taking into consideration resourcing constraints and the provision of  revised target dates
• D5 Sustainability Plan - in progress -the work is based on the ITIL RACI matrix developed as part of DTI006 BI/MI as a Service  with as-is, to-be and aspirational categories of services that can subsequently be costed.  A meetingis being arranged to clarify of purpose of the document against the backdrop of the need to develop a target operating model , for the implementation and management of the APIs.
• D6 Secure software development standard - a booking for Thalia  has now been made within ASTA  however development will not start until November 2018 .

The following deliverable are categorised as should-have:

• D7 Events Booking utility - The design document is out for review and sign-off and estimates for the build  process are being reviewed as this will  now include an update to an existing API.
• D9 Update Service Risk Log - There are strategic decisions that need to be made regarding the risk log development for the whole of the Service Management Team, these are currently being explored.

Issues

• The scope of the project will be changed to incorporate the definition of a Target Operating Model for the delivery and management of the APIs. This is required to ensure the successful  transition of the API development to Business as Usual and it will also put the sustainability plan in context. A PICCL will be raised to enable this

Next Steps

• Continue with outstanding deliverables;  D5, D6, D4, D7 ,  D9 &  D10
• Raise a PICCL to revise milestone based on the output of the re-planning

DTI018 Continuous Service Improvement APIs

Discretionary

Milestones

RAG

AMBER

Report for August  2018

Achievements in Last Period

The Steering Group on 8th May approved the following list of APIs for development, the status of each is shown below:

• EUGEX Schools Feed
  • Approval from Data Steward (Lisa Dawson) is required before development can begin

• Card API
  • User Acceptance Testing arrangements have now been completed. Tests will commence in the next two weeks

• Pure API - UUN to UUID
  • User Acceptance Testing arrangements have now been completed. Tests will commence in the next two weeks 

• Org Hierarchy

  • Deployed into the  production environment  on 2 Jul 2018. Further clarification on ownership is being sought but in the interim this will be supported by the Service Management Team

• HR

  • User Acceptance Testing arrangements have now been completed. Tests will commence in the next two weeks 

The Enterprise API Steering Group meeting was held on 21/08/2018  and the next batch of API's to be developed  was presented for approval and prioritisation. These are 

1. AD password reset date: This is needed to determine if new students have synchronised their AD password and the target communication to the students. This will avoid the 1000s of support calls we had last year relating to wifi access as a result of this not being done.
2. Learn Gradebook Access - This will get the  results of Data Protection and Information Security courses available for reporting. Currently this is a manual process of exporting to csv but the API will provide real-time information
3. Computer Lab occupancy: This will allow student interns in LTW to  deliver a better display of free computers in labs, including using geo-location to guide students to free PCs. 
4. TOPdesk General API  - This will be used with “Quick Calls” Application
5. Lab Monitoring API - This will monitor student usage of the labs;  provide start and finish time of the session by student; usage of individual labs, groups of labs and lab alias
6. EDW Person ID Resolver - This will resolve an ID of any type into all the possible IDs associated with that account, so that each account holder will have a single record in the EDW
7. IDM Functional Status API - This is for assisting with managing functional accounts in the IDM.
8. VRS API - enhancement  - This will support pulling down data on current/future visitors

Three JIRA boards have been created - one for managing all requests, one for managing withdrawals and one for managing those taken forward for development.

Issues

•  Issue 10 - Inability to complete the development of the API's within the current academic year 17/18. This has now been realised and an updated project plan with new milestones has been created

Next Steps

• Continue with analysis and development of APIs above

• Raise PICCL to change delivery timelines 

22/12/17 - Project withdrawal approved by WIS 22/12/17 - PICCL Change 6

6/12/17 - Recommendation is to withdraw and review requirements again in 18/19 due to PICCL Issue 5, project risk 5

13/10/17 - Project suspension approved by WIS 13/10/17 - PICCL Change 4

Project closure approved by WIS 23/3/18

5/2/18 - Recommendation is to close project early - PICCL Decision 8

6/12/17 - Recommendation is to review conditions for removing project from suspension in 18/19, PICCL Change 7, project risk 10, project risk 11

17/11/17 - Project suspension approved by WIS 17/11/17 - PICCL Change 7