Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

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

AreaMicroserviceGaps IdentifiedCriticalityWhy ImportantRecommended Actions
DeviceOPC UAMissing

HIGH

New installations of SCADA systems are typically expected to be compliant with the OPC UA standard
DeviceOPC DAMissing

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
DeviceModbusSeems 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
DeviceZigbeeMissing

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.
DeviceLoRaMissing

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.
DeviceGPSMissing

MEDIUM

Could a GPS DS serve to get the coordinates (lat/long - 2 floating point metrics) from the gateway?
DeviceProfinetMissing

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
DeviceDDSMissing

MEDIUM

DDS is used in drilling for data messaging on critical items
CoreData



CoreMetadata



CoreCommand



SupportRules Engine / Analytics



SupportScheduling



SupportAlerts & Notifications



SupportLoggingNeed 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
ExportClient Registration & DistributionMissing mechanism for backfilling historical data. (perform an export job from start-timestamp to end-timestamp).


SystemSystem ManagementConnection loss handling: changes made while offline will be cached and sent when connection is re-established
Edges could be often disconnected
SecuritySecurityNeed to lock down access to EdgeX 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

  • No labels