Outsourcing tower list — which towers go out of house in Phase 1.it.decisions.d06
P0
G
Summary
Defines our proposal scope. Decision owner (sheet): IT Head + KC. Sheet target: Wk 1.
Rationale prompt skeleton
Capture the rationale for this decision. Sheet-recorded justification: "Defines our proposal scope.". Reference the evidence questions, name the alternatives considered, and explain how this decision propagates to design, BoM, and operating model.
Default options (5)
l1_l2_helpdesk
L1/L2 helpdesk
Tier-1/2 user support outsourced.
network_ops
Network operations
WAN / LAN / SD-WAN operate.
endpoint_mgmt
Endpoint management
MDM / patching / image build.
edr_mgmt
EDR/XDR managed
Managed detection of endpoint events.
soc
SOC (24x7)
Security operations centre.
Default approval chain
AdminExecutiveViewer
Linked evidence questions (4)
| id | prompt | workstream |
|---|---|---|
| it.operating_model.q10 | Outsourcing posture — which towers are open to outsource (e.g., L1/L2 helpdesk, network ops, endpoint mgmt, EDR mgmt, SOC)? Which stay in-house? | it.operating_model |
| it.operating_model.q11 | Existing strategic vendor relationships (incl. ours). Multi-year contracts, expansion clauses, exclusivity. | it.operating_model |
| it.vendors_contracts.q08 | Towers already outsourced today and to whom (helpdesk, NOC, SOC, MDR, infra mgmt). Term and performance vs SLA. | it.vendors_contracts |
| it.vendors_contracts.q09 | Towers under consideration for outsourcing in this engagement — confirm list per holding/subsidiary. Capability vs. capacity scoping. | it.vendors_contracts |