Notification is used to provide an interface for laser systems to deliver information about errors, warnings and notifications (see the use case in chapter 5.2), this specification reuses all concepts of the MessagesType as defined in OPC 40501-1: Machine Tools.

Furthermore, this specification reuses the 4:PrognosisType as defined in OPC 40501-1: Machine Tools to provide an interface for delivering information regarding upcoming maintenance activities.

Note: The goal of the interface is not, provide information to a higher-level system which tracks when which components were changed or when a service was executed.

To tailor the existing model to laser systems and the use case described in chapter 5.3, two subtypes, the LaserSystemMaintenancePrognosisType and the LaserSystemUtilityChangePrognosisType are derived in chapter 7.3.1 and 7.3.2.

Figure 9 gives an overview of NotificationType model as defined in OPC 40501-1 and how the LaserSystemMaintenancePrognosisType and LaserSystemUtilityChangePrognosisType definitions extend that model.

Figure 9 – Instance Example for the 4:NotificationType as used by the OPC UA information model for Laser System

The LaserSystemMaintenancePrognosisType provides an interface to quickly identify which kind of maintenance is to be performed on a laser system and when this maintenance is due

The LaserSystemMaintenancePrognosisType is formally defined in Table 28.

Table 28 – LaserSystemMaintenancePrognosisType Definition

Attribute	Value
BrowseName	LaserSystemMaintenancePrognosisType
IsAbstract	False
References	Node Class	BrowseName	DataType	TypeDefinition	Other
Subtype of the 4:MaintenancePrognosisType defined in OPC 40501-1 i.e. inheriting the InstanceDeclarations of that Node.
0:HasComponent	Variable	Description	0:LocalizedText	0:BaseDataVariableType	M, RO
0:HasProperty	Variable	Code	0:String	0:PropertyType	O, RO
Conformance Units
LaserSystems LaserSystemMaintenancePrognosisType Basic

The 4:PredictedTime as defined by the 4:PrognosisType is used to indicate the point in time the predicted user interaction will become necessary.

The 4:Activity as defined in the super type 4:MaintenancePrognosisType is to be used to indicate the name of the activity to be executed on the machine. Examples may be "General service A" or "Check up of the main coolant loop".

The Description indicates in a more elaborate (as compared to 4:UtilityName) and textual form what is to be done for the specific maintenance.

The Code may, for example, be used to link a maintenance activity to one specified in a service manual.

The LaserSystemUtilityChangePrognosisType is to be used as an interface indicating upcoming maintenance measures, in which utilities are to be exchanged. One such might be the change of a filter or the refilling of a water coolant system.

Note: The LaserSystemUtilityChangePrognosisType differs from the LaserSystemMaintenancePrognosisType as it always refers to one specific component which is to be serviced.

The LaserSystemUtilityChangePrognosisType is formally defined in Table 29.

Table 29 – LaserSystemUtilityChangePrognosisType Definition

Attribute	Value
BrowseName	LaserSystemUtilityChangePrognosisType
IsAbstract	False
References	Node Class	BrowseName	DataType	TypeDefinition	Other
Subtype of the 4:UtilityChangePrognosisType defined in OPC 40501-1 i.e. inheriting the InstanceDeclarations of that Node.
0:HasComponent	Variable	Description	0:LocalizedText	0:BaseDataVariableType	M, RO
0:HasProperty	Variable	Code	0:String	0:PropertyType	O, RO
Conformance Units
LaserSystems LaserSystemUtilityChangePrognosisType Basic

The 4:PredictedTime as defined the 4:PrognosisType is used to indicate the point in time the utility change will become necessary.

The 4:UtilityName as defined in the super type 4:UtilityChangePrognosisType is to be used to indicate the name of the utility to be exchanged. Examples may be "Air filter" or "Coolant water".

The Description indicates in a more elaborate (as compared to 4:UtilityName) and textual form what is to be done for the specific utility change.

The Code may, for example, be used to link a maintenance activity to one specified in a service manual.