Backout (BO) Triggers

BO Triggers are the mechanism in ICEFLO that enable and disable Backout Stages participation.

A pre-requisite to adding BO Triggers is that both an Implementation and a Backout Plan exists with one or more tasks in each.

Please note that all Tasks in the Implementation phase are always participating.

The screen below shows you the default settings in the Implementation phase in run mode.  There are no BO Triggers set.

Backout Plan Stage Participation

If you wish to use BO Triggers then you should carefully consider the participation settings of all Backout Stages (i.e. before the Implementation has commenced, should the Backout stages form part of the Backout plan).  Very often when using BO Triggers, the initial setting is all Backout stages have their participation set to Off.  To do this navigate to screen 410, the Edit screen.

Click into the Participation and change the Participation from Yes to No.

Implementation Plan BO Trigger Task(s)

Select the Task from the Implementation Plan which you would like to Trigger the participation setting for one or more Backout Stages.

Updating BO Triggers

Select which Backout Stages you wish to become available once you activate the trigger task.

An action processed bar will appear highlighting the changes that have been made.  In Edit mode you will see that BO Trigger icon has changed.  This will be the same icon in Run mode.

Toggling back to run mode, your Backout Worse Case (BW) will show the complete suite of tasks (irrespective of their participation setting).  Note here that both stages 1 and 2 are not participating.

Stage 2 however does have a BO Trigger on it (as outlined above) so that when task 1.3 is activated, it's participation should toggle to Y.

Task 1.3 has now been activated, and Stage 2 is now participating.

Activate Backout

To Backout your STP and invoke the stage which is participating click Backout from the STP Summary panel.  You will be asked to raise an Issue for this.

Once the backout has been activated you will note that the backout tasks (the stage you selected for participation) will become available for activation and that status of the STP changes to Backing Out.

The Backout Worse Case (BW) will show all stages, participating or not.

Back Out Now 'v' Back Out Worse Case

The introduction of Stage participation configuration either directly by the user OR via BO Triggers means there is an increased likelihood that the Back Out Now plan will vary from the Back Out Worst Case plan.

Please note:

Back Out Now reflects the size and shape of the back out plan were we to invoke the Back Out button NOW (i.e from current System Time).

Back Out Worst Case reflects the invocation of the all-inclusive Back Out plan (i.e. every task in the Back Out plan participating).  Furthermore it assumes this Back Out invocation to commence at the very end of the Implementation plan (so it’s monitoring the scenario of getting to the very end of the Implementation and then realising there is a problem and thus having to back out everything).

The latter is the key metric  ICEFLO monitors to ensure we always have our eye on the worst case  scenario thus can confidently notify ICEFLO users well in advance of any potential service breach.

The BO Now and BO Worst Case values are endemic in the new ICEFLO solution and both values are constantly monitored and recalculated.