• Documentation
  • Application Scenarios

Application Scenarios


EnOS Device Data Integration Service can be applied to the following scenarios.


SCADA SFTP File Integration


Data in solar SCADA system is uploaded to SFTP server as CSV files. These device data need to be downloaded every minute, transferred to EnOS standard device format measurement points, and integrated to EnOS Cloud.


../_images/scenario_scada.png


  1. Timer triggers the flow every minute.
  2. Task Manager manages the task status and keeps the failed tasks for the next trigger.
  3. SFTP Client downloads and backs up CSV files.
  4. CSV parses the CSV files into JSON format and processes them line by line.
  5. Switch branches the data of different device types to different downstream node via cases.
  6. Script converts the device measurement points to EnOS standard format through JavaScript to integrate.
  7. Lookup Asset looks up asset IDs based on the device measurement points.
  8. Upload Measurement Pt. uploads measurement point information to EnOS Cloud.

Device Data Integration from 3rd-party system


The real-time monitoring data of sites has been connected to the 3rd-party system or platform. Device Data Integration Service can be used to connect, integrate, and process data from MQTT, HTTP, or Kafka server to EnOS Cloud, and transfer the data to the standard format for further processing in EnOS. The below takes an HTTP server as an example.


../_images/scenario_3rd_integration.png


  1. Inject triggers the flow every 15 minutes.
  2. HTTP Client requests to the 3rd-party HTTP server based on authentication and gets data according to the configured Headers and Body.
  3. Script verifies the input msg and transform it into JSON format.
  4. Script converts the data into the EnOS standard data format for uploading.
  5. Upload Measurement Pt. uploads the measurement points of the devices in real-time to EnOS.

Data Multicast to 3rd-party System


You can use Device Data Integration Service to transmit data to 3rd-party systems by invoking EnOS APIs. The following takes the Azure IoT Hub as an example.


../_images/scenario_3rd_transmission.png


  1. HTTP Client inputs data from HTTP server.
  2. Lookup Asset looks up devices by Device Key and output their asset IDs.
  3. Multicast multicasts the input msg into multiple downstream nodes.
  4. Update Device Status updates the device status to online according to asset IDs.
  5. Upload Measurement Pt. upload the measurement points of the devices in real-time to EnOS Cloud.
  6. Azure IoT Hub node uploads the data to the Azure IoT Hub.
  7. Kafka Pub publishes the data to the specified Topic of the Kafka server.

Device Command Integration


When applications issue control commands to NB-IoT devices that integrate with EnOS via 3rd party cloud and the devices report the execution status to the applications, DIS is needed to perform uplink/downlink integration.


../_images/scenario_command.png