Several options depending on how you organised the sturcture of your project.
Option 1 WBS
Imagine you created a wbs code like this
10. Engineering
10.10 Basic
10.10.10 Process flow Diags.
10.10.20 Layout
10.20.30 etc
then you have to attribute to each activity one of this codes.
After, you can create one activity type (example) WBS with code 10.10 - this activity will summarize all activities under code 10.10 .
Option 2
Summarize by layout
in the stucture of your database create the necessary codes for the summary phase you want (Eng. / Procurement / manufacturing / transport / construction / erection / commissioning / etc).
Then sort the activities by phase code and ask to have the summary bar (top or bottom).
Member for
22 years 8 monthsRE: Duration Summary
Jose
You may be left out the third option "Hammack Activity" and this may be one of the best option
Why
WBS you cannot link a relationship to the summary, and it a rigid structure so once setup its very hard to change the level
Code structure in Layout
Yes it is very flexible, but again you cannot link the summary bar with the actual activity.
So my suggestion is depend you need Code structure and Hammack is you best options
HTH
Alex
Member for
20 years 5 monthsRE: Duration Summary
Hello,
Several options depending on how you organised the sturcture of your project.
Option 1 WBS
Imagine you created a wbs code like this
10. Engineering
10.10 Basic
10.10.10 Process flow Diags.
10.10.20 Layout
10.20.30 etc
then you have to attribute to each activity one of this codes.
After, you can create one activity type (example) WBS with code 10.10 - this activity will summarize all activities under code 10.10 .
Option 2
Summarize by layout
in the stucture of your database create the necessary codes for the summary phase you want (Eng. / Procurement / manufacturing / transport / construction / erection / commissioning / etc).
Then sort the activities by phase code and ask to have the summary bar (top or bottom).
I hope to have been of any help.
BR
JMFrade