Skip to content

Project

What SISS replaces

Today, planning and building submissions to the Silicon Island CMU are coordinated through manual, paper-driven workflows: document hand-offs between the Principal Submitting Person (PSP), the local authority, and multiple technical agencies, with compliance checking, comment consolidation, and certificate issuance all done by hand. This is slow, hard to audit, and hard to scale.

SISS is the single digital system for this lifecycle — from pre-consultation all the way to digitally signed Kertas Perakuan and SIGL certificates.

Business outcomes

  • Faster turnaround — structured pre-consultation, SLA-driven routing, and AI-assisted checks shorten the time from submission to decision.
  • Consistent compliance — SIRP rules applied uniformly via a versioned, audited rule corpus; AI proposes, humans decide.
  • Auditable by default — every state-changing action and decision becomes an immutable event, retained for 10 years with tamper-evidence.
  • Digital certificates that verify in standard readers — PAdES-signed PDFs with embedded cert chain, timestamp, and a public verify URL.
  • Scalable to more tenants — tenant_id is present from day one; additional local authorities can be onboarded without re-architecting.

Primary user groups

See the full personas page for detail.

Group Role
PSP External applicants submitting and responding
CMU Officer Internal coordinator and administrator
ATD / ATL Officer Technical agency reviewer
SIRP Officer Planning / zoning review panel
External Auditor Read-only audit access

Scope boundary

SISS at launch is:

  • A digital submission and review platform for one local authority (Silicon Island CMU).
  • Human-in-the-loop for every AI-assisted decision — no auto-approval anywhere.
  • The system of record for submissions, comments, decisions, and signed certificates within its scope.

SISS at launch is not:

  • A public developer API for third-party submission portals.
  • An offline or air-gapped deployment.
  • A replacement for the upstream authoring tools used by PSPs (BIM, CAD, document preparation).

Where this fits in the planning hierarchy

  1. The planning CSVs (docs/SISS - Project Planning V1.0 - *.csv) define milestone scope, delivery dates, personas, and acceptance gates.
  2. The architecture spec (docs/superpowers/specs/...) defines the target platform shape across M2 through M5.
  3. The M2 implementation plan (docs/superpowers/plans/...) defines the first execution slice of that architecture.

See the Milestones page for how those slices land in time.