Sensor project: Workflows

The sensor project workflows describes broadly the various tasks the project has, and what each flow should result in. The participating members can apply to join any flow they are interested in. Any member will be able to always follow any flows work, even if they are not actively participating in it.

1.0

Communication

 

How the project should communicate with the outside world will be be defined here.

Web pages, events, meetings, campaigns etc.

2.0

Adoption: Certification, reference system, test portal

The work flow does not directly have to do with the development of the standard, but more the work that lies around the standard.

The main purpose of the workflow is to work out good methods that ensure the adoption of the standard by suppliers and aquaculture companies.

3.0

Sensor Types


Which sensor types the standard should prioritize, where the sensor fits into the semantic data model, what data to store per sensor type and the grouping of sensor types will be defined here.
 

4.0

API and data storage model

The API and data storage model workflow should define the API interface for stored sensor data, and storage model for the sensor data, for example a timeseries database. It must be decided how to store and retrieve data to ensure that extraction needs are taken care of independently of the system provider.

The standard should ensure that all extraction of data from sensor systems behaves equally regardless of which system you are working on.

5.0

System Infrastructure

The infrastructure workflow should define how systems that implement the standard must be built to meet the needs of the standard. It is not necessary to define specific system requirements here, but architecture and necessary components per level, and where these components must be located must be included.
 

6.0

Semantic Data Model, Biology Tracking

The standard should define a semantic data model to describe the content in a meaningful way. OPC UA is currently the prime candidate to build this data model upon. The data model is tightly connected to tracking of biology so it is included in this workflow.

7.0

OPC UA and alternatives

OPC UA is seen as the most interesting candidate technology for the data model and data carrier for the project and standard. OPC UA needs to be continually evaluated against the requirements of the standard as they emerge, in order to look at the suitability of OPC UA for the various data streams.

8.0

Data quality - Anomaly Detection and manual correction

Data quality on the sensor data is important to ensure when you have an automated data collection system. The workflow should define how best to implement anomaly detection in general, but if necessary also categorize the sensor types into groups that can use the same form of anomaly detection.

9.0

Security, encryption and authentication / access control

The task of the workflow is to define in the standard the requirements for security: encryption of data streams, authentication mechanisms and access control of data passing through the sensor system.

10.0

Standardization Process, Existing Standards and Standard Norway

The task of the workflow is to ensure that the standard being developed will have good conditions for survival over time, by defining a standardization process the standard will be incorporated when the first revision is ready. 

11.0

IoT Hub - API and system infrastructure
 

This workflow will describe the IoT Hubs specific functionality. Including any APIs, and if any, requirements to the infrastructure. A set of non-functional requirements should be included

©2019 by Aquacloud 2.0
Images copyright: Lerøy Seafood Group - Christoffer Meyer - Markus Fiskum - Hege Hovde - Kenneth Gamnes