The Air‑Conditioning, Heating, and Refrigeration Institute (AHRI) announced in August 2026 a new policy that will require certified HVAC equipment manufacturers to publish standardized, machine‑readable product performance files and offer API access to AHRI's Certified Ratings Directory (CRD). The move is intended to reduce friction in commissioning, streamline code compliance and enable faster integration with building automation, energy modeling and utility programs.
What AHRI's policy requires
Under the rollout plan AHRI published, manufacturers of equipment listed in the CRD — including residential and commercial heat pumps, rooftop units (RTUs), split systems, and packaged equipment — must provide a digital product data file for each certified model. The files must follow a prescribed schema that maps key test and performance attributes (capacity, rated and part‑load efficiencies, airflow characteristics, fan curves, control inputs/outputs, and declared nominal voltages) into machine‑readable formats such as JSON and XML.
AHRI will also publish a documented, authenticated API for the CRD so third parties can query certified performance data programmatically. The institute says the schema aligns with existing building‑data frameworks and ontologies — including Brick, Project Haystack and BuildingSync — to ease adoption by software vendors, commissioning professionals and utilities.
Timeline and scope
- August–December 2026: AHRI issues final schema, API specification and a set of validation tools for manufacturers to test export files.
- January 2027–December 2027: Compliance window for newly certified models; manufacturers may supply both human‑readable datasheets and machine files.
- January 2028: Requirement applies to all models listed on the CRD, including older models at the time of recertification.
AHRI framed the stepwise timeline as a balance between manufacturers' product‑data processes and the needs of downstream stakeholders such as energy modelers, controls contractors and utilities running demand‑response or incentive programs.
Why this matters to HVAC professionals
HVAC contractors, commissioning agents and controls integrators said that inconsistent product data formats are a chronic source of friction: manual lookups of datasheets, re‑entry of performance characteristics into commissioning software and mismatches between manufacturer declarations and what building automation systems expect.
Machine‑readable product files promise to:
- Reduce manual data entry during commissioning and pre‑construction BIM workflows.
- Make ASHRAE or code compliance calculations more repeatable by removing transcription errors.
- Allow energy‑model and controls vendors to auto‑ingest accurate manufacturer test data (EER/SEER/IEER, part‑load curves), improving simulation fidelity.
- Help utilities and aggregators verify baseline equipment parameters for incentives and aggregated load programs without repeated field verification.
Industry reaction and practical concerns
Manufacturers broadly welcomed the move toward standardization but flagged implementation costs and intellectual property concerns. Several manufacturers said they will need to adapt internal certification workflows and product lifecycle systems so the export files reflect the latest certified values.
Smaller equipment makers and private label assemblers noted that resources to develop export tooling are unevenly distributed across the supply chain. AHRI's rollout includes a vendor‑neutral validation toolkit and a scheduled set of webinars to help smaller firms comply.
Two practical concerns are likely to dominate conversations in the field:
- Version control and recertification: How CRD entries and machine files will reflect field changes, retrofits or later test updates to certified performance.
- Proprietary control sequences and IP: How to represent control logic without exposing proprietary algorithms. AHRI's schema separates physical performance data from control logic definitions and allows manufacturers to share declared control I/O mappings rather than full embedded code.
Implications for commissioning, codes and utilities
Commissioning providers see immediate benefits: access to validated fan curves, pressure‑flow data and part‑load maps reduces guesswork when balancing systems and tuning controls. Building departments and third‑party plan reviewers could also pull certified performance data directly when checking compliance with energy codes, potentially shortening plan review cycles.
Utilities that run incentive programs for efficient HVAC or electrification projects could leverage the API for faster pre‑approval and post‑installation verification. The AHRI specification includes fields for declared rated conditions and test methods, which helps align incentive rules with certified test standards.
What to expect next
Through the remainder of 2026 AHRI will finalize the schema and publish sample files. Tool vendors — from energy‑modeling software to building automation vendors — are expected to announce integrations during 2027. Contractors and commissioning firms should begin updating procurement and submittal checklists to require machine‑readable product files or CRD references.
For HVAC technicians and system integrators, the change will mean fewer PDF hunts and more direct data flows from manufacturers to jobsite software, with the potential to speed up commissioning and reduce rework. The degree to which the industry realizes those gains will depend on the quality and completeness of the initial manufacturer‑supplied files and how quickly software vendors add automated import capability.
AHRI's move marks a milestone in making HVAC performance data first‑class, machine‑consumable infrastructure. For an industry that increasingly sits at the intersection of buildings, utilities and software, standardized product files and a public API could be the plumbing that unlocks faster electrification, cleaner operations and better field workflows.