Creating Energy Meters

Modified on Fri, 12 Jul at 10:54 AM

Introduction


The Output:Meter in EnergyPlus simulations is a powerful class for grouping and reporting energy consumption data. It allows users to track, report and analyse various aspects of building energy use, from overall facility consumption to specific end-uses in individual zones. By understanding the structure and options available, users can create reports to suit their specific analysis needs.


Definition

The following meters can be defined with EMS scripts functionality and you can request additional outputs for your simulationThere are six forms that require predefined keywords or user-defined inputs to generate a wide range of energy meters. Energy meters are added to the eplusout.eso file and results which can be viewed in Results Viewer.


The Output:Meter object is defined from 3 fragments in the following structure:


Output:Meter, Meter Name, Reporting Frequency;

The Meter Name field is available in one of six forms that are built from different keywords:


1<ResourceType>:<GroupType>
2<EndUseType>:<ResourceType>
3<EndUseSubcategory>:<EndUseType>:<ResourceType>
4<ResourceType>:Zone:<ZoneIDFName>
5<EndUseType>:<ResourceType>:Zone:<ZoneIDFName>
6

<EndUseSubcategory>:<EndUseType>:<ResourceType>:Zone:<ZoneIDFName>


Keywords ResourceType, EndUseType, GroupType are predefined by the software and available only with these forms.

 
ResourceTypeEndUseTypeGroupType
ElectricityInteriorLightsFacility
NaturalGasExteriorLightsBuilding
GasolineInteriorEquipmentZone
DieselExteriorEquipmentHVAC
CoalFansPlant
FuelOilNo1Pumps
FuelOilNo2Heating
PropaneCooling
OtherFuel1HeatRejection
OtherFuel2Humidifier
WaterHeatRecovery
SteamDHW
DistrictCoolingCogeneration
DistrictHeatingRefrigeration
ElectricityPurchasedWaterSystems
ElectricitySurplusSold

ElectricityNet




EnergyTransferHeatingCoils

CoolingCoils

Chillers

Boilers

Baseboard

HeatRecoveryForCooling

HeatRecoveryForHeating


Note: The last 7 EndUseTypes from HeatingCoils to HeatRecoveryForHeating can be combined only with EnergyTransfer ResourceType.


The EndUseSubcategory keyword is defined by the user and depends on the inputs defined in the HVAC components or gains on the activity tab.


The ZoneIDFName keyword is also defined by the user and depends on the block and zone names used in the model.



GroupType Hierarchy

Facility meters contain all the energy of the model.

Building meters contain the sum of each zone’s energy. 

HVAC meters contain the energy from the air loops and zone HVAC system components. 

Plant meters contain the energy from the plant and condenser loops and their equipment.
Exterior meters contain the energy from the exterior components such as exterior lights.

Zone meters contain the energy from interior equipment and interior lights.


Thus, the following relationships should be observed: 


Reporting Frequency

Common options include Timestep, Hourly, Daily, Monthly and RunPeriod. 


Diagnostics

If a meter doesn't appear in the Results Viewer, check the eplusout.err file or the eplusout.mtd file. The latter contains a detailed list and explanation of all meters for a given run and the component values accumulated on each meter.


Examples


1. Total facility electricity consumption (hourly):
Output:Meter, Electricity:Facility, Hourly;


2. Building natural gas consumption (monthly): 

Output:Meter, Gas:Building, Monthly;
3. Cooling electricity use (run period): 
Output:Meter, Cooling:Electricity, RunPeriod;


4. HVAC water consumption (daily).

Output:Meter, Water:HVAC, Daily;


5. Plant water consumption (daily). It will collect data for cooling towers and domestic water heaters.

Output:Meter, Water:Plant, Daily;


6. The "Level1:BlueOffice" zone-specific interior lighting electricity use (timestep):

Output:Meter, InteriorLights:Electricity:Zone:Level1:BlueOffice, Timestep;

7. Chiller energy transfer (hourly): 

Output:Meter, Chillers:EnergyTransfer, Hourly;


8. Boiler energy transfer (daily):

Output:Meter, Boilers:EnergyTransfer, Daily;


9. Heat recovery for heating energy transfer (monthly): 

Output:Meter, HeatRecoveryForHeating:EnergyTransfer, Monthly;


10. Cooling coil energy transfer (run period):

Output:Meter, CoolingCoils:EnergyTransfer, RunPeriod;


Diagnostics and Troubleshooting


Key Diagnostic Files

  1. eplusout.err: error messages and warnings
  2. eplusout.mtd: detailed meter list and composition
  3. eplusout.eso: raw output data


Common Issues and Quick Fixes

  1. Missing Meters -> Check spelling, component existence, and model compatibility
  2. Unexpected Zero Values -> Verify component connections, schedules, and sizing
  3. Unrealistic Values -> Check units, input data, and modelling assumptions
  4. Inconsistent Totals -> Review subcomponents, avoid double-counting, ensure consistent reporting
  5. Simulation Crashes -> Invalid meter name, while this usually results in a warning, severe misconfigurations might crash the simulation


Troubleshooting Steps

  1. Isolate the issue
  2. Verify inputs
  3. Review output files
  4. Compare with expected results
  5. Consult EnergyPlus resources
  6. Iterate and test changes systematically

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article