Configure Metasys to send alarm notifications via email, SMS, or other channels to ensure critical issues reach the right people promptly.
| Component | Function |
|---|---|
| Alarm Source | Equipment/points generating alarms |
| Notification Class | Rules for who gets notified |
| Delivery Channel | Email, SMS, push notification |
| Schedule | When notifications are active |
| Escalation | Backup if primary contact unavailable |
Alarm Occurs → Matches Class → Active Schedule? → Send Notification → Log Delivery
smtp.company.commetasys@company.comCustomize what's included in notifications:
| Field | Example |
|---|---|
| Subject | [CRITICAL] High Space Temp - Room 301 |
| Equipment | AHU-01 |
| Point | Zone Temperature |
| Value | 82°F (Limit: 78°F) |
| Time | 2024-01-15 14:32:05 |
| Location | Building A, Floor 3 |
Use placeholders for dynamic content:
{AlarmMessage} - Alarm description{EquipmentName} - Source equipment{Value} - Current value{Timestamp} - When alarm occurred{Location} - Space/buildingDifferent contacts for different times:
| Time | Primary Contact | Backup |
|---|---|---|
| Business hours | Building Engineer | Supervisor |
| After hours | On-call Tech | Answering Service |
| Weekends | Duty Manager | Emergency Line |
If primary doesn't acknowledge:
| Priority | Recipients | Channel |
|---|---|---|
| Critical | All + On-call | Email + SMS |
| High | Engineers | |
| Medium | Operators | Email digest |
| Low | Logged only | None |
| Strategy | Implementation |
|---|---|
| Proper alarm limits | Tune thresholds to avoid nuisance |
| Appropriate priorities | Reserve Critical for true emergencies |
| Time delays | Require condition to persist |
| Consolidation | Group related alarms |
Maintain records of: