Software shall require the user to identify the type of project; either Compliance or Reach. The software shall require the user to choose one of the following options:
•New Building or Addition Alone. Software may do this by treating an addition alone as a new building, but an addition modeled in this way shall be reported on all output forms as an Addition (modeled alone).
•Addition Plus Alteration of Existing Building. (if software is approved for this optional capability)
•Alteration of Existing Building (if software is approved for this optional capability)
For each building or separately permitted space, software shall also require the user to identify the scope of the compliance submittal from the following list:
•Envelope only
•Mechanical only
•Envelope and Lighting
•Envelope and Partial Lighting
•Lighting and Mechanical
•Partial Lighting and Mechanical
•Envelope, Lighting and Mechanical (new construction)
Each of these situations requires specific assumptions, input procedures and reporting requirements. Modeling assumptions are documented in Chapter 5. Reporting requirements are documented in Chapter 4 Software shall only produce compliance reports specific to the scope of the submittal determined for the run. For example, an Envelope Only scope run is only allowed to produce ENV forms and PERF forms that are designated Envelope Only.
Lighting compliance for a partial compliance scenario may be for the entire building, or may be specified for only portions of the building. When the building applies for partial lighting compliance, the space(s) where lighting for the space is unknown or undefined shall be marked as “Undefined”, and the compliance software shall use the Standard Design lighting power for the user-defined space type for both the Proposed Design and Standard Design. Under this compliance scope, the entire building shall be modeled, and the compliance forms shall indicate the spaces for which lighting compliance is not performed.
The following modeling rules apply for when the scope of the compliance calculations do not include one of the following: the building envelope, the lighting system or the mechanical system.
|
Cases |
Modeling Rules for Proposed Design |
Modeling Rules for Standard Design (All): |
|
No Envelope Compliance Mechanical Only Lighting and Mechanical |
The envelope shall be modeled according to the as-built drawings and specifications of the building or as it occurs in the previously-approved compliance documentation of the building. All envelope features and inputs required for software by this 'manual shall be entered. |
The envelope shall be identical to the proposed design.
|
|
Note: A partial permit application involving no envelope compliance creates an exceptional condition. This requires either a copy of the previous envelope compliance approval or an equivalent demonstration by the applicant (to the satisfaction of the local enforcement agency) that the building is conditioned and an occupancy permit has previously been issued by the local enforcement agency. | ||
|
No Mechanical Compliance Envelope Only Envelope and Lighting |
Software shall model the proposed design HVAC system according to the standard design rules in Chapter 5 , using the standard design system map for determining HVAC system type. |
The mechanical systems shall be identical to the proposed design.
|
|
No Lighting Compliance Envelope Only Mechanical Only
|
Previously-approved lighting plans with approved lighting compliance forms may be entered. The exceptional conditions list on the PERF-1 form shall indicate that previously-approved lighting plans and compliance forms shall be resubmitted with the application. |
The baseline building lighting system shall be identical to the proposed design. |
|
In the absence of approved lighting plans and lighting compliance forms, the software shall model the standard design lighting system corresponding to the user-defined space types. |
The baseline building lighting system shall be identical to the proposed design. | |
The program shall account for variations in energy use due to the effects of the California climate zones and local weather data. Climate information for compliance simulations shall use the applicable data set in Reference Appendix JA2.
The candidate software shall calculate the hourly energy use for both the standard design and the proposed design by applying a TDV factor for each hour of the reference year. TDV factors have been established by the CEC for residential and nonresidential occupancies, for each of the climate zones, and for each fuel (electricity, natural gas, and propane). The procedures for Time Dependent Valuation of energy are documented in Reference Appendix JA3.
The compliance software shall meet required capabilities and pass applicable certification tests as defined in Appendix 3A, Appendix 3B and Appendix 3C. While the vendor’s software does not need to implement every modeling rule in the ACM reference manual, all software features, systems, components and controls that are modeled must follow the modeling guidelines in the ACM Reference 'Manual. Vendors seeking certification for software programs to be used for Title 24 compliance should clearly state the extent of the capabilities of their software with respect to compliance. Support of a modeling feature includes correctly processing user input, specifying the standard design correctly, applying that information to simulation models, and processing the results.
Any building features or systems that cannot be modeled in a compliance software program shall show compliance using prescriptive forms.