Table of Contents
To begin a HEScore session an assessment type must be selected. The assessment type
is determined from HPXML via the
Building/ProjectStatus/EventType element using the following mapping:
|XML Transaction Type||HPXML Event Type||HEScore Assessment Type|
|construction-period testing/daily test out||test|
|job completion testing/final inspection||final|
HEScore requires an assessment date. If a date is stored in the element
Building/ProjectStatus/Date, that date is used. If not, the current date is
HEScore requires specifying whether the building is a detached house or a town
house through their
building.shape input. HPXML can specify this (and a
variety of other house types) through the
element. Not all facility types in HPXML can be modeled in HEScore. The table
below shows how the possible enumerations of the HPXML field are translated
|manufactured home||not translated|
|2-4 unit building||not translated|
|5+ unit building||not translated|
|multi-family - uncategorized||not translated|
|multi-family - town homes||town_house|
|multi-family - condos||not translated|
|apartment unit||not translated|
|studio unit||not translated|
For enumerations that are not translated the HPXML file will fail to run in HEScore.
For town houses HEScore requires a
town_house_walls input to be specified.
This is available in HPXML in the
Building/BuildingSummary/Site/Surroundings element. The translation of the
enumerations is as follows:
|attached on one side||back_right_front or back_front_left|
|attached on two sides||back_front|
|attached on three sides||not translated|
If the HPXML enumeration of
attached on one side is present the translation
will determine which HEScore enumeration to select based on which side of the
house is missing windows.
- If windows are found on a shared town house wall, the translation will fail.
- HEScore cannot model townhouses that are “attached on three sides” or “stand-alone”. Using one of those inputs will result in a translation error.
The HEScore inputs
conditioned_floor_area are each retrieved from their corresponding HPXML
elements shown below.
<HPXML> ... <Building> ... <BuildingDetails> <BuildingSummary> <BuildingConstruction> <YearBuilt>1998</YearBuilt> <ConditionedFloorArea>2400</ConditionedFloorArea> <NumberofConditionedFloorsAboveGrade>2</NumberofConditionedFloorsAboveGrade> <AverageCeilingHeight>8</AverageCeilingHeight> <NumberofBedrooms>3</NumberofBedrooms> </BuildingConstruction> </BuildingSummary> </BuildingDetails> </Building> </HPXML>
The HEScore input
floor_to_ceiling_height will be calculated by dividing
AverageCeilingHeight is omitted.
In HPXML the orientation of a house and orientations in general can be specified
as either a compass direction (‘North’,’Southwest’,etc.) or an azimuth measured
in degrees clockwise from North. HEScore requires a compass direction for the
orientation of the front of the house. If the azimuth is available in
nearest compass direction is chosen. If the azimuth is omitted from HPXML but
OrientationOfFronOfHome element exists, the orientation is used.
HPXML allows the specification of multiple
elements, which can contain either a blower door test or a qualitative
assessment of “leakiness”. HPXML also allows the specification of multiple
which can contain a qualitative assessment of “leakiness”.
Either of the elements above is required.
HEScore can be used with either a measurement from a
blower door test or by specifying whether the house has been air sealed or
not (boolean). Preference is given to a blower door test measurement when it
is available in HPXML.
The translator first looks for an
AirInfiltrationMeasurement with units
of CFM50. If more than one of the
elements have units in CFM50, the last one to appear in the document is
used. If there are no measurements in CFM50, it will look for one in
ACH50. If more than one of the
have units in ACH50, the last one to appear in the document is used. If
UnitofMeasure element has a value of ACH, then the value is converted
to CFM using the building volume calculated by the floor area and floor height.
An example of the minimum expected elements in HPXML follows:
<AirInfiltrationMeasurement> <SystemIdentifier id="infilt1"/> <HousePressure>50</HousePressure><!-- Must be 50 --> <BuildingAirLeakage> <UnitofMeasure>CFM<!-- or ACH --></UnitofMeasure> <AirLeakage>1234</AirLeakage> </BuildingAirLeakage> </AirInfiltrationMeasurement>
When a blower door test is not available the translator looks for an
AirSealing that specifies an estimate of leakage.
An example of the minimum expected elements in that case looks like:
<AirInfiltrationMeasurement> <SystemIdentifier id="infilt2"/> <LeakinessDescription>tight</LeakinessDescription> </AirInfiltrationMeasurement>
<AirSealing> <SystemIdentifier id="infilt3"/> </AirSealing>
If more than one
AirInfiltrationMeasurement is found that have the above
elements, the last one to appear in the document is used. Whether the house is
marked as having air sealing present is determined according to the following
|Leakiness Description||Air Sealing Present|
AirSealing is found, the enclosure of the house is assumed to be air-sealed.