ML20155F911
| ML20155F911 | |
| Person / Time | |
|---|---|
| Site: | Pilgrim |
| Issue date: | 10/15/1987 |
| From: | BOSTON EDISON CO. |
| To: | |
| Shared Package | |
| ML20151H280 | List: |
| References | |
| FOIA-88-198 1.3.4-10, NUDOCS 8810130414 | |
| Download: ML20155F911 (36) | |
Text
BOSTON EDISON NUCLEAR OPERATIONS DEPARTHENT PILGRIN NUCLEAR P0HER STATION Procedure 1.3.4-10 HRITERS' GUIDE FOR EHERGENCY OPERATING PROCEDURES Total Pages:
36 FORI!yag;.uAlo ONL Approved I
/C// S// /
w Quality Assura tGhnager
'Date
/
Approved
/0 / /
Nudlea[ Operations 7fanager
?Date go13g4000907 j'
JOHNSON 00-198 PDR Safety Evaluation:
Atw1*e4/Not Required Prc:. 1.3.4.10 Rev. 2 Pa;s 1 cf H
Table of Contents Section Eige I.
INTRODUCTION......................
4 A.
Purpose.....................
4 B.
Scope......................
4 C.
Use of Examples.................
4 II.
PROCEDURE IDENTIFICATION......
4 A.
Procedure Numbering and Title..........
4 B.
Procedure Title B, lock..............
5 C.
Revi sion Identification.............
6 III.
PROCEDURE FORMAT............
6 A.
Flowchart Elements 6
B.
Step Numbering 18 C.
Listed Items 19 i
D.
Use of Emphasis Techniques 20 E.
Procedure Layout and Associated Conventions...
21 F.
Instructions for Printing. Copyin Storage.............g and 24 IV.
PROCEDURE CONTENT 24 A.
Level of Detail.................
24 B.
Writing Style..................
25 C.
Cautions and Notes 25 D.
Branching Instructions and Cross-References...
26 E.
Component Identification 28 F.
Spelling, Grammar, and Punctuation 29 G.
Nomenclature, Vocabulary, and Abbreviation 29 H.
Numerical Values 29 Proc. 1.3.4-10 Rev. 2 Page 2 of 35
Table ef Contents (Continued)
List of Examples Number Iltle Elat 1.
E0P title 4
2.
E0P title block 5
3.
Entry Conditions................
6 4.
Entry Point 7
5.
Concurrent execution statement (with Section and path designators.......
7 6.
Instructional step...............
8 7.
Individual decision 8
8.
"Yes/No" decision diamond with an instructional ste paths...... p in one of the response 9
9.
Conditional Statement 10 10.
Use of the word "UNTIL" 10 11.
Use of the word "EXCEPT"............
11 12.
Use of the word "BEFORE" 11 13.
Continuation Conditions.............
12 14.
Hold point...................
12 15.
Override statement...............
13 16.
Exit statement.................
13 17.
Supplemental Information............
14 18.
Caution 14 19.
i Figure.....................
16 20.
Table.....................
18 21.
Step numbering.................
19 22.
Listed items..................
19 23.
Page layout 23 24.
Intra-procedure branching 28 Proc. 1.3.4-10 Re/. 2 Pa;e 3 of 36
I.
INTRODUCTION A.
Purcose This document specifies appropriate instructions, requirements, and conventions for writing PNPS Emergency Operating Procedures (EOPs) to assure the proper and consistent application of human factors principles addressing procedure organization, format, style, and content of the E0Ps is established and effectively maintained.
B.
Erage This Writers' Guide addresses the specifics of procedure identification, format, and content.
The guidance provided herein is applicable to the initial preparation and subsequent revisions of all PHPS E0Ps.
This document supplements existing BECo and PHPS administrative procedures governing procedure preparation, revision, and control, but does not supplant them.
C.
Use of Examoles The examples provided are included solely to illustrate the graphics of the particular feature being discussed.
The text within examples is not to be interpreted as providing accurate instructions for plant operations.
II.
PROCEDURE IDENTIFICATION I
Each E0P shall be clearly and uniquely identified.
Identification shall consist of the procedure number, title, and revision number as described j
below.
A.
Procedure Numberina and Title I
Each E0P shall be assigned a unique identification number and a title which is descriptive of the procedure content.
The procedure number and title shall be presented in large, boldfaced, underlined print located across the top of the E0P (Example 1).
Example 1:
(EOP Title)
EOP-01 i
RPV CONTROL Proc. 1.3.4 10 Rev. 2 Pa;* 4 of 3d
i l
B.
Procedure Title Block Each E0P shall have a title block (Example 2).
The title block shall be located in the lower right-hand corner of the page, with the right and bottom sides adjoining the page border.
If more than one procedure is located on a single page, each title block shall be located in the lower right-hand corner of the associated bordered area surrounding each E0P (refer to Section III.E.5).
The procedure title block shall contain the following:
1.
Plant name 2.
Approval signature (s) 3.
Effective date 4.
Procedure title 5.
Procedure number 6.
Revision number Example 2:
(EOP Title Block)
PILGRIM NUCLEAR POWER STATION i
Approved:
QA Mana;pr
/ Da'e Approved:
Cperatons Secton Manager
/ Date l
Approved:
pad?at Operarons Manager
/ Date Effeciive Date:
ProcMure Tale RPV CONTROL t
ProcWure Number Revis'en E O P-01 0
Proc. 1.3.4-10 Rev. 2 Page 5 of 36 P
C.
Revision Identificati3n Procedure revisions shall be distinguished by a sequential number.
If the content of a procedure is changed for any reason the entire procedure shall be reissued.
III.
PROCEDURE FORMAT The E0Ps shall be structured as flowcharts and formatted in accordance with the conventions detailed below.
Unless otherwise specified, directional arrows entering and exiting flowchart elements shall be positioned along the element's vertical axis.
A.
Flowchart Elements 1.
Intry conditions shall be located at the top (i.e., beginning) of the procedure, enclosed in a heavy-bordered rectangle with rounded corners (Example 3).
The parameters and the associated values or conditions shall be presented in a tabular format. Variances are permitted where a tabular presentation of values / conditions may be confusing.
i Example 3:
(Entry Conditions)
\\
ENTRY CONDITIONS PARAMETER CONDITION RPV water level B e'o w + 9 in.
RPV prossure Above ic85 psg Orpeil pressure Above 2.5 psg Both of the totiowing condsons exist:
o A scram is required Reactor power is above 3% or cannot be determined
]
U Proc. 1.3.4-10 Rev. 2 Page 6 of 35
. -.- L
i A.
Flowchart Elements (continued)
Entry points for E0Ps entered only from other E0Ps shall be indicated by the word "START" printed in boldfaced uppercase letters centered in a heavy-bordered rectangle with rounded corners (Example 4).
This element shall be located at the top (i.e., beginning) of the procedure.
Example 4:
(Entry r int) o START V
2.
Concurrent execution staterreau shall be enclosed within a shaded elongated rectangle (Example 5).
The instruction directing concurrent performance of multiple sections or steps of a procedure shall be centered beneath the directional entrance arrow within the rectangle. The subsequent procedure sections, paths, or steps which are to be executed concurrently shall be arranged along parallel axes directly below the concurrent execution element, appropriately spaced so as to achieve a balanced presentation.
Example 5:
(Concurrent Execution Statement) u um= ve corw nev.c., w.ci.'RPV premte ud re eda p:=er corweerey,
i RPV WATER LEVEL O RPV PRESSURE REACTOR POWER l
If if IP 3.
Section designators shall be printed in boldfaced uppercase letters centered within a shaded trapezoid.
This element shall only be used in conjunction with a concurrent execution element (Example 5).
I
]
i Proc. 1.3.4-10 Rev. 2 Page 7 of 36
A.
Flowchart Elements (continued) 4.
Instructional sten 1 shall be formatted as complete sentences and enclosed in rectangles (Example 6).
Example 6:
(Instructional Step)
V Terminate drywett sprays.
U 5.
Individual decisions constituting major branch points within a procedure shall be phrased as "yes/no" questions enclosed in diamonds (Example 7).
Arrows extending from the points of the diamond shall be used to depict the "yes" and "no" response paths. The "yes" response path should exit from the right and the "no" response should exit from the bottom. Variances from this convention are permitted if necessary to accommodate proper phrasing of the "yes/no" question.
"Yes" and "No" response path labels shall be capitalized and placed adjacent to the respective exit points.
Example 7:
(Individual Decision)
U Has it been determined that the reader yn wal tamain shudown under all cond'ibns wahod bomn
?
No U
6.
Individual decisions not constituting major procedure branches shall be presented in one of the formats described below.
Consistent use of the format selected for a particular hpplication should be maintained.
A "Yes/No" decision diamond (as described in Section III.A.5) a.
with one o.f the response paths containing an instructional step (Example 8).
Proc. 1.3.4-10 Rev. 2 Page B of 36
i A.
Flowchart Elements (continued)
Example 8:
(Yes/No" Decision Diamond with an Instructional Step in One of the Response Paths) 1 Has ARi been Yes initiated
?
U Depress both 'AlWS' pushbuttons.
\\
U b.
A "Yes/No" decision diamond (as described in Section III.A.5) with one or more instructional steps in each response path.
Variances from the above guidelines are permitted where necessary to clarify the procedure flowpath or enhance the usability of the flowcharts.
7.
Conditional statements which modify instructional steps shall be l
presented in a format which clearly distinguishes between conditions and actions.
Highlighted logic terms shall be used to I
emphasize distinction.
The following format conventions shall apply:
i l
a.
The conditional part of the instruction shall be stated first, followed by the contingent action (Example 9).
l This formatting requirement does not apply to conditional clauses that begin with "UNTIL" (see Part c below) or "EXCEPT" (See Part d below).
i b.
Logic terms shall be printed in uppercase letters physically separated from the remainder of their respective clauses (Example 9).
Pre:
1.3.4 10 Rev. 2 Page 9 of 36
I A.
Flocchart Elements (continued) 7.
Canjitional statements (continued)
Example 9: (Conditional Statement) 1 r 1 HEN SRVs are used to stabilize RPV Open SRVs in the fonowing sequence,if possibfe: 8, C, D. A.
s A
SRVs are used to stabilize RPV pre ssure, THEN AND PW all SRV W sMes The continuous SRV pneumatic in the ' AUTO
- postuon.
^
suppY (Nitrogen and instrument Air)is or becomes unavttable, V
1 c.
When a prescribed action is to be performed until certain specified conditions occur, the condihons shall be prefaced I
by the word "UNTIL" printed in uppercase letters (Example 10).
Separation of "UNTIL" from the preceding and following text is not required.
Example 10:
(Use of the word "UNTIL")
I
__U l
Manuah open el SRVs UNTL RPV pressure drops bebw 940 po'.g l
U d.
When a prescribed action is to be performed with centain specified exceptions, the exceptions shall be prefaced by the word "EXCEPT" printed in uppercase letters (Example 11).
Separation of "EXCEPT" from the preceding and following text is not required.
Proc. 1.3.4-10 Rev. 2 Page 10 of 36
A.
Flowchart Elementi (continued) 7.
Conditional statements (continued)
Example 11:
(Use of the word "EXCEPT")
U Terminate injection into the RPV from oources external to the primary containment EXCEPT from boron injection systems, CRD, and those systems necessary to assure adequate core coolmg, e.
When a prescribed action may be performed any time before a specified condition occurs, the condition shall be prefaced by the word "BEFORE" printed in boldfaced uppercase letters.
"8EFORE" shall be separated from the text which defines the condition and formatted as shown (Example 12).
Example 12:
(Use of the word "BEFORE")
U Operate a!! available Suppression Pool Cooling using only those RHR pumps not required to assure adequate core cooling by continuous operation in the LPCI mode.
BEFORE Torus water temperature reaches the BifT (Figure 3 2).
i Enter EOrat. *RPV Control,' and execute i
ECP Ot concurrently with this procedure.
g U
f.
The intermixing of clauses beginning with "and" with those beginning with "or" within an individual step or decision
)
should be avoided whenever possible.
If use of an "and/or" i
logic structure is required, a decision table, an appropriately structured series of connected decision diamonds, or a acceptable alternate format shall be used to clearly depict the relationship between the conditional clauses.
Prc:. 1.3.4-10 Rev. 2 Pa;e 11 of H
l A.
Flowchart Elements (continued) i 8.
Continuation conditions are plant conditions that cause procedure execution to immediately proceed from one instructional step to a subsequent element in the flowchart path. Continuation conditions shall be prefaced by the word "HHEN" orinted in uppercase letters formatted as shown (Example 13). Note that more than one plant condition may apply to execution of an instructional step, and each separate condition may (or may not) proceed to a different i
flowchart element.
Example 13:
(Continuation Conditions)
U Mairanin RPV water level between 126.3 m. (TAF) and +48 in. wth one or more of the Group C RPV Injecton Systems.
WHEN.371 bs of boron have WHEN..RPV water level cannot been injeded into the be maintained above
y V
9.
Hold ooints shall be formatted as instructions beginning with "HAIT UNTIL..." enclosed in octagons (Example 14).
The words "RAIT UNTIL" shall be printed in uppercase letters.
Example 14:
(Hold point)
U WAIT UMTit. any of the following cond*.cns exist:
l o Allcontroi reAs are inserted i
to or bepnd poslton oo o I has been determined that the i
reactor wil remain shutdown under al condit' ns without boren o
o The reactor is shutdown and no boron has been injeded into the RPV o 539 bs of boron have been bWed into the RPV U
proc. 1.3.4-10 Rev. 2 Page 12 of 36
l A.
Flowchart Elements (continued)
- 10. Override statements are those conditional instructions which i
apply while executing one or move steps. Override statements shall be formatted as decision tables enclosed in shaded heavy
,' l bordered rectangles (Exartple 15). Conditional statements and contingent actions are presented in separate columns, each column headed by the respective logic term.
Logic terms shall be printed in boldfaced uppercase letters centered over the respective column.
Shaded lines extending downward from the left and right sides of the enclosing rounded-corner rectangle shall be used to indicate the steps to which an override statement applie..
t ;
(Extension lines need not be used where an override statement j
applies to an entire procedure.)
j Example 15:
(Override Statement)
I f IF THEN The offsite radioactivity Isolate the primary retsase rate is espected containment vent to toach or toaches the and purge.
sne release rate LCO V
L J
I
- 11. Procedure Exit statements and end ooints shall be enclosed in heavy-bordered rectangles with rounded corners (Example 16).
Variances to this convention are permitted when exit statements are an integral part of override statements; when this situation occurs, the override statement formatting conventions apply.
Example 16:
(Exit Statement)
V Exlt this procedure and enter the RPV Pressure secton d EOP.oi, *RPV contrd.'
Proc. 1.3.4-10 Rev. 2 Page 13 cf 36 W
A.
Flowchart Elements (continued)
- 12. Syppjemental information that applies to the performance of a step may be placed outside of the procedure flow path, with dashed lines used to indicate step association (i.nample 17).
Example 17:
(Supplemental Information) 1 U
RapidY depressurize the RPV, defeating l RPV DEPRESSURIZATON PATHS isolation interlocks if necessary, using one or more of the RPV Depressurization
.a o Main turbine teass vahes l
Paths. (Refer to Procedure 5.3.24 l o Wah steam Ene drains 8
'Ahernate Methods for Venting and i
Depressurizing the RPV Under Emergency
, o HPCIW wnEne Cond4 tons,' and Procedure 5.3.21, l o RelC stearn Ene i
- Bypassing So!*cted interlocks.')
'..o RPV head M e
U
- 13. Notes shall be printed in italics and placed within the respective flowchart elerent, located immediately preceding or following the associated text (as is most appropriate considering the information content of the notes).
The word "NOTE" printed in uppercase letters and punctuated with a colon shall preface the
)
text of the note.
- 14. Cautions shall be numbered consistent with the numbering scheme i
i em;,loyed in the Plant-Specific Technical Guidelines.
The applicability of a caution at a point in a procedure shall be indicated by a circle with a black background enclosing the caution number (Example 18).
The full text of each referenced caution shall be enclosed in a rectangle and arran periphery of the flowchart in numerical sequence, ged around the
)
located to the left or above any figures present (Refer to Section III.E.6).
Example 18:
(Caution)
O
^ 'apid inaease in injection into the RPV mey induce a large power excursbn and result in substantial core dr. mage.
4 Proc. 1.3.4-10 Rev. 2 Page 14 of 35
A.
Flowchart Elecents (continued) 15.
Ficures shall be used to present graphical plots of limits expressed as a function of two or more plant parameters (Example 19).
Figures shall be numbered sequentially, in the order referenced within the procedure (top to bottom and left to right in the procedure flow path), using a prefix corresponding to the number of the applicable procedure followed by a decimal numeral.
(For example:
Figure 1.2 would be the second figure referenced in E0P-1.) The symbol "#" and t'u abbreviation "No." shall not be used.
Figure references shall be enclosed within parentheses.
J Each figure shall have a label comprised of the figure number and a descriptive title.
Figures shall be grouped or stacked in sequence (top to bottom, left to right) around the periphery of the flowchart (refer to Section III.E.6).
Figures shall be constructed and presented in accordance with the following conventions:
a.
All text and graphics should be clear, simple, and easily
- readable, b.
Figure titles shall be printed in boldfaced uppercase letters and, together with the figure number, centered above the 3
figure.
c.
Axes of graphs shall b3 labeled with appropriate parameters, units, and numerical values.
Axis numerical gradations and units shall correspond to those of associated control room instruments.
d.
Grid lines shall be provided on graphs as appropriate to aid in interpolating plotted values to the required precision.
e.
Operating regions beyond the action level defined by a graph I
shall be delineated through use of cross-hatching or background shading.
Pro:. 1.3.4-10 Rev. 2 Pa;e 15 of 35
Exarnple 19:
(Figure)
U Terminate al injedion into the RPV and reduce RPV water level.
WHEN.. RPV water level WHEN Inhion into the RPV Indcation is restored, has been terminated and prevented for the MCUTL (Fgure 6.2).
U FIGURE 6.2 MCUTL (MAXIMUM CORE UNCOVERY TIME LIMIT) 20 -
l l :
16
- .i. !. f.
S
/
5
.g 5,14
/,
,...!...}. !. !. ).
> 12 gg-
... g.......;... >. ;. g. <.
y 10
~ "...). " " j... j...j ~.. !. j..
~
8
/
... g. v.3 3.;n o n n..y.n o tu ngo.,.ny....:. g <.
l
....... i....}.. j.. j. i.j.} 1,...........j..... j....:...:j...:.
s.
}jj 4
,,,,ii 1
to too TNE AFTER REACTOR SHUTDOWN (hr)
Proc. 1,3.4-10 Rev. 2 Page 16 of 36
A.
Flowchart Elements (continued)
- 16. lables shall be used to effectively organize, correlate, or subdivide lists of systems, values, sensors, or other data (Exampit 20).
Tables shall be numbered sequentially, in the order referenced within the procedure (top to bottom and left to right in the procedure flow path), using a prefix corresponding to the number
~
of the applicable procedure followed by a decimal numeral.
(For example: Table 4.2 would be the second table referenced in E0P-4.) The symbol "#" and the abbreviation "No." shall not be used.
Table number references shall be enclosed within parentheses.
Each table shall have a label comprised of the table number and a descriptive title.
Tables shall be grouped or stacked in sequence (top to bottom, left to right) around the periphery of the flowchart, to the right of any figures present (Refer to Section III.E.6). Small tables may be placed alongside the flowchart element in which they are referenced (Refer to Section III.A.12).
Tables shall be constructed and presented in accordance with the following conventions:
All text and graphics should be clear, simple, and easily a.
readable.
b.
Table title, shall be printed in boldfaced uppercase letters and, together with the table number, centered above the table, c.
A border shall enclose each table, d.
A heaoing shall be provided for each column. Headings shall be printed in uppercase letters and centered over the columns.
Engineering units shall be included with column headings where applicable.
I A double horizontal line shall be placed below the column e.
headings.
f.
Columns shall be divided by vertical lines.
g.
Dashed horizontal lines or blank spacing may be used within tables to group (or divide) entries as appropriate to aid readability across the entries, t
Proc. 1.3.4-10 Rev. 2 Page 17 of 3(
i A.
Flowchart Elements (continued)
Example 20:
(Table)
U
~
WAIT UNTIL the water levelin the reactor building floor drain sump or an area le above the maximum normat operating value (Table 4.1).
U TABLE 4.1 SECONDARY CONTAINMENT SUMP / AREA MAXIMUM WATER LEVELS l'
k%X NORA%L MAX SAFE OPERATING OPERATING SUMP / AREA VALUE VALUE (Inches above floor)
(Inches above floor)
SUMP 1 inch on HPCIpump Reactor build ng floor drajn room floor N/A AREA
{
N. W. quadrant 1
6 S. E. quadrant 1
6 HPCI compartment 1
6
- W. quadrant 1
6 CR0 quadrant 1
6 8.
Steo Numberina Only those operator actions that must be executed sequentially and that are presented within the confines of one flowchart element shall have designated step numbers. Such steps shall be assigned sequential arabic numt,ers (Example 21).
Proc. 1.3.4-10 Rev. 2 P4;e 15 of 36
i Exa:ple 21:
(Step numbering) i j
if
- 1. Shut down the reactor IF recirufstion pumps and drywen Torus water levelis below 183 in.
cooling fens.
AND EE
- 2. Initiate drywell sprays using Drywell pressure and temperature only those RHR pumps not are below the DSIL (Fgure 3.1) required to assure adequate a ion the dim e.
WHEN.. drywet temperature cannot be maintained below 281'F, r
if C.
Listed Items
{
Hultiple items (systems, plant conditions, etc.) for wh!ch there is no unconditional pre-designated preference or priority shall be arranged in a list format.
Each entry in the list prefaced with a bullet (o).
Bullets shall be indented two spaces to the right of the left margin of i
the imediately preceding text (Example 22).
Variances to this convention are permitted (Refce to Example 14) where listed items appear in elements whose shar necessitates a centered text format (i.e., octagons or diamonds).
Exaaple 22:
(Listed Items)
I if Inaiste each of the following wtuch should l
have in)tiated but dd not; o isolat'on oECCS o Emergercy deset generator If Proc. 1.3.4-10 Rev. 2 Page 19 of 36
D.
Use of Emohasis Techniaues (continued) 1.
Text of instructional steps which may cause control of a parameter to transfer from one procedure (or section of a procedure) to another (e.g., "Primary Containment Flooding is Cequired")
j.
Identification of as-labeled component designations, control switch positions, and annunciator engravings k.
The procedure title, number, 'evision number and plant name within title blocks 1.
The word "BEFORE" (r.efer to paragraph III.A.7.e) 3.
Flowchart titles shall be underlined.
4.
Italics shall be used for the text of notes.
5.
Quotation marks shall enclose the as-labeled instrument and component designations, control switch positions, and annunciator engravings. This enhancement shall not be used if it is deemed to
{
detract free the readability of the flowchart.
E.
Procedure layout and Associated Conventions (Example 22) 1.
More than one procedure may be placed on a page (page size restrictions permitting).
2.
Maximum page size shall be restricted to that which can be acconvnodated by reprographics capabilities.
3.
Page breaks in a procedure are not allowed.
j 4.
A border approximately 1/2 inch from the edge of each side of the page shall be used to enclose the procedure (s) on the page. A line of medium thickness shall be used to form this border.
I' 5.
d (he procedure title block (s) shall be located in the lower right corner (s) of the bordered area (s) surrounding the E0P(s)
(Example 23).
6.
Cautions, figures, and tables shall be placed along the page periphery as described in Sections III.A.14,15, and 16, respectively (Example 23).
7.
Solid lines ending in arrows shall be used to connect flowchart elements and thereby indicate flowpaths through the procedure.
Progression through a procedure ahall generally be down and to the right.
8.
Procedure titles and flowchart elements (including connecting lines and extension lines emanating from override statements) shall be located no closer than 1/2 ine.h to the page border.
Proc, 1.3.4-10 Rev. 2 Page 21 of 36
m m
M=
CAUTIONS f
CAUTIONS n
w PROCEDURE C
PROCEDURE m
l
]
l m
l j
I 8
f l
n I8 vo en..t)
FIGURES AND TABLES FIGURES AND TABLES
~
w-ow
-s.s w..
(_P TITLE TITLE BLOCK BLOCK W
I M
~
i l,_- -
e F.
Instructions for Printina. Convina. and Storaae 1.
Text within flowchart elements shall be single-spaced, with one-and-a-half line spacing maintained between listed items and between multiple instructions or statements enclosed within one flowchart element.
i 2.
Text within instructional steps, exit statements, and endpoints shall be left-aligned.
3.
Text within the individual columns of entry conditions, override statements, and elements with decision table formats shall be left-aligned.
4.
Text within hold points (octagons) and decision diamonds shall be centered.
5.
Type size shall be no smaller than 9-point.
6.
A simple, easy-to-read, type style shall be used. A type style which incorporates serifs or other character embellishments shall not be used.
7.
Copies of the E0Ps shall be legible, closely approximating the m
quality of the original.
8.
Control room copies of E0Ps shall be clearly distinguishable from other plant procedures, and shall be stored in a location where they are readily accessible to operators on shift.
IV.
PROCEDURE CONTENT A '.
Level of Detail A level of detail shall be established in the E0Ps that is consistent with the following guidelines:
1.
The level of detail should be consistent with the knowledge and capabilities of a newly-licensed reactor operator.
The relative complexity of and an operator's familiarity with the evolutions to be performed should be considered.
i 2.
Excessive detail should be avoided.
Expected results of routine actions need not be stated.
1 3.
Where instructions are written in general terms, the user should be able to explain the execution of the associated tasks in detail.
4.
Where appropriate, the following iaformation shall be provided:
- System response times
- Equipment limitations Prec. 1.3.4-10 Rtv 2 Page 24 of 36
\\
I l
A.
Level of Detail (continued) f
- Instrument inaccuracies
- Alternate or backup instrumentation
- Manual override instructions
- Methods of verifying correct plant response 5.
Instructions shall be brief and precise; however, technical accuracy takes precedence over brevity.
Short, simple sentences
~
shall be used. Any required verification of automatic plant response shall be included as a instruction.
B.
Writina Style The E0Ps shall be written in accordance with the following style guidelines:
1.
The procedure shall be easily readable and interpretable.
2.
Directions shall be written in the second person imperative mood withanimplicitsubject.
3.
Each instructional step shall address only one idea (e.g., a series construction of multiple instructions each coupled with the
- word "and" to form one long sentence shall not be used).
4.
The objects of actions shall be specifically stated (i.e., it should be obvious exactly what is to be done to what). Multiple objects (3 or more) shall be listed individually, and separately from the preceding text.
5.
Actions which must be performed concurrently shall be explicitly identified as such.
6.
1.imits shall be expressed quantitatively (Refer to Section IV.H).
7.
Instructions which require performance of arithmetical calculations should be avoided whenever possible.
C.
Cautions and Notes Cautions shall be ustd to identify a potential hazard to personnel or i
equipment.
Notes shall be used to provide supplementary information related to the perforunce of a particular action.
Use of cautions and notes should be minimized. Neither shall be contain instructional steps.
Proc, 1.3.4-10 Rev. 2 Page 25 of 36
0.
Branshina Instructions and Cross-References i
Branching instructions shall be used to direct the operator to transfer from one procedure (or section of a procedure) to another, or to execute an additional procedure concurrently rith the procedure (s)
[
presently being executed.
These instructions shall be clear and specific; wording shall be chosen so as to preclude ambiguity.
Branching instructions shall be presented as complete sentences in one of the formats dstalled below, as appropriate. Mithin the context of branching instructions, the term "section" means that portion of an E0P containing the instructions for controlling a particular plant parameter (e.g., the RPV Hater level section of the RPV Control Procedure).
Branching instruction formats:
1.
Exit this procedure and enter (Procedure X),
"(Procedure Title)".
Sptcifies that the operator shall exit the procedure c:mtaining the instruction (all sections if there are more than one), and enter the identified procedure.
2.
Exit the (Parameter) section of this procedure and enter (Procedure X), "(Procedure Title)".
Specifies that the operator shall exit the section of the procedure containing the instruction and enter the identified procedure; execution of otbtr sections of the procedure shall continue as appropriate (i.e., no exit is made from other sections of the procedure containing the instruction).
i 3.
Exit this procedure and enter the (Parameter) section of E0P-(X),
i
"[EOP Title)".
Specifies that the operator shall exit the procedure containing the instruction and enter the identified section of the identified procedure.
4.
Exit this procedure and enter the (Parameter) section and the (Parameter) section of E0P-(X) "(EOP Title)"; execute these sections of E0P-(X) concurrently.
Specifies that the operator shall exit the procedure containing the instruction and enter the identified sections of the specified E0P; both sections of the E0P being entered shall be executed concurrently.
5.
Enter (Procedure X), "(Procedure. Title)", and execute (Procedure X) concurrently with this procedure.
Specifies that the operator shall enter and execute the identified procedure concurrently with the procedure i
containing the instruction.
P r o c, 1,3,4 10 Rev. 2 Fa;e 26 of 3!
~
I D.
Branchina Instructions and Cross-Refarences (continued) 6.
Continue at (Y).
Specifies that execution of the procedure (or section of the l
procedure) containing the instruction shall transfer froe the step presently being executed to the location indicated.
This format shall be used to branch "forward" in ar EOP.
7.
Return to (Y).
Specifies that execution of the procedure (or section of the procedure) containing the instruction shall transfer from the step presently being executed to the location indicated.
This format shall be used to branch "backward" in the EOP.
For branching formats 1. 2, and 5:
The procedure to be entered shall be entered at the beginning.
For branching formats 3 and 4:
The proper entry point to an E0P section shall be indicated by the symbol shown below.
)
E0P47 )
The procedure number within the spbol shall be that of the procedure containing the exit branch instruction.
For branching formats 6 and 7:
The symbol "[Y)" shall be a capital letter placed within a circle as shown below:
g This symbol shall be repeated at the location where procadure r
exacution is to be continued (or returned to).
In each
['
instance the letter designator shall be unique within the E0P. A dotted line connecting the pair of symbols may be used as an aid for proler execution of the procedure (Example 24).
Forward and backward branching within a procedure should be minim' zed.
Prec. 1.3.4-10 Rev. 2 Page 27 of 36
I D.
Branchina Instructions and Cross-References (continued)
Example 24:
(Intra-Procede e Branching) i 1
if F
pp THEN f
37 g,,_,,s,,,,
_. g......................... f...!
.g =
u,= w w =ana wv.
qp maskin wth af Gray A RPV Iqedam e,w.snw. =
m e nryw.,w ews=
J
- 136 3 h f4 Ir l
Cross-references shall be specified where additional procedural instructions may be required to perform the specified task or evolution. The appropriateness of providing a procedure reference shall consider aspircts such as complexity of and operator familiarity with the actions to be performed.
Use of cross-references should be minimized; if only a few, relatively simple actions are involved, the referenced instructions shall be incorporated into the step itself.
References to supplemental procedures shall identify both the procedure number and title.
The title shall be enclosed within quotation marks.
Figures and tables referenced within a procedure shall be identified by 4
number; identification of the title is not required.
I i
E.
Costgagnt Identification Components shall be clearly and completely identified.
j conventions shall apply:
The following 1
1.
If the procedure refers to a specific control switch or instrument, the.=s-labeled designation shall be used, typed in uppercase letters and enclosed within quotation nsrks. Otherwise, coeren-usage designations shall be used, f
G Proc. 1.3.4 10 Rev. 2 Page 28 of 36 i
l i
E, commonent identification (continued) i 2.
System titles shall be capitalized.
The word "systes" need not be included in the title.
'l 3.
Component locations shall be specified if the components are infrequently used or if there would otherwise be a possibility of confusion.
F.
$nellina. Gra
- r. and Punctuation Spelling, gramar, and punctuation shall be consistent with standaro rules and modern usage. The following conventions shall also apply:
1.
Excessive use of commas should be avoided. Comas are not necessary in elements using a columnar format (e.g., override statements).
l 2.
Use of definite articles, pronouns, and adverbs should be minimized. Personal pronouns shall not be used.
G.
tOmenclature. Vocabularv. and Abbreviations Nords and abbreviations shall have consistent meanings. The following conventions shall apply:
3 1.
Simple, comon words shall be used.
i 2.
Words shall have specific, precise meanings. Use of ambiguous terms should be avoided.
1 3.
Logic terms shall be used consistent with the applications defined in Table 1.
4.
The standard definitions listed in Table 2 shall be adopted.
l 5.
Use of acronyms and abbreviations should be minimized and only those imediately recognizable shall be used.
(A list of acceptable acronyms and abbreviations is provided in Table 3.)
H.
Numerical Values Limits and values of operating parameters shall be expressed quantitatively. The following conventions shall apply:
1.
Arabic numerals shall be used.
1 I'
2.
Parameter values shall include the units of measurement. Units shall be the same as those displayed on associated panel instrumentation.
3.
Parameter values shall be expressed to a precision consistent with the intent of the action (s) specified in the step.
)
4 P r o c. 1. 3. 4 -10 Rev. 2 Page 29 of 35
t i
H.
Numerical Values (continued) 4.
Acceptance values shall be expressed in terms of a range rather than a tolerance band to obviate the need for mental arithmetic (e.g., 20 in to 30 in., rather than 25 in.15 in.).
l 5.
A slash mark (/) shall be used in place of the word "per" (e.g.,
mR/hr).
6.
Numbers between zero and one shall be expressed in decimal form with a zero preceding the decimal point (e.g., 0.12).
I l
I L
i i
d l
1 Pro:, 1,3,4,)n p'V-2 Page 33 of 3g 1
I Table 1: Application of Logic Terms l
Loate Tara Definition l
l l
AND Designates a combination of two or more l
conditions.
Identifies the second and l
subsequent elements of a set of conditions.
I I
BEFORE Indicates that the respective action is to l
be performed prior to the occurrence of a l
specified condition. Does not imply or j
require any specific margin be observed l
when a step states that action be taken j
"before" reaching a limit or value.
l l
I EXCEPT Specifies an exception to or exclusion from l
taking a prescribed action.
l l
IF Indicates that performance of the l
associated action is contingent upon the j
existence of the identified condition (s).
l If the identified conditions do not exist, l
the prescribed action is not to be taken l
i and execution of operator actions proceeds j
to the following step.
l i
l OR Designates alternative combinattors of l
conditions.
Indicates that the associated l
action is to be performed if any one of the l
specified conditions occur.
(Always used l
in the inclusive sense.)
l l
THEN Designates the action portion of an l
instruction.
l I
MIT UNTIL Pdicates that execution of subsequent l
operator actions is not permitted until l
3 the identified condition exists.
i I
WHEN Indicates that upon occurrence or existence l
of the identified condition (s), execution of l
1 the procedure should imediately proceed to l
the next identified flowchart element.
l l
UNTIL Indicates that the associated action is to l
t be terminated when the specified conoitton l
occurs.
l 1 _____________________________________l Proc. 1.3.4-10 Rev. 2 Page 31 of 35 1,
['
Table 2: Standard Nomenclature and Definitions Available: The state or condition of being ready and able to l
be used (placed into operation) to accomplish the stated l
(or implied) action or function.
I I
Cannot be determined: The value or status of the specified l
parameter relative to the procedure action level cannot l
be ascertained using available ino' cations.
I I
Cannot be maintained: The value of the specified parameter
[
cannot be kept above or below (as applicable) the identified l
limit.
Implies an evaluation based on system performance and l
availability considered in relation to parameter values l
and trends. Neither implies that the parameter must
{
actually exceed the limit before the action is taken nor l
that the action must be taken before the limit is reached.
l l
Cannot be restored: The value of the specified parameter l
cannot be returned to within the specified limit.
l Implies an evaluation based on system performance and l
availability considered in relation to parameter values l
and trends. Does not imply any specific time limit, but l
does not permit prolonged operation beyond the limit.
[
i l
Close: To position a valve or damper so as to prevent flow l
of the process fluid.
I I
Confira: Use available indications and, as appropriate, l
physical observation to establish that the specified l
action has occurred, conditions are as stated, etc.
l Includes an implied requirement to take corrective action l
if the identified conditions do not exist.
I I
Control: Take action, as necessary to maintain the value of l
the specified parameter within applicable limits.
l t
I l
Enter: Commence performing, in sequence, the steps of the l
identified procedure.
I l
Execute: Perform the actions prescribed in the identified l
step.
l l
l Exit: Cease performing the stept of the identified procedure.
l 1
l Initiate: Operate the necessary controls so as to establish l
)
the specified system configuration or plant condition.
l Prolonged attempts to jumper interlocks, align a) ternate j
or backup power supplies, enter remote areas to manually i
l operate valves, etc., are not intended by this term.
l I
1 Proc. 1.3.4-10 Rev. 2 Page 32 of 3i
I Table 2: Standard Nomenclature and Definitions (Continued)
Line up: Estab.ish the prerequisites necessary for systen l
operation. Does not encompass starting main system pumps.
l l
Maintain: Take action, as necessary, to keep the value of the l
specified parameter within the applicable limits.
I I
Monitor: Observe and evaluate at a frequency sufficient to remain
~
l apprised of the value, trend, and rate of change of the l
specified parameter..
I I
Open: To position a valve or damper so as to allow flow of l
the process fluid.
l l
Place: To align a switch to a specified position.
l l
Prevent: Take action to forestall or avert the state.
l condition, or action addressed by the step.
I I
Purge: Force flow through an enclosed volume.
Includes
[
establishing both an influent and effluent flowpath.
l l
Restore: Take action, as necessary, to return the value of l
the specified parameter to within appitcable limits.
I I
4 Set: To positten a control to a specified scale value.
I I
Shut: To position a breaker so as to permit the flow of l
current in the associated circuit.
l l
Slowly: Only as fast as can be accomodated and still maintain l
effective control of the associated parameter (s) l within specified values or limits.
l l
Start: To energize a pump or fan motor.
l l
Teralnate: Stop the stated action, process or evolution.
l The most direct action to stop the stated action / process /
l evolution is preferred, but a wide variety of actions may l
be esployed.
I I
Throttle: To position a valve or damper so as to partially l
restrict flow of the process fluid.
l l
Trip: To deenergize a pump or fan motor; to position a breaker l
so as to interrupt or prevent the flow of current in the l
associated circuit.
l l
Vent: Open an effluent (exhaust) flowpath from an enclosed volume.
l l______________________________________l Fro:. 1.3.4-10 Rev. 2 Page 23 of 3A 4
i
Table 3:
Standard Acronyms and Abbreviations I
i l_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _I Abbreviation Meanino i
(
ADS Automatic Depressurization System i
I APRM Average Power Range Monitor I
I ARI Alternate Rod Insertion l
l BIIT Boron Injection Initiation Temp.
I I
CAC Containment Atmospher#c Control I
I CAD Containment Atmospheric Dilution 1
I CPS Counts Per Second CRD Control Rod Drive i
I CS Core Spray I
I ECCS Emergency Core Cooling Systems I
l CST Condensate Storage Tank I
I Demin Domineralizer I
I DSIL Drywell Spray Initiation Limit i
I DH Drywell I
i 0F Degrees Fahrenheit I
I i
ft Feet I
I FM Feedwater I
I GPM Gallons Per Minute i
I I
H&V Heating and Ventilation i
I HCLL Heat Capacity level Limit I
i HCTL I
i Heat Capacity Temperature Limit I
HCU Hydraulic control unit l
1 HPCI I
I High Pressure Coolant Injection j
4 I
hr Hour i
l l
HX Heat exchanger j
l a
I in.
Inch I
I l
Proc. 1.3.4 10 Rev. 2 l
Page 3s of 35
I Table 3:
Standard Acronyms and Abbreviations (Continued)
I Abbreviation Meanina I
l l
lbs Pounds l
1 LCO Limiting Condition for Operation l
l LI Level Indicator I
l LOCA Loss of Coolant Accident l
I LPCI Low Pressure Coolant Injection 1
I LR Level Recorder I
I KARFP Minimum Alternate RPV Flooding l
Pressure j
l MCFI Minimum Core Flooding Interval l
l l
MCUTL Marimum Core Uncovery Time Limit l
l min Minimum l
l MPCHLL Maximum Primary Containment Water l
Level Limit i
I r
mR M1111 roentgen /M1111 rem (as j
appropriate to the context and the l
units of associated instrumentation)
MSIV Main Steam Isciation Valve l
l N/A Not applicable i
I NPSH Net positive suction head
'NW North Hest I
I 4
PCPL I
~
Primary Containment Pressure Limit l
psig Pounds per square inch (gauge)
I I
PSP Pressure Suppression Pressure u
I I
i RB Reactor Building I
I RBCCH Reactor Building Closed Cooling Mater i
I i
RCIC Reactor Core Isolation Cooling l
I
^
)
RHR Residual Heat Reroyal 1
I Page 35 of 35
Table 3: Standard Acronyms and Abbreviations (Continued)
Abbreviation titinjng i
I RPM Revolutions per minute 1
I RPV Reactor Pressure Vessel l
I RWCU Reactor Mater Cleanup I
I SBGT Standby Gas Treatment l
I SBLC Standby Liquid Control l
I SE South East I
I SRVTPLL SRV Tail Pipe Level Limit I
l SSH Salt Service Hater SH South Hest I
I TAF Top of the active fuel I
I TBCCH Turbine Building Closed l
Cooling Hater
[
l TIP Transverse In-Core Frobe l
Ampersand ("And")
I I
Feet Inches l____________________ Percent
___________________l 1
l Prc:. 1.3.4-10 Rev. 2 Pap 36 of 36 i
~ ~~ ~'~~
_