User manual

FAQ for CBECC-Res 2013

The value is the number of stories in the zone. If the building is one zone for a two-story building,

then the value is 2. If you have divided the building into one zone per floor, then the value is 1 and

the software determines the number of stories in the building when you correctly identify the

“bottom” or floor elevation as, for example, 10.7 for a slab on grade building with first floor ceiling

heights of 9 feet (see User Manual, Section 5.4.1.7, p. 5-7).

3. Can you explain azimuth and orientation as used in CBECC-Res for walls/windows?

Azimuth (or actual azimuth) is the numeric representation of the degrees the surface faces. It is

calculated based on the “plan” orientation plus the front orientation, which is why you are

encouraged to use front, left, back and right whenever possible and enter numeric values only for

walls that are at an angle. The value entered is “relative to the front” or the plan view. If your front

is input as 30 degrees and you input a left wall orientation as 120 rather than “left,” the output will

show 210 for the windows and walls facing left (plan orientation 90 + front orientation 30 = 210).

A different way of thinking of this to ignore the direction of the building except when entering the

front orientation. Consider only the surfaces as they relate to the front, which is represented

numerically by 0 and working clock-wise. Also, by using “front,” “left,” etc. you will assist the plan

checker and inspector, since the orientation or side of the building is reported on the CF1R in

addition to the actual azimuth.

If this concept is new to you, it is explained in Section 7.1, p. 7-1, of the User’s Manual.

4. Is there a limit to the length of fields?

There is no set limit to the length of fields, but the program adds data to the field names to keep

track of the parent/child relationships and interactions. So you might want to try limiting names to

25 characters.

FAQS POSTED ON JANUARY 21, 2014

1. Why doesn’t WinType work the way I think it should?

When I tried using the Window Types library by creating windows with just the U-factor and SHGC

(so that as soon as my client knew which window company they were going to use I would only need

to update the three to four window types rather than each window entry), sometimes my

efficiencies are updating and sometimes they are not. Am I doing something wrong?

Here is how to ensure it works consistently: (a) Make sure that the values in the window type library

(the very last library on the Envelope screen) have U-factor and SHGC values that are red (retype the

number rather than accepting the default), and (b) make sure that the values on the window data

screen (the window entry for the dwelling added underneath the wall) are blue. Blue means the

values will be updated if you happen to update the window efficiencies.

If you thought there was a connection to the window type library but the values are in red, they are

not connected. To change this on an existing file, swipe your cursor across the field, right-click, and

pick “Restore Default.”

2. Could you explain how CBECC-Res determines default values so I can take advantage of this

feature?

It is a sophisticated system that sets values based on the standard design assumption for the climate

zone selected. If you wish to take advantage of this feature, you can swipe the cursor across a field,

such as Solar Heat Gain Coefficient, right-click and select “Restore Default.” The field will change to

blue, indicating it may change based on the climate zone.