Manage Subscriptions

When a discipline issues data and it becomes available to be consumed by other disciplines, those other disciplines need to know when the data is available. Notifications are used to indicate that updated data is available.

Not all disciplines are interested in changes to all attributes on all element types. In order to control the notifications received by a discipline, a subscription mechanism is available that works on a per-attribute level and is set up, team by team.

A set of information is available that describes the set of attributes, by element type, which teams may be interested in viewing. Database Views, and the Database View definitions are immediately available to use in AVEVA Engineering Configuration and Lexicon.

The same Database View can be used to subscribe to more than one team. Their does not remain an automatic persistence between Database Views and Teams. The subscribed Database Views for a team are retained, only to support Unsubscription. Changes to Database Views without re-creating the subscription do not reflect any changes in the subscriptions for teams. Further, only Attribute Columns are used to create subscriptions. Expression Columns are ignored for the purpose of subscription, in this context.