ConditionSource – OPC Unified Architecture – Part 9: Alarms & Conditions

OPC Unified Architecture – Part 9: Alarms & Conditions

v1.05.06

1Scope
2Normative references
3Terms, definitions, and abbreviations
- 3.1Terms and definitions
- 3.2Abbreviations and symbols
4Concepts
5Model
6AddressSpace organisation
7System State & Alarms
8Alarm Summary and Objects
9Alarm Metrics
Annex ARecommended localized names (Informative)
- A.1Recommended state names for TwoState Variables
- A.2Recommended dialog response options
Annex BExamples (Informative)
- B.1Examples for Event sequences from Condition instances
- B.2AddressSpace examples
Annex CMapping to EEMUA (Informative)
Annex DMapping from OPC A&E to OPC UA A & C (Informative)
Annex E– IEC 62682 Mapping
Annex FSystem State (Informative)
- F.1Overview
- F.2SystemStateStateMachineType
Bibliography

3.1.9 ConditionSource

element which a specific Condition is based upon or related to

Note 1

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.