Template:Rotation - Revision history

Lisa Hacker: Redirected page to Example Using SCT for Standby Rotation

2012-07-31T09:37:08Z

Redirected page to Example Using SCT for Standby Rotation

← Older revision		Revision as of 09:37, 31 July 2012
Line 1:		Line 1:
	~~=== Standby Rotation===~~		#REDIRECT [[Example_Using_SCT_for_Standby_Rotation]]

	~~==== Purpose ====~~

	This example illustrates the use of state change triggers ([http://www.reliawiki.org/index.php/BlockSim_8:_State_Change_Triggers#State_Change_Triggers SCT]) in BlockSim Version 8 by using a simple standby configuration. ''Note that this example could also be done using the standby container functionality in BlockSim.''

	~~More specifically, the following settings are illustrated:~~
	~~#State Upon Repair: Default OFF unless SCT overridden~~
	~~#Activate a block if any item from these associated maintenance group(s) goes down<br>~~

	~~==== Statement ====~~

	Assume three devices A, B and C in a standby redundancy (or only one unit is needed for system operation). The system begins with device A working. When device A fails, B is turned on and repair actions are initiated on A. When B fails, C is turned on and so forth.

	~~==== BlockSim Solution ====~~

	~~The BlockSim model of this system is shown in the figure below.~~

	~~[[Image:Blocksim Example Rotation example.png\|center\|200px]]~~



	*The failure distributions of all three blocks follow a Weibull distribution with Beta = 1.5 and Eta = 1,000 hours.
	*The repair distributions of the three blocks follow a Weibull distribution with Beta = 1.5 and Eta = 100 hours.
	*After repair, the blocks are "as good as new."


	~~There are three maintenance groups, 2_A, 2_B and 2_C, set as follows:~~


	*Block A belongs to maintenance group 2_A.
	**It has a state change trigger.
	***The initial state is ON and the state upon repair is "Default OFF unless SCT overridden."
	***If any item from maintenance group 2_C goes down, then activate this block.



	*Block B belongs to maintenance group 2_B.
	**It has a state change trigger.
	***The initial state is OFF and the state upon repair is "Default OFF unless SCT overridden."
	***If any item from maintenance group 2_A goes down, then activate this block.


	*Block C belongs to maintenance group 2_C.
	**It has a state change trigger.
	***The initial state is OFF and the state upon repair is "Default OFF unless SCT overridden."
	***If any item from maintenance group 2_B goes down, then activate this block.


	*All blocks A, B and C are as good as new after repair.

	~~==== System Events ====~~



	~~The system event log for a single run through the simulation algorithm is shown in the Block Up/Down plot below, and is as follows:~~

	~~#At 73 hours, Block A fails and activates Block B.~~
	~~#At 183 hours, Block B fails and activates Block C.~~
	~~#At 215 hours, Block B is done with repair. At this time, Block C is operating, so according to the settings, Block B is standby.~~
	~~#At 238 hours, Block A is done with repair. At this time, Block C is operating. Thus Block A is standby.~~
	~~#At 349 hours, Block C fails and activates Block A.~~
	~~#At 396 hours, Block A fails and activates Block B.~~
	~~#At 398 hours, Block C is done with repair. At this time, Block B is operating. Thus Block C is standby.~~
	~~#At 432 hours, Block A is done with repair. At this time, Block B is operating. Thus Block A is standby.~~
	~~#At 506 hours, Block B fails and activates Block C.~~
	#~~At 515 hours, Block B is done with repair and stays standby because Block C is operating.~~
	~~#At 536 hours, Block C fails and activates Block A.~~
	~~#At 560 hours, Block A fails and activates Block B.~~
	#At 575 hours, Block B fails and makes a request to activate Block C. However, Block C is under repair at the time. Thus when Block C is done with repair at 606 hours, the OFF setting is overridden and it is operating immediately.
	#At 661 hours, Block C fails and makes a request to activate Block A. However, Block A is under repair at the time. Thus when Block A is done with repair at 699 hours, the OFF setting is overridden and it is operating immediately.
	#Block B and Block C are done with repair at 682 hours and at 746 hours respectively. However, at these two time points, Block A is operating. Thus they are both standby upon repair according to the settings.



	~~[[Image:Block Up Down plot for rotation example.png\|center\|450px]]~~

	[[~~Category:BlockSim_Examples~~]]

Richard House: /* System Events */

2012-07-31T08:17:54Z

System Events

← Older revision		Revision as of 08:17, 31 July 2012
Line 74:		Line 74:


	[[Image:Block Up Down plot for rotation example.png\|center\|~~350px~~]]		[[Image:Block Up Down plot for rotation example.png\|center\|450px]]

	[[Category:BlockSim_Examples]]		[[Category:BlockSim_Examples]]

Richard House: /* BlockSim Solution */

2012-07-31T08:17:35Z

BlockSim Solution

← Older revision		Revision as of 08:17, 31 July 2012
Line 17:		Line 17:
	The BlockSim model of this system is shown in the figure below.		The BlockSim model of this system is shown in the figure below.

	[[Image:Blocksim Example Rotation example.png\|center\|~~150px~~]]		[[Image:Blocksim Example Rotation example.png\|center\|200px]]

Melinda Caroline: /* System Events */

2012-06-15T13:03:15Z

System Events

← Older revision		Revision as of 13:03, 15 June 2012
Line 74:		Line 74:


	[[Image:Block Up Down plot for rotation example.png\|center\|~~250px~~]]		[[Image:Block Up Down plot for rotation example.png\|center\|350px]]

	[[Category:BlockSim_Examples]]		[[Category:BlockSim_Examples]]

Chuck Smith: /* System Events */

2012-04-25T20:52:26Z

System Events

← Older revision		Revision as of 20:52, 25 April 2012
Line 74:		Line 74:


	[[Image:Block Up Down plot for rotation example.png\|center\|~~500px~~]]		[[Image:Block Up Down plot for rotation example.png\|center\|250px]]

	[[Category:BlockSim_Examples]]		[[Category:BlockSim_Examples]]

Chuck Smith: /* BlockSim Solution */

2012-04-25T20:52:11Z

BlockSim Solution

← Older revision		Revision as of 20:52, 25 April 2012
Line 17:		Line 17:
	The BlockSim model of this system is shown in the figure below.		The BlockSim model of this system is shown in the figure below.

	[[Image:Blocksim Example Rotation example.png\|center\|~~361px~~]]		[[Image:Blocksim Example Rotation example.png\|center\|150px]]

Nikki Helms: /* System Events */

2012-03-30T17:59:32Z

System Events

← Older revision		Revision as of 17:59, 30 March 2012
Line 74:		Line 74:


	[[Image:Block Up Down plot for rotation example.png~~\|thumb~~\|center\|500px]]		[[Image:Block Up Down plot for rotation example.png\|center\|500px]]

	[[Category:BlockSim_Examples]]		[[Category:BlockSim_Examples]]

Nikki Helms: /* BlockSim Solution */

2012-03-30T17:44:23Z

BlockSim Solution

← Older revision		Revision as of 17:44, 30 March 2012
Line 17:		Line 17:
	The BlockSim model of this system is shown in the figure below.		The BlockSim model of this system is shown in the figure below.

	[[Image:Blocksim Example Rotation example.png~~\|thumb~~\|center\|361px]]		[[Image:Blocksim Example Rotation example.png\|center\|361px]]

Melinda Caroline: /* BlockSim Solution */

2012-03-08T22:56:09Z

BlockSim Solution

← Older revision		Revision as of 22:56, 8 March 2012
Line 21:		Line 21:


	*The failure distributions of all three blocks follow a Weibull distribution with Beta = 1.5 and Eta = 1,000.		*The failure distributions of all three blocks follow a Weibull distribution with Beta = 1.5 and Eta = 1,000 hours.
	*The repair distributions of the three blocks follow a Weibull distribution with Beta = 1.5 and Eta = 100.		*The repair distributions of the three blocks follow a Weibull distribution with Beta = 1.5 and Eta = 100 hours.
	*After repair, the blocks are "as good as new."		*After repair, the blocks are "as good as new."

Melinda Caroline: /* System Events */

2012-03-08T22:43:55Z

System Events

← Older revision		Revision as of 22:43, 8 March 2012
Line 54:		Line 54:


	The system event log is shown Block Up/Down plot below, ~~for a single run through the simulation algorithm~~ and is as follows:		The system event log for a single run through the simulation algorithm is shown in the Block Up/Down plot below, and is as follows:

	#At 73, Block A fails and activates Block B.		#At 73 hours, Block A fails and activates Block B.
	#At 183, Block B fails and activates Block C.		#At 183 hours, Block B fails and activates Block C.
	#At 215, Block B is done with repair. At this time, Block C is operating, according to ~~setting~~, Block B is standby.		#At 215 hours, Block B is done with repair. At this time, Block C is operating, so according to the settings, Block B is standby.
	#At 238, Block A is done with repair. At this time, Block C is operating. Thus Block A is standby.		#At 238 hours, Block A is done with repair. At this time, Block C is operating. Thus Block A is standby.
	#At 349, Block C fails and activates Block A.		#At 349 hours, Block C fails and activates Block A.
	#At 396, Block A fails and activates Block B.		#At 396 hours, Block A fails and activates Block B.
	#At 398, Block C is done with repair. At this time, Block B is operating. Thus Block C is standby.		#At 398 hours, Block C is done with repair. At this time, Block B is operating. Thus Block C is standby.
	#At 432, Block A is done with repair. At this time, Block B is operating. Thus Block A is standby.		#At 432 hours, Block A is done with repair. At this time, Block B is operating. Thus Block A is standby.
	#At 506, Block B fails and activates Block C.		#At 506 hours, Block B fails and activates Block C.
	#At 515, Block B is done with repair and ~~keeps~~ standby because Block C is operating.		#At 515 hours, Block B is done with repair and stays standby because Block C is operating.
	#At 536, Block C fails and ~~active~~ Block A.		#At 536 hours, Block C fails and activates Block A.
	#At 560, Block A fails and ~~active~~ Block B.		#At 560 hours, Block A fails and activates Block B.
	#At 575, Block B fails and ~~put~~ a request to ~~active~~ Block C. However, Block C is under repair at the time. Thus when Block C is done with repair at 606, the OFF setting is ~~overwritten~~ and it is operating immediately.		#At 575 hours, Block B fails and makes a request to activate Block C. However, Block C is under repair at the time. Thus when Block C is done with repair at 606 hours, the OFF setting is overridden and it is operating immediately.
	#At 661, Block C fails and ~~put~~ a request to ~~active~~ Block A. However, Block A is under repair at the time. Thus when Block A is done with repair at 699, the OFF setting is ~~overwritten~~ and it is operating immediately.		#At 661 hours, Block C fails and makes a request to activate Block A. However, Block A is under repair at the time. Thus when Block A is done with repair at 699 hours, the OFF setting is overridden and it is operating immediately.
	#Block B and Block C are done with repair at 682 and at 746 respectively. However, at these two time ~~point~~, Block A is operating. Thus they are both standby upon repair according to settings.		#Block B and Block C are done with repair at 682 hours and at 746 hours respectively. However, at these two time points, Block A is operating. Thus they are both standby upon repair according to the settings.