QA - Flow Rate Verification¶
40 CFR Part 58 Appendix A sections 3.2.3, 3.3.2, and 3.3.4.1 describe requirements for a one-point flow rate verification check on automated and manual monitors used to measure PM10, PM10-2.5, PM2.5, and Pb (Pb-TSP and Pb-PM10). To perform the flow rate verification check, the monitor’s normal flow rate is checked using a certified flow rate transfer standard. This check is performed at different frequencies depending on the type of monitor being used. For manual method hi-vol samplers, flow rates must be verified on at least a quarterly basis. For manual method lo-vol samplers, flow rates must be verified on at least a monthly basis. For automated methods, flow rates must also be verified monthly.
Particulate monitors using automated methods usually sample continuously and report hourly average values as raw data to AQS. When this check is performed, if the hourly average raw data value is not available for reporting, then a null value and null data code is reported for that hour. The known flow rate of the transfer standard, and the measured (or indicated) value from the monitor, are recorded by the operator for entry into AQS for that monitor on that date. For manual monitors, the check is performed prior to or after sampling so there is no data loss.
A field by field description of the Flow Rate Verification transaction follows.
Examples:
QA|I|Flow Rate Verification|0145|06|067|0010|81102|4|20200121|1|122|118|16.7|16.63
QA|I|Flow Rate Verification|0055|TT|905|9021|88101|1|20200102|1|145|118|16.7|16.5
Format¶
Seq. |
Name |
Description |
Formatting Rules |
Required |
Key |
---|---|---|---|---|---|
1 |
Quality Assurance transaction identifier. |
Must = QA |
Always |
||
2 |
Indicator for Insert, Update, or Delete action. |
Must = I, U, or D |
Always |
||
3 |
Indicates the specific QA assessment associated with the transaction. |
Must = Flow Rate Verification |
Always |
Y |
|
4 |
Agency Code of organization performing assessment. |
Must exist in AGENCIES reference table. |
Optional; defaults to user agency |
||
5 |
The FIPS state code of the monitor, or “TT” to indicate that the next field on the transaction is a Tribal code. |
Must exist in STATES Reference Table or be ‘TT’ for Tribal Site |
Always |
Y |
|
6 |
The FIPS County Code of the site. If the previous field on the transaction contains “TT”, then the Tribal Code of the site. |
Must exist in COUNTIES (for state) or TRIBAL_AREAS Reference table |
Always |
Y |
|
7 |
Four digit number to uniquely identify site in county and/or tribe. |
Must exist in SITES table with {State Code, county Code} or Tribal Code |
Always |
Y |
|
8 |
The AQS parameter code assigned to the monitor in AQS. |
Must exist in PARAMETERS reference table. |
Always |
Y |
|
9 |
Parameter Occurrence Code: One or two digit number identifying a specific monitor for a parameter at the site. |
Must exist in MONITOR table for non-Insert actions. |
Always |
Y |
|
10 |
Date that the assessment was performed |
YYYYMMDD. |
Always |
Y |
|
11 |
A unique number associated with an assessment performed at a site on a given day. Value should be “1” unless additional same assessments are performed. |
Integer. |
Always |
Y |
|
12 |
The sampling methodology of the monitor being assessed. |
Must exist in SAMPLING METHODOLOGIES reference table. |
Insert |
||
13 |
Units associated with the assessment. |
Must exist in UNITS reference table, and unit code must be for Flow units type. |
Unless Delete |
||
14 |
The measured flow rate provided by the monitor being assessed. |
Decimal. |
Insert |
||
15 |
The flow rate of the flow transfer standard. |
Decimal. |
Insert |