I have the following scenario and I am not sure that Part 3 allows it.

Due to the size of our system I have introduced the concept of object activation. Basically, objects are activated (connected?) only if they are being monitored. As a consequence, only activated objects generate certain types of events. My primary concern with this approach is the server object. I do not want to activate every object in the system just because a client creates a subsciption to the Server object. There are simply not enough resources to do that.

As an example lets take a state machine object that has no native equivalent in the source device. The UA server is supposed to generate an event whenever a transition in the state machine occurs. However, in my system the state machine would only get activated if it was added to a subscription (directly or indirectly via a HasNotifier chain). That means that the Server object would not get any state change events for the state machine unless the state machine was being monitored as well.

Randy suggested that "a UA server is not expected to produce events if the connection to the system is down for some reason (i.e. the system is offline). Your use case is a variation on that theme."