E.14:6.3 - Pump-vibration measurement: short recognition, exact assurance underneath

Recognition text. Pump-37 vibration at 09:00 was 2.1 mm/s with stated uncertainty 0.2 mm/s under the current inspection method. A maintenance reader can use that bounded statement and stop before the machinery below. It does not by itself say the pump passes a maintenance criterion, that work may start, or that any gate or permission is current.

Assurance text. This worked slice elects empirical assurance for a current reliance question. Pump37InspectionPlan-E3, admitted as a U.WorkPlan, had designated the intended measurement and selected PumpVibrationMeasurementMethod-E2, admitted as a U.Method; it cited PumpVibrationProcedure-E5, admitted as a U.MethodDescription, only for the setup and calibration claims used by the plan.

The measurement domain declares PumpVibrationMeasurementAssignment as the assignment species for this work. RA-ConditionMonitoring-7-E4 is its occurrence, is held by ConditionMonitoringSystem-7, and covers the measurement interval. That System performed the admitted Work Pump37VibrationMeasurement-2026-07-31T0900 under the assignment, and the Work enacted PumpVibrationMeasurementMethod-E2. Check the Work and enacted Method with A.15.1, and the Work-assignment attribution with F.6. The applicable A.6.1 bindings identify Pump-37, the sensor indication, calibration coefficients, and returned measurement value. Classification of the System under PumpVibrationMeasurementSystemRole is a separate claim.

Use C.16 to characterize the domain-local measurement result by its exact Characteristic, Scale, unit, uncertainty, time stance, and interpretation basis. C.2.1 identifies Pump37VibrationResult-E4, the episteme that states that result. A.10 path Pump37MeasurementProvenancePath-E6 cites the calibration, Work, bindings, and source publications; B.3 assurance claim Pump37MeasurementAssurance-E2 qualifies only the stated use and window. Neither provenance nor assurance is the measurement result. No A.15.PROD claim is needed merely because the result episteme exists; open it when a separately current question concerns the Work’s productive treatment, the episteme’s identity inception, or satisfaction of a production-completion condition. The inception branch specifically asks whether the exact measurement Work first constituted that episteme.

What changes in practice. A reader sees the usable statement first, can inspect the exact Work, result, and support chain when reliance matters, and uses the applicable maintenance-criterion, readiness, gate, or permission pattern if the next decision asks one of those different questions.