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

Compare with Current View Page History

« Previous Version 20 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
1DeviceOPC UAMissing

HIGH

New installations of SCADA systems are typically expected to be compliant with the OPC UA standard, this standard is good for new facilitiesIntegrate Samsung DS for OPC UA
2DeviceOPC DAMissing

HIGH

E&P Companies are still massively using OPC DA in legacy systems and - in limited cases - in new installations as wellAssess resources & roadmap with TSC
3DeviceModbusSeems 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 dutiesEngage Device WG and discuss with them how to handle this
4DeviceZigbeeMissing

LOW

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

LOW

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

MEDIUM

Could a GPS DS serve to get the coordinates (lat/long - 2 floating point metrics) from the gateway?Assess resources & roadmap with TSC
7DeviceProfinetMissing

LOW

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 EdgeXAssess resources & roadmap with TSC
8DeviceDDSMissing

MEDIUM

DDS is used in drilling for data messaging on critical itemsAssess resources & roadmap with TSC
9ApplicationsUINo UI for configuration (Data ingestion, Data Export...)

HIGH

E&P Companies use systems with a provided UI. Relying on postman would not even get them started with tests.Engage Applications WG and discuss with them how to handle this
10ApplicationsRules Engine / AnalyticsNeed a light & easy CEP engine

MEDIUM

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 edgeEngage Applications WG and discuss with them how to handle this
11CoreLoggingNeed 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 incidentsEngage Core WG and discuss with them how to handle this
12ApplicationsExportMissing mechanism for backfilling historical data. (perform an export job from start-timestamp to end-timestamp)

MEDIUM

Retrieve historical data back to the cloudEngage Applications WG and discuss with them how to handle this
13ApplicationsExportMissing Osisoft PI Export Capabilities

HIGH

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 Applications WG.
14ApplicationsExportMissing InfluxDB Export Capabilities

HIGH

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 operationsVertical Solutions WG will develop this. Sync with Applications WG.


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