Alarm

An Alarm defines a monitoring condition that triggers notifications when a process variable exceeds defined limits. Alarms are a key part of process safety and operator awareness, following ISA-18.2 alarm management principles.

💡 In pharmaceutical terms: Alarms protect your process by alerting operators when critical values go out of range — for example, when a CIP tank temperature exceeds the safe limit, or when WFI conductivity rises above specification. A well-configured alarm system is essential for GMP compliance and patient safety.

📋 Properties

Identity and Trigger

📏 Limit Configuration

🏷️ Classification

💬 Messaging

✅ Acknowledgement and Shelving

📡 Routing and Return-to-Normal

📊 Limit Types Explained

🏭 Example: A CIP tank temperature alarm might have: LL = 5 °C, L = 65 °C, H = 92 °C, HH = 98 °C — providing graduated warnings before reaching dangerous levels.

⚖️ Priority vs Severity

A Critical priority + Emergency severity alarm demands immediate operator action with maximum notification (horn, HMI popup, email, etc.). A Low priority + Log Only severity alarm is recorded for trending but does not interrupt the operator.

✅ Acknowledgement Rules

📖 How To: Configure Alarms for a CIP Tank

1. Open Module Data — Navigate to the Data panel in the Module Ribbon and open the Module Data window.

2. Go to the Alarms tab — Select the Alarms section.

3. Create alarm definitions — For each critical variable (temperature, pressure, level, flow), create alarm entries with appropriate limit types and setpoints.

4. Set priorities and severities — Use Critical/Emergency for safety-related alarms, Medium/Normal for process deviations, and Low/Advisory for informational alerts.

5. Configure acknowledgement — Safety-critical alarms should "Require operator acknowledgment". Routine alarms can use "Auto-acknowledge".

6. Set routing — Ensure critical alarms trigger Horn + HMI Popup + Historian Log. Lower-priority alarms may only need HMI Popup + Historian Log.

7. Add operator guidance — Fill in the "Operator Response" and "Consequence If Ignored" fields to help operators respond correctly.

♻️ Alarm Templates

A typical project repeats the same well-reasoned alarm again and again across whole equipment families. Every jacketed tank wants the same temperature alarm shape; every WFI loop wants the same conductivity alarm; every reactor wants the same pressure alarm. The only things that really change from one instance to the next are the tag, the setpoints, and the engineering units — the rationalization (priority, severity, classification, acknowledgement rule, shelving rule, routing, return-to-normal behaviour, message wording and operator guidance) stays the same.

Alarm templates let you capture a fully rationalized alarm once and stamp it out for every instance, so you never re-type the same reasoning. A template is a saved snapshot of an alarm together with a name, an optional category, and a description.

🖱️ The Alarms Toolbar

The bottom bar of the Alarms list is where the whole template workflow lives:

The split "+" button keeps the everyday "add a blank alarm" action one click away, while tucking the template choices behind the chevron so they are present but never in the way.

💾 Saving an Alarm as a Template

Whenever you realize an alarm you have just configured is going to be reused, you can promote it into a project-wide template:

1. Right-click the alarm row in the Alarms list and choose Save as Template… — or, while the alarm is open in the editor, click the Save as Template… button in the editor footer.

2. Give the template a name in the metadata prompt. The name must be unique within the project (matching is case-insensitive), so "High Temp" and "high temp" cannot both exist.

3. Optionally add a category and a description. A category such as "Temperature", "Conductivity", or "Pressure" groups related templates together; a description records when and why to use it.

4. Confirm. The template is added to the project library and is instantly available everywhere.

📋 Creating an Alarm From a Template

1. Click the chevron beside the "+" button and choose From Template…

2. The template picker opens — a searchable list of cards, each showing the template name, its category chip, and a coloured side bar that reflects the alarm's priority. Type in the search box to filter by name, category, tag, message, and more; use the up/down arrow keys to move through the list.

3. Pick a template (single click to select, double-click to choose it outright) and confirm.

4. The alarm editor opens pre-filled with the template's values. Change only the tag, the setpoints, and the units for this specific instance, then save. The result is a new, independent alarm in your module.

🧰 Editing Inside the Editor — the Templates Panel

While you are drafting an alarm, a Templates panel sits along the left edge of the alarm editor. It is a searchable card list — each card carries the priority side bar and category chip — so you can browse the library without leaving the form.

• Click any card to refill every field in the form with that template's snapshot. A banner reading "Applied template: name" appears so it is always clear what was just loaded.

• Applying a template while editing an existing alarm updates that alarm in place — it does not replace it with a different one — so you can re-rationalize an alarm against a template without losing its identity.

• Use the chevron toggle to collapse the panel to a thin rail when you want the full width for the form, and expand it again when you need it.

🗂️ The Manage Templates Window

The Manage Templates window is the home for curating your project's template library. It uses a master/detail layout: a searchable list of template cards on the left, and a full preview of the selected template on the right. The preview shows the snapshot's tag, units, condition, limit type and setpoints, deadband and delays, classification and severity, acknowledgement and shelving rules, routing, alarm message, and recommended operator response — everything you need to confirm a template before relying on it.

📖 How To: Roll Out a Temperature Alarm Across a Tank Farm

1. Configure one excellent temperature alarm on your first tank — for example on TT-101, with HH/H/L/LL setpoints, Critical priority, "Require operator acknowledgment", and Horn + HMI Popup + Historian Log routing, plus clear operator response text.

2. Right-click that alarm and choose Save as Template… Name it "Jacketed Tank High/Low Temp", category "Temperature".

3. Move to the next tank's module, click the "+" chevron, choose From Template…, and pick "Jacketed Tank High/Low Temp".

4. In the pre-filled editor, change only the tag (e.g. TT-201) and any setpoints that differ for this vessel, then save.

5. Repeat for every remaining tank. Each alarm carries the same rationalization while standing as its own independent definition.

🏭 Example: CIP Tank Temperature Alarms

🏭 Pharma context: During a CIP caustic wash, the solution must maintain a minimum temperature (typically 65-80 °C) for effective cleaning. The Low alarm warns operators when temperature drops below the minimum, while the Low-Low alarm indicates a failure that requires investigation and possible batch review.

🛠️ Common Operations

🔗 Related Pages

• 📋 Module Data — All module data types

• 🛡️ Interlock — Safety interlocks that can trigger on alarm conditions

• 🔁 Control Loop — Control loops with alarm integration

• 🧠 Algorithm Design — Condition logic that references alarms

• 📏 Parameter — Parameters used as alarm setpoints