Yong The
My feedback
-
20 votesYong The
supported this idea
·
-
134 votes
An error occurred while saving the comment Yong The
supported this idea
·
-
39 votesEVALUATING · 10 comments · OSIsoft Cloud Services » Data Egress · Flag idea as inappropriate… · Admin →Yong The
supported this idea
·
An error occurred while saving the comment Yong The
commented
PI pushes data to OCS for DS/ML/AI purposes. Cloud applications create predictive outcomes which needs to be pushed back into future tags in the PI System for situational awareness.
-
289 votes8 comments · PI Vision » Manual Data Entry / PI Manual Logger · Flag idea as inappropriate… · Admin →
We are aware of the interest in this integration, but at this time we do not have plans to integrate PI Manual Logger with PI Vision. I have updated the status of this item to reflect this.
An error occurred while saving the comment Yong The
commented
The manual logger requires updating. Competitive products in the market today has elevated the user experience associated with manual data entry and the market expectations now surpasses that of the PI Manual Logger
Yong The
supported this idea
·
-
28 votes
We have started development on Community Management features and Stream data sharing in OSIsoft Cloud Services (OCS) to enable sharing of operational data across tenants.
As part of the Community creation workflow, we are working on a way that Communities are formed without exposing other customer accounts/tenants in the process.
Additionally, Namespaces can now be used to segregate customer data (if you’re providing a service to those customers), or the data can be stored in their own OCS tenant/account and then shared via Community data sharing functionality (when it becomes available).
An error occurred while saving the comment Yong The
commented
Have a namespace concept so that Pi can service multiple tenants without the risk of breaching data security between tenants. Also allowing data from tags associated with a namespace be archived and the tags reassigned to another namespace.
Yong The
supported this idea
·
-
16 votesYong The
supported this idea
·
If we were to truly support downtime management using Event Frames (which is perhaps one of the most commonly requested operations management tools), we need a delay threshold for end of event like a "true for" at the start, but to close the event. Otherwise, a false start in the downtime event will close the event inadvertently and a second downtime event logged when it is actually the same downtime. Therefore, unless we use custom logic, we will create errors in KPI's like MTBF and MTTR. These are also some of the most common KPI's in operations.