arrow_back_ios

Main Menu

See All ソフトウェア See All 計測器 See All トランスデューサ See All 振動試験装置 See All 電気音響 See All 音響エンドオブライン試験システム See All アプリケーション See All インダストリーズ See All キャリブレーション See All エンジニアリングサービス See All サポート
arrow_back_ios

Main Menu

See All 解析シミュレーション See All DAQ See All APIドライバ See All ユーティリティ See All 振動コントロール See All 校正 See All DAQ See All ハンドヘルド See All 産業 See All パワーアナライザ See All シグナルコンディショナー See All 音響 See All 電流電圧 See All 変位 See All 力 See All ロードセル See All マルチコンポーネント See All 圧力 See All ひずみ See All ひずみゲージ See All 温度 See All チルト See All トルク See All 振動 See All アクセサリ See All コントローラ See All 測定加振器 See All モーダル加振器 See All パワーアンプ See All 加振器システム See All テストソリューション See All アクチュエータ See All 内燃機関 See All 耐久性 See All eDrive See All 生産テストセンサ See All トランスミッションギアボックス See All ターボチャージャ See All アコースティック See All アセット&プロセスモニタリング See All 電力 See All NVH See All OEMカスタムセンサ See All 構造的な整合性 See All 振動: See All 自動車・地上輸送 See All 圧力校正|センサー|振動子 See All 校正・修理のご依頼 See All キャリブレーションとベリフィケーション See All キャリブレーション・プラス契約 See All サポート ブリュエル・ケアー
arrow_back_ios

Main Menu

See All nCode - 耐久性および疲労解析 See All ReliaSoft - 信頼性解析と管理 See All API See All 電気音響 See All 環境ノイズ See All 騒音源の特定 See All 製品ノイズ See All 音響パワーと音圧 See All 自動車通過騒音 See All 生産テストと品質保証 See All 機械分析・診断 See All 構造物ヘルスモニタリング See All バッテリーテスト See All 過渡現象時の電力測定入門 See All トランスの等価回路図|HBM See All アグリ業界向けOEMセンサー See All ロボティクスとトルクアプリケーション用OEMセンサー See All 構造ダイナミクス See All 材料特性試験 See All pages-not-migrated See All ソフトウェアライセンス管理

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.