DC Design Tools
↓ About this tool
Drop an EPW file or fetch real weather to use the Adiabatic Calculator.

What this tool does

The Adiabatic Water Calculation Tool estimates how much water an adiabatic (evaporative) pre-cooling system would use over a full year at a given location, along with the energy it saves and the CO₂ emissions that saving avoids — all computed hour-by-hour from a real weather dataset rather than a single design-day assumption. Feed it either an EPW typical-year weather file or a year of real observed data fetched from Meteostat, and it runs the full psychrometric calculation across every hour, then rolls the results up into monthly and annual totals.

What adiabatic pre-cooling is

Adiabatic pre-cooling sprays a fine mist of water into the air upstream of a cooling coil or dry cooler. As that water evaporates, it absorbs heat from the air and drops its temperature before the air ever reaches the mechanical cooling equipment — the same evaporative-cooling effect behind a swamp cooler. This lets a facility's chillers or dry coolers work against a lower entering air temperature, cutting their compressor or fan energy, at the cost of the water consumed by evaporation. It's most effective in hot, dry climates: the drier the air, the more evaporation it can absorb, and the bigger the cooling benefit per liter of water sprayed.

How the calculation works

For every hour in the dataset, the tool derives the air's saturation vapor pressure from dry-bulb temperature using the Magnus equation, converts dew point into a humidity ratio, and computes air enthalpy from temperature and humidity. Comparing the entering air's state to a saturated (fully evaporated) state gives the water evaporated per unit of air mass for that hour; multiplied by estimated airflow, that becomes a water flow rate. The enthalpy drop achieved by pre-cooling that hour's air, multiplied by airflow, gives the cooling energy — and therefore compressor energy — saved for that hour. Hours below the system's activation threshold (too cool or too humid for pre-cooling to be worthwhile) are correctly excluded from both the water and energy totals, which is why Operating Hours is usually well under 8,760.

Reading the results

The full hourly breakdown, monthly aggregates, and KPI tiles are all included in the Excel export, along with native charts, so you can drop the results straight into a design report.

Step-by-step: using the calculator

  1. Drag and drop an .epw file, or switch to Meteostat and fetch a station/year of real observed weather.
  2. The calculator runs automatically once weather data is loaded — no separate "calculate" step.
  3. Read the KPI tiles for annual water use, peak/average flow, energy saved, and CO₂ avoided.
  4. Click Download Excel for the full hourly and monthly breakdown with charts, ready to attach to a design package.

Frequently asked questions

Does this account for water lost to drift or blowdown?

No — the water figure is the theoretical evaporated mass needed to reach the calculated psychrometric state, which is the core sizing number for the water supply. Real systems have additional losses (drift, bleed-off for water quality) on top of this, which your equipment vendor's data sheet will specify.

Why is Operating Hours less than 8,760?

Adiabatic pre-cooling only helps when the air is warm and dry enough for evaporation to meaningfully lower its temperature. Hours where conditions don't cross that activation threshold are excluded from the total, since running the system then wouldn't do anything useful.

Should I use an EPW file or Meteostat data?

An EPW typical year gives a consistent, standardized annual estimate suitable for early design sizing. A specific Meteostat year lets you check how the same system would have performed during an unusually hot, dry, or humid real year — useful for stress-testing a design against actual extremes.

Is this free, and does it store my inputs anywhere?

Yes, completely free, with no account and no server-side storage — every calculation and the Excel export are generated locally in your browser.