SIST EN IEC 62541-9:2026
(Main)OPC Unified Architecture - Part 9: Alarms and Conditions (IEC 62541-9:2026)
- Abstract
IEC 62541-9:2026 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. Other aspects of alarm systems like alarm philosophy, life cycle, alarm response times, alarm types and many other details are captured in standards such as IEC 62682 and ISA 18.2. The Alarms and Conditions Information Model in this document, is designed in accordance with IEC 62682 and ISA 18.2. Annex C specifies a recommended mapping between OPC Classic Alarm & Events (A&E) servers to the model described in this document. Annex A describes recommended localized names for Alarm states. Annex B describes examples (e.g. Event sequences, Alarm areas in AddressSpace). This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) addition of "Comment" parameter to Alarm shelving methods;
b) addition of method that allows a client to get the members of a group, since it is possible that the AddressSpace does not expose instances of alarms;
c) addition of deadband properties for all limits in the limit AlarmType (from which all other types described in this issue are derived);
d) addition of text explaining the disabling of alarms is no longer supported in ISA 18.2 and that it is maintained in this document for backward compatibility, but that it is recommended that Alarm not be disabled;
e) addition of optional severities for limit alarms;
f) addition of new AlarmState variable type that can be used to collect alarm information for displays on graphics;
g) addition of SupportsFilterRetain property to improve Client filtering;
h) removal of ConditionSubClassId and ConditionSubClassNames from the conditiontype definition since they are now defined in BaseEventType.
- Status
- Published
- Public Enquiry End Date
- 30-Mar-2024
- Publication Date
- 12-Oct-2026
- Technical Committee
- MOV - Measuring equipment for electromagnetic quantities
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 30-Jun-2026
- Due Date
- 04-Sep-2026
- Completion Date
- 13-Oct-2026
SIST EN IEC 62541-9:2026 is a standard from SIST on OPC Unified Architecture (OPC UA) for Alarms and Conditions (A & C). It specifies the information model for representing alarms and conditions in the OPC UA AddressSpace, so OPC UA client and server developers can exchange alarm state, acknowledgement, and related event data in a consistent way.
What does SIST EN IEC 62541-9:2026 specify?
SIST EN IEC 62541-9:2026 specifies how Alarms and Conditions are represented in OPC UA. Its focus is the information model in the OPC UA AddressSpace, while wider alarm-management topics such as alarm philosophy, life cycle, response times, and alarm types are handled in IEC 62682 and ISA 18.2.
The document is organized into clauses for concepts, the model, AddressSpace organization, system state and alarms, alarm summary objects, and alarm metrics. It also includes informative annexes for localized names, examples, mappings to EEMUA, mapping from OPC Classic Alarm & Events (A&E) to OPC UA A & C, IEC 62682 mapping, and a system state example.
| Annex | What it covers |
|---|---|
| Annex A | Recommended localized names for alarm states and dialog responses |
| Annex B | Examples of event sequences and AddressSpace structures |
| Annex C | Recommended mapping to EEMUA |
| Annex D | Mapping from OPC A&E to OPC UA A & C |
| Annex E | IEC 62682 mapping |
| Annex F | System State example |
What are the key requirements of SIST EN IEC 62541-9:2026?
SIST EN IEC 62541-9:2026 defines the alarm-and-condition model, the methods used to manage it, and the way those objects are placed in the AddressSpace. In practice, the document tells an implementer what state variables, methods, reference types, and event records need to exist so clients can browse, filter, acknowledge, shelve, suppress, and audit alarms.
Condition and dialog model
Clause 4 explains the core concepts behind Conditions, Acknowledgeable Conditions, previous states, state synchronization, severity, quality, comment, dialogs, multiple active states, and auditing. That matters because alarm data is not just a single flag - the model must preserve current state, prior state, and operator actions.
Clause 5 then defines the model objects. It includes Two-state state machines, ConditionVariable, and the ReferenceTypes HasTrueSubState, HasFalseSubState, HasAlarmSuppressionGroup, AlarmGroupMember, and AlarmSuppressionGroupMember. These are the building blocks that let a server describe how states relate to each other and how alarms are grouped or suppressed.
Clause 5.5 defines ConditionType and its methods: Disable, Enable, AddComment, ConditionRefresh, and ConditionRefresh2. For a real system, this means a client can enable or disable a condition, attach an operator comment, and request a refreshed state picture.
Alarm control and state handling
Clause 5.6 defines DialogConditionType and the Respond and Respond2 methods. Clause 5.7 defines AcknowledgeableConditionType and the Acknowledge and Confirm methods. This is the operator workflow part of the model: the server exposes the actions, and the client uses them to record awareness, response, and confirmation.
Clause 5.8 is the main alarm section. It defines AlarmConditionType, AlarmGroupType, AlarmSuppressionGroupType, Reset and Reset2, Silence, Suppress and Suppress2, Unsuppress and Unsuppress2, RemoveFromService and PlaceInService, GetGroupMemberships, ShelvedStateMachineType, and the alarm families LimitAlarmType, Exclusive Limit Types, NonExclusiveLimitAlarmType, Level Alarm, Deviation Alarm, Rate of change Alarms, Discrete Alarms, and DiscrepancyAlarmType. In practice, this gives implementers the standard alarm lifecycle actions and the major alarm categories used in industrial systems.
The document also adds alarm-related behavior that readers will notice in operation, such as shelving with a Comment parameter, optional severities for limit alarms, deadband properties for limit alarms, and a SupportsFilterRetain property for client filtering. These details matter because they directly affect operator display behavior and event traffic.
AddressSpace, classes, audit, and system state
Clause 5.9 defines ConditionClasses such as BaseConditionClassType, ProcessConditionClassType, MaintenanceConditionClassType, SystemConditionClassType, SafetyConditionClassType, HighlyManagedAlarmConditionClassType, TrainingConditionClassType, StatisticalConditionClassType, and TestingConditionClassType. These classes help users separate alarms by operational purpose, such as production, maintenance, or safety.
Clause 5.10 defines Audit Events for condition actions, including acknowledge, confirm, comment, shelving, suppression, silence, reset, and out-of-service handling. This is important for traceability, because alarm-related operator actions can be recorded and reviewed later.
Clause 5.11 defines refresh-related events: RefreshStartEventType, RefreshEndEventType, and RefreshRequiredEventType. Clause 6 explains AddressSpace organization with EventNotifier and source hierarchies, adding Conditions to the hierarchy, and placing Conditions in InstanceDeclarations and VariableType definitions.
Clause 7 describes System State & Alarms with HasEffectDisable, HasEffectEnable, HasEffectSuppressed, and HasEffectUnsuppressed. That lets a system state change influence many alarms at once. Clause 8 defines Alarm Summary and Objects through AlarmState Variable and AlarmMask, and Clause 9 defines Alarm Metrics through AlarmMetricsType, AlarmRateVariableType, and a Reset method.
What terms does SIST EN IEC 62541-9:2026 define?
SIST EN IEC 62541-9:2026 defines several practical terms that shape how alarm data behaves in OPC UA.
- Condition - a stateful object whose state can change and be reported as Events.
- AcknowledgeableCondition - a Condition that supports acknowledgement, and sometimes confirmation, by an operator.
- AlarmCondition - a Condition that represents an alarm and adds alarm behavior such as active state, shelving, and suppression.
- Branch - a stored previous state of a Condition that can remain relevant after a newer state exists.
- Retain - the flag that tells a client whether a Condition or Branch should still be kept in an alarm display.
- Shelving - a temporary operator action that removes an alarm from display without clearing the underlying condition.
- ConditionRefresh - the method used to request a renewed view of current condition states from the server.
Who uses SIST EN IEC 62541-9:2026?
SIST EN IEC 62541-9:2026 is used by OPC UA server and client developers, industrial automation vendors, system integrators, and alarm-management engineers. Quality, safety, and operations teams use it when they need alarm states, operator actions, and event histories to be modeled consistently.
It is also relevant in industrial process measurement and control, and in IT applications in industry, where OPC UA systems need to browse alarm hierarchies, filter events, map legacy OPC Classic A&E systems, and record audits for operator actions.
What changed in SIST EN IEC 62541-9:2026 from the previous edition?
SIST EN IEC 62541-9:2026 is the fourth edition and it cancels and replaces the third edition published in 2020. The document states that this edition is a technical revision.
The significant technical changes listed in the document are:
- addition of a Comment parameter to Alarm shelving methods
- addition of a method that lets a client get the members of a group
- addition of deadband properties for all limits in the limit AlarmType
- added text explaining that disabling alarms is no longer supported in ISA 18.2 and is kept here only for backward compatibility
- addition of optional severities for limit alarms
- addition of a new AlarmState variable type for graphics displays
- addition of SupportsFilterRetain to improve client filtering
- removal of ConditionSubClassId and ConditionSubClassNames from the ConditionType definition because they are now defined in BaseEventType
Which standards are used with SIST EN IEC 62541-9:2026?
SIST EN IEC 62541-9:2026 is designed in line with IEC 62682 and ISA 18.2, which provide the broader alarm-management context. The document also refers to several OPC UA companion parts used for event, address space, browsing, and state-machine behavior.
| Standard | Contribution in this document |
|---|---|
| IEC 62682 | Alarm-management concepts and mapping context for the A & C model |
| ISA 18.2 | Alarm-management alignment mentioned in the scope and revisions |
| IEC 62541-4 | Relative path syntax used for qualified area names |
| IEC 62541-5 | Event-related properties such as Message and Severity |
| IEC 62541-6 | String-encoded NodeId form used for qualified source names |
| IEC 62541-11 | Historical Events context used in the alarm-management discussion |
| IEC 62541-16 | FiniteStateMachineType foundation for the SystemState example |
What does the SIST EN IEC 62541-9:2026 document contain?
SIST EN IEC 62541-9:2026 contains state-machine figures, method definitions, event-type hierarchies, AddressSpace examples, and detailed mapping tables. It also includes annex material for localized state names, dialog response options, event-sequence examples, OPC Classic A&E mappings, and a SystemStateStateMachineType example.
For implementers, the practical value is in the tables that define parameters, result codes, and AddressSpace nodes for methods such as Acknowledge, Confirm, Reset, Suppress, and Shelve. For integrators, Annex D is especially useful because it shows how OPC Classic Alarm & Events concepts are mapped into OPC UA A & C.
Relations
- Effective Date
- 19-May-2026
- Effective Date
- 19-May-2026
- Refers
SIST EN IEC 62541-16:2026 - OPC unified architecture - Part 16: State machines (IEC 62541-16:2025) - Effective Date
- 19-May-2026
- Refers
SIST EN IEC 62541-3:2026 - OPC unified architecture - Part 3: Address space model (IEC 62541-3:2025) - Effective Date
- 19-May-2026
- Effective Date
- 19-May-2026
- Effective Date
- 19-May-2026
- Refers
SIST EN IEC 62682:2023 - Management of alarm systems for the process industries (IEC 62682:2022) - Effective Date
- 19-May-2026
- Refers
SIST EN IEC 62541-5:2026 - OPC unified architecture - Part 5: Information model (IEC 62541-5:2026) - Effective Date
- 19-May-2026
- Effective Date
- 19-May-2026
- Effective Date
- 19-May-2026
- Effective Date
- 30-Jun-2026
- Referred By
SIST EN IEC 62769-1:2023 - Field Device Integration (FDI®) - Part 1: Overview (IEC 62769-1:2023) - Effective Date
- 30-Jun-2026
- Effective Date
- 30-Jun-2026
- Effective Date
- 30-Jun-2026
- Effective Date
- 30-Jun-2026
Get Certified
Connect with accredited certification bodies for this standard

BSI Group
BSI (British Standards Institution) is the business standards company that helps organizations make excellence a habit.
DVS-ZERT GmbH
German welding certification society.
CARES (UK Certification Authority for Reinforcing Steels)
UK certification for reinforcing steels and construction.
Sponsored listings
Frequently Asked Questions
SIST EN IEC 62541-9:2026 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "OPC Unified Architecture - Part 9: Alarms and Conditions (IEC 62541-9:2026)". This standard covers: IEC 62541-9:2026 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. Other aspects of alarm systems like alarm philosophy, life cycle, alarm response times, alarm types and many other details are captured in standards such as IEC 62682 and ISA 18.2. The Alarms and Conditions Information Model in this document, is designed in accordance with IEC 62682 and ISA 18.2. Annex C specifies a recommended mapping between OPC Classic Alarm & Events (A&E) servers to the model described in this document. Annex A describes recommended localized names for Alarm states. Annex B describes examples (e.g. Event sequences, Alarm areas in AddressSpace). This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) addition of "Comment" parameter to Alarm shelving methods; b) addition of method that allows a client to get the members of a group, since it is possible that the AddressSpace does not expose instances of alarms; c) addition of deadband properties for all limits in the limit AlarmType (from which all other types described in this issue are derived); d) addition of text explaining the disabling of alarms is no longer supported in ISA 18.2 and that it is maintained in this document for backward compatibility, but that it is recommended that Alarm not be disabled; e) addition of optional severities for limit alarms; f) addition of new AlarmState variable type that can be used to collect alarm information for displays on graphics; g) addition of SupportsFilterRetain property to improve Client filtering; h) removal of ConditionSubClassId and ConditionSubClassNames from the conditiontype definition since they are now defined in BaseEventType.
IEC 62541-9:2026 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. Other aspects of alarm systems like alarm philosophy, life cycle, alarm response times, alarm types and many other details are captured in standards such as IEC 62682 and ISA 18.2. The Alarms and Conditions Information Model in this document, is designed in accordance with IEC 62682 and ISA 18.2. Annex C specifies a recommended mapping between OPC Classic Alarm & Events (A&E) servers to the model described in this document. Annex A describes recommended localized names for Alarm states. Annex B describes examples (e.g. Event sequences, Alarm areas in AddressSpace). This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) addition of "Comment" parameter to Alarm shelving methods; b) addition of method that allows a client to get the members of a group, since it is possible that the AddressSpace does not expose instances of alarms; c) addition of deadband properties for all limits in the limit AlarmType (from which all other types described in this issue are derived); d) addition of text explaining the disabling of alarms is no longer supported in ISA 18.2 and that it is maintained in this document for backward compatibility, but that it is recommended that Alarm not be disabled; e) addition of optional severities for limit alarms; f) addition of new AlarmState variable type that can be used to collect alarm information for displays on graphics; g) addition of SupportsFilterRetain property to improve Client filtering; h) removal of ConditionSubClassId and ConditionSubClassNames from the conditiontype definition since they are now defined in BaseEventType.
SIST EN IEC 62541-9:2026 is classified under the following ICS (International Classification for Standards) categories: 25.040.40 - Industrial process measurement and control; 35.100.05 - Multilayer applications; 35.240.50 - IT applications in industry. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN IEC 62541-9:2026 has the following relationships with other standards: It is inter standard links to SIST EN IEC 62541-4:2026, SIST EN IEC 62541-11:2026, SIST EN IEC 62541-16:2026, SIST EN IEC 62541-3:2026, SIST EN IEC 62541-1:2026, SIST EN IEC 62541-7:2026, SIST EN IEC 62682:2023, SIST EN IEC 62541-5:2026, SIST EN IEC 62541-8:2026, SIST EN IEC 62541-6:2026, SIST EN IEC 62541-21:2026, SIST EN IEC 62769-1:2023, SIST EN IEC 62541-12:2020, SIST EN IEC 62769-6:2021, SIST EN 62769-6:2015. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.
SIST EN IEC 62541-9:2026 is associated with the following European legislation: Standardization Mandates: M/490. When a standard is cited in the Official Journal of the European Union, products manufactured in conformity with it benefit from a presumption of conformity with the essential requirements of the corresponding EU directive or regulation.
SIST EN IEC 62541-9:2026 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
SLOVENSKI STANDARD
01-november-2026
Enotna arhitektura OPC - 9. del: Alarmi in pogoji (IEC 62541-9:2026)
OPC Unified Architecture - Part 9: Alarms and Conditions (IEC 62541-9:2026)
OPC Unified Architecture - Teil 9: Alarme und Zustände (IEC 62541-9:2026)
Architecture unifiée OPC - Partie 9: Alarmes et conditions (IEC 62541-9:2026)
Ta slovenski standard je istoveten z: EN IEC 62541-9:2026
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 IEC 62541-9
NORME EUROPÉENNE
EUROPÄISCHE NORM June 2026
ICS 25.040.40; 35.100.05 Supersedes EN IEC 62541-9:2020
English Version
OPC unified architecture - Part 9: Alarms and Conditions
(IEC 62541-9:2026)
Architecture unifiée OPC - Partie 9: Alarmes et conditions OPC Unified Architecture - Teil 9: Alarme und Zustände
(IEC 62541-9:2026) (IEC 62541-9:2026)
This European Standard was approved by CENELEC on 2026-05-21. 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, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the
Netherlands, Norway, Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Türkiye 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: Rue de la Science 23, B-1040 Brussels
© 2026 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN IEC 62541-9:2026 E
European foreword
The text of document 65E/1056/CDV, future edition 4 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 national (dop) 2027-06-30
level by publication of an identical national standard or by endorsement
• latest date by which the national standards conflicting with the (dow) 2029-06-30
document have to be withdrawn
This document supersedes EN IEC 62541-9:2020 and all of its amendments and corrigenda (if any).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC shall not be held responsible for identifying any or all such patent rights.
This document has been prepared under a standardization request addressed to CENELEC by the
European Commission. The Standing Committee of the EFTA States subsequently approves these
requests for its Member States.
Any feedback and questions on this document should be directed to the users’ national committee. A
complete listing of these bodies can be found on the CENELEC website.
Endorsement notice
The text of the International Standard IEC 62541-9:2026 was approved by CENELEC as a European
Standard without any modification.
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments)
applies.
NOTE 1 Where 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.cencenelec.eu.
Publication Year Title EN/HD Year
IEC 62541-1 - OPC Unified Architecture - Part 1: EN IEC 62541-1 -
Overview and concepts
IEC 62541-3 - OPC Unified Architecture - Part 3: Address EN IEC 62541-3 -
Space Model
IEC 62541-4 - OPC unified architecture - Part 4: Services EN IEC 62541-4 -
IEC 62541-5 - OPC Unified architecture - Part 5: EN IEC 62541-5 -
Information Model
IEC 62541-6 - OPC unified architecture - Part 6: EN IEC 62541-6 -
Mappings
IEC 62541-7 - OPC Unified Architecture - Part 7: Profiles EN IEC 62541-7 -
IEC 62541-8 - OPC unified architecture - Part 8: Data EN IEC 62541-8 -
access
IEC 62541-11 - OPC Unified Architecture - Part 11: EN IEC 62541-11 -
Historical Access
IEC 62541-16 - OPC unified architecture - Part 16: State EN IEC 62541-16 -
Machines
IEC 62682 - Management of alarm systems for the EN IEC 62682 -
process industries
ISA 18.2-2009 - Management of alarm systems for the - -
process industries
IEC 62541-9 ®
Edition 4.0 2026-04
INTERNATIONAL
STANDARD
OPC unified architecture -
Part 9: Alarms and Conditions
ICS 25.040.40; 35.100.05 ISBN 978-2-8327-1193-4
IEC 62541-9:2026-04(en)
IEC 62541-9:2026 © IEC 2026
CONTENTS
FOREWORD . 10
1 Scope . 12
2 Normative references . 12
3 Terms, definitions, abbreviated terms and used data types . 13
3.1 Terms and definitions. 13
3.2 Abbreviated terms and symbols . 15
3.3 Used data types . 16
4 Concepts . 16
4.1 General . 16
4.2 Conditions . 16
4.3 Acknowledgeable Conditions . 18
4.4 Previous states of Conditions . 19
4.5 Condition state synchronization . 20
4.6 Severity, quality, and comment . 21
4.7 Dialogs . 21
4.8 Alarms . 21
4.9 Multiple active states . 23
4.10 Condition instances in the AddressSpace . 24
4.11 Alarm and Condition auditing . 25
4.12 Alarms in a system . 25
5 Model . 25
5.1 General . 25
5.2 Two-state state machines . 26
5.3 ConditionVariable . 28
5.4 ReferenceTypes . 29
5.4.1 General . 29
5.4.2 HasTrueSubState ReferenceType . 29
5.4.3 HasFalseSubState ReferenceType . 30
5.4.4 HasAlarmSuppressionGroup ReferenceType . 30
5.4.5 AlarmGroupMember ReferenceType . 31
5.4.6 AlarmSuppressionGroupMember ReferenceType . 31
5.5 Condition Model . 32
5.5.1 General . 32
5.5.2 ConditionType . 32
5.5.3 Condition and branch instances . 37
5.5.4 Disable Method. 37
5.5.5 Enable Method . 38
5.5.6 AddComment Method . 39
5.5.7 ConditionRefresh Method . 40
5.5.8 ConditionRefresh2 Method . 42
5.6 Dialog Model . 44
5.6.1 General . 44
5.6.2 DialogConditionType . 44
5.6.3 Respond Method . 46
5.6.4 Respond2 Method . 47
5.7 Acknowledgeable Condition Model . 48
5.7.1 General . 48
IEC 62541-9:2026 © IEC 2026
5.7.2 AcknowledgeableConditionType . 48
5.7.3 Acknowledge Method . 49
5.7.4 Confirm Method . 50
5.8 Alarm model . 52
5.8.1 General . 52
5.8.2 AlarmConditionType . 53
5.8.3 AlarmGroupType . 57
5.8.4 AlarmSuppressionGroupType . 58
5.8.5 Reset Method . 59
5.8.6 Reset2 Method . 60
5.8.7 Silence Method . 61
5.8.8 Suppress Method . 61
5.8.9 Suppress2 Method . 62
5.8.10 Unsuppress Method . 63
5.8.11 Unsuppress2 Method . 64
5.8.12 RemoveFromService Method . 65
5.8.13 RemoveFromService2 Method . 66
5.8.14 PlaceInService Method . 67
5.8.15 PlaceInService2 Method . 68
5.8.16 GetGroupMemberships Method . 69
5.8.17 ShelvedStateMachineType . 70
5.8.18 LimitAlarmType. 80
5.8.19 Exclusive Limit Types . 82
5.8.20 NonExclusiveLimitAlarmType . 86
5.8.21 Level Alarm . 88
5.8.22 Deviation Alarm . 89
5.8.23 Rate of change Alarms . 91
5.8.24 Discrete Alarms . 92
5.8.25 DiscrepancyAlarmType . 96
5.9 ConditionClasses . 97
5.9.1 Overview . 97
5.9.2 BaseConditionClassType . 98
5.9.3 ProcessConditionClassType . 98
5.9.4 MaintenanceConditionClassType . 98
5.9.5 SystemConditionClassType . 99
5.9.6 SafetyConditionClassType . 99
5.9.7 HighlyManagedAlarmConditionClassType . 100
5.9.8 TrainingConditionClassType . 100
5.9.9 StatisticalConditionClassType . 100
5.9.10 TestingConditionClassType . 101
5.10 Audit Events . 101
5.10.1 Overview . 101
5.10.2 AuditConditionEventType . 102
5.10.3 AuditConditionEnableEventType . 103
5.10.4 AuditConditionCommentEventType . 103
5.10.5 AuditConditionRespondEventType . 104
5.10.6 AuditConditionAcknowledgeEventType . 104
5.10.7 AuditConditionConfirmEventType . 104
5.10.8 AuditConditionShelvingEventType . 105
IEC 62541-9:2026 © IEC 2026
5.10.9 AuditConditionSuppressionEventType . 105
5.10.10 AuditConditionSilenceEventType . 106
5.10.11 AuditConditionResetEventType . 106
5.10.12 AuditConditionOutOfServiceEventType . 107
5.11 Condition Refresh related Events . 107
5.11.1 Overview . 107
5.11.2 RefreshStartEventType . 107
5.11.3 RefreshEndEventType . 108
5.11.4 RefreshRequiredEventType . 108
5.12 HasCondition Reference type. 109
5.13 Alarm & Condition status codes . 109
5.14 Expected A & C server behaviours . 110
5.14.1 General . 110
5.14.2 Communication problems . 110
5.14.3 Redundant A & C servers . 111
6 AddressSpace organisation . 111
6.1 General . 111
6.2 EventNotifier and source hierarchy . 111
6.3 Adding Conditions to the hierarchy . 112
6.4 Conditions in InstanceDeclarations . 113
6.5 Conditions in a VariableType . 114
7 System State & Alarms . 114
7.1 Overview . 114
7.2 HasEffectDisable . 114
7.3 HasEffectEnable . 115
7.4 HasEffectSuppressed . 115
7.5 HasEffectUnsuppressed . 116
8 Alarm Summary and Objects . 117
8.1 Overview . 117
8.2 AlarmState Variable . 118
8.3 AlarmMask . 119
9 Alarm Metrics . 120
9.1 Overview . 120
9.2 AlarmMetricsType . 120
9.3 AlarmRateVariableType . 122
9.4 Reset Method . 122
Annex A (informative) Recommended localized names . 124
A.1 Recommended state names for TwoState Variables . 124
A.1.1 LocaleId "en" . 124
A.1.2 LocaleId "de" . 124
A.1.3 LocaleId "fr" . 125
A.2 Recommended dialog response options . 126
Annex B (informative) Examples . 127
B.1 Examples for Event sequences from Condition instances . 127
B.1.1 Overview . 127
B.1.2 Server maintains current state only . 127
B.1.3 Server maintains previous states . 128
B.1.4 Server current-State Model with Suppression . 129
IEC 62541-9:2026 © IEC 2026
B.1.5 Example for On-Delay, Off Delay and ReAlarmTime . 131
B.2 AddressSpace examples . 131
Annex C (informative) Mapping from OPC A&E to OPC UA A & C . 134
C.1 Overview . 134
C.2 Alarms and Events COM UA wrapper . 134
C.2.1 Event areas . 134
C.2.2 Event sources . 135
C.2.3 Event categories . 135
C.2.4 Event attributes . 136
C.2.5 Event subscriptions . 136
C.2.6 Condition instances . 139
C.2.7 Condition Refresh . 139
C.3 Alarms and Events COM UA proxy . 139
C.3.1 General . 139
C.3.2 Server status mapping . 139
C.3.3 Event Type mapping . 140
C.3.4 Event category mapping . 140
C.3.5 Event Category attribute mapping . 141
C.3.6 Event Condition mapping . 144
C.3.7 Browse mapping . 144
C.3.8 Qualified names. 145
C.3.9 Subscription filters . 146
Annex D (informative) IEC 62682 Mapping . 148
D.1 Overview . 148
D.2 Terms . 148
D.3 Alarm records & State indications . 154
Annex E (Informative) System state . 155
E.1 Overview . 155
E.2 SystemStateStateMachineType. 156
Bibliography . 160
Figure 1 – Base Condition state model. 17
Figure 2 – AcknowledgeableConditions state model . 18
Figure 3 – Acknowledge State Model . 19
Figure 4 – Confirm acknowledge State model . 19
Figure 5 – Alarm state machine model . 22
Figure 6 – Typical Alarm Timeline example . 23
Figure 7 – Multiple active states example . 24
Figure 8 – ConditionType hierarchy . 26
Figure 9 – TwoStateVariable Illustration . 28
Figure 10 – Condition model . 32
Figure 11 – SupportsFilteredRetain process . 35
Figure 12 – DialogConditionType Overview . 44
Figure 13 – AcknowledgeableConditionType overview . 48
Figure 14 – AlarmConditionType Hierarchy Model. 52
Figure 15 – Alarm Model . 53
IEC 62541-9:2026 © IEC 2026
Figure 16 – Shelve state transitions . 71
Figure 17 – ShelvedStateMachineType model. 71
Figure 18 – LimitAlarmType . 80
Figure 19 – ExclusiveLimitStateMachineType . 83
Figure 20 – ExclusiveLimitAlarmType . 85
Figure 21 – NonExclusiveLimitAlarmType . 87
Figure 22 – DiscreteAlarmType Hierarchy . 93
Figure 23 – ConditionClass type hierarchy . 97
Figure 24 – AuditEvent hierarchy . 102
Figure 25 – Refresh Related Event Hierarchy . 107
Figure 26 – Typical HasNotifier Hierarchy . 112
Figure 27 – Use of HasCondition in a HasNotifier hierarchy . 113
Figure 28 – Use of HasCondition in an InstanceDeclaration . 113
Figure 29 – Use of HasCondition in a VariableType . 114
Figure 30 – AlarmSummary equipment example . 117
Figure 31 – AlarmSummary Equipment Object Example . 118
Figure B.1 – Single state example . 127
Figure B.2 – Previous state example . 128
Figure B.3 – SuppressedState and OutOfServiceState example . 130
Figure B.4 – Alarm example – On Delay, Off Delay, ReAlarmTime . 131
Figure B.5 – HasCondition used with Condition instances . 132
Figure B.6 – HasCondition reference to a Condition type . 133
Figure B.7 – HasCondition used with an instance declaration . 133
Figure C.1 – The type model of a wrapped COM AE server . 136
Figure C.2 – Mapping UA Event Types to COM A&E Event Types . 140
Figure C.3 – Example mapping of UA Event Types to COM A&E categories . 141
Figure C.4 – Example mapping of UA Event Types to A&E categories with attributes. 144
Figure E.1 – SystemState transitions . 155
Figure E.2 – SystemStateStateMachineType model . 156
Table 1 – Parameter types defined in IEC 62541-3 . 16
Table 2 – Parameter types defined in IEC 62541-4 . 16
Table 3 – TwoStateVariableType definition . 27
Table 4 – ConditionVariableType definition . 28
Table 5 – HasTrueSubState ReferenceType . 29
Table 6 – HasFalseSubState ReferenceType . 30
Table 7 – HasAlarmSuppressionGroup ReferenceType . 30
Table 8 – AlarmGroupMember ReferenceType . 31
Table 9 – AlarmSuppressionGroupMember ReferenceType . 31
Table 10 – ConditionType definition . 33
Table 11 – ConditionType Additional Subcomponents . 33
Table 12 – ConditionId SimpleAttributeOperand Illustration . 36
Table 13 – Disable result codes . 37
IEC 62541-9:2026 © IEC 2026
Table 14 – Disable Method AddressSpace definition . 38
Table 15 – Enable result codes . 38
Table 16 – Enable Method AddressSpace definition . 38
Table 17 – AddComment arguments . 39
Table 18 – AddComment result codes . 39
Table 19 – AddComment Method AddressSpace definition . 40
Table 20 – ConditionRefresh parameters . 40
Table 21 – ConditionRefresh result codes . 40
Table 22 – ConditionRefresh Method AddressSpace definition . 41
Table 23 – ConditionRefresh2 parameters . 42
Table 24 – ConditionRefresh2 result codes . 42
Table 25 – ConditionRefresh2 Method AddressSpace definition . 43
Table 26 – DialogConditionType definition . 44
Table 27 – DialogConditionType Additional Subcomponents . 45
Table 28 – Respond parameters . 46
Table 29 – Respond Result Codes . 46
Table 30 – Respond Method AddressSpace definition . 46
Table 31 – Respond2 parameters . 47
Table 32 – Respond2 Result Codes . 47
Table 33 – Respond2 Method AddressSpace definition . 47
Table 34 – AcknowledgeableConditionType definition . 48
Table 35 – AcknowledgeableConditionType Additional Subcomponents . 49
Table 36 – Acknowledge parameters . 49
Table 37 – Acknowledge result codes . 50
Table 38 – Acknowledge Method AddressSpace definition . 50
Table 39 – Confirm Method parameters . 51
Table 40 – Confirm result codes . 51
Table 41 – Confirm Method AddressSpace definition . 52
Table 42 – AlarmConditionType definition . 54
Table 43 – AlarmConditionType Additional Subcomponents . 55
Table 44 – AlarmGroupType definition . 58
Table 45 – AlarmSuppressionGroupType definition . 58
Table 46 – Reset result codes . 59
Table 47 – Reset Method AddressSpace definition . 59
Table 48 – Reset2 Method parameters . 60
Table 49 – Reset2 result codes . 60
Table 50 – Reset2 Method AddressSpace definition . 60
Table 51 – Silence result codes . 61
Table 52 – Silence Method AddressSpace definition . 61
Table 53 – Suppress result codes . 62
Table 54 – Suppress Method AddressSpace definition . 62
Table 55 – Suppress2 Method parameters . 63
Table 56 – Suppress2 Method AddressSpace definition . 63
IEC 62541-9:2026 © IEC 2026
Table 57 – Unsuppress result codes . 64
Table 58 – Unsuppress Method AddressSpace definition . 64
Table 59 – Unsuppress2 Method parameters . 64
Table 60 – Unsuppress2 Method AddressSpace definition . 65
Table 61 – RemoveFromService result codes . 65
Table 62 – RemoveFromService Method AddressSpace definition . 66
Table 63 – RemoveFromService2 Method parameters . 66
Table 64 – RemoveFromService2 result codes . 66
Table 65 – RemoveFromService2 Method AddressSpace definition . 67
Table 66 – PlaceInService result codes . 67
Table 67 – PlaceInService Method AddressSpace definition . 68
Table 68 – PlaceInService2 Method parameters . 68
Table 69 – PlaceInService2 result codes . 68
Table 70 – PlaceInService2 Method AddressSpace definition . 69
Table 71 – GetGroupMemberships result codes . 69
Table 72 – GetGroupMemberships Method AddressSpace definition . 70
Table 73 – ShelvedStateMachineType definition . 72
Table 74 – ShelvedStateMachineType Additional References . 73
Table 75 – ShelvedStateMachineType Attribute values for child Nodes . 74
Table 76 – Unshelve result codes . 74
Table 77 – Unshelve Method AddressSpace definition . 75
Table 78 – Unshelve2 Method parameters . 75
Table 79 – Unshelve2 result codes . 75
Table 80 – Unshelve2 Method AddressSpace definition . 76
Table 81 – TimedShelve parameters . 76
Table 82 – TimedShelve result codes . 76
Table 83 – TimedShelve Method AddressSpace definition . 77
Table 84 – TimedShelve2 parameters . 77
Table 85 – TimedShelve2 result codes . 78
Table 86 – TimedShelve2 Method AddressSpace definition . 78
Table 87 – OneShotShelve result codes . 79
Table 88 – OneShotShelve Method AddressSpace definition . 79
Table 89 – OneShotShelve2 Method parameters . 79
Table 90 – OneShotShelve2 result codes . 79
Table 91 – OneShotShelve2 Method AddressSpace definition . 80
Table 92 – LimitAlarmType definition . 81
Table 93 – ExclusiveLimitStateMachineType definition . 83
Table 94 – ExclusiveLimitStateMachineType Additional References . 84
Table 95 – ExclusiveLimitStateMachineType Attribute values for child Nodes . 84
Table 96 – ExclusiveLimitAlarmType definition . 86
Table 97 – NonExclusiveLimitAlarmType definition . 88
Table 98 – NonExclusiveLimitAlarmType Additional Subcomponents . 88
Table 99 – NonExclusiveLevelAlarmType definition . 89
IEC 62541-9:2026 © IEC 2026
Table 100 – ExclusiveLevelAlarmType definition . 89
Table 101 – NonExclusiveDeviationAlarmType definition . 90
Table 102 – Exclusive
...



