EnergyPlus

Welcome! Please add your suggestion below or vote on other ideas for improving EnergyPlus following the posted guidelines.

This website is exclusively for ideas and suggestions for the EnergyPlus simulation engine.

This site is NOT intended for:

To link a suggestion to an existing Unmet Hours question or GitHub issue, simply copy and paste the URL into the suggestion.

How can we improve EnergyPlus?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Add Radiant Terminal Units to HVAC Templates

    Add a HVAC template for radiant zone terminal units. Currently (v8.7), if you want to implement radiant with DOAS, then you have to use a roundabout way of implementing it by first using the baseboard heat template and then replacing the objects. It would be nice to have the radiant terminal units as an option in the templates.

    4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Input  ·  Admin →
  2. Expand Autosizing for CHP

    Some input fields are not autosizable but it would be helpful if they were. For example the combined heat and power models have heat recovery plant connections but the plant flow rates are not autosizable making it difficult to use them in many models. Suggest to add autosizing to heat recovery in Generator:InternalCombustionEngine, Generator:CombustionTurbine, and Generator:MicroTurbine objects.

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Input  ·  Admin →
  3. Add new Schedule object that is based on weather

    Add a new Schedule type to EnergyPlus called Schedule:WeatherFile that could basically create a schedule by reading the weather file and testing a threshold. It seems like it would solve some simple issues of turning on and off all sorts of stuff in EnergyPlus based on outside temperature or humidity or whatever. I know if could be done in EMS but this would be simpler for most users. It would generate two different values (usually 0 and 1) depending on if the value from the weather file is above or below the threshold value.

    Schedule:WeatherFile

    Name

    ScheduleTypeLimits

    WeatherFileVariable (dry bulb,…

    4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Input  ·  Admin →
  4. In IDF Editor automatically extend extensible fields

    Currently IDF Editor shows a warning of "too many fields" when an IDF file is opened and a specific object has more fields than the number of fields defined in the Energy+.idd file when the object is extensible. Add a feature to automatically extend these fields in the IDF Editor.

    4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Input  ·  Admin →
  5. A new Data:File object

    Problem: E+ does not have an object, containing an external file with multiple independent and dependent variables.

    Rationale: Some type of datasets may contain multiple independent and dependent variables. E+ have objects, either to handle multiple independent variables and a single dependent variable, such as Table:* objects, or to have a single independent variable and multiple dependent variables, such as Schedule:File. The proposed object may allow users to import data from an external file with multiple independent and dependent variables, so that a user may need a single file with all possible datasets, such as optical properties:
    Multiple independent variables:…

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Input  ·  Admin →
  6. Add support for ASHRAE Standard 205 data representations

    Problem: Curve fits of manufacturer data are onerous and error prone.

    Rationale: Using standard data representations that are generated by manufacturers and read directly into EnergyPlus will eliminate substantial effort on behalf of energy modelers.

    Solution: ASHRAE Standard 205 defines such data representations (currently for liquid cooled chillers, unitary air conditioning equipment (i.e. DX cooling coils), and fan assemblies. Routines to read Standard 205 data and simulate the respective equipment should be added to EnergyPlus.

    Context: Read Standard 205 title, purpose and scope here: https://www.ashrae.org/standards-research--technology/standards--guidelines/titles-purposes-and-scopes#SPC205P

    Pros and Cons:
    + less work for modelers
    + standard data models lend themselves to…

    4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    in discussion  ·  0 comments  ·  Input  ·  Admin →
  7. Counter flow vs. parallel flow coil parameter

    For the clarification on counter flow vs. parallel flow coil parameter, it is not clear what’s the difference between the two settings.

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Input  ·  Admin →
  8. Support schedules as an input for all possible fields for all EP objects

    Currently only a number of inputs in energyplus supports annual schedules and for others advanced methods such as EMS should be used. Here is an example. https://unmethours.com/question/13279/change-u-value-of-construction-during-the-simulation-with-eplus/

    4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Input  ·  Admin →
  9. Add New EMS Actuators (Surface Outside Face*)

    Add new EMS available actuators. For example: Surface Outside Face * (Sunlit Area, Incident Solar Radiation, Incident Beam Solar Radiatio... etc)

    Thanks!

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Input  ·  Admin →
  10. Make "thickness" a property of the construction, and not the material

    Problem: For each different thickness of a material, I need to repeat the intensive properties (conductivity, density, and specific heat) in a separate Material object.

    Solution: The construction should specify two inputs for each layer: (1) a Material object reference (intensive properties only) and (2) the layer thickness.

    18 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Input  ·  Admin →

    We’re always looking for ways to make EnergyPlus more usable. We don’t have immediate plans to work on this as the current paradigm offers the same capability, albeit in a somewhat redundant manner. Once we address some higher priority usability issues, we’ll come back to this suggestion. Thank you for your suggestion.

  11. Remove redundant 'Branch', 'BranchList', and 'ConnectorList' objects

    Problem: EnergyPlus should be able to determine fluid paths of plant and air loops from node connections alone. 'Branch', 'BranchList', and 'ConnectorList' objects reference extra unnecessary information, making them redundant.

    Rationale: Currently, 'Branch' objects request individual plant or air loop components placed in series and the inlet / outlet node names of each component. 'BranchList' objects request names of 'Branch' objects located on the same side (supply or demand) of a plant or air loop. 'ConnectorList' objects request names of 'Connector:Splitter' and 'Connector:Mixer' objects on the same side (supply or demand) of a plant or air loop.

    Individual components of…

    11 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    in discussion  ·  1 comment  ·  Input  ·  Admin →
  12. Allow Components to be Simulated in a Stand-Alone Mode

    Problem: To test new objects (including air systems) and get a feel for how they work, one has to create an entirely new building model. This is time consuming and distracts from the component one wants to test.

    Solution: Rework EnergyPlus to be more flexible in terms of what it defines as a model. Create "input" and "output" objects that allow setting up the input and output conditions around components to simulate the given objects to allow users to get a good feel of how they work and to allow developers to better test objects together or in isolation. This…

    11 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Input  ·  Admin →

    This is one of the primary objectives of the SOEP project and fits well into the Modelica simulation paradigm.

    LBNL SOEP website: https://lbl-srg.github.io/soep/index.html
    GitHub: https://github.com/lbl-srg/soep

    Moving forward, the EnergyPlus team plans to focus more on adding new features as units that can be tested independently from the rest of the building model. The approach will be somewhat piecemeal depending on funding and priority.

  13. Change On / Off input field names to a Yes / No question

    Problem: Some input fields ask for a value of 1 to turn something on or 0 to turn something off. An example is the "Fraction Replaceable" field for Lights objects, which determines whether daylighting controls can change internal light use (enter value of 1.0) or whether daylighting controls cannot change internal light use (enter value of 0.0). The name "Fraction Replaceable" isn't immediately clear as to what aspect of the model this input field is changing.

    Rationale: Most input field names aren't inherently clear what they're changing in the model. If the input field was a question, "Allow daylighting controls?",…

    4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Input  ·  Admin →
  14. Replace IDF with a standardized data format (e.g., JSON, XML, etc.)

    Problem: IDF is non-standard, non-extensible, and positionally dependent.

    Solution: Moving to a key-value pair style input (instead of positional) means:

    * Better handling of defaulting fields (no explicit blanks).

    * Long lists can be infinitely extensible (the schema doesn't need to specify fields for items 1-N, like the IDD does).

    * Transitions between versions of objects is handled more simply.

    20 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    in progress  ·  6 comments  ·  Input  ·  Admin →
  15. Create scripting language bindings

    Problem: Writing and compiling C++ is daunting and prevents many users from contributing to the source code.

    Solution: Create scripting language bindings (e.g., Python or Ruby), that allow users to prototype new features that simulate at runtime.

    Dependency: Expanded API (http://energyplus.uservoice.com/forums/258860-energyplus/suggestions/9676680-expand-the-energyplus-api-library-to-expose-intern)

    7 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Input  ·  Admin →
  16. Reduce the number of component sub-categories

    Problem: There several components with multiple object types (e.g., there are five object types for fans). It is not always clear which object types should be used in what contexts. This is a level of complexity that makes it difficult for users learning the program.

    Furthermore, changing an object type requires changes anywhere the object is referenced since a component is uniquely identified by both the object name and the object type.

    Several examples are shown below:

    * Fans (5)
    * Coils (34)
    * Pumps (5)
    * Pipes (5)
    * Chillers (8)
    * Boilers (2)
    * Heat Pumps (4)
    *…

    9 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    in discussion  ·  1 comment  ·  Input  ·  Admin →
  17. Integrate version transition programs into main executable

    Problem: Transitioning an IDF to a newer version of EnergyPlus requires a fairly manual process.

    Solution: It would be nice if the transition rules were built into the executable and triggered with a command line flag.

    7 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    in discussion  ·  0 comments  ·  Input  ·  Admin →
  18. Add a "Zone Type" field for the Zone object

    This field could be used to reference all the zones of a same type when writing EMS program or when writing custom scripts (ie, python using the eppy library).

    The ZoneList object can be used for this purpose but having a dedicated field in the Zone object could be more convenient.

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Input  ·  Admin →
  • Don't see your idea?

Sign in to suggest ideas, vote, or participate in polls for your favorite feature request!

Feedback and Knowledge Base