Template:Standby with Delay (SCT Solution) - Revision history

Lisa Hacker: /* Standby with Delay(SCT Solution) */

2012-07-31T09:23:11Z

Standby with Delay(SCT Solution)

← Older revision		Revision as of 09:23, 31 July 2012
Line 1:		Line 1:
	~~===Standby with Delay(SCT Solution) ===~~		#REDIRECT [[Example_Using_SCT_to_Analyze_Standby_with_Delay]]

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

	~~The purpose of this example is to illustrate how to model standby with delay using SCT.~~

	~~==== Description ====~~

	~~Three devices A, B and C are in parallel. 2 out of 3 are required to perform the task. Initially A and B are working and C is in standby status. If A or B fails, C will replace~~
	the failed one with some delay. After the failed device is restored, it will become a standby device. For example, if A fails, with 10 hours delay C will become active and replace A. After A is restored, it will become a standby device for B and C.

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

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

	~~[[Image:SCT_with_delay_system.png\|center\|350px]]~~

	In order to model the delay, three extra blocks AA, BB and CC are added to the diagram. Each of them fails every 10 hours (normal distribution with mean 10 hours and standard deviation 0.0000001 hours). They operate even if the system is down and repair durations for them are 0 (immediate repair). Block AA(BB/CC) belongs to maintenance group AA(BB/CC). They all have state change triggers. The initial state for each is OFF and the state upon repair is "Always OFF." If Block A (B/C) goes down, then activate Block AA (BB/CC).

	Block A fails every 100 hours. It belongs to maintenance group A. It has state change triggers. The initial state is ON; the state upon repair is "Default OFF unless SCT overridden." If Block BB or Block CC goes down, Block A is activated.

	Block B fails every 200 hours. It belongs to maintenance group B. It has state change triggers. The initial state is ON; the state upon repair is "Default OFF unless SCT overridden." If Block AA or Block CC goes down, Block B is activated.

	Block C fails every 300 hours. It belongs to maintenance group C. It has state change triggers. The initial state is OFF; the state upon repair is "Default OFF unless SCT overridden." If Block BB or Block AA goes down, Block C is activated.

	~~The repair duration for Blocks A, B and C is 30 hours.~~

	~~====  Block Up/Down plot ====~~

	~~The system event log is shown in the figure below and is as follows:~~

	~~#At 100 hours, Block A fails and activates Block AA.~~
	~~#At 110 hours, Block AA fails and activates Block C.~~
	~~#At 230 hours, Block B fails and activates Block BB.~~
	~~#At 240 hours, Block BB fails and activates Block A.~~
	#~~At 340 hours, Block A fails and activates Block AA.~~
	~~#At 350 hours, Block AA fails and activates Block B.~~
	~~#...~~

	~~<br> [[Image:SCT with delay Up Down plot.png\|center\|400px]]~~

	[[~~Category:BlockSim_Examples~~]]

Richard House: /* BlockSim Solution */

2012-07-31T08:19:29Z

BlockSim Solution

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

	[[Image:SCT_with_delay_system.png\|center\|~~250px~~]]		[[Image:SCT_with_delay_system.png\|center\|350px]]

	In order to model the delay, three extra blocks AA, BB and CC are added to the diagram. Each of them fails every 10 hours (normal distribution with mean 10 hours and standard deviation 0.0000001 hours). They operate even if the system is down and repair durations for them are 0 (immediate repair). Block AA(BB/CC) belongs to maintenance group AA(BB/CC). They all have state change triggers. The initial state for each is OFF and the state upon repair is "Always OFF." If Block A (B/C) goes down, then activate Block AA (BB/CC).		In order to model the delay, three extra blocks AA, BB and CC are added to the diagram. Each of them fails every 10 hours (normal distribution with mean 10 hours and standard deviation 0.0000001 hours). They operate even if the system is down and repair durations for them are 0 (immediate repair). Block AA(BB/CC) belongs to maintenance group AA(BB/CC). They all have state change triggers. The initial state for each is OFF and the state upon repair is "Always OFF." If Block A (B/C) goes down, then activate Block AA (BB/CC).

Melinda Caroline: /* Block Up/Down plot */

2012-06-15T13:04:57Z

Block Up/Down plot

← Older revision		Revision as of 13:04, 15 June 2012
Line 38:		Line 38:
	#...		#...

	<br> [[Image:SCT with delay Up Down plot.png\|center\|~~250px~~]]		<br> [[Image:SCT with delay Up Down plot.png\|center\|400px]]

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

Chuck Smith: /* Standby with Delay(SCT Solution) */

2012-04-25T20:53:57Z

Standby with Delay(SCT Solution)

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

	[[Image:SCT_with_delay_system.png\|center\|~~500px~~]]		[[Image:SCT_with_delay_system.png\|center\|250px]]

	In order to model the delay, three extra blocks AA, BB and CC are added to the diagram. Each of them fails every 10 hours (normal distribution with mean 10 hours and standard deviation 0.0000001 hours). They operate even if the system is down and repair durations for them are 0 (immediate repair). Block AA(BB/CC) belongs to maintenance group AA(BB/CC). They all have state change triggers. The initial state for each is OFF and the state upon repair is "Always OFF." If Block A (B/C) goes down, then activate Block AA (BB/CC).		In order to model the delay, three extra blocks AA, BB and CC are added to the diagram. Each of them fails every 10 hours (normal distribution with mean 10 hours and standard deviation 0.0000001 hours). They operate even if the system is down and repair durations for them are 0 (immediate repair). Block AA(BB/CC) belongs to maintenance group AA(BB/CC). They all have state change triggers. The initial state for each is OFF and the state upon repair is "Always OFF." If Block A (B/C) goes down, then activate Block AA (BB/CC).
Line 38:		Line 38:
	#...		#...

	<br> [[Image:SCT with delay Up Down plot.png\|center\|~~500px~~]]		<br> [[Image:SCT with delay Up Down plot.png\|center\|250px]]

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

Chuck Smith: /* Block Up/Down plot */

2012-04-02T15:54:08Z

Block Up/Down plot

← Older revision		Revision as of 15:54, 2 April 2012
Line 38:		Line 38:
	#...		#...

	<br> [[Image:SCT with delay Up Down plot.png~~\|thumb~~\|center\|500px]]		<br> [[Image:SCT with delay Up Down plot.png\|center\|500px]]

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

Nikki Helms: /* BlockSim Solution */

2012-03-30T18:06:21Z

BlockSim Solution

← Older revision		Revision as of 18:06, 30 March 2012
Line 14:		Line 14:
	The BlockSim modeling of this system is shown in the figure below.		The BlockSim modeling of this system is shown in the figure below.

	[[Image:SCT_with_delay_system.png~~\|thumb~~\|center\|500px]]		[[Image:SCT_with_delay_system.png\|center\|500px]]

	In order to model the delay, three extra blocks AA, BB and CC are added to the diagram. Each of them fails every 10 hours (normal distribution with mean 10 hours and standard deviation 0.0000001 hours). They operate even if the system is down and repair durations for them are 0 (immediate repair). Block AA(BB/CC) belongs to maintenance group AA(BB/CC). They all have state change triggers. The initial state for each is OFF and the state upon repair is "Always OFF." If Block A (B/C) goes down, then activate Block AA (BB/CC).		In order to model the delay, three extra blocks AA, BB and CC are added to the diagram. Each of them fails every 10 hours (normal distribution with mean 10 hours and standard deviation 0.0000001 hours). They operate even if the system is down and repair durations for them are 0 (immediate repair). Block AA(BB/CC) belongs to maintenance group AA(BB/CC). They all have state change triggers. The initial state for each is OFF and the state upon repair is "Always OFF." If Block A (B/C) goes down, then activate Block AA (BB/CC).

Melinda Caroline: /* BlockSim Solution */

2012-03-08T23:12:33Z

BlockSim Solution

← Older revision		Revision as of 23:12, 8 March 2012
Line 16:		Line 16:
	[[Image:SCT_with_delay_system.png\|thumb\|center\|500px]]		[[Image:SCT_with_delay_system.png\|thumb\|center\|500px]]

	In order to model the delay, three extra blocks AA, BB and CC are added to the diagram. Each of them fails every 10 hours (~~Normal~~ distribution with mean 10 hours and standard deviation 0.0000001 hours). They operate even if the system is down and repair durations for them are 0 (immediate repair). Block AA(BB/CC) belongs to maintenance group AA(BB/CC). They all have state change triggers. The initial state for each is OFF and the state upon repair is "Always OFF." If Block A (B/C) goes down, then activate Block AA (BB/CC).		In order to model the delay, three extra blocks AA, BB and CC are added to the diagram. Each of them fails every 10 hours (normal distribution with mean 10 hours and standard deviation 0.0000001 hours). They operate even if the system is down and repair durations for them are 0 (immediate repair). Block AA(BB/CC) belongs to maintenance group AA(BB/CC). They all have state change triggers. The initial state for each is OFF and the state upon repair is "Always OFF." If Block A (B/C) goes down, then activate Block AA (BB/CC).

	Block A fails every 100 hours. It belongs to maintenance group A. It has state change triggers. The initial state is ON; the state upon repair is "Default OFF unless SCT overridden." If Block BB or Block CC goes down, Block A is activated.		Block A fails every 100 hours. It belongs to maintenance group A. It has state change triggers. The initial state is ON; the state upon repair is "Default OFF unless SCT overridden." If Block BB or Block CC goes down, Block A is activated.

Melinda Caroline: /* Block Up/Down plot */

2012-03-08T23:05:26Z

Block Up/Down plot

← Older revision		Revision as of 23:05, 8 March 2012
Line 28:		Line 28:
	====  Block Up/Down plot ====		====  Block Up/Down plot ====

	The system event log is shown in ~~Figure~~ below and is as follows:		The system event log is shown in the figure below and is as follows:

	#At 100, Block A fails, and activates Block AA.		#At 100 hours, Block A fails and activates Block AA.
	#At 110, Block AA fails, and activates Block C.		#At 110 hours, Block AA fails and activates Block C.
	#At 230, Block B fails, and activates Block BB.		#At 230 hours, Block B fails and activates Block BB.
	#At 240, Block BB fails, and activates Block A.		#At 240 hours, Block BB fails and activates Block A.
	#At 340, Block A fails, and activates Block AA.		#At 340 hours, Block A fails and activates Block AA.
	#At 350, Block AA fails, and activates Block B.		#At 350 hours, Block AA fails and activates Block B.
	#...		#...

Melinda Caroline: /* BlockSim Solution */

2012-03-08T23:04:37Z

BlockSim Solution

← Older revision		Revision as of 23:04, 8 March 2012
Line 12:		Line 12:
	==== BlockSim Solution ====		==== BlockSim Solution ====

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

	[[Image:SCT_with_delay_system.png\|thumb\|center\|500px]]		[[Image:SCT_with_delay_system.png\|thumb\|center\|500px]]

	In order to model the delay, three extra blocks AA, BB and CC are added to the diagram. Each of them fails every 10 hours (Normal distribution with mean 10 hours and standard deviation 0.0000001 hours). They operate even if system is down and repair durations for them are 0 (immediate repair). Block AA(BB/CC) ~~is belong~~ to maintenance group AA(BB/CC). They all have state change triggers. The initial state is OFF and the state upon repair is Always OFF. If Block A (B/C) goes down, then activate Block AA (BB/CC).		In order to model the delay, three extra blocks AA, BB and CC are added to the diagram. Each of them fails every 10 hours (Normal distribution with mean 10 hours and standard deviation 0.0000001 hours). They operate even if the system is down and repair durations for them are 0 (immediate repair). Block AA(BB/CC) belongs to maintenance group AA(BB/CC). They all have state change triggers. The initial state for each is OFF and the state upon repair is "Always OFF." If Block A (B/C) goes down, then activate Block AA (BB/CC).

	Block A fails every 100 hours. It belongs to maintenance group A. It has state change triggers. The initial state is ON; the state upon repair is Default OFF unless SCT overridden. If Block BB or Block CC goes down, Block A is activated.		Block A fails every 100 hours. It belongs to maintenance group A. It has state change triggers. The initial state is ON; the state upon repair is "Default OFF unless SCT overridden." If Block BB or Block CC goes down, Block A is activated.

	Block B fails every 200 hours. It belongs to maintenance group B. It has state change triggers. The initial state is ON; the state upon repair is Default OFF unless SCT overridden. If Block AA or Block CC goes down, Block B is activated.		Block B fails every 200 hours. It belongs to maintenance group B. It has state change triggers. The initial state is ON; the state upon repair is "Default OFF unless SCT overridden." If Block AA or Block CC goes down, Block B is activated.

	Block C fails every 300 hours. It belongs to maintenance group C. It has state change triggers. The initial state is OFF; the state upon repair is Default OFF unless SCT overridden. If Block BB or Block AA goes down, Block C is activated.		Block C fails every 300 hours. It belongs to maintenance group C. It has state change triggers. The initial state is OFF; the state upon repair is "Default OFF unless SCT overridden." If Block BB or Block AA goes down, Block C is activated.

	The repair duration for ~~Block~~ A, B and C is 30 hours.		The repair duration for Blocks A, B and C is 30 hours.

	====  Block Up/Down plot ====		====  Block Up/Down plot ====

Melinda Caroline: /* Description */

2012-03-08T22:57:35Z

Description

← Older revision		Revision as of 22:57, 8 March 2012
Line 7:		Line 7:
	==== Description ====		==== Description ====

	Three devices A, B and C are in parallel. 2 out of 3 are required to perform the task. Initially A and B are working, C is in standby status. If A or B fails, C will replace		Three devices A, B and C are in parallel. 2 out of 3 are required to perform the task. Initially A and B are working and C is in standby status. If A or B fails, C will replace
	the failed one with some delay. After the failed device is restored, it will become a standby device. For example, If A fails, with 10 hours delay C will become active and replace A. After A is restored, it will become a standby device for B and C.		the failed one with some delay. After the failed device is restored, it will become a standby device. For example, if A fails, with 10 hours delay C will become active and replace A. After A is restored, it will become a standby device for B and C.

	==== BlockSim Solution ====		==== BlockSim Solution ====