B.5 Notifications

B.5.1 Overview

As stated in 18.1, Notifications Objects expose Notifications either as Objects or as Events. In B.5.2, an example is given, where Objects are used. In B.5.3, an example is given, where Events are used. In Figure 30 in 18.1 a small example is shown, where both approaches are combined.

B.5.2 Notifications as Objects

In Figure 36, an example is given, where Objects are used as Notifications. The ObjectType X:ManualActivityType provides a notification that some manual activity (like the change of a tool in a machine tool) is needed. It provides information about the activity and when it is expected to be done. Whenever the machine predicts the need for such an activity, such an Object is created on the Notifications Object. The 0:NodeVersion Property can be used to identify such new Objects as a Client. After the action has been executed, the Notification Object will be removed.

B.5.3 Notifications as Events

In Figure 37, an example is given, where Events are used as Notifications. In this case, the log of maintenance activities as defined by Asset Management Basics [8] is used. The EventType X:MaintenanceEventType implements the IMaintenanceEventType defined by Asset Management Basics. The X:MyMachineType provides a GeneratesEvent Reference from its Notifications Object to the X:MaintenanceEventType. For each new maintenance event, or if the status is changing, such an Event is generated.