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 | New installations of SCADA systems are typically expected to be compliant with the OPC UA standard | HIGH | ||
Device | OPC DA | 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 | HIGH | ||
Device | Modbus | Seems like the way the current Modbus | HIGH | ||
Device | Zigbee | MEDIUM | |||
Device | LoRa | ||||
Device | GPS | ||||
Device | Profinet | 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 | MEDIUM | ||
Device | OpenDDS | ||||
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 as logs are required to be assessed as per safety incidents | |||
Export | Client Registration & Distribution | ||||
System | System Management | Connection loss handling: changes made while offline will be cached and sent when connection is re-established | |||
Security | Security | Need to lock down access to APIs from remote hosts not authenticated |
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