How does one check against progress and what baseline(s) are required to be shown to indicate progress/variance etc.?
As Gary says, the baseline should be the last accepted programme that was submitted. However, I have found it useful to utilise 2 baselines in a report, one being the last accepted programme, the other being the previous month/progress period progress. Most software packages will allow you to show at least 2 baselines (some can show more), and you should be able to export & import various baselines from previous progress periods.
In my experience, it is good practice, as the Planning Engineer on a project, to save a defined, native copy of the programme for each progress period, i.e. March, April, May, etc (i.e. 0123 - RevA01 Project Name 130611.<file extension>: Contract No.; Rev No.; Project Name; Date (YYMMDD)).
Yes, this does lead to having a lot of data "lying about", but as the Site Staff keep being reminded by the Commercial Staff, it's all about "Records, Records, Records", especially on NEC Projects.
Once you have saved a copy of the progress period, you can then produce a baseline for that period, as well as producing PDF's for submission as required. For the next progress period, you will then incorporate the previous progress periods baseline (as baseline 2 - baseline 1 being the last accepted programme) in a new/working version of the file.
Assuming that you are working from an Activity Schedule (key sections/areas of the project), you can create a report that not only tracks progress and variance against the last accepted programme, but also track progress and variance from the previous progress period. The reasons for this would be to highlight areas of the project that are doing better/worse than planned. If it's doing better than planned, what's happening in that section that can be brought through to other sections? If it's running behind schedule, then what are the issues affecting progress? Colour coding/traffic light highlighting of the report aids the understanding of it (though expect to explain the report/programme over and over and over again!).
Hope that convoluted answer helps...
Member for
16 years 7 months
Member for16 years7 months
Submitted by Gary Whitehead on Mon, 2013-03-18 08:49
Ideally, you should take the last programme you submitted that was accepted, and update that with progress / changes.
If your programmes are not regularly accepted unchallenged and promptly, this can prove to be a bit tricky to manage.
Bear in mind that any CEs affecting the contractual completion date are calculated based on the most recent accepted programme, hence it is in both party's best interests to keep the programme submission & acceptance cycle running smoothly.
Member for
21 years 8 monthsHow does one check against
How does one check against progress and what baseline(s) are required to be shown to indicate progress/variance etc.?
As Gary says, the baseline should be the last accepted programme that was submitted. However, I have found it useful to utilise 2 baselines in a report, one being the last accepted programme, the other being the previous month/progress period progress. Most software packages will allow you to show at least 2 baselines (some can show more), and you should be able to export & import various baselines from previous progress periods.
In my experience, it is good practice, as the Planning Engineer on a project, to save a defined, native copy of the programme for each progress period, i.e. March, April, May, etc (i.e. 0123 - RevA01 Project Name 130611.<file extension>: Contract No.; Rev No.; Project Name; Date (YYMMDD)).
Yes, this does lead to having a lot of data "lying about", but as the Site Staff keep being reminded by the Commercial Staff, it's all about "Records, Records, Records", especially on NEC Projects.
Once you have saved a copy of the progress period, you can then produce a baseline for that period, as well as producing PDF's for submission as required. For the next progress period, you will then incorporate the previous progress periods baseline (as baseline 2 - baseline 1 being the last accepted programme) in a new/working version of the file.
Assuming that you are working from an Activity Schedule (key sections/areas of the project), you can create a report that not only tracks progress and variance against the last accepted programme, but also track progress and variance from the previous progress period. The reasons for this would be to highlight areas of the project that are doing better/worse than planned. If it's doing better than planned, what's happening in that section that can be brought through to other sections? If it's running behind schedule, then what are the issues affecting progress? Colour coding/traffic light highlighting of the report aids the understanding of it (though expect to explain the report/programme over and over and over again!).
Hope that convoluted answer helps...
Member for
16 years 7 monthsIdeally, you should take the
Ideally, you should take the last programme you submitted that was accepted, and update that with progress / changes.
If your programmes are not regularly accepted unchallenged and promptly, this can prove to be a bit tricky to manage.
Bear in mind that any CEs affecting the contractual completion date are calculated based on the most recent accepted programme, hence it is in both party's best interests to keep the programme submission & acceptance cycle running smoothly.
Member for
19 years 10 monthsHi James The planners from
Hi James
The planners from both sides need to sit together and agree a process that commplies with the contract requirements.
And then follow it.
Best regards
Mike Testro