ASHRAE 90.1 Workflow Updates

Since launching our ASHRAE 90.1 duel-workflow for the Performance Cost Index and Energy Cost Budget Method compliance, we've spent a good chunk of time talking to users about where things stand and, more usefully, where they should go next.

Those conversations pointed pretty clearly to three areas worth addressing: reporting, HVAC transparency, and Imperial units. So that's what we built.

Our ASHRAE 90.1 Reporting

Automated reporting is one of those things that sounds like a nice-to-have until you've filled out your fifth PDF by hand. Anyone who has run a compliance model knows the drill: the simulation is done, the numbers check out, and then you spend another afternoon manually transcribing outputs into a submission template that someone designed in 2009 and has not been touched since.

We've aligned our outputs to standard reporting requirements so that step is handled automatically. The reports come out formatted and ready to submit, not as a data dump you have to interpret and reformat yourself. Right now this covers the core ASHRAE 90.1 compliance documentation, and we expect the scope to expand as more jurisdictions and state-level modeling mandates come into the picture. The structure is there to support that without it becoming a bespoke exercise every time.

HVAC Specification Transparency

This one matters more than it might sound, and it gets at something that frustrates a lot of energy modelers: the gap between what you specified and what the software actually modeled. We've reworked how HVAC specifications are presented so that both the baseline (or budget) and proposed systems are visible in a clear, parallel view.

System type, capacity, efficiency ratings, ventilation rates, controls logic, the things that actually drive your energy results are now surfaced in a readable format rather than buried in input screens or inferred from outputs after the fact. The goal is to give you a legible audit trail: here is what was specified, here is what was modeled, here is why the numbers look the way they do. Less archaeology when a reviewer asks a question three weeks after submission.

It also makes the baseline generation process more reviewable and also editable. Automated baseline assignment is convenient right up until someone queries your system type selection, and having a transparent view of both sides makes that conversation significantly less painful.

Imperial Units

Yes, we were biased toward metric. We knew it, and we've done something about it. All inputs and outputs are now being identified and made available in Imperial units as well, so if you're working in the US market and have spent any time converting W/m² back to BTU/h·ft² in your head, that tax is going away.

It sounds like a straightforward find-and-replace exercise. It is not. When you have a large number of inputs and outputs accumulated across different calculation modules over time, the audit process surfaces inconsistencies you didn't know were there, and fixing them properly takes longer than anyone's initial estimate suggested. But it's nearly done, with the final pushes landing in the next week.

---

If you have questions, feedback, or 20 minutes to walk through the platform and point us toward what's next, we'd genuinely like to hear from you. In return: a 50% time saving on your next project (we're confident enough to say it) and extended free access to the platform.