This is a sample WBS Dictionary template that you can use.

Project Name		Date
Project Number		Document Number
Project Manager		Project Owner/Client

JGLOBAL_READ_MORE_TITLE

Both, the Primavera PPM and Primavera EPPM are meant to be used in different environments. Although both share most of their functionalities, each of these software applications have their own use. Let's find out when PPM is preferred and when EPPM may be more suitable.

Uses and Benefits of Primavera P6 EPPM

The EPPM is most suitable when:

1. You have casual scheduling needs.

2. You want to manage programs and portfolios of projects, at a larger level.

3. You want access to your projects data online from anywhere

4. You want to have a centralized resource dictionary for use by all schedulers.

5. You want to manage project risks, issues and documents

6. You want to create reporting dashboards.

Uses and Benefits of Primavera P6 PPM

Also known as Primavera Professional, it is a most commonly used Primavera software. It is most suitable in environments when:

1. You want a tool to update, review, create and analyze project data every day.

2. You want to do basic to advanced or complex level scheduling work.

3. You want a fast and efficient scheduling tool.

4. You want to work with projects offline.

5. You want quick conversions between Primavera/Excel/Project

Further readings recommended for you.

1. Functionalities in Primavera PPM, Not Present in EPPM

2. Functionalities in Primavera EPPM, Not Present in PPM

For a properly prepared WBS (Work Breakdown Structure), the following guidelines provided in PMI's Practice Standard for WBS should be considered during the development of a WBS

● The set of child WBS elements into which a parent element has been decomposed should include all of the work contained in the parent, fulfilling the WBS's 100% Rule.

● A coding scheme should be used for all WBS elements which clearly represents the hierarchical structure of the WBS.

● Decomposition of all parent elements of WBS need not be of the same depth. Some parts of the WBS will need to have less or more detail than others.

● All work packages need not to be at the same level.

● The WBS development process should:

● Be iterative

● Be reviewed as well as revised just as the rest of the project planning process progresses.

● Provide a space for flexibility, specially when the scope of the project effort can change.

When developing a WBS, the following basic principles should be followed:

● Every WBS element represents one intangible or tangible deliverable. Intangible items include information/communication, training, administration, procurement and process management. Tangible elements are like wall, machinery, house, painting, a book, electrical/civil works, etc.

● Deliverables are distinct and unique.

● Deliverables include both interim and final deliverables that are required to create the final desired results.


● All important reporting processes such as weekly/monthly reports, review meetings,  test reports are included in WBS.

● Every project deliverables should so unique, ensuring no duplication in the outcomes of the project or end-products.

● Accountability for each work package should be assigned to a one team member or a subcontractor. In case, this seem impossible, reconsider whether or not
the work package can be further decomposed.

● Every element in WBS representing externally committed or subcontracted deliverables should directly correspond to associating elements in the subcontractor’s WBS.

● Deliverables are logically decomposed to the level that represents how they will be managed and produced.

● All WBS elements should be compatible with company's and accounting structures.


Also read: Guidelines for organizing WBS elements into the WBS hierarchy

Reference: Practice Standard for Work Breakdown Structures