Project status card · Unified Government e-Services Platform

MunjazStrategy & projects

MunjazPMO PLATFORM

Project status card

28 October 2026

Unified Government e-Services Platform

PRJ-2026-014 · Digital Transformation Sector · Strategic · WP-2025-014

In progressAt risk4ExecutionProject manager: Eng. Tarek Al-Mardini · Sponsor: Eng. Khaled Al-Kayyali

Progress: ⁦58%⁩ / ⁦67%⁩
SPI · CPI: 0.87 · 0.96
Spend: SYP 1.3B / SYP 2.2B
Estimate at completion: SYP 2.3B

Schedule

⁦9%⁩ behind⁦58%⁩

Planned to date ⁦67%⁩

Forecast finish: 2027-05-12 · 42 days late

SPI0.87CPI0.96

Health dimensions

At risk

Last update: 2026-10-27 · Up to date

Deliverables

⁦2⁩ of ⁦8⁩ due deliverables accepted on time (⁦25%⁩)

Next milestones

Wave 1 development complete (24 services)2026-11-12
Civil registry & national interoperability integration complete2026-12-10
Penetration test passed, security sign-off2027-01-28
User acceptance testing complete2027-03-14

Top risks

Civil-registry identity and interoperability interfaces not ready on time16
Shortage of integration and back-end engineers on the vendor team16
Late sign-off of service requirements by the owning ministries12
Possible critical findings in the pre-launch penetration test12

Open impediments

Shared civil-registry test environment down for 9 days · Escalated
Vendor late with the updated interoperability interface documents · Open
Two vendor integration engineers withdrawn with no replacement · Overdue

Decisions and changes waiting

Review the returned data migration plan
Replacement plan for the vendor integration engineers
Access request: integration adviser on the unified e-services platform project
CR-2026-004 · Add civil-record transfer & record merge to the first release

Copilot summary

The project is 58% complete against 67% planned (SPI 0.87) and is forecast to finish on 12 May 2027 instead of 31 March 2027 — 42 days late. The slip sits in national-systems and ministry integration (41% done) and the “Wave 1 complete” milestone, which missed 30 September and is now forecast for 12 November.

Three main causes: (1) the shared civil-registry test environment was down for 9 days; (2) two vendor integration engineers left with no replacement — an impediment now overdue; (3) internal resource strain — the lead integration engineer is at 135% and shared with the mobile app. The request-data migration plan was also returned for rework.