Oracle Primavera P6 is the dominant scheduling tool on major oil and gas capital projects worldwide. But knowing the tool is not the same as knowing how to use it on an actual refinery expansion, offshore platform, or turnaround. This roadmap walks through what oil-and-gas planners actually do with P6.
The 4 project types you will schedule
Oil and gas projects fall into four broad categories, each with different scheduling patterns:
- Capital expansion (greenfield refinery, new offshore platform): 3–7 year duration, 15,000+ activity schedules, multiple EPC contractors integrated into a master programme baseline
- Brownfield modification (unit upgrade, capacity increase): 6–18 month duration, 3,000–8,000 activities, must integrate with ongoing operations and planned shutdowns
- Turnaround / shutdown / outage (T/A): Fixed 15–60 day window, hyperdetailed hour-by-hour scheduling of thousands of interlocked activities, zero tolerance for date slippage
- Wells / drilling programmes: Rolling multi-year programmes with campaign-based scheduling, complex resource sharing across rigs
WBS design for oil and gas
A well-structured oil-and-gas WBS typically has these top-level branches:
- Engineering (broken by discipline: process, piping, instrumentation, electrical, civil, structural)
- Procurement (broken by long-lead vs bulk items)
- Construction (broken by area or unit)
- Commissioning & start-up
- Project management & controls
- Interfaces (with existing plant, with utilities, with client operations)
Common WBS mistakes on oil-and-gas projects:
- Mixing physical structure with functional structure at the top level
- WBS elements too shallow to support meaningful earned value
- No dedicated commissioning WBS branch — activities scattered across other branches
Activity coding for oil and gas
P6 activity codes let you slice the schedule by area, discipline, contractor, unit, or system. On oil-and-gas projects, essential codes typically include:
- Area (Unit 1, Unit 2, Utilities, Interconnecting Piperack)
- Discipline (Civil, Structural, Piping, Electrical, Instrumentation, Insulation)
- Contractor (EPC contractor, subcontractor, client-managed vendor)
- System (fire and gas, HVAC, process control, safety-critical)
- Commissioning system (pre-com, cold com, hot com, PSSR)
Set these codes at project setup. Retrofitting them mid-project is painful.
Resource loading in oil and gas
Oil and gas EPC schedules are typically cost-loaded but not resource-levelled. Reasons:
- Client cares about cash flow (which needs cost loading)
- Resource peaks are managed contractually, not through P6 levelling algorithms
- Levelling in P6 produces schedules that no field construction team will follow
For contract EVM reporting, cost loading tied to physical progress measurement is essential. Physical progress measurement means using deliverable-based rules (e.g. 20% at issue for approval, 40% at issue for construction, 100% at as-built).
Baseline management on oil-and-gas contracts
Long-duration oil-and-gas projects require rigorous baseline discipline:
- BL0 — Original contract baseline. Locked. Never touched.
- BL1–BL5 — Revised baselines after approved change orders. Each linked to the CO reference.
- Monthly current-schedule snapshots — Saved as separate baselines for Windows delay analysis if needed later.
Client teams will ask you to reconstruct "what did the schedule look like at end of March" three years after the fact. If you did not save the baseline, you cannot answer.
EVM on oil-and-gas EPC contracts
Oil-and-gas EPC contracts typically require monthly earned value reporting:
- Budget at Completion (BAC) locked at contract baseline
- Planned Value (PV) rebased if contract change orders are approved
- Earned Value (EV) measured through physical progress rules per WBS element
- CPI < 0.95 typically triggers a formal cost-recovery plan
- SPI < 0.95 typically triggers a formal recovery schedule
Where oil-and-gas planners typically add or lose value
Add value:
- Rigorous WBS + activity coding from Day 1
- Contemporaneous delay documentation (not retrospective reconstruction)
- Deep familiarity with the contract clauses that govern the schedule
- Weekly interface management with the client, EPC contractors, and vendors
Lose value:
- Producing schedules the field cannot follow
- Weak activity coding that prevents useful slicing for management reports
- Silent about slippage until it becomes irrecoverable
- Poor P6 baseline discipline throughout the project
Our Primavera P6 programme is built specifically around oil-and-gas, EPC, and infrastructure delivery contexts. See the P6 curriculum and the EOT planner guide for the delay-analysis complement.