Institutional Controls Data Exchange

1. Institutional Controls Data Exchange Michael Bellot, U.S. Environmental Protection Agency

2. Presentation Outline • What in the heck are ICs and why should I care? • How was the IC data standard developed and what are the key lessons? • What should I do if I want IC flows? • Leveraging other data purveyors to help publish…

3. What are ICs? • ICs are administrative and legal devices that control use of a site and/or modify behavior • Necessary when waste is left in place or operating remedy equipment remains • Governmental controls – zoning and permits (excavation and well drilling) • Proprietary controls – easements and covenants • Enforcement devices – orders and consent decrees • Informational devices – deed notice and state registries

4. Background • At contaminated sites, EPA, States, Tribes and local governments select remedies • When waste is left in place, long-term oversight is required • ICs often implemented, monitored, enforced and terminated by other parties/agencies • Strong need to coordinate and engage with co-regulators • IC Tracking identified as a critical step • Need a standard approach – Data Standard

5. Universe

6. Data Standard Development • Collaborative development process between EPA programs, other Federal agencies, States*, Local governments**, NGOs, and non-regulated-industry • Conducted through the Environmental Data Standards Council (lead by EPA/ECOS) • Developed as a cross-program, cross-agency tool • Component-based structure to facilitate data exchange and foster reuse • Flexible design to accommodate future additions to existing lists

7. 2002 Focus Group Meetings • EPA Headquarters – June 5 • States – June 18-19 • EPA Regional staff – June 26-27 • Other Federal Agencies – July 23-24 • Non-regulated-industry – October 8 • Local Government Agencies – October 10-11 • Policy Think Tanks – October 22

8. Data Standard Overview • Utilizes XML • Facilitates exchanging data between parties • Consists of XML Schema Definition (XSD) • Defines how IC data should be organized • Modular design to allow for reuse and extensibility • Multiple methods of implementation for cataloging and transferring data

9. IC Data Standard Lessons The majority of the time and effort focused on the following: • Assembling IC Definitions • Identifying and getting input from stakeholders • Learning the process and coordinating with individuals who review and approve the data standard • Identifying the existence of relevant standards (citation approach) • Designing a standard with flexibility and growth in mind (using context tags as opposed to tag names) • Solving the problem with many-to-many relations and multiple hierarchies (using association tags) • Conducting data collection pilots

10. Data Standard To Flows • Establishes data element relationship to facilitate IC data transfer through: • “Mapping” of data elements from existing tracking systems to the standard • “Adoption of exact data elements from the standard within new or enhanced tracking systems • Information on the standard available though the EDSC website http://www.envdatastandards.net/ • Just because you build it, they may not come..

11. Dangle Incentives • Continued involvement of State and Tribal partners • OEI grants again available to support: • implementation of the IC Data Standard • State/Tribal IC data flows through CDX • Look to local client based integration work • Future vision includes GIS information on ICs • Data purveyors as a partner to make data available