STANDARD by MetraSlate · Metrology Edition
The Measurement Engine.
In most systems the measurement is something the software stores. In Standard it is what the software is built around: the engine computes the uncertainty, applies the decision rule and produces the verdict inside the same transaction that records the reading, and everything else is arranged around it.
The decision rule
Guardbanded, Not Guessed.
Every reading carries its uncertainty into the verdict. When the test uncertainty ratio drops below 4:1, the guardband tightens the acceptance limit by a share of that uncertainty rather than setting it aside, and the math travels with the record.
Decision rule applied per ANSI/NCSL Z540.3. The uncertainty math travels with the record.
The bench
The Math is the Product.
In this industry the number is the deliverable. Standard treats it that way.
When a technician records a reading, the engine computes the GUM uncertainty budget on the spot, Welch-Satterthwaite effective degrees of freedom and all, inside the same transaction that stores the value. The test uncertainty ratio and the Z540.3 guardband follow, and the verdict is made by the decision rule, with the math attached to the record forever. Values are exact decimals from the wire to the database. Nothing in the measurement path ever passes through floating point, because a rounding error in the seventh digit is still an error.
GUM uncertainty is computed at the point of capture, inside the same transaction that records the reading. Not in a spreadsheet after the fact.
Z540.3 guardbanding runs as the decision rule, not a habit. Every pass and fail carries the math that produced it, attached to the record.
The engines are checked against published vectors from the GUM, ILAC-G8, Z540.3 and the Dobbert guardbanding literature. When the standards and our output disagree, the build fails.
Guardband method, coverage factor, resolution handling and pricing travel together as a service level, so the lab's policy is applied by the system, not remembered by the technician.
CMC budgets on the A2LA R205 methodology push into your specs, and your scope of accreditation lives beside the work it governs.
The artifact
The Certificate is Sealed.
When a calibration is complete the record freezes. The certificate is sealed and cryptographically signed, and anyone you hand it to can verify it themselves, the moment it is released.
No calling the lab to confirm. No PDFs of PDFs. Your customer's auditor checks the seal, not your word.
The composition
How the Edition is Put Together.
The industry knowledge is the honey that bonds the industry to the surface.
The platform underneath is service agnostic: assets, work orders, workflows, portals, documents, reports. The Metrology Edition is what happens when the industry's own structure is bound into those pieces instead of layered over them. An asset stops being a row in an equipment list and becomes a calibratable instrument, with a specification behind it, an interval in front of it, and every event it has been through attached to it. The specification carries the formulas, so a manufacturer's accuracy statement becomes a computable tolerance at each test point rather than a line in a PDF.
The service level carries the policy that decides the verdict, and the work order routes the instrument through the flows your quality system requires. The compliance structure sits across all of it: qualifications gate who may sign, the audit trail runs under every field, and the accreditation scope governs what the record is allowed to claim. Nothing is copied between the pieces, because there is only one record.
The argument
AI at the Edges. Never in the Measurement.
A calibration record is evidence, and evidence cannot rest on a model's guess. Standard does not depend on AI: deterministic automation runs the lifecycle, and where AI adds an enhancement, it stays at the edges, behind human review, attributed in the record, and never in the measurement path.
Read the PositionMeasured, not promised
Fast Enough to Disappear.
A system this central cannot keep people waiting.
These are real measurements at two million rows with multi-tenant isolation fully enforced.
Where this is going
Traceability as Data, Not Paperwork.
NIST traceability today lives in PDF text and test numbers, and every audit is a paper chase to rebuild a chain that was never stored as data. Standard treats traceability as data instead: the sealed certificate is already a machine-verifiable link, not a document to hunt down. The full chain, field instrument to working standard to reference standard to the test number, extends that same shape, with distributed-ledger anchoring under evaluation for the step where separate organizations verify each other's links.
Metrology Edition by MetraSlate
Help Us Get It Right.
Standard was built by a working calibration professional, for the way the work actually runs. The hard part was never the software: it is knowing what the bench needs at 2am on a failed as-found. If you are a metrologist, a quality manager, or someone who has run a lab, we would like your read on it. MetraSlate is bootstrapped, and we are actively beginning the funding journey.
Start a ConversationRunning This Out of Seven Different Systems?
Bring your hardest datasheet and watch it collapse into one: the measurement, the certificate, and the business around it, running live, on the same system.
Request a Demo