Understanding RCRAInfo Change Management Process

1. RCRAInfo Change Management Process What is it? How does it work?

2. WIN/INFORMED to CMP • V3: CMP replaced WIN/INFORMED in 2005 • V4: last WIN/INFORMED process to define / implement RCRAInfo changes • Waste Information Needs/Information Needs FOR Making Environmental Decisions • State & EPA partnership 1994 - 2005

3. Change Management Process • Continues State & EPA partnership • Designed to meet needs of alldata users: • data primarily used for info management • data primarily used for program management

4. Communication is Essential • Between States & EPA • Between users: • info management users • program management users • Capture data to support & implement the RCRA program

5. Change Management ProcessDesigned to • Identify required / desired changes to RCRAInfo data & software; • Facilitate review of change requests by national user community;

6. Change Management ProcessDesigned to cont’d • Facilitate communication between program management and information management staff, and • Track all RCRAInfo change requests from receipt through resolution.

7. 4 Major Types of Changes • O & M (Operations & Maintenance): current programming errors / bugs; • Streamlining: short-term, low-cost, low level-of-effort changes; • PG&R (Program, Guidance & Regulatory): new or changing info needs of the RCRA program; • Major Enhancements: do not meet criteria for “Streamlining” changes.

8. O & M Requests directly to DIG; ALL others to CG User Enters Change Request into USITS O & M Request? Yes O & M Requests to DIG No Enter Change Request into USITS User encounters a problem, has question, wants to make suggestion

9. O & M Changes are Operations & Maintenance changes like current programming errors / bugs

10. Streamlining Requests implemented after TG review; PG&R or Major Enhancement requests > National Review UC Notified of Implementation PG&R or Major Enhancement Review Process No Yes TG review To DIG forImplementation Request Reviewed / Implemented CG review - Streamlining Request?

11. Streamlining Changes are short-term, low-cost, low level-of-effort changes, like adding / deleting an event code.

12. PG Evaluation / Recommendation TG Evaluation National Review, Comments > CG CG > UC Review MB Approval? Yes MB Reviews Request No CG, PG & TG Comment review Program, Guidance & Regulatory or Major Enhancement Requests PG&R / ME

13. PG&R & Major Enhancements PG&R (Program, Guidance & Regulatory):new or changing info needs of the RCRA program, Major Enhancements:do not meet “Streamlining” criteria, i.e. are not short-term, low-cost, low level-of-effort changes.

14. CMP Groups • Coordination Group (CG) • Program Group(s) (PGs) • Design and Implementation Group (DIG) • Translation Group (TG) • Management Board (MB)

15. Coordination Group (CG) • Main body of CMP • Composed of State, EPA Region and EPA HQ members • Decision maker for most issues moving through CMP.

16. Program Groups (PGs) • Five subject matter specific, “standing groups” • Corrective Action • Permit/Closure • Site Identification (Site ID) • Waste Activity (WAG) • Compliance/Enforcement

17. Program Groups (PGs) cont’d • Provides in-depth analysis of requests within specific program area. • 6 members -- an equal number of State and EPA members

18. Design & Implementation Group (DIG) • Implements changes to RCRAInfo, • primarily RCRAInfo staff from OSW Information Management Branch.

19. Design & Implementation Group(DIG) cont’d • O & M requests – DIG makes changes to correct software ‘bugs’ & other issues • non-O&M requests (Streamlining, PG&R, Major Enhancements) consults with CG & Program Groups.

20. Translation Group (TG) • Makes recommendations following review of change request for translator issues. • 6 members: 3 state and 3 EPA • Ensures system enhancements made once a year and User Community notified (in writing with specifications) 6 months before.

21. Management Board (MB) • Supports Coordination Group as it implements CMP -- CG acts as decision maker for most change requests; • MB approval reserved for issues which require extensive resources or major changes in RCRA program direction.

22. Management Board Approval • In general, MB evaluates and approves a change request if • CG unable to reach consensus regarding implementation of a critical Program, Guidance or Regulatory change, or • Implementing a Major Enhancement will require significant resources at all levels (EPA HQ, Regions & States), e.g. adding a new module.

23. RCRAInfo CommunityRoles & Responsibilities • Submit all change requests or suggestions through USITS for review / implementation • Actively use RCRAInfo data, data quality tools and reports

24. RCRAInfo CommunityRoles & Responsibilities, cont’d • Participate in and use CMP to request improvements / enhancements in tracking program activity and reporting accomplishments.

25. Rene Anderson, Idaho Bud McCarty, N. Carolina Paula Canter, Ohio Jody Miller, Texas Lynn Hanifan, Region 1 Jan Martin, Region 4 Dan Bakk, Region 5 Ann Stephanos, EPA HQ Laura Lopez, EPA HQ Shashank Kalra, EPA HQ David Meredith, EPA HQ Lauren Way, EPA HQ Contacts – CG Members

27. Volunteers • The Change Management Process needs volunteers to function. • Please consider becoming a State, Regional or HQ representative on one of the CMP groups.