Industrial Networks and OT · #92

Online Historian Storage Calculator

Estimates the space a production data archive takes over the years.

  • Data is processed in your browser and not sent to a server

Tool

1 = every second.

8–20 B depending on product.

Share of points skipped by deadband/swinging door.

What does this tool do?

Historians sample each tag within seconds; 5,000 tags at one-second scan amount to 1.9 TB a year uncompressed. Deadband and swinging door compression usually cut this by 80–95 %, but the ratio depends on how 'lively' the process is. The tool calculates raw and compressed volume, yearly growth and index overhead.

How to use it

  1. Enter tag count and scan interval (seconds).
  2. Enter bytes per point (value + timestamp + quality) and expected compression.
  3. Enter retention (years), yearly tag growth and index/overhead share; press Run.

Fields

Tags
Scan interval (s)
1 = every second.
Bytes per point
8–20 B depending on product.
Compression savings
Share of points skipped by deadband/swinging door.
Retention (years)
Yearly tag growth
Index / overhead

Worked example

InputValue
Tags5000
Scan interval (s)1
Bytes per point12
Compression savings90
Retention (years)1
Yearly tag growth0
Index / overhead0

Expected result: 5,000 tags, one-second scan, 12 B, 90 % compression: 518.4 MB per day, 189.2 GB per year.

Uncompressed the same data would be 1.89 TB a year. Instead of assuming a compression ratio, measure real archive growth in a one-week pilot and rerun the tool with that ratio.

Second scenario

InputValue
Tags20000
Scan interval (s)5
Bytes per point16
Compression savings70
Retention (years)5
Yearly tag growth10
Index / overhead15

Expected result: 20,000 tags every 5 seconds, 16 B, 70 % compression, 5 years with 10 % yearly tag growth and 15 % index overhead: 605.5 GB in the first year, 4.25 TB in total over 5 years.

Method and assumptions

Points/day = tags × 86400 / scan. Daily = points × bytes × (1 − compression). Total = Σ years (daily × 365 × (1 + growth)year) × (1 + index). Fractional years are prorated.

Using the result and troubleshooting

Consider the result together with RAID capacity and backup needs (Backup Repository tool); define separate retention and backup policies for critical archives.

Limits and common mistakes

  • Product-specific file structures, event/alarm tables and aggregate tables must be calculated separately; the compression ratio is an estimate.

Frequently asked questions

How do I know the compression ratio?

Slow temperature/level tags reach up to 95 %, fast current/vibration tags typically 30–60 %. Best is to measure archive growth on the existing historian.

Related tools and service

  • PLC Data Buffer SizingCalculates how large the on-site buffer must be so data is not lost when the central link drops.

Related service: Production Monitoring and Dashboards

Industrial online tools · See all online tools