1 / 24

Raymond W. Blowitski, Office of Analysis, HS-32 Phone: (301) 903-3393

Strategy for Implementing DOE O 210.2, DOE Corporate Operating Experience Program. ISM Best Practices Workshop Aurora, CO September 12, 2006. Raymond W. Blowitski, Office of Analysis, HS-32 Phone: (301) 903-3393. Contents. Status of Order Basic Order Requirements

shona
Download Presentation

Raymond W. Blowitski, Office of Analysis, HS-32 Phone: (301) 903-3393

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. Strategy for Implementing DOE O 210.2, DOE Corporate Operating Experience Program ISM Best Practices Workshop Aurora, CO September 12, 2006 Raymond W. Blowitski, Office of Analysis, HS-32 Phone: (301) 903-3393

  2. Contents • Status of Order • Basic Order Requirements • Roles and Responsibilities • Contractors Requirement Document Requirements • Recommendations concerning Metrics

  3. Order Status • DOE O 210.2, DOE Corporate Operating Experience Program, was issued on June 12, 2006 • Order Fulfilled Commitment 18 to DOE Implementation Plan for DNFSB Recommendation 2004-1 • Order Requires the Contractors Requirements Document to be Incorporated Without Change into Operating Contracts within 6 Months – DUE 12/12/06 • DOE is required to Demonstrate Implementation by December 12, 2007 – per Commitment 19 to DNFSB Recommendation 2004-1

  4. Basic Order Requirements • Prescribes a Formal Process that: • Evaluates DOE Internal and External Operating Experiences (OPEX) to assess trends and safety issues and Promotes sharing of Good Work Practices that may affect safety and success of DOE missions • OPEX Clearing House Function: collection, storage, retrieval • OPEX Screened for Significance – by all stakeholders • Timely Communication of Screening Results and Insights • DOE Corporate Communication – thru Actionable or Informational Products • Effectiveness Evaluated – Periodic Safety Meetings and Metrics

  5. Corporate Operating Experience Program Approach

  6. Organizational Roles & Responsibilities Organizational Roles & Responsibilities are defined for: • DOE Corporate Operating Experience Program Lead Office • Headquarters Program Secretarial Officers/NNSA Deputy Administrators • DOE Field Elements • Government Owned/Government Operated (GOGO) Facilities • DOE Contractors and Subcontractors

  7. Basic Order Requirements and Organizational Roles & Responsibilities • Designated Lead Office (EH) for DOE Corporate Operating Experience Program – responsible for: • Clearinghouse Function – computer resources • Collects and analyzes DOE operating experience information to identify significant corporate level performance trends and issues related to Safety Issues • Collects and analyzes External operating experience related to Safety Issues • Communicates safety performance trending and analysis information to Management – Dailys, Weeklys, Monthly, Quarterly • HSS will assume functions described for EH

  8. Basic Order Requirements and Organizational Roles & Responsibilities • Designated Lead Office responsibilities (continued): • Develop/Disseminate Corporate lessons learned related to Safety Issues – SOR, SA, SB, SAd, OE Sum, JIT, DCS • Order Interpretation – Develop Guidance, interpret requirements, designate which Contracts must include the CRD, etc. • Operating Experience Committee– Columbia Davis-Besse Action 1.c • Membership will consist of designated DOE and Contractor Operating Experience Coordinators • Sponsor Periodic Safety Forums – to discuss safety trends, issues, lessons learned and good work practices – Columbia Davis-Besse Action 1.e

  9. Basic Order Requirements and Organizational Roles & Responsibilities (Continued) DOE Program Secretarial Offices • Collect and analyze DOE operating experience information to identify significant corporate level performance trends and issues related to Programmatic and Mission Related Issues • Review Mission and Safety Performance with Senior Management Periodically • Designate an OPEX Program Coordinator – who will be a member of the Operating Experience Committee • Screen and Disseminate Lessons Learned (forwarded by Field Elements) for Program and Mission Applicability.

  10. Basic Order Requirements and Organizational Roles & Responsibilities (Continued) DOE Program Secretarial Offices (continued) • Develop/Promulgate Program Unique Operating Experience Documents • Ensure lessons learned are developed and disseminated following completion of major program missions (e.g., RFETS closure) • Incorporation of Safety into Design Initiative • Participate (with Lead Office) in development and Concur on Safety related Corporate Operating Experience documents • Conduct Self-Assessment of OPEX Program during ISM Assessments • Oversight of Field Element Participation per DOE O 226.1

  11. Basic Order Requirements and Organizational Roles & Responsibilities (Continued) DOE Field Elements • Responsible for Oversight of Contractor OPEX Program – (per DOE O 210.2 and DOE O 226.1) • Screen Contractor OPEX for Operational Awareness, Performance and Trending, Lessons Learned • Recommend Local Lessons Learned to be shared locally – between contractors • Ensure Contractors held accountable – e.g.,contractor fee and performance mechanisms, CPOF clause • Designate an OPEX Program coordinator – who will be a member of the Operating Experience Committee

  12. Basic Order Requirements and Organizational Roles & Responsibilities (Continued) DOE Field Elements (Continued) • Forward Mission Related Lessons Learned to PSOs for Consideration • Share Field Element Developed LLs (DOE Database) • Self Assessment of OPEX Program during ISM Assessments

  13. Basic Order Requirements and Organizational Roles & Responsibilities (Continued) Operating Experience Coordinators • Develops and Manages Organization’s OPEX program: • Develop processes, procedures, communications methods, and documentation of OPEX program implementation • Maintains Oversight of Contractor’s OPEX Program • Communicate OPEX, including both DOE and external lessons learned, throughout the Organization • Obtain implementation feedback - effectiveness • Monitor overall safety and mission performance and trends • Raises OPEX issues to Management

  14. Basic Order Requirements and Organizational Roles & Responsibilities (Continued) Facility Representatives Role • Maintain Day-to-Day Oversight of Contractor Activities: • Ensure Reportable Occurrences are identified and reported • Ensure that Contractor identifies effective corrective actions and lessons learned – recommend lessons learned to be shared across site, PSO, and Corporately across DOE • Monitor overall safety performance and identify trends • Ensure information is brought to the attention of the Operating Experience Coordinators

  15. Basic Order Requirements and Organizational Roles & Responsibilities (Continued) GOVERNMENT OWNED/GOVERNMENT OPERATED(GOGOs) – Parallel requirements in the CRD • MUST Participate in Corporate OPEX Program • Share GOGO Developed LLs (DOE Database) • Screen DOE Corporate and External OPEX: • Distribute applicable OPEX to GOGO Personnel for review, analysis, internalization and corrective action

  16. Basic Order Requirements and Organizational Roles & Responsibilities (Continued) GOVERNMENT OWNED/GOVERNMENT OPERATED(Continued) • Implement Required Actions of Corporate OPEX Documents (e.g., SORs, SAs, SBs, etc.) and Formally respond as required • Trend GOGO Operating Events for Lesson Learned from Recurring Issues • Conduct Causal Analysis • Trend Corrective Actions and Develop Lessons Learned on Successful Actions • Assess OPEX Program Performance during ISM Assessment • Designate an Operating Experience Program coordinator

  17. Contractors Requirements Document (CRD) • MUST Have an OPEX Program that Participates in Corporate OPEX Program • MUST Share Contractor Developed LLs (DOE Database) • Required for Type A & B Accidents, Signficance Category 1 and R Occurrences • Optional for all other OPEX • MUST Screen DOE Corporate and External OPEX: • DOE OPEX Documents (e.g., SORs, SAs, SBs, SAd, OE Summaries, LL Database, JITs, DCS and respond as required • Major OPEX from other Government Agencies or Industry Accidents – As deemed Significant and Relevant by Contractor Management

  18. Contractors Requirements Document (CRD) (Continued) • MUST Distribute applicable OPEX to Contractor Personnel for review, analysis, internalization and corrective action implementation • MUST Designate an Operating Experience Program coordinator – who will be a member of the Operating Experience Committee • MUST Implement Required Actions of Corporate OPEX Documents (e.g., SORs, SAs, SBs, etc.) and Formally respond as required • MUST Trend Contractor Operating Events for Lesson Learned from Recurring Issues

  19. Contractors Requirements Document (CRD) • MUST Conduct Causal Analysis • MUST Trend Corrective Actions and Develop Lessons Learned on Successful Actions • MUST Establish Metrics and Assess OPEX Program Performance during ISM Assessment • Head of Contractor Organization – MUST Apply CRD requirements to Subcontracts within 6 months

  20. Metrics • DOE O 210.1 Requires: • DOE HQ and Field Elements MUST evaluate OPEX Program Effectiveness during ISM Assessments • Contractors – MUST Establish Metrics and Assess OPEX Program Performance during ISM Assessment • Specific Metrics are NOT Specified • Feedback and Improvement CRADs provide a basis for evaluation

  21. Recommendation for Metrics • Metrics Should Evaluate: • Effectiveness of Lessons Learned Communication • Lessons making it to those who need them • Lessons Delivered in a Timely Manner (i.e., when needed) • Feedback Provided to Originator on Value/Needed Improvements • Response on Actions Taken/Planned are Provided on Actionable Corporate Operating Experience Documents in Timely Manner

  22. Recommendation for Metrics • Metrics Should Evaluate: • Effectiveness of the Lessons Learned in Correcting/ Preventing Re-occurrence of Adverse Events • Lessons Learned solved a Performance Problem • No New Occurrences with the Same Type Problem, or have decreased in significance • The Same Lessons Learned are not being Repeatedly Developed • Lessons Learned are Actively sought by planners/workers to plan work

  23. Recommendation for Metrics • Metrics Should Evaluate: • Effectiveness of Lessons Learned in Improving Operations • Good Work Practice resulted in More Efficient Operations • Time or Cost Savings Resulted • Management Has Demonstrated Its Commitment to Lessons Learned

  24. QUESTIONS?

More Related