Time-series storage sizing
Tag count, sample rate and retention turned into terabytes, plus the edge buffer you need to survive a link outage of a given length.
Digital & data
Pages and scan quality turned into storage, processing hours and — the part that actually sets the schedule — the size of the human review queue.
Loading the calculation…
This calculation ran in your browser. No value you entered was sent anywhere, and nothing was stored.
Accuracy figures are representative, not predictive. A single archive can contain crisp typed reports, faded thermal prints, blueprints, and a driller's handwriting in two scripts, and the average is meaningless across that mix — the only way to know is to run two hundred representative pages through the actual pipeline before committing to a schedule. The review-queue model here is also deliberately crude: real queues grow when reviewers disagree with each other, which no estimate of confidence captures.
Tag count, sample rate and retention turned into terabytes, plus the edge buffer you need to survive a link outage of a given length.
Tags, report rate and protocol turned into the kilobits per second a link has to carry — including the backfill surge after the link comes back.