Question 1

OVID inspection reports respond to each question with "Yes," "No," "Not Seen," or "Not Applicable" — with "Not Seen" and "Not Applicable" both requiring a stated reason, distinct from a straightforward "No." Why does the OVID reporting structure treat "I could not verify this" as a category requiring its own justification, rather than simply defaulting an unverifiable item to "No"?

Accepted Answer

"No" represents a confirmed negative finding (the item was checked and found deficient), while "Not Seen" represents an inability to verify (e.g. access was restricted, or the relevant operation was not occurring during the inspection window) — collapsing these into one category would make every inspection report ambiguous about whether something was actually wrong or simply not observed, and the required reason for "Not Seen" forces the inspector to document why verification was not possible rather than silently treating absence of evidence as evidence of failure This distinction protects the integrity of the inspection record — a vessel should not be penalised with a confirmed negative finding for an item the inspector genuinely could not observe, but the inspection also should not let unverifiable items disappear silently. Requiring a documented reason for "Not Seen" achieves both: it avoids unfair negative findings while still surfacing exactly which items the report could not actually confirm.

Question 2

OVID's structure separates the OVPQ (Offshore Vessel Particulars Questionnaire — permanent/semi-permanent vessel features: dimensions, tonnage, crane capabilities, certification) from the OVIQ (the actual inspection questionnaire, completed by the inspector). Why does OVID require the vessel operator to maintain the OVPQ as a separate, standing document rather than having the inspector record all of this information fresh at every inspection?

Accepted Answer

Particulars like dimensions, tonnage, and crane capacity do not change between inspections, so having the operator maintain this as a standing record (which the inspector can verify rather than re-derive from scratch) lets the inspection itself focus its limited time on what actually needs fresh, on-the-spot assessment — current condition, crew competency, operational practice — rather than re-collecting static facts every visit This is a sensible division of labour between a standing-facts document (OVPQ, maintained by the operator) and a point-in-time assessment document (OVIQ, completed by the inspector) — it lets a time-limited inspection focus on what genuinely needs fresh verification rather than re-establishing facts that do not change visit to visit.

Question 3

IMCA M190's Annual DP Trials programme calls for an Independent Witness — "a suitably qualified and experienced individual removed from the day-to-day operational control of the vessel" — to attend, and industry guidance notes this provides "a degree of independence and objectivity to the trials." Why does the value of this independence specifically depend on the witness being removed from the vessel's normal operational control, rather than simply being any additional qualified person?

Accepted Answer

Someone embedded in the vessel's day-to-day operational chain has an inherent stake in the trial result reflecting well on their own normal operating practice, which can unconsciously bias what they notice or how they interpret a borderline result — a witness removed from that operational control has no equivalent stake in the outcome, making their assessment of a borderline pass/fail result more reliable This is the same self-checking-bias principle seen elsewhere in this content library (independent verification of cargo line-ups, second-person checks): someone whose own normal practice is being evaluated has a natural, often unconscious incentive to interpret an ambiguous result favourably. An Independent Witness specifically lacks that stake, which is exactly why the requirement specifies operational removal, not just an additional qualified person.