Main Menu

See All Software di analisi e simulazione See All Software DAQ See All Driver e API See All Utilità See All Controllo delle vibrazioni See All Sistemi di alta precisione e calibrazione See All Sistemi DAQ See All Dispositivi portatili S&V See All Elettronica industriale See All Analizzatore di potenza See All Condizionatore di segnale S&V See All Trasduttori acustici See All Sensori di corrente e tensione See All Sensori di spostamento See All Sensori di forza See All Load Cells See All Multi Component Sensors See All Pressure Sensors See All Strain Sensors See All Estensimetri See All Temperature Sensors See All Tilt Sensors See All Torque Sensors See All Vibration Transducers See All Accessories for Vibration Testing Equipment See All Vibration Controllers See All Measurement Exciters See All Modal Exciters See All Power Amplifiers See All LDS Shaker Systems See All Test Solutions See All Actuators See All Combustion Engines See All Durability See All eDrive See All Production Testing Sensors See All Transmission & Gearboxes See All Turbo Charger

Treating Common Cause Failures in Fault Trees

Common cause failure analysis is important in reliability and safety studies, as common cause failures often dominate random hardware failures. Systems affected by common cause failures are systems in which two or more events have the potential of occurring due to the same cause. Some typical common causes include impact, vibration, pressure, grit, stress and temperature. HBM Prenscia provides an innovative approach to handle common cause failures. Failures that cause different events to happen can be modeled with mirrored blocks in ReliaSoft BlockSim.

Mirrored blocks


Mirrored blocks allow you to place the exact same block in multiple locations within a reliability block diagram (RBD) or a fault tree. This can be useful for many purposes, such as modeling bi-directional paths within a diagram and common cause failures. Mirroring is accomplished by adding blocks to a mirror group. Mirror groups are resources that can be shared among analyses and can be managed via the Resource Manager. Blocks that belong to a mirror group have a square at the lower left corner of the block; the appearance of the indicator and its caption are configurable.


Mirrored blocks are treated as fully equivalent multiple instances of a single block, rather than considered as an original and copies. The failure times and all maintenance events are identical for every block in the mirror group. Any changes made to the properties of a block in a mirror group will apply to all other blocks in the mirror group.


Using mirrored blocks guarantees that multiple blocks will exhibit the same behavior (e.g. failures...) and experience the same action (e.g. corrective maintenance, inspections...) simultaneously. Entering the same properties for different blocks in a diagram does not ensure that these blocks will act like mirrored blocks. For example, because of the randomness, blocks that have the same failure distribution and the same parameters could still fail at different times when performing a simulation. 

Using mirrored blocks for common cause failure analysis


Common cause failures have traditionally been handled using the Beta, MGL, Alpha and BFR models. BlockSim has a simpler and more effective approach to handling common cause failure that relies on the use of mirrored blocks. Therefore, the traditional common cause failure analysis methods will not be discussed in this article. The following example illustrates the BlockSim approach.

Consider the following example in which Event A could cause both an X Failure (if it happens along with a B event) and a Y Failure (if it happens along with a C event).

The above example describes a simple common cause failure problem. In this example, the A event is the common cause. A failure distribution needs to be specified for the A, B and C events. The events' failure distributions are listed next.

You can use mirrored blocks to indicate that the two A events are actually the same event and to specify that if event A occurs then Failures X and Y could occur.

The probability of a system level failure occurrence can be found using the Quick Calculation Pad as follows.

If the two events A in this fault tree example were not mirrored, the results would have differed, as the following figure shows.

The difference becomes more significant when the model complexity increases.