Hammock

Hello,



Another hint,



If you decide to use Hammocks be sure to link each one with all activities in the group they are summarizing - An Hammock should have all activities in the group as predecessors with SS and all the same activities as successors FF relations.



Also, never put a WBS code in an Hammock. If you do it the WBS activity for such code will show a wrong star/finish dates.



BR

JMFrade

hi guys!



moutaz....may view about this is that



if you have a good activity coding system and WBS you may not need to use HAMMOCK activity..



but sometimes the management requires to see the whole duration of a certain group of activities then it is required to provide a HAMMOCK activity.......and the progress of these group of activities....



you can use this if the activities are in a different coding system.......different groups c",)

I agree with Trevor it should not be used in a detailed schedule where you need to produce updates often. It is can be used on prelimanry schedules where you dont have detailed BOQ and need to quantify RESOURCES.

Hammocks are useful for simulating Level of Effort activities like Management, or Lease, etc.

Leasing some machines you will pay for the whole period until the finish of the last work where they will be used. You will pay even if these machines are not used at some periods.

Hammock activity is usually used for summarizing group of activities, but recently I used it when I wanted a certain activity to start in a specific date and finishes when another activity finishes



(U cant link it Finish to Finish) as you want this activity to be in progress , you don’t want to move the bar but extend it.

I suggest you stay clear of hammock activities - they are primarily designed for compatibility with other software.



With proper activity coding (or WBS) it is possible to better obtain "roll-ups" similar to hammocks

(use Format->Organize menu).



The problem with hammocks is that if the logic changes, unreliable results can be generated. This increases schedule maintenance.



In summary, avoid hammocks if at all possible.



Hopefully this is helpful.



Trevor Lyle

it can be used to summarize a chain of task in a summary layout.But i think WBS is more flexible



it can also be used for high level resource planning, when detail information is not available.



I’ve not used it before