How hayk678/scada-alarms works
This is a SCADA alarm-monitoring application: plant signals (or simulated alarms) enter a Kafka-based pipeline, active alarms are deduplicated and stored, and users can query, acknowledge, and receive live alarm updates. The excerpts establish the connector, processor, API, and simulator behavior. The OPC UA server and frontend are represented from the tree; their runtime connections are not verified by sampled source.
Main entry points: alarm_processor.py Alarm Processor · main.py Alarms API · server.py OPC UA Server · opcua_connector.py OPC UA Connector
Components 13
Signal Sources
- Plant Signals
opcua-server/server.py - OPC UA Server
opcua-server/server.py - Alarm Simulator
simulator/simulator.py
Alarm Ingestion
- OPC UA Connector
connector/opcua_connector.py - Kafka Topic
Alarm Processing
- Alarm Processor
processing/alarm_processor.py - Alarm Deduplication
processing/alarm_processor.py - Alarm Schema
processing/schema.sql - Alarm Database
- Live Alarm Channel
User Access
- Alarms API
backend/main.py - Web Interface
frontend/index.html
Other components
- Operator
Connections 12
- Plant Signals → OPC UA Server: publishes signals
opcua-server/server.py - OPC UA Server → OPC UA Connector: provides signals
- OPC UA Connector → Kafka Topic: publishes alarms
connector/opcua_connector.py - Alarm Simulator → Kafka Topic: publishes alarms
simulator/simulator.py - Kafka Topic → Alarm Processor: delivers messages
processing/alarm_processor.py - Alarm Processor → Alarm Deduplication: checks duplicates
processing/alarm_processor.py - Alarm Processor → Alarm Database: writes batches
processing/alarm_processor.py - Alarm Processor → Live Alarm Channel: publishes live alarms
processing/alarm_processor.py - Alarms API → Alarm Database: queries and updates
backend/main.py - Alarms API → Live Alarm Channel: subscribes to alarms
backend/main.py - Operator → Web Interface: uses
- Operator → Alarms API: requests alarm data
backend/main.py