Interactive SCADA Edge Processing Explorer
See SCADA edge processing in action! Use the interactive explorer below to step through 4 stages of substation data processing. Watch as raw Modbus register readings are progressively parsed, filtered, classified, and routed — all without leaving the substation until the data is clean, structured, and CIP-compliant.
How to Use This Explorer
- Navigate using arrow keys (← →) or click the numbered stage buttons
- Compare the Input (left) and Output (right) at each stage
- Observe how raw register values become structured JSON (green), and noise gets filtered (removal)
- Inspect the YAML code showing exactly what processor handles each stage
- Learn from the stage description explaining the SCADA engineering context and business impact
Interactive SCADA Edge Processing Explorer
Raw Modbus Register Data
Raw telemetry from substation RTUs via Modbus TCP. At 50,000 readings/minute across dozens of RTUs, shipping all of this to the SCADA historian burns bandwidth and violates NERC CIP data minimization principles. These are raw register values — still need scaling, mapping, and normalization.
input:
socket:
network: tcp
address: 0.0.0.0:502
codec: linesTry It Yourself
Ready to build this SCADA edge processing pipeline? Follow the step-by-step tutorial:
Deep Dive into Each Step
Want to understand each transformation in depth?
- Step 1: Parse Modbus Register Data — Map register addresses to engineering units with scaling
- Step 2: Filter Nominal Readings at the Edge — Drop 99%+ of noise before it leaves the substation
- Step 3: Classify Fault Types with Bloblang — Tag each anomaly: VOLTAGE_DEVIATION, FREQUENCY_DRIFT, THERMAL_OVERLOAD
- Step 4: Route to SCADA Historian and Alerting — Critical faults to historian + PagerDuty; KPIs to cloud dashboard
Next: Set up your environment to build this pipeline yourself