What HVAC Engineers Actually Expect from Product Selection Software

Consulting mechanical engineers are not easily impressed by software. They've seen too many tools that look polished but produce outputs they can't defend in a technical review. When they find one they trust, they use it repeatedly and recommend it to colleagues. When they don't trust it, they work around it — using their own calculations and ignoring the tool entirely.

For HVAC manufacturers, understanding what engineers expect from selection software is critical. The tool your sales team gives consultants either builds credibility for your products or quietly undermines it.

The engineering bar is higher than you think

A consulting engineer specifying an energy recovery ventilator for a commercial project is responsible for guaranteeing performance. If the unit doesn't deliver the promised efficiency, they're the ones defending the design in a dispute. That means they need to trust the numbers — not just accept them.

Engineers trust software when they can verify the calculations against first principles and get the same answer. They don't trust software when the numbers seem reasonable but the methodology is opaque — or worse, when they can catch the tool in an error.

Getting caught once is enough. A selection tool that produces an obviously wrong output — even in an edge case — becomes a tool that engineers don't use.

What engineers actually look at

Based on the way consulting engineers interact with selection tools, the specific things they verify are consistent:

Fan curve accuracy

The operating point — where the fan curve meets the system resistance — needs to be correct. Engineers will check this against manufacturers' published data. If the tool shows a different operating point than the published curve, it loses trust immediately. The fan curve must be interpolated from actual test data, and the operating point must be clearly shown with the correct airflow and total static pressure at that point.

Psychrometric calculations

Heat exchanger performance involves both sensible and latent heat transfer. An engineer specifying a unit for a humid climate will check the supply air wet bulb temperature and relative humidity at the unit outlet. If these are wrong — if the tool is only doing a sensible calculation and labelling it as a full enthalpy calculation — they will catch it. Humidity ratio, enthalpy, and dew point need to be calculated correctly from actual psychrometric relationships, not approximations.

Coil performance

For cooling coil selections, the LMTD method or the ε-NTU method needs to be implemented correctly. Engineers will cross-check coil capacity, water flow rate, and pressure drop against their own calculations. A tool that doesn't show water-side pressure drop, or that calculates it using a simplified assumption, will be questioned. The coil selection needs to show rows, circuits, face area, and velocity — all verifiable against the coil manufacturer's published data.

Design conditions

Summer and winter design conditions should come from a recognised source — ASHRAE fundamentals, or equivalent local climate data. If the tool asks the engineer to input outdoor conditions manually without providing reference data, they'll spend time looking it up elsewhere. If the tool provides it automatically for the project location, they trust it more and use it faster.

The output matters as much as the calculation

Engineers don't just check the numbers — they use the output document in their specification package. The specification sheet needs to show everything a mechanical engineer needs to include in a tender document:

• →Unit model and configuration
• →Airflows (supply, extract, outdoor, exhaust) in L/s or m³/h
• →Fan operating point — airflow and static pressure, shown on the fan curve
• →Motor power, current, and electrical data
• →Heat exchanger performance — sensible and latent efficiency, outlet conditions
• →Coil data — duty, water temperatures, flow rate, pressure drop
• →Sound power levels across octave bands
• →Dimensions and weight
• →Filter specification

If the specification sheet is missing critical data — or if it's formatted in a way that makes the data hard to extract — engineers will either supplement it with their own calculations or ask the manufacturer for a more detailed submittal. Both outcomes create friction that erodes the tool's usefulness.

Speed matters — but only after accuracy

Engineers appreciate fast tools, but they won't use a fast inaccurate tool over a slower accurate one. The sequence is: get the engineering right, then optimise the experience. A tool that produces the right answer in five minutes is infinitely more valuable than one that produces a questionable answer in thirty seconds.

That said, once the engineering is solid, experience matters enormously. If a consultant can complete a selection and generate a specification sheet faster with your tool than with a competitor's, they will specify your product more often. Friction in the workflow costs market share — it just has to come second to accuracy.

What this means for manufacturers

If you're considering building a selection tool — or replacing an existing one — the engineering has to come first. That means:

• →Fan curve data built from actual test results, not catalogue approximations
• →Psychrometric calculations that handle both sensible and latent correctly
• →Coil selection using a recognised heat transfer method (ε-NTU or LMTD)
• →Climate design conditions from ASHRAE or equivalent, linked to project location
• →Outputs that match what consulting engineers include in tender documents

Cutting corners on any of these will eventually surface in a technical review — and when it does, it reflects on your product, not just your software.

A well-built tool, on the other hand, becomes an asset. Consultants who trust it will use it on every project. Your products get specified more often, with fewer calls to your engineering team, and with a professional documentation trail that supports the sale from specification through to installation.