SCADA Frontend
Web AppReal-time monitoring for plant status, alarms, equipment health, and operational KPIs.
Open SCADAINDUSTRIAL ENERGY MONITORING PLATFORM
A publish-once MQTT telemetry architecture feeds two purpose-built data products: low-latency operational monitoring and scalable historical analysis.
Access operational clients, analytics experiences, and integration endpoints from one place.
Real-time monitoring for plant status, alarms, equipment health, and operational KPIs.
Open SCADAMobile operational visibility for field and supervisory users with plant-centric monitoring.
View Mobile ModuleAdministration console for parks, plants, templates, users, and telemetry configuration.
Open ConsoleHistorical KPI, summary, and time-series analytics for park, plant, and equipment scopes.
Open AnalyticsOperational API for parks, plants, templates, users, and latest telemetry state.
Open APIDuckDB-backed query API over Parquet data lake for historical and aggregate reporting.
Open Analytics APIMap each product capability to the runtime component that delivers it.
| Capability | What You Can Demo | Primary App |
|---|---|---|
| Real-Time Operational Visibility | Track plant and equipment status, daily generation, active power, and alarms with low-latency refresh. | SCADA Frontend + Core API |
| Operational Configuration And Governance | Manage parks, plants, users, templates, and device setup from a centralized console. | Console Frontend |
| Historical Analytics At Scale | Run summary and time-series analysis against partitioned Parquet history without affecting SCADA reads. | Analytics Console + Analytics API |
| Unified Telemetry Fan-Out | Publish telemetry once to MQTT, then process in parallel for latest-state operations and long-range history. | Telemetry Ingestor + Parquet Ingestor |
| Scheduled Snapshot ETL | Run hourly, daily, and monthly ETL windows to generate pre-aggregated snapshots and ETL health status. | Telemetry Snapshot ETL + Analytics API |
| Cross-Surface Integration | Expose domain and telemetry data through dedicated APIs powering web and mobile clients. | Core API + Analytics API |
SignalBridge is built to improve reliability, observability, and analytics depth without overloading one datastore.
One MQTT publish drives both live operational state and historical analytics pipelines, reducing duplication across systems.
Latest-state telemetry is optimized in MySQL for low-latency SCADA dashboards and rapid operator response.
Partitioned Parquet plus DuckDB enables deep time-range analysis with lower infrastructure overhead.
Scheduled ETL builds hourly, daily, and monthly snapshots to accelerate dashboards and recurring reports.
Operational and analytics workloads scale independently, preventing heavy queries from impacting control-room visibility.
The architecture separates responsibilities while maintaining a shared telemetry contract.
ESP32 firmware and PC agents poll Modbus devices such as inverter, SMB, MFM, and WMS, then normalize payloads.
All field and simulated telemetry events are published to MQTT with QoS and persistent-session patterns.
Telemetry ingestor updates MySQL latest metrics consumed by Core API and SCADA clients for real-time monitoring.
Parquet ingestor writes partitioned historical files for long-range analytics and reporting workloads.
Telemetry snapshot ETL computes hourly, daily, and monthly rollups with ETL health tracking for reliable reporting.
SCADA surfaces read operational state, while Analytics API and console query Parquet history via DuckDB.
Each service has a defined role in the telemetry-to-insight lifecycle.
SignalBridge supports mixed edge environments from embedded agents to simulated labs.
ESP32-based telemetry firmware and PC polling agents collect Modbus registers and publish normalized payloads.
Designed for common plant equipment classes including inverter, SMB, MFM, and WMS telemetry sources.
Modbus simulator stack enables synthetic payload generation for development, validation, and demo readiness.
Field acquisition can run on plants while analytics runtime is hosted centrally or on separate on-prem nodes.