← SCADA Studio
🖥️

SCADA System Designer

Tags · Bandwidth · Historian · Servers · Redundancy

When to use: Use this designer when scoping a SCADA system for distributed field assets — sizing the telemetry bandwidth per remote site, the historian storage over the retention period, the server tier from total tag count, and the redundancy architecture. It flags when a low-bandwidth radio link cannot carry the poll load and recommends report-by-exception (DNP3 / IEC 60870-5-104). Estimates are engineering planning figures, not vendor-guaranteed specifications.

System Parameters
sites
tags
rest digital
%
sec
ops
days
sec
Tag Database
1,800
Total Tags
1,080
Analog
720
Digital
✓ LINK ADEQUATE
450 bps
Per-Site Telemetry Load · 0.0% of link
Report-by-exception assumed (~15% of full poll)
Bandwidth
Per-Site (full poll)3.0 kbps
Per-Site (effective)450 bps
Aggregate (effective)5.4 kbps
Bytes / Tag10 B (×1.25 ovhd)
Recommended CircuitNarrowband radio / low-speed serial sufficient
Historian Storage
Samples / Tag / Day8,640
Retention365 days
Raw Storage68.12 GB
Compressed17.03 GB
Compression~4× (swinging-door / dead-band)
Servers & Infrastructure
Server TierSingle Modest Server
Per-Server Spec4–8 cores · 16–32 GB RAM
SCADA Servers2 (primary/standby, heartbeat)
Historian Servers2
Network Paths1
HMI Workstations4 (3 ops + 1 eng/spare)
Comm Gateways / FEP2
Time SyncGPS / NTP master clock
References
Architecture: Field → RTU/PLC → Comms → SCADA Master/Historian → HMI
DNP3 / IEC 60870-5-104 — report-by-exception telemetry
OPC UA — secure interoperable data exchange
Historian: swinging-door / dead-band compression (5–20×)
IEC 62443 — Industrial automation & control system security