SCS reads alarms straight from your SCADA system. It calls, texts and emails your on-call people in order, and keeps escalating until someone acknowledges. It runs on your own servers, and it is in round-the-clock service at a major U.S. pipeline operator.
How SCS works
Nobody has to watch a screen at 2 a.m. for SCS to do its job. It works the same way on every alarm, day or night.
SCS reads each new alarm from your SCADA system within seconds. An alarm leaves the queue only after its callout has been built, so none is dropped.
From your personnel data it works out who to contact, on which phone or email, and in what order. People marked away are skipped.
Voice calls, texts and emails go out on schedule. Each one carries a short alert number that ties the reply to this alarm.
The first acknowledgement stops the callout for everyone. If nobody answers, SCS moves down the list and can finish with your control room.
What you get
SCS pairs a proven alarm callout engine with personnel management, so the right person hears about the right alarm, and you can prove it afterward.
Proven on ClearSCADA / Geo SCADA. Other SCADA systems can feed SCS through a standard alarm table in SQL Server. No email gateways, no fragile scripts.
Calls read the alarm aloud. Texts and emails carry the same details: point, status, time and message, plus the alert number.
Press 1 on the call. Reply to the text with the alert number. Or call in and key your employee ID and alert numbers. There are no links to click, so an email scanner can't acknowledge an alarm by accident.
No answer? SCS works down your call list on schedule, repeats the list if you want it to, and can finish with your control room as the backstop.
Who was contacted, who acknowledged, and when, alarm by alarm. Ready for your alarm-management reviews and incident investigations.
A companion watchdog service restarts SCS automatically if any part stops responding. Larger systems run several SCS servers, each covering its own region.
Personnel management
A callout is only as good as the list behind it. SCS keeps that list where it belongs: with the people who run your operation.
Manage everything that decides who gets called, in one place.
We customize SCS to connect to it. Your people and on-call data stay in the system you already use, and SCS works from it, so nobody keeps two lists.
Why SCS
Mass-notification platforms were built to broadcast. SCS was built for one job: getting a SCADA alarm to a person who will act on it.
Connecting a general notification platform to SCADA usually means an email gateway or custom scripts between your alarms and your people, and someone has to keep them running. SCS reads the alarm itself.
SCS runs next to your SCADA system, on hardware you control, instead of in a vendor's cloud.
Keypad and text-reply acknowledgements are tied to the person and the alarm. Nothing is confirmed because a link preview opened a page.
We'll tell you what connecting SCS to your SCADA and personnel systems actually takes. If it isn't worth doing, we'll say so.
Also from ComTek
We're specialists in industrial control and in the phone systems that run a business, and we stand behind what we build.
Design, integration and long-term support for the control systems that SCS listens to.
VoIP phone systems and interactive voice response: automated attendants, reminders and call flows that work.
Request a demo
Tell us what SCADA you run and how you call people out today. We'll come back with a straight, buildable plan, or an honest “here's why that's not worth it.”
We read every message. A real person gets back to you.