Alarm & Trip Schedule — Final Self-Verification Checklist

Use this before the first formal review (internal/external). Aligns with Alarm Philosophy (EEMUA 191 / ISA-18.2), Control/Safeguarding Narratives, C&E Matrix, and client standards.

0 of 0 checked

Header & Document Control

Document number/title follow project numbering; “Alarm & Trip Schedule” clearly stated with unit/area.
Revision index and purpose (IFR/IFA/IFC/IFD) correct; prepared/checked/approved names and dates completed.
Project identifiers, location, confidentiality classification and document ownership correct per contract.
Unit system declared (SI/US); time base and timestamp resolution (SOE) stated and consistent across docs.
References listed with numbers & revisions (Alarm Philosophy, C&E Matrix, Control/Safeguarding Narrative, P&IDs, Instrument Index, I/O List, IPF/LOPA, Area Classification, Client Specs).

Scope & Structure

Scope covers BPCS alarms, SIS/PSD/ESD trips, and F&G alarms where applicable; boundaries and exclusions stated.
Required columns present and consistently populated (Tag, Service/Description, System, Area/Unit, Type, Setpoint & Units, Deadband/Hysteresis, Delay On/Off, Priority, Class/Category, Alarm Code, Annunciation Point/HMI Node, Latching/Reset, Inhibits/Shelving Allowed, References).
Unique identifier per row (e.g., Tag + Alarm Code) used; no duplicate rows for the same function/alarm state.
Grouping/sorting logic (by Unit/Area/System) applied and consistent with Alarm Philosophy; filters cleared before issue.

Tagging & Cross-References

Tag numbers and descriptions match Instrument Index and P&IDs; instrument types align with ISA-5.1/client legend.
Alarm/Trip codes follow the project coding standard (e.g., HI/HIHI/LO/LOLO, ROC, DEV) and are used consistently.
Trips cross-referenced to C&E Matrix and IPF/SIF register (function IDs, shutdown level); narrative clause numbers noted.
F&G alarms reference zone numbers, detector types, and voting per NFPA 72/client specification.

Alarm Definition Quality

Setpoint values and units correct; within engineering range (LRV–URV) with adequate margin from normal operation.
Deadband/hysteresis defined and appropriate to noise and process dynamics; alarm flood risk considered.
Delay On/Off times specified and justified; PV filtering/damping considered to avoid chattering.
Priority assigned per Alarm Philosophy (risk/response time); classes/categories (Safety, Environmental, Equipment, Operational, Information) set.
Alarm text concise and action-focused (verb–object); supplemental fields (Cause, Consequence, Operator Action) completed/linked to operator guidance.
Special alarms handled: Rate-of-Change (ROC), Deviation (DEV), Bad PV/Out-of-Service, Instrument Diagnostics (NAMUR NE 107) mapped to correct priority/class.
Mode-based behavior defined (startup/maintenance suppression, permissives); automatic re-enable rules documented.
Shelving/temporary suppressions allowed? Max durations and authorization levels stated; standing alarm targets considered.

Trip Definition Quality

Trip type identified (BPCS Interlock vs SIS/PSD/ESD vs F&G); shutdown level and safe state declared.
Setpoint(s) and voting logic (1oo1/1oo2/2oo3, median select) specified; degradation rules on fault defined.
Latching vs non-latching behavior, reset conditions and authority (CCR/local/key switch) documented; bumpless reset ensured.
Actuation delays (on/off) stated; energize-to-trip vs de-energize-to-trip consistent with philosophy and C&E.
Effects/final elements referenced (SDV/ESDV/BDV/Motor Trip); PST requirements and test method captured where applicable.
Bypass/inhibit policy, time-bound rules and annunciation defined; proof-test intervals/coverage referenced to SIF register.

Signals, Ranges & Diagnostics

Signal types and scaling recorded (AI/AO/DI/DO, 4–20 mA/HART, pulse, dry contact, bus); engineering ranges (LRV/URV) consistent with setpoints.
Sensor failure behaviors defined (open/short, saturation, diagnostics) with corresponding alarm/trip actions (e.g., fail high/low).
Diagnostics mapping (NE 107) to alarm classes/priorities agreed; bad PV handling and substitution rules documented.
PV filtering/damping values and scan rates considered against delay settings and process dynamics.

HMI/Annunciation & SOE

Annunciation points defined (CCR console, local panel, package HMI); HMI page/faceplate references included.
Alarm/trip messages conform to length/style rules; units included where helpful; abbreviations consistent with legend.
First-out indication for trips specified; SOE timestamp resolution and time sync method (NTP/PTP) stated.
Bypass/shelving/override banners and inhibit indicators defined; alarm colors/sounds per Philosophy.

Testing & Lifecycle

FAT/SAT procedures reference each row with test steps and acceptance criteria; simulation method defined for analog/logic tests.
Commissioning enable/disable lists prepared (startup suppressions, temporary inhibits) with re-enable plan and MOC linkage.
SIF proof tests and PST schedules referenced; data capture requirements (stroke time, response time) documented.
Change log maintained with rationale and impact assessment; export/backup format agreed (Excel/CSV/XML).

Data Integrity & Formatting

No duplicate rows or conflicting setpoints; unique keys validated; formulas/links in working file protected or removed before issue.
Formatting clean: critical fields not blank; consistent units/decimal places/significant figures; print area and page breaks set.
Version control and revision history updated; confidentiality/footer correct; transmittal list alignment verified.

Notes, Attachments & Final Polish

Open items, assumptions, and TBDs listed with owners and due dates; temporary settings flagged clearly.
Attachments referenced with document numbers/revisions (Alarm Philosophy, C&E, Narratives, F&G zoning, vendor data).
Grammar and clarity pass complete; operator-facing texts reviewed by operations; sample HMI screenshots if available.
Final sanity scan: each alarm/trip can be traced to a source or requirement within 60 seconds.

Quick Sign-Off

Preparer

Checker

Date

Use this checklist before issuing the Alarm & Trip Schedule for first formal review.

Alarm and Trip Settings – Comprehensive I&C Engineering Checklists for EPC Projects

Alarm & Trip Schedule — Final Self-Verification Checklist

Leave a Reply Cancel reply