Project Brief
Document Sign Off
| Name | Project Role | Date Signed Off |
|---|---|---|
| Simon Chapple | Project Sponsor | |
| Steve Taylor | Project Manager | |
| Matt Hodson | Technical\Delivery Lead | |
Background
Project Description
This project will deliver single customer data infrastructure that will provide a customer (service\infrastructure) model that can then be replicated on business requirement. This data infrastructure will be capable of ingesting a plethora of IoT device readings, this data will then be indexed and stored according to the IoT device owner (an application in IoT context). The stored data can then be visualised accordingly. The data will have a second stage ingest in to a relational database whereby complex analysis and correlation of data be it time index or geospatial.
The infrastructure will be delivered by the EDINA team.
Scope
Changes to Scope will be logged on the Issue Log and also recorded on the Project Scope Change page.
In scope
- Automated, scalable, rapidly deployable infrastructure
- Facility for modelling incoming IoT data in JSON format via REST API call
- Data filtering mechanism anonymising data on ingest
- University authenticated access (EASE)
- Per ‘Application’ data separation
- Secondary data analysis tier; geospatial and additional datasets
- Customer ‘model’ for infrastructure
- SSL encrypted traffic, end to end
- Encrypted file systems
- Granular data partitioning; per index within elastic search
- Dashboard visualisation for tier 1 analysis
- Automated mechanism for import into secondary tier
- Provision users and applications throughout data tiers
- Automated backup mechanism
- Infrastructure and user documentation
- Sops defined
- Registration mechanism
Out of scope
- Multiple customer instances
- Unified Federated access to infrastructure
- Resilient infrastructure
- Container based deployment of application stack
- Charging model or any other financial tool for fiscal return on delivery of service
- Customer managed ‘self service’ interface
- A full service - this project will deliver the infrastructure only.
- Unified SSO to service to both analytics tiers, i.e. Postgres login is differentiated
Objectives and Deliverables and Success Criteria
Description |
|||
Objective |
A single coherent infrastructure that will provide a per customer (service/infrastructure) model that can then be replicated based on business requirement, with supporting documentation and source code and configuration details. |
||
| Deliverable D1.1 |
|
||
|
Deliverable D1.2 |
|
||
| Deliverable D1.3 |
|
||
Success Criteria |
|||
|
• The PoC infrastructure is hosted by and signed off by ISG ITI infrastructure |
|||
|
• The infrastructure has undergone and completed the EDINA QA process |
|||
|
• The infrastructure is accepting IoT data from multiple devices and across ‘applications’ |
|||
|
• The infrastructure has successful user registrations and displaying appropriate data |
Note : An 'Application' within the IoT framework is the equivalent of a registered entity, each entity can be one person 'a user' or many, a person can also belong to multiple 'applications' however there is complete separation between 'applications' and these cannot be managed or have datasets coalesced. However, this could be achieved in the secondary analysis tier however through an export/import process.
Requirements
Requirements
A single coherent infrastructure that will provide a per customer (service/infrastructure) model that can then be replicated based on business requirement - Must have.
Supporting documentation - Must have.
Source code and configuration details - Must have.
Scalability/Data partitioning - Could have.
Benefits
• Ability to perform real time analysis of IoT data within the University.
• ability to analyse IoT data and correlate information with other data sets.
• Potential to expands the IoT infrastructure and can offer analytical tools to third parties and affiliates
Funding
All effort is core funded.