Docs
Open Moduvio
Screen reference · Quality

Metrology impact and calibration recall

Assess an exact failed calibration certificate and its invalid measurement interval, approve affected uses, record Product Safety follow-up and independently verify evidence without changing calibration or custody.

Screen orientation

Who can use it

metrology:read is constrained by site and clearance. Assessment, approval, decision, response, verification and closure use metrology:assess, :approve, :decide, :coordinate, :verify and :close. Only the current scope author submits. QA excludes the case creator and current scope author/submitter; Product Safety also excludes the scope approver. Assigned owners must be active, scoped, cleared QUALITY_ENGINEER users independent of those actors and the safety decider. Only the assigned owner responds. Verification excludes all those prior actors plus the owner/response submitter. Final closure excludes the case creator, current scope author/submitter, scope approver and safety decider.

How the screen is arranged

Five summary cards show scope review, safety decision, action tracking, closure review and open actions. New OOT case opens the failed-certificate and affected-use editor. Searchable case cards contain measurement details/history, decision actions, responses and closure. Stage-specific forms open below the register.

Field reference

The entries below describe the current screen controls and read-only values. They do not relax server-side validation, site scope, classification handling or required independence in a governed decision.

Field or valueControlRequired or shown whenHow to use or read itResult
Search register / Filter register by status / Sort registerSearch and two selectsOptional view controls.Search case number, asset code, serial, part number, certificate reference, site or status. Filter returned states; sort newest/oldest by creation or A–Z/Z–A by case identity. Summary totals are not reduced by the local filter.Narrows the authorized case list without changing records.
Exact failed calibration certificateSelectRequired for creation; choose an unused FAIL certificate for the exact instrument.Selection fixes the instrument and pre-fills detection/invalid-from/use dates and laboratory reference. Review the assessment rather than treating defaults as completed investigation.Anchors the OOT case to the original failed certificate and its site/classification.
Scope title / Detected / failed on / Suspected invalid fromText and two datesTitle at least 10 characters; detection must equal the failed certificate date.The invalid interval must start on/before detection and not before the previous passing calibration when one exists. Every affected use must fall inside this interval.Defines the bounded interval for impact assessment.
Measured parameter / Measurement range / UnitThree text controlsRequired; parameter at least 2 characters, range at least 3 and unit at least 1.Use the actual parameter, working range and units from the measurement evidence.Provides context for tolerance and as-found results.
Tolerance minimum / Tolerance maximum / As-found minimum / As-found maximumFour numeric controlsFinite numbers required; tolerance maximum must exceed minimum; as-found maximum cannot be below minimum.At least one as-found limit must lie outside tolerance. A result wholly within the tolerance range cannot create an out-of-tolerance scope.Records the quantified failure without rewriting the certificate.
Measurement uncertainty / Laboratory reference / Accreditation reference / Reference-standard traceabilityThree texts and multiline textRequired; uncertainty at least 2 characters, laboratory/accreditation references at least 3 and traceability at least 10.Retain the uncertainty statement, laboratory/accreditation references and chain to reference standards. These are evidence assertions, not an accreditation lookup.Freezes the measurement provenance.
Failure mode / Impact assessment methodTwo multiline text controlsEach required; at least 20 characters.Explain what failed and how the affected-use population and consequences were assessed.Provides the technical basis for QA review.
Risk / safety Impact / regulatory Impact / customer ImpactSelect and three checkboxesRisk LOW/MEDIUM/HIGH/CRITICAL required; impact checkboxes reflect actual exposure.The lower-case generated checkbox labels are shown here exactly. HIGH/CRITICAL, safety or regulatory exposure cannot later use NO_PRODUCT_IMPACT.Constrains the safety decision without issuing a recall.
Trace completeness / Unresolved scopeSelect and conditional textCOMPLETE or PARTIAL; unresolved text at least 20 characters required only for PARTIAL.State unresolved exposure honestly. Switching completeness clears unresolved text.Retains uncertainty with the immutable scope.
Use key / Usage type / Occurred onRepeatable text, select and date1–100 uses; unique uppercase keys of letters, digits, underscores or hyphens; dates inside the invalid interval.Choose INSPECTION_LOT, FAI, PRODUCT_UNIT, MAINTENANCE_WORK, PROCESS or OTHER. Add Use/Remove manages draft rows; check generated keys for duplicates after removals.Identifies every assessed measurement use.
Governed source / Source referenceConditional select or textGoverned source required for inspection, FAI, product-unit or maintenance use; source reference at least 3 characters.Select the exact governed record; the server checks site and matching reference, and maintenance must concern the exact instrument. PROCESS/OTHER shows a free reference and omits the unused governed source ID.Snapshots the referenced use without changing its source record.
Impact status / AssessmentSelect and text per usePOTENTIAL, AFFECTED or CLEARED and assessment at least 20 characters required.Justify each classification. The safety editor creates one action for every non-cleared use. An all-CLEARED scope proceeds with NO_PRODUCT_IMPACT and zero actions.Distinguishes actionable exposure from uses assessed as clear.
Impact scope evidence / Replacement scope evidenceControlled evidence selectRequired for each scope version.Select one CLEAN immutable version from an active same-site document within case classification. Rejected scopes are replaced, not overwritten.Pins the assessment evidence to the scope version.
Scope submission noteMultiline textRequired; at least 20 characters; current author only.Explain readiness for independent QA approval.Moves DRAFT to SCOPE_REVIEW.
Decision / Independent QA decision / QA decision evidenceSelect, multiline text and controlled evidence selectAPPROVE/REJECT, note at least 20 characters and CLEAN same-site evidence required.An independent QA user checks the invalid interval and affected-use assessment.Approval enables DECISION_PENDING; rejection allows an immutable revision.
Outcome / Decision date / rationale / product Safety Assessment / regulatory Assessment / customer AssessmentSelect, date and four multiline text controlsRequired; each narrative at least 20 characters.Choose NO_PRODUCT_IMPACT, REINSPECTION, STOP_USE_RECOMMENDED or RECALL_RECOMMENDED under the risk constraints. Record all generated assessment fields. Recommendations do not execute stop-use or recall.Stores the independent Product Safety conclusion.
Action type / Quality Engineer owner / Due dateSelect, named-user select and date per non-cleared useExactly one action for every non-cleared affected use; due date on/after decision date.Choose REINSPECT, RECALCULATE, OPEN_NCR, PRODUCT_ESCAPE, STOP_USE_REVIEW or OTHER and an eligible independent owner. This fixed action set is derived from the approved scope.Assigns follow-up accountability for each unresolved/affected use.
Authoritative route / Expected authoritative reference / Description / Success criteriaSelect and three text controls per actionReference at least 3 characters; description and criteria at least 20.Route to QUALITY_NCR, PRODUCT_ESCAPE, INSPECTION, FAI, MAINTENANCE or OTHER. PRODUCT_ESCAPE actions must use that route; RECALL_RECOMMENDED must route every non-cleared PRODUCT_UNIT use to PRODUCT_ESCAPE. Cite the real expected record that will support completion.Defines the source of follow-up evidence, not an automatic record-creation command.
Product Safety decision evidenceControlled evidence selectRequired for the decision.Select CLEAN same-site evidence within case classification for the impact conclusion and assigned actions.Starts ACTION_TRACKING.
Completed on / Exact authoritative reference / Completion summary / Observed resultDate, text and two multiline textsRequired from the assigned owner; summaries at least 20 characters.The response reference must exactly match the expected authoritative reference. For governed routes, the server checks existence within site/classification; OTHER has no source-record existence lookup and relies on controlled evidence. Existence is not proof that the source workflow is closed.Creates an immutable response for independent verification.
Action response evidenceControlled evidence selectRequired for every response version.Select CLEAN same-site proof of the actual follow-up and observed result.Moves the action to PENDING_VERIFICATION.
Decision / Residual risk / Verification method / Observed result / Independent effectiveness evidenceTwo selects, two multiline texts and controlled evidence selectEFFECTIVE/REJECT and CLEAN same-site evidence required; texts at least 20 characters.An independent verifier evaluates the current response. EFFECTIVE cannot retain UNACCEPTABLE risk; ACCEPTABLE or MONITOR is allowed.EFFECTIVE verifies the action; REJECT reopens it for a new immutable response.
Closure summary / Impact conclusion / Residual risk / Independent closure evidenceTwo multiline texts, select and controlled evidence selectRequired at CLOSURE_REVIEW; texts at least 20 characters; risk ACCEPTABLE or MONITOR.Confirm every action remains independently VERIFIED and select CLEAN same-site closure evidence. Closing this assessment does not restore calibration eligibility.Closes the OOT case only, retaining all source records.

Actions and effects

New OOT case / Create case without changing calibration or custody

When to use: An assessor selects an unused failed certificate and a supported, complete scope payload.
What it does: Creates the immutable DRAFT assessment; it does not block or release the instrument.

Submit scope / QA scope / Revise

When to use: The author submits; independent QA decides; a rejected current scope can be replaced.
What it does: Approval enables a separate safety decision. Revision retains the source certificate and the prior history.

Safety decision / Record decision and attributable actions

When to use: An independent Product Safety actor accounts for each non-cleared use and assigns eligible owners.
What it does: Creates ACTION_TRACKING with references to authoritative follow-up; no NCR or Product Escape is automatically created.

Submit response / Verify

When to use: The assigned owner provides exact-reference evidence and an independent verifier evaluates it.
What it does: Rejection preserves the response and reopens the action. Every action verified moves the case to CLOSURE_REVIEW.

Close / Close without changing source records

When to use: Eligible independent QA closes after all actions are verified.
What it does: Stores the impact conclusion without recalibration, stock changes or recall execution.

Lists and states

  • Case cards show asset/serial, certificate, site, classification, current scope, invalid interval, risk and affected-use count. Measurement details and immutable scope history show tolerance/as-found values, assessed source uses and version authors/deciders.
  • Decision/action cards show owner, due date, authoritative route/reference and response/verification versions. A VERIFIED action is an assurance result, not a calibration certificate or proof of physical recall. Closed cases retain the named closer and residual risk.

Authority boundary

Metrology assurance never blocks/releases an instrument, moves stock, closes an NCR, changes an inspection or product unit, executes a recall or sends an external message. Calibration and custody remain authoritative elsewhere. OTHER references are evidence assertions, not validated source-record links; all-CLEARED scope is recorded explicitly as NO_PRODUCT_IMPACT.

Documentation version 2026.09

Last reviewed August 2026