200 likes | 331 Vues
This presentation from the Whad’ya Node? Conference explores the integration and pilot execution of the Toxics Release Inventory (TRI) data flow through the Exchange Network. Featuring insights from Michigan DEQ staff and Windsor Solutions, it highlights the challenges and achievements in processing TRI XML submissions. Key points include the importance of server access, transaction cycle times, data accuracy, and preliminary cost analyses. The session emphasizes how these advancements lead to improved efficiency, reduced reporting time, and significant cost savings for facilities and state agencies.
E N D
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
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
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
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)
Preliminary Costs* *Does not include Node development and db conversions, etc. (i.e., MS Access => SQL/Oracle)
Preliminary Costs* *Does not include Node development and db conversions, etc. (i.e., MS Access => SQL/Oracle)
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
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???
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