Do not synchronize description from OPC UA server into PI Tag
There are situations when customer prefers to use “description” in PI Tag attribute that is independent from item “description” provided by OPC UA Server.
Currently, during each synchronization, the OPC UA Connector synchronizes descriptor from OPC UA to PI Tag and overwrites desired “Descriptor” attribute provided by customer.
Although the solution would be to have desired description already on the OPC UA Server, in some situations (OPC Server managed by 3rd party) it is not possible. It would be good to have configurable parameter in OPC UA Connector, which disables synchronization of item description from OPC UA Server to PI tag.
Lucie Schaynova
shared this idea
-
Alessandro_B_enel
commented
This behaviour happens also with "step" attribute on the PI Adapter for OPC UA.
In particulart this happens every time Adapter is restarted or history recovery is performed.
The workaround is to have desired "description" already on the OPC UA server but in some situations (OPC UA server managed by 3rd party) this is not possible.
It would be good to have configurable parameter in OPC UA Adapter and Connector, which disables synchronization of "description" and "step" attributes from OPC UA server to PI tag. -
LalitKPokharana
commented
This is very critical functionality for many customers. OPC UA is the preferred way of connecting control system in coming days and industry 4.0 and other program like Open Process Automation have very high dependency with OPC UA . This is must to have idea where we need OSIsoft Support to enable functionality on choosing not to have auto update for Description and Eng-Unit.
-
paulfield
commented
Another use case is you connect to a Control System via OPC UA
The description in the control system is too generic e.g. the Control System has a connection to anther system and just has all the tags with the same description. Therefore you would want to have different description in PI. -
Julian Shearing
commented
We have a slightly different use case. It's fine to synchronise but we need the ability to turn it off after the connector has built the initial setup.
Our problem is when buying off the shelf equipment we have no control over how the vendors present the data. The built in OPC server to the equipment may not be configured in a way that is user friendly or even complete. We could of course resolve this by requesting customising of the source system but that leads to considerable increases in complexity and cost and some vendors are not prepared to entertain doing it! Therefore the ability to synchronise the initial build and then turn off the auto update and complete the build in PI would be really helpfull