NAVIGATION MAIN MENU

COMPENDIUM LIBRARY/TWITTER MONITOR
VIDEO GALLERY
Economic News
Newsbrief Archives
Democrat Leadership Twitter and Realtime Feeds
Cabinet twitter and realtime feeds
North America weblog
International weblog
Democrats twitter directory
Latest Government Jobs and Public Tenders
Jobs Matrix
Global Travel Information
Pop Entertainment Forum
Start Portal


Please make a donation to support upkeep of the daily news journal, back archives, twitter feeds and the compendium library.










Strengthening Safety through Managing Knowledge

Daily newsbrief journal for February 2012, also see http://www.usdemocrats.com/brief for a global 100-page perpetual brief and follow twitter @usdemocrats


Strengthening Safety through Managing Knowledge

Postby admin » Mon Feb 27, 2012 7:37 pm

If there are images in this attachment, they will not be displayed. Download the original attachment
Page 1
1“Strengthening Safety through Managing Knowledge”Prepared Remarks forThe Honorable Gregory B. JaczkoChairmanU.S. Nuclear Regulatory CommissionatThe South Texas Project Leadership ConferenceBay City, TXFebruary 24, 2012Good afternoon. I'm pleased to have the opportunity to address your Leadership Forumtoday. I have not had the opportunity to visit the South Texas Project before, so I have been looking forward to this trip. I spent an interesting morning today touring the plant. When Ed Halpin dropped by my office earlier this month, he suggested that I speak to you today about Knowledge Management and I was very pleased to accept, given the significantrole knowledge management plays in ensuring continued safety. Knowledge Management iscertainly something we have focused on at the NRC.Just this week, the Commission held a meeting to discuss Omaha Public Power District’splans to return the Fort Calhoun facility to service after prolonged flooding of the site last summer, as well as safety challenges experienced at the plant recently. It was interesting to methat a question asked by one of my fellow Commissioners, regarding leading indicators, wasvirtually the same question that was asked by a different Commissioner five years ago, in asimilar meeting. To me this was a good example of how knowledge management is vital to all levels of an organization. As a safety regulator, our mission requires us to evolve as we gain new information andexperience. We must continually incorporate new lessons into our approach to safety, and having a strong Knowledge Management program helps us to more effectively utilize ourinformation and experience. This is crucial to fulfilling our mission. NRC NEWSU.S. NUCLEAR REGULATORY COMMISSIONOffice of Public AffairsTelephone: 301/415-8200Washington, D.C. 20555-0001E-mail: opa.resource@nrc.gov Site: www.nrc.govBlog: http://public-blog.nrc-gateway.govNo. S-12-003
--------------------------------------------------------------------------------
Page 2
2Knowledge management is especially important when you are as fortunate as we have been in recruiting and retaining such high-quality staff. People who come to work for us tend to stay for a long time – on average around 22 years. So even though we are, relatively speaking, asmall federal agency, when an employee walks out the door due to retirements or normalattrition, we are losing a tremendous amount of knowledge. Given our critical mission, wecannot let that happen. Lessons learned about safety must be integrated into our everyday thinking or we risk history repeating itself.Despite the agency’s involvement in informal knowledge management activities formany years, in 2006 we decided to establish a more structured and formal way to manage and pass on knowledge. This more focused approach was driven by a several things, including an aging work force, an expectation of increased new hiring, and the advent of additionaltechnological tools. Today, we still use the traditional ways of capturing and sharing knowledge, such as through stored technical documents, mentoring, internal seminars and presentations, and training courses. But we are also now using a commercial web-based application thatincorporates social networking -- we call it the NRC Knowledge Center.The Knowledge Center provides an invaluable source of information for an agency likethe NRC. Employees can fill out a profile with their name, their education, skills, experience, languages spoken, and areas of high-level expertise. The profiles are searchable, and this isimportant. If, for example, we were in a situation where we needed a French-speaking nuclearengineer with specialized experience in a narrow technical area, we could quickly search the system and learn if anyone in our staff has that combination of knowledge and skills. And, wecould quickly reach them. Knowing what experts and expertise we have in our agency means we can meet safetychallenges more efficiently, and the Knowledge Center provides a way of doing just that. The Knowledge Center also allows us to establish virtual Communities of Practice andCommunities of Interest. At the present time, we have more than 150 communities, rangingfrom Nuclear Criticality to our Internal Leadership Development Programs.Employees can join the existing communities, or create new ones. And, within thosecommunities, members can post questions to one another, and those with the answers or related knowledge can reply. The discussion threads are searchable and they are kept permanently. So, new employees who are just beginning their work at the agency can access the community orcommunities that match their job responsibilities. They can search for specific information, and find discussions years after they actually took place. It's a great way to capture and make knowledge accessible throughout the staff. These communities of practice provide a very direct means of transferring knowledge and experience that has been accumulated over many years to staffers who are newer to the agency
--------------------------------------------------------------------------------
Page 3
3and a particular work function. It is also a form of informal learning that can compress the timeneeded for newer staff to build their competencies.In addition to these detailed and personnel-oriented programs, we also, of course, haveour high-level, technical programs to ensure we capture knowledge and lessons on a broad scale,and attempt to integrate those lessons into our everyday thinking so they are not lost. Forexample, we have an entire branch dedicated to Operating Experience. The staff in this branchanalyze events on a daily basis to identify trends and look for opportunities to improve safetythrough everyday experiences at licensee sites.Operating Experience not only benefits our staff and inspectors, but provides usefulinformation to licensees as well. We use our Operating Experience program to provide near real-time information on events and issues. Additionally, we use Operating Experience to provide in-depth analysis of significant events. That information is pushed to our staff for their use, and also is available in a searchable database.We also have a Lessons-Learned Program that is aimed at ensuring that knowledgegained from significant events and issues is retained and disseminated in a manner that will maximize benefit to the agency. The roots of this program go back to 2002 when the Davis BesseLessons Learned Task Force found that performance and programmatic issues it identified were a repeat of similar issues identified in previous NRC lessons-learned reports. That wasinconsistent with the agency’s culture of continuously self-evaluating and improving, and was, in part, a direct result of not having a more formalized knowledge management program. Here are a couple of examples that demonstrate how much transferring knowledge reallymatters. In 2010, there was a trip of an Emergency Diesel Generator (EDG) following a dualunit reactor trip. As it turned out, a relay on an EDG circuit did not perform properly. When thelicensee examined how that happened, they learned that a periodic replacement requirement for the relay was handled by an informal monitoring program that was not tracked by the preventivemaintenance program. In 2002, the component engineer who performed the informalmonitoring was moved to a new position, and that knowledge was lost. Since this periodicreplacement was not done, the relay did not perform properly in 2010, contributing to the loss ofthe EDG at a critical time.In another example, a licensee experienced a loss of inventory from the reactor vesselwhile preparing the reactor for refueling. Since the same procedure was used during priorshutdowns, it was unclear why the same problem had not occurred then. It was learned thatmore experienced operators had been in the control room during prior shutdowns, and knew theyneeded to close two main steam drain valves to avoid a loss of inventory. However, thoseoperators did not write condition reports to document and correct the deficient procedure.Those are just several examples that illustrate how easily knowledge can be lost, and howthat can substantially affect plant performance or create unnecessary problems.
--------------------------------------------------------------------------------
Page 4
4Coming from a slightly different direction, I would also like to provide one example ofusing knowledge management and sharing information. And that is industry’s efforts to resolvethe pressurized water reactor sump clogging issue. When we issued Generic Letter 2004-02, many licensees collaborated to share information on designing and installing improved reactorsump strainers to help resolve this important safety issue. One area where I understand you plan to share information is the work you are doing in developing a risk informed solution to thisproblem. While much has been done, we have not yet achieved closure.Over the past five and a half years, since we began a formal Knowledge Managementprogram at the NRC, we have identified a number of best practices. As you continue to focus on how to document and share the knowledge you gain every day from your jobs, I thought you might be interested in four of the best practices. First of all, change management is incredibly important. There must be strong, consistent support from the top of the organization and Knowledge Management expectationsand processes should be instilled in new employees right from the start. And, it’s not always theolder employees passing knowledge on to newer staff—sometimes new employees can teacholder employees new and better methods for accomplishing a task.Second, keep Knowledge Management efforts practical, and focus on the mission workand where that work gets done.Third, knowledge management should be leveraged to strengthen informal staff learningand development. After all, much of knowledge management is really what we used to callteaching. It’s mentoring on a daily basis.Fourth, try different ideas, and always keep the program evolving. As the one-year anniversary of the Fukushima Dai-ichi accident approaches, we are stillthinking about and discussing the lessons learned from that tragedy. As you might expect, theNRC has taken a broad range of steps to ensure that we capture the knowledge that is related toFukushima. These include the Near-Term Task Force report, a web-based training course, Steering Committee meetings with the staff, Commission papers, an After Action Report on lessons learned from the Operations Center, and more.In closing, I’d like to make the observation that the nuclear industry sets a very good example in the way it shares information and resources amongst its members. This may beunique across industries. I applaud you for taking that approach to help improve performance foreveryone.Thank you for inviting me to speak to you today. I’ve enjoyed being with you and Iappreciate your well-recognized Texas hospitality – you’ve certainly lived up to that reputation.I’ll be happy to take any questions you may have.
admin
Site Admin
 
Posts: 82092
Joined: Fri Nov 27, 2009 7:00 am

Return to February 2012

Who is online

Users browsing this forum: No registered users and 42 guests