NACAA Webinar 9-16-10.Metcalf

AFS Modernization:

Current Status and

Direction for Upcoming EventsDirection for Upcoming Events

NACAA Webinar

9/16/2010

1

Betsy Metcalf, AFS System AdministratorUS EPA, OECA, OC, ETDD, DSIMB(202) 564-5962, [email protected]

2

AFS will be modernized, not solely because it is technologically obsolete, but because it does not meet the needs of the

Clean Air Act Stationary Source compliance monitoring and enforcement

programs.

Successful Completion of the Air Facility System (AFS)

Modernization Project will:

•Strengthen and improve the national management

and oversight of the CAA enforcement and

compliance program by fully supporting existing and

adapting to future/emerging needs.

•Provide streamlined and easy transmission and receipt of electronic data among EPA, our state and local partners, and the regulated community, in part

Product of the OECA AFS Modernization Strategy Group

local partners, and the regulated community, in part by leveraging web services and the EPA and State

capabilities in the National Environmental Information Exchange Network (NEIEN).

•Improve collaboration and communication by utilizing modern web-based technologies.

•Increase transparency and accessibility by facilitating availability, sharing and integration of CAA

enforcement and compliance data/information with Agency stakeholders, including the public.

•Protect enforcement sensitive and CBI information in accordance with Agency information security policies

and guidelines.

What’s been done to date

• 2002 Needs Analysis

• 2004 State Modernization Workgroup

• 2008 Business Case Analysis

• 2009 Management Strategy Workgroup• 2009 Management Strategy Workgroup

• 2010 Summer: Needs & Requirements

Refresh

• 2010 Alternatives Analysis

• 2010 Work in Progress-Design Alternative

Selected4

Alternative Analysis

• The recently completed Alternative Analysis

recommended three approaches for AFS

Modernization to OECA:

– Utilization of RCRAInfo Programming code and

techniques to create a new AFS;techniques to create a new AFS;

– Incorporation within ICIS either as a new module

or other implementation; or

– Creation of a stand-alone system capable of

integration with ICIS and other systems.

• A decision will be made after briefing

Cynthia Giles. 5

What’s the plan?

• Fall 2010: Final Requirements Document

• Fall 2010: Research possible implementation

alternatives within ICIS

• Fall 2010: Brief Cynthia Giles on the • Fall 2010: Brief Cynthia Giles on the

modernization approach

• FY2011: Begin Design Phase

• Spring-Summer 2011: National Stakeholders

Meeting?

6

What’s New?

• Plans for a Document Management

Capability

– Working with OAR on the ability to transfer

electronic documents such as permits, electronic documents such as permits,

notifications, stack test reports, excess emission

reports and more.

• Plans for a Notification Process

– Ability to send messages and notifications to users

– Data quality checks

7

What’s New?

• Automated Compliance Status

– Status will generate from reported data*

• Integration with other Data Marts• Integration with other Data Marts

– Access to IDEA information including Emission

Inventory information, the new Green House Gas

(E-GGRT) database, and others

• Ability to use the Exchange Network

– New XML schema

8*EPA is still working out the mechanics of this for Federally-Reportable Violations

What’s New?

• Plant Information will be broken out into three sections:

Plant

General

Compliance

Monitoring Enforcement

Activities

9

Geographical

Default Values

Air Programs

Pollutants

FCEs & PCEs

Stack Tests

Investigations

TV Annual Compliance

Certifications

Others

Notices of Violation

Administrative Orders

Consent Decrees

Referrals

GeneralMonitoring

ActivitiesActivities

What new data requirements are

we talking about?

• Partial Compliance Evaluations

• Stack Tests: Date of Review and Pollutant

• Title V Annual Compliance Certifications

10

• Title V Annual Compliance Certifications

(TVACCs): Permit ID Number, Period of

Evaluation, Date Due, Date Received and

Deviations Reported

HOWEVER,If designed carefully,

electronic document

metadata could satisfy

reporting requirements for

11

reporting requirements for

both Stack Tests and

TVACCs, requiring only

the results of the

delegated agencies’

review.


we talking about?

• Compliance Status Generation: On all

Compliance Monitoring activities the question

will be asked: “Was violation found? Yes/No”

• Federally-Reportable Violation (FRV)

12

• Federally-Reportable Violation (FRV)

Reporting: To close out a violation for an FRV,

a Return to Compliance Action may be

required. Automatic Generation of

Compliance Status for FRV Violations is

currently under review.


we talking about?

• Enforcement Actions: Final and Collected

Penalty

• Tribal Indicator: Tribal ID (EPA Standard)

13

• Portable Source Indicator: Yes/No

• Many new OPTIONAL fields will be added.

Non-mandatory fields such as:

•Lat/Long

•Owner Names & Contact Info

•Name Change History

•Contact emails

•Title V Permit Fields

•Portable Source Work Locations

•Process Information

•Comments throughout the system

Recommended Data for

Reporting ActivitiesFull and Partial *

Compliance Evaluations

• Date of Activity

• Description of Activity

• Optional: Comments

Investigations and Excess Emission Reports (EERs)

• Date of Report

• Description of Activity

• Optional: Comments• Optional: Comments

• Optional: Process

Information

• Violation Case Identifier

(HPV)


• Optional: Process

Information

• Optional: Monitor Data

• Optional: EERs


(HPV)

*Indicates new data requirements for state and local agencies14


Reporting Activities

Stack Tests

• Type of Test

• Date of Test

• Date of Review*

Pollutant*

Title V Annual Compliance Certifications

• Permit ID and Review Timeframe*

• Due Date*

• Date Received*• Pollutant*

• Review Findings (Pass/Fail)


• Optional: Stack Description


• Optional: Process Information

• Date Received*

• Date Reviewed

• Review Findings


• Deviations*


• Optional: Process Information




Noncompliance-HPV

• Case Identifier

• Day Zero

• Violating Pollutants

• Violation Type

Noncompliance-FRVTier 1 or 2

• Violation: Yes/No*

• Return to Compliance Date*

• Optional: Comments• Violation Type

• Discovery Date

• Addressing Action

• Assessed Penalty

• Final Penalty*

• Resolution Date




Requirements for FRVs still

under review and analysis



Enforcement Actions

• Source ID

• Type of Action

• Date

Electronic Documents*

• Source ID*

• Activity Type* (FCE, PCE,

Investigation, Stack Test, TV

Ann Cert, • Date

• Assessed Penalty

• Final Penalty*

• Collected Penalty*



Ann Cert,

Notifications,Enforcement,

etc.)

• Activity Milestones*

(Defined by Activity Type)





Optional: Title V Permits

• Source ID

• Permit ID

• Type of Permit

Issued Date• Issued Date

• Effective Dates

• Expiration Date

• Dates Due for TV ACCs

• Major Modifications

• Comments


How about a new name???

OPEN AIROPEN AIR

AIRCOPSAIRCOPS

19

What can YOU do

To improve AFS Modernization?To improve AFS Modernization?

Join our team to work on:

•Final Requirements Approval

•Schema Development

•Design Activities

Contact Betsy Metcalf for details20