but remember...this what the real function of hammock "An aggregate or summary activity. All related activities are tied as one summary activity and reported at the summary level" and if we doesnt use it...what purposely it is?
Member for
18 years 1 month
Member for18 years1 month
Submitted by Johny Kesserwany on Thu, 2007-10-04 12:29
Im assuming you are working on a petro-chem project?
If you are, why are you using hammocks? Im also in the same game and have advocated that the use of hammocks be banned altogether as projects of this nature demands programme and logic flexibility which hammocking severely restricts.
For example, on a project I was on, the contractor insisted on using hammocks. I got their monthly progress update which showed the end date being pushed out. It took me 2 days to find out why. What happened was that the planner put in a really stupid logic string inside a hammock - a SF relationship with a forced negative float - crazy!
Hammocks are of any value in a conveyor belt or assembly line situation where lower level tasks are repetitive and can be summarised.
My advise to you is - get rid of hammocks entirely in your programme!
You problem is typical of trying to run a programme with hammocks. For summarising tasks, why not just use your activity codes or WBS.
Member for
19 years 5 monthsRE: Hammock Activity
but remember...this what the real function of hammock "An aggregate or summary activity. All related activities are tied as one summary activity and reported at the summary level" and if we doesnt use it...what purposely it is?
Member for
18 years 1 monthRE: Hammock Activity
I totally agree with Andy dont use hammocks!
Jk
Member for
18 years 1 monthRE: Hammock Activity
HI Izam,
you can try this:
TOOLS>OPTIONS>AUTOCOST RULES> adn click on "LINK REMAINING DURATION AND SCHEDULE PERCENT COMPLETE"
then reschedul your schedule
it should automaticali counts the %
Ramil
Member for
23 yearsRE: Hammock Activity
Hi Izam,
Im assuming you are working on a petro-chem project?
If you are, why are you using hammocks? Im also in the same game and have advocated that the use of hammocks be banned altogether as projects of this nature demands programme and logic flexibility which hammocking severely restricts.
For example, on a project I was on, the contractor insisted on using hammocks. I got their monthly progress update which showed the end date being pushed out. It took me 2 days to find out why. What happened was that the planner put in a really stupid logic string inside a hammock - a SF relationship with a forced negative float - crazy!
Hammocks are of any value in a conveyor belt or assembly line situation where lower level tasks are repetitive and can be summarised.
My advise to you is - get rid of hammocks entirely in your programme!
You problem is typical of trying to run a programme with hammocks. For summarising tasks, why not just use your activity codes or WBS.
Good luck