AHU Selection Projects: Define the Market Requirements

An AHU software brief needs more than a component list. The destination market, project specification and manufacturer's responsibilities affect the information your selection workflow must capture.

Start with a requirements register

For each project, record the destination market, unit type, operating conditions, applicable publications and the edition or effective date being used. Have the responsible engineer confirm the requirements before turning them into software acceptance criteria.

Request evidence for each result

A document should make its operating conditions, component sources and calculation assumptions understandable. Ask how unsupported data and incomplete selections are identified. Keep the engineering review separate from commercial acceptance of the software.

Define the deliverables

Agree the required PDF content and DXF drawing conventions. If the project also needs a BIM model, a bill of materials, a pricing interface or a particular report layout, include it explicitly in the proposed scope.

AirSelect3D demonstrations and pricing are provided by quotation. Contact the team with a representative project, supplier list and required outputs.