Post on 13-Dec-2015
transcript
Farside Slide Show
Multi-State Hazardous Waste Multi-State Hazardous Waste Information ExchangeInformation Exchange
WasteXWasteX
April 18-19, 2006April 18-19, 2006
San Francisco, CASan Francisco, CA
Presentation OutlinePresentation Outline
• Purpose Prove the concept of data exchange between states using the Node
• Business NeedTracking Interstate Hazardous Waste shipments
• WasteX Application (Node demonstration)WA <=> OR ; OR to OR ; WA to WA
• Next StepsDeveloping a Generic InterfacePrototype Manifest Discrepancy Report (better tool)
• Conclusions and Recommendations
Where is Washington?Where is Washington?
Washington is Most Famous For?Washington is Most Famous For?
Mt. RainierMt. Rainier
Washington is Most Famous For?Washington is Most Famous For?
Mt. St. HelensMt. St. Helens
WasteX
Purpose of WasteXPurpose 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
YES
YES
YES
Business Rule: Business Rule: Interstate Shipments of Hazardous Waste (HW)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: Business Need: Tracking Interstate Shipments of HWTracking Interstate Shipments of HW
Tracking Hazardous Waste Generation and ManagementTracking 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 (BRSBRS) – now part of RCRAInfo.
• BRS provides some reconciliation between implementers, but only every other yearevery other year at the facility level.
Tracking Interstate Shipments of HW (State option)Tracking Interstate Shipments of HW (State option) • Only some States track data annually and by manifest
Manifested Hazardous Waste Leaving Manifested Hazardous Waste Leaving Washington in 2005Washington in 2005
107,991910 pounds 9,775 manifests
Manifested Hazardous Waste Entering Manifested Hazardous Waste Entering Washington State in 2005Washington State in 2005
40,101,239 pounds 9,094 manifests
Movement of Hazardous Waste Movement of Hazardous Waste Manifests between WA – OR Manifests between WA – OR
(WA TurboWaste.Net data only)(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 Data Management of Hazardous Waste Shipments (HW)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 SimilaritiesWashington 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 Manifest Tracking Systems Evolution between WA and ORbetween WA and OR
TurboWaste.Net
HazWaste.NetHWIMSy
HWIMSy
Washington
Oregon
NodeNode
NodeNode
WasteXWasteX
Node Flow Example (WasteX Query)Node Flow Example (WasteX Query)Requestor Provider (STATE)
AGENCYNODE
PROGR.RDBMS
QueryProcessor
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
AGENCYNODE
Node Management
•Request results logged
•XML payload returned
Data Received
•Response logged
•Payload staged
Data available to the user
TurboWaste.NetApplication
TurboWaste.NetApplication
Permission granted by Windsor Solutions Inc.
PartnerNode
Node FacadeRequestor
ClientApplication
Node Data
Node Admin
Node Data Sources
Submit
GetStatus
Query
Authenticate
Execute
Notify
Download
Solicit
NodePing
GetServices
Node Engine
Transaction
Service
Fault
AccountClient
Application
Node Information Flow DiagramNode Information Flow Diagram
Permission granted by Windsor Solutions Inc.
Let’s take the Node for a test driveLet’s take the Node for a test drive
TurboWaste main screenTurboWaste main screen
WasteX - Node DemoWasteX - Node Demo
WAD041337130 Enter ID #
Click Search
Company Search ResultsCompany Search Results
WasteX - Node DemoWasteX - Node Demo
Click View Reporting History
Company Waste Stream ListingCompany Waste Stream Listing
WasteX - Node DemoWasteX - Node Demo
Click View for a single waste stream
Waste Shipment Detail – Link to NodeWaste Shipment Detail – Link to Node
WasteX - Node DemoWasteX - Node Demo
Link icon means
Node link
WA – WA
WA – OR
OR – WA
OR – OR
WasteX Results - Matching WA Generator and WA TSDWasteX Results - Matching WA Generator and WA TSD
WasteX - Node DemoWasteX - Node Demo
All shipment data reported received at TSD Facility
Selected Generator
WasteX - Node DemoWasteX - Node Demo
Selected TSD
Shipments sent by Generator
Shipments received by TSD
WasteX Results - Matching WA TSD and OR GeneratorWasteX Results - Matching WA TSD and OR Generator
Opens the data to review
Opens data for field inspectors
ExposesExposes data quality problems
ExposesExposes data quality problems
Data Sharing ChallengesData Sharing Challenges
[
Making WasteX “Operational”Making WasteX “Operational”
Mitch West mentioned a new phrase:
Making the Exchange Network “operationaloperational”• 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: Concept: Manifest Discrepancy ReportManifest Discrepancy Report
QUANTITYMANIFESTSHIPDATEGENERATOR RECEIVER
QUANTITYMANIFESTSHIPDATERECEIVER GENERATOR
It’s the differences in manifests and quantities that we are interested in
+ Diff
Simply put, it is a check and balance report.Simply put, it is a check and balance report.
Manifest Discrepancy ReportManifest Discrepancy Report
Operational Terminology:
How big is the problem?
Manifest Discrepancy Detail ReportManifest Discrepancy Detail Report
RecID WAD020257945
Data
GenID Manifest_NR GenShipmentDT RecShipmentDT Sum of GenPounds Sum of RecPounds
ORD000773937 5718 . 11/20/2003 0 1761.41
82209 . 12/20/2002 0 24209.35
86058 . 3/24/2003 0 23819.04
94779 . 9/15/2003 0 33696.94
99299 . 12/5/2003 0 36859.46
ORD000773937 Total 0 120346.2
WA9214053465 2290A . 10/17/2002 0 5020
3028A 1/28/2003 1/28/2003 2377 4190
3044L 2/13/2003 2/13/2003 1 3720
3097A . 4/7/2003 0 5660
3099L 4/9/2003 4/9/2003 2502 1460
3162A . 6/11/2003 0 13860
3216A 8/4/2003 8/4/2003 3753 360
Receiving TSDR
Sending Generator Manifest Number
Date Generator Shipped
Date Received at Facility
Sent Pounds Received Pounds
Manifest Discrepancy Detail ReportManifest Discrepancy Detail Report
RecID WAD020257945
Data
GenID Manifest_NR GenShipmentDT RecShipmentDT Sum of GenPounds Sum of RecPounds
ORD000773937 5718 . 11/20/2003 0 1761.41
82209 . 12/20/2002 0 24209.35
86058 . 3/24/2003 0 23819.04
94779 . 9/15/2003 0 33696.94
99299 . 12/5/2003 0 36859.46
ORD000773937 Total 0 120346.2
WA9214053465 2290A . 10/17/2002 0 5020
3028A 1/28/2003 1/28/2003 2377 4190
3044L 2/13/2003 2/13/2003 1 3720
3097A . 4/7/2003 0 5660
3099L 4/9/2003 4/9/2003 2502 1460
3162A . 6/11/2003 0 13860
3216A 8/4/2003 8/4/2003 3753 360
Missing Data (Yellow Boxes): Lost shipments Data not reported by Generator
Missing Pounds ? No data from Generator
Extra Pounds: TSD reported 120,346 pounds
3234A 8/25/2003 8/25/2003 2502 5640
3254A 9/11/2003 9/11/2003 3367 4780
3336A 12/2/2003 . 15463 0
WA9214053465 Total 29965 44690
WAD038529137 9628 1/31/2003 1/31/2003 4770.48 4770.48
2533B . 12/9/2003 0 17514
WAD038529137 Total 4770.48 22284.48
WAD041337130 M0053 1/17/2002 1/17/2002 34235 34194
M0055 1/16/2002 1/16/2002 20207 20182.8
M0199 3/7/2002 3/7/2002 28348.25 28314.3
M0200 3/7/2002 3/7/2002 26686.6 26654.64
M0201 3/9/2002 3/9/2002 30310.5 30274.2
M0229 3/17/2002 3/18/2002 27555 27522
M0231 3/13/2002 3/13/2002 39658.32 41192.93
M0360 4/30/2002 5/1/2002 18370 18348
M0373 5/2/2002 5/2/2002 4342 4170
M0447 6/1/2002 6/3/2002 26177.25 26145.9
M0519 6/21/2002 6/21/2002 11695.84 11442.48
Prototype: Manifest Discrepancy ReportPrototype: Manifest Discrepancy ReportMissing Pounds ? Generator reported 29,965 lbs
Extra Pounds: TSD reported 44,690 pounds
Difference: 14,725 pounds
N1030 10/21/2003 10/21/2003 21125.5 21100.2
N1125 11/7/2003 11/7/2003 1503 1417.8
N1192 12/5/2003 12/5/2003 40080 40032
N1193 12/5/2003 12/5/2003 40080 40032
N1210 12/16/2003 12/16/2003 21125.5 21100.2
N1256 12/23/2003 12/23/2003 29548.15 29512.76
WAD041337130 Total 933176.38 927564.63
Grand Total 967911.86 1114885.31
Concept: Manifest Discrepancy ReportConcept: Manifest Discrepancy Report
No Missing Manifests
Generator reports 933,176 poundsTSDF reports 927,564 poundsDifference: 5,612 pounds
0.6 %
Building an Operational WasteX Building an Operational WasteX Generic InterfaceGeneric Interface
Generators of HW TSDR Facilities Receiving HW
EXCHANGE NODEMulti-State Hazardous Waste Tracking
1 to 1Enter Generator EPA Site ID Number
All Generators
Washington
Oregon
Enter TSDR EPA Site ID Number
All TSDR Facilities
Washington
Oregon
W A D 1 2 3 4 5 6 7 8 9 O R D 1 2 3 4 5 6 7 8 9
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 1 2 3 4 5 6 7 8 9 1 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 1 2 3 4 5 6 7 8 9Many to 1
Next Steps in WasteX between Next Steps in WasteX between WA – ORWA – 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)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
ConclusionsConclusions
• 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
Follow sound project
management principles
Recommendation #1Recommendation #1
Recommendation #2Recommendation #2
It has to be Win-Win
for everybody
Recommendation #3Recommendation #3
Know where
you are going
Recommendation #4Recommendation #4
WasteXWasteX application application shows that there shows that there are many ways to are many ways to
use the Node use the Node capabilitiescapabilities
CreditsCredits
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 dan.kruger@doh.wa.gov 360.236.4346
Ed Bentley eben461@ecy.wa.gov 360.407.6466
Thank YouThank You