7.2. Fault Tree
Several rounds of brain-storm workshops have been held to understand the working philosophy of the subsystem. Besides, research findings in Reference [
23] have been referred to provide a better understanding of the application of FT in electrical subsystem. The hierarchy of subsystem has been clearly defined.
There are two independent energy transfer routes respectively connected to CP1 through the connectors 7 and 8 and two cables AC3 and AC6. The electricity is finally transmitted to the onshore terminal through the connector 9. Suppose that the two energy transfer routes are considered as a virtual unit denoted by T1. T1 is considered as a 1st-level sub-assembly. If either of CP1, X19 and T1 fails, the energy transfer system (T0) will be shut down (no electricity generated).
T1 is composed of two identical energy transfer routes respectively denoted by T2 and T3, which are the 2nd-level sub-assemblies. T1 fails, if both T2 and T3 fail.
T2 comprises X17, X3, a virtual unit T4, which comprises the other connectors directly connected to MECs and the other cables connecting these connectors. If either X17, X3, or T4 fails, this energy transfer route will be shut down. T2 can be considered a series system. T3 comprises X18, X6, a virtual unit T5, which comprises the other connectors directly connected to MECs and the other cables connecting these connectors. If either X18, X6, or T5 fails, this energy transfer route will be shut down. T3 can be considered a series system. Both T4 and T5 constitutes the 3rd-level sub-assembly.
T4 comprises X2, X13 and another virtual unit T6. If either two of X2, X13, and T6 fail, T4 fails. In a similar way, T5 comprises X6, X16 and another virtual unit T7. If either two of X6, X16, and T7 fail, T5 fails. Both T6 and T7 constitutes the 4th-level sub-assembly.
T6 comprises X12 and another virtual unit T8. If either X12 or T8 fails, T6 fails. T7 comprises X15 and another virtual unit T9. If either X15 or T9 fails, T7 fails. Both T8 and T9 constitutes the 5th-level sub-assembly.
T8 comprises X11 and X1. If either X11 or X1 fails, T8 fails. T9 comprises X14 and X4. If either X14 or X4 fails, T9 fails.
The hierarchy of the subsystem is given in
Table 5.
Based upon the qualitative system analysis, the FT can be constructed accordingly. The top event is denoted ‘Failure of ET system (T0)’. The intermediate failure events underneath the top event refer to ‘Failure of X19 (denoted X19 in the fault tree)’, ‘Failure of X20 (denoted X20 in the fault tree)’, and ‘Failure of T1’. An ‘OR’ gate is inserted according to the working philosophy. For simplicity, the label name is hereafter used to represent the failure event of this unit in the FT.
If ‘Failure of T1’ is considered the top failure event, the intermediate failure events refer to the two ‘Failure of T2’ or ‘Failure of T3’ events. An ‘AND’ gate is inserted according to the working philosophy.
If ‘Failure of T2’ is considered the top failure event, the intermediate failure events refer to ‘Failure of X17 (denoted X17 in the fault tree)’, ‘Failure of X3 (denoted X3 in the fault tree)’, and ‘Failure of T4’. An ‘OR’ gate is inserted according to the working philosophy. If ‘Failure of T3’ is considered the top failure event, the intermediate failure events refer to ‘Failure of X18 (denoted X18 in the fault tree)’, ‘Failure of X6 (denoted X6 in the fault tree)’, and ‘Failure of T5’. An ‘OR’ gate is inserted according to the working philosophy.
If ‘Failure of T4’ is considered the top failure event, the intermediate failure events refer to ‘Failure of X13 (denoted X13 in the fault tree)’, ‘Failure of X2 (denoted X2 in the fault tree)’, and ‘Failure of T6)’ A ‘2/3’ gate is inserted according to the working philosophy. If ‘Failure of T5’ is considered the top failure event, the intermediate failure events refer to ‘Failure of X16 (denoted X16 in the fault tree)’, ‘Failure of X5 (denoted X5 in the fault tree)’, and ‘Failure of T7’. A ‘2/3’ gate is inserted according to the working philosophy.
If ‘Failure of T6’ is considered the top failure event, the intermediate failure events refer to ‘Failure of X12 (denoted X12 in the fault tree)’ and ‘Failure of T8’. An ‘OR’ gate is inserted according to the working philosophy. If ‘Failure of T7’ is considered the top failure event, the intermediate failure events refer to ‘Failure of X15 (denoted X15 in the fault tree)’ and ‘Failure of T9’. An ‘OR’ gate is inserted according to the working philosophy.
If ‘Failure of T8’ is considered the top failure event, the bottom failure events refer to ‘Failure of X11 (denoted X11 in the fault tree)’ and ‘Failure of X1 (denoted X1 in the fault tree)’. An ‘OR’ gate is inserted according to the working philosophy. If ‘Failure of T9’ is considered the top failure event, the bottom failure events refer to ‘Failure of X14 (denoted X14 in the fault tree)’ and ‘Failure of X4 (denoted X4 in the fault tree)’. An ‘OR’ gate is inserted according to the working philosophy. The FT of the subsystem is shown in
Figure 6.
7.3. Mapped Bayesian Network
Hugin Expert 8.9 is used to do the Bayesian inference. Hugin Expert [
24] provides an independent interface for Python to construct the BN models, which is more efficient than manual operations of drawing BNs in the Hugin user interface are time-consuming. The BN model is shown in
Figure 7. It should be noted that the arrows linking the same nodes in two time slices, schematically illustrating the temporal conditional transition probabilities, are not explicitly drawn to provide a high-resolution overview of the dynamic BN model.
The dynamic Bayesian Network (BN) model describes the temporal probability evolution between time slices (a time slice refers to a time interval considered in a dynamic BN, e.g., 1 day, 1 week, 1 month, 1 year, etc.). The model in every time slice should be identical. In principle, the nodes representing the basic components in the current time slice should be linked through directed lines/arrows to the same nodes in the next time slice. If there are many nodes, e.g., in the case study, these lines/arrows will unfavorably affect the readability. The big blue arrow is used to approximately represent these arrows in
Figure 7.
The criterion for choosing a time interval between slices should depend upon the actual maintenance interval adopted by the owners. As mentioned in
Section 1, the marine energy industry is still at a pre-mature stage. So, the operating experience in wind industry can be borrowed. Generally, the wind turbine owners have both long-term of short-term maintenance plans. The short-term maintenance is usually planned on a monthly basis. Therefore, the time interval between slices is one month, namely
, as mentioned in
Section 3.3.3, is equal to 1 month. With consideration of 20-year design lifetime, there are 240 time slices in the dynamic BN model.
7.5. Realizations of Time to Failure of Basic Components
In nature, the TTF of basic components is a stochastic variable. The Monte Carlo simulation is used to take into account of the uncertainty associated with the estimation of TTF. A total of N lifetime simulations (
N = 1000) were performed. The TTF of basic components is simulated in parallel, based upon the fundamental assumption that the failures of basic components are statistically independent. The system TTF is determined by the logic dependencies in the hierarchy in
Table 5.
The results of one realization are given in
Table 6. The number of system failures simulated in this realization is listed in the first column. The second column includes the sequence of failure components until each system failure. The third column includes the time the components on the same row in the second column fail. For each system failure, the system failure time is just the last entry in the list. After the system failure, corrective maintenance should be done to replace the damaged basic components. The duration for corrective maintenance should take into account of the waiting time, the transportation time and the repair time, as
twait shown in
Figure 4. The accurate prediction of weather window is not the focus in this study. Therefore, an empirical estimation of
twait is 24 h (e.g., in a benign sea), no matter which failed component is repaired.
Each of the component failures can be considered as an observation (evidence). The BN model takes into account of these observations, by setting the states of the failed components to 0. How these observations are taken into account in the BN model will be presented as follows.
The second system failure in
Table 6 is used as an example to show the procedure, with the schematic shown in
Figure 8. The boxes on the top represent the chronologic months. Green represents that no basic component fails in the specific month. Yellow represents the failure of a basic component in the specific month. Red represents the time the energy transfer subsystem fails. The arrows underneath both yellow and red boxes point to the names of the failed components. In Month 107 and 112, the basic components ‘X6’ and ‘X1’ fail, and such an information is stored as observations. The information, including the names of failed components and the failure time, is transferred to the BN model, through an interface function represented by the green container in
Figure 9. The states of the nodes representing these two components are set to 0 and kept until they are replaced. The information is used to calculate the probabilities of different states of the units at all levels. In Month 113, the basic components ‘X20’ fails, which results in the energy transfer subsystem failure, based upon the logic interrelationship defined in
Table 5. Such an observation can also be transferred to the BN model to calculate the probabilities of different states of the units at all levels. The failed components are replaced after M113, and the states of these components will be restored to 1. The current time is shifted to M113 +
twait (
twait is the waiting time as mentioned above). The time to failure of basic components will be simulated in parallel again. Repeat the same aforementioned procedure.