1 Air Quality System (AQS) Status and Plans Part 1: Nick Mangus US EPA Boring Infrastructure Stuff Part 2: Mike Matsko NJDEP (Representing AQDE Team) Interesting Implementation Projects

2 Topics for Part 1: Status & Plans AQS and AirNow Background –Similar Data –Separate flows Flow Status –Node Flow –New Version of Schema –Flow Automation Data Publishing plans Communications Turn over to Mike I believe what happens in history is this: the old are always wrong; and the young are always wrong about what is wrong with them. -- G.K. Chesterton

3 AQS Background Collects air quality data (pollution and related information) Data is used to determine non- attainment areas and by health researchers Managed and operated in RTP, NC 1,000+ sites around the country 200+ parameters collected Reporting schedule: varies, but generally, data required 90 days after end of calendar quarter in which it was collected We get almost 2M data points per week from State, local, and tribal agencies (several hundred files) Highest volume through CDX

4 AirNow Background Collects air quality data (pollution and related information) and forecasts Data is used to inform public of immediate health concerns Managed in RTP, NC Operated in Sonoma, CA 1,000+ sites around the country (same as AQS) 2 primary parameters collected, anything allowed Reporting schedule: every hour for data; every day for forecasts Data converted into near-real-time maps at Not yet on the Exchange Network

5 Status – Continuing to Improve AQS –Accepts data via Node since May 2005 –Many formats Legacy flat file New flat file Schema v1.0 Schema v2.0 (almost!) –New version of the schema will be released soon (responding to conformance review) –“AQDE” = “AQSv2” AirNow –Working to implement node at DMC –Will use same schema for air quality data (not forecast) submissions –Pilot project completed (q.v. Part 2) When you break the big laws, you do not get freedom; you do not even get anarchy. You get the small laws. -- G.K. Chesterton

6 New Schema Version 1 developed with a pure information engineering approach –Node submission to feds –Minimize instance document size Version 2 developed for flexibility of exchange –ESAR compliant –Revamped structure Flat versus hierarchical –Better facilitates non-federal (e.g, state-to-state) sharing –Focus was “Air Quality” not just AQS –Will incorporate data for AirNow exchanges Testing plan / ability Progress is a comparative of which we have not settled the superlative. -- G.K. Chesterton

7 XML Testing AQS Node AQS PROD AQS QA Two databases –AQS Production (AQSPROD) –AQS Quality Assurance (AQSQA) AQSPROD database was backed up to AQSQA on Data and passwords will be as of then (90 day exp.) Contractors cannot get access Call helpdesk with problems EPA

8 Submission Automation The simplification of anything is always sensational. -- G.K. Chesterton

9 Data Publishing No node publishing yet –Users can get XML data from AQS as you get any other data New system for dissemination: AQS Data Mart –Prevent competition for resources –Uses CDX/EN web services Node client in test –Same protocol as AQDE project –No FCD yet –Additional web services geared toward scientists Additional schemas Stylesheets –Client for human interaction –Will eventually include AirNow data –Technical issue with SOAP message size and physical memory of EPA and client hardware Will then work on publishing from AQS –Smaller audience We look forward with enthusiasm because we are afraid to look back. -- G.K. Chesterton

10 Communications Helpdesk IPT calls: –Every other Wednesday –May 09 is the next one –3:00 pm eastern – , code # Nick Mangus –

11 Questions & Mike