A Task is deemed to be on the Critical Path of a Runbook if it has a direct impact on the Forecast End time of the Runbook. Any delays to tasks on the critical path will impact the end time of the Runbook.  The critical path is a dynamic aspect of the Runbook and  subject to continual change if Tasks are delayed, finished early etc.   ICEFLO will dynamically represent this ever shifting Critical Path model during execution and present this both visually  via the In Flight Tasks panel and as a filterable column in the task listing. 

The Critical Path is represented in a number of ways.

The first being on the Runbook List Tasks screen. The Column CP denotes if a Task falls on the Runbook Critical Path. If this column is populated with a Y, then the task is deemed to be on the Critical Path

It is also visualised on the Tasks Details, this is accessed by clicking into the task title.

The Blue Icon denotes that the task forms part of the Runbook Critical Path.

The Green Icon denotes that the task forms part of the Event Critial Path.

Any delays to the task in the example above will have an impact on the Forecast End Time of the Runbook and the Event which it is part of.

The Inflight Update Panel will also highlight and Late Critical Path Tasks and Critical Path Tasks. Clicking onto either one of the doughnuts above will return a filtered list of tasks below.