GCC Build OSv0
/api

GCC Context — Chennai Build & Transitionit.gcc_context

P1 owner role: ProgrammeLead display order 10

GCC-specific questions: identity tenancy, M365 SKU, engineering offshore-use, data residency, cutover plan, federated service integration.

Questions (18)

id prompt scope category priority artefact
it.gcc_context.q01 Confirm GCC sizing — Y1/Y2/Y3 user count by pillar (Engineering / Finance-HR-Procurement / IT shared services). Source: Alcent VC base case (180 → 540 → 720). GCC Scope & Sizing P0 table
it.gcc_context.q02 Confirm capability list to migrate into GCC in Phase 1 (mature only): which sub-functions, which services, which technical capabilities. GCC Scope & Sizing P0 table
it.gcc_context.q03 Identity tenancy decision — extend KSA Entra ID to India, or separate India tenant with B2B federation? GCC Identity Tenant P0 text
it.gcc_context.q04 M365 SKU strategy for GCC — E3 + targeted E5 add-ons, or full E5? Aligned to parent or India-specific? GCC M365 SKU P0 text
it.gcc_context.q05 Engineering software for GCC — license offshore-use rights confirmed via KSA. Aconex per-project vs owner-operator model. GCC Engineering P0 text
it.gcc_context.q06 Snowflake (or DW) residency — Azure Central India / Mumbai / Singapore for GCC analytics? Cross-border transfer rules. GCC Data Residency P0 text
it.gcc_context.q07 Capability cutover sequencing into GCC — wave plan, parallel-run windows, go/no-go gates per capability. GCC Cutover P1 text
it.gcc_context.q08 How will GCC services plug into the federated group ITSM (single instance? separate?), identity, EDR, SOC. GCC Service Integration P0 text
it.gcc_context.q09 India-specific items: G.O.34 payroll subsidy reporting, STPI/SEZ compliance, India-region cloud preferences, local helpdesk hours. GCC Local Reality P1 text
it.gcc_context.q10 Chennai seat/rack capacity plan — phase 1, phase 2. AV/conferencing density. Hardware refresh cadence. GCC Capacity & Refresh P1 text
it.gcc_context.q11 What are the primary expectations from the proposed GCC initiative — cost reduction, capability lift, governance maturity, all three? Rank. GCC Future State P0 text
it.gcc_context.q12 Which services or capabilities would benefit most from standardisation? Top 5 in priority order, with rationale. GCC Future State P0 table
it.gcc_context.q13 Which operational areas would benefit from improved visibility or reporting? Specific KPIs or dashboards leadership wants. GCC Future State P0 text
it.gcc_context.q14 Are there functions that may benefit from centralised governance (security, identity, ITSM, vendor mgmt, BCP)? Confirm priority order. GCC Future State P0 text
it.gcc_context.q15 Are there concerns around balancing standardisation with local flexibility (federated boundaries)? Top objections to address. GCC Future State P0 text
it.gcc_context.q16 Which improvements would provide the highest immediate business value (quick wins for first 90 days)? GCC Future State P0 text
it.gcc_context.q17 Are there subsidiaries more prepared for transformation initiatives than others? Readiness ranking with rationale (people, process, tech). GCC Future State P0 text
it.gcc_context.q18 What are the biggest concerns regarding centralised governance or shared services? Objections to surface and address explicitly in the proposal. GCC Future State P0 text

Decisions related to this workstream (4)

id title scope priority evidence questions
it.decisions.d02 Group identity tenancy — extend KSA Entra ID vs separate India tenant with B2B federation. G P0 3
it.decisions.d03 M365 SKU strategy — E3 + targeted E5 add-ons, or full E5 across the group. G P0 5
it.decisions.d11 Confirm GCC sizing — adopt Alcent VC base case (180/540/720) or revise. GCC P0 2
it.decisions.d12 Data residency for GCC — Azure Central India / Mumbai / Singapore. GCC P0 2