Skip to content

Main content

QC Spec Limit Inclusion Policy

Apply explicit endpoint inclusion policies to supplied result limits without choosing a specification.

Loading tool…

Description

Check a result against supplied limits with independent endpoint inclusion.

Quality-control results depend on measurement basis, calibration reference, rounding, limit inclusion and decision rules. A raw result can lie on a different side of a boundary from its reported value. Guard bands and relative differences must retain their exact definitions; a local comparison does not select a valid specification or establish conformance.

Check a result against supplied limits with independent endpoint inclusion.

When to use this tool

Use QC Spec Limit Inclusion Policy when you already have result, lowerLimit, upperLimit, includeLower, includeUpper and need to check a result against supplied limits with independent endpoint inclusion.

How to use the tool and how it works

  1. Enter result, lowerLimit, upperLimit, includeLower, includeUpper. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read withinSuppliedLimits. Inspect withinSuppliedLimits before interpreting the associated values.

Require upperLimit>=lowerLimit; combine the selected strict or inclusive lower and upper comparisons.1

Input fieldMeaning and unitsAccepted input
resultResultRequired. Finite number.
lowerLimitLower LimitRequired. Finite number.
upperLimitUpper LimitRequired. Finite number.
includeLowerWhether equality at the supplied lower limit passes.Required. Boolean.
includeUpperWhether equality at the supplied upper limit passes.Required. Boolean.
Output fieldInterpretationReturned shape
withinSuppliedLimitsWithin Supplied LimitsRequired. Boolean.
json
{
  "input": {
    "result": 5,
    "lowerLimit": 5,
    "upperLimit": 10,
    "includeLower": true,
    "includeUpper": false
  },
  "output": {
    "withinSuppliedLimits": true
  }
}

Limitations and assumptions

  • An equal-limit interval contains the endpoint only when both flags include it; no specification, uncertainty or compliance decision is selected.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Apply the documented measurement method, calibration records and complete decision rule when judging a result. Keep raw values, reported values, uncertainty and endpoint inclusion visible; a supplied guard band or replicate term does not select that rule.

References

  1. Calculation and input contract: quality-control/qc-spec-limit-inclusion-policy — tool.io

Similar or alternative tools