1 / 20

TRI Pilot Data Flow via the Exchange Network Michigan’s Experience

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. TRI Integrated Project Team. TRI XML Schema. TRI XML Schema Inputs.

eavan
Download Presentation

TRI Pilot Data Flow via the Exchange Network Michigan’s Experience

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TRI Pilot Data Flowvia the Exchange NetworkMichigan’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

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

  4. TRI Pilot Data Flow

  5. TRI Next Generation Data Flow

  6. Project Tasks

  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. XML Instance File – Facility Identification

  11. XML Instance File – Chemical and Activity

  12. Cycle Time Transactions

  13. 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)

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

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

  16. 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

  17. 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???

  18. 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

More Related