I would like to be able to configure an Edge Data Store to egress data to another Edge Data Store. Due to network limitations, I cannot egress data directly to OCS or PI Web API. Egressing to another Edge Data Store would allow me to configure an architecture where one EDS acts as a relay to the other before reaching a final egress endpoint like the PI Web API or OCS.16 votes
With the current supported version of EDS, egress from EDS can become ingress to EDS if both EDS instances are on same device.
We are considering this feedback as a potential feature sometime in future release of Edge Data Store. Meanwhile, please provide any additional information regarding this feedback.
Ability to transfer a subset of important data to PI/OCS and trigger transfer of less important data manually when connectivity of remote asset improves.
For example, send 1000 streams to PI or OCS continuously, and send remaining streams when ship asset comes to shore every couple of months.4 votes
We would like more information around this enhancement request, namely how you may classify important data streams. How would you identify which data streams need to be sent continuously? Please share more use cases with us so that we can review with those in mind.
Submitting on behalf of a customer concerned about meeting stringent security requirements. Kerberos is a staple in their security architecture and the would very much like to incorporate it here.2 votes
Implement transformation and scaling for OPC UA adaptor the way it exists for PI OPC DA interface tags. The user can modify egressed tags and the data will be transformed / scaled when egressed.2 votes
It would be great to have a REST API call available in EDS to get the current data egress state rather looking it up through the logfiles. The idea is to get information about when data was (successfully) egressed to OCS, AVEVA Data Hub or the PI WebAPI OMF Endpoint.1 vote
- Don't see your idea?