EN 62541-9:2015

SLOVENSKI STANDARD
01-september-2015
1DGRPHãþD
SIST EN 62541-9:2012
Enotna arhitektura OPC - 9. del: Alarmi in pogoji (IEC 62541-9:2015)
OPC Unified Architecture -- Part 9: Alarms and conditions (IEC 62541-9:2015)
OPC Unified Architecture - Teil 9: Alarme und Zustände (IEC 62541-9:2015)
Architecture unifiée OPC - Partie 9: Alarmes et conditions (IEC 62541-9:2015)
Ta slovenski standard je istoveten z: EN 62541-9:2015
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.240.50 Uporabniške rešitve IT v IT applications in industry
industriji
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD EN 62541-9
NORME EUROPÉENNE
EUROPÄISCHE NORM
May 2015
ICS 25.040.40; 35.100 Supersedes EN 62541-9:2012
English Version
OPC unified architecture - Part 9: Alarms and conditions
(IEC 62541-9:2015)
Architecture unifiée OPC - Partie 9: Alarmes et conditions OPC Unified Architecture - Teil 9: Alarme und Zustände
(IEC 62541-9:2015) (IEC 62541-9:2015)
This European Standard was approved by CENELEC on 2015-04-29. CENELEC members are bound to comply with the CEN/CENELEC
Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.
Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC
Management Centre or to any CENELEC member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation
under the responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the
same status as the official versions.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and the United Kingdom.

European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2015 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN 62541-9:2015 E
Foreword
The text of document 65E/382/CDV, future edition 2 of IEC 62541-9, prepared by SC 65E "Devices
and integration in enterprise systems", of IEC/TC 65 "Industrial-process measurement, control and
automation" was submitted to the IEC-CENELEC parallel vote and approved by CENELEC as
The following dates are fixed:
• latest date by which the document has to be implemented at (dop) 2016-01-29
national level by publication of an identical national
standard or by endorsement
(dow) 2018-04-29
• latest date by which the national standards conflicting with
the document have to be withdrawn

This document supersedes EN 62541-9:2012.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC [and/or CEN] shall not be held responsible for identifying any or all such
patent rights.
This document has been prepared under a mandate given to CENELEC by the European Commission
and the European Free Trade Association, and supports essential requirements of EU Directive(s).
Endorsement notice
The text of the International Standard IEC 62541-9:2015 was approved by CENELEC as a European
Standard without any modification.
In the official version, for Bibliography, the following notes have to be added for the standards indicated:
IEC 62541-7 NOTE Harmonized as EN 62541-7.
IEC 62541-11 NOTE Harmonized as EN 62541-11.

- 3 - EN 62541-9:2015
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
NOTE 1 When an International Publication has been modified by common modifications, indicated by (mod),
the relevant EN/HD applies.
NOTE 2 Up-to-date information on the latest versions of the European Standards listed in this annex is
available here: www.cenelec.eu.

Publication Year Title EN/HD Year
IEC/TR 62541-1 -  OPC unified architecture - CLC/TR 62541-1 -
Part 1: Overview and concepts
IEC 62541-3 -  OPC unified architecture - EN 62541-3 -
Part 3: Address Space Model
IEC 62541-4 -  OPC Unified Architecture - EN 62541-4 -
Part 4: Services
IEC 62541-5 -  OPC unified architecture - EN 62541-5 -
Part 5: Information Model
IEC 62541-6 -  OPC unified architecture - EN 62541-6 -
Part 6: Mappings
IEC 62541-8 -  OPC Unified Architecture - EN 62541-8 -
Part 8: Data Access
EEMUA 191  Alarm systems - A guide to design, - -
management and procurement
IEC 62541-9 ®
Edition 2.0 2015-03
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
OPC unified architecture –
Part 9: Alarms and conditions
Architecture unifiée OPC –
Partie 9: Alarmes et conditions

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 25.040.40; 35.100 ISBN 978-2-8322-2382-6

– 2 – IEC 62541-9:2015 © IEC 2015
CONTENTS
FOREWORD . 8
1 Scope . 10
2 Normative references. 10
3 Terms, definitions, and abbreviations . 10
3.1 Terms and definitions . 10
3.2 Abbreviations and symbols . 12
3.3 Used data types . 12
4 Concepts . 12
4.1 General . 12
4.2 Conditions. 12
4.3 Acknowledgeable Conditions . 14
4.4 Previous states of Conditions . 15
4.5 Condition state synchronization . 16
4.6 Severity, Quality, and Comment . 16
4.7 Dialogs . 17
4.8 Alarms . 17
4.9 Multiple Active States . 18
4.10 Condition Instances in the Address Space . 19
4.11 Alarm and Condition Auditing . 19
5 Model . 19
5.1 General . 19
5.2 Two-State State Machines . 20
5.3 Condition Variables . 21
5.4 Substate Reference Types . 22
5.4.1 General . 22
5.4.2 HasTrueSubState ReferenceType . 22
5.4.3 HasFalseSubState ReferenceType . 23
5.5 Condition Model . 23
5.5.1 General . 23
5.5.2 ConditionType . 24
5.5.3 Condition and Branch Instances . 27
5.5.4 Disable Method . 27
5.5.5 Enable Method . 28
5.5.6 AddComment Method . 28
5.5.7 ConditionRefresh Method . 29
5.6 Dialog Model . 31
5.6.1 General . 31
5.6.2 DialogConditionType . 31
5.6.3 Respond Method . 32
5.7 Acknowledgeable Condition Model . 33
5.7.1 General . 33
5.7.2 AcknowledgeableConditionType . 33
5.7.3 Acknowledge Method . 34
5.7.4 Confirm Method . 35
5.8 Alarm Model . 36
5.8.1 General . 36

IEC 62541-9:2015 © IEC 2015 – 3 –
5.8.2 AlarmConditionType . 37
5.8.3 ShelvedStateMachineType . 39
5.8.4 LimitAlarmType . 43
5.8.5 ExclusiveLimit Types . 44
5.8.6 NonExclusiveLimitAlarmType . 46
5.8.7 Level Alarm . 48
5.8.8 Deviation Alarm . 48
5.8.9 Rate of Change . 49
5.8.10 Discrete Alarms . 50
5.9 ConditionClasses . 52
5.9.1 Overview . 52
5.9.2 Base ConditionClassType . 52
5.9.3 ProcessConditionClassType . 53
5.9.4 MaintenanceConditionClassType . 53
5.9.5 SystemConditionClassType . 53
5.10 Audit Events . 53
5.10.1 Overview . 53
5.10.2 AuditConditionEventType . 54
5.10.3 AuditConditionEnableEventType . 55
5.10.4 AuditConditionCommentEventType . 55
5.10.5 AuditConditionRespondEventType . 55
5.10.6 AuditConditionAcknowledgeEventType . 55
5.10.7 AuditConditionConfirmEventType . 56
5.10.8 AuditConditionShelvingEventType . 56
5.11 Condition Refresh Related Events . 56
5.11.1 Overview . 56
5.11.2 RefreshStartEventType . 57
5.11.3 RefreshEndEventType . 57
5.11.4 RefreshRequiredEventType . 57
5.12 HasCondition Reference Type . 58
5.13 Alarm and Condition Status Codes . 58
5.14 Expected A&C Server Behaviours . 59
5.14.1 General . 59
5.14.2 Communication problems . 59
5.14.3 Redundant A&C Servers . 59
6 AddressSpace Organisation . 60
6.1 General . 60
6.2 Event Notifier and Source Hierarchy . 60
6.3 Adding Conditions to the Hierarchy . 61
6.4 Conditions in InstanceDeclarations . 61
6.5 Conditions in a VariableType . 62
Annex A (informative) Recommended localized names . 63
A.1 Recommended State Names for TwoState Variables . 63
A.1.1 LocaleId “en” . 63
A.1.2 LocaleId “de” . 63
A.1.3 LocaleId “fr” . 64
A.2 Recommended Dialog Response Options . 64
Annex B (informative) Examples . 65
B.1 Examples for Event sequences from Condition instances . 65

– 4 – IEC 62541-9:2015 © IEC 2015
B.1.1 Overview . 65
B.1.2 Server Maintains Current State Only . 65
B.1.3 Server Maintains Previous States . 65
B.2 Address Space Examples . 67
Annex C (informative) Mapping to EEMUA . 71
Annex D (informative) Mapping from OPC A&E to OPC UA A&C . 72
D.1 Overview. 72
D.2 Alarms and Events COM UA Wrapper . 72
D.2.1 Event Areas . 72
D.2.2 Event Sources . 73
D.2.3 Event Categories . 73
D.2.4 Event Attributes . 74
D.2.5 Event Subscriptions. 74
D.2.6 Condition Instances . 76
D.2.7 Condition Refresh . 76
D.3 Alarms and Events COM UA Proxy . 77
D.3.1 General . 77
D.3.2 Server Status Mapping . 77
D.3.3 Event Type Mapping . 77
D.3.4 Event Category Mapping . 78
D.3.5 Event Category Attribute Mapping . 79
D.3.6 Event Condition Mapping . 82
D.3.7 Browse Mapping. 82
D.3.8 Qualified Names . 83
D.3.9 Subscription Filters . 84
Bibliography . 86

Figure 1 – Base Condition State Model . 13
Figure 2 – AcknowledgeableConditions State Model . 14
Figure 3 – Acknowledge State Model . 15
Figure 4 – Confirmed Acknowledge State Model . 15
Figure 5 – Alarm State Machine Model . 17
Figure 6 – Multiple Active States Example . 18
Figure 7 – ConditionType Hierarchy . 20
Figure 8 – Condition Model . 24
Figure 9 – DialogConditionType Overview . 31
Figure 10 – AcknowledgeableConditionType Overview . 33
Figure 11 – AlarmConditionType Hierarchy Model . 37
Figure 12 – Alarm Model . 37
Figure 13 – Shelve state transitions . 39
Figure 14 – Shelved State Machine Model . 40
Figure 15 – LimitAlarmType . 43
Figure 16 – ExclusiveLimitStateMachine . 44
Figure 17 – ExclusiveLimitAlarmType . 46
Figure 18 – NonExclusiveLimitAlarmType . 47
Figure 19 – DiscreteAlarmType Hierarchy . 50

IEC 62541-9:2015 © IEC 2015 – 5 –
Figure 20 – ConditionClass Type Hierarchy . 52
Figure 21 – AuditEvent Hierarchy . 54
Figure 22 – Refresh Related Event Hierarchy . 57
Figure 23 – Typical Event Hierarchy . 60
Figure 24 – Use of HasCondition in an Event Hierarchy . 61
Figure 25 – Use of HasCondition in an InstanceDeclaration . 62
Figure 26 – Use of HasCondition in a VariableType . 62
Figure B.1 – Single State Example . 65
Figure B.2 – Previous State Example . 66
Figure B.3 – HasCondition used with Condition instances . 68
Figure B.4 – HasCondition reference to a Condition Type . 69
Figure B.5 – HasCondition used with an instance declaration . 70
Figure D.1 – The Type Model of a Wrapped COM AE Server . 74
Figure D.2 – Mapping UA Event Types to COM A&E Event Types . 78
Figure D.3 – Example Mapping of UA Event Types to COM A&E Categories . 79
Figure D.4 – Example Mapping of UA Event Types to A&E Categories with Attributes . 82

Table 1 – Parameter Types defined in IEC 62541-3 . 12
Table 2 – Parameter Types defined in IEC 62541-4 . 12
Table 3 – TwoStateVariableType Definition . 21
Table 4 – ConditionVariableType Definition . 22
Table 5 – HasTrueSubState ReferenceType . 22
Table 6 – HasFalseSubState ReferenceType . 23
Table 7 – ConditionType Definition . 25
Table 8 – Simple Attribute Operand . 27
Table 9 – Disable Result Codes . 28
Table 10 – Disable Method AddressSpace Definition . 28
Table 11 – Enable Result Codes . 28
Table 12 – Enable Method AddressSpace Definition . 28
Table 13 – AddComment Arguments . 29
Table 14 – AddComment result Codes . 29
Table 15 – AddComment Method AddressSpace Definition . 29
Table 16 – ConditionRefresh Parameters . 30
Table 17 – ConditionRefresh ReturnCodes . 30
Table 18 – ConditionRefresh Method AddressSpace Definition . 31
Table 19 – DialogConditionType Definition . 31
Table 20 – Repond Parameters . 32
Table 21 – Respond ResultCodes . 33
Table 22 – Respond Method AddressSpace Definition . 33
Table 23 – AcknowledgeableConditionType Definition . 34
Table 24 – Acknowledge Parameters . 34
Table 25 – Acknowledge result codes . 35
Table 26 – Acknowledge Method AddressSpace Definition . 35

– 6 – IEC 62541-9:2015 © IEC 2015
Table 27 – Confirm Method Parameters . 35
Table 28 – Confirm Result Codes . 36
Table 29 – Confirm Method AddressSpace Definition . 36
Table 30 – AlarmConditionType Definition . 38
Table 31 –ShelvedStateMachine Definition . 40
Table 32 – ShelvedStateMachine Transitions . 41
Table 33 – Unshelve Result Codes . 41
Table 34 – Unshelve Method AddressSpace Definition . 41
Table 35 – TimedShelve Parameters . 42
Table 36 – TimedShelve Result Codes . 42
Table 37 – TimedShelve Method AddressSpace Definition . 42
Table 38 – OneShotShelve Result Codes . 42
Table 39 – OneShotShelve Method AddressSpace Definition . 43
Table 40 – LimitAlarmType Definition . 43
Table 41 – ExclusiveLimitStateMachineType Definition . 44
Table 42 – ExclusiveLimitStateMachineType Transitions . 45
Table 43 – ExclusiveLimitAlarmType Definition . 46
Table 44 – NonExclusiveLimitAlarmType Definition . 47
Table 45 – NonExclusiveLevelAlarmType Definition . 48
Table 46 – ExclusiveLevelAlarmType Definition . 48
Table 47 – NonExclusiveDeviationAlarmType Definition . 49
Table 48 – ExclusiveDeviationAlarmType Definition . 49
Table 49 – NonExclusiveRateOfChangeAlarmType Definition . 50
Table 50 – ExclusiveRateOfChangeAlarmType Definition . 50
Table 51 – DiscreteAlarmType Definition . 51
Table 52 – OffNormalAlarmType Definition . 51
Table 53 – SystemOffNormalAlarmType Definition . 51
Table 54 – TripAlarmType Definition . 52
Table 55 – BaseConditionClassType Definition . 52
Table 56 – ProcessConditionClassType Definition . 53
Table 57 – MaintenanceConditionClassType Definition . 53
Table 58 – SystemConditionClassType Definition . 53
Table 59 – AuditConditionEventType Definition . 54
Table 60 – AuditConditionEnableEventType Definition . 55
Table 61 – AuditConditionCommentEventType Definition . 55
Table 62 – AuditConditionRespondEventType Definition . 55
Table 63 – AuditConditionAcknowledgeEventType Definition . 56
Table 64 – AuditConditionConfirmEventType Definition . 56
Table 65 – AuditConditionShelvingEventType Definition . 56
Table 66 – RefreshStartEventType Definition . 57
Table 67 – RefreshEndEventType Definition . 57
Table 68 – RefreshRequiredEventType Definition . 58
Table 69 – HasCondition ReferenceType . 58

IEC 62541-9:2015 © IEC 2015 – 7 –
Table 70 – Alarm and Condition Result Codes . 59
Table A.1 – Recommended state names for LocaleId “en” . 63
Table A.2 – Recommended display names for LocaleId “en” . 63
Table A.3 – Recommended state names for LocaleId “de” . 63
Table A.4 – Recommended display names for LocaleId “de” . 64
Table A.5 – Recommended state names for LocaleId “fr” . 64
Table A.6 – Recommended display names for LocaleId “fr” . 64
Table A.7 – Recommended Dialog Response Options. 64
Table B.1 – Example of a Condition that only keeps the latest state . 65
Table B.2 – Example of a Condition that maintains previous states via branches . 67
Table C.1 – EEMUA Terms . 71
Table D.1 – Mapping from Standard Event Categories to OPC UA Event Types . 73
Table D.2 – Mapping from ONEVENTSTRUCT fields to UA BaseEventType Variables . 75
Table D.3 – Mapping from ONEVENTSTRUCT fields to UA AuditEventType Variables. 75
Table D.4 – Mapping from ONEVENTSTRUCT fields to UA AlarmType Variables . 76
Table D.5 – Event Category Attribute Mapping Table . 80

– 8 – IEC 62541-9:2015 © IEC 2015
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
OPC UNIFIED ARCHITECTURE –
Part 9: Alarms and conditions
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
International Standard IEC 62541-9 has been prepared by subcommittee 65E: Devices and
integration in enterprise systems, of IEC technical committee 65: Industrial-process
measurement, control and automation.
This second edition cancels and replaces the first edition published in 2012. This edition
constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous
edition:
a) added section to describe expect behaviour for A&C servers and the associated
information model in the case of redundancy or communication faults, see 5.14 for
additional details.[ref 698 & 967];
b) changed the DialogConditionType to be not abstract since it is expect that instance of this
type will exist in the system, see Table 19 for additonal details [ref 1622];

IEC 62541-9:2015 © IEC 2015 – 9 –
c) updated ConditionRefresh Method to allow the use of the well know NodeIds associated
with the types for the MethodId and ConditionId instead of requiring the call to use only
the MethodId and ConditionId that is part of an instance. Without this change, servers that
do not expose instance may have problems with ConditionRefresh, see 5.5.7 for additional
details [ref 2091];
d) Fixed ExclusiveLimitStateMachineType and ShelvedStatemachineType to be sub-types of
FinitStateMachineType not StateMachineType. See 5.8.3 and 5.8.5.2 for additional details
[ref 2091].
The text of this standard is based on the following documents:
CDV Report on voting
65E/382/CDV 65E/408/RVC
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
A list of all parts of the IEC 62541 series, published under the general title OPC Unified
Architecture, can be found on the IEC website.
The committee has decided that the contents of this publication will remain unchanged until
the stability date indicated on the IEC web site under "http://webstore.iec.ch" in the data
related to the specific publication. At this date, the publication will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct
understanding of its contents. Users should therefore print this document using a
colour printer.
– 10 – IEC 62541-9:2015 © IEC 2015
OPC UNIFIED ARCHITECTURE –
Part 9: Alarms and conditions
1 Scope
This part of IEC 62541 specifies the representation of Alarms and Conditions in the OPC
Unified Architecture. Included is the Information Model representation of Alarms and
Conditions in the OPC UA address space.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any
amendments) applies.
IEC TR 62541-1, OPC Unified Architecture – Part 1: Overview and Concepts
IEC 62541-3, OPC Unified Architecture – Part 3: Address Space Model
IEC 62541-4, OPC Unified Architecture – Part 4: Services
IEC 62541-5, OPC Unified Architecture – Part 5: Information Model
IEC 62541-6, OPC Unified Architecture – Part 6: Mappings
IEC 62541-8, OPC Unified Architecture – Part 8: Data Access
EEMUA: 2nd Edition EEMUA 191 – Alarm System – A guide to design, management and
procurement (Appendixes 6, 7, 8, 9), available at http://www.eemua.co.uk/
3 Terms, definitions, and abbreviations
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC TR 62541-1,
IEC 62541-3, IEC 62541-4, and IEC 62541-5 as well as the following apply.
3.1.1
acknowledge
operator action that indicates recognition of a new Alarm
Note 1 to entry: This definition is copied from EEMUA. The term “Accept” is another common term used to
describe Acknowledge. They can be used interchangeably. This standard will use Acknowledge.
3.1.2
active
state for an Alarm that indicates that the situation the Alarm is representing currently exists
Note 1 to entry: Other common terms defined by EEMUA are “Standing” for an Active Alarm and “Cleared” when
the Condition has returned to normal and is no longer Active.

IEC 62541-9:2015 © IEC 2015 – 11 –
3.1.3
ConditionClass
Condition grouping that indicates in which domain or for what purpose a certain Condition is
used
Note 1 to entry: Some top-level ConditionClasses are defined in this specification. Vendors or organisations may
derive more concrete classes or define different top-level classes.
3.1.4
ConditionBranch
specific state of a Condition
Note 1 to entry: The Server can maintain ConditionBranches for the current state as well as for previous states.
3.1.5
ConditionSource
element which a specific Condition is based upon or related to
Note 1 to entry: Typically, it will be a Variable representing a process tag (e.g. FIC101) or an Object representing
a device or subsystem.
In Events generated for Conditions, the SourceNode Property (inherited from the BaseEventType) will contain the
NodeId of the ConditionSource.
3.1.6
confirm
operator action informing the Server that a corrective action has been taken to address the
cause of the Alarm
3.1.7
disable
system is configured such that the Alarm will not be generated even though the base Alarm
Condition is present
Note 1 to entry: This definition is copied from EEMUA and is further described in EEMUA.
3.1.8
operator
special user who is assigned to monitor and control a portion of a process
Note
...