IIOT PLATFORM
Introduction
The Industrial Internet of Things (IIoT) Platform component serves as the primary interface for communication, interaction, and real-time data retrieval from IoT devices, robots, simulation modules, reasoning modules, and perception modules. The platform is designed to operate into a Fog Cluster, enabling efficient and rapid processing closer to the data source. It operates in the Fog Tier and focuses on managing the real-time state of these modules and providing access to Northbound interfaces such the collaboration modules.
Usage Manual
Key aspects of the IIoT Platform Component include:
- Communication Layer: This layer is responsible for secure and efficient communication between the off-site and on-site infrastructure, using MQTT and REST API endpoints for real-time data collection and two-way communication. The communication layer incorporates Sensor, Robot, and Human-Machine Interface (HMI) APIs for translating raw data into semantically interpreted events and states.
- Core Layer: The core layer is the main application logic layer, which combines data, events, and states, facilitating two-way interaction with the monitored and controlled IoT devices. This layer synchronizes the entire infrastructure and services using a common event loop and state machine, and it monitors the IIoT platform process through metrics collection and watchdogs for each critical component.
- Reasoning Layer: The reasoning layer provides centralized automation rules, transformation services for decision support. This can be used in parallel with specialized reasoning modules deployed in the Fog cluster.
- Fog Cluster Control Function: The IIoT Platform supports control over the simulation, perception, reasoning, and collaboration modules within the Fog Cluster via High-level interfaces supported and exposed by the modules. This control function will interact with the core layer, ensuring seamless operation and interaction with the diverse modules in the Fog Cluster.
Use Case 1.
Use Case Diagram
The IIoT devices and simulation modules interact with the platform by sending real-time data and receiving commands. The reasoning modules use the processed data for decision support, and the Northbound interfaces may use the IIoT Platform high-level APIs for task lifecycle management.
Use Case Mock-ups
No mock-ups available (backend-component)
Functional Specifications
Functional Block Diagram
The activity begins with IIoT devices and simulation modules sending real-time data to the platform. The communication layer ingests this data and forwards it to the core layer for processing. The processed data is sent to the reasoning layer, where decision support occurs based on the data and set rules. The processed data is then communicated back to the IIoT devices, Northbound interfaces, and reasoning modules. Operators then may interact with the platform.
Main interfaces
List of main interfaces between functional components shown in the figure.
| ID | Component | Name | Description | Sense |
|---|---|---|---|---|
| 1 | IIoT Platform | Communication Layer | ingestion from IIoT devices and simulation modules & Processed data sent to IIoT devices, Northbound interfaces, and Reasoning Modules. | In and Out |
| 2 | IIoT Platform | Core Layer | Processes the ingested data and monitors system health. | In and Out |
| 3 | IIoT Platform | Reasoning Layer | Provides decision support based on the processed data. | In and Out |
Technical Specifications
The MQTT and REST API endpoints facilitate two-way communication, enabling data ingestion from and command dissemination to IIoT devices and simulation modules. The Sensor, Robot, and HMI APIs are part of the communication layer that translate raw data into meaningful information. The core layer uses a state machine and event loop for data flow and processing management. The rule-based automation engine and inference engines in the reasoning layer provide decision support. The processed data is then communicated to the relevant actors through the MQTT and REST API endpoints.
Software and hardware Requirements
Required software
- custom software for the implementation of the platform features
- MQTT broker (probably Mosquitto)
- HTTP(S) server
Required hardware
- 1 VM with 6 vCPUs, 16GB Ram for dev/testing.
- Production resources depend on number of devices, services, and the volume and velocity of data.