Production
Discover machines and connections in a production line. Identify dependencies during maintenance and outages.
focusAlert
focusAlert collects events from machines, monitoring, SCADASCADA refers to systems for monitoring and remotely controlling industrial processes., or email and brings the right alarm to the right person, not to everyone.
An incidentAn IT security incident is an event in which the confidentiality, integrity, availability, or authenticity of IT or OT systems may be impacted. is not only reported but made actionable: who owns it, how urgent it is, who picked it up, and what happens if no one responds.
From alarm to a clear response
An alarm sent to everyone quickly becomes one nobody takes seriously. focusAlert ingests events from WinCC, webhooks, SMTP, and other systems and routes them by your rules to the right group or person. What matters is what happens next: who picks it up, what gets escalated, and all of it stays traceable.
From source to acknowledgment
Agents on the source systems capture every event. focusAlert evaluates it with rules, groups and escalation to decide who is reached and how. Delivery then runs over the right channel.
From source to acknowledgment
Supported protocols and channels
focusAlert reads events from plant, monitoring, and mail systems and delivers them over the right channels. Inbound sources and outbound channels can be extended modularly.
Event sources
WinCC
Webhook
SMTP
SNMP trap
Notify targets
Email
SMS
Voice call
Browser push
Microsoft Teams
Slack
Telegram
Webhook
Rules decide who is reached, when, and over which channel. Configured in a few clicks, with no programming required.
- EventFrom WinCC, webhook or mail
- EvaluatePriority, group, shift, time
- EscalateParallel or one after another, with delay
- DeliverEmail, phone or push
- AcknowledgeAcceptance and feedback
Repeats until someone acknowledges.
For edge cases, every stage is fully scriptable. That is rarely necessary.
In practice
Water utilities
A pumping station reports a pressure drop. The control room has to react at once.
- WinCCEvent from the Siemens control system (SCADA) via the WinCC agent.
- prio 1Highest level: forwarded immediately, no delay.
- PhoneVoice call that reads out the alarm and is acknowledged by keypad.
- until acknowledgedRepeats until a recipient confirms. Otherwise it escalates.
Industry & production
A line fault during the night shift. Only the group on duty is woken.
- SMTPAn incoming email is ingested as an event.
- shift groupOnly the group currently on duty is notified.
- one after anotherRecipients are contacted sequentially, not all at once.
- escalate to leadIf no one responds, the message moves to the next level.
IT support
Monitoring reports an unstable service. focusAlert waits out a grace period in case it recovers on its own.
- WebhookHTTP call from monitoring tools such as Zabbix or Uptime Kuma.
- wait 1 minGrace period: if the service recovers on its own, no alarm is sent.
- Email + PushDelivered in parallel via email and browser push.
- on-callGoes to the on-call responder currently on duty.
focusAlert isolates everything through Teams. A Team bundles groups, recipients, rules, clients, and tokens, fully separated from every other Team.
Teams as tenants
Each Team encapsulates groups, users, recipients, rules, and integrations. Data access is filtered per Team on the server side.
Separate environments
Development, staging, and production run as their own Teams with their own tokens and rules, so configurations never mix.
Dedicated access per system
Every client and integration gets its own token, bound to a single Team.
Groups, order, and escalation
Within a Team, groups, notification order, and escalations decide who is reached and when.
A look inside focusAlert
Groups, rules, and receivers stay separate by task and share one event trail.
Configurator: routing groups, each with its team, rule, and receivers.
Rules: pre-actions, filters, actions, and conditions decide what happens to an event.
Receivers: configure retries and manage each person's registered push devices.
Related Solutions
Critical infrastructure
Bring together facilities, networks, and ownership across sites. Understand dependencies for operations and maintenance.
Building automation
Discover technical devices in a building and their connections. Assign ownership and remote access.
IT management
Bring together computers, servers, software, and cloud services. IT operations and support use the same inventory.
FAQ
Key questions before introducing focusAlert.
How do events arrive from inventory?
A configured webhook/API connection can pass events to focusAlert. This integration is optional. The source, event format and destination group are configured for the deployment.
Does focusAlert replace existing SCADA alarms?
No. focusAlert takes relevant events from existing systems and governs notification, escalation, acceptance, and traceability.
Which channels does focusAlert support?
Typical channels are email, phone, and browser push. The selection depends on urgency, role, group, and operating mode.
How are alerts acknowledged?
Recipients can accept alerts or provide feedback. These states feed escalation, history, and analysis.
Is focusAlert multi-tenant?
Yes. Organizations, groups, rules, recipients, and integrations can be operated separately and administered cleanly.
Turn alarms into a manageable response process
We review your sources, groups, on-call models, and escalation paths, then shape a first alerting scope that relieves operations quickly.