Non-event driven BODs

Non-event driven BODs are used for initial load of the applications that receive the BODs. With the situation prior to the introduction of non-event driven BODs, Sync BODs can be used to update applications. A disadvantage is that all subscribers will receive these BODs resulting in network load and unwanted Confirm BODs for subscribers that are already up-to-date.

A non-event driven BOD is a Show BOD that will be sent to the applications specified by their Logical ID. If a BOD should be sent to all subscribers, the Sync BOD could be used.

Note that if a new subscriber is updated with initial load, it can happen that at the same time a Sync BOD is published. The Sync BOD can contain an update on a not yet received instance. This will be processed as an Add.