As per the title...UniInt supports white listing of output PI Points and I wonder how many of you actually use that feature?
Also, it would be interesting to know from OSIsoft how PI Connectors will support such a feature.
We have just a few output TAGs. We do not use the white listing feature.
In fact I think there are many points in security where I would make improvements befor I would take steps to whitelisting putput points.
I think for output points though it is more of a consideration than inputs from a PI Interface. White listing is like the last (but important) in a line of security measures, something that the PI Interface checks on the interface node itself rather than a setting in the PI Data Archive where multiple users tend to have more access than they need (despite anybody's best intentions with a PI Data Archive security model). I haven't come across many clients using this feature.
My thoughts were being largely driven by PI Connectors and their "minimal configuration" approach.
I have not use yet this new feature which is a good one for security reasons. Most of the time, companies don't want to write to their data source and this feature gives a new layer of security for 2 aspects: access & data integrity (by selecting a range of allowed values).
I will definitely use it in the future (a shame that OSIsoft did not communicate more regarding this feature).
For your information, have a look on this KB, there is a really interesting element regarding the future of the output in PI interfaces (and I assume PI Connectors): KB01295 - Risks of using the PI System as an input for a control system
Your comments helped in revision of KB01295 to clarify interface changes in progress now.
The plan is two fold. Read-only versions are being released as well as adding the output point white list security option to those interfaces with full read write versions.
Regarding connectors, the current design intentionally supports unidirectional data flow.
Thanks again for the constructive feedback.
No, but we do use the /NoOutput parameter on the UniInt interfaces to prevent people to create output tags and control the process controllers.
I have a minimal knowledge on output tags. As per KB01295, output points may be depreciated in future. Out of curiosity, do we really need a output to trigger a control system from PI?
As per my knowledge, control system receives feedback from its own points and correct the deviation.
An output point from PI to a control system (or other data sources --> do not limit data sources to control systems) is not necessary used as a trigger. It could be any data used to improve your process (this can help to take the good decision).
It could be also the result of a complex calculation or a simulation that you cannot perform in the data source.
Of course, we always need to take care about using outputs but there are plenty of mechanisms that can be put in place to avoid any mistake.
Agree. I've seen so many occasions where Lab Sample Results are sent to a control system to show the results on a graphic.
Retrieving data ...