3.5 KiB
3.5 KiB
| name | description |
|---|---|
| alarm-management | CI Server R1.03 ALARM Service and alarm engineering. Use when the user wants to switch on alarms for an item (alarming, limits, HIGH / HIGH HIGH / LOW alarms, alarm state, priority, alarm text), set up acknowledgement types (manual / automatic acknowledgement, ack matrix, ALARM_ACK_DF), areas of interest (AOI), alarm selection areas (ASA, alarm filter expressions, compile), delayed or repeated alarms, first-out groups, alarm collections (first-up), read or acknowledge current alarms and alarm history (ALARM_CURRENT, ALARM_CHRONO), generate a test or informational event, check the alarm kernel or storage (ALM, ALH, ALDPRT, almdbg, alhdbg, alm.sup, alh.sup, aldprt.sup), configure alarm e-mail / SMS notification (alnmgr, alnsmtp), alarm shelving (asbman), alarm sound (aldaco), alarm counting (aldcnt), external alarms (EAL, OPC UA alarms, CENTUM VP Vnet alarms) or analyse alarm performance (ASPA, alarm floods, KPIs, EEMUA 191, ISA 18.2). Sources IM 36K10L15-01EN, IM 36K10C20-01EN, IM 36K10E30-01EN. |
Alarm management (R1.03)
Background: knowledge/manuals/IM36K10L15-01EN.md (kernel, events, mechanisms, setup files,
debuggers), IM36K10C20-01EN.md (Engineering Module forms, filters, grouping, shelving,
notifications, external alarms), IM36K10E30-01EN.md (ASPA tool and KPI targets). Item limits
and statuses: skill item-engineering. OPC UA alarm sources: skill data-access.
Rules:
- Run
system-checkfirst; follow the user's chosen way of working. - Alarms reach operators. Switching alarming on or off, changing acknowledgement types, or acknowledging alarms on a running plant changes what operators see: only with the user's approval. Changing an item's alarm settings also auto-acknowledges a pending return to normal (L15 summary, C20 §A2).
- Writing a value to force a test alarm changes live data (
system-management, taskread-write-item.md): only on test items, and restore the value. almdbgoptions 3, 13, 15, 17, 19, 20, 25, 26 andalhdbg3, 4 change or stop things: never without approval. Read-only options are listed intasks/alarm-checks.md.- Setup files (
alm.sup,alh.sup,aldprt.sup,aln*.sup,asbman.sup,wfladi.sup) need admin rights and a restart: hand changes to the user (skillportal-setup, taskchange-setup-file.md).
| Task | File | Status |
|---|---|---|
| Acknowledgement type, area of interest, alarm selection area by quick load; compile check | tasks/alarm-definitions.md |
verified |
| Switch on alarming for an item; delay / repeat; test an alarm; read and acknowledge current alarms and history | tasks/item-alarming.md |
verified |
| Read-only checks: alarm processes, destinations, statistics, item alarm parameters, storage group, setup files; generate an INFO event | tasks/alarm-checks.md |
verified |
| First-out groups, alarm collections (first-up, status/ack/reset items) | C20 summary §A6 | from docs |
| Alarm overviews, priority labels, link display, shelving | C20 summary §A3, §A9, §A10 | from docs (needs displays, phase 10) |
| E-mail / SMS notification | L15 summary §10, C20 §A11 | from docs (needs an SMTP server without authentication) |
Acoustic (aldaco) and count (aldcnt) destinations, split storage processes |
L15 summary §7, §8 | from docs |
| External alarms (EAL) from OPC UA servers or CENTUM VP | C20 summary part B | from docs (no A&C source / Vnet on the test system) |
| Alarm performance analysis (ASPA) | E30 summary | from docs |