Closure Report
Project Summary
Background
The University of Edinburgh is running an IoT Programme to help realise its IoT strategy. See the IoT strategy and IoT Programme Brief documents for more detail.
This project is part of the IoT Programme and it will deliver the first phase of the IoT Research & Innovation Service, and is aligned with the following objective from the IoT programme Brief: “Deploy and promote the IoT infrastructure so as to support research, development, innovation and teaching with a range of partners both inside and outside the University, including SMEs and industry.
Scope
The scope of this project was to create an IoT network and service to support research and innovation within the University. This will be a first phase delivery aimed at University researchers only. There will be no SLA for this phase, and users will be asked to provide feedback regarding their experience using the service.
Out of Scope
This first phase service was not intended for use by commercial or industry partners at this stage.
There will be no Privacy Impact Assessment as no personal data is processed by the project, and the service deliverable resulting from this project will not support collection or processing of personal data at this stage. This will be clearly stated in the Terms of Use for the service.
Outcome
End of project summary
The objectives and the key “Must” deliverables have all been completed, although the project ran on longer than expected. This was due to unexpected resource limitations, including a staff strike as we approached service go-live, and the security assessment taking more effort and time than expected. Only one “Could” deliverable was not met – which was the integration of additional network gateways – as the project decided not to enter into the relationship with Semtech which would have provided these additional gateways. The service went live (Phase 1) on 16th May 2018, but as the project’s IoT Workshop took place on 31st May 2018, and the subsequent post-workshop reports were appended as deliverables of the project, the full project completion and closure has run to 3rd October 2018.
Objectives from Brief:
|
No. |
Description |
Objective Met? |
|
O1 |
Ensure appropriate Project Governance and Planning. |
Yes |
|
O2 |
Provision of secure systems required to run and support the end to end IoT service. |
Yes |
|
O3 |
Provide service delivery elements required for the successful management of the new service. |
Yes |
|
04 |
Ensure operational readiness for go-live. |
Yes |
|
05 |
Service go-live. |
Yes |
Deliverables from Brief:
|
No. |
Description |
MoSCoW |
Delivered? |
|
D1.1 |
Approved Project Brief. |
Must |
Yes |
|
D1.2 |
Approved Solution Design. |
Must |
Yes |
|
D1.3 |
Agreed Project Schedule. |
Must |
Yes |
|
D2.1 |
A LoRaWAN IoT network, incorporating a TTN server(s), as defined in the approved solution design. |
Must |
Yes |
|
D2.2 |
A DAaV (Data Analysis and Visualisation) service running Kafka, Elastic Search, Postgres, and Kibana, for data capture, storage, analysis, as well as geo-spatial and visualisation services, integrated into the IoT network. |
Must |
Yes |
|
D2.3 |
Completed and signed off security assessment, with agreed action plan for any risk and issues identified |
Must |
Yes |
|
D2.4 |
Updated Security Assessment Action Plan with all required actions completed before go-live. |
Must |
Yes |
|
D2.5 |
Additional gateways from SemTech if these are provided in time. |
Could |
No |
|
D3.1 |
Approved Service description. |
Must |
Yes |
|
D3.2 |
Approved Support Model |
Must |
Yes |
|
D4.1 |
Agreed Operational Readiness Plan. |
Must |
Yes |
|
D4.2 |
Approved Operational Readiness report. |
Must |
Yes |
|
D4.3 |
Approved Test plan (incorporated in to the Test Report) |
Must |
Yes |
|
D4.4 |
Approved Test report |
Must |
Yes |
|
D4.5 |
Accepted RAID log |
Must |
Yes |
|
D5.1 |
Live service confirmation. |
Must |
Yes |
|
D5.2 |
Service Launch including appropriate communications |
Must |
Yes |
Benefit:
The network deployed by this project will address the internal element of Objective 5 from the IoT programme Brief: “Deploy and promote the IoT infrastructure so as to support research, development, innovation and teaching with a range of partners both inside and outside the University, including SMEs and industry. “
Benefit realisation:
An active promotion campaign for the new service has not taken place since the IoT service team still needs to be populated. However, projects that make use of the new service are underway and there are a number of potential projects in the pipeline, including those that will lead to teaching activities. All of this indicates that the stated benefit form this project will be met.
To fully realise the potential for the IoT Service further investment in staffing and IoT service infrastructure is required. The City Deal Data Driven Innovation Programme is the expected source of this investment.
Lessons learned.
No: 01 Title: Engineers can install gateways upside down.
Description: When investigating a failed gateway, it was discovered that the device had suffered a hardware failure to due rain getting in to the box. Rain got in to the box because it had been installed upside down.
Recommendations: Evidence/sign-off of installation should be performed, e.g. installation engineers should provide photographs of installation or a member of the IoT team should visit and inspect gateways shortly after install.
Date identified: 15/03/2018
Impact: Detrimental – gateway was damaged beyond repair.
No: 02 Title: Engineers can fail to close the access doors on gateways.
Description: When investigating a failed gateway, it was discovered that the device door was open and rain had caused a hardware fault. The door was closed the last time the IoT team attended the device, so the door must have been opened some since then, without the IoT team being aware.
Recommendations: Apply tamper detection and reporting to the gateways. IoT team to attend site when tampering is detected.
Date identified: 16/05/2018
Impact: Detrimental – gateway was damaged beyond repair.