Critical path

Dear Balu,



Start documenting all the delays caused by the other contractors. At the same time, you need to ask the other Contractors about their contracts and durations. Usually, what applies to them, will apply to you. It seems like a highly inter-related project. Many Contractors will finish at the same time.



Best Regards,



Samer

Hi Balu



Before we go any further we need to know a few details.



What type of project is it?



How many work sections are in your sub-contract programme?



How many sections are there in the project - do they have different completion dates?



What preceding Main Contractor activity needs to be complete before you are allowed in - what is the next activity after you finish?



Do you have exclusive access to your work zone or are other sub-contractors working in the same section as well?



What form of contract are you working under?



Best regards



Mike Testro

Hi Balu



Since both your threads are in the same subject I will leave them as thay are.



As I said in the other thread I do not think your programme for sub-contract cable pulling will have a critical path at sub-contract level.



It may have lots of sections which are stand alone critical.



Your best approach to your EOT is to use an As Pnned v As Built method.



Best regards



Mike Testro

Samer



Judging from Mike’s comments seems like somewhere a short circuit happened, and he took notice, anyway is good to hear from you, keep on debating and challenging, is my way of keeping in shape.



Best regards,

Rafael

Hi Balu



Has this thread got anything to do with your cable pulling query?



If so please keep all topics together.



Best regards



Mike Testro

Dear Rafael,



FIDIC clause 8.3 "Programme" states what the Programme should include only. It has no mention of the critical path or the analysis of the Programme.



With kind regards,



Samer

You should always look at both, the updates represents reality while the baseline represents your planning at some point in time, represents what reality should target, baseline is a sort of contractual commitment and cannot be overlooked.



At times a change in baseline schedule is in order, it has legal implications but it is not an absolute due to the dynamic nature of schedules.



Regarding Delay Analysis I would like to add that just looking at the Contractual Baseline ignores the as-built history of the project; it produces theoretical results; it does not measure the effect of delay on actual performance; and it assumes that the as-planned schedule does not change. Contemporaneous methods such as TIA are preferred when performed in due time. At times forensic methods are in order; TIA like the Contractual Baseline is not an absolute. In all cases baseline is still relevant.



Slippage is also relevant as it shows a trend, of major concern always, especially if between updates listing of Critical Path activities changes. This is an essential part of your critical path analysis.



All these are issues that should be spelled out in the narrative to be included with your updates. You should compare actual versus baseline and include your comments on why the difference, at times due to delay issues still pending to be resolved, at times due to non-compensable but excusable delays such as rain, hurricanes or maybe sand-storms. The same applies to slippage.



I am sure other comments will follow with regard to FIDIC requirements, at my location we use other standards, similar but not equal.

Balu,



Critical path is monitored on the updates:



1) Delay Analysis - between the approved baseline and current update (Target 1 vs. Current)



2) Slippage Analysis - between the last submitted update and the current update (Target X vs. Current)



Best regards,

Rommel