Senior Data Center Capacity Delivery Manager
When to Use
- Turn an approved capacity initiative into a dated delivery plan (kW/MW, racks, go-live)
- Run critical path across power, cooling, fit-out, network demarc, and acceptance tests
- Coordinate vendors: GC, MEP, colo, utility, carriers, commissioning agents
- Define readiness gates: construction complete → commissioned → rack-ready → workload-ready
- Track capacity at risk — slip vs demand date from engineering or portfolio
- Manage RAID and weekly status for capacity delivery programs
- Hand off to facilities ops and
cluster-deployment-engineer when capacity is install-ready
- Support multiple concurrent hall or row expansions with dependency map
When NOT to Use
- Multi-site capex prioritization and funding bands →
data-center-portfolio-planning-execution-lead
- Detailed hall design, single-line diagrams, tier selection →
data-center-design-execution-lead
- Host consolidation, GPU forecast, stranded kW optimization →
data-center-compute-supply-efficiency
- Cross-team software integration program →
technical-program-manager
- Terraform, cloud burst architecture →
infrastructure-engineer
Related skills
| Need |
Skill |
| Portfolio roadmap and steering |
data-center-portfolio-planning-execution-lead |
| MEP, layout, commissioning depth |
data-center-design-execution-lead |
| Compute utilization and supply |
data-center-compute-supply-efficiency |
| On-site install, cabling, acceptance |
field-services-engineer |
| K8s on new capacity |
cluster-deployment-engineer |
| Large mixed software+infra program |
technical-program-manager |
| Physical security and compliance |
cybersecurity, compliance-engineer |
| Exec status narrative |
communication-lead |
| WIP/CIP and capex capitalization |
director-infrastructure-capex-accounting |
| Strategic sourcing and supplier SCM |
supply-chain-manager |
Core Workflows
1. Delivery charter
Scope: site, increment (e.g. 2 MW, 80 racks), demand date, budget envelope, DRIs.
See references/delivery_charter.md.
2. Capacity delivery plan
Milestones from design release through rack-ready and optional workload-ready.
See references/capacity_delivery_plan.md.
3. Workstream coordination
Power, cooling, construction, network, security, DCIM — integrated schedule.
See references/workstream_coordination.md.
4. Readiness gates
Objective criteria before declaring capacity available for install or production.
See references/readiness_gates.md.
5. Vendor and construction management
RFI/submittal cadence, site safety, change orders, acceptance.
See references/vendor_construction.md.
6. Reporting and escalation
Weekly RAG, MW/rack burn-up, top blockers, decisions for steering.
See references/reporting_escalation.md.
Output standards
- Integrated master schedule with critical path identified
- Capacity burn-up: planned vs actual kW/racks by week
- RAID with owner and target date; escalate reds within 48h
- Readiness checklist signed by facilities and IT infrastructure
- Assumptions on utility lead times and colo lead times explicit
When to load references
- Charter →
references/delivery_charter.md
- Schedule and milestones →
references/capacity_delivery_plan.md
- Workstreams →
references/workstream_coordination.md
- Gates →
references/readiness_gates.md
- Site and vendors →
references/vendor_construction.md
- Status pack →
references/reporting_escalation.md
1---2name: senior-data-center-capacity-delivery-manager3description: Guides delivery of data center capacity increments—MW/kW and rack-ready halls on schedule: capacity delivery plans, critical path (power, cooling, construction, network), vendor and contractor coordination, readiness gates, handoff to operations and compute install, and program RAID across concurrent capacity projects. Use when executing an approved capacity build or expansion, tracking MW/rack delivery milestones, unblocking construction or MEP dependencies, or reporting capacity-at-risk to steering—not for portfolio prioritization (data-center-portfolio-planning-execution-lead), single-hall MEP design (data-center-design-execution-lead), utilization or GPU supply (data-center-compute-supply-efficiency), or generic software programs (technical-program-manager). On-site rack-and-stack and smart-hands: field-services-engineer.4---56# Senior Data Center Capacity Delivery Manager78## When to Use910- Turn an **approved capacity initiative** into a dated delivery plan (kW/MW, racks, go-live)11- Run **critical path** across power, cooling, fit-out, network demarc, and acceptance tests12- Coordinate **vendors**: GC, MEP, colo, utility, carriers, commissioning agents13- Define **readiness gates**: construction complete → commissioned → rack-ready → workload-ready14- Track **capacity at risk** — slip vs demand date from engineering or portfolio15- Manage **RAID** and weekly status for capacity delivery programs16- Hand off to **facilities ops** and `cluster-deployment-engineer` when capacity is install-ready17- Support **multiple concurrent** hall or row expansions with dependency map1819## When NOT to Use2021- Multi-site capex prioritization and funding bands → `data-center-portfolio-planning-execution-lead`22- Detailed hall design, single-line diagrams, tier selection → `data-center-design-execution-lead`23- Host consolidation, GPU forecast, stranded kW optimization → `data-center-compute-supply-efficiency`24- Cross-team software integration program → `technical-program-manager`25- Terraform, cloud burst architecture → `infrastructure-engineer`2627## Related skills2829| Need | Skill |30|---|---|31| Portfolio roadmap and steering | `data-center-portfolio-planning-execution-lead` |32| MEP, layout, commissioning depth | `data-center-design-execution-lead` |33| Compute utilization and supply | `data-center-compute-supply-efficiency` |34| On-site install, cabling, acceptance | `field-services-engineer` |35| K8s on new capacity | `cluster-deployment-engineer` |36| Large mixed software+infra program | `technical-program-manager` |37| Physical security and compliance | `cybersecurity`, `compliance-engineer` |38| Exec status narrative | `communication-lead` |39| WIP/CIP and capex capitalization | `director-infrastructure-capex-accounting` |40| Strategic sourcing and supplier SCM | `supply-chain-manager` |4142## Core Workflows4344### 1. Delivery charter4546Scope: site, increment (e.g. 2 MW, 80 racks), demand date, budget envelope, DRIs.4748**See `references/delivery_charter.md`.**4950### 2. Capacity delivery plan5152Milestones from design release through **rack-ready** and optional **workload-ready**.5354**See `references/capacity_delivery_plan.md`.**5556### 3. Workstream coordination5758Power, cooling, construction, network, security, DCIM — integrated schedule.5960**See `references/workstream_coordination.md`.**6162### 4. Readiness gates6364Objective criteria before declaring capacity available for install or production.6566**See `references/readiness_gates.md`.**6768### 5. Vendor and construction management6970RFI/submittal cadence, site safety, change orders, acceptance.7172**See `references/vendor_construction.md`.**7374### 6. Reporting and escalation7576Weekly RAG, MW/rack burn-up, top blockers, decisions for steering.7778**See `references/reporting_escalation.md`.**7980## Output standards8182- Integrated master schedule with critical path identified83- Capacity burn-up: planned vs actual kW/racks by week84- RAID with owner and target date; escalate reds within 48h85- Readiness checklist signed by facilities and IT infrastructure86- Assumptions on utility lead times and colo lead times explicit8788## When to load references8990- **Charter** → `references/delivery_charter.md`91- **Schedule and milestones** → `references/capacity_delivery_plan.md`92- **Workstreams** → `references/workstream_coordination.md`93- **Gates** → `references/readiness_gates.md`94- **Site and vendors** → `references/vendor_construction.md`95- **Status pack** → `references/reporting_escalation.md`
daemon-blockint-tech