The Master Discipline That Turns Chaos Into Capital
1. Definition in One Line
Portfolio Planning is the strategic, data-driven orchestration of every project, programme, and resource inside an organisation—using a single Primavera P6 database (EPS) to align capital spend, risk, and delivery with corporate goals.
2. Why It Exists
Most organisations run 10–200+ projects simultaneously. Without portfolio planning:
- Resource wars – Site A steals welders from Site B
- Cash crunches – $400 M due in Q3, finance only budgeted $220 M
- Blind spots – Project C slips 90 days, nobody notices until gate review
Portfolio planning sees everything at once and answers:
“If we approve Project X, what happens to cash, manpower, risk, and ROI across the entire 5-year horizon?”
3. The Core Framework: Primavera P6 EPS
| Element | Role in Portfolio Planning |
|---|---|
| EPS (Enterprise Project Structure) | Hierarchical “folder” tree that groups every project/programme |
| OBS (Organisational Breakdown Structure) | Maps responsibility (CEO → PM → Discipline Lead) |
| Global Calendars & Codes | Standardise shifts, holidays, risk categories, cost codes |
| Resource Dictionary | Single pool of labour, equipment, materials – no double-booking |
| Portfolios | Dynamic filters (e.g., “All Oil & Gas 2025–2027” or “High-Risk >$100 M”) |
Result: 150 separate project schedules live in one database, roll up instantly, and share the same DNA.
4. The 5 Layers of Portfolio Planning
| Layer | What You See | Key Deliverable |
|---|---|---|
| 1. Strategic Alignment | NPV, IRR, ESG score per project | Capital Allocation Matrix |
| 2. Capacity & Resource | Cross-project histograms (welders, cranes, cash) | Resource-Leveled 5-Year Plan |
| 3. Schedule Integration | Critical-path roll-up, programme milestones | Portfolio Gantt + S-Curves |
| 4. Risk Aggregation | Monte Carlo across 80 projects → P80 contingency | Enterprise Risk Heat-Map |
| 5. Performance (EVM) | Portfolio CPI/SPI, EAC vs BAC | Executive Dashboard (Power BI / P6 Analytics) |
5. How Multiple Schedules Live Together
- Each project = standalone P6 file (or partition)
- All linked via EPS node → instant roll-up
- Shared global elements:
- Activity codes (Phase, Location, Risk ID)
- Resource IDs (WELD-01, CRANE-50T)
- Cost accounts (1.02.03 Civil Foundations)
- Update cycle:
- PMs update their file weekly
- Central planner runs global resource leveling nightly
- Dashboard refreshes at 06:00
Example: A 30 000-activity refinery project and a 5 000-activity pipeline share the same WELD-01 crew. P6 flags overallocation before the welder boards the plane.
6. Key Artifacts You’ll Produce
| Artifact | Frequency | Audience |
|---|---|---|
| Portfolio Roadmap | Quarterly | C-Suite |
| Resource Heat-Map | Monthly | Operations |
| Cash-Flow S-Curve (Portfolio) | Weekly | CFO |
| Risk Radar Chart | Monthly | Risk Committee |
| EVM Dashboard | Bi-weekly | Programme Directors |
7. Real-World Payoff
| Metric | Before Portfolio Planning | After |
|---|---|---|
| Capital wasted on low-ROI projects | 22 % | <5 % |
| Resource overallocation | 40 % of crews | <3 % |
| Forecast accuracy (portfolio EAC) | ±18 % | ±4 % |
| Gate approval cycle | 6 weeks | 48 hours |
8. How to Start (3-Step Blueprint)
- Build the EPS skeleton – mirror your org chart + strategic buckets
- Migrate 3 pilot projects into P6 with global codes & resources
- Switch on portfolio dashboards – prove value in 30 days
9. One-Sentence Summary
Portfolio Planning = a single Primavera P6 EPS that synchronises every schedule, dollar, welder, and risk across your entire capital programme—so the right projects start on time, finish on budget, and never cannibalise each other.