I do not know what a DG Sewage Project is but I am assuming that it is not important.
It is easy to calculate the delay for each shaft by impacting the delay event that caused the delay and then comparing with the actual progress.
Unless there is some logic linking the shafts to the completion date then there will be no "knock on" effect from each standalone shaft to the rest of the programme.
So in order to see the effect of float on the Baseline Programme then some realistic logic has to be in place.
This logic could be physical or resource driven or both.
If you are putting it into an already approved programme you will be accused of rigging it.
Member for
14 years 11 monthsHi Mike,Thanks a lot for your
Hi Mike,
Thanks a lot for your valuable reply..
Best Regards,
Sunil
Member for
19 years 10 monthsHi Sunil The same principles
Hi Sunil
The same principles apply no matter who is operating the rigs.
Best regards
Mike Testro
Member for
14 years 11 monthsHi Mike,Thanks once again for
Hi Mike,
Thanks once again for your valuable reply, another problem in in the change of logic is that
there are defferent contractors operating for these rigs and we have to allocate them accordingly
depends on various conditions..
Best Regards,
Sunil.
Member for
19 years 10 monthsHi Sunil So you have 5 rigs
Hi Sunil
So you have 5 rigs deployed on a number of shafts.
So when rig 1 has finished it moves on to shaft 6 and so on.
You should arrange the shafts into groups of 5 and link Shaft 1 to shaft 6 > shaft 2 to Shaft 7 accordingly.
You can also set up rig resources numbered 1 to 5 and allocate them to the appropriate shafts.
Now if - say - shaft 3 is delayed then rig 3 will be late starting shaft 8 and all of rig 3 allocated shafts will be delayed.
However you must be prepared to rearrange (mitigate) the sequencing so Rig 3 could go to shaft 10 and rig 5 drop onto shaft 8 etc.
This is done by adjusting the logic.
Best regards
Mike Testro
Member for
14 years 11 monthsHi Mike,Thanks for your
Hi Mike,
Thanks for your reply, actualy this is a deep gravity sewerage project and the programme
was made based on the logic of rig movements, for example five rigs are in operatin under which
the total shafts are diveded into five groups , Various facts affecting the delay such as
delayed ifc drawings,traffic permits, rig break down, excavation in hard rock etc.
Can you explain further on "knock on effect" based on these factors..
Regards,
Sunil.
Member for
19 years 10 monthsHi Sunil I do not know what a
Hi Sunil
I do not know what a DG Sewage Project is but I am assuming that it is not important.
It is easy to calculate the delay for each shaft by impacting the delay event that caused the delay and then comparing with the actual progress.
Unless there is some logic linking the shafts to the completion date then there will be no "knock on" effect from each standalone shaft to the rest of the programme.
So in order to see the effect of float on the Baseline Programme then some realistic logic has to be in place.
This logic could be physical or resource driven or both.
If you are putting it into an already approved programme you will be accused of rigging it.
Best regards
Mike Testro