Same standard, every office: standardizing energy models across teams with EP3
Here is a situation most firm leads will recognize. Two modelers in two offices are each asked to model a “high-performance glazing” measure on a mid-size office building. One lowers the U-factor and SHGC on the existing window construction. The other builds a new construction with a different product in mind. Both apply the same VAV reheat system as the base case, but one hard-sizes the fans, the other autosizes them, and their minimum flow fractions and economizer limits differ.
Both models are defensible. The savings come out different, and nobody can say whether that is the building or the modeler. The reviewer has to read both models field by field to find out, and the client who owns both buildings sees two numbers that don’t line up.
EP3 was born out of frustration with existing modeling tools, and this was a big part of it. In EP3 a firm defines its standard once and every modeler builds from it.
A template is just a model in a shared folder
In EP3, any model saved into a library folder becomes a template. EP3 reads what the file contains and offers each piece in the right place: space and zone types, constructions, HVAC and service hot water systems, and the EEMs that go with them.
Library folders are set under Library Locations in Application Settings. Each modeler adds the firm’s folder once, and from then on the firm’s templates appear next to EP3’s built-in library, grouped by folder name so it’s clear which ones are the firm standard. Put that folder in a cloud-synced location such as Dropbox or OneDrive, and every office reads from the same library.
What goes into the library:
- Space and zone types. A space type carries the lighting, occupancy, equipment, infiltration and schedules for that space. It is paired with a zone type carrying the thermostat, zone sizing and, where it applies, domestic water use. Pick “Open Office” and the whole set arrives already connected.
- Constructions. EP3 ships construction sets organized by climate zone. A firm can save its preferred assemblies the same way, with the materials they reference.
- HVAC and service hot water systems. Each system arrives as a complete, connected system, with its curves, schedules and plant loops. The handbook recommends a four-step check before a system goes into the library: build it, simulate it, save it, then import it into a fresh model and simulate again. Do that once, and every office reuses a system that has already been tested.
- EEMs. A template file can carry measures along with the objects they change. When a modeler picks a template, EP3 offers only the EEMs that change something that template brings in. Your “high-performance glazing” measure is defined once, with the values your firm stands behind.
The Wizard as a common starting point
Most EP3 projects start in the Model Wizard. The modeler checks off the space types, construction set, service hot water and HVAC systems for the building, and the Wizard assembles a complete, simulation-ready model in one pass.
Each HVAC system checked in the Wizard becomes a separate EEM, ready to compare. If the firm’s standard comparison for a mid-size office is VAV reheat against a fan coil system, every office starts that comparison from the same two systems.
Templates at any stage of the project
Templates are not limited to the first day. A space type missed in the Wizard, or a system needed later to evaluate a new measure, can be imported at any point. When names collide, the modeler chooses to keep the existing object, create a new one with a suffixed name, or overwrite it with the template values.
Every template import is recorded in the model’s import history. A reviewer can open it and see which firm templates went into the model, and when.
Simplified view: show modelers what the firm wants them to edit
EnergyPlus has thousands of fields, and most projects need a small share of them.
EP3’s simplified view hides rarely used object types and fields. The list of what stays visible is a plain file, and a firm can write its version and place it at the top of the shared library folder. Every modeler who uses that folder then sees the same reduced set of objects and fields. Required fields that have no default always stay visible, so a short company list can’t leave a model incomplete.
Simplified view only changes what is displayed. The model, the EnergyPlus export and the validation checks all see every field. The Wizard turns simplified view on for new models, and an experienced modeler can switch to the complex view at any time.
One model, unlimited EEMs
An EP3 project uses one model, updated in place as the design develops. Design alternatives live inside that model as EEMs, and a model can carry as many as the project needs. Every measure runs against the same baseline in the same file, so comparisons stay consistent.
This is also where review gets faster. Each EEM lists exactly what it changes: every field with a custom value, and every object it switches on or off. When the baseline comes from firm templates, the reviewer can focus on the departures from the standard and skip what came straight from the library.
What the firm gets
- Consistent results. The same measure and the same system are modeled the same way in every office, so a difference in savings reflects the building.
- Faster review. Reviewers check what differs from the standard. The import history shows which templates were used.
- Faster onboarding. A new modeler starts from tested templates, in a view that shows the fields the firm expects them to touch.
- Portfolio comparisons. Owners and organizations running models across many buildings get results built on the same assumptions, so buildings can be ranked and compared fairly.
- Fewer errors. A system tested once and reused carries fewer surprises.
A note on AI
EP3’s AI assistant, Atlas, reads the model it is working on, so a model built from firm templates gives it a known, tested starting point. Atlas can’t change the model without the modeler’s approval, and every accepted suggestion is recorded in the same import history as the template imports.
Where to start
You don’t need a complete library on day one. A practical first set is the space types your firm models most often, one construction set per climate zone you work in, and the two or three HVAC systems that show up on most of your projects, each with the EEMs you routinely evaluate. Test each one, save it to the shared folder, and grow the library as projects come in.
At Infinite Atelier we help firms set up exactly this: building and testing a template library, writing a simplified view list that fits how your team works, and setting up the workflow across offices. If that would help your team, get in touch.
And a question for those of you running teams across several offices: what is the one modeling input you most wish everyone entered the same way?