State/EPA Environmental Information Exchange Network – Overview and Progress

1. State/EPA Environmental Information Exchange Network – Overview and Progress Orientation Meeting – Chesapeake Bay States January 2005

2. EN Core Components • Nodes • Hardware and software used to exchange information on the Network • Transfer point on the Network • Data Exchange Templates • Describe format of data being exchanged • Consist of XML schema • Incorporate Data Standards • XML Schema for flows found in the Registry

3. In Development Operational Not Yet Started Status of State Nodes - January 24, 2005 WA MT ME VT ND OR OR MN NH NH ID WI SD NY MA AK MI WY RI CT IA PA PA NE NJ NV OH IN IL UT DE CO MD WV WV CA VA KS DC MO KY NC TN OK AZ NM NM NM SC AR HI GA AL MS MS TX LA FL FL

4. What does it take to do a Network Flow? • Development of XML Schema and Data Exchange Template • Flow Configuration Plan to establish the web services that can be invoked for the exchange • User Guide to describe the data flow issues • Translators that put the XML file in a format that the Agency can upload into their databases. (Not always, but usually)

5. NE DE TX NJ MA WA DE MS MI VA IA NJ OR WV MS DE KY MA OR PA NH LA NE IL ME NY MD ME MT UT MN MD SD IA NY ND WA DE NC MO OR WV WI MS SC NH KS OH PA AZ CA CO ID IL IN MI NM NJ NE WA OR ID AK WA OR NH NJ ME VT RI IN SC VA MI DE NH CA NC NJ GA eDMR WI FL MI COLOR KEY In Development Operational LA WA DE AZ ME OR WV MI WI MS SC NH KS OH PA NE ID IL IN MD MA MN ND SD IA NV GA KY OK TX UT CA NJ NM NY MO MT NC AK VA WY VT CO Last Update Jan 5, 2005

6. Challenges • The data flows from States to EPA systems are harder than expected, but possible. Why? • Legacy databases are designed primarily for data entry and not data exchange. • Linking with primary keys makes it harder to do some Web Services because sending an update record has so many relationships. • Data ownership issues also need to be addressed in the exchange. Again, can’t simply send an updated record because the State may not the owner of the piece of data linked to another piece of data. Therefore, we have to find a way to identify ownership of data in the exchange. Future modernization efforts at EPA should factor in that “exchanging” data is a key or primary function and databases need to be structured to account for not only data entry but for data exchange.

7. Partner Node Partner Node Partner Node Partner Node Today’s Network and the Next Generation Network Flow Specific Data Flow Specific Format Flow Specific Data Data Standard Format DS DS Flows will happen with whatever pieces are ready Standard XML Components DS DS DS Permit Facility Flow Conf Doc Flows that meet business needs with standard Network parts

8. Reflections…. • With the exception of the FRS flow, we have had limited success on the State-to-EPA exchanges. That is expected to change in 2005 but will require effort and on-going commitment. • Publishing data in a secure place on the Exchange Network has proven far easier and sets a new paradigm for future data exchanges. • In order to develop the Next Generation Exchange Network, the partnership between states and EPA needs to continue to push for building databases for data exchange, developing more standards, and to stretch the breadth of the Network by embracing new types of exchanges.

9. Resources • Tools available on www.exchangenetwork.net website • Registry of XML Schema available • Contacts • Can create members only space for team projects if you need it • Building Communities of Interest over then next few months – help share products and resources created for EN data flows

10. Website

11. Contact Molly O’Neill ECOS 202-624-3507 Pat Garvey U.S. EPA 202-566-1687 www.exchangenetwork.net