INDUSTRIAL ENERGY MONITORING PLATFORM

SignalBridge Unifies Live SCADA Operations And Historical Analytics

A publish-once MQTT telemetry architecture feeds two purpose-built data products: low-latency operational monitoring and scalable historical analysis.

  • 2 Independent Data Paths
  • 7+ Runtime Services
  • 4 Device Types Supported
Utility-scale renewable energy site

Product Surfaces And Runtime Services

Access operational clients, analytics experiences, and integration endpoints from one place.

SCADA Frontend

Web App

Real-time monitoring for plant status, alarms, equipment health, and operational KPIs.

Operations Team https://scada.signalbridge.supersmallerp.com
Open SCADA

SCADA Mobile App

Android App

Mobile operational visibility for field and supervisory users with plant-centric monitoring.

Field + Operations Team scada-app
View Mobile Module

Console Frontend

Web App

Administration console for parks, plants, templates, users, and telemetry configuration.

Admin Team https://console.signalbridge.supersmallerp.com
Open Console

Analytics Console

Web App

Historical KPI, summary, and time-series analytics for park, plant, and equipment scopes.

Analyst Team https://analytics.signalbridge.supersmallerp.com
Open Analytics

Core API

Backend API

Operational API for parks, plants, templates, users, and latest telemetry state.

Integrations https://api.signalbridge.supersmallerp.com/api
Open API

Analytics API

Backend API

DuckDB-backed query API over Parquet data lake for historical and aggregate reporting.

Integrations https://analytics-api.signalbridge.supersmallerp.com
Open Analytics API

Product Feature Matrix

Map 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

Business And Technical Benefits

SignalBridge is built to improve reliability, observability, and analytics depth without overloading one datastore.

Single Telemetry Publish, Dual Outcomes

One MQTT publish drives both live operational state and historical analytics pipelines, reducing duplication across systems.

Fast Operational Reads

Latest-state telemetry is optimized in MySQL for low-latency SCADA dashboards and rapid operator response.

Cost-Efficient Historical Queries

Partitioned Parquet plus DuckDB enables deep time-range analysis with lower infrastructure overhead.

Pre-Aggregated Snapshot Reporting

Scheduled ETL builds hourly, daily, and monthly snapshots to accelerate dashboards and recurring reports.

Independent Scaling Paths

Operational and analytics workloads scale independently, preventing heavy queries from impacting control-room visibility.

How The Platform Works

The architecture separates responsibilities while maintaining a shared telemetry contract.

1

Acquire Telemetry At The Edge

ESP32 firmware and PC agents poll Modbus devices such as inverter, SMB, MFM, and WMS, then normalize payloads.

2

Publish Once To MQTT Backbone

All field and simulated telemetry events are published to MQTT with QoS and persistent-session patterns.

3

Ingest Latest Operational State

Telemetry ingestor updates MySQL latest metrics consumed by Core API and SCADA clients for real-time monitoring.

4

Build Historical Data Lake

Parquet ingestor writes partitioned historical files for long-range analytics and reporting workloads.

5

Materialize Snapshot Windows

Telemetry snapshot ETL computes hourly, daily, and monthly rollups with ETL health tracking for reliable reporting.

6

Serve Purpose-Built Experiences

SCADA surfaces read operational state, while Analytics API and console query Parquet history via DuckDB.

Software Components

Each service has a defined role in the telemetry-to-insight lifecycle.

Client Applications

  • scada-frontend (live operational web UI)
  • scada-app (Android monitoring client)
  • console frontend (configuration and governance)
  • analytics-console (historical dashboards and time-series views)

APIs And Query Layer

  • api (operational entities and latest telemetry)
  • analytics-api (DuckDB-backed Parquet query service)
  • Shared contracts powering dedicated frontend experiences

Background Services

  • telemetry-ingestor (MQTT to MySQL latest state)
  • telemetry-parquet-ingestor (MQTT to partitioned Parquet history)
  • telemetry-snapshot-etl (hourly/daily/monthly snapshot materialization)
  • PM2 production process manager for Node and Python workers

Data Stores And Messaging

  • MQTT broker for telemetry backbone
  • MySQL for latest operational state
  • Parquet data lake for historical telemetry
  • Snapshot tables and Parquet snapshot outputs for pre-aggregated reporting
  • DuckDB execution engine for analytics queries

Hardware And Edge Layer

SignalBridge supports mixed edge environments from embedded agents to simulated labs.

Telemetry Edge Agents

ESP32-based telemetry firmware and PC polling agents collect Modbus registers and publish normalized payloads.

Industrial Device Compatibility

Designed for common plant equipment classes including inverter, SMB, MFM, and WMS telemetry sources.

Lab And Pre-Commissioning Support

Modbus simulator stack enables synthetic payload generation for development, validation, and demo readiness.

Hybrid Deployment Readiness

Field acquisition can run on plants while analytics runtime is hosted centrally or on separate on-prem nodes.