Scenarios & Project Examples

Scenarios & Project Examples

Every underwater mission is project-specific. The following scenarios show typical project configurations, deliverables and documentation logic for ROV inspections.

3 sectors 3 typical scenarios Structured deliverables Reproducible documentation

Typical scenarios

Three typical scenarios from three sectors — with identical demands for documentation depth and reproducibility.

Ports & marine construction Example scenario ROV inspection

Example scenario Ports & Marine Construction — quay wall and dolphin inspection

Typical situation: A port operator wishes to document the condition of several dolphins and a quay wall section — for example as the basis for maintenance planning or a recurring structural inspection. Conventional diver operations are costly and often produce only verbal protocols without a comparable data basis.
Approach: ROV inspection with HD camera and lighting. Systematic traversal of structures along a defined route with video recording. Targeted stills at damage locations, biofouling zones and joints. Harbour operations typically continue.
Result: Structured findings report with image references, damage classification and recommended actions. Handover to the planning engineering office within a few working days depending on scope.
Deliverables: HD video · selected stills (e.g. 100–200 depending on scope) · damage classification table · findings report (PDF) · method protocol with route for follow-up inspection.
Scope: 3 mooring dolphins + approx. 120 m quay wall Duration: approx. one day, depending on current and visibility Diver logistics: can be reduced or partially replaced depending on the task

Linked clusters: Sector Ports & marine construction · ROV inspection · ROV vs. Diver

Industry & energy Example scenario ROV + Sonar (optional)

Example scenario Industry & Energy — basin or cooling water inspection

Typical situation: An industrial or energy operator wishes to inspect a cooling water, process water or storage basin without fully interrupting operations. Draining is often neither economically nor operationally feasible — for example with facilities that continuously supply cooling or process water.
Approach: ROV deployment, depending on visibility, geometry and safety requirements. Optional sonar support for areas with restricted visibility caused by suspended matter. Video coverage of floor, walls and inlet sections along a documented route.
Result: Documentation of visible deposits and condition features. Report with comparison photos as a possible monitoring baseline for future recurring inspections. Basis for internal maintenance planning and budgeting.
Deliverables: HD video · optional sonar dataset · selected stills · deposit map · monitoring baseline report · reproducibility memo for the follow-up inspection.
Scope: e.g. 500–1000 m² basin area Duration: depending on geometry and visibility Operational interruption: often avoidable or reducible, depending on safety clearance and facility

Linked clusters: Sector Industry & energy · ROV inspection · Sonar & scanning · Monitoring

Authorities & municipalities Example scenario Structural inspection

Example scenario Authorities & Municipalities — bridge pier inspection

Typical situation: A public body, planning office or asset owner needs a traceable underwater condition survey of bridge piers or other hydraulic structures. Requirement: authority-ready documentation that can flow into an inspection file or structural database without rework.
Approach: ROV inspection of each pier on all four sides, from waterline to riverbed. Documentation of scour, biofouling, concrete condition and joints along a reproducible route.
Result: Photo documentation with position reference per pier, summary report in a format suitable for the inspection file. Used as a comparison baseline for future inspection cycles — the first data point of a time series.
Deliverables: HD video · position-referenced stills (e.g. 100–200 depending on scope) · findings report in a format suitable for inspection files · damage classification · method and reproducibility memo · handover-ready data structure for inspection file or structural database.
Scope: e.g. 4 bridge piers depending on the structure Duration: depending on current, visibility and structure size Diver logistics: can be reduced or partially replaced depending on the task

Linked clusters: Sector Authorities & municipalities · ROV inspection · Monitoring

What a ScanSustain project typically delivers

Regardless of sector and asset, every project ends in a structured data package. These three building blocks are the minimum delivery — scope and format are agreed in the briefing.

Raw data package

Video, photos, sonar — chronologically sorted, with time and position reference. Directly archive-ready, without post-processing.

Structured findings report

Summary with image references, damage classification and action recommendations — in the format of the commissioning body.

Reproducibility memo

Method protocol and route for every follow-up inspection. Ensures the next survey connects as a time series.

Typical project workflow

Five steps with defined input and output — the shared path of every mission. Fully documented on the process page.

1. Briefing

Goal, area, conditions and reporting format are clarified — by phone, email or a brief meeting.

2. Mission

ROV operation from shore, jetty or vessel. Live feed on request. Systematic capture along a defined route, without operational downtime.

3. Handover

Structured data package: video, photos, report and reproducibility memo — within a few working days after the mission.

Which projects fit ScanSustain?

The three scenarios cover three sectors. The methodology works in all other sectors too, fully documented in the sector overview:

Frequently Asked Questions

What does a typical project look like?

After a short briefing we plan the mission, carry out the ROV deployment on site and deliver the results in a structured data package. The ScanSustain process describes the five steps in detail.

Can you deploy at short notice?

Yes. Depending on scope and travel distance, short-notice deployments are possible — particularly important for casualties, damage events or post-flood surveys. For plannable projects we recommend a brief lead time for route and target planning.

In which waters can you operate?

In fresh and salt water, harbours, rivers, lakes, basins and industrial facilities — as long as water access is available. ROV missions are usually permitted even in protected areas and sensitive conservation contexts because the deployment is non-contact.

Are results comparable over multiple years?

Yes — that is the central advantage over conventional diver deployments. Every initial survey is archived with method protocol and route. The follow-up inspection can reproduce the same path.

Are the scenarios on this page real customer projects?

The scenarios shown here are illustrative example configurations and demonstrate typical project flows, deliverables and documentation logic. Concrete scope, durations and outcomes are determined for every project based on the actual conditions.

Related pages

Similar project? Tell us in the briefing which deliverables you need.

Brief a mission
Plan inspection