1. Position Purpose

The Solution Architect is the commercial and operational mastermind responsible for the end-to-end service lifecycle. You bridge the gap between initial design and "Steady State" operations. You define how a service is onboarded (Day 1), how it is moved through the Service Transition gateway, and how it is sustained and governed (Day 2) within the Singapore Public Sector landscape.

2. Core Service Scopes (The Lifecycle Drill-Down)

A. Multi-Cloud & Hybrid Infrastructure  
Day1: Professional Services & Transition

• Onboarding Scope: Define the "Definition of Ready" for workloads moving to Government Commercial Cloud.
• Transition Governance: Lead the Operational Acceptance Criteria (OAC) process—validating that the landing zone build matches the performance requirements before "Go-Live."
• Migration Service Design: Architect the workflow for discovery, cutover, and UAT sign-off to ensure a clean handover to Ops.

Day 2: Managed Services (Steady State)

• FinOps& Governance: Architect the service for monthly cloud spend optimization and automated budget alerts.
• SLA Instrumentation: Define tiered support models (24x7 vs. 8x5) and ensure the ITSM tools are configured to track "Service Credits" from the moment Transition ends.

B. End-to-End Security Services (The Governance Layer)
Day1: Compliance Build & Transition

• Regulatory Alignment: Ensure the transition phase includes the delivery of all Security required artifacts (e.g., System Security Plans, VAPT remediation reports).
• Role Transition: Architect the "Handover of Power" for the ITSM/ITSO—ensuring they have the correct access and training to manage security approvals on Day2.
• Identity Governance: Define and test the "Privileged Access" workflow during the pilot phase of Transition.

Day2: Managed Security Operations

• Managed Interface: Architect the escalation path between Infrastructure Ops and the IT Security Officer / Manager
• Audit Continuity: Design the "Continuous Compliance" service, ensuring the Agency has real-time dashboards to prove compliance to AGO auditors.

3. Key Responsibilities (The "Transition Focus")

• Service Design Package (SDP) Ownership: Own the SDP from initial bid through to the final "As-Built" service documentation.
• Operational Gatekeeping: Act as the final "Sign-off" authority for Service Transition. If the build doesn't meet the operational support requirements, you have the mandate to halt the transition.
• Commercial Guardrails: Validate that the technical migration scope (Day 1) does not inadvertently create an unmanageable "resource debt" for the Day 2operations team.
• Stakeholder Liaison: Primary bridge between the Migration Project Manager (Day 1) and the Service Delivery Manager (Day 2).

4. Experience & Qualifications

• Public Sector Fluency: Deep, practical knowledge of Singapore Public Sector.
• Service Framework Mastery: ITIL v4 Managing Professional (specifically CDS: Create, Deliver and Support).
• Hybrid Infrastructure Context: A strong "mental map" of how GDC and Public Cloud interact from a support boundary perspective.
• Security Governance Grip: Understanding how to build a service that empowers the ITSM/ITSO during and after the transition.

5. Success Measures (KPIs)

Transition Quality: Percentage of services moving from Day 1 to Day 2 with zero "Critical" operational gaps. SLA Integrity: 100% alignment between the contracted SLAs and the reporting dashboards delivered at the end of Transition. Audit Readiness: Delivery of a "Compliance-Ready" service package at the point of operational handover.