Washington Ecology

Preview:

Citation preview

Incorporating the Exchange Network into Your Enterprise

Washington State Department of Ecology

THE

PAST

Facility Site

RCRA

Toxic Release Inventory

Pacific Northwest Water Qulaity

Department of Health Fish Tissue

WasteX

Pacific Northwest Data Catalog Refresh

PCS/IDEF

eBeaches

AQS In planning

WQX In planning

Air Now In planning

Node 2.0 Execute GeoLocation Finder

National Emissions Monitoring

Current and Future Flow Deployment

Brief Timeline

• 2003 – Built the node and first core EPA Flow

• 2004 – added 5 flows

• 2005 – added eBeaches flow

• 2006-2007 – added TRI and TRIDex

• 2008 – after far too long we completed RCRA Handler

Node Architecture - 2005

Ecology IntranetInternet Ecology IntranetInternet

Cloud

Node Database

Node Web Server Turbo Waste

EPA

DOH

HTTP Proxy Server

External Router & Firewall

DIS Fortress

OR DEQ

EIM

F/S

Node Architecture Now

Everything from 2005

AND

Wa TRIME User

EPATRI Data

Cloud

TRIDex

Node Admin Data

Web Pages

Reports

Recent Developments

• We implemented the Toxic Release Inventory flow and followed quickly with the development of TRIDEX

• For node flow management we built out a process that publishes node statistics/use.

Focus for a Moment on Toxic Release Inventory

The Toxic Release inventory is a U.S. EPA program enacted as part of the Emergency Planning and Community Right to Know Act (EPCRA) of

1986. Every year, tens of thousands of facilities in the United States submit reports to EPA and the States on releases and transfers of

certain toxic chemicals.

From the Node Exchange Web Page

In 2006 Kansas Department of Health and Environment

Developed the Initial Viewer

In early 2007 Washington Department of Ecology partnered with Windsor

Solutions to develop TRIDEX

The story has continued.

The Evolution or Success Story of TRIDEX

TRIDEX – Toxics Release Inventory Data Exchange

TRIDex Form R

Management of the Node

• Ongoing tracking of activity

• Exceptions or failures in processing

• Tracking of a specific flow

• Administrative tools and access to databases are limited

• If there is no tool then when people want to know what is happening they call.

Further Use of Admin Data

Waiting in the Wings

Air Data Flows

Analyzers

Data Loggers

Production Server

Ambient Air Quality Database

Quality Assurance

Reporting

Analysis

Exchange Network Node

AQS Data Flow

Air Now Data Flow

Access point for External Entities

A Few Quick Lessons Learned

• You have to know your data!

• Technology helps but …

• A quick fix can be a costly as a mistake.

• Doing it the right way can take more time.

• If you build it, it will cost.

• If you build it, it will meet business needs.

• EsS = D(waF)nM.

In Closing

• Contact Information

• Mnea461@ecy.wa.gov

• One last word – John Tooley will be addressing the latest innovation in Washington’s Node later in the conference. It is really cool!

Recommended