Specifications
Standards are data here, not code.
A tool that ships a fixed library of standards can only grade against the ones it shipped with, and the one your buyer just cited means waiting for a release. A specification here is a requirement set: encode its acceptance limits once, and every part that cites it inherits them.
How a requirement resolves
Base specification
Encoded once
The standard's acceptance limits, stored as a plain typed file you can open and read.
Customer overrides
Recorded as deltas
A buyer tightening sulfur or hardness is one line, not a second copy of the whole spec.
Effective requirements
What the part was graded against
Resolved per part and kept with the review, so an auditor can see exactly which limits applied.
Encoding one — a steel grade with its API 6A and NACE MR0175 sour-service limits, say — is reading the standard once and writing its limits down. Adding the next one is another file, not another release.
Specimen sets
Which bar the limit is about is part of the specification.
A mill certificate tests the same property on several specimens. Whether the requirement means their average, the lowest single value, or every one of them is stated by the standard — so it is carried as data alongside the limit, not guessed at.
| Rule | What has to satisfy the limit |
|---|---|
| average | The mean of the set, within one test condition. |
| min_single | The lowest single specimen of the set. |
| max_single | The highest single specimen of the set. |
| all | Every specimen, on its own. |
| blank | Not yet read for this specification — a straddling set goes to a reviewer rather than being guessed. |
See it run against your own documents.
We will walk through a real review end to end in about twenty minutes — the upload, the grading, the characteristics it hands back, and the sign-off — on a document you choose.