# Presentation: 249796

## Implementation of the Exceptional                Event Rule In AQS

- AQS Conference
-                    August 21, 2008

## Exceptional Event Rule

- Background/History
- AQS Implementation
- New Qualifier Codes
- Database Changes
- Software Changes
- New Report
- System Implementation

## Background/History	                                                                          

- Background/History

- Exceptional event data – defined initially in a EPA guideline for monitoring data
- Defined applicable events and pollutants applicable
- Regional Concurrence for exceptional event
- Data summarized (3 records) based on event flag and concurrence
- Exceptional Events Split into categories in current AQS
- NAT – caused by nature
- EX – caused by man
- Data summarized (7 records) by category and concurrence
- Exceptional Event Rule (EER) became effective May 21, 2007
- Authorized data exclusion from attainment analysis
- Expanded/increased documentation and defined schedule for submission
- Created revised definitions for events and applicable pollutants

## AQS Annual Summary Records

## AQS ImplementationNew Qualifier Codes

- AQS ImplementationNew Qualifier Codes

- Problem with current codes
- Same flags apply to all pollutants
- Always creates multiple summary records
- Low response rate for concurrence
- New codes
- Differentiate purpose - documentation or regulatory
- Match regulatory definitions for events
- “Other” category for undefined events
- Comments assist in defining event

## AQS ImplementationNew Qualifier Codes

- AQS ImplementationNew Qualifier Codes

- Types
- INFORM
- Informational only - no application for the EER
- Document any event that might affect concentration
- Use with any pollutant
- REQEXC
- Criteria pollutants – concentration above NAAQS or contribute
- Documentation/comment – submission schedule defined
- EPA concurrence action – required and based on submitted documentation , defined schedule to respond

## Old and New EE Qualifiers

## AQS Implementation Database Changes

- AQS Implementation Database Changes

- Add creation dates to several database records to track date submitted
- Add tables to document an “event” (several days and impacts multiple monitors)
- Add documentation fields for flags
- Add all applicable new codes to reference tables

## AQS ImplementationSoftware Changes

- AQS ImplementationSoftware Changes

- Develop process to maintain “events” – to enter comments for multiple raw data values
- Modify the concurrence process for the new flags
- Modify the update process to retain initial update date
- Modify the summary process to compute fewer records (no events, included, omit concurred)
- Modify reports to display the new summary records

## AQS Implementation New Report

- AQS Implementation New Report

- Report created using standard report process
- Standard geographic selections
- Pollutant and date range selection
- Report and/or Work file
- Report options
- Flag types – INFORM, REQEXC, QA, NULL
- Concurrence value – blank, yes, no
- Counts by monitor of flags

## AQS Implementation New Report

- AQS Implementation New Report

- Example format
- Additional meta data?
- Other data elements

## AQS Implementation New Report

- AQS Implementation New Report

## System Implementation

- Install software
- EX/NAT Code Conversion
- Make codes invalid
- INFORM if not concurred
- REQEX if concurred
- Calculate new summary records