Try to answer your question, when a activity is marked with finished, all the effect of its successor logic is gone. As a result, if you only have one activity then your "Latest finish date" will become project completion date.
Thanks for your answer. I got your E-mail and I will send the schedule in forthcoming days.
Give me some TIME, I am busy with JUN07 Cut-off and I need to put the schedule in the same conditions when that happened. Do not forget that I did some tricks in oreder to get the proper late dates.
Thanks again & nice week
PS: Personally I do not like hammocks. I would rather work with codes for summarizing. Hammocks for me are the unwanted activities.
Your issue on Hammocks summarising float incorrectly is a bit off topic from WBS activities not summarising hammocks correctly, its probably worth creating a separate thread to work that one through.
I would be interested in seeing a test schedule which replicates the problem you have described.
Try adding another activity, outside of your WBS summary, which finnished later than the activities under your WBS summary.
You will find that your WBS activity runs out to the overall completion date, not the completion date of the activities it is suppose to be summarising.
I read all your posts and created a test project & it seems to me that my project works well . my project has 9 activities , 3 task under 1 hammock & 2 task under another hammock & 1 task which is not under any hammock & 1 Wbs activity. all the activities have the same wbs code , i updated it and when the hammocks reach 100% , Wbs Activity works normal.
can u send your project to me , so i see what’s the problem & what’s the difference between my project & yours?
I was searching in all Forum the best “Forum Discussion Category” where I can place my question about Hammocks and I found your topic.
Although, my problem is not related to Hammock and roll up to WBS, I would like to forward my problem to the members to this discussion.
I have created some Hammocks for the purpose of allocating Man-hours and creating the man-hours distribution (based on early/late dates) using a trapezoidal curve.
I did it successfully but some hammocks did not show the proper late finish DATES according to the successors linked to Hammocks. I got some dates out of control.
My solution was to create Milestones with a mandatory finish DATE. I linked all the Hammocks to these Milestones so that the backward calculation of dates (late dates) was done correctly.
sorry, (maybe I just dont understand it); but Ive tried once using rolled-up with costs inputs and it works fine. I think its just a matter of organization, which you dont have to conflict as one function might drive the other.
I think im not qualified to help you, I believe there were lots of authorized persons round here..
The reason I use summary activities instead of rolled up summaries is because I need to record activity data (earned value and actual cost) at a higher level than my detailed schedule.
i suggest that you use rolled-up activities, but some are saying that it doesnt work in calculating exact Free Floats and Total Floats; i just dont have the time to find it myself
you know what? I maybe stupid! but I suppose Ill never use that kind of presentation; Why?; I think its conflicting, you got three (3) driving functions! WBS; Hammocks; and Tasks! and it would be very difficult to organize (at least from my experience). Why not try using Activity Codes? im not sure,.. you know better that I...
I have to admit that its the first time for me to see that kind of demostration/presentation (Test Project that you sent). Im not professionally trained in P3, I just learned it by chance by myself. I usually worked on Activity Codes...but give me time and let me try!
i dont understand what you mean exactly, but I guess youre referring to Activity Codes or coded activities against WBS..you can always roll-up activities to represent a summary but Hammock I guess has different function, it also summarises activities but in a different way I guess.
havent encountered actually, but P3s definition of Hammocks is that: it is to have one predecessor and one successor to define or drive its duration; I guess if the last activity in your WBS ends with the completion date and also serve as the successor activity to your Hammock, then I guess thats where the problem occurs. (but im not sure)
RE: WBS and Hammock Activities
try changing an updated (with actuals)WBS activity into a Hammock, Hammocks overrules actuals!
i dont prefer to use Hammocks or WBS because you can never roll them up! therefore you cannot summarize them!
RE: WBS and Hammock Activities
WBS activities dont summarise correctly if there is a hammock contained under that WBS level.
RE: WBS and Hammock Activities
Hi Brennan
Long time no c
Try to answer your question, when a activity is marked with finished, all the effect of its successor logic is gone. As a result, if you only have one activity then your "Latest finish date" will become project completion date.
HTH
Alex
RE: WBS and Hammock Activities
Brennan,
Fascinating issue. If you can send me the file please to chankc288-88@yahoo.com
Thanks
RE: WBS and Hammock Activities
Hi Brennan,
Thanks for your answer. I got your E-mail and I will send the schedule in forthcoming days.
Give me some TIME, I am busy with JUN07 Cut-off and I need to put the schedule in the same conditions when that happened. Do not forget that I did some tricks in oreder to get the proper late dates.
Thanks again & nice week
PS: Personally I do not like hammocks. I would rather work with codes for summarizing. Hammocks for me are the unwanted activities.
RE: WBS and Hammock Activities
Carmen,
Your issue on Hammocks summarising float incorrectly is a bit off topic from WBS activities not summarising hammocks correctly, its probably worth creating a separate thread to work that one through.
I would be interested in seeing a test schedule which replicates the problem you have described.
Cheers,
Brennan
bwestworth@gmail.com
RE: WBS and Hammock Activities
Hi Ali,
I have forwarded you the test schedule.
Try adding another activity, outside of your WBS summary, which finnished later than the activities under your WBS summary.
You will find that your WBS activity runs out to the overall completion date, not the completion date of the activities it is suppose to be summarising.
Thanks for your assistance with this.
RE: WBS and Hammock Activities
Hi Brennan ,
I read all your posts and created a test project & it seems to me that my project works well . my project has 9 activities , 3 task under 1 hammock & 2 task under another hammock & 1 task which is not under any hammock & 1 Wbs activity. all the activities have the same wbs code , i updated it and when the hammocks reach 100% , Wbs Activity works normal.
can u send your project to me , so i see what’s the problem & what’s the difference between my project & yours?
RE: WBS and Hammock Activities
Hi All,
I was searching in all Forum the best “Forum Discussion Category” where I can place my question about Hammocks and I found your topic.
Although, my problem is not related to Hammock and roll up to WBS, I would like to forward my problem to the members to this discussion.
I have created some Hammocks for the purpose of allocating Man-hours and creating the man-hours distribution (based on early/late dates) using a trapezoidal curve.
I did it successfully but some hammocks did not show the proper late finish DATES according to the successors linked to Hammocks. I got some dates out of control.
My solution was to create Milestones with a mandatory finish DATE. I linked all the Hammocks to these Milestones so that the backward calculation of dates (late dates) was done correctly.
Does anyone have experienced same problem.
Looking forward any comment.
carmen
RE: WBS and Hammock Activities
sorry, (maybe I just dont understand it); but Ive tried once using rolled-up with costs inputs and it works fine. I think its just a matter of organization, which you dont have to conflict as one function might drive the other.
I think im not qualified to help you, I believe there were lots of authorized persons round here..
cheers
RE: WBS and Hammock Activities
The reason I use summary activities instead of rolled up summaries is because I need to record activity data (earned value and actual cost) at a higher level than my detailed schedule.
RE: WBS and Hammock Activities
i suggest that you use rolled-up activities, but some are saying that it doesnt work in calculating exact Free Floats and Total Floats; i just dont have the time to find it myself
RE: WBS and Hammock Activities
you know what? I maybe stupid! but I suppose Ill never use that kind of presentation; Why?; I think its conflicting, you got three (3) driving functions! WBS; Hammocks; and Tasks! and it would be very difficult to organize (at least from my experience). Why not try using Activity Codes? im not sure,.. you know better that I...
cheers
RE: WBS and Hammock Activities
I have to admit that its the first time for me to see that kind of demostration/presentation (Test Project that you sent). Im not professionally trained in P3, I just learned it by chance by myself. I usually worked on Activity Codes...but give me time and let me try!
cheers
RE: WBS and Hammock Activities
I hope that test file I emailed you demonstrates the problem clearly.
RE: WBS and Hammock Activities
if you got spare one for me in Australia, then why not?
i can find out what exactly your problem is (if you dont mind)
RE: WBS and Hammock Activities
P3 has two summary activity types
- Hammock, which uses logic to summarise
- WBS, which uses WBS Code to summarise
I was using Hammock summary activities within a WBS summary activity and P3 couldnt handle it.
By the way... is there much work going on in Antarctia? :)
RE: WBS and Hammock Activities
i dont understand what you mean exactly, but I guess youre referring to Activity Codes or coded activities against WBS..you can always roll-up activities to represent a summary but Hammock I guess has different function, it also summarises activities but in a different way I guess.
RE: WBS and Hammock Activities
I just created a simple test schedule.
it seems that you can only have WBS OR Hammock activities.
RE: WBS and Hammock Activities
the only thing I can think of is to abandon WBS activities all together and convert them to hammocks.
RE: WBS and Hammock Activities
The hammocks are summarising fine, the problem occurs when a hammock activity, within a WBS level, reaches 100% complete.
RE: WBS and Hammock Activities
havent encountered actually, but P3s definition of Hammocks is that: it is to have one predecessor and one successor to define or drive its duration; I guess if the last activity in your WBS ends with the completion date and also serve as the successor activity to your Hammock, then I guess thats where the problem occurs. (but im not sure)