ML20092H018
| ML20092H018 | |
| Person / Time | |
|---|---|
| Site: | Vogtle  |
| Issue date: | 07/05/1989 |
| From: | Swartzwelder T GEORGIA POWER CO. |
| To: | |
| Shared Package | |
| ML20092F288 | List:
|
| References | |
| CON-IIT05-131-90, CON-IIT5-131-90, RTR-NUREG-1410 VEGP-10011-C, NUDOCS 9202200426 | |
| Download: ML20092H018 (35) | |
Text
..
7;--
Vogtle Electric Generating Plant 10011-C p
g NUCLEAR OPERATIONS g;,,,,,n go.
o t.
v 13 yN Georgia Power e.."1 of as 7-5-89
""a
(~)
. m/
051'M o m
n OPERATIONS PROCEDURE PREPARATION AND REVIEW GUIDELINES 70R N70RMA~l0N ONLY 1,,
,y,,ogs This procedure is to provide guidance for preparing Operations Department procedures and reviewing plant procedures.
Topics are as contained in the following sections:
2.0 Operations Procedure Writer / Reviewer Qualifications 3.0 Procedure Writing Guide 4.0 Writing Technique 5.0 Reviews 2.0 OPERATIONS PROCEDURE WRITER / REVIEWER QUALIFICATIONS U
2.1 Operations Department pr' edure writers / reviewers must have a minimum of 5 yea?
af power plant experience.
A maximum of 4 years of r requirement may be fulfilled by related technical anc.<or academic training.
2.2 A Procedure Writer / Reviewer Qualification Checklist (Figure 1) shall be completed for each operations procedure writer / reviewer.
2.3,
Disposition of the completed checklist is as follows:
Original to Document Control for filing as a a.
permanent record, b.
Copy to the Superintendent, Nuclear Training for insertion in the individual's training record file.
(D
\\
9202200426 920116 PDR ADOCK 05000424 i
S PDR i
i
'03tc5A uc$m
~Tisiiion hot so g
r.
~-'
3 VEGP 10011-C 13 2 of J5 l
r I
30 PROCEDURE WRITING GUIDE
()
This section provides specific detailed guidance for writing and handling Operations Department p' Procedure rocedures.
The general Development" guidance contained in 00050-C,
, should be followed for all procedured except as modified in this section.
3.1 GENERAL a,
Unit Operating ?rocedures {UOP), System Operating Procedures ISOP), Operations Survo111ance Procedures (OSP), Forms / Data Sheets (F/DS) and Annunciator Rosponse Procedures (ARP) should follow this general guidance.
A separate procedure applies to the writing of Emergency Operationa Procedures (EOP) and Abnstmai Operat.4.ng Procedurer (AOP),
b.
Before starting to write a procedure, the writer i
chould determine if the document is needed.
He should determine if the instructions-are covered -
in another procedure, or if it should be a different t He should also determine, ype of procedure.for example, if just the lineup l
sufficient, or the SOP needs ao lineup, or what forms are needed.
3.1.1 Definitions i
a.
Status l
The status of a system may be secured, standby or i
i operating.
Each level is independent, and a system car. be brought to operating status without going through the standby status, b.
Secured The' condition of a system when it is incapable of operating.
Equipment is not necessarily isolated and ready for maintenance.
The equipuent breakers L
may be racked out, or the control suit:h may be 1
off.
If the system has an -automatic initiation i
the system is shut down and the automatic I
initiation is prevented, c.
Standby The condition of an operabiz system when it is ready to perform its intended function, O
i
_M' k
, ~..
- .._u gn_
f.- o -
h,.se, a
CEVILloN PAGF No.
'l VEGP 10011-C 13 3 of 35 d.
Opera ting
(_./
The condition of a system when it is actively performing its intended function.
^
3.1.2 Forma ts Formats should generally conform et 00050-C, " Procedure Development" guidance. Specific secte'ons to be used when writing a UOP, or S0P are set forth below.
Other types of procedures wf.11 vary from this format as described later.
Prepare preliminar,y drafts of orocedures in the satte format as thac desired for
' typing.
3.1.2.1 1.0 PURPOS_E Provide a clear, conctae statement of what the procedur6 is to accomplish.
If the INSTRUCTION section contains mere than three major objectives (e.g., Startup Of The XYZ System, Shifting High Pressure Pumps. Shutdown Of The High Pressure linit, Shutdown Of The XYZ System, Filling The EHC-Reservoir) list these objectives by sub-instruction title.
3.1.2.2 2.0 PRECAUTIONLAND LIMITATIONS O
This subt:oction should be divided into two sections as follows:
a.
Procautions Precautions are the cautionary notes that are intended to protect equiprent and personnel or to avoid an abnormal or emergency situation.
Precautions listed should apply to the entire procedure.
Place cautionary notes that apply to a portion of a procedure immediately L
preceding the step for which the applicable and on the same page,y are l
t.
u
r avsbua naut uo.
'l VEOP 10011-C 13 4 of 35 b.
1, imitations (n)
Thin section contains operating limite and Technical Specification limits that shall not be exceoded during the performance of the procedure.
Specify limitations on the parameters being controlled and appropriate corrective measures to retinn the parameter to normal control band, where applicable, in the Hr.in Body.
3.1.2.3 3.0 PREREQUISITES OR INITIAL _ CONDITIONS Prerequisites or initial conditions will identify those independent actions or procedurne which must be completed or those plant conditions which must exist prior to use.
Prerequisites or initial conditions ap111 cable only to certain sections of a procedure should be identified by preceding the prerequisite with a conditional statement.
(e.g.,
Prior to reaching 350'F, Prior to starting XYZ' fan, cha 'imrbine P) ant Cooling Water (IPUW) System shall be in operation.)
Prercouisir.os are needed to accomplish the following:
()N Establish valve and system alignments for the a.
'm syrtem under consideration, b.
Establish operating status of systems required to support the system under consideration, Establish portions of other procedures that c.
may be required for the syctem under consideration, d.
Establish the need for Control Room notificaticn nrior to commencing an evolution.
3,1,2,4 4.0 INSTRUCTION The main body of the procedure.
Centent is described separntely for UOPs, SOPS, ARPs and OSPs.
If an alternate train / component is being shown in parenthesis, a note should be placed following the Instruction section heading to inform the user.
()
v 703 6
" ~
paar uc'
'~~ " ~
VEGp 10011-C 13 5 of 35 3.1.2.5 5.0 _ REFERENCE
()
List reference documents that may help the user of the procedure to better understand the procedure.
An. example of the type documents to be included in this section ar,' a sogrested formet follows.
5.1 Applicable Technical Specifications or FSAR paragraphs 5.2 Any applicabic procedures used or referred to within the procedure (i.e., If you start a pump per its appropriate procedure, then that procedure should be referenced.)
5.3 P&ID's (applicable to the procedure) 5.4 Electrical Diagrams (applicable to the procedure) 5.5 Elementary Diagrams (app'ticable to the pcceedure) 5.6 Logic Diagrams (applicable to the procedure) 5.7 Technical Manuals 5.8 Other
()
3.1.2.6 List of Incomplete Items List 311 items within a procedure which are omitted or incomplete.
Place this list at the end of the procedure.
This requirement applies to UOPs, SOPS, F/DS, Lineups, OSPs and ARPs.
3.2 FORMS / DATA SHEETS (F/DS)
E 3.2.1 F/DS Cuidelines 3.2.1.1 Develop F/DS with the corresponding procedure, to haves A borderline all the way around the page with.the a.
text within the borderlinas, b.
Clear headings, Sufficient size to provide good readability, c.
d.
Adequate detail to prevent user error, 3.2.1.2 Horizontal or vertical format may be used depending upon page content and complexity.
In checklists, rounds sheets and forms, p*ocedures may be referenced O.
by number only, not followed by the title.
EM.
W wo h
.., ~... _, _
... ~.
pxay g
.3 VEGP 10011-C 13 6 of 35
.i e
e 3.2.2 Valve And Electrical Lineups (See Figure 2) 3. 2. l4.1 -
Lineups are written for normal operation.
Differences between the alignment for startup and the normal operating configprat. ion are shown by footnotes with a number in parentheaf a placed just to the left of the lineup column.
)
3.2.2.2 Handswitches will normally be listed on checklists in the SOP.
Air operated volves era included in alignments to verify that air is available.
3.2.2.3 The sequence number of the lineup is the same as tho associated SOP.
For example:
13405-1, "125V DC 1E Electrical Distribution System" would correspond with alignment 11405-1, "125V DC 1E Electrical Distribution System Alignment".
In some cases there may only be a lineup and no associated 50P.
3.2.2.4 Order components in accordance with the procedure application, equipment complexity, safety and the path an operator can take.
Minimize the potential for equipment damage during startup of a system or component by perforn.ing t.he valve or mechanical alignment to ensure flowpath prior to placing power to the component or its control circuitry, and vice versa for system or component shutdown.
3.2.2.5 Valves inaccessible due to location or plant conditions such as radiation levels are annotated as " inaccessible d te to (condition)".
3.2.2.6 Valves and breakers should be described as given on their tags:
a.
List valves by area and flowpath, b.
Breakers (1)
List each breaker by its engraved cabinot/ cubicle number and description, (e.g.
1BA0319, Bus 1BA03 MER INCM BRKR),
(2)
Prioritize switchgear s tarting with highest voltago.
3.2.2.7 If a revision changes a component's required condition, add an informal note to the a his attention to the change. pproving authority calling O
- ^ ^ ~
vniwow~ ~
'~.
.. a....
baht nol'"
T I'
VEGP 10011-C 13 7 of 35 k
3.3 UNIT OPERATING PROCEDURES (UDP)
()
3.3.1 UDP Numbering UCP's shall be numbered per 00050-C, " Procedure Development".
3.3.2 UDP Format UOP's should be written as common procedures, c.
b.
UOP format is as given in Sub-subsection 3.1.2, f
Instructional steps may have a sign off space in c.
the right hand margin to allow the user to systematically wor.< through the procedure, d.
UOP's may duplierte parts of other procedures by incorporating steps into the UOP that can be completed by operators in the Control Room.
Support requited outside of the Control Room or from any other functional group should be indicated b procedure, y reference to the applicable c.
Unit designators should be omitted when referencing or branching to unit specific g
procedures.
Common unit procedures will be referenced as XXXXX-C, f.
Unit designators should be omitted when identifying equipment or components unless the equipment or component numbers differ.between Unit 1 and Unit 2, (1)
The preferred methoda for distinguishing unit differences are illustrated below.
Multiple componenta - Table form EXAMPLE:
UNIT 1 UNIT 2 1-HV-XXXX 2 -HV-XXX*{
1-LV-XXXX 2-LV-XXXX l-1301-U4-XXX 2-1301-U4-XXX Single components referenced within a sentence EXAMPLE:
(
OPEN XXXX pump suction isolation valve UNIT la 1-HV-XXXX or UNIT 2:
2-HV-XXXX bdN
v
.-FetQihuvri6 es.s.
r aiv t t 'U 4
VCGP 10011-C 13 8 of 35 3.4 SYSTEM OPEEATING PROCEDURES (SOP),
3.4.1 SOP Numbering:
a.
SOPS are numbered per 00050-C, " Procedure Development",
b.
SOPS have separate Unit 1 and Unit 2 procedures if there is different equipment for each unit, They are common procedures if the equioment is c.
comunn, or shared, betweer. Unit 1 and 'Jnit 2, d.
If the system is a combination of shared and unit specific equipment, one procedure deals with the Unit 1 and Conmon parts of the system.
The other pracedure deals with the Unit 2 equipment.
3.4.2 SOP Format 3.4.2.1 In addition to guidance in Sub-subsectiv:- 3.1.2, the SOP format includes:
4.0 JNSTRUCTION This section contains the detailed instructions to operate the system.
The sections do not need to O
be in the order listed below but should include applicable steps.
Some format guidelines are:
Instructional steps are sequentially numbered a.
for major steos and alphabetically designated for lists within substeps, b.
Indent each subsection as in Figure 3, 00050-C, "Procedu.re Development Section headings have all capitals and c.
underlined, subsection headings al.1 capitals, and sub-subsection headings the first letter in each word capitalized.
Steps of a section
- 1. ave the first letter of the first word capitalized, d.
Start major logical breaka within the procedure at the top of a new page.
O
\\
l
VEGP 10011-C 13 9 of 33 3.4.2.2 S tar tup l
()
This section of the SOP provides detailed, step by step instructions for taking a system from a low status t
level (toward non-operating) to a higher status level (toward' operating).
This section should contain subsections that provide for each planned method of startup.
The sequence of the subsection should take the system from the second status, through standby, if applicable, to the operating status.
Title each subsection so the title indicates the nature of the evolution.
For exam "Startup to Standby",
"Startup to Full Operation"ple:
Certain systems may not have an overall startup but instead have startups of individual components.
- Also, individual com and shutdowns.ponents within a system may have startups
_ In such cases, prepare a subsection for each individual component startup.
Examples include startup of a demineralizer, a hydrogen recombiner, and a fun unit within a HVAC System.
3.4.2.3 System Operation This section contains the instructions for acceptable methods of system operation. Such instructions are i
O necessary when operational steps are anticipated.and such steps do not change the operational stntus of the system.
Such steps alter the operation but maintain the system in an operation status. Examples of such operations include shifting pumps, shifting suctions, shifting between normal power supplies, etc.
This section contains subsections for each type of operacion and provides for altering the operation in either direction.
For example, a subsection that shifts a suction from its normal source to an alternate source followed by a subsection that shifts the suction from the alternate source to the normal source.
t h
- O
Psucwv.s
..s e
,v,,
g VEGP 10011 -C 13 10 of 35 4-3.4.2 4 Shutdown
()
'this section of the SOP contains the instructions for I
taking a system from a higher status to a lower status, i
An appropriate to the system, subsections provide for automatic shutdown, full operation to standby, standby to full shutdown and manual shutdown from full operation.
An interface exista between SOPS and Emergency Operating Procedures with respect to shutdown following an automntic startup from standby.
The EOP may include instructions for securing operation of the system following automa tic s tartup. However, such instruction is typf cally 11mitad to a few steps to shut down the system.
For this reason, an SOP is needed for the shutdown from operation to standby.
This permits the EOP to deal solely with the plant emergency and allows use of the SOP for restoring the system to standby.
i For an SOP having individual component startup subsections, provide a corresponding component shutdown subsection.
3.4.2.5 Non Periodic Operation This section of the SCP provides detailed instruction O
on unusual or off-normal operations.
These operations do not fit the other sections of the SOP.
They may pertain to a method of operation other than the design functions of the system.
Examples of non Periodic Operations include filling the cooling tower basin, venting pumps, operating on the bypass, etc.
3.4.3 Checklists 3.4.3.1 Checklists are used to list and provide sign-off space for ' system handswitch alignment.
3.4.3.2 Where independent verification is required for more than a few valve
. sign-off spaces. positions, provide a checklist with 3.5 OPERATIONS SURVEILLANCF, PROCEDURE (OSP)
)
3.5.1 CSP Numbering OSP'a shall be numbered per 00050-C. " Procedure Development".
_sy--w-rw-wiv-
-e-eem--e-*---g-wasr
-w-
-mws'ww-t--,---Wrreg-&eim---we-imr ex--w-
rn
-a e&
-ywen-4 e em e
M
~
4 P
,---,9
- =-
mocr.our.E NQ.
r e.o dan n e I
VEGP 10011-C 13 11 of 35 3.5.2 OSP Fo rma t,
()
a.
Title The title of the procedure appears en Page 1, b.
Purpose (1)
State the purpose of the pr ocedure in a clear, unambiguous maaner.
The user should be able to determine the Intent of the procedure without reading the entire procedure, (2)
As appropriate, list the followieg information:
(a)
Identification of the component (s)/
system (s) that the surveillance inc lude s,
(b)
The frequency of the eurveillance, (c)
The Surveillance Requirements of the Technical Specffications that are implemented, if applicable,
(~J
'\\
(d)
The ASME Section XI requirements of the
(
Inservice Test Program that are to be satisfied by the OSP, if appifcable, c.
Applicability State the plant conditions or operational mode (s) which require the applicable systems / components to ha operable, d.
Precautions and Limitations (1)
Identify and warn the user of any personal safety nazards, radiation hazards, equipmenc operating problems, or effects on plant safety which might arise during the performance of the OSP, (2)
See also paragraph 3.1.2.2.
O l
mn L__
4,
~
.~
4 VEGP 10011-C 13 12 of 35 Prerequisites or Initial Conditions e.
()
~
Include those items to be satisfied prior to performance of the OSP. Each prerequisite or initial condition shall have a cign-off space.
These items may include:
(1)
Alignment / Operation of nppropriate systeme, subsystems, or components, (2)
Verification that certain conditions exist, including suitable or controlled environmental conditions, (3)
Verification that the proposed test does not affect other testa currently in progress or jeopardize plant operation, I
(4)
Authorization from the Shift Supervisor to perform the test, (5)
Adequate and appropriate special test equipment, including identification number, (6)
Communications established as required.
f._
Instructional Steps (1)
Structure the instructional section on two levela, ' heading which states the goal of a group of rocedural steps (" Isolating SI Pump 1A"), fol owed by a series of actico steps l
which carry out the goal.
Put the action steps in a logical order, grouped together by operations that can be performed at one
- location, (2)
Link important steps to other actions so that an omitted step will be immediately apparent l
to the user, l
/3)
When appropriate state the anticipated response und method of observation prior to the step which will cause the response, (4)
Addreas only one action per step when E
possible.
Clearly identify actions which I
L result in a system response.
If there is a delay, state the time until e response will be seen,
6AvC s,.A.;d hd. ~
EEISIO'fI ~
PAGE No" ^
~ ~ ~
^
l VEGP 10011-C 13 13 of 35 (5)
Placc warnings, cautiona., or notes
{]/
.immediately before the first applicable step.
Clearly identify them for the user, (6)
Steps may have a sign-off space in the ri ht F
maagin to allow the user to work through the procedure systematically and to locate his place within the procedure at any time, (7)
Address system, instrument channel, equipment and/or component restoration at completion of
- testing, g.
Acceptance Criteria (1)
State clearly and concisely the acceptablo criteria to be used to evaluate the results, (2)
Structure the acceptance criteria to address each component, syateu or train as applicable so that the procedure may be used to prove operability of individual components, ayatems or trains during non periodic testing, (3)
Use quantitatit'e accepte.nce criteria when possible.
Where it is not possible to quantify acceptance criteria, establish clear fs()
qualitative criteria, h.
Evaluation and Review (1)
Note results obtained through test performance, i.e., acceptance criteria met or not met.
(2)
Identify corrective actions taken, including any reports submitted, i.
References As described i Step 3.1.2.5.
-3.5.3 OSP Content L
a.
The objective of the procedure and method of l
implenentation should be clearly underctood by the l
writer before drafting begins.
Be aware of which Surveillance Requirement (s) of the Technical Specifications are to be implemented by the procedure.
Review for any ASME Section XI requirements of the Inservice Tert Program that are to be included, O
.e r
w-,
n,
,v-.
n
m;;n, g.;,f ~
-- " " *-]n msson
~
SuAN
(
VEGp 10011-C 13 14 of 35 b.
Take into accoun*; not only thp qualifications of e-s the intended user, but also any physical or (j
organizational constraints which may affect procedure performance, Use more dotati for procedures which are used less c.
frequently, d.
Consider the number of personnel required for the performance of the procedure, Prepare the procedure to ensure plant safety e.
remains unaffected during procedure performance, f.
Use NOTES or CAUTIONS prior to steps that will cause an ESFAS or RFS actuation to alert operator of that fact, g.
The procedure shall identify all Technical Specifications' Limiting Conditions for Operation applicable if a system and/or component is determined inoperable by the survaillance, h.
Unless otherwise required to satisfy a Technical Specification requirement, all OSPs shall be written to test one component / system train at a
- time, 1.
Blanks shall be rovided for dates, times and signatures of individuals performing the survefilance and performing the supervisory
- review, J.
A blank shall be providad for M&TE equipment
- number, k.
Indapendent verifications shall be provided for as required by 00308-C, " Independent Verification rolicy",
1.
Installation and removal of temporary jumpers and liftsd wires shall be documented including location, notification of the Shift Supervisor when installed / removed and independent verification per Step j above, Provisions for data collection may be made in the m.
body of the procedure or on separate attachments.
The-method used to derive test data or results shall be provided, These procedures develop administrative controls n.
and frequencies for Operations Department O
responsible surveillances, in accordance with the plant surveillance tracking system.
n e
n-r a-
-m r e w
e
-e rn-r-- - -,
^
~ ~ ' ~
~
HEWiser clos'No.
U 4
VECP 10011-C 13 15 of 35 3.6 ANNUNCIATOR RESPONSE PROCEDURES (ARP)
()
This guide provides criteria and instructions fot the preparation of ARP's for respcnsea to mitigate single specific annunciated alarms.
Mu.1.tiple alarms usually indicate abnormal or emergency situations covered in AOPs or E0Ps.
3.6.1 ARP Nunbering Number ARPs per 00050-C, " Procedure Development".
The seventeen thousand indicates the ARP series and the last two digits are the Annunciator Light Board (ALB) number.
3.6.2 Assembly of Procedures All of the ARP sub-procedures for one ALB are contained hi one procedure.
Each procedure contains a title page, ALB drawing, and ARP sub-procedure index.
3.6.2.1 Title Page The title page identifies the ALB, and has a a.
drawin Room. g of its relative location in the Control The page also has a statement of the-procedure purpose, b.
The title page is numbered as Page 1.
3.6.2.2 ALB Drawing Includo a drawing showing all of the annunciator a.
Windows for the ALB in the procedure.
Label each annunciator window just ss it appears on the ALB, b.
The light board drawing is Page 2.
3.6.2.3 ARP Sub-procedure Index Each ARP includes an ARP Sub-procedure Index.
The a.
index lists the annunciator window coordinates, L_
title, and procedure page number of each l
sub-proc edur e.
Blank annunciator window numbers l-are included in the index, however, the title and l
page number sections are left blank, i
l O
~
.g3,4g
GTihnb"
~
f..
I nmw 1
' ~ " ~~
VEGP 10011-C 13 16 of 35 b.
Number, index pages sequentialJy as part of the proced2re starting with Page 3.
3.6.3 ARP Sub-procedure 3.6.3.1 Content and Detail:
A good ARP Sub-procedure is concise and identifies a.
what to check and what to co, b.
Each step reflects one operator action.
O' der steps in operating sequence.
When a step is listed for clearing an alarm, follow it with a verification step and one describing what to do if the anticipated result does r.ot occur, c.
ARP may interface with UOP, SOP, AOP and E0P.
If the ARP Sub-procedure can be :omplete but not r
lengthy without reference to other procedures, do not refer to other procedures.
If the step insolves an action that the operator is expected to know other procedures need not be referenced. -
However, if-the ARP Sub-procedure involvcs complex actions that are descri. bed in another procedure, that other procedure chould be referenced, d.
ARPs generally prescribe actions for mitiPating a oingle specific alarm.
When the alarm indicates a plant abnormal or emergency condition, the appropriate E0P or AOP should be referenced and relied upon.
ARP should not attempt to deal with plant emergencies, e.
ARPs direct the operato: to Emergency Response procedure 91001-C, " Emergency classification and Implementing Instructions", when applicable.
3.6.3.2 Title Write the title of each ARP Sub-procedure at its a.
i position in the window illustration.
The title i
shall be the same as the engravin g on the actaal i
alarm window.
Capitalization, abbreviations, and
[
acronyms will duplicate the engravings, b.
ALB vindows are identified by an alpha-numeric L
coordinate, e.g.:
A01, A02, B01.
The top left annunciator is A01.
Letters proceed top to bottom, and numbers left to right.
O
n.
1:
t.e. o.,,
yog;,
.. _. s VEGP 10011-C 13 17 of 35 3.6.3.3 Setpoint nrd origin
()
Each sub-procedure should provide a list of the origins I
which may cause the actuation of an alarm.
For the actual alarm setpoints the operator may be referred to the Master Setpoin: Document.
3.6.3.4 Probable Cause a.
This section should list, in order of probabili+.
the conditions likely to have caused the alarm. y, Only the reasonably probable causes should be
- listed, b.
For clarms that actuato as a result of any of sevetal alarm conditions at a remote panel (i.e.
Liquid Waste Panel-Trouble), each specific condition that may have caused the alarm need not be listed.
For these alarms, the cause of the alarm section should state that one of the alarms for the specific panel has actuated and provide reference to the 9pprcpriate ARP.
3.6.3.5 Automatic Actions This section lists automatic actions that should have
/~
occurred at the actuation of the alarm.
If further D) automatic actions may follow, this section should so state.
3.6.3.6 Initial Operator Actions This section should contain only those steps which a.
need to be performed quickly and with high l
priority to (1)
Prevent equipment damage or plant trip, (2)
Mitigate degradation of safety related
- systems, (3)
Respond to a personnel safety hazard, b.-
When the alarm condition is covered by an EOF or AOP, this section should refer to, not duplicate it, c.
If there are no Initial Actions, then this section should state "NONE".
!.O 103446
(
.*a~~~.
- .s.n....
nono.
~
7EGP 10011-0 13 18 of 35 c
3.6.3.7 Subsequent. Operator Actions Thic section should list those steps that do not need to be performed quickly and with high priority.
This cection.in used to state the method for returning the system to normal operation or, in the event return ta normal is delayed or prevented, the steps to minimize tne consequences of the alarm conditions.
If no subsecuent op"erator actions are necessary, this section shoulc. state NONE."
3.6.3.8 Compensatory Operator Actions This section should list any ap?licablu operator actions and thcir frecuency to be performed when the annunciator has been cisabled.
If no compensatory actions are necest.ary, this section should state "NONE".
3.6.3.9 References A list of the major references osed to prepare the sub-procedure should be included at the bottom of the last page.
This list need not include all references used in the research and vriting of the sub-procedure f
but should include reference to plant drawings or 1
technical manuals that show the clarm actuation circuitry and associated setpoinc(s).
4.0 HRITING TECHNIQUE 4.i PUNCTUATION Use punctuation only wnere necessary to aid reading and prevent nisunderstanding.
Select wording to require minimtn punctuation.
If extensive punctuation is required, rewrite or separate into several sentences.
4.1.1 Use hy7 hens sparingly.
Restructure compound words to avoid hyphenation, if possible.
Use hyphens in the-following circumstances:
a.
In compound numerals from twenty-one to ninety-nine.
L Example:
One hundred thirty-four, b.
In fractions, which cannot be avoided Examalent t
One-half, two-thirds, t
three sixty-fourths, lO
f~
PnvCEu@t hv i
PAGE No, l
VEGP 10011-C 13 19 of 35 c.
In compounds with self.
()
Examplesi self-contained,
(,j self-lubricated, d.
Wh2re misleading or awkward consonan ts would result by joining the words.
Examples bell-like, e.
To avoid confusion with another word.
Examples:
l re-cover to prevent conn.sion with recover, pre-position to avoid confusion with preposition, f.
Whero a letter in linked with l
a ncun.
Examples:
X-ra 0-ring, U-bolt, I-beam, y, g.
To separate chemical elements and their atomic weight.
Examples:
Uranium-235, U-235, 4.1.2 Apostrophe Use an apostrophe to indicate the possessive form of a f~}
noun.
Ex ample :
"The company's audit plan..."
Use an N
apostrophe to indicate plural of lettere and figures.
Examples:
PM's, Form 4's.
4.1.3 Brackuts Use brackets when two or more parenthetic phrases are in the same sentence.
.)
( ~
4.1.4 Colon Use a colon to inut: ate something is to follow.
Example :
Restore cool.i.ng flow as follows:
4.1.5 Comma Use of many commas is an indication that the instruction is too complex and needs to be rewritten.
Use conmas for the following:
t a.
Before "and" or "or" in a series of three or more, Example:
a, b, and c, n
b.
To separate five or more digits.
Exneples:
14,500: 1,600,000,
{
r
\\
(g c.
After introductory phrases or clausco when
( ).
necessary for clarity or ease of reading. Examplet When levol decreases to 60 inches, start pump.
~
ram
modv$sav
~ ~ ~
VEGP-10011-C 13 20 of 35 4.1.6 Dash
()
~
Do not use cashes except within procedure and component nu berr.
4.1.7
<arentheses Paventheses are used tc:
Set off su0plementary, phrenthetic, or explanatory a.
material waen the interruption is w re marked than that usually indicated by commas and when the inclusion of such nacerial does not casentially alter the meaning of the Jentence.
Examples (1)
Effluent points (vont, drains, or other lines) may require (2)
Tite Chemical and Volume Control System (CVCS) should be...
b.
Enclose numerals or letters in a series.
2xample:
Tha reasons for flushing are (1)
To reduce equipment damage, and (2)
TL meet legal requirements, Indicate the slternate train's components for c.
instructions dealing with two similar sets of egitipment.
For thren o* more similar sets use tables, checklists or ceparate sections for each set.
A note exalaining the use for the procedure is written at the beginning of the instructions
.weetion:
Example:
NOTE T: tic procedure is written using-Train A designations.
Train B designations are showa in parentheses.
4.1.8 Period Use a periid at the end of complete sentences, with abbrevia*. ions for No. (number) and in. (inches),
at thc snd of paragraph numbers, and for indicating the decimal place in r. umbers.
ew;,Z,;J.
~~ ~ ~ ~~" G y, - ~ ~ ~ - ~ ~,' ~ ~~ ^ ~~^;- { { ~ ~
~~~T r.
,.y VEGP 10011-C 13 21 of 35 4.1.9 Quotation Marks
()
Avoid using quotation marks.
Where jargon or figurative language must be used, the first use only should be set off with quotation marks.
Use when
' making direct quotations, such as from a tech spec, or to indicate a title of a referenced procedure.
4.1. 10 Semicolon
. Use semicolons to set off independent clauses and a run-on listing when such clauses or listings are internally punctuated with connas.
4.1.11 Virgule Use a virgule to indicate an "either/or" situation and as a substitute for "per" in units of measure.
Examples:
either/or, ft/sec, lbs/hr.
4.2 WRITING STYLE 1
4.2.1 Abbreviations, Letter Symbols, And Acronyms a.
Acronyms may be used in the text portion of the procedure provided they are defined in the first
- use, b.
Abbreviations and symbols should not be used in text.
They may be used in data sheets, checklists, tables, or when giving label engravings.
4.2.2 Component Identification Identify components by either their precise tag nomenclature (in all capital letters) or their full descriptive name (each word capitalized),.followed by the identification numbers.
4.2.2.1 Precise tag nomenclature is used for lineups, checklists and similar tabulations.
O e
,_.c.
rs.
m
,a<.,
..:.c
,r.
,g,.
.,,,..,-y 9
y
WOCE DUF<L NR.
g,, g, g VEGP 10011-C 13 22 of 35 4.2.2.2 In procedure text the normal name may be used if it 7 's provides easier, more natural operator understanding
(,)
and identification.
Further considerations are:
a.
When it firs t appears in the text, use the full descriptive name followed by system identifier and etmponen t number.
The full descriptive name should be the words that are abbreviated on the tag unless these are clearly not descriptive.
If the tag nomenclature is not clearly descriptive of the component, initiate action to have the tag
- changed, b.
After its first use, identify the component by either name er number.
(Numbers are the preferred way to indicate valves and panels )
The first letter of each word in the noun should be capitalized to enhance readability.
Example:
STOP the Jockey Pump, If two trains or similar components are c.
alternatives in an action step, indicate the alternate train as described in Step 4.1.7c, d.
If three or more similar components are alternatives in an action step, do not use s
parentheses to set them acart.
Use either a
( )T separate checklist with the complete tag w_
nomenclature, or list each alternate component with its train for each step.
Example:
" START one or more NSCW Cooling Tower Makeup Pumps as required:
a.
Pump 1, A-HS-17419, b.
Pump 2, A-HS-17420, c.
Pump 3, A-HS-17421."
or:
l "OPEN the inlet and outlet header isolations for the gas decay tank aligned for service.
If Cas Decay Tank 1-1902-V6-001, 2, 3, or 4 a.
is inse rvice :
(1)
OPEN the GWPS ISO GDT 1-4 IN HDR, 1-1902-U4-056, l
(2)
OPEN the GWPS ISO GDT 1-4 OUT HDR, s
1-1902-U4-077.
l
\\
v'
PAcclDU.E No.
~
HL WbtON r% g,
VEGP 10011-C 13 23 of 35 b.
If Gas Decay Tank 1-1902-V6-005, 6, or 7 is
(, )
inservice:
(1)
OPEN the GWPS ISO CDT 5-7 IN HDR, 1-1902-U4-046, (2)
OPEN the GUPS ISO GDT 5-7 OUT HDR, 1-1902-U4-071."
4.2.2.3 Where the procedure deals entirely with a specific system, the system identi ier need not be used in component numbers except for any components of other systems wh!.ch are used in this orocedure.
4.2.3 Dafinition of Terms Terms which may be understood in more than one a.
sense should be defined as a note.
It is important that the same term be given the same definition by all procedures which define the
- term, b.
Do not assume that key terms are understood by all users of procedures.
If the term is fundamental to the pro procedure,per understanding and use of the define it.
)
4.2.4 Directing the Specific Manipulation of Controls The features of controls must be known in order to select the p.oper terminology for directing the manipulation of control devices.
Switches may maintain positional placement or may be spring return.
Associated circuitry may lock in or the switch may need to be held in desired function is completed. position until the The following guidelines should be used to govern terminology for the specific manipulation of controls, For a control, whose number is engraved on the a.
control panel placard, the number should be included within the instructional step unless the control is so frequently used that it is very familiar to all trained operators.
Example:
START Condensate Pump B 1-1405-P3-002, b.
For control circuitry that executes the entire function upon actuation of the control switch, use the action verb appropriate to the control device.
Example:
CLOSE RHR PUMP A SUCTION VALVE 1-1224-U4-001,
r-r -
m..X,G M ed M ' ~~~"
' efe.vi,
~~
e.#
VEGP 10011 C 13 24 of 35 Recommended action verbs arer, c.
b (1)
For power driven rotating equipment:
Start V
or Stop, (2)'
For valves:
Open or Close, Throttle Open or l
Throttle Closed, Throttle, (3)
For aower distribution breakers:
Synchronize, Close or Trip.
(4)
For supply breakers and switchea to individual components:
Close or Trip, (5)
Multi-position switches:
Place handswitch (HS-XXX) in XX position.
(6)
Controllers:
Set centro 11er (HICXXXY) at 471, or Adjust controller (HICXXXX) to control flow at 100 gpm, (7)
For air operated valves:
4.2.5 Description of Component Status Indicate component status as:
Pi a.
In Service or Out of Service.
The component is or V
is not functioning within the plant mode of operation.
For Example, a domineralizer may be Out of Service although it is operable, b.
Running or Shutdown.
The condition of rotating equipment, c.
On Line or Off Line.
A generating unit is or is not tied into the power grid, d.
On or Off.
Used for simple equipment, such as recorders, and lights that are or are not powered, e.
Racked In or Racked Out.
The physical status of switch gear.
The switchgear is available or not available to equipment supplied thereby, f.
Energized or De-energized.
Indicates status of electrical circuits, such as logic circuits and electrical buses.
The circuit is or is not
- powezed, t
O
r
- e,hN,;..b
~
rIVisioN WOL NO.
~
VEGP 10011-C 13 25 of 35 9
a 4.2.6 Instruction Step Length And Content
(,y)
Instruction steps should be concise and precise.
Conciseness denotes brevity preciseness means exactly defined.
Thus, instructions should be short and exact.
This is easily ntated but not so easily done.
Goidelines which support these objectives are as follows:
Paragraphs and instruction steps should deal with a.
only one idea, b.
Short, simple sentences should be used in preference to long, compound, or complex sentences, Complex operations should be defined in a series c.
of steps.
Each step sho"Id be as siaple as
- possible, d.
Verbswithspecificmeanit.llhel) should be used.
Full capitalization of verbs wi the user to readily recognize the actien to ')e taken.
Examples are listed in Table 1, Objects of verbs should be specifically stated.
e.
(~
This includes identification of exactly what is to V) be done and what it is to be done to, f.
Limits should be expressed quantitatively whenever mossible.
Qualitative acceptance criteria given ay governing codes and standards should be described in quantitative terms if possible, g.
Avoid vagueness.
It is recognized by lack of specific meaning and it fosters different interpretations.
It leads toward divergent implementation that can result in noncompliance, h.
Content should be consistent with the minimum level of training and experience of the user.
That is, the instruction should not amplify on verbs, locations of components and controls, basis for limits, or other information that the user is expected to already know,
((
i PC 3445
~~ ~~'E sio n
~
PAGE NO' r
-.....v
"~~
" ~~
' ~
~
l VEGP 10011-C 13 26 of 35 l
1.
Action steps should not appear in caution r
statements and notes,
(
j.
Instruction steps should be included for any required documentation, notification, report, independent verification, and obtaining review or approval.
4.2.7 Plant Instrument Values a.
Values shc,uld be listed in the same units of measurements as found on the instrument, b.
Values should be listed as maximum and minimum whenever possibic, c.
Use a conservative value within the precision of operator reading.
Persons are generally able to read one-half the diatance between instrument markings accurately, d.
Minimize the t se or approximately" as it is difficult to quantity and interpretation of an acceptable " band" will vary from person to person, e.
Tolerance symbol use should be minimizedi use wording such as " greater than or equal to".
O) k_
5.0 REVIEWS 5.1 PRE APPROVAL PROCEDURE REVIEWS Each Operations procedure initial draft shall receive a thorough technical review by a reviewer, not the original author.
Reviewer and author will then mutually resolve comments before issuing the department initial reference revision.
Subsequent reviews may be made as deemed necessary, prior to approval and issue as a "Rev 0".
5.1.1 General Instimetions Reviewers should exercise good judgement and technical competence.
They should have a valid basis for all their comments.
Comments should contain only relevant information that will correct format and technical errors, or improve ease of understanding. Avoid ambiguous or extraneous comments.
5.1.1.1 Refer to the " Operations Procedure Review Checklist". 1 and 2 when reviewing an unapproved procedure.
Ov n,-,
~
Asisios" hoc No
~^
' ~ ' - "
~"~
j,m...
VEGP 10011-C 13 27 of 35 4
5.1.1.2 The Operations Department Procedure Coordinator ensures
(~N that OSPs (as identified by the QC Superintendent) are
(,/
routed to the QC Superintendent for a hold point review.
5.2 POST APPROVAL REVIEWS 5.2.1 Reviews should be in compliance with 00051-C,
" Procedure Review And Approval".
5.2.2 Biennial reviews will be as thorough as initial reviews, and be cor. ducted referring to Checklist 2, attached.
5.3 INTERDEPARTMENTAL REVIEWS Some Operations procedures may require a separate review by other departments.
The Operations Procedure Coordinator is responsible for identifying procedures requiring a review by others, for forwarding the documentation to the reviewer and for resolving comments.
6.0 REFERENCES
6.1 PROCEDURES
()
6.1.1 00050-C,
" Procedure Development" 6.1.2 00051-C,
" Procedure Review And Approval" 6.1.3 00308-C,
" Independent Verification Policy" 6.2 ANSI N18.1-1971
" Standard For Selection And Training Of Personnel For Nuclear Power Plants" 6.3 ANSI N18.7 - 1976
" Administrative Concrois And Quality Assurance For The Operational Phase of Duclear Power Plants" 6.4 USNRC Regulatory Guide 1.33, Revision 2 " Quality Assurance Program Requirements (Operation)"
6.5 USNRC Regulatory Guide 1.118, Revision 2, " Periodic Testing of Electric Power and Protection Systems" 6.6 VEGP FSAR Chapter 13 and 14.2 END OF PROCEDURE TEXT pd 703445
^ ~ ^ ^ ^
r yn...~
O uds Pact Ao? '
' ~ ~ ' ' " "
~ ~ ~
VEGP 100ll-C 13 28 of 35 Table 1.
Action Verbs.
O_,
Verb Application _
i Allow To permit a statad condition to be achieved prior to proceeding, e.
pressure to stabilize" g.,
" ALLOW discharge Check To perform a comparison with a procedural requirement " CHECK if S1 can be terminated" Close Is the opposite of open for valves, e.g.,
"CLOSE l
valve HV-142": op?osite of TRIP for breakers, e.g., "CLOSE brea <cr ANB1002".
Complete To accomplish speed.fied arocedural requirements, e.g., " COMPLETE valve checkoff list
'A,'" " complete data report QA-1 " " complete steps i
AthroughGofSub-subsection 4.1.1" Decrease Do not use because of oral communication probTims.
Ensure Take necessary actions to gucrantee conditions are as specified, e.g., " ENSURE all FWIVs CLOSED".
O' Establish To make arrangements for a stated condition, e.g., " ESTABLISH communication with control room" Increase Do not use because of oral couaunicction problems.
Inspect To measure, observe, or evaluate a feature or characteristic for comparison with saecified limits: method of inspection should be
- included, e.g., " visually INSPECT for leaks" I
Lower To adjust a value towards a smaller magnitude.
Monitor To periodically check the status to detect current trends, " MONITOR SG Blowdown flow".
Open To change the physical posicion of a mechanical device, such as valve or door to the unobstructed position that permits access or flott, e.g., "0 PEN valve IFP143" Raise To adjust a value upward, towards a larger magnitude.
Record To document specified condition or characteristic, (q
1.e., " RECORD discharge pressure"
~/
-. : :,:-.. ~-
f.
w..+..
l PAGE No.
VECP 10011 -C 13 29 of 35 Table 1.
Action Verbs (Cont;'d. )
O Verb
, Application Set To physically adjust to a specified value an odjustable feature, i.e., " SET diesel speed to... rpm" Start To originate motion of an electric or mechanleal device directly or by remote
- control, e,g., " START... pump" Stop To terminate op'eration, e.g.,
"STOP... pump Throttle To operate a valve in an intermediate position to obtain a certain flow rate, e.g., "TitROTn.E valve IFP140 to... "
Trip To manually activate a a,emi-automatic feature, e.g.,
" TRIP breaker...,
Vent To permit a gas or liquid confined under pressure to escape at a vent, e.g.,
" VENT
... pump" Verify To observe an expected condition or characteristic, e.g., " VERIFY discharge pressure is stable O
....w,
~-
lxA w g4 g '
y
.VEGP 10011-C 13 30 of45 4
U:
- PROCEDURE WRITER /RT/IEWER
. QUALIFICATI0F~CFeTRLIs'[_
1.
.NAME (PLEASE PRIh7)
~ ~ ~ ~ ~
4 o,
is 1 have a miniatun of 5 years of power plant experience.
I have read the:following and am familiar with the.ir content:
00050-C,
" Procedure Development" 00051-C-
" Procedure Keview And Approval" 00032_C,. " Temporary Changes To Procedures" 4
10011-C,
" Operations Procedure Preparation And Review Guidelines" LOO 308-C,
" Independent Verf,fication Policy" I can locate and une applicable reference materidls.
n
[:
SIGNATURE DATK
-2.
I have : assessed the performance and experience of this
- eep loyee :. - To the~.bestoof.my knowledge and judgment, he/she is qualified as a procedure writer / reviewer.
This iridividual,has--a minimum of 5 years of power plant-experience. ? A maximum of 4-yeers of this-experience may be fulfilled by related technie n~and/or academic-training.
i
~~5F5 RATIONS SUPERINIt.NDENT "
DATE J
i i-FIGURE 1 Mh 1
?
Jx--
~. -. - -. - - -. - - - - - -.. - - - - - -
l--
,-n-,
. - -.,. - +
. - ~,.
e r
f.')
. ;% )
,m
+
\\
t I
\\
t
'n/
LJ App; Oval
( Pyrw>ste No.
Date
~
Georoial)ower n 10011-C D
Reww>n No.
NtCLEAR OPEP.ATIONS 13 VOGTLE ELECTRIC GENERATING PLANT p, na UNIT _ _1__
31 of 35 TITLE:
'IURBINE BUILDING " RAIN SYSTEM ALIGNMENT LINEUP COMPLETED BY:
I, F
Signature Initial Date Signa'tT 3 Initial I ate l
I l
COMMENTS:
RESOLUTIOt.
~
1 REVIEWED BY:
f a
Figure 2,
- ,,,,,a maa:
~~
- f. ~
. e 3.
s
?s -
, -ar
, a g
~
c g,.,-
g e
O~^
Procature No.
Revisaan
~
Page No.
VEGP 10011-C 13 32: of 35
\\
4 1
CONDITION LINEUP VER'IFICATION COMPONENT DESCRIPTION REQUIRED (INITIALS),
(INITIALS)
TOP OF PRZR ROOM 1-1201-X4-072 RCS PRZR SPRAY LINE' VENT VALVE CLOSED 1-1201-X4-084 RCS PRZR SPRAY LINE VENT VALVE CLOSED /CAFFED TOP OR PRZR l
l 1-1201-U4-102 RCS PRZR SFTY VLV PSV-8010A LOOP CLOSED SEAL DRAIN i
i 1-1201-U4-103 RCS PRZR SFTY VLV PSV-8010B LOOP CLOSED l
SEAL DRAIN 1-1201-U4-104 RCS PRZR S NY VLV PSV-8010C LOOP CLOSED SEAL DRAIN 1-1201-U4-105 RCS PRZR SFTY VALVES LOOP SEAL CLOSED liEADER ISO 1-1201-U4-106 RCS PRZR SAFETY VALVE RELIEF Edit CLOSED / FLANGED VENT (Do not include this column if Independent Verification is gj not required. )
- May be used when only one footnote is used throughoct time procedure.
(1), (2), (3), etc.
Footnotes are numbered and in parenthesis if more than one is required.
Figure 2 (Cont'd'.,)
p
]
~
v g (
s
p:
~
10011-c' 13
-33 f-35
!:~
Sheet 1 of 1-
' OPERATIONS GROUP PROCEDURE REVIW CHECKLIST fl g
3 1.0 Adminio h tive' Review L. equi,rements Check-tnat procedure is consistent wita 10011-C, 10012-C, J
and 00050-C for the following items:
^
l.-1 The' exception' list is present and correct, if
[
applicable.
f' i.2 Each page has.-appropriate borders and enc:ings.
1.3 Proper numbering of pages.
1.4 All: supporting materials are referenced in proper procedure section.
1.5 _ Supporting materici number and r2.me(s) are consistent-
-throughout the procedure body.,
- 1. 6 References are current, adequate and applicable to the-procedure.
1.7' Cautions and Notes adher6 to guidelines.
.+
- O 1.8. Com onent identification number derivations adhere to gui elines.
M 1.9--:If flow chart is part of the_ procedure, verify that flow chart represents the procedure.
- g.
.1.10 Capitalization and use-of action verbs adhere to guidelines.
lill, Use; of acronyms,.abbreviarions, and action verbs adhures'to guidelines.
_1.12 Subdivision of steps : adheres to guidelines.
1.13 Adequate and ap111 cable-limits and precautions are '
addressed for tle performance. of the procedure.
l.14 All procedural information is-clear,; concise, and NOT
- amb?guous.
1.15cContents of.a proc dural step are placed on the same page.
' l.16-IndependentL verification - is provided as required.
gr A.)'
~'
r ' - '
pnocuouni n '
kywof ~
^~
~ ~ ~ ' },,,j,~
~ ^
~ '
VIGP.
-10011-C 13 34 of 35 Sheet 1 of 2
,0PERATIONS GROUP PROCEDURE REVIEW CHECKLIST #2
'^ #
Technical Review Requirements--
- 1. 0_
Sources To Be Used For Review 1.1 FSAR.-
-1.2-Technical Specifications 1.3 Design Criteria
- 1. 4 - P&ID.C&ID, Logic Drawing, etc.
r 1.5 Westir.ghouse Precautions, - Limitations, and Setpoints 1.6 Technical /'andor Manuals 1.7 Other Vendor Drawings 2.0- Procedure is. technically correct as follows:
9
-2.1-Precautions and Limits are clear,.of aufficient detail
]
and are' ordered according to importance.
-['
2.2-Prerequisites are not.too general. and adequate-detail-
%y for easy operator understanding.
2.3.-All actions, manipulations addressed ~in procedure meet the requirements-and intent of'the Purpose / Scope as stated in the-procedure.
2.4 The procedure :contains ~ sufficient level of detail tu
- sequentially. start. up the system / component in - a manner.
that reflects good operating practices.
2.5 The procedure contains/ sufficient' level of detail-to t
sequentially shut-down-the system / component in a manner:
l.
that reflects good operating practices.
'2.6 The z procedure contains sufficient --level of. detail for operating evolutions to maintain the system / component' v
in 'a. safe, efficient and effective-statue that reflects-good operating practices.
. f03445 -
lh
. -. -. ~
s
.-,n,
,m.,
~,
.,..m
pyngEy l
VEGP 10011-C 13 35 of 35
\\
1 1
Laeet 2 of 2 OPERATIONS GROUP FP.OCEDlfRE REVIEW CHECKLIST #2
[~)
2.7 The valve ~and electrical lineups contain:
v Sufficient valving ta support the procedure, a.
b.
Correct valve positioning to support the procedure.
Valve names are prectsely as given on tags, c.
d.
Corre.ct control switch / breaker positioning to support the procedure, as cpplicable.
Remotely operated VALVE / BREAKER identification is e.
as found on the control panels.
2.8 All supporting materials /attachmente are legible and useable.
Are additional attachments required to facilitate the efficient and effective use of the procedure?
2.9 Verification and approval signatures are addressed where applicable in the main body and where required in supporting materials.
2.10-For normal operations, procedure interrelations with gS other precedures are not in cenflict with:
t
)
Purpose / Scope of other operations procedures, a.
b.
Prerequisitec/ Initial Conditions of ether operating procedures, Valve and Electrical Lineup attachments of other c.
operating procedures.
4 ws