1 / 43

Farside Slide Show

Farside Slide Show. Multi-State Hazardous Waste Information Exchange WasteX. April 18-19, 2006 San Francisco, CA. Presentation Outline. Purpose Prove the concept of data exchange between states using the Node Business Need Tracking Interstate Hazardous Waste shipments

alva
Download Presentation

Farside Slide Show

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. Farside Slide Show

  2. Multi-State Hazardous Waste Information ExchangeWasteX April 18-19, 2006 San Francisco, CA

  3. Presentation Outline • Purpose Prove the concept of data exchange between states using the Node • Business Need Tracking Interstate Hazardous Waste shipments • WasteX Application (Node demonstration) WA <=> OR ; OR to OR ; WA to WA • Next Steps Developing a Generic Interface Prototype Manifest Discrepancy Report (better tool) • Conclusions and Recommendations

  4. Where is Washington?

  5. Mt. Rainier Washington is Most Famous For?

  6. Washington is Most Famous For? WasteX Mt. St. Helens

  7. Purpose of WasteX • Last year these are the questions we were asking: • Can we data exchange manifest data between states using the Environmental Exchange Network • Is the technology needed available? • Build the flow without a national standard? • Create a new flow using the existing Nodes at two states ( WA and OR)? • What is the level of effort? YES YES YES YES LOW

  8. Business Rule: Interstate Shipments of Hazardous Waste (HW) • Those who generate HW must send it to a Treatment Storage Disposal 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).

  9. Business Need: Tracking Interstate Shipments of HW Tracking Hazardous Waste Generation and Management • 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 the facility level. Tracking Interstate Shipments of HW (State option) • Only some States track data annually and by manifest

  10. Manifested Hazardous Waste Leaving Washington in 2005 107,991910 pounds 9,775 manifests

  11. Manifested Hazardous Waste Entering Washington State in 2005 40,101,239 pounds 9,094 manifests

  12. Movement of Hazardous Waste Manifests between WA – OR (WA TurboWaste.Net data only) WA 2,904 manifests 3,923 manifests OR 95,898,757 lbs 13,223,293 lbs

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

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

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

  16. 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 Permission granted by Windsor Solutions Inc.

  17. 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 Permission granted by Windsor Solutions Inc.

  18. Let’s take the Node for a test drive WasteX

  19. TurboWaste main screen WasteX - Node Demo Enter ID # WAD041337130 Click Search

  20. Company Search Results WasteX - Node Demo Click View Reporting History

  21. Company Waste Stream Listing WasteX - Node Demo Click View for a single waste stream

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

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

  24. WasteX Results - Matching WA TSD and OR Generator WasteX - Node Demo Selected TSD Shipments sent by Generator Shipments received by TSD

  25. Opens the data to reviewOpens data for field inspectorsExposes data quality problemsExposes data quality problems Data Sharing Challenges [

  26. Making WasteX “Operational” • Mitch West mentioned a new phrase: • Making the Exchange Network “operational” • query • Solicit • We have to use more conversational terminology • Making reports easier to read • Reviewing User Interface (UI) designs • Making the “Decoder Ring” to tame XML

  27. Concept: Manifest Discrepancy Report GENERATOR SHIPDATE MANIFEST QUANTITY RECEIVER RECEIVER SHIPDATE MANIFEST QUANTITY GENERATOR + Diff It’s the differences in manifests and quantities that we are interested in Simply put, it is a check and balance report.

  28. Manifest Discrepancy Report Operational Terminology:How big is the problem?

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

  30. 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

  31. Prototype: Manifest Discrepancy Report Extra Pounds: TSD reported 44,690 pounds Missing Pounds ? Generator reported 29,965 lbs Difference: 14,725 pounds

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

  33. 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 Building an Operational WasteX Generic Interface EXCHANGE NODE Multi-State Hazardous Waste Tracking Generators of HW Match to TSDR Facilities Receiving HW

  34. Next Steps in WasteX between WA – OR • Step 1 • Test Hypothesis of Lost Manifests • Set up work team WA-OR • Review each State’s data • Step 2 • Push data to Node • Confirm WasteX results

  35. Return on Investment (ROI) • Design the exchange (XML schema, FCD) costs about 7K • One time expense, in theory other states could just adopt the design • Estimate 5K to build the user interface part for TurboWaste.Net • Estimate about $10K – to develop for another State • Need to factor in cost to change regulatory framework, IT system changes, etc. in the cost/benefit analysis

  36. Conclusions • Technology is here today – where are you? • Methods and techniques are fairly straight forward • Is possible to create a data flow without a National Data Standard • All partners must agree • Be willing to rework Node following a national standard • Opens new business opportunities for state cooperation • Approximately $12,000 to build prototype

  37. Follow sound project management principles Recommendation #1

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

  39. Recommendation #3 Know where you are going

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

  41. Credits Debbie Stewart – WA Department of Ecology Miles Neale – WA Department of Ecology Bill Kellum – WA Department of Ecology Ed Bentley – WA Department of Ecology Dan Kruger – WA Department of Health Mitch West - Oregon Department of Environmental Quality Glen Carr – Oregon Department of Environmental Quality Windsor Solutions Inc. (Lake Oswego, OR)

  42. Thank You Dan Krugerdan.kruger@doh.wa.gov 360.236.4346 Ed Bentleyeben461@ecy.wa.gov 360.407.6466

More Related