Measuring It Properly: ISO 19030
This course opened with a promise: the fouling tax detected early, as a clean, quantified drift from a baseline. Three lessons built the capability — monitoring fine enough to see the drift, a pipeline honest enough not to invent it, quality sound enough to defend it. The natural objection remains: says who? By what method, filtered how, compared against what? If every fleet answers differently, no two measurements can be compared and no claim about performance can be checked. ISO 19030 exists to make the answers standard.
What the standard is for
ISO 19030 standardises the measurement of changes in hull and propeller performance over time. Its purpose is to replace rough assumptions and subjective observation with a disciplined method: measure consistently, compare over time, and connect the result to maintenance and operational decisions. It matters because the questions it answers carry money — was the new coating worth it, is it time to clean, what did that propeller polish actually deliver?
In practice the standard is discussed through two routes. Part 2 is the default method: stricter requirements, high-frequency data, higher expected accuracy. Part 3 allows alternative methods with broader applicability but potentially lower accuracy. The choice is not administrative — it decides how much confidence the output deserves. If decisions of consequence hang on the numbers, measurement quality is not a detail; it is the foundation.
Four indicators, four questions
The standard's output is four performance indicators, each answering a question an operator actually asks:
- Dry-docking performance — how does the vessel compare across docking cycles? (Did the yard stay and coating investment pay?)
- In-service performance — how is performance evolving within this docking cycle? (The fouling drift of lesson one, made official.)
- Maintenance trigger — has degradation crossed the threshold where intervention pays for itself?
- Maintenance effect — what did that cleaning or polish measurably deliver? (The before/after, quantified instead of asserted.)
Where implementations fail
ISO 19030 leans entirely on data quality — and that is where it breaks. The primary inputs are speed through water and delivered power, with the default method requiring high-frequency measurement. Around them stand the secondary parameters — wind, waves, water depth, temperature, draught, trim, rudder activity — without which records cannot be properly filtered and normalised.
The recurring failure points are exactly the ones this course has been circling: poor sensor quality, insufficient acquisition rates, weak data handling, incomplete normalisation. In such cases the framework exists on paper while the output is too noisy to support confident decisions — the standard's name lending authority to numbers that have not earned it. That is the trap to respect: ISO 19030 is a test of data discipline before it is a measurement method, and implemented without the discipline it creates something worse than ignorance — false confidence.
Implemented well, it is the payoff of everything so far: honest sensors, an engineered pipeline, defensible quality — condensed into indicators a technical manager can act on and defend.
Go deeper: the original article Measuring Hull & Propeller Performance with ISO 19030.