11.1 FMEA & Annual DP Trials
Key Takeaways
- FMEA (Failure Modes and Effects Analysis) documents how single failures propagate through the DP plant and proves Class 2/3 single-failure design intent
- Proving trials and annual DP trials verify that FMEA assumptions remain valid after construction, modification, or time in service
- FMEA is a living document — hardware, software, and configuration changes require reassessment and often updated trials evidence
- The DPO should know the vessel’s worst-case failure (WCF), residual thrusters/power after that failure, and key FMEA conclusions that constrain CAM/ASOG
- Trials are not a paperwork ritual: they expose hidden common-mode links, protection gaps, and thruster/power behaviours that only appear under test
Why FMEA sits at the heart of Class 2/3 DP
Dynamic Positioning Class 2 and Class 3 are not marketing labels. They are engineering claims: after a defined single failure (and for Class 3, with additional fire/flood compartment thinking), the vessel should retain enough thruster and power capability to hold position in the analysed environment. Failure Modes and Effects Analysis (FMEA) — sometimes titled DP FMEA, redundancy analysis, or failure-mode study — is the structured document that proves or disproves that claim before the vessel is trusted for critical work.
On the NI Induction and Simulator path you are not expected to write an FMEA. You are expected to know what it is for, how trials relate to it, why modifications matter, and which conclusions a DPO must carry into everyday operations. Without that knowledge, capability plots, consequence analysis, open/closed bus decisions, and ASOG colours become disconnected guesswork.
What an FMEA actually does
An FMEA walks the DP-relevant plant failure by failure and asks:
- What can fail? (generator, bus section, thruster drive, DP process station, reference common power, cooling, fuel common rail, control network, protection mis-trip, etc.)
- What is the effect on power, thrusters, control, sensors, and station-keeping?
- Is the effect contained so residual capability remains after that single failure?
- Are there hidden common-mode links that make two “independent” items fail together?
- What residual thrusters, power, and control paths survive?
| FMEA question | Operator-relevant answer |
|---|---|
| What is the design single failure of concern? | Often loss of one bus/power section or one thruster group |
| What thrusters remain? | The residual set that must still hold weather |
| What power remains? | Online generation and distribution still feeding residual thrusters |
| Does control survive? | Redundant DP computers / networks as designed |
| What must the crew configure? | Open bus, thruster enables, CAM plant state |
The product of a good FMEA is not only a thick binder. It is a failure graph of the vessel: partitions, residual capability, and the worst-case failure (WCF) used later for capability plots and online consequence analysis.
[!IMPORTANT] FMEA proves single-failure tolerance for Class 2/3 design. It does not claim the vessel can survive every combination of simultaneous independent failures. Exam stems that pile three unrelated failures into one event are testing whether you confuse FMEA/WCF with multi-fault fantasy scenarios.
FMEA and equipment class — the design link
| Class intent (simplified) | Role of FMEA |
|---|---|
| Class 1 | Loss of position may occur after a single failure — FMEA may still exist for awareness, but single-failure hold is not the class promise |
| Class 2 | No single failure of active component should cause loss of position — FMEA must show residual power/thrusters/control |
| Class 3 | As Class 2 plus resistance to fire/flood in any one compartment — FMEA (and layout) must address compartment-level loss |
FMEA is therefore the evidence trail that the redundancy you see on drawings is real in failure physics. A vessel can have two bus sections on paper and still fail FMEA if a common cooling pump, common UPS feed, or protection discrimination gap blacks both sides from one initiating event.
Proving trials: first real-world proof
After design analysis, the vessel must be tested. Proving trials (DP proving trials, FMEA proving trials, or equivalent shipyard/class trials language) exercise selected failure modes on the real plant to confirm:
- residual thrusters actually receive power after section loss,
- bus-tie and protection behaviour matches analysis,
- thruster enable/disable and allocation respond as modelled,
- control redundancy (process station failover, network paths) works,
- sensors and UPS behaviour under partial power loss is acceptable,
- no unexpected common-mode collapse appears.
| Trials concept | Meaning |
|---|---|
| Proving trials | Initial (or major-modification) demonstration that FMEA conclusions hold on the built vessel |
| Annual DP trials | Yearly (or interval-based) re-check that the plant still behaves as designed |
| Failure simulation | Controlled trip/isolation of a unit or section under safe conditions |
| Acceptance | Documented results that support class notation and operational use |
Proving trials convert theory into measured residual capability. If a simulated bus failure also trips the “healthy” side thrusters because of a wiring error, the FMEA must be revised and the defect fixed — you do not “paper over” the trial with a note that ignores reality.
Annual DP trials: assumptions age
Time, maintenance, software updates, and small modifications erode confidence that last year’s plant is this year’s plant. Annual DP trials (and similar periodic trials required by company, class, or charterer) re-verify critical FMEA assumptions:
- generators still start and take load as expected,
- preferential trip and load-shed paths still work,
- thrusters still respond and can be isolated cleanly,
- changeover of DP computers / networks still succeeds,
- open-bus residual configuration still leaves a usable thruster set,
- alarms and changeovers that operators rely on still appear correctly.
| Why annual trials matter | Example risk if skipped |
|---|---|
| Software/firmware drift | Protection settings no longer match FMEA addendum |
| Undocumented cable/jumper changes | Common-mode power to both “redundant” controllers |
| Maintenance residue | Inhibited trip left in place after work |
| Thruster/drive changes | Residual force after WCF no longer matches plots |
| Crew familiarity | Operators never saw real residual configuration |
Annual trials are also a training event: bridge and engine room practise the failure signatures they may only see once in a career. For the exam, treat annual trials as validation that FMEA remains true, not as a random survey checklist item.
FMEA is a living document
Any material change can invalidate previous conclusions:
- new thruster, drive, or generator,
- switchboard or bus-tie protection upgrade,
- DP system software major revision,
- closed-bus protection package added or removed,
- PRS suite change that affects common power or interfaces,
- conversion work that re-routes cooling, fuel, or control air.
| Change type | Typical FMEA action |
|---|---|
| Minor like-for-like spare | Often covered by existing analysis if identical function |
| New thruster or power path | Reanalysis + targeted trials |
| Closed-bus protection scheme | Formal FMEA addendum + proving evidence |
| Major DP software upgrade | Impact assessment; possible re-trial of control failures |
| Undocumented “temporary” wiring | Immediate risk — analysis no longer trustworthy |
Operational rule: if the plant no longer matches the FMEA, the vessel is no longer operating on proven redundancy. Capability plots and online consequence analysis that assume the old residual set become optimistic lies. Company procedures usually require management of change (MOC), FMEA update, and trials before returning to critical DP work.
What the operator must know (without being the author)
You will not memorise every failure table. You should know, for your vessel and for exam scenarios:
- What is the WCF in the normal open-bus (or proven closed-bus) configuration?
- Which thrusters and how much power remain after WCF?
- Does FMEA allow closed bus for the activity you are doing, and under what protection conditions?
- What configuration does CAM demand so that residual capability is real (open bus, thrusters enabled both sides, generators online both sections)?
- Where are key conclusions summarised for the bridge (DP operations manual, FMEA summary, ASOG notes)?
| Operator knowledge | Why exams care |
|---|---|
| Vessel WCF description | Links to capability and consequence analysis |
| Residual thruster set | Explains post-failure footprint growth |
| Config that FMEA assumes | Open bus vs closed; thrusters online |
| Trials currency | Plant must still match analysis |
| Modification triggers | Living document, not shelf ornament |
Worked bridge scenario
A DP construction vessel arrives on a new charter. The master hands the DPO a capability plot set and says “we are fine up to 40 knots.” The DPO asks for the FMEA summary and annual trials date. Trials are thirteen months overdue; a thruster drive was replaced six months ago with a different type and no FMEA addendum exists. The DPO refuses to treat the old post-WCF plots as authoritative for diving support until engineering and class/company MOC restore a proven residual picture. Lesson: plots without a living FMEA and current trials are decoration, not proof.
Exam traps for FMEA and trials
| Trap | Correct framing |
|---|---|
| “FMEA is only for shipyard/class, not DPOs” | DPO must know WCF and operational conclusions |
| “Annual trials replace the FMEA” | Trials verify FMEA; they do not rewrite class philosophy alone |
| “Any software update is free” | Material changes need reassessment |
| “FMEA proves multi-fault survival” | Focus is single failure (plus Class 3 compartment cases) |
| “Green annual sticker means unlimited weather” | Trials confirm failure behaviour, not infinite intact capability |
Bottom line: FMEA documents how single failures propagate and proves Class 2/3 design intent; proving and annual DP trials keep those assumptions honest on the real ship; modifications demand reassessment; and the operator must know the vessel WCF and the FMEA conclusions that drive configuration, capability, and stop-work decisions.
What is the primary purpose of a DP vessel FMEA in a Class 2/3 context?
Why are proving trials and annual DP trials essential relative to the FMEA?
A major thruster drive type is replaced and the electrical protection settings are revised. What should happen to the FMEA?
Which FMEA-related knowledge is most important for a DPO on watch?