Logbook events are fired by the machine for the documentation of relevant changes in the machine configuration/status. The LogbookEventType is formally defined in Table 12.

Table 12 – LogbookEventType Definiton

Attribute

Value

BrowseName

LogbookEventType

IsAbstract

True

References

Node Class

BrowseName

DataType

TypeDefinition

Other

Subtype of 0:BaseEventType defined in OPC UA Part 5

0:HasComponent

Object

User

UserType

M

0:HasProperty

Variable

EventOriginator

EventOriginatorEnumeration

0:PropertyType

M

0:HasProperty

Variable

JobCycleCounter

0:UInt64

0:PropertyType

O

0:HasSubtype

ObjectType

ParameterChangeLogType

Defined in 9.5

0:HasSubtype

ObjectType

UserLogType

Defined in 9.6

0:HasSubtype

ObjectType

RemoteAccessLogType

Defined in 9.7

0:HasSubtype

ObjectType

SequenceChangeLogType

Defined in 9.8

0:HasSubtype

ObjectType

MachineModeChangeLogType

Defined in 9.9

0:HasSubtype

ObjectType

ProductionStatusChangeLogType

Defined in 9.10

0:HasSubtype

ObjectType

ProductionDatasetChangeLogType

Defined in 9.11

0:HasSubtype

ObjectType

ProductionDatasetFrozenLogType

Defined in 9.12

0:HasSubtype

ObjectType

StandstillReasonLogType

Defined in 9.13

0:HasSubtype

ObjectType

MessageLogType

Defined in 9.14

0:HasSubtype

ObjectType

UserFeedbackLogType

Defined in 9.15

The LogbookEventType is abstract. There will be no instances of a LogbookEventType itself, but there will be instances of its subtypes which provide detailed information.

The EventSource is the root node of the interface (e.g. instance of IMM_MES_InterfaceType for OPC 40077).

NOTE: The EventSource, Time and a Message are already included in the BaseEventType of OPC UA.

There shall be a buffer to be accessible via the OPC UA service history read (even when the machine has been switched off in the meantime). The minimum size is 100 LogbookEvents to be stored in a (persistent) ring buffer containing the recent 100 events (over all LogbookEvents).