Sieve Calibration Database
Local log of your lab's test sieves — history, verdicts and recalibration alerts.
Calculator
Loading registry…
Theory & method
Test sieves drift: wire cloth stretches with use, apertures widen and a sieve that passed verification when new can silently fall out of tolerance. Laboratory practice (and ISO 3310-1 itself) therefore treats sieve verification as a periodic activity — each sieve carries an identification, a verification history and a due date for the next check. This tool is that logbook, kept entirely in your browser.
Each sieve is registered under a standard designation of ISO 3310-1 (Tables 1 and 2, 20 µm to 125 mm) or ASTM E11-95 (Table 1). Apertures only exist as normative designations — the tool never accepts arbitrary nominal sizes, and never derives an aperture from a mesh count.
For ISO 3310-1 sieves, each logged calibration is checked with the same engine as the one-shot Sieve Calibration Check tool: the mean of the measured apertures must stay within w ± Y (§5.1.1.3), no aperture may exceed w + X (§5.1.1.2), and the sample standard deviation must not exceed σ₀ from Tables 1/2 (with the note-b exception above 50 mm, where σ₀ has no physical reality). Inspection and calibration levels add a confidence interval on the mean with K = 2.576 (99.0%) and K = 3.0 (99.73%) — a documented approximation of the standard's non-public equations 4–7.
For ASTM E11 sieves, the three Table 1 checks are applied: the average opening must stay within the column-4 tolerance, not more than 5% of openings may exceed the column-5 size, and no individual opening may exceed the column-6 maximum. Columns 5 and 6 are absolute opening sizes, not deltas — e.g. for an 850 µm sieve they are 925 µm and 970 µm.
Verdicts are never stored: only the raw measurements are. Every time the history is displayed, each record is re-evaluated against the current engine, so an engine improvement retroactively applies to old records. When a calibration comes from an external certificate (mean ± standard deviation only), the tool runs a declared partial verification: the individual-aperture checks are marked "not evaluable" instead of silently passing.
How to use
- 01Register each test sieve of your lab: pick the standard (ISO 3310-1 or ASTM E11), the normative designation, your internal identification (e.g. P-012) and the recalibration interval in months.
- 02After each verification, log a calibration record: date, method (optical measurement or microspheres) and the measured apertures — pasted as free text, one value per line or separated by spaces. A verdict preview appears before you save.
- 03If the verification came from an external certificate, switch to certificate-summary mode and enter the reported mean (and standard deviation, if available). The verdict is explicitly marked as partial.
- 04For the microsphere method, the tool suggests which glass or polymer standards cover the sieve's aperture within their certified range (±2.5σ) — estimate the equivalent aperture with the Microsphere Aperture calculator and log the result here.
- 05Watch the registry list: sieves are sorted by criticality (overdue → due soon → never calibrated → OK). Export a per-sieve CSV/PDF calibration report, and keep a JSON backup of the whole registry — the data lives only in your browser.
Frequently asked questions
Where is my sieve registry stored?
Exclusively in your browser's localStorage, on this device. Nothing is uploaded to any server — which also means clearing site data, switching browsers or using another machine will not carry the registry over. Use the JSON backup export/import to move or safeguard it.
Why can't I type an arbitrary aperture for a sieve?
Test sieves only exist in the normative designations of ISO 3310-1 / ISO 565 and ASTM E11. Tolerances (Y, X, σ₀, and the E11 columns) are defined per designation, so a free-typed aperture would have no defined acceptance criteria. This is the same policy as every other tool on this site: apertures are never derived or invented.
What does a "partial" verdict mean?
It means the record only contains a certificate summary (mean, possibly standard deviation), not the individual apertures. The mean check — and the σ₀ check, when a standard deviation is present — are evaluated; the individual-aperture checks (ISO §5.1.1.2, ASTM columns 5–6) are marked not evaluable. The verdict covers only what could be checked.
How is the next-due date computed?
Last calibration date plus the recalibration interval you set per sieve (12 months is a common default; high-usage or abrasive-material sieves often use shorter intervals). The tool flags sieves 30 days before the due date ("due soon") and after it ("overdue"). The interval is your lab's quality-system decision — the tool only tracks it.
Normative references
- ISO 3310-1:2016 — Test sieves — Technical requirements and testing — Part 1: Test sieves of metal wire cloth (Tables 1–2, §5.1.1).
- ASTM E11-95 — Standard Specification for Wire-Cloth Sieves for Testing Purposes, Table 1 (dataset edition used by this site, transcription audited).
- ISO 565 — Test sieves — Metal wire cloth, perforated metal plate and electroformed sheet — Nominal sizes of openings.
- Whitehouse single-shot microsphere method — equivalent aperture estimation from the passing fraction of calibrated microspheres (see the Microsphere Aperture calculator).