SCADA

SCADA, short for Supervisory Control and Data Acquisition, is the control-system architecture that industrial operators use to watch and steer physical processes at scale—power generation, water treatment, oil and gas pipelines, and factory floors. It pulls telemetry from field devices like PLCs and RTUs into a supervisory layer where humans and software can see state and push commands back out. It predates the modern web API by decades, which is exactly why it matters when these systems start connecting to the broader digital world.

• Field-to-control telemetry - Sensors, PLCs, and RTUs report measurements up to a supervisory layer in near real time.
• Supervisory control - Operators and automation issue commands back down to actuators, valves, and switches from a central console.
• Industrial protocols - Historically spoken in Modbus, DNP3, OPC, and other purpose-built protocols rather than HTTP and JSON.
• Operational, not transactional - Optimized for continuous monitoring and safety, not for the request/response patterns web developers assume.

Where SCADA shows up in my API work is at the integration seam: the industrial world runs on these systems, and the pressure to expose their data to analytics, cloud platforms, and now AI agents is real. That gap—between decades-old operational technology and the OpenAPI-and-JSON world the rest of the API economy lives in—is where the risk and the opportunity both concentrate. Bridging it well means treating SCADA data as a governed, secured API surface rather than something you bolt a raw connector onto, because the same interface that feeds an AI model can also reach a physical valve.