Delay Navigator

Compare any schedule against a baseline and answer questions like: Why was an actualized activity delayed? Why is a future activity delayed? Accelerate the tedious workflow required to answer these questions in multi-thousand activity schedules.

Delay Navigator works by comparing your currently selected schedule and against the one you have specified as your baseline. It can be activated in order to investigate activities whose finish date has moved between those 2 schedule versions.

How does Delay Navigator work?

The tool inspects the specified activity and start going backwards predecessor by predecessor throughout the activity network. Required information and data are calculated whilst that backward pass takes place (ie the start delay of the activities, their possible timespan increase, how much delay they are transferring to their successors etc).

Which activities show up in the Delay Navigator canvas?

After the calculations have been made, activities with Delay Contribution equal or greater than 1% show up in the canvas. The criteria that activities need to meet in order to get Delay Contribution assigned to them are as follows:

Float = 0 in Selected Schedule
OR
Float = 0 in Baseline Schedule
OR
Transmitted Delay > 0 in Selected Schedule
AND
Working days Increase or Non-working days Increase or Non Inherited Start delay > 0
AND
Following relationship = FF OR FS

 

Activities that exist within the illustrated delay attribution network but do not satisfy the following criteria can be found by opening the intermediate paths pop up. When intermediate activities exist between 2 cards in the canvas, the connection line illustrates that by having 3 dots. The lines with 3 dots can be clicked which will result in a pop up showcasing the path with the least amount of float between those 2 cards.

 

How does the delay contribution assignment happen?

An activity gets assigned delay contribution when it transmits delay in addition to it having either a duration increase, non-inherited start delay or both. The delay contribution that that an activity gets is analogous with the proportion of the delay it transmits to its successor/s compared to other activities that also transmit delay to those successor/s. After all calculations are complete, the contribution of all the activities is normalised to add up to 100%.

I want to decide the Delay Contribution on my own!

Our own algorithm created by our scientists reads the data and calculates delay contribution for each activity in Contribution Mode. However, since there are a lot of intricacies in legal frameworks across countries, companies and legal contracts, we are also offering a Dates mode showcasing all available data, for the experts to decide themselves.  You can switch into that mode by selecting "Check Dates" at the top right

Highlighting Activity Codes

You can also filter the activities in the graph based on their Activity codes to see which of your suppliers, activities, or contractors have the most delay contributions.

 

Cases where the Delay Navigator will not run

  1. Having a single file uploaded in your project.
  2. Having no baseline set.
  3. Having the baseline as the currently selected schedule.
  4. Attempting to investigate an activity whose finish date has not been altered between the 2 schedules.
  5. Attempting to investigate an activity which is part of a network with cycles.

 

Understanding Delay Navigator better through examples

Scenario 1

Activity X has a Total Delay of 10 days (Finish Delay). This delay is affected by Activity A’s transmitted delay to Activity X and its own Timespan Change.

Scenario 2

Activity X has a Total Delay of 10 days (Finish Delay). This delay is affected by Activity A’s transmitted delay to Activity X and its own Timespan Change.

Glossary

Total Delay (Finish Delay)

Absolute days difference between planned finish and actual finish.

 Total delay = 10 days

 

Timespan

The timespan is the sum of Working and Non-working days.

 Timespan = 85 + 45

 

Working Days Change

Working days difference between planned and actual.
 

 Working days change = +50 days

 

Non Working Days Change

Non Working days difference between planned and actual e.g weekends and bank holidays.

 Non Working days change = +28 days

 

Start Delay

Absolute days difference between planned start and actual start.

 Start delay = 10 days

 

Transmitted Delay

How much of an activity’s delay is being leaked to the next activity, pushing its Start date (or Finish date if the relationship is Finish-Finish).

 Transmit. delay = 10 days

 Activity’s Actual Finish + Actual Lag - Successor’s Planned Start