SCADA Historian Storage calculator
What the same data costs once it is archived rather than transported.
SCADA / OT · Professional Microtool
Telemetry Bandwidth Calculator
Bit rate · Daily and monthly data
Estimate the bandwidth and monthly data a polled telemetry link needs from point count, poll interval, payload size, protocol overhead and the number of sites sharing the link.
- —Sites
- —Points each
- —Polled every
- —Overhead
- —Link
Start from an example: One remote site, 500 points every five seconds →
Full output
- —Data per day
- —Data per 30 days
- —Values per second
- —Throughput
Bandwidth required against poll interval
Bandwidth falls away sharply as the poll slows, which is why the first fix for a saturated link is almost always the interval rather than the circuit.
Keep it
Both carry the figures you entered, in the part of the address that is never sent to a server. Share only where that is appropriate. To keep a copy for a project file, print the page — it lays itself out as a document.
Need this against your real link and protocol?
We can measure what the poll actually costs on your circuit, model batching and retries, and design the acquisition so the data plan stops being the constraint.
Calculation basis 4 steps · view the method →
Values per second = points per site ÷ poll interval × sites—Application bytes per second = values per second × bytes per point—Bandwidth = bytes per second × (1 + overhead) × 8 bits—Monthly data = bytes per second × 2,592,000 seconds—
Assumptions & limitations Screening estimate for link sizing and data-plan budgeting · 6 assumptions →
This is a screening estimate. Real traffic depends on the protocol, on how many points fit in one request, on retries and keep-alives, and on whether the link carries anything else. Cellular plans also bill rounded sessions rather than exact bytes. Confirm against a measurement on the live link before committing to a plan or a circuit.
- Every point is polled on the same interval and every poll succeeds.
- Overhead is applied as a flat percentage; in reality it depends on how many points fit into one request.
- Retries, keep-alives, time synchronisation and management traffic are excluded.
- A month is taken as 30 days.
- Bandwidth is quoted in decimal bits per second, as links are sold.
- Nothing else is assumed to share the link.
Worked examples
- One remote site, 500 points every five seconds
Open with these figures → - Four sites, one-second poll on 2,000 points
Open with these figures →
About this tool
Remote sites are usually connected by whatever link was available, and the poll is configured later by someone who never sees the bill. This tool puts the two together: what the configured poll actually costs in bits per second and in gigabytes a month, across every site sharing the link. Written for control, telecoms and operations engineers.
Go deeper
SCADA, Telemetry & Industrial Monitoring challenge
Twelve questions on polling, report-by-exception, protocols and the OT/IT boundary.
Power & Utilities expertise
Cloud SCADA and distributed data acquisition around real infrastructure.