Study guide

9.1 Auto DP Mode

Nautical Institute DP Operator DPO

Track your progress as you read

Finished sections get a check mark.

1 Introduction & NI Scheme

1.1 Current Exam Facts 1.2 Phases A–E Pathway 1.3 Certificates, Eligibility & Revalidation

2 DP Principles Fundamentals

2.1 What is Dynamic Positioning & Degrees of Freedom 2.2 Seven Components of a DP System 2.3 The DP Operator & Human-Machine Interface

3 Controller, Model & Environmental Sensors

3.1 DP Controller & Mathematical Model 3.2 Kalman Filtering & Current Estimation 3.3 Gyrocompass & Heading Feedback 3.4 Wind Sensor, MRU & UPS

4 GNSS & Acoustic Position References

4.1 DGNSS & Differential Correction 4.2 Relative GNSS / RTK Concepts 4.3 Hydroacoustics USBL/SSBL 4.4 Long Baseline (LBL) Systems

5 Relative PRS, Selection & Voting

5.1 Light Taut Wire 5.2 Laser Relative References (Fanbeam/CyScan) 5.3 Radar/Microwave Relative References (RadaScan) 5.4 Reference Selection, Voting & Common-Mode Failure

6 Power Generation & PMS

6.1 Diesel-Electric Power Architecture 6.2 Power Management System 6.3 Load Sharing, Load Shedding & Spinning Reserve

7 Bus Configuration & Power Failures

7.1 Open vs Closed Bus-Tie 7.2 Blackout & Blackout Recovery 7.3 Drive-Off vs Drift-Off

8 Thrusters & Allocation

8.1 Tunnel, Azimuth & Retractable Thrusters 8.2 Thrust Allocation, Forbidden Zones & Bias 8.3 Thruster Interaction & Faulty Thruster Response

9 Control Modes

9.1 Auto DP Mode 9.2 Joystick & Independent Joystick System 9.3 Mode Selection & Practical Setup

10 DP Equipment Classes

10.1 IMO Equipment Classes 1, 2 and 3 10.2 MSC.1/Circ.1580 vs MSC/Circ.645 10.3 Sensor Redundancy & 2-out-of-3 Voting

11 FMEA, Worst Case Failure & Consequence Analysis

11.1 FMEA & Annual DP Trials 11.2 Worst Case Failure 11.3 Consequence Analysis

12 ASOG, CAM & TAM

12.1 Activity Specific Operating Guidelines (ASOG) 12.2 Critical Activity Mode (CAM) 12.3 Task Appropriate Mode (TAM)

13 Capability Plots & Approach Planning

13.1 DP Capability Plots 13.2 Footprint Plots & Weather-Optimal Heading 13.3 500 m Zone Approach & Escape Routes

14 Watchkeeping & Industry Guidance

14.1 Watchkeeping & Handover 14.2 Checklists, Alarms & Time to Terminate 14.3 IMCA M103/M117 Guidance Context

15 Integrated Operations & Assessment Strategy

15.1 Multi-System Failure Scenarios 15.2 Integrated Operations Case Studies 15.3 Induction Assessment Strategy

9.1 Auto DP Mode

Key Takeaways Explain This Topic AI

Auto DP is full automatic closed-loop control of surge, sway, and yaw to selected position and heading setpoints using the model, PRS, sensors, and thrust allocation.

Use Auto DP for sustained station-keeping and heading hold when references, thrusters, and power are healthy and the model has been allowed to settle.

After enabling Auto DP, allow a settling period: watch residuals, thruster activity, and footprint before declaring the vessel ready for critical work.

Gains and model quality affect aggressiveness and stability at a conceptual level—too high causes thruster chatter; too low causes lag and large position errors.

Alarms in Auto DP do not pause operational judgment: treat reference, thruster, power, and model-measurement alarms as cues to investigate, degrade, or drop mode per ASOG.

Last updated: July 2026

Auto DP is the default station-keeping mode for critical work

Auto DP (also called full automatic DP, automatic position and heading control, or similar vendor labels) is the control mode in which the DP system automatically maintains the vessel’s position and heading at selected setpoints . In the three degrees of freedom that matter for station-keeping, the controller continuously closes the loop on:

  • Degree of freedom Motion name What Auto DP holds
  • Surge Fore–aft translation Position along ship’s longitudinal axis (or Northing/Easting in earth frame)
  • Sway Port–starboard translation Position along ship’s transverse axis
  • Yaw Rotation about vertical axis Heading setpoint

The operator does not continuously push a joystick to hold station. Instead the operator selects position and heading setpoints (or freezes present position/heading as setpoints), enables thrusters and references, and monitors the system while the controller generates force demands and thrust allocation logic (TAL) distributes them among enabled thrusters.

What “full automatic” does and does not mean

Does mean:

  • Continuous closed-loop correction of surge, sway, and yaw toward setpoints
  • Use of the mathematical model , estimator (often Kalman-based), PRS, gyro, wind, and MRU inputs as designed
  • Automatic thruster allocation within enable/power/forbidden-zone limits
  • Operator focus on supervision , alarms, weather, and operational status—not hand-flying every thruster

Does not mean:

  • The system is unsupervised or “set and forget” for hours without watchkeeping
  • Every failure is self-healing without DPO action
  • Auto DP is always available regardless of reference quality, thruster set, or power plant health

The vessel cannot move—setpoints can be changed deliberately (slow moves, approach tracks) while remaining in automatic control

Contrast with joystick mode (next section), where the operator commands translation (and often heading) manually while TAL still allocates thrusters. Contrast also with pure manual thruster control, where individual levers or local panels drive units without the DP position loop.

When Auto DP is used

Auto DP is the mode of choice whenever the operational goal is stable station-keeping or controlled automatic manoeuvring under DP:

Situation Why Auto DP fits

Holding near a platform, FPSO, or buoy for cargo, ROV, dive, or construction Continuous correction without operator fatigue

  • Critical activity modes under ASOG/CAM Predictable closed-loop behaviour with consequence analysis online
  • Weather-optimal heading hold with fixed worksite position Auto heading + auto position together
  • Long waits on location after setup Model and references keep footprint tight if plant is healthy
  • Simulator assessment “hold position” tasks Matches NI Phase C expectation for supervised automatic control

Auto DP is not always the right first mode during approach from open water, during gross repositioning when the operator wants direct feel of force, or when references are degraded and the DPO must take immediate manual combined thruster control (joystick or IJS). Mode selection is covered in Section 9.3; the principle here is: Auto DP for sustained automatic hold/track once the system is ready.

Enabling Auto DP and the settling period

A common exam and simulator failure is selecting Auto DP and immediately assuming the footprint is “locked.” Real systems need a short settling interval after enable or after major changes.

Typical enable sequence concepts (vendor menus differ; the logic is common):

  • Confirm power and thrusters available; thrusters enabled for DP
  • Confirm adequate independent PRS online and selected
  • Confirm gyros, wind, MRU healthy
  • Build or accept the model estimate (vessel may have been in joystick or another mode while the model adapts)

Set or freeze position setpoint and heading setpoint (present position / present heading is common when already roughly on location)

Select Auto DP (or Auto Position + Auto Heading, depending on HMI)

Watch settling : thruster activity often peaks briefly as the controller corrects residual errors, then should quiet toward a steady allocation pattern for the weather

During settling, expect:

  • Temporary thruster bias or higher RPM while errors shrink
  • Model vs measured residuals to converge toward normal bands
  • Possible soft alarms if gains or reference noise are high—investigate, do not ignore
  • Footprint plots or position history to show oscillation damping rather than growing walk-off

Do not start critical simultaneous operations (hose connect, dive basket launch under tight offset limits, heavy lift within a tight watch circle) in the first seconds after enable. Allow the system—and yourself—to confirm that Auto DP is actually holding.

Gains and model considerations (conceptual level)

Induction exams do not ask you to tune PID coefficients by number. They do expect conceptual understanding that controller gains and model quality change how Auto DP behaves.

Concept Too aggressive / poor Too soft / poor Operator implication

Position/heading gains Thruster chatter, oscillation, high wear Large lag, slow recovery, oversized footprint Prefer settings proven for vessel and condition; change only under procedure

Model fidelity Wrong draft/load/thruster status → wrong force prediction Residual “current” absorbs unknown forces but can mask faults Keep thruster enables truthful; watch model–measurement split

Reference quality Noisy PRS drives noisy thruster demand Sparse PRS leaves model free to drift Maintain multi-PRS voting; do not “auto through” single wild references

Power/thruster limits Saturation → inability to meet demand despite high gains Artificial disable of thrusters shrinks capability Gains cannot invent force that TAL cannot allocate

Key exam idea: if thrusters thrash after Auto DP enable with good weather, think noise, gains, or settling , not instantly “drive-off.” If the vessel slowly walks off with thrusters hard over, think capability vs weather , bad reference , thruster not producing , or wrong setpoint —not “turn gains up blindly.”

Alarms while in Auto DP

Auto DP does not silence the alarm philosophy. Common families of alarms while automatic control is engaged:

Alarm family Examples Typical DPO response direction

Position / footprint Position warning/alarm, large excursion Assess weather, thrusters, references; prepare degrade or escape

PRS Reference rejected, frozen, high residual, voting conflict Deselect bad PRS; ensure remaining independence

Heading / sensors Gyro discrepancy, wind sensor fault, MRU fault Switch to healthy sensor path; watch yaw control

Thruster Feedback fault, fail-to-follow, overheat, offline Disable bad thruster if required; reassess capability

Power / PMS Generator trip, bus event, thruster power limit Coordinate with ECR; may need mode change or stop work

Model / system Model–measurement deviation, consequence analysis alarm Investigate residual cause; follow ASOG red/yellow actions

Operator / mode Mode change, setpoint change, offline panel Confirm intentional vs accidental

Important

An alarm in Auto DP is not automatically a reason to stay in Auto “because the computer is still running.” Consequence analysis or ASOG may require stop work , change setpoint/heading , drop to joystick , or escape while thrusters still respond.

Worked Auto DP scenarios

Scenario 1 — Clean enable. Vessel is 20 m from setpoint after joystick approach. DPO freezes present position as setpoint only after PRS are stable, enables Auto DP, watches thrusters settle for a short period, confirms footprint within limits, then allows deck work to start. Correct discipline.

Scenario 2 — Enable during wild PRS. DPO selects Auto DP while one laser reference is swinging. Thrusters thrash; position alarm follows. Correct action is deselect the bad PRS and re-settle, not raise gains or blame allocation alone.

Scenario 3 — Alarm during steady Auto DP. Consequence analysis warns that after worst-case thruster loss, remaining capability is insufficient in rising wind. Work stops or degrades per ASOG even though Auto DP is still holding now.

Exam traps for Auto DP

  • Trap Correction
  • “Auto DP means joystick free, no watch required” Supervision and alarm response remain continuous

“Joystick and Auto DP are the same because thrusters still allocate” Auto closes the position/heading loop ; joystick is operator demand

  • “No settling needed after enable” Always allow and verify settling before critical work
  • “Gains fix every large position error” Capability, PRS, and thruster health matter more than gain knobs
  • “Alarms in Auto can be deferred until end of shift” Treat alarms as operational triggers per checklist/ASOG

Bottom line: Auto DP is full automatic control of surge, sway, and yaw to position and heading setpoints . Enable it when the plant is ready, settle after enable, understand gains and model only at the response/stability level, and treat alarms as reasons to think and act—not as background colour on the HMI.