Work Breakdown Structure (WBS) Development

How to Control Project with Primavera P6 1. Set Up the Baseline (Foundation of Control) Project control starts before execution. Key actions: Build a logic-driven schedule (FS relationships, minimal constraints) Define: WBS (clear, control-oriented) Activities (measurable, ≤ 10–15 days where possible) Calendars (work, shutdowns, shifts) Resources & costs (if using cost control) Save a Baseline 👉 Project → Maintain Baselines → Add → Assign 📌 Without a baseline, Primavera cannot measure performance. 2. Set Up Control Structure To control effectively, align Primavera with how the project is managed. Recommended setup: WBS → Management control level Activity Codes → Area, discipline, subcontractor, phase OBS + Responsible Manager → Accountability Steps / Physical % Complete → Accurate progress measurement 3. Progress Updating (Weekly / Monthly) This is the core of project control. Update cycle: Set Data Date Update: Actual Start / Actual Finish Remaining Duration % Complete (prefer Physical %) Record: Issues Changes Delays 🚫 Avoid updating by only entering % complete without logic review. 4. Schedule Recalculation & Logic Review After updates: Run Schedule (F9) Check: Open ends Out-of-sequence activities Negative float Excessive constraints 📌 A bad logic schedule = misleading control results. 5. Monitor Key Control Metrics Use these indicators every reporting period: Schedule control Total Float Critical Path SPI (Schedule Performance Index) SPI = EV / PV Cost control (if resource-loaded) Planned Value (PV) Earned Value (EV) Actual Cost (AC) CPI (Cost Performance Index) CPI = EV / AC 6. Variance Analysis (Control Action) Compare Current Schedule vs Baseline: Analyze: Start / Finish Variance Duration Variance Float consumption Critical path changes Ask: What changed? Why? Who is responsible? What is the recovery plan? 📌 Primavera shows the problem — management decides the action. 7. Forecasting & Recovery Planning Use Primavera to look ahead, not only backward. Tools: Remaining Duration trends Finish date forecast What-if scenarios (Copy project → simulate recovery) Schedule compression: Fast-tracking Crashing Logic resequencing 8. Reporting for Management Create consistent reports: Typical reports: 2–4 week look-ahead Critical activities list Milestone trend analysis Delay & impact report S-Curve (PV / EV / AC) 📌 Management wants decisions, not raw data. 9. Change & Claim Control When scope or delays occur: Log changes Update current schedule only Preserve baseline Use fragnets to analyze time impact Primavera is widely used for delay analysis & claims because of this. 10. Best Practices Summary ✔ One update cycle (weekly or monthly) ✔ One responsible owner per activity ✔ No unnecessary constraints ✔ Baseline never overwritten ✔ Control focuses on future risk, not past blame Typical Primavera Control Workflow Plan → Baseline → Update → Analyze → Forecast → Correct → Report

🔧 How to Structure a Mechanical Maintenance WBS for a Gas Compressor Plant (#Oil & #Gas) with a Focus on Resource and Performance Control? Success in a plant turnaround isn't just about the schedule: it all starts with a proper breakdown of the work. 🎯 Here’s how I structure a WBS focused on control for maintenance projects involving critical rotating equipment such as compressors and gas engines. 📐 WBS – Mechanical Maintenance Gas Compressor Plant (Structure focused on progress, cost, and resource control) #Level 1: General Maintenance – Gas Compressor Plant   └── #Level 2: Mechanical Discipline     └── #Level 3: Equipment       ├── Compressor 1 (Ariel, Dresser, etc.)       │  └── #Level 4: Activities       │    ├── Visual Inspection       │    ├── Disassembly & Cleaning       │    ├── Seal / Bearing Replacement       │    ├── Assembly & Alignment       │    └── Functional Testing       └── Gas Engine 1 (CAT, Waukesha, etc.)         └── Similar Activities 📊 How are performance and resources calculated? Performance per activity: Based on historical CMMS data (SAP, Maximo) or manufacturer manuals. #Example: Mechanical seal replacement → 6 hours/man Complete disassembly of Ariel JG compressor → 18 hours/man 🛢️ Resources per activity: Assigned by specialty and crew: 🛢️ Rotating Equipment Mechanics Alignment Technicians Specialized Supervisors Auxiliary Equipment: Cranes, hydraulic jacks, torque tools 🛢️ Resource Curve: The WBS generates resource spreadsheets (by discipline and shift). These can be integrated into P6 or Excel to create resource load curves and histograms. 📊 📈 Derived KPIs: ✔️ Physical Progress % vs. Scheduled Progress by Equipment 📊 ✔️ Man-hours consumed vs. estimated 📜 ✔️ Downtime by Equipment 📈 ✔️ Rework Index (if applicable) 📈 ✔️ Expected availability post-maintenance 📊 💡 Conclusion: A well-defined WBS structure not only organizes the scope but also helps you anticipate deviations, optimize execution, and deliver reliable results. Have you ever had to structure critical maintenance in compressor plants? What methodology do you apply? #PlanningEngineer #OilAndGas #WBS #MaintenancePlanning #RotatingEquipment #PrimaveraP6 #ProjectControls #MechanicalEngineer #GasCompressorPlant #KPI #PredictiveMaintenance #SAP #Maximo

Workflow for a Project Control Engineer to perform effectively in controlling schedule, cost, and performance 🔹 1. Kick-off & Scope Definition Define WBS, OBS and project deliverables. Set the level of detail (LoD) 1-3 days Establish baseline schedule and budget 🔹 2. Build Control Structure Develop the schedule with logic ties, resources, and coding system. Create cost accounts per WBS element. Save and approve the baseline in Primavera, MS Project, or SAP. 🔹 3. Data Integration Daily reports (progress, manpower) Timesheets, procurement data HSE and QA/QC updates 🔹 4. Progress Measurement Physical % complete Earned Value (EV) Quantity-based progress reporting frequency (daily site input, weekly review). Validate reported progress with evidence — photos, inspection reports 🔹 5. Schedule & Cost Update Actual Start/Finish dates Percent Complete Actual Cost Recalculate (reschedule) Avoid unnecessary changes to baseline logic. 🔹 6. Performance Analysis (EVM & Schedule) Calculate Earned Value (EV), Planned Value (PV), and Actual Cost (AC). key indices: SPI = EV / PV CPI = EV / AC 🔹 7. Forecasting Estimate final cost and completion: EAC = AC + (BAC - EV) / CPI ETC = EAC - AC Forecast completion date using revised schedule. Present recovery or mitigation plan 🔹 8. Change Control Record all scope or budget changes through a formal process (RFC / CCB). Update baseline only after approval. Maintain a change log showing impact on cost & time. 🔹 9. Risk & Issue Management Maintain a risk register with probability, impact, owner, and mitigation plan. Quantify schedule and cost impact of each risk. Review and update risk register regularly (weekly or monthly). 🔹 10. Reporting & Communication Daily: short update Weekly: detailed progress + EVM report (SPI, CPI, variance). Monthly: management report with forecast, cost summary, and executive insights. Visuals — S-curves, Gantt charts, and performance dashboards. 🔹 11. Project Close-out As-built schedule Final EAC & variance report Lessons learned Handover documentation Archive all baselines, progress reports, and cost records. 🔹 12. Continuous Improvement Conduct lessons-learned sessions after milestones. Update templates, methods, and automation tools for future projects. 🧩 Typical Deliverables Category Document / Output Planning WBS, baseline schedule, cost breakdown Control Weekly/Monthly progress report, EVM dashboard Risk register & mitigation log Change Change request & approval record Forecast EAC/ETC report, recovery plan Close-out As-built schedule, final report, lessons learned 📅 Routine Activities Daily Site progress capture, update key activities, issue log Weekly Schedule & cost update, EVM analysis, progress meeting Monthly Forecast review, management report, risk update ⚙️ Tools & Best Practices Primavera P6, MS Project, Excel, Power BI, SAP. 📊 Key Formulas SPI EV / PV CPI EV / AC EACAC + (BAC - EV)/CPI VAC BAC - EAC TCPI (BAC - EV)/(BAC - AC)

I was sitting in a WIP meeting with a PM and Superintendent last week. They were reviewing cost to completes and the PM asked about a job. The Super said they were 80% done on a job. The problem was they had burned 95% of the hours. I asked how frequently this happened and they both just kind of looked at each other. They didnt need to answer I already knew. Then I asked: "How are you tracking percent complete against cost used?" Silence again. They did not have a system to track percent complete, and tracking costs vs budget tells you what you've spent. It does not tell you what you've built. When 95% of your hours are gone, are you 95% complete? Maybe. But without a work breakdown Structure(WBS) tied to installed quantities, you don't actually know. By the time you find out you're behind, you're usually too far in to recover the margin. A WBS converts total estimated hours into daily production rates. Devices per day. Linear feet of pipe per crew hour. Square footage of surface prep per shift. It gives the field a number to hit. It gives leadership an early warning mechanism, Not a feeling. A specific, trackable rate that tells everyone whether the job is on track before it's too late. These targets should come from estimating collaborating with the field on prior performance, but they should also be set on what good looks like. Purely setting targets based on historical performance and you're estimating to your own inefficiencies. Set the target based on what good looks like. That's how you stop finding out about problems when your your 80% complete.