Closed Bus – PMS failure leads to thrust limitation of all thrusters
- DP Event
- Published on 3 April 2024
- Generated on 26 December 2024
- DPE 01/24
- 5 minute read
Incident
Jump to:
A malfunction in the I/O module triggered a series of events leading to a loss of vessel position and an emergency disconnect.
Overview
The vessel encountered a critical situation due to a fault in the Power Management System
(PMS). A malfunction in the Input/Output (I/O) module for the No. 4 centre generator
triggered a series of events leading to a loss of vessel position and an emergency disconnect.
What happened?
- Misleading alarm and response: An alarm signalled a generator fault, leading the engineer to disconnecting the faulty generator by opening the circuit breaker but leaving the affected generator running. However, due to the I/O module fault, the breaker status incorrectly showed to the PMS as still closed/connected.
- I/O module fault: The I/O module for the No. 4 centre generator developed a fault, causing the generator circuit breaker status to freeze in the ‘closed’ position when the breaker was physically opened.
- Load sharing imbalance: The disconnection of the generator caused a load sharing imbalance. The PMS attempted to correct this imbalance, but as the disconnected generator could not take any load, the imbalance persisted. The PMS believed it was controlling three generators not two, the status signal was not just for indication but an important input to the PMS control. PMS lowered the fuel setting to G2 & G6 and increased fuel setting to G4.
- Bus frequency decline and thrust limitation: The persistent imbalance led the PMS to reduce the bus frequency, eventually triggering a frequency-based thrust limitation function on all thrusters. This resulted in the loss of the vessel’s position and necessitated an emergency disconnect.
When a Power Management System (PMS) tries to manage three generators but only two are actually connected in parallel, while the PMS believes all three are connected, several issues can arise due to this discrepancy:
- Load sharing problems: The PMS is designed to balance the load across all connected generators. If it believes three generators are connected and operating, it will attempt to distribute the load across all three. However, since only two are actually connected, it will still try and load up the unconnected generator, which in this case meant lowering the governor setting on the two connected generators and raising the governor settings on the unconnected generator.
- Voltage and frequency instability: Generators in a parallel setup need to maintain synchronicity in terms of voltage, frequency, and phase. If the PMS tries to synchronise three generators but only two are present, it can lead to instability in voltage and frequency. In this case the two connected generators were ‘slowing down’ this had the effect of reducing the bus frequency, as the frequency detreated the thruster drives tripped on their protection settings. The unconnected generator was ‘speeding up’ and eventually tripped on overspeed.
- Incorrect system readings and responses: The PMS uses data from all generators to make decisions about load distribution, start-up, shutdown, and other operational aspects. Incorrect data due to a non-existent third generator can lead to inappropriate decisions, such as unnecessary generator start-ups or shutdowns, or failure to start an additional generator when needed.
- Protection system mis-operation: The protection systems in power management are designed to prevent damage to generators and connected systems in cases of faults. If the PMS incorrectly assumes the presence of a third generator, it may not correctly identify and react to real faults, potentially leading to equipment damage or safety hazards.
G4 eventually tripped off on overspeed, once this trip happened the two connected generators returned to normal load sharing and returned the bus frequency to 60Hz, however this was too late as the thrusters had already reduced their thrust output to zero.
The standby generators were prevented from connecting prior to G4 trip due to the low bus frequency. Once G4 tripped, the PMS return to normal load sharing and as the frequency returned to normal level the standby generators were able to connect.
Once the thruster drives detected the normalisation of the bus frequency the thrusters were able to return from phase back allowing DP Control.
The time duration was relatively short (approximately three mins) – however, the position excursion was in excess of 75 metres.
Considerations
- FMEA inclusion of PMS interface –The vessel’s Failure Modes and Effects Analysis (FMEA) should be revised to include the PMS interface, ensuring that similar failure modes are identified and mitigated.
- Testing of PMS in closed bus operations – The incident suggests that the PMS was not adequately tested for operations in closed bus mode. Comprehensive testing in this mode is recommended to prevent similar occurrences.
- Generator protection evaluation – The occurrence of frequency issues points to a lack of advanced generator protection or its malfunction. This aspect must be investigated and rectified.
- Review of operational manuals – The vessel’s Dynamic Positioning (DP) operations manual, Standard Operating Procedures (SOPs) and Well Specific Operating Guidelines (WSOG) should be reviewed and updated in light of this incident.
Conclusions
The incident underscores the criticality of robust PMS functioning in marine vessels, especially in complex configurations like closed bus mode. It highlights the need for comprehensive FMEA, rigorous system testing, and continuous review of operational procedures to ensure the safety and reliability of marine operations.
Additionally, the need for appropriate protective function related to load control (i.e. additional generator protection).
Latest DP incidents
-
Prepare for 2025 solar activity
This case study covers events that occurred on the same vessel, eight months apart.
DPE 02/24
29 July 2024
Undesired event
-
Know your vessel capabilities and when to stop!
An incident that occurred on an equipment class 2 MODU, during well intervention operations.
DPE 02/24
29 July 2024
Incident
-
Duty/not duty, which is the question?
With no steering control of the port azimuth thruster, and no other thrusters operational, the heading of the FPU could not be maintained.
DPE 02/24
29 July 2024
Undesired event
-
You’ve got the ASOG, so now you’ve got to follow it
This case study examines an incident that occurred on an equipment class 2 MODU, during well intervention operations.
DPE 02/24
29 July 2024
Incident
-
Button trouble
A Dynamically Positioned vessel experienced a loss of Dynamic Positioning (DP) control while installing cable within a wind farm.
DPE 01/24
3 April 2024
Incident
The case studies and observations above have been compiled from information received by IMCA. All vessel, client, and operational data has been removed from the narrative to ensure anonymity. Case studies are not intended as guidance on the safe conduct of operations, but rather to assist vessel managers, DP operators, and technical crew.
IMCA makes every effort to ensure both the accuracy and reliability of the information, but it is not liable for any guidance and/or recommendation and/or statement herein contained.
Any queries should be directed to DP team at IMCA. Share your DP incidents with IMCA online. Sign-up to receive DP event bulletins straight to your email.