Delay Navigator
Why was a particular activity delayed to finish? You can now significantly accelerate the tedious workflow required to answer this question in multi-thousand activity schedules.
How does Delay Analysis 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).
Understand which activities show in the canvas
Activities that meet the criteria listed below are displayed in the delay analysis canvas as cards.
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.
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
Deciding the contribution on your 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, we also offer you the raw data in Dates mode for the experts to decide themselves.
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%.
Highlighting the 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.
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