BlockSim Example: CM Triggered by Subsystem Down: Difference between revisions
Jump to navigation
Jump to search
Dingzhou Cao (talk | contribs) |
Dingzhou Cao (talk | contribs) |
||
| Line 16: | Line 16: | ||
Reliability of all blocks follow Weibull distribution with Beta =1.5 and Eta=500 hours. | Reliability of all blocks follow Weibull distribution with Beta =1.5 and Eta=500 hours. | ||
Block A and Block B are belong to maintenance group MG_AB. | |||
CM of Block A and B are set to "When found failed during an inspection". The CM duration is 120 hour and upon repair, it is as good as new. | CM of Block A and B are set to "When found failed during an inspection". The CM duration is 120 hour and upon repair, it is as good as new. | ||
Revision as of 22:21, 22 August 2011
CM triggered by subsystem down
Purposes
The purposes of this example is to illustrate how to model the case when CM is triggered by failure of subsystem.
Description
Three devices A, B and C are in parallel. A and B form a subsystem. Only both A and B fail (subsystem fails), then start to repair A and B. The repair of C is depend on its failure. When C fails, then start to repair C.
BlockSim Solution
The BlockSim modeling of this system is shown in Figure below.
Reliability of all blocks follow Weibull distribution with Beta =1.5 and Eta=500 hours.
Block A and Block B are belong to maintenance group MG_AB.
CM of Block A and B are set to "When found failed during an inspection". The CM duration is 120 hour and upon repair, it is as good as new.