ML18033A707
| ML18033A707 | |
| Person / Time | |
|---|---|
| Site: | Browns Ferry  |
| Issue date: | 10/07/1986 |
| From: | Gridley R TENNESSEE VALLEY AUTHORITY |
| To: | Zech G NRC OFFICE OF INSPECTION & ENFORCEMENT (IE REGION II) |
| References | |
| TAC-62264, NUDOCS 8904250092 | |
| Download: ML18033A707 (12) | |
Text
TENNESSEE VALLEYAUTHORlTY CHATTANOOGA, TENNESSEE 37401
,o)<
5N 157B Lookout Place OCT 07 $86 Mr. Gary G. Zech Director TVA Projects Nuclear Regulatory Commission Region II 101 Marietta Street, N.M.
Atlanta, Georgia 30323
Dear Mr. Zech:
SUBJECT:
BROWNS FERRY NUCLEAR PLANT (BFN) RESTART TEST PROGRAM PLAN Enclosed are the following:
(1) Memo, "Browns Ferry Unit 2 Restart Test Program Plan" (2) Overall Program Schedule showing the systems included in the restart test program.
(3) Generic System Test Schedule showing the sequence of activities involved in the program for each system to be tested.
This information is being transmitted to NRC in response to NRC's request made in meetings which*were held at BFN September-15-17, 1986.
'I Very truly yours, TENNESSEE VALLEY AUTHORITY R.
G idley, Dir ctor Nuclear Safety and Licensing Enclosures cc:
Mr. R. J. Clark U.S. Nuclear Regulatory Commission Browns Ferry Project Manager 7920 Norfolk Avenue
- Bethesda, Maryland 20814 Mr. D. R. Muller, Project Director BMR Project Directorate No.
2 Division of Boiling Mater Reactor Licensing U.S. Nuclear Regulatory Commission Washington, D.C.
20555 89042500'y2 850002bo PDR ADDCK 0 PDR P
e V
An Equa) Opportun)ty Emp)oyer
IlKOWNS VKKRY (Il'.'T Rl:h'TART TEST PROGRAM PI,AN f.-
Summary Program Description The primary purpose of the Restart Test Program (RTP) is to insuir t.h~t all systems requ'ired for safe and efficient operation are ad@qua) e]y-demonstrated as operable prior to use of that system.
Operability criteria for testing will consider the design specification of the system including modifications, vendor recommendations and Tech Spec requirements for surveillance testing.
Consideration for additional:testing will also be given to the scope and number of modifications to a particular
- system, the operational history prior to and during the outage, and other documents relating to the status of system components.
From these criteria a System Test Specification (Test Spec) will be generated for each system Demonstration of a system's operability will consist of Surveillance Instructions (SI's),
Post Modification Tests (PMT's),
and any additional steps necessary to confirm operability of that particular system or integrated tests of several systems; all of these will be compiled in the Test Spec which will be reviewed and approved by the Plant Operational Review Committee.
(PORC).
For a System Test Spec that requires additional testing beyond SI's and PMT's, a Special Test Procedure will be written.
~
~
fn addition to the above Test Spec, a System Status Punchlist will be generated that vill track all open items by system.
This punchlist, together with the completed Test Spec checklist and Special Test Procedure will be submitted to the Operations section as an outage system turnover package to document the determination of system operability, II.
RTP Detailed Descri tion A.
Scope Test Specs will be developed for the following list of systems.
This list is based on the systems or portions oi systems being evaluated by the Design Baseline Evaluation Program, 1
2 3
23 24 25 27 31 32A 47 57 63 Main Steam/EHC Condensate and Demineralizers Feedvater/FW Control System (incl. 46)
RHR Service Mater System Rav Cooling Mater System Raw Service Mater System Circulating Mater System Air Conditioning (Control Room)
Control/Station Air and Dryvell Control Air Turbine/Generator and Auxiliaries Auxiliary Electrical Systems (incl. all elect.
sys.)
64 65 66 67 68 69 70 71 73 74 75 84 82 85 90 92 94 99 Primary Cont a i nmi.nt
( inc 1
a)1 i so 1. f>>nc t i ons )
Standby Gas Treatment./St condaty Cottt,.
Offgas System Emergency Fquipment Cooling Mater Reactor Water Recirculation System (incl. 96)
Reactor Mater Cleanup System Reactor Closed Cooling Water Reactor Core Isolation Cooling, High Pressure Cooling Injection Residual Heat Removal Core Spray System Containment Atmosphere Dilution Standby Diesel Generator System (incl. 18,86)
Control Rod Drive System Radiation Monitoring Neutron Monitoring System Traversing Incore Probe System Reactor Protection System In addition, a Test Spec will be generated for the Loss of Off-Site Power/LOCA Test.
B.
System Evaluation In order to determine the system testing requirements, the test engineer must be familiar with the following items on his system:
l.
2.
3.
4.
Design Specifications System as-built design Uendor manuals Tech Specs Due to the length of the outage, the number of modifications performed and the desire to assure reliable startup and operation, many aspects of system status will be reviewed to determine testing requirements and define acceptance criteria.
The following items will be considered during the system evaluation:
2.
Additional testing that may be specified by the Design Baseline Evaluation Program.
3.
MR's completed during the outage or still outstanding.
4.
Outstanding SCR's, NCR's, CAR's, and DR's.
5.
System status as related to Tag,-outs, TACF's, equipment removed.
6.
System status during outage with respect to proper layup, preventive maintenance, problems experienced.
The system will be evaluated based on these items individually and taken together.
Items affecting safety related components must be confirmed to be adequately tested.
Testing, of non-safety related components as a result of the above i'tems, may be specified to provide additional assurance of reliable operation during plant startup and operation.
Any vendor recommended
- tests, inspections, or adjustments shall also be addressed.
l
~
The review process wi11 focus on testing alrrady p}>>nn~6 on Lhi~
system such as SI's or PHT's to determine.the scope of'ddition>>i testing needed.
The Test Spec wi11 then be check1ist of'll thi above testing (Sf's/PHT's} plus a short description of thr additional testing required.
A Special Test Instruction (per Standard Practice BF 17.2) wi)) be written to perform the additions] testing.
The tests will be tracked to completion, using the checklist in the Test Spec, by the test engineer assigned to the system, who will also direct the performance of the Special Test (See attached description of Test Spec development).
C.
System'tatus Punchlist In order to effectively track all the system open
- items, the test engineer will establish and maintain a System Status Punchlist during the review process.
All the open items would be entered onto the punchlist
- and, in addition, spare parts
- needed, information or analysis needed to close open LER's or for other
- reasons, or any other item that may be applicable for the purpo of t
~
~
urpose o
rackxng or expediting of other organizations.
This punchlist will be continued after the RTP by the System Engineer.
D, Outage System Turnover Package
~
~
At the completion of the system test, the test engineer will assemble an outage turnover package consisting of the Test Spec and its checklist of SI's and PMT's, Special Test Instructions if applicable, a list of ECN's and their effect, and the current punchlist showing the status of all open items.
This turnover package will be submitted to the Operations section to assist them in declaring the system operable and preparing for startup.
BYH tlNIT ~ kKS'i'hkT TK. T Pko(g Test. Speci ficat ion Devc.lopmont Introduction System testing requirements for the unit 2 Restart Test Program (RTl-')
will come from three general areas:
I l.
Tech Specs:
All safety related testing required on a system is specified in Tech Specs and performed by SI's.
All of these tests have been reviewed and revised as necessary.
It will be confirm~<i that they are performed as necessary prior to restart of unit 2.
2.
Design Baseline Evaluation Program:
Some testing may be specified as a result of the Design Baseline Evaluation Program in cases where it cannot be determined if a system meets the new desi gn criteria without a physical test, These testing requirements will be incorporated into the System Test Spec (described below).
3.
System Evaluations:
All safety related and some portions of non-safety related components and systems will be reviewed and evaluated for additional testing needed as described below.
The primary concern for testing in this category is to assure a
'eliable system to support overall plant operation.
All safety related system operability is addressed by number 1 above.
Each RTP System Test Spec will incorporate the testing requirements from the above three categories.
Item 1 is already established and item 2 will be provided by another program.
The RTP main focus will bc on item 3
as described below.
II, S stem Evaluations In an effort to standardize the review and evaluation process used to determine required system testing for the RTP, consistant evaluation guidelines must be used.
Systems and components will be selected for testing based on several considerations:
l.
Effect on system operability (critical or non-critical) 2, History of operability, problems 3.
Vendor recommended inspections, adjustments, tests 4.
Status during, the outage; in operation, lay-up conditions, preventive maintenance done, etc.
The primary concern for testing in this category is to assure a
reliable system to support overall plant operation.
The var ious areas Lhat most br r<<vir wed>>rc li>>ted h>>low.
Each iter will be eval>>atrd a>>d Lr~: Ling specified based. on whether or rrot it affects a component.
nr system per the guidel i>>es stated above.
Evaluation of U2C5 ECN's:
A)l ECN's comp)eted, in progre-s, or planned to be completed during the cyc)e 5 outage on unit 2 must be reviewed for adequate post-instal] ation testing.
The review of ECN's that affect safety related components must confirm that some type of functional testing is performed after the modification.
If this review is performed by other organizations, obtain the result:
of the review and insure that any open items are addressed (punchlist item).
2.
MR's Completed:
Review all MR's that have been completed on the system during cycle 5.
Record MR numbers that were for maj or work or that required significant testing after completion.
3.
MR's Outstanding:
Maintain awareness of MR's to be completed on your system.
Review to determine which will require testing.
Record MR numbers and descriptions of major MR's (punchlist item).
4.
DCR's Outstanding:
Review the DCR's that will reguire work to be performed prior to startup.
Determine the potential testing impact and.track or expedite the modification (punchlist item).
5.
Prior Committment Retests Outstanding:
Investigate and compile a
list of testing that may have been committed to or required by some other organization or document, e.g.,
Corrective Action Requests (CAR's), Deficiency Reports (DR's),
QA Nonconformance
- Reports, correspondence with the NRC, Significant Condition Reports, etc.
(punchlist items).
6..
Hold Orders:
Establish and maintain a status of hold orders on th system.
Use this to establish the proper system configuration reguired for testing and startup.
7.
Eguipment Removed:
Establish and maintain a status list of equipment removed with return dates, purchase order numbers for replacements, retest requirements, etc.
(punchlist item).
8.
9.
Equipment status during outage:
Compile an account of system and component operation during the duration of the outage.
Include operation of the system or component, SI's performed, inadvertent initiations, or layup and inactivity of the system.
Identify functional testing based upon the above outage history.
TACF's in place:
Compile a list of all TACF's in place on the system with reasons, removal dates, retesting reguired, etc.
(punchlist item).
- 10. Vendor Recommendations:
Review vendor manuals and recommendations for proper system operation.
Insure that any testing meets vendor requirements for inspections, adjustments or preventive maintenance.
For major equipment, consider a visit by a vendor representative to inspect the eguipment and make recommendations as necessary.
)1.
Tech Spe<'equir oments:
Roviow system
'fech Spec r equirem~n' the Sl's that address those requirements.
Be fnmi) iar with ail Sl's and their frequency.
37.
Design Spec.
and other documents:
Copies of any re]eted specs br other information should be kept on fi]e and reviewed:
Preop.
Test
- Spec, Design Spec, Instrument Data Sheets, the original completed preop test, etc.
should all be reviewed for aspects that are critical to system operation and should be tested, I
The above evaluations will be used to generate a System Test Specification (STS) which will list the testing identified by the system evaluation in a single document to be used as the basis for test procedures.
Proper documentation of the evaluation is required to ensure tracability and to justify that the system can be returned to an operable status.
The STS will list the specific test (SI, PMT, Special Test, etc...) to be used to meet each testing requirement, The STS will receive a formal review and will be approved by PORC.
To ensure uniformity between all systems, the format below should be used for each STS.
1.
The.first section of the STS will be designated as SPECIFICATION OBJECTIVES AND SYSTEM SCOPE.
This section will contain a brief explanation of the purpose of the System Test Specification and what vill be accomplished by performance of the specified tests.
Also, the system boundaries, for evaluation purposes, will be documented as the System Scope.
The points of interface with other systems at which the system evaluations were terminated will be identified to ensure adequate system to system coverage.
2.
The next section, vhich consists of three subsections, is intended to be a compilation of testing identified through the system evaluations.
This section will be designated TESTING REQUIREMENTS.
A.
U2CS ECN Post-Installation Test Requirements In this sub-section each ECN shall be listed by number and description along with the associated work plan(s) used to install the ECN.
Test requirements should be briefly described and the test used to meet the requirements shall be listed. This applies whether the test is performed in the text of a work plan, if an established test vill be performed to meet the requirements, or if a Special Test Procedure will be written.
For those ECN's that do not require testing, the ECN number and description vill be listed as veil as the implementing work plan vith the notation that no testing is needed.
B.
Design Baseline Program Test Requirements
- Testing requirements specified in this sub-section vill result from the baseline program walkdowns and evaluations.
Any ECN's specified by the baseline program will be noted here,
- however, testing requirements vill be determined in the U2CS ECN evaluation sub-section above.
C.
Other Testing Rcquiremc.nts Any othe.r Lesting i cccjuirrmcat s identified from the system evaluatjons will he listed in tt<<..
sub-section.
A description of the source of each Lest requirement along with a statement of what will he LesLed will be listed with the test designated to meet each requirement.
3.
The final section, excluding Appendices, will be.designated as the REQUIRED TESTING CHECKLIST.
This section is to be used as the checklist to verify that all testing, that has been identified through the evaluation process and compiled in the above three sub-sections, has been successfully completed with a minimal amount of redundant testing.
For this section, the three previous sub-sections will be condensed into a checklist-type form.
In the three sub-sections, a particular test may be specified a number of times to satisfy more that one identified test requirement.
Based on an overview of these three sub-sections a test, whether it be an SI, MI, TI, PMT, or a Special Test, will be listed once along with all identified requirements that will be satisfied by successful completion of that test.
Each testing requirement will have a sign off for the system/test engineer to ensure that all of the identified testing requirements are satisfied.
4.
Two appendicies, at a minimum, should be utilized in the STS.
APPENDIX l will be used to designate reference documents, including
- drawings, vendor manuals, design specifications, etc.,
that were utilized during the evaluation process.
APPENDIX 2 will be used to identify test deficiencies and exceptions resulting from the above outlined testing.
Resolutions to any test deficiencies or test exceptions will also be provided in Appendix 2.
OVERALL PROGRAM SCHEDULE RTP ItP;".UC APP'OP SYS=W LOP/LOCA F/L SYS=P
~FUEL LD SYS.
REQPD.
FQR LQP/LOCA TEST SYS.
REQ'D.
FOR FUEL LOAD SYS.
REQ'D.
FOR STARTUP 23-RHR SW.
24-RAW CW.
25-RAW SW.
31-CONTROL RM. A/C 57-AUX. ELECT(ALL) 67"EECW 70-RBCCW 74-RHR 75-CORE SPRAY 82-STBY.
DG(18-FUEL OIL 99-RPS 32-CONT.
AIR/DW CA (P) 64-PRIMARY CONT.
(P) 65-SBGT/SEC.CONT.
(P) 68-RECIRC.SYS.
(P) 69-RWCU (P) 71-RCI C (P )
73-HPCI (P) 2-COND.
DEMINS.
3-FW/FW CONTROL(46'7-CIRC.
WATER 64-PRIMARY CONT.
66-OFF GAS 71-RCIC 73-HPCI 84-CONTAIN.
D ILUTt C"'4-T I P REQUIRED AFTER STARTUP:
47-T/G CONTROL 8
AUX.
1-MAIN STEAM/EHC 32-CONT.
AIR/DW CA 63-SBLC 65-SBGT/SEC.
CONT.
68-RECIRC.
SYS.(96-FLOW 69-RWCU CON'f.
INCL) 85-CRD 90-RAD.
MONIT.
92-NEUT.
MQNIT.
AND 86-STARTING AIR INCL)
(P)-ONLY'ART OF THE SYSTEM IS REQUIRED AT THIS T IME ALL THE ABOVE SYSTEMS ARE INCLUDED IN THE RESTART TEST PROGRAM.
THL SYST':""
LISTED BELOW ARE NOT INCLUDED IN THE RESTART TEST PROGRAM.
4-MAIN STEAM CRQSSTIE 5-EXTRACTION STE'AM 6-HEATER VENTS 8
DRAINS 12-AUX. BOILER 20-.CENTRAL LUBE OIL 26-HP FIRE PROTECTION 28-WATER TREATMENT 29-PQTABLE WATER 30-NORMAL BLDG. VENT.
33-SERVICE AIR 34-VACUUM PRIMING 35-GEN.
HYDROGEN COOLING 37-GLAND SEAL WATER 38-INSULATING OIL 39-CQ2 SYSTEMS 40-STAT I ON DRAI MAGE 4-Ig-HALON FIRE PROTECTION 42-CHEMI CAL CLEANING A3-WATER SAMPLING 44-BUILDING HEATING 49-BREATHING AI R 50-SODIUM HYPQCHLOR I TE D I STR t B.
51-RAW WATER CH( ORINATION 53-DEMIN.
BACKWASH AIR 55-ANNUN ~
L SEQUENCE EVENTS REC'3Rt'I;-.
56-TEMPERATURE MONITORING 58-BIO-THERMAL RESEARCH FACILITY'6-CONTAINMENT INERTING 77-RADWASTE 78-FUEL POOL COOLING 79-FUEL HANDLING 8 STORAGE 80-PR IMARY CONTAINMENT COOL I N;-.
0 1
GENERIC SYSTEH TEST SCHEDULE DOLit TST (CP KL
'RSLE Ej f3ll 5T" SDK tTGÃt.
me.t mt'VALUATE DESIN BASELINE EVALUATIOM PERFORHAMCE Df:S BSLN DESIGN BASELIIIE EVALUATIOMCNPLETE DRAFT STS DRAFT STS ONPLETE REVW STS PERFORH REVIBf OF STS ST APROV SPECIAL TEST PROC APPROVED HOD DOME SYSTEH KIDIFICATINS ONPLETE SPEC TST PERFORH SPECIAL TESTS ST QNPL SPECIAL TEST CNPLETE PINCH LST DEVELOP AMD DISPOSITIM PUMCHLIST ITEH PHT POST~
TESTS GNPLETE BSLN STS DEVELOP SYSTEH TEST SPECIF ICATIOff FROH BASELINE EVALUATION STS APRV SYSTEH TEST SPEC.
APPROVED BY PORC BEG TEST BEGIN SPECIAL TESTS VFY RSLT VERIFY TEST RESULTS PERF SIs PERFORH REQUIRED SURVEIL LANCES SYS EVAL DEVELOP STS FROH PLAMT AND ECH DATA WITE ST WITE SPECIAL TESTS REQUIRED BY STS APRV TST APPROVE SPECIAL TEST RESULTS (PORC)
TST COHP ALL REQUIRED SYSTEH TESTING CINPLETED OPS REVW OPERATIONS REVIEW FOR OPERABILITY OPERABLE SYSTEH IS DECLARED OPERABLE
~
~