Step 1: Create - Navigate to Alarms → Groups
- Add Verify pre-defined groups exist:
Critical Alarms:
- Name:
Critical
- Priority: 1
- Acknowledgment: Required
- Sound: Critical.wav
- Color: Red
Warnings:
- Name:
Warnings
- Priority: 3
- Acknowledgment: Optional
- Color: Yellow
Group | AckRequired | LogEvents |
Critical | Yes | ActiveAck |
Warning | No | Active |
AuditTrail | No | Active |
Modify Critical group:
- Open the ComboBox Sound field
- Select Exclamation
- Press Enter
2. Create
Step 2: Define Alarm Items
- Go to Alarms → Items
- Create Add high temperature alarm:
High Temperature:
- Name:
Tank1_HighTemp
- Group:
Critical
- Tag:
Tank1_Temperature
- Condition: Greater than
- Limit: 85
- Message: "Tank 1 temperature exceeds limit"
- Deadband: 2
Low Level:
- Name:
Tank1_LowLevel
- Group:
Warnings
- Tag:
Tank1_Level
- Condition: Less than
- Limit: 10
- Message: "Tank 1 level low"
For rate-of-change monitoring:
- Name:
Pressure_Deviation
- Type: Deviation
- Tag:
Line_Pressure
- Setpoint Tag:
Pressure_Setpoint
- Deviation: ±10
- Time: 60 seconds
Step 4: Set Up Email Notifications
- Navigate to Alarms → Groups
- Select group → Email settings:
Property | Value |
---|
TagName | TankFarm/Tank1/Temp |
Condition | HiHi |
Limit | 85 |
Group | Critical |
Message | Tank 1 Critical Temperature: {Tag.TankFarm/Tank1/Temp}°C |
Priority | 100 |
- Add low level alarm:
Property | Value |
---|
TagName | Tag.ankFarm/Tank1/Level |
Condition | Lo |
Limit | 20 |
Group | Warning |
Message | Tank 1 Low Level Warning |
Priority | 50 |
- Navigate to Alarms → Areas
- Create hierarchy:
Assign alarms to areas:
- Return to Alarms → Items
- Set Area =
Plant_Production_Tank1
for both alarms - Right click the columns to enable visibility for the Area column
4. Enable
Step 5: Configure Audit Trail
- Go to Alarms → Global Settings
- In Audit Trail section: logging
- Audit Trail
- Enable options:Login/Logout: Yes
- User Logon/Logoff
- Tag Changes
: Yes - Alarm Acknowledgments: Yes
- Configuration Changes: Yes
- Set storage:
- Database: SQL Server
- Table: AuditTrail
- Retention: 365 days
Step 6: Create Alarm Areas
For plant organization:
- Alarms → Areas
- Create hierarchy:
Plant/
??? Production/
? ??? Line1/
? ??? Line2/
??? Utilities/
??? Boilers/
??? Compressors/
- Assign alarms to areas
Step 7: Test Alarms
- Start Runtime
- Open Alarms → Online
- Force tag values to trigger alarms
- Verify:
- Alarm appears in list
- Color coding correct
- Sound plays
- Email sent
Step 8: Alarm Summary Display
Create operator display:
- Displays → New
- Add AlarmViewer control
- Configure:
- Show: Active alarms
- Columns: Time, Area, Message, Value
- Filter: By area or priority
- Allow: Acknowledge, silence
FDA 21 CFR Part 11 Setup
For compliance:
- Electronic signatures on acknowledgments
- Audit trail cannot be disabled
- User authentication required
- Time synchronization enabled
- Data integrity checksums
Best Practices
- Use consistent naming conventions
- Set appropriate priorities (1-5)
- Include clear messages
- Test all alarm conditions
- Document alarm philosophy
- Regular alarm rationalization
Next Steps
[Historian] - Store alarm history[Reports Module] - Alarm reports[Security Module] - User permissions- Operator Actions
- Custom Messages
- Configure database retention:
- Life Time: 2555 days (7 years for FDA compliance)
5. Create Alarm Display
- Navigate to Displays → New
- Name:
AlarmMonitor
- Add AlarmViewer control from toolbox
- Double Click the button and go to Settings
- Configure:
- List: OnlineAlarms
- Columns: Time, TagName, Message, Value, Group
- Add AlarmArea control for navigation
- Save display
6. Test Alarms
- Start Runtime (Runtime → Startup)
- Open Alarms→ Alarms Monitor
- Simulate alarm conditions by changing tag values
- Verify the alarms showing in the alarm viewer
7. Verify Audit Trail
- Change AlarmViewer List to
AuditTrail
- Verify logged events:
- User login
- Alarm triggers
- Acknowledgments
- Tag changes
Excerpt Include |
---|
| Alarms Module |
---|
| Alarms Module |
---|
nopanel | true |
---|
|