Why a Primavera WBS is Important
People converting from P3 and SureTrak will be used to using Activity Codes and Activity ID Codes. Primavera does not have Activity ID codes.
You may be tempted to ignore the WBS and use Activity Codes instead. This paragraph will explain the main purposes of the WBS function:
- User Access may be assigned at this level, so two schedulers may open the same project and one may only change activities in WBS Nodes that have been assigned to that user.
- Earned Value calculations and Project Performance may be measured at this level.
- Progress at the WBS level may be measured with the use of WBS Milestones.
- WBS Activities are very useful as summary activities.
- Anticipated Dates may be assigned at the WBS level to provide a bar when no activities have been added to a WBS Node.
- The Tracking Window operates down to WBS Node level.
- There are a number of standard Reports that function at WBS Node level.
A WBS Node is a term used by Primavera that is often called a WBS Code and is a single point in the WBS structure that activities are assigned to. A Primavera WBS Node may record more information than P3, SureTrak, or Microsoft Project including the following data:
- Anticipated Dates, which are used to create a bar in the WBS Window when there are no activities under the WBS Node, but do not summarize in the Projects Window.
- Notes, which are recorded under Notebook Topics,
- Budget, Spending Plan and Budget Change Log,
- WBS Milestones, which may be used for assigning progress at WBS Node,
- WP & Docs that provide links to documents, and