Understanding HAP: What Data Actually Drives a Cooling Load Calculation?

Carrier's Hourly Analysis Program (HAP) is one of the most widely used tools in HVAC design for calculating cooling and heating loads — but like any calculation software, its output is only as good as what goes into it. A perfectly capable piece of software fed incomplete or careless input data will still produce a wrong answer, just a wrong answer that looks precise.

Understanding what HAP actually needs, and why, matters more than knowing which buttons to click. Here's a breakdown of the core input categories and what each one is actually doing in the calculation.

The Underlying Method

HAP calculates loads using the ASHRAE Heat Balance method, working through a true hour-by-hour analysis across all 8,760 hours of the year using real weather data — not a single worst-case snapshot. That's a meaningful distinction from simpler load calculation approaches: rather than sizing a system for one assumed peak condition, HAP tracks how a building's loads actually shift hour by hour, which is part of why it can also generate detailed energy consumption and cost data alongside the load calculation itself.

This system-based approach also tailors its calculations to the specific type of HVAC system being designed — rooftop units, VRF, chilled beams, DOAS, and more — rather than producing one generic load number that the engineer then has to manually translate into equipment sizing.

Building-Level Inputs: Setting the Stage

Before any individual space can be calculated, HAP needs project-level context: the building's location (which determines the weather data set used for the hour-by-hour analysis), design conditions, and overall building parameters. Weather data selection matters more than it might seem — using a nearby but climatically different weather station can meaningfully skew results, since the entire calculation runs against that dataset for every hour of the year.

Space-Level Inputs: Where Most of the Real Data Lives

The bulk of the actual input work in HAP happens at the individual space level — each room or zone in a building needs its own set of data across several categories:

General space data — the basic geometry and identification of the space itself.

Internal load data — occupancy counts, lighting loads, and equipment loads. These represent heat generated inside the space itself, independent of outdoor conditions, and they're often where the biggest input errors happen — an assumed occupancy or equipment load that doesn't match actual building use can throw off a load calculation just as much as a wrong wall material.

Envelope data (walls, windows, doors, roof, skylights) — the physical construction and materials of the space's boundary, which determine how much heat transfers in from outside. This is where getting the actual construction assemblies right, rather than defaulting to generic assumptions, has real consequences for accuracy.

Infiltration data — accounts for uncontrolled air leakage into the space, a factor that's easy to underestimate but genuinely affects load, particularly in older or less airtight construction.

Floor and partition data — covers heat transfer through floors and interior partition walls, relevant particularly where a space borders an unconditioned or differently-conditioned area.

Why Getting This Right Matters More Than the Software Itself?

It's worth being direct about something the marketing around any load calculation software tends to gloss over: the software doesn't know whether your input data is accurate. A confidently generated, professional-looking report built on assumed occupancy numbers or a generic wall assembly instead of the actual specified construction will still produce a number — just not a trustworthy one.

This is really the core discipline HAP (or any load calculation software) demands of an engineer: knowing which inputs genuinely reflect the building being designed, and which ones are being defaulted or assumed because the actual data isn't available yet. Recognizing the difference — and flagging it rather than quietly proceeding — is the skill that separates a reliable load calculation from one that merely looks reliable.

Why This Skill Is Worth Building Early?

Load calculation software is genuinely central to HVAC design work, and fluency with tools like HAP is a real, in-demand skill across MEP consulting and contracting roles. But the tool itself is teachable in a way that judgment about input data isn't — understanding which inputs matter most, and developing an instinct for when a default assumption is good enough versus when it needs to be replaced with real building-specific data, is something that develops through practice and, ideally, mentorship from someone who's already made those judgment calls many times over.