arrow_back_ios

Main Menu

See All Software See All Instrumente See All Aufnehmer See All Schwingungsprüfung See All Elektroakustisch See All Akustische End-of-Line-Testsysteme See All Events See All Akademie See All Anwendungen See All Industrien See All Kalibrierung See All Ingenieurdienstleistungen See All Unterstützen
arrow_back_ios

Main Menu

See All Durability See All Reliability See All Analyse Simulation See All DAQ See All API Treiber See All Dienstprogramm See All Vibrationskontrolle See All Kalibrierung See All DAQ See All Handheld See All Industriell See All Power Analyzer See All Signalaufbereiter See All Akustik See All Strom und Spannung See All Weg See All Kraft See All Wägezellen See All Mehrkomponenten See All Druck See All Dehnung See All Dehnungsmessstreifen See All Temperatur See All Neigen See All Drehmoment See All Vibration See All Zubehör See All Steuerungen See All Messerreger See All Modalerreger See All Leistungsverstärker See All Shaker Systeme See All Testlösungen See All Aktoren See All Verbrennungsmotoren See All Betriebsfestigkeit See All eDrive See All Sensoren für Produktionstests See All Getriebe See All Turbolader See All Schulungskurse See All Akustik See All Anlagen- und Prozessüberwachung See All Elektrische Energie See All Kundenspezifische Sensoren See All NVH See All Smarte Sensoren See All Schwingbelastung See All Strukturelle Integrität See All Automobil & Bodentransport See All Druckkalibrierung | Sensor | Messumformer See All Kalibrierung oder Reparatur anfordern See All Kalibrierung und Verifizierung See All Kalibrierung Plus Vertrag See All Brüel & Kjær Support
arrow_back_ios

Main Menu

See All Aqira See All nCode Viewer (DE) See All Weibull++ - NEW TEST (DE) See All Weibull++ - NEW TEST (DE) See All BlockSim - New Test (DE) See All BlockSim - New Test (DE) See All XFRACAS - New Test (DE) See All XFMEA - New Test (DE) See All XFMEA - New Test (DE) See All RCM++ - New Test (DE) See All RCM++ - New Test (DE) See All SEP - New Test (DE) See All SEP - New Test (DE) See All Lambda Predict - New Test (DE) See All Lambda Predict - New Test (DE) See All MPC - New Test (DE) See All nCode - Durability and Fatigue Analysis See All ReliaSoft - Reliability Analysis and Management See All API See All Elektroakustik See All Umgebungslärm See All Identifizierung der Lärmquelle See All Produkt-Lärm See All Schallleistung und Schalldruck See All Vorbeifahrgeräusche See All Produktionsprüfung und Qualitätssicherung See All Maschinenanalyse und -diagnose See All Strukturelle Gesundheitsüberwachung See All Strukturüberwachung See All Batterieprüfung See All Einführung in die Messung elektrischer Leistung bei transienten Vorgängen See All Transformator-Ersatzschaltbild | HBM See All Strukturelle Dynamik See All Prüfung der Materialeigenschaften See All Sicherstellung der strukturellen Integrität von Leichtbaustrukturen See All Elektrifizierung von Fahrzeugen See All Seiten, die nicht migriert wurden See All Software-Lizenzverwaltung

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.