TRI Pilot Data FlowTRI Pilot Data Flowvia the Exchange Networkvia the Exchange Network

Michigan’s ExperienceMichigan’s Experience

TRI Pilot Data FlowTRI Pilot Data Flowvia the Exchange Networkvia the Exchange Network

Michigan’s ExperienceMichigan’s Experience

Michael BeaulacMichael Beaulac – Michigan DEQ – Michigan DEQ

Bill RensmithBill Rensmith – Windsor Solutions, Inc. – Windsor Solutions, Inc.

Whad’ya Node? ConferenceWhad’ya Node? Conference

New Orleans, LA – 2/28/05-3/1/05New Orleans, LA – 2/28/05-3/1/05

TRI Integrated Project TeamTRI Integrated Project Team

EPA ECOS

Virginia DEQ Indiana DEM

South Carolina DEQ Michigan DEQ

Windsor Solutions, Inc. EnfoTech & Consulting, Inc.

Computer Science Corp. Lockheed Martin

Business Requirements

TRI XML Schema InputsTRI XML Schema Inputs

TRI XMLSchema

Standards &Guidelines Existing TRI Formats

CRM1CRM1

CRM2/SSC’sCRM2/SSC’s

EDSC 2.0EDSC 2.0

EN DRCs &W3C Standards

EN DRCs &W3C Standards

TRI-ME Flat File Format

TRI-ME Flat File Format

EnviroFactsData ModelEnviroFactsData Model

Form R and AForm R and A

ReportingInstructionsReporting

Instructions

IPT MeetingsIPT Meetings

TRI Pilot Data FlowTRI Pilot Data Flow

TRI Next Generation Data FlowTRI Next Generation Data Flow

Project TasksProject Tasks

High-Level TasksHigh-Level Tasks

1. Convert TRI production database to SQL Server 1. Convert TRI production database to SQL Server and remap front end and remap front end

2. Configure Node for TRI data flow2. Configure Node for TRI data flow

3. Testing with CDX3. Testing with CDX

The Michigan TRI Technical ArchitectureThe Michigan TRI Technical Architecture

deqwebdmz

web

deqsqldmz

Node Database

TRI Database

(exchange tables)

(CDX)deqsqlprod

DMZ Inner Network

EPA Node Michigan Node

Michigan TRI OverviewMichigan TRI Overview

EPA CDX Node submits Michigan Node TRI XML file

1

Node logs incoming request

as Processing

2

Node parses XML file, stores in TRI exchange

tables

4

XML file stored on

Node

5

Node logs incoming request

as Complete

6

Node grabs XSLT from Node (contains XML parsing logic)

3Michigan Node returns transaction

ID to EPA

7

TRI Node Administration ConsoleTRI Node Administration Console

Some Preliminary Lessons Learned …Some Preliminary Lessons Learned …

Make the exchange server accessible to the Node because firewall “rules” may prevent data passing through the Node Application Server to Exchange Tables

Verify cycle-time per transaction for single and multiple chemical reports per submission

XML Instance files archived in Node Application Server and file server to verify accuracy and completeness of data

DM

Z Zo

neIn

tern

et

MI Infrastructure to Support TRI Pilot

Machine Access to Web

Services web

EPA-NAAS

CDX

EPA Program Offices

EPA-TRI

Deqw1dmz(TRI Converter)

Deqw2dmz(TRI Converter)

Deqsqldmz(Production Node_db)

Deqsqlprd(TRI database)

Deqinet (Node.Administration)

DB Format

XMLFormat

1433

1

2

3

Inte

rnal

Net

wor

k

443

Load Balanced

Node.WebServices

XML Instance File – Facility IdentificationXML Instance File – Facility Identification

XML Instance File – Chemical and ActivityXML Instance File – Chemical and Activity

Cycle Time TransactionsCycle Time Transactions

TRIFIDTRIFID # Chem.# Chem. Cycle-TimeCycle-Time

48192BSFCR1609B48192BSFCR1609B 1212 4 Min 12 sec4 Min 12 sec

49001THPJH7171P49001THPJH7171P 3434 2 Min 5 sec2 Min 5 sec

48174MCHGN3634548174MCHGN36345 4747 5 Min 45 sec5 Min 45 sec

48667THDWCMICHI 48667THDWCMICHI 8686 3 Min 16 sec3 Min 16 sec

To Be Completed …To Be Completed …

CDX translator (TRI ME => XML) issues:CDX translator (TRI ME => XML) issues:

creates one submission block for all chemicals generated w/in a facility. creates one submission block for all chemicals generated w/in a facility. Does not handle multiple SIC codes per chemical. This has been/is Does not handle multiple SIC codes per chemical. This has been/is being corrected.being corrected.

Translator doesn’t handle Dioxins due to reporting unit differences Translator doesn’t handle Dioxins due to reporting unit differences (grams vs. lbs.)(grams vs. lbs.)

State notification to facilities: MI cannot echo back to reporting State notification to facilities: MI cannot echo back to reporting facilities that we received a submitted instance file from CDXfacilities that we received a submitted instance file from CDX

Who best to do this? CDX or states?Who best to do this? CDX or states?

Possible joint development of solution to “submit” from State Possible joint development of solution to “submit” from State Node to back-end db (multiple platforms and environments … Node to back-end db (multiple platforms and environments … Oracle and SQL, J2EE and .NET)Oracle and SQL, J2EE and .NET)

Preliminary Costs*Preliminary Costs*

TaskTask CostCost

Document review, testing, QA, etc. (100-200hrs)

Develop and implement a TRI data flow strategy

$1,000-2,000

Install TRI Converter w/site visit (dB and App.)

$2,000-3,400

Linkage of converter with existing Node

$1,500-3,000

*Does not include Node development and db conversions, etc. *Does not include Node development and db conversions, etc. (i.e., MS Access => SQL/Oracle)(i.e., MS Access => SQL/Oracle)

Preliminary Costs*Preliminary Costs*

TaskTask CostCost

Map TRI Schema to data backend data source

$1,500-3,000

Develop procedures to convert from exchange tables to backend system

$2,000-4,000

Test of data flow (with EPA) $2,000-4,000

Document results $1,500-3,000

Total $11,500-22,400

*Does not include Node development and db conversions, etc. *Does not include Node development and db conversions, etc. (i.e., MS Access => SQL/Oracle)(i.e., MS Access => SQL/Oracle)

Conclusion & IncentivesConclusion & Incentives

TRI CDX transactions reduces data processing time, save resources and improves data accuracy,

Enables continuous QA/QC,

Eliminates need for the UTIL upload program,

Could potentially eliminate redundancy in reporting certain environmental and business information to the state and local governments

Reporting facilities could realize a reduction in reporting time resulting in cost saving

Process ~ Time• Open mail and separate current from

previous year (if applicable), • data stamp (paper and disk)

submission & log receipt

3 weeks

• Authenticate certification letter and disk

• Upload data on disk to TRI db via UTIL (Electronic submittals equate to 3229 reports; 90% of data received)

2 weeks

• Manually key paper submittals using TRI-ME and upload data into TRI dB via UTIL (Paper submittals equate to 343 reports; 10%)

3 weeks

• QA accuracy of uploaded data 1 week

• File certification letter with paper reports & disks,

• archive prior year data at record center.

1 week

Cost BenefitsCost Benefits

State:

10-12 weeks savings in internal staff resources = ~0.25 FTE => $17,500/yr

ROI => 6 months - 2 years

Facility:

1000 facilities @ 1-2 hours X $25.00/hr => $25,000 - $50,000 per year

EPA:

Unknown at this time … anybody???

More Information:More Information:

http://www.exchangenetwork.net/flow/cross/tri.htmRobert Jackson Robert Jackson (MI DEQ) 517-373-2731(MI DEQ) 517-373-2731

Ruth Borgelt Ruth Borgelt (MI DEQ) 517-373-9804(MI DEQ) 517-373-9804

Michael Beaulac Michael Beaulac (MI DEQ) 517-241-7808(MI DEQ) 517-241-7808

Sara Pushpala Sara Pushpala (MI DIT) 517-373-8565(MI DIT) 517-373-8565

Phyllis Donahue Phyllis Donahue (EPA–TRI) 202-566-0338(EPA–TRI) 202-566-0338

Natalia Vainshtein Natalia Vainshtein (CSC) 301-306-6465(CSC) 301-306-6465

Bill Rensmith Bill Rensmith (Windsor Solutions) 503-675 7833, x217(Windsor Solutions) 503-675 7833, x217

Kevin Jeffery Kevin Jeffery (Windsor Solutions) 503-675 7833, x202(Windsor Solutions) 503-675 7833, x202

Doug Timms Doug Timms (enfoTech) 609-896-9777, x129(enfoTech) 609-896-9777, x129

Ryan Teising Ryan Teising (enfoTech) 609-896-9777, x148(enfoTech) 609-896-9777, x148