R307-250. Western Backstop Sulfur Dioxide Trading Program  


R307-250-1. Purpose
Latest version.

This rule implements the Western Backstop (WEB) Sulfur Dioxide Trading Program provisions in accordance with the federal Regional Haze Rule, 40 CFR 51.309, and Section XX.E of the State Implementation Plan for Regional Haze, titled "Sulfur Dioxide Milestones and Backstop Trading Program," incorporated under R307-110-28.


R307-250-2. Definitions
Latest version.

The following additional definitions apply to R307-250:

"Account Certificate of Representation" or "Certificate" means the completed and signed submission required to designate an Account Representative for a WEB source or an Account Representative for a general account. "Account Representative" means the individual who is authorized through an Account Certificate of Representation to represent owners and operators of the WEB source with regard to matters under the WEB Trading Program or, for a general account, who is authorized through an Account Certificate of Representation to represent the persons having an ownership interest in allowances in the general account with regard to matters concerning the general account.

"Actual Emissions" means total annual sulfur dioxide emissions determined in accordance with R307-250-9 or determined in accordance with the Sulfur Dioxide Milestone Inventory requirements of R307-150 for sources that are not subject to R307-250-9.

"Allocate" means to assign allowances to a WEB source in accordance with SIP Section XX.E.3.a through c.

"Allowance" means the limited authorization under the WEB Trading Program to emit one ton of sulfur dioxide during a specified control period or any control period thereafter subject to the terms and conditions for use of unused allowances as established by R307-250.

"Allowance Limitation" means the tonnage of sulfur dioxide emissions authorized by the allowances available for compliance deduction for a WEB source under R307-250-12 on the allowance transfer deadline for each control period.

"Allowance Transfer Deadline" means the deadline established in R307-250-10(2) when allowance transfers must be submitted for recording in a WEB source's compliance account in order to demonstrate compliance for that control period.

"Compliance Account" means an account established in the WEB EATS under R307-250-8(1) for the purpose of recording allowances that a WEB source might hold to demonstrate compliance with its allowance limitation.

"Compliance Certification" means a submission to the director by the Account Representative as required under R307-250-12(2) to report a WEB source's compliance or noncompliance with R307-250.

"Control Period" means the period beginning January 1 of each year and ending on December 31 of the same year, inclusive.

"Existing Source" means a stationary source that commenced operation before the Program Trigger Date.

"General Account" means an account established in the WEB EATS under R307-250-8 for the purpose of recording allowances held by a person that are not to be used to show compliance with an allowance limitation.

"Milestone" means the maximum level of stationary source regional sulfur dioxide emissions for each year from 2003 to 2018, established according to the procedures in SIP Section XX.E.1.

"New WEB Source" means a WEB source that commenced operation on or after the program trigger date.

"New Source Set-aside" means a pool of allowances that are available for allocation to new sources in accordance with the provisions of SIP Section XX.E.3.c.

"Program trigger date" means the date that the director determines that the WEB Trading Program has been triggered in accordance with the provisions of SIP Section XX.E.1.c.

"Program trigger years" means the years shown in SIP Section XX.E.1.a, Table 3, column 3 for the applicable milestone if the WEB Trading Program is triggered as described in SIP Section XX.E.1.

"Retired source" means a WEB source that has received a retired source exemption as provided in R307-250-4(4).

"Serial number" means, when referring to allowances, the unique identification number assigned to each allowance by the Tracking Systems Administrator, in accordance with R307-250-7(2).

"SIP Section XX.E" means Section XX, Part E of the State Implementation Plan, titled "Sulfur Dioxide Milestones and Backstop Trading Program." SIP Section XX, Regional Haze, is incorporated by reference under R307-110-28.

"Special Reserve Compliance Account" means an account established in the WEB EATS under R307-250-8(1) for the purpose of recording allowances that a WEB source might hold to demonstrate compliance with its allowance limitation for emission units that are monitored for sulfur dioxide in accordance with R307-250-9(1)(b).

"Sulfur Dioxide emitting unit" means any equipment that is located at a WEB source and that emits sulfur dioxide.

"Submit" means sent to the director or the Tracking system Administrator under the signature of the Account Representative. For purposes of determining when something is submitted, an official U.S. Postal Service postmark, or equivalent electronic time stamp, shall establish the date of submittal.

"Ton" means 2000 pounds and any fraction of a ton equaling 1000 pounds or more shall be treated as one ton and any fraction of a ton equaling less than 1000 pounds shall be treated as zero tons.

"Tracking System Administrator" or "TSA" means the person designated by the director as the administrator of the WEB EATS.

"WEB Source" means a stationary source that meets the applicability requirements of R307-250-4.

"WEB Trading Program" means R307-250, the Western Backstop Trading Program, triggered as a backstop in accordance with the provisions in SIP Section XX.E, if necessary, to ensure that regional sulfur dioxide emissions are reduced.

"WEB Emissions and Allowance Tracking System (WEB EATS)" means the central database where sulfur dioxide emissions for WEB sources as recorded and reported in accordance with R307-250 are tracked to determine compliance with allowance limitations, and the system where allowances under the WEB Trading Program are recorded, held, transferred and deducted.

"WEB EATS account" means an account in the WEB EATS established for purposes of recording, holding, transferring, and deducting allowances.


R307-250-3. WEB Trading Program Trigger
Latest version.

(1) Except as provided in (2) below, R307-250 shall apply on the program trigger date that is established in accordance with the procedures in SIP Section XX.E.1.c.

(2) Special Penalty Provisions for the 2018 Milestone, R307-250-13, shall apply on January 1, 2018, and shall remain effective until the requirements of R307-250-13 have been met.


R307-250-4. WEB Trading Program Applicability
Latest version.

(1) General Applicability. R307-250 applies to any stationary source or group of stationary sources that are located on one or more contiguous or adjacent properties and that are under the control of the same person or persons under common control, belonging to the same industrial grouping, and that are described in paragraphs (a) and (b) of this subsection. A stationary source or group of stationary sources shall be considered part of a single industrial grouping if all of the pollutant emitting activities at such source or group of sources on contiguous or adjacent properties belong to the same Major Group (i.e., all have the same two-digit code) as described in the Standard Industrial Classification Manual, 1987.

(a) All BART-eligible sources as defined in 40 CFR 51.301 that are BART-eligible due to sulfur dioxide emissions.

(b) All stationary sources that have actual sulfur dioxide emissions of 100 tons or more per year in the program trigger years or any subsequent year. The fugitive emissions of a stationary source shall not be considered in determining whether it is subject to R307-250 unless the source belongs to one of the following categories of stationary source:

(i) Coal cleaning plants (with thermal dryers);

(ii) Kraft pulp mills;

(iii) Portland cement plants;

(iv) Primary zinc smelters;

(v) Iron and steel mills;

(vi) Primary aluminum ore reduction plants;

(vii) Primary copper smelters;

(viii) Municipal incinerators capable of charging more than 250 tons of refuse per day;

(ix) Hydrofluoric, sulfuric, or nitric acid plants;

(x) Petroleum refineries;

(xi) Lime plants;

(xii) Phosphate rock processing plants;

(xiii) Coke oven batteries;

(xiv) Sulfur recovery plants;

(xv) Carbon black plants (furnace process);

(xvi) Primary lead smelters;

(xvii) Fuel conversion plants;

(xviii) Sintering plants;

(xix) Secondary metal production plants;

(xx) Chemical process plants;

(xxi) Fossil-fuel boilers (or combination thereof) totaling more than 250 million British thermal units per hour heat input;

(xxii) Petroleum storage and transfer units with a total storage capacity exceeding 300,000 barrels;

(xxiii) Taconite ore processing plants;

(xxiv) Glass fiber processing plants;

(xxv) Charcoal production plants;

(xxvi) Fossil-fuel-fired steam electric plants of more than 250 million British thermal units per hour heat input; or

(xxvii) Any other stationary source category, which as of August 7, 1980, is being regulated under Section 111 or 112 of the Clean Air Act.

(b) A new source that begins operation after the program trigger date and has the potential to emit 100 tons or more of sulfur dioxide per year.

(2) The director may determine on a case-by-case basis, with concurrence from the EPA Administrator, that a stationary source defined in (1)(b) above that has not previously met the applicability requirements of (1) is not subject to R307-250 if the stationary source had actual sulfur dioxide emissions of 100 tons or more in a single year and in each of the previous five years had actual sulfur dioxide emissions of less than 100 tons per year, and:

(a)(i) the emissions increase was due to a temporary emission increase that was caused by a sudden, infrequent failure of air pollution control equipment, or process equipment, or a failure to operate in a normal or usual manner, and

(ii) the stationary source has corrected the failure of air pollution equipment, process equipment, or process by the time of the director's determination; or

(b) the stationary source had to switch fuels or feedstocks on a temporary basis and as a result of an emergency situation or unique and unusual circumstances besides the cost of such fuels or feedstocks.

(3) Duration of Applicability. Except as provided for in (4) below, once a stationary source is subject to R307-250, it will remain subject to the rule every year thereafter.

(4) Retired Source Exemption.

(a) Application. Any WEB source that is permanently retired shall apply for a retired source exemption. The WEB source may be considered permanently retired only if all sulfur dioxide emitting units at the source are permanently retired. The application shall contain the following information:

(i) identification of the WEB source, including the plant name and an appropriate identification code in a format specified by the director;

(ii) name of account representative;

(iii) description of the status of the WEB source, including the date that the WEB source was permanently retired;

(iv) signed certification that the WEB source is permanently retired and will comply with the requirements of R307-250-4(4); and

(v) verification that the WEB source has a general account where any unused allowances or future allocations will be recorded.

(b) Notice. The retired source exemption becomes effective when the director notifies the WEB source that the retired source exemption has been granted.

(c) Responsibilities of Retired Sources.

(i) A retired source shall be exempt from R307-250-9 and R307-250-12, except as provided below.

(ii) A retired source shall not emit any sulfur dioxide after the date the retired source exemption is issued.

(iii) A WEB source shall submit sulfur dioxide emissions reports, as required by R307-250-9, for any time period the source was operating prior to the effective date of the retired source exemption. The retired source shall be subject to the compliance provisions of R307-250-12, including the requirement to hold allowances in the source's compliance account to cover all sulfur dioxide emissions prior to the date the source was permanently retired.

(iv) A retired source that is still in existence but no longer emitting sulfur dioxide shall, for a period of five years from the date the records are created, retain records demonstrating that the source is permanently retired for purposes of this rule.

(d) Resumption of Operations.

(i) Before resuming operation, the retired source must submit registration materials as follows:

(A) If the source is required to obtain an approval order under R307-401 or an operating permit under R307-415 prior to resuming operation, then registration information as described in R307-250-6(1) and a copy of the retired source exemption must be submitted with the notice of intent under R307-401 or the operating permit application required under R307-415;

(B) If the source does not meet the criteria of (A), then registration information as described in R307-250-6(1) and a copy of the retired source exemption must be submitted to the director at least ninety days prior to resumption of operation.

(ii) The retired source exemption shall automatically expire on the day the retired source resumes operation.

(e) Loss of Future Allowances. A WEB source that is permanently retired and that does not apply to the director for a retired source exemption within ninety days of the date that the source is permanently retired shall forfeit any unused and future allowances. The abandoned allowances shall be retired by the TSA.


R307-250-5. Account Representative for WEB Sources
Latest version.

(1) Each WEB source must identify one account representative and may also identify an alternate account representative who may act on behalf of the account representative. Any representation, action, inaction or submission by the alternate account representative will be deemed to be a representation, action, inaction or submission by the account representative.

(2) Identification and Certification of an account representative.

(a) The account representative and any alternate account representative shall be appointed by an agreement that makes the representations, actions, inactions or submissions of the account representative and any alternate binding on the owners and operators of the WEB source.

(b) The account representative shall submit to the director and the TSA a signed and dated certificate that contains the following elements:

(i) identification of the WEB source by plant name and an appropriate identification code in a format specified by the director;

(ii) the name, address, e-mail (if available), telephone and facsimile number of the account representative and any alternate;

(iii) a list of owners and operators of the WEB source;

(iv) information to be part of the emission tracking system database that is established in accordance with SIP Section XX.E.3.i. The specific data elements shall be as specified by the the director to be consistent with the data system structure, and may include basic facility information that may appear in other reports and notices submitted by the WEB source, such as county location, industrial classification codes, and similar general facility information.

(v) The following certification statement: "I certify that I was selected as the account representative or alternate account representative, as applicable, by an agreement binding on the owners and operators of the WEB source. I certify that I have all the necessary authority to carry out my duties and responsibilities under the WEB Trading Program on behalf of the owners and operators of the WEB source and that the owner and operator each shall be fully bound by my representations, actions, inactions, or submissions and by any decision or order issued to me by the director regarding the WEB Trading Program."

(c) Upon receipt by the director of the complete certificate, the account representative and any alternate account representative represents and, by his or her representations, actions, inactions, or submissions, legally binds each owner and operator of the WEB source in all matters pertaining to the WEB Trading Program. Each owner and operator shall be bound by any decision or order issued by the director regarding the WEB Trading Program.

(d) No WEB EATS account shall be established for the WEB source until the TSA has received a complete Certificate. Once the account is established, all submissions concerning the account, including the deduction or transfer of allowances, shall be made by the account representative.

(3) Responsibilities.

(a) The responsibilities of the account representative include, but are not limited to, the transferring of allowances and the submission of monitoring plans, registrations, certification applications, sulfur dioxide emissions data and compliance reports as required by R307-250, and representing the source in all matters pertaining to the WEB Trading Program.

(b) Each submission under this program shall be signed and certified by the account representative for the WEB source. Each submission shall include the following truth and accuracy certification statement by the account representative: "I am authorized to make this submission on behalf of the owners and operators of the WEB source for which the submission is made. I certify under penalty of law that I have personally examined, and am familiar with, the statements and information submitted in this document and all its attachments. Based on my inquiry of those individuals with primary responsibility for obtaining the information, I certify that the statements and information are to the best of my knowledge and belief true, accurate, and complete. I am aware that there are significant penalties for submitting false statements and information or omitting required statements and information, including the possibility of fine or imprisonment."

(4) Changing the Account Representative or Owners and Operators.

(a) Changing the Account Representative or the alternate Account Representative. The account representative or alternate account representative may be changed at any time by sending a complete superseding certificate to the director and the TSA under R307-250-5(2). The change will be effective upon receipt of such certificate by the TSA. Notwithstanding any such change, all representations, actions, inactions, and submissions by the previous account representative or alternate prior to the time and date when the TSA receives the superseding certificate shall be binding on the new account representative and the owners and operators of the WEB source.

(b) Changes in Owner and Operator.

(i) Within thirty days of any change in the owners and operators of the WEB source, including the addition of a new owner or operator, the account representative shall submit a revised certificate amending the list of owners and operators to include such change.

(ii) In the event a new owner or operator of a WEB source is not included in the list of owners and operators submitted in the certificate, such new owner or operator shall be deemed to be subject to and bound by the certificate, the representations, actions, inactions, and submissions of the account representative of the WEB source, and the decisions, orders, actions, and inactions of the director as if the new owner or operator were included in the list.


R307-250-6. Registration
Latest version.

(1) Deadlines.

(a) Each source that is a WEB source on or before the program trigger date shall register by submitting the initial certificate required in R307-250-5(2) to the director no later than 180 days after the program trigger date.

(b) Any existing source that becomes a WEB source after the program trigger date shall register by submitting the initial certificate required in R307-250-5(2) to the director no later than September 30 of the year following the inventory year in which the source exceeded the 100 tons sulfur dioxide emission threshold in R307-250-4(1)(b).

(c) Any new WEB source shall register by submitting the initial certificate required in R307-250-5(2) to the director prior to commencing operation.

(2) Any allocation, transfer or deduction of allowances to or from the source's compliance account shall not require a revision of the WEB source's operating permit under R307-415.


R307-250-7. Allowance Allocations
Latest version.

(1) The TSA will record the allowances for each WEB source in the source's compliance account once the allowances are allocated by the director under SIP Section XX.E.3.a through c. If applicable, the TSA will record a portion of the sulfur dioxide allowances for a WEB source in a special reserve compliance account to account for any allowances to be held by the source that conducts monitoring in accordance with R307-250-9(1)(b).

(2) The TSA will assign a serial number to each allowance in accordance with SIP Section XX.E.3.f.

(3) All allowances shall be allocated, recorded, transferred, or used as whole allowances. To determine the number of whole allowances, the number of allowances shall be rounded down for decimals less than 0.50 and rounded up for decimals of 0.50 or greater.

(4) An allowance is not a property right, and is a limited authorization to emit one ton of sulfur dioxide valid only for the purpose of meeting the requirements of R307-250. No provision of the WEB Trading Program or other law should be construed to limit the authority of the director to terminate or limit such authorization.

(5) Early Reduction Bonus Allocation. Any non-utility WEB source that installs new control technology and that reduces its permitted annual sulfur dioxide emissions to a level that is below the floor level allocation established for that source in SIP Section XX.E.3.a(1)(b)(i) or any utility that reduces its permitted annual sulfur dioxide emissions to a level that is below best available control technology may apply to the director for an early reduction bonus allocation. The bonus allocation shall be available for reductions that occur between 2003 and the program trigger year. The application must be submitted no later than 90 days after the program trigger date. Any WEB source that applies and receives early reduction bonus allocations must retain the records referenced in this section for a minimum of five years after the early reduction bonus allowance is certified in accordance with SIP Section XX.E.3.a(1)(c). The application for an early reduction bonus allocation must contain the following information:

(a) copies of all approval orders, operating permits or other enforceable documents that include annual sulfur dioxide emissions limits for the WEB source during the period the WEB source qualifies for an early reduction credit. Approval orders, permits, or enforceable documents must contain monitoring requirements for sulfur dioxide emissions that meet the specifications in R307-250-9(1)(a).

(b) demonstration that the floor level established for the source in SIP Section XX.E.3.a(1)(b)(i) for non-utilities or best available control technology for utilities was calculated using data that are consistent with monitoring methods specified in R307-250-9(1)(a). If needed, the demonstration shall include a new floor level calculation that is consistent with the monitoring methodology in R307-250-9.

(6) Request for Allowances for New WEB Sources or Modified WEB Sources.

(a) A new WEB source may apply to the director for an allocation from the new source set-aside, as outlined in SIP Section XX.E.3.c. A new WEB source is eligible for an annual floor allocation equal to the lower of the permitted annual sulfur dioxide emission limit for that source, or sulfur dioxide annual emissions calculated based on a level of control equivalent to best available control technology (BACT) and assuming 100 percent utilization of the WEB source, beginning with the first full calendar year of operation.

(b) An existing WEB source that has increased production capacity through a new approval order issued under R307-401 may apply to the director for an allocation from the new source set-aside, as outlined in SIP Section XX.E.3.c. An existing WEB source is eligible for an annual allocation equal to:

(i) the permitted annual sulfur dioxide emission limit for a new unit; or

(ii) the permitted annual sulfur dioxide emission increase for the WEB source due to the replacement of an existing unit with a new unit or the modification of an existing unit that increased production capacity of the WEB source.

(c) A source that has received a retired source exemption under R307-250-4(4) is not eligible for an allocation from the new source set-aside.

(d) The application for an allocation from the new source set-aside must contain the following:

(i) for a new WEB source or a new unit under R307-250-7(6)(b)(i), documentation of the actual date of the commencement of operation and a copy of the approval order issued under R307-401;

(ii) for an existing WEB source under R307-250-7(6)(b)(ii), documentation of the production capacity of the source before and after the new permit.


R307-250-8. Establishment of Accounts
Latest version.

(1) WEB EATS. All WEB sources are required to open a compliance account. Any person may open a general account for the purpose of holding and transferring allowances. In addition, if a WEB source conducts monitoring under R307-250-9(1)(b), the WEB source shall open a special reserve compliance account for allowances associated with units monitored under those provisions. To open any type of account, an application that contains the following information must be submitted to the TSA:

(a) the name, mailing address, e-mail address, telephone number, and facsimile number of the account representative. For a compliance account, the application shall include a copy of the certificatefor the account representative and any alternate as required in R307-250-5(2)(b). For a general account, the application shall include the certificate for the account representative and any alternate as required in (3)(b) below.

(b) the WEB source or organization name;

(c) the type of account to be opened;

(d) identification of the specific units that are being monitored under R307-250-9(1)(b) and that must demonstrate compliance with the allowance limitation in the special reserve compliance account; and

(e) a signed certification of truth and accuracy by the account representative according to R307-250-5(3)(b) for compliance accounts and for general accounts, certification of truth and accuracy by the account representative according to (4) below.

(2) Account Representative for General Accounts. For a general account, one account representative must be identified and an alternate account representative may be identified and may act on behalf of the account representative. Any representation, action, inaction or submission by the alternate account representative will be deemed to be a representation, action, inaction or submission by the account representative.

(3) Identification and Certification of an Account Representative for General Accounts.

(a) The account representative shall be appointed by an agreement that makes the representations, actions, inactions or submissions of the account representative binding on all persons who have an ownership interest with respect to allowances held in the general account.

(b) The account representative shall submit to the TSA a signed and dated certificate that contains the following elements:

(i) the name, address, e-mail (if available), telephone and facsimile number of the account representative and any alternate;

(ii) the organization name, if applicable;

(iii) the following certification statement: "I certify that I was selected as the account representative or alternate account representative, as applicable, by an agreement binding on all persons who have an ownership interest in allowances in the general account with regard to matters concerning the general account. I certify that I have all the necessary authority to carry out my duties and responsibilities under the WEB Trading Program on behalf of said persons and that each such person shall be fully bound by my representations, actions, inactions, or submissions."

(c) Upon receipt by the TSA of the complete certificate, the account representative represents and, by his or her representations, actions, inactions, or submissions, legally binds each person who has an ownership interest in allowances held in the general account with regard to all matters concerning the general account. Such persons shall be bound by any decision or order issued by the director.

(d) A WEB EATS general account shall not be established until the TSA has received a complete certificate. Once the account is established, the account representative shall make all submissions concerning the account, including the deduction or transfer of allowances.

(4) Requirements and Responsibilities for General Accounts. Each submission for the general account shall be signed and certified by the account representative for the general account. Each submission shall include the following truth and accuracy certification statement by the account representative: "I am authorized to make this submission on behalf of all person who have an ownership interest in allowances held in the general account. I certify under penalty of law that I have personally examined, and am familiar with, the statements and information submitted in this document and all its attachments. Based on my inquiry of those individuals with primary responsibility for obtaining the information, I certify that the statements and information are to the best of my knowledge and belief true, accurate, and complete. I am aware that there are significant penalties for submitting false statements and information or omitting required statements and information, including the possibility of fine or imprisonment."

(5) Changing the Account Representative for General Accounts. The account representative or alternate account representative may be changed at any time by sending a complete superseding certificate to the director and the TSA under (3)(b) above. The change will take effect upon the receipt of the certificate by the TSA. Notwithstanding any such change, all representations, actions, inactions, and submissions by the previous account representative or alternate prior to the time and date when the TSA receives the superseding certificate shall be binding on the new account representative and all persons having ownership interest with respect to allowances held in the general account.

(6) Changes to the Account. Any change to the information required in the application for an existing account under (1) above shall require a revision of the application.


R307-250-9. Monitoring, Recordkeeping and Reporting
Latest version.

(1) General Requirements on Monitoring Methods.

(a) For each sulfur dioxide emitting unit at a WEB source the WEB source shall comply with the following, as applicable, to monitor and record sulfur dioxide mass emissions.

(i) If a unit is subject to 40 CFR Part 75 under a requirement separate from the WEB Trading Program, the unit shall meet the requirements contained in Part 75 with respect to monitoring, recording and reporting sulfur dioxide mass emissions.

(ii) If a unit is not subject to 40 CFR Part 75 under a requirement separate from the WEB Trading Program, a unit shall use one of the following monitoring methods, as applicable:

(A) a continuous emission monitoring system (CEMS) for sulfur dioxide and flow that complies with all applicable monitoring provisions in 40 CFR Part 75;

(B) if the unit is a gas- or oil-fired combustion device, the excepted monitoring methodology in Appendix D to 40 CFR Part 75, or, if applicable, the low mass emissions (LME) provisions (with respect to sulfur dioxide mass emissions only) of 40 CFR 75.19;

(C) one of the optional WEB protocols, if applicable, in Appendix B of State Implementation Plan Section XX, Regional Haze; or

(D) a petition for site-specific monitoring that the source submits for approval by the director and approval by the U.S. Environmental Protection Agency in accordance with R307-250-9(9).

(iii) A permanently retired unit shall not be required to monitor under this section if such unit was permanently retired and had no emissions for the entire control period and the account representative certifies in accordance with R307-250-12(2) that these conditions were met.

(b) Notwithstanding (a) above, a WEB source with a unit that meets one of the conditions of (i) below may submit a request to the director to have the provisions of this subsection (b) apply to that unit.

(i) Any of the following units may implement this subsection (b):

(A) any smelting operation where all of the emissions from the operation are not ducted to a stack; or

(B) any flare, except to the extent such flares are used as a fuel gas combustion device at a petroleum refinery; or

(C) any other type of unit without add-on sulfur dioxide control equipment, if the unit belongs to one of the following source categories: cement kilns, pulp and paper recovery furnaces, lime kilns, or glass manufacturing.

(ii) For each unit covered by this subsection (b), the account representative shall submit a notice to request that this subsection (b) apply to one or more sulfur dioxide emitting units at a WEB source. The notice shall be submitted in accordance with the deadlines specified in R307-250-9(6)(a), and shall include the following information (in a format specified by the director with such additional, related information as may be requested):

(A) a list of all units at the WEB source that identifies the units that are to be covered by this subsection (b);

(B) an identification of any such units that are permanently retired.

(iii) For each new unit at an existing WEB source for which the WEB source seeks to comply with this subsection (b) and for which the account representative applies for an allocation under the new source set-aside provisions of R307-250-7(6), the account representative shall submit a modified notice under (ii) above that includes such new sulfur dioxide emitting units. The modified request shall be submitted in accordance with the deadlines in R307-250-9(6)(a), but no later than the date on which a request is submitted under R307-250-7(6) for allocations from the set-aside.

(iv) The account representative for a WEB source shall submit an annual emissions statement for each unit under this subsection (b) pursuant to R307-250-9(8). The WEB source shall maintain operating records sufficient to estimate annual sulfur dioxide emissions in a manner consistent with the emission inventory submitted by the source for calendar year 2006. In addition, if the estimated emissions from all such units at the WEB source are greater than the allowances for the current control year held in the special reserve compliance account for the WEB source, the account representative shall report the extra amount as part of the annual report for the WEB source under R307-250-12 and shall obtain and transfer allowances into the special reserve compliance account to account for such emissions.

(v) R307-250-9(2) - (10) shall not apply to units covered by this paragraph except where otherwise noted.

(vi) A WEB source may opt to modify the monitoring for a sulfur dioxide emitting unit to use monitoring under (a) above, but any such monitoring change must take effect on January 1 of the next compliance year. In addition, the account representative must submit an initial monitoring plan at least 180 days prior to the date on which the new monitoring will take effect and a detailed monitoring plan in accordance with (2) below. The account representative shall also submit a revised notice under R307-250-9(1)(b)(ii) at the same time that the initial monitoring plan is submitted.

(c) For any monitoring method that the WEB source uses under R307-250-9 including (b) above, the WEB source shall install, certify, and operate the equipment in accordance with this section, and record and report the data from the method as required in this section. In addition, the WEB source may not:

(i) except for an alternative approved by the EPA Administrator for a WEB source that implements monitoring under (a) above, use an alternative monitoring system, alternative reference method or another alternative for the required monitoring method without having obtained prior written approval in accordance with (9) below;

(ii) operate a sulfur dioxide emitting unit so as to discharge, or allow to be discharged, sulfur dioxide emissions to the atmosphere without accounting for these emissions in accordance with the applicable provisions of this section;

(iii) disrupt the approved monitoring method or any portion thereof, and thereby avoid monitoring and recording sulfur dioxide mass emissions discharged into the atmosphere, except for periods of recertification or periods when calibration, quality assurance testing or maintenance is performed in accordance with the applicable provisions of this section; or

(iv) retire or permanently discontinue use of an approved monitoring method, except under one of the following circumstances:

(A) during a period when the unit is exempt from the requirements of this Section, including retirement of a unit as addressed in (a)(iii) above;

(B) the WEB source is monitoring emissions from the unit with another certified monitoring method approved under this Section for use at the unit that provides data for the same parameter as the retired or discontinued monitoring method; or

(C) the account representative submits notification of the date of certification testing of a replacement monitoring system in accordance with this Section, and the WEB source recertifies thereafter a replacement monitoring system in accordance with the applicable provisions of this Section.

(2) Monitoring Plan.

(a) General Provisions. A WEB source with a sulfur dioxide emitting unit that uses a monitoring method under (1)(a)(ii) above shall meet the following requirements.

(i) Prepare and submit to the director an initial monitoring plan for each monitoring method that the WEB source uses to comply with this Section. In accordance with (c) below, the plan shall contain sufficient information on the units involved, the applicable method, and the use of data derived from that method to demonstrate that all unit sulfur dioxide emissions are monitored and reported. The plan shall be submitted in accordance with the deadlines specified in (6) below.

(ii) Prepare, maintain and submit to the director a detailed monitoring plan in accordance with the deadlines specified in (6) below. The plan will contain the applicable information required by (d) below. The director may require that the monitoring plan or portions of it be submitted electronically. The director may also require that the plan be submitted on an ongoing basis in electronic format as part of the quarterly report submitted under (8)(a) below or resubmitted separately within 30 days after any change is made to the plan in accordance with (iii) below.

(iii) Whenever a WEB source makes a replacement, modification, or change in one of the systems or methodologies provided for in (1)(a)(ii) above, including a change in the automated data acquisition and handling system or in the flue gas handling system, that affects information reported in the monitoring plan, such as a change to serial number for a component of a monitoring system, then the WEB source shall update the monitoring plan.

(b) A WEB source with a sulfur dioxide emitting unit that uses a method under (1)(a)(i) above shall meet the requirements of this subsection (2) by preparing, maintaining and submitting a monitoring plan in accordance with the requirements of 40 CFR Part 75. If requested, the WEB source also shall submit the entire monitoring plan to the director.

(c) Initial Monitoring Plan. The account representative shall submit an initial monitoring plan for each sulfur dioxide emitting unit or group of units sharing a common methodology that, except as otherwise specified in an applicable provision in Appendix B of State Implementation Plan Section XX, contains the following information:

(i) For all sulfur dioxide emitting units:

(A) plant name and location;

(B) plant and unit identification numbers assigned by the director;

(C) type of unit, or units for a group of units using a common monitoring methodology;

(D) identification of all stacks or pipes associated with the monitoring plan;

(E) types of fuels fired or sulfur containing process materials used in the sulfur dioxide emitting unit, and the fuel classification of the unit if combusting more than one type of fuel and using a 40 CFR Part 75 methodology;

(F) types of emissions controls for sulfur dioxide installed or to be installed, including specifications of whether such controls are pre-combustion, post-combustion, or integral to the combustion process;

(G) maximum hourly heat input capacity, or process throughput capacity, if applicable;

(H) identification of all units using a common stack; and

(I) indicator of whether any stack identified in the plan is a bypass stack.

(ii) For each unit and parameter required to be monitored, identification of monitoring methodology information, consisting of monitoring methodology, monitor locations, substitute data approach for the methodology, and general identification of quality assurance procedures. If the proposed methodology is a specific methodology submitted pursuant to (1)(a)(ii)(D) above, the description under this paragraph shall describe fully all aspects of the monitoring equipment, installation locations, operating characteristics, certification testing, ongoing quality assurance and maintenance procedures, and substitute data procedures.

(iii) If a WEB source intends to petition for a change to any specific monitoring requirement otherwise required under this Section, such petition may be submitted as part of the initial monitoring plan.

(iv) The director may issue a notice of approval or disapproval of the initial monitoring plan based on the compliance of the proposed methodology with the requirements for monitoring in this Section.

(d) Detailed Monitoring Plan. The account representative shall submit a detailed monitoring plan that, except as otherwise specified in an applicable provision in Appendix C of State Implementation Plan Section XX, the Regional Haze SIP, shall contain the following information:

(i) Identification and description of each monitoring component (including each monitor and its identifiable components, such as analyzer or probe) in a continuous emissions monitoring system (e.g., sulfur dioxide pollutant concentration monitor, flow monitor, moisture monitor), a 40 CFR Part 75, Appendix D monitoring system (e.g., fuel flowmeter, data acquisition and handling system), or a protocol in Appendix B of SIP Section XX, including:

(A) manufacturer, model number and serial number;

(B) component and system identification code assigned by the facility to each identifiable monitoring component, such as the analyzer and/or probe;

(C) designation of the component type and method of sample acquisition or operation such as in situ pollutant concentration monitor or thermal flow monitor;

(D) designation of the system as a primary or backup system;

(E) first and last dates the system reported data;

(F) status of the monitoring component; and

(G) parameter monitored.

(ii) Identification and description of all major hardware and software components of the automated data acquisition and handling system, including:

(A) hardware components that perform emission calculations or store data for quarterly reporting purposes, including the manufacturer and model number; and

(B) identification of the provider and model or version number of the software components.

(iii) Explicit formulas for each measured emissions parameter, using component or system identification codes for the monitoring system used to measure the parameter that links the system observations with the reported concentrations and mass emissions. The formulas must contain all constants and factors required to derive mass emissions from component or system code observations and an indication of whether the formula is being added, corrected, deleted, or is unchanged. The WEB source with a low mass emissions unit for which the WEB source is using the optional low mass emissions excepted methodology in 40 CFR Part 75.19(c) is not required to report such formulas.

(iv) For units with flow monitors only, the inside cross-sectional area in square feet at the flow monitoring location.

(v) If using CEMS for sulfur dioxide and flow, for each parameter monitored, include the scale, maximum potential concentration and method of calculation, maximum expected concentration, if applicable, and method of calculation, maximum potential flow rate and method of calculations, span value, full-scale range, daily calibration units of measure, span effective date and hour, span inactivation date and hour, indication of whether dual spans are required, default high range value, flow rate span, and flow rate span value and full scale value in standard cubic feet per hour for each unit or stack using sulfur dioxide or flow component monitors.

(vi) If the monitoring system or excepted methodology provides for use of a constant, assumed, or default value for a parameter under specific circumstances, then include the following information for each value of such parameter:

(A) identification of the parameter;

(B) default, maximum, minimum, or constant value, and units of measure for the value;

(C) purpose of the value;

(D) indicator of use during controlled and uncontrolled hours;

(E) types of fuel;

(F) source of the value;

(G) value effective date and hour;

(H) date and hour value is no longer effective, if applicable; and

(I) for units using the excepted methodology under 40 CFR 75.19, the applicable sulfur dioxide emission factor.

(vii) Unless otherwise specified in subsection 6.5.2.1 of Appendix A to 40 CFR Part 75, for each unit or common stack on which continuous emissions monitoring system hardware are installed:

(A) the upper and lower boundaries of the range of operation as defined in subsection 6.5.2.1 of Appendix A to 40 CFR Part 75, or thousands of pounds per hour (lb/hr) of steam, or feet per second (ft/sec), as applicable;

(B) the load or operating level(s) designated as normal in subsection 6.5.2.1 of Appendix A to 40 CFR Part 75, or thousands of lb/hr of steam, or ft/sec, as applicable;

(C) the two load or operating levels (i.e., low, mid, or high) identified in subsection 6.5.2.1 of Appendix A to 40 CFR Part 75 as the most frequently used;

(D) the date of the data analysis used to determine the normal load (or operating) level(s) and the two most frequently-used load or operating levels; and

(E) activation and deactivation dates when the normal load or operating levels change and are updated.

(viii) For each unit that is complying with 40 CFR Part 75 for which the optional fuel flow-to-load test in subsection 2.1.7 of Appendix D to 40 CFR Part 75 is used:

(A) the upper and lower boundaries of the range of operation as defined in subsection 6.5.2.1 of Appendix A to 40 CFR Part 75, expressed in thousands of lb/hr of steam;

(B) the load level designated as normal, pursuant to subsection 6.5.2.1 of Appendix A to 40 CFR Part 75, expressed in thousands of lb/hr of steam; and

(C) the date of the load analysis used to determine the normal load level.

(ix) Information related to quality assurance testing, including, as applicable: identification of the test strategy; protocol for the relative accuracy test audit; other relevant test information; calibration gas levels expressed as percent of span for the calibration error test and linearity check; and calculations for determining maximum potential concentration, maximum expected concentration if applicable, maximum potential flow rate, and span.

(x) If applicable, apportionment strategies under sections 75.10 through 75.18 of 40 CFR Part 75.

(xi) Description of site locations for each monitoring component in a monitoring system, including schematic diagrams and engineering drawings and any other documentation that demonstrates each monitor location meets the appropriate siting criteria. For units monitored by a continuous emission monitoring system, diagrams shall include:

(A) a schematic diagram identifying entire gas handling system from unit to stack for all units, using identification numbers for units, monitor components, and stacks corresponding to the identification numbers provided in the initial monitoring plan and (i) and (iii) above. The schematic diagram must depict the height of any monitor locations. Comprehensive and/or separate schematic diagrams shall be used to describe groups of units using a common stack; and

(B) stack and duct engineering diagrams showing the dimensions and locations of fans, turning vanes, air preheaters, monitor components, probes, reference method sampling ports, and other equipment that affects the monitoring system location, performance, or quality control checks.

(xii) A data flow diagram denoting the complete information handling path from output signals of CEMS components to final reports.

(e) In addition to supplying the information in (c) and (d) above, the WEB source with a sulfur dioxide emitting unit using either of the methodologies in (1)(a)(ii)(B) above shall include the following information in its monitoring plan for the specific situations described:

(i) For each gas-fired or oil-fired sulfur dioxide emitting unit for which the WEB source uses the optional protocol in Appendix D to 40 CFR Part 75 for sulfur dioxide mass emissions, the Account Representative shall include the following information in the monitoring plan:

(A) parameter monitored;

(B) type of fuel measured, maximum fuel flow rate, units of measure, and basis of maximum fuel flow rate expressed as the upper range value or unit maximum for each fuel flowmeter;

(C) test method used to check the accuracy of each fuel flowmeter;

(D) submission status of the data;

(E) monitoring system identification code;

(F) the method used to demonstrate that the unit qualifies for monthly gross calorific value (GCV) sampling or for daily or annual fuel sampling for sulfur content, as applicable;

(G) a schematic diagram identifying the relationship between the unit, all fuel supply lines, the fuel flowmeters, and the stacks. The schematic diagram must depict the installation location of each fuel flowmeter and the fuel sampling locations. Comprehensive or separate schematic diagrams shall be used to describe groups of units using a common pipe;

(H) for units using the optional default sulfur dioxide emission rate for "pipeline natural gas" or "natural gas" in appendix D to 40 CFR Part 75, the information on the sulfur content of the gaseous fuel used to demonstrate compliance with either subsection 2.3.1.4 or 2.3.2.4 of Appendix D to 40 CFR Part 75;

(I) for units using the 720 hour test under subsection 2.3.6 of Appendix D to 40 CFR Part 75 to determine the required sulfur sampling requirements, report the procedures and results of the test; and

(J) for units using the 720 hour test under subsection 2.3.5 of Appendix D to 40 CFR Part 75 to determine the appropriate fuel GCV sampling frequency, report the procedures used and the results of the test.

(ii) For each sulfur dioxide emitting unit for which the WEB source uses the low mass emission excepted methodology of 40 CFR 75.19, the WEB source shall include the information in (A) through (F) in the monitoring plan that accompanies the initial certification application.

(A) The results of the analysis performed to qualify as a low mass emissions unit under 40 CFR 75.19(c). This report will include either the previous three years' actual or projected emissions. The report will include the current calendar year of application; the type of qualification; years one, two, and three; annual measured, estimated or projected sulfur dioxide mass emissions for years one, two, and three; and annual operating hours for years one, two, and three.

(B) A schematic diagram identifying the relationship between the unit, all fuel supply lines and tanks, any fuel flowmeters, and the stacks. Comprehensive or separate schematic diagrams shall be used to describe groups of units using a common pipe.

(C) For units which use the long term fuel flow methodology under 40 CFR 75.19(c)(3), a diagram of the fuel flow to each unit or group of units and a detailed description of the procedures used to determine the long term fuel flow for a unit or group of units for each fuel combusted by the unit or group of units.

(D) A statement that the unit burns only gaseous fuels or fuel oil and a list of the fuels that are burned or a statement that the unit is projected to burn only gaseous fuels or fuel oil and a list of the fuels that are projected to be burned.

(E) A statement that the unit meets the applicability requirements in 40 CFR 75.19(a) and (b) with respect to sulfur dioxide emissions.

(F) Any unit historical actual, estimated and projected sulfur dioxide emissions data and calculated sulfur dioxide emissions data demonstrating that the unit qualifies as a low mass emissions unit under 40 CFR 75.19(a) and (b).

(iii) For each gas-fired unit, the account representative shall include the following in the monitoring plan: current calendar year, fuel usage data as specified in the definition of gas-fired in 40 CFR 72.2, and an indication of whether the data are actual or projected data.

(f) The specific elements of a monitoring plan under this section shall not be part of a WEB source's operating permit issued under R307-415, and modifications to the elements of the plan shall not require a permit modification.

(3) Certification and Recertification.

(a) All monitoring systems are subject to initial certification and recertification testing as specified in 40 CFR Part 75 or Appendix B of State Implementation Plan Section XX, as applicable. Certification or recertification of a monitoring system by the U.S. EPA for a WEB source that is subject to 40 CFR Part 75 under a requirement separate from this Rule shall constitute certification under the WEB Trading Program.

(b) The WEB source with a sulfur dioxide emitting unit not otherwise subject to 40 CFR Part 75 that monitors sulfur dioxide mass emissions in accordance with 40 CFR Part 75 to satisfy the requirements of this section shall perform all of the tests required by that regulation and shall submit the following to the director:

(i) a test notice, not later than 21 days before the certification testing of the monitoring system, provided that the director may establish additional requirements for adjusting test dates after this notice as part of the approval of the initial monitoring plan under (2)(c) above; and

(ii) an initial certification application within 45 days after testing is complete.

(c) A monitoring system will be considered provisionally certified while the application is pending.

(d) Upon receipt of a disapproval of the certification of a monitoring system or component, the certification is revoked. The data measured and recorded shall not be considered valid quality-assured data from the date of issuance of the notification of revocation until the WEB source completes a subsequently-approved certification or re-certification test in accordance with the procedures in this rule. The WEB source shall apply the substitute data procedures in this rule to replace all of the invalid data for each disapproved system or component.

(4) Ongoing Quality Assurance and Quality Control. The WEB source shall satisfy the applicable quality assurance and quality control requirements of 40 CFR Part 75 or, if the WEB source is subject to a WEB protocol in Appendix B of State Implementation Plan Section XX, the applicable quality assurance and quality control requirements in Appendix B of State Implementation Plan Section XX on and after the date that certification testing commences.

(5) Substitute Data Procedures.

(a) For any period after certification testing is complete in which quality assured, valid data are not being recorded by a monitoring system certified and operating in accordance with R307-250, missing or invalid data shall be replaced with substitute data in accordance with 40 CFR Part 75 or, if the WEB source is subject to a WEB protocol in Appendix B of State Implementation Plan Section XX, with substitute data in accordance with that Appendix.

(b) For a sulfur dioxide emitting unit that does not have a certified or provisionally certified monitoring system in place as of the beginning of the first control period for which the unit is subject to the WEB Trading Program, the WEB source shall use one of the following procedures.

(i) If the WEB source will use a continuous emissions monitoring system to comply with this Section, substitute the maximum potential concentration of sulfur dioxide for the unit and the maximum potential flow rate, as determined in accordance with 40 CFR Part 75. The procedures for conditional data validation under section 75.20(b)(3) may be used for any monitoring system under this Rule that uses these 40 CFR Part 75 procedures, as applicable.

(ii) If the WEB source will use the 40 CFR Part 75 Appendix D methodology, substitute the maximum potential sulfur content, density or gross calorific value for the fuel and the maximum potential fuel flow rate, in accordance with section 2.4 of Appendix D to 40 CFR Part 75.

(iii) If the WEB source will use the 40 CFR Part 75 methodology for low mass emissions units, substitute the sulfur dioxide emission factor required for the unit as specified in 40 CFR 75.19 and the maximum rated hourly heat input, as defined in 40 CFR 72.2.

(iv) If using a protocol in Appendix B of State Implementation Plan Section XX, follow the procedures in the applicable protocol.

(6) Deadlines.

(a) The initial monitoring plan required under R307-250-9(2)(a)(i) shall be submitted by the following dates:

(i) for each source that is a WEB source on or before the program trigger date, the monitoring plan shall be submitted 180 days after such program trigger date.

(ii) for any existing source that becomes a WEB source after the program trigger date, the monitoring plan shall be submitted by September 30 of the year following the inventory year in which the source exceeded the 100 tons per year sulfur dioxide emissions threshold in R307-250-4(1)(b).

(iii) for any new WEB source, the monitoring plan shall be included with the notice of intent required by R307-401.

(b) The detailed monitoring plan required under R307-250-9(2)(a)(ii) shall be submitted no later than 45 days prior to commencing certification testing in accordance with (c) below. Modifications to the monitoring plan shall be submitted within 90 days of implementing revised monitoring plans.

(c) Emission monitoring systems shall be installed, operational and shall have met all of the certification testing requirements of R307-250-9(3), including any referenced in Appendix B of State Implementation Plan Section XX, by the following dates:

(i) for each source that is a WEB source on or before the program trigger date, two years prior to the start of the first control period as described in R307-250-12.

(ii) for any existing source that becomes a WEB source after the program trigger date, one year after the due date for the monitoring plan under (6)(a)(ii) above.

(iii) for any new WEB source or any new unit at a WEB source, the earlier of 90 unit operating days or 180 calendar days after the date the new source commences operation.

(d) The WEB source shall submit test notices and certification applications in accordance with the deadlines set forth in R307-250-9(3)(b).

(e) For each control period, the WEB source shall submit each quarterly report no later than 30 days after the end of each calendar quarter, and shall submit each annual report no later than 60 days after the end of each calendar year.

(7) Recordkeeping.

(a) The WEB source shall keep copies of all reports, registration materials, compliance certifications, sulfur dioxide emissions data, quality assurance data, and other submissions under this Rule for a period of five years. In addition, the WEB source shall keep a copy of all certificates for the duration of the WEB Trading Program. Unless otherwise requested by the WEB source and approved by the director, the copies shall be kept on site.

(b) The WEB source shall keep records of all operating hours, quality assurance activities, fuel sampling measurements, hourly averages for sulfur dioxide, stack flow, fuel flow, or other continuous measurements, as applicable, and any other applicable data elements specified in this section or in Appendix B of State Implementation Plan Section XX. The WEB source shall maintain the applicable records specified in 40 CFR Part 75 for any sulfur dioxide emitting unit that uses a Part 75 monitoring method to meet the requirements of this Section.

(8) Reporting.

(a) Quarterly Reports. For each sulfur dioxide emitting unit, the account representative shall submit a quarterly report within thirty days after the end of each calendar quarter. The report shall be in a format specified by the director, including hourly and quality assurance activity information, and shall be submitted in a manner compatible with the WEB EATS. If the WEB source submits a quarterly report under 40 CFR Part 75 to the U.S. EPA Administrator, no additional report under this paragraph (a) shall be required. The director may require that a copy of that report or a separate statement of quarterly and cumulative annual sulfur dioxide mass emissions be submitted separately.

(b) Annual Report. Based on the quarterly reports, each WEB source shall submit an annual statement of total annual sulfur dioxide emissions for all sulfur dioxide emitting units at the source. The annual report shall identify total emissions for all units monitored in accordance with (1)(a) above and the total emissions for all units with emissions estimated in accordance with (1)(b) above. The annual report shall be submitted within 60 days after the end of a control period.

(c) If directed by the director, monitoring plans, reports, certifications or recertifications, or emissions data required to be submitted under this section also shall be submitted to the TSA.

(d) If the director rejects any report submitted under this subsection that contains errors or fails to satisfy the requirements of this section, the account representative shall resubmit the report to correct any deficiencies.

(9) Petitions. A WEB source may petition for an alternative to any requirement specified in (1)(a)(ii) above. The petition shall require approval of the director and the Administrator. Any petition submitted under this paragraph shall include sufficient information for the evaluation of the petition, including, at a minimum, the following information:

(a) identification of the WEB source and applicable sulfur dioxide emitting unit(s);

(b) a detailed explanation of why the proposed alternative is being suggested in lieu of the requirement;

(c) a description and diagram of any equipment and procedures used in the proposed alternative, if applicable; and

(d) a demonstration that the proposed alternative is consistent with the purposes of the requirement for which the alternative is proposed, is consistent with the purposes of R307-250, and that any adverse effect of approving such alternative will be de minimis; and

(e) any other relevant information that the director may require.

(10) For any monitoring plans, reports, or other information submitted under this Rule, the account representative shall ensure that, where applicable, identifying information is consistent with the identifying information provided in the most recent certificate for the WEB source submitted under R307-250-5.


R307-250-10. Allowance Transfers
Latest version.

(1) Procedure. To transfer allowances, the account representative shall submit the following information to the TSA:

(a) the number or numbers identifying the transferor account;

(b) the number or numbers identifying the transferee account;

(c) the serial number of each allowance to be transferred; and

(d) the transferor's account representative's name, signature, and the date of submission.

(2) Allowance Transfer Deadline. The allowance transfer deadline is midnight Pacific Standard Time on March 1 of each year, or, if this date is not a business day, midnight of the first business day thereafter, following the end of the control period. By this time, the transfer of the allowances into the WEB source's compliance account must be correctly submitted to the TSA in order to demonstrate compliance under R307-250-12 for that control period.

(3) Retirement of Allowances. To permanently retire allowances, the transferor's account representative shall submit the following information to the TSA:

(a) the transfer account number identifying the transferor account;

(b) the serial number of each allowance to be retired; and

(c) the transferor's account representative's name, signature, and the date of submission accompanied by a signed statement acknowledging that each retired allowance is no longer available for future transfers from or to any account.

(4) Special Reserve Compliance Accounts. Allowances shall not be transferred out of special reserve compliance accounts. Allowances may be transferred into special reserve compliance accounts in accordance with the procedures in paragraph (1) above.


R307-250-11. Use of Allowances from a Previous Year
Latest version.

(1) Any allowance that is held in a compliance account or general account will remain in the account until the allowance is either deducted in conjunction with the compliance process, or transferred to another account.

(2) In order to demonstrate compliance under R307-250-12(1) for a control period, WEB sources shall only use allowances allocated for that control period or any previous year.

(3) If flow control procedures for the current control period have been triggered as outlined in SIP Section XX.E.3.h(2), then the use of allowances that were allocated for any previous year will be limited in the following ways.

(a) The number of allowances that are held in each compliance account and general account as of the allowance transfer deadline for the immediately previous year and that were allocated for any previous year will be determined.

(b) The number determined in (a) above will be multiplied by the flow control ratio established in accordance with SIP Section XX.E.3.h to determine the number of allowances that were allocated for a previous year that can be used without restriction for the current control period.

(c) Allowances that were allocated for a previous year in excess of the number determined in (b) above may also be used for the current control period. If such allowances are used to make a deduction, two allowances must be deducted for each deduction of one allowance required under R307-250-12.

(4) Special provisions for the year 2018. After compliance with the 2017 allowance limitation has been determined in accordance with R307-250-12(1), allowances allocated for any year prior to 2018 shall not be used for determining compliance with the 2018 allowance limitation or any future allowance limitation.

(5) Special Reserve Compliance Accounts. Unused allowances in any special reserve compliance account will be retired after the compliance deductions under R307-250-12 have been completed for each control period, and shall not be available for use in any future control period.


R307-250-12. Compliance
Latest version.

(1) Compliance with Allowance Limitations.

(a) The WEB source must hold allowances, in accordance with (b)and (c) below and R307-250-11, as of the allowance transfer deadline in the WEB source's compliance account, together with any current control year allowances held in the WEB source's special reserve compliance account under R307-250-9(1)(b), in an amount not less than the total sulfur dioxide emissions for the control period from the WEB source, as determined under the monitoring and reporting requirements of R307-250-9.

(i) For each source that is a WEB source on or before the program trigger date, the first control period is the calendar year that is six years following the calendar year for which sulfur dioxide emissions exceeded the milestone as determined in accordance with SIP Section XX.E.1.

(ii) For any existing source that becomes a WEB source after the program trigger date, the first control period is the calendar year that is four years following the inventory year in which the source became a WEB source.

(iii) For any new WEB source after the program trigger date, the first control period is the first full calendar year that the source is in operation.

(iv) If the WEB Trading Program is triggered in accordance with the 2013 review procedures in SIP Section XX.E.1.d, the first control period for each source that is a WEB source on or before the program trigger date is the year 2018.

(b) Allowance transfer deadline. An allowance may only be deducted from the WEB source's compliance account if:

(i) the allowance was allocated for the current control period or meets the requirements in R307-250-11 for use of allowances from a previous control period, and

(ii) the allowance was held in the WEB source's compliance account as of the allowance transfer deadline for the current control period, or was transferred into the compliance account by an allowance transfer correctly submitted for recording by the allowance transfer deadline for the current control period.

(c) Compliance with allowance limitations shall be determined as follows.

(i) The total annual sulfur dioxide emissions for all sulfur dioxide emitting units at the source that are monitored under R307-250-9(1)(b), as reported by the source to the director, in accordance with R307-250-9, and recorded in the WEB EATS shall be compared to the allowances held in the source's special reserve compliance account as of the allowance transfer deadline for the current control period, adjusted in accordance with R307-250-11. If the emissions are equal to or less than the allowances in such account, all such allowances shall be retired to satisfy the obligation to hold allowances for such emissions. If the total emissions from such units exceed the allowances in such special reserve compliance account, the WEB source shall account for such excess emissions in the following paragraph (ii).

(ii) The total annual sulfur dioxide emissions for all sulfur dioxide emitting units at the source that are monitored under R307-250-9(1)(a), as reported by the source to the director in accordance with R307-250-9 and recorded in the WEB EATS, together with any excess emissions as calculated in the preceding paragraph (i), shall be compared to the allowances held in the source's compliance account as of the allowance transfer deadline for the current control period, adjusted in accordance with R307-250-11.

(iii) If the comparison in paragraph (ii) above results in emissions that exceed the allowances held in the source's compliance account, the source has exceeded its allowance limitation and the excess emissions are subject to the allowance deduction penalty in R307-250-12(3)(a).

(d) Other than allowances in a special reserve compliance account for units monitored under R307-250-9(1)(b), to the extent consistent with R307-250-11, allowances shall be deducted for a WEB source for compliance with the allowance limitation as directed by the WEB source's account representative. Deduction of any other allowances as necessary for compliance with the allowance limitation shall be on a first-in, first-out accounting basis in the order of the date and time of their recording in the WEB source's compliance account, beginning with the allowances allocated to the WEB source and continuing with the allowances transferred to the WEB source's compliance account from another compliance account or general account. The allowances held in a special reserve compliance account pursuant to R307-250-9(1)(b) shall be deducted as specified in paragraph (c)(i) above.

(2) Certification of Compliance.

(a) For each control period in which a WEB source is subject to the allowance limitation, the account representative of the source shall submit to the director a compliance certification report for the source.

(b) The compliance certification report shall be submitted no later than the allowance transfer deadline of each control period, and shall contain the following:

(i) identification of each WEB source;

(ii) at the account representative's option, the serial numbers of the allowances that are to be deducted from a source's compliance account or special reserve compliance account for compliance with the allowance limitation; and

(iii) the compliance certification report according to (c) below.

(c) In the compliance certification report, the account representative shall certify, based on reasonable inquiry of those persons with primary responsibility for operating the WEB source in compliance with the WEB Trading Program, whether the WEB source for which the compliance certification is submitted was operated in compliance with the requirements of the WEB Trading Program applicable to the source during the control period covered by the report, including:

(i) whether the WEB source operated in compliance with the sulfur dioxide allowance limitation;

(ii) whether sulfur dioxide emissions data was submitted to the director in accordance with R307-250-9(8) and other applicable requirements for review, revision as necessary, and finalization;

(iii) whether the monitoring plan for the WEB source has been maintained to reflect the actual operation and monitoring of the source, and contains all information necessary to attribute sulfur dioxide emissions to the source, in accordance with R307-250-9(2);

(iv) whether all the sulfur dioxide emissions from the WEB source if applicable, were monitored or accounted for either through the applicable monitoring or through application of the appropriate missing data procedures;

(v) if applicable, whether any sulfur dioxide emitting unit for which the WEB source is not required to monitor in accordance with R307-250-9(1)(a)(iii) of this rule remained permanently retired and had no emissions for the entire applicable period; and

(vi) whether there were any changes in the method of operating or monitoring the WEB source that required monitor recertification. If there were any such changes, the report must specify the nature, reason, and date of the change, the method to determine compliance status subsequent to the change, and specifically, the method to determine sulfur dioxide emissions.

(3) Penalties for Any WEB Source Exceeding Its Allowance Limitations.

(a) Allowance Deduction Penalty.

(i) An allowance deduction penalty will be assessed equal to three times the number of the WEB source's tons of sulfur dioxide emissions in excess of its allowance limitation for a control period, determined in accordance with R307-250-12(1). Allowances allocated for the following control period in the amount of the allowance deduction penalty will be deducted from the source's compliance account. If the compliance account does not have sufficient allowances allocated for that control period, the required number of allowances will be deducted from the WEB source's compliance account regardless of the control period for which they were allocated, once allowances are recorded in the account.

(ii) Any allowance deduction required under R307-250-12(1)(c) shall not affect the liability of the owners and operators of the WEB source for any fine, penalty or assessment or their obligation to comply with any other remedy, for the same violation, as ordered under the Clean Air Act, implementing regulations or Utah Code 19-2. Accordingly, a violation can be assessed each day of the control period for each ton of sulfur dioxide emissions in excess of its allowance limitation, or for each other violation of R307-250.

(4) Liability.

(a) WEB Source liability for non-compliance. Separate and regardless of any allowance deduction penalty, a WEB source that violates any requirement of this Rule is subject to civil and criminal penalties under Utah Code 19-2. Each day of the control period is a separate violation, and each ton of sulfur dioxide emissions in excess of a source's allowance limitation is a separate violation.

(b) General Liability.

(i) Any provision of the WEB Trading Program that applies to a source or an account representative shall apply also to the owners and operators of such source.

(ii) Any person who violates any requirement or prohibition of the WEB Trading Program will be subject to enforcement pursuant to Utah Code 19-2.

(iii) Any person who knowingly makes a false material statement in any record, submission, or report under this WEB Trading Program shall be subject to criminal enforcement pursuant to the Utah Code.


R307-250-13. Special Penalty Provisions for the 2018 Milestone
Latest version.

(1) If the WEB Trading Program is triggered as outlined in SIP Section XX.E.1, and the first control period will not occur until after the year 2018, the following provisions shall apply for the 2018 emissions year.

(a) All WEB sources shall register, and shall open a compliance account within 180 days after the program trigger date, in accordance with R307-250-6(1) and R307-250-8.

(b) The TSA will record the allowances for the 2018 control period for each WEB source in the source's compliance account once the director allocates the 2018 allowances under SIP Section XX.E.3.a and XX.E.4.

(c) The allowance transfer deadline is midnight Pacific Standard Time on May 31, 2021 (or if this date is not a business day, midnight of the first business day thereafter). WEB sources may transfer allowances as provided in R307-250-10(1) until the allowance transfer deadline.

(d) A WEB source must hold allowances allocated for 2018, including those transferred into the compliance account or a special reserve account by an allowance transfer correctly submitted by the allowance transfer deadline, in an amount not less than the WEB source's total sulfur dioxide emissions for 2018. Emissions will be determined using the pre-trigger monitoring provisions in SIP Section XX.E.2, and R307-150

(e) In accordance with R307-250-11(4) and (d) above, the director will seek a minimum financial penalty of $5,000 per ton of sulfur dioxide emissions in excess of the WEB source's allowance limitation.

(i) Any source may resolve its excess emissions violation by agreeing to a streamline settlement approach where the source pays a penalty of $5,000 per ton or partial ton of excess emissions, and payment is received within 90 calendar days after the issuance of a notice of violation.

(ii) Any source that does not resolve its excess emissions violation in accordance with the streamlined settlement approach in (i) above will be subject to enforcement action in which the director will seek a financial penalty for the excess emissions based on the statutory maximum civil penalties.

(f) Each ton of sulfur dioxide emissions in excess of a source's allowance limitation is a separate violation and each day of a control period is a separate violation.

(2) The provisions in R307-250-13 shall continue to apply for each year after the 2018 emission year until:

(a) the first control period under the WEB trading program; or

(b) the director determines, in accordance with SIP Section XX.E.1.c(10), that the 2018 sulfur dioxide milestone has been met.

(3) If the special penalty provisions continue after the year 2018 as outlined in (2) above, the deadlines listed in (1)(b) through (e) above will be adjusted as follows:

(i) for the 2019 control period the dates will be adjusted forward by one year, except that the allowance transfer deadline shall be midnight Pacific Standard Time on May 31, 2021 (or if this date is not a business day, midnight of the first business day thereafter); and

(ii) for each control period after 2018 that the special penalty provisions are assessed, the dates in (i) above for the 2019 control period will be adjusted forward by one year.

(4) The TSA will record the same number of allowances for each WEB source as were recorded for the 2018 control period for each subsequent control period.


R307-250-14. Integration into Permits
Latest version.

(1) Initial Permitting. Each source that is a WEB source on or before the program trigger date shall follow the procedures outlined in R307-415 to incorporate all of the applicable requirements of this rule into the permit issued to it under R307-415.

(2) Post Trigger Permitting.

(a) New WEB Source. Any existing source that becomes a WEB source after the program trigger date shall submit a Notice of Intent pursuant to R307-401 to incorporate all of the requirements of this rule into an approval order issued under R307-401 within 90 days of the date the source became a WEB source, and shall follow the procedures of R307-415 to obtain an operating permit.

(b) WEB Sources No Longer Subject to Permitting Under R307-415. If a WEB source's permit issued under R307-415 ceases to be effective or required, the WEB source must submit a Notice of Intent pursuant to R307-401 to incorporate all of the requirements of this rule into an approval order issued under R307-401 within 90 days of the date the permit issued under R307-415 ceased to be effective or required.