Operating Experience Committee - Meetings

• Type B Accident Investigation Electric Cart Injury 02/25/09

• WIPP Type B Accident Investigation Board Report Chair's Close-Out

The Task Team on Qualification Standards for Coordinators will welcome the opportunity to meet and hammer out details on 4/28.

Our agenda will be to evaluate the basis of the OPEX Coordinator qualification standard using the Systematic Approach to Training and NRC's OPEX qualification standard. The team will then develop the qualification proposal to be presented the following day, during the OPEX conference.

I would like the team to schedule at least 6 hours (0900-1500, lunch included) for the Tuesday meeting.

This Task Team meeting will be focused on defining what controls the quality of a lessons learned and identifying actions that we can take collectively and individually to improve LL quality. We will use some simplified versions of Lean Six Sigma tools to quickly define the basic challenges, localize them in the creation/communication process, and then develop and share ideas and best practices for addressing them

• Create a LL Value Chain Map (90 minutes)
• Cause and Effect Diagram (90 minutes)
• Learning Deployment Action Development
  o Action Brainstorm (45 minutes)
  o Modifications to Attributes Tool (30 minutes)
  o Specific program-wide and site-localized recommendations to implement the actions (45 minutes)
• Develop report to full committee (30 minutes)

Agenda for April 2009 OEC meeting, Carlsbad, New Mexico
Divide team into different working groups to discuss/prioritize tools and resources (half day). Convene entire group and finalize priorities and scope (half day). Present to OEC next day.

HSS Lessons Learned Database Improvements

1. Improve our input for better output

a. Do we need to revise the Submittal Form? Are the current input fields helpful?
b. Work Function and Hazard categories.

i. Discuss how we use them?
ii. Do we need a new binning process, possible two tiers? Can the existing database do this? (Improvements to the work function and hazard categories, keywords will only affect future submittals. If we expect the database to provide accurate information based on new searches then all of the existing data entries must be revised. Maybe someone from HQ database support could attend the workshop.

c. Keyword search list:

i. How are keywords used?
ii. What can be dropped/added. (Do we still need Y2K or keyword like WSRC?)
iii. Can the keyword list be modified to allow multiple word selections?

d. New Submittals - how to improve the quality of submittals.

i. Look into development of criteria for "Lessons Learned Statement", "Discussion", "Analysis" and "Recommended Actions" that could be added to section headers as link similar to the work functions etc. Use input from the group working on "writing better lessons".
ii. Add link to other input headers (Contact Name, Savings, Reviewer, References) to ensure consistency.
iii. Continually emphasize the importance of entering only lessons that have been learned, what you learned, and how you changed. Clearly state what the lesson is and provide references so the article can be kept as concise as possible. Write with the idea that you are writing so others can learn.

e. Determine if the "Search Text" field could be modified to allow for multiple words for drilling down to a more specific results set. (Requires HQ database support)

2. Additional Tools: Consider updating and distributing SELLS information (Fact Sheets) to promote improvement.

a. Tips for writing LL (include tips for determining if you have a lesson)
b. Value of LL
c. Screening LL for site applicability
d. LL dissemination