Search

200 result(s) for Event

• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  2.1.15 Event
  Event generic term used to describe an occurrence of some significance within a system or system component
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  2.1.9 Condition
  Condition generic term that is an extension to an Event Note 1 to entry: A Condition represents the conditions of a system or one of its components and always exists
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  2.1.12 DataSet
  list of named data values Note 1 to entry: A DataSet typically consists of Event fields or Variable values
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  2.1.16 EventNotifier
  signifies that a Client may subscribe to that particular Node to receive Notifications of Event occurrences
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  4.3 Design goals
  major feature of all OPC servers is the ability to publish data and Event Notifications . OPC UA provides mechanisms for Clients to quickly detect and recover from communication failures associated
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  4.4.1.3 Auditing
  located and examined. OPC UA also provides the capability for Servers to generate Event Notifications that report auditable Events to Clients capable of processing and logging them. OPC UA defines ... security audit parameters that can be included in audit log entries and in audit Event Notifications . OPC 10000-5 defines the data types for these parameters. Not all Servers
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  6.9 MonitoredItem Service Set
  status; Attributes for a change in value; and EventNotifiers for newly generated Alarm and Event reports. Each MonitoredItem identifies the item to monitor and the Subscription to use to periodically
• OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model
  4.14.1 General
  require that they be available. OPC UA provides the capability for Servers to generate Event Notifications that report auditable Events to Client s capable of processing and logging them
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.1.8 EventType
  EventType ObjectType Node that represents the type definition of an Event
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.7.1 General
  General The Event Model defines a general purpose eventing system that can be used in many diverse vertical markets. Events represent specific transient occurrences. System configuration changes and system errors ... examples of Events . Event Notifications report the occurrence of an Event . Events defined in this document are not directly visible in the OPC UA AddressSpace . Objects and Views
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.7.2 EventTypes
  EventTypes Each Event is of a specific EventType . A Server may support many types. This part defines the BaseEventType that all other EventTypes derive from. It is expected that other ... this document are specified as abstract and therefore never instantiated in the AddressSpace . Event occurrences of those EventTypes are only exposed via a Subscription . Components of an EventType defined with
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.7.3 Event Categorization
  Event Categorization Events can be categorised by creating new EventTypes which are subtypes of existing EventTypes but do not extend an existing type. They are used only to identify ... event as being of the new EventType . For example, the EventType DeviceFailureEventType could be subtyped into TransmitterFailureEventType and ComputerFailureEventType. These new subtypes would not add new Properties or change
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.4 BrowseName
  BrowseNames passed in Service requests as case insensitive. Examples are the TranslateBrowsePathsToNodeIds Service or Event filter. If a Server accepts a case insensitive BrowseName it needs to ensure that
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.2 ObjectType NodeClass
  instances of the ObjectType may generate. These Objects may be the source of an Event of the specified type or one of its subtypes. Servers should make GeneratesEvent References bidirectional ... might not be used as Objects to which Clients subscribe to get the corresponding Event notifications. GeneratesEvent References are optional, i.e. Objects may generate Events of an EventType that
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.2 Variable NodeClass
  Server is running, the SemanticChange flag shall be set for it. Servers that support Event Subscriptions shall generate a SemanticChangeEvent whenever a Property with SemanticChange flag set changes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.5 VariableType NodeClass
  GeneratesEvent References identify that Variables of the VariableType may be the source of an Event of the specified EventType or one of its subtypes. Servers should make GeneratesEvent References bidirectional
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.7.1 Method NodeClass
  Object . ModellingRules are defined in 6.4.4 . GeneratesEvent References identify that Methods may generate an Event of the specified EventType or one of its subtypes for every call of the Method ... Server may generate one Event for each referenced EventType when a Method is successfully called. AlwaysGeneratesEvent References identify that Methods will generate an Event of the specified EventType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.17 HasEventSource
  subtype of HierarchicalReferences . The semantic of this ReferenceType is to relate event sources in a hierarchical, non-looping organization. This ReferenceType and any subtypes are intended to be used ... discovery of Event generation in a Server . They are not required to be present for a Server to generate an Event from its source (causing the Event ) to its notifying
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.18 HasNotifier
  other notifier Object Nodes . The ReferenceType is used to establish a hierarchical organization of event notifying Objects . It is a subtype of the HasEventSource ReferenceType defined in 7.16 . The TargetNode ... this ReferenceType shall be Objects that are a source of Event Subscriptions . If the TargetNode of a Reference of this type generates an Event , then this Event shall also
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.55 PermissionType
  Objects or Views (for deleting historical events). ReceiveEvents 11 A Client only receives an Event if this bit is set on the Node identified by the EventTypeId field
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.2 BaseEventType
  BaseEventType The BaseEventType defines all general characteristics of an Event . All other EventTypes derive from it. There is no other semantic associated with this type
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.3 SystemEventType
  SystemEventType SystemEvents are Events of SystemEventType that are generated as a result of some Event that occurs within the Server or by a system that the Server is representing
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.5 AuditEventType
  source and the user and Client session as the initiators of the Event . Figure 44 illustrates the defined behaviour of an OPC UA Server in response to an auditable action ... system in the process but it is the Server 's responsibility to provide the Event to any interested Clients . Clients are free to subscribe to Events from the Server
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.30 DeviceFailureEventType
  DeviceFailureEventType A DeviceFailureEvent is an Event of DeviceFailureEventType that indicates a failure in a device of the underlying system
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.31 SystemStatusChangeEventType
  SystemStatusChangeEventType A SystemStatusChangeEvent is an Event of SystemStatusChangeEventType that indicates a status change in a system. For example, if the status indicates an underlying system is not running, then
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.32.3 Views
  Node was also contained in a View "A", there would be one Event having the AddressSpace as context and another having the View "A" as context ... receive duplicates of changes then it shall use the filter mechanisms of the Event Subscription to filter only for the default View and suppress the ModelChangeEvents having other Views
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.32.4 Event compression
  Event compression An implementation is not required to issue an Event for every update as it occurs. An OPC UA Server may be capable of grouping a series of transactions ... series, to cover all of the changes. This is referred to as Event compression . A change in the NodeVersion and the ViewVersion may thus reflect a group of changes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  9.32.6 GeneralModelChangeEventType
  Node is a Variable or Object , then the TypeDefinitionNode is also present. To allow Event compression, a GeneralModelChangeEvent contains an array of changes
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.3.2 Parameters
  include a timestamp. If the HistoryReadDetails is EVENTS: The NodeId of the Node whose Event history is to be read. If the Node does not support the requested access
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.5.1 Description
  Several request parameters indicate how the Server is to update the historical value or Event . Valid actions are Insert, Replace or Delete
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.1.1 Overview
  filter defined in this document (see 7.22.3 ) is used to determine if an Event received from the Node is sent to the Client . The filter also allows selecting fields ... EventType that will be contained in the Event such as EventId , EventType , SourceNode , Time and Description . OPC 10000-3 describes the Event model and the base EventTypes . The Properties
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.1.5 Queue parameters
  Server when monitoring Events . In this case, the Server is responsible for the Event buffer. If Events are lost, an Event of the type EventQueueOverflowEventType is placed in the queue ... This Event is generated when the first Event is discarded on a MonitoredItem subscribing for Events. It is put into the Queue of the MonitoredItem in addition to the size
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.1.6 Triggering model
  wire by configuring some items to sample frequently but only report when some other Event happens. The following triggering behaviours are specified. If the monitoring mode of the triggering item
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.2.2 Parameters
  TimestampsToReturn enumeration is defined in 7.39 . When monitoring Events , this applies only to Event fields that are of type DataValue . itemsToCreate [] MonitoredItem CreateRequest A list of MonitoredItems to be created
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.3.2 Parameters
  TimestampsToReturn enumeration is defined in 7.39 . When monitoring Events , this applies only to Event fields that are of type DataValue . itemsToModify [] MonitoredItemModifyRequest The list of MonitoredItems to modify. This structure
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.14.1.2 State table
  identified by "()" after their name. They are described in 5.14.1.4 . When an Event is received, the first transition for the current state is located and the transitions ... searched sequentially for the first transition that meets the Event or conditions criteria. If none are found, the Event is ignored. Actions are described by functions and state Variable manipulations
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.14.1.3 State variables and parameters
  this state Variable from FALSE to TRUE creates the "New Notification Queued" Event in the state table. PublishingEnabled The parameter that requests publishing to be enabled or disabled
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.5.3 General audit Events
  Server that maintains an audit log shall provide the audit log entries via Event Messages . The AuditEventType and its sub-types are defined in OPC 10000-3 . An audit Event
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.5.5 Auditing for SecureChannel Service Set
  correct audit record Id to be provided. The OpenSecureChannel Service shall generate an audit Event of type AuditOpenSecureChannelEventType or a subtype of it for the requestType ISSUE . Audit Events ... only created if the renew fails. The CloseSecureChannel service shall generate an audit Event of type AuditChannelEventType or a subtype of it. Both of these Event types are subtypes
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.5.6 Auditing for Session Service Set
  Events for both successful and failed Service invocations. These Services shall generate an audit Event of type AuditSessionEventType or a subtype of it. In particular, they shall generate the base
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.5.7 Auditing for NodeManagement Service Set
  Events for both successful and failed Service invocations. These Services shall generate an audit Event of type AuditNodeManagementEventType or subtypes of it. See OPC 10000-5 for the detailed assignment
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.5.8 Auditing for Attribute Service Set
  Events for both successful and failed Service invocations. These Services shall generate an audit Event of type AuditUpdateEventType or subtypes of it. In particular, the Write Service shall generate ... audit event of type AuditWriteUpdateEventType or a subtype of it if the Write modifies the state of a system (e.g. operator changed a setpoint). Write operations that do not modify
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.5.9 Auditing for Method Service Set
  acknowledge, batch sequencing or other system changes). These method calls shall generate an audit Event of type AuditUpdateMethodEventType or subtypes of it. Methods that do not modify the AddressSpace , write
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.5.10 Auditing for View, Query, MonitoredItem and Subscription Service Set
  Subscription Service Set . In general, these services will not generate audit entries or audit Event Messages . The TransferSubscriptions Service shall generate an audit Event of type AuditSessionEventType or subtypes
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.3 FilterOperator
  copied when it is converted to and from a UInt16 or Int16 value. Since Event fields can have a StatusCode instead of the expected DataType , a StatusCode can only
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.21 MonitoringParameters
  statusCode is set in the new value. The following values have special meaning for event monitored items: Value Meaning 0 the Server returns the default queue size for Event Notifications ... revisedQueueSize for event monitored items. 1 the Server returns the minimum queue size the Server requires for Event Notifications as revisedQueueSize . MaxUInt32 the Server returns the maximum queue size that
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.22.3 EventFilter
  EventFilter The EventFilter provides for the filtering and content selection of Event Subscriptions . If an Event Notification conforms to the filter defined by the where parameter of the EventFilter , then ... Notification is sent to the Client . Each Event Notification shall include the fields defined by the selectClauses parameter of the EventFilter . The defined EventType s are specified
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.25.1 Overview
  NotificationData parameterTypeIds Symbolic Id Description DataChange Notification data parameter used for data change Notifications . Event Notification data parameter used for Event Notifications . StatusChange Notification data parameter used for Subscription status
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.25.3 EventNotificationList parameter
  EventNotificationList parameter Table 162 defines the NotificationData parameter used for Event notifications. The EventNotificationList defines a table structure that is used to return Event fields to a Client Subscription ... more fields. The selection and order of the fields returned for each Event is identical to the selected parameter of the EventFilter . Table 162 - EventNotificationList Name Type Description EventNotificationList structure
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.32 RequestHeader
  auditEntryId is included in the AuditEvent to allow human readers to correlate an Event with the initiating action. More details of the Audit mechanisms are defined
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.2 ServerCapabilitiesType
  maximum length of a one or multidimensional array supported by Variables, Method arguments and Event fields of the Server . In a multidimensional array it indicates the overall length. For example ... Server might further restrict the length for individual Variables, Method arguments or Event fields without notice to the client. Servers may use the Property MaxArrayLength defined
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.2 BaseEventType
  Address Space Events EventId is generated by the Server to uniquely identify a particular Event Notification . The Server is responsible to ensure that each Event has its unique EventId ... StatusCode for the EventId indicating an error. EventType describes the specific type of Event . The EventType shall always be returned as value and the Server is not allowed to return
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.3 AuditEventType
  generic audit Client to collect all relevant information using an EventFilter consisting of Event fields from the core AuditEventTypes . ActionTimeStamp identifies the time the user initiated the action that resulted ... TRUE) or not (set Status to FALSE). ServerId uniquely identifies the Server generating the Event . It identifies the Server uniquely even in a server-controlled transparent redundancy scenario where several
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.5 AuditChannelEventType
  this type shall be "SecureChannel/" and the Service that generates the Event (e.g. SecureChannel/ OpenSecureChannel or SecureChannel/ CloseSecureChannel ). If the ClientUserId is not available for a CloseSecureChannel call
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.6 AuditOpenSecureChannelEventType
  Properties defined for this EventType reflect parameters of the Service call that triggers the Event . ClientCertificate is the clientCertificate parameter of the OpenSecureChannel Service call. ClientCertificateThumbprint is a thumbprint ... parameter of the OpenSecureChannel Service call. CertificateErrorEventId is the EventId of the corresponding AuditCertificateEventType Event used to report a certificate error
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.7 AuditSessionEventType
  inherits all Properties of the AuditSecurityEventType . Their semantic is defined in 6.4.4 . If the Event is generated by a TransferSubscriptions Service call, the SourceNode Property shall be assigned ... type shall be "Session/" and the Service or cause that generates the Event (e.g. CreateSession , ActivateSession or CloseSession ). The SessionId shall contain the SessionId of the session that
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.8 AuditCreateSessionEventType
  Properties defined for this EventType reflect parameters of the Service call that triggers the Event . SecureChannelId shall uniquely identify the SecureChannel. The application shall use the same identifier
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.9 AuditUrlMismatchEventType
  Properties defined for this EventType reflect parameters of the Service call that triggers the Event . EndpointUrl is the endpointUrl parameter of the CreateSession Service call
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.10 AuditActivateSessionEventType
  Properties defined for this EventType reflect parameters of the Service call that triggers the Event . ClientSoftwareCertificates is the clientSoftwareCertificates parameter of the ActivateSession Service call. UserIdentityToken reflects the userIdentityToken parameter
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.11 AuditCancelEventType
  Properties defined for this EventType reflect parameters of the Service call that triggers the Event . RequestHandle is the requestHandle parameter of the Cancel Service call
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.19 AuditNodeManagementEventType
  this type shall be "NodeManagement/" and the Service that generates the Event (e.g. AddNodes , AddReferences , DeleteNodes , DeleteReferences
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.20 AuditAddNodesEventType
  Properties defined for this EventType reflect parameters of the Service call that triggers the Event . NodesToAdd is the NodesToAdd parameter of the AddNodes Service call
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.21 AuditDeleteNodesEventType
  Properties defined for this EventType reflect parameters of the Service call that triggers the Event . NodesToDelete is the nodesToDelete parameter of the DeleteNodes Service call
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.22 AuditAddReferencesEventType
  Properties defined for this EventType reflect parameters of the Service call that triggers the Event . ReferencesToAdd is the referencesToAdd parameter of the AddReferences Service call
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.23 AuditDeleteReferencesEventType
  Properties defined for this EventType reflect parameters of the Service call that triggers the Event . ReferencesToDelete is the referencesToDelete parameter of the DeleteReferences Service call
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.15 SubscriptionDiagnosticsDataType
  DataChangeNotification Structure sent in a Publish response. eventNotificationsCount UInt32 The number of Event Notifications sent by the subscription. An Event Notification is one event entry in an EventNotificationList sent ... UInt32 The number of times a monitored item in the subscription has generated an Event of type EventQueueOverflowEventType. Its representation in the AddressSpace is defined in Table 253 . Table
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  3.1.16 Refresh
  Refresh act of providing an update to an Event Subscription that provides all Alarms which are considered to be Retained Note 1 to entry: This concept is further defined
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  4.2 Conditions
  Condition (the trunk) has a NULL BranchId. Server s can generate separate Event Notifications for each branch. When the state represented by a ConditionBranch does not need further attention ... final Event Notification for this branch will have the Retain Property set to False. Clause 5.5 provides more information and use cases. Maintaining previous states and therefore the support
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  4.5 Condition state synchronization
  general replay capability since the Server is not required to maintain an Event history. Clients request a Refresh by calling the ConditionRefresh Method . The Server will respond with a RefreshStartEventType ... Event . This Event is followed by the Retained Conditions . The Server may also send new Event Notifications interspersed with the Refresh related Event Notifications . After the Server is done with
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  4.6 Severity, quality, and comment
  Quality are important elements of Conditions and any change to them will cause Event Notification s. The severity of a Condition is inherited from the base Event model defined
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  4.10 Condition instances in the AddressSpace
  node may not always correspond with the value that appears in the Event. The value could be more recent than the value in the Event . While exposing Condition instances
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  4.11 Alarm and Condition auditing
  state of the system, for example, an Acknowledge Method call would generate an AuditConditionAcknowledgeEventType Event . The standard AuditEventTypes defined in 10000-5 already include the fields required for Condition related ... Server . For example, the Disable Method has an AlwaysGeneratesEvent Reference to an AuditConditionEnableEventType . An Event of this type shall be generated for every invocation of the Method if audit events
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.1 General
  General The Alarm and Condition model extends the OPC UA base Event model by defining various Event Types based on the BaseEventType . All of the Event Types defined in this
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.2 Two-state state machines
  Type , Servers shall not allow these Properties to be selected in the Event filter for a MonitoredItem. The TrueState Property and FalseState Property shall only exist on InstanceDeclarations . See Figure
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.5.1 General
  General The Condition model extends the Event model by defining the ConditionType . The ConditionType introduces the concept of states differentiating it from the base Event model. Unlike the BaseEventType , Conditions
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.5.2 ConditionType
  thus listed (to update the modelling rule) . ConditionName identifies the Condition instance that the Event originated from. It can be used together with the SourceName in a user display ... name element of the BrowseName of the ConditionType . BranchId is NULL for all Event Notifications that relate to the current state of the Condition instance. If BranchId is not NULL
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.5.3 Condition and branch instances
  Condition instance. If one or more Variable values change the Server generates an Event with a unique EventId . If a Client calls Refresh the Server will report the current state ... Condition instance by re-sending the last Event (i.e. the same EventId and Time is sent). A ConditionBranch is a copy of the Condition instance state that can change independently
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.5.4 Disable Method
  ConformanceUnits A & C Enable If Auditing is supported, this Method shall generate an Event of AuditConditionEnableEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.5.5 Enable Method
  ConformanceUnits A & C Enable If Auditing is supported, this Method shall generate an Event of AuditConditionEnableEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.5.6 AddComment Method
  Table 15 Table 15 - AddComment arguments Argument Description EventId EventId identifying a particular Event Notification where a state was reported for a Condition . Comment A localized text that shall ... comment or is invalid in some other manner. Comments Comments are added to Event occurrences identified via an EventId . EventIds where the related EventType is not a ConditionType (or subtype
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.5.7 ConditionRefresh Method
  code Bad_NothingToDo The ConditionRefresh Method was called on a SubscriptionId that has no event MonitoredItems. Bad_RefreshInProgress See Table 137 for the description of this result code Bad_UserAccessDenied ... Subscription is accepted the Server will react as follows: The Server issues an event of RefreshStartEventType (defined in 5.11.2 ) marking the start of Refresh. A copy of the instance
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.5.8 ConditionRefresh2 Method
  defined in 5.11.2 ) marking the start of Refresh. The RefreshStartEvent is queued into the Event stream for the Notifier MonitoredItem in the Subscription . The Server issues Event Notifications ... maintaining the same values as originally sent, but other Servers would only regenerate the Event . The regenerated Event might contain some updated Property/ Variable values. For example, if the Alarm
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.6.3 Respond Method
  ConformanceUnits A & C Dialog If Auditing is supported, this Method shall generate an Event of AuditConditionRespondEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.6.4 Respond2 Method
  ConformanceUnits A & C Dialog2 If Auditing is supported, this Method shall generate an Event of AuditConditionRespondEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.7.3 Acknowledge Method
  Acknowledge Method The Acknowledge Method is used to acknowledge an Event Notification for a Condition instance state where AckedState is False. Normally, the NodeId of the object instance is passed ... Table 34 Table 34 - Acknowledge parameters Argument Description EventId EventId identifying a particular Event Notification . Only Event Notifications where AckedState/Id was False can be acknowledged. Comment A localized text that
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.7.4 Confirm Method
  Confirm Method The Confirm Method is used to confirm an Event Notifications for a Condition instance state where ConfirmedState is False. Normally, the NodeId of the object instance is passed ... Table 37 Table 37 - Confirm Method parameters Argument Description EventId EventId identifying a particular Event Notification . Only Event Notifications where the Id property of the ConfirmedState is False
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.5 Reset Method
  Latched State If Auditing is supported, this Method shall generate an Event of AuditConditionResetEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.6 Reset2 Method
  Latched State If Auditing is supported, this Method shall generate an Event of AuditConditionResetEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.7 Silence Method
  ConformanceUnits A & C Silencing If Auditing is supported, this Method shall generate an Event of AuditConditionSilenceEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.8 Suppress Method
  Suppression by Operator If Auditing is supported, this Method shall generate an Event of AuditConditionSuppressionEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.9 Suppress2 Method
  Suppression2 by Operator If Auditing is supported, this Method shall generate an Event of AuditConditionSuppressionEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.11 Unsuppress2 Method
  Suppression2 by Operator If Auditing is supported, this Method shall generate an Event of AuditConditionSuppressionEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.12 RemoveFromService Method
  ConformanceUnits A & C OutOfService If Auditing is supported, this Method shall generate an Event of AuditConditionOutOfServiceEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.13 RemoveFromService2 Method
  ConformanceUnits A & C OutOfService2 If Auditing is supported, this Method shall generate an Event of AuditConditionOutOfServiceEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.14 PlaceInService Method
  ConformanceUnits A & C OutOfService If Auditing is supported, this Method shall generate an Event of AuditConditionOutOfServiceEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.15 PlaceInService2 Method
  ConformanceUnits A & C OutOfService2 If Auditing is supported, this Method shall generate an Event of AuditConditionOutOfServiceEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.17.2 Unshelve Method
  ConformanceUnits A & C Shelving If Auditing is supported, this Method shall generate an Event of AuditConditionShelvingEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.17.3 Unshelve2 Method
  ConformanceUnits A & C Shelving2 If Auditing is supported, this Method shall generate an Event of AuditConditionShelvingEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.17.4 TimedShelve Method
  ConformanceUnits A & C Shelving If Auditing is supported, this Method shall generate an Event of AuditConditionShelvingEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.17.5 TimedShelve2 Method
  ConformanceUnits A & C Shelving2 If Auditing is supported, this Method shall generate an Event of AuditConditionShelvingEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.17.6 OneShotShelve Method
  ConformanceUnits A & C Shelving If Auditing is supported, this Method shall generate an Event of AuditConditionShelvingEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.8.17.7 OneShotShelve2 Method
  ConformanceUnits A & C Shelving2 If Auditing is supported, this Method shall generate an Event of AuditConditionShelvingEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.10.2 AuditConditionEventType
  shall be "Method/" and the name of the Service that generated the Event (e.g. Disable , Enable , Acknowledge, etc. ). This EventType can be further customized to reflect particular Condition
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.10.3 AuditConditionEnableEventType
  Auditing The SourceName shall indicate Method/Enable or Method/Disable. If the audit Event is not the result of a Method call, but due to an internal action of the Server
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.10.6 AuditConditionAcknowledgeEventType
  Acknowledge Auditing The ConditionEventId field shall contain the id of the Event that was acknowledged. The Comment contains the actual comment that was added, it may be a blank comment
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.10.7 AuditConditionConfirmEventType
  Confirm Auditing The ConditionEventId field shall contain the id of the Event that was confirmed. The Comment contains the actual comment that was added, it may be a blank comment
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.10.9 AuditConditionSuppressionEventType
  inheriting the InstanceDeclarations of that Node. ConformanceUnits A & C Suppression Auditing This Event indicates an Alarm suppression operation. An audit Event of this type shall be generated, if audit
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.10.12 AuditConditionOutOfServiceEventType
  inheriting the InstanceDeclarations of that Node. ConformanceUnits A & C OutOfService Auditing An audit Event of this type shall be generated if audit Events are supported
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.11.4 RefreshRequiredEventType
  ConformanceUnits A & C Refresh A & C Refresh2 When a Server detects an Event queue overflow, it shall track if any Condition Event s have been lost ... Condition Event s were lost, it shall issue a RefreshRequiredEventType Event to the Client after the Event queue is no longer in an overflow state
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.14.2 Communication problems
  with the underlying system is: If communication fails to the underlying system, For any Event field related information that is exposed in the address space, the Value/ StatusCode obtained when ... reading the Event fields that are associated with the communication failure shall have a value of NULL and a StatusCode of Bad_CommunicationError. For Subscription s that contain Conditions
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.14.3 Redundant A & C servers
  Server the following behaviour is expected: The EventId is used to uniquely identify an Event . For an Event that is in each of the redundant Servers , it shall be identical ... This applies to all standard Event s, Alarms and Conditions . This may be accomplished by sharing of information between redundant Server (such as actual Event
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  6.1 General
  more areas; the Client can subscribe to specific areas to limit the Event Notifications sent by the Server . Additional examples can be found in Clause
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  6.2 EventNotifier and source hierarchy
  source hierarchy HasNotifier and HasEventSource References are used to expose the hierarchical organization of Event notifying Objects and ConditionSources . An Event notifying Object represents typically an area of Operator responsibility ... type of HasEventSource . I.e. the target Node of a HasNotifier Reference (an Event notifying Object ) may also be a ConditionSource . The HasEventSource Reference is used if the target Node
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  6.4 Conditions in InstanceDeclarations
  HasEventSource Reference in the context of InstanceDeclarations and TypeDefinition Nodes has no effect for Event generation. Figure 28 - Use of HasCondition in an InstanceDeclaration
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  9.4 Reset Method
  Alarm Metrics If Auditing is supported, this Method shall generate an Event of AuditConditionMethodEventType for all invocations of the Method
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  B.1.1 Overview
  B.1.1 Overview The following examples show the Event flow for typical Alarm situations. The tables list the value of state Variables for each Event Notification
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  B.1.2 Server maintains current state only
  initial state of the Condition . This state will not be reported by an Event
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  B.1.3 Server maintains previous states
  initial state of the Condition . This state will not be reported by an Event . b) If the current state of the Condition is acknowledged then the Acked flag ... state is reported ( Event #2). If the Condition state changes before it can be acknowledged ( Event #6) then a branch state is reported ( Event #7). Timestamps for the Event
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  Annex C Mapping to EEMUA (Informative)
  flag which as part of its definition states: "when a Client receives an Event with the Retain flag set to False, the Client should consider this as a Condition
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.1 Overview
  Overview Serving as a bridge between COM and OPC UA components, the Alarms and Event s proxy and wrapper enable existing A&E COM Clients and Servers to connect ... enables a UA Alarms and Conditions Client to connect to an existing Alarms and Event s COM Server via a UA Server wrapper. This wrapper is notated from this point
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.1 Event areas
  D.2.1 Event areas Event Areas in the A&E COM Server are represented in the A&E COM UA Wrapper as Objects with a TypeDefinition of BaseObjectType
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.2 Event sources
  D.2.2 Event sources Event Sources in the A&E COM Server are represented in the A&E COM UA Wrapper as Objects with a TypeDefinition of BaseObjectType ... used as the BrowseName and DisplayName. The QualifiedSourceName is used to construct the NodeId . Event Source Node s are always targets of a HasEventSource Reference from an Area
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.3 Event categories
  D.2.3 Event categories Event Categories in the A&E COM Server are represented in the UA Server as ObjectTypes which are subtypes of BaseEventType . The BrowseName and DisplayName ... ObjectType Node for Simple and Tracking Event Types are constructed by appending the text 'EventType' to the Description of the Event Category. For Condition Event Types the text 'AlarmType
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.4 Event attributes
  D.2.4 Event attributes Event Attribute s in the A&E COM Server are represented in the UA Server as Variables which are targets of HasProperty Reference s from ... ObjectTypes which represent the Event Categories. The BrowseName and DisplayName are the description for the Event Attribute . The data type of the Event Attribute is used to set DataType
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.5 Event subscriptions
  D.2.5 Event subscriptions The A&E COM UA Wrapper creates a Subscription with the COM AE Server the first time a MonitoredItem is created for the Server Object ... forms the NodeId and one with the text '/*' appended to it. This ensures that Event s from sub areas are correctly reported by the COM AE Server . A simple
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.3.1 General
  address space of UA A & C Server into the appropriate COM Alarms and Event Object s. Subclauses D.3.2 through D.3.9 identify the design guidelines and constraints used to develop ... Server . As a result, the A&E COM Client gets a COM Event Server interface pointer
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.3.3 Event Type mapping
  D.3.3 Event Type mapping Since all Alarms and Conditions Event s belong to a subtype of BaseEventType , the A&E COM UA Proxy maps the subtype as received from ... Server to one of the three A&E Event types: Simple, Tracking and Condition . Figure D.2 shows the mapping as follows: Those A & C Event s which
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.3.4 Event category mapping
  D.3.4 Event category mapping Each A&E Event type (e.g. Simple, Tracking, Condition ) has an associated set of Event categories which are intended to define groupings ... Event s. For example, Level and Deviation are possible Event categories of the Condition Event type for an A&E COM Server . However, since A & C does
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.3.5 Event Category attribute mapping
  D.3.5 Event Category attribute mapping The collection of Attribute s associated with any given A&E Event is encapsulated within the ONEVENTSTRUCT. Therefore ... Proxy populates the Attribute fields within the ONEVENTSTRUCT using corresponding values from UA Event Notification s either directly (e.g., Source, Time, Severity) or indirectly (e.g., OPC COM Event category determined
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.3.6 Event Condition mapping
  D.3.6 Event Condition mapping Event s of any subtype of ConditionType are designated COM Condition Event s and are subject to additional processing due to the stateful nature of Condition ... Event s. COM Condition Event s transition between states composed of the triplet ENABLED|ACTIVE|ACKNOWLEDGED. In UA A & C, Event subtypes of ConditionType only carry a value which
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.3.9.2 Filter by Event, category or severity
  D.3.9.2 Filter by Event, category or severity These filter types are implemented using simple numeric comparisons. For Event filters, the received Event shall match the Event type(s) specified ... filter. For Category filters, the received Event 's category (as mapped from UA Event type) shall match the category or categories specified by the filter. For severity filters, the received
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.3.9.3 Filter by source
  Node s discovered via browsing can be matched to the SourceName Property of the Event returned by the UA A & C Server using string comparisons. Further ... Client may receive Event s from sources which are not discoverable by following only HasNotifier and/or HasEventSource Reference s. Thus, source filters will only apply if the source string
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.3.9.4 Filter by area
  Server Object . In doing so, the A&E COM UA Proxy will receive Event s from the entire Server address space - that is, all Areas
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  4.2.8 Program state transition effects
  external. An external effect of a state transition is the generation of an Event notification. Each Program state transition is associated with a unique Event . These Events reflect the progression
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  4.2.9.2 Intermediate result data
  Events specify the data items for each transition. When the transition occurs, the generated Event conveys the result data values captured to the subscribed Clients . If no Client is monitoring
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  4.2.9.3 Terminal result data
  terminal state, this result data can be conveyed to the Client by the transition Event . Terminal result data is also available within the Program to be read by a Client
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  5.2.5.1 Overview
  HasEffect Reference to a ProgramTransitionEventType and can have an AuditProgramTransitionEventType. When the transition occurs, Event notifications of the referenced type are generated for subscribed Clients. The Program Invocation may serve
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  5.2.5.2 ProgramTransitionEventType
  BaseDataVariableType Mandatory Conformance Units Program Basic TransitionNumber identifies the Program transition that triggered the Event . FromStateNumber identifies the state before the Program transition. ToStateNumber identifies the state after the Program
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  5.2.6 AuditProgramTransitionEventType
  AuditEventType", identifies when the time the Program state transition that resulted in the Event being generated occurred. The TransitionNumber Property is a Variable that identifies the transition that triggered ... Event
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  A.2.5.1 General
  specified for each of the DomainDownload Program transitions. The EventTypes trigger a specific Event notification to the Client when the associated state transition occurs in the running Program Instance ... Event notification identifies the transition. The SendingToSending state transition also includes intermediate result data
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  A.2.5.2 Event information
  A.2.5.2 Event information The SendingToSending Program transition Event relays intermediate result data to the Client along with the notification. Each time the transition occurs, data items describing the amount
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  A.2.6.2 DomainDownloadType
  enters the Running state and the subordinate Transfer Opening state. The Server issues two Event notifications, ReadyToRunning (2), and ToOpening (19). Table A.9 - Start Method additions Attribute Value BrowseName Start ... time the state transition occurs. The values are sent to the Client with the Event notification. Table A.11 defines the IntermediateResults ObjectType and Table A.12 defines the Variables
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  4.1 General
  General This document defines the handling of historical time series data and historical Event data in the OPC Unified Architecture (in a Historian). Included is the specification of the representation
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  4.2 Data architecture
  supporting Historical Access provides Clients with transparent access to different historical data and/or historical Event sources (e.g., process Historians , event Historians , etc.). The historical data or Events ... Server can consist of a broad range of different historical data and/or historical Event sources. Figure 1 - Possible OPC UA Server supporting Historical Access The Historian can be implemented
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  4.3 Historians and interruption of data collection
  interruption can have been for collecting the current values of data or for an event stream. The interruption can have been due to an interruption in the source ... status for the value with the timestamp of when the connection was broken. For Event collection, in addition to what is described for a data collection the following also
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  4.4 Modification of Historical Data/Events
  information related to who made the change (see 6.9 for HistoryUpdateDetails ). Generating an audit event describing the history edit action (see 5.8 ). Some Historians obtain data from other sources ... Modification of Events is different than modification of data, in that in a single event stream there can be many Events with the same Timestamp . Events need to be identified
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  4.5 Timestamps
  apply. This parameter is ignored since the entries returned are dictated by the Event Filter. See OPC 10000-4 for details
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  4.7 Changes in AddressSpace over time
  HistoricalDataNode in the AddressSpace is changed and audit events are supported, an audit Event of AuditHistoryConfigurationChangeEventType shall be generated. A Historian shall expose the Historizing attribute on any nodes that
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.1.2 Annotations Property
  HistoricalNodes , modifications, deletions or additions of Annotations will raise the appropriate historical audit Event with the corresponding NodeId
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.4.1 General
  General The Historical Event model defines additional Properties . These descriptions also include required use cases for HistoricalEventNodes. Historical Access of Events uses an EventFilter . It is important to understand ... differences between applying an EventFilter to current Event Notifications , and historical Event retrieval. In real time monitoring Events are received via Notifications when subscribing to an EventNotifier . The EventFilter provides
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.4.2 HistoricalEventFilter Property
  HistoricalEventFilter Property A HistoricalEventNode that has Event history available shall provide the Property . This Property is formally defined in Table 10 . Table 10 - Standard Historical Events Properties Name Use Data ... Type Description HistoricalEventFilter M EventFilter A filter used by the Server to determine which Event fields are available in history. It also includes a where clause that indicates the types
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.4.3 HistoricalEventConfigurationType
  HistoricalEventConfigurationType The Historical Access Event model extends the standard type model by defining the HistoricalEventConfigurationType. This Object defines the general characteristics of a Node that defines the historical configuration ... listed type shall be capable of being stored as part of the Event history. It is recommended that all optional properties that are supported by the EventType can also
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.5.1 General
  HasCurrentData or the HasCurrentEvent Reference to indicate the source node for the data or Event . Mirroring Variables is typically simple. Variables usually do not have complex structure or nested Variables
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.6.4 HistoricalEventNodes Address Space Model
  this Attribute. Figure 5 illustrates the basic AddressSpace Model of an Event model that includes History. Figure 5 - Representation of an Event with History in the AddressSpace
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.6.5 Historical Events
  Historical Events Figure 6 provides an illustration of information related to Event sources that are in a Historian , where the events are being source from external Servers . Figure 6 - Event
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.8.1 General
  source and the user and Client Session as the initiators of the Event . Not all Servers support auditing, but if a Server supports auditing, then it shall support audit Events ... case where the HistoryUpdate Service is invoked to insert Historical Events , the AuditHistoryEventUpdateEventType Event shall include the EventId of the inserted Event and a description that indicates that the Event
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.8.2 AuditHistoryEventUpdateEventType
  AuditHistoryEventUpdateEventType This is a subtype of AuditHistoryUpdateEventType and is used for categorization of History Event update related Events . This type follows all the behaviour of its parent type. Its representation ... Variable NewValues HistoryEventFieldList [ ] PropertyType Mandatory HasProperty Variable OldValues HistoryEventFieldList [ ] PropertyType Mandatory ConformanceUnits Historical Access Event Audit Events This EventType inherits all Properties of the AuditHistoryUpdateEventType . Their semantic is defined
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.8.3 AuditHistoryValueUpdateEventType
  Service call. The NewValues identify the value that was written to the Event . The OldValues identify the value that the Event contained before the write. It is acceptable
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.8.8 AuditHistoryEventDeleteEventType
  have this information to report a null value. The OldValues will contain an Event with the appropriate fields, each with appropriately encoded values
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.8.10 AuditHistoryBulkInsertEventType
  used for tracking a bulk insertion of HistoricalData or HistoricalEvents into a Historian . This Event should not be generated for a given Node more frequently than once per minute, even
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.2.2 Operation level result codes
  Access the StatusCode is used to indicate the conditions under which a Value or Event was stored, and thereby can be used as an indicator of its usability ... Symbolic Id Description Bad_NoData No data exists for the requested time range or Event filter. Bad_BoundNotFound No data found to provide upper or lower bound value. Bad_BoundNotSupported
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.5.2.1 ReadEventDetails structure details
  ReadEventDetails Structure Name Type Description ReadEventDetails Structure Specifies the details used to perform an Event history read. numValuesPerNode Counter The maximum number of Events returned for any Node over
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.5.2.2 Read Event functionality
  Read Event functionality The ReadEventDetails structure is used to read the Events from the history database for the specified time domain for one or more HistoricalEventNodes . The ReadEventDetails2 can also ... startTime and the endTime to be identical. This allows the Client to request the Event(s) at a single instance in time. When the startTime and endTime are identical then
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.5.2.3 ReadEventDetails2 structure details
  readModified Boolean is set to FALSE. This updated structure can be used for all event retrieval operations. ReadEventDetails2 is only valid for Objects that have the EventNotifier Attribute ... ReadEventDetails2 Structure Name Type Description ReadEventDetails2 Structure Specifies the details used to perform an Event history read. readModified Boolean TRUE for Read Modified functionality Its representation in the AddressSpace
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.5.2.4 Read modified functionality
  multiple replaced Events the Server shall return all of them. The updateType specifies what Event is returned in the modification record. If the updateType is INSERT the Event ... Event that was inserted. If the updateType is anything else the Event is the old Event that was changed. See 6.9 HistoryUpdateDetails parameter for details on what updateTypes are available
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.5.2.5 ReadEventDetailsSorted structure details
  ReadEventDetailsSorted Structure Name Type Description ReadEventDetailsSorted Structure Specifies the details used to perform an Event history read. SortClause SortRuleElement[] Sorting rules for the filtered notification that match the EventFilter
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.6.4 HistoryEvent DataType
  HistoryEvent DataType Table 51 defines the HistoryEvent parameter used for Historical Event reads. The HistoryEvent defines a table structure that is used to return Event fields to a Historical Read ... more fields. The selection and order of the fields returned for each Event are identical to the selected parameter of the EventFilter . Table 51 - HistoryEvent structure Name Type Description HistoryEvent
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.6.5 HistoryModifiedEvent DataType
  HistoryModifiedEvent DataType Table 49 defines the structure of the HistoryEvent parameter used for Historical event reads when the readModified = True. The HistoryModifyEvent defines a table structure that is used ... return Event fields along with modification information to a Historical Read . The structure is in the form of a table consisting of one or more Events , each containing an array
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.1 Overview
  history database for the specified timestamps for one or more HistoricalDataNodes . DeleteEventDetails Delete event This function deletes Events from the history database for the specified filter for one or more ... term "entry" will be used to mean either DataValue, Annotation, or Event depending on the context in which it is used. Auditing requirements for History Services are described
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.4.1 UpdateEventDetails structure detail
  Structure Name Type Description UpdateEventDetails Structure The details for insert, replace, and insert/replace history Event updates. nodeId NodeId Node id of the Object to be updated. performInsertReplace PerformUpdateType Value determines ... EventFilter , the history of the Notification is updated. eventData[] HistoryEventFieldList List of Event Notifications to be inserted or updated (see 6.6.4 for HistoryEventFieldList definition). Its representation in the AddressSpace
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.4.2 Insert event functionality
  Insert event functionality This function is intended to insert new entries, e.g., backfilling of historical Events . Setting performInsertReplace = INSERT inserts entries into the Event history database for one or more ... EventFilter shall be empty. The selectClause shall, as a minimum, provide the following Event fields: EventType, and Time . It is also recommended that the SourceNode and the SourceName fields
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.4.3 Replace event functionality
  Replace event functionality This function is intended to replace fields in existing Event entries, e.g., correct Event data that contained incorrect data due to a bad sensor. Setting performInsertReplace = REPLACE ... replaces entries in the Event history database for the specified EventIds for one or more HistoricalEventNodes . The selectClause parameter of the EventFilter shall specify the EventId Property and the eventData
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.4.4 Update event functionality
  Update event functionality This function is intended to unconditionally insert/replace Events . Setting performInsertReplace = UPDATE inserts or replaces entries in the Event history database for the specified filter ... HistoricalEventNodes . The Server will, based on its own criteria, attempt to determine if the Event already exists; if it does exist then the Event will be deleted
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.7.2 Delete event functionality
  Delete event functionality The DeleteEventDetails structure deletes all Event entries from the history database matching the EventId for one or more HistoricalEventNodes . If no Events are found that match
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.2.1 TrustListType
  TrustLists . If a Server is not able to determine the LastUpdateTime after an event such as a restart, then the LastUpdateTime shall be DateTime.MinValue. The UpdateFrequency Property specifies how often ... AddCertificate (see 7.8.2.6 ) , RemoveCertificate (see 7.8.2.7 ) or ApplyChanges (see 7.10.9 ) Methods . The Event is only raised once after the asynchronous update process completes
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.10.26 CertificateUpdateRequestedAuditEventType
  CertificateUpdateRequestedAuditEventType This event is raised when the UpdateCertificate Method is called. If a PrivateKey was one of the InputArguments then that argument is set to NULL before generating this Event
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.10.27 CertificateUpdatedAuditEventType
  CertificateUpdatedAuditEventType This event is raised when a Certificate is actually changed as a result of a Method call. This is the result of a successful call to UpdateCertificate or ApplyChanges ... ServerConfigurationType Object . No Event is raised if the Method call fails. If ApplyChanges affects multiple Certificates then this Event is raised for each changed Certificate . Its representation in the AddressSpace
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  8.5.8 KeyCredentialAuditEventType
  KeyCredentialAuditEventType This abstract event is raised when an operation affecting KeyCredentials occur This Event and it subtypes are security related and Servers shall only report them to users authorized
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  8.6.9 KeyCredentialUpdatedAuditEventType
  KeyCredentialUpdatedAuditEventType This event is raised when a KeyCredential is updated. This Event and its subtypes report sensitive security related information. Servers shall only report these Events to Clients which
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  9.6.10 AccessTokenRequestedAuditEventType
  AccessTokenRequestedAuditEventType This event is raised when a AccessToken is requested as a result of a FinishRequestToken Method being called. This Event and its subtypes are security related and Servers shall
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  9.6.11 AccessTokenIssuedAuditEventType
  AccessTokenIssuedAuditEventType This event is raised when a AccessToken is issued. This is the result of a RequestAccessToken Method completing. This Event and its subtypes are security related and Servers shall
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.3.2 Operation level result codes
  Aggregates the StatusCode is used to indicate the conditions under which a value or Event was stored, and thereby can be used as an indicator of its usability
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  3.1.8 PublishedDataSet
  entry: A PublishedDataSet can be a list of monitored Variables or an Event selection
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.2.1 General
  thought of as a list of name and value pairs representing an Event or a list of Variable Values . A DataSet can be created from an Event or from ... DataSet in the process of publishing A PublishedDataSet is similar to either an Event MonitoredItem or a list of data MonitoredItems in the Client Server Subscription model. Similar
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.1.2 Message sending
  with standard OPC UA configuration are PublishedDataItems for Variable base collection and PublishedEvents for Event based collection. In the next step, a DataSetWriter takes the DataSet and creates a DataSetMessage
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.6.3.2 Broker-based model
  required for the messaging protocol. A DataSet can be collected from a list of Event fields and/or selected Variables . Such a configuration is called PublishedDataSet . Each DataSet is sent
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.3.8.2 SelectedFields
  SelectedFields The parameter SelectedFields defines the selection of Event fields contained in the DataSet generated for an Event and sent through the DataSetWriter . The SimpleAttributeOperand DataType is defined ... DataType of the selected Event field in the EventType defines the DataType of the DataSet field. Event fields can be null or the field value can be a StatusCode
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.6.2 PublishingInterval
  resent or no DataSetMessage is sent. In the case non-cyclic PublishedDataSets like Event based DataSets , this may result in zero to many DataSetMessages produced for one PublishedDataSet ... sent. If the number of Events exceeds the buffer capability of the DataSetWriter, an Event of type EventQueueOverflowEventType is inserted as last entry into the buffer and all Events that
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  7.2.4.5.7 Event DataSetMessage
  Event DataSetMessage The Event DataSetMessage data and the related headers are shown in Figure 37 . Figure 37 - Event DataSetMessage The encoding of the Event DataSetMessage structure is specified in Table ... Table 165 - Event DataSetMessage structure Name Type Description FieldCount UInt16 Number of fields of the DataSet contained in the DataSetMessage . DataSetFields BaseDataType [FieldCount] The field values of the DataSet
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  7.2.5.3 NetworkMessage containing DataSetMessages
  encoded NetworkMessage size exceeds the Broker limits the message is dropped and a PubSubTransportLimitsExceeded Event is reported
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.1 General
  information flow The PublishedDataSetType represents the selection and configuration of Variables or Events . An Event notification or a snapshot of the Variables comprises a DataSet . A DataSet is the content
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.2.1 PublishedDataSetType
  list of monitored Variables used to create cyclic DataSets . For PublishedEventsType this is an Event selection used to create acyclic DataSets . The list of monitored Variables or the list
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.4.1 PublishedEventsType
  important role for Subscribers. It is used as handle to reference the Event field in DataSetMessages received by Subscribers . The index may change after configuration changes. Changes are indicated
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.4.2 ModifyFieldSelection Method
  ModifyFieldSelection Method This Method is used to modify the event field selection of a PublishedEventsType Object . The Client shall be authorized to modify the configuration for the PubSub functionality when ... field in the FieldMetaData that is part of the DataSetMetaData . SelectedFields The selection of Event fields contained in the DataSet generated for an Event and sent through the DataSetWriter
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.5.3 AddPublishedEvents Method
  PublishedEventsType . The DataSetMetaData of the PublishedDataSetType is created from metadata of the selected Event fields and the settings in FieldNameAliases and FieldFlags . The Client shall be authorized to modify ... DataSet Object to create. EventNotifier The NodeId of the Object in the event notifier tree of the OPC UA Server from which Events are collected. FieldNameAliases The names assigned
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.4.5.5 AddPublishedEventsTemplate Method
  name in the DataSetMetaData . EventNotifier The NodeId of the Object in the event notifier tree of the OPC UA Server from which Events are collected. SelectedFields The selection of Event ... Fields contained in the DataSet generated for an Event and sent through the DataSetWriter . The size of the array shall match the size of the fields array in the DataSetMetaData
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.13.1 PubSubStatusEventType
  NodeId PropertyType Mandatory HasProperty Variable State PubSubState PropertyType Mandatory Conformance Units PubSub Model Status Event This EventType inherits all Properties of the SystemEventType . Their semantic is defined ... NodeId of the PubSubConnectionType , PubSubGroupType , DataSetWriterType or DataSetReaderType Object associated with the Event . The SourceName is the BrowseName of the SourceNode . The ConnectionId Property is the NodeId of the PubSubConnectionType
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.13.3 PubSubCommunicationFailureEventType
  PubSub Model Diagnostics Events This EventType inherits all Properties of the PubSubStatusEventType . The Message Event field inherited from BaseEventType has a localized description of the error. The Error Property
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.2.1 Simple state machine
  action) of the transition can also be specified, for example the generation of an Event of the "EventType1" in the same transition. The notation used to identify
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.4.2 StateMachineType
  current state of the machine. An instance of this ObjectType shall generate an Event whenever a significant state change occurs. The Server decides which state changes are significant. Servers shall ... GeneratesEvent ReferenceType to indicate which Event(s) could be produced by the StateMachine . Subtypes may add Methods which affect the state of the machine. The Executable Attribute is used