ML20207A116
| ML20207A116 | |
| Person / Time | |
|---|---|
| Site: | 05000000, Comanche Peak |
| Issue date: | 11/13/1979 |
| From: | TEXAS UTILITIES ELECTRIC CO. (TU ELECTRIC) |
| To: | |
| Shared Package | |
| ML20206S800 | List:
|
| References | |
| FOIA-85-59 CP-QP-2.3, NUDOCS 8607110421 | |
| Download: ML20207A116 (11) | |
Text
.
("
i i
i PROCEDURE ISSUE l
REVISION PAGE NUMBER DATE TEXAS UTILITIES GENERATING CO CPSES F
"~
j l
1 1 of 5 j11_13_79 PREPARED BY:
QUALIFICATION OF M,
//.fc. 77 d
DATE SURVEILLANCE SPECIALISTS e,
APPROVED BY dds y g /cf DA E 4
i i
1.0 REFERENCES
4
'e b
1-A CP-QP-19.2, " Site Surveillance Procedure" 2.0 CENERAL The purpose of this procedure is to document the technical training requirements of Surveillance Specialists involved in activities prescribed by Reference 1-A.
The qualification program for surveillance specialists is designed to provide assurance that personnel have appropriate
- technical knowledge, skill and experience to properly perform the required sur-veillance functions.
Qualified personnel trained and certified by others will be considered for certification as CPSES QA Surveillance Specialists without additional training, on a case by case evaluation basis.
h
~; e m. %e n* M""i "h h gn 2
g, d 3
- 3. 0 PROCEDURE t
3.1 SURVEILLANCE SPECIALISTS Surveillance specialists should have experience in and shall have satisf actorily cempleted a training course in site and vendor /sub-contract surveillance functions.
3.1.1 Education and Experience i
i t
'o qualify for Surveillance Specialist training a person must have a high school education as a minimum and at least 2, years i
of experience in Nuclear QA/QC or equivalent. A d.>
re.
in i technical field from an accredited allege wi11 qua1 i!-
a per on without.the experience requirement.
8607110421 860627 PDR FOIA GARDE 85-59 PDR v
w
~BL o a
i i
4 l
- -- TUGCO O A F or m *v.
I' PROCEOURE ISSUE REVISION P A G '~C i
NUMBER DATE TEXAS UTILITIES GENERATING CO.
11-13-79 2 of 3 E
3.1.2 Surveillance Functions Surveillance functions may include, but are not limited to i
the following:
(a)
Planning, performing and documenting surveillances of TUGCO, Contractor, Sub-Contractor and Vendor Quality Assurance Programs.
(b) Performing follow-up and corrective action verification functions related to surveil-lance deficiencies.
3.1.3 Trainine and Examination Surveillance Specialists shall have knowledge and skill to adequately perform their assigned tasks. The following shall be used as a guide for training and examination of Surveillance Specialists:
1.
ANSI N 45.2 3.
FSAR, Section 17 4.
CPSES Engineering Specifications 5.
CPSES Construction Procedures 6.
CPSES QA Program / Procedures / Instructions l
i 7.
Vendor QA Programs 8.
Contractor /Sub-Contractor QA Programs 9.
Checklists and Reports used to plan, perform and document site and vendor audit /surveillances.
In addition, the trainee shall witness a minimum of E site surveillances conducted by a qualified surveillance specilist prior to certification for conducting a site surveillance.
In addition to witnessing ] site surveillances, the trainee shall witness a minimum of 1 vendor /subcontrac tor surveillance conducted by a qualified surveillance specialist prior to certification for conducting a vendor / subcontractor survei'.-
lance.
3.2 TRAINING DOCUMENTATION Qualification cf surveillance specialista shall be documented in accordance with Figure 1.
In addition surveillance spec talists shall camplete the Surveillance Specialist Technical Outline (Figure 2) withir j
30 working days after assignment to the QA Site Surveillance l
I Croup.
L_ _. _ _ _ _.
ro m m
__, s,, m N, i
i I
l i
i PROCEDURE ISSUE i
REVISION PAGE NUMBER DATE TEXAS UTILITIES GENERATING CO.
CPSES I
i
[
l 11-13-79 i
3 of 5 3.3 TRAINING CERTIFICATION A copy of the Surveillance Certification form (Figure 1),
when completed, will be placed in individual file for each employee.
e 5
t 4
e i
j l
i i
I I
I i
l i
i I
l l
b n 7- -- --.
ronca e-s J
i_ _...
J t
l PROCEDURE ISSUE l
REVISION PAGE i
I NUMBER DATE
+
TEXAS UTILITIES GENERATING CO.
CFSES l
1 11-13-79 l
I0 i
l 1
i FIGURE 1 1
4 1
1 6
TFJtA9 t; Tit,t TIES f.T% FF ATINT. CC? IPA!!Y
't f
6t'AL.!TT AbtPP.tn f
- Fa kMNT 5uvrt t.tANCE C'
- 0A" Tm I
- t. *.'if.
__., _ DATE:
e LM I, UP (F 6 7 [ F(vgllii*!!
)
f
,n:rrvin etnTit irs m rr:w-1 1
~~
f ka
.I8 h N 'I k h.'
h ! k 9 k N ! k. ' 0 '*#.
k5 T) Pi' t'h' t Wi!." O *. t 1. 6 D_
WP.!?TTN fAACTICAL f
l i
I c i.t n> rveir.o :
cs i
i h
Lt. '"U.?.Th 3 j
I t
1 l
I e
I I
I M H.
MMM e.nh
____h
.h.
=-
l
. -. ~.....
k i
j i
^<
. -.,, _ -... +. ~..
t I
i
,r... _
]
s ro
-r j
t i
i I
j e.i.--
)
i i
f
)
i 1
i I
l f
I 9
i i
__ -~.,_.- -
~
+
IllOCh C4 -'-* ~ '^ '~ ~
+
i e
s.
.. 9
=
...a l
I PROCEDURE ISSUE REVISION PAGE NUMBER DATE TEXAS UTILITIES GENERATING CO.
._. _ _]
11-13-79 3 of i FIGURE 2 SITE StlRVEf t.I.ANCE TEC10lICAL CUT!.!!!E NAME DATE CCM)ENCC i
j Read and discuss the following standards / procedures /instructicas with '
Designated Surveillance Group Leader.
A.
10CTR 50, Ap;endL* 8. " Nuclear Quality Assurance" i
Trale,e s / Da te Group Leader /Cate 1
8.
A!!31 Nf.5.2, Cuality Assurance Program Require:sents for Nuclear l
Power Plants" i
i Trainee /Date vroup Leader /;; ate C.
CPSES Final Safety Analysis Report. Section 17 Tratsee/Date Group Leader /Cate D.
CP-QP-19.2, "$ tte Surveillance Procedure".'
l Traineergate Group Leider/Date S
E.
CPMP-16.1, "$1gnificant Construction Deficiencies" l
Trat=eesDate Group Loa <ter/J.ste SITE SRVEILLNICE SUPERVIGOR INTERVII'J
+
Cate
$LF.Jtute s
i rooco m i
DQI -ST-3.1 Riv. O TEXAS UTII.ITIES GENERATING CO Page 4 ot 3
- 7. ' 'k AD.f!?lA1 STARTUP/ TURNOVER SURVEILI> lice L I : t.a14..
T2 -
vsu I
T DEFICIENCY NO.
api;L SURV REPORT
,Usk ST5 DR. -ct O ACTIVITT REFERENCE DOCUMENT DATE REPORTED CASES S PGCa si L c A? DG q 0 9 5 AlfTIO N b 3 l/ 7 ~J
/
.5 C - E3 C 6 7 DESCRIPTION OF DEFICIENCY Qp 3 - t f - S' 3, W bn-a in t' wsedYdY lC
?.~2 $.v e nrk
~
y 7%yedMf.9ugCAY S sk in s,&;{---
yfert y N.0 k vs &
S y
i Aff' C 5' eY f O C Cb ' A C, M fi' u 19 e Cf=
4 /v T
I 0
N A
RE70RTED BY REPORTED TO STS SUPERVISOR APPROVAL DUE DATE
['inc. I M D. %e,z nek Pa cfy
)!
3 -g. g 3 DISFCSITION/ CORRECTIVE ACTION DEFICIENCY NO. STS-DR-83-010.
DISPOSITION /CORRICTIV::
ACTION. Operations Depart =ent personnel erroneously assu=ed that, as a result of discussions between the Hot Functional Test Director and the Operations Superintendent, S
the startup testing activity in question had been defined in the EFT procedure. Io E
prevent recurrence, a meeting of all Shift Supervisors, the Operations Supervisor, and C
the Operations Super 1ntendent was held on 3/21/83 to discuss the use of procedures, T
this deficiency, and other related deficiencies.
The attached was provided by TUGCo I
Operations Q.A. and was made available to all Operations Department personnel.
O N
3 CCMPLETED BY DATE REVIEWED BY DAIZ
'O
/
R. B. Seidel 3/2?/83
/
,d% ~
_~' d 2,O C,
a CORRECTIVE ACTION VERIFICATION S
E f(
k?
r*
- ~w-p,
'A I
f N
)
C VERIFICATION SY DATE STS SUPERVISOR CLOSE0CI DM; i
..'s QUALITY A%\\PINESS Procedures and Instructions March 1983 Of c11 the problems associated with building and operating a nuclear power plane, procedures or the failure to follow procedures creates the biggest.
The Code of Fcdcral Regulations requires that procedures be used to conduct activities at nuclear power plants.and that these. procedures be followed.
The activities include cil activities where there is a possibility of.'an error which could cause an accident.
Three procedures must be followed word for word or the procedure must be changed.
In any event, the procedure and any change must be properly approved prior to its us3.
Thore are many reasons for procedures and cc=pliance to these procedures. Listed b low are a fev:
A.
Procedures are just good business.
In preparation of procedures we look for the best method available to perfor= the task.
These methods take into account all the regulations and require =ents i= posed on nuclear power plants.
B.
Not following procedures can cause reduced public confidence in nuclear power in general and specifically in Texas Utilities as a company.
If we are violating procedures and this is observed by an N.R.C. inspector, it is written in his report which becc=es a public docu=ent.
The public docu=ents are oftan reviewed by the news =edia and can be the subject of a news report.
All the thousands of ti=es we follow procedures is not discussed but only the ti=es where procedures are not followed.
This can be only one individual out of hundreds not following his procedure.
C.
Not following procedures can and often does create unsafe plant conditions which could cause injury or death to a plant a=ployee and equip =ent da= age.
D.
In nuclear power, procedures are required and cust be followed.
This company can be fined bv the Nuclear Regulatorv Cec =ission for failure to follow procedures.
This fine can be in the six figure range.
In su==ary, procedures are as =uch a part of the job as your tools and equip =ent and like the=, cust be used correctly to be effective.
Re=e=ber, procedures are required and nust be followed exactly.
If you should find a proble= with a procedure while using it, contact your superviser, but do not centinue until the proper procedure change has been made.
STARTUP/ TURNOVER SURVEILLANCE APPL SURV REPORT DEFICIENCY NO.
U/A STS-DR-83-011 ACTIVITY REFEPINCE DOCUMENT DATE REPORTED Operations STA-207, Revision 1 03/21/83 DESCRIPTION OF DEFICIENCY S
On March 10, 1983, Special Order No. 1-50-83-006, Revision 1 was approved E
and issued in violation of paragraph 4.3.9.
C T
I O
N A
REPORT Y
REPORTED TO STS SUPERVISOR APPROVAL DUE DATE f
- N -
R. A. Jones 03/28/83 DISPOSITION / CORRECTIVE ACTION DEFICIENCY No. STS-DR-83-011, DISPOSITION / CORRECTIVE ACTION 3
The violation of STA-207, Rev. 1, Paragraph 4.3.9, represents an error en the part of the Operations Superintendent.
Special Order No. 1-50-83-006, Revision 1, C
will be cancelled in accordance with STA-207, Paragraph 4.3.8.
I I
O N
B CCMPLETED BY DATE REVIE'JED BY DATE
/
/
/
A R. B. Seidel 3/24/83
/
,j o
/L.
/
-.;=', @ 9V' G CORRECTIVE ACTION VERIFICATION S
E C
T I
( ' ',
kl i l'(
i j
h,s C
VERIFICATION BY DATE STS SUPERVISOR C:.0SECUT DA E
^
l Rav. O TEXAS UTILITIES GENERATING CO Page 4 of $
STARTUP/ TURNOVER SURVEII. LANCE
.).
I I
DEFICIENCY NO.
REPORT N/A STS-DR-83-012 ACTIVITT REFERENCE DOCUMENT DATE REPORTED 1CP-PT-37-01, Revision 0 CP-SAP-21, Revision 1 03/25/63 DESCRIPTION OF DEFICIENCY Loop calibration 1-F-2456 and 1-F-2457 were verified completed es prerequisites in g
Table II of ICP-PT-37-01 (items FI-2456A, FD-2456 FI-2457A and,FD-2457A).
E Neither Special Prerequisite Test Results nor Channel Calibration For= 205 documen-C cati n could be located in the PPRV to indicate loop calibration had been satisfac-I torily performed.
g O
This is a violation of paragraph 4.9.11 of the referenced document.
N A
REPORTED SY REPORTED TO STS SUPERVISGR APPROVAL DUE DATE B. Cowan 04/01/83
[p [
DISPOSITIONAEORRECTIVE ACTION SEE MMNED S
E C
T I
O N
B DATE CCMPLETED BY DATI REVII'JED BY f,/m/
Of 4-/-Y3
-/,9 /c v
~m
/-
CORRECTIVE ACTION VERIFICATION S
E f~,..
C
- 4 4
1
- J T
f
,.(
o C
VERIFICATICN BY DATE STS SUPERVISOR.CLOSE0GT CAIE 4
- 1. is a copy of the subject Table II.
The set point and range in question are substantiated by attach =ents 2 and 3, both of which are in records.
It should be noted that a TDR was initi-ated because of the discrepancy between the procedures and actual installation.
2.
The system STE was notified of the above discrepancy prior to sign-ing the Table II.
Following further discussion a decision was made to perform the pre-requisite' tests again. This ti=e the affected l
dada sheets were to be changed via TPD's.
As noced in attachment 4 the as found valves were within the required tolerances.
3.
The data packages for 1CP-ST-4416 and 4418 have not been submitted to ARMS pending the I&C Engineer's final review. They are presently available in the I&C Engineer's office.
4.
There was no, violation of paragraph 4.9.11 of CP-SAP-21.
e e
8
i%uu QO S-asettr---
TEXAS UTILITIES GENERATING COMI%h"(
OFFICE 31E3f 0R A ND U31 March 23, 1983 Tony Vega G..en Rose. Texas Ta_
Surveillance of Startup Activities Subject ATTE:TDEES:
R. A. Jones J. T. Merritt C. H. Welch T
D. E. Deviney To better define the surveillance responsibilities and deficiency reporting responsibilities, a meeting was held with the following results:
Startup/ Turnover Surveillance personnel will perform surveillance 1.
of startup activities, including support activities perfor=ed under the Startup Quality Assurance Program.
Example:
If a P.T. procedure references steps of an operational procedure (i.e., SOP), these steps will have surveillance performed by Startup surveillance personnel as appropriate.
Exanple:
If a Maintenance Action Request is generated by Startup, Operations Quality Assurance will perform surveillance of this acitvity as appropriate.
To expedite resolution of-deficiencies involving actions by :uclear 2.
Operations personnel (i.e., failure to follow procedures), these deficicncies will be brought to the attention of the Manager, Plant All other deficiencies (i.e., progra:tatic) shall be Operations.
brought to the attention of the Manager, CPSES Startup for resolution.
Other problems which are identified and not directly associated with 3.
a Startup procedure will be brcught to the attention of the responsible Quality Assurance Organi:stien for resolution as appropriate.
O oE0 MV bg Should you have questionc, please advise.
M2 Ch GP6a Tr4 ec '5s p <
L TNe d g 3
/
/
'/
C4 AC
//--.
/
sM - ^ '
L VSR'S,&
c
,h,/
i v ?,
r Cea MT CPdrfk.
i (_
~
R.' A. Joney f
W 3J v' ~
Oh
~
R.U, XD/ebj
- U*27 CM k
cc:
- 3. R. Cle:enta Q Lu, /g l(
J. C. Kuykendall l~ MM __
~*
w D. N. Charman Q
~
1__.
R. G. Tolnen AR:t m
~
CPSES STARTUP ADMINISTRATIVE PROCEDURE
'CP-SAP-3 I
CUSTODY TRANSFER OF STATION COMPONENTS
}
N Revision:
12 i
Prepared By:
R.
E. Cano I
W Reviewed By:
ead St r.cp Engineer Reviewed By:
M t
TUGC0 QA '> Ear:up/ Turnover Surveillance Supervisor l.
Reviewed By:
<d
Title:
Oll? E L. 4 0 M, -
Reviewed By:
d'.
Title:
f
!"3 Approved 3y:
4 Date:
Ma sger.' CPSIS S car:u c.
h.I r
If f dd c k'/C ).1 c C om, y_.ayg_ M HORME08 CNLii
CP-SAP-3 Revision 12 Page 2 ef 15 TABLE OF CONTENTS SECTION TITLE PAGE COVER SHEET 1
TABLE OF CONTENTS 2
1.0 PURPOSE 3
2.0 APPLICABILITY 3
3.0 DEFINITIONS 3
4.0 PROCEDURE 4
4.1 PREPARATION FOR TURNOVER 4
4.1.1 Test Release Boundary Definition 4
4.1.2 Assembly & Distribution of Test Releaso Packages 5
4.1.3 Pre-Turnover System Walkdowns
& Punchlists 5
4.2 CUSTODY TRANSFER OF EQUIPMENT FROM CONSTRUCTION TO TUCCO 5
4.3 CONTROL OF TEST RELEASE AND POST-TEST RELEASE DEFICIENCIES 8
4.4 ADDITION OF COMPONENTS AFTER TEST RELEASE ACCEPTANCE 8
4.5 EQUIPMENT MAINTENANCE AFTER TEST RELEASE ACCEPTANCE 8
4.6 CUSTCDY TRANSFER OF EQUIPMENT FROM TUGC0 TO CONSTRUCTION 8
4.7 TRANSFER OF OPERATIONAL CONTROL FROM STARTUP TO OPERATIONS LO
5.0 REFERENCES
11 6.0 AITACHMENTS 12 G
F 3 ! : !" L b, i t a c : s f < td L a
CP-SAP-3 Revision 12 P2ge 3 cf 15 Interim Change 02/08/8l.
CUSTODY TRRISFER OF STATION COMPONENTS 1.0 PURPOSE The purpose of this pr,oc,edure is to establish the requirements and responsibilities for transferring,cu_stody..of, components,.. partial subsyste=s,
..subsys,tems,,,gr_sy,s,temsj rom;,B.rgwn & Root or other. subcontractors to TUG 00 for y r,f,ormanca.of.Startup, testing,;;,TUGC,0jto Brown-&-Roor or other j
subcontractors.for rework or-modificationg 'a' rid'Yslease 'of 'operationali c
~
'c^ontrol from TUGCO-Startup to 0'p'er'atio'nE f ~
[
~
2.0 APPLICABILITY The requirements of this procedure apply to the organizatior responsibilities and interface activities of B&R, TUSIk nd TUGC0 for release or turnover of all components and systems of CPSES Units 1 and 2.
Physical plant areas and/or structures will be released from construction p.
to Startup in accordance with this procedure, however test release packages will not be prepared.
Internal B&R and/or TUGC0 QA procedures for processing release of turnover packages or identification and tracking of record deficiencies are not described herein.
Note Control of work on compon.ints after custody transfer will be in accordance with CP-SAP-6 or custody of the component will be returned to the contractor in accordance with paragraph 4.6 of this procedure.
3.0 DEFINITIONS Acceptance Tests - Tests conducted on non-safety related statica systems to demcnstrate their ability to satisfactorily perform their design function.
Preoperational Tests -
Tests conducted prior to fuel leading to demonstrate the capability of ecmponents, syste:s or structures to meet safety-related performance requirements.
Prerequisite Tests - Tests forformed on individual components te verify complete installation, operability, cleanliness, calibration, etc.
Also referred to as checkout or initial checkout, ib=lfdYA111L Uul(l a i.
'ti e
% =
=
=,
qd...
i
CP-SAP-3 Revision 12 Page 4 of 15 Interin Change 02/08/84 Special Performance Test -
Test conducted to demonstrate component / system performance, collect operating data or to control special testing activities.
Results of Special Performance Tests will not be used to comply with test committments in the Final Safety Analysis Report.
Documentation - Any written or pictorial information describing, defining, specifying, reporting or certifying activities, requirements, procedures or results.
The transfer of component, partial subsystem, Test Release (Turnover) subsystem or system custody from the contractor to TUGC0 for the purpose of functional testing. Test release and turnover are synonymous.
{' Custody} -[Immediate authority and responsibility for operational control.'
Test Release Deficienc') -
Condition of construction ince=pleteness at the time custody of a component, subsystem or system is released to TUGCO.
Partial Subsystem - All ccuponents of the same type in a subsystem, i.e.,
all electrical equipment and associated cables, all instrumentation, all piping, etc.
Subsystem - A grouping of components combined to perform a single function.
System - A grouping of subsystems united by some inter-action er interdependance performing many functions as a single unit.
STE A.S'ystem Test Engiiteer
/
Master Data Base -l Management information system which is a ccmputeri::ed punchlist of outstanding work on components, syste=s and/or structures.
/
4.0 PROCEDURE 4.I PREPARATION FOR TURNOVER 4.1.1 Test Release Boundarv Definition The TUCC0 Startup group is responsible for the determination of subsysten turnover boundaries as required to schedule and perform startup testing activitics on project drawings such as flow and auxiliary one-line diagrams.
These diagrams will be marked-up to clearly indicate the turncver boundaries.
i l
i tM
CP-SAP-3 L
i Revision 12 i
Page 5 of 15 l'
4.1.2 Assembly and Distribution of Test Release Packages The Completions Group Manager shall be responsible for assembly l
of turnover packages consisting of equipment, valve, piping and
)
instrument lists and drawings such as flow, instrumentation and control and auxiliary one-line diagrams as required to sufficiently describe the content and boundaries of the turnover. Turnover packages shall be distributed to TUGC0-Startup and other project groups for their information and use 2
to support turnover activities.
}
c 4.1.3 Pre-Turnover System Walkdowns and Punchlists
(
The Completions Group Manager shall be responsible for coordinating all required pre-turnover walkdowns by Construction, Engineering and Quality Assurance.and punchlist J
activities for the purpose of establishing the status of remaining construction work and expediting completion of that work prior to releasing custody to TUGCO.
Approximately six (6) to eight (8) weeks prior to a carget turnover date, or when assigned, startup personnel will conduct
[_
periodic walkdowns within the turnover boundaries and compile i
punchlists of uncompleted work, missing components and/or l,
damaged equipment. These punchlists are intended to be an aid to construction during the turnover process and will be forwarded to the Completion Group Manager for work coordination.
i.
i 4.2 CUSTODY TRANSFER OF EQUIPMENT FROM CONSTRUCTION TO TCGC0 1
i The test release process described below will allow the custody transfer of individual components, a partial subsystem (i.e. all j
instrumentation for a specific subsystem), a complete subsystec (i.e.
j all electrical, instrumentation and mechanical components of a pre-defined subsystem), or a complete system from. construction to i
l TUCCO.
j 4.2.1 The Ccmpletions Group Manager shall be responsible for initiating and processing Test Releases (TR's), using the TR form shown as Attachment A, censistent with establish.td j
schedules and as requested by TUCCO startup as follews:
i j
4.2.1.1 Identify the Unit, System Title and Startup System Number.
4.2.1.2 Assign a TR number coded to identify the system, subsystem and sequential transfer number fer the i
specific subsystem.
i i
d 7) l
.h
a f,
- 'l Revision 12 Page 6 of 15 Ex pie:
0401.3 This TR number indicates that it is the third (.3) TR issued for release of equipment from B&R to TUGC0 for the y
service water system (04), subsystem t
/h (01).
-> 4.2.1.3 Indicate the scope of the test release (i.e. component, I
n' p%Feial subsystem, etc.) in the space provided.
t 3' s,
Notes A
3
, x a'
'(1) If the TR is for the release of i
/
_ a component, describe the component and associated equipment using equip-
' ment piece numbers and/or descriptive 2, %,
%'\\
terminology in the space provided.
4 4
i
.. g
'y c~",
Example:
Condensate Pump Motors - CPI-COAPCP-01
- ' % v and CP1-C0APCP-02 and associated power supply breakers 1A3 cubicle 6 and 1A4 cubicle 6 and associated power and control cables NK-12345, NK-678910 and s
NK-45321, etc.
4 (2) If the 14 is for a partial subsystem, list
)",,
the components being released and attach
x i.
to TR form or attach the applicable portion
'i C
of the test release package to TR form.
s y
~?"*
(3) If the TR is for the release of a complete subsystem, or system, attach a copy of the i
N subsystem test release package (s) to the TR
,,,,l form.
[
4.2.1.4 Attach latest revision full size flev diagrams and/or
.one-line diagra=s and applicable design change documents, marked-up to define the test release boundaries to the TR.
j i
4.2II.5 List test release deficiencies, including design changes that have not been implemented by constructi n,
/\\
i.open non-conformance reports and inccmplete 4,*- '
l.
construction work.
Include clarifying status of
[
defittencies such as; procure =ent document number and l
L delivery date for missing materials, estimated completion date and organization, department or t, W. R'
' individual responsible for clearing the deficiency.
r, s
u t
s l
4.2.1.6 Signify custody transfer of the components contained a'
within the turnover boundaries to TUGC0 in the space
~
provided.
\\..
i i
l
\\[
,e v
=
CP-SAP-3 Revisien 12 Page 7 cf 15 Interim Change 02/08/51 Note For TR's including electrical equipment the electrical super-intendent shall signify his agreement with the TR in space provided on TR form.
4.2.1.7 Forward the TR and all attachments to TUGC0 Startup.
4.2.2 TUGC0 Startup shall be responsibl'e for processing.the test release as follows:
4.2.2.1'Startup personnel shall review the package and perfer a walkdown inspection using the guidelines provided by CP-SAP-20, to determine if the components identified in the TR package are ready to transfer.
Any additional construction deficiencies, requiring resolution prior to accepting the turnover, shall be brought to the attention of the Completions /Startup Support Group Supervisor for corrective action. Deficiencies not requiring resolution prior to test release acceptance c
shall be added to the Master Data Base.
If the necessary corrective action cannot be taken on those deficiencies or if the test release is rejected, the entire test release package will be returned to the Completions /Startup Support Group Supervisor stating the reason (s) the test release is being rejected.
4.2.2.2 Upon completion of the Startup walkdown inspection and correction of deficiencies as required by Startup, the assigned Startup Engineer and Lead Startup Engineer will signify custody acceptance of components specified by the test release package in the space provided on the TR form.
4.2.2.3 Upon custody acceptance of the Test Release, TUGC0 custody tags shall be placed in accordance with CP-SAP-4.
4.2.2.4 The TUCC0 Startup group secretary shall ensur'e that the accepted test release package is filed in the appropriate startup system file and copies of the TR are distributed to the individuals listed on the TR form.
Note After custedy acceptance, assigned 1
startup personnel will be respons-ible for coordinating work and conducting test activities on com-ponents within the TR.bcundaries in accordance with applicable Startup Administrative Procedures.
I b
CP-SAP-3 Revisien 12 s
4 Page 8 Of 15 Interi= Change 02/08/c' 4.3 CONTROL 0F TEST RELEASE AND POST-TEST RELEASE DEFICIENCIES 4.3.
The Completions /Startup Support Group Supervisor shall ensure that Hll Test Release deficiencies are entered into the Master
~'
47 Data Base upen acceptance of the associated Test Release by TUGCO Startup.
IS
'4.3.2 The STE shall be res onsible for ensuring that incomplete
['c'HEEishtion: work'id ntified by Startup af ter acceptance of a o
test release is entered on the Master Data Base.
l 4.4 ADDITION OF COMPONENTS AFTER TEST RELEASE ACCEPTANCE s
4.4.1 If the need arises to add components to a test release package within the boundaries of a Test Release that has already been accepted by TUGCO, a TR form, Attachment A, shall be processed by the Completions /Startup Support Group Supervisor as follevs:
4.4.1.1 Identify the Unit, System Title and Startup System Number on the form.
1 4.4.1.2 Process the test release package as specified by paragraphs 4.2.1.2. through 4.2.1.7.
4.4.2 Upon receipt of a test release package, TUGC0 Startup will process the package as specified by paragraph 4.2.2.1. through l
4.2.2.4.
4.5 EQUIPMENT MAINTENANCE AFTER TEST RELEASE ACCEPTANCE 4.5.1 The TUGC0 Maintenance Depart =ent shall be responsible for preventative maintenance of permanent plant equipment after acceptance of custody by TUCC0 Startup, j
4.5.2 When required, corrective maintenance cill be performed by the i
TUGC0 Maintenance Department or by the appropriate vendor er contractor in accordance with CP-SAP-6.
4.5.3 Startup personnel shall be cognizant of equipment storage requirements and coordinate with TUGC0 Maintenance Departmen:
personnel to ensure that equipment is properly stored.
I 4.6 CUSTCDY TRANSFER OF EQUIPMENT FROM TUCCO TO CONSTRUCTION i
Custody of station ecmponents may be returned to construction from TUCCO for perfortance of work such as; major modifications, repair er clearing of construction deficiencies, when determined necessary by the Lead Startup Engineer. The assigned STE shall implement the transfer as follcws:
4 4
ER INFORMAil0E DMi.?.
CP-SAP-3 Revision 12 Page 9 of 15 Notes (1) Return of component custody to f
the contractor will void all
/f.s
~~
previous startup testing per-formed on the components.
(2) If operational control of the equipment has been transferred
-to TUGC0 Cperations as described in paragraph 4.7, the STE shall coordinate the transfer with the Operations Superintendent or Operations Engineer.
Complete the required information in paragraphs A, B and C on 4.6.1
+
the Return to Contractor Custody (RTCC) form, shown as Attachment B, and forward the form to the Lead Startup Engineer for approval.
Note If safety tags are required, they shall be placed in accor-i dance with CP-SAP-5 or STA-605 and a copy of the clearance at-eached to the RTCC form prior to j
submittal to the Lead Startup Engineer.
4.6.2 After the Lead Startup Engineer has reviewed and approved the fid '
p transfer, the RICC will be sequentially numbered, logged,
~~
distributed to the individuals listed on the RTCC form.
4.6.3 After approval of the transfer, the STE shall remove all TUGC0 custody tags from the equipment being transferred.
Note l
While equipment is in the Cus-tody of construction; (a) per-manent plant equipment shall be operated only as directed by the STE.
(b) all work performed shall adhere to the quality con-trol / assurance requirements specified for the original in-stallation.
f
.y
.\\
l 2
CP-SAP-3 Revision 12 Page 10 of 15
-Interim Change 02/08/81 4.6.4 Upon receipt of a RTCC, the Completions /Startup Support Group Supervisor shall coordinate construction activities as required to complete the work specified by the RTCC.
4.6.5 Upon completion of the work, the Completions /Startup Support Group Supervisor shall complete paragraph D of the RTCC and return the RTCC and all attachments to the Lead Startup Engineer.
4.6.6 Upon receipt of a completed RTCC, the assigned STF shall review any outstanding deficiencies and perform a walkdown inspectica j
using the guidelines provided by CP-SAP-20 to determine if the i
components affected by the RTCC are ready to transfer.
Upon satisfactory completion of his review and inspection, the STE shall. signify custody acceptance of the components in paragraph E of the RTCC form and forward the RTCC to the Lead Startup Engineer for final acceptance.
l Note If custody is accepted with deficiencies, the deficiencies will be entered on the Master yc Data Base.
4.6.7 Upon final acceptance by the Lead Startup Engineer, custody tags / stickers shall be placed in accordance with CP-SAP-4.
4.6.8 Completed RTCC's shall be closed in the RTCC Log and distributed to the individuals listed on the RTCC form.
4.7 TRANSFER OF OPERATIONAL CONTROL FROM STARTUP TO OPERATIONS After appropriate prerequisite tests, including initial operation of station equipment has been completed, the STE will relinquish operational control of the equipment to TUGC0 operations as follows:
4.7.1 The STE shall initiate a Startup Release to Operations, see Attachment C, and forward the Release to the Lead Startup Engineer for release approval.
Notes (1) Drawings and/or equipment list should be attached to *.he re-lease as required for clarifi-cation of boundaries, etc.
FOR MORMATTON UNif.
--y-
,--m___,-
,-.v
CP-SAP-3 Revision 12 Page 11'of 15 Interim Change 02/08/84 (2) All safety tags, placed in ac-cordance with CP-SAP-5, that are still needed on equipment being transferred to TUGC0 Operations, shall be replaced with safety tagging in accordance with Station Administrative Procedure STA-605, All other safety tags within the system turnover boundary placed in accordance with CP-SAP-5 shall be removed.
Replacement / removal,of all safety tagging shall be veri-fied by the STE on the Startup Release to Operations form.
4.7.2 Upon approval, the release will be forwarded to the TUGC0 Operations Superintendent for his review and acceptance.
Notes (1) Custody acceptance by TUGC0 Operations does not relieve the STE of the responsibility to complete system deficiencies.
l (2) Upon acceptance of custody by TUGC0 Operations, all operation
~
and work performed on the trans-ferred components shall be co-ordinated with the' Shift Super-visor.
4.7.3 Upon acceptance or rejection of the release, the Operations Superintendent will return the signed release form to the Lead Startup Engineer for filing and distribution as shewn on the release form.
5.0 REFERENCES
5.1 CP-SAP-4, Custody Transfer Tagging
-5.2 CP-SAP-5, Safety Tagging Procedure 5.3 CP-SAP-6, Control of Work on Station Components After Release from Construction to TUCCO.
I 5.4 CP-SAP-20, Guideline for Syste= Walkdown Inspections 5.5 CP-SAP-21, Conduct of Testing 5.6 STA-605, Clearance and Safety Tagging 9s d
i
- Revision 12 Page 12 of 15 gs 6.0 ATTACHMENTS 1
I A - Test Release Form f
B - Return to Contractor Custody Form 4
i a
C - Startup Release to Operations Form 4
l-4 I
l i
i I
L
}
'i i
b d
I F:R INFh MAT;0N ~0NLi.
L w
e.
r-%-
-v-we-e--,Sr
-e---
-+===
-wm-n-tt-----w--c,--++ww--am-... - -
-:---------w
'--.-v--,-+-m
-,.., - -1s e
w--.---
ATTACHMENT A CP-SAP-3 Revision 12 TEST RELEASE Page 13 of 15 UNIT NO.:
SYSTEM TITLE:
TR NO.:
STARTUP SYSTEM NO.:
A.
CONSTRUCTION COMPLETION:
This Test Release transfers custody of:
Component (list below)
Partial Subsystem (Elect. Instr. Mech.)
(Circle One)
Subsystem System All construction and construction testing has been completed on the components within the boundaries of this test release except as identified on the test release deficiency list. Description of test release contents and/or boundary is attached.
Check One:
All incomplete construction work items are listed on the attached deficiency list jQg There are no incomplete construction work items ELECTRICAL SUPERINTENDENT:
DATE:
COMPLETIONS GROUP MANAGER:
DATE:
B. CUSTODY:
Custody of the components shown within the boundaries of this test release are hereby transferred from B&R to TUCCO Startup.
COMPLETIONS GROUP MANAGER:
DATE:
C. CUST0DY ACCEPTED BY:
SYSTEM TEST ENGINEER:
DATE:
LEAD STARTUP ENGINEER:
DATE:
Distribution: Original - Startup System file 1 copy - (Test Release Package) IUGC0 Maintenance Superintendent I copy - Completions Group Manager 1 copy - TUCCO Construction QA Supervisor 1 copy - (Test Release Package) TUGCC Operations Engineer 1 copy - TUGC0 QA Startup/ Turnover Surveillance Superviser b
k
ATTACEMENT B CP-SAP-3 Revision 12 RETURN TO CONTRACTOR CUSTODY Page 14 of 13 RTCC No.:
Unit No:
System
Title:
Startup System No:
A.. Custody of all components within the boundaries shown on the attached drawing (s) or as described below is hereby transferred frem TUCCO to construction for performance of the following,vork:
4 B.
Safety Tag Clearance Required:
Yes No If Yes, CP-SAP-5 Authorization No.
STA-605 Clear. No.
C.
Initiated By:
Approved By:
STE/Date Lead Startup Engr /Date D.
Work Co'cpleted:
1 All construction and construction testing required for the above work has been completed except as described on the attached deficiency list as folicws:
(Check as applicable)
Check One:
No Construction Deficiencies Construction Deficiency List Attached Electrical Superintendent:
Date:
Completions Group Manager:
Date:
Ec Custody Accepted By:
System Test Engineer:
Date:
Lead Startup Engineer:
Date:
[$
6 I
Distribution:
TUGCO Maintenance Superintendent -1 TUCCO QA Startup/ Turnover Surveillance Supervisor - 1 TUGC0 Operations Engineer - 1 RTCC File l
MSP Group h
b
'ACHMENT B CP-SAP-3 Revision 12 7
6 NTRACTOR CUSTODY Page 14 of
'.5 e
RTCC No.:
/
he boundaries shcwn on the attached y',d s hereby transferred from TUCCO to 2 following work:
7 gg (/ Cx e y 6f. CA' s5-l 4
ma f.rs7 B.
Safety Tag Clearance Required:
Yes No If Yes, CP-SAP-5 Authorization No.
STA-605 Clear. No.
C.
Initiated By:
Approved By:
STE/Date Lead Startup Engr / Data D.
Work Cc=pleted:
All construction and construction testing required for the above work has been completed except as described on the attached deficiency list as follows:
(Check as applicable)
Check One:
No Construction Deficiencies Construction Deficiency List Attached Electrical Superintendent:
Date:
Co'cpletions Group Manager:
Date:
E.
Custody Accepted By:
System Test Engineer:
Date:
Lead Startup Engineer:
Date:
E,v ct jev if i <L
{ b."
bN Distribution: TUCCO Maintenance %
----r -1 TUCCO QA Startup/ Turnover Surveillance Supervisor - 1 TUGC0 Operations Engineer - 1 RTCC File MSP Group
. yT
-4 =,, s~
. b ~I Y,
l r b i )
b b !_
a bh h
ATTACHMENT C CP-SAP-3 Revision 12
'STARTUP RELEASE TO OPERATIONS Page 15 of 15 i
Interim Change 02/28/84 Unit No.:
System
Title:
Startup System No.:
RELEASE BOUNDARY:
Operational custody of the components listed below or shown on the attached boundary drawing (s) is released _from TUGC0 Startup to Operations:
Y V
j INCOMPLETE WORK:
Outstanding construction work,' nonconformance reports, test deficiency reports and/or other problems associated with the components within the above described release boundaries are listed on the attached Master Data Base.
List Attached No Outstanding Items c
i OPERATIONAL LIMITATIONS:
Operating limitations are as follows:
i j
REQUIRED SAFETY TAGS HAVE BEEN PLACED PER STA-605:
Date:
RELEASE INITIATED BY:
Date:
RELEASE APPROVED BY:
Date:
)
Lead Startup Engineer l-A RELEASE ACCEPTED BY:
Date:
RELEASE REJECTED BY:
Date:
(If rejected, please attach list of reasons) i Distribution:
Startup Rele~ase File Initiating STE i
TUCCO Maintenance Superintendent TUCCO Operation QA Supervisor TUCCO QA Startup Surveillance Supervisor Is sh
or ww-g; enamacana, 7-Revision 12 STARTUP RELEASE TO OPERATIONS Page 15 of 15 Unit No.:
System
Title:
Startup System No.:
RELEASE BOUNDARY:
Operational custody of the components listed below or shown on the attached boundary drawing (s) is released from TUGC0 Startup to Operations:
INCOMPLETE WORK:
Outstanding construction work, nonconformance reports, test deficiency reports and/or other problems associated with the components within the above described release boundaries are listed on the attached Master System Punchlist.
List Attached No Outstanding Items
[
OPERATIONAL LIMITATIONS: Operating limitations are as follows:
REQUIRED SAFETY.. TAGS EAVE BEEN PLACED PER STA-605:
Date:
d RELEASE INITIATED BY:
Date:
RELEASE APPROVED BY:
Date:
i Lead Startup Engineer RELEASE ACCEPTED 3Y:
Date:
RELEASE REJECTED BY:
Date:
l (If rejected, please attach list of reasons)
Distribution:
Startup Release File 2
TUCC0 Maintenance Sre-g y,.y 4
g g,
Initiating STE g-7 TUGC0 Operation QA Supervisor TUGC0 QA Startup Surveillance Supervisor l
sv FrR EFORMAT;0h DNLi2
-.