Hi Yahya,
The work breakdown structure has to be developed from the project scope and deliverables. It is the backbone that maps all project components together and the first and most important step towards having proper controls on the project. Not only for project controls use, but for engineering, project management and construction use.
The project scope & deliverables are the same for engineering, construction, estimating, scheduling ...etc .Therefore, the WBS should be the same across all project disciplines. (i.e: same coding, same structure, same deliverables).
The project WBS structure should be a tree that rolls up & down according to the specific requirements of the discipline; if planning requires a more detailed or a different level of detail than estimating; they need to have that flexibility built in the WBS, so they can go down to the level of detail that allows the proper control the schedule. However; they need to maintain the ability to roll-up to a control level that estimate cost can still be mapped against schedule data to produce a cost loaded schedule for example. The same applies for all project disciplines.
The best (if not the only) way to unify the WBS structure is to develop it from the project scope. I cannot emphasize enough on how important this is.
Regards,
------------------------------
Ghaith Al-Hiyari PMP CCP
Project Controls Lead
SNC-Lavalin
Toronto ON, Canada
------------------------------
Original Message:
Sent: 10-07-2017 06:38
From: Yahya Al-Khatib
Subject: Establishing a proper integrated project control system
Hi all and happy to be with you on board!
We are working on a PMO setup for a set of mega projects. We are building an integrated project management and control system. The general approach is to break up the project into manageable WBS items and each WBS activity will be our reference to assign tasks, monitor progress, allocate resources, costs... etc. Now for creating the WBS, we have two approaches, the first to build the WBS structured towards serving the project planning and the second to create it to be structured towards cost estimation/control. Obviously, the structure in both approaches is different and probably WBS for cost control will be more detailed. If we use planning WBS, we will need to make some manual work to allocate cost items from BOQ. On the other hand, if we use the estimating WBS, we are causing the planner to be involved in unnecessary details that will disturb his schedule. Can I know your suggestions about best WBS structure for project controls?
Note: There is a group of experts working on this issue, but for me I need to know this information for our brainstorming session by next week.
Thank you
YAHYA
------------------------------
Yahya Al-Khatib CEP PSP
Senior PMO planner
------------------------------