1 / 7

Using the Exchange Network One State ’ s Perspective

Using the Exchange Network One State ’ s Perspective. Deb Soule New Hampshire Department of Environmental Services NERACOOS/NECOSP Data Management Workshop, Sept. 26, 2012. NHDES and the EPA Exchange Network.

justus
Download Presentation

Using the Exchange Network One State ’ s Perspective

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Using the Exchange NetworkOne State’s Perspective Deb Soule New Hampshire Department of Environmental Services NERACOOS/NECOSP Data Management Workshop, Sept. 26, 2012

  2. NHDES and the EPA Exchange Network • Exchange Network is becoming the main way to give data to the EPA, other states, and stakeholders • Currently “flow” 6 flows: • Air quality (AQS), Beach advisories, Facility (FRS) data, RCRA (Hazardous waste generators), SDWIS (Drinking water), WQX (water quality exchange) are the regulated flows • ODPX (Ocean Data Partnership Exchange) is non-regulated • Anticipate adding other flows (UIC, Assessment data) • Funding/reporting requirements often drive flows

  3. About our data • Data ranges across all divisions of the dept – air, waste, and water • Lots of monitoring data and regulatory data • Data updated according to program needs • Many programs have been collecting data for many years

  4. How we manage our data • Primarily use several relational databases (Oracle, FoxPro, or Access) some of which are linked but many are not • Metadata is a problem for us – particularly for our GIS data. No standard and no policy. Only have GCMD record for 1 database. This metadata was built after partnership workshop. • Can get some of our data from: • NHDES OneStop web site • EPA system web sites we contribute data to • Exchange Network • upon request

  5. Data Management Successes In terms of the Exchange Network… • With a few clicks of the mouse, able to create beach notification and WQX files, submit to the EPA, determine status, and update our internal databases with what data was sent. • We search for WQX data (using EPA WQX warehouse on-line form and now web services) from surrounding states to help in assessing waterbodies. Get data in a format we already know with adequate documentation, quickly, and with no cost.

  6. Data Management Challenges • Setting up flows takes a lot of time. • Flows change over time so continual updating needed. • Have to compete for limited IT resources – jury of your peers • Dept focus for next several years is to convert Oracle forms to .Net for many (30 +/-) databases. Very little new development anticipated. • Hardware constraints – no space or speed to run programs. Difficult to find test environments.

  7. Take home points • Standardization of data and ease to submit data (once flows are built) • Received a lot of money to set up these flows • Can take a lot of time to create the flows although things are getting easier (plug-ins) • Lots of security which is good and bad • Lot of data readily available from states/EPA web sites

More Related