1 / 71

RCRAInfo Version 3 Overview

RCRAInfo Version 3 Overview. 2005 RCRAInfo National Users Conference August 2 – 5, 2005 Nashville, TN. V3 in a Nutshell. Lori Furr, OSW. V3 Overview. New technology/New Look Handler Searches Sort options Easier viewing of lists Easier viewing of selected information

rschofield
Download Presentation

RCRAInfo Version 3 Overview

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. RCRAInfo Version 3 Overview 2005 RCRAInfo National Users Conference August 2 – 5, 2005 Nashville, TN

  2. V3 in a Nutshell Lori Furr, OSW

  3. V3 Overview • New technology/New Look • Handler Searches • Sort options • Easier viewing of lists • Easier viewing of selected information • Edits/Informative Messages

  4. New Technology/New Look

  5. New Technology/New Look (cont.)

  6. Handler Searches

  7. Sort Options

  8. Easier Viewing of Lists

  9. Easier Viewing of Lists (cont.)

  10. Easier Viewing of Lists (cont.)

  11. Easier Viewing of Selected Information

  12. Edits/Informative Messages

  13. Edits/Informative Messages cont.

  14. Edits/Informative Messages

  15. Changes to the CM & E Module Debbie Goodwin, OECA

  16. Creation or Collection Criteria • National Information: Information that has mandatory creation or collection. • National information must be tracked except where the Implementer is not authorized for that aspect of the RCRA program; i.e., some national information will remain essentially voluntary, either on the part of the Implementer (as in the case of the Universal Waste rules) or the affected entity (as in the case of CESQGs). • Shared and Optional Information: Information that is optionally created or collected.

  17. Specified Level of Quality & Currency Criteria Putting in place standards for data currency and quality will enable useful sharing but requires additional attention from all implementers. • National Information: Information that is maintained to a specified level of quality and currency. • Shared and Optional Information: Information that may be collected in many different ways and is not always current or fully qualified.

  18. Relies on Federal Rule OR Identified Directly by the Program Criteria • National Information: Information that relies on Federal rule to support the authority for its collection from the regulated community. • This is true for all national information needs that are collected from the regulated community. However, a Federal rule is not required in cases where the information is identified directly by the program, which is the case for most all CM&E data (e.g., Evaluation, Violation and Enforcement Data). • Shared and Optional Information: Information that does not depend on Federal authority for its collection.

  19. Accessible to All Regulators from RCRAInfo Criteria As implementers begin to share information, certain standards for use and dissemination must be defined to prevent misunderstanding, especially if the data is to be made publicly available. • National Information: Information that is always accessible to all regulators from RCRAInfo. • Shared Information: Information that is accessible to all regulators from RCRAInfo at the discretion of the Implementer. Shared Information should be shared by an Implementerunless there is a valid mitigating reason not to.

  20. Accessible to All Regulators from RCRAInfo Criteria • Shared Information is considered to be very important information to share with the RCRA regulatory community. The reason that this information need is not ‘National’ is because it is believed to be impractical to require that all Implementers provide this information. For example, if the Implementer has the data but believes that it is of a poor quality; if the Implementer does not currently track that data, and the added burden of collecting it is too great to justify its future collection; or if the data is considered to be confidential by the Implementer’s State. • Optional Information: Information that is accessible to all regulators from RCRAInfo at the discretion of the Implementer. Even if implementers collect this Optional Information they do not need to share it unless they choose to.

  21. CM&E Data Elements in V3 Evaluation Data (cevaluation3) National (Mandatory): Evaluation Activity Location Evaluation Identifier Evaluation Start Date Evaluation Agency Day Zero Found Violation Evaluation Type Citizen Complaint Multimedia Inspection Sampling Not Subtitle C Focus Area Focus Area Description Optional (Optional – Implementer’s choice): Evaluation Responsible Person Evaluation Suborganization Evaluation Notes

  22. CM&E Data Elements in V3 (continued) C6003Fed3 Data This table contains data only for EPA inspections at Federal facilities. National (Mandatory): Inspection Performed Questionnaire Given Questionnaire Completed Inspector Questionnaire Received Site Questionnaire Received Optional (Optional – Implementer’s choice): Notes

  23. CM&E Data Elements in V3 (continued) Request Data (crequest3) All Request information is shared. Shared (Optional – but really should be there): Date of Request Date Response Received Agency Activity Location

  24. CM&E Data Elements in V3 (continued) Commitment Data (commitment3) All Commitment information is optional. Optional (Optional – Implementer’s choice): Commitment Type Commitment Description Activity Location Federal FY Start Date End Date Notes

  25. CM&E Data Elements in V3 (continued) Violation Data (cviolation3) National (Mandatory): Activity Location Sequence Number Determined By Agency Determined Date Violation Type Actual RTC Date RTC Optional (Optional – Implementer’s choice): Notes

  26. CM&E Data Elements in V3 (continued) Citation Data (ccitation3) National (Mandatory): Citation Sequence Number Citation Type Citation Citation Description Optional (Optional – Implementer’s choice): Notes

  27. CM&E Data Elements in V3 (continued) Enforcement Data (cenforcement3) National (Mandatory): Activity Location Enforcement Identifier Enforcement Action Date Agency Enforcement Type Enforcement Type Description Appeal Initiated Date Appeal Resolved Date Disposition Status Disposition Status Date CAFO Seq CA Component Optional (Optional – Implementer’s choice): Attorney Docket Number Responsible Person Suborganization Notes

  28. CM&E Data Elements in V3 (continued) Media Data (cmedia3) Shared (Optional – but really should be there): Media Type Optional (Optional – Implementer’s choice): Notes

  29. CM&E Data Elements in V3 (continued) SEP Data (csep3) National (Mandatory): SEP Sequence Number SEP Type Scheduled Completion Date Actual Completion Date Expenditure Amount SEP Type Description Optional (Optional – Implementer’s choice): Notes

  30. CM&E Data Elements in V3 (continued) Milestone Data (cmilestones3) Shared (Optional – but really should be there): Sequence Number Technical Requirement No. Technical Requirement No Technical Requirement Description Scheduled Completion Date Actual Completion Date Defaulted Date Optional (Optional – Implementer’s choice): Notes

  31. CM&E Data Elements in V3 (continued) Penalty Data (cpenalty3) National (Mandatory): Penalty Type Amount Optional (Optional – Implementer’s choice): Notes

  32. CM&E Data Elements in V3 (continued) Payment Data (cpayment3) Shared (Optional – but really should be there): Scheduled Date Scheduled Amount Paid Date Paid Amount Defaulted Date Optional (Optional – Implementer’s choice): Notes

  33. V3 Site Activity Highlights Rene’ Anderson, Idaho

  34. Active/Inactive Timeline Highlights • June 2003 - Workgroup formed. • May/June 2004 - National Review. • February 2005 - WIN/INFORMED ESC final approval. • April 2005 - Final documents distributed to User Community. • July 2005 - Posted under the Version 3 documentation portion of the RCRA Partnership Web within RCRAInfo.

  35. Active/Inactive Flag • The Active/Inactive Flag will be added to the Handler Detail screen. • Universe calculations will run to determine the active or inactive status of a facility by looking for SI Handler, Permitting, Converter, CA, and state-specific activities (Recommendations 1-14).

  36. HPACS • HPACS - Acronym will be similar to the Permitting LIBST model for determining activities (Recommendation 1).

  37. New Usage Codes • New Usage codes will be added to show whether a state-specific activity should be used in the active universe calculation (Recommendations 11 and 14). • 9 - Implementer-defined, not Nationally Required, Routinely Released, Used in Universe Calculations. • 0 - Implementer-defined, not Nationally Required, Routinely Released, Not Used in Universe Calculations.

  38. State Information Table • A table that States can use to provide an overview and description of their activities will be established; data will be sent to public access Web sites (Recommendation 20). • The Workgroup suggested improvements be made to Envirofacts outside the realm of active/inactive status.

  39. Handler Data Entry Screens • Handler data entry screens will include a note for Implementers to standardize State Generator Status and State-specific activity descriptions (Recommendation 21).

  40. New BR Reports will… • Compare a State’s RCRA EPA ID Numbers against customer ID numbers in BR WR data (Recommendation 26). • Reverse search of WR data to find shipment information for a specific RCRA EPA ID Number (recommendation 27).

  41. Standing Committee • A standing committee will be created to review site identification and activity data issues and develop proposals to address them (Recommendation 33). • The committee is anticipated to be one of the program groups as part of the new Change Management Process.

  42. Summary of Universe Changes Beverly Allen, OSW

  43. Summary of Universe Changes • What’s A Universe? • Universe: A collection of sites which share a common RCRA status. • Universe Calculations: Standardized database queries routinely & automatically performed on RCRAInfo data which populate universe flags in the RCRAInfo database.

  44. Summary of Universe Changes • RCRAInfo V3 incorporates additions & enhancements to universes. • Recommended in HMA PAA & Site Activity Status Project reports. • Needed for next HQ Management GPRA reporting cycle. • Three universe categories: • Significant Non-compliers (SNCs). • Active Sites. • 2006 Permitting & 2008 Corrective Action GPRA.

  45. Summary of Universe Changes • Significant Non-Complier (SNC) Universes. • Twelve new SNC Universes which indicate SNC status: • State Addressed SNC, EPA Addressed SNC • BOY State Addressed SNC, BOY EPA Addressed SNC • State Unaddressed SNC, EPA Unaddressed SNC • BOY State Unaddressed SNC, BOY EPA Unaddressed SNC • State SNC w/Compliance Schedule, EPA SNC w/Compliance Schedule • BOY State SNC w/ Compliance Schedule, BOY SNC w/Compliance Schedule

  46. Summary of Universe Changes • Significant Non-Complier (SNC) Universes (cont.). • V2 SNC, BOYSNC Universes. • Rules for determining Overall SNC change. • Overall BOYSNC goes away. • The V2 SNC universe says whether or not the site is a SNC and includes every site regardless of agency. (whether unaddressed, addressed, or on a compliance schedule. • Each SNC universe flag is 1-character field, value = Y or N. • For detailed discussion, don’t miss the general session: Everything You Ever Wanted To Know About Designating a SNC.

  47. Summary of Universe Changes • Significant Non-Complier (SNC) Universes (cont.). • Reference: News Alerts & General Information link on RCRAInfo main menu, RCRAInfo Partnership Website, RCRAInfo News, Version 3 Documentation, HMA PAA Team’s Final Report

  48. Summary of Universe Changes • Active Site Universe. • New 5-character universe field indicates whether & why a site is considered active. • “HPACS” indicates activities/other universes that cause the site to be active. • By default a site is inactive & Active Site = “-----”. • Ex: “----S” means facility is in Active Site Universe because it is a State Regulated TSDF.

  49. Summary of Universe Changes • Active Site “Sub-Universes.” • Three new universes used in calculating Active Site Universe. • Active Site Federally Regulated TSDF • 5-character, “LIBST” • Active Site Converter TSDF • 5-character, “LIBST” • Active Site State Regulated TSDF • 8-character, “LIBSTYYY” • Y’s indicate State Universal Waste, Gen. Status, Other State Activities

  50. Summary of Universe Changes • Active Site Universes. • For more information, attend breakout session WIN/INFORMED Site Activity Workgroup: Overview of Recommendations. • Reference: News Alerts & General Information link on RCRAInfo main menu, RCRAInfo Partnership Website, RCRAInfo News, Version 3 Documentation, Site Status Report - Final for RCRA Subtitle C Site Activity Status Project Report

More Related