Not necesarily, but I would guess theres either one or two other clauses dealing with an assessment at the completion date and possibly one dealing with a final assessment at some point after completion. For another guess, both use similar wording and are Cls 44(4) and (5).
Member for
20 years 6 months
Member for20 years6 months
Submitted by Puneet Gupta on Thu, 2006-08-03 22:54
You have added one critically important point - the analysis is being done retrospectively.
The analysis should be carried out (retrospectively or prospectively) in accordance with the contract but this is especially relevant when the analysis is retrospective.
The wording of your EoT clauses will be all important, particularly any interim clause EoT assessment.
Your entitlement to an EoT will have accrued at some point during the contract (assuming youre entitled to one!) and it could be that the state of the Engineers knowledge at the time your entitlement accrued is what is relevant and what he should be basing his assessment on, not what he knows now.
Member for
20 years 6 months
Member for20 years6 months
Submitted by Puneet Gupta on Thu, 2006-08-03 12:02
Actually engineer approach while determining EOT is retrospective. He has not giving us EOT yet. So we were fast in our work to avoid LDs. We even worked in monsoon though we were not supposed to work in monsoon. But that was all our risk.
So Engineer is now saying that as we worked in monsoon on that activity so he will not consider monsoon calendar for that activity.
Also on one activity which ( yet to execute) is driving my project completion date ,he is saying this activity can be done in dry season.
Yeah i got your point , and i am thankful to all of you for sharing your knowledge and experiance here.
Member for
19 years 7 months
Member for19 years7 months
Submitted by Karim Mounir on Thu, 2006-08-03 11:33
I also think Puneet said at the beginning of this thread that the programme was an actual contract document, if so theres no doubt that the Engineers alterations constitute variations.
Member for
20 years 10 months
Member for20 years10 months
Submitted by Andrew Flowerdew on Thu, 2006-08-03 08:56
Yep, totally agree - it would appear hes trying to be clever in order to award the minimum EoT but I think his cleverness might come back to bite him.
Member for
20 years 10 months
Member for20 years10 months
Submitted by Andrew Flowerdew on Thu, 2006-08-03 08:24
They might even have a claim for full prolongation and an EoT, just depends on the definition on completion. Which would be nicely ironic, the Engineer reduces the EoT by excluding an activity and then has to give an EoT for his instruction to exclude the activity!
Member for
20 years 6 months
Member for20 years6 months
Submitted by Puneet Gupta on Thu, 2006-08-03 07:26
I generally agree with your thoughts - however, the changes made by the Engineer, should he wish to stick to them, will almost certainly amount to a instructed variation entitling you to claim for them, eg, additional costs of carrying out works in the monsoon season. They may even amount to an instruction to accelerate.
Have a think about the changes the Engineers made in this context.
Member for
20 years 6 months
Member for20 years6 months
Submitted by Puneet Gupta on Wed, 2006-08-02 23:59
1. Well Engineer is not changing the baseline duration.
Let me give more explaination on this. We have defined baseline schedule on the day basis & considering 1 day is equal to 24 hours. so if any of my activity has FS relationship then if predecessor finishes on say 1 Jan 06 its successor starts on 2 Jan 06. Now when in his determination of EOT he has defined hours in a day and most of the lost is in hours say 2 hours of working in a day and rest 22 hours lost on 1 jan 06. So my predecessor activity finishes on say 2 jan 06 and the successor activity can start on same day i.e 2 jan 06 ( as predecessor consumed 2 hours on 1jan 06 and 22 hours on 2 jan 06 so in remaining 2 hours of 2 jan 06 i can start my successor). Well some how this approach of engineer is acceptable to me. But the way he defined the hours in the software is not acceptable to me. As i already mentioned by default in suretrack a day consists of 8 hours and our 1 working day is equal to 24 hours. While defining the non working hours Engineer need to be more careful. I am working on making his assessment to make it more accurate and will let you know my results soon.
2.Well on as-built logic approach, i have the understanding that schedule belongs to contract he can change the as-planned logics to meet the key dates, but engineer can not do that as for determining EOT we are using as-planned as-impacted approach. This appraoch we are using to see the impact of culpable events on as-planned schedule. Is my understanding correct here????
3. Well he changed the planned monsoon calendar by saying that this activity can be done in monsoon. while in our contractual (baseline) schedule it was planned to do this activity in dry season only. He is doining so as this activity is driving the project completion date , so just by changing the calendar he is reducing EOT by a good time.
4. The same activity as mentioned in point 3 is linked with my project completion date, and he is deleting this relationship by saying that we can do this even after project completion and during de-mobilization. Again he is saving project EOT by a good time.
Can we change the Planned schedule logics (as long as there is no logical error in them) in As-Planned-As-Impacted approach???
Member for
20 years 5 months
Member for20 years5 months
Submitted by Raja Izat Raja… on Wed, 2006-08-02 13:32
1. If hes changing the shift pattern such that the original baseline activity durations are reduced then were back to the argument that the overall duration of the baseline activities were based on the shift patterns actually worked rather than on the calendar settings of the software. He shouldnt be altering any baseline activity duartions unless it is a known fact to him that the baseline durations were based on say an 8hr day and you actually chose to work a 12hr day. That said, even if it that is the case, the productivity obtained between an 8hr and 12hr working day is not a direct relationship and cannot be simply interchanged without consideration of the extra hours worked in terms of its affect on the workforce - fatigue, etc.
2. It isnt unreasonable for him to take account of the as built logic, ie reflect the situation as it actually is on site at the time of making his assesment. His changes must follow the correct logic however and the result properly reflect the state of the site.
3. I would ask him to confirm in writing all changes made to the baseline logic/calendars but especially this one - or if you are aware of all the changes then confirm them to him in writing. Is the change is reasonable in the circumstances is the best answer I can give you without knowing more. It sounds doubtful to me unless he has a crystal ball to predict the monsoons.
4. Ask for his written instruction (or confirm to him) to do this item of work after mobilisation and confirm that it will not affect the issue of the completion certificate prior to this work being started (if thats the case) - or that he wants you to do the work in the defects correction period. Then when hes given the instruction claim prolongation/EoT for the instruction. Cant really be precise on this one without knowing more about the programme but I hope you have the idea - the jist of the answer is that if he choses to change the logic and dictate your sequence of work then theres probably a way to make him pay for it!!!!!!!!!!
Member for
20 years 6 months
Member for20 years6 months
Submitted by Puneet Gupta on Wed, 2006-08-02 12:29
1. He changed the schedule into shift basis. Shifts were not defined in the baseline schedule.
2. He resequnced the activities by saying that as per the as-built logic. However there was no logical error in baseline schedule.
3. He is changig monsoon calendar of few activities to non-monsoon calendar. Can he really do that??? i mean can he change the planned calander.
4. Finally one activity which is driving project completion date, he is saying that project completion is not affected by this activity as we can execute it even during the time of mobilization. Yes we can do it after mobilization, but is he not changing the planned logical sequence without any logical error in them.
And giving us a new reduced date.
Please keep giving your expert comments on above mentioned points.
Thanks
Member for
20 years 6 months
Member for20 years6 months
Submitted by Puneet Gupta on Wed, 2006-08-02 12:18
Mr. Andrews is right, P3 & Suretrack are compatible.
In our contract they listed software is Primavera & version suretrack.
Engineer is using Suretrack and we are using both suretrack and P3.
So engineer approach is valid only in suretrack as we cannot define hours in a working day when our planning units are days in P3. But we can define hours on a working day in suretrack even when our planning unit is day.
Member for
20 years 10 months
Member for20 years10 months
Submitted by Andrew Flowerdew on Wed, 2006-08-02 10:32
I agree it does beg the question of why two different types of software are being used - it isnt always stated in the contract what to use and I guess as P3 and Suretrak are compatible as such, maybe the Engineer thinks hes saving some money.
Irrespective of the software, my suspicion is the Engineer thinks doing what hes doing will reduce the EoT duration.
Member for
19 years 7 months
Member for19 years7 months
Submitted by Karim Mounir on Wed, 2006-08-02 10:16
how come the contractor and the engineer uses 2 software for planning and monitoring the same schedule?, u have to revert to the contract and use the software which is stated their in the first place.
after that u can go back to the APPROVED baseline and implement your CURRENT situations on it for an EOT (this may include change in calender for example work for more hours or delete some holidays).
Member for
20 years 10 months
Member for20 years10 months
Submitted by Andrew Flowerdew on Tue, 2006-08-01 13:04
Dont know what conditions of contract you are working under but for a guess the wording that empowers the Engineer to give an EoT says something along the lines of "at the discetion of the Engineer...." or "in the opinion of..." or "as he sees fit...." ie, the Engineer can use his discetion in making the assessment as long as what he produces is a fair and reasonable assessment.
He would have to have a good reason for his chosen method of assessment and theres nothing to stop you asking for an explanation of those reasons. If they are likely to prejudice the result then you can challenge his assesment as unfair and or unreasonable.
Member for
20 years 6 months
Member for20 years6 months
Submitted by Puneet Gupta on Tue, 2006-08-01 12:53
Well in the baseline schedule,there was no shifts and planning units were days only....everything was planned on 24 hours basis.
But then duration lost was in hours . so the whole night shifts were lost for a good period of time. that means half day lost.
We adopt a method of two consecutive non-working night shifts as 1 complete non working day (half shift + half shift = 1 days lost)and defined it as a non working day in software for the baseline schedule and impacted it. As in the baseline schedule planning units were days.
Now engineer changed the calendars and still considering planning units as days but defining non-working hours in a day.
My question is ...Is it fair on engineer side to change the calendars (Into Hourly calendar) of baseline schedule while considering EOT.
Again the baseline schedule is a contractual document, and my understanding is that , Engineer cannot change it until and unless it has some logical error.
Thanks
Member for
20 years 10 months
Member for20 years10 months
Submitted by Andrew Flowerdew on Tue, 2006-08-01 12:24
A good of example of how to complicate something simple!!!
Theres no reason why days / hours arent interchangable as long as they both end up representing the same thing and the two versions are consistent consistent.
Obvious to say, but the first thing to compare are the calendars used in both versions - especially the working day hours and or shift patterns. These should be the same whatever units you are working in.
The baseline programme calendars and working patterns should be used unless there is very good reason not to. eg you decided to change and work a 12hr rather than an 8hr working day - that said, and it is often the case, that a Contractor doesnt use calendars in his programme that properly reflects the actual working hours. If this is the case you will have to argue that hours are inappropriate and that days should be used as the overall duration of activities was calculated for example a 12hr day rather than the 8hr default setting of the software.
Member for
20 years 10 monthsRE: EOT Planning Unit
Puneet,
Not necesarily, but I would guess theres either one or two other clauses dealing with an assessment at the completion date and possibly one dealing with a final assessment at some point after completion. For another guess, both use similar wording and are Cls 44(4) and (5).
Member for
20 years 6 monthsRE: EOT Planning Unit
Mr. Andrew
I think you have a point here.
Clause 44.3 for Interim determination of Extensions says....
"Engineer shall review all the circumstances and shall determine an overall EOT in regard to the event"
Does this means he can be retrospective???
Member for
20 years 10 monthsRE: EOT Planning Unit
Puneet,
You have added one critically important point - the analysis is being done retrospectively.
The analysis should be carried out (retrospectively or prospectively) in accordance with the contract but this is especially relevant when the analysis is retrospective.
The wording of your EoT clauses will be all important, particularly any interim clause EoT assessment.
Your entitlement to an EoT will have accrued at some point during the contract (assuming youre entitled to one!) and it could be that the state of the Engineers knowledge at the time your entitlement accrued is what is relevant and what he should be basing his assessment on, not what he knows now.
Member for
20 years 6 monthsRE: EOT Planning Unit
Thanks Mr. Karim
Actually engineer approach while determining EOT is retrospective. He has not giving us EOT yet. So we were fast in our work to avoid LDs. We even worked in monsoon though we were not supposed to work in monsoon. But that was all our risk.
So Engineer is now saying that as we worked in monsoon on that activity so he will not consider monsoon calendar for that activity.
Also on one activity which ( yet to execute) is driving my project completion date ,he is saying this activity can be done in dry season.
Yeah i got your point , and i am thankful to all of you for sharing your knowledge and experiance here.
Member for
19 years 7 monthsRE: EOT Planning Unit
Puneet
I think point 3 is a very good support for you in the claim, i think u are entitled for an additional cost and also for an EOT.
u will do more precautions to work in the monsoon season rather than working in the dry season.
Also it is logic for me to have more time doing the required work due to this weather conditions thus affecting the completion date of the project.
I do not figure out how can the engineer avoid this in judging the EOT.
Member for
20 years 10 monthsRE: EOT Planning Unit
Richard,
I also think Puneet said at the beginning of this thread that the programme was an actual contract document, if so theres no doubt that the Engineers alterations constitute variations.
Member for
20 years 10 monthsRE: EOT Planning Unit
Richard,
Yep, totally agree - it would appear hes trying to be clever in order to award the minimum EoT but I think his cleverness might come back to bite him.
Member for
20 years 10 monthsRE: EOT Planning Unit
Richard,
They might even have a claim for full prolongation and an EoT, just depends on the definition on completion. Which would be nicely ironic, the Engineer reduces the EoT by excluding an activity and then has to give an EoT for his instruction to exclude the activity!
Member for
20 years 6 monthsRE: EOT Planning Unit
Yesss Mr. Andrews
You are absolutely right that will be our next claim.
Regards
Member for
20 years 10 monthsRE: EOT Planning Unit
Puneet,
I generally agree with your thoughts - however, the changes made by the Engineer, should he wish to stick to them, will almost certainly amount to a instructed variation entitling you to claim for them, eg, additional costs of carrying out works in the monsoon season. They may even amount to an instruction to accelerate.
Have a think about the changes the Engineers made in this context.
Member for
20 years 6 monthsRE: EOT Planning Unit
Thanks Mr.Andrews for giving me your opinion
1. Well Engineer is not changing the baseline duration.
Let me give more explaination on this. We have defined baseline schedule on the day basis & considering 1 day is equal to 24 hours. so if any of my activity has FS relationship then if predecessor finishes on say 1 Jan 06 its successor starts on 2 Jan 06. Now when in his determination of EOT he has defined hours in a day and most of the lost is in hours say 2 hours of working in a day and rest 22 hours lost on 1 jan 06. So my predecessor activity finishes on say 2 jan 06 and the successor activity can start on same day i.e 2 jan 06 ( as predecessor consumed 2 hours on 1jan 06 and 22 hours on 2 jan 06 so in remaining 2 hours of 2 jan 06 i can start my successor). Well some how this approach of engineer is acceptable to me. But the way he defined the hours in the software is not acceptable to me. As i already mentioned by default in suretrack a day consists of 8 hours and our 1 working day is equal to 24 hours. While defining the non working hours Engineer need to be more careful. I am working on making his assessment to make it more accurate and will let you know my results soon.
2.Well on as-built logic approach, i have the understanding that schedule belongs to contract he can change the as-planned logics to meet the key dates, but engineer can not do that as for determining EOT we are using as-planned as-impacted approach. This appraoch we are using to see the impact of culpable events on as-planned schedule. Is my understanding correct here????
3. Well he changed the planned monsoon calendar by saying that this activity can be done in monsoon. while in our contractual (baseline) schedule it was planned to do this activity in dry season only. He is doining so as this activity is driving the project completion date , so just by changing the calendar he is reducing EOT by a good time.
4. The same activity as mentioned in point 3 is linked with my project completion date, and he is deleting this relationship by saying that we can do this even after project completion and during de-mobilization. Again he is saving project EOT by a good time.
Can we change the Planned schedule logics (as long as there is no logical error in them) in As-Planned-As-Impacted approach???
Member for
20 years 5 monthsRE: EOT Planning Unit
Hi Puneet,
Is this working 24 hours double shift in your contract.
Just want to know....cause its intresting have case like this.
Member for
20 years 10 monthsRE: EOT Planning Unit
Puneet,
1. If hes changing the shift pattern such that the original baseline activity durations are reduced then were back to the argument that the overall duration of the baseline activities were based on the shift patterns actually worked rather than on the calendar settings of the software. He shouldnt be altering any baseline activity duartions unless it is a known fact to him that the baseline durations were based on say an 8hr day and you actually chose to work a 12hr day. That said, even if it that is the case, the productivity obtained between an 8hr and 12hr working day is not a direct relationship and cannot be simply interchanged without consideration of the extra hours worked in terms of its affect on the workforce - fatigue, etc.
2. It isnt unreasonable for him to take account of the as built logic, ie reflect the situation as it actually is on site at the time of making his assesment. His changes must follow the correct logic however and the result properly reflect the state of the site.
3. I would ask him to confirm in writing all changes made to the baseline logic/calendars but especially this one - or if you are aware of all the changes then confirm them to him in writing. Is the change is reasonable in the circumstances is the best answer I can give you without knowing more. It sounds doubtful to me unless he has a crystal ball to predict the monsoons.
4. Ask for his written instruction (or confirm to him) to do this item of work after mobilisation and confirm that it will not affect the issue of the completion certificate prior to this work being started (if thats the case) - or that he wants you to do the work in the defects correction period. Then when hes given the instruction claim prolongation/EoT for the instruction. Cant really be precise on this one without knowing more about the programme but I hope you have the idea - the jist of the answer is that if he choses to change the logic and dictate your sequence of work then theres probably a way to make him pay for it!!!!!!!!!!
Member for
20 years 6 monthsRE: EOT Planning Unit
Yeah engineer is trying to reduce the EOT.
His approach is
1. He changed the schedule into shift basis. Shifts were not defined in the baseline schedule.
2. He resequnced the activities by saying that as per the as-built logic. However there was no logical error in baseline schedule.
3. He is changig monsoon calendar of few activities to non-monsoon calendar. Can he really do that??? i mean can he change the planned calander.
4. Finally one activity which is driving project completion date, he is saying that project completion is not affected by this activity as we can execute it even during the time of mobilization. Yes we can do it after mobilization, but is he not changing the planned logical sequence without any logical error in them.
And giving us a new reduced date.
Please keep giving your expert comments on above mentioned points.
Thanks
Member for
20 years 6 monthsRE: EOT Planning Unit
Hello Mr Karim
Mr. Andrews is right, P3 & Suretrack are compatible.
In our contract they listed software is Primavera & version suretrack.
Engineer is using Suretrack and we are using both suretrack and P3.
So engineer approach is valid only in suretrack as we cannot define hours in a working day when our planning units are days in P3. But we can define hours on a working day in suretrack even when our planning unit is day.
Member for
20 years 10 monthsRE: EOT Planning Unit
Karim,
I agree it does beg the question of why two different types of software are being used - it isnt always stated in the contract what to use and I guess as P3 and Suretrak are compatible as such, maybe the Engineer thinks hes saving some money.
Irrespective of the software, my suspicion is the Engineer thinks doing what hes doing will reduce the EoT duration.
Member for
19 years 7 monthsRE: EOT Planning Unit
how come the contractor and the engineer uses 2 software for planning and monitoring the same schedule?, u have to revert to the contract and use the software which is stated their in the first place.
after that u can go back to the APPROVED baseline and implement your CURRENT situations on it for an EOT (this may include change in calender for example work for more hours or delete some holidays).
Member for
20 years 10 monthsRE: EOT Planning Unit
Puneet,
Dont know what conditions of contract you are working under but for a guess the wording that empowers the Engineer to give an EoT says something along the lines of "at the discetion of the Engineer...." or "in the opinion of..." or "as he sees fit...." ie, the Engineer can use his discetion in making the assessment as long as what he produces is a fair and reasonable assessment.
He would have to have a good reason for his chosen method of assessment and theres nothing to stop you asking for an explanation of those reasons. If they are likely to prejudice the result then you can challenge his assesment as unfair and or unreasonable.
Member for
20 years 6 monthsRE: EOT Planning Unit
Dear Mr. Andrew
I read your post again and i think i got my answer in your post.
Thanks but still if you have some comments on my second post please do give your expert comments.
Member for
20 years 6 monthsRE: EOT Planning Unit
Thanks Mr. Andrew
Well in the baseline schedule,there was no shifts and planning units were days only....everything was planned on 24 hours basis.
But then duration lost was in hours . so the whole night shifts were lost for a good period of time. that means half day lost.
We adopt a method of two consecutive non-working night shifts as 1 complete non working day (half shift + half shift = 1 days lost)and defined it as a non working day in software for the baseline schedule and impacted it. As in the baseline schedule planning units were days.
Now engineer changed the calendars and still considering planning units as days but defining non-working hours in a day.
My question is ...Is it fair on engineer side to change the calendars (Into Hourly calendar) of baseline schedule while considering EOT.
Again the baseline schedule is a contractual document, and my understanding is that , Engineer cannot change it until and unless it has some logical error.
Thanks
Member for
20 years 10 monthsRE: EOT Planning Unit
Puneet,
A good of example of how to complicate something simple!!!
Theres no reason why days / hours arent interchangable as long as they both end up representing the same thing and the two versions are consistent consistent.
Obvious to say, but the first thing to compare are the calendars used in both versions - especially the working day hours and or shift patterns. These should be the same whatever units you are working in.
The baseline programme calendars and working patterns should be used unless there is very good reason not to. eg you decided to change and work a 12hr rather than an 8hr working day - that said, and it is often the case, that a Contractor doesnt use calendars in his programme that properly reflects the actual working hours. If this is the case you will have to argue that hours are inappropriate and that days should be used as the overall duration of activities was calculated for example a 12hr day rather than the 8hr default setting of the software.