In PLANTA project, work breakdown structure means a project plan in which tasks are structured hierarchically. Not to be confused with the project structure, which describes the division of a project into main and subprojects. This means that every project in PLANTA possesses its own work breakdown structure, regardless of whether it is a main or subproject.
The parent tasks of a structured project plan are called summary tasks in PLANTA project.
The Work break down structure code (WBS code) identifies individual project tasks in accordance with their hierarchical structure.
Where can I structure tasks?
In the Schedule and WBS modules of the required project
You can open the project a) by opening a dialog window via the Extras → Go to menu or via CTRL + G and entering the ID of the required project or b) by clicking on the link on the ID of the required project in any module. Subsequently, click on the Schedule or WBS module tab.
The work breakdown structure is displayed graphically in the WBS module and in table form in the Schedule module.
Who is allowed to structure tasks?
All users who have access to the ScheduleandWBSmodules and have modification rights for projects. These are, in PLANTA standard, managers of the respective project, their deputies, or multi-project managers. For further information on rights, please click here.
Create a Work Breakdown Structure in the Schedule Module
Procedure
Open the Schedule module by clicking on the tab of the same name in the Project panel.
If it is a new project, you will have to create tasks.
Structure the tasks hierarchically as required by moving them to the required position by holding down SHIFT + left mouse button.
Select the Generate WBS code command from the context menu by right-clicking on the project header or by clicking on the Generate WBS code symbol (on the left hand side below the project header).
The WBS code is generated automatically for every task in the WBS Code field in accordance with the structure. Thus, the WBS code is both an identifier for single elements in the schedule and an indicator of the hierarchical structure.
Start the calculation of the schedule by clicking on the Calculate schedule button in the toolbar.
As a result, all parent tasks are marked bold and are therefore visualized as summary tasks.
If changes have been made to the task structure since last updating the WSB codes, the codes are updated as well when the schedule is calculated.
If you have created your project by copying standard schedules, the tasks will already be structured. As a matter of course this structure can be changed as described above.
Create a Work Breakdown Structure in the WBS Module
Procedure
Open the WBS module by clicking on the tab of the same name in the Project panel.
Create the required tasks. They will initially be positioned on one level here.
Structure tasks by left-clicking on the left box margin and dragging the box to the required position.
When the boxes are moved, the specification in the node field, which visualizes the number of boxes per level, will be updated automatically.
Click on the Generate WBS code button (the wheel symbol below the project bar).
The WBS code is generated automatically for every task in the WBS code field in accordance with the structure. Thus, the WBS code is both an identifier for single elements in the schedule and an indicator of the hierarchical structure.
If you have created your project by copying standard schedules, the tasks will already be structured. Of course, the structure can be changed.
If there are less than 10 tasks, the numeration of the codes is done by the 1, 2,... 9 schema, if there are more than 10 tasks, the numeration is done by the 01, 02,... 09, 10, ...
When working with structured projects you have to keep in mind that the generation of a WBS code in the main project causes the generation of the WBS code for all subprojects concerned. The generation of the WBS code in individual subprojects, on the other hand, only has an effect on the respective subproject.
Caution
When working with structured schedules, PLANTA recommends that you use summary tasks as structuring elements only, i.e. you should not carry out effort or cost planning or enter durations on this level. This includes resource planning or time recording directly to the summary task. Instead, PLANTA recommends that you carry out the planning on the child task only.
Reason: Since the scheduling detects some parameters of the summary tasks from child tasks, there may be collisions between your own planned values and those detected by the scheduling. As a result, there may be values on summary tasks that are incomprehensible at first sight.
