Skip to content

Output Reporting

The primary goal of modeling is seeing the results of the model contained in the output reporting. EnergyPlus has several different types of outputs, but initially the most important to understand are the tabular output reports that summarize the results of the simulation. The Output:Table:SummaryReports and OutputControl:Table:Style input objects described below are the only two necessary to start generating the tabular output reports:

  • Output:Table:SummaryReports - allows the specification of different tabular reports but usually just specifying AllSummary is necessary. Additional reports can be shown by specifying AllSummaryAndMonthly, AllSummaryMonthlyAndSizingPeriod.
  • OutputControl:Table:Style - specifying the output format for the tabular reports which is most commonly HTML but a comma, tab, fixed width, and XML options are also available. Depending on what is specified the output reports can have different file extensions and the file name usually has the word "Table" or "tbl" in it.

You can also create your own custom tabular reports by using one of the following input objects:

  • Output:Table:TimeBins - shows the amount of time in hours that occurs in different bins for the single specific output variable or meter specified
  • Output:Table:Monthly - shows a series of output variables or output meters on a monthly basis using different aggregation schemes. For output variables that reoccur for each zone or other input objects, the monthly report will be repeated for each one.
  • Output:Table:Annual - shows a series of output variables or output meters on an annual basis using different aggregation schemes. For output variables that reoccur for each zone or other input objects, additional rows of results will be displayed.
  • Output:VariableDictionary - provides a list of available output variables for use with these custom tabular reports as well as the time step reporting described next. The list of output variables that are available for specific simulation appear in a file with a .rdd extension, and the output meters appear in a file with a .mdd extension.

When you need to dive deeper into the results for a specific output variable or output meters, time step outputs allow you to see the values of an output variable for each timestep or other time periods. By looking at multiple output variables and seeing how they change together over time, a deeper understanding of the system and control operation can be gained.

  • Output:Variable - these input objects are added one for each output variable desired. Usually, an asterisk is used for the "key value" field so that all instances of the output variable are included. The output shows up in the .eso file which is generally converted to a .csv file for use with a spreadsheet.
  • Output:Meter and Output:Meter:MeterFileOnly - these input objects specify the output meters (think of them as very detailed submeters). The output from these input objects show up in the .mtr file which is generally converted to a Meter.csv file for use with a spreadsheet. Also, note that the .mtd file shows the exact relationship between specific end-use output report variables and each output meter.
  • Output:SQLite - use this input object if you want to output in the SQLite database format. Not only can the output variables and meters be in SQLite format but the tabular reports are also included.

EnergyPlus also includes a number of special reports that usually appear in different output files or in the .eio output file

  • Output:Surfaces:List - provides a report on all the surfaces in a file and the output appears in the .eio and .sln output files.
  • Output:Surfaces:Drawing - provides a DXF drawing that can be opened in some CAD programs .
  • OutputControl:SurfaceColorScheme - controls the colors used in the DXF file.
  • Output:Schedules - provides a summary of the schedules in the input file and appears as part of the file with the .eio extension.
  • Output:Constructions - provides a summary of constructions in the input file and appears as part of the file with the .eio extension.
  • Output:EnergyManagementSystem - creates a list of detailed output related to the energy management system in a file with the .edd extension.
  • OutputControl:ReportingTolerances - provides more control over the amount of time reported for the setpoints not being met.
  • Output:Diagnostics - provides additional detail in the output messages in the .err file . Normally this extra detail is not shown to reduce confusion for new users.
  • Output:DebuggingData - provides an additional detailed output related to HVAC nodes in a file with a .dbg extension.

Environmental reporting adds new meters showing the emissions related to the building and is triggered by the use of the following three input objects. See the 5ZoneTDV.idf file for examples.

  • Output:EnvironmentalImpactFactors - specifies the frequency of the output variables related to emissions.
  • EnvironmentalImpactFactors - specifies the efficiency of district heating and cooling systems as well as the carbon equivalent emission factors for N20, CH4, and CO2.
  • FuelFactors - for each type of energy resource (electricity, natural gas, etc..) provides a way to enter factors related to source energy and emissions of CO2, CO, CH4, NOx, N20, SO2, PM, NH3, NMVOC, Hg, Pb, and other factors.

Other input objects in this group allow the accumulation of metered results, the combination of output variables or meters to create custom meters, and a method for preprocessors to include error messages in the normal error file. Many example files contain some of these input objects. All of these are described in the "Input/Output Reference" but note that this group is described in Chapter 5 "Input for Output" and Chapter 7 "Standard Output Reports" while most of the other groups of input objects are described in Chapter 1. The OutputDetailsAndExamples documentation provides even more details on the outputs created by each of these input objects. Several other output related input objects appear in other areas such as Output:DaylightFactors input object in the Daylighting group.