Example Using SCT for Standby Rotation - Revision history

Lisa Hacker at 21:02, 18 September 2023

2023-09-18T21:02:47Z

← Older revision		Revision as of 21:02, 18 September 2023
Line 1:		Line 1:
	<noinclude>{{Banner BlockSim Examples}}		<noinclude>{{Banner BlockSim Examples}}
	''This example also appears in the [~~[Repairable_Systems_Analysis_Through_Simulation#State_Change_Triggers\|~~System ~~Analysis Reference book]~~]''. </noinclude>		''This example also appears in the [https://help.reliasoft.com/reference/system_analysis System analysis reference]''. </noinclude>

	This example illustrates the use of state change triggers in BlockSim (Version 8 and above) by using a simple standby configuration. ''Note that this example could also be done using the standby container functionality in BlockSim.''		This example illustrates the use of state change triggers in BlockSim (Version 8 and above) by using a simple standby configuration. ''Note that this example could also be done using the standby container functionality in BlockSim.''

Richard House at 20:26, 6 January 2016

2016-01-06T20:26:59Z

← Older revision		Revision as of 20:26, 6 January 2016
Line 16:		Line 16:
	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\|~~300px~~\|link=]]		[[Image:Blocksim Example Rotation example.png\|center\|250px\|link=]]

	*The failure distributions of all three blocks follow a Weibull distribution with Beta = 1.5 and Eta = 1,000 hours.		*The failure distributions of all three blocks follow a Weibull distribution with Beta = 1.5 and Eta = 1,000 hours.

Richard House at 18:34, 5 January 2016

2016-01-05T18:34:05Z

← Older revision		Revision as of 18:34, 5 January 2016
Line 65:		Line 65:


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

Richard House at 18:33, 5 January 2016

2016-01-05T18:33:24Z

← Older revision		Revision as of 18:33, 5 January 2016
Line 16:		Line 16:
	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\|~~200px~~]]		[[Image:Blocksim Example Rotation example.png\|center\|300px\|link=]]

	*The failure distributions of all three blocks follow a Weibull distribution with Beta = 1.5 and Eta = 1,000 hours.		*The failure distributions of all three blocks follow a Weibull distribution with Beta = 1.5 and Eta = 1,000 hours.

Lisa Hacker at 16:47, 11 June 2013

2013-06-11T16:47:10Z

← Older revision		Revision as of 16:47, 11 June 2013
Line 2:		Line 2:
	''This example also appears in the [[Repairable_Systems_Analysis_Through_Simulation#State_Change_Triggers\|System Analysis Reference book]]''. </noinclude>		''This example also appears in the [[Repairable_Systems_Analysis_Through_Simulation#State_Change_Triggers\|System Analysis Reference book]]''. </noinclude>

	This example illustrates the use of state change triggers 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.''		This example illustrates the use of state change triggers in BlockSim (Version 8 and above) 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:		More specifically, the following settings are illustrated:

Lisa Hacker at 07:14, 17 August 2012

2012-08-17T07:14:53Z

← Older revision		Revision as of 07:14, 17 August 2012
Line 1:		Line 1:
	<noinclude>{{Banner BlockSim Examples}}		<noinclude>{{Banner BlockSim Examples}}
	''This example also appears in the [[Repairable_Systems_Analysis_Through_Simulation#State_Change_Triggers\|System Analysis Reference book]]''. </noinclude>		''This example also appears in the [[Repairable_Systems_Analysis_Through_Simulation#State_Change_Triggers\|System Analysis Reference book]]''. </noinclude>

	This example illustrates the use of state change triggers 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.''		This example illustrates the use of state change triggers 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.''

Lisa Hacker at 07:14, 17 August 2012

2012-08-17T07:14:42Z

← Older revision		Revision as of 07:14, 17 August 2012
Line 1:		Line 1:
	<noinclude>{{Banner BlockSim Examples}}</noinclude>		<noinclude>{{Banner BlockSim Examples}}
			''This example also appears in the [[Repairable_Systems_Analysis_Through_Simulation#State_Change_Triggers\|System Analysis Reference book]]''. </noinclude>
	This example illustrates the use of state change triggers 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.''		This example illustrates the use of state change triggers 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.''

Richard House at 07:23, 7 August 2012

2012-08-07T07:23:05Z

← Older revision		Revision as of 07:23, 7 August 2012
Line 6:		Line 6:
	#Activate a block if any item from these associated maintenance group(s) goes down<br>		#Activate a block if any item from these associated maintenance group(s) goes down<br>

	~~<br>~~
	'''Problem Statement'''		'''Problem Statement'''
	~~<br>~~

	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.		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.

	~~<br>~~
	'''BlockSim Solution'''		'''BlockSim Solution'''
	~~<br>~~

	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\|200px]]		[[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 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.		*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."


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


	*Block A belongs to maintenance group 2_A.		*Block A belongs to maintenance group 2_A.
Line 34:		Line 26:
	***The initial state is ON and the state upon repair is "Default OFF unless SCT overridden."		***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.		***If any item from maintenance group 2_C goes down, then activate this block.



Line 52:		Line 43:

	'''System Events'''		'''System Events'''
	~~<br>~~

	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:		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:
Line 71:		Line 61:
	#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.		#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.		#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]]		[[Image:Block Up Down plot for rotation example.png\|center\|450px]]

Melinda Caroline at 05:11, 6 August 2012

2012-08-06T05:11:55Z

← Older revision		Revision as of 05:11, 6 August 2012
Line 1:		Line 1:
	<noinclude>{{Banner BlockSim Examples}}		<noinclude>{{Banner BlockSim Examples}}</noinclude>
	~~''This example appears in the [[Repairable_Systems_Analysis_Through_Simulation#State_Change_Triggers\|System Analysis Reference book]]''.~~
	</noinclude>
	This example illustrates the use of state change triggers 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.''		This example illustrates the use of state change triggers 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.''

Lisa Hacker at 02:56, 2 August 2012

2012-08-02T02:56:52Z

← Older revision		Revision as of 02:56, 2 August 2012
Line 2:		Line 2:
	''This example appears in the [[Repairable_Systems_Analysis_Through_Simulation#State_Change_Triggers\|System Analysis Reference book]]''.		''This example appears in the [[Repairable_Systems_Analysis_Through_Simulation#State_Change_Triggers\|System Analysis Reference book]]''.
	</noinclude>		</noinclude>
			This example illustrates the use of state change triggers 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.''

	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:		More specifically, the following settings are illustrated:
Line 10:		Line 8:
	#Activate a block if any item from these associated maintenance group(s) goes down<br>		#Activate a block if any item from these associated maintenance group(s) goes down<br>

			<br>
	'''Problem Statement'''		'''Problem Statement'''
	<br>		<br>
Line 15:		Line 14:
	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.		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.

			<br>
	'''BlockSim Solution'''		'''BlockSim Solution'''
	<br>		<br>