Alert routing built for distribution operations — not IT teams
Multi-channel routing, noise suppression, acknowledgment tracking, and escalation paths that match how your operations team actually runs. SCADA and PagerDuty integration included.
"event_id": "evt_2026031422140001",
"severity": "critical",
"segment": "SEG-0447",
"trigger": "turbidity_sustained",
"value": 0.81 // NTU, 180s confirmed
"routed_to": "oncall_pager",
"ack_required_by": "2026-03-14T02:27:03Z",
"escalation_path": [
"operator → supervisor → emergency"
]Every channel your team already uses
Watsynq connects to your existing operational toolchain. No new mobile apps required for field staff.
Email & SMS
Configurable per-user alert delivery preferences. Severity threshold filters let junior operators receive warnings while supervisors receive only confirmed critical events.
PagerDuty Integration
Native PagerDuty API integration. Watsynq creates and resolves PagerDuty incidents in sync with alert state — no manual incident management or double-ticketing.
SCADA Write-back
Confirmed high-severity alerts can write alert codes back to OSIsoft PI or other SCADA historians. Keep your existing control room display synchronized without manual cross-referencing.
Microsoft Teams & Slack
Structured alert messages posted to dedicated channels. Inline acknowledge buttons let supervisors ACK directly from Teams or Slack without opening the Watsynq dashboard.
Webhook API
Outbound webhooks for any custom integration — city GIS dashboards, emergency management platforms, or regional authority notification systems.
Acknowledgment Tracking
Full audit trail: who received, who acknowledged, how long to first acknowledgment, escalation count. Required for some regulatory compliance and post-incident review.
Fewer false alerts. More signal.
Raw sensor threshold crossings are not the same as actionable events. Watsynq applies a configurable confirmation window, cross-parameter correlation check, and neighboring-segment context filter before triggering any alert.
Exceedance must persist for a configurable duration (default: 120 seconds) before alert is created. Eliminates single-sample sensor glitches and brief hydraulic transients.
When turbidity spikes without a corresponding pressure event or conductivity change, the alert is downgraded from "critical" to "informational" — likely a sensor calibration drift.
Maintenance windows, valve exercise operations, and planned flushing events can be pre-scheduled to suppress expected turbidity events.
Alert rate comparison
Based on Sonoran Metro Water pilot — 12-segment network, 90-day observation
We'll walk through alert configuration for your network topology.
45-minute technical walkthrough with the engineering team. No slides — we use your network data if you can share it.