Learning from Experience (LfE) Database

Introduction

The database is to record Learning from Experience (LfE) relevant to the criticality safety discipline. The goal of the database is to highlight experiences at other sites that might be applicable to the readers site/facilities (i.e., to help the reader answer the valuable questions of “is the event or learning relevant to my site/facility?” and “have I considered the possible events?”). Entries should include sufficient information to enable a reader to understand its relevance to their site/facilities. The hope is that we can share experience and not relive history over and over. In addition, the LfE database may provide valuable lessons-learned for sites dealing with similar situations.

View LfE database

 

Event-Entry Form Process Guide

Process for Preparing an Event Entry

  • Download/complete the "Event entry form template" with the information below (see "Preparing an Event Entry for the LfE database").
  • Have your completed document reviewed locally for release.
  • Once the local release is approved click "LfE Question and/or Submit an Event" button.
    • Attach Event Entry form to the email.
    • Submit you entry to the LfE team for review, lfe-team [at] llnl.gov (lfe-team[at]llnl[dot]gov).
  • Once your entry has been reviewed, it will be added to the LfE database and you will be notified.

View SAMPLE event entry

Event entry form template download      lfe-team [at] llnl.gov (LfE question / submit an event)

 

Preparing an Event Entry for the LfE Database

Information not shared in the database

  • Contact name: Needed if the LfE Team needs to contact the provider for additional information.
  • Contact email/phone number: Needed if the LfE Team needs to contact the provider for additional information.
  • Organization: Needed if the LfE Team needs to contact the organization for additional information.
  • Release number [or] is information acceptable for release? (Y/N): Needed to verify that the information can be released publicly. All information in the database will be available to the public.
  • Optional information: This is where you will provide detailed information if Other is selected for Facility Type, Criticality Safety Parameters affected, Apparent Cause, or Type of Information. Also, the provider may include additional information that might be useful for a more in-depth review of the event. This will only be released with the permission of the provider.

 

Information shared in the database

  • Facility type: A general description of the facility.
    • Select from the filter one of the following: Reactor, Fuel Cycle Facility, Storage/Waste/Repository, Office based, Research, and Other.
    • If Other is selected, provide a short description of the facility (this will not be included in the database). Our team will review Other entries to determine if a new facility choice should be included.
  • Description of event: Provide a short description of the event that would help others in the criticality safety community understand how the event might be similar to possible events in their facility. This entry should not include any site specific (i.e., site name/location, building, or room). This entry should not include information as to the final product of the entire process or specifics as to the quantity of material involved in the event.
  • Criticality safety parameter affected: Select from the filter what criticality safety parameter was impacted by the event: Mass, Absorption, Geometry, Interaction/ Spacing, Concentration/ Density, Moderator, Enrichment, Reflection, Volume, Temperature, CWS/CAAS/NIM, or Other.
    • If Other is selected, provide a short description of the operation that can be included in the database. Our team will review the Other entries to determine if a new choice should be included.
  • Immediate action(s) taken: Provide a description of actions taken immediately upon discovery of the event. The actions described should emphasize actions that might be appropriate to other sites.
  • Method of resolution: Include corrective or preventive actions that might be transferable to other sites/facilities. Preplanned actions might be included. All of the internal corrective/preventive actions do not need to be presented.
  • Apparent cause(s): Select from the filter what the apparent cause(s) of the event was: Human Error, Maintenance, Equipment Failure, Incorrect Assumption, Software Error, or Other. If Other is selected, provide a short description of the cause that can be included in the database.
  • Root cause: Provide a brief description of the underlying issues that might be appropriate for other sites/facilities to consider.
  • Lessons learnt:
    • What should be taught to your criticality safety staff and others in the criticality safety community?
    • What is the positive lesson that could be implemented in the criticality safety community?
  • Type of operation: Select from the filter what type of operation this was: Test/Trial/Experiment, Commissioning, Normal Operations, Routine Maintenance, Major Maintenance/ Facility Modification/ Shutdown, Decommissioning, Emergency Planning/ Recovery, Criticality Safety Assessment (documents or analysis), Transportation Operations or Other. If Other is selected, provide a short description of the operation that can be included in the database. The LfE support team will review the Other entries to determine if a new choice should be included.
  • Keyword(s): Provide a few keywords that might help others find out about this event.

 

LfE Team Roles and Responsibilities

  • Provide support to the criticality safety community who wish to add entries to the LfE database.
  • Review LfE database entries and potentially request further information to clarify entries.
  • Use sensible metrics to provide trending analysis.
  • Ensure the LfE database and system work properly, identifying improvements and fixing any glitches that could impact the user experience.
  • Identify if new information categories (i.e. facility type or lessons learnt) or if further options within an information category are required.
  • Engage with as many international criticality safety communities to encourage entries and learnings from for the LfE database.
  • Seek feedback from the international criticality safety communities to understand the impact of the LfE database and any potential user improvements.

 

Database

Originally developed for the UK Working Party on Criticality by: M. Savage, G. Willock, B. Philpotts, D.A. Hill, M. Erlund, A. Till, A. Brown. This database and website implementation is updated and maintained by ORNL and LLNL staff and funded by the DOE/NNSA Nuclear Criticality Safety Program with assistance from our international partners for this project.

LfE Team Contacts

Aurelie Bardelay, Doug Bowen, Charlotte Davis, Fabien Duret, Deb Hill, Andy Prichard

LfE-Team [at] llnl.gov (LfE-Team[at]llnl[dot]gov)

 

Disclaimer
The statements, views, and opinions presented in this database are those of the contributors and do not necessarily reflect the view of the NCSP. The NCSP does not guarantee the accuracy of the information provided. Use of the information is strictly at the user’s own risk.