Reliable financial planning for a data center begins by separating capital expenditure from operating expenditure while recognizing that technical decisions often move cost between the two.
Define CAPEX clearly
Typical CAPEX includes site preparation, building works, electrical infrastructure, cooling systems, fire protection, telecommunications, security, controls, commissioning, professional services and initial spares.
Define OPEX clearly
OPEX commonly includes electricity, fuel, maintenance contracts, consumables, staffing, software licences, monitoring platforms, insurance, periodic testing and replacement of limited-life assets.
Model at system level
Cost models should be broken down by major systems rather than using one lump-sum value. This allows sensitivity analysis for UPS, generators, cooling, electrical distribution, network infrastructure and support systems.
Include growth and redundancy
Cost must reflect installed capacity, future expansion and the selected redundancy architecture. A 2N design will have a very different capital profile from an N+1 design even if both initially support the same IT load.
Use controlled assumptions
Exchange rates, escalation, electricity tariff, load growth, utilization and equipment-life assumptions should be documented and version-controlled so financial conclusions can be reproduced.
References
- ISO 21502:2020, Guidance on project management.
- ISO 15686-5:2017, Buildings and constructed assets — Service life planning — Life-cycle costing.