Application for preliminary certification
- • eligibility
- • contents
- • fees
- • certification to remain valid for three years
- • rules
(1) Prior to the installation or construction of an energy conservation project, any person may apply to the State Department of Energy for preliminary certification under ORS 469B.288 (Submissions for preliminary certification) if:
(a) The project complies with the standards adopted by the Director of the State Department of Energy; and
(b) The applicant will be the owner, contract purchaser or lessee of the project at the time of installation or construction of the project.
(2) An application for preliminary certification shall be made in writing on a form prepared by the department and shall contain:
(a) A statement that the applicant plans to acquire, construct or install a project that substantially reduces the consumption of purchased energy or uses energy more efficiently.
(b) A detailed description of the project and its operation and information showing that the project will operate as represented in the application and remain in operation for at least five years, unless the director by rule specifies another period of operation.
(c) Information on the amount by which consumption of purchased energy by the applicant will be reduced, and, if applicable, information about the expected level of sustainable building practices project performance.
(d) The anticipated total project cost.
(e) Information on the number and type of jobs, directly connected to the allowance of the credit, that will be:
(A) Created by the project; and
(B) Sustained throughout the construction, installation and operation of the project.
(f) Information demonstrating that the project will comply with applicable state and local laws and regulations and obtain required licenses and permits.
(g) Information relating to the standards described in ORS 469B.279 (Standards for energy conservation projects).
(h) A recommendation for a research and development project as demonstrative of innovation that has been made by a qualified third party selected by the director.
(i) Any other information the director considers necessary to determine whether the project is in accordance with the provisions of ORS 469B.270 (Definitions for ORS 315.331 and 469B.270 to 469B.306) to 469B.306 (Policies and procedures), and any applicable rules or standards adopted by the director.
(3) An application for preliminary certification shall be accompanied by a fee established under ORS 469B.294 (Fees for certification or recertification). The director may refund all or a portion of the fee if the application for certification is rejected.
(4) The director may allow an applicant to file the application for preliminary certification after the start of installation or construction of the project if the director finds that:
(a) Filing the application before the start of installation or construction is inappropriate because special circumstances render filing earlier unreasonable; and
(b) The project would otherwise qualify for certification under ORS 469B.270 (Definitions for ORS 315.331 and 469B.270 to 469B.306) to 469B.306 (Policies and procedures).
(5) The director may, by rule, waive preliminary certification under ORS 469B.288 (Submissions for preliminary certification), or may establish an informational filing system in place of preliminary certification, for projects that:
(a) Have eligible costs of less than $20,000;
(b) Consist of measures that the director determines to be eligible for waiver of preliminary certification; and
(c) Comply with any other requirements established by the director.
(6) A preliminary certification shall remain valid for a period of three calendar years after the date on which the preliminary certification is issued by the director, after which the certification becomes invalid even if:
(a) The applicant is awaiting identification of a pass-through partner; or
(b) The preliminary certification has been amended. [2011 c.730 §43; 2012 c.45 §21]
3 OregonLaws.org assembles these lists by analyzing references between Sections. Each listed item refers back to the current Section in its own text. The result reveals relationships in the code that may not have otherwise been apparent.