Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Time Impact Analysis

38 replies [Last post]
Siva Kumar
User offline. Last seen 5 years 12 weeks ago. Offline
Joined: 5 Jul 2005
Posts: 44
Groups: None
Hello everyone,.

Ths is related to Time Impact analysis,as i know this takes into account the progress update at the time of delay event..
1.If there is a delay because of self inefficieny,and if
above that the delay event is introduced..how can it
show the real impact of delay event???


Thanks and regards,
Shiva

Replies

Ali Osama
User offline. Last seen 4 years 2 weeks ago. Offline
Joined: 19 Dec 2017
Posts: 39
Groups: None
Christian lehnen
User offline. Last seen 17 years 35 weeks ago. Offline
Joined: 21 Jun 2006
Posts: 3
Groups: None
Hello All

I am a new kid on board.. and also new to the claims and delay analysis. I would appreciate any help in understanding the delay analysis techniques called time slice / window analysis.

Thanks and regards,

Christian Lehnen
Jawad Al-Nimri
User offline. Last seen 12 years 5 weeks ago. Offline
Joined: 7 Aug 2006
Posts: 39
Groups: None
sure,
but what is the problem with the traditional approach???
why should we searech for such approaches?
is this approach getting international recognition? not upto my knowladge at least.

shouldn’t we stick to legality of the method proved?

anyway, searching new approaches is always benifical, for sure.

Nice subject,

regards
Andrew Flowerdew
User offline. Last seen 2 years 23 weeks ago. Offline
Joined: 14 Dec 2004
Posts: 960
Groups: None
Jawad,

If the solution was simple, we’ed have all sorted it out along time ago!!!!!!!!!!
Jawad Al-Nimri
User offline. Last seen 12 years 5 weeks ago. Offline
Joined: 7 Aug 2006
Posts: 39
Groups: None
Okay, now I have the picture. Lets use shamail’s symbols.
What (I) believe is fair is as follows:
Firstly, the contract must be extended by X duration, as it was occurring no matter what happened by the Contractor. This has caused damages to the contractor the amount of Y.
The contractor’s performance caused Z delay and damages to the (Employer) of M

The contractor is liable to pay the amount of M1 = M – Y (X/Z)
The Employer is liable to pay the amount of Y1 = Y – M (Z/X)

Net payable to the contractor is Y1-M1
Net Payable to the Employer is – (Y1-M1)

As I told you before it is my first time to encounter such a principle, so maybe using the above formulas I based it on the costs, right, it is interesting. But it is also difficult to say that this delay caused Y damages by the Employer because of the wide spectrum of damages types, and you will not have the sufficient time to make all the cost analysis each time a concurrency occured.

actually, i can not decide if this is a correct principle
Andrew Flowerdew
User offline. Last seen 2 years 23 weeks ago. Offline
Joined: 14 Dec 2004
Posts: 960
Groups: None
Jawad,

The way I read the voting question is that it asking you how YOU think the liability when two competing Contractor/Employer delays occur at the same time, should be allocated - NOT how TIA, the contract or the law says it should.

Apportionment of liability is used in Canada and has been followed in a couple of cases in Austrailia.
Jawad Al-Nimri
User offline. Last seen 12 years 5 weeks ago. Offline
Joined: 7 Aug 2006
Posts: 39
Groups: None
Dear Shamail,

Actually, we are talking on the same wave length but with different perspectives, please help me here, I do not understand why you are keep linking the EOT to be determined at the Original Completion Date with the Event subsequent delays made by the Contractor???

From my perspective, making the final determination over EOT at the original completion date is only to obtain more confidence about the correctness of the analysis. The amount of EOT to be granted is to have a retroactive effect.
EG: To make it clearer; the project starts on 01-01-2006 and the original completion date is 01-01-2007, say on Jun 2006 the Contractor requested EOT and it is determined that he is entitled to 30 days, using the project updates and the final determination on 01-01-2007 it is found that the real effect is 24 days only. The new contract completion date is 25-1-07 so this date is applied with retroactive effect starting from Jun – 06,

My point is that the Subsequent delays after JUN-06 must be studied against the prevailing time for completion that should have been granted (i.e. 25-01-2007) not against the original completion date (01-01-07).
What I mean is simply that:
If it is found by using the TIA, that the contractor is entitled to an EOT the subsequent delays (by the contractor) will not affect the validity of his right, the same applies for the Employer (his delays after JUN will be studied against the new completion date, not the original).

I used this example as it will help demonstrating my answer to the voting question:

I came across this voting question, it is really strange, and it is my first time to hear about this proportional method. Things do not go this way, instead, each delay event will be analyzed against the prevailing contract completion date at the time of impaction. The result (the Cost Engineers name it as the Final Entitlement Schedule) will automatically be divided between parties. EOT that the contractor is entitled to, must be granted no matter what were the subsequent delays he made, and the actual completion date will be recorded, the difference will be the contractor caused delays.

The time related costs will be generated from this final entitlement schedule (taking concurrencies into consideration, where the contractor will be entitled only for EOT).


It is really hard to explain all the aspects of this analysis in this short space, but shamail I would be welling to forward you an article that will make your life easier, please give me your email.

Again, your question (the question of the vote) can not be answered unless crucial data was provided especially (Timing of delays, classification of delays, concurreny)
as these data items will affect the legal entitlements and enforcement of LD. proprtioning the risponsibility and the cost in this manner will not make and will not give even close fair determination.

or do you have another openion???


Best regards,
shamail shardan
User offline. Last seen 17 years 33 weeks ago. Offline
Joined: 22 Jan 2006
Posts: 23
Groups: None
Dear Jawad.

Now i can see that we were talking on the same language but with differences in procedures only,i’ll explain more ,,

I know that the FIDIC inculded the interium determination of an EoT, and i dont know why do you think that i do not agree on that, actually what i said is that the final determination of an EoT should NOT be made before the Original Completion Date is exceeded. Howoever, interium EoT’s could be determined but are NOT to be considered final as the failure of the Engineer to issue certain drawings could be superceeded by another delay by the Contractor that will cover this delay. The Contractor has the right and should actually record each delay and causes of delay and at the completion date, all the correspondeces shall be reviewed along with cost implications to determine the actual damages caused to each party from the other’s party delay. Its so complicated, and its so difficult but its the only way to do it ...

For example, suppose the Engineer has approved an interuim EoT of 7 days, and the Contractor has submitted full documentation including cost implications, these data will be kept in record, until the original completion date is exceeded, ONLY then we can determine if the Contactor is STILL entitled for the certified EoT or by the means of his concurrent and superceeding delays, his rights for such an EoT is no longer valid, the EoT cannot be treated as an algebric sum, i.e EoT = Delay due to Employer - Delays due to Contractor, it reasonably has to be on a concurrent basis, but the BIG quesion is (which was the question of the vote) ,, suppose that at the original completion date, the Employer’s delay is 30 days, but the Contractor’s delay is 31 days, should the Contractor take all damages !!?? or vis versa ,, should the Employer take the damages if he caused the 30 days !!?

I agree with you, there will be financial impact on both parties due to this delay, thats why i really think that the current Contracts DOES NOT help us as Contractors or Employers on the concept of the accountabilities ,,,

The vote basic question was, would u split the responsibility and therefore the damages based on time, cost or ..... ?

Employer’s delay = X days , Employers Damages = Y
Contractor’s delay = Z days , Contractor’s Damages = M

Employer Responsibility = ??????
Contractor Responssiblity = ??????

what do you think Jawad ?
Jawad Al-Nimri
User offline. Last seen 12 years 5 weeks ago. Offline
Joined: 7 Aug 2006
Posts: 39
Groups: None
Shamail,

Very good points, it is a fruitful discussion. I agree on many of your inputs. But due to my painful experience I can not agree on one thing. “Postponing determination over EOT to commence to the original completion date”.

It is a recommended practice in claims management to claim (not to reserve your right to claim) during the performance time.

Reserving your right to claim will put you in a situation where you might:

1. Loose all your claims based on incompliance with procedural clauses in the Contract.
2. Furthermore it will give the Engineer the opportunity (which he will never miss, believe me) to leave determination on some of your clear claims, which is very important reference point, to others (courts, arbitrators, …etc) remember you have no contractual relationship with the engineer.
3. In conclusion I would like to say that you do not have to reserve the right to claim, your right to claim is maintained and reserved under the law governing the contract.

In addition to the differences in contracts types and experiences, there are differences in duties related to the planning engineer role in claim preparation, ranging from preparation only the analysis (retrospective or otherwise) to fully managing the delay claim. In the second (farthest) extent the legal knowledge or background is of the same or more importance than the correctness of the analysis itself.

To fully understand my point, I will give you the following horrible example:

At some point in time, the Engineer delayed the provision of drawings, a clear failure on the part of the Engineer entitles the Contractor to an EOT and cost. At this stage the issue of establishing entitlement is done and it is not negotiable.

The contractor as it is the old-bad-practice in our part of the word did not claim the EOT / Cost, instead he notified and “Reserved his right to claim”. Things seem okay till now

Under clause 14 of the FIDIC the Engineer requested the contractor to provide a recovery schedule. And the Contractor complied.

Then the Contractor was delayed (due to his own problems) in meeting the scheduled recovery plan.

You know what happened? He lost the golden card of establishing entitlement by giving the employer a gift, the employer now can allege that the overall delay in meeting the original contract time for completion was NOT due to the issue of the Late drawings, but it is due to the failure on the part of the Contractor to meet his schedule dates (of the revised activities in the recovery plan).

See my friend, interim determinations over EOT are of great importance they do not necessarily result in the same EOT amount granted at completion, actually these determinations are the only REAL reservation of the claimant’s right.

Another issue is that if the project is delayed, then at the original date for completion there would be remaining activities (their number and scope depends on the magnitude of delay suffered) that have not been completed and your determination would also carry some inaccuracy (but sure it would be more precise), so why not to carry the analysis at the event date? And obtain approval over the most likely delay due to that event, with periodic review? Actually FIDIC requested that, implicitly.

Besides, shamail, any change in the original schedule (in case of delay) will, as a matter of fact, result in change at least to the contractor’s cash flow (reduced billings with constant overheads) and the consequent change in the finance requirements (magnitude) to do the same job. These changes are claimable and are a legitimate right to the contractor why to lose them? Their name is not “Extra profits” they are DAMAGES.

When requesting the contractor to increase resources, you have ignored a very important point in the THEORY OF CONTRACT; “The intent of the parties” at the time they entered in to the contract. If the Employer consumed time originally agreed and planned for to be available to the Contractor then the contractor should be compensated and allowed SOME time to perform its obligations under the contract. I agree that it is an implied duty on the Contractor to mitigate losses; however it is not the right (legitimate right) of the Employer or the Engineer to criticize what the contractor can do or could have done.

Finally, I do agree that the contract must be detailed to include procedures for this matter, and not only to include them implicitly. .






Andrew Flowerdew
User offline. Last seen 2 years 23 weeks ago. Offline
Joined: 14 Dec 2004
Posts: 960
Groups: None
John,

The contract may not expressly state the contractor can reserve his rights but all the contractor has to do is write a letter or make a note on the change order (variation order or similar) to that effect.

It has been known to catch a few contractors out, especially in some Middle East countries where a signed change order is often taken to be the whole bargain struck - if there’s no qualifications, they can’t be added or claimed later.

Difference places do things slightly differently, it’s wise to enquire and find out the particular practices of a place when starting out on a contract.
Charleston-Joseph...
User offline. Last seen 2 years 39 weeks ago. Offline
Joined: 10 Jul 2005
Posts: 1347
Groups: None
Hi Shamail,

Bravo.

That was a brilliant understanding of claims.

I wish you will continue to expound your overall understanding in project management not only in the area of claims but in other fields.

Personally, it helps me a lot. Thank you.

Cheers,

charlie

John Whitney
User offline. Last seen 8 years 38 weeks ago. Offline
Joined: 26 Jul 2004
Posts: 35
Groups: None
Shamail,

To clarify, my comments were not made in respect of FIDIC, but to obligations frequently contained in the bespoke contracts that most EPC client organisations produce these days.

I have been working on such bespoke contracts for the past ten years, and in not one of them (in first draft form, anyway) has there ever been a recognition that the Contractor may be entitled to claim extra costs - or even reserve his rights to such costs - as a result of a client demanding a recovery programme. Without exception, the language is framed in the manner of the contractor automatically assumed to be responsible for the delay. This is most certainly not always the case, as we all know.

I always say that, within reason, the client can instruct whatever he wants - all he has to do is pay for it!


John
Andrew Flowerdew
User offline. Last seen 2 years 23 weeks ago. Offline
Joined: 14 Dec 2004
Posts: 960
Groups: None
Shamial,

Can’t disagree with anything you’ve said.
shamail shardan
User offline. Last seen 17 years 33 weeks ago. Offline
Joined: 22 Jan 2006
Posts: 23
Groups: None
Dear All

I fully understand where you people come from and your backgrounds, which i fully respect, however; Jawad believe me that i know what i’m talking about when i spoke about the final determination of the EoT, i’ve done as a Contractor and as a Client Rep. , its the best way , anyway ,,

I think that its not true that any change to the original schedule will necessarily involve additional cost to the Contractor, i think by saying so we are being SOOOOO naive (sorry guys but this is true), we all know how plans are built up , they are simply not perfect, however; i am saying that at some point there MIGHT be NO WAY to do this without "accelerating" the progress (but this case invloves events that would arise during the last third of the project duration, when changes to the schedule are very limited in options and methods.

Moreover, yes it is the obligation of the Contractor (even if a dispute was ongoing regarding the responsibility of the delay) to submit (upon the request of the Engineer)a "REVISED" programme , to recover the delay (or the maximum part of the delay) by any means possible, the FIDIC does not include the conditional if "if the Contractor was the cause of the delay" rather it said if the Contractor’s progress of works is falling behind the programme (which could be due to a reason by the Contractor or by the Employer) then he should submit a revised programme , ...etc

On the other side, and to answer your fears about the rights of the Contractor, while it is the Contractor’s obligation to submit such a recovery programme its his right to "RESERVE HIS RIGHTS" to claim for the related cost in case the delay was proven to be caused by the Employer. and this should be fair and accepted by the Employer. However; the Engineer has the right to discuss the Contractor’s programme and propose solutions that invloves the min. cost implications or even NO COST implications, the Contractor should verify these costs.

Jawad, there are many points in my previous post that i think you might want to read them again in a different way, your interpretations does not relate to what i said my friend.

In conclusion, i think that variations are not to be taken as an opportunity by any party (being the Contractor or the Employer) to take it as an advantage to make extra profits by acting unfair, we have to admit that both Contractors and Employers are doing it (each in his way) and this is creating the lack of trust between all parties when it comes to judging a V.O, thats why i think that Condtions of Contract such as FIDIC or other Contracts should go down a level more and detail some methodologies regarding these issues.

Cheers all
John Whitney
User offline. Last seen 8 years 38 weeks ago. Offline
Joined: 26 Jul 2004
Posts: 35
Groups: None
Jawad,

Some good points there.

Another spin-off from this topic is the requirement (under all contract forms that I know) for the Contractor to give recovery programmes when his progress is showing late on the original critical path.

When negotiating contract terms, I always argue that the Contractor is only obliged to give a recovery programme if it is agreed by both parties that the Contractor is solely responsible for a critical delay. However, consider the situation where the Contractor is, say, one month late on the critical path yet has submitted a two month delay claim that is disputed by the client. In this scenario, arguably no such recovery programme is due because the Contractor should have had an EoT and be monitoring progress against a two month delayed completion date.

This always raises a spirited debate during tender negotiations, but so far I have always managed to include adequate wording to cover the Contractor’s position. So, sensible do recognise that the Contractor does not have an open-ended obligation to meet the original date. They just need reminding of the fact.


John
Jawad Al-Nimri
User offline. Last seen 12 years 5 weeks ago. Offline
Joined: 7 Aug 2006
Posts: 39
Groups: None
Shamail,

you do not need to change the FIDIC there are numerous clauses talks about "interim determination" over EOT and cost, However there is no any interim "Granting" of an extension of time.

It is an issue of legal practice in not granting an extension of time. determination, on the other hand, is what meant by Periodic or interim accounts to be supplied by the contractor.

The issues you raised are interesting but what Mr. Andrew pointed is the correct (from my perspective and experience) why? please consider the following:
1- The contractor shall provide Notices. Legally if the Contractore does not provide such a notice he is prohibting the Employer from taking any recovery / correction measures. If it is found that the Employer could have taken such a measure and he was prevented by means of not providing such notice then the contractor will bear all the consequences.
2- The best time to analyse a delay event affecting CP or a NON-CP to produce (delay / disruption) is at the start date of the event. (to know if the contractor was already delayed or not) and the likely consequences of delay and after the delay event the actual cause and the legal determination exactly (taking into coonsidferation the concurrent delays.
3- The example you mentioned Shamal is not applicable since you are talking about consequent events and not a parallel event.
4- Changing the sequence of work and crunching the contractor’s schedule can never end up with no additional cost on the part of the contractor (please consider overcrowding for example)
5- What am so sure about is that the required documintation at the completion oof the project can never be sufficient to support disruption & delay claims take it from your brother it is based on a very painfull experience.
6- by taking and forcing the AC/ Engineer to fix an interim EOT you will guarantee that any deduction in this EOT will require explanation on the part of the Engineer. and you will never worry about issues like perfect documents control. pla pla pla

Regards,


Andrew Flowerdew
User offline. Last seen 2 years 23 weeks ago. Offline
Joined: 14 Dec 2004
Posts: 960
Groups: None
Shamail,

That’s one way of doing it but why not view an interim EoT award as provisional, subject to revision by other interim reviews and later the final review.

Haven’t got the FIDIC documents to hand as I write this so I’m not going to be specific in case I get the various versions mixed up.
shamail shardan
User offline. Last seen 17 years 33 weeks ago. Offline
Joined: 22 Jan 2006
Posts: 23
Groups: None
Andrew,

Agreed in principle, so do you think a "Provisional EoT" would solve the case, i.e the Engineer would certify an EoT PROVIDED that the Contractor DOES NOT cause any delay that exceeds the above delay later on in the project. would that be reasonable and fair?

if yes I’ll change the FIDIC immediately for you ;-)

Cheers ;-)
Andrew Flowerdew
User offline. Last seen 2 years 23 weeks ago. Offline
Joined: 14 Dec 2004
Posts: 960
Groups: None
Shamail,

I do agree with a comprehensive analysis at completion, I just also believe that there should be interim assessments as well.

You are correct that the contractors time related costs should be covered up to the original completion but that’s not 100% of the story.

1. The Contractors contractual entiltement to an EoT will have accrued earlier (assuming he’s due an EoT) and therefore he should have the benefit of that entitlement as I’m sure the Employer would like the benefit of any entitlement he’s due, when it’s due.

2. Leaving it all to the end creates uncertainty, both for Contractor and Employer as discussed previously.

3. If the Contractor is entitled to an EoT and it is withheld then as discussed below, he has two choices.

(1) to unilaterally accelerate to hit the existing date or at least minimise his exposure to LD’s if the date can’t be met.

(2) to carry on regardless and in anticipation that an EoT will be awarded later.

If he accelerates, except maybe in the USA, any claim for constructive acceleration will not be recogised and he’s stuck with these costs unless he’s prepared for a difficult and risky fight. Trying to seperate out and prove acceleration costs is as hard as trying to prove disruption. In your example of a bricklayer, your assumption may be right but it may often be the case that 1 gang = 100% production, 2 gangs = 180% production, not 200%. Therefore by doubling the resource, the time is not halved and the overall cost is not the same - it increases. But you try agreeing these sorts of things with the CA, more often than not you may as well be talking to the site cat!

If he carries on regardless, it often ends in an ever increasing feeling of frustration on all sides, blame being levelled in all directions, with all the associated bad feeling, soured relationships, etc, and hey presto, we have a dispute. Lets spend lots more money and time in sorting it out!

It could all be avoided, or at least substantially avoided, if the EoT was assessed and awarded on an interim basis as the project went along. I’m sure there would still be disagreements, some leading to full blown disputes, but the numbers would be significantly less.

And if for no other reason, both Contractor, Employer and Consultants would have a better of idea of what’s happening, what’s expected of them and when - and that can only help the project.

I’m actually a big supporter of dispute avoidance believe it or not, and I believe that ongoing interim assessments of EoT’s is one of the most significant ways to reduce time related disputes.
shamail shardan
User offline. Last seen 17 years 33 weeks ago. Offline
Joined: 22 Jan 2006
Posts: 23
Groups: None
Andrew,

The Contractor’s indirect costs are and should be covered by the Contract up to the original completion date of the project, why do you disagree to have the comprehenisve analysis be done at that date rather than on interim basis, what would harm the Contractor to do so ?
Andrew Flowerdew
User offline. Last seen 2 years 23 weeks ago. Offline
Joined: 14 Dec 2004
Posts: 960
Groups: None
Shamail,

You raise some very relavent points but I still disagree that it it should all be left to the due date of completion. The interim EoT’s should (and can only) be awarded on the knowledge at the time. If that knowledge changes so can the EoT awarded.

Forgeting the contractor, the Employer in my experience wants the answer to two questions above all else:

1. How much is it going to cost?
2. When’s it going to be finished?

The CA’s obligation to the Employer is amongst other things, to advise the Employer on these two matters. He can not do this properly unless he makes some form of assessment on the time for completion and the liability attached to it as the contract progresses.

We always hear Contractors moaning and forget about the Employer not knowing where he stands and how much it’s going to end up costing him. Whether not being able to suitably advise the Employer on these matters would amount to a breach of the CA/Employer contract depends on the terms of the CA’s employment, but I would guess in general that it would. The same arguments that are leveled at Contractors for not notifying delay such the Employers loss of a chance to mitigate would be equally applicable.

I therefore maintain that it is in all the parties interests that the situation is monitored and assessed at regualr intervals during the contract and not left until later.
shamail shardan
User offline. Last seen 17 years 33 weeks ago. Offline
Joined: 22 Jan 2006
Posts: 23
Groups: None
Gentlemen,

The whole idea of a retrospective analysis does not “theoretically” constrain the Contractor from any of his rights for any EoT. Colleagues, we have to look at the issue in a practical way, as follows:

The occurrence of events that cause delays to the CP is common to be either at the early to mid stages of the project life time. As we all know, plans are NEVER perfect, and every project MUST have different ways of doing it, its just that the planner has chosen one of them (should be the best in terms of time vs cost), the whole idea is, at an early to mid stage of the project, problems MIGHT be solved by going back to the master programme and doing changes that MIGHT not add any cost to the Contractor, an example; say the block works was a critical activity and the resources could be doubled to do it in 50% of the duration with the same cost to the Contractor (at the same productivity for labor), another example, say the planner have estimated an activity on the CP at 14 days , instead it could be done in 7 days (over estimation).

I think it’s the right of the Contractor to get the EoT for the duration that COULD NOT IN ANYWAY be dissolved with no extra cost (or even with extra cost that might be negotiated and agreed by the Client), rather than just get it because the CP which is all based on estimated norms, certain resource levels and assumptions says that the project is ANITCIPATED to be delayed by so and so…., this is not fair to the Client at all.

Add to the above, what if the Engineer awarded the EoT to the Contractor, and just few weeks later the Contractor procurement of an item was found to be delayed a lot more than the EoT certified previously to the Contractor, should the Engineer change his mind and delete the Variation Order awarding the EoT ?! It wont be right, all events should be studied at the completion date of the Contract (not at the actual, just when we pass the original completion date), the events should be analyzed to determine whether the Contractor is entitled for an EoT or not and by how much.


Andrew Flowerdew
User offline. Last seen 2 years 23 weeks ago. Offline
Joined: 14 Dec 2004
Posts: 960
Groups: None
John,

Totally agree, and people wonder why there’s so many disputes over time. Certainly in the UK there’s virtually no legal recognition of constructive acceleration and that just plays into the hands of the Client in not awarding an EoT when one is due - it was the case before statutory adjudication that this course of action by the Client had the effect of forcing the Contractor to either try and meet the often impossible completion date or take the risk that he would be awarded an EoT at arbitration and carry on regardless.

The right to Adjudication "at any time" has now given Contractors the possibility of getting an interim (binding if the parties agree) decision on such things but the downside is that the 28 day timescale is often hopelessly inadequate for anything but the simplest of time related questions. If the Contractor spends the proper amount of time preparing his claim before issuing a notice of referal to adjudication so as to stay in the time limits, the claim is often likely to be out of date before he starts, so what then. Another adjudication and another until the end of the contract. All just to resolve what should be resolved by the CA doing his job in an independant, fair and impartial manner in the first place.

Although the above said, I do have some sympathy for the CA as "independant, fair and impartial" in theory is great - in the real world maintaining that stance is often difficult or nigh on impossible if he want’s to keep his job, not be sued, etc, etc.

Probably the best reason for using an independant "Dispute Review Board" with no ties to either side that I can think of, especially if where it’s available, the board/person has the power of adjudication.
John Whitney
User offline. Last seen 8 years 38 weeks ago. Offline
Joined: 26 Jul 2004
Posts: 35
Groups: None
Andrew,

I absolutely agree that, as a matter of good practice, valid EoT should be awarded prospectively. I have found that the so-called retrospective EOT "assessment" is one of the biggest frauds in the industry. I think we all know why, and it isn’t really necessary to explain it here.

I was on large EPC project some years ago which suffered a 10-month delay on the critical path (CP). There was no argument about the CP or the extent of the delay - just the minor matter of whose responsibility it was!

It went to arbitration during the currency of the project (called by the client) and we won. The client had no further reason to avoid giving the EoT but was in denial even after the arbitrator’s award. eventually we had the time awarded but it was a painful process.

Under the alternative, retrospective award scenario, why should we have been forced to accelerate 10 months to try and achieve a redundant and impossible completion date simply because the client was just too bloody-minded to give the entitlement we were due? This happens on many projects all the time.

I say prospective EoT awards should be the order of the day!

John
Andrew Flowerdew
User offline. Last seen 2 years 23 weeks ago. Offline
Joined: 14 Dec 2004
Posts: 960
Groups: None
Shamail,

I agree the final EoT is determined at or after the completion date but I also believe that the EoT should be awarded progressively during the contract as and when it reasonably obvious that one will be due. The final determination of the EoT should be no more than a review of the EoT already granted during the contract.
Jawad Al-Nimri
User offline. Last seen 12 years 5 weeks ago. Offline
Joined: 7 Aug 2006
Posts: 39
Groups: None
Dear All:

This is an interim response, i do not have the time right now to provide details.

the fidic came to mention the possible and actual delays for example "sub-clause 6.3" the contractor shall give notice for whenever "planning or execution is likely to be delayed or disrupte"

however the engineer shall grant the under clause 6.4 "the delay the contractor suffers"

the reason for not granting interim EOTs is due to:
1- Lack of experience on the Engineer side related to both schedule analysis and legal positioning.
2- the deep problem of attitude, where granting EOT means bad management by the Engineer and redusing his future opportunities with the same Employer.
shamail shardan
User offline. Last seen 17 years 33 weeks ago. Offline
Joined: 22 Jan 2006
Posts: 23
Groups: None
Andrew,

Again my friend :-) what you said is right but the problem it only applies when there is such a phrase in the Contract, the phrase “POSSIBLE DELAY" & "ACTUAL DELAY" are both not used in FIDIC, and the Engineer’s interpretation for the meaning of the word "DELAY" as if its the actual delay (then he should adopt a retrospective method) or theoretical (interim EoT awarded) is totally dependant on the Engineer in my part of the world, some of them would award, others would not. I was on the Contractor side once, and now i’m the Client Rep., on both cases i believe that the time whereby an EoT should be considered final should not be before the Original Contract Completion date has already been exceeded.



Cheers
shamail shardan
User offline. Last seen 17 years 33 weeks ago. Offline
Joined: 22 Jan 2006
Posts: 23
Groups: None
Dear All ,

We are from different parts of the world, and i think "sometimes" we are talking on different wave lengths when it comes to Contracts, because simply we have different Contracts in different parts of the world :-)

For example, in the U.K there are many types of Contracts (JCT Contracts,IFC, NEC for Engineering projects, GC (Works)for governmental projects, ..etc), while in United Arab Emirates we use FIDIC, so the words "Likely" & "Actual" are never attached to the word "Delay" in our Conditions of Contract.

I advise post starters to furnish more details and be more specific to get the best results of the forum.

Cheers All
Andrew Flowerdew
User offline. Last seen 2 years 23 weeks ago. Offline
Joined: 14 Dec 2004
Posts: 960
Groups: None
Jawad,

Welcome to the forum. You have identified some relevant points:

a. It depends on the case, EOT is claimed during or after the project “time for completion”

To this I would add it also depends whether the contract talks of "likely" delays or "actual delays", ie is the EoT based on the contractors theoretical entitlement to a possible delay or only that for actual delays.

b. Did the analyst consider the varied durations of all the OTHER activities not affected by the delay event or not.

Correct, it is not only the new impacted events that require consideration but also delays to existing events. The qtiming of when this delay was actaully known about though is often hard to pin down.


c. Did the analyst consider the varied logic caused by nothing but poor prepared schedule or not.

Obvious errors in the as planned baseline schedule should be amended (noted and justified as to why it was changed) but changes in "good" logic will be reflected by rescheduling using progress overide mode, ie the logic is ignored if progress dictates it is incorrect, eg there is an FS link between two activities but in reality the second activity was started before the first activity finished. In progress overide mode the link will be ignored and the progress will take precedence and be reflected in the analysis.
Jawad Al-Nimri
User offline. Last seen 12 years 5 weeks ago. Offline
Joined: 7 Aug 2006
Posts: 39
Groups: None
dear all,

it is my first time to contribute in such a great forum of brain storming, am a civil engineer working in direct with claims preparation. I have applied the technique of TIA several times.

Let’s start as follows:
1. Assuming all the input data are correct (burden of proof which is other issue to deal with),and
2. Assuming that the delay analyst applied the correct as-built (record) schedule dates.
3. Then the TIA (from scientific point of view) is legal and binding. However,
a. It depends on the case, EOT is claimed during or after the project “time for completion”
b. Did the analyst consider the varied durations of all the OTHER activities not affected by the delay event or not.
c. Did the analyst consider the varied logic caused by nothing but poor prepared schedule or not
4. see my friends I will be welling to provide more information, this is only some issues to think of.
Andrew Flowerdew
User offline. Last seen 2 years 23 weeks ago. Offline
Joined: 14 Dec 2004
Posts: 960
Groups: None
Shamail,

FIDIC (depending on which version) has probably the word "actual" attached to it.

If the clause talks about "...taking into account THE DELAY caused" then it is arguable that it is talking about the "actual" delay caused - therefore the arguement follows that an Engineer can’t award an EoT until he knows the actual delay and an award has to be done retrosoectively.

If the clause talks about "...taking into account THE POSSIBLE DELAY caused" (or likely delay, etc) then the arguement follows that an Engineer can award an EoT based on a theoretical forward looking entitlement. ie the EoT can be awarded prospectively.

Personally, if it is reasonably apparent to the Engineer that the Contractor is entitled to an EoT then I think he should award one "taking into consideration all the circumstances" or whatever the contract calls for him to do.

Given that most contracts call for a 2 or 3 stage process for the award on an EoT, ie (1) interim, (2) review (may be final) at completion date and often a (3) final review at a given period after the completion date then my belief (not shared by everyone) that read as a whole, the intent is the Engineer should give EoT’s as the contract goes along and not wait until the end to do it.

It is this play on words that give many the excuse not to award an EoT until the end of a contract(as they can’t possibly know the full extent of a delay until it’s all over!!!!! - ie, the actual delay caused) of a contract and therefore inhibit the proper management of a contract and cause disputes.

There are however many other factors that come into play, Engineers worried about being sued by the Employer if they give an excessive EoT, the belief that an EoT once given can not be reduced, etc. (I’ll wait for the questions on that last point!!!!)

But that’s the world we live and work in .
Charleston-Joseph...
User offline. Last seen 2 years 39 weeks ago. Offline
Joined: 10 Jul 2005
Posts: 1347
Groups: None
Hi Andrew,

Only now I acknowledge that this help me a lot. And many thanks to you.

Actually, your opinion broaden my understanding on how to handle claims.

My previous experienced was a combnination of all, I encountered a case as stated in the 1st paragraph. It was very plain and simple. Also, it was very easy.

In addition, I did encountered situations as explain in the other paragraphs. The experienced was to much work but pay remain the same because it was the same compnay. On the other hand, I like TIA. The planner role was very important.

Cheers,

Charlie

Andrew Flowerdew
User offline. Last seen 2 years 23 weeks ago. Offline
Joined: 14 Dec 2004
Posts: 960
Groups: None
Charleston,

Alittle bit more:

How to treat the situation when the Contractor / Employer are both causing delay at the same time - most contracts are silent on this matter but more and more are expressly stating what to do in this situation. If yours does, follow it, if not then it will be the law of the contract that prevails - eg in UK, a breach by the Employer is sufficient to award an EoT even if the Contractor is also in delay. (At least for JCT contracts)


Is TIA compliant with the contract conditions and therefore the correct method to use - normally yes. TIA is a forward looking analysis, does your contract require or at least empower the CA to award interim EoT’s on a forward looking basis? If so TIA will normally be compliant.


How to apply TIA in accordance with the contract? The main point here is who is awarding the EoT. Again, usually the CA and therefore the programme should be updated and impacted using what the CA knew or reasonably should have known at the update date. Eg the Contractor may have ordered an important piece of equipment and knows the delivery date - but did the CA know this? If not then the update shouldn’t use the delivery date but what it is reasonable to expect the CA’s knowledge at the time.

The NEC familly of contracts uses TIA as its chosen method of programming but it is updated from the Contractors point of view because the contract requires the Contractor to update and submit the programme, not the CA.

Hope this helps, TIA will work on a short term, long term or any term contract, just a case of getting your head round the finer points like those above in order to use it.
Charleston-Joseph...
User offline. Last seen 2 years 39 weeks ago. Offline
Joined: 10 Jul 2005
Posts: 1347
Groups: None
Hello Andrew,

Most project I got involved with were not very clear in the contract with regards to:

"There are a number of other things to think about depending on the terms of the contract - such as how to treat the situation when the Contractor / Employer are both causing delay at the same time, is TIA compliant with the contract conditions and therefore the correct method to use, and if it is, how to apply TIA in accordance with the contract."

meaning TIA was not mentioned in the contract.

In this regard, your explanation as above may be construed as the international norms???

This is really complicated in the event the projects will run for years, let say five years with lots of variation and interim EOT.

Anyway I really and sincerly thank you for your idea in TIA. I knew it is a very hard exercise and also a good reason to earn big bucks.

Cheers,

Charlie
Andrew Flowerdew
User offline. Last seen 2 years 23 weeks ago. Offline
Joined: 14 Dec 2004
Posts: 960
Groups: None
Kuma,

Firstly progress is updated to the update date (often coincides with the monthly progress meeting or similar), programme rescheduled and baselined.

Then each event is put in ONE AT A TIME and the programme rescheduled after EACH event is added/updated and baselined. NOTE BOTH CONTRACTOR AND EMPLOYER EVENTS THAT MAY CAUSE DELAY NEED TO BE INCLUDED, NOT JUST THE EMPLOYER EVENTS.

Therefore for each update date you will have a number of baselines corresponding to:

Progress update
Event 1
Event 2
Event 3
etc,etc.....

Each baseline will show the separate effect on the programme of progress / each event, on the completion date. ie you have cause and affect.

eg say the progress update moved the completion date back 1 wk and the lack of progress was down to the contractor - no EoT is awarded. Event 1 was a potential Employer delay but only reduced float and had no effect on the completion - no EoT. Event 2 was an Employer delay and moved the completion back a further week - 1 wk EoT is awarded. The 1wk is added to the current completion date, the new completion date it is not the date shown on the baseline.

There are a number of other things to think about depending on the terms of the contract - such as how to treat the situation when the Contractor / Employer are both causing delay at the same time, is TIA compliant with the contract conditions and therefore the correct method to use, and if it is, how to apply TIA in accordance with the contract.

The above is a very short and general overview but by no means exhaustive, but hope it helps.
Raja Izat Raja Ib...
User offline. Last seen 12 years 48 weeks ago. Offline
Joined: 2 Jun 2005
Posts: 299
Hi Kumar,
In my practices, I did collect every interfacing causes in my personal booklet from the start to end of the project, EOT to be request 3 month before MCD to make sure the time of letter co-respondence in time can be reply and U have the time to prepare your the schedule but dont include with VO(Variation Order), CO(Change Order). First thing U have to do is let the client decide:
1. Letter head
2. reason claiming EOT
3. History Causes of Delay when it happen.
4. Proposed EOT Schedule in Package( SCURVE, Histogram etc
).

regards
Siva Kumar
User offline. Last seen 5 years 12 weeks ago. Offline
Joined: 5 Jul 2005
Posts: 44
Groups: None

Andrew,

I Agree...,
But how this method can be used to claim EOT..
since the progress update may itself have delays.


Kumar,
Andrew Flowerdew
User offline. Last seen 2 years 23 weeks ago. Offline
Joined: 14 Dec 2004
Posts: 960
Groups: None
Kuma,

Before impacting any delay event, the programme should be fully updated for progress. ie, the delay event should be impacted on a programme that refects the true state of the site at that date.

The event is impacted, a result drops out. In the next update, the progress is updated first and then the remaining impact of the event impacted. ie every update consists of a progress update and an event update. This seperates out the effect of progress and the event.