Ignore the advice about trying to plan in detail work you don't have access to information about - a detailed schedule needs input from the people doing the work - all you end up with is esoteric rubbish.
Mike, using rolling wave we plan the whole project in less details than nearest 3 months. Of course we plan finish date and total cost and apply risk simulation.
Like level 3 schedule for the whole project and level 4 or 5 schedule for nearest three months. I don't approve using several schedules (Level 2, Level 3, Level 4, etc.) for the same project, but one schedule may have different level of details at different parts.
we use Rolling Wave planning at the projects of that duration.
30000 activities is not a problem but it does not make sense to describe in details activities of the future years. Changes are inevitable and we manage the schedule with different levels of detail at different parts.
Usually the schedule is most detailed in the coming three months with much less detailed in the future periods.
At least once in a month the schedule is developed further to keep the same 3 months detailed period ahead.
But if the detailed schedule is already developed I do not see much problem in its maintainence. Actual information that shall be entered is the same. Only changes in future periods may take a lot of time and effort if need creating of detailed model. If these changes are frequent use Rolling Wave.
Member for
24 years 9 monthsA more sophisticated approach
A more sophisticated approach to rolling wave is at http://www.mosaicprojects.com.au/WhitePapers/WP1016_Schedule_Density.pdf
Ignore the advice about trying to plan in detail work you don't have access to information about - a detailed schedule needs input from the people doing the work - all you end up with is esoteric rubbish.
Schedule levels are outlined at: http://www.mosaicprojects.com.au/PDF/Schedule_Levels.pdf
Member for
24 years 8 monthsMike, using rolling wave we
Mike, using rolling wave we plan the whole project in less details than nearest 3 months. Of course we plan finish date and total cost and apply risk simulation.
Like level 3 schedule for the whole project and level 4 or 5 schedule for nearest three months. I don't approve using several schedules (Level 2, Level 3, Level 4, etc.) for the same project, but one schedule may have different level of details at different parts.
Member for
19 years 10 monthsHi VladimirUsing a rolling
Hi Vladimir
Using a rolling wave you have no clear idea what the end date is likely to be.
Best regards
Mike T.
Member for
24 years 8 monthsHi Morne,we use Rolling Wave
Hi Morne,
we use Rolling Wave planning at the projects of that duration.
30000 activities is not a problem but it does not make sense to describe in details activities of the future years. Changes are inevitable and we manage the schedule with different levels of detail at different parts.
Usually the schedule is most detailed in the coming three months with much less detailed in the future periods.
At least once in a month the schedule is developed further to keep the same 3 months detailed period ahead.
But if the detailed schedule is already developed I do not see much problem in its maintainence. Actual information that shall be entered is the same. Only changes in future periods may take a lot of time and effort if need creating of detailed model. If these changes are frequent use Rolling Wave.
Member for
19 years 10 monthsHi Morne - Welcome to
Hi Morne - Welcome to planning planet.
I agree with you that the large number of tasks would be un wieldy.
Also you do need to link up all the sections so that problems on one section will reflect on others that are affected.
My advice is to start again with a clean sheet. Keep it simple.
From my very limited experience of mining you start with a vertical shaft and then the horizontal tunnels - what could be simpler?
Of course there are complexities particularly with health and safety but unless they are driving factors they can be covered by hammocks.
It is unlikely that there will be a critical path unless it is resource driven.
I hope that helps a bit.
Best regards
Mike Testro