DATA REVIEW AND VALIDATION - arb.ca.gov · SOP VC600 Data Review, Verification, and Validation...

STANDARD OPERATING PROCEDURE

FOR

DATA REVIEW AND VALIDATION

SOP VC600

First Edition

MONITORING DIVISION

November 2018

Approval of Standard Operating Procedure (SOP)

Title: Data Review, Verification, and Validation

SOP: VC600, First Edition

Approval: This SOP has been reviewed and approved by:

____________________________ 11/30/2018

Mallory Ham Date

Manager, Monitoring Division

SOP VC600 Data Review, Verification, and Validation

First Edition, November 2018 Page 1 of 40

TABLE OF CONTENTS

Data Review, Verification, and Validation

Page Date

List Of Acronyms 3

1.0 General Description 4 11/18

1.1 Purpose 4

1.2 Personnel Qualifications and Responsibilities 4

2.0 Data Acquisition 6 11/18

2.1 Data Collection 7

2.2 Data Storage 7

3.0 Enabling/Disabling Channels in Site Data Loggers 8 11/18

3.1 Enabling/Disabling Channels in 8832 Data Loggers 8

4.0 Using AirVision to Review and Edit Data 10 11/18

4.1 Logging onto AirVision 10

4.2 Running Data Reports in AirVision 10

4.3 Accessing/Editing Data Using AirVision Editors 12

4.4 AQS Null Codes, AirVision Data Flags, and AQS 13

Qualifier Codes

5.0 Ongoing Review to Minimize Data Loss 19 11/18

6.0 Monthly Data Review 21 11/18

6.1 General Guidelines on Data Review 22

6.2 Level 1 Data Review 23



6.5 AQS Submissions and Reports 36

7.0 Annual Data Certification 37 11/18

8.0 References 40 11/18



FIGURES Page

Figure 1 Data Collection, Review, and Validation Flow Chart 6

Figure 2 Report Generation Screen 11

Figure 3 Data Editor Screen 13

Figure 4 Monthly Data Review Chain of Custody 22

Figure 5 Level 1 Data Review Check Sheet 30



Figure 8 Data Certification Letter 39

TABLES Page

Table 1 Commonly used AirVision Reports 11

Table 2 Commonly used Qualifier Codes and Events 14

Table 3 AQS Null Codes 14

Table 4 AirVision Data Flags 16

Table 5 AQS Qualifier Codes 17

Table 6 Required QC Tasks and Frequency 25

Table 7 Gas Parameter Warning and Invalidation Limits 26

Table 8 Meteorological Parameter Validation 26

and Corrective Action Limits

Table 9 PM10/2.5 QC Invalidation Criteria 27

Table 10 Minimum Allowable Hourly Values 27

Table 11 PM10/2.5 Sample Volume Validation Criteria 28



LIST OF ACRONYMS

ADVP Automated Data Validation Processor

AQS Air Quality Systems

AutoCal Automated verification test for gaseous analyzers

AV AirVision (DMS/DAS)

BAM Beta Attenuation Monitor

CARB California Air Resources Board

CFR Code of Federal Regulations

COC Chain of Custody

CV Coefficient of Variation

DAS Data Acquisition System

DMS Data Management System

ENSC Environmental Network Service Center

ESC Environmental System Corporation

EPA United States Environmental Protection Agency

LC10 Local Conditions PM10

MDL Minimum Detectable Limit

MDR Monthly Data Review

NO Nitric Oxide

NO2 Nitrogen Dioxide

NOx Oxides of Nitrogen

O3 Ozone

PAMS Photochemical Assessment Monitoring Stations

PM2.5 Particulate Matter less than 2.5 µm in diameter

PM10 Particulate Matter less than 10 µm in diameter

PQAO Primary Quality Assurance Organization

PREC Precipitation

Qstd Standard Flow Rate

R & R Roles and Responsibilities document between PQAO and VCAPCD

SDHD Standard Deviation of Horizontal (Wind) Direction

SOP Standard Operating Procedure

TEMPI Indoor Temperature

TEMPO Outdoor Temperature

VCAPCD Ventura County Air Pollution Control District

VOC Volatile Organic Compounds



1.0 General Description

The Ventura County Air Pollution Control District (VCAPCD) air monitoring program

collects real-time pollutant values and meteorological values of ambient air throughout

Ventura County. The program is designed to ensure the quality of the data collected by

VCAPCD, through California Air Resources Board’s (CARB) Primary Quality Assurance

Organization (PQAO) authority. The data generated is used to determine areas of

Ventura County in attainment or non-attainment of federal and state air quality

standards, and the severity of air pollution in Ventura County. The data also is used in

air models and for real-time air quality public alerts.

This Standard Operating Procedure (SOP) contains details on performing data

acquisition, editing, and revisions in AirVision, the data management system utilized at

VCAPCD, and also the general elements that should be evaluated during the multi-step

data review, verification, and validation process.

Data review, verification and validation are techniques used to accept, reject, or qualify

data in an objective and consistent manner. Verification can be defined as confirmation,

through provision of objective evidence, that specified requirements have been fulfilled

(for example that QC checks were performed at the required interval). Validation can be

defined as confirmation, through provision of objective evidence, that the requirements

for a specific intended use are fulfilled (for example that the results of QC checks are

within the allowable tolerance).

1.1 Purpose

The purpose of this document is to outline how VCAPCD monitoring staff are to handle,

store, edit, and review ambient air quality data before releasing the data for use by

various end-users. This SOP should be used in conjunction with the AirVision manual

and is not intended to replace it.

1.2 Personnel Qualifications and Responsibilities

Operation of the AirVision DAS and any data processing and editing should only be performed by properly trained personnel. Personnel should meet all minimum requirements and qualifications commensurate with their position or title. Qualifications for the respective staff functions are typically first established through the successful completion of a probationary period with supervisorial oversight. Successive levels of responsibility are achieved via internal and external training classes, experience and a demonstrated display of abilities until a “journey level” is attained.



Staff at all levels of data review must have a very good working knowledge of AirVision.

Staff should review the AirVision Manual, train with existing staff on use of the software,

and when available, participate in AirVision training by Agilaire staff.

Level 1 data reviewers must have a thorough understanding of the equipment used to

collect the data in the field at the monitoring sites, as well as familiarity with

characteristics of each site they are reviewing. Level 2 and Level 3 data reviewers must

have a good working knowledge of the U.S. Environmental Protection Agency (EPA) Air

Quality System (AQS). AQS contains ambient air pollution and meteorological data

collected by EPA, state, local, and tribal air pollution control agencies. AQS also

contains descriptive information about each monitoring station (including its geographic

location and its operator), and data quality assurance/quality control information. The

station operator has the primary responsibility for distinguishing valid measurements

from indications caused by malfunctioning instruments or source interference (e.g.,

roofing, gasoline vapors, or structure fires) for all pollutant measurements. The staff

meteorologist has the primary responsibility for distinguishing valid measurements from

malfunctioning meteorological sensors or erroneous meteorological data. The station

operator/staff meteorologist is responsible for daily review of minute, hourly, and

calibration data on an ongoing basis to minimize any data loss. Additionally, the station

operator/meteorologist performs the monthly Level 1 data review. A second reviewer,

either the data processing specialist or one of the other station operators, is responsible

for the monthly Level 2 data review that consists of reviewing the work performed by the

site operators/meteorologist and serve as the second level data reviewer to ensure that

data is of sufficient quality outlined in the Code of Federal Regulations (CFRs), Title 40,

Appendix A to part 58, to be deemed “data for record.” A third reviewer, typically either a

different station operator, or the data processing specialist, provide further review and

oversight by performing the monthly Level 3 data review. The Monitoring Manager

provides further oversight to ensure all maintenance and repair actions are fully

documented, that the stations are being properly maintained, and that the instruments

are operated within acceptable criteria.

http://agilaire.com/solutions-for/airvision/

https://www.epa.gov/aqs/aqs-users-guide-0



2.0 Data Acquisition

The task of data acquisition involves retrieving ambient air quality data from each

analyzer/sampler/sensor, transmitting the data from the field stations to the VCAPCD,

and ingesting the data into a central database. Station operators and data validation

staff are then able to review the air quality data. Figure 1 shows VCAPCD data flow

from acquisition to submittal to the EPA.

Figure 1: Data Collection, Data Review, and Data Validation Process

Gas Analyzers and

Meteorological Sensors

BAM Particulate

Monitors

ESC 8832Data Logger

Agilaire AirVision Central

Data System

Level 1 Review

Level 2 Review

Level 3 Review

Upload to AQS



2.1 Data Collection

The Environmental Systems Corporation (ESC) 8832 data logger and the Met One Beta

Attenuation Monitor (BAM) 1020 PM sampler collect raw data. The ESC 8832 retrieves

and stores data from analyzers and meteorological sensors. The BAM 1020 stores PM

concentrations and PM sampler metadata. The raw data are polled hourly by the central

Data Acquisition System (DAS). The files are transmitted via an Ethernet connection

back to the office where they are stored. In the event of an intermittent communication

failure, an automatic back poll is conducted to retrieve missing data. If the automatic

back poll is unsuccessful, staff may initiate a manual poll.

The station data loggers are programmed to collect concentration and meta data from

ozone and NOx analyzers utilizing general serial interface (GSI) digital methodology.

Additionally, concentration data from these analyzers are also collected by standard

analog acquisition. The analog and digital concentration values are compared to

ensure the digital concentration data accurately reflects analyzer response. The data

loggers are programmed to collect meteorological data by standard analog acquisition.

2.2 Data Storage

The central Data Acquisition System utilized by VCAPCD, AirVision was developed by Agilaire, Inc., using Microsoft SQL server database. AirVision and all associated data base tables reside on a server maintained at VCAPCD’s office. VCAPCD staff utilizes AirVision client software to review, edit, and generate reports of air quality data stored by AirVision in the SQL database. The SQL database is regularly backed up to off-site storage.



3.0 Enabling/Disabling Channels in Site Data Loggers

This section is a means of quickly navigating through the 8832 data logger for the purpose of disabling or enabling a data channel. Enabling and disabling data channels are critical to alert real-time data users of the condition of instrumentation prior to releasing the data to the public. Data channels should be disabled prior to maintenance, repair, extended testing, audits, or calibrations. Note that typical site set up of the data logger/site calibrator automatically flag the appropriate channel when a calibration sequence is triggered. Refer to the appropriate data logger manual to set up a data logger, installing/removing instrumentation from a station, or other operations. BAM samplers automatically disable concentration data and indicate the reason through bad status bits whenever they are taken offline for maintenance, calibration, or other reasons. AirVision automatically applies the correct data flag to BAM data based on the flag mapping function.

3.1 Enabling/Disabling Channels in 8832 Data Loggers ESC 8832 data loggers have the ability to continue data acquisition, but flag data as either disabled “D” or in maintenance “M”. Disable a Channel:

1. Select Disable/Mark Channel Offline (hot key M) from the Channel Configuration Menu. A list of existing channels will display.

2. The first channel in the list will automatically be highlighted. Select or deselect individual channels by highlighting the desired channel name and pressing the Spacebar. An indicator (>) will appear next to a selected channel name. If you need to select all channel names, press <Ctrl><A>. If you need to deselect all channel names, press <Ctrl><D>.

3. Press <Enter> to disable the selected channels. Their data readings will be marked with a “D” validation flag. If you want to exit the screen without disabling any channels, press <Esc> to exit.

Enable a Channel:

1. Select Enable/Mark Channel Online (hot key E) from the Channel Configuration Menu. A list of existing disabled channels will display. If no channels are disabled, a message indicating this fact will display instead of a list.

2. Select or deselect individual channels by highlighting the desired channel name and pressing the spacebar. An indicator (>) will appear next to a selected channel name. Press <Ctrl><A> to select all channel names in the list. Press <Ctrl><D> if you need to deselect all channel names in the list.

3. Press <Enter> to enable all selected channels. Their data readings will no longer be marked with a “D” validation flag. If you want to exit the screen without disabling any channels, press <Esc> to exit.



Putting Channels in Maintenance: 1. Select “Put Channel In Maint.” (hot key I) from the Channel Configuration Menu.

A list of existing channels will display. 2. Select or deselect individual channels by highlighting the desired channel name

and pressing the Spacebar. An indicator (>) will appear next to a selected channel name. Press <Ctrl><A> to select all channel names in the list. Press <Ctrl><D> if you need to deselect all channel names in the list.

3. Press <Enter> to put selected channels into maintenance. Their data readings will be marked with an “M” validation flag. If you want to exit the screen without putting any channels into maintenance, press <Esc> to exit.

Taking Channels out of Maintenance:

1. Select “Take Channel Out Of Maint.” (hot key O) from the Channel Configuration Menu. A list of existing channels in maintenance will display. If no channels are in maintenance, a message indicating this fact will display instead of a choose list.

2. Select or deselect individual channels by highlighting the desired channel name and pressing the spacebar. An indicator (>) will appear next to a selected channel name. Press <Ctrl><A> to select all channel names in the list. Press <Ctrl><D> if you need to deselect all channel names in the list.

3. Press <Enter> to take all selected channels out of maintenance. Their data readings will be no longer be marked with an “M” validation flag. If you want to exit the screen without taking any channels out of maintenance, press <Esc> to exit.



4.0 Using AirVision to Review and Edit Data

This section is a description of the features in AirVision used to review and edit data.

Refer to Agilaire’s AirVision Manual for a more thorough description of the features and

functions of the software.

4.1 Logging onto AirVision

Each staff member is assigned a unique user name and password to access AirVision.

Per request from the Monitoring Division manager, authorized Monitoring Division or IT

personnel grants access to the AirVision by establishing the login credentials for each

first-time user. This function requires administrative permissions to the AirVision security

utilities.

To login, the authorized user double-clicks the AirVision icon on the assigned Windows

desktop. The AirVision login is automated and secured by the user’s Windows operating

system authentication. This allows the users to bypass entering AirVision user and

password information every time they open AirVision software if they are logged into

their PCs using their personal authorized windows authentication. The main AirVision

screen will open after a short automated logon period.

4.2 Running Data Reports in AirVision

Under the main menu, from the home tab, under the reports icon, a dropdown is available showing all pre-programmed reports available. To generate one of the reports, simply click on the dropdown under Reports and select the desired report. Each report is configured by specifying the site/parameters, time period, and averaging interval (no averaging interval for calibration reports) of the data to display. The report criteria are all contained in the portion of the screen under the top banner of the AirVision main menu screen. After the report criteria have been specified, simply click on the “Generate Report” button to have the report displayed in the lower portion (Report Output) of the screen. Note that once the report criteria have been specified, that section of the screen can be hidden to allow more space to view the report by clicking on the “-“ button to the right of the report criteria title. Figure 2 is an example of a Daily Summary Report.




Figure 2 – Report Generation Screen

Some of the more commonly utilized standard reports and their typical use are listed in Table 1 below. For a complete listing of standard reports available in AirVision, please refer to the AirVision manual.

Name of Report Typical Use

Basic Data Export Export data from AirVision for use with other tools.

Calibration Results Report Daily review of auto and any manual calibrations.

Calibration Trend Graph Review calibration trends

Logger Configuration Report Document how each logger is configured

Precision Report Review “One-Point QC Checks”

Data Recovery Report Evaluate data recovery

Maximum Hourly Values Report Quick report to review maximum hourly values.

Daily Summary Report Daily review of data from each site

Monthly Report Present one month of data on one page, very useful in monthly review of data.

AQS Text Report Generate AQS strings for submission to EPA.

Table 1 – Commonly used AirVision Standard Reports and Typical Use



4.3 Accessing/Editing Data Using AirVision Editors

AirVision data editors are available to display minute, hourly, and calibration data in both tabular and graphical formats. The data value, AQS null code, flags, AQS qualifier codes, and AQS method codes can be edited from the average editor screen. The true concentration and analyzer response can be edited from the calibration editor screen. Under the main menu, from the home tab, under the Data Editor icon, a dropdown is showing the data editors available. The data editor screens are set up similar to the report screens, with selection criteria under the top banner of the screen. Similar to the report criteria, the time frame of data to retrieve, the averaging interval (except calibration editor), and the site/parameters to retrieve are specified. After the selection criteria has been set, simply click on the “Retrieve Data” button on the top banner to retrieve the selected data. As with the report screen, the data requested will be displayed in the lower portion of the screen. Once the data has been retrieved, it can be displayed in various tabular or graphical formats by selecting the appropriate presentation options in the top banner. Edits to the data value, AQS null code, flags, AQS qualifier codes, and AQS method codes are made in any tabular format and are saved to the database by clicking on the file save icon in the upper left corner of the screen. AirVision keeps an audit trail for any changes made with the average data editor screen and allows the data value to be set back to the original acquired value. Figure 3 is an example of the Average Data Editor in Linear Data format.



Figure 3- Data Editor Screen

4.4 AQS Null Codes, AirVision Data Flags, and AQS Qualifier Codes

AirVision utilizes internal data flags to identify data values associated with various

conditions and/or events. Most data flags are applied by the ESC 8832 data logger, but

data flags can also be applied utilizing the central AirVision software. AirVision can be

programmed to automatically apply null codes based on a particular data flag, but null

codes can also be applied manually using the central AirVision software. Table 2

presents a list of the more common qualifier codes used at VCAPCD, and the events

that the codes are applied to. Qualifier codes can be Null Data, Quality Assurance,

Informational, or Request Exclusion. Null codes describe the reason for invalidating

data and go in place of data extracted from AirVision and submitted into AQS. Qualifier

Codes describe a localized event or data handling procedure that may affect the

reported value. Up to ten Qualifier Codes can be applied to a value.

When assigned, Null codes will be exported in lieu of data when submitting data to

AQS, while Qualifier codes will be exported with the data into AQS.

Data reviewers should use good judgment when selecting the best combination of

flags/Qualifier codes to best describe any condition that may arise. At VCAPCD, data



flags and annotations may be applied at any level of data review, however only Level 2

and Level 3 data reviewers apply Qualifier codes to the data.

EVENT

QUALIFIER TYPE CODE DESCRIPTION

Morning Span BF (Null) Precision/Zero/Span

Multipoint Calibration BC (Null) Multipoint Calibration

Mid-, End-Month QC Flow and Leak Check

BA (Null) Maintenance/Routine Repairs

Missing Data AQ (Null) Collection Error

CARB Flow Audit BL (Null) QA Audit

Excessive Negative Ozone Values

AN (Null) Machine Malfunction

Power Failure AV (Null) Power Failure

PM2.5 Data <-5 (flag “Bad”) AN (Null) Machine Malfunction

Gust Excessively High DA (Null) Aberrant Data

72-Hour Zero Test AT (Null) Calibration

Meteorological Calibration AT (Null) Calibration

Table 2 Commonly Used Qualifier Codes and Events

Tables 3-5 list all the AQS Null Codes, AirVision Data Flags, and AQS Qualifier Codes and situations where they may be used. Station operators should use good judgement when selecting the best combination of codes to best describe any condition that may arise. Be aware that AirVision runs routines that may automatically apply various data flags and null codes to the gaseous analyzer and BAM particulate data for conditions such as high rate of change, insufficient data, bad status bits, or automated QC sequences.

Table 3 – AQS Null Codes

AA Sample Pressure out of Limits

AB Technician Unavailable

AC Construction/Repairs in Area

AD Shelter Storm Damage

AE Shelter Temperature Outside Limits

AF Scheduled but not Collected

AG Sample Time out of Limits

AH Sample Flow Rate out of Limits

AI Insufficient Data (cannot calculate)

AJ Filter Damage

AK Filter Leak

AL Voided by Operator

AM Miscellaneous Void

AN Machine Malfunction



AO Bad Weather

AP Vandalism

AQ Collection Error

AR Lab Error

AS Poor Quality Assurance Results

AT Calibration

AU Monitoring Waived

AV Power Failure

AW Wildlife Damage

AX Precision Check

AY Q C Control Points (zero/span)

AZ Q C Audit

BA Maintenance/Routine Repairs

BB Unable to Reach Site

BC Multi-point Calibration

BD Auto Calibration

BE Building/Site Repair

BF Precision/Zero/Span

BG Missing ozone data not likely to exceed level of standard

BH Interference/co-elution/misidentification

BI Lost or damaged in transit

BJ Operator Error

BK Site computer/data logger down

BL QA Audit

BM Accuracy check

BN Sample Value Exceeds Media Limit

BR Sample Value Below Acceptable Range

CS Laboratory Calibration Standard

DA Aberrant Data (Corrupt Files, Aberrant Chromatography, Spikes, Shifts)

DL Detection Limit Analyses

FI Filter Inspection Flag

MB Method Blank (Analytical)

MC Module End Cap Missing

SA Storm Approaching

SC Sampler Contamination

ST Calibration Verification Standard

TC Component Check & Retention Time Standard

TS Holding Time Or Transport Temperature Is Out Of Specs.

XX Experimental Data



Table 4 – AirVision Data Flags

T Out of Control

+ Max Exceeded

a Audit

D Channel Disabled

H High-High Alarm

L Low-Low Alarm

O Overrange

Q Quality Assured

X Dig Info#3

F Boiler Offline

A Arithmetic Error (math calculation error)

- Min Exceeded

B Bad Status

E Edited

h High Alarm

l Low Alarm

o Other

R Rate of Change Exceeded

Y Dig Info#4

j Low Rate of Change Exceeded

t Out of Control (Partial)

< Logger Invalid

C Calibration

e Site Malfunction

I Invalidated By Edit

M Maintenance

P Power Failure

V Dig Info#1

Z Dig Info#5

> Some Data Missing

? Suspect

c Ceiling Limit

f Floor Limit

J High Rate of Change Exceeded

m Marked Maint by edit

p Precision Check

W Dig Info#2

z Zero Adjusted



Table 5 – AQS Qualifier Codes (QA and Informational)

IA African Dust

IB Asian Dust

IC Chem. Spills & Indust Accidents

ID Cleanup After a Major Disaster

IE Demolition

IF Fire - Canadian

IG Fire - Mexico/Central America

IH Fireworks

II High Pollen Count

IJ High Winds

IK Infrequent Large Gatherings

IL Other

IM Prescribed Fire

IN Seismic Activity

IO Stratospheric Ozone Intrusion

IP Structural Fire

IQ Terrorist Act

IR Unique Traffic Disruption

IS Volcanic Eruptions

IT Wildfire-U. S.

J Construction

1 Deviation from a CFR/Critical Criteria Requirement

2 Operational Deviation

3 Field Issue

4 Lab Issue

5 Outlier

6 QAPP Issue

7 Below Lowest Calibration Level

9 Negative value detected - zero reported

CB Values have been Blank Corrected

CC Clean Canister Residue

CL Surrogate Recoveries Outside Control Limits

DI Sample was diluted for analysis

EH Estimated; Exceeds Upper Range

FB Field Blank Value Above Acceptable Limit

FX Filter Integrity Issue

HT Sample pick-up hold time exceeded

LB Lab blank value above acceptable limit



LJ Identification Of Analyte Is Acceptable; Reported Value Is An Estimate

LK Analyte Identified; Reported Value May Be Biased High

LL Analyte Identified; Reported Value May Be Biased Low

MD Value less than MDL

MS Value reported is 1/2 MDL substituted.

MX Matrix Effect

ND No Value Detected

NS Influenced by nearby source

QX Does not meet QC criteria

SQ Values Between SQL and MDL

SS Value substituted from secondary monitor

SX Does Not Meet Siting Criteria

TB Trip Blank Value Above Acceptable Limit

TT Transport Temperature is Out of Specs.

V Validated Value

VB Value below normal; no reason to invalidate

W Flow Rate Average out of Spec.

X Filter Temperature Difference out of Spec.

Y Elapsed Sample Time out of Spec.



5.0 Ongoing Review to Minimize Data Loss Complete data sets, with minimal data lost to QA/QC activities and instrument/site maintenance, are necessary for making regulatory decisions critical to VCAPCD. Performing these daily review steps will dramatically reduce the monthly review effort. The following actions should be taken by all VCAPCD monitoring staff to minimize data loss. Site Operators:

1. Review hourly tabular and minute graphical data for all parameters at each site you are assigned each work day.

a. This review includes both concentration data as well as operational parameters.

b. Watch operational parameters that are trending toward out of tolerance condition.

c. BAM hourly values in AirVision are automatically flagged and annotated whenever the BAM data string contains any bad status indicators. Watch for these flags and annotations.

d. In review of graphical concentration data, watch for atypical data patterns, including:

i. High NO and O3 at the same time ii. Noisy trace iii. Sudden shifts in concentration not accompanied by simultaneous

shifts in wind conditions. iv. Positive spikes in O3 trace. v. Periods of negative concentration value.

2. Review all calibration data in AirVision for all parameters at each site where you

are assigned each work day. a. Review tabular calibration data using the Calibration Results Report in

AirVision. Note any parameter’s result that exceeds warning limits. b. Review calibration trends with the use of Air Vision tools. Pay attention to

any parameter trending towards warning limits. c. If any calibration results observed in a or b above appear unusual, plot the

one-minute data for that parameter for the calibration period in graphical format using the average data editor in AirVision.

3. Review certification periods for all standards utilized at the monitoring stations you are assigned.

a. Ensure all standards certification dates are within valid timeframe. b. Schedule and perform any re-certifications before the certification expires.

4. Investigate any possible problems identified in the above steps. a. Determine if any corrective action is required. Should corrective action be

required, make that action a top priority to perform as soon as possible. If a problem or issue is encountered where the cause of the problem, solution to the problem, and/or the data implications are unclear, the



CARB Corrective Action Notification (CAN) process is implemented. The CAN process allows for a thorough review of the problem, ensuring that the problem, potential solutions, and impacts to data are thoroughly reviewed and considered. See reference section for a link to the CAN SOP.

b. If your schedule precludes immediate corrective action/investigation, notify the Monitoring Manager immediately so other staff can be assigned.

Monitoring Manager:

1. Provide assistance to site operators investigating atypical results in their review of data as needed.

2. Provide assistance to site operators in obtaining any necessary replacement parts as needed.

3. Schedule substitute site operators for sites operated by staff not available to perform ongoing review.

4. Provide general technical assistance as needed. 5. If a problem or issue is encountered where the cause of the problem, solution to

the problem, and/or the data implications are unclear, the CARB Corrective

Action Notification (CAN) process is implemented. The CAN process allows for a

thorough review of the problem, ensuring that the problem, potential solutions,

and impacts to data are thoroughly reviewed and considered. See reference

section for a link to the CAN SOP.



6.0 Monthly Data Review

In addition to the daily review of data described in the previous section, VCAPCD staff

performs formalized reviews of data produced from their air monitoring network in

monthly batches. The monthly review procedure utilizes three levels of review, each

performed by a different staff person. Level 1 reviewers typically try to complete their

review by the end of the month following the month of data being reviewed. This

ensures that Level 2 and Level 3 data reviewers can complete their review and submit

the month’s data into AQS within the 45 days of collection.

VCAPCD utilizes a Monthly Data Review (MDR) Chain of Custody Sheet that

documents each level of review has been completed for each parameter measured in

the monitoring network. All staff performing data review must initial and date each

parameter on the Monthly Data Review Chain of Custody Sheet upon completion of

their review of that parameter. When monthly review is complete, the Monitoring

Manager, signs and dates the sheet, indicating that data review is complete for that

month, and ready to be submitted to AQS, the national database that contains ambient

air quality monitoring data collected by states, tribes, and local air monitoring districts.

Figure 4 shows a Monthly Data Review Chain of Custody sheet.

For each level of review, a checklist is utilized by the reviewer to document and ensure

each step of the review was completed.



Figure 4 Monthly Data Review Chain of Custody Sheet

6.1 General Guidelines on Data Review Data review will be greatly enhanced if the station operator is conscious of several guidelines in data review. These are listed below:

1. The data reviewer should be familiar with typical diurnal (daily) concentration variations (e.g., the times daily maximum concentrations occur and the interrelationship of pollutants). For example: NO and ozone (O3) cannot coexist at high concentrations; nitrogen dioxide (NO2) and NO concentrations, or their sums, should not be greater than oxides of nitrogen (NOx).

2. The data reviewer should be familiar with the type of instrument malfunctions that cause characteristic trace irregularities.

3. Cyclical or repetitive variations (at the same time each day or at periodic intervals during the day) may be caused by excessive line voltage or temperature variations. Nearby source activity can also cause erroneous or non-



representative measurements and should be properly noted in the station logbook as well as with the use of Null/Qualifier codes.

4. Graphical displays of data on AirVision showing little or no activity often indicate a loss of sensitivity, flow problems, or sample line leaks.

5. For Meteorological parameters, graphical displays showing flat line traces often indicate a sensor failure. Sudden wind speed shifts from zero to values greater than 2 mph can be a sign of sensor bearing failure. Spikes or sudden shifts in the ambient temperature trace are a sign of a sensor beginning to fail.

6. Excessively negative PM10 values (<-4ug/m3 for more than one hour) and PM2.5 (<-5ug/m3 for more than one hour) are a sign of malfunction in BAM PM samplers.

7. For sites with both PM10 and PM2.5, periods where PM2.5>PM10 while the concentrations are significantly above detection levels are a sign of a problem with one or both of the PM samplers.

8. Nightly precision and/or span checks provide a means of detecting shifts in instrument performance. If instrument response varies by more than 5% from the expected value, this should be investigated immediately if not already addressed in daily reviews.

9. The following are the data completeness criteria utilized by the District (Based on EPA and CARB guidance):

• At least 45 continuous minutes of valid data are required to determine an hourly average (excluding PM2.5 BAM valid hour based on 42 minute sampling cycle).

• In determining the hourly average concentrations, disregard both recorded

excursions lasting less than ten minutes and excursions that indicate obvious

deviations from actual conditions in the surrounding area.

6.2 Level 1 Data Review

The overall purpose of this procedure is to ensure that finalized data have been accurately calculated, meet EPA requirements, and the data quality is sufficient for the intended use of the data. The data processing procedures validate all data by bracketing all valid data with valid calibrations and/or QC checks. Any data that is not bracketed in time by valid calibrations within the required tolerance is invalidated unless meta-data or other indicators demonstrate the time the data likely exceeded tolerance limits. For example, if the cause of an out of tolerance calibration was the failure of a sample pump, and the sample flow data showed when the failure occurred, data would only need to be invalidated from the time the sample flow dropped below operational conditions until the analyzer was repaired and a valid calibration within tolerance was performed. The Level 1 review is normally performed by the station operator (AQ Instrument Technician) but can also be performed by the Supervising AQ Instrument Technician or other qualified staff. In addition to the daily review performed by the station operator



described in Section 5, additional review steps are performed on each month of data following the end of the month. The Level 1 review is performed utilizing the Level 1 Data Review Check Sheet (Figure 5 below) to document and ensure each step of the review was performed. The Level 1 review steps are outlined below: 1. All site documentation, including site log book entries, multi-point calibration forms,

and Monthly Quality Control Checksheets are reviewed to provide a clear picture to the level 1 reviewer of the monthly activities that could potentially influence data validity.

2. Review site documentation to ensure that each of the following tasks were

performed within the required interval. Table 6 below provides the required tasks and frequency by parameter.

Ozone

QC Task Frequency Required

Calibration Standard (Photometer) Certification

6 Months

1-Point QC check 14 Days

Level 1 Span Check 14 Days

Full multi-point Calibration 6 Months

NOx


Certification of Calibrator Flows

6 Months

Certification of Compressed Gas Cylinder

As Specified by

Certification

1-Point QC check 14 Days

Level 1 Span Check 14 Days

Multi-point Calibration 6 Months

PM10 and PM2.5 BAM


Flow/Temperature/Pressure and Leak Check

Verification

2X/Month



Full Calibration 6 Months

Zero Background Check 1 Year

Meteorological Sensors


Full Calibration 6 Months

Station Temperature


One Point Calibration 6 Months

Table 6- Required QC Tasks and Frequency 3. Review the station temperature monthly report. Station temperature is typically

maintained between 20-30 Deg.C, but analyzers utilized by VCAPCD have an equivalency designation that allows station temperature to be between 5-40 Deg.C. If the station temperature exceeds the allowable temperature range, invalidate those hours and note the reason by annotating in AirVision. Also review for temperature change from hour to hour. Changes greater than +/-2 Deg.C from one hour to the next can influence the BAM readings. Investigate and potentially invalidate any hours that appear influenced by the site temperature where there was greater than a 2 Deg.C change in temperature.

4. Auto-cal data from the month of the data being processed is examined using one of

AirVision’s Calibration Reports. The Calibration Trend Graph report allows the reviewer to view a graph of the month’s automated zero, span, and precision checks. Any auto-cal results that are not as expected are examined closer by viewing the minute data for the auto-cal period. Any valid, but out of tolerance calibration records require invalidation of data so that all data is bracketed in time by valid calibration checks within allowable tolerance. Any auto-cal data determined to be in error, and not accurately reflecting the analyzer’s response is excluded from use in the AirVision calibration database. (see Table 7 below for allowable gas pollutant calibration tolerance)

5. Review manual gas parameter calibration data for the month of data being

processed. Any valid, but out of tolerance calibration records require invalidation of data so that all data is bracketed in time by valid calibration checks within allowable tolerance. (see Table 7 below for allowable gas pollutant calibration tolerance)



Parameter Warning Limit Invalidation Limit

Ozone Zero <=+/- 1.5 ppb <+/- 3.1 ppb

Ozone Upscale Span/1-pt QC check

<=+/- 5% <+/- 7.1%

NO/NO2/NOx Zero <=+/- 1.5 ppb <+/- 3.1 ppb

NO/NO2/NOx Upscale Span

<=+/- 7% <+/-10.1%

NO/NO2/NOx 1-pt QC Check

<=+/-10% <+/-15.1%

Table 7- Gas Parameter Warning and Invalidation Limits

6. Review recent meteorological calibrations that could impact this month’s data. If data is bracketed with valid calibrations whose results are within the validation criteria listed in Table 8 below, the data is validated as is. Any period of data bracketed with one or more calibration greater than the invalidation criteria listed below must be invalidated (unless other indicators clearly demonstrate the start point of the out of tolerance period). Using the data editor in AirVision, make any invalidations to the hourly data necessary based on the calibration data review. Document all edits by annotating the data in AirVision

Sensor Validation Criteria Corrective Action Threshold

Ambient Temperature

All points +/- 0.5 Deg.C. Any point +/- 0.4 Deg.C.

Wind Speed ±0.25m/s ≤5m/s; 5%>2m/s not to exceed 2.5m/s

±0.2m/s ≤5m/s; 4%>2m/s

Wind Direction

All points +/- 5 Deg.C Any point +/- 3 Deg.C

Station Temperature

+/-1 Deg.C +/- 0.7 Deg.C

Relative Humidity

All points +/- 5% RH Any point +/-4% RH

Barometric Pressure

+/- 1hPa +/- .7 hPa

Precipitation +/- 10% of input volume +/- 7% of input volume

Table 8 – Meteorological Parameter Validation and Corrective Action Limits

7. Review all PM10 and PM2.5 BAM verifications/calibrations for the month. If data is bracketed with valid verification/calibrations whose results are lower than the criteria listed in Table 9 below, the data is validated as is. Any period of data bracketed with one or more calibration/verification greater than the invalidation criteria listed below must be invalidated. Make any necessary edits to the data set using the data editor in AirVision. Document any edits by making annotations to the data in AirVision.



Parameter Invalidation Criteria

PM10/2.5 BAM Flow Verification or AS IS Flow Calibration

+/- 4% (at 16.7 sample flow)

PM10/2.5 AS IS Leak Check

>1.0 l/m

Table 9 –PM10/2.5 QC Invalidation Criteria

8. The PM10/2.5 BAM sampler’s data records include bad status bits that indicate a potential problem with the hourly value. The AirVision software automatically applies a flag to any PM10 or PM2.5 hourly value that has a bad status bit in the BAM record. In the AirVision editor, when you hover over a data value with a flag that was applied due to a BAM bad status bit, the data system automatically displays the bad status bit(s) that were detected and caused the flag to be applied. Review each flagged PM10 and PM2.5 hourly value in the AirVision editor with a flag to determine what bad status bit or other reason caused the flag to be applied. Investigate each occurrence to confirm that the validity of the hourly value is correct in AirVision. Note the results of the investigation in each hour by annotating the data in AirVision.

9. Review all pollutant data for any negative concentration values. Invalidate any

values less than the minimum allowed in Table 10 below using the AirVision data editor. Note that if either PM10 local conditions or PM10 standard conditions is below the minimum allowed value, both parameters values are invalidated. Annotate any edits in AirVision.

Pollutant Minimum Allowable Hourly Value

Ozone -5 ppb

NO/NO2/NOx -5 ppb

PM2.5 -5 ug/m3

PM10 -4 ug/m3

Table 10 – Minimum Allowable Hourly Values

10. Review the average flow rate monthly report for each BAM PM2.5 sampler and the actual flow sample volume monthly report for each BAM PM10 sampler to ensure that all valid hourly values for that hour are within the allowable tolerance of +/-5% of the design value (see table 11 below). Invalidate any values exceeding this tolerance using the AirVision data editor and document the invalidation reason by annotating the data in AirVision.



Parameter Average Maximum (+5%)

Minimum (-5%)

PM10 Sample Volume (50- minute sample period)

.834 m3 .876 m3 .792 m3

PM2.5 Flow Rate (42- minute sample period)

16.7 LPM

17.535 LPM

15.865 LPM

Table 11 – PM10Sample Volume and PM25 Flow Rate Validation Criteria

11. Hourly pollutant concentration and meteorological data for the month is examined

using the Average Data Editor in AirVision. The review of the hourly data includes

examining that all hourly data is correctly flagged and annotated in AirVision, looking

for unusual or unexpected values, as well as examining the highest and lowest

hourly concentration values for the month to ensure these values are correct and

flagged appropriately. Post-processing of data is no longer allowed in most

circumstances by EPA (QA Manual Vol II) and CARB (see CARB QA Bulletin 6 on

the CARB QA webpage). In the review each month’s hourly values; focus on any

missing data, obvious erroneous data, and any questionable data value. Query all

monthly parameters with each Parent Parameter (i.e. Ozone, PM10, PM2.5, Wind

Speed, Wind Direction) grouped with the daughter channels (i.e. O3 sample flow, O3

lamp temp, etc.). The daughter channel data is used to support the validity of the

parent pollutant parameters. Many parameters are programed to automatically flag

high or low whenever the parameter value is outside of acceptable range. Pay

special attention to data values with “screening flags”. These “screening flags” are

very useful in identifying suspect data points. Investigate all data values with

screening or other flags to determine validity. Make any necessary changes in data

values and/or flags using the AirVision data editor. Document the reason for any

edits by annotating the data in AirVision.

12. The following documents are gathered and added to each monitoring site’s

completed Monthly Data Review Packet and submitted for Level 2 data review:

• All documents generated as part of the Monthly O3, NOx, NO and NO2

AutoCal data review.

• All documents generated as part of the Monthly O3, NOX, NO, NO2, NOX-A

(analog) and NO-A (analog) hourly data review.

• All documents generated as part of the Monthly PM10 and LC10 hourly data

review.



• All documents generated as part of the Monthly LC25 hourly data review.

• All documents generated as part of the Monthly Meteorological data review.

• All weekly quality control check forms for the month in review

• All site logbook carbonized copies for the month in review

• All semi-monthly PM sampler quality control forms for the month in review

• All calibration/verification forms for the month in review

• All maintenance and troubleshooting forms for the month in review



VETURA COUNTY APCD LEVEL 1 DATA REVIEW AND VALIDATION Month/Year Monitoring Site Technician

1) Gather and review all site documentation for the month being processed. Pay special

attention to any indications of equipment failures, out of tolerance conditions or other problems.

2) Verify that all required QC Checks and other activities were performed within the required time frame

3) Review the monthly report for station temperature. Any gas parameter values outside of the EPA equivalency operating temperature require the invalidation of data for those periods. Also investigate all BAM data for hours where STM change from one hour to the next is greater than 2 Deg.C.

4) Review gas pollutant auto-cals. Invalidate any data periods not meeting drift requirements. 5) Review all gas pollutant multi-point calibration records. Invalidate any data periods not

meeting drift requirements.

6) Review any meteorological calibration records. Invalidate any data periods not meeting calibration tolerance requirements.

7) Review all BAM PM10/2.5 verifications/calibrations. Invalidate any data periods not meeting tolerance limits.

8) Review any PM2.5 or PM10 values invalidated by the data system in the AirVision editor to ensure the invalidation was appropriate. Note that when you hover over the invalid value, the software automatically lists the reason for invalidation.

9) Review any negative pollutant values in the data set. Any values less that the minimum allowed are invalidated in AirVision and the reason annotated.

10) Review sampled average flow rate for the month for PM2.5 and sampled actual volume for the month for PM10. Invalidate all PM2.5 or PM10 and LC10 hourly concentrations where the corresponding readings are not within the required +/-5% of the design flow value or the design volume.

11) Review PM2.5 and PM10 BAM verifications and calibrations for the month. Invalidate any data periods for either parameter not bracketed by valid verifications/calibrations within +/-4% flow tolerance and leak check >1.0 l/m.

12) Review each parameter’s hourly values using the AirVision average data editor. Focus on any areas of missing, questionable, or obviously erroneous data. Pay special attention to data flags, periods of data that site documentation indicates is invalid or questionable, investigate the validity of any suspect value, values with flags, or other anomalies. Using the AirVision editor, make any necessary changes to data values and/or flags or null codes based on this review. Document the reason for any edits/changes by annotating the affected data in AirVision.

13) Investigate each instance of missing data listed on the monthly reports. Determine if the data can be retrieved from strip charts, from BAM internal records, or if the data is truly missing or invalid. Note the reason for each invalid/missing data value by annotating the data in AirVision. If data can be retrieved from strip charts or BAM internal records, edit the values in AirVision and annotate the data with the reason for the edits.

14) Sign and date the review check sheet and alert the Level 2 reviewer that the data has passed the Level 1 review and is available for the Level 2 review. Gather all documents utilized/generated in the Level 1 review.

15) Initial and date the Monthly Data Review Chain of Custody Sheet

Figure 5 – Monthly Level 1 Data Review Check Sheet




After the Level 1 data review, the data packet is delivered to the Level 2 data reviewer.

Level 2 data review is a more specific review focusing on diurnal and seasonal trends

surrounding high/low values and exceedances.

The Level 2 review is normally performed by the Air Quality Specialist but can be performed by the AQ Instrument Technician that did not perform the Level 1 review, or other qualified staff. The Level 2 review makes the final determination of validity of each data point and assigns appropriate null and data qualifier codes. The Level 2 review utilizes the documentation assembled in the Data Review Packet and builds on the previous Level 1 review. The Level 2 review is performed utilizing the Level 2 Data Review Check Sheet (Figure 6 below) to document and ensure each step of the review was performed. The Level 2 review steps are outlined below:

1. Confirm and record receipt of all Quality Control Records from the monthly data

review packet onto the Ventura County APCD Log for Monthly Quality Control Checks sheet.

2. Review each meteorological and pollutant concentration parameter for the month using the Matrix data view in AirVision’s Average Data Editor. In this step take the following action:

a. Using the site log notes, review the flags and annotations added by the Level 1 review. Ensure that all site activities and observations are properly annotated, and the data values are properly flagged. Special attention is payed to missing values, unusual values, repeating zero values, and that the data values are consistent with the expected values based on the season and time of day.

b. Manually apply the appropriate null code to any data values flagged for invalidation. Confirm the applied null code is now present in the data base.

c. Manually apply any informational qualifier codes to any data value requiring a qualifier code. Confirm the qualifier code was correctly applied.

3. Review each meteorological and pollutant concentration parameter for the month using the Linear Data view in AirVision’s Average Data Editor. In this step take the following action:

a. Sort the data by concentration, first highest to lowest, then lowest to highest. Examine the high and low concentration data values to ensure they are flagged correctly and any necessary null or qualifier code is correctly applied.

b. Sort the data by flag. Ensure that null codes have been correctly applied to flagged data.



c. Sort the data by null code. Ensure that data values with null code have the correct flag applied.

4. Review all meteorological values and pollutant concentrations for the month using the Cross Tab view in AirVision’s Average Data Editor. In this step the monthly data set is reviewed to confirm that any systematic issues that would require invalidation of all or multiple parameters (such as power failures, failures of one NOx parameter, etc.) are correctly applied to all appropriate parameters.

5. Review ozone and NOx parameters for the month using the Time Series view in AirVision’s Average Data Editor. In this step the reviewer can view any interactions between the ozone and NOx parameters to ensure the relationship between ozone and NOx follows the typical pattern. Some of these relationships to examine are:

a. That NO is always equal or lower than NOx. b. That during periods of high NO, ozone values are low (near zero). c. That during periods of high ozone, the NO values are low (near zero).

6. Any documents generated in the Level 2 review are added to the data review

packet, and the Data Review Chain of Custody is dated, signed, and is passed to

the Level 3 reviewer.



VENTURA COUNTY APCD LEVEL 2 DATA REVIEW AND VALIDATION

Month/Year Monitoring Site Technician

TASK OK?

1) Confirm and record receipt of all Quality Control Records from the monthly data review packet onto the Ventura County APCD Log for Monthly Quality Control Checks sheet.

2) Review each meteorological and pollutant concentration parameter for the month using the Matrix data view in AirVision’s Average Data Editor. Using the site log notes, review the flags and annotations added by the Level 1 review. Ensure that all site activities and observations are properly annotated, and the data values are properly flagged. Special attention is payed to missing values, unusual values, repeating zero values, and that the data values are consistent with the expected values based on the season and time of day.

3) Using the Matrix data view in AirVision’s Average Data Editor, manually apply the appropriate null code to any data values flagged for invalidation. Confirm the applied null code is now present in the data base.

4) Using the Matrix data view in AirVision’s Average Data Editor, manually apply any informational qualifier codes to any data value requiring a qualifier code. Confirm the qualifier code was correctly applied.

5) Review each meteorological and pollutant concentration parameter for the month using the Linear Data view in AirVision’s Average Data Editor. Sort the data by concentration, first highest to lowest, then lowest to highest. Examine the high and low concentration data values to ensure they are flagged correctly and any necessary null or qualifier code is correctly applied.

6) Using the Linear Data view in AirVision’s Average Data Editor, sort the data by flag. Ensure that null codes have been correctly applied to flagged data.

7) Using the Linear Data view in AirVision’s Average Data Editor, sort the data by null code. Ensure that data values with null code have the correct flag applied.

8) Review all meteorological values and pollutant concentrations for the month using the Cross Tab view in AirVision’s Average Data Editor. In this step the monthly data set is reviewed to confirm that any systematic issues that would require invalidation of all or multiple parameters (such as power failures, failures of one NOx parameter, etc.) are correctly applied to all appropriate parameters.

9) Review ozone and NOx parameters for the month using the Time Series view in AirVision’s Average Data Editor. Examine the relationship between ozone and NOx parameters to ensure the data patterns are as expected.

10) Sign and date the review check sheet and alert the Level 3 reviewer that the data has passed the Level 2 review and is available for the Level 3 review. Gather all documents utilized/generated in the Level 2 review.

11) Initial and date the Monthly Data Review Chain of Custody Sheet

Additional Comments:

Figure 6 – Level 2 Data Review Check Sheet




The Level 3 review is normally performed by either the AQ Instrument Technician that

has not performed the Level 1 or 2 review, or the AQ Specialist (if has not performed

the Level 2 review), or other qualified staff. The Level 3 review first confirms that the

Level 2 review correctly applied all flags, null codes, and qualifier codes and follows the

procedure outlined above for the Level 2 review but is performed by a different staff

person. Additionally, Monthly Reports for all gas pollutants are generated in AirVision

that provide a monthly matrix view with added maximum, average, and number of valid

hourly value statistics for the month. Once the Level 2 reviewer initials and dates the

MDR Chain of Custody Sheet, the Level 3 data reviewer can begin reviewing the data.

All gaseous data, PM data, and meteorological data are reviewed at Level 3.

The Level 3 review is performed utilizing the Level 3 Data Review Check Sheet (Figure 7 below) to document and ensure each step of the review was performed. The Level 3 review steps are outlined below:

1. Ensure that previous data reviewers have initialed and dated the MDR Chain of

Custody Sheet (see Figure 4). Using steps described in Section 6.3 above (Level 2

Data Review), review all data, flags, qualifier codes, and annotations.

2. Using AirVision, generate a Monthly Summary Report (Reports/Summary

Reports/Monthly Report) for the site, parameter, and month/year being reviewed.

The data is presented very similarly as in the Matrix Data Editor, but also includes

statistics such as Maximum Values, Averages, and Number of Recorded Hours.

Review these statistics and evaluate for the following:

• Are these values typical for the time of year?

• Is the diurnal profile reasonable?

• Is the hour of the daily maximum value typical?

• Do the values trend up to a maximum or down to a minimum?

• Is the day complete? Are the reasons for missing data noted?

• Are the daily maximum/minimum values impacted by a source or unusual condition?

Are the sources or unusual conditions noted?

3. Using the Monthly Report, ensure that all appropriate flags, annotations, and null

data codes have been applied.

4. Upon completion of Level 3 review, submit the sheet to the Monitoring Manager for

review, signature, and date. Scan the MDR Chain of Custody Sheet and save the

electronic copy to R://MDR Chain of Custody. File the paper copy original in the

folder for that month’s data review.



VENTURA COUNTY APCD LEVEL 3 DATA REVIEW AND VALIDATION

Month/Year Monitoring Site Technician

TASK OK?

1. Ensure that previous data reviewers have initialed and dated the MDR Chain of Custody Sheet

2. Using procedures utilized in the Level 2 Data Review, review all data, flags, qualifier codes, and annotations to ensure their accuracy.

3. Using AirVision, generate a Monthly Summary Report (Reports/Summary Reports/Monthly Report) for the site, parameter, and month/year being reviewed.

4. Review the Monthly Summary Reports, confirm that the values typical for the time of year

5. Review the Monthly Summary Reports, confirm the diurnal profile reasonable (where applicable)

6. Review the Monthly Summary Reports, confirm the hour of the daily maximum value typical for the site and parameter

7. Review the Monthly Summary Reports, examine any trends in data that might indicate a problem.

8. Review the Monthly Summary Reports, confirm any missing data is correctly annotated with the reason for missing data.

9. Review the Monthly Summary Reports, examine if the daily maximum/minimum values are impacted by a source or unusual condition? If so, are the sources or unusual conditions noted?

10. Review the Monthly Summary Reports, confirm that all appropriate flags, annotations, and null data codes have been applied.

11. Sign and date the review check sheet. Gather all documents utilized/generated in the Level 3 review.

12. Upon completion of Level 3 review, submit the data packet and MDR Chain of Custody Sheet to the Monitoring Manager for review, signature, and date. Scan the MDR Chain of Custody Sheet and save the electronic copy to R://MDR Chain of Custody. File the paper copy original in the folder for that month’s data review.

Figure 7- Level 3 Monthly Data Review Check Sheet



6.5 AQS Submissions and Reports

Once the data has been thoroughly reviewed (Level 1, 2, and 3 reviews completed),

and the Monitoring Manager has signed and dated the Monthly Data Review Chain of

Custody Sheet, the Level 2 or Level 3 reviewer submits the data to AQS. VCAPCD

submits hourly data, PM10/2.5 flow verification data, and gaseous pollutants “1-Point

QC” data monthly to AQS.

AirVision is utilized to generate a transaction file in pipe delimited format that will be

accepted into AQS for all hourly and “1-Pt. QC” records. VCAPCD uses the AQS QA

Transaction Generator to create the PM10/2.5 flow rate verification records. The values

needed for the transaction generator are available from the PM10/2.5 QC sheets or

calibration sheets.

VCAPCD maintains a bound composition book as a logbook of all transactions

submitted to AQS. Once data review is complete, generate the transaction files, save

the files to the designated location on the M:\ drive, submit the files to AQS, and record

the submittal details in the AQS logbook. Include the file name, date of submittal, and

initial the logbook entry. Typical entries include monthly data submittal file names, and

number of records, and precision and accuracy submittals. Document any errors

encountered, and steps taken to correct the errors

In accordance with the document Primary Quality Assurance Organization Roles and

Responsibilities (R & R) for the Air Resources Board and Ventura County Air Pollution

Control District (October 2014), VCAPCD staff must generate two AQS reports twice

per year for January thru June, and July thru December. This is to verify data accuracy

and completeness after data has been submitted to AQS. Quality Assurance Bulletin

005, Post-AQS Data Confirmation outlines the procedure for reviewing the reports.

AQS reports AMP430 (completeness Report) and AMP256 (QA Data Quality Indicator

Report) must be reviewed for transcription errors, missing values, or values associated

with incorrect codes.

https://arb.ca.gov/aaqm/qa/pqao/repository/ventura_rolesandresponsibilities.pdf



http://arb.ca.gov/aaqm/qa/pqao/pdfs/qab005-AQS.pdf

http://arb.ca.gov/aaqm/qa/pqao/pdfs/qab005-AQS.pdf



7.0 Annual Data Certification

Data certification indicates that the monitoring agency has loaded all data for the year

and has completed the monitoring agency’s normal validation process. The responsible

official certifies that 1) the ambient concentration data and the quality assurance data

are completely submitted into AQS, and that 2) the ambient data are accurate to the

best of his or her knowledge taking into consideration the quality assurance findings.

The first part means that all of the ambient and quality assurance data that were

collected, and that have completed and passed the monitoring agency’s data validation

process have been submitted into AQS. The second part means that the official has

considered the results of periodic quality control checks and any other relevant

performance assessments.

By May 1 every year, state and local government monitoring organizations must certify

their data. A state official should certify all data submitted for affected monitors in that

state, except where responsibility for compliance with 40 CFR Part 58 requirements has

been delegated to a local monitoring agency. Note that even if multiple monitoring

organizations are considered to be with a single PQAO, the certification may come from

the state level, or from each local agency which has delegated responsibilities for

compliance with 40 CFR Part 58.

Only data collected by FRM, FEM, and ARM monitors at SLAMS and SPM monitoring

stations that meet Appendix A must be certified. VCAPCD must certify data for O3, NO2,

PM10, and PM2.5.

The following data does not need to be certified:

• PAMS data

• Meteorological data

The general process to certify the data is presented below:

1. In AQS, generate the AMP600 report.

2. Review the report. Review the AQS flags. Make any corrections necessary to the

data. If corrections are made, run AMP600 again.

3. When satisfied with AQS’s recommended flags, apply a concurrence flag in the

Data Certification Form in AQS and save.

4. Generate the AMP600 again. This populates the district’s flags as concurring with

those assigned with AQS.



5. Have the APCO sign the summary page (page 2) of the AMP600.

6. Write a certification letter for the APCO’s signature and have APCO sign the letter

(see Figure 8 below).

7. Submit all documents to the EPA Regional Administrator, with a cc: to selected

EPA and CARB staff.



Figure 8 Data Certification Submittal Letter



8.0 References

Agilaire LLC., AirVision Manual, January 2016.

California Air Resources Board, Primary Quality Assurance Organization Roles

and Responsibilities for the Air Resources Board and Ventura County Air

Pollution Control District, October 24, 2014.

California Air Resources Board, Quality Assurance Bulletins, various dates.

U.S. EPA, Quality Assurance Handbook for Air Pollution Measurement Systems,

Volume II, Ambient Air Quality Monitoring Program, EPA QC Manual Vol. II,

Appendix D, Measurement Quality Objectives and Validation Templates, March

2017.

U.S. EPA, QA Handbook for Air Pollution Measurement Systems: "Volume II:

Ambient Air Quality Monitoring Program" (EPA-454/B-17-001), January 2017.

U.S. EPA, Meteorological Monitoring Guidance for Regulatory Modeling

Applications (EPA-454/R-99-005), February 2000.

U.S. EPA, Quality Assurance Handbook for Air Pollution Measurement Systems,

Vol. IV: Meteorological Measurements, Version 2.0, (EPA-454/B-08-002), March

2008.

U.S. EPA, Air Quality System (AQS) User Guide, August 4, 2016.

Environmental Systems Corporation, E-DAS Ambient for Windows Version 5.50,

March 2005.

California Air Resources Board, Corrective Action Notification SOP, October

2014.





https://www.arb.ca.gov/aaqm/qa/qa.htm

https://www3.epa.gov/ttn/amtic/files/ambient/pm25/qa/APP_D%20validation%20template%20version%2003_2017_for%20AMTIC%20Rev_1.pdf



https://www3.epa.gov/ttn/amtic/files/ambient/pm25/qa/Final%20Handbook%20Document%201_17.pdf

https://www3.epa.gov/ttn/amtic/files/ambient/pm25/qa/Final%20Handbook%20Document%201_17.pdf

https://www3.epa.gov/ttn/scram/guidance/met/mmgrma.pdf

https://www3.epa.gov/ttn/scram/guidance/met/mmgrma.pdf

https://www.epa.gov/ttn/amtic/files/ambient/met/Volume%20IV_Meteorological_Measurements.pdf

https://www.epa.gov/ttn/amtic/files/ambient/met/Volume%20IV_Meteorological_Measurements.pdf

https://www.epa.gov/aqs/aqs-users-guide-0

https://www.arb.ca.gov/aaqm/qa/pqao/can/can_sop.pdf

Date post:	15-Feb-2019
Category:	Documents
Upload:	truongkhanh
View:	231 times
Download:	0 times

DATA REVIEW AND VALIDATION - arb.ca.gov · SOP VC600 Data Review, Verification, and Validation...

Documents