Dane Sabo
f1095af826
M .task/backlog.data M .task/completed.data M .task/pending.data M .task/undo.data M .taskrc A "Zettelkasten/Permanent Notes/20251030141457-nuclear-operating-procedures.md" A "Zettelkasten/Permanent Notes/20251030141936-emergency-operating-procedures.md" M "Zettelkasten/Permanent Notes/Literature Notes/LIT-20251023125758-nureg899.md"
41 lines
1.2 KiB
Markdown
41 lines
1.2 KiB
Markdown
---
|
|
id: 20251030141936
|
|
title: Emergency Operating Procedures
|
|
type: permanent
|
|
created: 2025-10-30T18:19:36Z
|
|
modified: 2025-10-30T19:30:12Z
|
|
tags: []
|
|
---
|
|
|
|
# Emergency Operating Procedures
|
|
Emergency operating procedures for nuclear power are special
|
|
procedures that are used when off-normal conditions are
|
|
present. They are for when 'shit hits the fan'.
|
|
|
|
EOPs have defining regulations. Most notably [[nureg899]].
|
|
NUREG899 is a writers guide to emergency operating
|
|
procedures.
|
|
|
|
EOPs should be 'function-oriented'. This means operators
|
|
should not need to know a root cause to start performing
|
|
control operations in an emergency. Critical functions in an
|
|
emergency are usually:
|
|
|
|
1. [[Containment Integrity]]
|
|
2. [[Reactivity Control]]
|
|
3. [[Heat Removal]]
|
|
4. [[Reactor Coolant Inventory Control]]
|
|
|
|
If each of these are maintained, the reactor can be 'safe',
|
|
and the risk of environmental release is minimized. [[nureg899]]
|
|
|
|
EOPs should minimize cross referencing because it increases
|
|
decision time and is disruptive changing between documents
|
|
[[nureg899]].
|
|
|
|
EOPs today are reveiwed with simulation exercises,
|
|
control-room walkthroughs, seminars, and numerical analysis
|
|
[[nureg899]].
|
|
|
|
|