Read and normalize
Bring PLC, Modbus TCP/RTU, MQTT, or gateway data into one edge layer.
Back to solutions
SCADA EDGE / LOCAL CONTROL
SCADA edge for systems that need data and logic on site.
Bring collection, buffering, alerts, and the integration contract closer to the cabinet so operators can see the boundary between devices and software.
SCADA / EDGE BOUNDARYLOCAL-FIRSTHANDOVER-READY
INUT / SCADA / EDGE BOUNDARYLIVE
REFERENCE DATA PATH
01PLC · Sensor · Meter
02iNut PC / Datalogger
03Buffer · Logic · Alert
04FUXA · Local API · MQTT
01 / ARCHITECTURE
Separate devices, edge, and screens.
A handover-ready SCADA architecture starts by deciding who reads data, who keeps it, and which system owns the interface.
01PLC · Sensor · Meter
02iNut PC / Datalogger
03Buffer · Logic · Alert
04FUXA · Local API · MQTT
05Web SCADA · App · CRM
02 / WHERE IT FITS
When SCADA needs a clearer operating layer.
Use this flow when a system has multiple protocols, unreliable outside connectivity, or a software team that needs a stable contract.
Buffer and alert
Keep data and state according to the operating policy agreed for the site.
Handover by layer
Separate ownership between edge, SCADA, applications, and user access.
03 / NEXT LAYER
Material for an architecture review.
04 / START FROM THE CURRENT STATE
Share the SCADA diagram Want a clearer SCADA boundary?
Share the cabinet diagram, protocols, and current screens. iNut will map an edge flow that can be tested and handed over.
FAQ / CLARITY BEFORE CONTACT
Questions teams ask before an architecture review.
How is SCADA edge different from a web dashboard?
SCADA edge places reading, storage, logic, and the contract near devices; a dashboard is one consumer of that data.
Does the architecture require a dedicated cloud?
No. LAN, WiFi, 4G, P2P, or an internal API path can be chosen around the actual site and policy.