Ideally, you should never develop WBS on your own. It should always be a team effort corresponding to concerned disciplines or specialties. Like for example: You were asked to develop a process flow diagram when you were never a process engineer. So how could you be able to do that? However, reality in construction projects is so difficult to understand or managed. And just ultimately resulting to whatever they can just do best and fast (even copying other works that were totally different from what they intend to do), only to satisfy some stupid contract requirements or not defaulting the contract. So still wondering why most construction projects (if not all) fail? Or always spending beyond budget and always late?
Ideally, you should never
Ideally, you should never develop WBS on your own. It should always be a team effort corresponding to concerned disciplines or specialties. Like for example: You were asked to develop a process flow diagram when you were never a process engineer. So how could you be able to do that? However, reality in construction projects is so difficult to understand or managed. And just ultimately resulting to whatever they can just do best and fast (even copying other works that were totally different from what they intend to do), only to satisfy some stupid contract requirements or not defaulting the contract. So still wondering why most construction projects (if not all) fail? Or always spending beyond budget and always late?
hi,Simple WBSEnggineering
hi,
Simple WBS
Enggineering
> Submissions (Drwgs)
> Review and Approval (Drwgs)
Procurement
> Submissions (Material/Technical)
> Review and Approval (Material/Technical)
> P.O
> Fabrication/Manufacturing Cycle
> Onsite Deliveries
Hi . I Need WBS for EPC
Hi . I Need WBS for EPC Project
A raw example (curtailed
A raw example (curtailed version) of a typical FPSO project WBS may look like
PHASES
Milestones,Management
Engg, Proc, Const
WORK PACKAGES
Vessel
Topsides & Process
Turret & Mooring
Subsea system etc
AREA/MODULES
Gas Compression
Polishing
K O Drum
Power Generation / LocEqpRm
Utilities
Helideck
DISCIPLINES
SMP E&I
MISC
Project Name
Milestone
Project Management
Statuary Approvals
ENGINEERING
client deliverables
Detailed dwg development & Approvals
QC documents
PROCUREMENT
CONSTRUCTION
Completion & COMMISSIONING
Load-out / Handover
Just for the sake of
Just for the sake of emphasis, your WBS for engineering and procurement in a typical Oil and gas environment may look like this:
(1) Process, Mechanical, E & I Design
(2) Location (pipe racks, Flare, inlet manifolds, utility area,etc)
(3) Work items (pipes, KOD, Tank, heaters Pumps, valves, etc)
(4) Deliverables(P&IDs, Plot plans, Isometrics, etc)
Procurement
(1)Discipline ( Civil/structural, M&E, Instrument)
(2) categories ( local, Foreign)
(3) Shipment (Discuss methology & procurement sequence with experts in procurement Dept)
(4) Work item (equipment, valves, pumps, specialists of diff trades).
Note that process leads in engineering while Civil structural activities take precedence in most construction activities.
Regards
Ujam
wbs = work breakdown
wbs = work breakdown structure. the clue is in the name. How do your engineering & procurement departments breakdown their work?
They might break it down like the following example, they might not. Speak to them to find out
1) Engineering
2) Discipline (civ, mech, elec, etc)
3) Sub-discipline (groundworks, paving, buildings, etc)
4) Area / workfront / whatever you call it
5) Deliverable type (calcs, drawing, survey, etc)
1) Procurement
2) Discipline
3) Procurement Item (rebar, piling contractor, etc)