Insights & Resources
Project management articles, PMP exam tips, Primavera P6 guides, and EPC industry insights from our practitioners.
PMBOK® 7th Edition: Complete Guide for PMP 2025
The PMI Examination Content Outline (ECO) now centers on three domains: People, Process, and Business Environment. The 7th Edition moves away from process groups toward principles — a fundamental shift from prescriptive to principles-based guidance.
What changed: PMBOK® 7th replaces the 49 processes of 6th Edition with 12 Project Management Principles and 8 Performance Domains. This is not a removal of process knowledge — exam questions still test scheduling, risk, cost, and quality — but framed in outcome-based and hybrid contexts.
Exam distribution (2025): People ~42%, Process ~50%, Business Environment ~8%. Approximately 50% of questions are predictive (waterfall), 50% hybrid/agile. You must know both Scrum and traditional CPM scheduling equally well.
- ◆Study the PMBOK® 7th Principle chapters — they appear in situational questions
- ◆Practice 50+ agile scenario questions per week — half the exam is hybrid/agile
- ◆EVM formulas (CPI, SPI, EAC, TCPI) still appear — know them cold
- ◆Read the PMI Code of Ethics — 1-2 questions always appear on ethical dilemmas
- ◆Use the "PMI Way" lens: prefer proactive, stakeholder-first, risk-aware answers
Mastering Baseline Management in Oracle Primavera P6 for EPC Projects
The baseline is the heartbeat of project control. In EPC (Engineering, Procurement, Construction) projects where scope changes and procurement delays are routine, a disciplined baseline management process separates professional schedulers from the rest.
Step 1 — Create the Project Baseline: Once the schedule is logic-checked, resource-loaded, and approved, navigate to Project → Maintain Baselines → Add → "Convert current project to baseline." Name it BL0 (Original Contract Baseline). Lock it. Never modify BL0 — it is your contractual reference.
Step 2 — Assign the Baseline: Go to Project → Project Details → Baselines tab. Set "Project Baseline" = BL0. Set "User's Primary Baseline" = BL0 (for variance columns). Add columns BL Project Start, BL Project Finish, Start Variance, Finish Variance to your layout.
- 📌 BL0 — Original Contract Baseline
- 📌 BL1 — Revised Baseline (post VO)
- 📌 BL2 — Current Period Update
- 📌 TB — Target Baseline (internal)
- 📊 BL Project Start / Finish
- 📊 Start Variance / Finish Variance
- 📊 BL Duration / Duration Variance
- 📊 Schedule % Complete
EOT Claims in FIDIC Contracts: A Practitioner's Complete Guide
Extension of Time (EOT) claims are among the most contested aspects of EPC contracts. Under FIDIC Red Book (1999) Clause 20.1, the Contractor must give notice of claim within 28 days of becoming aware of the event. Miss this window and you may lose entitlement entirely — even if you have a valid claim on merits.
Under FIDIC 1999, Sub-Clause 20.1 states the claim notice must be submitted within 28 days of the Contractor being "aware, or should have been aware" of the delaying event. Courts and arbitral tribunals interpret this strictly. Even a valid 6-month delay may be unrecoverable if you missed the notice deadline.
Building a defensible EOT claim requires four elements: (1) Entitlement — identify the contractual basis (Cl. 8.4, 8.5, 19, etc.); (2) Causation — prove the event actually delayed the critical path; (3) Quantification — use a recognized delay analysis method (TIA, Windows Analysis, or Collapsed As-Built); (4) Documentation — daily site records, correspondence, RFI logs, weather records.
Most common mistake: Contractors submit a claim that proves the event occurred but fails to demonstrate critical path impact. The Engineer will reject it. You must show the delay event was on the critical path at the time of occurrence — not as the path existed at contract award.
📋 Talk to Our Experts →More articles on PMP, P6, EOT Claims and EPC Project Controls coming soon.
📬 Subscribe for Updates