BlockSim Example: Default OFF unless SCT Overridden - Revision history

Lisa Hacker at 21:04, 18 September 2023

2023-09-18T21:04:07Z

← Older revision		Revision as of 21:04, 18 September 2023
Line 1:		Line 1:
	<noinclude>{{Banner BlockSim Examples}}		<noinclude>{{Banner BlockSim Examples}}
	</noinclude>		</noinclude>
	The purpose of this example is to illustrate how the following options in BlockSim's [[State Change Triggers]] affect simulation:		The purpose of this example is to illustrate how the following options in BlockSim's State Change Triggers affect simulation:

	#State Upon Repair: Default OFF unless SCT overridden<br>		#State Upon Repair: Default OFF unless SCT overridden<br>

Richard House at 07:25, 7 August 2012

2012-08-07T07:25:17Z

← Older revision		Revision as of 07:25, 7 August 2012
Line 9:		Line 9:
	#Deactivate a block if any item from these associated maintenance group(s) is restored<br>		#Deactivate a block if any item from these associated maintenance group(s) is restored<br>

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

	Consider the system shown in the figure below:		Consider the system shown in the figure below:
Line 23:		Line 21:
	*All blocks A1, A2, B and C have a Weibull distribution with Beta = 1.5 and Eta = 100 for reliability. Blocks A1 and C have a Weibull distribution with Beta = 1.5 and Eta = 100 for the repair action. Block B has Weibull a distribution with Beta = 1.5 and Eta = 150 for the repair action. Block A2 has a Weibull distribution with Beta = 1.5 and Eta = 200 for the repair action. All blocks are as good as new after repair.		*All blocks A1, A2, B and C have a Weibull distribution with Beta = 1.5 and Eta = 100 for reliability. Blocks A1 and C have a Weibull distribution with Beta = 1.5 and Eta = 100 for the repair action. Block B has Weibull a distribution with Beta = 1.5 and Eta = 150 for the repair action. Block A2 has a Weibull distribution with Beta = 1.5 and Eta = 200 for the repair action. All blocks are as good as new after repair.

	~~<br>~~
	'''Block Up/Down Plot'''		'''Block Up/Down Plot'''
	~~<br>~~

	The system event log, for a simulation of 820 hours, is shown in the figure below and explained next		The system event log, for a simulation of 820 hours, is shown in the figure below and explained next

Richard House at 07:28, 6 August 2012

2012-08-06T07:28:05Z

← Older revision		Revision as of 07:28, 6 August 2012
Line 15:		Line 15:
	Consider the system shown in the figure below:		Consider the system shown in the figure below:

	[[Image:Default OFF unless SCT overridden.png~~\|thumb~~\|center\|500px]]		[[Image:Default OFF unless SCT overridden.png\|center\|500px]]

	*Block A1 belongs to maintenance group A1.		*Block A1 belongs to maintenance group A1.
Line 50:		Line 50:
	#At 802 hours, Block A2 fails		#At 802 hours, Block A2 fails

	[[Image:Block up down plot for default OFF unless SCT overridden example.png~~\|thumb~~\|center\|600px]]		[[Image:Block up down plot for default OFF unless SCT overridden example.png\|center\|600px]]

Richard House at 06:49, 2 August 2012

2012-08-02T06:49:37Z

← Older revision		Revision as of 06:49, 2 August 2012
Line 27:		Line 27:
	<br>		<br>

	The system ~~behavior~~ for a simulation of 820 hours ~~duration~~ is shown in the figure below and explained next.		The system event log, for a simulation of 820 hours, is shown in the figure below and explained next

	#At 7 hours, Block B fails and activates Block C.<br>		#At 7 hours, Block B fails and activates Block C.<br>

Richard House at 06:37, 2 August 2012

2012-08-02T06:37:18Z

Richard House at 06:33, 2 August 2012

2012-08-02T06:33:08Z

← Older revision		Revision as of 06:33, 2 August 2012
Line 50:		Line 50:
	#At 802 hours, Block A2 fails		#At 802 hours, Block A2 fails

	[[Image:Block up down plot for default OFF unless SCT overridden example.png\|thumb\|center\|~~500px~~]]		[[Image:Block up down plot for default OFF unless SCT overridden example.png\|thumb\|center\|600px]]

Richard House at 06:32, 2 August 2012

2012-08-02T06:32:50Z

← Older revision		Revision as of 06:32, 2 August 2012
Line 27:		Line 27:
	<br>		<br>

	The system behavior for a simulation of 820 hours ~~durations~~ is shown in the figure below and explained next.		The system behavior for a simulation of 820 hours duration is shown in the figure below and explained next.

	#At 7 hours, Block B fails and activates Block C.<br>		#At 7 hours, Block B fails and activates Block C.<br>

Richard House at 06:32, 2 August 2012

2012-08-02T06:32:34Z

← Older revision		Revision as of 06:32, 2 August 2012
Line 27:		Line 27:
	<br>		<br>

	The system behavior for simulation of 820 hours durations ~~(seed:23)~~ is shown in the figure below and explained next.		The system behavior for a simulation of 820 hours durations is shown in the figure below and explained next.

	#At 7 hours, Block B fails and activates Block C.<br>		#At 7 hours, Block B fails and activates Block C.<br>

Richard House at 06:24, 2 August 2012

2012-08-02T06:24:50Z

← Older revision		Revision as of 06:24, 2 August 2012
Line 13:		Line 13:
	<br>		<br>

	Consider a system shown in the figure below:		Consider the system shown in the figure below:

	[[Image:Default OFF unless SCT overridden.png\|thumb\|center\|500px]]		[[Image:Default OFF unless SCT overridden.png\|thumb\|center\|500px]]

Richard House at 05:33, 2 August 2012

2012-08-02T05:33:19Z

← Older revision		Revision as of 05:33, 2 August 2012
Line 27:		Line 27:
	<br>		<br>

	The system behavior for simulation of 820 hours durations (seed:23) is shown in ~~Figure~~ below and explained next.		The system behavior for simulation of 820 hours durations (seed:23) is shown in the figure below and explained next.

	#At 7, Block B fails and activates Block C.<br>		#At 7 hours, Block B fails and activates Block C.<br>
	#At 50, Block C fails and ~~gets~~ repair at 125. According to ~~setting~~, Block C is OFF upon repair.<br>		#At 50 hours, Block C fails and the repair is finished at 125 hours. According to its settings, Block C is OFF upon repair.<br>
	#At 71, Block A2 fails.<br>		#At 71 hours, Block A2 fails.<br>
	#At 214, Block B is restored. ~~And it~~ fails again at 254 and activates Block C at that point.<br>		#At 214 hours, Block B is restored. It fails again at 254 hours and activates Block C at that point.<br>
	#At 276, Block A1 fails, puts a request to deactivate Block A2. However, Block A2 is down for repair at this time. Nothing happens.<br>		#At 276 hours, Block A1 fails, puts a request to deactivate Block A2. However, Block A2 is down for repair at this time. Nothing happens.<br>
	#At 363, Block B is restored, ~~deactivates~~ Block C.		#At 363 hours, Block B is restored, deactivating Block C.
	#At 376, Block A1 is restored, and puts a request to activate Block A2. However, Block A2 is down for repair at this time. The state upon repair of Block A2 ~~is overridden~~ (~~default~~ OFF). Thus when it gets ~~repair~~ at 432, it is ON ~~upon repair~~. <br>		#At 376 hours, Block A1 is restored, and puts a request to activate Block A2. However, Block A2 is down for repair at this time. The state upon repair of Block A2 (Default OFF unless SCT overridden) is overridden. Thus when it gets repaired at 432 hours, it is ON. <br>
	#At 404, Block B fails and activates Block C.		#At 404 hours, Block B fails and activates Block C.
	#At 461, Block A1 fails and deactivates Block A2.		#At 461 hours, Block A1 fails and deactivates Block A2.
	#At 483, Block C fails.		#At 483 hours, Block C fails.
	#At 566, Block B is restored.		#At 566 hours, Block B is restored.
	#At 585, Block B fails and puts a request to activate Block C. However, Block C is down for repair at this time. The state upon repair of Block C ~~is overridden~~ (~~default~~ OFF)~~, thus~~ when it gets ~~repair~~ at 625, it is ON ~~upon repair~~.		#At 585 hours, Block B fails and puts a request to activate Block C. However, Block C is down for repair at this time. The state upon repair of Block C (Default OFF unless SCT overriddent) is overridden. Thus when it gets repaired at 625 hours, it is ON.
	#At 631, Block B is restored and deactivates Block C.		#At 631 hours, Block B is restored and deactivates Block C.
	#At 630, Block A1 is restored and activates Block A2.		#At 630 hours, Block A1 is restored and activates Block A2.
	#At 647, Block A2 fails.		#At 647 hours, Block A2 fails.
	#At 670, Block B fails and activates Block C.		#At 670 hours, Block B fails and activates Block C.
	#At 700, Block A1 fails~~, puts~~ a request to deactivate Block A2. Block A2 is down for repair at this time, and furthermore, the default setting of state for Block A2 upon repair is OFF. Thus when Block A2 gets ~~repair~~ at 740, it is OFF.		#At 700 hours, Block A1 fails and makes a request to deactivate Block A2. Block A2 is down for repair at this time, and furthermore, the default setting of state for Block A2 upon repair is OFF. Thus when Block A2 gets repaired at 740 hours, it is OFF.
	#At 770, Block A1 is restored and activates Block A2.		#At 770 hours, Block A1 is restored and activates Block A2.
	#At 780, Block C ~~gets repairs~~. According to setting, it is OFF upon repair.		#At 780 hours, Block C is restored. According to setting, it is OFF upon repair.
	#At 802, Block A2 fails		#At 802 hours, Block A2 fails

	[[Image:Block up down plot for default OFF unless SCT overridden example.png\|thumb\|center\|500px]]		[[Image:Block up down plot for default OFF unless SCT overridden example.png\|thumb\|center\|500px]]

← Older revision		Revision as of 06:37, 2 August 2012
Line 33:		Line 33:
	#At 71 hours, Block A2 fails.<br>		#At 71 hours, Block A2 fails.<br>
	#At 214 hours, Block B is restored. It fails again at 254 hours and activates Block C at that point.<br>		#At 214 hours, Block B is restored. It fails again at 254 hours and activates Block C at that point.<br>
	#At 276 hours, Block A1 fails, ~~puts~~ a request to deactivate Block A2. However, Block A2 is down for repair at this time. Nothing happens.<br>		#At 276 hours, Block A1 fails, and makes a request to deactivate Block A2. However, Block A2 is down for repair at this time. Nothing happens.<br>
	#At 363 hours, Block B is restored, deactivating Block C.		#At 363 hours, Block B is restored, deactivating Block C.
	#At 376 hours, Block A1 is restored, and ~~puts~~ a request to activate Block A2. However, Block A2 is down for repair at this time. The state upon repair of Block A2 (Default OFF unless SCT overridden) is overridden. Thus when it gets repaired at 432 hours, it is ON. <br>		#At 376 hours, Block A1 is restored, and makes a request to activate Block A2. However, Block A2 is down for repair at this time. The state upon repair of Block A2 (Default OFF unless SCT overridden) is overridden. Thus when it gets repaired at 432 hours, it is ON. <br>
	#At 404 hours, Block B fails and activates Block C.		#At 404 hours, Block B fails and activates Block C.
	#At 461 hours, Block A1 fails and deactivates Block A2.		#At 461 hours, Block A1 fails and deactivates Block A2.
	#At 483 hours, Block C fails.		#At 483 hours, Block C fails.
	#At 566 hours, Block B is restored.		#At 566 hours, Block B is restored.
	#At 585 hours, Block B fails and ~~puts~~ a request to activate Block C. However, Block C is down for repair at this time. The state upon repair of Block C (Default OFF unless SCT ~~overriddent~~) is overridden. Thus when it gets repaired at 625 hours, it is ON.		#At 585 hours, Block B fails and makes a request to activate Block C. However, Block C is down for repair at this time. The state upon repair of Block C (Default OFF unless SCT overridden) is overridden. Thus when it gets repaired at 625 hours, it is ON.
			#At 630 hours, Block A1 is restored and activates Block A2.
	#At 631 hours, Block B is restored and deactivates Block C.		#At 631 hours, Block B is restored and deactivates Block C.
	~~#At 630 hours, Block A1 is restored and activates Block A2.~~
	#At 647 hours, Block A2 fails.		#At 647 hours, Block A2 fails.
	#At 670 hours, Block B fails and activates Block C.		#At 670 hours, Block B fails and activates Block C.