1 / 39

Exchange Network Overview

Exchange Network Overview. 2010 RCRAInfo National Users Conference. Andrew Battin EPA – Headquarters. RCRAInfo and the Exchange Network Partnering to Share RCRA Data Andrew Battin Deputy Director, Office of Information Collection March 4, 2010. 3. Introduction to the Exchange Network.

kierar
Télécharger la présentation

Exchange Network Overview

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. Exchange Network Overview 2010 RCRAInfo National Users Conference

  2. Andrew BattinEPA – Headquarters

  3. RCRAInfo and the Exchange NetworkPartnering to Share RCRA DataAndrew BattinDeputy Director, Office of Information CollectionMarch 4, 2010 3

  4. Introduction to the Exchange Network • What is the Exchange Network? • What made it necessary? • How did we build it? • Why should you care? 4

  5. What is the Exchange Network? • A partnership to support better environmental decisions through improved access to, and exchange of, improved environmental information • Tools and services that help integrate, analyze and report data • Partners participate extensively in Network governance • Data and Technology Standards that allow for data to be integrated regardless of the technology • Secure data exchanges over the Internet • More efficient business operations that improves data quality and timeliness • Value: Cost, quality, timeliness, web-ready, geo-enabled, reusable, standardized 5

  6. What Made it Necessary? • 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 • Many states doing double data entry 6

  7. Business Case • Hazardous waste must by law be tracked “cradle to grave” • Waste that crosses state borders is “out of sight, out of mind” • Is there really a way to confirm what left one state is received in another? • If it’s done at all, it’s a very large, resource-intensive effort • Local inspectors know where and when to look • So does it matter? 7

  8. Hazardous Waste Movement from WA79,982,082 pounds 10,141 manifests 8

  9. Waste Application Launches a Web Service from the Node Waste Shipment Detail – Link to Node Link icon means Node link WA – WA WA – OR OR – WA OR - OR 9

  10. State/EPA Shared Vision “The States and EPA are committed to a partnership to build locally and nationally accessible, cohesive and coherent environmental information systems that will ensure that both the public and regulators have access to the information needed to document environmental performance, understand environmental conditions, and make sound decisions that ensure environmental protection.” 10

  11. 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 costs 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

  12. What’s XML (and why)? • Machines can read it. In fact, they can read the blank form and know what should or should not fit – they won’t let you get it wrong! • Built-in error checking • Insulation: Changes in RCRAInfo don’t have to make work for you • Text files are just so 90s • Modern programmer tools can do a lot with XML. Text is just that – could be anything. • All the other kids are doing it! • Banking (your Quicken updates) • Travelocity – hotel and airlines • Office 2007 .docx and .xlsx are specialized XML • We’ll have a plan and some help for you before we make any wholesale switch 12

  13. RCRAInfo on the Exchange Network • RCRAInfo contains regulatory data on hazardous waste treatment, storage, and disposal • Containing both programmatic and enforcement data, RCRAInfo consists of seven modules • Handler • Permitting • Corrective Action • Compliance, Monitoring and Enforcement • Financial Assurance • GIS • Biennial Waste Activity Reporting • EN allows partners to submit data to EPA’s RCRAInfo System 13

  14. Methods to Flowing RCRA Data • Exchange Network Data Flows • Local EN Node • Local EN Node Client • Non-Exchange Network Data Flows • Direct data input via RCRAInfo • Flat-File submission via RCRAInfo Translation process 14

  15. Benefits of Using the Exchange Network • For states with RCRA data systems, EN flow pathways are: • More automated • Less error prone • In synch with RCRAInfo changes • Outbound Services (from RCRAInfo back to the states) • Data publishing • Return of data to state in more usable format • States do not need their own RCRA data system • Demonstration scheduled for EN Users’ Conference in April • Significant business process improvements by redesigning processes and leveraging the capability of the Network • RCRA outbound service is likely to be a key contributor to the success of state-level eManifest projects 15

  16. RCRA Data on a Larger Stage EPA remains committed to Data Interoperability and will see results in the following data areas: • Large Aquatic Ecosystems • Climate Change and Greenhouse Gas Emissions • National Information Exchange Model (NEIM) • Other Environmental Data “Silos” 16

  17. RCRAInfo as Part of the Network’s Future • The EN Strategic Plan defines success as all states flowing all data for 11 priority national systems by 2012. • Full implementation was defined as 35 states flowing RCRAInfo data via the EN • In eight years, 12 states have begun to flow RCRAInfo data and an additional 20 states directly entering their data • ECOS Resolution commits to long-term support to the Exchange Network and its partners. (3/2009) • The Administrator has called upon the Agency to focus efforts on “Achieving the Promise of the Exchange Network.” (7/2009) • EPA is currently working on the HQ and Regional “Drive to Finish.” 17

  18. EN “Drive to Finish” by 2012 EPA is soliciting everyone’s help to make the Exchange Network the preferred mechanism for reporting, integrating, publishing, and analyzing environmental information Implementation Plans: • Flowing RCRAInfo via EN: MA NH DE MD PA MS NC SC TX AZ CA WA • Formerly Flowing via EN: NJ MN KS OR • Direct Users: CT ME VT NY VA WV AL GA KY TN IL OH AR LA CO MT ND HI NV ID • Developing Flow via EN: 2010: AL TN WI MO 2011: IN MI MN 2012: NJ OK KS • Plans Pending: RI FL NM IA NE SD UT WY AK 18

  19. Contacts Regional Coordinators Ken Blumberg, Region 1 (617) 918-1084 Bob Simpson, Region 2 (212) 637-3335 Joe Kunz, Region 3 (215) 814-2116 Rock Taber, Region 4 (404) 562-8011 Glynis (Gigi) Zywicki, Region 5 (312) 886-4571 Zenny Sadlon, Region 5 (312) 886-6682 Jim Poindexter, Region 6 (214) 665-8586 Maryane Tremaine, Region 7 (913) 551-7430 Josie Lopez, Region 8 (303) 312-7079 Patricia Eklund, Region 9 (415) 972-3738 David Tetta, Region 10 (206) 553-1327 Headquarters Andrew Battin, Deputy Director Office of Information Collection (202) 566-1630 Connie Dwyer, Director Information Exchange and Services Division (202) 566-1691 Jonathan Jacobson, Chief Information Exchange Partnerships Branch (202) 566-1984 Chuck Freeman, Chief Information Exchange Technology Branch (202) 566-1694 Lee Kyle, Chief Information Services and Support Branch (202) 564-4622 John Harman, Acting Chief Data Standards Branch (202) 566-0748 Karl Alvarez Exchange Network Program Manager (202) 566-0989 19

  20. Marcy FlemingArizona

  21. Arizona Department of Environmental Quality RCRA Plan 21

  22. What We Did • Built a module in our enterprise database to collect RCRAinfo data • Set up an exchange flow to transmit data to RCRAinfo 22

  23. How We Did It • Exchange Network Grant • FY03 to Develop new node and integrate hazardous waste and water quality data for exchange over the network • FY04 to exchange hazardous waste, air quality monitoring data and environmental data in GIS format 23

  24. How We Did It (cont.) • In-House Database Development • Handler 2007 – 2008 • Corrective Action 2009 • Permit and Financial Assurance 2009 • CM&E 2010 • GIS 2010 24

  25. Program Systems Agency-wide Systems ARID SITES & VEMUR CoreData CTS ICE Person Customer Place APC & ERC WCET LTF (permits) AAA UST & SAF 25

  26. Why We Did It • Eliminate Duplicate Entries • Improve Labor Effectiveness Through a Reduction in Staff Time Required for Data Entry • Improve the Quality of Data • Agency Wide Access to the Data 26

  27. Dwane YoungEPA – HeadquartersOffice of Resource Conservation and Recovery

  28. RCRAInfo and the Exchange Network

  29. Outline • Why the Exchange Network? • Why XML? • Downsides of XML • Why now? • How does RCRAInfo implement the Exchange Network? • What does all this mean to RCRAInfo? • Demo of a submittal • Demo of a web service call

  30. Why the Exchange Network? • Provides for the concept of automated computer-to-computer data sharing • Allows us to eliminate double data entry • Provides for better data quality • Provides for more timely data • Overall, it will save resources

  31. Why XML? • Self describable format • Easily incorporated into varying applications • One file fully contains all of the information needed to add, update, or delete a record • Data follows a defined format, and that format can be easily validated • Web standard • No need to repeat ‘primary key’ information (i.e. Handler ID, Sequence Number, Source Type, etc.) nor a need to provide optional information that you don’t track • More resilient to change (v5 changes are a good example)

  32. Downsides of XML • File sizes can be much bigger • Generation of XML often requires some programming expertise • It’s a relatively new technology

  33. Why Now? • March 23, 2009 ECOS Resolution: Committing to the full implementation of the Exchange Network • July 7, 2009 Memo from Lisa Jackson (EPA): Restating EPA’s commitment to completing the Exchange Network • What does this mean for us?

  34. How Does RCRAInfo Implement the Exchange Network? • XML Translation has been around for a while for RCRAInfo • Made some significant changes in Version 4 to how XML Translation worked

  35. Changes to the Process

  36. Current Data Flow

  37. V5 Fully Implements RCRAInfo in the Exchange Network • Because of the way V4 was developed, V5 was a relatively simple change • V5 supports all of the RCRAInfo modules as XML (with the exception of Biennial Reporting)

  38. What does all this mean to RCRAInfo? • We definitely have a need to move away from double data entry • By building out XML translation in RCRAInfo and developing outbound web services, we’re ready to begin embracing the Exchange Network • Ultimately, this will save time and money

  39. Questions?

More Related