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"
67 lines
2.0 KiB
Markdown
67 lines
2.0 KiB
Markdown
---
|
|
id: LIT-20251023125758
|
|
title: NUREG899
|
|
type: literature
|
|
created: 2025-10-23T16:57:58Z
|
|
modified: 2025-10-30T18:20:30Z
|
|
citekey:
|
|
---
|
|
|
|
# NUREG899
|
|
|
|
Emergency operating procedures should be
|
|
*function-oriented*. That means that operators 'do not have
|
|
to immediately diagnose an event... to maintain the plant in
|
|
a safe configuration." Critical functions are cited as:
|
|
|
|
1. Containment integrity
|
|
2. Reactivity Control
|
|
3. Heat Removal
|
|
4. Reactor coolant inventory control
|
|
|
|
Functions are maintained by 'tasks'. Tasks are specific
|
|
actions that are taken to maintain or achieve a function.
|
|
|
|
This doc says EOPs are verified and validated by:
|
|
1. Excercising EOPs on simulators
|
|
2. Control room walk-throughs
|
|
3. Desk top reviews
|
|
4. Seminars
|
|
5. Computer modeling and analysis
|
|
|
|
OPs should minimize the use of cross referencing because it
|
|
increases decision times and increases the chance of human
|
|
error. It's 'disruptive'.
|
|
|
|
Operator Aids are things like flowcharts or graphs that can
|
|
help an operator learn things more quickly and clearly than
|
|
text alone can provide. They should be easily learned and
|
|
retained, while being precise and not cluttered.
|
|
Interpretability is paramount.
|
|
|
|
EOPs have segments:
|
|
1. Cover page
|
|
2. Table of contents if applicable
|
|
3. Scope
|
|
4. A set of entry conditions
|
|
5. Automatic actions that happen by automated systems
|
|
6. What the operator should do immediately
|
|
7. Things the operator should do afterwards based on
|
|
reference to written procedures
|
|
8. Relevant supporting material.
|
|
|
|
Control rooms should have a sufficient number of EOP
|
|
handbooks such that everyone can use one, they're easy to
|
|
get to, and also be located such that they don't interfere
|
|
with workstations or cover up controls. If there's multiple
|
|
control rooms that share a common area, each control room
|
|
should have it's own set of EOPs. They should not be sharing
|
|
copies, essentially.
|
|
|
|
Appendix B talks about logical statements. They're written
|
|
strangely like program control flow, underlined, and
|
|
capitalized:
|
|
|
|
IF RPS scram has not initiated,
|
|
THEN initiate SLC and isolate RWCU
|