Five-year TCO modular micro data center vs traditional build (MDC)

If you’re evaluating a 30–80 kW micro data center / modular cabinet for an edge site, a factory, a branch facility, or a small on‑prem expansion, “Is modular cheaper?” is usually the wrong first question.

The better question is:

Over five years, which approach gives you the lowest auditable total cost of ownership once you include energy, demand charges, and the operational overhead you’ll actually carry?

This post provides a procurement‑friendly comparison with explicit assumptions. It’s not a quote.

Key Takeaway: In a 5‑year model, the largest swing factors are typically PUE (efficiency), electricity tariff structure (energy + demand), and the size of your on‑site labor/coordination burden—not a single line item on the CapEx spreadsheet.

Key Takeaway: For a modular micro data center vs traditional build, treat PUE and demand charges as scenario variables and publish the assumptions alongside the numbers.

Quick comparison: five-year TCO modular micro data center vs traditional build

What we include (and what we do not)

This comparison intentionally focuses on three cost buckets you specified:

1. Electrical & power chain (UPS, distribution/switchgear equivalents at the module level, rack PDUs)

2. Cooling plant at the micro/MDC scale (integrated DX/in‑row/rear‑door, or liquid‑ready options depending on design)

3. White space fit‑out (racks, containment where applicable)

Not included (because it varies wildly by site): building/shell, land/lease, network backhaul, taxes, insurance, security staffing, and enterprise IT hardware refresh.

Definitions you need before modeling (so the math doesn’t lie)

PUE (Power Usage Effectiveness)

PUE is the standard metric for infrastructure energy overhead:

• PUE = Total Facility Energy / IT Equipment Energy

A PUE of 1.50 means: for every 1 kWh consumed by IT, the facility consumes 1.5 kWh total (the extra 0.5 kWh goes to cooling, power conversion losses, lighting, etc.).

For definitions and measurement boundaries, see the U.S. Department of Energy’s guidance in U.S. DOE “Measuring PUE for Data Centers” (2011) and the boundary discussion in LBNL “PUE: A Comprehensive Examination of the Metric”.

Demand charges (why $/kWh isn’t enough)

Many commercial tariffs include a demand charge: you pay for the highest measured kW during a billing period (often the peak 15‑minute interval), regardless of total kWh.

For micro data centers, demand charges matter because:

• peaks can be driven by cooling transients, compressor starts, and operational events

• the meter sees facility kW, not “just IT”

In this model, we keep demand charges explicit and adjustable.

Five-year TCO model: modular micro data center vs traditional build

Step 1: Set the baseline inputs

Use your project’s real values when you have them. For a worked example, we’ll use:

• IT load: 60 kW (inside your 30–80 kW band)

• Operating hours: 8,760 hours/year

• Electricity energy price: $0.092/kWh (representative midpoint of your $0.089–$0.095 band)

• Demand charge: $18/kW‑month (illustrative; replace with your tariff)

• Demand billing kW basis: peak facility kW in the month

• PUE scenarios: 1.15 vs 1.50

• Time horizon: 5 years

⚠️ Warning: A PUE value is not a guarantee and it is not constant. Treat PUE as a scenario variable that depends on design, controls, loading, and commissioning quality.

Step 2: Energy cost from PUE

Annual facility energy (kWh) is approximated as:

• Facility kWh/year ≈ IT kW × 8,760 × PUE

Annual energy cost is:

• Energy $/year = Facility kWh/year × $/kWh

Worked example: 60 kW IT

• At PUE 1.15: Facility kWh/year ≈ 60 × 8,760 × 1.15 = 604,440 kWh

• At PUE 1.50: Facility kWh/year ≈ 60 × 8,760 × 1.50 = 788,400 kWh

Annual energy cost at $0.092/kWh:

• PUE 1.15 → $55,608/year

• PUE 1.50 → $72,533/year

Delta: ≈ $16,925/year, or $84,625 over five years (energy only).

Step 3: Demand charges (a simple, auditable approach)

Demand charges require one extra assumption: the peak facility kW that drives the bill.

For a micro/MDC module, a conservative way to estimate billing kW is:

• Peak facility kW ≈ IT kW × PUE × Peak factor

Where Peak factor captures peaks above average (e.g., 1.05–1.20). For the worked example we use 1.10.

Worked example (60 kW IT):

• PUE 1.15 → peak facility kW ≈ 60 × 1.15 × 1.10 = 75.9 kW

• PUE 1.50 → peak facility kW ≈ 60 × 1.50 × 1.10 = 99.0 kW

Annual demand charge:

• Demand $/year = peak facility kW × $/kW‑month × 12

At $18/kW‑month:

• PUE 1.15 → 75.9 × 18 × 12 = $16,394/year

• PUE 1.50 → 99.0 × 18 × 12 = $21,384/year

Delta: ≈ $4,990/year, or $24,950 over five years (demand only).

CapEx vs OpEx: a practical breakdown for a single micro/MDC module

Rather than forcing a single “$ per kW” number (which hides scope differences), split costs into categories that map to procurement packages.

CapEx categories (in this scope)

• Power chain: UPS, distribution/protection (module‑level), rack PDUs

• Cooling: integrated in‑row/DX/rear‑door or other cabinet/row‑scale cooling approach

• White space: rack/cabinet enclosure, containment elements where applicable

OpEx categories (in this scope)

• Energy (kWh) and demand (kW‑month)

• Preventive maintenance and spares (contracts, filters, wear parts)

• Operational overhead (site coordination time, service dispatch friction, vendor management)

In comparisons, keep “maintenance” split into (a) contractable parts and (b) internal time. Traditional builds often undercount (b).

Worked 5‑year example (illustrative numbers, not a quote)

Below is a simplified example to show how the math behaves. You should replace CapEx numbers with your vendor quotes and local labor rates.

Assumptions for CapEx (illustrative):

• Modular micro/MDC package CapEx (power + cooling + cabinet/white space): $340,000

• Traditional build fit‑out CapEx for comparable scope: $300,000

Assumptions for maintenance & spares (illustrative):

• Annual maintenance/spares = 3% of in-scope equipment CapEx

  • Modular: $10,200/year

  • Traditional: $9,000/year

Now combine the energy + demand from earlier:

In this illustrative example:

• Modular’s higher in‑scope CapEx (+$40,000) is offset by OpEx savings, primarily from the PUE scenario.

• The 5‑year delta is ~$63,575.

Sensitivity: what moves the result most

A sensitivity view is more useful than a single answer. For a micro/MDC module, the dominant variables typically include:

Payback: a clean way to calculate it

Payback is simply:

• Payback (years) = (Incremental CapEx) / (Annual OpEx savings)

Using the worked example:

• Incremental CapEx = $340,000 − $300,000 = $40,000

• Annual OpEx savings (energy + demand + maintenance) ≈

  • Energy delta: $16,925

  • Demand delta: $4,990

  • Maintenance delta: $1,200 (modular higher here)

  • Net ≈ $20,715/year

Payback ≈ 40,000 / 20,715 = ~1.9 years (illustrative).

Procurement checklist: what to request so the TCO comparison is fair

Use this list to avoid “apples vs oranges” quotes.

• BOM with clear inclusions (UPS topology, distribution/protection, PDU monitoring granularity)

• Cooling scope clarity (what’s inside the cabinet/module vs what must be built on site)

• Commissioning and test scope (factory test, site acceptance, instrumentation points)

• Metering boundaries (what feeds are measured for PUE; what loads are excluded)

• Maintenance scope (filters, compressors/fans, battery service, spares policy)

• Assumptions for peak kW events (start-up transients, failover behavior)

• Expansion path (what changes when you add a second module or increase density)

Where Coolnetpower fits (neutral, procurement-friendly)

If you’re evaluating integrated micro/modular options, Coolnetpower publishes specifications and packaging descriptions for:

• the Coolnetpower MetaRack micro data center cabinet (rack-scale integration of power, cooling, monitoring and cabinet systems)

• the Coolnetpower MetaRow modular data center (row-scale modular expansion)

• the Coolnetpower power distribution systems (distribution options and monitoring)

For cooling sizing discipline that improves the quality of any TCO model (modular or traditional), this guide is a useful reference: sizing air conditioning systems for server rooms.

Download: 5‑year TCO calculator + illustrative BOM sample

To make this model reusable for your bids and internal approvals, provide two downloads:

1. Five-year TCO calculator (Excel + Google Sheet)

   • Inputs: IT kW, hours, PUE, $/kWh, demand $/kW‑month, peak factor, CapEx line items, maintenance %

   • Outputs: 5‑year TCO table, sensitivity table, payback

2. Illustrative costed BOM sample (not a quote)

The BOM is valuable even when the pricing is illustrative—because it forces the quote comparison to be structurally consistent.

Next steps

If you want a version of this model aligned to your tariff and density envelope (including clear quote-comparison structure), request the calculator and a quote-ready BOM template via Contact Coolnetpower.