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.
Sizing a SCADA system requires estimating the telemetry bandwidth per remote site, the historian storage over the retention period, the server tier from total tag count, and the redundancy architecture — all at the feasibility and FEED stage before vendor selection. This designer integrates all four sizing disciplines and flags when the communication medium cannot carry the polling load, prompting the engineer to select a report-by-exception protocol like DNP3 or IEC 60870-5-104.
SCADA sizing begins with the tag count: the total number of I/O points monitored and controlled by the system. Tags are divided into analog (process variables requiring 16-bit values) and digital (status and command bits). Bandwidth per site is calculated as: bytes_per_poll = tags_per_site × bytes_per_tag × protocol_overhead, then bps = bytes × 8 / poll_period_seconds. The effective bandwidth using report-by-exception (DNP3/IEC-104) is approximately 15% of the full-poll bandwidth because only changed points are transmitted.
Historian storage is calculated as: storage = total_tags × samples_per_day × retention_days × bytes_per_sample. Raw samples at 12 bytes each (8-byte timestamp + 2-4 byte value + quality byte) are compressed using swinging-door or dead-band algorithms to approximately 3 bytes/sample (4× compression). The server tier (single, mid-range, enterprise, or distributed) is selected from the total tag count using industry benchmarks.
DNP3 (IEEE 1815) is the dominant SCADA protocol for electric utility and water/wastewater applications in North America, providing report-by-exception, time-stamped events, and integrity poll functions. IEC 60870-5-104 is the international equivalent used extensively in European and international utility projects. OPC UA (IEC 62541) provides secure, semantically rich data exchange between SCADA systems, historians, and enterprise systems. IEC 62443 applies to the cybersecurity architecture of the SCADA communication network. ISA-100.11a and WirelessHART govern wireless field instrumentation integration into SCADA systems.
Protocol selection is the most consequential early decision. Modbus TCP and EtherNet/IP are polling-only protocols; they transmit all tag values on every poll cycle regardless of whether values have changed, which wastes bandwidth on low-speed radio or cellular links. DNP3 and IEC 60870-5-104 support report-by-exception (unsolicited reporting of changed data points), reducing steady-state bandwidth by 85–90% for slowly changing process values like reservoir levels and pump run-status.
Historian sizing requires careful attention to compression ratio assumptions. Dead-band compression only stores values when the process variable changes by more than a configured threshold. For a stable process (e.g., a tank level that changes slowly), compression can be 10–50×. For a turbulent process (flow rate fluctuating continuously), compression may be only 2–4×. Use 4× as a conservative default for initial sizing.
Select the application type (water, oil & gas, power, manufacturing) which pre-fills the typical percentage of analog tags. Enter the number of remote field sites and average I/O tags per site. Set the poll rate in seconds (5–60 seconds is typical for SCADA), the telemetry protocol, and the communication medium. Enter the number of operator workstations and the redundancy level. Set the historian retention period in days and the log rate in seconds. The designer outputs per-site bandwidth, total aggregate bandwidth, historian storage (raw and compressed), server tier recommendation, and hardware counts.
Report-by-exception (RBE) means that a field device (RTU or PLC) only transmits a data point when its value changes by more than a defined threshold (dead-band), rather than transmitting every point on every poll. DNP3 and IEC 60870-5-104 support unsolicited RBE reporting, which reduces steady-state telemetry bandwidth by 80–90% for slowly changing analog values. RBE is essential for narrowband radio links (9600–19200 bps) and is recommended for any link where bandwidth cost or capacity is limited.
Storage = total_tags × (86400 / log_interval_sec) × retention_days × bytes_per_sample. For uncompressed storage at 12 bytes/sample: 10,000 tags × 86,400 samples/day/tag × 365 days × 12 bytes = 38 TB/year. With 4× dead-band compression: approximately 9.5 TB/year. Modern process historians (OSIsoft PI, Wonderware Historian, ICONICS Genesis64) achieve 10–20× compression on typical process data, making multi-year retention at terabyte scale manageable.
Server tier scales with total tag count: under 2000 tags — a modest single server (4–8 cores, 16–32 GB RAM) is sufficient; 2000–25000 tags — a mid-range server (8–16 cores, 32–64 GB RAM); 25000–100000 tags — an enterprise server (16–32 cores, 64–128 GB RAM); above 100000 tags — a distributed/clustered architecture with multiple SCADA servers, a dedicated historian cluster, and load balancing. For redundancy, all tiers use dual servers (primary/standby) with automatic failover.
Cellular LTE is adequate for SCADA telemetry at polling rates of 5–60 seconds, which is typical for water distribution, wastewater lift stations, gas pipelines, and remote oil wells. A site with 150 tags at 5-second polling using DNP3 with RBE requires approximately 1–3 kbps effective bandwidth, well within LTE capacity. The limitations are latency (30–100 ms RTT, not suitable for closed-loop control) and availability (cellular coverage gaps in remote areas require satellite or radio backup).
The SCADA server (or front-end processor, FEP) manages communication with all remote field sites, executes alarm logic, and provides real-time data to operator HMIs. The historian (process data historian) stores time-series process data at configured sampling rates and retentions for trend analysis, reporting, and optimization. They are separate functions and often separate servers in mid-to-large systems, though small SCADA packages combine them. Historians require different storage (columnar time-series databases) and I/O patterns than the real-time SCADA server.
Try our SCADA Studio
More calculators, simulators, and guides for this discipline.