| # | Area | Microservice | Gaps Identified | Criticality | Why Important | Recommended Actions |
|---|
| 1 | Device | OPC UA | Missing | | New installations of SCADA systems are typically expected to be compliant with the OPC UA standard, this standard is good for new facilities | Integrate Samsung DS for OPC UA |
| 2 | Device | OPC DA | Missing | | E&P Companies are still massively using OPC DA in legacy systems and - in limited cases - in new installations as well | Assess resources & roadmap with TSC |
| 3 | 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. | | Sending too many requests is invasive on the PLC which needs to conserve CPU cycles to perform its control duties | Engage Device WG and discuss with them how to handle this |
| 4 | Device | Zigbee | Missing | | 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. | Assess resources & roadmap with TSC
|
| 5 | Device | LoRa | Missing | | 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. | Assess resources & roadmap with TSC
|
| 6 | Device | GPS | Missing | | Could a GPS DS serve to get the coordinates (lat/long - 2 floating point metrics) from the gateway? | Assess resources & roadmap with TSC
|
| 7 | Device | Profinet | Missing | | 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 | Assess resources & roadmap with TSC
|
| 8 | Device | DDS | Missing | | DDS is used in drilling for data messaging on critical items | Assess resources & roadmap with TSC
|
| 9 | CoreApplications | UI | No UI for configuration (Data ingestion, Data Export...) | | E&P Companies use systems with a provided UI. Relying on postman would not even get them started with tests. | Engage Core Applications WG and discuss with them how to handle this |
| 10 | SupportApplications | Rules Engine / Analytics | Need a light & easy CEP engine | | In order not to transfer all data to the cloud (an Offshore Rig generates 1TB per day) you need to move some of the logic to the edge | Engage Applications WG and discuss with them how to handle this |
| 11 | SupportCore | Logging | Need to be able to specify persistency policies for type of logs | | Different logs are required for liability purposes and can be assessed in case of incidents | Engage Core WG and discuss with them how to handle this |
| 12 | Applications | ExportClient Registration & Distribution | Missing mechanism for backfilling historical data. (perform an export job from start-timestamp to end-timestamp) | | Retrieve historical data back to the cloud | Engage Applications WG and discuss with them how to handle this |
| 13 | Applications | Export | Client Registration & Distribution | Missing Osisoft PI Export Capabilities | | Majority of E&P Companies use Osisoft PI as historian in the data center. Need to be able to export data to such system. | Vertical Solutions WG will develop this. Sync with Export Applications WG. |
| 14 | Applications | ExportClient Registration & Distribution | Missing InfluxDB Export Capabilities | | There is a need for a local optimized time series database in order to handle big amounts of data for long periods due to the disconnected nature of operations | Vertical Solutions WG will develop this. Sync with Export Applications WG. |