Report for July 2018

DTI026 API Gateway and API Management Tool

Discretionary

Milestones

Target Date	Title
21- Aug - 2018	Build Review
TBA	Acceptance Review
TBA	Delivery
TBA	Deployment Review
TBA	Closure

RAG

AMBER

Report for July 2018

Achievements in Last Period

• The issues raised in PICCL 12 have now been mitigated and work is progressing on D2 (Delivery and setup of infrastructure to support API Gateway and API Management Tool) and D3 (Installation and configuration of WSO2 into the dev, test and live environments). 

Issues

• PICCL Change 12 - Change to milestones

Next Steps

• Complete the configuration of the "low request call" pattern 2 instance  on the development environment and make available for  pre-assessment user testing 
• Undertake Gateway requirement assessment and Build Review (scheduled for 21 August 2018)
• Re-plan the deliverables based on the output from the Review meeting and associated resource constraints 
• Complete D2 (Delivery and setup of infrastructure to support API Gateway and API Management Tool) and D3 (Installation and configuration of WSO2 into the dev, test and live environments)

DTI028 Maturing the API Infrastructure

Discretionary

Milestones

RAG

AMBER

Report for July 2018

Achievements in Last Period

• WP 1 - caching service complete

• WP 3 - DR / resilience testing complete

• WP 5 -  store security details in central tools complete

Issues

ENT020 Centralised Logging Project has not delivered required functionality and this will impact the delivery of WP7.1 and WP7.2  below

Next Steps

• Complete the following work packages:
  • WP 2 - containerised microservice - to complete once implementation of containerised infrastructure delivered by DTI026 , which has been significantly delayed 
  • WP 4.1 - templates for new APIs - Python - due to resource constraints , this will not be completed until October 2018
  • WP 6.1 - implement security scanning - ZAP - revised estimates have been provided and the resource is currently being requisitioned within Asta
  • WP 6.2  - implement security scanning - Dependency Check - revised estimates have been provided and the resource is currently being requisitioned within Asta
  • WP 7.1 - utilise centralised logging - writing to logs - this was dependent on the successful delivery of the centralised logging platform by ENT020. On delivery it  seems that all the functionality required has not been provided. Further investigation to assess the  additional functionality required and if it can been accommodated within the current budget.
  • WP 7.2 -  utilise centralised logging - reporting from logs - this was dependent on the successful delivery of the centralised logging platform by ENT020. On delivery it  seems that all the functionality required has not been provided. Further investigation to assess the  additional functionality required and if it can been accommodated within the current budget.
  • 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
TBA	Delivery - D5 (Sustainability Plan)
TBA	Delivery - D4 (Enhanced API monitoring)
TBA	Delivery - D6 (Secure software development standard)
TBA	Delivery - D7 (Events Booking utility)
TBA	Delivery - D9 (Update Service Risk Log)
TBA	Delivery (project)
TBA	Deployment Review
TBA	Closure

RAG

AMBER

Report for July 2018

Achievements in Last Period

• D1 Revised data landscape - it was agreed previously that there was no longer an immediate business requirement A PICCL will be raised to de-scope it and included in the next project;  Embed and Optimise the API Service 
• D2 Process for managing and approving requests   -  This deliverable is complete
• D3 Checkpoint in the authorisation process -  This deliverable is complete
• 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.  Final amendments to the initial draft document are being  circulated for review
• D6 Secure software development standard - this is dependent on completion of delivery of security training to development staff; The resource conflict  with FIN119 is currently being progressed
• D8 Validate API pipeline.  This deliverable is complete.
• D10 Forward visibility of the API pipeline - This has now been progressed in conjunction with the deliveries in DTI018 (CSI APIs) and three JIRA boards have been created: one for managing all requests , one for managing those taken forward for development and one for those that have been withdrawn. We cannot publish these widely yet due to some security concerns and  these are being investigated . In the meantime the  Wiki is  being used for improved visibility.  

The following deliverable are categorised as should-have:

• D4 Enhanced API monitoring -  This deliverable is dependent on the successful completion of the evaluation of WSO2  (part of deliverable 4.2 in project DTI026  API Gateway and API Management Tool). This  has been significantly delayed 
• 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

• There has been an absence of a project manager for a month and as such number of the deliverables have  been delayed.  Tola Odedina ,  the new project manager has now started in July 2018.
• PICCL Change 4 - change to milestones

Next Steps

• Re-plan outstanding deliverables,  taking into consideration resourcing constraints and the provision of  revised target dates
• Continue with outstanding deliverables;  D5, D6, D4, D7 ,  D9 &  D10

DTI018 Continuous Service Improvement APIs

Discretionary

Milestones

RAG

AMBER

Report for July 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
  • Business analysis complete
  • Requirements documented in JIRA DTI018-29
  • Approval from Data Steward (Lisa Dawson) is required before development can begin

• Card API
  • Requirements documented in  JIRA DTI018-67
  • Development complete

• Pure API - UUN to UUID
  • Requirements documented in JIRA DTI018-46
  • Deployed into the test environment
  • User Acceptance Testing arrangements are being  finalised 

• Org Hierarchy

  • Deployed into the  production environment  on 2 Jul 2018

• HR

  • Retrospective approval has been received 
  • Requirements documented in  JIRA DTI018-10
  • Deployed into the test environment
  • User Acceptance Testing arrangements are being  finalised 

The Head of Service Management has approved  the implementation of  three additional APIs. This has been done on the basis of a tactical need to move quickly in order to realise the benefits

• AD password reset date: This is needed to determine if new students have synchronised their AD password. This is needed for start of term to try and target comms to avoid the 1000s of support calls we had last year relating to wifi access as a result of this not being done.
• Learn gradebook access: getting results of Data Protection and Information Security courses available for reporting. Currently this is a manual process of exporting to csv, and we need real-time information
• Computer Lab occupancy: Student interns in LTW are working on delivering a better display of free computers in labs, including using geo-location to guide students to free PCs. 

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

Next Steps

• Continue with analysis and development of APIs above

• Present the next batch of API's to be developed,  to the Enterprise API Steering Group , for approval and prioritisation

• Re-plan the API development and deployments

• 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