Scott Robertson
My feedback
-
18 votes0 comments · OSIsoft Cloud Services » Assets & Metadata Rules · 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
·
-
89 votesScott Robertson
supported this idea
·
-
137 votesScott Robertson
supported this idea
·
-
83 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
·
-
8 votes0 comments · OSIsoft Cloud Services » Health & Manageability · Flag idea as inappropriate… · Admin →
We’re currently working on the ability to remotely monitor and manage the configuration of OSIsoft’s edge software.
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.