Prepare for DPB by learning the station-keeping chain as one connected system: position and heading references, vessel sensors, power generation, and thrusters all feed a computer controller that must know where the vessel is, where it should be, and what force is needed. Practise by tracing faults through that chain on paper, comparing reference systems, and distinguishing drift-off from drive-off before checking readiness against a self-set rubric.
The station-keeping loop: what DP actually does minute by minute
Dynamic positioning is a computer-controlled system that keeps a vessel on station and heading using thrusters, without anchors. Learn it as a closed loop: measure, compare, compute force, command thrusters.
Start by naming the loop's four inputs and one output. Inputs: position references (where the vessel appears to be), heading sensors (which way the bow points), environmental measurement such as wind (what is pushing the vessel), and the operator-set or operator-accepted position and heading. The output is force commands distributed across available thrusters. Every DPB topic you meet is either one of these inputs, the controller between them, or a failure mode somewhere along the chain.
Now apply the loop to an everyday observation: a vessel holding station in a rising crosswind. Wind measurement changes first, the controller predicts the growing force before position error even develops, and thrust is redistributed. Contrast that with a sudden reference failure, where the controller no longer knows where it is and must fall back on whatever inputs remain. Recognising whether a scenario describes a force problem or a knowledge problem is the core reasoning habit to build before any other study.
Write the loop from memory as four boxes and one arrow diagram, then label each box with at least two components from your course material. You should be able to say, for any component, whether it measures position, heading, environment, or produces force. If you cannot place a component in the loop, you do not yet understand it; return to that item rather than rereading whole chapters.
- Measure: position references, heading sensors, environmental sensors
- Compare: controller holds the vessel against a set point
- Act: thrusters receive force commands split across units
- Feed back: every action changes the measurements, closing the loop
Position references versus vessel sensors: a distinction the syllabus separates
Position references tell the controller where the vessel is relative to the outside world; vessel sensors (gyrocompass, motion unit, wind sensor) tell it the ship's own state. They fail differently and are treated differently.
Position reference systems each answer the same question in a different way. A satellite-based reference solves ranges to satellites and compares with a correction source. An acoustic system measures range and bearing to a transponder deployed on the seabed. A taut wire measures angle and length of a tensioned wire running to the seabed or a clump weight. Laser and radar-based systems track a fixed or vessel-mounted target at known coordinates. Vessel sensors, by contrast, are internal: the gyro for heading, the motion reference unit for vessel attitude, the wind sensor for environmental force.
The distinction matters because of how each group fails. Internal sensors usually degrade on their own terms: a gyro drifts, a motion unit output stops matching the vessel's motion. External references fail from outside causes: an acoustic transponder is lost or blocked, a surface target is obscured, and satellite signals can be degraded or denied by interference, which industry bodies such as IMCA have addressed in dedicated guidance on jamming and spoofing impacts for DP. When you study a reference system, always ask what environmental conditions it needs and what makes it disagree with the others.
Cross-checking is the operational answer. A controller, and a competent operator, never trusts one reference implicitly; agreement between independent systems is the evidence that position knowledge is sound. In your notes, group every reference system by two qualities: independence from the vessel's own systems, and independence from the seabed or from satellites. Systems that are independent in different ways are worth having together, and this logic explains why DP vessels carry a mix.
| Reference system | Working principle | Works well when | Watch out for |
|---|---|---|---|
| Satellite-based (DGNSS) | Ranges to satellites with differential corrections | Open sky, corrections available | Signal interference, jamming, spoofing, shadowing |
| Hydroacoustic | Acoustic range/bearing to a seabed transponder | Deep water operations with clear acoustic path | Depth and terrain limits, acoustic noise, transponder loss |
| Taut wire | Angle and payout of a tensioned wire | Limited water depths, stable seabed attachment | Wire angle grows with depth and scope, current bend |
| Laser-based | Tracks a passive target on a fixed structure | Close to installations with visible targets | Fog, rain, line-of-sight obstruction |
| Radar-based | Tracks a coded radar target or reflector | Range beyond laser, moderate weather | Target obscuration, radar interference |
Drift-off versus drive-off: one word of difference, opposite causes
Drift-off is the vessel moving off position because available thrust is insufficient; drive-off is the vessel moving because thrusters apply wrong or excessive force. The diagnosis and response differ completely.
Scenario 1 (worked). A DP vessel is holding station when one engine trips, reducing available power; shortly afterwards the remaining thrust can no longer match the growing current, and the vessel slowly moves off the set point. A plausible mistake in reasoning here is to call this a drive-off and suspect the controller of commanding wrong thrust. Trace the chain instead: position knowledge was intact, the controller behaved correctly, but total available force dropped below the environmental demand. The correct classification is a drift-off, and the reasoning that follows is about capability and environment, not controller error.
Why the distinction matters: classifying the event determines what you look at next. For a drift-off, you examine power availability, thruster availability, and environmental margin, and the vessel's movement is typically gradual and down-weather. For a drive-off, you suspect a fault in the control chain itself: a wrong position input, a heading error, a faulty thruster feedback. Movement is often rapid and in an unexpected direction, which is exactly why drive-offs are treated with such urgency in DP practice. Build the habit of asking first: did we lose force, or gain wrong force?
Practise by writing six short paper faults, three of each type: an engine trip, a thruster trip, rising current for drift-offs; a corrupted heading input, a reference feeding the controller a false position, a thruster responding to a wrong command for drive-offs. For each, state in one sentence what the vessel does and which box of the loop the fault sits in. Correct self-check: all six classified with the fault located in the right subsystem.
Degraded satellite position: a scenario in trusting and cross-checking
Satellite positioning is only one input among several. A scenario that degrades it tests whether you cross-check references and react to quality indications instead of assuming the position display is always right.
Scenario 2 (worked). During a hold, the satellite-derived position begins to wander a few metres, while an acoustic reference and a radar reference hold steady and agree with each other. A plausible mistake is to accept the satellite display as authoritative because it is the familiar, bridge-mounted source, and to try to adjust the set point to it. Trace the chain: two independent references disagree with a third, the controller sees conflicting position inputs, and the operator's decision is about which inputs to trust and how the controller weighs them, not about moving the vessel.
The better decision is to treat the outlier as suspect, verify with the agreeing references and with visual or radar observation where available, and manage the controller's use of those inputs according to the vessel's procedures. This is precisely the situation IMCA guidance on GNSS jamming and spoofing addresses: satellite signals can be degraded deliberately or accidentally, and DP operations must plan for loss of that input. The lesson for study is that no reference is privileged; trust is earned by agreement among independent sources and lost by unexplained deviation.
Turn this into a recurring question while you study: whenever a scenario shows one system disagreeing with others, immediately list (1) which systems agree, (2) what could make the outlier wrong, and (3) what the operator controls in that situation. You should finish able to explain why independent sources with different failure modes are carried together, and why quality indications matter as much as the position number itself.
Redundancy and equipment class: why the same fault is serious on one vessel and survivable on another
Redundancy means the vessel can lose a component and keep station. Equipment class describes how much single-fault tolerance the DP system design provides, from a single failure causing position loss to designs that tolerate a fire or flooding compartment.
Learn the class concept by its logic rather than by rote labels. One end of the scale: a single fault anywhere in the DP system can cause loss of position, so the vessel suits operations where that consequence is acceptable. Further along: the design tolerates any single technical fault without losing position, achieved by splitting power, control, and thrusters so one fault removes only a fraction of capability. At the top: even a loss of one compartment, such as a fire or flood, leaves the vessel able to hold station. The class of the vessel is matched to the criticality of the operation it performs.
Connect this to scenarios. In the drift-off example from earlier, whether that engine trip causes position loss depends entirely on the design: on a low-redundancy vessel it may be decisive, on a higher-class vessel the remaining machinery simply absorbs the load. When a DPB question mentions equipment class, ask which failures the design is intended to survive and which operation justifies that level. Distinguish, too, between the installed equipment class and how a vessel is actually operated and documented; the class concept lives in the design, and operational acceptability is assessed for the specific task.
Study exercise: take three paper vessels, A with no single-fault tolerance, B with any-single-fault tolerance, C with compartment-loss tolerance. For each, write which single faults would cause loss of position and which would not. Expected observation: for A, almost any technical fault is critical; for B, no single technical fault is; for C, only faults destroying a whole compartment are. If your three lists do not show that pattern, revisit the class definitions before moving on.
A paper reference-system audit: your main practice exercise
The best DPB exercise is a written audit of a fictitious DP operation: choose the vessel's references, justify the mix, predict failures, and grade your own reasoning against a fixed rubric.
Set up the scenario on paper: a support vessel holding station alongside a fixed structure in moderate weather, carrying satellite, acoustic, and radar references plus gyro, motion unit, and wind sensors. Task one: for each reference, write what it needs to work, what makes it degrade, and whether it is independent of the seabed, of satellites, and of the structure. Task two: write one plausible degradation for each, then a combined scenario where two degrade together, and state how the operator would know something is wrong.
Now grade yourself with this rubric. Correct independence reasoning: you identified which systems fail together and which fail separately. Correct causal direction: every degradation traced to a real mechanism (obscured line of sight, blocked acoustic path, degraded signal), not vague 'system error'. Correct operator actions: cross-checking references before trusting one, and managing inputs according to procedures rather than improvising a set-point change. Score one point each; a score of six or more on a first attempt shows the chain logic is forming, and below that, target the mechanism explanations rather than the definitions.
Repeat the exercise with the vessel moved to deep water and the structure removed. Expected observation: some references lose their justification entirely in the new setting, and your justification table should change accordingly. This is the transfer you want the exam to see: you can adapt a reference mix to conditions, rather than recalling a fixed answer.
Readiness checks and an adaptable study sequence
Finish DPB preparation with evidence, not page counts: you are ready when you can draw the loop, classify faults, audit references, and explain class logic on blank paper without notes.
Adaptable sequence: first pass, draw the station-keeping loop and place every course concept inside it; second pass, learn each reference system against the comparison table, adding depth, weather, and interference considerations; third pass, drill drift-off versus drive-off with written fault scenarios; fourth pass, do the paper audit exercise twice in different settings; fifth pass, take a full practice set under quiet conditions and review every wrong answer by tracing where your chain broke. Stretch the passes over whatever time you have; the order matters more than the calendar.
Concrete readiness checks before you sit the exam: (1) redraw the loop from memory, correctly, on the first attempt; (2) classify eight written faults as drift-off or drive-off with the subsystem named, at least seven correct; (3) complete the reference table without notes; (4) explain, in two sentences each, why equipment class exists and why references are cross-checked; (5) score six or more on the audit rubric in a new setting. Treat these as learning milestones you set yourself, not predictions of any score; their value is that they tell you which pass to repeat.
For administrative matters, including course accreditation, phases of the DP scheme, and certification requirements, consult the Nautical Institute directly rather than study materials, since such rules sit outside what a review guide should restate. IMCA publications on DP topics, including the GNSS interference guidance and station-keeping reporting, are useful background reading once the fundamentals are solid.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.