BlockSim Example: CM Triggered by Subsystem Down: Difference between revisions
Dingzhou Cao (talk | contribs) |
Dingzhou Cao (talk | contribs) |
||
| Line 31: | Line 31: | ||
#At 271, Block C fails and get repair at 291. | #At 271, Block C fails and get repair at 291. | ||
#At 331, Block B fails. Since the subsystem is not down (Both A and B fails, then subsystem fails), Block B is waiting for repair opportunity after its failure. | #At 331, Block B fails. Since the subsystem is not down (Both A and B fails, then subsystem fails), Block B is waiting for repair opportunity after its failure. | ||
#At 381, Block A fails and subsystem AB fails. Subsystem fails trigger | #At 381, Block A fails and subsystem AB fails. Subsystem fails trigger the inspection and then inspection triggers CM. | ||
#At 501, both Block A and B are restored. | |||
#At 791, Block B fails and is waiting for repair opportunity. | |||
#At 943, Block C fails and get restored at 963. | |||
#At 1358, Block A fails and subsystem AB fails, triggering CM for Block A and B. | |||
#At 1478, both Block A and B are restored. | |||
... | |||
Revision as of 23:12, 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, they are as good as new.
There is an inspection for both block A and B. The inspection is performed based on events in maintenance group MG_AB. If "Block fails" or "Start of corrective maintenance" event occurs for any of the blocks in the maintenance group MG_AB, then the inspection is performed. The inspection duration is set to "Immediate Repair" and upon inspection, the device is restored to same as it was when it failed (as bad as old).
CM of Block C is performed upon failure of Block C and the duration is 20 hours. It is as good as new upon repair.
Block Up/Down plot
The system event log is shown in Figure belwo and is as follows:
- At 271, Block C fails and get repair at 291.
- At 331, Block B fails. Since the subsystem is not down (Both A and B fails, then subsystem fails), Block B is waiting for repair opportunity after its failure.
- At 381, Block A fails and subsystem AB fails. Subsystem fails trigger the inspection and then inspection triggers CM.
- At 501, both Block A and B are restored.
- At 791, Block B fails and is waiting for repair opportunity.
- At 943, Block C fails and get restored at 963.
- At 1358, Block A fails and subsystem AB fails, triggering CM for Block A and B.
- At 1478, both Block A and B are restored.
...
