WBS / Activity Codes Utility
Featured Partner
Top Posters
Ashkan Mohammadi
0 posts
Jeroen De Bauw
0 posts
yerukalapudi
1 posts
Senior Planning Engineer
0 posts
Kristian Mcwilliams
1 posts
dagogo dan - jumbo
2 posts
Alex Lyaschenko
27 posts
James Williams
75 posts
xerxes
0 posts
edwin
0 posts
Our Partners
Thanks all for your help especially Dieter.
It helped me to understand my problem.
mh,
I suggest you delete all the data in your existing dictionary (codes, WBS or whatever) and start from scratch. I believe it will only give you a headache reading those codes I presumed you dont understand as well.
Dieter and Alex are right, WBS is easy in P6 (you can write whatever you want), the same thru with activity codes.
Hi All
I believe the biggest different between code and WBS is flexibility
Once a WBS structure is setup, you cannot organise your project in anyother format (Grouping) unless to use code.
As a result, you schedule is very rigid. However, comes to reporting and changing layout and analysis, it becomes a nightmare.
HTH
Regards
Alex
Hi
I dont know of a way to copy codes into a wbs, sorry. How much in detail the wbs must be, for project management or internal regulations? For reporting purpose its better with a big code dictionary.
Regards
Dieter
Thanks for your help Dieter.
Further I have very limited WBS dictionary, but comparatively the activity code dictionary is large. Can I use activity code dictionary to develop the WBS dictionary in this new environment for me or how can I develop the WBS dictionary?
Hi
As project data has to be represented in accounting, financial controlling, strategic planning ... and has to use data from the erp software (Enterprise Resource Planning) especially master data you have to consider a common key that both systems can understand each other. For projects in general data will be accumulated, because financial controlling has an interest for the status of e.g. engineering in total not for a certain document. To make live easier only cumulated data is transferred - by wbs.
Reporting requirements: All stakeholders have a need for information, but grouped in a different way, only specific parts of the project, ... After you gathered these requirements youll assign codes to activities to fulfil all those requirements.
If youll need more specific information, just ask for them.
Regards
Dieter
Thanks for your response Dieter. Is it possible you please explain a little more about "Interfacing with erp-software" with WBS?
What all other reporting requirements we may achieve by codes?
Hi
WBS:
- According to standards
- Interfaces with erp-software and other scheduling in general by wbs
- Not each report group is able to group or to filter by wbs
- Access rights by wbs
- Budget by wbs
- Earned Value parameters by wbs
- Combination of parts of different projects to one project easier
Codes:
- Accessible from (almost) each report group
- Security code
We use both: wbs is standard, related to needs of financial controlling; all other reporting requirements by codes.
Regards
Dieter
Well for me, if using P6, i just go with WBS, if it is P3, I prefer activity codes. I believe both serves the purpose, it only depends upon the user.