Você está na página 1de 2

ANALYSES

Delay Event 1

Despite being documented as a Non-excusable, Non-compensable Delay event, this was not
deemed an actual delay. It applied to a critical task, however this critical task was actually
completed ahead of schedule. As such, this activity is not a delay event.

Delay Event 2

Despite being documented as a Non-excusable, Non-compensable Delay event, this was not
deemed an actual delay. It applied to a critical task, however, due to time saved on other
tasks, this event did not result in a delay to the As-planned completion date. As such, this
activity is not a delay event.

Delay event 3

Removal of this activity results in a completion date of 10 Jun 2015. Inclusion of this 10-day
event results in a completion date of 17 Jun 2015. The original completion date is 12 June
2015. This event, therefore, carries the project 5 days beyond the original completion date.

This is an Excusable, Compensable Delay of 5 days.

Uncertainties

Who owns float in a program?

If, for example, I have a baseline of ten days to do a job. After 5 days time, I have one more
day of work left, then I’m delayed by the Employer for 3 days. I actually finish on the 9th
day, was there a delay for which I can claim compensation?

Alternatively, was there a disruption for which I can claim compensation?

Is it that the Employer can be said to own float as much as the Contractor i.e. if there are
unforeseen circumstances that cause setbacks to non-critical tasks, the Employer is not held
to account because of the float.

Seeing the completed excel table as you expected it to be prepared would be very helpful as I
don't think I was using it properly. Columns I to N are supposed to be filled based on
information taken from P6, yet the existing cells contained formulae.. so I wasn't clear on
what was supposed to happen there.

Feedback will be appreciated.

Você também pode gostar