Project Brief
IoT004 IoT Research & Innovation Service Phase 1 Project Brief
Document Sign-off
Name |
Role |
Date signed off |
Tony Weir, Director of ITI |
Project Sponsor |
|
Steve Taylor, IoT Programme Manager |
Project\Programme Manager |
|
Ewan Klein, Professor of Language Technology. School of Informatics. |
Programme Sponsor |
|
Simon Chapple, Snr Data Technologist |
Service Owner |
|
|
|
|
|
|
|
Background
The Internet of Things (IoT) is a cluster of technologies spanning hardware devices, networking, data collection and data applications. It is a rapidly growing area that will underpin many new forms of interaction and has the potential to create significant scientific, social and commercial impact. Recent estimates predict the number of devices that connect to the Internet will rise from about 13 billion today, to 50 billion by 2020.
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
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 is not intended for use by commercial or industry partners at this stage.
Objectives and Deliverables
What are we aiming to ultimately deliver that will be key to the measure of the success of this project - but potentially any significant other things along the way (that may outlive the project).
Ideally we set these as MoSCoW:
MUST - we would see the project as failing totally or partially if these are not achieved
SHOULD - we have a high expectation that these will be doable with planned work and budget - but if necessary
these can be de-scoped
COULD - if all goes very well, these might be possible
WON'T - we want to be explicit about certain things that people might expect us to deliver but we want to be clear we won't deliver
Key Milestones for this deliverable- if known, any hard dates and highly desirable dates
Objective 1 : Ensure appropriate Project Governance and Planning. |
Description of the Deliverables needed to achieve the objective |
MoSCoW |
Key Milestones |
Deliverable D1.1 |
Approved Project Brief |
MUST |
Yes |
Deliverable D1.2 |
Approved Solution Design. |
MUST |
Yes |
Deliverable D1.3 |
Baselined Project Schedule |
MUST |
Yes – Planning complete. |
Deliverable D1.3 |
Privacy Impact assessment template to support assessments by projects using the service. |
COULD |
|
Objective 2 Provision of secure systems required to run and support the end to end IoT service. |
|
|
|
Deliverable D2.1 |
An IoT network, incorporating a TTN server(s), as defined in the approved solution design. |
MUST |
YES - Build complete |
|
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 in to the IoT network. |
|
|
Deliverable D2.2 |
Completed and signed off security assessment, with agreed action plan for any risk and issues identified. |
MUST |
YES – Security assessment complete |
Deliverable D2.3 |
Updated Security Assessment Action Plan with all required actions completed before go-live. |
MUST |
YES – Security action plan complete |
Deliverable D2.4 |
Additional gateways from SemTech if these are provided in time. |
COULD |
|
Objective 3 : Provide service delivery elements required for the successful management of the new service. |
|
|
|
Deliverable D3.1 |
Approved Service description. |
MUST |
|
Deliverable D3.2 |
Approved Support Model |
MUST |
|
Objective 4 : Ensure operational readiness for go-live. |
|
|
|
Deliverable D4.1 |
Agreed Operational Readiness Plan. |
MUST |
|
Deliverable D4.2 |
Approved Operational Readiness report. |
MUST |
YES – Service ready for go-live. |
Deliverable D4.3 |
Approved Test plan. |
MUST |
|
Deliverable D4.4 |
Approved Test Report. |
MUST |
YES : Testing complete |
Objective 5 : Service go-live |
|
|
|
Deliverable D5.1 |
Live service confirmation. |
MUST |
YES – Service is live. |
Deliverable D5.2
|
Service Launch including appropriate communications
|
MUST |
|
Benefits
Benefits management and realisation will be available on the ITI SharePoint space.
The network deployed by this project will address the internal element of objective number 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. “
Success Criteria
Driven by the Deliverables and Objectives. Do we have objective measures that we can point to say the project has been a success (typically we said we would deliver X and we have)?
Alignment with Strategic Vision \ IS Themes
Please refer to the Programme Brief Addendum (* LINK TO BE PLACED HERE *)
Priority and Funding
This is a high priority project within the IoT Programme.
This project is funded by a combination of the ITI IoT budget 2017-18 and core funding.
Service Excellence - Information and Security
- Standard server builds are being used.
- We will use new IoT technologies, and we have engaged PwC as external IoT security specialist to carry out a security assessment of the IoT service solution.
- Although the project is not dealing directly with personal data, there is an expectation that research projects that will make use of the service, will capture personal data at times. The first pass of the service being delivered by this project, will not support personal data and users will be advised that no personal data should be stored within the service. Each project making use of the service will be instructed to carry out a risk assessment, and if that assessment identifies that personal data will be captured, then they will need to undertake a PIA.
- This project will produce a PIA template and this will be made available to users to support them in the production of their own PIAs.
Organisation
Governance
Project will all have these governance roles by default.
Role |
Name |
Division / Group / Team / College / School and Title |
Project Sponsor |
Tony Weir |
Director of ITI |
Programme Owner |
Ewan Klein |
Ewan Klein, Professor of Language Technology. School of Informatics. |
Programme Manager |
Steve Taylor |
IoT Programme Manager. |
|
|
|
Resources Skills
Steve Taylor (IoT): Project Management. Simon Chapple (IoT): Technical lead Mark Strevens (IoT): Technical engineer.
Nicola Osborne (Edina): Project Management. Matt Hodson\Jimmy Angelakos\Ben Soares: DAaV service build and config.
CIS team: network support.
Assumptions
- Defined requirements are complete.
- Defined scope is correct.
- The technology is well enough understood and we won’t come across any unexpected technical or performance limiting issues.
Constraints
- GDPR legislation.
- External IoT consultancy for a security assessment.
Risks
- The time line for the project is tight and the core team are also involved in other key IoT projects and IoT Programme work at the same time. This may result in a clash of demands on the team between projects, and may result in a delay to go-live..
- Key staff or skill sets will not be available when needed.
- Requirements for additional effort will surface which may not be deliverable in the project timeline.
- Issues identified during the security assessment may not be resolvable within the project timeline.
- The full set of 9 gateways, with full coverage mapping may not be complete for service go-live.
Issues
Non identified at this time.
Previous Lessons Learned
N\A
Dependencies
PwC for a security assessment.
Communication
Meetings and emails updates within the team as needed.
Monthly status reporting within the Project Services system.