...
Osisoft PI is the most used historian in the Oil&Gas industry. EdgeX needs to be capable to ingest export data into to such a platform.
Requirements
- Authenticate the edge node through standard OSI PI premises ( Basic Authentication at minimum)
- Create new tags in PI Archive
- Edit existing tags in PI Archive
- High throughput data ingestion up to 10k events/second
- Ability to send data to multiple PI Nodes concurrently (up to 3)Export throughput up to 1,000 events/second from each EdgeX node
- Local buffering and retry mechanism with resilience to network downtime
- Local logging of error messages & events through EdgeX Log service
Design
Two approaches are possible in order The easiest way to implement this export service:
...
capability is to clone the current EdgeX REST export
...
feature and modify it accordingly to send messages to PI Web API
...
. This is an approach that has been adopted by other IIoT platforms as well.
- Step 1 - Configuration
- Parameters that define the configuration of the export service are:
- TBD
- TBD
- Parameters that define the configuration of the export service are:
- Step 2 - Initialization
- The following steps need to be executed after the client registration through export client:
- TBD
- TBD
- The following steps need to be executed after the client registration through export client:
- Step 3 - Data Export
- TBD
Possible improvements for a later version:
- Support Kerberos authentication
- Ability to send data to multiple PI Nodes concurrently (up to 3)
- High throughput up to 100,000 events/second from each EdgeX node by using an ad-hoc OMF connector to send messages
...
Code
To be updated.
Current status
Waiting for Go Export Client & Distribution to be finalized by the appointed group before making the contributionsupport HTTPS REST