Release gates
Each milestone has a set of gate conditions that must pass before the next
one begins. Source: docs/SISS - Project Planning V1.0 - Release Gate Milestone.csv.
M1 — Planning & Mobilisation
| Gate condition |
Acceptance criterion |
| Resource allocation chart |
Chart + project plan signed off |
| Product backlog with estimations |
Backlog complete with effort estimations |
M2 — KM Digital Backbone
| Gate condition |
Acceptance criterion |
| Pre-consultation checklist (admin + planning) |
All required checklist items validated; pushback path works |
| AI KM compliance |
Parameter checking validates all rules; HITL review captures decisions |
| KM approval workflow |
Workflow engine routes per role; SLAs trigger reminders |
| Kertas Perakuan & Surat Sokongan generation |
Documents produced in prescribed format; comments aggregated |
| SIGL generation |
Digital signatures verifiable; certificates downloadable by PSP |
| Notifications |
Trigger on approval-needed events |
| RBAC |
Admin functions restricted by role; permission-denial events audited |
| Full audit trail |
All state changes captured; trail complete per submission |
| Centralised repository |
Documents in GCS, scoped access |
| Gate condition |
Acceptance criterion |
| In-line markup |
Markup with audit history (who marked, when) |
| Comment template builder |
Templates configurable per department |
| Comment library |
Searchable, reusable comments |
| Review status dashboard |
Status visible per submission and per department |
| SLA monitoring |
Overdue reviews flagged and surfaced |
| Submission revision comparison |
Revision diff tool works on files + structured data |
| Risk highlighting |
AI highlights risk areas in documents |
| Comment response tracker |
PSP responses tracked against each comment |
M4 — BIM Visual Inspection
| Gate condition |
Acceptance criterion |
| BIM file handling |
IFC version + integrity validation; naming convention check |
| BIM viewer |
Pan / zoom / rotate / measure functional in the browser |
| Operational dashboard |
Metrics displayed accurately (SLA, throughput, queue depth) |
| Gate condition |
Acceptance criterion |
| Height extraction |
≥ 90% accuracy on the golden set |
| Zoning comparison |
Exceedance flags trigger correctly |
M6 — SIT / UAT
| Gate condition |
Acceptance criterion |
| System integration test |
Critical and high defects resolved |
| Security |
No critical vulnerabilities per VAPT |
| Performance |
Within published SLO thresholds |
M7 — Go-Live & Final Handover
| Gate condition |
Acceptance criterion |
| Production deployment |
Production environment stable, monitoring enabled |
| Final documentation |
Runbooks, training material, closure report delivered |
Status
The CSV shows every milestone as "Ready to proceed: FALSE" — this is the
baseline state. Update those rows as each gate passes.
How these gates link to delivery
- Every M2 gate maps to a verification task in Phase 8 of the M2 plan.
- Every gate is covered by an integration test in the testing strategy.
- Failed gates are blockers, not warnings — the next milestone does not begin until green.