ML20132F304
| ML20132F304 | |
| Person / Time | |
|---|---|
| Site: | 05000000, Waterford |
| Issue date: | 08/11/1983 |
| From: | LOUISIANA POWER & LIGHT CO. |
| To: | |
| Shared Package | |
| ML082320156 | List:
|
| References | |
| FOIA-84-206 MD-1-011, MD-1-11, NUDOCS 8510010295 | |
| Download: ML20132F304 (46) | |
Text
r N
r.
4 f
)
- m PAGE (APPROVAL SIGII)
DEPA1CMENTAL P1tDCEDURE MD-1-011 REVISION 2
APPROVAL DATE August 11, 1983 EFFECTIVE DATE August 11, 1983 MAINTENANCE DEPARTMENT PROCEDURES - DEVELOPMENT, CONTROL, AND DISTRIBUTION APPECTED:
N s' '
ptW3 L
MD-1-011 Revision 1 28 Atrac h nt 6.7 (1 of 1)
"M
?8 B" eso22' poin-sy us BERNABE84-206 PDR 747
DEPa* MPG FROCEDURE l
CHANOE/ REVISION / DELETION REQUEST pnoegagnz yn, lh D-/-of /
3,.1% :- L.-es Den. d.s,. J bosof.ros -
1.c m ava. DAr _e DeveIm. I G /~8 o~[
(if different from Group Head approval datel FROCEDURE STATUS M//[. t [w h."
A.
Caanse m.
~1 1.
Revision No.
1 C.
Datacion e4 REASON FOR CHANGE. REVISION, OR DELETION b ke *b au ha e/ss.l keu row (bo k ksh (Af C.T) f o*t poet t'=*
L,. II,.
Ae bri,-.h JMt c4 b, +
if, a w..u w...r c.,u,, : J e 4 e
~
REVIEU SIGNATURES I
Originator Data 3~I3 Technical Review bdIN dM Date -l'/7/*'E FEDCEDURE EVALUATION - Does this e, revision, or dalation: Ygs yn 1.
Change the facility as described in the FSAE7 X
2.
Change the procedures as described in the FSAE7 X
3.
Conduct testa / experiments not described in the FSAE?
V' A.
Create a condition or conduct an operation which exceeds or could result in exceeding, the limits in Technical f
Specification?
If the answer to any of the above is yes, complete and attach a 10 CFR 50.59 Safety Evaluation checklist.
PROCEDURE EVALUATION Date
// /2/F 3 Q.C. Revtew AWd6
- wP I'
Date
//- 3'-dl Department Head d2h-w1E, Date v /?/93 TEMPORARY AFFROVAL NOS Data Maint. Super (or Group / Dept. Baad)
Date
- Tamporary approval must be followed by QC Review, Department Baad Review and Group Enad Approval within IA days.
FERMANENT AFFROVAL STGNATURE (,Chanaes/ Deletions Only - For Revisions, see Title Page) i Group Bead e
Date /' '/r'3 f/
i MD-1-011 Revision 2 31.8 (1 of 1)
o DEPA]CMENTAL PROCEDURE CHANGE / REVISION / DELETION REQUES*
PROCEDURE NO.
+*#
tin.r
"'t#~
EmCTm DATE
- p.. t.. e f G k.f..o,,lt, L k.-
(if different from Group Head approval datel PROCEDURE STATUS A.
Change A I
5.
Revision No.
'1 C.
Deletion e*'/4 REASON POR CHANGE, REVISION, OR DELETION Amnl'h w s rhi. e S.s.o ~C$e.es" be esofree$ issh M c.it n
iJ.J.%.
J/... /,.,
e F 'c wrascea ti*e w e.r. A,, ;<e teasefthe.a.$s.r VttStre b'oao e) l9<.r b t sitty lwe vret].
REVIEkiSIGNATURES Originator Date
? - 2 /- P J Technical Review b d b Ib
-T i
Date 6
i PROCEDURE EVALUA'f' ION - Does this change, revision, or deletion:
Ygs 30 1.
Change the facility as described in the FSAR?
/
2.
Change the procedures as described in the FSAR?
3.
Conduct tests / experiments not described in the FSAR?
/
4 Creat.e a condition or conduct an operation which exceeds or could result in exceeding, the limits in Technical l/
Specification?
If the answer to any of the above is yes, complete and attach a 10 CFR 50.59 Safety Evaluation checklist.
PROCEDURE EVALUATION v _./
Date 2
3 Q.C. Review
- 4 4t"/l b M I
Date 9 - 2 7 -1P' )
Department Head h7 N A l~
Date //#///
TEMPORARY APPROVAL SIGNATURES
- NOS Date Maint. Super (or Group /D<.pt. Head)
Date
- Temporary approval must be followed by QC Review, Department Head Review and Group Bead Approval within 14 days.
PERMANENT APPROVAL SIGNATURE (Channes/ Deletions Only - For Revisions, see Title Page)
Group Head
/
Date T/
f/
MD-1-011 Revision 2 31
- .8 (1 of 1)
...-_-__.._--,.-,._m_-
.--,.,_-,.,.._.-_,___________.,m_,__,_m__
-, _ _ _ _ _, _,, _ - _ _ -. _,. _ ~.,.. _.....
s i
- A:ZL*JE 3 SE3
=
DIFAI:MZlr.".AI. PECM CI&BGE/IET:2:3N/ w N h m Prasadure 3e. /M D -/ - O//
TA:la M ais /*w = w ee Oee.e /as ear / /e. ee./ red -
E$***'L E'**
Osvg {.p., s.ah C =lr*l e.~ h
(.*
d12farums *=uss Group Band approvaA dace)
J Ois bo~ab bo'o.a.
CannLate L.~
E. er C ChangaMs.d*'[4 A.
E.
Revistas Es.
- 1_
d'!d C.
Salatian IEASON FOR CI45GE.
.v.y.a aam. CR OF 7
.1 ~..o. <Je Ge..a He. 9.s
.,,,.... / a /l.,,4,. A c)9 x,y. L. /, c. i
. J h d C. k.i c',
v..,Lali.
.o s.ti.
AJA sh,1
/.
e..a t J.9s.
- r
_r -,..r,4 4,+i.
.a J..~. a.a,a 9
.t-. W. s 1 sir..a.w e e.
.Od.h nana F - / - #3 osistmasse Tashmiaal Reviser W K Mll )
Dass ( / c'- / P 3 gi a
SAFEy ETALEL**.llN Dean this ehunge, meistas, se delacias:
TES 30 1.
Chess the 8--*"*y-as daeasthed La the FIAE!
]
2.
Chames promodeses as h w in the FSAE!
d
- 3. Camdmet b / e ast domesthed La the FIAI2 d
4 Cressa a esad131am er h as W= skiah ammanda er could result is ammaadtag, the 11suLes 'in Ta**=4 *=t 2
n
- ,.h. _...
.h. - is
, - a.=aa, a 10 C21 30.35 Sadasy Evalencias chsehlia.
A 4 r 8
r/r/n a.7 1a s.
oa.s Tw t
os.a r
.a.,re,r e,,s 1
ca Qc BarteurI =
Dass f" / J -/3-oveup/Depesumana need // + mE _
sama
<4%
A/
Memps.uor appnevnt met be==w by oc En,1sw ad crow /nepartamac Band approval within 14 days.
l M>= L-411 Emristan 1 29 Am*==h===r 6. 8 (1 of 1)
O
_ _. _, _. _ _ _ _ _. _,. _. _ ~ _ _ _ _ _. _ _ _ _ _ _ _ _ _ _., _ _ _ _
Administrative Procedure MD-1-011 Mnintenance Department-Procedures - Development, Revision 2 Control and Distribution TABLE OF CONTENTS 1.0 PURPOSE
2.0 REFERENCES
30 DEFINITIONS 4.0 RESPONSIBILITIES 50 PROCEDURE 51 General 5.2 Development, Review and Approval of.New Procacures 53 Deveicoment. Review and Apprevel et* Revisie=s 54 Development, Review and Approval of Changes 5.5 Deletion of Procedures 5.6 Control and Distribution of Procedures 6.0- ATTACEMENTS 6.1 New Procedure / Revision Flow Chart (1 page) 6.2 Procedure Change Flow Chart (1 page) 63 Missing Information List (1 page).
'6. 4 Review Cover Sheet (1 page) 65 to CFR 50 59 Safety Evaluation (1 page) 6.6 Document ' Review Comments (1 ' page )
67 Title Page (Approval Sheet) (1 page) j 6.8-Change / Revision / Deletion Request (1.page) m
(-.ej ;/N.M LW;/,3 G led-es(rf.yu pk 69 Technical Review Checiclist 6.10 Field Control Copy Verification Form (1 page) v W.L 6.11 Field controlled Copy Change Log (1 page) 6.12 Controlled copies (Locations and Verification) (1 page) 70 COMMITMENTS AND REFERENCE 3 cmst i
LIST OF EFFECTIVE PAGES y PA Title Revision 2
?~
1-41 Revision 2 1
hNl{3/,2{YL
- A"*f
/
oe %
s
, hun " ' ~ ' '
c"4 ^' c ' 1 1,rp,ir, >; a 11, n,1g 3 'A - 3 7.
1
,,,_.--..-7,,,., _, _,
_.,.____-,___._,..,-.._-.,7_____m___,_m._,.
_m-,_..,,,,,.
O Administrative Procedure MD-1-011 Maintenance Depar$ ment Procedures - Development, Revision 2 Control and Distribution 1.0 PURPOSE This procedure provides the guidance and the mechanism necessary to l
develop, review and approve; change or revise; and delete, control l
and distribute Waterford 3 SES Maintenance Department Procedures.
2.0 REFERENCES
2.1 UNT-1-002, Procedure Numbering and Format 2.2 UNT-4-009, Control, Distribution and Handling of Program Descriptions and Plant Operating Procedures 23 UNT-1-004, Plant Operations Review Committee 2.4 ANSI N18 7-1976 (ANS3 2), Administrative Controls and Quality Assurance for the Operational Phase of Nuclear Power Plants 2.5 USNRC Regulatory Guide 1 33, Revision 2, February 1978, Quality Assurance Program Requirements (Operations) 2.6 Waterford 3 SES Final Safety Analysis Report, Section 13 5, Plant Procedures 2.7 Waterford 3 SES Final Safety Analysis Report, Section 16.6.0, Administrative Controls 2.8 UNT-1-003, Procedure Development, Review and Approval; Change and Revision; and Deletion 29 UNT-5-002, Condition Identification and Work Authorization 30 DEFINITIONS 31 PERSONNEL TERMS 3 1.1 Author - The person assigned by the cognizant Group Head or l
Department Head to write a procedure; or any individual designated by the cognizant Group / Department Head to perform a function assigned to the " Author" in this procedure.
2
O Administrative Procedure MD-1-011 Maintenance Department Procedures - Development, Revision 2 Control and Distribution 3 1.2 originator - The person who initiates a change, revision or dele-tion of an approved procedure.
313 Technical Reviewer - The person assigned by the cognizant Group Head or Department Head to conduct a technical review of a new procedure or of a change, revision or deletion of an approved procedure.
The Technical Reviewer shall not be the Author / Originator of'the subject new procedure change, revision or l
deletion.
32 PROCEDURAL TERMS 3 2.1 Departmental Procedures - Procedures which are not required to be in the Plant Operating Manual (POM), but which are necessary for t,he proper functioning of departments.
Reference 2.8 requires that certain procedures be reviewed by PORC and approved by the Plant Manager-Nuclear.
These include administrative procedures that control maintenance of safety-related equipment, Technical Specification Surveillance Procedures, and procedures for maintenance of major equipment such as:
l 3 2.1.1 Rework of steam generator tubes 3 2.1.2 Replacement of reagtor coolant pump seals 3 2.1 3 Replacement of important strainers and filters 3 2.1.4 Rework or replacement of safety valves 3 2.1.5 Rework or replacement of nuclear instruments 3 2.1.6 Removal and replacement of reactor vessel head 3 2.2 Typographical Correction - The correction of an obvious, non-I numerical typographical error in an approved procedure by a single line through the erroneous character (s) writing in the correct character (s), and initialing and dating the correction.
Anyone may make a typographical correction to a departmental procedure.
Review and approval are not applicable.
3
-.m
.,,,.,._.m
,.,_.,_,_..__.___.__,,m__,_
t
f Administrative Procedure MD-1-011 Maintenance Department Procedures - Development, Revision 2 Control and Distribution 323 Revision - The word processing and reissuing of an approved procedure for the purpose of incorporating any modification (s) to its content, organization or format.
The difference between a revision and a change (step 3 2.4) is one of scope; a proposed change that would render a procedure difficult to read or comprehend due to multiple addendum pages and/or strikeouts should be processed as a revision.
Revisions are approved by the Group Head or his designee.
Unless specifically stated otherwise in this procedure, approval by Group Head is to mean " Group Head or his designee."
3 2.4 Change - The reissuing of individual marked-up pages of an approved procedure for the purpose of incorporating any modification (s) to its content, organization or format.
Changes are approved by the Group liend.
3 2.4.1 The following types of modification require Group Head approval l
prior to implementation:
A.
Any change which alters either the purpose or scope of a procedure as stated in the " Purpose" section B.
Any change which alters an acceptance criterion or acceptance limits associated with a procedure C.
Any change to quantitative setpoints or limits associated with a nuclear safety-related system or components D.
Any change which results in operation of equipment or components in a mode of operation or to satisfy a function for which they were not designed 3 2.4.2 The following types of modification require Plant Engineering evaluation prior to approval by the Group Head:
l A.
Any change which results in a change to the facility as described / presented in the FSAR 1
4 w -_,
_my_-
7,-3 ge.-----,--,.-,.,
-9 r
,,.,9y
-.,,w
,,,,-,,,,,-wr*.,,w,.,-,y,,
ywpp_,-,
wg--e.,-,-*,.-._%-.,-y y
p,,
,q_w,9,,_,e,,,
4 O
Administrative Procedure MD-1-011 Maintenance Department Procedures - Development, Revision 2 Control and Distribution B.
Any change to plant procedures or administrative controls as
~
described or referenced in the FSAR C.
Any change which proposes a test or experiment not described in the FSAR D.
Any change which creates a condition or conducts an operation which exceeds or could result in exceeding the limits in Technical Specifications 3 2.5 Temporary Change - A change (step 3 2.4) which is needed on an in-mediate basis and which does agt involve any of the eight criteria of step 3 2.4.1 or 3 2.8.2.
A temporary change is implemented following temporary approval by the NOS and Maintenance Supervisor (or Group Head).
Temporary changes must be reviewed by QC and approved by the Group Head within 14 days of the temporary approval date.
If the Group Head grants approval within the 14-day period, they beccme permanent changes.
3 2.6 Approval Date - The date upon which the Group Head signs approval of a new procedure, revision, change or deletion.
327 Effective Date - A specific implementation date for a new procedure revision, change or deletion.
The effective date may be a milestone activity such as afuel load."
When an effective cate is not indicated on a Review Cover Sheet or Change / Revision /
Deletion Request, the approval date (step 3 2.6) serves as the er-factive date.
3 2.8 POMC Print - The typed / edited copy of the procedure draft from word processing.
3 2.9 Central Distribution Location - The storage location where the departmental Master Copy of each procedure is kept.
5
Administrative Procedure MD-1-011 Maintenance Department Procedures - Development, Revision 2 Control and Distritution 3 2.10 Master Copy - The.first copy produced from the Group Head-approved POMC print.
The Master Copy shall be kept as a Controlled Copy and designated as the Master Copy.
3 2.11 Controlled Copy - Procedures which are stamped on the title page in red as " Controlled Copy."
Each department shall maintain ac-countability of its Controlled Copies and verfiy that they are l
the latest approved version of the procedure.
3 2.12 Field Controlled Copy - Procedures which are stamped on the title page in red as " Field Controlled Copy."
Each department will maintain accountability of issued Field Controlled procedures for seven (7) days and ensure that they are verified (as required) to a
be the latest approved version of the procedure.
3 2.13 Uncontrolled Copy - Any procedure not meeting the criteria of step 3 2.11 or 3 2.12.
Copies of original RED marked procedures are to be considered Uncontrolled Copies.
Uncontrolled Copies shall not be used to perform "in-hand" procedure maintenance.
3 2.14 verification - Comparison of a procedure's content to a Controlled Copy of the procedure to ensure that they are identical.
3 2.15 "In-Hand" Procedure Use - Maintenance tasks to be done by l
physically having and referring to the appropriate written Field Controlled procedure.
Thse tasks are defined in UNT-4-009 (Reference 2.2).
3 2.16 Group Head - The supervisor who is responsible for all maintenance tasks and departments (I&C, Electrical, Mechanical).
3 2.17 Department Head - The supervisor who is responsible for an individual maintenance department (I&C, Electrical, Mechanical) and the maintenance tasks associated with the department.
6 I
i*
Administrative Procedure MD-1-011 Maintenance Department Procedures - Development, Revision 2 Control and DistrLbution 4.0 RESPONSTETLITIES 4.1 The Group Head or his designee shall have overall responsibility for l
implementation of this procedure.
4.2 The Group Head or his designee shall be responsible for preparing, l
implementing and maintaining this procedure.
43 The department is responsible for:
431 Maintaining the department's procedure binders 432 Entering new procedures into the binders 433 Ensuring that all procedure revisions and changes are promptly entered into all Controlled Copies including Field Controlled l
Copies 434 Ensuring that all procedures which involve coordination with other departments receive a technical review by the affected department 4.4 Plant Engineering shall review procedures which involve complex maintenance as determined by the Department Head.
4.5 Central Records shall maintain a copy of all procedures (including changes, revisions and deletions) as the historical record.
4.6 Other responsibilities are as delineated in section 5 0.
50 PROCEDURE 5.1 GENERAL 5 1.1 Maintenance that can affect the performance of plant equipment and/or the quality of.such maintenance shall be properly preplanned and performed in accordance with written procedures.
Skills normally possessed by qualified maintenance personnel may not require detailed step-by-step delineation in a procedure.
3 UNT-5-002, section 5.1.11, contains additional guidance for I
determining when a procedure is required.
7
-v,
- -, -- -,,-~,
,.,r,,.n,-
-,,---,,,w-,----.
-,e
,w-w,--,
,-,-----,,,,.,.e+
Administrative Procedure MD 011 Maintenance Department Procedures - Development, Revision 2 Control and Distribution 5.1.2 Procedures which are to be used on an infrequent or one-time basis should be issued as Special Work Instruction.
The Department Head should determine which procedures are issued as permanent procedures.
5.1 3 Procedures shall be reviewed at least every two years.
A procedure is considered reviewed if a revision has been approved.
Departments shall ensure that documentation of the two-year procedure review is produced.
5.1.4 Procedures which were deleted from the POM because it was determined that PORC/PM-N approval is not required shall be designated as departmental procedures.
The department shall designate's Master Copy of the procedure.
The Master Copy shall be kept at the Central Distribution Location.
Copies of the Master Copy shall be placed in the departmental procedure binders in accordance with section 5.6.
5.2 DEVELOPMENT, REVIEW AND APPROVAL OF NEW PROCEDURES NOTE.1 is a flow chart.cf new procedure development.
5 2.1 The cognizant Department Head initiates a new procedure by assigning the Author and one or more Technical Reviewer (s).
5 2.2 The Author shall prepare a clean, legible rough draf t in a format prescribed by UNT-1-002 (Reference 2.1).
The Author shall ensure that adequate provisions have been made to provide necessary usp6f Quality Control Hold and/or Witness Points. The author shall utilize the' guidelines of Attachment 6.9 (pages 2 thru 8) in preparing the draf t.
/
5 2.2.1 The Author shall determine which attachments can be word i r.3 # }
processed and which will require draf ting.
Attachments requiring drafting shall be approved by the Department Head.
~
Rough drafts of attachments requiring draf ting should be 8
Administrative Procedure MD-1 011 Maintenance Department Procedures - Development, Revision 2 Control and Distrib*ution submitted to Drafting in time to receive completed work prior to Group Head approval.
5.2.2.2 If a procedure is not complete, the author shall prepare a Missing Information List (Attachment 6 3) prior to submission for technical review.
Each missing item (such as UNID tag numbers, setpoints, procedure references, acceptance criteria, etc.) shall be listed on the Missing Information List.
The Author shall insert a "(LATER)" in the procedure at the location of the missing iten.
Missing information is cleared by a change or revision.
5.2.2 3 The Author shall complete entries at the top of the Review Cover Sheet (Attachment 6.4).
If the procedure is to have a specific effective date, the effective date/ milestone activity shall be indicated.
5.2.2.4 The Author shall determine the number of review copies needed and duplicate his rough draft to provide copies for the Technical Reviewer (s).
5.2.2.5 The Author shall attach forms and distribute copies of the rough draft as follows:
A.
Attach Review Cover Sheet and Missing Information List for copy (or copies) for the Technical Reviewer (s) 5.2 3 Technical Review - The Technical Reviewer (s) shall perform the following function:
~
5.2 3 1 Conduct a thorough review, including verification of any Hold / Witness Points.
The Technical Reviewer should review the procedure to verify compliance C//pG/
with the applicable procedure writing guidelines established on Page 2 g
thru 8 of Attachment 6.9.
The Technical-Reviewer (s) should document g
the conduct of the technical review by completing a Technical Review i
//~ 3 '
Checklist (Page 1 of Attachment 6.9).
Any questions answered "NO" on i the Technical Review Checklist shall be documented on a Document Review Comments sheet by entering :he appropriate comment. Comments will be submitted by the Technical Reviewer to the Author for resolution. If the 9
l
.. - --,- -- - l
ga e
Administrative Procedure MD 011 Maintenance Department Procedures - Development, Revision 2 Control and Distribution Technical Reviewer and the Author are unable to resolve com-ments, the responsible Department Head shall determine a resolution and document the resolution on the affected Document Ag44 G(
Review Comments shestrT::hrir:1 ?:"10-
"h blict 0:::r IL.;; :r g55 t;th (if : ;11ecy!-y_
} ti-3'I}
5232 After the Author has incorporated any comments in the draft, the Technical Reviewer shall answer procedure evaluation questions 1 l
through 4 on the Review Cover Sheet (Attachment 6.4),' sign it and cate it.
5.2 3 3 If the Review Cover Sheet has a "YES" answer for any of I
questions 1 through 4, the Technical Reviewer shall complete, sign and date the 10CFR50.59 Safety Evaluation (Attachment 6.5),
and:
A.
In an attachment, set forth the bases and criteria used to determine ~that the reviewed procedure does or does not involve an "unreviewed safety question."
B.
Include an evaluation for each question 1 through 7 of the Safety Evaluation.
5.2 3 4 Attach these sheets, the Missing Information List, the Technical C #4 *' F j
Review Checklist,Ce.;.- Sh::t, : d th: *:: :i;;l P.;ric" Ch :' li:t 914 a
l to the Review Cover Sheet and draft.
Submit to Author.
,/h J -P}
1 10 i
Administrative Procedure MD-1-011 Maintenance Department Procedures - Development, Revision 2 Control and Distribution NOTE When a procedure is needed immediately, the editing _vord processing cycle may be bypassed; however, the procedure must be submitted to word processing on a timely basis following Group Head approval so that a typed and edited copy will be produced.
Instructions for the processing of handwritten RUSH procedures are given in section 5 2.13
. -... ~
5.2.4 After obtaining approval recommendation signatures from the Technical Reviewer (s) on the Review Cover Sheet, the procedure shall be prepared for editing / word processing by verifying the following items:
5 2.4.1 The Review cover Sheet has required signatures and all required information is pro'perly completed.
' w Gr 5.2.4.2 Any *N0' answer on the Technical Review Checklist C:"cr Ch;;t is j[,
accompanied by a Document Review Comments sheet and is indicated)/*2-J'7 '
"Reso1'ved. h 5 2.4 3 All draft pages, including photocopies of any attachments not yet drafted, are present.
5 2.5 The department shall then submit the draft procedure to PoMC, where it is edited and a print is made and proofread.
5 2.6 After receipt of the PCMC print (typed and edited),.the department shall forward the PCMC print (or a copy) to the QC Engineer with the Review Cover Sheet.
527 QC Review - The QC Engineer shall perform a quality control review of the procedure.
11
_ -____= _ _ _ _ -
Administrative Procedure MD-1-011 Maintenance Department Procedures - Development, Revision 2 Control and Distribution 5.2 7 1 The QC Engineer shall verify or, if necessary, identify any QC Hold / Witness Points required in the procedure.
5.2 7 2 He shall meet, when necessary, with the Technical Reviewer or l
Department Head to resolve any comments.
5.2.7 3 He shall indicate completion of the review and satisfactory incorporation of comments by signing and dating the Review Cover Sheet.
He shall then return the procedure, Review Cover Sheet and QC Checklist (if applicable) to the department.
5.2.8 Department Head review - After QC review, the Department Head shall review the procedure.
5.2.8.1 The Department Head shall use Document Review Comments sheets l
(Attachment 6.6) to note comments.
5.2.8.2 The Author shall resolve comments received and incorporate them in the POMC print of the procedure.
5.2.8 3 In the event that a draf t is accompanied by a Safety Evaluation, Plant Engineering and PORC shall evaluate any unreviewed safety question.
5.2.8.4 Upon satisfactory resolution of Department Head comments, the Department Head shall sign the Review Cover Sheet.
5.2 9. Upon satisfactory resolution of Department Head comments, the department shall forward the POMC print with all comments incorporated to word processing where a final print of the procedure incorporating all review comments shall be made.
5 2.10 The department shall prepare a Title Page (Attachment 6 7) and submit the following for Group Head approval:
l 5.2.10.1 Final POMC print of procedure 5.2.10.2 Title Page 5.2.10 3 Review Cover Sheet 12
5 Administrative Procedure MD 011 Maintenance Department Procedures - Development, Revision 2 Control and Distribution 1(CWA"Gf 5 2.10.4 Technical Review Checklist
.... CL;;; ;... T.;L;1:;1 R: ':
3,$,
44eeeie M e4>
)/AJ - T 3 5.2.10.5 Document Review Comments sheets 5 2.10.6 to CFR 50 59 safety Evaluation, if applicable
.5 2.10 7 QC Review Checklist, if applicable 5.2.11 Group Head Approval - The Group Head shall review the procedure (resolve comments with Author), then sign the Title Page (Attachment 6 7), thereby signifying procedure app *.* oval.
The I
department shall ensure that the approval date (and effective date, if different) appear on the Title Page.
5 2.12 The department shall reproduce the final POMC print and designate this as the Master Copy.
The Master Copy shall be kept at the Central Distribution Location where it will be maintained and controlled in accordance with section 5.6.
5 2.13 In an immediate need situation, a procedure may be reviewed, approved and issued for use in handwritten form, The procedure for this is as follows:
5 2.13 1 The draft procedure shall be prepared per steps 5 2.2 through 5.2.2.5.
In addition, the Author shall ensure that:
A.
The procedure number appears on each page, including attachments.
B.
Each page is clearly numbered in the format apage n of n.'
Technical review and comment resolution. shall be performed per steps 5 2 3 through 5 2 3 4 5 2.13 2 Following technical review, the department shall forward the procedure, Review Cover Sheet, and 10 CFR 50 59 Safety Evalua-tion (if applicable) to QC.
QC review shall be performed per steps 5.2 7 through 5 2 7 3.
13
Administrative Procedure MD-1-011 Maintenance Department Procedures - D velopment, Revision 2 Control and Distrfbution 5 2.13 3 The Department Head shall review the procedure per steps 5 2.8 through 5 2.8.4.
5 2.13 4 _The Group Head shall review and approve the procedure per step 5.2.11, then sign and date the Title Page.
5 2.13 5 The department shall ensure that the proper revision number appears on each page of the procedure, then distribute the procedure per step 5 2.12.
5.2.13 6 The department shall prepare an entry for the " tickler file,"
whose purpose it is to track procedures which are approved in handwritten form.
5.2.13 7 The Department shall submit the handwritten procedure to editing / word processing on a timely basis and remove the entry from the " tickler file" upon approval.
The draft as submitted to word processing shall include all changes approved by the Group Head (when still applicable).
5 2.13.8 The revision to the handwritten procedure shall be processed, reviewed and approved per section 5 3 of this procedure.
53.EVELOPMENT, REVIEW AND APPROVAL OF REVISIONS NOTE.1 is a flow chart of revision development.
531 originator. The originator completes the top of a Change / Revision / Deletion Request form (Attachment 6.8) by entering the procedure number, procedure title and effective date (if applicable); entering tne revision number (step 5 3 1.1); writing a brief description of the reason for the revision; and signing and dating the " Originator" line.
Blank spaces (e.g., " Effective Date," " Change No.." " Deletion") shall be filled in with "N/A."
14
1 Administrative Procedure MD-1 -011 l
Maintenance Department Procedures - Development, Revision 2 i
Control and Distribution
)
5 3 1.1 The revision number shall be the latest approved revision number of the procedure incremented by one (1).
l 5 3 1.2 The originator shall attach althar a marked-up copy of the procedure or a rewritten draft of the procedure.
5313 The originator shall ensure that all changes whien have been i
approved since the last approved revision of the procedure are incorporated into his proposed revision.
l 5 3 1.4 If the revision will add or clear any missing information, the criginator shall attach a revised Missing Information List.
I 5315 The originator shall prepare the procedure for processing per i
section' 5.2 of cais procedure, except that:
1.
7:e
- .y..
... "; d ;;; _;i;; 0;: ;i;;1 r;;i;r ty ;;t;ria; l4
- . 1 ::1;1; ;; ::: - 1
- -1; - 1.;; ;: ::. r_.....,
4P,e 1
i "wvasavuf Lw1w.... I
^"'""I.
i 4,
PA anual periw.--
D J5.
... Oep;rt;;;t ":;f "-i---
t^-'='a
' -;~.i.,
u.
d
."r;;;f -- tvalume4a-= -- tt;
.u,,jE.,iaiunfL,1 54wm y
-a wsuess.-
41 Wherever the ters " Review Cover Sheeta appears in section 5 2, the term " Change / Revision / Deletion Request
- should be substituted.
i 54 DEVELOPMENT, REVIEW AND APPROVAL OF CHANGES i
i
_===
NOTE
- 1..2 is a flow chart of change i
development.
i 2.
To correst an obvious, nonnumerical typographical error in an approved procedure, see step 3 2.2 of this procedure.
3
-=====
i j
i i
15 e-e
,,,-n--
. ew r, -..
l Ad=inistrative Procedure MD-1 011 M2intenance Department Procedures - Develep=er.:,
Revision 2 Ocntrol and Distribut1*on 5 4.1 Originator - The originator shall complete the top of a Change / Revision / Deletion Request (Attachment 6.8) by entering the procedure number, procedure title and effective date (if applicable); entering the change number and the latest revision number of the procedure; writing a brief description of the reason for the change; and signing and dating the " Originator line.
a Blank spaces (e.g.,
- Effective Date" and " Deletion") sna11 be filled in with "N/A."
5 4.1.1 The Originator shall attach all pages affected by the change, including the c g44Y
" LIST OF ETTECTIVE PAGES" page. Changes may be entered as follows:
7 A.
Deletions may be made by a single line crossout or the deleted portion erased by means of xerography.
&V B.
Additicas and deletions shall be written with a black smearproof ink or tyg typed on the af fected page (if brief enough to be legible) or en addendum pages numbered (previous page no.)
-A, ~B, etc.
5 4.1.2 The originator shall draw a change bar in the right-hand margin next to each change and write " Change and the change nu=ber a
next to it.
The originator shall enter his initials anc the current date in the right margin basice the change bar.
54.13 The Originator shall mark up the L.iST OF EFFECTIVE PAGES to indicate which pages were affected by the enange.
An exa=ple follows:
LIST OF EFFECTIVE PAGES Title Revision 0 1-35 Revision 0 2, 8, 8A Change t 31, 33-35 Change 2 5 4.1.4 If the change will add or clear any missing inter =ation, tne Originator stall prepare a revised Missing Infer =ation List and attach it to the Change / Revision / Deletion Request.
5.u.2 Technical Review is as follows:
16 e
- -.. ~ _
Administrative Procedure MD-1 011 t
Maintenance Department Procedures - Development, Revision 2 Control and Distribution j
f NOTE The originator may have a temporary change i
reviewed by the Technical Reviewer as for a normal change; the temporary change review is designed to speed processing in immediate need situations.
5.4.2.1 Change. The Technical Reviewer shall perform and sign
" Technical Revieva on the Change / Revision / Deletion Request (completion of the Technical Review Checklist is not applicable to changes).
5 4.2.2 Temporary Change - The originator shall enter "NA* and his initials on the ' Technical Review" line.
543 Procedure Evaluation is as follows:
5431 Change. The Technical Reviewer shall perform and sign
" Procedure Evaluation" on the Change / Revision / Deletion Request.
i For any procedure evaluation question answerec "YES," he shall complete.a 10 CFR 50 59 Safety Evaluation per steps 5 2 3 3 (A and B) of this procedure.
5432 Temporary Change. The originator shall perform and sign
" Procedure Evaluation" on the Change / Revision / Deletion Request.
l For any procedure evaluation question answered "YES," he shall
[
complete a 10 CFR 50 59 Safety Evaluation per steps 5.2 3 3 ( A and.8) of this procedure.
5 4.4 QC Review is as follows:
5 4.4.1 Change - The originator shall submit the change package (consisting of the Change / Revision / Deletion Request; the at.
tached, marked-up procedure pages; a revised Missing Information List, if applicable; and a 10 CFR 50 59 Safety Evaluation, if 17 e
Admintstrative Procedure MD-1-011 Maintenance Departner.t Procedures - Develop =ent, Revision 2 Control and Distribution applicable) to the QC Engineer.
The QC Engineer or his designee shall review the change and sign on the "QC Review" line.
5 4.4.2 Temporary change - CC review is delayed until after the change has received temporary approval (step 5 4.6.2).
5.4.5 Department Head review is as follows:
M4 Y 5.4.5.1 Change - The Department Head shall review the change and sign the line on I
the Change / Revision / Deletion Request.
Y #M >
5.4.5.2 Temporary Change - Department Head review may be delayed until after the g
change has received temporary approval (step 5.4.6.2).
5.u.6 Approval is as follows:
5.4.6.1 Change - Following QC review, the change shall be forwarced to the Group Head.
The Group Head shall review and sign the itne on the Change / Revision /Delection Requ,est.
5 4.6.2 Tamporary change - The originator shall obtain temporary
( ,
approval signatures from a Nuclear Operations Supervisor (SRO if a plant operating license has been' issued) and the Maintenance Supervisor or Group / Department Head.
The Maintenance Supervisor or Group / Department Head approval can be obtained via telephone.
On the following work day, the Group Heac s, hall countersign the telephone authorization.
5.4 7 Procedure Change Distribution 5.4 7 1 Change - The department shall process the change package per section 5.6 with the following exceptions:
A.
A copy of the procedure change package shall te entered into all Controlled Copies of procacures.
The revised change pages shall replace preexisting pages.
B.
A copy of the Change / Revision / Deletion request form shall remain anead of the Title Page (arranged in descending-change-number or:er if previous changes have been entered).
5472 Temperary Change - The department shall docu=ent approval cf the temporary change in the Change Log for each procecure in the 18 e
L.-
Administrative Procedure MD-1-011 Maintenance Department Procedures - Development, Revision 2 l
Control and Distribution
^
l appropriate Field Controlled procedure file.
Additional processing shall be as per section 5.6 with the following ex-ceptions:
l A.
Place the entire Change / Revision / Deletion Request package in front j
of the procedure's Title Page.
Do not' replace preexisting pages i
with changed pages; this is only done following Group Head l
approval.
B.
If there have been previous changes to the procedure, the Change / Revision / Deletion Request packages will be arranged in descending-change-number order in front of the procedure's Title Page (e.g. Change 3, Change 2, Change 1).
C.
The department shall obtain,the QC Engineer, Department Head and l
Group Head approval within 14 days following the date of temporary approval.
The temporary change is then processed and distributed as for a change (step 5.4 7 1).
55 DELETION OF PROCEDURES 5. 5.1 - Nonapproved procedure - In the course of submitting input to the Procedure Status Report (PSR), the department may indicate the deletion of any nonapproved department proce'ure.
d 552 Approved procedure - Deletion of an approved department procedure requires the following review and approval process:
5.5 2.1 Originator - The originator completes the top of a Change / Revision / Deletion Request (Attachment 6.8) by entering the procedure number, procedure title and effective deletion date (if applicable); checking the " Deletion" Line; writing a brief description of the reason for the deletion; and signing and dating the " Originator" line.
The description shall include identification of any replacement procedures.
5.5 2.2 Technical Review - The Technical Reviewer reviews the procedure for the impact, if any, that its deletion would have on the 19
e Administrative Procedure MD-1-011 Maintenance Department Procedures - Development, Revision 2 Control and Distribution plant.
The Technical Review Checklist is not applicable, but Document Review Comments sheets (Attachment 6.6) may be attached.
He then signs-the " Technical Review" line on the Change / Revision / Deletion Request.
5.5.2 3 Safety Evaluation - The Technical Reviewer then completes the Safety Evaluation section of the Change / Revision / Deletion Request.
If the procedure's deletion would cause a "YES" answer to any one of the four Safety Evaluation questions, he completes and attaches the 10 CFR 50.59 Safety Evaluation (Attachment 6 5) per steps 5 2 3 3A and 5.2 3 3B of this procedure.
5 5.2.4 QC Review - The QC Engineer determines whether a quality assurance review is required.
Completion of the QC Review Checklist is not required, but any comments can be noted on Document Review Comments sheets (Attachment 6.6).
He then either signs the "QC Review" line on the Change / Revision /
Deletion Request form, or enters "NA" and his initials if review is not required.
5.5.2.5 Departrent Head Review - The Department Head may use Document Review Comments sheets to note any comments and shall submit any comments sheets to the Author for resolution.
In the event that the deletion request is accompanied by a Safety Evaluation, Plant Engineering shall evaluate any unreviewed safety question.
The Department Head shall indicate his approval by signing the " Department Head Approval" line.
5.5.2.6 Group Head Approval - If the Group Head approves the deletion l
request, he shall sign the " Group / Department Head Approval" line.
5527 Word Processing - The department shall submit a Procedure Report Revision Form (Attachment 6.4, UNT-1-002) to Word Processing so the procedure title will be removed from the POM Index.
20
=
Administrative Procedure MD-1-011 Maintenance Department Procedures - Develop =ent, Revision 2 8
Control and Distribu 1on 5.5.2.8 Departmental Processing - The department shall remove the procedure fres departmental binders and field files and cub it the deletion package to Central Records for the Historical Record File. A copy of the Deletion Request for= shall replace the deleted procedure in all controlled depart-mental procedure binders. Procedure numbers of deleted procedures shall not be re-used.
5.6 CONTROL AND DISTRIBUTION OF PROCEDURES l
zgAY 5.6.1 Each Department shall maintain complete sets (as necessary) of Controlled Departmental procedures and those POM and inter-departmental procedures 7
deemed necessary for proper Department operation. The Department shall
$ Dh.
maintain a listing of the current locations of these procedures on Attach-ment 6.12 of this procedure. The Depart =cne shall insert a copy of
- g.12 into the front of every Departmental Controlled Copy 9
binder and verify (by initialing the appropriate blank) that the binder contains the most recent version of the procedure no less than once every two years.
i 5.6.2 F.ach department shall maintain and issue Controlled Copies of departmental procedures for field use.
This responsibility may be i
p.
delegated to a Control Distribution I.ocation.
5.6 3 Field controlled copies shall be iss'ued for use where "in-handa procedures are to be used.
5.6 3 1 The name of the person holding Field Controlled copies shall be maintained for a period of not less than seven cays.
Within l
this se' van-day period, the issued procedure shall te returnec as required to post all updates-(i.e., changes, revisions, deletions) against the procedure.
5.6 3 2 Documentation that the Field Controlled Copy reflects tne latest approved version of the procedure shall be performed by comparing it to the departmental Master Copy of least once every seven days while in use and upon checkout.
This documentation -
shall be recorded on a copy of the Field control Copy Verifica-tion Form (Attachment 6.10).
This copy shall be inserted after the title page of the procedure.
j 5633 Field Controlled Copies shall be conspicuously icent fied on :ne title page as follows:
i 21
Administrative Procedure MD-1-011 Maintenance Department Procedures - Development, Revision 2 Control and Distribution FIELD CONTROLLED Catamped in red)
MUST BE RE-VERIFIED 7 DAYS FROM CHECEOUT DATE l
5 6.4 Departmental Controlled Copies shall not be written on or marked in any manner, except for typographical corrections, nor shall any portion be removed.
The procedure must remain intact to be considered a Controlled Copy.
5 6.5 A Change Log (Attachment 6.11) shall be established and maintained for each Field Controlled copy.
5.6.5.1 All changes, both permanent and temporary, affecting the Field -
Controlled procedure shall be posted in this log.
5 6.5 2 If there is no Field Controlled copy file for a procedure, then
-the Change Log will be maintained in the departmental Master Copy file.
5.6.6 The Department shall transmit the following to Central Records for Historical record storage:
5.6.6.1 Final POMC procedure print (also change packages, or handwritten approved procedures) 5.6.6.2 original signature pages for the following (as applicable):
A.
Title Page B.
Review Cover Sheet C.
Change / Revision / Deletion Request 5.6.6 3 Original QC Checklist 5.6.6.4 Document te
'#d#0F s.t.c.s TecAMc=/ biew Comments sheets
>=%
ut<-
C ha a 4 /s.r f 5.6.6 The Central Distribution Location will maintain a copy of the
"-'~F7 final POMC procedure print (as approved) which is to be designated 22 O
e
O e
Administrative Procedure MD-1-011 Mnintenance Department. Procedures - Development, Revision 2 Control and, Distribution as the departmental Master Copy.
The Central Distribution Loca-tion will use the Master Copy to provide Controlled / Uncontrolled Copies for departmental use as required.
6.0 19 curv s 6.1 New Procedure / Revision Flow Chart 6.2 Procedure change' Flow Chart 63 Missing Information List 6.4 Review Cover Sheet 6.5 10 CFR 50 59 Safety Evaluation 6.6 Document Review Commenta 67 Title Page (Approval Sheet)
.s
, ' 6.8 Change / Revision / Deletion Request C/4 AsG f l//r/[/g b6/
6.9 Technical Review Checklist [/re sa
- e.$ g [ g e
vra 6.10. Field Control Copy 7erification Fors r eg48 6f 6.11 Field Controlled Copy Change Los i
6.12 Controlled Copies (Locations and Verification)
- yOh g 70 co wrw ev s an or m e w s I
tal O
e l
l e
23
.-,,,.,-<,n,.-n.
,,,,,,,,.,,--n,..,,.~
NEW PROCEDURE /RE7!SION FLOW CHART DRAFT PREPARATION: Author TECHNICAL REVIEW: Technical Reviewer (s) l PROCEDURE EVALUATION:
R e
INCORPORATION OF COMMENTS: Author l
PROCESSING OF DRAFT: POMC QC REVIEW DEPARTMENT HEAD REVIEW PROCESSING OF COMMENTS: POMC APPROVAL: GROUP HEAD DISTRIBUTION: Department MD-1-011 Revision 2 24.1 (1 of 1)
I D
j 1
t PROCEDURE CHANGE FLOW CHART FREPARATION OF CHANGE: Originator
[ \\ emporary?
T NO TES V
TECW ICAL REVIEW:
TECW ICAL REVIEW: Originatos Technical Reviewer (s) ent.ar "N/A" PROCEDURE EVALUATION:
PROCEDURE EVALUATION:
Technical Reviewer (s)
Originator TEMPORARY APPROVAL: NOS (SRO INCORPORATION OF if plant operational) and COBSERTS: Originator Maintenance Supervisor or Group /Lepartment Baad.
QC EEVIEW DISTRIEUTION :
Department l
DEPARTMENT HEAD:
PERMANENT APPROVAL:
Q.C.
Review and Group / Department Head Review and Approval (within 14 days of temporary CROUP HEAD:
approval)
Review and Approval DISTRIBUTION:
Department MD-1-011 Revision 2 25.2 (1 of 1)
D MISSING INFORMATION LIST PROCEDURE TITLE; PROCEDURE NUMBER:
REVISION NUMBER:
CLEARED BY/DATE ITEM AFFECTED ITEM NLMBER PARAGRAPH DATE INITIALS l
l i
l l
ALL MISSING INFORMATION ON THIS LIST HAS BEEN CLEARED.
/
INITIALS /DATE MD-1-011 Rev'.sion 2 26.3 (1 of 1)
'4ATERFORD 3 SES DEPAP.DfEhdL FPEE::URE REVIEW COVER SHEEI PROCEDURE TYPE
!!TLE PROCEDURE EFFECTIVE DATE
(.If different from Group Head approval date)
AUTER TECWICAL REVIEW Signature, Technical Reviewer Date PROCEDURE EVALUATION Does this procedure:
1.
Change the facility as described in the FSAR?
YES NO
- 2.
Change the procedures as describei in the FSAR?
YES NO 3.
Conduct test /experi.nents not described in the FSAR?
YES NO 4
Croats a condition or conduct an operatica wui'ch TIS NO exceeds, or could result in w4ag, the limits in Technical Specification?
If any question 1 through 4 has been answered TIS, complete and attach a 10 CFR 50.59 S/FETT EVALUATION.
PROCEDURE EVALUATION Signature. Technical Reviewer Date QC REVIEW Signature. QC Engineer Date DEPARTMENT HEAD REVIEW Signature Date j
l MD-1-011 Revision 2 27.4 (1 of 1)
, ~ - - -,. -,
to CFR 50.59 3AFETT.7. 113AT :N Ftc 3 DURE 30.
TT.*_r CIARGE 80.
IET132D5 50-DMT TIE _ ED _
UEIE7:EVED SAFE:T Q5I32:05 1.
Will Me pretakuity of escarresse et an accident TE3 _ 30 _
l previously saleslated La the F341 he ineressed?
4 2.
Will Me,essaequeneca of as assident previsualy h NQ_
j evaluated La the FRAE be ineressed7 i
3 Will the prehability of malfumation of equipment TE3 _ 50 _
previously saleslated La Se FIAR he ineressed?
{
4.
Will the esaaequeness of a malfmeties' of
!!3_ NC_
ogstament ;.. 1 - 17 evalustad la the F541 he immremmed?
5.
Will me posaintlity to'areated for as sealdent h sc_
]
et a differest type than any previsualy evaluated La the FIAE7 6.
Will Me posaihuity be erested for a aalfaction
!!3 _ NC _
of a differest type than any previously evaluated La me F3417 Will the margia of safety as defined is us hasta TE3 _ NC _
'for any Teeksissa Spesificaties he redaced?
The bases and eriteria used ta determine t3at the proposed caanse does or does set involve as %sreviseed safety questions are attacaea to taia Safety Evaluatten.
- ECIIICal as,u.a sG M"T 31ssature 1c-1-011 Revision 2 28.5 (1 of 1) emmune sess em se
.e e
1 j
1 I
i DOCM REVIEW C0!@ENTS DOCUMENT No.
RI7./DRAF TWE RESET. 2 so.
COMMET RESOLUTION m.
4 i
i e
4
.1 4
I i
i 1.
Aaviewed Byt 2.
Co u nts Reviewed Sys Reviewer Date Author Date
- 3. Resolution af Causent's Accepted. By Reviewer Dace E-1-011 Revision 2 29 Attachmaat 6.6 (1 of 1) a.
--,~m,------.
y
-- -- -,,m,w-e--,--,
m-v---n-w
_nwgq_
.-~.,w
,wme~w--,m
---,-g,
,,,,---e,--w-.,,vaam,,-w
TITLE PAGE (APPROVAL SEC)
(procedure no.)
DEFA N FROCEDURE REVISION l
APPROVAL DATE EFFECTIVE DATE l
i (procedure type, all capitals)
(title, all capitals) l AFFROVED:
GROUP HEAD (or designee) SIGNATURE I
1 MD-1-011 Revision 2 30.7 (1 of 1)
~'
~ -. _
DEPAILTTAL PROCEDURE CHANGE / REVISION / DELETION REQUEST PROCDURE NO.
TITTr EFFECTIVE DATE (if different from Group Head approval datel PROCEDURE STATUS A.
Change Ib-R.
Revision No.
C.
Deletion 1
REASON FOR CHANGE REVISION. OR DELETION REVIEW SIGNATURES Originator Date Technical Review Date PROCEDURE EVAI.11ATION - Does this change, revision, or deletion:
ygs 30 1.
Change the facility as described in the FSAR?
2.
Change the procedures as described in the FSAR?
3.
Conduct tests / experiments not described in the FSAR?
4.
Create a condition or conduct an operation which exceeds or could result in exceeding, the limits in Technical Specification?
If the answer to any of the above is yes, complete and attach a 10 CTR 50.59 Safety Evaluation checklist.
PROCEDURE EVALUATION Date Q.C. Review Date Department Bead Date
_ TEMPORARY APPROVAL SIGNATURES
- NOS Date Maint. Super (or Group / Dept. Head)
Date
- Temporary approval must be followed by QC Review Department Head Review and Group Head Approval within 14 days.
PERMANENT AFFROVAL SIGNATURE (Channes/ Deletions Only - For Revisions, see Title Pa68)
Group Head Date MD-1-011 Revision 2 31.8 (1 of 1) 4 S
.,_-__.._m.,._._
_,y._.
_.m_.._
,,_._my..-,___
TECHNICAL REVIEW CHECKLIST PROCEDURE No.
TITLE REVISION No.
ISSTRUCTIONS FOR* TECHNICAL REVIEWER A.
This form is required for new procedures'and revisions.
It is not applicable to changes or deletions.
B.
If any of the checklist items cannot be verified with a "YES" answer, document each item on an attached Document Review Comment Sheet; and return to the author for resolution.
C.
Following resolution of comments, change the answer, initial and date and return this checklist to the Author.
No Technical Review Check-list with an unresolved "NO" answer should be submitted to the POMC.
YES NO l
1.
Can this procedure be performed in verbatim compliance j
and in the sequence listed?
2.
Is all the information necessary for procedure per-formance in the procedure or listed as a Reference?
3.
Are all necessary references readily available?
%j Il 4.
Are all necessary materials, test equipment, etc.,
listed in the procedure?
g 5.
Are.all steps clear and require no interpretation?
6.
Are the prerequisites / initial conditions sufficient?
l 7.
Do precautions or notes warn Operators of alarms to be received or equipment made inoperable during the procedure?
8.
Are plant systems / components properly restored and f
retested?
9.
Are all equipment numbers and/or nomenclature in the N
procedure identical to those displayed on the equip-ment or controls?
t 10.
Can all of the equipment / components in the procedure be o
easily located?
q 11.
Are applicable safety precautions included in the T
procedure?
h 12.
Does the procedure meet the requirements of the appli-cable codes, standards, regulatory guides, Technical Specifications, FSAR, ete?
13.
Does the procedure conform to the applicable procedure guidelines (pages 2 thru 8 of Attachment 6.9)?
14.
Is post-maintenance testing conducted in accordance with the applicable Technical Specifications and vendor and/or engineering recommendations?
i 15.
Is the procedure consistent with all Technical Specifi-cation limiting conditions for operation and applicable vendor-recommended operating limits?
TECHNICAL REVIEWER:
DATE:
KD-1-011 Revision 2 32.0 (1 a# mi
i PROCEDURE WRITING GUIDELINES l
l A.
GrurnAt i
1.
h procedura does not have the potential of involving an unrevisued safety question, as documented by "NO" answers to all Safety Evaluation questions on the attached Eaview Cover Sheet or Change /Bavision/ Deletion Esquest.
3.
FDEtic
)
i 1.
h procedure format is correct for the i
appropriate procedure type as described in n
m-t-oo2.
A n
2.
Me procedure categorization (e.g.,
b Surve111anca, Administzation, etc.) is correct per the requirements of M o02.
k PUIPOSE t'
1.
h purpose statement cleariv *_8-W*==
c) the ob.iective of the orocedure.
J' 2.
N Purpose statement clearly identifies the systems, subsystems, or equipment to which the procedure is applicable.
g 3.
REFERENCES 86 1.
All reference deciments are identified correctly, c
1 2.
All references identified are easily available I
to any individual who might be performing this k
procedure.
V I.
DEFIITTIONS 1.
Definicians are provided for all terms or phrases which have a special or limited --a4a when applied within the contest of the procedure.
MD-t-011 Eavision 2 33 At achment 6.9 (2 of 8)
PROCEDURE WRITING GUIDELINES F.
RESPONSI3MJ3 i
1.
Significant group and departmental interfaces associated with the conduct of the procedure are clearly idenified.
2.
Organizational and position cities and j
describtions are current and correct.
jg 1 4 3.
Rasconsibilities are clear and designate i
accountability and evaluation of tesults.
g 3
i G.
PRE 2ZQUISr!ES 1
3a FRE1EQUIS M section provides the individuals perforising the procedure enough information to preparly ly plan and whad'ila procedure performance, including:
q hY 1.
Other procedures which must be complaced prior to use.
2.
3a number and/or types of personnel required to y
perform the procedura.
I i
3.
All bulk materials, chemicals, solvents, bottled j
gases, etc. required during the conduct of the i b procedura.
o a.
Any required condition not associated with k
specific system or plant operatingconditions 3
(e.g., reactor vassal head installed, airlock g
inner door strong backs in place, blind flanges insta11ad, etc.)
V H.
PRECAUCONS AND LMATIONS 1.
All major. equipment operating precautions and 13mits recommended by the appropriate vendor manuals are included MD-1-011 Eavision 2 34.9 (3 of 8)
PROCEDURE 1.'RITING GUIDELINES 2.
Any unique personnel hasard unich any exist during the conduct of the procedure is iden-tified along with any personnel protective equipment required.
3.
Any procedural evolution which may introduce a significant probability of degrading nuclear, equipment, or personnel safety through a single 6
human or equipment failure is noted with an A
appropriate caution.
8h 4
Any entry into a Technical Specification action
(
statemer.c through removing components from ser-vice for testing, maintenance, etc. is noted.
5.
Controls are included to ensure that all ap-plicable c1===14===s requirements are satisfied per appropriate plant procedures / industry standards.
A I.
INITIAL CONDITIONS 1.
All plant or system operating conditions re-quired to be establised prior to the start of the procedure are identified. This includes
/
operational mode or =14 - c and operating parameters.
2.
All initial conditions associated with indi-(
cated process parameters have a colerance as-sociated with them (e.g., pressurizar pressure C
is 2150 t20 psig).
}
t 3.
Notification and authorization of the NOS to start the procedure is obtained and documented g
for any procedure affecting equipment or system d
availability, nuclear safety, capacity, or which will affect operating indications.
4.
Cross references to other procedures utilized to.
establish initi n operating modes or system con-figurations are correct (e.g., system in operation per section of 0F
).
i MD-1-011 Rev ion 2 35.9 (4 of 8)
i PROCEDURE WRITING GUIDELINES J.
MA m m AMD TEST EQUIPMENT 1.
All special tools or test equipment required to perfots the procedura are specified (by the ap-propriate part number and/or unique nomenclatura, if applicabla).
2.
Calibration requirements are specified for all special tools and/or test. equipment.
b i
3.
Adequate provisions exist when specifying the h
type of test equipment to be utilized to ensure that the appropriate ranges are specified and
(
chat required accuracias are obtained.
4.
All materials necessary to perform the procedura are adequately specified.
K.
ACCEPTANCE CLITEETA 1.
Source documentation for the development of ac-4 captance critaria is included in the REFERENCES fg section of the procedura.
2.
The acceptanas critaria provided are consistant with the values provided in the referenced g
source documentation.
3.
Verification of acceptance critaria is consis-cent with the stated purpose of the procedura.
b a
4 If a quantitative acceptance critation La based 1
on deviation from a design value, the acceptance T
criterion is stated as a range with an upper or 4
lower acceptance value, as appropriata.
O L.
PROCEDURE 1.
.The procedure =4=4=4*as radarences to other procedures and providas all instructional in-formation required to perform the activity.
2.
Rafarences to ochar proceduras specify the exact section, paragraph, page, or steps, as appropriata.
MD-1-011 Revision 2 36.9 (5 of 8)
PROCEDURE WRITING GUIDELINES 3.
Adequata provisions have been anda to provida necessary Quality Control hold and/or witness points.
4 Se procedura provides for verification and signoff of actions.
M b
5.
Individual steps are short, concisa, identi-i fiabla steps as opposed to multi-sentence paragraphs.
6.
Each step has the following provisions in-corporated:
a.
Each action to be taken is specifically identified.
g b.
Limits and serpoints are accurate and h
stated quantitatively with the proper p
units.
c.
It is clear which individual is to perform the sten.
7*
Warninas, cautions,ific steps or series of steps and nona soo11 cable e the performance of spec h14-hted, and placed imenadiately are accurata, h4t ahead of the step to be performed.
I,.
8.
All equipment', switches, controls, indications, V
or alarms requiring alignment are specifically g
identified using the approprince step (does not rafar to previous steps).
I k
- 10. The procedura is written so as to employ good g
i ALARA principles sad avoid unnecessary personnel exposure.
11.
If system components ars =14W in ochar than their as-found or normal operational alignment, tha procedura includes the following:
a.
Each item or component requiring realignment is individually specifind.-
b.
Each igen is correctly identified with a unique number or noaanclatura.
2fD-1-011 Eavision 2 37.9 (6 of 8)
--m,
, -, - ~, - -,
-n,n--,,., - - - - -, -,,
_a,
,,-,,,---ar,
,,-,,r--,,-,,-,,-~,,,,,,~,_-,,,-v1
,--,ee w-
4 9
PROCEDURE L'RITING GUIDELINES c.
h position or state to which the component is to be placed is clearly and correctly specified with a sigacff *a document restoration.
d.
If proper restoration of the component has
(
safety significance, double independent verification is provided with provisions for n
signoffs for each verification performed.
k
- 11. h procedure includes positive verification that applicable acceptance criteria have been satisfied and provides guidance for subsequent action to be taken in the event that 4.cceptance t'
criteria are not met.
k e
13.
h procedure can be performed in the sequence in wtLich it wea written.
14.
The procedure is consistant with all Tee w a=1 tJ Specification limiting conditions for operation and applicable vendor-recommended operating limits.
k, C
Q.
SEPOINTS k
1.
All seapoints. listed are provided with the proper = F = d.ng units.
k 2.
All.setpoints are consistent with values
\\/
1 provided in the latest source documentation.
R.
FINAL CONDITIONS 1
1.
All conditions whose existance indicates that
-the purpose of an Emergency Implementing Plan procedure or instruction has been fulfilled are list.d.
1 S.
Al" N l
1.
All illustrations, graphs, charts, cables,and I
con s cional formulas are accurate and app-repriate for their intended use.
MD-1-011 Revision 2 38.9 (7 of 8) 9
r
~
~
PROCEDURE WRITING GUIDELINES 2.
Data sheets have provisions for recording all data to be collected, the cima each data. set was recorded, idenity of the data recorder, and the n
process cr cast instrumentation used to obtain 4
the data.
j m
3.
Adequate identification is provided on each data sheet to idenify cast equipment used in the cast k
equipment control program.
All data sheets that involve computations provide adequate instructions for performance of
?
calculations and use of the data sheet.
h
?
5.
All
-=1_
1=Hanal results are provided with an independent verification for accuracy.
T.
CatefI2fENTS AED REFERL"CES 1.
All co d emants to NRC Ragulatory Guides or
(
NUREC documents are consistent with commit:nents made in the FSAL 0
k 2.
All commitments listed are applicable to the y
procedure.
g J
MD-1-011 Revision 2 39.9 (.8 of 8)
o I
FIELD CONTROL COPY VERIFICATION FORM Procedure Number:
Revision Number:
VERIFIED BY DATE VERIFIID BT DATE (sianatura)
(signature) 9 l
l l
l 1
i 1
1 l
l l
l l
l I
I I
i MD-1-Oll Rev. 2 40.10 (1 of 1) j e
)
I f
o Y
I B
S.
(
l D A 1
E I
1 R T E
I 6
T N N
I t
E nem hca t
t A
E T
T A
N D E
N L A
A M V R
O E
R P
P PA
.e ta d
l S
X
'U R) a P y v
A T
o P n l
A r
A a E
T p
S G
Yf p
N E
Ri a
A(
A C
R y
li N
C OE r
A E.
l PT a
I i
MA r
Y P
T C
ED o
O T
p I
C T
me D
t 1
E G
4 L
N f
L I
o O
T )y R
S s
n T
O y
a N
P a
O d
f C
EV (i 4
~
l 1
I'E I.
T l
E A
n T
I T A i
F N
h D
E t
T i
w den R
i O
a T
t A
b N
o I
G )
e R I T
b O R N
H O I
t T
R s
UE P
u AG
(
m NA l
H a
C vo 2
rp n
p o
a i
O s
N O
t i
N n
v E
e e
R N
n R
U O
a D
I m
E S
r l
- B C
I R
e l
O V
E P
O R
E S
P R
AM E
1 "U
T F
N O
I N
3 M
e 9
~ i l'
4 l
1
e 8
CONTROLLED COPIES (LOCATIONS AND VERIFICATION)
MAIFTENANCE DEPARTMENT CONTROLLED VOLUME LOCATIONS ELECTRICAL DEPARTMENT (Control Sta=p Number: 054-D,054) 1.
EMAPS Trailer 2.
Q.C. Department 3.
Central Distribution Location 4.
Electrical Shop Supervisor's Office 5.
Startup Location - Trailer 95 6.
INSTRUMENTATION AND CONTROL DEPARTMENT (Control Stamp Number:.054
)
1.
I & C Trailer 2.
Q.C. Department 3.
Central Distribution Location 4.
5.
M 6.
g g
MECHANICAL DEPARTMENT (Control Stamp Number:P29.P09.S47,054) to s
- 1. Mechanical Maintenance Trailer (2 cooles) b
- 2. Mechanical Maintenance mn 3,
Central Distribution Location 0
4.
5.
6.
N VOLUME VERIFICATION COPY LOCATION:
d VERIFIED AS MOST VOLUME DATE VOLUME DATE VERIFIED AS MOST UP-TO-DATE COPY UP-TO-DATE COPY NUMBER VERIFIED (INITIALS)
NUMBER VERIFIED (INITIALS)
MD-1-Oll Revision 2 42.12 (1 of 1)
.