1 The National Environmental Information Exchange Network History and Overview Office of Water National STORET/WQX User Meeting November 27, 2007

2 What is the Exchange Network? HTTP servers using SOAP messaging and a common WSDL to enable synchronous and asynchronous blah-blah, blah-blah... An Internet and standards-based method for exchanging environmental information between partners. A common approach to sharing data that lets you use your partners’ data as if it is a part of your own systems. Principles: 1.Each partner manages their own data, and is the steward for data they originate. 2.The Network “doesn't care” how a partner manages and stores information. 3.Partners who need to store copies of data locally are responsible for the design, format, and maintenance of the copy they create. 4.Network partners agree to use adopted technology and data standards.

3 Why? High demand for access to environmental information among partners Multiple approaches to information exchanges are inefficient and burdensome States modernizing information systems and migrating away from use of EPA national systems Use of integrated information technologies and approaches is on the rise Yesterday’s Answer for Today’s question

4 Business Case: Water Monitoring ~30% of water monitoring data ever sees the light of day. Discoverable, Searchable Many failed efforts had focused on data consolidation, technology standards, and (always) a big database. Large investments in competing technologies. Cost of participation was too high for small organizations.

5 The “Blueprint” Adopted 2001 Member Infrastructure Capacity to participate Data Standards Common way to define shared terms Data Exchange Templates Common way to package shared data Trading Partner Agreement How information flows between partners Exchange Network Components Network Administration Registration, process support, communication Technical Infrastructure Uses standard Internet tools Data Standard s Council, 2000 Network Grants, 2002 Existing Agreements Flow Configuration Document, (FCD) 2004 Node, 2003 New TPAs as needed Governance, evolving over time Schema, 2002

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

7 Status of Network– April 2006 CA OR WA ID MT WY CO NM TX AK HI OK KS SD ND MN IA WI IN OH KY TN MS AL GA FL NC WV PA NY DE CT NH RI IL MO AR LA NV UT AZ OR NM MS WV PA NJ MA NH MD DC VA MI NM SC NE VT ME FL In Development Operational Not Yet Started St. Regis Mohawk

8 Status of Network - Today CA OR WA ID MT WY CO NM TX AK HI OK KS SD ND MN IA WI IN OH KY TN MS AL GA FL NC WV PA NY DE CT NH RI IL MO AR LA NV UT AZ OR NM MS WV PA NJ MA NH MD DC VA MI NM SC NE VT ME FL St. Regis Mohawk Cherokee Nation (OK) Navajo Nation (AZ) Salt River Pima- Maricopa Indian Community Samish Indian Nation Snohomish County Yurok Tribe In Development Operational Not Yet Started

9 States with Multiple Data Exchanges MT WY ID WA OR NV UT CA AZ ND SD NE CO NM TX OK KS AR LA MO IA MN WI IL IN KY TN MS AL GA FL SC NC VA WV OH MI NY PA MD DE NJ CT RI MA ME VT NH AK HI

10 Not Just Another Web Site! Can be “built in” to tools you use Send reports—or look it up. Build once, use many times Diminishing cost for new initiatives As protected as the owner chooses Shared Quality Assurance tools—before you try to load Data Standards—shared understanding Discovery Services

11 Finding Data Discovery services let you: –Find out what is on the Network –Learn which partners have nodes –Find out how to access each node and how to request the needed data. –For sensitive data, learn how to obtain permissions for data you have a need to access –If someone has made tools that improve usability of the data, find and use those tools

19 Questions? Need Info