What an ROV is and how it differs from other technologies
An ROV is an unoccupied underwater vehicle operated remotely, usually connected through a cable or umbilical providing communication and control. NOAA distinguishes it from an autonomous underwater vehicle, or AUV, which operates without the same continuous tethered control. The informal term «underwater drone» can obscure this distinction.
Inspection planning should identify the particular system and operating mode. Vehicles do not all have the same sensors, manipulators or positioning capabilities. An observation vehicle should not be treated as a heavy intervention platform. Nor is every robot travelling through a pipe a free-swimming ROV. These distinctions prevent procurement of a capability the equipment does not possess or comparison of proposals that address different problems. The intended use should be established before specifications are compared or a supplier demonstration is interpreted.
Sources: [1]
What information it can provide about a pipeline
The Bureau of Reclamation’s original 2022 technical report examines ROV applications and data collection technologies, including visual observation and other instrumental methods. It describes capabilities and selection needs; it does not establish that every vehicle can perform every test or endorse manufacturers commercially.
For a submerged pipeline, the question may involve locating an area, observing its surroundings or documenting a condition needing further examination. Define whether information is required about the exterior, interior or associated components. An external image does not establish the condition of the entire wall or automatically replace a specialised test. The inspection report should distinguish observations, inferences and matters that could not be checked with the available equipment and conditions. This makes the evidence usable without overstating what it establishes.
Sources: [2]
Relationship with occupational safety and health
The potential preventive value is obtaining information remotely and reducing particular needs for human presence underwater. The decision should compare the complete mission with alternatives: preparation, deployment, operation, recovery and data processing. Avoiding a dive does not eliminate every occupational risk.
Assessment should identify which exposure is reduced and which new surface tasks arise. It should also explain when results support a decision and when another technique is needed. Presenting an ROV as a universal replacement for divers or a guarantee against accidents would be incorrect. Benefits need to be demonstrated for the particular intervention and remain conditional on system capability, team competence and authorised planning. A useful comparison considers both the evidence obtained and the practical work required to obtain it safely, rather than focusing only on the absence of a person underwater.
Plan before selecting equipment
IMCA R004 addresses tasks, environment, operations, equipment, personnel and responsibilities in offshore ROV use. The identified public edition is revision 6 of February 2024. Consulting its scope does not provide a complete operating procedure for a mission.
As a procurement approach, begin with the technical question, the asset and the required outcome. Then establish whether a supplier can obtain sufficient evidence under expected conditions and which circumstances would require suspension or replanning. The agreement should assign responsibility for directing operations, interpreting data and deciding what happens to the asset. These functions may require different competencies and should not remain implicit in purchasing a vehicle. Clear responsibilities also help determine who can accept incomplete coverage and who must arrange additional examination before a conclusion is issued.
Sources: [3]
Image, access and positioning limits
Technical review should examine visibility, geometry, water conditions, access and the ability to locate each observation. An attractive video is insufficient: an anomaly without adequate location references may be difficult to find again. The team should also know which parts of the asset remained outside the observed field.
Evidence needs to show when it was obtained, which area it represents and which limitations affected interpretation. Absence of a visible anomaly does not establish absence of defects beyond the method’s detection capability. If measurements are required, identify the instrument producing them and its validation. Visual estimates should not become precise figures without a documented technical basis. Agree these limitations before the mission and retain them visibly in the final report, rather than relegating them to an undocumented verbal qualification.
Sources: [2]
Residual risks and surface coordination
A preventive framework for the full operation should review preparation, equipment handling, deployment, power supply, cable management and recovery. Specific controls belong with competent personnel and the conditions at the site. A technology description does not replace assessment of these tasks.
The organisation should coordinate access, other activities and communication between vehicle operators and those managing the installation. Define how changed conditions are communicated and how activity is stopped when it no longer matches the plan. Document maintenance and system checks. Remote operation can transfer demands to a control station, so sustained attention, handovers and workstation ergonomics also deserve review. The operation should remain manageable when personnel change or an unexpected interruption occurs, rather than depend on one operator remembering every detail of a long mission.
Sources: [3]
Combined operations with divers
IMCA D054/R020, revised in October 2026, specifically addresses combined ROV and diving operations. Its public scope highlights planning, risk assessment, communication, responsibilities and emergency preparedness. Coexistence requires its own coordination; it cannot be assumed safe merely because the vehicle is unoccupied.
A combined-operation decision belongs to the competent team and applicable requirements. This article does not provide separation distances, manoeuvres or rescue instructions. As an organisational criterion, the plan should identify interfaces and stop-work authority and confirm that participants understand the same framework. Mission changes should not be introduced informally during execution without reviewing consequences for people who may be underwater. The review needs to include everyone whose activity affects that shared environment, rather than treating vehicle operations and diving as unrelated contracts.
Sources: [4]
Data, traceability and asset assessment
A proposed record structure can separate original files, operator notes, technical observations and specialist conclusions. Link each element to the relevant asset and mission. When images are processed, retain originals and document transformations relevant to interpreting the result.
If automated analysis is used, verify detections for their intended purpose; an on-screen marker is not a confirmed defect. Decisions to repair, continue monitoring or use another technique require technical criteria and assigned responsibility. Access to sensitive infrastructure information also needs control. A management system can support tracking and evidence, but should not mark an inspection complete merely because video has been uploaded without anyone reviewing its scope. Review should establish whether the original question has been answered and preserve any uncertainty that remains material to the asset decision.
Sources: [2]
A hypothetical application
The owner of a submerged pipeline needs to document an area before planning maintenance. Specialists define which information remote observation can obtain and which questions require other methods. The planned mission includes location references and a criterion for declaring an observation insufficient.
After inspection, one part has useful images while another remains unassessed because of conditions encountered. The report preserves this distinction, assigns technical review and proposes an authorised next step for the unresolved area. It does not declare the whole pipeline sound simply because the route was completed. The preventive outcome is a better-informed decision and more precise exposure planning, without promising complete risk elimination or attributing unproven capabilities to the vehicle. The example illustrates management of evidence, not a field operating procedure or an integrity certification.
Useful indicators and comparison mistakes
Monitoring can cover resolved inspection objectives, areas with sufficient evidence, outstanding observations, repeated missions caused by incomplete data and verified closure of resulting actions. Also record operational incidents and conditions requiring suspension or change. These data can improve selection and planning.
Video hours, distance travelled or equipment dives do not independently demonstrate preventive quality. Comparison with another technique should use equivalent missions and consider access and detection limits. If avoided human exposure is estimated, explain the alternative scenario rather than present an estimate as a proven accident prevented. The most useful indicator connects collected information with a verifiable technical decision and the measures used to carry out the work. This keeps the evaluation focused on practical outcomes instead of treating technological activity as its own justification.
Integration into maintenance and OSH
ROV use connects with digital inspections, maintenance safety and underwater work. Planning should retain scope, responsibilities, operating conditions, results and follow-up actions. A detected anomaly needs an owner and deadline; an inspection limitation needs an explicit decision about how uncertainty will be resolved.
Before reusing an earlier plan, review changes in the asset, environment, equipment and participants. Mission learning can improve later contracts and acceptance criteria. This continuity prevents technology acquisition from becoming detached from actual infrastructure maintenance. The aim is not to accumulate images but to obtain sufficient evidence through a planned operation and use it competently to protect people and manage the asset. Records should make that connection visible to future reviewers, including those who did not participate in the original inspection.
Sources: [3]
Frequently asked questions
Is an ROV the same as an AUV?
No. An ROV is remotely operated, usually through a tether; an AUV performs autonomous operations. The specific system mode should be checked.
Can it replace every diver inspection?
No. Suitability depends on the mission, access, instruments and required evidence. Some tasks can be remote and others need a different strategy.
Does video showing no visible defects prove integrity?
No. It establishes only what the method could observe. Coverage, limitations and requirements for other tests must be stated.
What should the provider deliver?
Agreed scope, traceable data, conditions and limitations, reviewable results and clear interpretation and follow-up responsibilities, alongside operational documentation.
