alarm_analysis:cross_data_updates
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
alarm_analysis:cross_data_updates [2022/09/22 13:03] – su | alarm_analysis:cross_data_updates [2024/06/05 09:17] (current) – su | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Cross Data Updates ====== | ====== Cross Data Updates ====== | ||
- | The Alarm Analysis event sink is where import rules are configured. | + | The Alarm Analysis event sink is where import rules are configured. Events are processed in a strict FIFO (First In - First Out) sequence. During this phase, the event is parsed purely on the content of the individual record. |
- | Events are processed in a strict FIFO (First In - First Out) sequence. During this phase, the event is parsed purely on the content of the individual record. | + | However, there is a secondary phase called |
+ | |||
+ | Cross Data checks run independently of the import flow. If enabled, the Cross Data Checks poll the Alarm Analysis indices for new entries. If found, the process then seeks out related records and performs calculations. | ||
Cross Data Updates include the following functions... | Cross Data Updates include the following functions... | ||
Line 14: | Line 16: | ||
===== Dupe Check ===== | ===== Dupe Check ===== | ||
- | An event is considered a dupe if if shares the following properties with another event: | + | An event is considered a dupe if it shares the following properties with another event: |
- | * Timestamp | + | |
- | * EventType | + | * EventType |
- | * AlarmIdentifier | + | * AlarmIdentifier |
- | * Paramater | + | * Paramater |
- | * Priority | + | * Priority |
- | If a dupe is identified, the Event Type is updated with a "_Dupe" | + | If a dupe is identified, the Event Type is updated with a “_Dupe” suffix. The event remains in the Sequence of Events, but is removed from any KPIs. |
===== Compile Alarm Properties ===== | ===== Compile Alarm Properties ===== | ||
- | This process matches up ALMs and RTNs and calculates alarm duration, on-to-on | + | This process matches up ALMs and RTNs and calculates alarm duration, on-to-on |
- | + | ||
+ | * On to Off (IO): Time from the alarm coming on to it going off (how long it is on) | ||
+ | * Off to On (OI): Time from alarm going off to it next coming on (how long it is off) | ||
+ | * On to On (II): Time from the alarm coming on to it next coming on (time between alarms) | ||
Line 39: | Line 42: | ||
This can only be calculated if the Alarm Analysis record has properties: | This can only be calculated if the Alarm Analysis record has properties: | ||
- | * EventType: INT (intervention) | + | |
- | * OpAction: DISABLE_ON or DISABLE_OFF | + | * OpAction: DISABLE_ON or DISABLE_OFF |
Line 49: | Line 52: | ||
This can only be calculated if the Alarm Analysis record has properties: | This can only be calculated if the Alarm Analysis record has properties: | ||
- | * EventType: INT (intervention) | + | |
- | * OpAction: MANUAL_ON or MANUAL_OFF | + | * OpAction: MANUAL_ON or MANUAL_OFF |
alarm_analysis/cross_data_updates.txt · Last modified: 2024/06/05 09:17 by su