Task Start Times are derived from a number of factors. ICEFLO uses a system called Current System Time, meaning that no Task can be set to start before the present (ie Now).

Current System Time is always factored into the calculation of a Task's anticipated Start time ( a Task's forecast Start Time). Other influences on a Task's forecast Start Time are:

• The logging of an Explicit Start Time (which manifests itself as a Start no Earlier Than the Explicit Start Time)
• The End Times of all the Task's predecessor Tasks
• Dependencies

Pre-Implementation Phase Tasks

For a newly created Runbook, the first Pre-Implementation Phase Task (and any Pre-Imp Tasks without Pedecessors) will have a Start Time of the present. The only exception to this general rule is where the Pre-Imp Phase Task has been given a future Explicit Start Time or the Pre-Imp Phase Task has a dependency on a Task in another Runbook.

Implementation Phase Tasks

The Start Time of the first Task of the Implementation Phase or any tasks which do not have a predecessor will have a Start Time of the Change Window Start or the Time of the Explicit Start time if one has been applied. If either of these have been exceeded then the Start Time of the Task will be the same as Current System Time.

Planned times will be superseded by system time when any predecessors tasks have not been completed.  

Post-Implementation Phase Tasks

The Start Time of the Post-Implementation Phase will be set for the forecast End Time of the last Task in the Implementation Phase (and can not be set earlier). This general rule applies unless the Post Implementation Phase Task has been given a future Explicit Start Time, or the Post- Imp Phase Task has a dependency on a Task in another Runbook, which will dictate, or the Start Time of the Task.