ELCCA & LEED Documentation

Topic: Links to essential ELCCA & LEED documents, bookmarked and commented by Hargis Engineers.

ELCCA Documentation:

• ELCCA Guidelines, 2005
  
• Washington State Energy Code, 2004
• ASHRAE Standard 90.1-2004

LEED Documentation:

• LEED-NC v2.2 Rating System

Report Documentation:

• ELCCA Sample Report
  
• 8.5x11 "This Page Intentionally Left Blank" sheet
  
• 11x17 "This Page Intentionally Left Blank" sheet
  

Note: The above link(s) are only valid within the HEI intranet. Firefox users install the "IE Tab Plug-in", then right-click the link and select "Open in IE Tab" from the context menu.

eQuest Schedule Modification

Topic: Modifying the default eQuest schedules for schools

• Delete extra weeks
• Make all schedules consistent
• xx
• xx
  

Note: This is the sketch of an outline procedure, it will be updated.

The ASHRAE Appendix G Baseline

Topic: The latest edition of the ELCCA Guidelines calls for the comparison of the high-performance building alternative to a baseline building as defined by ASHRAE Standard 90.1-2004 Appendix G.


Eliminate self shading: SHADING-SURFACE = NO

eQuest Sensible Heat Recovery

Topic: Parametrically simulating sensible heat recovery in eQuest requires specifying a number of items in coordination to obtain meaningful results.

$ This example models a sensible-only, in-line flat plate air-to-air heat
$ exchanger (FP A2A HX) as the energy recovery equipment. Adjust the supply
$ and returns statics of the main unit to account for the increased pressure
$ drop, if the associated HX circuit not bypassed when off-line.
$ SUPPLY-STATIC = 2.5 (original, assume OSA not bypassed when HX is offline)
$ RETURN-STATIC = 1.6 (original, assume exhaust is bypassed when HX offline)
$ Parametric example, given the above initial statics:
SUPPLY-STATIC = 3.00
RETURN-STATIC = 1.60
$ Change the following keyword to YES in a parametric run; all other heat
$ recovery parameters are ignored when set to NO for the baseline case:
RECOVER-EXHAUST = NO
$ An FP A2A HX is a sensible-only heat recovery device:
ERV-RECOVER-TYPE = SENSIBLE-HX
$ Specify OA and EXH flows if only a fraction of the exhaust is recovered;
$ partial-recovery example is shown:
ERV-OA-FLOW = 22000
ERV-EXH-FLOW = 20000
$ Check manufactures data for effectiveness rating, efficiencies near 70% are
$ obtainable with FP A2A HX units:
ERV-SENSIBLE-EFF = 0.70
$ Control on the basis of differential temperature between exhaust and OSA; the
$ default deadband is 5°F and as such may be left unspecified:
ERV-RUN-CTRL = OA-EXHAUST-DT
$ Heat recovery is usually economic in the Pacific NW, OA-HEAT/COOL also an option:
ERV-RECOVER-MODE = OA-HEATING
$ FLOAT gives maximum heat recovery but recovers even unwanted heat, so
$ be sure to use mixed air reset for temperature control:
ERV-TEMP-CTRL = MIXED-AIR-RESET
$ Exhaust bypass control is typical for FP A2A HX:
ERV-CAP-CTRL = BYPASS-EXHAUST
$ This example uses main unit's fans for heat recovery:
ERV-FANS = HVAC-SUPPLY/RETURN
$ Keywords STANDARD and PREMIUM may alternately be specified here, but
$ the motor class parameter is not applicable to an in-line FP A2A HX:
$ ERV-MOTOR-CLASS = HI-EFF
$
$ Set the ERV OA static to zero, since in this example it is 'unswitched'
$ in series with the main unit; set ERV EXH static to the design pressure drop
$ across the HX (pressure drop IS switched).
$ If left undefined, both will default to 1.5 inches:
ERV-OA-STATIC = 0
ERV-EXH-STATIC = 0.4
$ This setting eliminates condensation and frost simulation warnings:
ERV-FROST-CTRL = USE-CAP-CTRL

Generally, air-to-air and passive-refrigerant heat recovery work out favorably as an energy efficiency measure in the Pacific Northwest. Using runaround circuits that introduce operational parasitics for heat recovery often makes the investment unattractive from an energy savings standpoint.

In hot and humid climate, better results may be obtained using a heat (enthalpy) wheel with sensible and latent recovery capability. Sensible-only as shown in the example above is economical in relatively low humidity, cool-summer climates that don't provide much summertime heat recovery opportunity.

To determine if total enthalpy recovery may be attractive, first calculate the theoretical summertime opportunity value:

• What are the estimated flow rates of the outdoor and exhaust airstreams?
• What are the outdoor air expected summer average conditions in terms of temperature and humidity (i.e. enthalpy)?
• What is the expected temperature and humidity of the exhaust airstream?
• The exhaust airstream in general occupancy applications can be estimated at about 85°F and 35% relative humidity, corresponding to the absolute moisture content at 55°F saturation temperature from a typical cooling coil, plus 2% for people and processes.
• Now the opportunity value of summertime heat recovery may be estimated:
• Calculate the enthalpy difference between the outdoor summer average and the estimated exhaust airstream, and multiply by the ratio of the exhaust/OSA flow rates.

Without significant differential enthalpy between outdoor ambient average and the exhaust airstreams, there simply may not be much summertime heat recovery opportunity.

ELCCA Report QC Checklist

Topic: A quality-control checklist for the ELCCA report, sampled from comments of the ELCCA reviewers

• Preface
• Verify date, client, analysts name and job number on title page
• Section 1 Executive Summary
  
• The executive summary should include a description of the overall project and how the building will be operated; refer page 41 to 2005 ELCCA guidelines. This should be covered by formula linking Paragraph A.1 & A.2 to Section 2; if not, then you're using an old template. Update from master template.
  
• Verify signature from architect and engineer have been obtained on the "Statement of Compliance" page; forward PDF copy of report if requested.
• Verify signed and dated professional engineers stamp at the lower right hand corner of the "Statement of Compliance" page.
  
• Verify there are no #VALUE! errors appearing in any calculations
  
• Section 1 PFEC
• Verify that the correct alternative has been selected
• Verify all "blue" input statements, and assure that they the agree with the selected alternative.
• Verify that the U-values calculated in Section 4 match the U-values shown on the PFEC.
• Section 6 High Performance Alternative
• Verify that the High-Performance Alternative has been compared to an ASHRAE 90.1-2004 Appendix G compliant baseline using packaged rooftop units, without "rotation averaging" or "glazing leveling", for purposes of energy goal comparison. If this baseline is not one of the standard alternates analyzed, then include an eQuest "Annual Utility Bills" report at the end of this section comparing this baseline to the best-performing parametric runs of the other simulations:
  

(click on the image to see a larger version)

• LCC, Estimate, & Maintenance Calcs
• Verify there are no #VALUE! errors in any calculations
• Appendices
  
• Verify contents of the PDF appendices; ensure that all sections have been exchanged from the template.
• Appendix A
• Verifying that all comments on the workplan have been addressed. Be sure that any supporting simulation reports required by the comments have been included in Appendix C (e.g. envelope alternatives, daylighting, etc.).
• Appendix A thru E:
  
• Verify that there are NO pages in the appendix which are carried over from an old job.
  
• Preprinting Final Check
  
• Do a keyword search on the name of the facility, city, architect and owner from which the template was copied; assure that all pages containing references to the previous facility, city, architect and owner have been exchanged.
  
• Note this doesn't mean 'do a search and replace'.
  
• Finding previous references indicates that pages in the PDF report document need to be replaced with output pages from the analysis.
• Perhaps an entire section or appendix was overlooked; skipping this step risks finding out from the owner, architect or reviewer after publication.
• Working from front to back and utilizing the PDF bookmarks, verify that all major sections (Table of Contents, 1.0, 2.0, 3.0 etc.) and lead sheet of each appendix begins on odd pages. Insert or delete an 8.5x11 or 11x17 "This Page Intentionally Left Blank" sheet as required.
• Source Spreadsheet
  
• QC checks for the authors only
• Click the 'Reset All Page Numbers' button to ensure proper page numbering prior to printing replacement pages.
• Note the integer value in the cell in the PFEC spreadsheet to the right of the EUI number. If it needs to be changed, reprint both the PFEC and Section 1.

Ground & Water Source Heat Pumps

Topic: Performance parameters of ground and water source heat pumps (@ about 1400 CFM & 8 GPM)

The table below is useful for evaluating the lifecycle costs of ground and water source heat pumps with relative efficiency ratings of "standard", "high" and "ultrahigh":

	Reference	Standard	High	Ultrahigh
WSHP	ARI EER[EIR] (85°F, cooling)	12.2[0.280]	14.0[0.244]	14.3[0.239]
WSHP	ARI COP[EIR] (70°F, heating)	4.14[0.242]	4.57[0.219]	4.70[0.213]
GSHP	NW EER[EIR] (56°F, cooling)	15.5 [0.220]	20.2[0.169]	23.4[0.146]
GSHP	NW COP[EIR] (50°F, heating)	3.76[0.266]	4.15[0.241]	4.30[0.233]

For water source heat pumps utilizing a fluid cooler in the maritime Pacific Northwest, Standard ARI Conditions are recommended with condenser water available at 85°F in the summertime for cooling, and 70°F in the wintertime for heating.

For groundsource heat pumps in the maritime Pacific Northwest, design conditions were estimated to provide 56°F condenser supply water temperature in the summertime for cooling, and 50°F in the wintertime for heating.

Equipment efficiencies are defined for eQuest in terms of the Electric Input Ratio (EIR), which is simply the inverse of the COP. Divide EER by 3.412 to obtain COP.

Compare the above performance numbers with those of the WSEC 2006 and ASHRAE 90.1 Appendix G, ... [TBD]

The following manufacturer and equipment model published data was used to compile the above table (note the relative subjectivity of the terms 'standard', 'high' and 'ultrahigh'):

Standard & High-Efficiency: ClimateMaster, Genesis Series, High and UltraHigh Efficiency
Ultrahigh Efficiency: Florida Heat Pump, ES Series, Two Stage R-410A

eQuest Multi-Level Spaces

Topic: Defining eQuest multilevel spaces is relatively simple, but there are a couple of issues to be aware of.

Rule #1: Unless your analysis specifically requires plenums, eliminate them by specifying the floor-to-ceiling height to be the same as the floor-to-floor height on Screen 1 of the shell editing wizard. This simplification will generally prove to be a big time saver going forward.

Rule #2: For atriums and multilevel spaces to be defined properly, the lowest-level shell must be unique. If the "Number of Floors" is greater than 1, you will not have the option of specifying the multilevel space height, as the inputs missing from the dialog box below illustrate by their absence.


Rule #3: Use "Number of Floors" multiplier for identical floors.

The "Zone Characteristics" dialog box above shows multilevel space editing for the multilevel shell, i.e. the "upper floors" from the second on up, which are identical. The image below illustrates how a single shell definition may be used with a floor multiplier of "8" applied. This multi-level shell has been placed "Immediately Above" the lowest level shell.


Rule #4: Elevate the roof of lowest level of the multilevel space, and delete the remaining roofs later in detailed edit mode.

The image above shows part of the roof of the unique lower-level shell, which extends underneath the upper-level shells. The part which is exposed when elevated will become the roof of the multilevel space; the remaining zone roofs for this shell should be removed later in detail edit mode.

The "Zone Characteristics" dialog box above shows multilevel space editing for the lowest level shell. When a constituent zone is specified to be a multilevel space, a shell without a floor multiplier should display a "Conditioned Height" input box. Getting it to appear may require clicking the "Zone Type" drop-down, and changing the space from "Conditioned" to "Unconditioned" and back again.


The image above shows the completed multilevel space, before the application of windows and skylights. Note that the exterior wall was automatically extruded simply by raising the roof.

eQuest Runaround Heat Recovery

Topic: Simulating runaround heat recovery in eQuest requires modifying the standard air-to-air heat recovery system

Suggest selecting system 'PSZ' for DX cooling or 'SZRH' for chilled water; other system selections may work satisfactorily. The following parametric components were utilized to obtain a combined $5,000 in savings (initially, without parasitics) on a $90,000 per year utility bill in the Pacific Northwest on a pair of 'PSZ' systems with heat recovery using 100% outside air.

$ Adjust the supply and returns statics of the main unit to
$ account for the increased pressure drop, originally:
$ SUPPLY-STATIC = 5.25
$ RETURN-STATIC = 2.60 (less delta-P, due to partial exhaust flow)
$ Example, given the above initial statics
SUPPLY-STATIC = 6.00
RETURN-STATIC = 3.00
$ Change the following keyword to YES in a parametric run; all other heat
$ recovery parameters are ignored when set to NO for the baseline case:
RECOVER-EXHAUST = NO
$ Runaround heat recovery recovers sensible energy only, no latent
ERV-RECOVER-TYPE = SENSIBLE-HX
$ Specify OA and EXH flows if only a portion of the exhaust is recovered
$ Partial recovery example
ERV-OA-FLOW = 46960
ERV-EXH-FLOW = 28590
$ Potentially the effectiveness can increase to 0.75 if a two-pass coil used
ERV-SENSIBLE-EFF = 0.53
ERV-RUN-CTRL = OA-EXHAUST-DT
ERV-RECOVER-MODE = OA-HEAT/COOL
$ FLOAT gives maximum heat recovery but recovers even unwanted heat, so
$ use the setting for temperature control
ERV-TEMP-CTRL = MIXED-AIR-RESET
$ modulation capacity control simulates variable-speed pumping
ERV-CAP-CTRL = MODULATE-HX
$ input maximum runaround pump power consumption here, it will be switched
$ on only when the ERV is activated
ERV-HX-KW = 4.5
$ use main unit's fans for heat recovery
ERV-FANS = HVAC-SUPPLY/RETURN
$ Keywords STANDARD and PREMIUM may alternately be specified here
ERV-MOTOR-CLASS = HI-EFF
$ Set the ERV statics to zero, since it is NOT a separate unit
$ in series with the main unit; i.e. pressure losses are 'unswitched'.
$ If left undefined, they will default to 1.5 inches:
ERV-OA-STATIC = 0
ERV-EXH-STATIC = 0
$ This setting eliminates condensation and frost simulation warnings
ERV-FROST-CTRL = USE-CAP-CTRL

However when the parasitic loads of the additional supply/return fan energy and runaround pump power are accounted for, eQuest demonstrates again that is difficult to break even with runaround heat recovery in this relatively mild maritime climate:

(click on the image to see a larger version)

eQuest Standard Reports

Topic: Suggested eQuest output reports for inclusion in ELCCA appendices

Input Data, Appendix B

Text (Simulation) File Reports:

• LV-A General Project Parameters, for selected alternative
• LV-B Summary of Spaces, for selected alternative
• LV-D Details of Exterior Surfaces, for selected alternative
• PV-A Plant Design Parameters, for each alternative
• SV-A System Design Parameters, for each alternative

Output Data, Appendix C

Text (Simulation) File Reports:

• BEPS Building Energy Performance Summary, for each alternative
• SS-D Building HVAC Load Summary, for each alternative
• SS-E Building HVAC Load Hours, for each alternative

Graphical Reports, Single-Run:

• Monthly Energy Consumption by Enduse, for each alternative
• Annual Energy Consumption by Enduse, for each alternative

Graphical Reports, Comparison:

• Monthly Total Energy Consumption, comparison of each alternative
• Annual Utility Bills by Rate, comparison of each alternative
• Monthly Utility Bills, comparison of each alternative

eQuest File Naming

Topic: Naming eQuest files in a consistent manner to create backups in the course of project development.

• Jobname - Wizard: eQuest project name at the end of the Wizard checklist including custom window and door placement, but before initiating detailed edit mode.
  
• Jobname - Envelope: eQuest project name at the end of envelope detailed edit modifications, including
  
• Addition of walls and windows missing at the end of Wizard edit,
  
• Renaming of spaces, zones and systems and
  
• Assignment of baseline constructions, and
  
• Schedule modifications
  
• The model at this point is ready to begin simulation
  
• Jobname: Working project file name. This file contains the 'moving forward' baseline simulation model.

Note: This is an outline procedure, it will be updated as time permits.

Updating eQuest Utility Rates

Topic: How to keep utility rates current by editing the library file.

• Open the local eQLib.dat file with a text editor
  
• Find utility rate section to be updated, e.g. search for 'PSE', 'SCL' or 'Snohomish'
  
• Note the latest revision date at the beginning of the rate section
  
• Change only the rate needed, e.g. Schedule 36, Schedule 31, Schedule 20 etc.
  
• Add a 'rate changed', 'revised by' and 'date' comments for the latest revision
• BE SURE TO TEST the rate update in an actual simulation!
• If the test passes, run the 'Update eQuest' script to propagate the change
• If the test fails, run the 'Restore eQuest' script and start over
• If the test fails, DO NOT try to repair the library file as it may have been inadvertently damaged. Finding the damage is like finding the proverbial needle in a haystack, so best to limit losses and start over.
• NEVER leave the library file in a broken condition, else it may be propagated to other workstations.

Note: The above link(s) are only valid within the HEI intranet. Firefox users install the "IE Tab Plug-in", then right-click the link and select "Open in IE Tab" from the context menu.

Trace 700 Weather File Modifications

Topic: Trace 700 ships with a fixed set of weather files that are all installed with the program. Use the following procedure to modify a weather file for a new location.

• Find a weather file that's close
• Save as to new file name
• Edit the file and change if necessary the latitude, longitude and elevation
• Do not change any of the temperatures
• In the project weather screen, override the winter & summer design temperatures with the design temperatures for the new location.
• All hour by hour weather data will be shifted proportionally based on the difference between the design temperatures.
• Drawback: You have to remember to use the override every time

Note: This is an outline procedure, it will be updated as time permits.

Utility Incentives & Rebates

Topic: Links to selected Washington State utility company web pages describing their respective energy conservation incentive and rebate programs.

Incentives & Rebates

• Cascade Natural Gas
  
• Puget Sound Energy
• Seattle City Light
• Snohomish County PUD

ELCCA Reviewer Contact Information

Topic: Contact information for selected ELCCA reviewers

Department of General Administration
Div. of Engineering & Architectural Services
210 SW 11th Ave, Rm 206
PO Box 41012; Olympia, WA 98504-1012
Fax 360-586-9186

Ed Miller
Contracts Administrator
emiller@ga.wa.gov
360-902-7219

Jim Hayes, PE
Energy Project Manager
jhayes@ga.wa.gov
360-902-7281

Robert Johnson
Energy Systems Engineer
rjohnso@ga.wa.gov
360-902-7267

JR Johnson
Energy Systems Engineer
JRJohns@ga.wa.gov
360-902-7179

Stuart Simpson
Energy Systems Engineer
ssimpso@ga.wa.gov
360-902-7199

Roger Wigfield, PE
Energy Systems Engineer
rwigfie@ga.wa.gov
360-902-7198

Kirsten Wilson, PE
Energy Systems Engineer
kwilson@ga.wa.gov
509-533-8282

Trace 700 Notes

Topic: Notes for using Trace 700 in the ELCCA analysis

• Domestic hot water: Trace applies an occupancy schedule to and calculates a number for domestic hot water usage, but please note the following
  
• Inputs parameters for domestic hot water consumption are in the Base Utility/Miscellaneous Accessory tab of the 'Create Plants' module.
  
• Calculated domestic hot water consumption is shown as a line item on the Equipment Energy Consumption report.
• But domestic hot water totals are not included in the Energy Cost Budget, Energy Consumption Summary, Monthly Energy Consumption, or Monthly Utility Cost reports.
• Therefore it is necessary to add the domestic hot water consumption numbers to the HVAC totals in the ELCCA report spreadsheet.
  

ASHRAE 'Design Essential' Standards

Topic: Links for purchasing ASHRAE's most referenced standards and guidelines

• Standard 15-2004 Safety Standard for Refrigeration Systems
  
• Standard 34-2004 Designation and Safety Classification of Refrigerants
  
• Standard 52.2-1999 Method of Testing General Ventilation Air-Cleaning Devices for Removal Efficiency by Particle Size
  
• Standard 55-2004 Thermal Environmental Conditions for Human Occupancy
  
• Standard 62.1-2004 Ventilation for Acceptable Indoor Air Quality
  
• Standard 62.2-2004 Ventilation and Acceptable Indoor Air Quality Low-Rise Residential Buildings
  
• Standard 90.1-2004 (IP Version) Energy Standard for Buildings Except Low-Rise Residential
  
• Standard 90.2-2004 Energy-Efficient Design of Low-Rise Residential Buildings
• Standard 135-2004 BACNet - A Communication Protocol for Building Automation and Control Networks
• Guideline 0-2005 The Commissioning Process
• Guideline 1-1996 The HVAC Commissioning Process
• Guideline 13-2000 Specifying Direct Digital Control Systems

All of the above documents are available on a single CD at about a 30% discount to the individual price:

• Design Essentials ASHRAE's Most Referenced Standards and Guidelines on CD
  

eQuest Boiler Curve Example

Topic: Efficiency performance curves published by equipment manufacturers may not be in a format helpful for energy modeling. This example presents a manufacturers condensing boiler, and derives a set of data points to which a curve can be fit using DOE2 routines.

The following efficiency curve is published by Aerco, representing the thermal performance of KC-1000 Series condensing boilers; the color annotations have been added by the author:

(click on the image to see a larger version)

The three curves on the chart represent firing rates of 37.5%, 75% and 100% from top to bottom. Thermal efficiency can be read on the vertical axis by knowing the firing rate and return water temperature. eQuest/DOE2 however requires input data points for boiler performance curves to be in entering water temp / leaving water temp / heat input ratio (inverse of thermal efficiency) format.

According to the chart, thermal efficiency is independent of both flow and supply water temperature, so the firing rate data curves and entering water temperature points should indicate efficiency regardless of the infinite combinations of flow rates and supply temperatures possible. This produces however, essentially an infinite number of efficiency curve solutions. To solve this problem, we must temper the manufacturer's published data with a measure of sound engineering judgement.

(click on the image to see a larger version)

Realizing that a low firing rate should occur at low load conditions, a high firing rate at high load conditions, and a mid firing rate somewhere in between, let us make the careful assumption that a high firing rate will result in a 40° (100%) ΔT, a mid firing rate in a 30° (75%) ΔT , and a low firing rate in a 15° (37.5%) ΔT across the boiler.

Using these ΔT's, we can now compute a corresponding leaving water temperature for each of the data points on the chart, except for the five at the extreme right. Efficiency is poorest here as entering water temperature approaches that of leaving water temperature. So dispensing with these data points should not detract much from the resultant accuracy of the curve fit, since our control system and operational sequencing should not allow the equipment to operate in this regime anyway.

Following is the BDL code required for a binomial quadratic curve fit of the Aerco KC-1000 condensing boiler's heat input ratio in terms of entering and leaving water temperatures:

"Aerco-KC1000-HIR" = CURVE-FIT
TYPE = BI-QUADRATIC-T
INPUT-TYPE = DATA
INDEPENDENT-1 = ( 80, 80, 80, 100, 100, 100, 120,
120, 120, 140, 140, 140, 160 )
INDEPENDENT-2 = ( 95, 110, 120, 115, 130, 140, 135,
150, 160, 155, 170, 180, 175 )
DEPENDENT = ( 1.010, 1.070, 1.093, 1.058, 1.111, 1.117, 1.093,
1.136, 1.143, 1.130, 1.143, 1.149, 1.136 )

In addition to efficiency, another significant item that needs to be changed when comparing firetube to condensing boilers parametrically is the standby time, which figures directly into standby losses as a percentage of full load capacity.

For example, the default STANDBY-TIME of 0.027 (corresponding to a standby loss of 2.7%) in eQuest may be a bit high for larger firetube boilers; check the manufacturer's data as relative standby losses tend to decrease as boiler size increases. However, condensing boilers do not need to stay warm to avoid thermal shock; hence standby loss factors are on the order of one-tenth that of firetube boilers.

Per Cleaver-Brooks, the standby loss on a 1,000,000 BTU per hour Clearfire condensing boiler is 1810 BTUH or 0.1810%, which translates to a STANDBY-TIME of 0.00181 factor.

eQuest Detailed Editor Checklist

Topic: Miscellaneous notes for using eQuest in detailed edit mode.

eQUEST DETAILED EDITOR

Post-Wizard Shell Editing

• Add note about saving wizard snapshot...
• Add any missing upper level shell exterior walls.
  
• Import the following BDL code fragments from the network library:
• H:\eQuest\Library\Envelope_WSEC_Compliant.inp
  
  and, if doing an ELCCA...
  
  
• H:\eQuest\Envelope_ELCCA_Prescriptive.inp
• Assign the baseline envelope shell components corresponding to WSEC Compliant
  
• Remove the roofs of lower-level shells where upper level shells are placed.
  
• Verify that the floors of the upper level shells are adiabatic; it may be helpful to separate the shells by temporarily specifying z-coordinates of 100 feet or more between them.
  
• Define air-walls between zones where appropriate.

Post-Wizard Space Editing

• Specify the number of people per square foot under the 'Basic Specifications' tab of the Space Properties dialog box for each space.
  
• Do this or else eQuest will calculate the people density for you, and it will be low
• Specify 31 persons for classroom, multiply the number of classrooms in the space, and divide by the total square footage of the space.
  
• Specify the maximum number of occupants of the school for gymnasiums, cafeterias, auditoriums and multipurpose rooms; scheduling will account for daily diversity.
• Specify 75 SF/person for administrative areas and libraries
  
• Specify 1000 SF/person for restrooms, corridors, and support areas; this will help to moderate outside air demands.
  
• Note that when the area per square foot is specified, and the number of people are reset to the default or 'green' value, this default value is calculated by eQuest to be the total area divided by the people factor per square foot.
• Check daylighting sensors for location and orientation; adjust as required.
  

Renaming Spaces, Zones and Systems

Renaming shells, spaces, zones and systems to improve the interpretability of simulation output and improve the accuracy of internal load factor assignment is best done at the beginning of detailed edit mode. The 15 minutes to half-hour spent doing this will pay great dividends going forward, for even modestly complex projects.

• Rename Shells: By default all shells are named "ELn Ground Flr", where "n" is the sequence number of the shell in the order in which it was added to the project. Rename the shell to something more descriptive like "EL1 Bldg 100" or "EL2 Second Floor" while retaining the shell designation prefix, which is used throughout the project by eQuest for the automatic naming of related components.
• Renames Spaces: In Component Tree view, next rename spaces for each shell to something more descriptive. For example, a group of classrooms may be automatically named "EL2 North Perim Spc (G.N1)"; rename to something like "EL2 Classrooms North Space", retaining the shell designation prefix and adding the "Space" suffix.
• Renames Zones: Switch to the Air-Side HVAC tab. Starting at the top of the component tree, double-click on each zone and rename it corresponding to its space. For instance, continuing the previous example, rename "EL2 North Perim Zn (G.N1)" to "EL2 Classrooms North Zone"; note that the corresponding space is listed in the properties dialog box of the zone for easy reference.
• Renames Systems, Single-Zone: For packaged single zone systems, rename the system to correspond to the zone. For instance, continuing the previous example, rename "EL2 Sys2 (PSZ) (G.N1)" to "EL2 Classrooms North Sys"; note that the corresponding zone is listed in the component tree view below the system for easy reference.
• Renames Systems, Multi-Zone: For multiple zone systems, rename the system to a using a general geographic designation. For instance, continuing the previous example, if the system type of "EL2 Sys2 (PSZ) (G.N1)" is changed from 'packaged single zone' to 'packaged multizone', the automatically assigned system name will not be changed by eQuest. Hence change the system name to something like "EL2 Multizone North System"; with the name selected to enable easy recognition when reading DOE2 reports.

Note: This needs to be integrated into a comprehensive sequential detailed edit checklist.

Post-Wizard System Editing

• Specify minimum CFM per square foot values for each system under the 'Flow Parameters' subtab of the 'Fans' tab of the Air-Side HVAC System Parameters dialog box for each system.
  
• Do this or else eQuest will calculate the value for you, and it will be low
• Specify 1.3 CFM/SF for classroom, administrative and other high-occupancy areas
• Specify 1.0 CFM/SF for gymnasiums, cafeterias, multipurpose rooms and corridors
• For cooling-only systems, remove the drybulb economizer lock-out. The default is 65°F, which is OK if mechanical cooling is provided. However to reduce the number of unmet load hours in natural, displacement and conventional ventilation systems without mechanical cooling, this constraint should be removed.
  

Parametric Runs

• Using spreadsheet view, set Daylighting to 'No' for all zones, for the baseline case.
  
• Create the following four parametric runs in the "working copy" of the project after it has been saved with all shell & envelope modifications captured:
  
• Envelope Improvements
• Lighting Improvements
• Daylighting
• Demand Ventilation
• Others may be added, specific to each of the particular systems studied, after the working copy of the project is saved in system-specific versions.
• Any 'Appendix G' baseline generally does not require parametric runs. [more detail]
  

Note: This is a work-in-progress procedure, additional details forthcoming time permitting

Doors & Windows

• Generally custom door and window placement should be accomplished in Wizard mode. The following procedures may be useful when doors and windows need to be defined in detailed edit mode.
  

• Assure that the total area of the windows does not exceed total wall area, else an error will result. This is problem can arise particularly on all glass stair towers, entryways, and corridors where the wall is essentially all glass. To prevent this from happening, the following user expressions may be used for positioning and defining the width and height of "glass wall" windows:
  

X = {PARENT("WIDTH")*0.025}
Y = 0
HEIGHT = {PARENT("HEIGHT")}
WIDTH = {PARENT("WIDTH")*0.95}

• The following expression may be used to center doors and windows in the parent wall:

X = {PARENT("WIDTH")/2-LOCAL("WIDTH")/2}

• The following expression places doors or windows centered on the one third or two thirds points from the origin of the parent wall, respectively:

X = {1*PARENT("WIDTH")/3-LOCAL("WIDTH")/2}
X = {2*PARENT("WIDTH")/3-LOCAL("WIDTH")/2}

• Use the following expression to create windows of a fixed height as wide as the parent wall:

WIDTH = {PARENT("WIDTH")}

• Use the following expression to right-justify doors and windows:

X = {PARENT("WIDTH")-LOCAL("WIDTH")}

• Editing Windows Frame and Spacer:
• In order to eliminate windows frame. first go to the Building Shell mode and click on Spreadsheet.
  
• While on the Component Tree tab, click on one of the windows (i.e E1 South Win).
  
• Change the Frame Width of the window to default (zero) - this can be done easier and faster using multi-edit if you working with thousands of windows.
• Next, change the frame spacer type from the default 'Aluminum' to 'Insulated'
• WRITE-UP MULTIEDIT METHOD USING REGULAR EXPRESSIONS.
• 
  

Schedules

Follow this link for schedule sharing. Implement common schedules now so you don't have to do it 3 or 4 times going forward.

Fan Schedules

After implementing the schedules sharing, the "Fan Schedules" in the Fan Power and Control tab needs to be adjusted. The Cooling should be set automatically to ESM Fan Sch after the schedule input; however, the Exhaust tab will still be empty. ESM Exhaust Fan Sch need to be selected in the Exhaust tab.

Simulations

Change the TITLE, LINE-1 parameter at the beginning of each baseline INP file.

• Rename systems appropriately (e.g. PVVT, PSZ etc.) to for instance, GSHP using MultiEdit (expound).
• Noted if system name is changed via GUI or inp, any reference to the system name in the parametric run definition (.prd) file must be changed manually, most easily via text editor.

Run trial simulation for each system type.

• Eliminate any errors (e.g. 'LOOP has ZERO FLOW') to obtain valid trial simulations.
  

• Examine .SIM output file for each valid trial simulation, and update .INP file to eliminate warnings and errors.
• Exceptions: __ warnings are insignificant (list).
  

Run the 'Annual Energy Consumption by Enduse Report' for the baseline for each system (need graphic).

• The lighting, misc. energy usage, ventilation, domestic hot water and ___? should all be the same.
• If not, there is a variance in the energy densities or scheduling...correction needed.
  

eQuest Graphical Editor Notes

Topic: The eQuest graphical editor is simple, but the documentation for it is difficult to locate. This post is a quick-reference guide.

Use the following list of keyboard and mouse combinations within the eQuest graphical model editor window:

• 'W' changes to wireframe view mode
• 'S' changes to surface view mode (default)
• Ctrl+ left mouse button allows 3D model orbiting with the mouse
• Ctrl+ right mouse button allows 3D model zooming with the mouse
• Right-clicking with the mouse deploys a context menu with additional options

If the building model "disappears" in the process of orbiting and zooming, click out of the 'Building Shell' on the toolbar, for instance to 'Internal Loads', then back to 'Building Shell'. Then right-click within the graphical display window and select 'Reset Camera'.

Contents of eQuest Project/Runs List

Topic: In Reports Output mode, what controls the contents of the list in the Project/Runs tab, and how can that list be edited?

The Project/Runs list is populated by the simulation results that are contained in the "Projects" folder of your eQuest program directory.

If it is desired to prevent items from showing up, one alternative is to make a new folder (for example, "Projects Archive") in the eQuest program file directory and move the unused files to that folder.

For eQuest projects stored in a network folder, the results viewer will show the results for all projects in the "Projects" folder of eQuest along with all of the results that are in the folder for the currently active project. Thus copies of known good baseline projects may be stored locally, for use in comparison to network projects under development.

It may also be necessary to edit feed the .pdh file with a text editor. For example, if parametric runs are renamed, the .pdh file may continue to list the old names; in this case the old names contain 'DCV' resulting in an erroneous project/runs list:

1,"Garfield ES - GSHP" ,
1,"4 - Classroom, Admin & Library DCV" ,"Garfield Elementary - GSHP - 5" ,1172020623,
1,"3 - Gym & Cafeteria DCV" ,"Garfield Elementary - GSHP - 4" ,1172020604,
1,"2 - Lighting Improvements" ,"Garfield Elementary - GSHP - 2" ,1172020568,
1,"1 - Envelope Improvements" ,"Garfield Elementary - GSHP - 1" ,1172020551,
1,"Baseline Design" ,"Garfield Elementary - GSHP - Baseline Design" ,1172020536,
1,"4 - Demand Ventilation" ,"Garfield Elementary - GSHP - 4" ,1172012402,
1,"3 - Daylighting" ,"Garfield Elementary - GSHP - 3" ,1172012385,
-1,

Simply delete the lines containing old parametric run names from the .pdh file, replacing them with the lines containing the new names:

1,"Garfield ES - GSHP" ,
1,"4 - Demand Ventilation" ,"Garfield Elementary - GSHP - 4" ,1172012402,
1,"3 - Daylighting" ,"Garfield Elementary - GSHP - 3" ,1172012385,
1,"2 - Lighting Improvements" ,"Garfield Elementary - GSHP - 2" ,1172020568,
1,"1 - Envelope Improvements" ,"Garfield Elementary - GSHP - 1" ,1172020551,
1,"Baseline Design" ,"Garfield Elementary - GSHP - Baseline Design" ,1172020536,
-1,

Be sure to do this with eQuest closed; upon reopening eQuest the project/runs list should now meet or exceed expectations.