Confirm GCC sizing — adopt Alcent VC base case (180/540/720) or revise.it.decisions.d11

P0 GCC

Summary

Drives BoM and ramp plan. Decision owner (sheet): GCC Head + CFO. Sheet target: Wk 1.

Rationale prompt skeleton

Capture the rationale for this decision. Sheet-recorded justification: "Drives BoM and ramp plan.". Reference the evidence questions, name the alternatives considered, and explain how this decision propagates to design, BoM, and operating model.

Default options (2)

alcent_base_case Adopt Alcent VC base case (180 / 540 / 720)

Sizing follows the prepared VC base case across Y1/Y2/Y3.

Pros

+ Externally benchmarked
+ Aligns with funding model

Cons

− Locks early; revise harder later

revised_sizing Revise sizing

Re-baseline Y1/Y2/Y3 against actual capability migration plan.

Pros

+ Bottom-up grounded
+ Matches mature-capability rule

Cons

− Slower to lock

Default approval chain

Admin
ExecutiveViewer

Linked evidence questions (2)

id	prompt	workstream
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).	it.gcc_context
it.gcc_context.q02	Confirm capability list to migrate into GCC in Phase 1 (mature only): which sub-functions, which services, which technical capabilities.	it.gcc_context