One other caution. Dont use Hammock activities under the WBS structure. That is: remove WBS codes from hammock activities.
Ive noticed when you organise by WBS that some Hammock activities dont appear (depsite filtering all activities) and that these hidden hammocks can throw out the WBS activitiy type.
Solution is, to orgranise by Activity Codes (rather than WBS) and then Filter all Hammocks, and null their WBS codes. Then re-organise by WBS structure and the WBS bars should better reflect the dates.
I had a similar problem with WBS bar extending till the end of the project.
It took me quite some time to discover why till I found it:
The hammocks had also a WBS code - I removed the code from the Hammock and the problem was solved, with the WBS bar showing the correct duration of contained activities.
I hope it helps.
BR
JMFrade
Member for
20 years 3 months
Member for20 years3 months
Submitted by Hannes de Bruyne on Wed, 2006-09-13 08:36
Although they could not solve the problem, thank you for first answers. Each idea is very welcome.
= The linking of the hammocks is checked more than once by several people. Normal Early Finish does not give this problem only Actual Finish. We checked this problem with 2 persons, each having about 10 yrs of experience with P3. Of course this does not mean that we are perfect, but I think most common errors such as wrong linking are recognized.
= Yes, I prefer WBS as well. The whole project works with WBS-Code and WBS-Bars. But in this case a hammock (for piling activities) combines 4 normal activities beeing in different WBS-Groups all around the project. I.e. that no WBS-Bar can combine those activities, only a hammock.
Member for
20 years 6 months
Member for20 years7 months
Submitted by Zhang Haixiang on Tue, 2006-08-29 22:09
I prefer use WBS instead of hammock. you do not need to link it to other activities with logic, and you do not need to worr y about out-of-sequence when updating the schedule
Member for
22 years 10 months
Member for22 years10 months
Submitted by Ronald Winter on Tue, 2006-08-29 09:58
This ‘error’ is usually the result of improperly relating the hammocks. Check to see that all hammock predecessors are Start-to-start and than all successors are Finish-to-finish. Improperly coded hammocks default to starting on the data date and finishing on project completion. Good luck!
Member for
20 years 6 monthsRE: Error in WBS-Bar ???
One other caution. Dont use Hammock activities under the WBS structure. That is: remove WBS codes from hammock activities.
Ive noticed when you organise by WBS that some Hammock activities dont appear (depsite filtering all activities) and that these hidden hammocks can throw out the WBS activitiy type.
Solution is, to orgranise by Activity Codes (rather than WBS) and then Filter all Hammocks, and null their WBS codes. Then re-organise by WBS structure and the WBS bars should better reflect the dates.
Member for
20 years 5 monthsRE: Error in WBS-Bar ???
Hello Hannes,
I had a similar problem with WBS bar extending till the end of the project.
It took me quite some time to discover why till I found it:
The hammocks had also a WBS code - I removed the code from the Hammock and the problem was solved, with the WBS bar showing the correct duration of contained activities.
I hope it helps.
BR
JMFrade
Member for
20 years 3 monthsRE: Error in WBS-Bar ???
Thank you
I think you mean Solution ID 1999324103355
"WBS-Activities were not designed to summarize "summary type"
This is called the "FIX" for the problem !!!!!!!
Member for
20 years 6 monthsRE: Error in WBS-Bar ???
There is an answer to this on the Primavera knowledgebase.
Member for
20 years 3 monthsRE: Error in WBS-Bar ???
Although they could not solve the problem, thank you for first answers. Each idea is very welcome.
= The linking of the hammocks is checked more than once by several people. Normal Early Finish does not give this problem only Actual Finish. We checked this problem with 2 persons, each having about 10 yrs of experience with P3. Of course this does not mean that we are perfect, but I think most common errors such as wrong linking are recognized.
= Yes, I prefer WBS as well. The whole project works with WBS-Code and WBS-Bars. But in this case a hammock (for piling activities) combines 4 normal activities beeing in different WBS-Groups all around the project. I.e. that no WBS-Bar can combine those activities, only a hammock.
Member for
20 years 6 monthsRE: Error in WBS-Bar ???
Hi,
I prefer use WBS instead of hammock. you do not need to link it to other activities with logic, and you do not need to worr y about out-of-sequence when updating the schedule
Member for
22 years 10 monthsRE: Error in WBS-Bar ???
This ‘error’ is usually the result of improperly relating the hammocks. Check to see that all hammock predecessors are Start-to-start and than all successors are Finish-to-finish. Improperly coded hammocks default to starting on the data date and finishing on project completion. Good luck!