From the description, one gets a clear idea that there were delays for which the contractor was not responsible. However, the Client is very much justified in thinking and assuming that the contractor is obligated to mitigate the delays and the impacts in a prudent manner.
In such a scenario, if the contractor Re-baslines the project without reserving his right to additional time and compensation, he may be forfeiting his rights to any future claims in this connection.
As suggested by other members, the reasons for the delays should be incorporated in the schedule, and if possible, re-sequencing should be done to give client an idea that the contractor has mitigated the delays. This exercise should be complimented with a request of change order for new completion date, and if desired, a request/signal for compensation due to the extended duration.
Note: The completed activities should always remain in the schedule. The schedule should be so maintained that the last update gives the as-built picture of the project.
Regards and hope it helps.
Rashid
Member for
21 years
Member for21 years
Submitted by Philip Jonker on Mon, 2006-07-24 14:51
I have used lately something which I call an interface date register. How it works is that parties agree on handover dates, and these dates are used in the programme as milestones. You can initialy set these as mandatory constraints while the programme is in the development stage, later you can release them, but record the date in your log. You also need to record the notice periods, for items such as mobilisation, site establishment, etc, should the contractor who has to deliver cannot. Should an early warning not be forthcoming within the notice period, and you mobilise, the contractor in default has a problem, and a claim on his hands, unless he can free up other ares, where you can use your resources. It is always in all parties concerneds interest to work together, and commucate.
Member for
20 years 10 months
Member for20 years10 months
Submitted by Andrew Flowerdew on Sun, 2006-07-23 13:59
A couple of possibilities spring to mind but the oriding question is the revised start date a change to the actual contract or a variation of the contract which had the original start date?
If a change to the actual contract then one would hope that in agreeing the revision any additonal costs incurred to date would have been negotiated and form part of that agreement. If so, you could start at the new date with a new baseline programme.
In any other circumstances Id keep the original baseline and use this as the basis for updates.
Member for
20 years 3 months
Member for20 years3 months
Submitted by Jerry Alivio on Fri, 2006-07-21 06:17
For me Base Line schedule had been created and approved by relevant parties, Now if delayed activities happened that base Line schedule should not be change or revise. For my own view what we have to do is to create an up-dated realistic schedule whereby the data input is from the front liner (Construction Group).
Of course we do the Planned schedule, but let the front liner do the comments and incorporate them, at this point we are on the safe mode. And at the same time try to observe the invironment around you where the issue of variation order and claims is on hot pursuite.
Member for
21 years 10 months
Member for21 years10 months
Submitted by shaju varkey on Fri, 2006-07-21 04:10
It all depend on whether you should accept the NEW commencement date! One should think of the effort and overhead spent till date and hence should be careful to accept any revised commencement date as this can eliminate potential claims.
You dont change baseline very often and when you do it, it can be a major variation.
For your case, I think a simple programme update should be sufficient. I would think that you have milstone activity for completion of the "other contractors works". This milestone should be precedessor for your other activities. Now when you update your programme, there will be no progress in the "other contractors works" milestone. Your subsequent activities are delayed. That is the status. You should, of course, make a copy of your updated programme at this stage. You can use it as secondary baseline to compare future performance against it. But until the new updated programme is agreed as the NEW BASELINE which is possible only with contractual variation, you should continue to use the original baseline.
Completed activities should be shown as complete in the update. And even if this update is used as new baseline latter, it is necessary to show those activities as completed.
Member for
20 years 6 monthsRE: Revised Baseline Schedule
From the description, one gets a clear idea that there were delays for which the contractor was not responsible. However, the Client is very much justified in thinking and assuming that the contractor is obligated to mitigate the delays and the impacts in a prudent manner.
In such a scenario, if the contractor Re-baslines the project without reserving his right to additional time and compensation, he may be forfeiting his rights to any future claims in this connection.
As suggested by other members, the reasons for the delays should be incorporated in the schedule, and if possible, re-sequencing should be done to give client an idea that the contractor has mitigated the delays. This exercise should be complimented with a request of change order for new completion date, and if desired, a request/signal for compensation due to the extended duration.
Note: The completed activities should always remain in the schedule. The schedule should be so maintained that the last update gives the as-built picture of the project.
Regards and hope it helps.
Rashid
Member for
21 yearsRE: Revised Baseline Schedule
Hi Guys,
I have used lately something which I call an interface date register. How it works is that parties agree on handover dates, and these dates are used in the programme as milestones. You can initialy set these as mandatory constraints while the programme is in the development stage, later you can release them, but record the date in your log. You also need to record the notice periods, for items such as mobilisation, site establishment, etc, should the contractor who has to deliver cannot. Should an early warning not be forthcoming within the notice period, and you mobilise, the contractor in default has a problem, and a claim on his hands, unless he can free up other ares, where you can use your resources. It is always in all parties concerneds interest to work together, and commucate.
Member for
20 years 10 monthsRE: Revised Baseline Schedule
A couple of possibilities spring to mind but the oriding question is the revised start date a change to the actual contract or a variation of the contract which had the original start date?
If a change to the actual contract then one would hope that in agreeing the revision any additonal costs incurred to date would have been negotiated and form part of that agreement. If so, you could start at the new date with a new baseline programme.
In any other circumstances Id keep the original baseline and use this as the basis for updates.
Member for
20 years 3 monthsRE: Revised Baseline Schedule
Dear Friends,
For me Base Line schedule had been created and approved by relevant parties, Now if delayed activities happened that base Line schedule should not be change or revise. For my own view what we have to do is to create an up-dated realistic schedule whereby the data input is from the front liner (Construction Group).
Of course we do the Planned schedule, but let the front liner do the comments and incorporate them, at this point we are on the safe mode. And at the same time try to observe the invironment around you where the issue of variation order and claims is on hot pursuite.
Member for
21 years 10 monthsRE: Revised Baseline Schedule
Dear,
It all depend on whether you should accept the NEW commencement date! One should think of the effort and overhead spent till date and hence should be careful to accept any revised commencement date as this can eliminate potential claims.
Regards
SV
Member for
20 years 4 monthsRE: Revised Baseline Schedule
Thanks!!
In this case the entire contract is revised with a new start date..
so we have scheduled with the new start date and approved as New Baseline Programme..
Shiva
Member for
20 years 8 monthsRE: Revised Baseline Schedule
You dont change baseline very often and when you do it, it can be a major variation.
For your case, I think a simple programme update should be sufficient. I would think that you have milstone activity for completion of the "other contractors works". This milestone should be precedessor for your other activities. Now when you update your programme, there will be no progress in the "other contractors works" milestone. Your subsequent activities are delayed. That is the status. You should, of course, make a copy of your updated programme at this stage. You can use it as secondary baseline to compare future performance against it. But until the new updated programme is agreed as the NEW BASELINE which is possible only with contractual variation, you should continue to use the original baseline.
Completed activities should be shown as complete in the update. And even if this update is used as new baseline latter, it is necessary to show those activities as completed.