STANDARD OPERATING PROCEDURES FOR barbara/sb... · supervisor provide further general oversight with a special emphasis on investigation of the highest measured pollutant concentrations

SANTA BARBARA COUNTY AIR POLLUTION CONTROL DISTRICT

STANDARD OPERATING PROCEDURES

FOR

DATA REVIEW AND VALIDATION

August 2017

SBCAPCD SOP Data Review and Validation First Revision, August 2017

1

SANTA BARBARA COUNTY AIR POLLUTION CONTROL DISTRICT

Approval of Standard Operating Procedures (SOP)

DATA REVIEW AND VALIDATION


2

TABLE OF CONTENTS DATA REVIEW AND VALIDATION

Page(s) Date 1.0 GENERAL DESCRIPTION 3 08/17

1.1 Purpose 3

1.2 Responsibilities 3

1.3 Personnel Qualifications 3

2.0 DATA ACQUISITION 4-5 08/17

2.1 Collecting Data 5

2.2 Data Storage 5

3.0 ENABLING/DISABLING CHANNELS IN SITE

DATA LOGGERS 6-8 08/17

3.1 Enabling/Disabling Channels in 8872

Data Loggers 6

3.2 Enabling/Disabling Channels in 8832

Data Loggers 7

4.0 USING AIRVISION TO EDIT AND REVIEW DATA 9-15 08/17

4.1 Logging in to AirVision 9

4.2 Running Reports in AirVision 10

4.3 Editing Data in AirVision 11

4.4 List of AQS Null Codes, AirVision Data Flags,

and AQS Qualifier Codes 11

5.0 ONGOING REVIEW TO MINIMIZE DATA LOSS 16-17 08/17

6.0 MONTHLY LEVEL 1 DATA REVIEW AND PROCESSING 18-27 08/17

6.1 General Guidelines on Data Review 18

6.2 Level 1 Review Procedures 19

7.0 MONTHLY LEVEL 2 DATA REVIEW 28-30 08/17

7.1 Monthly Level 2 Data Review Procedures 28

8.0 MONTHLY LEVEL 3 DATA REVIEW 31-33 08/17

8.1 Monthly Level 3 Data Review Procedures 31

REFERENCES 34


3

1.0 GENERAL DESCRIPTION The SBCAPCD's air monitoring program collects real-time ambient air pollutant and meteorological values across Santa Barbara County. The program is designed to ensure the quality of the data collected and disseminated by the SBCAPCD, as part of the CARB Primary Quality Assurance Organization (PQAO). The data generated are used to determine which areas of Santa Barbara County are in attainment, or non-attainment of federal and State air quality Standards, impacts from local sources, and/or the severity of air pollution in Santa Barbara County. The data are also used in air models and real-time air quality public alerts. This Standard Operating Procedure (SOP) contains specific details on performing data acquisition, editing, and revision in SBCAPCD’s Data Management/Acquisition System (AirVision), and also the general elements that should be evaluated during the multi-step data review and validation process. 1.1 Purpose The purpose of this document is to outline how SBCAPCD 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 Responsibilities 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). A second reviewer, usually one of the other station operators, is responsible for reviewing the work performed by the site operators 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.” The monitoring section supervisor provide further general oversight with a special emphasis on investigation of the highest measured pollutant concentrations and any measurements exceeding state or federal air quality standards. 1.3 Personnel Qualifications 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. All air monitoring staff at SBCAPCD are hired as Air Quality Specialist I, II, III, or Monitoring/IT Supervisor positions. 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.


4

2.0 DATA ACQUISITION The task of data acquisition involves retrieving ambient air quality data from each analyzer, transmitting the data from the field stations to the District office central data acquisition system (DAS), and ingesting the data into a central database. Station operators are then able to review, edit and validate the air quality data. Figure 1 outlines the data collection, review, and validation process.

Figure1: Data Collection, Data Review, and Data Validation Process

Gas Analyzers and

Meteorological Sensors BAM Particulate

Monitors

Agilaire 8832/8872

Data Logger

Agilaire AirVision Central

Data System

Level 1 Review

Level 2 Review

Supervisory Review

Upload to AQS


5

2.1 Collecting Data SBCAPCD’s data acquisition for gas and meteorological parameters is composed of two systems: A primary system utilizing the Agilaire 8832 or 8872 data logger, and a backup system utilizing each analyzer’s internal data logging feature, only where the analyzer has the data logging capability. The Agilaire 8832/8872 continuously polls each gas analyzer, via Ethernet utilizing Modbus protocol (or via back up voltage signal), and processes minute and hourly averages into data files. Meteorological parameters are acquired by the 8832/8872 data logger via voltage signals from the sensor. Particulate parameters (PM10 and PM2.5) are measured with the MetOne BAM 1020 and also have two systems. The primary data acquisition of hourly and operational parameters from the particulate monitors are accomplished by direct polling via the internet of each particulate monitor by the Districts AirVision central data acquisition system. The backup system utilizes the internal data logging feature of the BAM monitors. Both data acquisition systems are operated at all SBCAPCD ambient air monitoring stations for either primary data acquisition or for backup and troubleshooting, using the internal data logging feature of each analyzer where available. Each station’s 8832/8872 data logger is polled by the central AirVision server once each minute and sends the minute, hourly, and calibration data for all gas analyzer and meteorological sensors. The minute and hourly values include both concentration data and operational data from each gas analyzer. Each stations BAM monitor(s) are directly polled for concentration and operational parameters by the central AirVision server once each hour. SBCAPCD’s station operators can view and edit the station’s minute and hourly data using their PC workstation through an AirVision client software. The SBCAPCD central AirVision server is programmed to automatically send email alarms to the appropriate site operator whenever concentration or operational data exceeds normal/expected values. In the event of an intermittent failure of site data logger, SBCAPCD staff has the ability to utilize the backup system, if available, and download the data from each analyzer directly, then incorporate the data into central AirVision database. 2.2 Data Storage AirVision was developed by Agilaire, Inc., using Microsoft SQL server database. AirVision resides on a server maintained at SBCAPCD’s office. SBCAPCD staff utilizes AirVision client software to review, edit, and generate reports of air quality data stored by AirVision in the SQL database.


6

3.0 ENABLING/DISABLING CHANNELS IN SITE DATA LOGGERS This section is a means of quickly navigating through the 8832 or 8872 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 Agilaire 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 8872 Data Loggers Enabling/Disabling channels is accomplished with the use of the site node logger toolbox. The site node logger toolbox screen is accessed in the main menu under Utilities. Each channel has an option to disable data acquisition and flag the channel as maintenance with an “M” flag or simply disable the channel and apply a “D” flag. The only time data acquisition is stopped and the “M: flag is applied is when true instrument maintenance or instrument removal from the station occurs. Each channel has a column to disable data acquisition entirely (Enable), to acquire the data, but flag as disabled with a “D” flag, and a column to acquire the data, but flag as maintenance with a “M” flag. The Enable column is utilized to disable data acquisition when an instrument is removed from the site or powered down. The Disable Flag column is utilized whenever an analyzer or sensor is taken offline for purposes other than maintenance. And the Maintenance Flag column is utilized to take an analyzer or sensor offline to perform maintenance. Each column has a button to click on for each channel to accomplish the appropriate enabling/disabling.

Figure 2 – 8872 Site Node Logger Toolbox Screen


7

3.2 Enabling/Disabling Channels in 8832 Data Loggers Agilaire 8832 data loggers also have the same ability to continue data acquisition, but flag data as either disabled “D” or in maintenance “M”. There is also an option to enable and disable Modbus client devices. This is used when an instrument is taken offline or removed for maintenance in order to prevent data disruption from other instruments gathering data via Modbus. 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.


8

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.

Disable Modbus Client Devices

1. Select Status menu. (hot key S) from the Home Menu. Select view Modbus status (hot key V) from the logger status Menu. Select disable Modbus client devices (hot key D) from the Modbus client status Menu. Choose either Ethernet or serial devices. A list of existing active instrument IP addresses will display. Choose the instrument IP that corresponds to the instrument being maintained or removed and hit enter.

Enable Modbus Client Devices 1. Reverse.


9

4.0 USING AIRVISION TO EDIT AND REVIEW DATA This section is a means of quickly navigating through AirVision for the purposes of reviewing, and editing data. It should not be considered an in-depth manual into all the functions of AirVision, refer to the AirVision manual for a description on other operations of AirVision. 4.1 Logging in to AirVision Each staff is assigned a unique user name and password to access AirVision using a AirVision client software residing on each staff’s PC or laptop. Access is available from the District LAN (and all air monitoring sites) as well as via an internet connection. From the computer desktop, click on the AirVision icon (or find AirVision in the programs menu). When the login screen appears, enter your AirVision User Name and Password on the menu screen, then select “OK”. The main menu screen will become visible after a short automated brief delay. The main AirVision screen should now be viewable. 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 of the 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 has 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 3- Report Generation Screen


10

Some of the more commonly utilized standard reports and their typical use are listed in the table 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 Editing Data in AirVision 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 a 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.


11

Figure 4- Data Editor Screen

4.4 Lists of AQS Null Codes, AirVision Data Flags, and AQS Qualifier Codes Tables 2-4 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 2 – 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


12

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


13

Table 3 – 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


14

Table 4 – 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


15

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.


16

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 SBCAPCD. The following actions should be taken by all SBCAPCD 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. All parameters are programmed with high/low flags (and alarms), pay special attention to any values with these flags.

d. 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.

e. 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 (indicated with a “*” on report).

b. Review calibration trends with the use of a control chart, using the Calibration X Bar R Viewer Report in AirVision. 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 at least once a week.

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


17

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 IT/Monitoring Supervisor immediately so other staff can be assigned.

IT/Monitoring Supervisor:

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.


18

6.0 MONTHLY LEVEL 1 DATA REVIEW AND PROCESSING The station operator is responsible for performing the level 1 data review and processing. This task should be performed as soon as possible after the end of each calendar month to ensure timely response to any potential problems uncovered in the review as well as ensuring that data is finalized and submitted to AQS within the required time period (Each calendar quarter of data shall be submitted to AQS within 90 days of the end of the quarter). The station operator will have performed daily review of data as outlined in Section 5 of this SOP, so should already be familiar with any unusual issues in the month’s data set. However, the monthly level 1 review provides a more detailed review of all data values and QC results allowing the site operator to make final decisions as to the validity of each data value. Any data deemed invalid by this review will be invalidated in AirVision, with assigning the appropriate null code. Additionally, qualifier codes can also be assigned to any data value by the site operator in this review. Data that has been manipulated or invalidated outside of the automated flagging procedure done by AirVison should be annotated by the editor to explain the change made and why. This ensures the second level data reviewer has the information necessary to understand first level data validation. It also keeps an electronic record of who, when, and why data was manipulated. 6.1 General Guidelines on Data Review Data review will be greatly enhanced if the station operator is conscious of several aids. These are listed below:

1. The station operator should be familiar with typical diurnal (daily) concentration variations (e.g., the times daily maximum concentrations occur and the interrelationship of pollutants). For example: Carbon monoxide (CO), nitric oxide (NO), and hydrocarbon (HC) concentrations usually increase and decrease together; 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 station operator 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 large shifts in wind speed and direction, are a sign of water disrupting the sonic path for sonic wind sensors, and require data invalidation. Spikes or sudden shifts in the ambient temperature trace are a sign of a sensor beginning to fail.


19

6. Excessively negative PM values (<-4ug/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. Station operators should continuously review the automated emails from AirVision for their stations. These automated emails provide information on any alarm conditions present on instrumentation.

10. 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 Review Procedures 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. A data processing check sheet (figure 5) is used to ensure that each step of this process is followed. The process involves reviewing a monthly report for each parameter, reviewing all site documentation and calibration records and noting any changes to the data set that need to be made based on the review of records. Any changes or edits to the data set are annotated in AirVision. The AirVision annotation will record who made the edit, the reason for the edit, and date/time. These annotations are automatically stored in the AirVision database to document all changes to the data set. Note that the AirVision database maintains all original data, even when data values are edited or flagged. Additionally, any edits to the database are tracked with the timestamp of when the edit was performed and who made the edit. Once the data


20

technician is satisfied that the data set is correct, an Excel file that documents the progress of each month of data being processed is initialed to indicate the Level 1 review has been completed. These records are then reviewed by a different site operator to provide the Level 2 review to ensure that all actions taken in the Level 1 review are appropriate. Finally, the IT/Monitoring Supervisor reviews both the Level 1 and Level 2 reviews, but focus on the highest recorded concentrations and health standards exceedances to finalize the data. Once the data is final, AQS files are uploaded to AQS and all check sheets, marked up monthly reports, and other documents are filed. The step by step procedure for the monthly processing of gas pollutants, PM2.5, PM10, and meteorological data (Level 1 review) from a single monitoring site is as follows: 1) Using AirVision, perform an initial review of the monthly report for each parameter to become familiar with the monthly data for each parameter. 2) Review all site documentation for the month. This includes site logs, site checks, equipment QC and maintenance sheets. If site documents indicate a period of data that is invalid or requires adjustment make an annotation to the data in AirVision for the period affected. 3) Review each monthly report; focus any missing data, obvious erroneous data, and any questionable data value. Query all monthly parameters with each Parent Parameter (ie Ozone, PM10, PM2.5, Wind Speed, Wind Direction) grouped with the daughter channels (ie O3 sample flow, O3 lamp temp, etc). The daughter channel data is used to support the validity of the parent pollutant parameters. All 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 null or informational codes using the AirVision data editor. Document the reason for any edits by annotating the data in AirVision. 4) Review site documentation to ensure that each of the following tasks were performed within the required interval. Table 5 below provide 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


21

Non-Ozone Gas Parameters


Certification of Calibrator Flows

3 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

14 Days

Full Calibration 6 Months

Zero Background Check 1 Year

Sonic Wind Sensors


Wind Tunnel Calibration 1 Year

Ambient Temperature


Multi-point Calibration 6 Months

Station Temperature


One Point Calibration 6 Months

Table 5- Required QC Tasks and Frequency 5) Review the station temperature monthly report. Station temperature is typically maintained between 20-30 Deg.C. If any hours are outside this range, check the EPA equivalency operating temperature range (Table 6 below) for each gas analyzer operating in the site is within the allowable temperature range. If the station temperature exceed the allowable temperature range for any instrument, invalidate those hours and noting the reason by annotating in AirVision. Also review for temperature change from hour to hour. Changes greater than +/-2 Deg C from one


22

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. change in temperature.

Instrument Minimum Operating Temperature (DegC)

Maximum Operating Temperature (DegC)

TAPI 100E/T100 SO2 5 40

TAPI 200E/T200 NOx 5 40

TAPI 300E/T300 CO 10 40

TAPI 400E/T400 Ozone 5 40

TEI 43i SO2 20 30

TEI 42i NOx 15 35

TEI 48i CO 20 35

MetOne BAM 1020 PM10/2.5 0 50

Table 6 – EPA Operating Temperatures 6) In order to evaluate calibration data for each gas parameter, generate a monthly calibration control chart for all gas parameters using the Calibration X Bar R Viewer in AirVision. A separate control chart is generated for zero, precision, and Level 1 calibration points. Research any calibration points exceeding warning limits to determine if the calibration was performed correctly, that the calibration system was operating correctly, and was captured correctly by the data logger. Any calibration points determined to be generated incorrectly due to problems with the calibration system are excluded in the AirVision calibration database using the Calibration Editor. Any calibration points determined to be captured incorrectly by the data logger are edited to the correct value in the AirVision calibration database using the Calibration Editor. DO NOT EDIT ANY CALIBRATION POINT THAT APPEARS TO BE GENERATED AND CAPTURED CORRECTLY REGARDLESS OF WHETHER THE POINT IS WITHIN TOLERANCE. If any edits were made to the AirVision calibration database, re-generate the control chart to reflect these changes. 7) Review all gas parameter calibrations for the month presented in the final control charts generated in the above step. If data is bracketed with valid calibrations whose results are within the validation criteria listed in Table 7 below, the data is validated as is. For any calibration points exceeding warning limits, corrective action must be taken ASAP unless corrective action was taken previously during ongoing data review. Any period of data bracketed with one or more calibration greater than the invalidation criteria listed below must be invalidated (unless other indicators such as meta data 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.


23

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%

1-pt QC Check <=+/-10% <+/-15.1%

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

SO2 Upscale Span/1-pt QC Check

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

CO Zero <=+/- 0.2 ppm <+/- 0.41 ppm

CO Upscale Span/1-pt QC Check

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

Table 7- Gas Parameter Warning and Invalidation Limits 8) 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 such as meta data 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.

Ultrasonic Anemometer

Wind tunnel calibration must show sensor within published specifications. Alignment must be within 2 degrees of true north.

Wind tunnel calibration must show sensor within published specifications. Alignment must be within 1 degrees of true north.

Table 8 – Meteorological Parameter Validation and Corrective Action Limits 9) Review the strip chart record for each parameter that stores minute data for the month. Generate the charts using the AirVision average editor. Multiple parameters can be loaded on the same chart as long as all traces can be distinguished and evaluated. Select the appropriate scale or auto-scale. Best to generate the chart periods of 24 hours to allow evaluation of daily patterns.

Spot check any gas analyzer auto-cal response listed in the auto-cal worksheet exceeding warning limits against the strip chart value. Do not invalidate an auto-cal value just because the result was out of tolerance if it appears the result is actually how the analyzer responded. Do invalidate or edit an auto-cal value if it


24

appears that the result is not representative of how the analyzer actually responded or if it appears the calibrator malfunctioned.

Study the gas parameters chart trace looking for atypical patterns.

For ozone, pay attention to periods where the trace does not change for over 8 hours, especially if under 20ppb (in mid day) or over 100ppb. Expect the normal diurnal pattern for ozone. Watch for positive spiking. Negative spiking can occur due to Nox titration from a nearby source. Negative spiking is unusual in mid day. Invalidate and flag any hours with apparent errors based on the chart traces by annotating in AirVision.

Study the wind speed, direction, and temperature traces. Pay attention to sudden shifts in wind speed that is not accompanied with a shift in direction. Watch for periods of inactivity in the trace as this could indicate a malfunctioning sensor. Examine the wind speed trace when low speeds are present. Invalidate and flag any hours apparent errors based on the chart traces by annotating in AirVision.

10) 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 11) 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. 12) 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


25

minimium 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

SO2 -5 ppb

CO -.05 ppm

PM2.5 -5 ug/m3

PM10 -4 ug/m3

Table 10 – Minimum Allowable Hourly Values 13) Review the actual flow sample volume monthly report for each BAM sampler to ensure that all valid hourly values of PM10 or PM2.5 had a sample volume for that hour within the allowable tolerance of +/-5% of the design value (see table 11 below). AirVision is configured to flag any values exceeding these tolerances to allow for easy review of these values. Invalidate any values exceeding this tolerance using the AirVision data editor, and document the invalidation reason by annotating the data in AirVision.

Parameter Normal Sample Volume

Maximum Sample Volume (+5%)

Minimum Sample Volume (-5%)

PM10 (50 minute sample period)

.834 m3 .876 m3 .792 m3

PM2.5 (42 minute sample period)

.700 m3 .735 m3 .665 m3

Table 11 – PM10/2.5 Sample Volume Validation Criteria

14) Investigate each instance of missing data. Wind speed and direction data can only be retrieved from chart for scalar wind speed/direction parameters, vector averaged wind speed/direction and sigma theta cannot be retrieved from chart records. Determine if any missing gas parameter data can be recovered from the chart or internal analyzer stored data. Determine if missing PM2.5 or PM10 data can be retrieved from the BAM internal memory. If data can be retrieved from chart or BAM internal memory, enter the correct data using the AirVision editor and annotate the reason for the edit of the data. 15) Sign and date the review checksheet and alert the Level 2 reviewer that the data has passed the Level 1 review and is available for the Level 2 review. 16) 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


26

data are thoroughly reviewed and considered. See Reference section for link to CAN

SOP.


27

SANTA BARBARA COUNTY APCD LEVEL 1 DATA REVIEW AND VALIDATION Month Year Technician

1) Perform an initial review monthly reports for each parameter. 2) 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.

3) Review each monthly report. 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.

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

5) Review the monthly report for station temperature (STM). 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.

6) Create a calibration control chart for each gas pollutant for the month in AirVision. 7) Review gas pollutant calibration control charts. Invalidate any data periods not meeting drift

requirements.

8) Review meteorological calibrations for the period. Invalidate any data periods not meeting acceptance criteria.

9) Review the strip charts for gas parameters and meteorological parameters. Check that the cal response on the control chart matches the chart value. Whenever the chart shows unusual or questionable patterns, investigate and make any necessary edits in AirVision. Annotate any changes made in AirVision.

10) 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.

11) 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.

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

13) Review sampled actual volume records for the month for PM2.5 and PM10. Invalidate all PM2.5 or PM10 hourly concentrations where the corresponding sample volume is not within the required +/-5% of the design flow value.

14) 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 on the monthly report. 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.

15) 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. Date and initial in the Deadline.xlsx spreadsheet found in \\sbcapcd.org\shares\Groups\monitoring\AQS.

Figure 5 – Monthly Level 1 Data Review Check Sheet


28

7.0 MONTHLY LEVEL 2 DATA REVIEW The monthly data Level 2 review is utilized to provide a second set of eyes to review the work performed in the Level 1 review. The Level 2 review is performed by a different site operator than the operator of the site that performed the Level 1 review. The Level 2 review should be performed within 14 days of receiving the Level 1 review submittal to ensure timely response to any outstanding issues and ensure that AQS submittal is performed within 30 days following the end of each calendar quarter. 7.1 Monthly Level 2 Data Review Procedures A data processing check sheet (figure 6) is used to ensure that each step of this process is followed. The process involves reviewing the changes to the data set from the Level 1 review, all site documentation and calibration records to ensure all actions and determinations made in the Level 1 review were appropriate. Should the Level 2 reviewer have a different determination on any data values, this issue is discussed with the Level 1 reviewer to allow both reviewers to reach a consensus. Any additional changes or edits to the data set are made using the AirVision data editor and documenting any changes by making annotations to the data values. The step by step procedure for the monthly Level 2 review from a single monitoring site is as follows: 1) Review Site Log and other site documentation. Note any entries indicating possible problems with any equipment, indications of potential invalid data, or local conditions that could influence ambient data. 2) Run the monthly summary and the annotation report in AirVision for all parameters. Review annotations and how they relate to the monthly data. Ensure that all changes to the data (invalidation, retrieval of lost data, etc) have logical reasons for the action taken in the Level 1 review. Investigate any issues that are unclear. Discuss with the Level 1 reviewer for further clarification. 3) Review calibration data for each gas parameter using AirVision reports. The Calibration X Bar R Viewer will generate calibration control charts for quick review. Review meteorological calibration records. Review BAM calibration/verification data. Ensure that any periods exceeding calibration/verification tolerance were correctly invalidated. Confirm that records of analyzer operational data indicates equipment was within allowable tolerances. 4) Confirm that required QC checks were performed as listed in EPA QA Vol II, Appendix D. 5) If unusual values, that appear valid based on review are present, compare with other nearby site(s) as an added tool to determine validity. It is important to understand that not all nearby sites data is always similar, so use caution in this evaluation. If there is a question if the nearby site is typically representative of the site data being reviewed, compare some historical data from both sites to better understand the data relationships between the two sites.


29

6) If any differences in determination of validity from the Level 1 review occurred in the above steps, discuss with the Level 1 reviewer to reach a consensus on the best course of action. 7) If any changes to validity or values are needed, make those changes in the AirVision database using the average data editor. Document all changes by annotating the affected data. 8) Generate AQS strings for all reported hourly data and gas precision checks using AirVision and store in monitoring/AQS folder. 9) Generate AQS strings for BAM flow verifications performed for the month using EPA’s AQS QA Transaction Generator program. Store in monitoring/AQS folder. 10) Add any comments explaining action taken in Level 2 review to the comment section of this check sheet. 11) Submit this check sheet, and any other documentation to the IT/Monitoring Supervisor for Level 3 review. 12) 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 link to CAN SOP.


30

SANTA BARBARA COUNTY APCD LEVEL 2 DATA REVIEW AND VALIDATION

Month Year Technician

TASK OK?

1) Review Site Log and other site documentation. Note any entries indicating possible problems with any equipment, indications of potential invalid data, or local conditions that could influence ambient data.

2) Run the monthly summary and the annotation report in AirVision for all parameters. Review annotations and how they relate to the monthly data. Ensure that all changes to the data (invalidation, retrieval of lost data, etc) have logical reasons for the action taken in the Level 1 review. Investigate any issues that are unclear.

3) Review calibration data for each gas parameter using AirVision reports. Review BAM calibration/verification data. Review any meteorological calibrations for the period. Ensure that any periods exceeding calibration/verification tolerance were correctly invalidated. Confirm that records of analyzer operational data indicates equipment was within allowable tolerances.

4) Confirm that required checks were performed as listed in EPA QA Vol II, Appendix D.

5) If unusual values, that appear valid based on review are present, compare with other nearby site(s) as an added tool to determine validity.

6) If any differences in determination of validity from the Level 1 review occurred in the above steps, discuss with the Level 1 reviewer to reach a consensus on the best course of action.

7) If any changes to validity or values are needed, make those changes in the AirVision database using the average data editor. Document all changes by annotating the affected data.

8) Generate AQS strings for all reported hourly data and gas precision checks using AirVision and store in the monitoring/AQS folder.

9) Generate AQS strings for BAM flow verifications performed for the month using EPA’s DASC program. Store in the monitoring/AQS folder.

10) Add any comments explaining action taken in Level 2 review to the comment section of this check sheet.

11) Submit this check sheet, and any other documentation to the IT/Monitoring Supervisor for Level 3 review.

Additional Comments:

Figure 6- Level 2 Monthly Data Review Check Sheet


31

8.0 MONTHLY LEVEL 3 DATA REVIEW The monthly data Level 3 review is utilized to provide a more in-depth review of critical data. The Level 3 review is performed by the IT/Monitoring Supervisor. The level 3 review focus on the highest pollutant values and/or any values resulting in state or federal air quality exceedances. The Level 3 review should be performed within 14 days of receiving the Level 2 review submittal to ensure timely response to any outstanding issues and ensure that AQS submittal is performed within 30 days following the end of each calendar quarter. 8.1 Monthly Level 3 Data Review Procedures A data processing check sheet (Figure 7) is used to ensure that each step of this process is followed. These procedures step the reviewer through first identifying the highest values and/or air quality exceedances for each reported parameter. Each high value or exceedance is then investigated to ensure the validity of those data prior to finalization of the data. The step by step procedure for the monthly Level 3 review from a single monitoring site is as follows: 1. Note the highest hourly value and Date/hour it occurred from each final monthly

report. 2. Note each hourly value (and Date/hour it occurred) from the appropriate monthly

report that exceeds the value in Table 11 below. This will identify any hourly values exceeding air quality standards based on hourly values.

Parameter Value

Ozone 90 ppb

Carbon Monoxide 20 ppm

Nitrogen Dioxide 100 ppb

Sulfur Dioxide 75 ppb

Hydrogen Sulfide 30 ppb

Table 11- Hourly Values Triggering Air Quality Standards

3. Note any day for PM10 or PM2.5 where the daily average exceeds the value listed in Table 12. This will identify any values exceeding air quality standards based on 24 hour average values.

Parameter Value

PM10 50 ug/m3

PM2.5 35 ug/m3

Table 12- 24 hour Values Triggering Air Quality Standards

4. Generate 8 hour running average reports for ozone and carbon monoxide using AirVision. Note any values that exceed the value listed in Table 12. This will identify any values exceeding air quality standards based on 8 hour averages.


32

Parameter Value

Ozone 70 ppb

Carbon Monoxide 9.0 ppm

Table 12- 8 hour Values Triggering Air Quality Standards

5. Review the chart (gaseous pollutants only) for each noted period identified in steps 1, 2, and 4 above (including the 8 hour rolling average reports for ozone and carbon monoxide). Confirm that the chart trace appears normal, using historical patterns for this site/pollutant as well as the guidelines outlined in Section 6.2 above.

6. Review PM10 and PM2.5 hourly values for each noted period identified in step 3 above in the AirVision average editor. Confirm that each finalized hourly value matches the original value unless there was an appropriate reason to edit the data. Confirm that any PM10 and PM2.5 values in the highlighted periods that were flagged by AirVision due to bad status bits in the BAM data string are correctly invalidated in AirVision with the appropriate null code.

7. Review gas pollutant calibration control charts to ensure that the noted periods are bracketed in time by valid calibration checks within allowable tolerance.

8. Review PM10/2.5 verification/calibration records to ensure that the noted periods are bracketed in time by valid verifications/calibrations within allowable tolerance.

9. If any parts of this review indicates possible errors in the data set, discuss with the Level 1 and 2 reviewers, reach a consensus and make the appropriate corrections. Document these corrections with AirVision annotations.

10. If any corrections to the data set were made, re-generate hourly AQS files and replace the old files with the corrected files.

11. Upload the hourly and QC AQS files to AQS. Confirm upload was successful. This task can be delegated to the site operator or other staff and needed.

12. 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 link to

CAN SOP.


33

SANTA BARBARA COUNTY APCD LEVEL 3 DATA REVIEW AND VALIDATION

Month Year IT/Monitoring Supervisor

TASK OK?

1) Note the highest hourly value on each final monthly report.

2) Note each hourly value on the appropriate final monthly report that exceeds the value to trigger a standards exceedance based on hourly values.

3) Note each day’s hourly values on the appropriate final monthly report that exceeds the value to trigger a standards exceedance based on 24 hour average values.

4) Generate 8 hour running average reports for ozone and carbon monoxide. Note any values triggering a standards exceedance based on 8 hour average values.

5) Review the chart (gaseous pollutants only) for each noted period identified in steps 1-4 above.

6) Review PM10 and PM2.5 hourly values for each noted period identified in steps 1-4 above in the AirVision average editor.

7) Review gas pollutant calibration control charts to ensure that the noted periods are bracketed in time by valid calibration checks within allowable tolerance.

8) Review PM10/2.5 verification/calibration records to ensure that the noted periods are bracketed in time by valid verifications/calibrations within allowable tolerance.

9) If any parts of this review indicates possible errors in the data set, discuss with the Level 1 and 2 reviewers, reach a consensus and make the appropriate corrections. Document these corrections by annotating the data in AirVision.

10) If any corrections to the data set were made, re-generate hourly AQS files and replace the old files with the corrected files.

11) Submit all hourly and QA AQS files to AQS. Confirm the upload was successful.

AQS Upload Performed by:

AQS Upload Completion Date:

Figure 7- Level 3 Monthly Data Review Check Sheet


34

REFERENCES

40 CFR 58 Appendix A

US EPA Quality Assurance Manual, Vol II, Appendix D

CARB Data Review and Validation SOP (AQSB SOP 610)

AirVision Operation Manual, January 2016, Agilaire, Inc.

CARB Corrective Action Notification (CAN) SOP - https://www.arb.ca.gov/aaqm/qa/pqao/can/can_sop.pdf

Documents

STANDARD OPERATING PROCEDURES FOR barbara/sb... · supervisor provide further general oversight with a special emphasis on investigation of the highest measured pollutant concentrations