CP-2026-05Version 1
SCA ERP System
One corrective plan: why the project slipped, the rule that triggered it, the actions, the days won back, approval and follow-up.
What triggered the plan
The project’s reading the day the rule fired, and today.
Detected on 2026-09-30
Slip past the baseline
- At detection
- 52 days
- Today
- 58 days
- Limit
- > 40
Schedule performance index
- At detection
- 0.83
- Today
- 0.82
- Limit
- < 0.85
A rule approved by the Project Approval Committee (PMO-2026/14), read automatically from the project’s data.
Days won back
The forecast finish without the plan, with it, and the difference.
Baseline
2026-12-31Without the plan
2027-03-31+90 days
With the plan
2027-02-27+58 days
Wins back 32 days
Achieved so far: 10 days
Why it slipped
Customisations and integrations missed in the tender book, the Etimad link failing twice, and late migration of historical financial data
Corrective actions
Each action with its owner, date, status and the days it wins back; overdue ones are shaded.
Freeze all non-mandatory customisations
Dana S. Al-SalehDana S. Al-SalehDirector, Enterprise Systems & IntegrationP-025d.alsaleh@sca.saDone2026-10-302026-10-3019 Jumada I 1448 AHWins back 10 daysA joint fix session with the Etimad team
Dana S. Al-SalehDana S. Al-SalehDirector, Enterprise Systems & IntegrationP-025d.alsaleh@sca.saACT-0316Not startedIn 2 days2026-10-3019 Jumada I 1448 AHWins back 7 daysAn independent review of the vendor’s estimates
Haifa S. Al-RuwailiHaifa S. Al-RuwailiSenior Financial AnalystP-037h.alruwaili@sca.saIn progressIn 11 days2026-11-0828 Jumada I 1448 AHA critical-path analysis and a two-stage financial go-live
Dana S. Al-SalehDana S. Al-SalehDirector, Enterprise Systems & IntegrationP-025d.alsaleh@sca.saACT-0315Not startedIn 7 days2026-11-0424 Jumada I 1448 AHWins back 15 days
Follow-up
The project’s readings after the plan was approved, with the PMO’s notes.
No readings yet; follow-up starts after approval.