Description
Scope of this activity is to perform a gap analysis on the current status of EdgeX microservices and deliver specific market requirements to other Working Groups.
Requirements
As part of the gap analysis, common requirements in Oil&Gas will be taken into account.
Design
| Area | Microservice | Gaps Identified | Criticality | Why Important | Recommended Actions |
|---|---|---|---|---|---|
| Device | OPC UA | Missing | HIGH | New installations of SCADA systems are typically expected to be compliant with the OPC UA standard | |
| Device | OPC DA | Missing | HIGH | Although OPC UA is an emerging standard, E&P Companies are still massively using OPC DA in legacy systems and in some cases in new installations as well | |
| Device | Modbus | Seems like the current Modbus implementation is querying 1 register at a time on the Modbus Slave. Modbus requests should be grouped together requisting multiple registers with a single call. | HIGH | Sending too many requests is invasive on the PLC which needs to conserve CPU cycles to perform its control duties | |
| Device | Zigbee | Missing | MEDIUM | Wireless sensors are slowly gaining traction for non-critical measurements as wiring can be tough in certain constrained environments. Zigbee would be a good option. | |
| Device | LoRa | Missing | MEDIUM | Wireless sensors are slowly gaining traction for non-critical measurements as wiring can be tough in certain constrained environments. LoRa would be a good option. | |
| Device | GPS | Missing | MEDIUM | Could a GPS DS serve to get the coordinates (lat/long - 2 floating point metrics) from the gateway? | |
| Device | Profinet | Missing | MEDIUM | Siemens hardware is used in many Oil&Gas installations (e.g. North Sea) and Profinet I/O would be a suitable protocol for interfacing with EdgeX | |
| Device | DDS | Missing | MEDIUM | DDS is used in drilling for data messaging on critical items | |
| Core | Data | ||||
| Core | Metadata | ||||
| Core | Command | ||||
| Support | Rules Engine / Analytics | ||||
| Support | Scheduling | ||||
| Support | Alerts & Notifications | ||||
| Support | Logging | Need to be able to specify persistency policies for type of logs | HIGH | Different logs are required for liability purposes and can be assessed in case of incidents | |
| Export | Client Registration & Distribution | Missing mechanism for backfilling historical data. (perform an export job from start-timestamp to end-timestamp) | MEDIUM | Retrieve historical data back to the cloud | |
| System | System Management | Connection loss handling: changes made while offline will be cached and sent when connection is re-established | MEDIUM | Edges could be often disconnected | |
| Security | Security | Need to lock down access to EdgeX from remote hosts not authenticated | HIGH | High security concerns |
Code
If specific code addressing some of the identified gaps will be implemented as part of this project, the contributor will submit a PR on the relevant github repository.
Current status
Waiting on v0.5 release.
A preliminary document was shared here EdgeX-Foundry-Oil&Gas-v3.pdf