Every Vision 2030 programme has a KPI story to tell — from the ministry down to the giga-project package. Here's the four-layer KPI framework we deploy across Saudi EPMOs, SMOs and giga-project PMOs.

Layer 1 — Strategic (SMO / Ministerial)

Vision 2030 KPI attainment against ministry targets.
OKR progression at pillar and objective level.
Portfolio benefits realisation vs. business case.
Strategic alignment score across active initiatives.

Layer 2 — Portfolio (EPMO)

Portfolio schedule and cost performance index (SPI, CPI).
Cross-programme dependency and escalation count.
Portfolio risk exposure — inherent vs. residual.
Contractor and vendor performance rollup.

Layer 3 — Programme (PMO)

Earned value against baseline at package level.
RAID trend — new, aging, closed.
Milestone attainment and schedule variance.
Change and scope-creep rate.

Layer 4 — Delivery (Site / Team)

Daily site progress (%), manpower, plant.
HSE — incident rate, near-misses, LTI.
Quality — NCRs, snags, first-time-right.
RFI turnaround and open items aging.

How to roll it up

The four layers should share a single KPI dictionary and roll up automatically — not via spreadsheet reconciliation each month. That's what PMO-Connect's reporting layer does: SiteAxis captures layer 4 in the field, StratexHub owns layers 1–2, and the shared model handles layer 3.

Ministerial and PIF reporting

For PIF portfolio companies and ministry-level Vision 2030 programmes, KPIs must map cleanly to the sector VRP (Vision Realization Programme) targets and roll up in Arabic-first ministerial briefs. Build the mapping once — not every reporting cycle.

A Practical PMO KPI Framework for Vision 2030 Programmes