Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Activity Code vs WBS field

5 replies [Last post]
P3 Scheduler
User offline. Last seen 19 years 39 weeks ago. Offline
Joined: 16 Feb 2002
Posts: 18
Groups: GPC Malaysia
I noticed how other project controls people in my company organize their activities. Most use the activity code fields (define field like "level" or "phase") rather than use the built-in WBS field in P3. Can someone speak to the pros and cons of different approaches?

Thank you
CS Ong

Replies

Dayanidhi Dhandapany
User offline. Last seen 3 years 4 weeks ago. Offline
Joined: 18 Mar 2003
Posts: 470
Groups: None
Dear Eric,

I’ve gone through your article. I must appreciate your efforts, well done.

Regards

Daya
Eric Chou
User offline. Last seen 41 weeks 1 day ago. Offline
Joined: 19 Jul 2004
Posts: 29
Groups: None
Attached is the write-up by me regarding the Activity Code vs WBS. Please review for your reference. Go to the http://www.htcprojectcontrols.com/TTB2003-9.pdf Also, you may find this is useful regarding Activity Code vs Custom Data Item. Go to the http://www.htcprojectcontrols.com/TTB2003-6.pdf Eric Chou, PE HTC Project Controls, Inc.
Jorge Taguinod
User offline. Last seen 2 years 19 weeks ago. Offline
Joined: 8 Jul 2003
Posts: 139
I think that WBS was developed to help project managers to at least be able summarize large project data. WBS provides only one way to look at the project.

However, with the advent of computerized project management software, PMs dont have to be limited anymore to just one perspective. And P3 uses Activity Codes so that you can slice and dice information in many many ways... by activity codes, project codes, resources, time, float, etc. Imagine if you needed to do this manually?

I would always recommend the use of Activity Codes becauase filtering, grouping and summaryzing, and performing global change is much easier this way... plus the fact that I can view project information in countless perspectives which can be saved in different layouts.

Jorge
Crown Systems (Philippines)
Tara Muddappa
User offline. Last seen 17 years 2 weeks ago. Offline
Joined: 17 Dec 2002
Posts: 26
Groups: None
hi,

The way I view is to have WBS structured the way you build the Job.On the other hand activity coding gives you ample flexibility to view the reports of your choice.
George Hislop
User offline. Last seen 21 years 22 weeks ago. Offline
Joined: 7 Nov 2002
Posts: 9
Groups: None
The WBS code is a useful if the project emphasis will not change. In the Oil and Gas industry the emphasis often swings from geographic breakdown during construction to systems as the commissioning starts (about 70% through construction). In this kind of situation the code fields are more useful as the definition of systems is not always clear early in the project and can evolve during the project life.
Another factor with WBS is that you have to define every element even though it may be repetitive. For example, if you have 40 groups of cabling activities spread over 10 areas you would create 40 unique WBS codes. Using code fields the cabling could be a generic code created only once but shown in each area. The latter option only requires 10 Area codes and 1 Generic Cabling code.
Also worth noting that Resource loading reports in P3 do not allow grouping on the WBS.
I would be interested to hear any other thoughts on this one...