Milestones¶
SISS is delivered in seven milestones from April 2026 through June 2027.
Dates come from docs/SISS - Project Planning V1.0 - Project Milestone.csv.
Roadmap¶
gantt
title SISS M1–M7 delivery
dateFormat YYYY-MM-DD
axisFormat %b %Y
section Planning
M1 Planning & Mobilisation :m1, 2026-04-01, 2026-04-16
section Build
M2 KM Digital Backbone :m2, after m1, 2026-08-14
M3 Technical Comment AI :m3, after m2, 2026-10-13
M4 BIM Visual Inspection :m4, after m3, 2026-12-12
M5 BIM Extraction AI :m5, after m4, 2027-02-10
section Acceptance
M6 SIT / UAT :m6, after m5, 2027-03-12
M7 Go-Live & Handover :m7, after m6, 2027-06-10Delivery schedule¶
| # | Milestone | Delivery date | Payment | Deliverable artifact |
|---|---|---|---|---|
| M1 | Planning & Mobilisation | 2026-04-16 | 20% | Signed initialisation doc |
| M2 | KM Digital Backbone | 2026-08-14 | 25% | UAT / SIT sign-off |
| M3 | Technical Comment AI | 2026-10-13 | 15% | UAT / SIT sign-off |
| M4 | BIM Visual Inspection | 2026-12-12 | 15% | UAT / SIT sign-off |
| M5 | BIM Extraction AI | 2027-02-10 | 15% | UAT / SIT sign-off |
| M6 | SIT and UAT completion | 2027-03-12 | 5% | Certificate of System Acceptance |
| M7 | Go-Live and Final Handover | 2027-06-10 | 5% | Project Closure Report |
Architecture increment per milestone¶
Each milestone adds a well-defined slice of the platform. The services exist as deployable skeletons from M2 onward; each later milestone activates their features.
| Milestone | Architecture increment |
|---|---|
| M2 | core-svc, submission-svc, workflow-svc, comment-svc (basic), ai-svc (compliance extraction + HITL), notification-svc, signing-svc (interim trust). SPA with PSP + officer consoles, submission dashboard |
| M3 | comment-svc full (inline markup, library, revision compare, response tracker), ai-svc comment drafting + risk highlight, advanced dashboard, SLA monitor |
| M4 | bim-svc validation + tile pipeline, xeokit viewer in SPA, operational dashboards |
| M5 | bim-svc metadata extraction + zoning comparison, exceedance flagging, federated-view mode |
| M6 | Security and performance hardening, VAPT, load testing, final CA trust-anchor cutover |
| M7 | Production promotion, hypercare, runbooks, training |
Release gates
Every milestone has a set of acceptance criteria that must pass before the next begins. See Release gates for the full list per milestone.
Current execution focus¶
The approved implementation plan targets M2 (14 August 2026). Teams should already leave clean extension points for M3–M5 in every service they touch.
See M2 plan for the execution breakdown.