Presentation is loading. Please wait.

Presentation is loading. Please wait.

TRI Pilot Data Flow via the Exchange Network Michigan’s Experience Michael Beaulac – Michigan DEQ Bill Rensmith – Windsor Solutions, Inc. Whad’ya Node?

Similar presentations


Presentation on theme: "TRI Pilot Data Flow via the Exchange Network Michigan’s Experience Michael Beaulac – Michigan DEQ Bill Rensmith – Windsor Solutions, Inc. Whad’ya Node?"— Presentation transcript:

1 TRI Pilot Data Flow via the Exchange Network Michigan’s Experience Michael Beaulac – Michigan DEQ Bill Rensmith – Windsor Solutions, Inc. Whad’ya Node? Conference New Orleans, LA – 2/28/05-3/1/05

2 TRI Integrated Project Team EPAECOS Virginia DEQIndiana DEM South Carolina DEQMichigan DEQ Windsor Solutions, Inc.EnfoTech & Consulting, Inc. Computer Science Corp.Lockheed Martin

3 Business Requirements TRI XML Schema Inputs TRI XML Schema Standards & Guidelines Existing TRI Formats CRM1 CRM2/SSC’s EDSC 2.0 EN DRCs & W3C Standards EN DRCs & W3C Standards TRI-ME Flat File Format TRI-ME Flat File Format EnviroFacts Data Model Form R and A Reporting Instructions Reporting Instructions IPT Meetings

4 TRI Pilot Data Flow

5 TRI Next Generation Data Flow

6 Project Tasks High-Level Tasks 1. Convert TRI production database to SQL Server and remap front end 2. Configure Node for TRI data flow 3. Testing with CDX

7 The Michigan TRI Technical Architecture

8 TRI Node Administration Console

9 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

10

11 XML Instance File – Facility Identification

12 XML Instance File – Chemical and Activity

13 Cycle Time Transactions TRIFID # Chem. Cycle-Time 48192BSFCR1609B12 4 Min 12 sec 49001THPJH7171P34 2 Min 5 sec 48174MCHGN3634547 5 Min 45 sec 48667THDWCMICHI86 3 Min 16 sec

14 To Be Completed … CDX translator (TRI ME => XML) issues: creates one submission block for all chemicals generated w/in a facility. Does not handle multiple SIC codes per chemical. This has been/is being corrected. Translator doesn’t handle Dioxins due to reporting unit differences (grams vs. lbs.) State notification to facilities: MI cannot echo back to reporting facilities that we received a submitted instance file from CDX Who best to do this? CDX or states? Possible joint development of solution to “submit” from State Node to back-end db (multiple platforms and environments … Oracle and SQL, J2EE and.NET)

15 Preliminary Costs* TaskCost 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. (i.e., MS Access => SQL/Oracle)

16 Preliminary Costs* TaskCost 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. (i.e., MS Access => SQL/Oracle)

17 Conclusion & 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

18 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

19 Cost 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???

20 More Information: http://www.exchangenetwork.net/flow/cross/tri.htm Robert Jackson (MI DEQ) 517-373-2731 Ruth Borgelt (MI DEQ) 517-373-9804 Michael Beaulac (MI DEQ) 517-241-7808 Sara Pushpala (MI DIT) 517-373-8565 Phyllis Donahue (EPA–TRI) 202-566-0338 Natalia Vainshtein (CSC) 301-306-6465 Bill Rensmith (Windsor Solutions) 503-675 7833, x217 Kevin Jeffery (Windsor Solutions) 503-675 7833, x202 Doug Timms (enfoTech) 609-896-9777, x129 Ryan Teising (enfoTech) 609-896-9777, x148


Download ppt "TRI Pilot Data Flow via the Exchange Network Michigan’s Experience Michael Beaulac – Michigan DEQ Bill Rensmith – Windsor Solutions, Inc. Whad’ya Node?"

Similar presentations


Ads by Google