Professional Documents
Culture Documents
FMEA Procedure K-Pos
FMEA Procedure K-Pos
FMEA Procedure K-Pos
CODE 1 ACCEPTED
ACCEPTED WITH
CODE 2
COMMENTS INCORPORATED
NOT ACCEPTED
CODE 3
REVISE AND RESUBMIT
Reviewer Signature: Date: SDRL Code: SFI Code: Area: System: Res. Unit:
Project: 28540
Product K-Pos DP-1, K-Pos DP-2 and cJoy
Synopsis: FMEA for the Kongsberg Maritime deliverery.
Classification society: DNV AUTRO
Document number: 1059180 Revision: A
Customer doc number: Document version: 1.0
Contract number: Number of pages: 89
Rev. Date Reason for issue Made by Checked Approved
Kongsberg Maritime AS
Kongsberg Maritime AS
Table of contents
1 ABOUT THIS DOCUMENT ..................................................................................6
1.1 Document history ..................................................................................................6
1.2 References .............................................................................................................6
1.3 Definitions / Abbreviations ...................................................................................6
2 INTRODUCTION....................................................................................................8
2.1 Purpose ..................................................................................................................8
2.2 Scope .....................................................................................................................8
2.3 Assumptions and limitations .................................................................................8
Table of figures
Figure 1:.......................................................................................................................... 53
Figure 2:.......................................................................................................................... 54
Figure 3:.......................................................................................................................... 55
Figure 4:.......................................................................................................................... 56
Figure 1: Power and wiring diagram for Operator Station............................................. 97
Figure 2: Network Structure, 2xOS and DPC-2............................................................. 98
Figure 3: Principle block diagram, DPC-2 ..................................................................... 99
Figure 4: Principle block diagram of I/O signals, DPC-2 ............................................ 100
Figure 5: Power & Wiring Diagram, DPC-2................................................................ 101
Figure 6: Power & Wiring Diagram, RBUS A-Section, DPC-2 .................................. 102
Figure 7: Power & Wiring Diagram, RBUS B-Section, DPC-2 .................................. 103
Figure 8: Termination Diagram, 88ch I/O Serial ch1-8 A-Section, DPC-2 ................. 104
Figure 9: Termination Diagram, 88ch I/O Serial ch9-16 B-Section, DPC-2 ............... 105
Figure 10: Change over switch, 3-position................................................................... 106
Figure 11: Principle block diagram, cC-1 .................................................................... 107
Figure 12: Principle block diagram of I/O signals, cC-1.............................................. 108
Figure 1: Principle block diagram, cC-1 ...................................................................... 109
Figure 2: Principle block diagram of I/O signals, cC-1................................................ 110
The analysis has not revealed any single failure in the main system that could have
critical consequences with regards to personnel or operational safety.
The most serious single points that are detected through the analysis are loss of one
RMP module. Failure in these different modules may cause a loss of one generator /
thruster and may cause reduction of positioning performance, dependent on weather /
force conditions. Operator intervention may be needed to maintain DP-function.
A single joystick is provided and is independent of the other control systems. The
system is hardwired to each thruster and operates independent of the dual network.
A single fire backup switch switches between the main and the backup system. In case
of failure of the switch, it may not be possible to switch between different modes. The
criticality of this depends on the current operating mode before failure. If none of the
modes are functioning, you have to operate each thruster manually. The reliability for
this fire backup switch is, however, considered high and the probability for critical
failure is low.
A First issue
1.2 References
Documentation used for the FMEA is included in the appendix of this report.
In addition, product descriptions for the generic products are used.
AO Analogue Output
DO Digital Output
DI Digital Input
JC Joystick Cabinet
KM Kongsberg Maritime
NC Normally Closed
NO Normally Open
OS Operator Station
TC Thruster Control
STBD Starboard
SW Software
TB Terminal Board
THR Thruster
2 INTRODUCTION
2.1 Purpose
This document is a Failure Mode and Effect Analysis (FMEA) for KM delivery. This
document covers some general information in addition to the project specific FMEA.
2.2 Scope
The scope of the analysis is Kongsberg Maritimes delivery. Which sensors and position
reference systems that are KM delivery, is presented in section 4.1.5. Interfaces are
prepared for the sensors and systems that are not delivered by KM, but they are not
included in the analysis.
The software, thrusters and ship supply are not part of the analysis.
The control system in the computers has not been analysed, as it is a part of the
computer's software. Ideally, it could be assumed that after the system is tuned up and
tested, no errors will arise from the computer software. This is however not always true,
but there are no requirement that this assessment should be included in the FMEA.
As software errors are difficult to predict within a reasonable confidence level, the
software error probabilities are based on experienced data from similar systems and
applications.
This is among others due to the nature of the software, and to the fact that there is no
known good method for calculation of predicted software reliability data. Reference is
made to section 4.2.2 Experienced reliability for DP control system software.
Hardware is discussed on a detail level represented by failure modes which in each case
is considered being relevant and sufficient for the item in question with respect to
critical effect on primary functions.
Only functions / items that are considered to have influence on vital functions are
analysed, hence peripheral equipment like printers, data logging equipment etc. are not
analysed.
Units with redundancy like reference systems, sensors etc. are discussed in the same
manner, as there are backup systems / units for each of them.
The dynamic positioning controller A and B is discussed on block level. Blocks that in
the pre analysis (PSA) are found to have common components are analysed further for
potential common mode/cause failures.
The Autopilot is not analysed.
Possible failures that may be caused by external environmental influences like lightning,
collisions by other vessels, sabotage etc. are not considered here.
1. Top level Failure Mode and Effect Analysis (FMEA) utilising the
Preliminary Safety Analysis (PSA) method (described in section 3.1.1) and
if relevant:
2. Detailed FMEA on component level (described in section 3.1.2)
The PSA is as shown in Table 1 divided in 3 major parts; Item description, Failure
description and Additional info. The meaning of the different parameters is explained
below:
Redundancy Ticked as Yes if there is one, or more than one, identical unit
providing full redundancy function
Failure Failure mode Main failure modes addressed in the PSA are:
description
Power failure (too high, too low etc.)
Power fuse faulty
Signal missing/faulty
Unit/Module faulty (loss of main function)
Additional failure modes are used where relevant as listed in
chapter 3.3
Failure detection Main failure detection method, e.g. if failure is evident (e.g.
alarm) or dormant (revealed when operated/tested)
PARAMETER DESCRIPTION
1. Item/Component ident. The analysed item/component (Compartment) identified by a
(or Compartment ident.) number or by name.
2. Function Main function of the analyzed component
3. Mode of operation Assumed operational mode of the item before failure occurs or
the event phase in which the failure occurs.
4. Failure mode Failure modes associated with the element.
5. Failure cause(s) Failure cause(s)/mechanism(s) of each failure mode.
6. Detection method Method by which the failure mode is normally detected. It
should in particular be stated whether the failure will be
immediately detected (e.g. alarm) or only be detected upon
testing or on-demand (hidden failure).
7. Failure effect locally (or Local effects of failure mode (on Component/ Item level)
other)
8. Failure Effect on Effect of a failure mode on the performance of functions of
Primary (DP) Functions higher level, normally the DP-function. A column explaining
Other effects may also be included where relevant.
9. Compensating How the failure mode may be compensated for (e.g.
provisions redundancy, safety devices etc.)
10.Comments Additional information as deemed required for assessing the
effect of this failure.
Examples: (1) Recommended additional measures to eliminate
a failure mode or minimise its effect on main functions. (2)
Possible pre-planned alternative methods of operation.
4 SYSTEM DESCRIPTION
This section includes an outline of the specific system in addition to some general
information on the Kongsberg Maritime systems.
Th. 1 1 G1/G2
Th. 2 2 G1/G2
Th. 3 3 G5/G6
Th. 4 4 G5/G6
Th. 5. 5 G3/G4
Th. 6 6 G3/G4
Th. 7 7 G7/G8
Th. 8 8 G7/G8
4.1.2 Controllers
The following controllers are installed on this vessel:
dual DP controller
backup controller
joystick controller (independent joystick system)
All logic with respect to safety, control and monitoring is located in the controllers.
4.1.4 Network
There is a redundant network, with Net A and Net B. This is shown in Appendix C.
Net switch for Net A is located in DP OS 1, and net switch for Net B is located in DP
OS 3 / backup OS.
LTW 0 of 2 1 1
RAM 0 of 1 1 -
Gyros 3 of 3 1, 2 and 3 1
5 RESULT OF FMEA
In the following the system is broken down into manageable sub systems/functions and
a Top Level FMEA (PSA) for each main system/function is performed. This is done
using the PSA as a tool to determine if a detailed FMEA is needed for any of these.
Element: K-Pos Operator Station 1/2/3 Element function: Operator communication with the DP-controllers
Comments:
Equipment not delivered by KM is connected to Net C (Adm. Net.) through a router or firewall.
1)
All applications are carefully tested regarding network load. It is also proved that the distributed solution will work with a very high network load,
although this is not the normal case.
Periodic network verification will also be done to ensure that both networks with their components are ok. Hence, the probability for such a double
failure is considered to be very small, and is not treated further here.
Data provided from field experience statistics for IAS (Integrated systems) networks shows that the MTTF is about 100 years. This is based on
experienced critical failures on 100 installations during the last 5 years
Element: UPS (Uniterruptable Power Supply) 1/2/3 Element function: Electrical power supply
1) The probability of unreliable communication on the internal RBUS is small due to the short length of the cable.
5.2.2 DPC-1
1) The probability of unreliable communication on the internal RBUS is small due to the short length of the cable.
1) The probability of unreliable communication on the internal RBUS is small due to the short length of the cable.
Element: Fire Backup Switch Element function: Switch between main and backup systems
Comments:
A single change over switch switches between the different modes; DP, independent joystick and manual levers (The fire backup switch switches
between main DP and backup DP systems). In case of failure of the switch, it may not be possible to switch between different modes. The
criticality of this depends on the current operating mode before failure. If none of the modes are functioning, you have to operate each thruster
manually. The reliability for this change over switch is, however, considered high and the probability for critical failure is low.
If fault in one contact, only one thruster will be lost.
HiPAP Provide No 4. Signal Warning Result depends on magnitude The system uses pos. ref. No
position failure - and speed of drift and the data from the other
input Output overall mixture of Position reference sensors.
signal drift Reference Systems and their (Automatic or based on
relative weight. The faulty operator interaction if
position reference data might be needed).
rejected by the DP system, but
the DP system might also reject
the valid position reference
systems.
HiPAP Provide No 5. Signal Warning The faulty data is rejected by the The system uses pos. ref. No
position failure - DP system data from the other
input Output reference sensors
signal jump
HiPAP Provide No 6. Signal Alarm. Data not available to the DP The system uses pos. ref. No
position failure system data from the other
input Output reference sensors.
signal lost
Sensor input Provide No 7. Signal Alarm. Faulty data not used by DP The system uses pos. ref. No
VRS and failure system data from the other
heading reference sensors.
signal
Comments:
1)
Frozen position data is a very unlikely error mode; this will result in an invalid status (failure mode #2)
Element: Interface Taut Wire 1/2 Element function: Provide Position data
Gyro Provide Yes 5. Sensor Alarm Not critical. Lost telegram, The system uses data No
heading failure - Lost ready signal OK. from the other Gyro.
signal
Gyro Gyro ready Yes 6. Signal Alarm. Not critical. Loss of ready The system uses data No
failure signal. from the other Gyro.
Comments:
1) If three Gyros are available, the faulty Gyro is excluded by the voting.
Element: Wind sensor 1/2/3 Element function: Provide wind direction and speed
Wind sensor Provide Yes 2. Sensor Alarm Wind sensor different. Operator has to select No
wind, speed failure - correct sensor.
and direction Freeze The system uses data
signal from the other Wind
sensor.
Wind sensor Provide Yes 3. Sensor Alarm Wind sensor different. Operator has to select No
wind, speed failure correct sensor.
and direction Slow The system uses data
signal drifting from the other Wind
sensor.
Element: MRU 1/2/3 Element function: Provide Pitch and Roll data
MRU MRU ready Yes 6. Signal Alarm. Loss of Ready signal. The The system uses data No
failure faulty MRU is rejected by the from the other MRU.
system.
Comments:
If three MRUs are available, the faulty MRU is excluded by the voting.
Figure 1:
Figure 2:
Figure 3:
Figure 4:
Thr. 1 Ready X1 : 3 c DI
7 Generator 1 connected X4 : 1 s DI
Generator 1 connected X4 : 3 c DI
Thr. 2 Ready X1 : 3 c DI
7 Generator 2 connected X4 : 1 s DI
Generator 2 connected X4 : 3 c DI
Thr. 5 Ready X1 : 3 c DI
7 Generator 3 connected X4 : 1 s DI
Generator 3 connected X4 : 3 c DI
Thr. 6 Ready X1 : 3 c DI
7 Generator 4 connected X4 : 1 s DI
Generator 4 connected X4 : 3 c DI
3 UPS 1 Alarm X2 : 1 s DI
UPS 1 Alarm X2 : 3 c DI
5 BU Switch DPC-1 X3 : 2 c AI
BU Switch DPC-1 X3 : 3 s AI
7 BU Switch DPC-2 X4 : 1 s DI
BU Switch DPC-2 X4 : 3 c DI
4 MRU (3) OK X2 : 4 s DI
MRU (3) OK X2 : 6 c DI
7 GYRO (2) OK X4 : 1 s DI
GYRO (2) OK X4 : 3 c DI
Thr. 3 Ready X1 : 3 c DI
7 Generator 5 connected X4 : 1 s DI
Generator 5 connected X4 : 3 c DI
Thr. 4 Ready X1 : 3 c DI
7 Generator 6 connected X4 : 1 s DI
Generator 6 connected X4 : 3 c DI
Thr. 7 Ready X1 : 3 c DI
7 Generator 7 connected X4 : 1 s DI
Generator 7 connected X4 : 3 c DI
Thr. 8 Ready X1 : 3 c DI
7 Generator 8 connected X4 : 1 s DI
Generator 8 connected X4 : 3 c DI
2 GYRO (3) OK X1 : 4 s DI
GYRO (3) OK X1 : 6 c DI
3 UPS 2 Alarm X2 : 1 s DI
UPS 2 Alarm X2 : 3 c DI
4 MRU (2) OK X2 : 4 s DI
MRU (2) OK X2 : 6 c DI
OFF X1 : 3 c DI
2 DRILLING X1 : 4 s DI
DRILLING X1 : 6 c DI
3 PREPARE TO DISCONNECT X2 : 1 s DI
PREPARE TO DISCONNECT X2 : 3 c DI
4 DISCONNECT X2 : 4 s DI
DISCONNECT X2 : 6 c DI
I/O specification for KcJoy is generated from I/O database 1053732 Rev. B
Thr. 1 Ready X1 : 3 c DI
Thr. 2 Ready X1 : 3 c DI
Thr. 3 Ready X1 : 3 c DI
Thr. 4 Ready X1 : 3 c DI
Thr. 5 Ready X1 : 3 c DI
Thr. 6 Ready X1 : 3 c DI
Thr. 7 Ready X1 : 3 c DI
Thr. 8 Ready X1 : 3 c DI
I/O specification for KPos-1 is generated from I/O database 1053732 Rev. B
Thr. 1 Ready X1 : 3 c DI
7 Generator 1 connected X4 : 1 s DI
Generator 1 connected X4 : 3 c DI
Thr. 2 Ready X1 : 3 c DI
7 Generator 2 connected X4 : 1 s DI
Generator 2 connected X4 : 3 c DI
Thr. 5 Ready X1 : 3 c DI
7 Generator 3 connected X4 : 1 s DI
Generator 3 connected X4 : 3 c DI
Thr. 6 Ready X1 : 3 c DI
7 Generator 4 connected X4 : 1 s DI
Generator 4 connected X4 : 3 c DI
2 UPS 3 Alarm X1 : 4 s DI
UPS 3 Alarm X1 : 6 c DI
4 GYRO (1) OK X2 : 4 s DI
GYRO (1) OK X2 : 6 c DI
5 BU Switch DPC-2 X3 : 1 s DI
BU Switch DPC-2 X3 : 3 c DI
7 BU Switch DPC-1 X4 : 1 s DI
BU Switch DPC-1 X4 : 3 c DI
Thr. 3 Ready X1 : 3 c DI
7 Generator 5 connected X4 : 1 s DI
Generator 5 connected X4 : 3 c DI
Thr. 4 Ready X1 : 3 c DI
7 Generator 6 connected X4 : 1 s DI
Generator 6 connected X4 : 3 c DI
Thr. 7 Ready X1 : 3 c DI
7 Generator 7 connected X4 : 1 s DI
Generator 7 connected X4 : 3 c DI
Thr. 8 Ready X1 : 3 c DI
7 Generator 8 connected X4 : 1 s DI
Generator 8 connected X4 : 3 c DI
5 MRU (1) OK X3 : 1 s DI
MRU (1) OK X3 : 3 c DI
Figure 12: Termination Diagram, 88ch I/O Serial ch1-8 A-Section, DPC-2
Figure 13: Termination Diagram, 88ch I/O Serial ch9-16 B-Section, DPC-2
cC-1
To RCU
Switch
Field 501
A
A
U41-49
U31-33
UPS1 PWR
PSU
A
1 M
Legend:
RBUS A
NET A
SERIAL
cC-1
To RCU
Switch
Field 501
A
A
U41-49
U31-33
UPS1 PWR
PSU
A
1 M
Legend:
RBUS A
NET A
SERIAL