ML20151C811
| ML20151C811 | |
| Person / Time | |
|---|---|
| Site: | Pilgrim |
| Issue date: | 04/06/1988 |
| From: | BOSTON EDISON CO. |
| To: | |
| Shared Package | |
| ML20151C809 | List: |
| References | |
| 1.3.4-10, NUDOCS 8804130194 | |
| Download: ML20151C811 (37) | |
Text
. _ _ _ _ _ _ _ _
BOSTON EDISON PILGRIM NUCLEAR POWER STATION Procedure 1.3.4-10 HRITERS' GUIDE FOR EMERGENCY OPERATING PROCEDURES I
J Approved
>@dswAru Y//M Quality Assurance Manager
/Date Approved M tP
+
Station Dire 6t6r
'/Date
- Un irQRsAlluis
-e m r
-0M 8804130194 880406 Proc. 1.3.4-10 Rev. 3
' DR ADOCK 0500 3
Page 1 of 37 h
Table of Contents Section EA99 I.
INTRODUCTION......................
5 A.
Purpose.....................
5 B.
Scope......................
5 C.
Use of Examples.................
5 II.
PROCEDURE IDENTIFICATION 4
A.
Proc. dure Numbering and Title..........
4 B.
Procedure Title Block..............
6 C.
Revision Identification.............
7 III.
PROCEDURE FORMAT..................
7 A.
Flowchart Elements 7
B.
Step Numbering 19 C.
Listed Items 20 D.
Use of Emphasis Techniques 21 E.
Procedure layout and Associated Conventions...
22 F.
Instructions for Printing, Copying and Storage.....................
25 IV.
PROCEDURE CONTENT
..................25 A.
Level of Detail.................
25 B.
Wri ti ng Styl e..................
26 C.
Cautions and Notes 26 D.
Branching Instructions and Cross-References...
27 E.
Component Identification 29 F.
Spelling, Grammar, and Punctuation 30 G.
Nomenclature, Vocabulary, and Abbreviation 30 H.
Numerical Values 31 t
h Oli iiIdIiniriii()II Proc. 1.3.4-10 Rev. 3 Page 2 of 37 l
hN
Table of Contents (Continued)
List of Examples Number Titie Eage 1.
E0P title 5
2.
E0P title block
.6 3.
Entry Conditions................
7 4.
Entry Point 8
5.
Concurrent execution statement (with Section and path designators.......
.8 6.
Instructional step...............
9 7.
Individual decision 10 8.
"Yes/No" decision diamond with an instructional step in one of the response paths......................
10 9.
Conditional Statement 11 10.
Use of the word "UNTIL" 11 11.
Use of the word "EXCEPT"............
11 12.
Use of the word "BEFORE"............
12 13.
Continuation Conditions.............
13 14.
Hold point...................
13
)
15.
Override statement...............
14 16.
Exit statement.................
14 17.
Supplemental Information............
15 18.
Caution 16 19.
Figure.....................
17 20.
Table 19 21.
Step numbering.................
20
\\
I UU II I k)1 g O/;ri l l(l ji Proc. 1.3.4-10 Rev. 3
. ;i s
- i i L }t Page 3 of 37
_ _. ~
~
. _. _... _. m. _. _..
I Table of Contents (Continued) r F
List of Examples i
l Number Tit 1e East l
l 22.
Listed items..................
20 I
l 23.
Page layout 24 l
t i
i 24.
Intra-procedure branching 29 i
i f
25.
Component Location 30 I
i l
I i
f i
P i
1 I
i i
i i
t a
]
l 9
i, f
I j
fQf(
lli; ! I l s t r i ri i l il l't i
i
-i, Proc. 1.3.4-10 Rev. 3 L__ _ __
(' i i i 4"
p,g, 4 of 37 i
9 1
l 1
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.
kone This Hriters' Guide adiresses the specifics of procedure identification, format, and content.
The guidance provided herein is applicable to the init'.al preparation and subsequent revisions of all PNPS E0Ps.
TMs document supplements existing BECo and PNPS 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.
ERQCIDURE IDENTIFICATION Each E0P shall be clearly and uniquely identified.
Identification shall consist of the procedure number, title, and revision number as described below.
A.
Procedure Numberino and Title 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)
E O P-01 RPV CONTROL
/\\
l
<,_,:,;i t.;
Ci d g {,'
Proc. 1.3.4-10 Rev. 3 E
Page 5 of 37
n 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 Approved:
QAMana;pr
/ Date Approved:
Operatons Secibn Manager
/ Da'e Approved:
Nuclear Operatons Manager
/ Da'e Effective Date:
Procedure Tale RPV CONTROL Proceduro Number Revision 1
E O P-01 0
)
I d !M Proc. 1,3.4-10 Rev. 3 l t~j j g
- ,s, is,,iew4 Page 6 of 31 C [ \\'
(
i
C.
Revision Identification 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.
i III.
PROCEDURE FORMAT The E0Ps shall be structured as flowcharts and formatted in accordance with the conventions detailed below.
Unless otherwise specified, directional arrows Intering and exiting flowchart elements shall be positioned alor,V tha element's vertical axis.
A.
Flowchart Elements 1.
Entry conditions shall be located at the top (i.e., beginning) of the procedure, enclosed in a i.eavy-bord 9 red rectangle with rounded corners (Example 3).
The pararaeters and the tssociat'id values or conditions shall be presented i a tabulai fornet. Variances are permitted where a tabular p6sentetton of eltes/ conditions may be confusing.
Example 3:
(Entry Conditionsi SMYRi CONDITIONS P AR AME1 ER CONDITION RPV water level Beltw @n.
RPV pressure
- Abow inSJ psig Drywell pressure
.bove 2.5 prig
_s.
Both of the following conditons exist; o A scram is required o Reactor power is above 3*/. or cannot be determined 1
V 1h h l\\ hi l
\\ {l i !P j
l i
Prod. 1.3.4-10 Rev. 3 Page 7 of 37 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 Point)
START U
2.
Concurrent execution statements shall be enclosed within a shaded elongated rectangle (Example 5).
The instruction directing concurrent performance of multiple sections or steps of a procedur) 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 and appropriately spaced.
Example 5:
(Concurrent Execution Statement) o I
' Ju...na wnuu nev ie, Lei. RPV preuvre and toad $r hwer concurentty RPV WATER LEVELy O RPV RESSuRE R CToR POWERi u
u y
3.
Section designators shall be p..nted in boldfaced upperv.se letters centered within a shaded trapezoid.
This element shall only be usei in conjunction with a concurrent execution element (Example S).
I V,.*
[1) h, I I'd r i n g r/ i n i i
?
Proc. 1.3.4-10 Rev. 3 y,_ bp' Lj' Page 8 of 37 f
A.
Flowchart Elements (continued) 4.
Instructional steos shall be formatted as complete sentences and enclosed in rectangles (Example 6).
Example 6:
(Instructional Step)
U Termbate dywen spays.
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) if 4
Has Mbeen determined that the reador yn wW rema:n shudown under alt mndabns without boren
?
No if 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 application should be maintained, a.
A "Yes/No" decision diamond (as described in Section III.A.5) with one of the response paths containing an instructional step (Example 8).
h
\\,
I O '
h f h Page 9 of 37 t___
= = -
A.
Flowchart Elements (continued)
Example 8:
(Yes/No" Decision Diamond with an Instructional Step in One of the Response Paths) f Has ARI been Yes initiated
?
No U
Depress both 'ATWS* pushbuttons.
V 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 presented in a format which clearly distinguishes between conditions and actions. Highlighted logic terms shall be used to emphasize distinction.
The following format conventions shall apply:
a.
The conditional part of the instruction shall be stated first, followed by the contingent action (Example 9).
This formatting requirement does not apply to conditional clauses that begin with "UNTIL" (see Part c below) or "EXCEPT" (See Part d below).
b.
Logic terms shall be printed in uppercase letters physically separated from the remainder of their respective clauses (Example 9).
)
li f i/ f i fy;ri i i d [ h Proc. 1.3.4-10 Rev. 3 CIV LIc Page 10 of 37 L__ __ _.
1
A.
Flowchart Elements (continued) 7.
Conditional statements (continued)
Exan.ple 9:
(Conditional Statement)
J U
THEN Open SRVs in tho ;olbwing SRVs are used to stabilize RPV sequence,if possible: B, C, D, A.
pressure A
SRVs are used to stabilize RPV
- pressure, AND k
Place all SRV control swaches The continuous SRV pneumatic in the ' AUTO' position.
suppY (Narogen and instrument Air)is or becomes unavailable, U
c.
When a prescribed action is to be performed until certain specified conditions occur, the conditions shall be prefaced 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")
U Manuatty open all SRVs UNTIL RPV pressure drops below 940 ps'g.
r U
d.
When a prescribed action is to be performed with certain 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.
.- idd l"hj(I,';Ai I $l>,
Proc. 1.3.4-10 Rev. 3 Page 11 of 37 g 7
A.
Flowchart Elements (continued) 7.
Conditional statements (continued)
Example 11:
(Use of the word "EXCEPT")
U Terminate injecton into the RPV from sources external to the primary containment EXCEPT from boron injection systems, CRD, and those systems necessary to assure adequate core cooling.
e.
When a prescribed action may be performed any time before a specified :ondition occurs, the condition shall be prefaced by the word "BEFORE" printed in boldfaced uppercase letters.
"BEFORE" shall be separated from the text which defines the conditioit and formatted as shown (Example 12).
I Example 12:
(Use of the word "BEFORE")
U Operate all available Suppression Pool Cooling using onY those RHR pumps not required to assure adequate core cooling by continuous operation in the LPCI mode.
BEFORE Torus water temperature reaches the BitT (Figure 3.2),
Enter EOP-01, *RPV Control,' and execute EOP 01 cor:couentY vath this pre ur;w.
U 1
f.
The intermixing of clauses beginning with "and" with those j
beginning with "or" within an individual step or decision should be avoided whenever possible.
If tise of an "and/or" 4"
logic structure is required, a decision table, an
]
appropriately structu:<d series of connected decision diamonds, or a acceptable alternate format shall be used to clearly depict the relationship between the conditional clauses.
b'ON llMI Oti!b;n j I t!!
Proc. 1.3.4-10 Rev. 3 i
Page 12 of 37 bm.--
hy..
[
[]
_i
A.
Flowchart Elements (continued) 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 "WHEN" printed 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 flowchart element.-
Example 13:
(Continuation Conditions)
If Maintain RPV water level between 126.3 in. (TAF) and +48 in, with one or more of the Group C RPV Injection Systems.
WHEN. 371 lbs of boron have WHEN..RPV water level cannot been injected into the be maintained above RPV.
126.3 in. (TAF),
if If 9.
Hold coints shall be formatted as instructions beginning with "HAIT UNTIL..." enclosed in octagons (Example 14).
The words "HAIT UNTIL" shall be printed in uppercase lette"s.
Example 14:
(Hold point)
If WAIT UNTilany of the following conditions exist:
o Allcontrol rods are inserted to or beyond positen 00 o it has been determined that the reactor will remain shutdown under all conddions without boron o The reactor is shutdown and no boron has been injected into the RPV o 539 lbs of boron have been injected into the RPV l
l if Oli I19 i i) i n, o ! !(;si Proc. 1.3.4-10 Rev. 3 Page 13 of 37 b,
)
h i
A.
Flowchart Elements (continued)
- 10. Override statements are those conditional instructions which apply while executing one or more steps.
Override statements shall be formatted as decision tables enclosed in shaded heavy bordered rectangles (Example 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 applies.
(Extension lines need not be used where an override statement applies to an entire procedure.)
Example 15:
(Override Statement)
I f f
tp THEN The offsite radcactivity isolate the primary release rate is expected containment vent to reach or reaches the and purge, site retease rate LCO
]
V J
L 11.
Procedure Exit statements and end coints 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)
I f r
Exit this procedure and en'er the RPV i
Pressure secten of EOP 01,'RPV Control.'
c Proc. 1.3.4-10 Rev. 3 j V iT lii i
Page 14 of 37 Lm.___
h [ ( L ),,
A.
Flowchart Elements (continued) 12.
Sucolemental 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 (Example 17).
Supplemental information is information which enhances the operators ability to perform an action statement but is either to 3
bulky to be placed in the flowpath as a note or the information is referenced from several locations within a flowpath.
Example 17:
(Supplemental Information)
U l RPV DEPRESSUR12ATION P/ THS 9l Rapidly depressurize the RPV, defeating isolation interlocks if necessary, using one or rnore of the RPV Depressurization
.4 o Main turbine bypass valves Paths. (Refer to Procedure 5.3.24 l o Main stearn Ene drains I
' Alternate Methods for Venting and a
Depressurizing the RPV Under Emergency
, o HPCI steam Ene l
Conditions." and Procedure 5.3.21, l o RCIC steam Ene i
- Bypassing Selected interlocks.')
'..o RPV head wnt
................i U
13.
Notes shall be printed in italics and placed within the respective flowchart element, located immediately preceding or following the associated text. Notes which simply provide information which enhances the operators ability to perform an action shall be located following the action text.
Notes should contain only one topic.
The word "NOTE" printed in uppercase letters and 3-punctuated with a colon shall preface the text of the note.
Notes shall be short so as not to detract the operator from the action flowpath.
- 14. Cautions shall be numbered consistent with the numbering scheme 1
employed in the Plant-Specific Technical Guidelines.
The i
applicability of a caution at a point in a procedure shall be indicated by a circle with a bleck background enclosing the caution number (Example 18;.
The full text of each referenceJ i
caution shall be enclosed in a rectangle and arranged around the periphery of the flowchart in numerical sequence, located to the left or above any figures present (Refer to Section III.E.6).
The 3
word CAUTIONS" shall be located directly above the cautions which apply to a given flowpath and shall be underlined in upper case, boldfaced print.
(Refer to III.E.6).
y-LM
/
I ):[ br!
- i 1
- 4; L.
L Proc. 1.3.4 10 Rev. 3 Page 15 of 37
A.
Flocchart Elements (continued)
Example 18:
(Caution) g A rapid increase in injecten into the RPV rnay induce a large power excursion and result in substantial core damage.
15.
Fiaures 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 the abbreviation "No." shall not be used.
Figure references shall be enclosed within parentheses.
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 figure.
c.
Axes of graphs shall be 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 shall be delineated through use of cross-hatching or background shading, f.
Figures shall contain only information ralevant to the E0P.
3
, y.
hI! I:,4 Proc. 1.3.4-10 Rev. 3 I
L
,a Page 16 of 37 k
C i
i
Example 19:
(Figure) i lf Terminate all injedion into the RPV and reduce RPV water level.
WHEN.. RPV water level VMEN injectionintothe RPV indication is restored, has been terminated and prevented for the MCUTL (Figure 6.2).
If m
FIGURE 6.2 MCUTL (MAXIMUM CORE UNCOVERY TIME LIMIT) 20 i
16-g 5
I G
.E.14 -
....:...j,. i. i.
g k
H C 12-
. " :" ": ".:. ") :. : ".
y 8
5 to-
.......!..... i....i...!...!. i. i. i.
w
.. :........ ;. :..:........... >..... :.... :......y. :. g..;
8-6-
~' ' '. ' ': '.' : ':.:. ' ' " ' : " ' ::. ".: ".:: '::. : ::. ~:.
4
-iiiiii i
i i iiiii i
i i
1 to 100 TIME AFTER REACTOR SHUTDOWN (hr) l
~Q(1 k l4 i I ls!/td iiil'<
i Proc. 1.3.4-10 Rev. 3 I
Page 17 of 37 L
s i
I
~
A.
Flowchart Elements (continued) 16.
Tables shall be used to effectively organize, correlate, or subdivide lists of systems, values, sensors, or other data (Example 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:
a.
All text and graphics should be clear, simple, and easily readable.
b.
Table titles shall be printed in boldfaced uppercase letters and, together with the table number, centered above the table. Table titles, numerical units and gradations shall y
correspond to those of associated control room instruments as applicable, c.
A border shall enclose each table.
d.
A heading 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.
e.
A double horizontal line shall be placed below the column 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 i
readability across the entries, h.
Tables shall contain only information relevant to the E0P.
31 l
1 L U i1 lis:
' i s iv i ri
's-Proc. 1.3.4-10 Rev. 3 L
Page is of 37
<4
A.
Flowchart Elements (continued)
Example 20:
(Table)
IF 4
WAIT UNTIL the water levelin the reactor building floor drain sump or an area is above the maximum normaloperating value (Table 4.1).
If TABLE 4.1 SECONDARY CONTAINMENT SUMP / AREA MAXIMUM WATER LEVELS i
MAX NORMAL MAX SAFE OPERATING OPERATING SUMP / AREA VALUE VALUE (Inches above floor)
(Inches above floor)
SUMP 1 inch on HPCIpump Reactor building floor drain room floor N 'A i
AREA N. W. quadrant 1
6 S. E. quadrant 1
6
]
HPCi compartment 1
6 S. W. quadrant 1
6 CRD quadrant 1
6 B.
Sten Numbering Only those operator actions that must be executed sequentially and that j
are presented within the confines of one flowchart element shall have designated step numbers.
Such steps shall be assigned sequential i
1 arabic numbers (Example 21).
h(1ij j H T ! I d 6 b ri i !-
Proc. 1.3.4-10 Rev. 3 i
4 i
Page 19 of 37
[
i
Example 21:
(Step numbering)
If
- 1. Shut down the reactor IF recirulation pumps and drywo!!
Torus water levelis below 183 in, cooling fans.
AND WEL
- 2. Initiate drywell sprays using Drywell pressure and temperature ony those RHR pumps not are below the DSil(Figure 3.1) required to assure adequate o a n o th Cl WHEN.. drywell temperature cannot be maintained below 281'F.
If C.
Listed Items Hultiple items (systems, plant conditions, etc.) for which 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 the immediately preceding text (Example 22). Variances to this convention are permitted (Refer *to Example 14) where listed items appear in elements whose shape necessitates a centered text format (i.e., octagons or diamonds).
Example 22:
(Listed Items)
I i
If initiate each of the following which should
{
have initiated but did not:
o isolation o ECCS o Emergencyd;eselgenerator if i
j
!ei li\\i i!'-
Proc. 1.3.4-10 Rev. 3 L],'d f \\;
Page 20 of 37
.\\ u !
L ___.
I D.
Use of Emohasis Techniaues Boldfaced print, uppercase letters, italics, and underlines shall be used to emphasize portions of a procedure consistent with the following conventions:
1.
Boldfaced print shall be used in the following applications:
a.
Flowchart titles b.
The words "ENTRY CONDITIONS" and the column headings within this flowchart element c.
The word "START" at procedure entry points d.
Section/designators (e.g., "RPV WATER LEVEL")
e.
Figure and Table labels f.
Headings and logic terms used in flowchart elements having tabular formats g.
The word "BEFORE" (Refer to Paragraph III.A.7.e) h.
The procedure title, number, and revision number within title blocks Where boldfaced print is used, characters shall be of a slightly l
larger size than that normally used for the standard text of flowchart elements.
I 2.
Uppercase letters (all capital letters) shall be used in the
' 3 following applications:
e a.
Flowchart titles i
b.
The words "ENTRY CONDITIONS" and the column headings within l
this flowchart element c.
The word "START" at procedure entry points d.
Section designators (e.g., "RPV WATER LEVEL")
e.
Logic terms f.
Figure titles and axis labels (except associated enginecring units) g.
Titles and column and row headings in tables (except associated engineering units) h.
The word "NOTE" when prefacing the respective text i.
Abbreviations and acronyms that are printed in upper case 3
letters in table 3.
I Proc. 1.3.4-10 Rev. 3 U g j[j[.} i!'/ir' jig l43 I
\\
Page 21 of 37 b_ _ _
.]
3 I
I
(
),6 D.
Use of Emohasis Technioues (continued) i j.
Text of instructional steps which,m ause control ofV parameter to transfer from one procedure (or section if'a procedure) to another (e.g., "Primary Consainment F)ooding is Required")
i j
k.
Identificationofas-labeledcompo/sentdesignatinus, control switch positions, and annunciator efigruvt.1gs 1.
The procedure title, number, revision number and plant name within title blocks m.
The word "BEFORE" (Refer 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 This enhancement shall not be used if itl/
Is deemed to engravings.
detract from the readability of the flowchart.'
e E.
Procedure layout and Associated Conventions f
(Example 23)
/
1.
More than one pro:edure may be placed on a page (page size restrictions permitting).
2.
Maximum page size shall be restricted to that which can be j
accommodated by reprographics capabilities.
3.
Pagebreaksinaprocedurearenotallowed/.
4.
Aborderapproximately1/2inchfromthe[dgeofeachsideofthe page shall be used to enclose the proced6te(s) on the page.
A line of medium thickness shall be used to form this border.
5.
The procedure title block (s) shall be located in.the lower right corner (s) of the bordered area (s) surrounding the E0P(s)
(Example 23).
5 i
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).
l 7.
Solid lines ending in arrows shall be used to connect flowchart elements and thereby indicate flowpaths through the procedure.
Progression through a procedure shall generally be down and to the i
l
- tight, i
~
i 8.
Procedure titles and flowchart elements (including connecting lines and extension lines emanating from override statements) l shall be located no closer than 1/2 inch to the page border.
1 C'
4 0 Rev. 3
~ V ii il4 F ! i ni ty;n i !(/!i 1
L
,2 bm d
l
E.
Procedure Layout and Associated Conventions (continued) 9.
A minimum spacing of 3/8 inch shall be maintained betecen
-flowchart elements.
l t
- 10. A minimum spacing of 3/8 inch shall be maintained between parallel lines connecting flowchart elements, and between extension lines emanating from override statements.
- 11. Cross-over of lines connecting flowchart elements shall be minimized. Variances to this convention are permitted for dashed lines connecting supplemental information and dotted intra-procedure branch lines if required for spacial considerations.
,,l 1
/
4 F
t I
i
'1 l
1 W
i i
I Proc. 1.3.4-10 Rev. 3
'- () y ljN7iId ihrt!'il,
.Page 23 of 37 t
{-
E y-4
.w.
4
=_-
m DC w-p f
CAUTIONS CAUTIONS
-g s
I I
w g
+
e 8
G g
g
- e I
I g
g g
8 I
g g
W e'
B 8
^
y 7-i t
I g
m X___.
~s PROCEDlfhE 7
i PROCEDURE i
- ~
e s
8 I
3 g-
,19 e
g i
a-i s
5 I
g p
I I
g I
I L
8 8
g g.-
i i
i I
I 3
i I
I g
s
'_____________________.g s
- u o -,
mv T: 'g 8 FIGURES ANDTABLES FIGURES AND TABLES N.
ro
(
u-Ob
~'
%- 4 WI
~
u-TITLE TITLE BLOCK BLOCK E
c.
(X)
(Y) s-M h
\\
k m.
d
_m
F.
Instructions for Printina. Cooyina. and Storage j
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.
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 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.
2.
Excessive detail should be avoided.
Expected results of routine actions need not be stated.
3.
Hhere 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 information shall be provided:
- System response times
- Equipment limitations hun j iii
'ii n,. >
i
}' k j' Proc. 1.3.4-10 Rev. 3 Page 25 of 37 i'
5
A.
Level of Deta:1 (continued)
- 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 with an implicit subject.
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.
Limits 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 used to identify a potential hazard to personnel or j
equipment.
Notes shall be used to provide supplementary information related to the performance of a particular action.
Use of cautions and notes should be minimized.
Neither shall be contain instructional steps.
I N
Oi i
3 ei Proc. 1.3.4-10 Rev. 3 i
Page 26 of 37
{ g ;,. _
i s
m i
R 0.
Branchina Instructions and Cross-References Branching instructions shall be used to direct the operator to transfer i
from one procedure (or section of a procedure) to anotner, or to i
execute an additional procedure concurrently with 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 detailed below, as appropriate.
Hithin 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 Water Level section of the RPV Control Procedure).
Branching instruction formats:
1.
Exit this procedure and enter (Procedure X],
"[ Procedure Title]".
Specifies that the operator shall exit the procedure containing 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 litle]".
Specifies that the operator shall exit the section of the procedure containing the instruction and enter the identified procedure; execution of other sections of the procedure shall continue as appropriate (i.e., no exit is made from other sections of the procedure containing the instruction).
3.
Exit this procedure and enter the [ Parameter) section of E0P-[X],
"[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 I
identified procedure concurrently with the procedure containing the it.struction.
- <- c
-' Q h i N i'
3 Proc. 1.3.4-10 Rev. 3 Page 27 of 37
}
1
D.
Branchina Instructions and Cross-References (continued) 6.
Continue at (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 "forward" in an E0P.
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 E0P.
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.
)
E0P 07 )
The procedure number within the symbol shall be that of the procedure containing the exit branch in:truction.
For branching formats 6 and 7:
The symbol "[Y]" shall be a capital letter placed within a circle as shown below:
This symbol shall be repeated at the location where procedure execution 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 proper execution of the procedure (Example 24).
Forward and backward branching within a procedure should be minimized.
l iliV;a
' p p)
T'I
}
Proc. 1.3.4-10 Rev. 3 Page 28 of 37
{,
D.
Branchina Instructions ind Cross-References (continued)
Example 24:
(Intra-Procedure Branching)
U IF THEN
)
b p
( RPV pressure drops below 125 psig Continue at h r.......................j Une up for iniedion, star 1 pumps, and irrespective of pump NPSH and vortea Limitt. increase injection flow to the y
rnaximum wth al Grow A RPV Injection Systems and Subsystems.
WHEN.. RPV water level drops to 126.3 in. (TAF),
U 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' aspects 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 number; identification of the title is not required.
E.
Component Identification Components shall be clearly and completely identified.
The following conventions shall apply:
1.
If the procedure refers to a specific control switch or instrument, the as-labeled designation shall be used, typed in uppercase letters and enclosed within quotation marks.
Otherwise, common-usage designations shall be used.
Proc. 1.3.4-10 Rev. 3 Vb I
Page 29 of 37 Iggg
e E.
Comoonent Identification (continued) 2.
System titles shall be capitalized.
The word "system" need not be included in the title.
3.
Component locations shall be specified if. the components are infrequently used or if there would otherwise be a possibility of confusion.
The component identification number shall be listed followed by a note which provides a description of the component location.
Examole 25: (Component Location)
Open isolation valves HO-177 and H0-178.
3 EIE These valves are located outside the north wall of the Reactor Building in the condensate storage area.
F.
Soellina. Grammar. and Punctuation Spelling, grammar, and punctuation shall be consistent with standard rules and modern usage.
The following conventions shall also apply:
1.
Excessive use of commas should be avoided.
Commas are not necessary in elements using a columnar format (e.g., override statements).
2.
Use of definite articles, pronouns, and adverbs should be minimized.
Personal pronouns shall not be used.
G.
Nomenclature. Vocabularv. and Abbreviations Words ano abbreviations shall have consistent meanings. The following conventions shall apply:
1.
Simple, common words shall be used.
2.
Words shall have specific, precise meanings.
Use of ambiguous terms should be avoided.
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.
5.
Use of acronyms and abbreviations should be minimized and only those immediately recognizable shall be used.
(A list of acceptable acronyms and abbreviations is provided in Table 3.)
j fVil-
) jiI,/11IYin i ii> c.
Proc. 1.3.4-10 Rev. 3 2. v; s
Page 30 of 37 bau l
H.
Numerical Values Limits and values of operating parameters shall be expressed quantitatively.
The following conventions shall apply:
1.
Arabic numerals shall be used.
2.
Parameter values shall include the units of measurement.
Unitt 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.
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.
5 in.).
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).
ft h h !' i j t i n i n Proc. 1.3.4-10 Rev. 3 h
- p I, Page 31 of 37 L.
Table 1: Application of Logic Terms l
Logic Term Definition l
I I
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 j
specified condition.
Does not imply or l
require any specific margin be observed l
when a step states that action be taken l
"before" reaching a limit or value.
l 1
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 l
existence of the identified condition (s).
l If the identified conditions do not exist, l
the prescribed action is not to be taken l
and execution of operator actions proceeds l
to the following step.
l l
OR Designates alternative combinations 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.
HAIT UNTIL Indicates that execution of subsequent l
operator actions is not permitted until l
the identified condition exists.
l l
HHEN Indicates that upon occurrence or existence j
of the identified condition (s), execution of l
the procedure should immediately proceed to l
the next identified flowchart element.
l l
UNTIL Indicates that the associated action is to l
be terminated when the specified condition l
occurs.
l l______________________________________l Proc. 1.3.4-10 Rev. 3 (J m '
Page 32 of 37 lj U jY
/!)M I d iilViril ! U :i i
~
Table 2: Standard Nomenclature and Definitions Available: The state or condition of being ready and able to j
be used (placed into operation) to accomplish the stated l
(or implied) action or function.
I l
Cannot be determined: The value or status of the specified l
parameter relative to the procedure action level cannot l
be ascertained using available indications.
I l
Cannot be maintained: The value of the specified parameter l
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 l
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.
l l
Close:
To position a valve or damper so as to prevent flow l
of the process fluid.
I I
Confi rm' available indications and, as appropriate.
l r! t observation to establish that the specified l
$ st occurred, conditions are as stated, etc.
l Includes an implied requirement to take corrective action l
if the identified conditions do not exist.
l l
Control: Take action, as necessary, to maintain the value of l
the specified parameter within applicable limits.
l l
Enter: Commence performing, in sequence, the steps of the l
identified procedure.
l l
Execute: Perform the actions prescribed in the identified l
step.
l l
Exit: Cease performing the steps of the identified procedure.
l 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 alternate l
or backup power supplies, enter remote areas to manually l
operate valves, etc., are not intended by this term.
l l
l Proc. 1.3.4-10 Rev. 3 L U f; e,,
Page 33 of 37 A
Table 2:
Standard Nomenclature and Definitions (Continued)
Line up:
Establish the prerequisites necessary for system 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.
l l
Monitor: Observe and evaluate at a frequency sufficient to remain j
apprised of the value, trend, and rate of change of the j
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.
Purge:
Force flow through an enclosed volume.
Includes l
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 applicable limits.
l l
Set: To position a control to a specified scale value.
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 accommodated 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
Terminate: 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 employed.
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 m~ g j h r o m n 1 c,-
Proc. 1.3.4-10 Rev. 3
{
{[y,j Page 34 of 37
Table 3:
Standard Acronyms and Abbreviations Abbreviation Meanina I
l ADS Automatic Depressurization System I
I APRM Average Power Range Monitor I
I ARI Alternate Rod Insertion i
I BIIT Boron Injection Initiation Temp.
I I
CAC Containment Atmospheric Control I
l CAD Containment Atmospheric Dilution I
i CPS Counts Per Second CRD Control Rod Drive l
I CS Core Spray I
I ECCS Emergency Core Cooling Systems l
CST Condensate Storage Tank Demin Demineralizer i
l DSIL Drywell Spray Initiation Limit I
I DH Drywell I
I 0F Degrees Fahrenheit i
I ft Feet I
I FH Feedwater GPM Gallons Per Minute l
I H&V Hedting and Ventilation I
I HCLL Heat Capacity Level Limit l
l HCTL Heat Capacity Temperature Limit i
I HCU Hydraulic control unit i
I HPCI High Pressure Coolant Injection l
l hr Hour I
I HX Heat exchanger I
I in.
Inch l 7 Q j1 ijji'i!tibin I
s
azw.
Page 35 of 37 m.
Table 3:
Standard Acronyms and Abbreviations (Continued)
Abbreviation Heanina l
I ibs Pounds l
I LCO Limiting Condition for Operation l
I LZ Level Indicator LOCA Loss of Coolant Accident i
I LPCI Low Pressure Coolant Injection I
l LR Level Recorder I
I HARFP Hinimum Alternate RPV Flooding l
Pressure l
l MCFI Minimum Core Flooding Interval l
l MCUTL Haximum Core Uncovery Time Limit l
l min Minimum l
l HPCHLL Haximum Primary Containment Water l
Level Limit i
I mR Hilliroentgen/Hillirem (as l
appropriate to the context and the l
units of associated instrumentation)
MSIV Main Steam Isolation Valve l
l N/A Not applicable I
I NPSH Net positive suction head i
I NH North West I
I PASS Post Accident Sample System 3
I I
PCPL Primary Containment Pressure Limit l
I psig Pounds per square inch (gauge) 1 l
PSP Pressure Suppression Pressure 1
1 I
RB Reactor Building I
I RBCCH Reactor Building Closed Cooling Hater I
I RCIC Reactor Core Isolation Cooling I
l
-e ti,
_ _ ;gt _d@ ! hi m M i l o 'c e
Proc. 1.3.4-10 Rev. 3
[;;
)
Page 36 of 37
.y Table 3:
Standard Acronyms and Abbreviations (Continued)
Abbreviation Meanina l
I RPM Revolutions per minute l
I RPV Reactor Pressure Vessel I
I RHCU Reactor Hater Cleanup I
I SBGT Standby Gas Treatment I
I SBLC Standby Liquid Control I
l-SE South East i
l SRVTPLL SRV Tail Pipe Level Limit I
I SSH Salt Service Hater I
I SH South Hest i
I TAF Top of the active fuel l
I TBCCH Turbine Building Closed I
Cooling Hater.
l l
TIP Transverse In-Core Probe l
Ampersand ("And")
Feet Inches Percent l_______________________________________l lb'id;
- i.
Page 37 of 37 Proc. 1.3.4-10 Rev. 3 s i \\' ' I: 3 ;V; i 5 i t;:,
i n
_.