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

Where is Washington?

Washington is Most Famous For? Mt. Rainier

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

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? LOW YES

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

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 …) BRSEPA stores data in the Biennial Report System (BRS) – now part of RCRAInfo. every other yearBRS 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

Manifested Hazardous Waste Leaving Washington in , pounds 9,775 manifests

Manifested Hazardous Waste Entering Washington State in ,101,239 pounds 9,094 manifests

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

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

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

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

WasteX Application Topology

Node Flow Example (WasteX Query) RequestorProvider (STATE) AGENCY NODE PROGR. RDBMS Query Processor Data Request Authenticate at NAAS Perform Query Node Management Request received Account/Service Authorized at NAAS Request logged (Access, Query, Parameters etc.) Data Transformation Query parameters parsed Relational data retrieved XML transformation Schema validation AGENCY NODE Node Management Request results logged XML payload returned Data Received Response logged Payload staged Data available to the user TurboWaste.Net Application TurboWaste.Net Application Permission granted by Windsor Solutions Inc.

Partner Node Node FacadeRequestor Client Application Node Data Node Admin Node Data Sources Submit GetStatus Query Authenticate Execute Notify Download Solicit NodePing GetServices Node Engine Transaction Service Fault Account Client Application Node Information Flow Diagram Permission granted by Windsor Solutions Inc.

Let’s take the Node for a test drive

TurboWaste main screen WasteX - Node Demo WAD Enter ID # Click Search

Company Search Results WasteX - Node Demo Click View Reporting History

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

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

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

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

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

Making WasteX “Operational” Mitch West mentioned a new phrase: operational 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

Concept: Manifest Discrepancy Report QUANTITYMANIFESTSHIPDATEGENERATORRECEIVER QUANTITYMANIFESTSHIPDATERECEIVERGENERATOR It’s the differences in manifests and quantities that we are interested in + Diff Simply put, it is a check and balance report.

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

Manifest Discrepancy Detail Report RecIDWAD Data GenIDManifest_NRGenShipmentDTRecShipmentDTSum of GenPoundsSum of RecPounds ORD /20/ /20/ /24/ /15/ /5/ ORD Total WA A.10/17/ A1/28/ L2/13/ A.4/7/ L4/9/ A.6/11/ A8/4/ Receiving TSDR Sending GeneratorManifest Number Date Generator Shipped Date Received at Facility Sent Pounds Received Pounds

Manifest Discrepancy Detail Report RecIDWAD Data GenIDManifest_NRGenShipmentDTRecShipmentDTSum of GenPoundsSum of RecPounds ORD /20/ /20/ /24/ /15/ /5/ ORD Total WA A.10/17/ A1/28/ L2/13/ A.4/7/ L4/9/ A.6/11/ A8/4/ Missing Data (Yellow Boxes): Lost shipments Data not reported by Generator Missing Pounds ? No data from Generator Extra Pounds: TSD reported 120,346 pounds

3234A8/25/ A9/11/ A12/2/ WA Total WAD /31/ B.12/9/ WAD Total WAD M00531/17/ M00551/16/ M01993/7/ M02003/7/ M02013/9/ M02293/17/20023/18/ M02313/13/ M03604/30/20025/1/ M03735/2/ M04476/1/20026/3/ M05196/21/ Prototype: Manifest Discrepancy Report Missing Pounds ? Generator reported 29,965 lbs Extra Pounds: TSD reported 44,690 pounds Difference: 14,725 pounds

N103010/21/ N112511/7/ N119212/5/ N119312/5/ N121012/16/ N125612/23/ WAD Total Grand Total Concept: Manifest Discrepancy Report No Missing Manifests Generator reports 933,176 pounds TSDF reports 927,564 pounds Difference: 5,612 pounds 0.6 %

Building an Operational WasteX Generic Interface Generators of HWTSDR Facilities Receiving HW EXCHANGE NODE Multi-State Hazardous Waste Tracking 1 to 1 Enter Generator EPA Site ID Number All Generators Washington Oregon Enter TSDR EPA Site ID Number All TSDR Facilities Washington Oregon W A D O R D Match to Enter Generator EPA Site ID Number All Generators Washington Oregon Enter TSDR EPA Site ID Number All TSDR Facilities Washington Oregon _______________________ _ O R D to Many Enter Generator EPA Site ID Number All Generators Washington Oregon Enter TSDR EPA Site ID Number All TSDR Facilities Washington Oregon _______________________ _ O R D Many to 1

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

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

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

Next Steps for WasteX in Washington State Review Data Mapping (TurboWaste database has changed since first release of WasteX) Test Hypothesis of Lost Manifests Set up work team WA-OR Review data Push data to Node Confirm WasteX results

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

Follow sound project management principles Recommendation #1

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

Recommendation #3 Know where you are going

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

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)

Dan Kruger Ed Bentley Thank You