MunjazStrategy & projects
MunjazPMO PLATFORMProject status card
28 October 2026 · 17 Jumada I 1448 AH
Muqawil Platform — Release 4
PRJ-2026-014 · Digital Transformation Sector · Strategic · WP-2025-014
- Progress
- 58% / 67%
- SPI · CPI
- 0.87 · 0.96
- Spend
- SAR 52.2M / SAR 86.4M
- Estimate at completion
- SAR 90M
Schedule
Planned to date 67%
Forecast finish: 2027-05-126 Dhuʻl-Hijjah 1448 AH · 42 days late
SPI0.87Schedule performance index · 0.87CPI0.96Cost performance index · 0.96Health dimensions
Last update: 2026-10-2716 Jumada I 1448 AH · Up to date
Deliverables
2 of 8 due deliverables accepted on time (25%)
Next milestones
- Wave 1 development complete (24 services)2026-11-122 Jumada II 1448 AH
- Nafath & Government Service Bus integration complete2026-12-101 Rajab 1448 AH
- Penetration test passed, security sign-off2027-01-2820 Shaʻban 1448 AH
- User acceptance testing complete2027-03-146 Shawwal 1448 AH
Top risks
- Nafath and Government Service Bus integration interfaces not ready on time16
- Shortage of integration and back-end engineers on the vendor team16
- Late sign-off of membership-service requirements by the owning departments12
- Possible critical findings in the pre-launch penetration test12
Open impediments
- Shared Nafath test environment down for 9 days · Escalated
- Vendor late delivering updated Government Service Bus interface specs · 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 Muqawil project
- CR-2026-004 · Add membership 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 agency 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 Nafath 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 membership-data migration plan was also returned for rework.