ML23242A003
| ML23242A003 | |
| Person / Time | |
|---|---|
| Issue date: | 08/31/2023 |
| From: | Sushil Birla NRC/RES/DE |
| To: | |
| Sushil Birla 301-415-2311 | |
| References | |
| Download: ML23242A003 (4) | |
Text
Reactor Protection System for the Virtual Ford Nuclear Reactor Designed-in Assurance Faculty Advisor: Brendan Kochunas External Advisor: Sushil Bria, US NRC Graduate Student Advisor (if applicable):
Project Motivation:
In current practice, industry is experiencing high cost, uncertainty, and delay in obtaining regulatory approvals for digital reactor protection systems.
The state-of-the-art in software systems engineering can help overcome these issues, but very few know how to use these technologies.
These competencies are needed desperately in every application sector but the training and education infrastructure is not in place.
This project is a hands-on opportunity to learn from world leaders the principles, concepts, methods, and languages, and use of open-source tools and be at the forefront of safety assurance.
References:
- 1. B. Kochunas, et al., Development of the Virtual Reality Ford Nuclear Reactor Learning Environment, Trans. Am. Nucl. Soc., 2023.
Project
Description:
- 1. Extract the SCRAM logic currently in the Virtual Ford Nuclear Reactor (FNR) System model.
- 2. Realize the SCRAM logic as separately generated code.
- 3. During its engineering, generate the evidence of its correct performance.
- 1. Learn the correct-by-construction (C-by-C) process from the example at https://github.com/GaloisInc/HARDENS
- 2. With help from NRC and Galois experts, obtain and configure the necessary tools.
- 3. Follow the C-by-C process for your Reactor Protection System (RPS) to obtain the software implementation.
- 4. (optional stretch goal) Implement the RPS in emulated hardware
- 4. Interface the correct-by-construction RPS with the FNR.
- 5. Demonstrate its correct performance and absence of unspecified behavior.
- 6. Create the safety case (evidence-supported reasoning), patterned after or adapted from a given example.
Desired Outcomes:
- 1. A RPS demonstrated to work correctly with the FNR.
- 2. A safety case for the RPS.
- 3. A modified Virtual FNR System Model including interface with the RPS.
- 4. A report and a conference paper on the development experience.
Tools required (codes, databases, etc): See a case study for a reactor trip system at https://github.com/GaloisInc/HARDENS
- Select the tools applicable to your project.
Recommended team size: 4 Minimum team size: 3 Suggested team roles:
- 1. Reactor analyst to modify the FNR model & develop the interface to the RPS.
- 2. RPS formal specification developer, incl. adaptation of needed tools.
- 3. RPS implementor, incl. adaptation of needed tools.
- 4. Safety case developer.
- 5. [Joint] Report; conference paper.