1 / 59

Multi-State Hazardous Waste Information Exchange WasteX

Multi-State Hazardous Waste Information Exchange WasteX. February 28 – March 1, 2005. Outline. Purpose Prove the concept of data exchange between states using the Node Business Area Interstate Hazardous Waste shipments WasteX Node demonstration WA to OR and OR to WA and WA to WA

arleen
Télécharger la présentation

Multi-State Hazardous Waste Information Exchange WasteX

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. Multi-State Hazardous Waste Information ExchangeWasteX February 28 – March 1, 2005

  2. Outline • Purpose Prove the concept of data exchange between states using the Node • Business Area Interstate Hazardous Waste shipments • WasteX Node demonstration WA to OR and OR to WA and WA to WA • Next Steps Example Generic Interface Prototype Manifest Discrepancy Report • Conclusions • Recommendations • eFiling in Washington – impacts for the Node

  3. Purpose • Prove the concept of data exchange between states using the National Environmental Information Exchange Network (NEIEN) • Is the technology needed available? • What is the level of effort? • Build the flow without a national standard? • Can we create a new flow using the existing Nodes at two states (WA and OR)?

  4. Business Area: Interstate Shipments of Hazardous Waste (HW) • Those who generate HW must send it to a Treatment Storage Disposal Recycling facility (TSDR) which is permitted for that type of waste. • Large Quantity Generators must report on a Generation and Management form (GM). • TSDR s must report the waste they receive on a Waste Received form (WR).

  5. Business Area: Interstate Shipments of Hazardous Waste (HW) • The “Implementer” (Tribe, State…) must have a solution to manage the information, and provide data to EPA every other year (2001, 2003 …) • EPA stores data in the Biennial Report System (BRS) – now part of RCRAInfo. • BRS provides some reconciliation between implementers, but only every other year at a company level.

  6. Hazardous Waste Movement from Washington 79,982,082 pounds 10,141 manifests

  7. Data Management of Hazardous Waste Shipments (HW) • The Node presents an opportunity for On-Line data sharing of HW manifest data: “Did they receive what we sent?” • Implementers can place data on their Network Node as soon as it is available

  8. Washington and Oregon • Washington State and Oregon require annual submissions of data. • Track HW shipments by manifest. • WA and OR have similar solutions.

  9. Washington Node HWIMSy TurboWaste.Net WasteX HWIMSy HazWaste.Net Node Oregon Manifest Tracking Systems Evolution between WA and OR

  10. HW Movement between WA – OR (WA TurboWaste.Net data only) WA 2,448 manifests 3,712 manifests OR 43,340,000 lbs 32,760,000 lbs

  11. Node Node TurboWaste.net HazWaste.net EIP WasteX Application Topology

  12. Node Flow Example (WasteX Query) Requestor Provider (STATE) • Data Request • Authenticate at NAAS • Perform Query • Node Management • Request received • Account/Service Authorized at NAAS • Request logged (Access, Query, Parameters etc.) TurboWaste.Net Application AGENCYNODE • Data Transformation • Query parameters parsed • Relational data retrieved • XML transformation • Schema validation PROGR.RDBMS QueryProcessor • Node Management • Request results logged • XML payload returned • Data Received • Response logged • Payload staged TurboWaste.Net Application AGENCYNODE Data available to the user

  13. Requestor Node Facade Node Engine Node Admin PartnerNode Authenticate Account ClientApplication Submit Transaction GetStatus Service ClientApplication Query Fault NodePing Node Data Sources Solicit Execute Notify Node Data Download GetServices Node Information Flow Diagram

  14. Let’s take the Node for a test drive Waste X

  15. TurboWaste main screen Node Demo Enter ID # WAD041337130 Click Search

  16. Company Search Results Node Demo Click View Reporting History

  17. Company Waste Stream Listing Node Demo Click View for a single waste stream

  18. Waste Shipment Detail – Link to Node Node Demo Link icon means Node link WA – WA WA – OR OR – WA OR - OR

  19. Selected Generator All shipment data reported received at TSD Facility WasteX Results - Matching WA Generator and WA TSD Node Demo

  20. Selected TSD Shipments sent by Generator Data from Oregon Node Shipments received by TSD WasteX Results - Matching WA TSD and OR Generator Node Demo

  21. Opens the data for our field inspectors Data Sharing Challenges Opens the data for review Exposes data quality problems Exposes data quality problems

  22. Next Steps for WasteX • Is WasteX the right application for determining manifest discrepancy reporting? • Develop simple tool for determining manifest discrepancies • Develop a generic interface concept • Define requirements

  23. Concept: Manifest Discrepancy Report GENERATOR SHIPDATE MANIFEST QUANTITY RECEIVER RECEIVER SHIPDATE MANIFEST QUANTITY GENERATOR It’s the differences in manifests and quantities that we are interested in

  24. Concept for a report that identifies the magnitude of the problem, if any. Manifest Discrepancy Summary Report

  25. Manifest Discrepancy Detail Report Receiving TSDR Date Generator Shipped Sending Generator Manifest Number Date Received at Facility Sent Pounds Received Pounds

  26. Manifest Discrepancy Detail Report Missing Data (Yellow Boxes): Lost shipments Data not reported by Generator Missing Pounds ? No data from Generator Extra Pounds: TSD reported 120,346 pounds

  27. Notice this Company Prototype: Manifest Discrepancy Report TSD reported 44,690 pounds Generator reported 29,965 lbs Difference: 14,725 poundsWhere is the error? Generator, TSDF, or a little of both.

  28. Concept: Manifest Discrepancy Report No Missing Manifests Generator reports 933,176 pounds TSDF reports 927,564 pounds Difference: 5,612 pounds 0.6 %

  29. Enter Generator EPA Site ID Number Enter TSDR EPA Site ID Number 1 to 1 W A D 1 2 3 4 5 6 7 8 9 O R D 1 2 3 4 5 6 7 8 9 All Generators All TSDR Facilities Washington Washington Oregon Oregon Enter Generator EPA Site ID Number Enter TSDR EPA Site ID Number 1 to Many O R D 1 2 3 4 5 6 7 8 9 ________________________ All Generators All TSDR Facilities Washington Washington Oregon Oregon Enter Generator EPA Site ID Number Enter TSDR EPA Site ID Number Many to 1 ________________________ O R D 1 2 3 4 5 6 7 8 9 All Generators All TSDR Facilities Washington Washington Oregon Oregon Generic Interface EXCHANGE NODE Multi-State Hazardous Waste Tracking Generators of HW Match to TSDR Facilities Receiving HW

  30. Conclusions • Technology is here • Methods and techniques are fairly straight forward • Opens new business opportunities for state cooperation • Possible to create a data flow without a National Data Standard • All partners must agree • Be willing to rework to make a national standard

  31. Follow sound project management principles Recommendation #1

  32. Recommendation #2 It has to be Win-Win for everybody

  33. Recommendation #3 Know where you are going

  34. Recommendation #4 WasteX shows that there are many ways to use the Node capabilities

  35. eFiling and the NodeTurboWaste.NetROI(Return On Investment)

  36. Node Node TurboWaste.net HazWaste.net EIP TurboWaste.Net Impacts the Node

  37. Electronic Records Comprise 92% of the Data Reported

  38. Companies Reporting Electronically Rises Dramatically Reporting Deadline 3/1/05 TurboWaste Access Version TurboWaste.Net

  39. TurboWaste.Net is Changing Our Daily Business Practices in One Year 91% 18%

  40. How Did We Achieve These Results ? • Listening to clients needs • Investing in enhancements • Client outreach • Training • Being flexible with deadlines

  41. Let’s take TurboWaste.Net for a Spin TurboWaste

  42. TurboWaste.Net Welcome to TurboWaste.Net

  43. TurboWaste.Net Login

  44. TurboWaste.Net User Profile

  45. TurboWaste.Net Welcome to TurboWaste.Net My Sites

  46. TurboWaste.Net Site Profile

  47. TurboWaste.Net Reporting History

  48. TurboWaste.Net Site ID Form

  49. TurboWaste.Net GM / WR Simple Version

  50. TurboWaste.Net GM / WR Expert Version

More Related