All articles
Technology10 min readApril 9, 2026

Survey Data Quality Assurance: Ensuring Your ROV Data Meets Client Specs

A technical guide for experienced ROV pilots on positioning accuracy, video quality standards, as-built data validation, KP referencing, and avoiding common QA failures on offshore surveys.

Survey data quality assurance is where operational competence meets technical rigor. Delivering survey data is not the same as delivering good survey data. Clients in the pipeline inspection, offshore infrastructure, and subsea construction sectors have specification documents that define exactly what they require — work that does not meet those specifications will be rejected, re-mobilized, or discounted at final accounting. This guide addresses the key QA dimensions that experienced pilots need to master to consistently deliver compliant survey data.

Understanding Positioning Accuracy Requirements

Before any survey dive, the pilot and survey engineer must be aligned on the positioning accuracy requirement for the specific scope. General route surveys typically require absolute positioning accuracy of 1 to 5 meters (2 sigma), achievable with a well-calibrated USBL system. Detailed structural inspection may require 0.5-meter accuracy. Metrology and tie-in positioning work often requires sub-decimeter accuracy, achievable only with a calibrated LBL array or an inertial navigation system (INS) with LBL aiding, such as the Sonardyne Sprint or Kongsberg IXblue Rovins. Operating with a USBL-only system on a scope that contractually requires INS-aided positioning is a QA failure before the first data point is collected — verify the positioning specification against the equipment on board at the start of every campaign.

Video Quality Standards

  • Resolution: Most clients now specify minimum 1080p HD for inspection video — 4K is increasingly requested for close-up structural work; verify contract requirements before mobilization
  • Frame rate: 25 or 30 fps is standard; high-motion tasks such as thruster-wash cleaning may require 60 fps to avoid motion blur in the deliverable
  • Lighting: Illumination must be sufficient to clearly resolve the inspection target — CP anode condition, weld quality, coating damage — at the working standoff distance; underpowered lighting is a common rejection reason
  • Overlay data: Clients typically require date-time stamp, dive number, KP or structure reference, depth, and heading overlaid on video — verify the overlay format against the specification
  • Compression and codec: Uncompressed or lightly compressed video (H.264 at high bitrate or H.265) is typically required for deliverable footage — heavily compressed footage from low-end recording systems fails QA
  • Continuity: Video must be continuous and uninterrupted during inspection passes — pauses, dropouts, or scene cuts during an inspection sequence are a QA failure
  • Camera calibration: For photogrammetric or measurement applications, camera calibration data must be included in the deliverable package

Automate your dive logs with ThrusterLog

Stop filling out paper forms. ThrusterLog captures every dive detail, keeps your records audit-ready, and works offline.

Download on the App Store

KP Referencing and Pipeline Survey Data

Kilometre point (KP) referencing is the primary spatial reference system for pipeline and cable inspection surveys. Every observation — anomaly location, anode reference, freespan measurement, burial depth — must be referenced to the pipeline KP with sufficient accuracy to be usable for asset integrity management. Pilots must understand the difference between the nominal KP (from the design document), the as-built KP (from the installation survey), and the current-survey KP (calculated during the inspection). Discrepancies between these values must be documented and explained, not silently reconciled. A common QA failure is unexplained KP discontinuities in the data, which arise when the navigation software resets or when the route-following algorithm crosses a pipeline bend with incorrect geometry.

Georeferencing and Coordinate Systems

All survey data must be georeferenced in the coordinate system specified by the client — typically WGS84 or a local projected system such as UTM. Georeferencing errors are among the most damaging QA failures because they are often invisible in the data itself and only emerge when the survey is compared against other datasets. Common sources of error include: incorrect datum transformation between the vessel navigation system and the subsea positioning system, inconsistent application of the acoustic calibration offset, and failure to apply vessel heave, pitch, and roll corrections to the USBL antenna position. Verify the full positioning data chain — from the satellite system on the vessel to the position reported at the ROV — before the survey begins, not after the data has been collected.

As-Built Data Validation

  • Compare the surveyed route against the as-built drawing — flag any route deviations exceeding the tolerance specified in the project survey specification
  • Verify that all structures visited are correctly identified in the dive log and matched to the client's asset register reference numbers
  • Check that all anomaly observations include location reference (KP or structure ID), depth, description, and a still image or video timestamp
  • Validate that CP readings are within the expected range for the cathodic protection system type — anomalous readings must be flagged, not averaged away
  • Confirm that freespan measurements include both span length and maximum gap height, referenced to the pipeline KP at the start and end of the span
  • Verify that burial depth measurements were acquired with a calibrated instrument and that the measurement method is documented
  • Cross-check the dive log data against the video record — every observation in the log should have a corresponding video timestamp

Common QA Failures and How to Avoid Them

  • Positioning system not calibrated before data collection — always perform USBL calibration on every new vessel position before starting survey work
  • Video overlay data incorrect or missing — verify overlay configuration in the control room before splash, not on the seafloor
  • KP referencing lost due to navigation software reset — implement a procedure for re-establishing KP reference after any system restart during the dive
  • Anomaly descriptions too vague to be usable — 'corrosion noted' is not a finding; 'circumferential corrosion at 2 o'clock position, estimated area 150mm x 80mm, at KP 12.450' is a finding
  • Survey data delivered in the wrong coordinate system — verify the output coordinate system with the client's survey team before the first data transfer
  • Incomplete data coverage left unexplained — document any sections of the survey route not inspected and the reason, rather than leaving gaps with no explanation

Quality assurance is not a post-dive activity — it is a continuous process that begins before the dive and ends when the client accepts the deliverable. Pilots who treat QA as a box-ticking exercise at campaign close-out will consistently produce data that requires costly re-work or re-mobilization. Build QA into every dive, every observation, and every data export.

Ready to streamline your ROV operations?

ThrusterLog is available free on the App Store.

Download on the App Store