# ECMPS Reporting Instructions Monitoring Plan

United States Environmental Protection Agency

Office of Air and Radiation

Clean Air Markets Division

1310 L Street, NW Washington, DC 20005

March 07, 2012 September 19, 2012Table of Contents March 07, 2012 September 19, 2012



### Table of Contents

Page

1.0 Introduction: The Monitoring Plan

.................................................................................... 1

2.0 Monitoring Plan (Root Element)

.......................................................................................... 5

2.1 Monitoring Plan Comment Data

........................................................................................ 7

2.2 Unit Stack Configuration Data

........................................................................................... 9

2.3 Monitoring Location Data

................................................................................................ 11

3.0 Stack Pipe Data

.................................................................................................................... 13

4.0 Unit Data

............................................................................................................................... 17

4.1 Unit Capacity Data

........................................................................................................... 19

4.2 Unit Control Data

............................................................................................................. 21

4.3 U nit Fuel Data

.................................................................................................................. 25

5.0 Monitoring Location Attribute Data

.................................................................................. 29

6.0 Monitoring Method Data

.................................................................................................... 33

7.0 Component Data

.................................................................................................................. 41

7.1 Ana lyzer Range Data

....................................................................................................... 49

8.0 Monitoring System Data

...................................................................................................... 53

8.1 Monitoring System Fuel Flow Data

................................................................................. 63

8.2 Monitoring System Component Data

.............................................................................. 67

9.0 Monitoring Formula Data

................................................................................................... 69

10.0 Monitoring Default Data

................................................................................................... 91

11.0 Monitoring Span Data

..................................................................................................... 109

12.0 Rectangular Duct WAF Data

.......................................................................................... 119

13.0 Monitoring Load Data

..................................................................................................... 123

14.0 Monitoring Qualification Data

....................................................................................... 131

14.1 Monitoring Qual LME Data

......................................................................................... 135

14.2 Monitoring Qual Percent Data

..................................................................................... 141

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page i

### 5

10

15

20

25

30

35 March 07, 2012 September 19, 2012 Table of Contents



### List of Tables

Pa ge

Table 1 Stack Pipe ID Prefixes

.................................................................................................... 14 Table 2 Parameter Codes and Descriptions

................................................................................. 22 Table 3 Control Codes and Descriptions

..................................................................................... 22 Table 4 Unit Fuel Codes and Descriptions

.................................................................................. 26 Table Unit Fuel Indicator Codes and Descriptions

................................................................... 27 Table 6 Demonstration Method to Qualify for Monthly Fuel Sampling for GCV Codes and Descriptions

.................................................................................................................. 27 Table 7 Demonstration Method to Qualify for Daily or Annual Fuel Sampling for %S (ARP) Codes and Descriptions

................................................................................................ 28 Table 8 Duct/Stack Material Codes and Description

................................................................... 31

Table 9 Duct/Stack Shape Codes and Descriptions

..................................................................... 31 Table Parameter Codes and Descriptions for Monitoring Methods

....................................... 34 Table 11 Measured Parameters and Applicable Monitoring Methods

........................................ 35 Table 12 Substitute Data Codes and Descriptions

....................................................................... 37 Table 13 Bypass Approach Codes and Descriptions

................................................................... 38 Table 14 Component Type Codes and Descriptions

................................................................... 43 Table Sample Acquisition Method Codes for Components

................................................... 44 Table 16 Basis Codes and Descriptions for CEM Analyzer Components

................................... 46 Table 17 Analyzer Range Codes and Descriptions

...................................................................... 50 Table 18 System Type Codes and Descriptions

.......................................................................... 54 Table 19 System Designation Code and Descriptions

................................................................. 56 Table Monitoring System Fuel Codes and Descriptions

........................................................ 57 Table 21 Units of Measure for Maximum Fuel Flow Rate Codes and Descriptions

................... 64 Table 22 Parameter Codes and Descriptions for Monitoring Formula

....................................... 70

Table 23 F- Factor* Reference Table

........................................................................................... 72

Table 24 SO 2 

### Formula References

............................................................................................... 74

Table SO 2 

### Emission Formulas

................................................................................................ 74

Table 26 NO

x 

### Emission Rate Formula Reference Table

............................................................. 76

Table 27 NO

x 

### Emission Rate Formulas (lb/mmBtu)

................................................................... 77

Table 28 Moisture Formulas

........................................................................................................ 78

Table 29 CO 2 

### Formula Reference Table

...................................................................................... 78

Table CO 2 

### Concentration and Mass Emission Rate Formulas

............................................... 79 Table 31 Heat Input Formula Reference Table

............................................................................ 81 Table 32 Heat Input Formulas

..................................................................................................... 83 Table 33 Apportionment and Summation Formulas

.................................................................... 85

Table 34 NO

x 

### Mass Emissions Formulas (lbs/hr)

........................................................................ 86

Table Miscellaneous Formula Codes

...................................................................................... 87 Table 36 Representations for Electronic Reporting of Formulas

................................................ 88 Table 37 Parameter Codes and Descriptions for Monitoring Default

......................................... 94 Table 38 Rounding Rules f or Default Values

.............................................................................. 96

Table 39 Fuel

- Specific Minimum Default Moisture Values for SO 2 

### , NO

x 

### , CO 2 

### , and Heat Input

Rate Calculations

.......................................................................................................... 98

Table 40 Fuel

- Specific Maximum Default Moisture Values for NO

x 

### Emission Rate Calculations

................................................................................................ ...................................... 98

Monitoring Plan Reporting Instructions

-- Page ii Environmental Protection AgencyTable of Contents March 07, 2012 September 19, 2012



### Table 41 NO

x 

### Emission Factors (lb/mmBtu) for Low Mass Emissions Units

............................ 99

Table 42 SO 2 

### Emission Factors (lb/mmBtu) for Low Mass Emissions Units

............................. 99

Table 43 CO 2 

### Emission Factors (ton/mmBtu) for Low Mass Emissions Units

.......................... 99 Table 44 Units of Measure Codes by Parameter

....................................................................... 100 Table 45 Default Purpose Codes and Descriptions

.................................................................... 101 Table 46 Monitoring Default Fuel Codes and Descriptions

...................................................... 101 Table 47 Monitoring Default Operating Condition Codes and Descriptions

............................ 105 Table 48 Default Source Codes and Descriptions

..................................................................... 105 Table 49 Component Type Codes and Descriptions for Monitor Span

..................................... 110 Table 50 Provision for Calculating MPC/MEC/MPF Codes and Descriptions

......................... 111

Table 51 Criteria for MPC/MEC/MPF Determinations

............................................................. 112 Table 52 Flow Span Calibration Units of Measure

................................................................... 115 Table 53 WAF Method Code and Descriptions

......................................................................... 121 Table 54 Maximum Load Value Codes and Descriptions

......................................................... 125 Table 55 Qualification Type Codes and Descriptions

............................................................... 132 Table 56 Data Requirements for Monitoring Qual LME

........................................................... 136 Table 57 Qualification Data Type Code and Descriptions

........................................................ 142 Table 58 Example Data for Qualification Based on Historical and Projected Data

.................. 144 Table 59 Example of Gas- Fired Qualification Based on Unit Operating Data

......................... 145

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page iiiMarch 07, 2012 September 19, 2012 Table of Contents



### List of Figures

Page

Figure 1 Monitoring Plan XML Schema Complex Elements

........................................................ 3 Figure 2 M ONITORING 

### P LAN 

### XML Elements

................................................................................. 5 Figure 3 M ONITORING 

### P LAN 

### C OMMENT 

### D ATA 

### XML Elements

..................................................... 7 Figure 4 U NIT 

### S TACK 

### C ONFIGURATION 

### D ATA 

### XML Elements

...................................................... 9 Figure 5 M ONITORING 

### L OCATION 

### D ATA 

### Elements

...................................................................... 11 Figure 6 S TACK 

### P IPE 

### D ATA 

### Elements

.......................................................................................... 13 Figure 7 U NIT 

### D ATA 

### XML Elements

........................................................................................... 17 Figure 8 U NIT 

### C APACITY 

### D ATA 

### XML Elements

.......................................................................... 19 Figure 9 U NIT 

### C ONTROL 

### D ATA 

### XML Elements

........................................................................... 21 Figure 10 U NIT 

### F UEL 

### D ATA 

### XML Elements

................................................................................ 25 Figure 11 M ONITORING 

### L OCATION 

### A TTRIBUTE 

### D ATA 

### XML Elements

....................................... 29 Figure 12 M ONITORING 

### M ETHOD 

### D ATA 

### XML Elements

............................................................. 33 Figure 13 C OMPONENT 

### D ATA 

### XML Elements

............................................................................. 41 Figure 14 A NALYZER 

### R ANGE 

### D ATA 

### XML Elements

................................................................... 49 Figure 15 M ONITORING 

### S YSTEM 

### D ATA 

### XML Elements

.............................................................. 53 Figure 16 M ONITORING 

### S YSTEM 

### F UEL 

### F LOW 

### D ATA 

### XML Elements

........................................... 63 Figure 17 M ONITORING 

### S YSTEM 

### C OMPONENT 

### D ATA 

### XML Elements

......................................... 67 Figure 18 M ONITORING 

### F ORMULA 

### D ATA 

### XML Elements

........................................................... 69 Figure 19 M ONITORING 

### D EFAULT 

### D ATA 

### XML Elements

............................................................ 91 Figure 20 M ONITORING 

### S PAN 

### D ATA 

### XML Elements

................................................................. 109 Figure 21 R ECTANGULAR 

### D UCT 

### WAF D ATA 

### XML Elements

................................................... 119 Figure 22 M ONITORING 

### L OAD 

### D ATA 

### XML Elements

................................................................ 123 Figure 23 M ONITORING 

### Q UALIFICATION 

### D ATA 

### XML Elements

................................................ 131 Figure 24 M ONITORING 

### Q UAL 

### LME D ATA 

### XML Elements

....................................................... 135 Figure 25 M ONITORING 

### Q UAL 

### P ERCENT 

### D ATA 

### XML Elements

................................................ 141

Monitoring Plan Reporting Instructions

-- Page iv Environmental Protection AgencyTable of Contents March 07, 2012 September 19, 2012



### [This page intentionally left blank.]

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page v1.0 Introduction: The Monitoring Plan March 07, 2012 September 19, 2012



## ECMPS Reporting Instructions Monitoring Plan

1.0 I NTRODUCTION 

## : The Monitoring Plan

About This Document

In the Emissions Collection and Monitoring Plan System (ECMPS), data must be submitted to the EPA through the Client Tool using extensible-markup language (XML) format. XML files must contain certain data elements, which are defined in the XML schema. (Note: More information about the ECMPS XML Schemas can be found in the XML Schema Description Documents.)

The purpose of the reporting instructions is to provide the necessary information for owners and operators to meet the reporting requirements for sources affected by:

1) T he Acid Rain Program (ARP); 2) T he Clean Air Interstate Rule (CAIR); and 3) Other programs required to report data using these XML schemas.

These instructions explain how to report the required data for the applicable regulations. Owners and operators of units should refer to the applicable regulations for information about what data are required to be reported.

The Monitoring Plan XML Schema is made up of a root element, complex elements, and simple

elements. A simple element is a single piece of data. A complex element is a group of simple elements which are logically grouped together. The root element is the base of the XML

schema.

The elements are related to each other in parent

- child relationships. The root element is the parent element of the entire schema. Complex elements are children of the root element, and complex elements can also be children of other complex elements. If a complex element is dependent on a parent complex element, the child complex element cannot be included in the

XML file unless the appropriate parent complex element is also included. Figure 1 below illustrates the relationships between the monitoring plan root element and the complex elements.

This document provides instructions on how the required data should be reported using this data structure. A separate section is provided for each complex element, its dependencies, and its simple elements. In addition, there are " specific considerations " that apply to particular types of

mo nitoring plan configurations.

About Monitoring Plan Data

The Monitoring Plan describes how a monitoring configuration monitors its emissions. Monitoring plan data define relationships between stacks, pipes, and units, specify locations at a

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 1March 07, 2012 September 19, 2012 1.0 Introduction: The Monitoring Plan



### facility from which emissions are monitored, and ide ntify systems of monitoring equipment by detailing the individual system components. Monitoring plan data also provide operational characteristics and qualifications for certain special types of monitoring (e.g., Low Mass Emissions monitoring).

Monitoring Plan Reporting Instructions

-- Page 2 Environmental Protection Agency1.0 Introduction: The Monitoring Plan March 07, 2012 September 19, 2012



### Figure 1 Monitoring Plan XML Schema Complex Elements

Parent

and
Child

Child Only

Root

Element LEGEND

2.0 Monitoring Plan

2.3 Monitoring

Location 2.1 Monitoring
Plan Comment 2.2
Unit Stack Configuration

3.0 Stack Pipe

Data 4.0

Unit Data 4.1

Unit Capacity

4.2

Unit
Control

4.3

10.0 Monitoring

Default 12.0 Rectangular

Duct WAF 6.0 Monitoring

Method 11.0 Monitoring

Span 9.0 Monitoring

Formula

8.0 Monitoring

System 7.0 Component

8.2 Monitoring

System Component 14

. 2 Monitoring
Qualification

LME 14

. 1 Monitoring
Qualification

Percent Unit Fuel

13.0 Monitoring

Load 5.0 Monitoring

Location

Attribute

7.1 Analyzer

Range 14.0 Monitoring
Qualification

7.2
Calibration

Standard

8.1 Monitoring

System

Fuel Flow

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 3March 07, 2012 September 19, 2012 1.0 Introduction: The Monitoring Plan



### [This page intentionally left blank.]

Monitoring Plan Reporting Instructions

-- Page 4 Environmental Protection Agency2.0 Monitoring Plan March 07, 2012 September 19, 2012



## 2.0 M ONITORING 

## P LAN 

## (Root Element)

Figure 2

M ONITORING 

### P LAN 

### XML Elements

Description of Data

The M ONITORING 

### P LAN 

### root element defines the configuration of the monitoring plan and is the "keystone" record for building a monitoring plan. Hence t he M ONITORING 

### P LAN 

### record includes essential identifying information for a complete monitoring plan. Submit one M ONITORING 

### P LAN


### record for each monitoring plan and ensure that it is the first data record reported.

Dependencies for M ONITORING 

### P LAN



### The M ONITORING 

### P LAN 

### re cord is not dependent on any other elements of the monitoring plan.

The following complex elements specify additional monitoring plan data and are dependent on

the M ONITORING 

### P LAN 

### record:

● M ONITORING 

### P LAN 

### C OMMENT 

### D ATA



### ● U NIT 

### S TACK 

### C ONFIGURATION 

### D ATA



### ● M ONITORING 

### L OCATION 

### D ATA



### These complex elements cannot be submitted for a monitoring plan unless an applicable

M ONITORING 

### P LAN 

### record is included.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 5March 07, 2012 September 19, 2012 2.0 Monitoring Plan



### M ONITORING 

### P LAN 

### Elements

Instructions for completing each element of the M ONITORING 

### P LAN 

### section are provided below:

ORIS Code

Element Name: ORISCode

Report the code that indicates the unique identifying number given to a plant by the Energy

Information Administration ( EIA ) and remains unchanged under ownership changes.

Version

Element Name: Version

Report the XML schema version number. Note that this is a numeric field

-- do not include a "v"

before the number.

Monitoring Plan Reporting Instructions

-- Page 6 Environmental Protection Agency2.1 Monitoring Plan Comment Data March 07, 2012 September 19, 2012



## 2 .1 M ONITORING 

## P LAN 

## C OMMENT 

## D ATA



### Figure 3

M ONITORING 

### P LAN 

### C OMMENT 

### D ATA 

### XML Elements

Description of Data

If necessary, you may s ubmit a M ONITORING 

### P LAN 

### C OMMENT 

### D ATA 

### record with each monitoring plan submission or revision. The M ONITORING 

### P LAN 

### C OMMENT 

### D ATA 

### record allows you to include comments regarding the monitoring plan submission. If you do not have any comments on the plan, omit the M ONITORING 

### P LAN 

### C OMMENT 

### D ATA 

### complex element entirely.

Dependencies for M ONITORING 

### P LAN 

### C OMMENT 

### D ATA



### The M ONITORING 

### P L AN 

### C OMMENT 

### D ATA 

### record is dependent on the M ONITORING 

### P LAN 

### record.

No other records are dependent upon the M ONITORING 

### P LAN 

### C OMMENT 

### D ATA 

### record.

M ONITORING 

### P LAN 

### C OMMENT 

### D ATA 

### Elements

Instructions for completing each element of the M ONITORING 

### P LAN 

### C OMMENT 

### D ATA 

### section are provided below:

Monitoring Plan Comment

Element Name: MonitoringPlanComment

Report any comments concerning the monitoring plan.

Begin Date
Element Name: Begin Date

Report the date on which the comment became effective

.

End Date
Element Name: EndDate

If applicable, report the last date on the comment was effective

. This value should be left blank

for active records.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 7March 07, 201 2 September 19, 2012 2.1 Monitoring Plan Comment Data



### [This page intentionally left blank.]

Monitoring Plan Reporting Instructions

-- Page 8 Environmental Protection Agency2.2 Unit Stack Configuration Data March 07, 2012 September 19, 2012



## 2.2 U NIT 

## S TACK 

## C ONFIGURATION 

## D ATA



### Figure 4

U NIT 

### S TACK 

### C ONFIGURATION 

### D ATA 

### XML Elements

Description of Data

Submit a U NIT 

### S TACK 

### C ONFIGURATION 

### D ATA 

### record for each unit- stack relationship defined in the monitoring plan. Each U NIT 

### S TACK 

### C ONFIGURATION 

### D ATA 

### record identifies a specific configuration or relationship between a unit and a monitored stack through which it exhausts, or a unit and a pipe that serves the unit. This relationship defines the configuration and methods used for monitoring. See the instructions for the S TACK 

### P IPE 

### D ATA 

### record for more information about when and how to define multiple and common stacks and pipes.

Dependencies for U NIT 

### S TACK 

### C ONFIGURAT ION 

### D ATA



### The U NIT 

### S TACK 

### C ONFIGURATION 

### D ATA 

### record is dependent on the M ONITORING 

### P LAN 

### record.

No other records are dependent upon the U NIT 

### S TACK 

### C ONFIGURATION 

### D ATA 

### record.

Unit Stack Configuration Data Elements

Instructions for completing each element of the U NIT 

### S TACK 

### C ONFIGURATION 

### D ATA 

### section are provided below:

Stack Pipe ID

Element Name: StackPipeID

Report the Stack Pipe ID that corresponds to the monitoring location. This is the alphanumeric code assign ed by a source to identify a multiple or common stack or pipe at which emissions are

determined.

Unit ID

Element Name: UnitID

Report the applicable Unit ID for the unit that is linked to the stack or pipe. This is the one to six alphanumeric character code assigned by a source to identify a unit.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 9March 07, 2012 September 19, 2012 2.2 Unit Stack Configuration Data



### Begin Date
Element Name: Begin Date

Report the date on which some or all of the emissions from the unit were first measured at the common or multiple stack/p ipe. This data should be equal to or later than the ActiveDate for the StackPipe, as reported in the S TACK 

### P IPE 

### D ATA 

### record.

End Date
Element Name: EndDate

If the unit is no longer linked to the stack or pipe in terms of monitored emissions, report the last

date on which the emissions from the unit were measured at the common or multiple stack/pipe. For an active relationship, leave this field blank.

Monitoring Plan Reporting Instructions

-- Page 10 Environmental Protection Agency2.3 Monitoring Location Data March 07, 2012 September 19, 2012



## 2.3 M ONITORING 

## L OCATION 

## D ATA



### Figure 5

M ONITORING 

### L OCATION 

### D ATA 

### Elements

Description of Data

The M ONITORING 

### L OCATION 

### D ATA 

### record is used to identify the unit(s) in the monitoring plan, as well as any stack(s) or pipe(s) defined as a monitoring location. Submit a M ONITORING


### L OCATION 

### D ATA 

### record for each stack, pipe, and unit in the monitoring plan. See instructions for

the S TACK 

### P IPE 

### D ATA 

### record for more information about defining stacks and pipes.

Dependencies for Monitoring Location Data

The M ONITORING 

### L OCATION 

### D ATA 

### record is dependent on the M ONITORING 

### P LAN 

### record.

The following complex elements specify additional monitoring location data and are dependent

on the M ONITORING 

### L OCATION 

### D ATA 

### record:

● S TACK 

### P IPE 

### D ATA



### ● U NIT 

### D ATA



### These complex elements cannot be submitted for a monitoring location unless an applicable

M ONITORING 

### L OCATION 

### D ATA 

### record is included.

M ONITORING 

### L OCATION 

### D ATA 

### Elements

Instructions for completing each element of the M ONITORING 

### L OCATION 

### D ATA 

### section are provided below:

Stack Pipe ID

Element Name: StackPipeID

If this record is for a stack or pipe, report the Stack Pipe ID that corresponds to the monitoring location. This is the alphanumeric code assigned by a source to identify the stack or pipe. If this record is for a unit, leave this field blank.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 11March 07, 2012 September 19, 2012 2.3 Monitoring Location Data



### Unit ID

Element Name: UnitID

If this record is for a unit, report the Unit ID that corresponds to the monitoring location being

described. This is the alphanumeric code assigned by a source to identify a unit. If this record is for a Stack or Pipe, leave this field blank.

Monitoring Plan Reporting Instructions

-- Page 12 Environmental Protection Agency3.0 Stack Pipe Data



## 3.0 S TACK 

## P IPE 

## D ATA March 07, 2012September 19, 2012



### Figure 6

S TACK 

### P IPE 

### D ATA 

### Elements

Description of Data

Submit a S TACK 

### P IPE 

### D ATA 

### record describing each stack or pipe at which emissions from more than one unit are measured or determined (i.e., a common stack or pipe) or stacks from which partial emissions from a unit are measured (i.e., a multiple stack). Bypass stacks should be defined as monitoring locations only if the emissions from the bypass are monitored (as opposed to using maximum potential or other appropriate substitute data values).

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 13March 07, 2012 September 19, 2012 3.0 Stack Pipe Data



### Types of Stacks and Pipes

When assigning IDs to stack s or pipes, consider the following types of stacks and pipes and the associated ID prefix:

● Common Stacks : If a stack serves more than one unit and emissions are monitored at that stack, it must be defined as a " common stack " for reporting purposes. Assign a common stack ID beginning with the prefix " CS " followed by one to four alphanumeric

characters.

● Common Pipes: If a fuel pipe serves more than one unit and fuel flow is monitored at that common pipe header, it must be defined as a "common pipe" for reporting purposes. Assign a pipe ID beginning with the prefix " CP " followed by one to four additional alphanumeric characters . If more than one fuel type is associated with the same group of units, it is not necessary to report a common pipe for each fuel type; rather, define one "common pipe" and define separate fuel flow monitoring systems for each fuel type at the pipe.

● Multiple Ducts or Stacks: A multiple stack defines two or more ducts or stacks in

which C EMS are located for a single unit

. (I t also defines any additional monitoring location(s) for a single unit that is also monitored at a common stack or common pipe.) If a unit has a CEMS located in more than one duct or stack from the unit, assign a mult iple stack ID to each monitoring location. Assign a stack ID beginning with the prefix " MS " followed by one to four alphanumeric character s.

● Multiple Pipes : For a combined cycle (CC) peaking unit with a combustion turbine and duct burner for which: (1) Appendices D and E are used; and (2) fuel flow is measured separately for the turbine and duct burner, define multiple pipes, i.e., one for each fuel flowmeter location. Assign a pipe ID beginning with the prefix " MP " followed by one to four alphanum eric characters. Consult with the EPA Clean Air Markets Division or s tate agency prior to initial monitoring plan submission if a facility has this configuration.

Table 1 summarizes the information above:

Table 1 Stack Pipe ID Prefixes

Prefix Descrip tion

CS Common Stack

CP Common Pipe

MS Multiple Stack o r Duct

MP Multiple Pipe

Monitoring Plan Reporting Instructions

-- Page 14 Environmental Protection Agency3.0 Stack Pipe Data March 07, 2012 September 19, 2012



### Dependencies for S TACK 

### P IPE 

### D ATA



### The S TACK 

### P IPE 

### D ATA 

### record is dependent on the M ONITORING 

### L OCATION 

### D ATA 

### record.

The following complex elements specify additional monitoring plan data and are dependent on

the S TACK 

### P IPE 

### D ATA 

### record:

● M ONITORING 

### L OCATION 

### A TTRIB 

### D ATA



### ● M ONITORING 

### M ETHOD 

### D ATA



### ● M ONITORING 

### F ORMULA 

### D ATA



### ● M ONITORING 

### D EFAULT 

### D ATA



### ● M ONITORING 

### S PAN 

### D ATA



### ● M ONITORING 

### L OAD 

### D ATA



### ● C OMPONENT 

### D ATA



### ● M ONITORING 

### S YSTEM 

### D ATA



### ● M ONITORING 

### Q UALIFICATION 

### D ATA



### ● R ECTANGULAR 

### D UCT 

### WAF D ATA



### These complex elements cannot be submitted for a stack or pipe unless an applicable S TACK 

### P IPE


### D ATA 

### record is included.

S TACK 

### P IPE 

### D ATA 

### Elements

Instructions for completing each element of the S TACK 

### P IPE 

### D ATA 

### section are provided below:

Active Date

Element Name: ActiveDate

Report either the date emissions first went through the stack or, for a stack or pipe existing prior to the date that the associated unit(s) became subject to the applicable program, report that program effective date . For a stack or pipe that became operational after the associated unit ' s

program effective date, report the actual date on which emissions first exit ed the stack or fuel

wa s combusted at the pipe or stack location by an affected unit.

Retire Date

Element Name: RetireDate

If applicable, report the actual date the stack or pipe was last used for emissions measurement or estimation purposes. Do not report estimated dates in this field. For active stacks and pipes,

leave this field blank.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 15March 07, 2012 September 19, 2012 3.0 Stack Pipe Data



### [This page intentionally left blank.]

Monitoring Plan Reporting Instructions

-- Page 16 Environmental Protection Agency4.0 Unit Data



## 4.0 U NIT 

## D ATA March 07, 2012September 19, 2012



### Figure 7

U NIT 

### D ATA 

### XML Elements

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 17March 07, 2012 September 19, 2012 4.0 Unit Data



### Description of Data

The U NIT 

### D ATA 

### record is used to define, for each unit identified in the M ONITORING 

### L OCATION


### D ATA 

### record

, whether that unit is a non- load -based unit under Part 75. Submit a U NIT 

### D ATA


### record for each unit that is part of the monitoring plan configuration, whether or not monitoring is to be performed at the unit level. Information regarding the unit' s heat input capacity, associated controls, and available fuels will be linked to each unit identified by a U NIT 

### D ATA


### record.

Dependencies for U NIT 

### D ATA



### The U NIT 

### D ATA 

### record is dependent on the M ONITORING 

### L OCATION 

### D ATA 

### record.

The following complex elements specify additional unit data and are dependent on the U NIT


### D ATA 

### record:

● M ONITORING 

### L OCATION 

### A TTRIBUTE 

### D ATA



### ● U NIT 

### C APACITY 

### D ATA



### ● U NIT 

### C ONTROL 

### D ATA



### ● U NIT 

### F UEL 

### D ATA



### ● M ONITORING 

### M ETHOD 

### D ATA



### ● M ONITORING 

### F ORMULA 

### D ATA



### ● M ONITORING 

### D EFAULT 

### D ATA



### ● M ONITORING SPAN 

### D ATA



### ● M ONITORING LOAD 

### D ATA



### ● C OMPONENT 

### D ATA



### ● M ONITORING SYSTEM 

### D ATA



### ● M ONITORING QUALIFICATION 

### D ATA



### ● R ECTANGULAR 

### D UCT 

### WAF D ATA



### These complex elements cannot be submitted for a unit unless an applicable U NIT 

### D ATA 

### record

is included. See the instructions for each complex element to determine whether or not to

include it for a particul ar unit.

U NIT 

### D ATA 

### Elements

Instructions for completing each element of the U NIT 

### D ATA 

### section are provided below:

Non Load Based Indicator

Element Name: NonLoadBasedIndicator

Report a non load-based indicator value of "1" if the unit does not produce electrical or steam load. Report a "0" if the unit does produce electrical or steam load.

Monitoring Plan Reporting Instructions

-- Page 18 Environmental Protection Agency4.1 Unit Capacity Data March 07, 2012 September 19, 2012



## 4.1 U NIT 

## C APACITY 

## D ATA



### Figure 8

U NIT 

### C APACITY 

### D ATA 

### XML Elements

Description of Data

Report a U NIT 

### C APACITY 

### D ATA 

### record for each unit defined in a U NIT 

### D ATA 

### record of the monitoring plan. This record is used to specify the maximum hourly heat input capacity for each unit. Update this record only if the maximum hourly heat input capacity changes based on the design of the unit or its observed data over the past five years.

For more information on derated, combined cycle, and Low Mass Emission ( LME ) units for this

record see the " Specific Considera tions" section below.

Dependencies for U NIT 

### C APACITY 

### D ATA



### The U NIT 

### C APACITY 

### D ATA 

### record is dependent on the U NIT 

### D ATA 

### record.

No other records are dependent upon the U NIT 

### C APACITY 

### D ATA 

### record.

U NIT 

### C APACITY 

### D ATA 

### Elements

Instructions for completing each element of the U NIT 

### C APACITY 

### D ATA 

### section are provided

below:

Maximum Hourly Heat Input Capacity

Element Name: MaximumHourlyHeatInputCapacity

Report the design heat input capacity (in mmBtu/hr) for the unit or the highest hourly heat input rate observed in the past five years, whichever is greater.

Begin Date
Element Name: Begin Date

Report the date on which the reported maximum hourly heat input capacity for a unit became

effective.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 19March 07, 2012 September 19, 2012 4.1 Unit Capacity Data



### End Date
Element Name: EndDate

Report the last date on which the reported maximum hourly heat input capacity for a unit was

valid. This value should be left blank for active records.

Specific Considerations

Derated Units

● If a unit has been derated, report the derated maximum heat input capacity.

Combined Cycle Units

● For combined cycle units without duct burners, report the maximum heat input of the unit

combustion turbine. For combined cycle units with duct burner s, report the combined maximum heat input for the combustion turbine and duct burner, unless, in agreement with EPA, the duct burner has been defined as a separate unit.

Low Mass Emission (LME) Units

● Enter the maximum rated hourly heat input for units using the LME methodology as defined in §72.2 or modified according to §75.19(c)(2)(i).

Monitoring Plan Reporting Instructions

-- Page 20 Environmental Protection Agency4.2 Unit Control Data March 07, 2012 September 19, 2012



## 4 .2 U NIT 

## C ONTROL 

## D ATA



### Figure 9

U NIT 

### C ONTROL 

### D ATA 

### XML Elements

Description of Data

The U NIT 

### C ONTROL 

### D ATA 

### record is used to identify emissions controls that are utilized or planned for the specified unit. Submit a U NIT 

### C ONTROL 

### D ATA 

### record for each type of NO

x 

### , SO 2 

### , or particulate control equipment in place or planned for each unit defined in the monitoring plan. These data include information describing the parameter emitted and the corresponding control

type

. For con trols with co -benefits (e.g., flue gas desulfurization systems ( FGD ) ), just list the control once using the parameter code that corresponds to the pr imary pollutant controlled.

Do not report U NIT 

### C ONTROL 

### D ATA 

### for any parameter ( NOX, SO 2, or PART ) for which the unit

is uncontrolled. Similarly, do not report unit control data for a parameter if emissions of that parameter are controlled only by limiting production or by switching fuels.

Dependencies for U NIT 

### C ONTROL 

### D ATA



### The U NIT 

### C ONTROL 

### D ATA 

### record is dependent on the U NIT 

### D ATA 

### record.

No other records are dependent upon the U NIT 

### C ONTROL 

### D ATA 

### record

.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 21March 07, 2012 September 19, 2012 4.2 Unit Control Data



### U NIT 

### C ONTROL 

### D ATA 

### Elements

Instructions for completing each element of the U NIT 

### C ONTROL 

### D ATA 

### section are provided

below:

Parameter Code

Element Name: ParameterCode

Report the parameter being controlled by using one of the following upp ercase codes as shown

in Table 2 :

Table 2

Parameter Codes and Descriptions

Code Description

NOX Nitrogen Oxides

SO2 Sulfur Dioxide

PART Particulates (o pacity)



### Control Code

Element Name: ControlCode

Report the code for the corresponding control device by reporting the uppercase contr ol code as

shown in Table 3:

Table 3 Control Codes and Descriptions

Parameter Control

Code Description

NOX CM Combustion Modification/Fuel Reburning

DLNB Dry Low NO

x Premixed Technology (t urbines only)

H2O Water Injection (turbines and cyclone b oilers only)

LNB Low NO

x Burner Technology (dry bottom wall

- fired b oilers or process h eaters only)

LNBO Low NO

x Burner Technology with Overfire Air (dry bottom w all

fired boilers, dry bottom t urbo

- fired boilers, or process h eaters o nly)

(cont.)

Monitoring Plan Reporting Instructions

-- Page 22 Environmental Protection Agency4.2 Unit Control Data March 07, 2012 September 19, 2012



### Table 3 Control Codes and Descriptions (cont.)

Parameter Control

Code Description

NOX (cont.) LNC1 Low NO

x Burner Technology with Close

- C oupled Overfire Air ( OFA ) (t angentially fired units only)

LNC2 Low NO

x Burner Technology with Separated OFA (t angentially fired units only)

LNC3 Low NO

x Burner Technology with Close

- C oupled and Separated OFA (t angentially fired units only)

LNCB Low NO

x Burner Technology for Cell Burners

NH3 Ammonia Injection

O Other

OFA Overfire Air

SCR Selective Catalytic Reduction

SNCR Selectiv e Non

- C atalytic Reduction

STM Steam Injection

SO2 DA Dual Alkali

DL Dry Lime FGD

FBL Fluidized Bed Limestone Injection

MO Magnesium Oxide

O Other

SB Sodium Based

WL Wet Lime FGD

WLS Wet Limestone

PART B Baghouse(s)

ESP Electrostatic Precipitator

HESP Hybrid Electrostatic Precipitator

WESP Wet Electrostatic Precipitator

WS Wet Scrubber

O Other

C Cyclone

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 23March 07, 2012 September 19, 2012 4.2 Unit Control Data



### Original Code

Element Name: OriginalCode

For each record, indicate whether or not the control equipment was installed and operational as part of the original unit design. The number "1" indicates the equipment was a part of the original unit, and "0" indicates that it was not.

Install Date
Element Name: InstallDate

Report the approximate date on which controls were installed o r will be installed at the unit, if the control equipment was not part of the original installation. If the equipment was part of the original installation, leave this field blank.

Optimization Date

Element Name: OptimizationDate

Report the approximate date on which optimization of the control equipment was completed and the equipment was fully operational at the unit, if the control equipment was not part of the original installation. If the equipment was part of the original installation, leave this field blank.

Seasonal Controls Indicator

Element Name: SeasonalControlsIndicator

Report a "1" in the Seasonal Control Indicator field for NO

x 

### Budget Program units if the NO

x 

### control equipment is used only during the ozone season. If not, report "0" ( zero ).

Retire Date

Element Name: RetireDate

Report the date on which the control equipment was removed or retired from the unit. This value

sh ould be left blank if the control equipment is still in use

.

Monitoring Plan Reporting Instructions

-- Page 24 Environmental Protection Agency4.3 Unit Fuel Data



## 4 .3 U NIT 

## F UEL 

## D ATA March 07, 2012September 19, 2012



### Figure 10

U NIT 

### F UEL 

### D ATA 

### XML Elements

Description of Data

For each unit identified in the U NIT 

### D ATA 

### record of the monitoring plan, submit a U NIT 

### F UEL


### D ATA 

### record for each type of fuel combusted by the unit. The U NIT 

### F UEL 

### D ATA 

### record is used to indicate the primary, secondary, emergency, and startup fuels combusted by each unit, to report changes in the types of fuels combusted and to indicate when such changes occurred.

Dependencies for U NIT 

### F UEL 

### D ATA



### The U NIT 

### F UEL 

### D ATA 

### record is dependent on the U NIT 

### D ATA 

### record.

No other records are dependent upon the U NIT 

### F UEL 

### D ATA 

### record

.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 25March 07, 2012 September 19, 2012 4.3 Unit Fuel Data



### U NIT 

### F UEL 

### D ATA 

### Elements

Instructions for completing each element of the U NIT 

### F UEL 

### D ATA 

### section are provided below:

Fuel Code

Element Name: FuelCode

Report one of the following uppercase codes to indicate the types of fuel combust ed by a unit as

shown in Table 4:

Table 4

Unit Fuel Codes and Descriptions

Code Description

C Coal

CRF Coal Refuse (culm or gob)

DSL Diesel Oil *

LPG Liquefied Petroleum Gas

NNG Natural Gas

OGS Other G as

OIL Residual Oil

OOL Other Oil

OSF Other Solid Fuel

PNG Pipeline N atural Gas (as defined in § 72.2)

PRG Process Gas

PRS Process Sludge

PTC Petroleum Coke

R Refuse

TDF Tire Derived Fuel

W Wood

WL Waste Liquid

* Diesel oil is defined in § 72.2 as low sulfur fuel oil of grades 1

- D or 2

- D, as defined by ASTM D

- 975

- 91,

grades 1

- GT or 2- GT, as defined by ASTM D2880

- 90a, or grades 1 or 2, as defined by ASTM D396

- 90. By those definitions (specifically ASTM D396

- 90 ) and for the purposes of this p rogram, kerosene and

ultra

- low sulfur diesel fuel (ULSD) are considered subset s of diesel oil and therefore should be identified with the code DSL. If a fuel does not qualify as one of these types, do not report the code DSL.

Monitoring Plan Reporting Instructions

-- Page 26 Environmental Protection Agency4.3 Unit Fuel Data March 07, 2012 September 19, 2012



### Indicator Code

Element Name: IndicatorCode

Report whether the fuel type listed is th e primary fuel (as defined in §72.2), a backup (secondary) fuel, a startup fuel, or an emergency fuel for this unit by using one of the uppe rcase codes shown in Table 5:

Table 5

Unit Fuel Indicator Codes and Descriptions

Code Description

E Emergency

I Ignition (s tartup)

P Primary

S Backup (s econdary)



### Ozone Season Indicator

Element Name: OzoneSeasonIndicator

Report "1" in the Ozone Season Indicator for the secondary fuel(s) record(s) if fuel switching (to a secondary fuel or fuels) is used for seasonal control of ozone. If not, report "0" ( zero ).

Demonstration Method to Qualify for Monthly Fuel Sampling for GCV

Element Name: DemGCV

If applicable, report the method used to demonstrate that a unit using Appendix D qualifies for monthly GCV fuel sampling (see Section 2.3.5 of Appendix D) by using one of the following

uppe rcase codes as shown in Table 6:

Table 6 Demonstration Method to Qualify for Mont hly Fuel Sampling for GCV Codes and Descriptions

Code Description

GHS 720 Hours of Data Using Hourly Sampling

GGC 720 Hours of Data Using an On line Gas Chromatograph

GOC 720 Hours of Data Using an On line

Calorimeter

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 27March 07, 2012 September 19, 2012 4.3 Unit Fuel Data



### Demonstration Method to Qualify for Daily or Annual Fuel Sampling for %S (ARP)

Element Name: DemSO2

If applicable, report the method used to demonstrate that an Acid Rain unit using Appendix D qualifies for daily or annual percent sulfur sampling (see Section 2.3.6 of Appendix D) using one of the upp ercase codes shown in Table 7 :

Table 7 Demonstration Method to Qualify for Daily or Annual Fuel Sampling for %S (ARP) Codes and Descriptions

Code Description

SHS 720 Hours of Data Using Manual Hourly Sampling

SGC 720 H ours of Data Using On line Gas Chromatograph



### Begin Date
Element Name: Begin Date

Report the first date on which the unit combusted this fuel type (or the best available estimate if

the exact date is not known). The fuel type Begin Date must precede or coincide with the date of any monitoring system certifications while combusting the fuel.

End Date
Element Name: EndDate

Report the last date on which a given fuel type was combusted at the unit if the combustion of this fuel type has been permanently discontinued at this unit. This value should be left blank for fuels that are still being used

.

Monitoring Plan Reporting Instructions

-- Page 28 Environmental Protection Agency5.0 Monitoring Location Attribute Data March 07, 2012 September 19, 2012



## 5 .0 M ONITORING 

## L OCATION 

## A TTRIB UTE 

## D ATA



### Figure 11

M ONITORING 

### L OCATION 

### A TTRIBUTE 

### D ATA 

### XML Elements

Description of Data

The M ONITORING 

### L OCATION 

### A TTRIBUTE 

### D ATA 

### record provides a description of the physical characteristics of a specified monitoring location. Submit a M ONITORING 

### L OCATION 

### A TTRIBUTE


### D ATA 

### record for each multiple or common stack defined in a monitoring plan . Also report a

M ONITORING 

### L OCATION 

### A TTRIBUTE 

### D ATA 

### record for each unit in the monitoring plan if

emissions are monitored or determined there. Do not report this record for pipes.

For multiple stack ( MS) configurations, if the monitors are located on the stacks, report the height, elevation and inside cross- sectional area ( CSA ) information for each stack (i.e., stack exit CSA and, if applicable, the CSA at the flow monitor location). If the monitors a re located at breechings or ducts rather than on the stack, in the M ONITORING 

### L OCATION 

### A TTRIBUTE 

### record for each multiple stack report the stack exit height, base elevation and inside CSA information for the exhaust stack, and report the CSA at the stack e xit and, if applicable, the inside CSA at the

flow monitor location in the ductwork.

For units that are part of a common pipe (CP) or multiple (MP) configuration and use Appendix D estimation procedures for heat input, CO 2 

### , or SO 2 

### , report (using the appropriate Unit ID or Stack ID) the stack height, elevation and inside cross- sectional area of the stack through which emissions are discharged to the atmosphere. This can be a single unit stack or a stack serving more than one unit. If the unit emits through more than one stack, report information for the stack typically associated with higher emissions for the unit.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 29Marc h 07, 2012 September 19, 2012 5.0 Monitoring Location Attribute Data



### Dependencies for M ONITORING 

### L OCATION 

### A TTRIBUTE 

### D ATA



### The M ONITORING 

### L OCATION 

### A TTRIBUTE 

### D ATA 

### record is dependent on the U NIT 

### D AT A 

### record or

the S TACK 

### P IPE 

### D ATA 

### record.

No other records are dependent upon the M ONITORING 

### L OCATION 

### A TTRIBUTE 

### D ATA 

### record.

M ONITORING 

### L OCATION 

### A TTRIB UTE 

### D ATA 

### Elements

Instructions for completing each element of the M ONITORING 

### L OCATION 

### A TTRIBUTE 

### D ATA 

### section are provided below:

Duct Indicator

Element Name: DuctIndicator

Report a "1" or a "0" indicating whether the monitoring locati on is a duct, with "1" meaning yes

and "0" meaning no.

Bypass Indicator

Element Name: BypassIndicator

Report a "1" or a "0" indicating whether the monitoring location is a bypass stack

, with "1" meaning yes and "0" meaning no.

Ground Elevation

Element Name: GroundElevation

Report the elevation of the ground level, in feet above sea level

, at the base of a stack or u nit.

Stack Height

Element Name: StackHeight

Report the height of the stack exit, in feet above ground level.

Monitoring Plan Reporting Instructions

-- Page 30 Environmental Protection Agency5.0 Monitoring Location Attribute Data March 07, 2012 September 19, 2012



### Material Code

Element Name: MaterialCode

If applicable (i.e., there is a stack flow monitor at this location), r eport a code from Table 8 that most accurately describes the material from which the inner wall of the duct or stack is

constructed at the flow monitoring location:

Table 8

Duct/Stack Material Codes and Description

Code Description

BRICK Brick and mortar

OTHER Any material other than brick and

mortar



### Shape Code

Element Name: ShapeCode

If applicable (i.e., there is a stack flow monitor at this location), r eport a code from Table 9 that most accurately describes the shape of a duct or stack at the flow monitoring location:

Table 9

Duct/Stack Shape Codes and Descriptions

Code Description

RECT Rectangular

ROUND Round



### Cross Area Flow

Element Name: CrossAreaFlow

If applicable (i.e., there is a stack flow monitor at this location), report the inside cross- sectional area, in square feet, of the stack at the flow monitoring location.

Cross Area Stack Exit

Element Name: CrossAreaStackExit

Report the inside cross- sectional area, in square feet, of the stack at the flue exit.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 31Marc h 07, 2012 September 19, 2012 5.0 Monitoring Location Attribute Data



### Begin Date
Element Name: Begin Date

Report the date on which these physical characteristics first applied to the location. If this is the first or only M ONITORING 

### L OCATION 

### A TTRIBUTE 

### D ATA 

### record f or the location, this date should equal the Active Date in the S TACK 

### P IPE 

### D ATA 

### record (for common or multiple stacks), or the date that a unit first became subject to any applicable program (for units). If this is an updated

M ONITORING 

### L OCATION 

### A TTRIBUTE 

### D ATA 

### record showing a change in one or more attribute

value (s) , this date should be the date on which the change took place.

End Date
Element Name: EndDate

Report the last date on which these physical characteristics applied to the location. This value

should be left blank for active attribute information

.

Monitoring Plan Reporting Instructions

-- Page 32 Environmental Protection Agency6.0 Monitoring Method Data March 07, 2012 September 19, 2012



## 6 .0 M ONITORING 

## M ETHOD 

## D ATA



### Figure 1 2

M ONITORING 

### M ETHOD 

### D ATA 

### XML Elements

Description of Data

The M ONITORING 

### M ETHOD 

### D ATA 

### record describes the emissions monitoring methodologies used

at each monitoring location identified in the monitoring plan. A separate M ONITORING 

### M ETHOD


### D ATA 

### record must be inclu ded for each parameter ( NOX, SO2, CO2, etc.) monitored or

calculated at each identified monit oring location. Note that when heat input is not monitored at the unit level, a M ONITORING 

### M ETHOD 

### D ATA 

### record for heat input must be included for both the monitoring location and at the unit level.

For example, if all emissions are monitored at a common stack for Units 1 and 2, report one set of monitor method records for the common stack location, which includes a single record for each parameter monitored, and (if heat input monitoring is required) two additional records (i.e., one each for Units 1 and 2) indicating the method by which heat input is determined at the unit

level.

Report only one active method for each parameter monitored at the location. For locations with an unmonitored bypass stack, use the Bypass Approach Code field in the applicable method record(s) to report whether or not a fuel- specific default value will be used for bypass hours. For information on particular usages of this record for moisture , heat input, ARP units, NBP units,

LME units and Alternative Monitoring System (AMS)

, refer to " Specific Considerations " below.

Also, for information on how to update this record, refer to the " Updating the M ONITORING


### M ETHOD 

### D ATA 

### Record " sec tion below.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 33March 07, 2012 September 19, 2012 6.0 M onitoring Method Data



### Dependencies for M ONITORING 

### M ETHOD 

### D ATA



### The M ONITORING 

### M ETHOD 

### D ATA 

### record is dependent on the U NIT 

### D ATA 

### record or the S TACK


### P IPE 

### D ATA 

### record.

No other records are dependent upon the M ONITORING 

### M ETHOD 

### D ATA 

### record.

M ONITORING 

### M ETHOD 

### D ATA 

### Elements

Instructions for completing each element of the M ONITORING 

### M ETHOD 

### D ATA 

### section are provided below:

Parameter Code

Element Name: ParameterCode

Report the appropriate Parameter Code as shown in Table 10:

Table 10 Parameter Codes and Descriptions for Monitoring Methods

Code Description (Units)

CO2 CO 2 Mass Emissions Rate (tons/hr)

CO2M CO 2 Mass Emissions (tons)

H2O Moisture (% H 2 O)

HI Heat Input Rate (mmBtu/hr)

HIT Heat Input Total (mmBtu) (LME o nly)

NOX NO

x Mass Emissions Rate ( lb/hr)

NOXM NO

x Mass Emissions (lb) (LME only)

NOXR NO

x Emissions Rate (lb/mmBtu)

OP Opacity (percent )

SO2 SO 2 Mass Emissions Rate (lb/hr)

SO2M SO 2 Mass Emissions (lb) (LME only)

Monitoring Plan Reporting Instructions

-- Page 34 Environmental Protection Agency6.0 Monitoring Method Data March 07, 2012 September 19, 2012



### Monitoring Method Code

Element Name: MonitoringMethodCode

Report the Monitoring Method Code that identifies the methodology employed to monitor the specified parameters at the specified monitoring location. Report the appropriate uppercase code

as shown in Table 11:

Table 11 Measured Parameters and Applicable Monitoring Methods

Parameter Method Code Description

CO2 AD Appendix D Gas and/or Oil Flow System(s) (Formula G

- 4)

AMS Alternative Monitoring System *

CEM CO 2 Continuous Emission Monitor

CO2M FSA Fuel Sampling and Analysis (Formula G

- 1)

LME Low Mass Emissions (§75.19)

H2O MMS Continuous Moisture Sensor

MDF Moisture Default

MTB Moisture Lookup Table

MWD H 2 O System with Wet and Dry O 2 Analyzers

HI AD Appendix D Gas and/or Oil Flow System(s)

ADCALC Appendix D Gas and/or Oil Flow System at location (unit) and different Oil or Gas Measured at Common Pipe. (Heat Input at the unit is determined by adding the appropriate value apportioned from th e Common Pipe to the unit value )

AMS Alternative Monitoring System *

CALC Calculated from Values Measured at O ther Locations

. (U sed for three situations: (1) t his is the method at a unit when heat input is determined at a common stack or common pipe and then appor tioned to the constituent units; or (2) t his

is the method at a unit when heat input is determined at multiple sta cks and then summed to the unit; or (3) t his is the method at a common stack if heat input is determined at the

units and then summed to the common stack in order to

calculate NO

x mass )

CEM Flow and O 2 or CO 2 Continuous Emission Monitors

EXP Exempt from Heat Input monitoring

HIT LTFF Long

- Term Fuel Flow (Low Mass Emissions

- - §75.19)

(cont.)

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 35March 07, 2012 September 19, 2012 6.0 M onitoring Method Data



### Table 11 Measured Parameters and Applicable Monitoring Methods (cont.)

Parameter Method Code Description

HIT (cont.) LTFCALC Long

- Term Fuel Flow (Low Mass Emissions

- - §75.19) at the unit and different Long Term Fuel Flow at the common pipe. (Heat Input at the unit is determined by adding the appropriate value apportioned from th e Common Pipe to the unit val ue )

MHHI Maximum Rated Hourly Heat Input (Low Mass Emissions)

CALC Calculated from v alues m easured at the common pipe

. (T his is the method at a unit when heat input is determined at a common pipe and apportioned to the constituent units)

NOX AMS Alternative Monitoring System *

CEM NO

x Concentration times Stack Flow rate

CEMNOXR NO

x Concentration times Stack Flow rate and NO

x Emission Rate times Heat Input Rate (one as a primary method and the other as secondary)

. This method is not permitted after December 31, 2007

NOXR NO

x Emission Rate times Heat Input Rate

NOXM LME Low Mass Emissions (§75.19)

NOXR AMS Alternative Monitoring System *

AE Appendix E

CEM NO

x Emission Rate CEMS

PEM Predictive Emissions Monitoring System (as approved by petition)

OP COM Continuous Opacity or Particulate Matter Monitor

EXP Exempted

SO2 AD Appendix D Gas and/or Oil Flow System(s)

AMS Alternative Monitoring System *

CEM SO 2 Continuous Emission Monitor

CEMF23 SO 2 Continuous Emission Monitor, and Use of F

- 23 Equation during hours when only very low sulfur fuel is burned per § § 75.11(e) and 75.11(e)(4)

F23 Use of F

- 23 Equation if only very low sulfur fuel is burned

per § § 75.11(e) and 75.11(e)(4)

SO2M LME Low Mass Emissions (§75.19)

* Use of this method requires EPA approval

Monitoring Plan Reporting Instructions

-- Page 36 Environmental Protection Agency6.0 Monitoring Method Data March 07, 2012 September 19, 2012



### Substitute Data Code

Element Name: SubstituteDataCode

Report the Substitute Data Code that designates the methodology used to determine substitute values during periods of missing data. L eave this field blank when NOX Mass is calculated from NOX Rate and HI (Method Code NOXR and Parameter Code NOX). Also, l eave this field blank for parameter code OP and all LME methods, with the following exception. When using long- term fuel flow as the heat input methodology for an LME unit, report a Substitute Data Code of MHHI only if it will ever be necessary to report the unit' s maximum rated hourly heat input rate as the heat input rate for any hour. This may be necessary for either of two reasons: (1) for any hour when burning a secondary fuel that is not measured by a long- term fuel flow system, or (2) if a unit operated for only a very short period or used only a very limited amount of fuel during a quarter or reporting period, so that a tank dr op measurement will not yield an accurate estimate of the fuel combusted during the reporting period. Report the appropriate

up percase code as shown in Table 12:

Table 12 Substitute Data Codes and Descriptions

Code Description Appropriate For Parameter Code s

SPTS Standard Part 75 NOXR, NOX, SO2, CO2, H2O

, and HI

FSP75 Fuel

- Specific Part 75 NOXR, NOX, SO2, CO2, H2O

, and HI

FSP75C Fuel

- Sp ecific Part 75 with separate

co

- fired d atabase NOXR, NOX, SO2, CO2, H2O

, and HI

OZN75 Ozone vs. Non

- Ozone Sea son NOX , NOXR

NLB Non

- Load Based NOXR, NOX, and HI

NLBOP Non

- Load Based with Operational

Bins NOXR, NOX, and HI

REV75 Reverse of Standard Part 75 H2O

MHHI Maximum Rated Hourly Heat Input Rate for LME Units u sing Long Term Fuel Flow

m ethodology HIT

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 37March 07, 2012 September 19, 2012 6.0 M onitoring Method Data



### Bypass Approach Code

Element Name: BypassApproachCode

Report the Bypass Approach Code used to calculate emissions for an unmonitored bypass stack whose method of determining emissions is based on a default value. The Bypass Approach Code

is not required if a bypass stack is di rectly monitored or valid data are calculated from monitors at other locations (e.g., at a control device inlet). This code is only applicable for parameters SO2, NOX

, and NOXR with CEM, CEMF23, and NOXR method codes. Report the appropriate

uppe rcase codes as shown in Table 13 :

Table 13 Bypass Approach Codes and Descriptions

Code Description

BYMAX MPC or MER * for Highest Emitting

Fuel

BYMAXFS Fuel

- Specific MPC or MER *



### * Note that MEC or MCR may be used for documented controlled hours.



### Begin Date
Element Name: Begin Date

Report the date on which the methodology was first used to determine emissions or heat input rate for the monitoring location. For opacity, report the same starting date as for emission reporting, whether the applicable units are exempted from opacity monitoring or not.

For new units, report the first date on which the methodology is expected to be used to determine

emissions or heat input rate. Correct as needed when the actual begin date is known.

Begin Hour
Element Name: Begin Hour

Report the hour in which the methodology was first used to determine emissions or heat input rate for the monitoring location.

End Date
Element Name: EndDate

Report the date on which the methodology was last used to determine emissions or heat input rate for the monitoring location. This value should be left blank for active records.

Monitoring Plan Reporting Instructions

-- Page 38 Environmental Protection Agency6.0 Monitoring Method Data March 07, 2012 September 19, 2012



### End Hour
Element Name: EndHour

Report the hour in which the methodology was last used to determine emissions or heat input rate for the monitoring location . This value should be left blank for active records.

Specific Considerations

Moisture

● If required to correct for moisture (H 2 

### O) when calculating emissions or heat input at a monitoring location, report a separate monitor method record for the H2O parameter. Do this for each location at which moisture is needed, defining the methodology used to determine hourly moisture for emissions calculations.

Heat Input

● If heat input monitoring is required, there must be a separate monitor method record for heat input (HI) data for each unit, even if the monitor location is not at the unit level. For example, if SO 2 

### , CO 2 

### , NO

x 

### , and Flow monitors are installed at CS001, which serves Unit 1, 2, and 3, there will be a full set of monitor method records for CS001 and only one

monitor method record for HI at each unit. The unit records for monitor method should indicate that the heat input is calculated for the unit, using the " CALC " monitoring

method code.

Acid Rain Program Units

● If a location which has an SO 2 

### monitor combusts both high sulfur fuel (e.g., coal or oil)

and a low sulfur fuel , and uses a default SO 2 

### emission rate in con junction with Equation

F-23 for hours in which very low sulfur fuel is combusted (see § 75.11(e)(1)), report one monitor method record for parameter SO2 with a monitoring methodology code CEMF23. If only low-sulfur fuel is combusted and the F- 23 calculatio n is used for every hour, report the SO 2 

### monitoring method as F23.

● If a unit or stack is exempt from opacity monitoring, report a monitor method record for

the unit or stack defining the parameter OP with a monitor method code of EXP.

● If opacity is monitored at a common stack or multiple stacks, but no other parameters are monitored at that location, do not define the stack(s). Instead, report the opacity method and system data at the unit level.

● If a unit is also subject to Subpart H, be sure to include the appropriate method record(s) indicating how NO

x 

### mass is determined.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 39March 07, 2012 September 19, 2012 6.0 M onitoring Method Data



### NO

x 

### Budget Program Units

● Report a monitor methodology record for parameter NOX at each applicable location.

● Report the method code as NOXR if NO

x 

### mass emissions are calculated by determining

NO

x 

### emission rate and heat input rate. Report method code CEM if NO

x 

### mass is calculated as the product of NO

x 

### concentration and stack gas flow rate.

● If applicable, report methodol ogy records for NO

x 

### emission rate and/or heat input.

Low Mass Emissions (LME) Units

For all LME units as under the methodology in §75.19:

● For Acid Rain Program LME units: Submit separate monitor methodology records for parameters SO2 M , NOX M , CO2 M, HI T , and , if applicable OP.

● For Non- Acid Rain

, NO

x 

### Budget Program LME Units: Submit monitor method records to describe the methodologies for both NO

x 

### mass (NOX M) and heat input (HIT ).

Part 75 Alternative Monitoring System (AMS)

● The use of method code AMS for determining average hourly emissions for parameters CO2, HI, NOX, NOXR, or SO2 is granted through petition based on meeting the requirements of Subpart E of Part 75.

Updating the M ONITORING 

### M ETHOD 

### D ATA 

### Record

When changing monitoring methodologies for a parameter, report both the old and new

M ONITOR ING 

### M ETHOD 

### D ATA 

### records. First, close out the existing monitoring methodology record by entering the date and hour that the methodology was discontinued (EndDate, EndHour). Seco nd, create a new monitoring method record for that parameter indicating the date and hour during which use of the replacement methodology began ( Begin Date, Begin Hour). For the new method, leave the values for End Date and End Hour blank.

In order to correct a previously submitted record that contains erroneous information, re submit

that M ONITORING 

### M ETHOD 

### D ATA 

### record with the corrected information. For example, if the SO 2 

### Monitoring Method Code was previously submitted as " CEM " and the correct code shoul d have

been "CEMF23," the record should be updated and resubmitted. Note that the Begin Date and Begin Hour elements should not be updated, unless the Begin Date and/or Begin Hour are the

elements to be corrected.

Monitoring Plan Reporting Instructions

-- Page 40 Environmental Protection Agency7.0 Component Data



## 7 .0 C OMPONENT 

## D ATA March 07, 2012September 19, 2012



### Figure 13

C OMPONENT 

### D ATA 

### XML Elements

Description of Data

The C OMPONENT 

### D ATA 

### record describes each of the components used to make up the monitoring

system s defined in the monitoring plan . A component can be either a hardware component, such

as a NO

x 

### analyzer, or a software component , such as a DAHS. Under most circumstances, o nly

one C OMPONENT 

### D ATA 

### record is required for components that are shared by multi ple monitoring systems defined at that location. For example, an O 2 

### monitor that is used in both the NO

x 

### emissions rate system and the moisture monitoring system needs only to be identified in one

C OMPONENT 

### D ATA 

### record . The exception exists for a combined cycle combustion unit using a

" time

- share " CEMS configuration to monitor emissions from both the main and bypass stacks.

Please refer to " Specific Considerations " below for more information.

Information describing the monitoring system of which the component is a part is not needed for this record. The relationship between component s and monitoring s ystem s is de fined by the

M ONITORING 

### S YSTEM 

### C OMPONENT 

### D ATA 

### record.

For information on defining DAHS components, how to report fuel flowmeter data when using

flowmeter rotation, and how to represent manufacturer and serial number information, refer to "Specific Considerations" below.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 41March 07, 2012 September 19, 2012 7.0 Component Data



### Dependencies for C OMPONENT 

### D ATA



### The C OMPONENT 

### D ATA 

### record is dependent on the U NIT 

### D ATA 

### record or the S TACK 

### P IPE 

### D ATA


### record.

The following records are dependent upon the C OMPONENT 

### D ATA 

### record:

● A NALYZER 

### R ANGE 

### D ATA



### ● M ONITORING 

### S YSTEM 

### C OMPONENT 

### D ATA



### C OMPONENT 

### D ATA 

### Elements

Instructions for completing each element of the C OMPONENT 

### D ATA 

### se ction are provided below:

Component ID

Element Name: ComponentID

Report the three-character ID assigned to the component. This ID is assigned by a source and must be unique to a stack, pipe, or unit. For example, two different monitored units or stacks, e.g., CS1 and CS2, could each have an O 2 

### monitor with the same assigned Component ID of 123. However, no two components at the same monitored location (in this case, either CS1 or CS2)

are allowed to have the same Component ID. For temporary like

- kind analyzer replacements under §75.20(d), the component ID of the like-kind analyzer must begin with the prefix " LK " (e.g., " LK1, " " LK2, " etc.).

Note that components are linked to each system that the component serves using the

M ONITORING 

### S YSTEM 

### C OMPONENT 

### record. The M ONITORING 

### S YSTEM 

### C OMPONENT 

### record

includes a begin date and hour to track when a particular component is placed into service as part of the system, and an end date and hour to indicate when the component is removed or is replaced.

Do not close out primary monitoring components that are temporarily removed from service for

maintenance , e.g., when a like-kind monitoring component is placed into service while the primary component is being repaired.

Also, do not close out temporary like- kind replacement analyzer ( " LK ") components unless a particular like -kind analyzer will never be used again at the unit or stack location. You may represent the " LK " analyzer in the monitoring plan as an active component of the primary monitoring system, for the entire useful life of the LK analyzer.

Monitoring Plan Reporting Instructions

-- Page 42 Environmental Protection Agency7.0 Component Data March 07, 2012 September 19, 2012



### Component Type Code

Element Name: ComponentTypeCode

Report the code indicating the function of the component. The code does not necessarily correspond to the function of the monitoring system as a whole in which a component is included. Report the Component Type Code by using the appropriate up percase code as shown

in Table 14:

Table 14 Component Type Codes and Descriptions

Code Description

BGFF Billing Gas Fuel Flowmeter

BOFF Billing Oil Fuel Flowmeter

CALR Calorimeter

CO2 Carbon Dioxide Concentration Analyzer

DAHS Data Acquisition and Handling System

DL Data Logger or Recorder

DP Differential Pressure

Transmitter/ Transducer

FLC Flow Computer

FLOW Stack Flow Monitor

GCH Gas Chromatograph

GFFM Gas Fuel Flowmeter

H2O Percent Moisture (Continuous Moisture System only)

NOX Nitrogen Oxide Concentration Analyzer

O2 Oxygen Concentration Analyzer

OFFM Oil Fuel Flowmeter

OP Opacity Measurement

PLC Programmable Logic Controller

PM Particulate Matter Measurement

PRB Probe

(cont.)

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 43March 07, 2012 September 19, 2012 7.0 Component Data



### Table 14 Component Type Codes and Descriptions (cont.)

Code Description

PRES Pressure Transmitter/Transducer

SO2 Sulfur Dioxide Concentration Analyzer

TANK Oil Supply Tank

TEMP Temperature Transmitter/Transducer



### Sample Acquisition Method Code

Element Name: SampleAcquisitionMethodCode

Report the appropriate concentration/diluent codes, operational principle (volumetric flow codes), or type of fuel flowmeter (fuel flowmeter type codes)

. Leave this field blank if a sample acquisition method is not applicable to the component type (e.g., for a DAHS component). For LME long

- term fuel flow components, leave this field blank unless using a certified fuel

flowmet er to quantify heat input. Report the Sample Acquisition Method Code by using the appropriate upp ercase codes as shown in Table 15 :

Table 15 Sample Acquisition Method Codes for Components

Component Code Description

For CEMS DIL Dilution

DIN Dilution In

- Stack

DOD Dry Out

- of

- Stack Dilution

DOU Dilution Out

- of

- Stack

EXT Dry Extractive

IS In Situ

ISP Point/Path in Situ

ISC Cross Stack in Situ

O Other

WXT Wet Extractive

(cont.)

Monitoring Plan Reporting Instructions

-- Page 44 Environmental Protection Agency7.0 Component Data March 07, 2012 September 19, 2012



### Table 15 Sample Acquisition Method Codes (cont.)

Component Code Description

For Volumetric Stack Flow Monitor DP Differential Pressure

O Other

T Thermal

U Ultrasonic

For Fuel Flowmeter Types COR Coriolis

DP Differential Pressure (e.g., Annubar)

NOZ Nozzle

O Other

ORF Orifice

PDP Positive Displacement

T Thermal Mass Flowmeter

TUR Turbine

U Ultrasonic

VCON V

- Cone

VEN Venturi

VTX Vortex

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 45March 07, 2012 September 19, 2012 7.0 Component Data



### Basis Code

Element Name: BasisCode

For CEM analyzer components, report a code indicating whether the applicable components sample on a wet or dry basis or use both wet and dry methods. Use the appropriate uppe rcase codes as shown in Table 16:

Table 16

Basis Codes and Descriptions for CEM Analyzer Components

Code Description

W Wet

D Dry

B Both wet and dry (O 2 only)

* For sample acquisition method (SAM) codes IS, ISP, ISC, DIN, DOU, DIL, and WXT = wet extractive ;

EXT = dry extr active, located under Component . Exceptions are possible. For all stack flow monitors

-­ wet basis. Check with vendor if uncertain.



### Manufacturer

Element Name: Manufacturer

Report the name or commonly used acronym for the manufacturer or developer of the component. Do not use this field to identify the unit or location of the component. For LME long-term fuel flow components, leave this field blank unless using a certified fuel flowmeter to quantify heat input.

Model Version

Element Name: ModelVersion

Report the manufacturer designated model name or number of any hardware component or the version number of a software component. For LME units using long- term fuel flow, leave this field blank unless using a certified fuel flowmeter to quantify heat input.

Serial Number

Element Name: SerialNumber

Report the serial number for each component. For hardware or analytical components, the serial number should be unique and should allow identification of the instrument or device in the field. For flow monitors, provide a single component serial number that represents the control unit of

the monitor. Leave this field blank for LME long

- term fuel flow components, unless using a certified fuel flowmeter to quantify heat input.

Monitoring Plan Reporting Instructions

-- Page 46 Environmental Protection Agency7.0 Component Data March 07, 2012 September 19, 2012



### Specific Considerations

Essential DAHS Components (Software and Hardware)

● Identify the software component(s) of the Data Acquisition and Handling System (DAHS) as individual components. Any software program that calculates emissions or

heat input rate, or implements missing data substitution algorithms or quarterly reporting

fu nctions should be defined as a component. Identify the programmable logic controller (PLC) or automated data logger (DL) as a system component if it performs any of those

functions.

Non

- Essential Software or Hardware Components

● Software or hardware c omponents that perform the following functions do not have to be identified as part of the DAHS and therefore do not need component definitions 1 

### :

-- Calculation of RATA results;

-- Calculation of flow- to

- load results (that are merged with t he final quart erly report); or

-- Record ing of operating parameters (that are merged with the final quarterly report)

, e.g., unit load.

Rotating Fuel Flowmeters

When fuel flowmeters are rotated among different units to facilitate the removal of meters for accuracy testing (e.g., three fuel flowmeters rotated between two units), submit a new

MONITORING SYSTEM COMPONENT DAT A 

### record each time that a fuel flowmeter is being placed into service, and update the end date and hour of the MONITORING SYSTEM CO MPONENT DATA


### record for the fuel fl owmeter that is being removed. Use the reinstallation date and hour in the

FUEL FLOWMETER ACCURACY D ATA 

### record as the begin date and hour in the new MON ITORING

SYSTEM COMPONENT DAT A 

### record, and use the hour prior to the reinstallation date and hour as the

end date and hour in the MONITORING SYSTEM CO MPONENT DATA 

### record for the fuel flowmeter that is being removed. If the fuel flowmeter that is being plac ed into service had previously been installed, you may report its previously assigned component ID in the MONITORING SYSTEM

COMPONENT DATA 

### record or you may assign a new component ID.

The rotation of dilution probes should be reported in the same manner a s fuel flowmeters.

1 While these components do not have to be identified in the monitoring plan, identify them in the data flow

diagram under § 75.53(c)(5)(iii) and/or the quality assurance plan under Appendix B to Part 75.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 47March 07, 2012 September 19, 2012 7.0 Component Data



### Manufacturer and Serial Number Data for DAHS Components

● Use an abbreviation that clearly identifies the utility or operating company responsible for the software development if softw are has been developed in -house. Use the same

abb reviation or name in the Manufacturer field for all units and sources using the

software.

● Serial numbers are optional for DAHS software components and billing fuel flowmeters. If choosing to assign one, it must be unique to the software installation.

Time -S hare CEMS on Single Unit

When using a " time

- share " CEMS configuration to monitor emissions from both the main stack and bypass stack for a combined cycle combustion unit using a single monitoring location, define separate systems with unique Monitoring System IDs for each effluent point, and define

separa te component records with unique Component IDs for each system. Defining separate components for each system will allow for the tracking of component specific tests (e.g., linearity, seven day cal, online offline cal, and cycle time) where the test cannot be otherwise uniquely identified. (This is a distinct change from the previous EDR format, where it was acceptable to include the same component in both systems, since the Monitoring System ID used to be included in the test record.) If the same component was previously reported in both systems, EPA recommends that affected units define new component records only for the system that represents the monitoring of the bypass stack, so as to minimize the amount of data that

would need to be resubmitted. The most recent component specific QA test data (previously submitted under the old format) will need to be resubmitted under the new Component IDs.

Monitoring Plan Reporting Instructions

-- Page 48 Environmental Protection Agency7.1 Analyzer Range Data March 07, 2012 September 19, 2012



## 7 .1 A NALYZER 

## R ANGE 

## D ATA



### Figure 14

A NALYZER 

### R ANGE 

### D ATA 

### XML Elements

Description of Data

Submit an A NALYZER 

### R ANGE 

### D ATA 

### record for each gas analyzer component (NO

x 

### , SO 2 

### , CO 2 

### , and O 2 

### ) identified in a C OMPONENT 

### D ATA 

### record of the monitoring plan . This record specifies for each component whether that component is a high scale, low scale , or autoranging component, and whether it is a dual range analyzer

.

Dependencies for A NALYZER 

### R ANGE 

### D ATA



### The A NALYZER 

### R ANGE 

### D ATA 

### record is dependent on the C OMPONENT 

### D ATA 

### record.

No other records are dependent upon the A NALYZER 

### R ANGE 

### D ATA 

### record

.

A NALYZER 

### R ANGE 

### D ATA 

### Elements

Instructions for completing each element of the A NALYZER 

### R ANGE 

### D ATA 

### section are provided

below:

Analyzer Range Code

Element Name: AnalyzerRangeCode

Report the code specifying the range by using the appropriate upp ercase code as shown in Table

17. If using a default high range value for SO 2 

### or NO

x 

### , the correct range code for the analyzer is

L.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 49March 07, 2012 September 19, 2012 7.1 Analyzer Range Data



### Table 17 Analyzer Range Codes and Descriptions

Code Description

H High Range

L Low Range

A Auto Ranging



### Dual Range Indicator

Element Name: DualRangeIndicator

Report a Dual Range Indicator code equal to "1" whenever a single analyzer is used to satisfy a dual range monitoring requirement . There are two possible ways to represent this in the component data:

● As two separate components in the monitoring plan (i.e., when the Analyzer Range Code is reported as "H" for the analyzer under one component ID and as "L" for the same analyzer under another unique component ID); or

● As a single auto -ranging component in the monitoring plan (i.e., Analyzer Range Code equal to "A" ).

Note that reporting dual range analyzers as a single auto -ranging component is recommended.

If more than one analyzer is used to satisfy a dual range monitoring requirement (i.e., when two separate analyzers are used, one for the low -range and another for the high- range), report each analyzer component separately in the monitoring plan and report "0" as the Dual Range

Indicator.

Also report "0" if the compon ent represents a single range analyzer that is not part of a dual range monitoring configuration.

Begin Date
Element Name: Begin Date

Report the date on which the range information reported in this record became effective. In most cases, this date will be the same as the earliest begin date in the MONITOR SYSTEM COMPO NENT

D ATA 

### record. However, if the analyzer range changes (e.g., from a single scale to dual range), be sure to put the proper End Date and End Hour in the existing A NALYZER R ANGE DATA 

### record and

enter another ANALYZER RANGE DATA 

### record for the new range code using the appropriate Begin

Date and Hour.

Begin Hour
Element Name: Begin Hour

Report the hour during which the range information reported in this record became effective.

Monitoring Plan Reporting Instructions

-- Page 50 Environmental Protection Agency7.1 Analyzer Range Data March 07, 2012 September 19, 2012



### End Da te
Element Name: EndDate

Report the last date on which the range information reported in this record was effective

. This

value should be left blank for active records.

End Hour
Element Name: EndHour

Report the last hour in which the range information reported in this record was effective

. This

value should be left blank for active records.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 51March 07, 2012 September 19, 2012 7.1 Analyzer Range Data



### [This page intentionally left blank.]

Monitoring Plan Reporting Instructions

-- Page 52 Environmental Protection Agency8.0 Monitoring System Data March 07, 2012 September 19, 2012



## 8 .0 M ONITORING 

## S YSTEM 

## D ATA



### Figure 15

M ONITORING 

### S YSTEM 

### D ATA 

### XML Elements

Description of Data

Submit a M ONITORING 

### S YSTEM 

### D ATA 

### record to define each monitoring system that is installed (or will be installed) at each monitoring location in the monitoring plan . For CEMS methodologies, a monitoring system is any combination of analytical components, sensors, and data software components for which a relative accuracy test is required (e.g., SO 2 

### concentration system, flow rate system, NO

x 

### diluent system, NO

x 

### concentration system, O 2 

### concentration system, CO 2 

### concentration system, or moisture system) . For monitoring methodologies based on fuel flowmeter ing, a monitoring system consists of the fuel flowmeter

component (s) and the software component (s) needed to calculate and report hourly fuel flow for a unit or common pipe for a particular fuel. See the " Specific Considerations" section below for more detailed information about system types.

Information describing the monitoring s ystem 's individual components is not needed for this record. The relationship between C OMPONENT 

### D ATA 

### and M ONITORING 

### S YSTEM 

### D ATA 

### is

defined in the M ONITORING 

### S YSTEM 

### C OMPONENT 

### D ATA 

### record.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 53March 07, 2012 September 19, 2012 8.0 Monitoring System Data



### Dependencies for M ONITORING 

### S YSTEM 

### D ATA



### The M ONITORING 

### S YSTEM 

### D ATA 

### record is dependent on the U NIT 

### D ATA 

### record or the S TACK


### P IPE 

### D ATA 

### record.

The following records are dependent upon the M ONITORING 

### S YSTEM 

### D ATA 

### record:

● M ONITORING 

### S YSTEM 

### C OMPONENT 

### D ATA



### ● M ONITORING 

### S YSTEM 

### F UEL 

### F LOW 

### D ATA



### M ONITORING 

### S YSTEM 

### D ATA 

### Elements

Instructions for completing each element of the M ONITORING 

### S YSTEM 

### D ATA 

### section are provided below:

Monitoring System ID

Element Name: MonitoringSystemID

Assign unique three- character alphanumeric IDs to each monitoring system at a stack, pipe, or

unit. Do not repeat a system ID for a given stack, pipe, or unit, and do not re- use the ID number of a system that has been permanently removed from service . However, the same system numbering scheme may be used for different units, stacks, or pipes at the sa me facility.

System Type Code

Element Name : SystemType Code

Report the code that indicates the type of system by using the appropriate upp ercase codes as

shown in Table 18:

Table 18 System Type Codes and Descriptions

Code Description

CO2 CO 2 Concentration System

FLOW Stack Flow System

GAS Gas Fuel Flow System

H2O Moisture System that uses wet and dry

O 2 analyzers

H2OM Moisture System that uses a

continuous moisture sensor

H2OT Moisture System that uses a temperature sensor and a table of lookup values

(cont.)

Monitoring Plan Reporting Instructions

-- Page 54 Environmental Protection Agency8.0 Monitoring System Data March 07, 2012 September 19, 2012



### Table 18 System Type Codes and Descriptions (cont.)

Code Description

LTGS Long Term Gas Fuel Flow System (LME)

LTOL Long Term Oil Fuel Flow System (LME)

NOX NO

x Emission Rate System

NOXE Appendix E NO

x System

NOXC NO

x Concentration System

NOXP NO

x Emission Rate PEMS System

O2 O 2 Concentration System

OILV Volumetric Oil Fuel Flow System

OILM Mass of Oil Fuel Flow System

OP Opacity (ARP only)

PM Particulate Matter Monitoring System

SO2 SO 2 Concentration System



### System Designation Code

Element Name: SystemDesignationCode

Report one of the following uppercase codes indicating the designation of the monitoring

system.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 55March 07, 2012 September 19, 2012 8.0 Monitoring System Data



### Table 19 System Designation Code and Descriptions

Code Description

P Primary

.

PB Primary Bypass. A primary bypass (PB ) describes a monitoring system

located on a bypass stack before a heat recovery steam generator (HRSG)

. 1

RB Redundant Backup. A redundant backup (RB) monitoring system is operated and maintained by meeting

all of the same p rogram QA/QC requirements as a primary system

.

B Non

- R edundant Backup. A non

redundant backup system (B) is a

" cold " backup or portable monitoring system, having its own probe, sample interface, and analytical components.

DB Data Backup. A data backup system is comprised of the analytical components contained in the primary monitoring system (or in a redundant backup system), but inc ludes a backup DAHS component.

RM Reference Method Backup. A reference method (RM) monitoring system is a monitoring system that is operated as a reference method pursuant to the requirements of Appendix A to Part 60.

CI 2 Certified Monitoring System at the

Inlet to an Emission Control Device.

1 Use code "P" for the monitoring system located on the main HRSG stack.

2 Use code " CI " only for units with add

- on SO 2 or NO

x emission controls. Specifically, the use of a " CI "

monitoring system is limited to the following circumstances:

● I f the unit has an exhaust configuration consisting of a monitored main stack and an unmonitored bypass stack, and you elect to report SO 2 data from a certified monitoring system located at the control device inlet (in lieu of reporting maximum potential concentration) during hours in which the flue gases are routed through the bypass s tack; or

● I f the outlet SO 2 or NO

x monitor is unavailable and proper operation of the add

- on emission controls is not verified, and you elect to report data from a certified SO 2 or NO

x monitor at the control device inlet in lieu of reporting MPC or MER values. However, note that for the purposes of reporting NO

x emission rate, this option may only be used if the inlet NO

x monitor is paired with a diluent monitor and represented as a NO

x - diluent monitoring system in the Component record

.

Monitoring Plan Reporting Instructions

-- Page 56 Environmental Protection Agency8.0 Monitoring System Data March 07, 2012 September 19, 2012



### Fuel Code

Element Name: FuelCode

For Appendix D fuel flowmeter systems and Appendix E NO

x 

### systems , report the type of fuel measured by the system by using the appropriate uppe rcase codes as shown in Table 20. For all other systems, report the Fuel Code as " NFS " (Non Fuel- Specific).

Table 20 Monitoring System Fuel Codes and Descriptions

Code Description

BFG Blast Furnace Gas

BUT Butane Gas

CDG Coal Derived Gas

COG Coke Oven Gas

DGG Digester Gas

DSL Diesel Oil

LFG Landfill Gas

LPG Liquefied Petroleum Gas (if measured as a gas)

MIX Mixture of oil/gas fuel types (for NOXE system for co

- fired curve only)

NFS Non

- Fuel

- Specific for CEM (including H 2 O) and Opacity Systems

NNG Natural Gas

OGS Other Gas

OIL Residual Oil

OOL Other Oil

PDG Producer Gas

PNG Pipeline Natural Gas (as defined in

§ 72.2 

### )

PRG Process Gas

PRP Propane Gas

RFG Refinery Gas

SRG Unrefined Sour Gas

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 57March 07, 2012 September 19, 2012 8.0 Monitoring System Data



### Begin Date
Element Name: Begin Date

Report the date on which the system became responsible for reporting emissions data. Under most circumstances, this date should be the actual date when the system first reported

emissions data. However, if this is a primary monitoring system associated with the use of a new methodology, this date should be the same as the BeginDate of th e associated Monitor

Method record.

This date may be later than the dates of any initial certification tests performed on the system or related components.

Begin Hour
Element Name: Begin Hour

Report the hour on which the system became responsible for reporting emissions data.

End Date
Element Name: EndDate

Report the date the system was last used if a system is retired or permanently deactivated. Do

not submit emissions data using this monitoring system ID after this date. This value should be

lef t blank for active records.

End Hour
Element Name: EndHour

If the system is retired or permanently deactivated, r eport the hour during which the system

was last used. Do not submit emissions data using this monitoring system ID after this time.

This value should be left blank for active records.

Specific Considerations

Characteristics of Monitoring Systems

● Monitoring systems are generally comprised of the actual, physical components that are installed or will be installed for a unit, pipe, or stack where the measurement equipment is installed. Each monitoring system either directly measures a specific emissions parameter (for example, NO

x 

### emission rate) or provides a parameter necessary for calculating emissions (for example, pollutant concentration, stack flow, moisture, or mass oil flow). A monitoring system can include both hardware and software

components.

● CEM Systems must include t he probe component in addition to the analyzer(s) and

DAHS software.

Monitoring Plan Reporting Instructions

-- Page 58 Environmental Protection Agency8.0 Monitoring System Data March 07, 2012 September 19, 2012



### Types of Systems Which May B e Defined and Used

● CO 2 

### or O 2 

### System . A CO 2 

### monitoring system may be used to: (1) measure percent

CO 2 

### to determine CO 2 

### mass emissions; or (2) determine hourly heat input rate (in conjunction with a flow monitoring system). O 2 

### monitoring systems are only used for determining hourly heat input rate. A CO 2 

### or O 2 

### system is comprised of a CO 2 

### or O 2 

### analyzer and a DAHS software component. When using Equation F-14A or F-14B to

convert a measured O 2 

### value to CO 2 

### for purposes of determining hourly CO 2 

### mass emissions, define a CO 2 

### monitoring system containing an O 2 

### component and DAHS software. A probe component must be added to the system when the sample acquisition method of the CO 2 

### or O 2 

### System is either dilution (DIL), dilution in

- stack (DIN), dilution out-of- stack (DOU), dry extractive (EXT), or wet extractive (WXT).

● Flow Monitoring System . This monitoring system is used to measure stack flow rate in standard cubic feet per hour (scfh). The flow rate is used to calculate heat input rate

and/or SO 2 

### , CO 2 

### , and/or NO

x 

### mass emissions. At a minimum, the system i s comprised of a flow monitor and DAHS software. For flow monitors, identify a single component as representative of the control unit of the monitor. If the average of two or more flow monitors will be used to determine the hourly flow value, identify ea ch separate flow monitor as a component in the flow monitoring system.

● Gas Fuel Flow System. This monitoring system measures gas flow rate in 100 standard cubic feet per hour. Gas flow rate is used to calculate SO 2 

### and CO 2 

### mass emissions

and/or heat input rate. At a minimum, this system is comprised of a gas fuel flow meter
and DAHS software.

● Moisture System . This system is used to measure hourly percent moisture for the calculation of hourly heat input rate, NO

x 

### emission rate, NO

x 

### mass emissions, CO 2 

### mass emissions, or SO 2 

### mass emissions, if an hourly moisture adjustment is required because component monitors use different moisture bases. A moisture system may be comprised of a moisture sensor and DAHS software or one or more dry and wet basis oxygen analyzers and DAHS software. One of these oxygen analyzers may also be a component of the NO

x 

### -diluent system described below. For units with saturated gas streams (e.g., following a wet scrubber, it is also possible to use a moisture system comprised of a temperature sensor and a moisture look-up table. This type of system is represented by a single DAHS software component (note that this is the same DAHS component that is listed as a component of the other monitoring systems at the unit or stack).

● Long Term Gas or Oil Fuel Flow System. These monitoring systems are for low mass emissions (LME) units only. They measure fuel flow on a long term (non-hourly) basis, for the purpose of quantifying unit heat input. The systems are comprised of

DAHS software components and, depending on the methodology selected, may also include Appendix D or billing fuel flowmeters or other relevant components. These systems are used in conjunction with default or unit- specific, fuel

- specific emission

rates to determine SO 2 

### , NO

x 

### , and CO 2 

### mass emissions for LME units (see § 75.19(c)(3)(ii)).

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 59March 07, 2012 September 19, 2012 8.0 Monitoring System Data



### ● NO

x 

### -D iluent System . This monitoring system is used to determine NO

x 

### emission rate in lb/mmBtu. It is comprised of a NO

x 

### concentration monitor, a CO 2 

### or O 2 

### diluent monitor, and DAHS software. A probe component must be added to the system when the sample acquisition method of the NO

x 

### -D iluent System is either dilution (DIL),

dilution in -stack (DIN), dilution out-of- stack (DOU), dry extractive ( EXT), or wet extractive (WXT).

● Appendix E NO

x 

### System (NOXE)

. This monitoring system is used to determine NO

x 

### emission rate in lb/mmBtu based on a NO

x 

### /heat input rate correlation curve derived from emission testing. Each NOXE system represents a single correlation cu rve (either for a single fuel or for a consistent mixture of fuels) and is comprised of the DAHS software component. Appendix E systems are associated with a unit, not with multiple

or common stacks.

● NO

x 

### Concentration System. This monitoring system is used to determine NO

x 

### concentration, and is used in conjunction with a separately certified flow monitoring system to calculate NO

x 

### mass emission rate (lb/hr). It is comprised of a NO

x 

### concentration monitor and DAHS software.

● NO

x 

### Predictive Emissions Monitoring System. This type of monitoring system must be approved by petition under §75.66 and Subpart E of Part 75. It is used to determine

NO

x 

### emission rate for a gas or oil-fired turbine or boiler and is comprised only of a

DAHS software component (or components).

● Volumetric Oil Fuel Flow System

. This monitoring system measures hourly volumetric

oil flow rate. Oil flow rate is used to calculate SO 2 

### and CO 2 

### mass emissions and/or heat input rate. At a minimum, it is comprised of an oil fu el flowmeter and DAHS

software.

● Mass Oil Fuel Flow System

. This monitoring system measures hourly mass of oil combusted in pounds per hour. Oil flow rate is used to cal culate SO 2 

### or CO 2 

### mass emissions and/or heat input rate. At a minimum, it i s comprised of an oil fuel

flow meter and DAHS software.

● Opacity System. This monitoring system is used to determine the opacity of emissions. It is comprised of a continuous opacity monitor (COM) and DAHS software.

● Particulate Matter Monitoring System

. This monitoring system is used to continuously monitor particulate emissions. Affected units with a particulate monitoring system are exempt from opacity monitoring under Part 75.

● SO 2 

### Concentration System . This monitoring system is used to measure SO 2 

### concentration. It is used in conjunction with a flow monitoring system to determine hourly SO 2 

### mass emission rates in lb/hr. The system consists of an SO 2 

### concentration monitor and a DAHS software component. A probe component must be added to the system when the sample acquisition method of the SO 2 

### Concentration System is either dilution (DIL), dilution in-stack (DIN), dilution out-of- stack (DOU), dry extractive ( EXT), o r wet extractive (WXT).

Monitoring Plan Reporting Instructions

-- Page 60 Environmental Protection Agency8.0 Monitoring System Data March 07, 2012 September 19, 2012



### OILM, OILV, and GAS Systems

● If different types of oil or gas are burned in one unit, define a separate oil or gas system for each type of fuel combusted in the unit.

● Each oil or gas system must include at least one fuel flowmeter hardware component. Each oil and gas system must also include a DAHS component to record and calculate fuel flow and heat input and to perform missing data substitutions.

● The oil or gas system for the unit or common pipe must include all fuel flowmeters that are necessary to determine net fuel flow for one type of fuel. For example, if net oil flow is measured by using one flowmeter for the main fuel line to the unit and subtracting the value measured by the flowmeter on the return fuel line, the system must include both the main and return flowmeters as separate components of the same system. If more than one pipe supplies the same type of fuel to a unit and separate fuel flowmeters are installed on each of the pipes (e.g., for a combined cy cle turbine with a duct burner), all the flowmeters measuring that one fuel are considered separate components of the same system.

Low Mass Emissions Units ( LME s)

● For low mass emissions units reporting under §75.19, do not define monitoring

systems , and do not report this record unless long term fuel flow monitoring systems are used to measure fuel flow and heat input.

● For a group of oil or gas- fired LME units served by a common pipe (or supply tank), define a LTOL or LTGS monitoring system for the pipe or tank. In both cases (i.e., for common pipe or tank), the pipe or tank ID number must begin with a " CP " prefix (e.g., CP001). If two or more common pipes or tanks of different fuel types supply the same group of LME units, define a separate LTOL or LTGS system for each pipe or tank. If two or more pipes or tanks supply the same type of fuel to a group of LME units, define a single LTOL or LTGS system.

M ONITORING 

### S YSTEM 

### D ATA 

### U PDATES



### If changes must be made to key data fields and/or a system m ust be re defined after that system has been certified and used to report emissions, recertification testing may be required. If it is necessary to make such changes and it is unclear what testing or other requirements may be associated with that change, c ons ult with EPA or the applicable s tate agency

.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 61March 07, 2012 September 19, 2012 8.0 Monitoring System Data



### [This page intentionally left blank.]

Monitoring Plan Reporting Instructions

-- Page 62 Environmental Protection Agency8.1 Monitoring System Fuel Flow Data March 07, 2012 September 19, 2012



## 8 .1 M ONITORING 

## S YSTEM 

## F UEL 

## F LOW 

## D ATA



### Figure 1 6

M ONITORING 

### S YSTEM 

### F UEL 

### F LOW 

### D ATA 

### XML Elements

Description of Data

The M ONITORING 

### S YSTEM 

### F UEL 

### F LOW 

### D ATA 

### record provides the maximum fuel flow rate for the system for use in missing data substitution routines. Report one M ONITORING 

### S YSTEM 

### F UEL


### F LOW 

### D ATA 

### record for each GAS, OILV, OILM, LTOL, or LTGS system defined in

M ONITORING 

### S YSTEM 

### D ATA



### .

Dependencies for M ONITORING 

### S YSTEM 

### F UEL 

### F LOW 

### D ATA



### The M ONITORING 

### S YSTEM 

### F UEL 

### F LOW 

### D ATA 

### record is dependent on the S YSTEM 

### D ATA 

### record.

No other records are dependent upon the M ONITORING 

### S YSTEM 

### F UEL 

### F LOW 

### D ATA 

### record.

M ONITORING 

### S YSTEM 

### F UEL 

### F LOW 

### D ATA 

### Elements

Instructions for completing each element of the M ONITORING 

### S YSTEM 

### F UEL 

### F LOW 

### D ATA 

### section are provided below:

Maximum Fuel Flow Rate

Element Name: MaximumFuelFlowRate

Report the maximum fuel flow rate for the system. This maximum fuel flow rate is needed for missing data purposes. If the system is comprised of main supply and return components, calculate the net system maximum fuel flow rate assuming that the main supply is operating at the maximum potential fuel flow rate, as defined in Section 2.4.2.1 of Appendix D, and that the return flow rate is zero. For a combined cycle turbine with a duct burner, if the fuel flowmeter

syst em includes both the turbine and duct burner flowmeter components, report the sum of the maximum potential fuel flow rates of the component flowmeters.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 63March 07, 2012 September 19, 2012 8.1 Monitoring System Fuel Flow Data



### System Fuel Flow UOM Code

Element Name: SystemFuelFlowUOMCode

Report the units of measure for fuel flow rate provided by the system using the appropriate

upp ercase codes as shown in Table 21:

Table 21 Units of Measure for Maximum Fuel Flow Rate Codes and Descriptions

Parameter Code Description

Volumetric Flow of Oil SCFH Standard cubic feet per hour

GALHR Gallons per hour

BBLHR Barrels per hour

M3HR Cubic meters per hour

Mass of Oil LBHR Pounds per hour

Gas F low HSCF 100 standard cubic feet per hour



### Maximum Fuel Flow Rate Source Code

Element Name: MaximumFuelFlowRateSourceCode

Report either " URV " to indicate that the maximum rate is based on the upper range value, or

" UMX " to indicate that the maximum rate is determined by the rate at which the unit can

combust fuel.

Begin Date
Element Name: Begin Date

Report the date on which the monitoring system fuel flow data became effective. This will usually be the same as the begin date for the monitoring system. If there was a change to the maximum fuel flow rate, in the record for the new information report the date that the change took place.

Begin Hour
Element Name: Begin Hour

Report the hour in which the monitoring system fuel flow data became effective

.

End Date
Element Name: EndDate

If applicable, report the last date on which the fuel flow record w as in effect . This value should

be left blank for active records.

Monitoring Plan Reporting Instructions

-- Page 64 Environmental Protection Agency8.1 Monitoring System Fuel Flow Data March 07, 2012 September 19, 2012



### End Hour
Element Name: EndHour

If applicable, r eport the last hour in which the fuel flow record was in effect . This value should

be left blank for active records.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 65March 07, 2012 September 19, 2012 8.1 Monitoring System Fuel Flow Data



### [This page intentionally left blank.]

Monitoring Plan Reporting Instructions

-- Page 66 Environmental Protection Agency8.2 Monitoring System Component Data March 07, 2012 September 19, 2012



## 8 .2 M ONITORING 

## S YSTEM 

## C OMPONENT 

## D ATA



### Figure 17

M ONITORING 

### S YSTEM 

### C OMPONENT 

### D ATA 

### XML Elements

Description of Data

This record links individual monitoring components to each monitoring system in which they serve and defines the time frame for that relationship . Report a M ONITORING 

### S YSTEM


### C OMPONENT 

### D ATA 

### record for each system -component relationship. See the desc riptions for each type of monitoring system in the instructions for the M ONITORING 

### S YSTEM 

### D ATA 

### record for general information about what components to include in each system.

Except for primary monitoring systems containing like -kind replacement (" LK " ) components, a system should not contain any active components that are not in service when the system is being used to monitor and report data. For example, do not include backup DAHS software as an additional DAHS component of a primary system. If you h ave defined primary SO 2 

### system 101, consisting of a SO 2 

### concentration monitor (component ID S01) and a DAHS software installation (component ID D01), and you also have a second installation of that DAHS software, you should define a separate Data Backup (D B) SO 2 

### monitoring system

.

Dependencies for M ONITORING 

### S YSTEM 

### C OMPONENT 

### D ATA



### The M ONITORING 

### S YSTEM 

### C OMPONENT 

### D ATA 

### record is dependent on the M ONITORING 

### S YSTEM


### D ATA 

### record.

No other records are dependent upon the M ONITORING 

### S YSTEM 

### C OMPONENT 

### D ATA 

### record.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 67March 07, 2012 September 19, 2012 8.2 Monitoring System Component Data



### M ONITORING 

### S YSTEM 

### C OMPONENT 

### D ATA 

### Elements

Instructions for completing each element of the M ONITORING 

### S YSTEM 

### C OMPONENT 

### D ATA 

### section are provided below:

Component ID

Element Name: ComponentID

Report the three- character alphanumeric ID for the component.

Begin Date
Element Name: Begin Date

Report the date on which the component became an active part of the system. If this component is an original part of the system, this date will be the same as the System Begin D ate.

Begin Hour
Element Name: Begin Hour

Report the hour in which the component became an active part of the system

.

End Date
Element Name: EndDate

Report the last date that the component was an active part of the system . This value should be

left blank for active system -component relationships.

End Hour
Element Name: EndHour

Report the last hour that the component was an active part of the system . This value should be

left blank for active system -component relationships.

Monitoring Plan Reporting Instructions

-- Page 68 Environmental Protection Agency9.0 Monitoring Formula Data March 07, 201 2 September 19, 2012



## 9 .0 M ONITORING 

## F ORMULA 

## D ATA



### Figure 18

M ONITORING 

### F ORMULA 

### D ATA 

### XML Elements

Description of Data

The M ONITORING 

### F ORMULA 

### D ATA 

### record is used to identify the formulas that will be used to calculate required data from the monitoring systems defined in the M ONITORING 

### S YSTEM 

### D ATA 

### record. It is not necessary to define formulas referencing backup monitoring systems unless the backup monitoring systems use different formulas than the primary system.

M ONITORING 

### F ORMULA 

### D ATA 

### are used for three primary purposes:

● To verify that the formulas selected are appropriate to the monitoring approach and reflect a thorough understanding of emissions calculations and the use of appropriate variables;

● To provide the basis for formula verification to ensure that the DAHS software calculates emissions and selected values accurately; and

● To verify hourly calculations in quarterly reports.

Dependencies for M ONITORING 

### F ORMULA 

### D ATA



### The M ONITORING 

### F ORMULA 

### D ATA 

### record is dependent on the U NIT 

### D ATA 

### record or the S TACK


### P IPE 

### D ATA 

### record.

No other records are dependent upon the M ONITORING 

### F ORMULA 

### D ATA 

### record.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 69March 07, 2012 September 19, 2012 9.0 Monitoring Formula Data



### M ONITORING 

### F ORMULA 

### D ATA 

### Elements

Instructions for completing each element of the M ONITORING 

### F ORMULA 

### D ATA 

### section are provided below:

Formula ID
Element Name: FormulaID

Assign a unique three- character Formula ID for each formula defined at a unit, stack, or pipe. Assign unique formula IDs across all related units and stacks, if a facility includes a common stack, pipe header, or multiple stack. Do not reuse formula IDs if chang ing component types ( e.g. , from dry extractive to wet dilution systems) and therefore chang ing the type of for mula in

use.

Parameter Code

Element Name: ParameterCode

Report the parameter representing the pollutant or parameter calculated by the formula by using the appropriate upp ercase codes as shown in Table 22.

Table 22 Parameter Codes and Descriptions for Monitoring Formula

Code Description

CO2 CO 2 Hourly Mass Emission Rate (tons/hr)

CO2C CO 2 Concentration (% CO 2 )

CO2 M CO 2 Daily Mass (tons)

FC F

- Factor Carbon

- B ased

FD F

- Factor Dry

- B asis

FGAS Gas Hourly Flow Rate (hscf)

FLOW Net Stack Gas Volumetric Flow Rate

FOIL Net Oil Flow Rate to Unit/Pipe

FW F

- Factor Wet

- B asis

H2O Moisture (% H 2 O)

HI Heat Input Rate (mmBtu/hr)

HIT Heat Input Total (mmBtu)

NOX NO

x Hourly Mass Emission Rate (lb/hr)

(cont.)

Monitoring Plan Reporting Instructions

-- Page 70 Environmental Protection Agency9.0 Monitoring Formula Data March 07, 201 2 September 19, 2012



### Table 22 Parameter Codes and Descriptions

for Monitoring Formula (cont.)

Code Description

NOX R NO

x Emission Rate (lb/mmBtu)

OILM Oil Mass Flow Rate (lb/hr)

SO2 SO 2 Hourly Mass Emission Rate (lb/hr)

SO2R SO 2 Em i ssion Rate (lb/mmBtu) When

E quation D

- 1h Is Used



### Formula Code

Element Name: FormulaCode

Report the formula code of the formula that appears in the tables below and in 40 CFR Part 75, Appendices D through G (or, if appropriate, in 40 CFR Part 60, Appendix A, Method 19) that is applicable to the parameter and the typ es of monitoring components. EPA relies on the accuracy of the formula code to verify hourly emissions calculations. Tables 23 through 34 provide summaries of the primary formulas used to calculate SO 2 

### , NO

x 

### emissions , and CO 2 

### ; moisture and heat input rat e using CEMS ; and fuel flowmeter methodologies. For moisture monitoring systems comprised of wet and dry oxygen analyzers, see Table 28, Equations F-31 and M- 1K. For net fuel flow and average stack flow formulas, see Table 35. All formula codes must be entered exactly as they are presented in Tables 23 through 34. This includes the use of dashes and capital letters.

For example, report "F-1" (from Table 25) if using the equation for converting measurements of

SO 2 

### concentration and flow rate on a wet basis to SO 2 

### in lb/hr. Report "F-5" (from Table 27 ) if using the equation from Method 19, Appendix A, 40 CFR Part 60 for converting measurements

of NO

x 

### concentration and O 2 

### diluent on a dry basis to NO

x 

### emission rate in lb/mmBtu. In the second example, formula code "19-1" could have been used instead of "F- 5, " since Equation 19-1 in Method 19 is identical to Equation F-5 in Appendix F to Part 75.

For custom or non- standard intermediate equations that are not listed in Tables 2 3 – 34 below,

leave the Formula Code blank.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 71March 07, 2012 September 19, 2012 9.0 Monitoring Formula Data



### Tab le 2 3

F- Factor * Reference Table

Option 1: Fuel

- Based Constants

Fuel F

- F actor (dscf/ mmBtu) F c - F actor (scf CO 2 / mmBtu) F w -F actor (wscf/mmBtu)

Coal Anthracite 10,100 1,970 10,540

Bituminous 9,780 1,800 10,640

Sub

- bituminous 9,820 1,840

-----­

Lignite 9,860 1,910 11,950

Petroleum Coke 9,830 1,850

-----­

Tire

- Derived Fuel 10,260 1,800

-----­

Gas Natural Gas 8,710 1,040 10,610

Propane 8,710 1,190 10,200

Butane 8,710 1,250 10,390

Oil Oil 9,190 1,420 10,320

Waste Municipal Solid Waste 9,570 1,820

--- --­

Wood Bark 9,600 1,920

--- --­

Wood Residue 9,240 1,830

--- --­

(cont.)

Monitoring Plan Reporting Instructions

-- Page 72 Environmental Protection Agency9.0 Monitoring Formula Data March 07, 201 2 September 19, 2012



### Table 2 3

F- Factor * Reference Table (cont.)

Option 2 : Calculated F

- Factors

Code Para

meter Formula Where:

F

- 7A FD

x 10 GCV 0.46(%O) - 3.64(%H)+1.53(%C)+0.57(%S)+0.14(%N) F = 6 F = Dry

- basis F

- factor (dscf/mmBtu)

F

c = Carbon

- based F

- factor (scf

CO 2 /mmBtu)

F

w = Wet

- basis F

- factor (wscf/mmBtu)
%H,%N, = Content of element, percent %S, %C, by weight, as determined %O,%H 2 O on the same basis as the gross calorific value by

ultimate analysis of the fuel combusted using ASTM

D3176

- 89 for solid fuels,

ASTM D1945

- 91 or ASTM

D1946

- 90 for gaseous fuels, as applicable

GCV = Gross calorific value F

- 7B FC



### GCV x (%C) 321 x 10

= F 3

c

19

- 14 FW

x 10 GCV O) 0.46(%O)+0.21(% H

- 5.57(%H)+1.53(%C)+0.57(%S)+0.14(%N)

= F 6

w 2

w

(Btu/lb) of fuel combusted determined by ASTM

D2015

- 91 for solid and liquid fuels or ASTM

D1826

- 88 for gaseous fuels, as applicable

GCV

w = Calorific value (Btu/lb) of fuel combusted, wet basis

F

- 8* * FD, FC, or

FW 

### X F F = ii n

i =1 

# ∑ F = Dry

- basis F

- factor (dscf/mmBtu)

F

c = Carbon

- based F

- factor (scf

CO 2 /mmBtu)

n = Number of fuels being

combusted

F i ,(F

c ) i, = Applicable F, F

c , or F

w (F

w ) i factor for each fuel type

X i = Fraction of total heat input derived from each type of

fossil fuel 

### ) X ( F = F i ci n

i =1 c 

# ∑

) X ( F = F i wi n

i =1 w 

# ∑

* F- factor is the ratio of the gas volume of all the products of combustion (less water) to the heat content of the

fuel. F

c - factor is the ratio of the gas volume of the CO 2 generated to the heat content of the fuel (see Part 75, Appendix F, Section 3.3). F

w - factor is the ratio of the quantity of wet effluent gas generated by the combustion to the heat content of the fuel including free water in the fuel.

** This formula sh ould be used for affected units that combust combinations of fossil fuels or fossil fuels and wood

residue. For affected units that combust a combination of fossil and non

- fossil fuels, the selected F

- factor must

receive state or EPA approval.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 73March 07, 2012 September 19, 2012 9.0 Monitoring Formula Data



### Table 24

SO 2 

### Formula References

Usage Moisture Basis* Appropriate Hourly Formulas (Part 75, Appendices D&F)

SO2 CEMS WET F

- 1

DRY F

- 2

D efault SO 2 emission rate when low

sulfur fuels are burned (e.g.

, natural gas) F

- 23 (and D

- 1H)

Oil Fuel Flowmeter D

- 2

Gas Fuel Flowmeter D

- 4 or D

- 5 (and D

- 1H)

Overall values for multiple fuel flowmeter systems D

- 12

* For sample acquisition method (SAM) codes IS, ISP, ISC, DIN, DOU, DIL, and WXT = wet extractive ;

f or EXT = dry extractive, located under component

. Exceptions are possible. Check with vendor if

uncertain.



### Table 2 5

SO 2 

### Emission Formulas

Code Parameters Formula Where:

F

- 1 SO2 

### x Q = K x C E h h h E h K

C hp

C h

Q h and Q hs %H 2 O =

=

=

=

=

= Hourly SO 2 mass emission rate (lb/hr)

1.660 x 10 -7 for SO 2 ((lb/scf)/ppm) Hourly average SO 2 concentration (ppm (dry)) Hourly average SO 2 concentration (ppm (stack moisture basis)) Hourly average volumetric flow rate (scfh (stack moisture basis) ) Hourly a verage stack moisture content (percent by volume) F

- 2 SO2



### 100 % H O 100 ­

xx

Q = K x C E 2

hs hp h

D

- 1H SO2R



### GCV S

xx

10 7000

2.0

= ER total 6 ER

S total

GCV =

=

= Default SO 2 emission rate for natural gas (or " other " gaseous fuel) combustion (lb/mmBtu) Total sulfur content of gaseous fuel (grains/100 scf) Gross calorific value of the gas (Btu/100 scf)

2.0

7000

10 6 =

=

= Ratio of lb SO 2 /lb S Conversion of grains/100 scf to lb/

100 scf

Conversion of Btu to mmBtu

(cont.)

Monitoring Plan Reporting Instructions

-- Page 74 Environmental Protection Agency9.0 Monitoring Formula Data March 07, 201 2 September 19, 2012



### Table 2 5

SO 2 

### Emission Formulas (cont.)

Code Parameters Formula Where:

D

- 2 SO2



### 100.0 % S

x = 2.0 x OIL SO 2 oil

rate rate

- oil SO 2 rate-oil

OIL rate

%S oil

2.0 =

=

=

= Hourly mass emission rate of SO 2 emitted from combustion of oil (lb/hr) Mass rate of oil consumed per hour during combustion (lb/hr) Percent sulfur by weight measured in oil sample

Ratio of lb SO 2 to lb S

D

- 4 SO2



### x S x GAS =SO 2 gas rate rate 

### (2.0 / 7000) SO 2rate

GAS rate

S gas

2.0

7000 =

=

=

=

= Hourly mass rate of SO 2 from combustion of gaseous fuel (lb/hr) Hourly metered flow rate of gaseous fuel combusted ( 100 scf/hr) Sulfur content of gaseous fuel (grains/100 scf)

Ratio of lb SO 2 /lb S Conversion of grains/100 scf to lb/

100 scf

D

- 5 SO2



## = ER x HI SO 2 rate rate SO 2rate

ER

HI rate =

=

= Hourly mass emission rate of SO 2 from combustion of gaseous fuel (lb/hr)

SO 2 emission rate from Appendix D, Section 2.3.1.1 or Appendix D, Section 2.3.2.1.1 to Part 75 (lb/mmBtu) Hourly heat input rate of a gaseous fuel, calculated using procedures in Appendix D, Section 3.4.1 to Part 75 (mmBtu/hr)

F

- 23 SO2



## = ER x HI E h E h ER

HI =

=

= Hourly SO 2 mass emission rate (lb/hr) Applicable SO 2 default emission rate from Appendix D, Section 2.3.1.1, or Appendix D, Section 2.3.2.1.1 to Part 75 (lb/mmBtu) Hourly heat input rate, determined using a certified flow monitor and diluent monitor, according to Appendix F, Section 5.2 (mmBtu/hr)

D

- 12 * SO2

u i rate -i

all

- fuels

rate 

### t tSO

=SO 2 2 

# ∑ SO 2rate

SO 2rate-i

t i

t
u =

=

=

= Hourly mass emission rate of SO 2 from

combustion of all fuel s (lb/hr)

SO 2 mass emission rate for each type of gas or oil fuel combusted during the hour (lb/hr) Time each gas or oil fuel was combusted for the hour (fraction of an hour) Operating time of the unit

* This equation is a modified form of Equation D

- 12 as described in Appendix D, Section 3.5.1, and must be used

when reporting in the XML format.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 75March 07, 2012 September 19, 2012 9.0 Monitoring Formula Data



### Table 2 6

NO

x 

### Emission Rate Formula Reference Table

Usage Moisture Basis Appropriate Hourly

Formulas NO

x CO 2 O 2

NO

x CEMS (CO 2 Diluent) DRY DRY 19

- 6

DRY WET 19

- 9

WET DRY 19

- 8

WET WET 19

- 7 or F

- 6

NO

x CEMS (O 2 Diluent) DRY DRY 19

- 1 or F

- 5

DRY WET 19

- 5 or 19

- 5D

WET DRY 19

- 4

WET WET 19

- 2, 19

- 3, or 19

- 3D

Overall V alue from M ultiple Appendix E Systems E

- 2

Monitoring Plan Reporting Instructions

-- Page 76 Environmental Protection Agency9.0 Monitoring Formula Data March 07, 201 2 September 19, 2012



### Table 27

NO

x 

### Emission Rate Formulas (lb/mmBtu)

Code Parameter Formula Where:

19

- 1 (F

- 5) NOXR



### % O 20.9 ­ 20.9

xx

F = K x C E

2 d d

d Formulas should be multiplied by the

conversion factor "K" (if C d or C

w is in ppm)

FROM TO MULTIPLY BY "K" ppm NO

x lb/scf K = 1.194 X 10 -7

E = Emission rate (lb/ mmBtu)

C d = Pollutant concentration (ppm, dry basis)

C

w = (Pollutant concentration ppm, wet basis)

F d = Dry

- basis F

- factor (dscf/mmBtu)

F

c = Carbon

- based F

- factor (scf

CO 2 /mmBtu)

F

w = Wet

- basis F

- factor (wscf/mmBtu)

B

wa = Moisture fraction of ambient air ( default value 0.027)

%H 2 O = Moisture content of effluent gas

O 2 d = Oxygen diluent concentration
(percent of effluent gas, dry basis)

O 2 w = Oxygen diluent concentration
(percent of effluent gas, wet basis)

O 2 def = Default diluent cap O 2 value (14.0
percent for boilers, 19.0 percent for combustion turbines)

CO 2 d = Carbon dioxide diluent
concentration (percent of effluent gas, dry basis)

CO 2 w = Carbon dioxide diluent
concentration (percent of effluent gas, wet basis)

E f = NO

x emission rate for the unit for a given fuel at heat input rate HI f , lb/mmBtu

HI f = Heat input rate for the hour for a given fuel, during the fuel usage time, as dete rmined using Equation F

- 19 or F

- 20 in Section

5.5 of A p pendix F to this part,

mmBtu/hr

H T = Total heat input for all fuels for the hour from Equation E -1

t f = Fuel usage time for each fuel (rounded to the nearest fraction of an hour (in equal increments that can range from one hundredth to one quarter of an hour, at the option of the owner or operator)) 19

- 2 NOXR



### % O -)-

B 20.9 (1 20.9

xx

F = K x C E

2 wa w w

w

19

- 3* NOXR

% O

- 100 % H O-100 20.9 x 20.9

xx

F = K x C E

2 2 d w

w      

19

­ 3D* NOXR

           

100 100 -% H O x-% O 100 100 -% H O 20.9 x 20.9

xx

F E = K x C

2

2 2 d w

def

19

- 4* NOXR



### )% O (20.9 ­ 20.9

x % H O) 100 (100 ­ x F )(

C = K xE

2 2 d w

d 

### ÷

19

- 5* NOXR



###            

÷ 100 % H O 100 ­ % O 20.9 ­ x F 20.9 x K x C E =

2

2 d d

w

19

- 5D NOXR



### % O 20.9 ­ 20.9

xx

F E = K x C

2 d d

def

19

- 6 NOXR



### % CO 100

xx

F E = K x C

2 c d

d

19

- 7 (F

- 6) NOXR



### % CO 100

xx

F E = K x C

2 c w

w

19

- 8* NOXR



### % CO 100

x 100 % H O) (100 ­ x F )(

C E = K x

2 2 c w

d 

### ÷

19

- 9* NOXR



### % CO 100

xx

F 100 % H O 100 ­ x= K x C E

2 c 2
d

w 

###      

E

- 2 NOXR



### H ) t x HI ( E

= E

T f ff all fuels

f =1

h 

# ∑

* Note that [(100 - %H 2 O/100] may also represented as (1 - B

ws ), where B

ws is the proportion by volume of water

vapor in the stack gas stream.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 77March 07, 2012 September 19, 2012 9.0 Monitoring Formula Data



### Table 28

Moisture Formulas *

Code Parameter Formula Where:

F

- 31 H2O 

### x 100 O ) O -(

O =% H O

2 22
2

d w d %H 2 O = O 2 d =

O 2 w = Percent m oisture Oxygen diluent concentration
(percent of effluent gas, dry basis) Oxygen diluent concentration
(percent of effluent gas, wet basis) M

- 1K H2O 

# ( )

% H O O O

O d w

d 2 2 2

2 

### 100 = −
×



### , as adjusted 1

* Please contact the EPA Clean Air Markets Division for the assigned code for other moisture formulas.

1 Using a K

- factor or other mathematical algorithm, per Appendix A, Section 6.5.7(a).



### Table 29

CO 2 

### Formula Reference Table

Usage Moisture Basis Appropriate Formulas (Part 75, Appendices F, G)

CO 2 CEMS (O 2 A nalyzer ) WET F

- 14B and F

- 11

DRY F

- 14A and F

- 2

CO 2 CEM (CO 2 A nalyzer ) WET F

- 11

DRY F

- 2

Fuel Sampling G

- 1 ( and possibly G

- 2, G

- 3, G

- 5, G

- 6 and

G

- 8 )

Gas or Oil Flowmeter G

- 4

O v eral l Value from Multip l e Flowmeter Systems G

- 4A

Monitoring Plan Reporting Instructions

-- Page 78 Environmental Protection Agency9.0 Monitoring Formula Data March 07, 201 2 September 19, 2012



### Table 3 0

CO 2 

### Concentration and Mass Emission Rate Formulas

Code Parameter Formula Where:

F

- 2 CO2



### E K C Q H O

h hp hs



### = × × × 100

−
100 2



### % E h = K =

C hp =

Q hs =

%H 2 O = Hourly CO 2 mass emissions (tons/hr)

5.7 x 10 -7 for CO 2 ((tons/scf)/percent CO 2 ) Hourly average, CO 2 concentration (percent CO 2 , dry basis) Hourly average volumetric flow rate (scfh, wet basis) Hourly a verage stack moisture content (percent b y volume)

F

- 11 CO2



## E K C Q h h h 

## = × × E h =

K =

C h =

Q h = Hourly CO 2 mass emission rate (tons/hr)

5.7x10 -7 for CO 2 ((tons/scf)/percent CO 2 ) Hourly average CO 2 concentration (percent CO 2 , wet basis) Hourly average volumetric flow rate (scfh, wet basis)

F

- 14A CO2C



### CO F

F O

d c d

2 2 

### 100 20 9

20 9 = × × −

.

. CO 2d =

F =

F

c =

20.9 =
O 2 d = Hourly average CO 2 concentration (percent by volume, dry basis) Dry

- basis F

- factor (dscf/mmBtu)

Carbon

- based F

- factor (scf CO 2 /mmBtu) Percentage of O 2 in ambient air
Hourly average O 2 concentration (percent by volume, dry basis)

F

- 14B CO2C

CO F

F H O O

w c

W 2 2

2 100

20 9 20 9 100

100 = × × −      

− 

  

 

. . % CO 2w =

F =

F

c =

20.9 = O 2W =

%H 2 O = Hourly average CO 2 concentration (percent by volume, wet basis) Dry

- basis F

- factor (dscf/mmBtu)

Carbo n- based F

- factor (scf CO 2 /mmBtu) Percentage of O 2 in ambient air Hourly average O 2 concentration (percent by volume, wet basis)

Moistur e content of gas in the stack (percent )

G

- 1 CO2M 

# ( )

W MW MW W

MW CO c O c

c 2 2 

### 2000 = + × W CO 2 =

MW

c = MW O 2 =

W

c = CO 2 emitted from combustion
(tons/day) Molecular weight of carbon (12.0) Molecular weight of oxygen (32.0)
Carbon burned (lb/day) determined using fuel sampling and analysis and

fuel feed rates *

(cont. )

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 79March 07, 2012 September 19, 2012 9.0 Monitoring Formula Data



### Table 3 0

CO 2 

### Concentration and Mass Emission Rate Formulas (cont.)

Code Parameter Formula Where:

G

- 2 CO2M

W W MW

MW A C W NCO CO CO

c COAL 2 2 2
100 100

=

− ×       ×       × % % W NCO2

W CO2

MW CO2

MW

c = Net CO 2 mass emissions discharged to the atmosphere (tons/day)

= Daily CO 2 mass emissions calculated

by Equation G

- 1 (tons/day)

= Molecular weight of carbon dioxide (44.0)

= Molecular weight of carbon (12.0)

A%

C%

W COAL = Ash content of the coal sample (percent by weight)

= Carbon content of ash (percent by

weight)

= Feed rate of coal from company

records (tons/day)

G

- 3 CO2M



## W W NCO CO 2 2 

## = 99 ×

. W NCO2

.99

W CO2 = Net CO 2 mass emissions from the combustion of coal discharged to the atmosphere (tons/day)

= Average fraction of coal converted

into CO 2 upon combustion

= Daily CO 2 mass emissions from the combustion of coal calculated by Equation G

- 1 (tons/day)

G

- 4 CO2



### W F H U MW

CO c f CO

2 2 

### 2000 = × × × W CO 2

F

c = CO 2 emitted from combustion
(tons/hr)

= Carbon

- based F

- factor, 1,040 scf/mmBtu for natural gas; 1,420 scf/mmBtu for crude, residual, or distillate oil and calculated according to the procedures in Section 3.3.5 of Appendix F to Part 75 for other gaseous fuels

H

U f

MW CO 2 = Hourly heat input rate (mmBtu/hr )

= 1/385 scf CO 2 /lb

- mole at 14.7 psi and

68 Ε F

= Molecular weight of carbon dioxide

(44.0)

G

- 4A CO2

CO CO t

t unit fuel fuel

all fuels

unit 2 2

= − 

# ∑ CO2 unit

CO2 fuel

t fuel
t unit = Unit CO 2 mass emission rate (tons/hr)

= CO 2 mass emission rate calculated

using Equation G

- 4 for a single fuel (tons/hr)

= Fuel usage time

= Unit operating time

(cont.)

Monitoring Plan Reporting Instructions

-- Page 80 Environmental Protection Agency9.0 Monitoring Formula Data March 07, 201 2 September 19, 2012



### Table 30

CO 2 

### Concentration and Mass Emission Rate Formulas (cont.)

Code Parameter Formula Where:

G

- 5 CO2M



### SE W F MW

MW CO CaCO u CO

CaCO 2 3 2

3



### = × × SE CO 2 = CO 2 emitted from sorbent (tons/day)

W CaCO 3 = Calcium carbonate used (tons/day)

F

u = 1.00, the calcium to sulfur

stoichiometric ratio

MW CO 2 = Molecular weight of carbon dioxide

(44 .0 )

MW CaCO 3 = Molecular weight of calcium
carbonate (100 .0 )

G

- 6 CO2M



### SE F W MW

MW CO u SO CO

SO 2 2

2 

### 2000 2



### = SE CO 2 = CO 2 emitted from sorbent (tons/day)

MW CO 2 = Molecular weight of carbon dioxide

(44 .0 )

MW SO 2 = Molecular weight of sulfur dioxide

(64 .0 )

W SO 2 = Sulfur dioxide removed (lb/day)
based on applicable procedures, methods, and equations in § 75.15

F

u = 1.00, the calcium to sulfur

stoichiometric ratio

G

- 8 CO2M

2 2 CO CO t 

### SEWW += W t = Estimated total CO 2 mass emissions (tons/day)

W CO 2 = CO 2 emitted from fuel combustion
(tons/day)

SE CO 2 = CO 2 emitted from sorbent (tons/day)

* See Appendix G, sections 2.1.1 through 2.1.3

** For a unit linked to a common pipe with one additional fuel flowmeter system defined at the unit, report a G

- 4A formula to calculate the unit hourly CO2 rate, even though there is only a single fuel flowmeter defined at the unit. Because the fuel usage time may not be equal to the unit operating time, the hourly CO2 rate for the fuel may be

different f rom the hourly CO2 rate for the unit

. Use formula G

- 4A to calculate the unit hourly CO2 rate.



### Table 31 Heat Input Formula Reference Table

Usage Moisture Basis* Appropriate Hourly Formulas (Part 75, Appendices D and F)

CEMS (O 2 A nalyzer ) WET F

- 1 7

DRY F

- 18

CEMS ( C O 2 A nalyzer ) WET F

- 1 5

DRY F

- 16

Gas Fuel Flowmeter System D

- 6 (F

- 20)

(cont.)

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 81March 07, 2012 September 19, 2012 9.0 Monitoring Formula Data



### Table 31 Heat Input Formula Reference Table (cont.)

Usage Moisture Basis* Appropriate Hourly Formulas (Part 75, Appendices D and F)

Oil Fuel Flowmeter System (Mass) D

- 8 (F

- 19)

Oil Fuel Flowmeter System (Volumetric) D

- 3 and D

- 8 (F

- 19) or F

- 19V

Overall Value from Multiple Fuel Flowmeter Systems D

- 15A

Apportioned Value from Common Stack or Common Pipe F

- 21A, F

- 21B, or F

- 21

Summed Value from Multiple

Stacks F

- 21C

Summed Value from Unit F

- 25

* For sample acquisition method (SAM) codes IS, ISP, ISC, DIN, DOU, DIL, and WXT = wet extractive ; for

EXT = dry extractive, locate under the component. Exceptions are possible. Check with vendor if

uncertain.

Monitoring Plan Reporting Instructions

-- Page 82 Environmental Protection Agency9.0 Monitoring Formula Data March 07, 201 2 September 19, 2012



### Table 32 Heat Input Formulas

Code Parameter Formula Where:

D

- 15A HI



### t HI

= HI i rate -i

all

- fuels

rate -hr 

# ∑ HI rate-hr = Heat input rate from all fuels combusted during the hour (mmBtu/hr)

HI rate-i = Heat input rate for each type of gas or oil combusted during the hour (mmBtu/hr)


### t u t i = Time each gas or oil fuel was combusted for the hour (fuel usage time) (fraction of an hour)

t
u = Operating time of the unit

F

- 15 HI



### 100 % CO

x F 1

x Q HI = 2w

c w HI = Hourly heat input rate (mmBtu/hr) Q

w , Q h = Hourly average volumetric flow rate (scfh, wet basis)

F

c = Carbon

- based F

- factor (scf/mmBtu)

F = Dry basis F

- factor (dscf/mmBtu)

%CO 2w = Hourly concentration of CO 2 (percent CO 2 , wet basis)

%CO 2d = Hourly concentration of CO 2 (percent CO 2 , dry basis)

%O 2w = Hourly conce ntration of O 2 (percent O 2 , wet basis)

%O 2d = Hourly concentration of O 2 (percent O 2 , dry basis)

%H 2 O = Hourly average moisture of gas in the stack (percent ) F

- 16 HI 

###            

100 % CO

100 F % H O 100 ­

x HI = Q 2d

c 2

h

F

- 17 HI

20.9 ]% O -%

H O) [(20.9/100)(100 ­

x F 1

x HI = Q 2w 2

W

F

- 18 HI



###            

20.9 )% O (20.9 ­

100F

% H O) (100 ­

x Q HI = 2d 2

w

D

- 3 OILM



### x D = V OIL oil

- rate oil rate OIL rate = Mass rate of oil consumed per hr (lb/hr)

V oil-rate = Volume rate of oil consumed per hr, measured (scf/hr, gal/hr, barrels/hr, or m 3 /hr)

D oil = Density of oil, measured (lb/scf, lb/gal, lb/barrel, or

lb/m 3 )

D

- 8 ** HI HI rate-oil = Hourly heat input rate from (F

- 19V) combustion of oil (mmBtu/hr)

OIL rate = Rat e of oil consumed (lb/hr for



### 10 GCV

x OIL = HI 6 oil

rate rate

- oil Equation D

- 8 or gal/hr for Equation F- 19V)

GCV oil = Gross calori fic value of oil (Btu/lb for Equation D

- 8 or Btu/gal for Equation F- 19V)

10 6 = Conversion of Btu to mmBtu

(cont.)

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 83March 07, 2012 September 19, 2012 9.0 Monitoring Formula Data



### Table 32 Heat Input Formulas (cont.)

Code Parameter Formula Where:

F

- 19 HI



### 10 GCV

x=

M HI 6 o

oo HI

o =

M

o =

GCV

o =

10 6 = Hourly heat input rate from combustion of oil (mmBtu/hr) Mass rate of oil consumed per hour (lb/hr)

Gross calorific value of oil (Btu/lb)

Conversion of Btu to mmBtu

D

- 6 HI



### 10 x GCV GAS

= HI 6 gas rate

gas rate

­ HI rate- gas , = HI g

GAS rate ,= Q g GCV gas ,= GCV g 10 6 = Hourly heat input rate from

combustion of gaseous fuel (mmBtu/hr) Average volumetric flow

rate of fuel (100 scfh)

Gross calorific value of gaseous fuel (Btu/100 scf)

Conversion of Btu to mmBtu F

- 20 HI



### 10 )x

GCV ( Q

= HI 6 g g

g

** For units required to monitor NO

x mass emissions but not SO 2 mass emissions , if there is a volumetric oil flowmeter, it is possible to use Equation D

- 8 on a volumetric basis, rather than a mass basis. If using this option, represent the Equation as F

- 19V in the monitoring plan

.

Monitoring Plan Reporting Instructions

-- Page 84 Environmental Protection Agency9.0 Monitoring Formula Data March 07, 201 2 September 19, 2012



### Table 33 Apportionment and Summat ion Formulas

Code Parameter Formula Where:

F

- 21A HI



###            

       



# ∑ tMW MW t

t t

= HIHI

ii n

i =1 ii

i CS
CS i HI i

HI CS

MW i
t i

t CS

n

i =

=

=

=

=

=

= Heat input rate for a unit (mmBtu/hr) Heat input rate at the common stack or pipe (mmBtu/hr) Gross electrical output (MWe) Operating time at a particular

unit Operating time at common stack or pipe Total number of units using the common stack or pipe Designation of a particular unit

F

- 21B HI



###            

       



# ∑ SF t SF t

t t

= HIHI

ii n

i =1 ii

i CS
CS i HI i

HI CS

n SF i
t i

t CS =

=

=

=

=

= Heat input rate for a unit (mmBtu/hr) Heat input rate at the common stack or pipe (mmBtu/hr) Number of stacks or pipes Gross steam load (flow) (lb/hr) Operating time at a particular

unit Operating time at common stack or pipe

n

i =

= Total number of units using the

common stack or pipe Designation of a particular unit

F

- 21C HI



### t t HI

= HI

Unit s s n

s =1
Unit 

# ∑ HI Unit

HI

s

t Unit
t
s

s

n =

=

=

=

=

= Heat input rate for a unit (mmBtu/hr) Heat input rate for each stack or duct (mmBtu/hr) Operating time for the unit Operating time for a particular

stack or duct Designation of a particular

stack or duct Total number stacks, ducts

(cont.)

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 85March 07, 2012 September 19, 2012 9.0 Monitoring Formula Data



### Table 3 3 Apportionment and Summation Formulas (cont.)

Code Parameter Formula Where:

F

- 21D HI



###            

       



# ∑ FF t FF t

t t

= HIHI

i i n

i =1 i i

i CP
CP i HI i

HI CP

FF i

t i

t CP =

=

=

=

= Heat input rate for a unit (mmBtu/hr) Heat input rate at the common pipe (mmBtu/hr) Fuel flow rate to a particular unit (appropriate units) Operating time at a particular unit (hr) Operating time at common pipe (hr)

n

i =

= Total number of units using the common pipe Designation of a particular unit

F

- 25 HI



### t HI

= HI u u p

u=1 CS 

# ∑ HI CS

HI

u

p

t
u =

=

=

= Hourly average heat input rate

at the common stack (mmBtu/hr) Hourly average heat input rate for a unit (mmBtu/hr)

Number of units Operating time at a particular


### t CS

t CS

u =

= unit Operating time at common

stack Designation of a particular unit



### Table 34

NO

x 

### Mass Emissions Formulas ( lbs/hr )

Code Parameter Formula Where:

F

- 24 A NOX



### x HI = ER E h (NOx)h NOx ) h ( E (NOx)h =

K =

C h d =

C h w =

Q h =

%H 2 O =

HI h =

ER (NOx) h = Hourly NO

x mass emissions

rate in lb/hr

1.194 x 10 -7 for NO

x ((lb/scf)/ppm) Hourly average, NO

x concentration (ppm (dry)) Hourly average, NO

x concentration, stack moisture basis (ppm (wet)) Hourly average volumetric flow rate (scfh) Hourly a verage stack moisture content (percent by volume) Hourly average heat input rate (mmBtu/hr) Hourly average NO

x emission
rate (lb/mmBtu) F

- 26 A NOX

hhw NOx h 

### QCKE ××= )(

F

- 26 B NOX



### 100 % H O) (100 ­

xx

Q = K x C E 2

h h NOx h d )(

Monitoring Plan Reporting Instructions

-- Page 86 Environmental Protection Agency9.0 Monitoring Formula Data March 07, 201 2 September 19, 2012



### Table 35

Miscellaneous Formula Codes

Code Parameter Description

N

- GAS FGAS Net or total g as fuel flow rate (100 scfh)

N

- OIL FOIL Net or total o il fuel flow rate (scf/hr, gal/hr, barrels/hr, m 3 /hr

, or lb/hr )

X

- FL FLOW Average hourly stack flow rate (scfh). (To calculate the average of two or more primary flow monitors, for example, two ultrasonic monitor s in an

X

- pattern )

T

- FL FLOW Total stack flow rate (scfh)

SS

- 1A SO2 Total hourly SO 2 mass emissions from the affected unit(s) in a subtractive stack configuration (lb /hr )

SS

- 1B SO2 Hourly SO 2 mass emissions from a particular affected unit in a subtractive stack configuration (lb /hr )

SS

- 2A NOX Total hourly NO

x mass emissions from the affected unit(s) in a subtractive stack configuration (lb /hr )

SS

- 2B NOX Hourly NO

x mass emissions from a particular affected unit in a subtractive stack configuration (lb /hr )

. (Apportioned by gross load)

SS

- 2C NOX Hourly NO

x mass emissions from a particular affected unit in a subtractive stack configuration (lb /hr )

. ( Apportioned by steam load)

SS

- 3A HI T Total hourly heat input for the affected unit(s) in a subtractive stack configuration (mmBtu)

SS

- 3B HI Hourly heat input rate for a particular affected unit in a subtractive stack configuration (mmBtu/hr)

NS

- 1 NOX R Hourly NO

x apportionment for NO

x affected units in a subtractive stack configuration (lb/mmBtu)

NS

- 2 NOX R Hourly NO

x apportionment for NO

x affected units using simple NO

x apportionment (lb/mmBtu)



### Formula Text
Element Name: FormulaText

When using a standard formula from Tables 23 through 34, above, leave the Formula Text field blank. The Formula Text element is required only when a non-standard or custom equation is used, i.e., either: (1) one of the equations in Table 35; or (2) another site- specific equation not

listed in Table 37. Use the following guidelines to construct formula text:

● Variables

. In non-standard and custom equations, use recognizable symbols in conjunction with the operators and other representations shown in Table 38. To the extent possible, use symbols and nomenclature consistent with Tables 23 – 34. Use

pa rentheses and square brackets as needed, for added clarity

.

● Formula References

. Wherever another formula in the monitoring plan is part of a nonstandard or custom equation, you may r efer to the other formulas as " F#( XYZ )" where

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 87March 07, 2012 September 19, 2012 9.0 Monitoring Formula Data



### XYZ is the Formula ID

, rather than rewriting the entire text of the formula in the non

standard or custom equation.

● Constants

. Appropriate constants must also be included in each non-standard or custom equation, such as unit conversion factors, fuel factors, etc., that are required for the

calculation.

Table 36 Representations for Electronic Reporting of Formulas

Operation Recommended Representation Example

Addition + MW_1 + MW_2

Subtraction

- (100

- % H 2 O)

Multiplication * C d * F d

Division / %CO 2 /100

Exponential P ower ** 1.66 x 10 - 7 = 1.66 * 10 **

- 7

Subscript Underscore MW 1 = MW_1

Fraction of Heat Input from Fuel X_<fuel> X_oil

Gross Electrical Output MW_<unit> MW_1

Gross Steam Load (Flow) SF_<unit> SF_1

Hourly Emissions E_h E_h

Operating Time T_< unit/stack> T_CS1



### Begin Date
Element Name: Begin Date

Report the date on which the formula was first applied to calculate the data. This date should correspond to the earliest date of the Begin Dates for the systems used in the calculation.

Begin Hour
Element Name: Begin Hour

Report the hour in which the formula was first applied to calculate the data.

End Date
Element Name: EndDate

For formulas that are discontinued due to a change in monitoring, r eport the last date on which

the formula was used to calculate the data. This value should be left blank for active records.

Monitoring Plan Reporting Instructions

-- Page 88 Environmental Protection Agency9.0 Monitoring Formula Data March 07, 201 2 September 19, 2012



### End Hour
Element Name: EndHour

Report the last hour in which the formula was used to calculate the data. This value should be

left blank for active records.

Spe cific Considerations

Required Formulas

● Depending on the monitoring methodologies and component types in use, include in the monitoring plan one or more of the following formulas:

● For CEMS Based Methodologies

-- SO 2 

### mass emission rate

-- NO

x 

### emission rate

-- NO

x 

### mass emission rate

-- CO 2 

### concentration

-- CO 2 

### mass emission rate

-- Heat input rate

-- F- factor proration calculation for mixed fuels (if elected)

-- Flow -weighted or heat input-weighted NO

x 

### emission rate formulas for multiple stacks using two primary NO

x 

### systems

-- Moisture formulas for moisture systems using O 2 

### wet and dry readings

-- Flow formulas for all flow systems containing two flow monitors

● For Fuel Flow Based Methodologies

-- SO 2 

### mass emission rate (ARP)

-- CO 2 

### mass emission rate (ARP)

-- NO

x 

### emission rate for the unit where separate Appendix E single fuel curves were used (Equation E-2)

-- Heat input rate

-- Mass of oil formulas for OILV measurements (ARP)

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 89March 07, 2012 September 19, 2012 9.0 Monitoring Formula Data



### -- Net fuel flow formulas for systems with more than one flowmeter

-- F- factor proration calculation for mixed fuels (if elected)

F- Factors and F -Factor Formulas

● Heat input rate, NO

x 

### emission rate, and CO 2 

### emission rate formulas based on CEMS require the inclusion of a specific F- factor based on the f uel being combusted. If a combination of fuels may be combusted within any given hourly period, two options for calculating emissions are available: (1) use the hig hest F -factor, or (2) use a prorated Ffactor. Calculate prorated F

- factors using Equation F-8 in 40 CFR Part 75, Appendix F. If a pro

- rated F

- factor formula is used, include it in this data set.

Situations That Do Not Require Formulas

● Appendix E units do not need formulas for the NO

x 

### emission rate.

● Units using LME methodology in §75.19 do not need formulas.

● Do not include formulas for cumulative quarterly or annual emissions or heat input.

● Do not provide formulas representing the defa ult heat input rate or default NO

x 

### emission

rate for the unit or stack.

Monitoring Plan Reporting Instructions

-- Page 90 Environmental Protection Agency10.0 Monitoring Default Data March 07, 2012 September 19, 2012



## 10 .0 M ONITOR ING 

## D EFAULT 

## D ATA



### Figure 19

M ONITORING 

### D EFAULT 

### D ATA 

### XML Elements

Description of Data

M ONITOR ING 

### D EFAULT 

### D ATA 

### records define Maximum Values, Minimum Values, Defaults, and

Constants that are used in the Part 75 calculations or in the missing data routines. Report one record for each fuel type and parameter combination to define the applicable emission factor,

moisture conten t, maximum potential value or diluent cap to be used at a monitoring location, as described below.

M ONITOR ING 

### D EFAULT 

### D ATA 

### record s are required for the following situations :

Missing Data Defaults (Default PurposeCode " MD ")

● Maximum NO

x 

### emission rate (MER) for any location using a NO

x 

### - diluent monitoring CEM system.

● Maximum controlled NO

x 

### emission rate (MCR) for bypass stacks or missing data

substitution for hours in which the add -on controls are documented to be operating properly (see §§75.17(d) , 75.31(c)(3), and 75.34(a)(5)).

Environmental Protection Agency Mo nitoring Plan Reporting Instructions

-- Page 91March 07, 2012 September 19, 2012 10.0 Monitoring Default Data



### ● Fuel

- specific maximum potential SO 2 

### or NO

x 

### concentrations (MPCs), maximum potential NO

x 

### emission rates (MERs), or maximum potential flow rates (MPFs), for units using fuel- specific C EMS missing data option under §75.33.

● Fuel

- specific maximum potential SO 2 

### or NO

x 

### concentrations or maximum potential NO

x 

### emission rates, for units with add-on emission controls and unmonitored bypass stacks, if

the fuel -specific MPC or MER is reported during hours when the flue gases are routed through the bypass stack and the add-on controls are either bypassed or not documented to be operating properly (see §§75.16 (c)(3) and 75.17 (d) ).

● Fuel

- specific maximum controlled NO

x 

### concentrations or maximum controlled NO

x 

### emission rates (MCR) , for units with add-on emission controls and unmonitored bypass stacks, if the fuel -specific MEC or MCR is reported during hours when the flue gases are routed through the bypass stack when the add-on emissions controls are not bypassed, are in use, and are documented to be operating properly (see §75.17 (d) ).

● Generic NO

x 

### emission rate defaults for low mass emissions units. Use this value when

NO

x 

### controls are not operating or when default has expired.

● Maximum potential NO

x 

### concentration and emission rate for Appendix E units. Use

maximum emissions rate when NO

x 

### controls are not operating, when burning emergency fuels, or when Appendix E curve has been invalidated or has expired.

● Maximum or minimum potential moisture percentage (required only if monitoring moisture continuously or using a moisture look-up table). U se d for missing data

purposes.

● Minimum emission values for subtractive stack situations, if approved by petition.

● Minimum potential O 2 

### used for missing data purposes.

● Maximum potential CO 2 

### concentration for missing data purposes for unit/stacks using an

O 2 

### monitor to determine CO 2



### .

Low Mass Emissions Defaults (DefaultPurposeCode " LM ")

● Defaults for NO

x 

### , SO 2 

### , and CO 2 

### emission rates for low mass emissions (LME) units under §75.19.

● Defau lt maximum rated hourly heat input rate (mmBtu/hr) for low mass emissions unit s. Use this value if the heat input monitoring method is MHHI or if the substitute data code

for a LTFF unit is MHHI.

Monitoring Plan Reporting Instructions

-- Page 92 Environmental Protection Agency10.0 Monitoring Default Data March 07, 2012 September 19, 2012



### Primary Monitoring Methodology Default (DefaultPurposeCode " PM ")

● Default moisture values from § 75.11(b) or §75.12(b), used to estimate stack moisture content for specific fuels.

● Site

- specific default moisture percentage s, approved by petition under §75.66.

● Moisture Fraction in Ambient Air for use with equation 19-2.

Diluent Cap Default (DefaultPurposeCode " DC ")

● CO 2 

### or O 2 

### diluent cap for NO

x 

### emission rate calculations

.

Default for Use with E quation F-23 (DefaultPurposeCode " F23 ")

● Default SO 2 

### emission rates for units which use Equation F-23 to determine SO 2 

### mass emissions (see § 75.11(e)(1)).

Minimum Fuel Flow Rate Default (DefaultPurposeCode " DM ")

● Default minimum fuel flow rate (refer to the Part 75 Emissions Monitoring Policy

Manual ).

See "Spe cific Considerations" section about when not to report this record.

Dependencies for M ONITORING 

### D EFAULT 

### D ATA



### The M ONITORING 

### D EFAULT 

### D ATA 

### record is dependent on the U NIT 

### D ATA 

### record or the S TACK


### P IPE 

### D ATA 

### record.

No other records are dependent upon the M ONITORING 

### D EFAULT 

### D ATA 

### record.

Environmental Protection Agency Mo nitoring Plan Reporting Instructions

-- Page 93March 07, 2012 September 19, 2012 10.0 Monitoring Default Data



### M ONITORING 

### D EFAULT 

### D ATA 

### Elements

Instructions for completing each element of the M ONITORING 

### D EFAULT 

### D ATA 

### section are provided below:

Parameter Code

Element Name: ParameterCode

Report the parameter for which a default value is defined by using the appropriate uppercase

codes as shown in Table 37:

Table 37 Parameter Codes and Descriptions for Monitoring Default

Category Parameter

Code Description

Diluent Cap CO2N CO 2 Diluent Cap

.

O2X O 2 Diluent Cap

.

Low Mass Emissions Parameters (§ § 75.19 and 75.81(b)) CO2R CO 2 Default Emission Factor, from Table 43 or Fuel

and Unit -S pecific CO 2 Default Emission Factor, for

Combustion of " Other " Gaseous Fuel (tons/mmBtu)

.

NOXR NO

x Default Emission Factor, from Table 41 or Fuel

and Unit

- S pecific NO

x Emission Rate 1 (lb/mmBtu)

.

SO2R SO 2 Default Emission Factor, from Table 42 or Fuel and

Unit -S pecific SO 2 Default Emission Factor Calculated Using Equation D -1h , either (1) for combustion of

" other " gaseous fuel; or (2) for fuel oil combustio n, based on the maximum weight percent sulfur in the operating permit (lb/mmBtu)

.

MHHI Maximum Rated Ho urly Heat Input Rate (mmBtu/hr).

(cont.)

Monitoring Plan Reporting Instructions

-- Page 94 Environmental Protection Agency10.0 Monitoring Default Data March 07, 2012 September 19, 2012



### Table 3 7

Parameter Codes and Descriptions for Monitoring Default (cont.)

Category Parameter

Code Description

Missing Data Values

or

Maximum Values for Unmonitored Bypass Stack and Emergency Fuels H2ON Minimum Pote ntial Percent Moisture

.

H2OX Maximum Potential Percent Moisture

.

CO2X Maximum Percent CO 2

.

O2N Minimum Potential Percent Oxygen

.

SO2X Fuel

- Specific Maximum Potential SO 2 Concentration (ppm)

.

NOCX Fuel

- Specific Maximum Potential (MPC) or Maximum Expected NO

x Concentration (ppm) for all hours or controlled hours. For Appendix E missing data purposes, report the MPC use d to calculate the

Maximum NO

x Emission R ate for each fuel curve and, if applicable, for Emergency fuel.

NORX Maximum NO

x Emission Rate (MER) , MCR, or and

Fuel

- Specific Maximum Potential or Maximum Expected Controlled NO

x Emission Rate (lb/mmBtu) for all hours or controlled hours. For Appendix E missing data purposes, an MER must be determined for each fuel curve and, if applicable, for Emergency fuel

.

F LOX Fuel

- Specific Maximum Potential Flow Rate (scfh)

.

Moisture Default Parameter H2O Ho urly Percent Moisture Content (% H 2 O)

.

BWA M oisture Fraction in Ambient Air.

SO 2 Emission Rate Parameter

f or Use in Formula F

- 23 SO2R SO 2 Generic Default Emission Factor for Pipeline

Natural Gas ; or

Fuel and Unit

- Specific Default Emission Factor Calculated Using Equation D -1h for combustion of

" other " gaseous fuel ; or

Emission Factor approved by petition for a very low

sulfur solid or liquid fuel (or combination of fuels) per § 75.11 (e)

.
Other Parameters ( subject to EPA approval of p etition) MNHI Minimum Heat Input Rate (mmBtu/hr)

.

MNNX Minimum NO

x Emission Rate (lb/mmBtu)

.
Other Parameters (not subject to

EPA a pproval of p etition) MNOF Minimum Oil Flow Rate

.

MNGF Minimum Gas Flow Rate

.

1 Report " NOXR " in the following cases: (1) for fuel

- and

- unit specific NO

x emission rates obtained by testing;

and (2) for the maximum potential NO

x emission rate, if that value is reported in the interval from the first hour of use of the LME methodology until the hour of completion of fuel

- and

- unit specific NO

x emission rate testing (see § 75.19 (a)(4)).

Environmental Protection Agency Mo nitoring Plan Reporting Instructions

-- Page 95March 07, 2012 September 19, 2012 10.0 Monitoring Default Data



### Default Value

Element Name: DefaultValue

Re port the Maximum, Minimum, Default, or Constant Value to be used to the number of decimal places consistent with the corresponding hourly data record.

Table 38 Rounding Rules for Default Values

Round to 0 Round to 1 Round to 2 Round to 3 Round to 4 Round to

Decimal D ecimal Decimal Decimal Decimal Nearest

P lace s P lace P laces P laces P lace s 1000

Parameter CO2N, CO2X, BWA, CO2R, SO2R FLOX

Code s H2O, H2ON, H2OX, MHHI, MNNX, NORX, NOXR MNGF,
MNHI,

MNOF

, NOCX, O2X, O2N, SO2X



### NO

x 

### Maximum Emission Rate (MER)

For a NO

x 

### -diluent monitoring system (lb/mmBtu), calculate and report a maximum potential

NO

x 

### emission rate (MER), based on the MPC value (reported in the Monitoring Span record ) for use with missing data procedures.

Calculate NO

x 

### MER on a unit or stack basis by using one of the following formulas and values:



### 20.9 E = K x C d 

### x F d 

### x 20.9 -% O 2 d



### (Equation F- 5)

Where:

E = Pollutant emissions during unit operation, lb/mmBtu ;
K = 1.194 x 10 -7 

### (lb/dscf)/ppm NO x; 

### C d 

### = NO

x 

### concentration (dry) (use MPC value) ;
F d 

### (dscf/mmBtu) = Dry basis F -factor used for the unit in Monitoring Formula ; and

%O 2 d 

### = Maximum oxygen concentration during normal operating conditions,

or

use the diluent cap value of 14.0 percent O 2 

### for boilers and 19.0

percent O 2 

### for turbines or if MPC is derived from historical data, the

O 2 

### reading recorded at the hour of the MPC may be used.

Monitoring Plan Reporting Instructions

-- Page 96 Environmental Protection Agency10.0 Monitoring Default Data March 07, 2012 September 19, 2012



### 100 E = K x C

w 

### x F

c 

### x % CO 2 w



### (Equation F- 6)

Where:

E = Pollutant emissions during unit operation, lb/mmBtu ;
K = 1.194 x 10 -7 

### (lb/dscf)/ppm NO

x 

### ; C

w 

### = NO

x 

### concentration (wet) (use MPC value) ;
F
c 

### (scf CO 2 

### /mmBtu) = Carbon- based F -factor used for the unit in Monitoring Formula 20 ; and

%CO 2 w 

### = Minimum CO 2 

### concentration during normal operating conditions,

or

use the diluent cap value of 5.0 percent CO 2 

### for boilers and 1.0

percent CO 2 

### for turbines or if MPC is derived from historical data,

the CO 2 

### reading recorded at the hour of the MPC may be used.

Diluent Cap Values

For a CO 2 

### diluent cap value, report 5.0 percent for a boiler or 1.0 percent for a combustion

turbine. For an O 2 

### diluent cap value, report 14.0 percent for a boiler or 19.0 percent for a

turbine.

Moisture Defaults

If using a default value to determine moisture, report fuel- specific moisture default values.

Tables 39 and 40 provide the fuel- specific moisture default values for coal -fired and woodburning units and natural gas-fired boilers. Table 39 provides minimu m default moisture values that are used in all emission (SO 2 

### , NO

x 

### , CO 2 

### ) and heat input rate calculations requiring moisture corrections, except for calculation of NO

x 

### emission rates using Equation 19-3, 19-4, or 19- 8 from EPA Method 19 in Appendix A-7 to 40 CFR 60. If Equation 19-3, 19-4, or 19-8 is used to

calculate NO

x 

### emission rate, use the appropriate maximum default moisture value from Table 40.

If using a monitoring system to determine moisture

, report either the maximum or minimum potential moist ure percentage , depending on whether you use the standard or inverse missing data procedure from Part 75. For the minimum potential moisture percentage, report either a default value of 3.0 percent H 2 

### O or a site -specific value obtained from 720 or more ho urs of historical data. For the maximum potential moisture percentage, report either a def ault value of

15.0 percent H 2 

### O or a site -specific value derived from 720 or more hours of historical data.

Environmental Protection Agency Mo nitoring Plan Reporting Instructions

-- Page 97March 07, 2012 September 19, 2012 10.0 Monitoring Default Data



### Table 39

Fuel

- Specific Minimum Default Moisture Values

for SO 2 

### , NO

x 

### , CO 2 

### , and Heat Input Rate Calculations

Minimum Moisture

Fuel Default Value

Anthracite Coal 3.0%

Bituminous Coal 6.0%

Sub

- bituminous Coal 8.0%

Lignite Coal 11.0%

Wood 13.0%

Natural Gas ( b oilers

o nly) 14.0%



### Table 40

Fuel

- Specific Maximum Default Moisture Values

for NO

x 

### Emission Rate Calculations

Maximum Moisture

Fuel Default Value

Anthracite Coal 5.0%

Bituminous Coal 8.0%

Sub

- bituminous Coal 12.0%

Lignite Coal 13.0%

Wood 15.0%

Natural Gas ( b oilers

o nly) 18.0%



### LME Defaults

Table 41 contains the " generic " default NO

x 

### emission factors for qualifying oil and gas- fired low

mass emissions units under §75.19, which are based on the unit type and the type of fuel

combusted. Unit and fuel- specific NO

x 

### emission rates may be determined for low mass emissions units by emission testing, in lieu of using the defaults in Table 41. For fuel oil combustion, in lieu of using the default values in Table 42, fuel and unit- specific default SO 2 

### emission rates may be determined based on the maximum allowable weight percentage of sulfur in the fuel, as specified in the operating permit (see §75.19(c)(1)(i)). For gaseous fuels other than natural gas, there are no generic default values available. Therefore, fuel and unit- specific emission rates must be determined for all emission parameters.

Monitoring Plan Reporting Instructions

-- Page 98 Environmental Protection Agency10.0 Monitoring Default Data March 07, 2012 September 19, 2012



### Table 41

NO

x 

### E mission Factors (lb/mmBtu) for Low Mass Emissions Units

Boiler Type Fuel Type NO

x Emission Factors

Turbine Natural Gas 0.7

Oil 1.2

Boiler Natural Gas 1.5

Oil 2 .0



### Table 42 contains the Part 75 SO 2 

### emission factors for low mass emissions units

, which are based on the type of fuel combusted.

Table 42

SO 2 

### Emission Factors (lb/mmBtu) for Low Mass Emissions Units

Fuel Type SO 2 Emission Factors

Pipeline Natural Gas (as d efined in § 72.2) 0.0006

Natural Gas 0.06

Residual Oil

or Other Oil 2.1 0

Diesel Fuel 0.5 0



### Table 43 contains fuel

- specific CO 2 

### emission factors for low mass emissions units.

Table 43

CO 2 

### Emission Factors (ton/mmBtu) for Low Mass Emissions Units

Fuel Type CO 2 Emission Factors

Natural Gas 0.059

Oil 0.081

Environmental Protection Agency Mo nitoring Plan Reporting Instructions

-- Page 99March 07, 2012 September 19, 2012 10.0 Monitoring Default Data



### Default Units o f Measure Code

Element Name: Def aultUnitsOfMeasureCode

Report the appropriate measurement units using the appropriate uppercase codes as shown in

Table 44. For Parameter BWA , leave this field blank.

Table 44 Units of Measure Codes by Parameter

Units of

Measure Code Description Parameter Code

PCT Percent CO2 N

, CO2X, H2O, H2O N

, H2OX

, O2 N , O2X

LBMMBTU Pounds p er Million Btu MNNX, NOX R

, SO2R, NORX

MMBTUHR Million Bt u p er Hour MNHI , MHHI

TNMMBTU Tons p er Million Btu CO2 R

SCFH Standard Cubic Feet p er Hour MNOF, FLOX

,

PPM Parts per million SO2X, NOCX

GALHR Gallons of Oil p er Hour MNOF

BBLHR Barrels of Oil p er Hour MNOF

M3HR Cubic Meters of Oil p er Hour MNOF

LBHR Pounds of Oil p er Hour MNOF

HSCF Hundred SCF of Gas p er Hour MNGF

Monitoring Plan Reporting Instructions

-- Page 100 Environmental Protection Agency10.0 Monitoring Default Data March 07, 2012 September 19, 2012



### Default Purpose Code

Element Name: DefaultPurposeCode

Identify the purpose or intended use of the Default Value for reporting and emissions measurement by using the appropriate upp ercase codes as shown in Table 45 :

Table 45 Default Purpose Codes and Descriptions

Code Description Parameter Code

DC Diluent Cap CO2N, O2X

DM Default Minimum Fuel Flow Rate MN GF, MNOF

F23 SO 2 Emission Rate De fault for Use in Equation F

- 23 SO2R

LM Low Mass Emissions Unit Default ( §§ 75.19 and

75.81 (b) ) CO2R, SO2R, NOXR, MHHI

MD Missing Data, Unmonitored Bypass Stack, or Emergency Fuel CO2X , FLO X, H2ON, H2OX,
MNHI, MNNX, NOCX, NORX, O2N, SO2X

PM Primary Measurement Methodology BWA, H2O



### Fuel Code

Element Name: FuelCode

Report the type of fuel associated with the default by using the appropriate uppercase codes as

shown in Table 46. For maximum NO

x 

### emission rate that is not fuel

- specific or f or maximum or minimum potential moisture or O 2 

### / CO 2 

### values , report a Non-Fuel Specific code, or " NFS. "

Table 46 Monitoring Default Fuel Codes and Descriptions

Type Code Description

LME Defaults (§75.19) BFG Blast Furnace Gas

BUT Butane (if measured as a gas)

CDG Coal Derived Gas

COG Coke Oven Gas

DGG Digester Gas

DSL Diesel Oil

LFG Landfill Gas

(cont.)

Environmental Protection Agency Mo nitoring Plan Reporting Instructions

-- Page 101March 07, 2012 September 19, 2012 10.0 Monitoring Default Data



### Table 4 6 Monitoring Default Fuel Codes and Descriptions (cont.)

Type Code Description

LME Defaults (§75.19) (cont.) LPG Liquefied Petroleum Gas (if measured as a gas)

NNG Natural Gas

OGS Other Gas

OIL Residual Oil

OOL Other Oil

PDG Producer Gas

PNG Pipeli ne Natural Gas (as defined in § 72.2)

PRG Process Gas

PRP Propane (if measured as a gas)

RFG Refinery Gas

SRG Unrefined Sour Gas

Moisture ANT Anthracite Coal

BT Bituminous Coal

CRF Coal Refuse (culm or gob)

LIG Lignite

NNG Natural Gas (i ncluding Pipeline Natural Gas)

PNG Pipeline Natural Gas

SUB Sub

- bituminous Coal

W Wood

SO 2 Emission Rate Default for Use in Equation F

- 23 NNG Natural Gas

PNG Pipeline Natural Gas

OGS Other Gas

* or MIX *With an approved petition, any liquid or solid fuel type that qualifies as very low sulfur fuel , or a mixture of such fuels.

See fuel code list in U NIT F UEL D ATA

Fuel

- Specific CEMS Missing

Data BFG Blast Furnace Gas

BUT Butane (if measured as a gas)

C Coal

CDG Coal

- Derived Gas

COG Coke Oven Gas

(cont.)

Monitoring Plan Reporting Instructions

-- Page 102 Environmental Protection Agency10.0 Monitoring Default Data March 07, 2012 September 19, 2012



### Table 4 6 Monitoring Default Fuel Codes and Descriptions (cont.)

Type Code Description

Fuel

- Specific CEMS Missing Data (cont.) CRF Coal Refuse (culm or gob)

DGG Digester Gas

DSL Diesel Oil

LFG Landfill Gas

LPG Liquefied Petroleum Gas (if measured as a gas)

MIX Co

- Fired Fuels

NNG Natural Gas

OGS Other Gas

OIL Residual Oil

OOL Other Oil

OSF Other Solid Fuel

PDG Producer Gas

PNG Pipeline Natural Gas (as defined in §72.2)

PRG Process Gas

PRP Propane (if measured as a gas)

PRS Process Sludge

PTC Petroleum Coke

R Refuse

RFG Refinery Gas

SRG Unrefined Sour Gas

TDF Tire

- Derived Fuel

W Wood

WL Waste Liquid

Fuel

- Specific MPC/MER or MEC/MCR Reporting During Bypass Stack Operating

Hours BFG Blast Furnace Gas

BUT Butane (if measured as a gas)

C Coal

CDG Coal

- Derived Gas

COG Coke Oven Gas

CRF Coal Refuse (culm or gob)

DGG Digester Gas

DSL Diesel Oil

(cont.)

Environmental Protection Agency Mo nitoring Plan Reporting Instructions

-- Page 103March 07, 2012 September 19, 2012 10.0 Monitoring Default Data



### Table 4 6 Monitoring Default Fuel Codes and Descriptions (cont.)

Type Code Description

Fuel

- Specific MPC/MER or MEC/MCR Reporting During Bypass Stack Operating Hours (cont.) LFG Landfill Gas

LPG Liquefied Petroleum Gas (if measured as a gas)

NNG Natural Gas

OGS Other Gas

OIL Residual Oil

OOL Other Oil

OSF Other Solid Fuel

PDG Producer Gas

PNG Pipeline Natural Gas (as defined in §72.2)

PRG Process Gas

PRP Propane (if measured as a gas)

PRS Process Sludge

PTC Petroleum Coke

R Refuse

RFG Refinery Gas

SRG Unrefined Sour Gas

TDF Tire

- Derived Fuel

W Wood

WL Waste Liquid

Monitoring Plan Reporting Instructions

-- Page 104 Environmental Protection Agency10.0 Monitoring Default Data March 07, 2012 September 19, 2012



### Operating Condition Code

Element Name: OperatingConditionCode

If the value is used only for controlled or uncontrolled hours, indicate this using a "C" or " U, " as appropriate (for example, if using separate NORX codes for controlled and uncontrolled operating conditions, use the “C” code for the MCR rate value and “U ” code for the MER rate value)

. If this is a unit

- specific default NO

x 

### emission rate for an LME combustion turbine that has base and peak rates, report "B" or "P" to indicate the operating condition to which this rate applies . Report "A" if the use of th e value is not related to the control status of the unit or base versus peak operation, such as for diluent cap records. Table 47 summarizes operating condition codes and descriptions.

Table 47 Monitoring Default Operating Condition Codes and Descript ions

Operating Condition Code Description

A Any Hour

C Controlled Hour

B Base Load Hour (LME units)

P Peak Load Hour (LME units)

U Uncontrolled Hour



### Default Source Code

Element Name: DefaultSourceCode

Report the means of selecting or determining the Maximum, Minimum, or Constant value by using the appropriate uppercase codes for the paramete rs reported as shown in Table 48:

Table 48 Default Source Codes and Descriptions

Default

Source Code Source of Value Description Parameter

APP * Approved (Petition) MNNX

, SO2 R , MNHI , H2O

, MHHI

DATA* * Historical or Other Relevant Data O2 N

, O2X, CO2X, H2O N

, H2OX, FLOX, SO2X, NOCX, NORX, NOX R , MNOF, MNGF

, BWA

PERM Maximum Weight Percent Sulfur in Fuel Oil, as Specified by Operating Permit (for LME) SO2 R , NORX, NOCX

TEST Unit/Stack Testing NOX R , FLOX, SO2X, NOCX,

Environmental Protection Agency Mo nitoring Plan Reporting Instructions

-- Page 105March 07, 2012 September 19, 2012 10.0 Monitoring Default Data

NORX

(cont.)



### Table 48 Default Source Codes and Descriptions (cont.)

Default

Source Code Source of Value Description Parameter

SAMP Fuel Sampling SO2 R , CO2 R , SO2X

CONT Contract Maximum SO2 R

DEF Default Value from Part 75 CO2 R , NOX R , CO2N, O2X,

SO2 R , H2O N , H2OX, SO2X, NOCX, NORX , H2O

MAXD Maximum Value Based on Design or Nameplate Capacity MHHI , NORX, NOCX

* Report " APP " if you have an approved petition to use a site

- specific SO 2 emission factor for very low sulfur solid or liquid fuels

.

** Report code " DATA " in this field if reporting the maximum potential NO

x emission rate in the interval from the first hour of use of the LME methodology until the hour of completion of fuel

- and

- unit specific

NO

x emission rate testing (see § 75.19 (a)(4)).



### Group ID

Element Name: GroupID

Report data in this field only if the unit is included in a group of identical low mass emissions (LME) units under §75.19. Otherwise, leave this field blank.

Report the Group ID that has been assigned by the Designated Representative, if the default value reported in this M ONITORING 

### D ATA 

### D E FAULT 

### record is a currently

- applicable (i.e., active)

fuel

- and -unit- specific default NO

x 

### emission rate for this unit and for the other units in a group of identical LME units under §75.19.

The default value for the group of identical units must be updated each time that a subset of the group is tested to establish the new default NO

x 

### emission rate (for LME units). The minimum retest frequen cy for LME units is once every five years (20 calen dar quarters).

Begin Date
Element Name: Begin Date

Report the date on which the default became effective for purposes of reporting emissions data

.

Monitoring Plan Reporting Instructions

-- Page 106 Environmental Protection Agency10.0 Monitoring Default Data March 07, 2012 September 19, 2012



### Begin Hour
Element Name: Begin Hour

Report the hour on which the default became effective for purposes of reporting emissions data.

End Date
Element Name: EndDate

Report the date after which the value will no longer be used. Submit a second Monitor Default record with an effective date to report a new value. This value should be left blank for active

r ecords.

End Hour
Element Name: EndHour

Report the hour after which the value will no longer be used. Submit a second Monitor Default record with an effective hour to report a new value. This value should be left blank for active

records.

Specific Considerations

Situations Not Requiring Monitoring Default Data Submission

● Values for CO 2 

### or O 2 

### used to calculate the maximum potential velocity (MPV), which is used to determine the flow rate span value. Submit the information to support flow span calculations in hardcopy with the initial monitoring plan (and store on site). Do not report this information electronically in the EDR.

● Maximum oil and gas fuel flow rate

. These values are defined in S YSTEM 

### F UEL 

### F LOW


### D ATA



### .

● Maximum potential (or maximum expected) SO 2 

### , NO

x 

### , CO 2 

### , or flow rate values, for units using the standard ( non- fuel

- specific (NSF ) ) CEMS missing data routines in §75.33. (These maximum potential and expected values are defined in Monitor Span Data.)

● Default high range value fo r SO 2 

### or NO

x 

### (already defined in monitor span ).

● Default SO 2 

### emission rates for Acid Rain Program units that use Appendix D to account

for SO 2 

### mass emissions from the combustion of gaseous fuel. For these units, report the

default SO 2 

### emission rates in the P ARAMETER 

### F UEL 

### F LOW 

### D ATA 

### record

.

● Appendix D density and GCV values for oil and gas. These values are defined in the

F UEL 

### F LOW 

### D ATA 

### record.

Environmental Protection Agency Mo nitoring Plan Reporting Instructions

-- Page 107March 07, 2012 September 19, 2012 10.0 Monitoring Default Data



### Specific Considerations f or Units Using Equation F -23

● For pipeline natural gas combustion, report 0.0006 lb/mmBtu.

● For other natural gas combustion, report the default SO 2 

### emission rate (lb/mmBtu) calculated using Equation D-1h.

● For gaseous fuels other than natural gas that qualify under Section 2.3.6 of Appendix D

to use a defaul t SO 2 

### emission rate, report the emission rate (lb/mmBtu), calculated using Equation D-1h.

● For very low sulfur solid or liquid fuels or mixtures of these fuels with gaseous fuel, report the custom default SO 2 

### emission rate(s) approved by petition.

Monitoring Plan Reporting Instructions

-- Page 108 Environmental Protection Agency11.0 Monitoring Span Data March 07, 2012 September 19, 2012



## 11 .0 M ONITORING 

## S PAN 

## D ATA



### Figure 20

M ONITORING 

### S PAN 

### D ATA 

### XML Elements

Description of Data

M ONITORING 

### S PAN 

### D ATA 

### contains information concerning the span and range values associated with the continuous emission monitors installed at unit or stack and the time period in which

these values are effective. It also contains information regarding the Maximum Potential an d Maximum controlled values for each parameter monitored.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 109March 07, 2012 September 19, 2012 11.0 Monitoring Span Data



### Dependencies for M ONITORING 

### S PAN 

### D ATA



### The M ONITORING 

### S PAN 

### D ATA 

### record is dependent on the U NIT 

### D ATA 

### record or the S TACK 

### P IPE


### D ATA 

### record.

No other records are dependent upon the M ONITORING 

### S PAN 

### D ATA 

### record.

M ONITORING 

### S PAN 

### D ATA 

### Elements

Instructions for completing each element of the M ONITORING 

### S PAN 

### D ATA 

### section are provided

below:

Component Type Code

Element Name: ComponentTypeCode

Identify the component type ( parameter ) of the monitor using the following uppercase codes:

Table 49 Component Type Codes and Descriptions for Monitor Span

Code Description

CO2 CO 2 Concentration (percent )

FLOW Stack Flow

NOX NO

x Concentration (ppm)

O2 O 2 Concentration (percent )

SO2 SO 2 Concentration (ppm)



### Span Scale Code

Element Name: SpanScaleCode

Report either "H" to indicate high scale or "L" to indicate low scale for SO 2 

### , NO

x 

### , CO 2 

### , or O 2



### . For FLOW leave this field blank.

Monitoring Plan Reporting Instructions

-- Page 110 Environmental Protection Agency11.0 Monitoring Span Data March 07, 2012 September 19, 2012



### Span Method Code

Element Name: SpanMethodCode

Report the method used to determine the maximum potential (or expected) concentration (MPC

or MEC ) or flow rate (MPF) by using the appropriate upp ercase codes as shown in Table 50:

Table 50 Provision for Calculating MPC/MEC/MPF Codes and Descriptions

Code Description

F Formula ( low and high

- scale SO 2 , flow rate, and low

- scale NO

x only)

HD Historical Data

TR Test Results

TB Table of Constants from Part 75 or

Default Values from Part 75 ( e.g. , 800 ppm NO

x for coal

- firing)

OL Other Limit

GS Low Scale Default for SO 2 for Gas

Units

PL NO

x MEC B ased on Permit L imit

ME NO

x MPC B ased on Manufacturer ' s Estimate of U ncontrolled E missions



### Table 51 summarizes the recommended methods for determining MPC/MEC/MPF.

● Submit documentation with the original hardcopy monitoring plan submission and retain files of the supporting information concerning a unit for recordkeeping purposes if using Equations A-1a or A-1b from Appendix A to Part 75 or historical data to determine maximum potential flow (MPF)

.

● Leave th is field blank for O 2 

### records.

● For CO 2 

### , enter a default MPC value o f 14.0 percent CO 2 

### for boilers and 6.0 percent CO 2 

### for turbines. For turbines, an alternative default MPC value below 6.0 percent CO 2 

### may be used if a technical justification is provided in the hard copy monitoring plan. Report a Span Method Code of " TB " if the default value is reported. T he MPC may also be determined based on historical data. If historical data are used (720 hours, m inimum), report the highest %CO 2 

### value observed in the historical look-back period as the MPC.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 111March 07, 2012 September 19, 2012 11.0 Monitoring Span Data



### Table 51

Criteria for M PC /M EC /M PF Determinations

Parameter Scale Method Used to Determine

MPC/MEC/MPF Selection Criteria Method

Code

NO X High 800 or 1600 ppm, as applicable For coal

- fired units TB

400 ppm For oil

- or gas

- fired units TB

2000 ppm Cement kilns TB

500 ppm Process heaters burning oil TB

200 ppm Process heaters burning only gaseous

fuels TB

Historical CEM d ata For initial determination or for changes in

MPC as described in Section 2.1.2.5 of Appendix A HD

Other constant values from Appendix A, Tables 2

- 1 and 2

- 2 If historical data not available by boiler type and fuel TB

Test r esults If historical data not available TR

Other, including other

state /federal requirements As justified OL

Manufacturer = s estimate of

uncontrolled emissions For initial MPC determination, principally for new units ME

Low Equation A

- 2 For units with emission controls F

Historical CEM d ata For initial determination or for changes in

MEC as described in Section s 2.1.2.2(c)

and 2.1.2.5 of Appendix A HD

Other, including other

state /federal requirements As justified OL

Test r esults If available TR

Permit limit For initial MEC determination, principally for new units PL

FLOW N/A Equation A

- 3a and Equation of Continuity * Based on %CO 2 F

Equation A

- 3b and Equation of Continuity * Based on %O 2 F

Historical d ata For changes in MPF, as described in Section 2.1.4.3 of Appendix A HD

Test r esults If available TR

(cont.)

Monitoring Plan Reporting Instructions

-- Page 112 Environmental Protection Agency11.0 Monitoring Span Data March 07, 2012 September 19, 2012



### Table 51

Criteria for MPC/MEC/MPF Determinations (cont.)

Parameter Scale Method Used to Determine

MPC/MEC/MPF Selection Criteria Method

Code

SO 2 High Equation A

- 1a Based on %CO 2 F

Equation A

- 1b Based on %O 2 F

Historical CEM d ata For initial determination or for changes in

MPC as described in Section 2.1.1.5 of Appendix A HD

Test r esults If available TR

Other, including other

state /federal requirements As justified OL

Low Equation A

- 2 For units with emission controls F

Historical CEM d ata For initial determination or for changes in

MEC as described in Section 2.1.1.5 of Appendix A HD



### # 200 ppm (span value) For units burning only very low sulfur fuel (as defined in § 72.2) GS

Other, including other

state /federal requirements As justified OL

* The maximum potential flow rate (MPF) is calculated using the Equation of Continuity: MPF = 60 x MPV x

A

s . In this equation, MPV is the maximum potential velocity (from Equation A

- 3a or A

- 3b or from test results), in units of wet, standard feet per minute, and A

s is the cross

- sectional area of the stack at the flow

monitor location.



### MEC Value

Element Name: MECValue

If required to determine MEC per Part 75, Appendix A, r eport the Maximum Expected Concentration (MEC) value for the location in the SO 2 

### and NO

x 

### span records

. Report MEC for

SO 2 

### and NO

x 

### to one decimal place . Report this value in the high- scale record and, if a low scale is defined, also in the low- scale record. Leave this field blank for other parameters.

MPC Value

Element Name: MPCValue

In the high scale record for NO

x 

### , SO 2 

### , or CO 2 

### , r eport the Maximum Potential Concentration (MPC) value for the location . Report MPC for NO

x 

### or SO 2 

### to one decimal place. For O 2 

### , leave

this field blank.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 113March 07, 2012 September 19, 2012 11.0 Monitoring Span Data



### MPF Value
Element Name: MPFValue

If the span record is for parameter FLOW, r eport the Maximum Potential Flow (MPF) value for

the monitoring location in standard cubic feet per hour (scfh) on a wet basis.

Span Value

Element Name: SpanValue

Report the Span Value determined according to the requirements of Part 75. If using a default high range value for SO 2 

### or NO

x 

### , leave this fiel d blank in the high scale record.

For SO 2 

### and NO

x 

### , high- scale span values must be between 100 percent and 125 percent of the maximum potential concentration, rounded up to the next highest multiple of 100 ppm (or,

alternativ ely, rounded up to the next 10 ppm if 125 percent of MPC is less than 500 ppm). Lowscale span values must be between 100 percent and 125 percent of MEC, rounded upward to the next highest multiple of 10 ppm.

For flow rate, the span value is the calibration span value and must be reported in the units used for daily calibrations. To determine the calibration span value for monitors that are not

calibrated in units of inches of H 2 

### O, first convert the maximum potential velocity (MPV) from

units of wet sta ndard feet per minute (wsfpm) to the units used for daily calibration. Multiply the result by a factor no less than 1.00 and no more than 1.25 and round up, retaining at least two significant figures. For flow monitors calibrated in inches of water, repo rt the calibration span

value to two decimal places.

For CO 2 

### and O 2 

### , report the appropriate percentage (see Part 75, Appendix A, §2.1.3), to the

nearest one percent CO 2 

### or O 2 

### , not ppm.

Full Scale Range

Element Name: FullScaleRange

Report the full- scale range in the units used for daily calibrations for SO 2 

### , NO

x 

### , CO 2 

### , O 2 

### , and

flow rate. As a general guideline, s elect the range such that, to the extent practicable, the majority of the readings obtained during normal operation of the monitor are between 20 and 80 percent of full -scale. See Section 2.1 of Appendix A to Part 75 for allowable exceptions to this guideline. The full- scale range must be greater than or e qual to the span value. L eave this field blank in the high scale Monitoring Span record if using a default high range value for SO 2 

### or NO

x 

### .

Monitoring Plan Reporting Instructions

-- Page 114 Environmental Protection Agency11.0 Monitoring Span Data March 07, 2012 September 19, 2012



### Span Units o f Measure Code

Element Name: SpanUnitsOfMeasureCode

For SO 2 

### and NO

x 

### , report PPM. For O 2 

### and CO 2 

### , report PCT.

For a flow span record, report one of the following uppercase codes to indicate the units used to report and perform daily calibrati ons based on span:

Table 52

Flow Span Calibration Units of Measure

Code Description

ACFH Actual Cubic Feet of Stack Flow p er Hour

ACFM Actual Cubic Feet of Stack Flow p er Minute

AFPM Actual Feet of Stack Flow p er Minute

AMSEC Actual Meters of Stack Flow p er Second

AFSEC Actual Feet of Stack Flow per Second

INH2O Inches of Water

KACFH Tho usand A ctual Cubic Feet of Stack Flow

p er Hour

KACFM Thousand A ctual Cubic Feet of Stack Flow

p er Minute

KAFPM Thou sand Actual Feet of Stack Flow p er Minute

KSCFH Thousand Standard Cubic Feet of Stack

Fl ow p er Hour

KSCFM Thousand Sta ndard Cubic Feet of Stack Flow p er Minute

KSFPM Thousa nd Standard Feet of Stack Flow p er Minute

MACFH Million A ctual Cubic Feet of Stack Flow

p er Hour

MSCFH Million Sta ndard Cubic Feet of Stack Flow

p er Hour

SCFH Standard Cubic Feet of Stack Flow p er Hour

SCFM Sta ndard Cubic Feet of Stack Flow p er Minute

SFPM Standard Feet of Stack Flow p er Minute

SMSEC Standard Meters of Stack Flow p er Second

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 115March 07, 2012 September 19, 2012 11.0 Monitoring Span Data



### Scale Transition Point

Element Name: ScaleTransitionPoint

If a dual range analyzer is installed for NO

x 

### , SO 2 

### or CO 2 

### (see Analyzer range data), report the concentration value at which the DAHS switches from recording on the normal range to recording on the secondary range (usually low to high). Report this value in both the low and high scale records. Scale transition point is not reported for FLOW span.

Default High Range

Element Name: DefaultHighRange

For parameter SO 2 

### or NO

x 

### , if using a default high range, report the actual default value in this field in the high scale record. The defau lt high range value must be 200 percent of the maximum potential concentration. Report this value only in the high scale record for the parameter.

For the parameters CO 2 

### , O 2 

### , or FLOW , leave this field blank.

Flow Span Value

Element Name: FlowSpanValue

For the parameter FLOW, report the flow rate span value in scfh , which is the product of the MPF and a factor no less than 1.00 and no greater than 1.25. This factor must be the same one that was used to determine the calibration span value. Round the flow rate span value upward to the next highest 1000 scfh.

Flow Full Scale Range

Element Name: FlowFullScaleRange

Report the actual full

- scale range value expressed in units of scfh for the parameter FLOW. The

flow rate full

- scale range value must be greater than or equal to the flow rate span value.

Begin Date
Element Name: Begin Date

Report the date that the current span value became effective for reporting emissions data.

If you have elected to use a default high range value for SO 2 

### or NO

x 

### , r eport the date on which the default high range was implemented in the DAHS.

Begin Hour
Element Name: Begin Hour

Report the hour that the current span value became effective for reporting emissions data.

If you have elected to use a default high range value for SO 2 

### or NO

x 

### , r eport t he hour on which the default high range was implemented in the DAHS.

Monitoring Plan Reporting Instructions

-- Page 116 Environmental Protection Agency11.0 Monitoring Span Data March 07, 2012 September 19, 2012



### End Date
Element Name: EndDate

Report the last date on which the span record was in effect. Leave this field blank for active span

records. If a span change was made , report both the original span record with the appropriate end date and the new span record with the appropriate begin date.

End Hour
Element Name: EndHour

Report the last hour in which the span record was in effect . Leave this field blank for active span

records

.

Specific Considerations

CEMS Methodology

● If you are using a CEMS methodology, M ONITORING 

### S PAN 

### D ATA 

### must be included for each parameter ( e.g. , NOX, SO2, CO2, O2, or FLOW) that is measured with CEMS. Note that for units that combust more than one type o f fuel, the maximum potential concentration (MPC) values reported in M ONITORING 

### S PAN 

### D ATA 

### are based solely on the fuel that produces the highest pollutant concentration or emission rate. Therefore, if you

elect to use one of the fuel

- specific missing data options in §75.33, 75.16(c)(3), or 75.17(d)(2), in addition to reporting the "conventional" MPC or MER values in

M ONITORING 

### S PAN 

### D ATA 

### , you must report a fuel -s pecific maximum potential value for

each of the other fuels , using M ONITORING 

### D EFAULT 

### D ATA



### .

Dual Ranges and Separate M ONITORING 

### S PAN 

### D ATA 

### Records

● If SO 2 

### , NO

x 

### , CO 2 

### , or O 2 

### emission concentrations vary such that dual ranges are required ( e.g. , due to fuel switching or emission controls), provide separate Monitoring Span Data

records for the low scale and high scale values.

High Scale and Low Scale Span Records

● If you elect to use a default high range value (200 percent of MPC for SO 2 

### or NO

x 

### )

instead of calibrating and maintaining a high monitor range for hours in which emissions

exceed the fu ll

- scale of the low range , submit both high scale and low scale span records, but in the high scale record, only report values for the following elements: the MPC

, Begin Date and Begin Hour, the activation date and hour of the default high range value,

an d Default High Range (the default high range value of 200 percent of MPC).

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 117March 07, 2012 September 19, 2012 11.0 Monitoring Span Data



### DP -Type Flow Monitors Calibrated in Units of Inches of H 2 

### O

● For DP -type flow monitors that are calibrated in units of inches of H 2 

### O, select a value between 100 percent and 125 percent of the MPV. Then convert that value from units of wet, standard feet per minute ( wsfpm ) to units of wet actual feet per second (wafps). Then use Equation 2-7 in EPA Reference Method 2 (40 CFR 60, Appendix A-1 ) to convert the actual velocity to an equivalent delta-P value in inches of H 2 

### O. Retain at least two decimal places in the delta -P value. In performing these calculations, the values of stack temperature, stack pressure, stack gas molecular weight and the pitot tube coefficient may be estim ated based on the results of previous emission testing.

Updating the M ONITORING 

### S PAN 

### D ATA 

### Record

When any value i n a M ONITORING 

### S PAN 

### D ATA 

### record change s, update the information by reporting both the original span record with the appropriate end date and the new span record with the appropriate begin date.

If you have discontinued the use of a default high range value for SO 2 

### or NO

x 

### in favor of using a

sp an value, report in the old record the last date and hour on which the default high range was in use. In the new record, report the date and hour on which the new span value became effective. If changing from a span value to a default high range value fo r SO 2 

### or NO

x 

### , report the date on which the default high range was implemented in the DAHS.

In order to correct a previously submitted record that contains erroneous information, resubmit

the M ONITORING 

### S PAN 

### D ATA 

### record with the corrected information.

Monitoring Plan Reporting Instructions

-- Page 118 Environmental Protection Agency12.0 Rectangular Duct WAF Data March 07, 2012 September 19, 2012



## 12 .0 R ECTANGULAR 

## D UCT 

## WAF D ATA



### Figure 2 1

R ECTANGULAR 

### D UCT 

### WAF D ATA 

### XML Elements

Description of Data

Submit a R ECTANGULAR 

### D UCT 

### WAF D ATA 

### record for rectangular ducts or stacks with installed flow monitors, in which a wall effects adjustment factor (WAF) was determined using Conditional Test Method CTM-041 and applied to the hourly flow rate data. Conditional Test

Method CTM-041 is used to either:

● Determine a site

- specific default WAF; or

● Make wall effects measurements and calculate an average WAF, based on three or more

test runs.

If you elect to measure wall effects, the measurements may be made at any load level (low, mid

or h igh) and may either be coupled with the test runs of a flow RATA or may be made separately. Once a default or measured WAF has been determined, it may be entered into the programming of the flow monitor as a correction to the cross- sectional area of the rectangular stack or duct, thereby adjusting the measured stack gas flow rates for wall effects. Then, when a

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 119March 07, 2012 September 19, 2012 12.0 Rectangular Duct WAF Data



### subsequent RATA of the flow monitor is performed, the same WAF that is being used to correct the flow monitor readings should be applied to the reference method test data.

All units/stacks currently applying a wall effects correction obtained using CTM -041 to flow rate data must report a R ECTANGULAR 

### D UCT 

### WAF D ATA 

### record in each quarterly submission. For units not presently applying a wall effects correction, if you intend to begin using a WAF, report this record after the WAF has been determined and prior to the next quarterly file that uses that

WAF.

If a new WAF test has been performed (because the stack or ductwork is altered such that the flow profile is significantly changed), report two R ECTANGULAR 

### D UCT 

### WAF D ATA 

### records : one that ends the record that is no longer effective, and one that reports the new wall effects adjustment factor data.

Dependencies for R ECTANGULAR 

### D UCT 

### WAF D ATA



### The R ECTANGULAR 

### D UCT 

### WAF D ATA 

### record is dependent on the U NIT 

### D ATA 

### record or the

S TACK 

### P IPE 

### D ATA 

### record.

No other records are dependent upon the R ECTANGULAR 

### D UCT 

### WAF D ATA 

### record.

R ECTANGULAR 

### D UCT 

### WAF D ATA 

### Elements

Instructions for completing each element of the M ONITORING 

### L OCATION 

### A TTRIBUTE 

### D ATA 

### section are provided below:

WAF Determination Date

Element Name: WAFDeterminationDate

Report the date the WAF was determined. Unless you are a first time user of CTM -041, this date must be on or prior to the WAF Begin Date. First time users of CTM -041 may retroactively apply the rectangular duct WAF back to January 1 of the year in which the rectangular duct

WAF determination is made , unless the flow profile changed significantly during that period. Therefore, f or first

- time users, the WAF Begin Date may be earlier than the WAF Determination

Date.

WAF Begin Date

Element Name: WAFBeginDate

Report the date on which the WAF was first applied to the flow rate data.

WAF Begin Hour

Element Name: WAFBeginHour

Report the hour in which the WAF was first applied to the flow rate data.

Monitoring Plan Reporting Instructions

-- Page 120 Environmental Protection Agency12.0 Rectangular Duct WAF Data March 07, 2012 September 19, 2012



### WAF Method Code

Element Name: WAF MethodCode

Report the appropriate WAF Method Code displayed in Table 53 to indicate the WAF calculation approach.

Table 53

WAF Method Code and Descriptions

Code Description

FT Full Test (CTM

- 041 § § 8.1 and 8.2)

AT Abb reviated Test (CTM

- 041 § 8.4.1)

DF Default Value (CTM

- 041 § 8.4.2)



### WAF Value

Element Name: WAFValue

Report the WAF applied to the flow rate data, to four decimal places, with a leading zero ( e.g.
, 0.9750).

Number of Test Runs

Element Name: NumberOfTestRuns

Report the number of runs in the WAF test (must be one for default WAF and at least three for a measured WAF).

Number of Traverse Points WAF

Element Name: NumberOfT raversePointsWAF

Report the number of Method 1 traverse points in the WAF test runs.

Number of Test Ports

Element Name: NumberOfTestPorts

Report the number of test ports at which measurements were made during the WAF test runs.

Number of Traverse Points Reference

Element Name: NumberOfTraversePointsRef

Report the number of Method 1 traverse points in the " reference " flow RATA test runs. The reference flow RATA is either the RATA that accompanied the CTM -041 determination, or if the WAF was determined separately from a RATA, the RATA that most recently preceded the

WAF determination. Consistent with CTM -041, the num ber of this data element for the

" reference " flow RATA and for all subsequent flow RATAs must equal the Number of Traverse

Points WAF data element, for the WAF test run(s). If you wish to increase the number of

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 121March 07, 2012 September 19, 2012 12.0 Rectangular Duct WAF Data



### Method 1 traverse points used in a subsequent flow RATA, you must re- determine the WAF using an equal number of Method 1 traverse points.

Duct Width

Element Name: DuctWidth

Report the width of the rectangular duct at the test location ( i.e. , dimension L

x 

### in Figure 1 of

CTM -041), to the nearest 0.1 ft.

Duct Depth
Element Name: DuctDepth

Report the depth of the rectangular duct at the test location (i.e. , dimension L y 

### in Figure 1 of

CTM -041), to the nearest 0.1 ft.

WAF End Date

Element Name: WAFEndDate

Report the date on which the WAF was last applied to the flow rate data. Leave this field blank if this WAF is still being applied.

WAF End Hour
Element Name: WAFEndHour

Report the hour in which the WAF was last applied to the flow rate data. Leave this field blank

if this WAF is still b eing applied.

Monitoring Plan Reporting Instructions

-- Page 122 Environmental Protection Agency13.0 Monitoring Load Data March 07, 2012 September 19, 2012



## 13 .0 M ONITORING 

## L OAD 

## D ATA



### Figure 22

M ONITORING 

### L OAD 

### D ATA 

### XML Elements

Description of Data

The M ONITORING 

### L OAD 

### D ATA 

### record identifies the maximum load, the lower and upper

boundar ies of the range of operation and, if applicable, the normal load level(s) for a unit or other monitoring location. Report this record for every unit, stack, and pipe in the monitoring plan.

Dependencies for M ONITORING 

### L OAD 

### D ATA



### The M ONITORING 

### L OAD 

### D ATA 

### record is dependent on the U NIT 

### D ATA 

### record or the S TACK 

### P IPE


### D ATA 

### record.

No other records are dependent upon the M ONITORING 

### L OAD 

### D ATA 

### record.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 123March 07, 2012 September 19, 2012 13.0 Monitoring Load Data



### M ONITORING 

### L OAD 

### D ATA 

### Elements

Instructions for completing each element of the M ONITORING 

### L OAD 

### D ATA 

### section are provided

below:

Maximum Load Value

Element Name: MaximumLoadValue

This value is required for all units and all additional monitoring locations with the exception of

non-load based units

. Define the maximum hourly gross load associated with the unit, stack, or pipe at full capacity:

● For boilers and simple cycle turbines (including units with multiple stack exhaust configurations), this value is based on one of the follo wing: (1) the nameplate capacity; (2) the nameplate capacity as derated; or (3) a value higher than nameplate, if the unit or stack historically operates at levels exceeding nameplate.

● For common stack (or common pipe) configurations, the maximum load will be the highest sustainable combined operating load for the units serving the common stack (or pipe).

● For multiple stacks, report the maximum hourly gross load for the associated unit.

● Determine the total maximum hourly gross load according to the guidelines in the Part 75 Emissions Monitoring Policy Manual for combined cycle (CC) combustion turbine units. For combined cycle combustion turbines where the HRSG produces steam, the equivalent load for the HRSG must be included in the maximum hourly gross load determination. Express the total unit load on a consistent basis, i.e., either in terms of electrical or steam

load.

● Leave this field blank for units that do not produce electrical or steam load.

Monitoring Plan Reporting Instructions

-- Page 124 Environmental Protection Agency13.0 Monitoring Load Data March 07, 2012 September 19, 2012



### Maximum Load Units of Measure Code

Element Name: MaximumLoadUnitsOfMeasureCode

Identify the type of load information reported in this record by using the appropriate uppercase codes as shown in Table 54. Note that you must use the same units of m easure as will be used to report hourly load.

Table 54 Maximum Load Value Codes and Descriptions

Code Description

MW Electrical Capacity (in megawatts)

KLBHR Steam (load) Mass Rate (in units of 1000 lbs/hr)

MMBTUHR BTUs of Steam P roduced (in

mmBtu/ hr)

Note: Leave this field blank for units that do not produce electrical or steam load.



### Lower Operation Boundary

Element Name: LowerOperationBoundary

This value is required for all units and all additional monitoring locations where load- based missing data are used. Report the lower boundary of the range of operation for units that produce electrical or steam load, in units of megawatts, 1000 lb/hr of steam or mmBtu/hr of steam, as appropriate.

For single units (including units that have a multiple stack exhaust configuration), report the minimum safe, sustainable load for the unit.

For a common stack (or pipe), report the lowest safe, sustainable load for any of the units using the stack (or pipe) as the lower boundary of the range of operation. Alternatively, for frequently operated units discharging to a common stack (or using a common pipe), the sum of the

min imum safe, stable loads of the units serving the common stack (or pipe) may be reported as the lower boundary of the operating range.

For multiple stacks, report, the minimum safe, stable load for the associated unit.

For non load-based units, report the lower boundary of the range of operation in terms of stack gas velocity (ft/sec), as described in Section 6.5.2.1(a) of Appendix A.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 125March 07, 2012 September 19, 2012 13.0 Monitoring Load Data



### Upper Operation Boundary

Element Name: UpperOperationBoundary

This value is required for all units and all additional monitoring locations where load- based missing data are used. Report the upper boundary of the range of operation for units that

pr oduce electrical or steam load, in units of megawatts , 1000 lb/hr of steam, or mmBtu/hr of

steam, as appropriate. The upper boundary of the range of operation must be equal to or less than the maximum hourly gross load reported in the Maximum Load Value.

Report the maximum sustainable load for single units (including units that have a multipl e stack exhaust configuration), to either : (1) the nameplate capacity of the unit (less any physical or regulatory deratings); or (2) the highest sustainable load, based on a minimum of four representative quarters of historical operating data.

Report the sum of the maximum sustainable lo ads of all units using the stack (or pipe) f or a common stack (or pipe), as the upper boundary of the range of operation. If that combined load is unattainable in practice, report the highest sustainable combined load, based on a minimum of four represent ative quarters of historical operating data.

For multiple stacks, report the maximum sustainable load for the a ssociated unit.

For non load-based units, report the upper boundary of the range of operation in terms of stack gas velocity (ft/sec)

, as desc ribed in Section 6.5.2.1(a) of Appendix A.

Normal Level Code

Element Name: NormalLevelCode

This value is required for all units and all additional monitoring locations where load- based missing data are used, except for peaking units or stacks linked to peaking units. Designate and report the most frequently used load level ( " L, " " M, " or "H" ) as the "normal" load level f or units that produce electrical or steam load, based upon the results of the historical load data analysis

described in Section 6.5.2.1(c) of Appendix A. For all SO 2 

### , NO

x 

### , and flow RATAs conducted at the designated normal load, a bias test is required.

For non load-based units, designate the normal operating level based on knowledge of the unit and operating experience with the industrial process.

Second Level Code

Element Name: SecondLevelCode

This value is required for all units and all additional monitoring locations where load- based missing data are used, except for peaking units or stacks linked to peaking units. Report the second most frequently used level base d on the results of the histo rical load data analysis

described in Section 6.5.2.1(c) of Appendix A (for units that produce electrical or steam load), or, based on knowledge of the unit and operating experience with the industrial process (for non

load -based units).

Monitoring Plan Reporting Instructions

-- Page 126 Environmental Protection Agency13.0 Monitoring Load Data March 07, 2012 September 19, 2012



### Second Normal Indicator

Element Name: SecondNormalIndicator

This value is required for all units and all additional monitoring locations where load- based missing data are used, except for peaking units or stacks linked to peaking units. For units that produce electrica l or steam load, based upon the results of the historical load data analysis, the

second most frequently used load level may be elected to be designated as an additional normal load level. If you wish to designate the second most frequently used operating level as a second

normal level , report "1" for this element. Otherwise, report "0". Note that if you designate the

second level as a normal level , you must perform a bias test for all SO 2 

### , NO

x 

### , and flow RATAs

conducted at this load level.

For non load-based units, a second normal operating level may be designated, based on knowledge of the unit and operating experience with the industrial process.

Load Analysis Date

Element Name: LoadAnalysisDate

Report the year, month and day of the historical load data analysis (see Section s 6.5.2.1 (c) and (d) of Appendix A) that defines the two most frequently used load levels, and the normal load level(s) for units that produ ce electrical or steam load.

L eave this field blank for new units since no load analysis has yet been completed.

Leave this field blank for non load-based units.

Begin Date
Element Name: Begin Date

Report the date on which the load information became effective . For the initial load ana lysis at a particular unit or stack, report the Begin Date as the first day of the quarter in which the data analysis was performed (i.e., 2005-01-01 or 2005-04- 01, etc.), rather than the actual date of the analysis unless the two dates are the same. For records created to indicate a change to the load information, t his date should equal the load analysis date if the change is based on a new load analysis . But, if you are simply elect ing to add a second normal load or to make minor adjustments to the boun daries of the operating range, or updating other information that is not dependent on the load analysis , the Begin Date may be later than the load analysis date

.

For peaking units, report the later of: (a) the date of program participation; or (b) the date on which peaking status was first claimed for the unit.

For non load-based units, report the date on which the determination of the operating range, the most frequent operating level(s), and the norm al operating level(s) is made.

Begin Hour
Element Name: Begin Hour

Report the hour in which the load information became effective

.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 127March 07, 2012 September 19, 2012 13.0 Monitoring Load Data



### End Date
Element Name: EndDate

Report the last date on which the load information was in effect. Report an end date only when

another M ONITORING 

### L OAD 

### D ATA 

### record will be reported to provide a change to one or more

data element s , either because a new historical load data analysis was performed which indicated a change , or because you elect to change the second normal load designation or the range of operation. When this occurs, submit one M ONITOR ING 

### L OAD 

### D ATA 

### record with the results of the previous load data analysis and report the end date in this field. Submit a second M ONITORING


### L OAD 

### D ATA 

### record with the results of the new load data analysis or choice , leaving this field

blank (see " Specific Consi derations" below)

.

For non load-based units, report an end date only when a change in the manner of unit or process operation results in a change in the operating range and/or the most frequently- used operating levels, and/or the designated normal operating level(s). Should this occur, submit two

M ONITOR ING 

### L OAD 

### D ATA 

### records, one to deactivate the old information, and one to activate the

new in formation, as described immediately above for load-based units.

End Hour
Element Name: EndHour

Report the last date on which the load information was in effect. This value should be left blank

for active records.

Specific Considerations

Range of Operation for Electrical or Steam Load Units and Non Load- Based Units

● M ONITOR ING 

### L OAD 

### D ATA 

### defines the upper and lower boundaries of the "range of operation" for the unit (or units, for a common stack or pipe). For units that produce electrical or steam load, the range of operation extends from the minimum safe, stable operating load to the maximum sustainable load, and provides the basis for defining the low, mid, and high operating load levels. For non load-based units (e.g., cement kilns, refinery process heaters, etc.), the range of operation extends from the minimum potential stack gas velocity, in ft/sec (or, alternatively, from 0.0 ft/sec) to the maximum potential velocity.

Purpose of Historical Load Data Analysis

● M ONITOR ING 

### L OAD 

### D ATA 

### is also used to report the results of an analysis of historical load data for the unit or stack, as described in Part 75 (see Section 6.5.2.1(c) of Appendix A). The results of the historical load data analysis provide the basis for: (1) defining the normal operating load level (or levels) for the unit or stack; (2) determining the two appropriate load levels at which to conduct annual two-load flow RATAs; (3) determining, for multi -load flow RATAs, the two appropriate load levels at which to calculate bias adjustment factors, when a normal load bias test is failed; and (4) determining the appropriate load level at which to conduct the quarterly flow- to -load ratio test. Note that for peaking units, the historical load data analysis is not required.

Monitoring Plan Reporting Instructions

-- Page 128 Environmental Protection Agency13.0 Monitoring Load Data March 07, 2012 September 19, 2012



### Histor ical Load Data Analysis for Non Load- Based Units

● Non load- based units are exempted from the historical load data analysis in Section

6.5.2.1 (c) of Appendix A. For these units, the most frequently used operating levels and the normal operating level(s) are determined by the owner or operator, using sound engineering judgment, based on operating experience with the unit and knowledge of the industrial process.

Upper and Lower Boundaries for New or Newly

- Affected Units

● For new or newly- affected units , in the initial monitoring plan submittal, use the best available estimates of the upper and lower boundaries of the range of operation and determine the normal load (or operating level) and the two most frequently-used load (or operating) levels based on the anticipated manner of operating the unit. Report the date of submittal of the initial monitoring plan or the date on which commercial operation of the unit begins (whichever is earlier) in the Begin Date field.

Updating the M ONITORING 

### L OAD 

### D ATA 

### Record

When the manner of operating the unit(s) changes significantly, update the information in

M ONITOR ING 

### L OAD 

### D ATA 

### by submitting two M ONITOR ING 

### L OAD 

### D ATA 

### records. First, close out the existing monitor load record by entering an end date and hour. Next, create a new monitor load record indicating the Begin D ate and Hour for the new record.

In order to correct a previously submitted record that contains erroneous information, resubmit

the M ONITORING 

### L OAD 

### D ATA 

### record with the corrected information. For example, if the Normal Level Code was previously submitted as "H" (for high -load) when the normal load level should

have be "M" (for mid -load), the record should be updated and resubmitted. Note that the Begin Date and Begin Hour elements should not be updated, unless the Begin Date and/or Begin Hour are the elements to be corrected.

Once the operating range and normal load level(s) have been established, Part 75 does not require repeating the historical load analysis unless a significant change in the manner of unit operation occurs, which may result in a re-designation of the operating range and/or the normal load level(s) and/or the two most frequently used load levels. At least two quarters of representative data are required to document that such a change in unit operation has occurred. If such a change has been determined, establish the new load information by creating a new

M ONITORING 

### L OAD 

### D ATA 

### record with the new information, and report the old record with the appropriate End Date and End Hour (which must be just prior to the Begin Date and Begin Hour of the new record).

If, however, you elect to repeat the load analysis periodically, e.g., prior to each annual RATA, in order to confirm that nothing has changed (this is good practice, even though this is not required by the regulation), do not change the Begin Date unless the new data analysis shows

that a re -designation of the operating range and/or the normal load and/or the two most frequently- used load levels is necessary.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 129March 07, 2012 September 19, 2012 13.0 Monitoring Load Data



### For peaking units, if peaking status is lost at the end of a year or ozone season, the M ONITORING


### L OAD 

### D ATA 

### record information must be deactivated as of December 31 (for a year -round reporter) or September 30 (for an ozone season- only reporter) of that year. Then, you must perform a historical load analysis and activate a new M ONITORING 

### L OAD 

### D ATA 

### record, as described in the Load Analysis data element instructions above.

When transitioning from non-peaking status to peaking unit status at the beginning of a n ew calendar year or ozone season, deactivate the existing M ONITORING 

### L OAD 

### D ATA 

### record, as of December 31 of the previous year (for a year -round reporter) or September 30 of the previous year (for an ozone season-only reporter). Then, activate a new M ONITORING 

### L OAD 

### D ATA 

### record, as of January 1 of the current year (for a year-round reporter) or October 1 of the previous year (for an ozone season-only reporter). A new load analysis is not required, because the whole operating range is considered normal for a peaking unit. Therefore, in the new M ONITORING


### L OAD 

### D ATA 

### record, leave Normal Level Code through Second Level Indicator data elements

blank. A M ONITORING 

### Q UALIFICATION 

### P ERCENT 

### D ATA 

### record must also be submitted, to claim peaking unit status.

Monitoring Plan Reporting Instructions

-- Page 130 Environmental Protection Agency14.0 Monitoring Qualification Data March 07, 2012 September 19, 2012



## 14 .0 M ONITORING 

## Q UALIFICATION 

## D ATA



### Figure 23

M ONITORING 

### Q UALIFICATION 

### D ATA 

### XML Elements

Description of Data

Report a M ONITORING 

### Q UALIFICATION 

### D ATA 

### record for a unit for which qualification is sought

as a gas -fired unit or a peaking unit, or to use the low mass emissions (LME) monitoring and reporting provisions in §75.19. A separate record must be submitted for each type of qualification sought. F or example, two separate rec o rd sets must be submitted for a single unit to
indicate both gas- fired and peaking unit status . Also include the appropriate Monitoring Qualification records providing the historical or projected information to demonstrate peaking,

gas

- fired , or LME status. See instructions for M ONITORING 

### Q UAL 

### LME D ATA 

### and M ONITORING 

### Q UAL 

### P ERCENT 

### D ATA 

### for more information.

To indicate that a unit or stack has an approved petition to perform flow RATAs at only a single load or two loads, report this record with applicable Qual Type Code (PRATA1 or PRATA2).

Dependencies for M ONITORING 

### Q UALIFICATION 

### D ATA



### The M ONITORING 

### Q UALIFICATION 

### D ATA 

### record is dependent on the U NIT 

### D ATA 

### record or the

S TACK 

### P IPE 

### D ATA 

### record.

The following complex elements specify additional qualification data and are dependent on the

M ONITORING 

### Q UALIFICATION 

### D ATA 

### record:

● M ONITORING 

### Q UAL 

### LME D ATA



### ● M ONITORING 

### Q UAL 

### P ERCENT 

### D ATA



### The complex elements cannot be submitted for a monitoring plan unless an applicable

M ONITORING 

### Q UALIFICATION 

### D ATA 

### record is included.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 131March 07, 2012 September 19, 2012 14.0 Monitoring Qualification Data



### M ONITORING 

### Q UALIFICATION 

### D ATA 

### Elements

Instructions for completing each element of the M ONITORING 

### Q UALIFICATION 

### D ATA 

### section are provided below:

Qu alification Type Code

Element Name: QualificationTypeCode

Report a code from the Table 55 specifying the type of qualification being sought:

Table 55 Qualification Type Codes and Descriptions

Category Code Description

Gas

- Fired GF Gas

- Fired Qualification

Low Mass Emitter LMEA Low Mass Emitter Qualification (Annual)

-- Required when reporting on a year

- round basis

LMES Low Mass Emitter Qualification ( Ozone Season )

-­ Required when subject to an Ozone

- Season NO

x program

Peaking PK Peaking Unit Qualification (Annual)

SK Peaking Unit Qualification for Ozone Season (applies exclusively to sources that report on an ozone season

- only basis)

QA Test Exemption PRATA1 Single Load RATA Q ualification by petition approval

PRATA2 Two Load RATA Q ualification by petition approval

COMPLEX Exemption from Flow

- to

- Load Testing Due to Complex

C onfiguration

LOWSULF SO 2 RATA Exemption for a Source Combusting Only Very Low Sulfur Fuel



### Begin Date
Element Name: Begin Date

Report the date on which qua lification will become effective.

For gas -fired and peaking unit qualifications and for LME qualifications , this should equal the first date on which the qualification is needed for monitoring and reporting purposes. It must be no later than the begin date of any M ONITOR ING 

### M ETHOD 

### D ATA 

### record that depends on the qualification.

For Flow RATA qualifications, this date should be equal to or earlier than the first RATA which relies on the petition provisions.

Monitoring Plan Reporting Instructions

-- Page 132 Environmental Protection Agency14.0 Monitoring Qualification Data March 07, 2012 September 19, 2012



### For Flow

- to -Load exemptions, this date should be equal to the completion date of the first flow RATA that qualifies for the exemption.

End Date
Element Name: EndDate

If applicable, r eport the date on which the qualification ended.

For gas -fired and peaking unit qualifications and for LME qualifications, this would be the last day of the calendar year (or ozone season) in which the qualification was lost

. This date triggers the requirement to meet new monitoring and reporting requirements within the specifi ed time allowed by Part 75.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 133March 07, 2012 September 19, 2012 14.0 Monitoring Qualification Data



### [This page intentionally left blank.]

Monitoring Plan Reporting Instructions

-- Page 134 Environmental Protection Agency14.1 Monitoring Qual LME Data March 07, 2012 September 19, 2012



## 14 .1 M ONITORING 

## Q UAL 

## LME D ATA



### Figure 24

M ONITORING 

### Q UAL 

### LME D ATA 

### XML Elements

Description of Data

Report M ONITORING 

### Q UALIFICATION 

### D ATA 

### records to provide the initial evidence that a unit qualifies for low mass emissions (LME) status. If the unit reports on a year-round basis, report a

MONITORING QUALIFICATION DATA 

### record with a QualificationTypeCode of " LMEA " and three supporting M ONITORING 

### Q UAL 

### LME D ATA 

### records (one for each required QualificationDataYear). If the unit is subject to an ozone-season NOx program (e.g., CAIROS, NBP, etc.), report a MONITO RING QUALIFICATION DATA record with a QualificationTypeCode of "LMES" and three supporting MONITORING QUAL LME DATA records (one for each required QualificationDataYear).

If the unit reports on a year-round basis, and is also subject to an ozone-season NO

x 

### program, the unit must report both sets of records and meet both the annual and ozone- season emissions limits to qualify for LME status.

See Table 56 for more information about which MONITORING QUALIFICATION DATA 

### records to report and which elements must be filled out in the associated M ONITORING 

### Q UAL 

### LME D ATA


### records

.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 135March 07, 2012 September 19, 2012 14.1 Monitoring Qual LME Data



### Table 56

Data Requirements for Monitoring Qual LME

Reporting Frequency Program Applicability Linked to M ONITORING Q UALIFICATION D ATA
R ecord with Quali ficationTypeCode:

LMEA LMES

SO 2 Tons NO

x Tons SO 2 Tons NO

x Tons

Annual Subject to Acid Rain Program (or CAIRSO2 plus CAIRNOX), but not s ubject

to Ozone Season NO

x Program  

Do not report LMES

record

Subject to Acid Rain Program (or CAIRSO2 plus CAIRNOX), and also s ubject

to Ozone Season NO

x Program  

-­ 

Subject to CAIRSO2, but not subject to any NO

x Program 

-­ Do not report LMES

record

Subject to Ozone Season

NO

x program and reporting

year

- round, but not subject to

CAIRSO2 -­ 

-­ 

Subject to CAIRNOX, but not subject to CAIRSO2 or Ozone Season NO

x program -­  Do not report LMES

record

Ozone Season

O nly Subject to Ozone Season

NO

x program and reporting during Ozone Season only Do not report LMEA

record -­ 



### Dependencies for M ONITORING 

### Q UAL 

### LME D ATA



### The M ONITORING 

### Q UAL 

### LME D ATA 

### record is dependent on the M ONITORING 

### Q UALIFICATION


### D ATA 

### record.

No other records are dependent upon the M ONITORING 

### Q UAL 

### LME D ATA 

### record.

Monitoring Plan Reporting Instructions

-- Page 136 Environmental Protection Agency14.1 Monitoring Qual LME Data March 07, 2012 September 19, 2012



### M ONITORING 

### Q UAL 

### LME D ATA 

### Elements

Instructions for completing each element of the M ONITORING 

### Q UAL 

### LME D ATA 

### section are provided below:

Qualification Data Year

Element Name: QualificationDataYear

Report the calendar year used for the measured, estimated, or projected SO 2 

### and/or NO

x 

### mass emissions.

Operating Hours

Element Name: OperatingHours

Report the number of unit operating hours (as defined in §72.2) for the Qualification Data Period (i.e., full year or ozone season) in the Qualification Data Year.

SO 2 

### Tons
Element Name: SO2Tons

If this record is linked to a M ONITORING 

### Q UALIFICATION 

### D ATA 

### record with a QualificationTypeCode of " LMEA ", and the unit is subject to an SO 2 

### program, report the SO 2 

### mass emissions for the Qualification Data Year based on either measured or estimated SO 2 

### mass emissions or projected SO 2 

### mass emissions, as appropriate according to § 75.19. Round and report this value to one decimal place.

Otherwise, l eave this field blank.

NO

x 

### Tons
Element Name: NOxTons

If this record is linked to a M ONITORING 

### Q UALIFICATION 

### D ATA 

### record with a QualificationTypeCode of " LMEA ", and the unit is subject to a NO

x 

### program and is reporting

year -round, r eport the annual NO

x 

### mass emissions for the Qualification Data Year based on

either measured or estimated NO

x 

### mass emiss ions or projected NO

x 

### mass emissions, as appropriate according to §75.19. Round and report this value to one decimal place.

If this record is linked to a M ONITORING 

### Q UALIFICATION 

### D ATA 

### record with a QualificationTypeCode of " LMES ", and the unit is subject to an ozone- season NO

x 

### program, report the seasonal NO

x 

### mass emissions for the Qualification Data Year based on either

measured or estimated NO

x 

### mass emissions or projected NO

x 

### mass emissions , as appropriate according to § 75.19. Round and report this value to one decimal place.

Otherwise, leave this field blank.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 137March 07, 2012 September 19, 2012 14.1 Monitoring Qual LME Data



### Specific Considerations

SO 2 

### Mass Emissions Reduction Program Units

● Use this record type to qualify as a low mass emissions unit by demonstrating that the

unit emits no more than 25 tons o f SO 2 

### per year

.

NO

x 

### Mass Emissions Reduction Program Units

● For a unit subject to a program with a seasonal NO

x 

### emission cap, use this record type to qualify as a low mass emissions unit by demonstrating that the uni t emits no more than

50 tons of NO

x 

### per ozone season.

● For a unit that reports NO

x 

### mass emission data year -round, use this record to qualify as a low mass emissions unit by demonstrating that the unit emits < 100 tons of NO

x 

### per year.

Data Projections

Projections may be used, as necessary, for Year 1, Year 2, or Year 3 (or for Ozone Season 1, 2, or 3), when:

● Actual measured data (e.g., EDR reports) or reasonable estimates of actual emissions derived from other sources (e.g., Part 60 monitoring data, process operating data, fuel usage records, etc.) are not available (e.g., for a new un it);

● One or more of the past three years is not representative of current unit operation (e.g., if controls were recently installed); or

● The owner or operator takes a f ederally enforceable p ermit restriction on unit operating

hours.

Historical Data

● If only historical data are being used to qualify, Year 1 would be three years before the Qualification Data Year (i.e., the year of the LME application (see §75.19(a)(2)).

● If only projected data are being used, Year 1 would be the calendar year of the Qualification Data Year (i.e., the year of the LME application).

● If only historical data are being used, Year 3 would be one year before the Qualification

Data Year or if o nly projected data were being used, Year 3 would be two years after the Qualification Data Year (i.e., the year of the LME application).

● The appropriate calendar years for Ozone Seasons 1, 2, and 3 are determined in a similar

manner.

Monitoring Plan Reporting Instructions

-- Page 138 Environmental Protection Agency14.1 Monitoring Qual LME Data March 07, 2012 September 19, 2012



### LME Attainment Fai lure

● If a qualifying LME unit emits more than the allowable number of tons of SO 2 

### or NO

x 

### in a particular year or ozone season, the unit loses its LME status. Should this occur, the owner or operator must install and certify monitoring systems in a time ly manner, as described in §75.19 (b)(2)

.

● If LME status is lost, update the M ONITORING 

### Q UALIFICATION 

### D ATA 

### record by completing the end date. Also submit a M ONITORING 

### M ETHOD 

### D ATA 

### record indicating changes in monitoring methodologies with the appropriate effective dates.

LME Emission Testing

● For information on emission testing of a group of identical LME units, refer to the U NIT


### D EFAULT 

### T EST 

### S UMMARY 

### D ATA 

### record instructions in t he QA Certification Data section of the reporting instructions.

Updating the M ONITORING 

### Q UAL 

### LME D ATA 

### Record

This record is not designed to be updated from year to year. Rather, on going LME status is demonstrated by the cumulative SO 2 

### and NO

x 

### mass emissions reported in the hourly emissions records. Changes to this data should only be necessary if the unit loses its LME status or needs additional qualification records based on a change in program applicability or a change in reporting frequenc y.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 139March 07, 2012 September 19, 2012 14.1 Monitoring Qual LME Data



### [This page intentionally left blank.]

Monitoring Plan Reporting Instructions

-- Page 140 Environmental Protection Agency14.2 Monitoring Qual Percent Data March 07, 2012 September 19, 2012



## 14 .2 M ONITORING 

## Q UAL 

## P ERCENT 

## D ATA



### Figure 25

M ONITORING 

### Q UAL 

### P ERCENT 

### D ATA 

### XML Elements

Description of Data

Report this record in conjunction with the M ONITORING 

### Q UALIFICATION 

### D ATA 

### record to support the qualifications of a peaking unit or gas- fired unit. For any year or ozone season in which a unit qualifies as a peaking or gas-fired unit, submit a M ONITORING 

### Q UAL 

### P ERCENT 

### D ATA 

### record documenting the capacity or fuel usage of the unit during a three year period. "Peaking unit" is defined in 40 CFR 72.2 for an annual basis and is described in 40 CFR 75.74(c)(11) for an ozone

season basis. " Gas

- fired " is defined in 40 CFR 72.2. Do this for any regulatory purpose ( i.e.

, either for the selection of monitoring methodology, exemption from multi-load testing, or frequency of on- going QA/QC activities).

Dependencies for M ONITORING 

### Q UAL 

### P ERCENT 

### D ATA



### The M ONITORING 

### Q UAL 

### P ERCENT 

### D ATA 

### record is dependent on the M ONITORING 

### Q UALIFICATION


### D ATA 

### record.

No other records are dependent upon the M ONITORING 

### Q UAL 

### P ERCENT 

### D ATA 

### record.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 141March 07, 2012 September 19, 2012 14.2 Monitoring Qual Percent Data



### M ONITORING 

### Q UAL 

### P ERCENT 

### D ATA 

### Elements

Instructions for completing each element of the M ONITORING 

### Q UAL 

### P ERCENT 

### D ATA 

### section are provided below:

Qualification Year

Element Name: QualificationYear

Report the year for which qualification is sought.

Average Percentage Value

Element Name: AveragePercentageValue

Report the average of the three years ' Percentage V alues.

Year 1 Qualification Data Year
Element Name: Yr1 QualificationDataYear

Report the calendar year or season represented by Year 1

.

Year 1 Qualification Data Type Code

Element Name: Yr1 QualificationDataTypeCode

Report one of the following codes that describe the type of percent data for Year 1 supporting qualification as a peaking unit or gas -fired unit:

Table 57 Qualification Data Type Code and Descriptions

Code Description

A Actual Percent Capacity Factor or Fuel Usage

P Projected Capacity Factor or Fuel Usage

D 720 Hours of Unit Operating Data (gas

- fired only)



### Year 1 Percentage Value
Element Name: Yr1 PercentageValue

Report the percent capacity factor or the percent of heat input from gaseous fuel for Year 1.

Monitoring Plan Reporting Instructions

-- Page 142 Environmental Protection Agency14.2 Monitoring Qual Percent Data March 07, 2012 September 19, 2012



### Year 2 Qualification Data Year

Element Name: Yr 2QualificationDataYear

Report the calendar year or season represented by Year 2.

Year 2 Qualification Data Type Code

Element Name: Yr 2QualificationDataTypeCode

Report one of the codes from Table 57, above, that describe s the type of percent data for Year 2 supporting qualification as a peaking unit or gas-fired unit:

Year 2 Percentage Value
Element Name: Yr2 PercentageValue

Report the percent capacity factor or the percent of heat in put from gaseous fuel for Year 2.

Year 3 Qualification Data Year

Element Name: Yr3 QualificationDataYear

Report the calendar year or season represented by Year 3.

Year 3 Qualification Data Type Code

Element Name: Yr3 QualificationDataTypeCode

Report one of the codes from Table 57, above, that describe s the type of percent data for Year 3 supporting qualification as a peaking unit or gas-fired unit:

Year 3 Percentage Value
Element Name: Yr3 PercentageValue

Report the percent capacity factor or the percent of heat input from gaseous fuel for Year 3.

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 143March 07, 2012 September 19, 2012 14.2 Monitoring Qual Percent Data



### Specific Considerations

Qualifying Using Historical and/or Projected Data

● Provide three years of historical percent capacity factor or fuel usage information using projected data as provided for in the definitions of gas-fired and peaking unit in §72.2.

● For a unit in a NO

x 

### mass emissions reduction program reporting on an ozone season -only basis, provide ozone season capacity factor information for the period from May 1 through September 30 of each year. Year 1 should be the earliest year for which data are reported (for example, if all historical data are being used, Year 1 would be three years before the current calendar year or, if all projected data were being used, Y ear 1 would be the current calendar year). Similarly, Y ear 3 should be the last year for which data are reported (for example, if all historical data are being used, Year 3 would be one year before the current calendar year or if all projected data were being used, Y ear 3 would be two years after the current calendar year).

● Calculate the three year average annual capacity factor or percentage of the annual heat input (HI) from the combustion of gaseous fuel, by averaging the percent capacity factor (or percent of HI from gaseous fuel) for the three years of data provided. For example, if a unit has operated for three years at 6.0 percent, 10.0 percent, and 12.0 percent annual capacity factor, report each of these values as a Percentage Value element.

Table 58 Example Data for Qualification Based on Historical and Projected Data

Initial Qualifying Methodology Data Reported in M ONITORING Q UAL P ERCEN T D ATA R ecord

Current

Year Year 1 Type * Year 2 Type * Year 3 Type *

Actual Historical

Data 2000 1997 A 1998 A 1999 A

2001 1998 A 1999 A 2000 A

2002 1999 A 2000 A 2001 A

Projected Data 2000 2000 P 2001 P 2002 P

2001 2000 A 2001 P 2002 P

2002 2000 A 2001 A 2002 P

2003 2000 A 2001 A 2002 A

Combination of

Actual Historical Data and Projected

Data 2001 2000 A 2001 P 2002 P

2002 2000 A 2001 A 2002 P

2003 2000 A 2001 A 2002 A

* A = Actual historical data; P = Projected data

Monitoring Plan Reporting Instructions

-- Page 144 Environmental Protection Agency14.2 Monitoring Qual Percent Data March 07, 2012 September 19, 2012



### Peaking and Gas

- Fired Unit Qualification

● If reporting to qualify both as a peaking unit and as a gas-fired unit, submit two

M ONITORING 

### Q UALIFICATION 

### D ATA 

### records, one with QualificationTypeCode of GF (gas -fired) and one with QualificationTypeCode of PK or SK. With each, report the appropriate M ONITORING 

### Q UAL 

### P ERCENT 

### D ATA 

### record to demonstrate that the unit meets the gas

- fired or peaking unit criteria.

Qualifications for Gas

- Fired Units

● In accordance with paragraph (3)(ii)(B) of the "gas- fire d" definition in §72.2, 720 hours of unit operating data may be provided to initially qualify as a gas-fired unit, if the designated representative certifies that the pattern of fuel usage has permanently changed.

● A unit is classified as gas

- fired as of the date on which the results of the 720 hour demonstration are submitted to the Administrator (see paragraph (3)(iii) of " gas

- fired " definition). The 720 hour demonstration data qualifies a unit as gas- fired from the date

on which the results of the d emonstration are submitted until the end of that same calendar year.

● For the next year, actual, historical fuel usage data must be submitted from the previous year (beginning with the date on which gas- fired qualification was first met) to verify that fuel usage requirements were met for the first reporting year.

● For example, if qualified based on the 720 hour demonstration as of June 30, 2000, then, in 2001, historical data must be submitted for the time interval from June 30, 2000 through Decemb er 31, 2000 (labeled as Year 1). In 2002, historical data would be submitted for 2000 (labeled as Year 1) and 2001 (labeled as Year 2). In 2003, historical data would be submitted for 2000, 2001, and 2002, labeled as Year 1, Year 2, and Year 3, respectively (see Table 59 , below).

Table 59 Example of Gas- Fired Qualification Based on Unit Operating Data

Initial Qualifying Methodology Data Reported in M ONITORING Q UAL P ERCENT D ATA R ecord

Current

Year Year 1 Type Year 2 Type Year 3 Type

Qualifying Based

on 720 Hours of Unit Operating 2000 2000 D ** 2001 P 2002 P

2001 2000 A 2001 P 2002 P

Data 2002 2000 A 2001 A 2002 P

After the first year, available

historical data must be provided. 2003 2000 A 2001 A 2002 A

** Initial qualification based on 720 hours of unit operating data

Environmental Protection Agency Monitoring Plan Reporting Instructions

-- Page 145March 07, 2012 September 19, 2012 14.2 Monitoring Qual Percent Data



### Initial and Subsequent Qualification

● It is possible a unit may initially qualify as a gas -fired or peaking unit by using historical data or projected data. A combination of historical and projected data may be used. However, to maintain peaking unit or gas- fired unit status, actual capacity factor or fuel usage data for each subsequent year must be reported. Thus, if the basis for qualifying in the first reporting year is on three years of projections, it is not poss ible to re -qualify in the second reporting year based solely on projections. The qualifying data for the second reporting year must include the actual capacity factor or fuel usage data from the first reporting year

.

Loss of Status

● If, after evaluating the capacity factor or fuel usage data for a particular reporting year, the unit no longer qualifies as a peaking or gas-fired unit, update the M ONITORING 

### Q UAL


### D ATA 

### record by reporting the appropriate End Date, to indicate that the peaking or gasfired u nit status has been lost.

● If a unit has previously qualified as a peaking or gas-fired unit but has lost that status and

re -establishing peaking or gas- fired status is wished, the unit may only re

- qualify based on three years of actual historical data . The use of projections is disallowed in such cases (see §72.2, paragraph (4) of " gas

- fired " definition and paragraph (3) of the "peaking unit" definition).

Updating the M ONITORING 

### Q UAL 

### P ERCENT 

### D ATA 

### Record

For each unit, as applica ble, add another M ONI TORING 

### Q UAL 

### P ERCENT 

### D ATA 

### record at the beginning of each calendar year (for year -round reporters) or at the start of the ozone season (for

ozone season- only reporters) to demonstrate on-going qualification, based on the previous year (or ozone season) of historical data

.

Monitoring Plan Reporting Instructions

-- Page 146 Environmental Protection Agency