2017 ORS 468A.325¹
Priority of department work schedule

(1) Nothing in ORS 468A.040 (Permits), 468A.300 (Definitions for federal operating permit program) to 468A.320 (Accountability for costs of program) or this section shall require the Environmental Quality Commission or Department of Environmental Quality to make less stringent any existing element of the state’s air pollution control program.

(2) To the maximum extent possible under federal laws and regulations and within budgetary constraints, the department shall prioritize its permitting work schedule to address all of the following:

(a) Sources required to have permits under the federal operating permit program;

(b) Other sources over which the department has been granted authority for control of the emission of air contaminants that:

(A) Are either within nonattainment areas or within attainment areas projected by the department to exceed air standards within five years, and which substantially contribute to or cause the nonattainment or projected nonattainment of air quality standards; or

(B) May individually be causing exceedances of air quality standards;

(c) Applications for construction or modification; and

(d) Sources that request a federally enforceable permit from the department regardless of whether such a permit would be required under the federal operating permit program. Within budgetary constraints, the department shall cooperate with sources seeking a federally enforceable permit. [1991 c.752 §8]

(formerly 468.360 to 468.405)

Atty. Gen. Opinions

Motor Vehicle Emission Control Inspec­tion Program funding, (1974) Vol 37, p 130

1 Legislative Counsel Committee, CHAPTER 468A—Air Quality, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ors468A.­html (2017) (last ac­cessed Mar. 30, 2018).
 
2 Legislative Counsel Committee, Annotations to the Oregon Revised Stat­utes, Cumulative Supplement - 2017, Chapter 468A, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ano468A.­html (2017) (last ac­cessed Mar. 30, 2018).
 
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.