7.26 VendingBaseAuditEventType definition

7.26.1 Overview

The VendingBaseAuditEventType provides base audit information to the audit collect. A more detailed overview is given in 6.3.4. It is formally defined in Table 86.

7.26.2 ObjectType definition

Table 85 - VendingBaseAuditEventType definition
Attribute Value
BrowseNameVendingBaseAuditEventType
IsAbstractTrue
References Node Class BrowseName DataType TypeDefinition Other
Subtype of the 0:BaseEventType
0:HasPropertyVariableInMaintenanceMode0:Boolean0:PropertyTypeM
0:HasPropertyVariableCategory0:String0:PropertyTypeM
0:HasPropertyVariableEVADTSStatusCode0:String0:PropertyTypeO
0:HasPropertyVariableEVADTSStatusIsActive0:Boolean0:PropertyTypeO
Conformance Units
UnattendedRetail MachineEngine
UnattendedRetail PaymentService
UnattendedRetail UI
UnattendedRetail PaymentDevice Coin
UnattendedRetail PaymentDevice Bill
UnattendedRetail PaymentDevice Cashless

The Properties defined in the BaseEventType shall be used in the following way:

EventId as defined in OPC 10000-5, uniquely identifying each Event.

EventType as defined in OPC 10000-5, identifying the type of Event.

SourceNode and SourceName as defined in OPC 10000-5, identifying the component of the Vending Machine generating the Event in the Server. This is helpful in environments where the OPC UA Server represents several components of a Vending Machine, e.g., payment service and machine engine. In addition, for Events specific to the payment device, the Object representing the payment device is used as SourceNode and SourceName in order to identify the payment device.

Time and ReceiveTime as defined in OPC 10000-5, indicating the time the Event occurred.

Message as defined in OPC 10000-5, containing a human-readable text of the Event.

Severity as defined in OPC 10000-5. For Events of VendingBaseAuditEventType the Severity shall be in the range of 201 to 400.

The optional Properties LocalTime, ConditionClassId, ConditionClassName, ConditionSubCassId and ConditionSubClassName should be omitted.

The mandatory InMaintenanceMode indicates whether the Event is generated while the component generating the Event is in maintenance mode. Set to true if in maintenance mode, false otherwise.

The mandatory Category defines the category of Event. Details of predefined categories are defined in 7.27.2, in Table 87.

The optional EVADTSStatusCode Variable contains a status code according to Annex C of EVA DTS. For the standardized Categories (see Table 87) it is defined whether this optional Property shall be provided.

The optional EVADTSStatusIsActive Variable shall only be provided in combination with EVADTSStatusCode and provides the information, if the status code has become active (True) or not (False).