Meana Petro

Digital & data

Archive OCR project estimator

Pages and scan quality turned into storage, processing hours and — the part that actually sets the schedule — the size of the human review queue.

Inputs

Persian and English in one document counts as two.

Throughput assumptions

Per GPU, through the full extraction pipeline.

Results

Loading the calculation…

This calculation ran in your browser. No value you entered was sent anywhere, and nothing was stored.

How it is calculated

  • Page size by capture class: 0.35 MB for clean 300 dpi text, 0.9 MB for mixed text and diagrams, 1.6 MB for photographed pages, 12 MB for large-format logs and maps.
  • Base OCR accuracy by the same class, reduced by the handwritten share and by each language past the first.
  • Pages falling below your confidence threshold go to the review queue; the queue size drives the reviewer-months figure.
  • Derived artefacts — extracted text, layout JSON, a searchable PDF layer — are taken as 35 % on top of the images.

Standards it speaks

Where this stops being true

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.

Related tools

  • 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.

  • Remote site bandwidth

    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.