BlockSim Example: Default ON unless SCT Overridden - Revision history

Lisa Hacker at 21:03, 18 September 2023

2023-09-18T21:03:14Z

← Older revision		Revision as of 21:03, 18 September 2023
Line 1:		Line 1:
	<noinclude>{{Banner BlockSim Examples}}		<noinclude>{{Banner BlockSim Examples}}
	</noinclude>		</noinclude>
	The examples illustrate, for BlockSim's [[State Change Triggers]], how selecting the '''Default ON unless SCT overridden''' option in the '''State upon repair''' field affects simulation. Two cases are presented.		The examples illustrate, for BlockSim's State Change Triggers, how selecting the '''Default ON unless SCT overridden''' option in the '''State upon repair''' field affects simulation. Two cases are presented.

	=== Example 1 ===		=== Example 1 ===

Cruz Daniel: /* Example 1 */

2021-03-26T18:19:45Z

Example 1

← Older revision		Revision as of 18:19, 26 March 2021
Line 33:		Line 33:
	#At 694 hours, Block P fails and activates Block S.		#At 694 hours, Block P fails and activates Block S.
	#At 702 hours, Block S fails and the repair is finished at 775 hours. According to the block's settings, it is ON upon repair.		#At 702 hours, Block S fails and the repair is finished at 775 hours. According to the block's settings, it is ON upon repair.
	#At 788 hours, Block P ~~fails~~ and ~~activates~~ Block S.		#At 788 hours, Block P is restored and deactivates Block S.
	#At 845 hours, Block P ~~is restored~~ and ~~deactivates~~ Block S.		#At 845 hours, Block P fails and activates Block S.

	[[Image:Block up down plot for primary and standby example.png\|center\|600px]]		[[Image:Block up down plot for primary and standby example.png\|center\|600px]]

Richard House at 07:25, 7 August 2012

2012-08-07T07:25:57Z

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

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

	Consider the system shown in the figure below:		Consider the system shown in the figure below:
Line 23:		Line 21:
	*Both Block P and Block S are as good as new after repair.		*Both Block P and Block S are as good as new after repair.

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

	The system event log is shown in the figure below and explained next.		The system event log is shown in the figure below and explained next.
Line 50:		Line 46:
	#Activate a block if any item from these associated maintenance group(s) is restored		#Activate a block if any item from these associated maintenance group(s) is restored

	~~<br>~~
	'''BlockSim Solution'''		'''BlockSim Solution'''
	~~<br>~~
	Consider the system is shown in the figure below.		Consider the system is shown in the figure below.

Line 63:		Line 58:
	[[Image:One way dependence.png\|center\|500px]]		[[Image:One way dependence.png\|center\|500px]]

	~~<br>~~
	'''Block Up/Down Plot'''		'''Block Up/Down Plot'''
	~~<br>~~
	The system event log, for a duration of 1,200 hours, is shown in the figure below and explained next		The system event log, for a duration of 1,200 hours, is shown in the figure below and explained next

Richard House at 07:28, 6 August 2012

2012-08-06T07:28:33Z

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

	[[Image:Primary and Standby.png~~\|thumb~~\|center\|500px]]		[[Image:Primary and Standby.png\|center\|500px]]

	*Block P is the primary device. It belongs to maintenance group P.		*Block P is the primary device. It belongs to maintenance group P.
Line 40:		Line 40:
	#At 845 hours, Block P is restored and deactivates Block S.		#At 845 hours, Block P is restored and deactivates Block S.

	[[Image:Block up down plot for primary and standby example.png~~\|thumb~~\|center\|600px]]		[[Image:Block up down plot for primary and standby example.png\|center\|600px]]

	=== Example 2 ===		=== Example 2 ===
Line 61:		Line 61:
	*Blocks A, C and D all are as good as new after repair.		*Blocks A, C and D all are as good as new after repair.

	[[Image:One way dependence.png~~\|thumb~~\|center\|500px]]		[[Image:One way dependence.png\|center\|500px]]

	<br>		<br>
Line 77:		Line 77:
	#From 910 hours to 1060 hours, Block D fails and is repaired. There is no trigger in this period, so it is ON upon repair.		#From 910 hours to 1060 hours, Block D fails and is repaired. There is no trigger in this period, so it is ON upon repair.

	[[Image:Block up down plot for one way dependence example.png~~\|thumb~~\|center\|600px]]<br>		[[Image:Block up down plot for one way dependence example.png\|center\|600px]]<br>

Richard House: /* Example 2 */

2012-08-02T06:58:50Z

Example 2

← Older revision		Revision as of 06:58, 2 August 2012
Line 69:		Line 69:

	#At 300 hours and at 330 hours, Blocks C and D fail respectively. <br>		#At 300 hours and at 330 hours, Blocks C and D fail respectively. <br>
	#At 350 hours, Block A fails. This brings system down, turns Block B OFF and also puts a request to turn Block C OFF. However, Block C is down for repair at this time, thus after the repair on Block C is finished, the default setting of Block C (default ON unless overridden) will be overridden and it will stay OFF upon repair.		#At 350 hours, Block A fails. This brings the system down, turns Block B OFF and also puts a request to turn Block C OFF. However, Block C is down for repair at this time, thus after the repair on Block C is finished, the default setting of Block C (default ON unless overridden) will be overridden and it will stay OFF upon repair.
	#At 450 hours, Block A is restored, which activate Blocks B and C. Block D is still down for repair at this point, so nothing happens to Block D.		#At 450 hours, Block A is restored, which activate Blocks B and C. Block D is still down for repair at this point, so nothing happens to Block D.
	#At 480 hours, Block D is restored. According to its settings, D is ON upon repair.		#At 480 hours, Block D is restored. According to its settings, Block D is ON upon repair.
	#At 750 hours, Block C fails.		#At 750 hours, Block C fails.
	#At 800 hours, Block A fails, and deactivates Blocks B and D. ~~And it~~ also makes a request to turn Block C OFF. However, Block C is down for repair at this point, the state upon repair of Block C is overridden. Thus when repair on Block C is finished at 850 hours, it stays OFF.		#At 800 hours, Block A fails, and deactivates Blocks B and D. It also makes a request to turn Block C OFF. However, Block C is down for repair at this point, so the state upon repair of Block C is overridden. Thus when repair on Block C is finished at 850 hours, it stays OFF.
	#At 900 hours, Block A is restored, and activates Blocks B, C and D.		#At 900 hours, Block A is restored, and activates Blocks B, C and D.
	#From 910 hours to 1060 hours, Block D fails and is repaired. There is no trigger in this period, so it is ON upon repair.		#From 910 hours to 1060 hours, Block D fails and is repaired. There is no trigger in this period, so it is ON upon repair.

	[[Image:Block up down plot for one way dependence example.png\|thumb\|center\|600px]]<br>		[[Image:Block up down plot for one way dependence example.png\|thumb\|center\|600px]]<br>

Richard House: /* Example 2 */

2012-08-02T06:53:39Z

Example 2

← Older revision		Revision as of 06:53, 2 August 2012
Line 58:		Line 58:
	*Block B cannot fail. It has state change triggers. The initial state is ON, and the state upon trigger is "Default On unless SCT overridden." If any item from maintenance group A goes down, this block is deactivated; if any item from maintenance group A is restored, this block is activated.		*Block B cannot fail. It has state change triggers. The initial state is ON, and the state upon trigger is "Default On unless SCT overridden." If any item from maintenance group A goes down, this block is deactivated; if any item from maintenance group A is restored, this block is activated.
	*Block C fails every 300 hours and the duration for the repair action is 100 hours. It is has state change triggers. The initial state is ON, and the state upon trigger is "Default On unless SCT overridden." If any item from maintenance group A goes down, this block is deactivated; if any item from maintenance group A is restored, this block is activated.		*Block C fails every 300 hours and the duration for the repair action is 100 hours. It is has state change triggers. The initial state is ON, and the state upon trigger is "Default On unless SCT overridden." If any item from maintenance group A goes down, this block is deactivated; if any item from maintenance group A is restored, this block is activated.
	*Block D fails every 330 hours and the duration for repair action is 150 hours . It has state change triggers. The initial state is ON, and the state upon trigger is "Default On unless SCT overridden". If any item from maintenance group A goes down, this block is deactivated; if any item from maintenance group A is restored, this block is activated.		*Block D fails every 330 hours and the duration for repair action is 150 hours . It has state change triggers. The initial state is ON, and the state upon trigger is "Default On unless SCT overridden." If any item from maintenance group A goes down, this block is deactivated; if any item from maintenance group A is restored, this block is activated.
	*Blocks A, C and D all are as good as new after repair.		*Blocks A, C and D all are as good as new after repair.

Richard House: /* Example 2 */

2012-08-02T06:53:11Z

Example 2

← Older revision		Revision as of 06:53, 2 August 2012
Line 53:		Line 53:
	'''BlockSim Solution'''		'''BlockSim Solution'''
	<br>		<br>
	Consider a system is shown in the figure below.		Consider the system is shown in the figure below.

	*Block A fails every 350 hours and the duration for the repair action is 100 hours. It belongs to maintenance group A.		*Block A fails every 350 hours and the duration for the repair action is 100 hours. It belongs to maintenance group A.

Richard House: /* Example 1 */

2012-08-02T06:53:00Z

Example 1

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

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

	[[Image:Primary and Standby.png\|thumb\|center\|500px]]		[[Image:Primary and Standby.png\|thumb\|center\|500px]]

Richard House: /* Example 1 */

2012-08-02T06:51:17Z

Example 1

← Older revision		Revision as of 06:51, 2 August 2012
Line 19:		Line 19:

	*Block P is the primary device. It belongs to maintenance group P.		*Block P is the primary device. It belongs to maintenance group P.
	*Block S is the standby device. It has state change triggers. The initial state is OFF. If Block P goes down, then activate this block; if Block P is restored, then deactivate this block. The State Upon Repair is ~~“Default~~ ON unless SCT ~~Overridden”~~.		*Block S is the standby device. It has state change triggers. The initial state is OFF. If Block P goes down, then activate this block; if Block P is restored, then deactivate this block. The State Upon Repair is "Default ON unless SCT Overridden."
	*Both Block P and Block S have a Weibull distribution with Beta = 1.5 and Eta = 100 for reliability and repair action.		*Both Block P and Block S have a Weibull distribution with Beta = 1.5 and Eta = 100 for reliability and repair action.
	*Both Block P and Block S are as good as new after repair.		*Both Block P and Block S are as good as new after repair.
Line 30:		Line 30:

	#At 123 hours, Block P fails and activates Block S.		#At 123 hours, Block P fails and activates Block S.
	#At 186 hours ,Block S fails and is restored at 208 hours. According to the block's settings, it is ON upon repair.		#At 186 hours, Block S fails and is restored at 208 hours. According to the block's settings, it is ON upon repair.
	#At 223 hours, Block S fails again.		#At 223 hours, Block S fails again.
	#At 301 hours, Block P is restored, and put a request to deactivate Block S. However, Block S is down for repair at this point. The request overwrites the default state upon repair setting of Block S. Thus when Block S is done with repair at 385 hours, it is OFF.		#At 301 hours, Block P is restored, and put a request to deactivate Block S. However, Block S is down for repair at this point. The request overwrites the default state upon repair setting of Block S. Thus when Block S is done with repair at 385 hours, it is OFF.

Richard House: /* Example 2 */

2012-08-02T06:50:29Z

Example 2

← Older revision		Revision as of 06:50, 2 August 2012
Line 66:		Line 66:
	'''Block Up/Down Plot'''		'''Block Up/Down Plot'''
	<br>		<br>
			The system event log, for a duration of 1,200 hours, is shown in the figure below and explained next
	The system ~~behavior~~ for ~~simulation~~ of ~~1200~~ hours ~~durations~~ is shown in the figure below and explained next.

	#At 300 hours and at 330 hours, Blocks C and D fail respectively. <br>		#At 300 hours and at 330 hours, Blocks C and D fail respectively. <br>