Scott Robertson
My feedback
-
51 votesScott Robertson
supported this idea
·
-
8 votes0 comments · OSIsoft Cloud Services » Context & Data Mapping · Flag idea as inappropriate… · Admin →
We are extending PI to OCS to support users selecting AF elements and attributes to transfer as OCS assets. If you would like to discuss your use cases and requirements around this feature, please reach out!
Scott Robertson
supported this idea
·
-
8 votes
Please vote and comment on this enhancement request with you use cases for enabling/disabling TLS.
Scott Robertson
supported this idea
·
-
216 votesScott Robertson
supported this idea
·
-
38 votesScott Robertson
supported this idea
·
-
108 votesScott Robertson
supported this idea
·
-
4 votesScott Robertson
supported this idea
·
-
20 votes
Since OMF is just a specification that can be used to create data acquisition applications, it does not seem appropriate to add this feature here. However, I am curious, what are the roadblocks from introducing this rule into your application? OMF does not control what gets posted and what doesn’t, but an application could introduce a register for the last value sent and compare that to the current value before posting or ignoring the data.
Scott Robertson
supported this idea
·
-
29 votesScott Robertson
supported this idea
·
An error occurred while saving the comment An error occurred while saving the comment Scott Robertson
commented
I have a very similar use case. Potentially 1,000s of remote PI Servers will need to be kept in sync. A typical deployment pattern is to use Machine Learning to update analytics for real-time alerting. ML would update the central AF server, and the remote AF servers would check in periodically for their updates.
-
3 votesScott Robertson
supported this idea
·
-
6 votes
We’re currently working on the ability to remotely manage OSIsoft’s edge software.
If you have a few minutes, we’re actively collecting feedback to learn more about your remote asset scenarios and needs for remotely managing data collection at the edge.
If you would like to share your feedback with us, please complete the survey linked below. This survey will take less than 5 minutes to complete.
https://osisoft.az1.qualtrics.com/jfe/form/SV_26jOm9TdwfuXPHn
Scott Robertson
supported this idea
·
In response to Fabiano Batista, "Interesting use case. It looks like yo..."
I'm thinking that a scheduled update would be best. For the continuous use case, as in ML, I would say "Daily at 3 AM". For the Template updates, I would set a day and time when the update would occur, which could be days or weeks in advance. The ideal model, from a security standpoint, is an outbound connection from the remote sites, that checks periodically for updates, downloads the updates, and schedules locally for execution.