Learning from Experience (LfE) Database

Introduction

This database is to record Learning from Experience (LfE) relevant to the activities of members of the criticality safety community.

View LfE Database

 

Entry Process Guide

Preparing an entry for the database:

  • Information release number: This provides the NCSP with evidence the information provided has been cleared for public release. This number will not be provided in the publicly available database. After the LfE support team has reviewed the information, the entry will be assigned a LfE ID number and added to the public database.
  • Facility type: This is a general description of the facility. Currently the database has the following choices: Reactor, Fuel Cycle Facility, Storage/Waste/Repository, Office based, Research, and Other. If Other is selected, provide a short description of the facility will not be included in the database. The LfE support team will review the Other entries to determine if a new facility choice should be included.
  • Description of the event: This is 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 information on the site, 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.
  • Immediate actions taken: This is 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: Need to discuss with the LfE support team to determine what would be useful here.
  • Apparent cause(s): Currently, the database has the following choices: 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 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 community.
  • Type of operation: Currently, the database has the following choices: Test/Trial/Experiment, Commissioning, Operations, Maintenance/Shutdown, Decommissioning, Emergency Planning/ Recovery, Criticality Safety Assessment (docs or analysis), or Other. If Other is selected provide a short description of the operation that can be included in the database.
  • Criticality safety parameters affected: Currently, the database has the following choices: 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; The LfE support team will review the other entries to determine if a new choice should be included.
  • Possible keywords: Possible keywords to help others in the community find out about this event.
  • Further information: This is where additional information about the event can be found. This will not be in the database or shared by the LfE support team without permission of the information provider.
  • Information provider contact information: The information will be used by the LfE support team to clarify any of the information provided. This will not be in the database. This will be shared outside of the LfE support team only with the permission of the provider.
  • Before the entry is made public the information will be reviewed by the LfE support team.

Download Template      LfE Question and/or Submit an Event

 

LfE Coordinator Role

The NCSP LfE Coordinator roles and responsibilities are:

  • Sanity check entries in the NCSP LfE database to review, correct, or request information to update any issues found with an entry in the database (example: classification).
  • Prompt members to populate the database.
  • Ensure key international learning events are added to the database.
  • Determine the most appropriate metrics to assess NCSP LfE data.
  • Perform a yearly review of the entries and undertake a trending analysis that best showcases the content of the data.
  • Annually, the workability of the database’s infrastructure should also be examined to identify any potential improvements (e.g., the spreadsheet and associated guidance) based on input from the criticality safety community.

The NCSP LfE support team roles and responsibilities are:

  • Provide advice as requested by the LfE Coordinator. This may include assistance with determining which events are worthy of being classed as Key Learning for immediate dissemination to the criticality safety community.
  • Encourage action from the criticality safety community as needed.
  • Review trending analysis drafted by the LfE Coordinator, provide guidance, and report on how the LfE database is being used.
  • Maintain a high-level overview of the LfE work and conduct annual “health checks” of how the process is going.
  • Review new entries to make sure they are publicly available to share. Assign a LfE ID number if applicable.
  • Review the other entries to determine if a new facility choice should be included.
  • Review the other entries to determine if a new choice in Criticality Safety Parameters Affected should be included.

 

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.

Disclaimer

The statements, views, and opinions presented in this database are those of the contributors and do nor 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.