arrow_back_ios

Main Menu

See All Simulação e Análise See All DAQ See All Drivers API See All Utilitário See All Controle de vibração See All Calibração See All DAQ See All Portátil See All Industrial See All Analisadores de potência See All Condicionadores de sinal See All Acústica See All Tensão e Corrente See All Deslocamento See All Força See All Células de carga See All Multicomponente See All Pressão See All Deformação See All Strain Gauges See All Temperatura See All Inclinação See All Torque See All Vibração See All Acessórios See All Controladores See All Excitadores de medição See All Excitadores modais See All Amplificadores de potência See All Sistemas Shaker See All Soluções de teste See All Atuadores See All Motores de combustão See All Durabilidade See All eDrive See All Sensores de teste de produção See All Caixas de transmissão See All Turbo Charger See All Cursos de formação See All Acústica See All Monitorização de activos e processos See All Energia eléctrica See All Sensores personalizados See All NVH See All Sensores personalizados do OEM See All Vibração See All Integridade estrutural See All Transporte automotivo e terrestre
arrow_back_ios

Main Menu

See All nCode - Análise de Durabilidade e Fadiga See All ReliaSoft - Análise e gerenciamento de confiabilidade See All API See All Ruído do produto See All Ruído de passagem de veículos See All Electroacoustics See All Identificação da fonte de ruído See All Ruído ambiental See All O que é potência sonora e pressão sonora See All Certificação de ruído See All Teste de produção e garantia de qualidade See All Análise e Diagnóstico de Máquinas See All Monitoramento de integridade estrutural See All Teste de bateria See All Introdução à Medição de Energia Elétrica Durante Transitórios See All Diagrama de circuito equivalente do transformador | HBM See All Sensores OEM para a indústria agrícola See All Sensores OEM para aplicações robóticas e de torque See All Dinâmica estrutural See All Ensaio das propriedades dos materiais

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.