Description
Osisoft PI is the most used historian in the Oil&Gas industry. EdgeX needs to be capable to export data to such a platform.
Requirements
- Authenticate the edge node through Basic Authentication
- Create new tags in PI Archive
- 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
This capability can be implemented by cloning the current EdgeX HTTPS REST export feature and modifying it accordingly to send messages in a format accepted by 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:
- PI Web API Endpoint (e.g. https://mypiwebapi.domain.com/piwebapi)
- PI Archive Name (e.g. mypiarchive)
- Export interval in milliseconds (e.g. 1000)
- Username (e.g. piwebapiuser)
- Password (e.g. piwebapipassword)
- Topic(s) Name
- 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 to PI Connector Relay with OMF
Code
To be updated.
Current status
Waiting for Go Export Client & Distribution to support HTTPS REST