Creating Alarms
This guide shows you how to configure alarm levels, categories, groups, and alarm points.
When to Use This Page
Use this page when:
- live values already work in the project
- you are ready to define abnormal conditions
- operators need clear alarm messages instead of raw tag changes
Before You Start
Make sure:
- the relevant tags are already tested
- you know the alarm thresholds or logical conditions
- you are willing to start with a small alarm set instead of designing the full alarm philosophy on day 1
What You Will Complete
After this page, you should be able to:
- create severity levels, categories, and groups
- define a few practical alarm points
- record alarm history appropriately
Recommended First Alarm Set
For a first project, start with two or three alarms:
| Alarm Name | Example condition | Suggested level | Suggested category |
|---|---|---|---|
Temperature_High | {Temperature} > 80 | High | Temperature |
Pressure_Low | {Pressure} < 0.8 | Medium | Pressure |
Device_Comm_Loss | {Dev_<ChannelName>_State} == false | Critical | Communication |
If the project uses only internal tags, configure the first two alarms first and add the communication alarm later.
Day-1 Quick Path
For the first useful alarm setup, keep the work small:
- create only the levels you need now, such as
HighandMedium - create one category group and a few categories such as
Temperature,Pressure, andCommunication - create one alarm group such as
Starter_Alarms - add two practical alarm points such as
Temperature_HighandPressure_Low - save and test the alarm conditions
Alarm history recording and import/export are useful later, but they are not required for the first success milestone.
Configure Alarm Levels
Alarm levels indicate the severity of an alarm. Define levels that match your operational priorities.
Step 1: Open Alarm Level Configuration
- Navigate to Alarm Management
- Click Alarm Levels button
- The Alarm Level configuration dialog opens
📷 [UG-ALARM-CREATE-01] Alarm Level configuration dialog
Step 2: Create Alarm Levels
- Click Add to create a new level
- Enter a level name (e.g.,
Critical,High,Medium,Low) - Repeat for all required levels
- Click Save
Common Alarm Level Schemes:
| Level | Use Case | Color Convention |
|---|---|---|
| Critical | Safety hazards, equipment damage risk | Red |
| High | Process deviations requiring immediate action | Orange |
| Medium | Conditions requiring attention within hours | Yellow |
| Low | Informational, no immediate action needed | Blue |
Step 3: Manage Alarm Levels
Edit a Level:
- Click the level name to edit
- Modify the name
- Click Save
Delete a Level:
- Select one or more levels (checkbox)
- Click Delete
- Confirm deletion
Search Levels:
- Enter a level name in the search box
- Click Search
⚠️ Caution: Deleting a level that is assigned to alarms will cause those alarms to lose their level assignment.
Configure Alarm Categories
Alarm categories classify alarms by type for statistical analysis and filtering.
Step 1: Open Alarm Category Configuration
- Navigate to Alarm Management
- Click Alarm Categories button
- The Alarm Category configuration dialog opens
📷 [UG-ALARM-CREATE-02] Alarm Category configuration dialog showing category groups
Step 2: Create Category Groups
Category groups organize related categories (e.g., Process Alarms, Equipment Alarms, Safety Alarms).
- Click Add to create a new category group
- Enter a group name
- Click Save
Step 3: Create Categories within Groups
- Select a category group
- Click Manage (operations button)
- In the Category Management dialog:
- Click Add to create a category
- Enter a category name (e.g.,
Temperature,Pressure,Communication) - Repeat for all categories
- Click Save
📷 [UG-ALARM-CREATE-03] Category Management dialog showing categories within a group
Example Category Structure:
📁 Process Alarms
└─ Temperature
└─ Pressure
└─ Flow
📁 Equipment Alarms
└─ Motor Fault
└─ Valve Failure
└─ Sensor Error
📁 Safety Alarms
└─ Emergency Stop
└─ Fire Detection
└─ Gas Leak
Step 4: Manage Categories
Edit a Category:
- Click the category name to edit
- Modify the name
- Click Save
Delete a Category:
- Select one or more categories (checkbox)
- Click Delete
- Confirm deletion
Reorder Category Groups:
- Drag a category group to a new position
- Click Save
Create Alarm Groups
Alarm groups organize alarms by equipment, line, or function.
Step 1: Create a Group
- Navigate to Alarm Management
- Click Add Alarm Group
- Enter a group name (e.g.,
Starter_Alarms,Monitoring_Alarms) - Click Confirm
📷 [UG-ALARM-CREATE-04] Add Alarm Group dialog
Step 2: Organize Groups with Folders
- Create folders to organize groups
- Drag alarm groups into folders
Recommended Structure:
📁 Process
└─ 📂 Starter_Alarms
└─ 📂 Threshold_Alarms
📁 Equipment
└─ 📂 Status_Alarms
📁 Communication
└─ 📂 Channel_State_Alarms
Step 3: Manage Alarm Groups
Rename a Group:
- Double-click the group name
- Or click the operations button (⋮) → Rename
- Enter a new name
- Press Enter
Delete a Group:
- Click the operations button (⋮) → Delete
- Confirm deletion
⚠️ Caution: Deleting a group also deletes all alarms within it.
Search Groups:
- Enter a group name in the search box
- Matching groups are highlighted
Create Alarm Points
Alarm points define the conditions that trigger alarms.
Step 1: Add an Alarm Point
- Select an alarm group
- Click Add in the toolbar
- A new alarm row appears in the list
📷 [UG-ALARM-CREATE-05] Alarm point list with new row
Step 2: Configure Alarm Properties
| Property | Description | Example |
|---|---|---|
| Alarm Name | Unique identifier | Temperature_High |
| Alarm Message | Description shown to operators | Temperature exceeds safe limit |
| Trigger Condition | Logical expression | {Temperature} > 80 |
| Alarm Level | Severity level | High |
| Alarm Category | Classification (optional) | Temperature |
Step 3: Configure Trigger Condition
- Click the Trigger Condition button for the alarm
- The Expression Builder dialog opens
- Build a logical expression using tags and operators
📷 [UG-ALARM-CREATE-06] Expression Builder dialog with tag picker and operators
Expression Syntax:
| Operator | Description | Example |
|---|---|---|
> | Greater than | {Temperature} > 80 |
< | Less than | {Pressure} < 10 |
>= | Greater than or equal | {Level} >= 100 |
<= | Less than or equal | {Flow} <= 5 |
== | Equal to | {Status} == 1 |
!= | Not equal to | {Mode} != 0 |
&& | Logical AND | {Temp} > 80 && {Pressure} > 50 |
|| | Logical OR | {Alarm1} == 1 || {Alarm2} == 1 |
Common Alarm Patterns:
| Alarm Type | Expression | Description |
|---|---|---|
| High-High Limit | {X} >= 200 | Critical high threshold |
| High Limit | {X} >= 150 && {X} < 200 | Warning high threshold |
| Low Limit | {X} > 5 && {X} <= 10 | Warning low threshold |
| Low-Low Limit | {X} <= 5 | Critical low threshold |
| Range Violation | {X} < 10 || {X} > 90 | Outside acceptable range |
| Equipment Fault | {FaultCode} != 0 | Non-zero fault code |
| Communication Loss | {Dev_<ChannelName>_State} == false | Device disconnected |
💡 Tip: Use descriptive tag names in expressions for easier troubleshooting. For example,
{Temperature}is clearer than{Tag001}.
Step 4: Configure Alarm Constraint (Optional)
Alarm constraints prevent nuisance alarms by requiring the condition to persist for a minimum duration.
- Click the Alarm Constraint button for the alarm
- Enable the constraint
- Set the Duration (e.g.,
5 seconds,1 minute) - Click Confirm
📷 [UG-ALARM-CREATE-07] Alarm Constraint dialog with duration setting
When to Use Constraints:
- Noisy Sensors: Prevent alarms from flickering on/off due to sensor noise
- Transient Conditions: Ignore brief spikes that don't indicate real problems
- Startup Sequences: Avoid alarms during normal startup when values temporarily exceed limits
Example:
- Without constraint: Temperature briefly spikes to 201°C for 2 seconds → Alarm triggers
- With 5-second constraint: Temperature must stay above 200°C for 5 seconds → Alarm triggers only if sustained
Step 5: Save Alarm Configuration
- Click Save in the toolbar
- All changes are committed to the project
Advanced Alarm Administration
If the alarm points already work, you can stop here for the first-project path.
Use the remaining sections only when you need record-retention control, bulk reuse, or larger governance workflows.
Configure Alarm History Recording
By default, all alarms are recorded in the historical table when they recover. You can customize which alarms are recorded.
Step 1: Open Alarm Recording Configuration
- Navigate to Alarm Management
- Click Alarm Recording button
- The Alarm Recording dialog opens
📷 [UG-ALARM-CREATE-08] Alarm Recording dialog showing alarm list with checkboxes
Step 2: Select Alarms to Record
Record All Alarms (default):
- All checkboxes are selected
- All alarms are saved to the historical table when recovered
Record Specific Alarms:
- Uncheck alarms you don't want to record
- Only checked alarms will be saved to history
Filter Alarms:
- By Group: Select an alarm group from the dropdown
- By Level: Select an alarm level from the dropdown
- By Category: Select a category from the dropdown
- By Name: Enter text to search alarm names, messages, or conditions
- Show Selected Only: Display only checked alarms
Step 3: Save Recording Configuration
- Click Save
- The configuration is applied
💡 Tip: Disable history recording for low-priority informational alarms to reduce database size.
Import/Export Alarms
Export Alarms
- Select an alarm group
- Click Export in the toolbar
- Choose a save location
- An Excel file is created with all alarm configurations
Use Cases:
- Backup alarm configurations
- Share alarms between projects
- Document alarm settings for compliance
Import Alarms
- Select an alarm group
- Click Import in the toolbar
- Select an Excel file
- Alarms are imported based on Alarm Name:
- If the name exists: Update the alarm configuration
- If the name doesn't exist: Create a new alarm
⚠️ Caution: Alarm levels and categories referenced in the import file must already exist in the system.
Next Steps
- Displaying Alarms: Show alarms on views and create analysis dashboards
- Understanding Alarms: Review alarm concepts and data flow if you need to explain the model to others
- Creating Monitoring Views: Return to the view path to display alarm status for operators
- Alarms Reference: Return here later for expression syntax, best practices, and troubleshooting