Energy modeling budgets are typically structured around compliance — the permit submission, the incentive application, the final report. That’s where the funding is, so that’s when the model gets built. By then, the decisions that matter most have already been made. The massing is locked. The mechanical system is chosen. The window to actually influence the building’s performance has quietly closed.
Early-stage modeling does happen, but it’s the exception — reserved for well-resourced projects where someone can justify maintaining two parallel workflows in two separate models. For everyone else, the tool overhead makes it impractical: every scenario lives in its own file, every design change has to be reconciled across all of them, and that overhead compounds fast. It’s not a lack of intent. It’s a structural problem with how traditional modeling tools work.
EP3 changes that equation. Because every EEM lives in the same file as your baseline, a single model can serve the full arc of a project — from early massing studies through to final compliance. There’s no separate exploratory model to maintain, no reconciliation pass when the design moves on. The same model that informed the schematic design decision is the one that gets submitted at the end.
One Model. Evaluate Everything.
In EP3, energy efficiency measures are integrated directly into you energy model in a single file. Not separate files linked by a script, not a parametric variable in an expression. One file, with every scenario you’re evaluating living inside it.
What this means in practice is that when something changes in the base model, whether it’s an updated operation schedule, a revised floorplan, a simplified roofline – that change flows automatically through every EEM you’ve defined. You make the change once. Every scenario inherits it. End of story.
No hunting down which files still have the old geometry. No wondering whether the infiltration rate got updated in all HVAC alternative files. No rebuilding alternatives from a new master model because this is slightly less painful than reliably making a geometry change across multiple files.
Stop waiting for the design to stabilize
You don’t have to wait for the design to stabilize to start modeling or to provide design feedback. With EP3, you can define your efficiency measures at any stage, whether it’s at schematic design against a massing model, using a placeholder mechanical system, or during detailed analysis of a value-engineering item. Measures introduced early in the modeling process will still be there, consistent and current when you reach CDs.
When the design changes, you don’t rebuild or reconcile. The base model updates and every EEM reflects it. What that gives you isn’t just time saved, it’s the ability to hand the client a genuinely apples-to-apples comparison at any point in the project. The measures evaluated in month two are directly comparable to the measures evaluated in month ten, because they’ve all evolved from the same source.
This consistency is harder to achieve than it sounds. It’s the difference between being a resource the design team consults throughout the project and being the person who shows up at the end with a report nobody has time to act on.
Energy modeling has the potential to do more than validate designs. EP3 makes that possible in your professinal workflow.
One model, from first run to final submission
A few years ago we built an EP3 model for a hotel during schematic design. Rather than waiting for the design to stabilize, we used that early model to evaluate around thirty efficiency measures — testing combinations, narrowing the field, helping the owner understand the performance implications of their choices before those choices were locked in.
By the time the project reached the incentive submission, we had a final set of measures and a model that had traveled with the project the entire way. Then the authority introduced a new requirement: each measure had to be modeled individually, in a stacked incremental configuration — the baseline, then baseline plus the first upgrade, then that plus the second, and so on through the full list.
In a traditional workflow, that’s a significant reorganization of files that were never set up for it. In EP3, it meant reorganizing how the EEMs were applied, and took us about 5 minutes with a few clicks. The model we started in schematic design was the one we submitted. The audit trail was clean, the comparisons were consistent, and the story we told the reviewer traced directly back to the analysis we had been doing since day one.
That kind of resilience — the ability to absorb scope changes without a structural rework — is what makes it possible to say yes when a client asks “what if we swapped this out?” instead of quietly calculating how many hours the answer will cost.
A cleaner record for clients and reviewers
There’s another benefit that doesn’t always get counted: what a single-file model does for your credibility when it’s time to present results or submit for review.
When all scenarios live in the same file, the relationship between them is unambiguous. There’s no question of whether the baseline in file A is the same baseline as file B. No need to explain a version control system to a reviewer. No risk that someone opens the wrong file and draws the wrong conclusion.
Every EEM traces back to the same source. The comparisons are clean. The story is easy to tell.
The right tool for the whole project
If you’ve been waiting until late design to stand up your EEM comparisons, or spending hours reconciling changes across a folder of model files, I’d encourage you to see what a different workflow feels like.
Leave a Reply