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
•
Next Steps
Example Generic Interface
Prototype Manifest Discrepancy Report
•
•
•
Conclusions
Recommendations
eFiling in Washington – impacts for the Node
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)?
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).
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.
Hazardous Waste Movement from Washington
79,982,082 pounds
10,141 manifests
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
Washington and Oregon
•
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
Washington
HWIMSy
TurboWaste.Net
Node
WasteX
HWIMSy
Oregon
HazWaste.Net
Node
HW Movement between WA – OR
(WA TurboWaste.Net data only)
3,712 manifests
32,760,000 lbs
WA
OR
2,448 manifests
43,340,000 lbs
WasteX Application Topology
Node Flow Example (WasteX Query)
Requestor
Provider (STATE)
Data Request
•Authenticate at
NAAS
Node Management
TurboWaste.Net
Application
AGENCY
NODE
•Request received
•Account/Service Authorized at NAAS
•Perform Query
•Request logged (Access, Query, Parameters etc.)
Data Transformation
Query
Processor
PROGR.
RDBMS
•Query parameters parsed
•Relational data retrieved
•XML transformation
•Schema validation
Node Management
Data Received
•Response logged
•Payload staged
Data available
to the user
TurboWaste.Net
Application
AGENCY
NODE
•Request results logged
•XML payload returned
Node Information Flow Diagram
Requestor
Partner
Node
Client
Application
Node Facade
Node Engine
Authenticate
Account
Submit
Transaction
GetStatus
Service
Query
Fault
Node Admin
Client
Application
NodePing
Node Data Sources
Solicit
Execute
Notify
Node Data
Download
GetServices
Let’s take the Node for a test drive
Node Demo
TurboWaste main screen
WAD041337130
Click Search
Enter ID #
Node Demo
Company Search Results
Click View
Reporting
History
Node Demo
Company Waste Stream Listing
Click View for
a single waste
stream
Node Demo
Waste Shipment Detail – Link to Node
Link icon
means
Node link
WA – WA
WA – OR
OR – WA
OR - OR
Node Demo
WasteX Results - Matching WA Generator and WA TSD
Selected
Generator
All shipment
data reported
received at
TSD Facility
Node Demo
WasteX Results - Matching WA TSD and OR Generator
Selected
TSD
Shipments
sent by
Generator
Data from
Oregon Node
Shipments
received
by TSD
Data Sharing Challenges

Opens the data for review

Opens the data for our field inspectors


Exposes data quality problems
Exposes data quality problems
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
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
Manifest Discrepancy Summary Report
Concept for a
report that
identifies the
magnitude of
the problem,
if any.
Manifest Discrepancy Detail Report
Receiving TSDR
RecID
WAD020257945
Sending Generator
Date Generator Shipped
Manifest Number
Date Received at Facility
Data
GenID
Manifest_NR
ORD000773937
GenShipmentDT
RecShipmentDT
Sum of GenPounds
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
0
120346.2
10/17/2002
0
5020
ORD000773937 Total
WA9214053465
2290A
Sum of RecPounds
.
3028A
1/28/2003
1/28/2003
2377
4190
3044L
2/13/2003
2/13/2003
1
3720
4/7/2003
0
5660
4/9/2003
2502
1460
6/11/2003
0
13860
8/4/2003
3753
360
3097A
.
3099L
3162A
3216A
4/9/2003
.
8/4/2003
Sent Pounds
Received Pounds
Manifest Discrepancy Detail Report
RecID
Missing Data (Yellow Boxes):
Lost shipments
Data not reported by Generator
WAD020257945
Data
GenID
Manifest_NR
ORD000773937
GenShipmentDT
RecShipmentDT
Sum of RecPounds
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
0
120346.2
10/17/2002
0
5020
ORD000773937 Total
WA9214053465
Sum of GenPounds
2290A
.
3028A
1/28/2003
1/28/2003
2377
4190
3044L
2/13/2003
2/13/2003
1
3720
4/7/2003
0
5660
4/9/2003
2502
1460
6/11/2003
0
13860
8/4/2003
3753
360
3097A
.
3099L
3162A
3216A
Missing Pounds ?
No data from Generator
4/9/2003
.
8/4/2003
Extra Pounds:
TSD reported 120,346 pounds
Prototype: Manifest Discrepancy Report
TSD reported 44,690 pounds
Generator reported 29,965 lbs
3234A
8/25/2003
8/25/2003
2502
5640
3254A
9/11/2003
9/11/2003
3367
4780
3336A
12/2/2003
15463
0
29965
44690
1/31/2003
4770.48
4770.48
12/9/2003
0
17514
4770.48
22284.48
.
WA9214053465 Total
WAD038529137
9628
2533B
1/31/2003
.
WAD038529137 Total
WAD041337130
Notice
this
Company
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
Difference: 14,725 pounds
Where is the error? Generator, TSDF, or a little of both.
Concept: Manifest Discrepancy Report
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
No Missing Manifests
Generator reports 933,176 pounds
TSDF reports
927,564 pounds
Difference:
5,612 pounds
0.6 %
Generic Interface
EXCHANGE NODE
Multi-State Hazardous Waste Tracking
Generators of HW
Enter Generator EPA Site ID Number
W A D 1 2 3 4 5 6 7 8 9
Match to
1 to 1
All Generators
Washington
Oregon
Enter Generator EPA Site ID Number
O R D 1 2 3 4 5 6 7 8 9
All Generators
Washington
Oregon
Enter Generator EPA Site ID Number
_______________________
All _
Generators
Washington
Oregon
TSDR Facilities Receiving HW
Enter TSDR EPA Site ID Number
O R D 1 2 3 4 5 6 7 8 9
All TSDR Facilities
Washington
Oregon
1 to Many
Enter TSDR EPA Site ID Number
_______________________
_
All TSDR
Facilities
Washington
Oregon
Many to 1
Enter TSDR EPA Site ID Number
O R D 1 2 3 4 5 6 7 8 9
All TSDR Facilities
Washington
Oregon
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
Recommendation #1
Follow sound
project
management
principles
Recommendation #2
It has to be
Win-Win
for everybody
Recommendation #3
Know
where
you are
going
Recommendation #4
WasteX shows
that there are
many ways to
use the Node
capabilities
eFiling and the Node
TurboWaste.Net
ROI
(Return On Investment)
TurboWaste.Net Impacts the Node
Electronic Records Comprise 92% of the
Data Reported
Electronic Data Comprises the Bulk of Our Data
70,000
Paper
60,000
eFile
50,000
Number of Total 40,000
Shipments
30,000
Reported
20,000
10,000
0
2000
2001
2002
2003
2004
Companies Reporting Electronically
Rises Dramatically
Increase in HW eFiling in Washington
7000
Paper
eFile
6000
# of Companies
5000
Reporting
Deadline
3/1/05
4000
3000
2000
1000
0
2000
2001
2002
TurboWaste Access Version
2003
2004
TurboWaste.Net
TurboWaste.Net is Changing Our Daily
Business Practices in One Year
Comparing Paper and eFiling of HW Reports for the Same Period
3000
Paper
2500
# of Companies
eFile
2000
1500
91%
1000
500
18%
0
"Jan 1 - Feb 25, 2004"
"Jan 1 - Feb 25, 2005"
How Did We Achieve These Results ?
• Listening to clients needs
• Investing in enhancements
• Client outreach
• Training
• Being flexible with deadlines
Let’s take TurboWaste.Net for a Spin
TurboWaste.Net
Welcome to TurboWaste.Net
TurboWaste.Net
Login
TurboWaste.Net
User Profile
TurboWaste.Net
Welcome to TurboWaste.Net
My Sites
TurboWaste.Net
Site Profile
TurboWaste.Net
Reporting History
TurboWaste.Net
Site ID Form
TurboWaste.Net
GM / WR Simple Version
TurboWaste.Net
GM / WR Expert Version
TurboWaste.Net
Annual Report Checklist
Key Features of TurboWaste.Net
- PIN security and encrypted passwords
- Administrators can easily add users and change
permissions
- Administrators / Data Entry Staff responsible for many
sites can see all their sites on one screen
- Three roles: Administrators ; Data Entry; View Only
- Only Administrators can submit data
Key Features of TurboWaste.Net
- Complete data validation rules in place
- Data can be imported, copied from an earlier year, or
hand entered
- Expert versions of application screens for rapid data
entry
- Simple versions of screens for drop down menus
Key Features of TurboWaste.Net
- Data is not available to Ecology for view until it is officially
submitted or authorized for view by the client
- Annual Reporting can be combined with notification revisions
and withdrawals (one Site ID form, multi purpose)
- First notification and ownership changes require paper
submittals
-TurboWaste staff have administrator rights
- Ecology staff with “view only” rights on submitted data
What our clients are saying about
TurboWaste.Net
President of EnviroTech…..”I want to complain about your
TurboWaste, it’s too easy !”
Beth Gilbertson - Kent School District - she has many sites and
used it last year. She absolutely loves the new improvements we
made this year!
I submitted two weeks early. Why? Because the turbowaste
program now works so well. It has matured over the years, and
your efforts have now really paid off. My hat's off to the turbowaste
staff.
Submitted in TurboWaste.Net
Node Available
Comparing Paper and eFiling of HW Reports for the Same Period
3000
Paper
2500
# of Companies
eFile
2000
1500
91%
1000
500
18%
0
"Jan 1 - Feb 25, 2004"
"Jan 1 - Feb 25, 2005"
Credits
Debbie Stewart – WA Department of Ecology
Miles Neale – WA Department of Ecology
Bill Kellum – WA Department of Ecology
Mitch West - Oregon Department of Environmental Quality
Glen Carr – Oregon Department of Environmental Quality
Windsor Solutions Inc. (Lake Oswego, OR)
Thank You
Ed Bentley [email protected] 360.407.6466
Dan Kruger [email protected] 360.407.6728