ML20247N366
| ML20247N366 | |
| Person / Time | |
|---|---|
| Site: | Seabrook  |
| Issue date: | 05/14/1987 |
| From: | PUBLIC SERVICE CO. OF NEW HAMPSHIRE |
| To: | |
| Shared Package | |
| ML20247N354 | List: |
| References | |
| FOIA-89-309 STPD, NUDOCS 8909260204 | |
| Download: ML20247N366 (24) | |
Text
g;ef,2 fill:no; ; l?l.l;C., :.s.; c.. : .. e n': +:; .uu . ,, n:x.:.y. s_ ^ s h %. '.-
1 ,;.L f ,l 5,1 3 X & :i:d 1 3 : f ' :. s -
4 STPD REV. 2 e1 of 24 1
SEABROOK STATION STARTUP TEST PROGRAM DESCRIPTION s !
REVISION 2 ,
. 7 1
RevIeued: /)$?/) . & f/)3hi7
'~
STARTUP MANAGER DATE,
\ -
.D s 5 /14/t 7 DATE SEABROOK STsTleKMANAGER
' i '
/
\ D ~
.: /
E AR QU ALITY M AN AGER -
- D ATE-f ,
[
Approved; b OY O VICE PRESWENT-NUCLE AR PRODUCTION DATE' DocumentControlCenter Control Number _%,
t 8909260204 870919 PDR FDIA BROCKB9-309 PDR <
)
b c -
- . " STPD REV. 2 Pago 2 of 24
1.0 INTRODUCTION
f i
The Seabrook Station initial test program is subdivided into two programs, which are defined as follows:
~
Preoperational Test Program - Tests performed subsequent to the completion of system fabrication and prior to the initial loading of fuel into the reactor vessel. These tests verify the proper design and fabrication of plant systems and equipment to the extent necessary to operate the plant at power.
Startup Test Program - Tests performed during and subsequent
~
to initial fuel loading. These tests verify the proper design of the reactor core and the dynamic characteristics of the plant during both normal and anticipated abnormal operating conditions at power levels up to and including 100% design reactor power.
Section 14.2 of the Final Safety Analysis Report provides a general description of the administration of the initial startup program and the technical content of the tests which are performed during the preoperational and startup test pnograms.
Table 1-1 is an extract of FSAR Table.14.2-1 and describes the organizational responsibility and authority during each phase of the Startup Test Program.
This document - Startup Test Program Description - will provide guidance for the administration of the Startup Test Program and will describe the types of tests which will be performed.during the startup, the responsibilities of the various personnel during performance of a test, and the administrative controls and procedures used to ensure that all tests are conducted in a uniform and predetermined manner.
1.1 CHANGES Distribution of this document and any changes to this document are the responsibility of the Startup Manager.
Proposed changes may be made by contacting the Startup Manager or his alternate.
1.2
SUMMARY
OF CONTENTS Section 2.0 provides a general description of the phases which constitute the startup test program.
Section 3.0 describes the organization and personnel involved in the conduct of this test program and defines their responsibilities, s
__.~_._.-____._____
_ . _ _ _ _ _ ' 1.Y
_____I I _ _~"
" ~~~~~ ~
'~~*'I_i_._ _~~_ _T_*_____._____.___a
i A
~
C STPD REV. 2 Page 3 of 24 Section 4.0 describes the administrative controls used during the startup test program, including preparation and performance of'startup tests.
Section 5.0 describes the quality assurance requirements used during the startup test program.
'2.0 GENERAL DESCRIPTION The Seabrook Station initial test program is subdivided into the various test phases listed below:
Phase 1 - Construction Verification Tests Phase 2 - System Acceptance /Preoperational Tests Phase 3 - Integrated System.Preoperational Tests Phase 4 - Initial Fuel Loading Phase 5 - Initial Criticality and Low Power Tests Phase 6 - Power Ascension Phases 1, 2 and 3 constitw e the preoperational test program and are discussed in the Preoperational Test Program Description.
The Startup Test Program spans the time period from the\beginning of fuel loading to the completion of testing at rated power.
This period covers Phases 4, 5, and 6 of the Seabrook Station
' initial test program. The individual test procedures are listed in Table 2-1.
Phase 4, also known as initial fuel loading, involves assembly of the primary sources, verification of initial setpoints, loading fuel into the reactor vessel under controlled conditions, and reassembly of the reactor vessel upper internals and head.
Phase 5, low power testing, verifies the proper design and installation of the reactor core by measurement of various nuclear
- and thermal-hydraulic parameters under sub-critical, critical, and low power conditions. This phase begins after reactor vessel head installation and ends after the turbine-generator has been placed on-line at approximately 10% of rated power. Some of the tests that are performed during Phase 5 are rod worth measurements, boron worth measurements, rod drop times, reactor coolant system flow rate measurement, and reactor coolant system flow coastdown measurement.
Phase 6, power ascension testing, verifies proper operation of plant equipment and systems during both normal and abnormal operating conditions and is also used to fine tune various control systems. The Phase 6 testing is primarily done at stable power levels of 305, 50%, 755, and 1005, called plateaus. The power ascension testing at Seabrook includes such tests as station blackout, simultaneous MSIV closure, negative rate trip, remote shutdown, large load reduction, load swings, NSSS acceptance test, moisture carryover measurements, and 100% power I
1 trip.
C _ = .____ r -_z__ f -
- ~ _
.. ~
STPD REV. 2 Pago 4 of 24 TABLE 1-1 STARTUP TEST PROGRAM RESPONSIBILITY / AUTHORITY MATRIX ACTIVITY PHASE 4 PHASE 5 PHASE 6 Tcat Program STD STD STD Management Tost Procedure STD or SS .STD or SS STD or SS Pecparation Tcat Procedure STD, SORC" STD, SORC' STD, SORC' Approval Tc0t Coordination STD or SS STD or SS STD or SS snd Direction ,
\
Systems and Equipment SS SS SS Op0 rations Syctems and Equipment SS SS SS
~ Maintenance Tcst Completion STD, SORC' STD, SORC' STD, SORC" Approval Tcchnical Support NSD, NSS, AE NSD, NSS, AE NSD, NSS, AE, TG Logend:
STD - Startup Test department SS - Station Staff SORC - Station Operations Review Committee / Station Manager NSD - Nuclear Services Division, Yankee Atomic Electric Company AE - Architect Engineer, United Engineers and Constructors TG - Turbine Generator vendor, General Electric Company NSS - Nuclear Steam Supply vendor, Westinghouse Electric Note: SORC reviews; Station Manager approves.
~
- ~ . _ _ _ . _. ._ _. . . . _ . _ _ _ ,
e=- . .
i L' STPD REV. 2 l l
Pago 5 of 24 Definitions for TABLE 1-1 Tc9t Program Management This is the organization responsible for coordinating and sequencing tha startup program activities.
Tnat Procedure Preparation This is the organization (s) responsible for preparation of the test procedure initial draft, coordination of the procedure review, and recolution of comments.
Tnat Procedure Approval Th;se are the organizations that will approve test procedures prior to thoir performance.
Tcat Coordination and Direction These organizations will coordinate the activities prior to, during, and after each test. A Test Director will ensure that the test is properly conducted and all relevant data is properly recorded and ana-lyzed as necessary, Upon completion of the test, the data will be reviewed for results approval.
Systems and Equipment Operations This organization is responsible for the operation and manipulation of pinnt equipment used during the startup test program.
,Syntems and Equipment Maintenance This organization is responsible for the maintenance of plant equip-cant during each phase of the test program.
Tcst Completion Approval Those organizations will review and approve the results of completed tcat procedures.
Tcchnical Support Those are the off-site organizations that may be used to provide tech-nical input for the startup test program as required. This list is not all inclusive and other organizations may be used as considered nocessary by Startup Test Department management.
l STPD REV. 2 Page'6 of 24 TABLE 2-1 STARTUP TEST PROGRAM PROCEDURE INDEX, Procedure Number Title 1-ST-1 Startup Program Administration 1-ST Primary Source Installation-1-ST-3 Core Loading Prerequisites 1-ST-4 Initial Core Loading 1-ST-5 Control Rod Drive Mechanism Operational Test 1-ST-6 Rod Control System 1-ST-7 Rod Drop Time Measurement Rod Position Indication i 1-ST-8 1-ST-9 Pressurizer Spray and Heater Capability Test 1-ST-10 Resistance Temperature Detector Bypass Loop Flow Verification 1-ST-11 Reactor Coolan.t System Flow Measurement 1-ST-12 Reactor Coolant System Flow Coastdown 1-ST-13 operational Alignment of Nuclear Instrumentation
. 1-ST-14.1 Operational Alignment of the Process Temperature Instrumentation 1-ST-14.2 RTD Cross-Calibration 1-ST-15 Reactor Plant Systems Setpoint Verification 1-ST-16 Initial Criticality 1-ST-17 Boron Endpoint Measurement 1-ST-18 Isothermal Temperature Coefficient Measurement 1-ST-19 Flux Distribution Measurements at Low Power 1-ST-20 Control Rod Worth Measurement 1-ST-21 Pseudo Rod Ejection Test e- .
__ . _ . . . , _ . , _ _ . , , . . = _ _ _ _ _ _ _ _ _ _ _ _ _ . _ ._ _ . _ _ _ . . _ _ _ _ _ _ . _ _ _ _ _ _ _ _ _ _ _ _ . _ _ _ _ _ _ _ _ _ _ _ _ . _ _ _ _ _ _ _ . _ _ . _ _ _ . _ . _ . _ _ _ . _ _ _ _ _ _ . . _ _ _ _ _ _ . _ _ _ . _ _ . _ _ _
~ . -
STPD REV, 2.
Pcge 7 of 24 TABLE 2-1 Continued STARTUP TEST PROGRAM' PROCEDURE INDEX Procedure Number Title Natural Circulation Test
~
1-ST-22 1-ST-23 Dynamic Automatic Steam Dump Control 1-ST-24 Automatic Reactor Control .
1-ST-25 Automatic Steam Generator Level Control 1-ST-26 Thermal Power Measurement and Statepoint Data Collection 1-ST-27 Startup Adjustments of R6 actor Control System i
1-ST-28 Calibration of Steam and Feedwater Flow Instrumentation 1-ST-29 Core Performance Evaluation 1-ST-30 Power Coefficient Measurement 1-ST-33 Shutdown from Outside the Control Room 1-ST-34 Load Swing Test 1-ST-35 Large Load Reduction a
1-ST-36 Axial Flux Difference Instrumentation Calibration 1-ST-37 Steam Generator Moisture Carryover Measurement 1-ST-38 Unit Trip from 1001 Power 1-ST-39 Station Blackout Test 1-ST 40 NSSS Acceptance Test 1-ST 41 Radiation Survey 1-ST 42 Water Chemistry Control 1-ST 43 Process Computer 1-ST 44 Vibration and Loose Parts Monitor
- rr - - - - ~ - - - . . _ _ .
P_ n_. _ __ _ _ ___r~r71_ _ ___ __ - - _7 _
STPD REV. 2 Pege 8 of 24 s
TABLE 2-1 Continued STARTUP TEST PROGRAM PROCEDURE INDEX Procedure Number Title 1-ST 45 Process Effluent' Radiation Monitoring System 1-ST-46 Ventilation System Operability Test 1-ST 47 Main Steam Line Isolation Valve Closure Test 1-ST 48 Turbine-Generator Startup Test 1-ST 49 Circulating Water System Thermal-Hydraulic Test 1-ST-50 Movable Incore Detector System 1-ST-51 Power Ascension Dynamic Vibration Test 'g 1-ST-52 Thermal Expansion 1-ST-53 Turbine Driven Emergency Feedwater Start Verification 1-ST-54 Steam Generator Blowdown 1-ST-55 Steam Dump Valve Test 1-ST-56 Piping Vibration Testing s.
. --___i___._ . _ _ _ . _ _ . _ _ __
REV. 2 STPD Pago 9 of 24 30 ORGANIZATION The initial test program represents a transition fr6m the installation of the station structures, equipment, and systems to the integrated operation of the station to produce electricity.
The Construction organization and its associated contractors are responsible for the installation of structures, equipment, and systems. The Seabrook Station operating staff is responsible for the operation of the facility from the time of initial fuel load in accordance with the requirements of the operating license and the Technical Specifications. In order to provide a smooth and orderly transition from construction to operation and the asso-ciated transfer of authority from Construction to the Station Staff, the Startup Test Department will provide a temporary onsi'te organization to manage testing of plant systems and equip-ment.
The Startup Test Department is composed of employees of New Hampshire Yankee, Yankee Atomic Electric Company, United Engineers and Constructors Inc. , and Westinghouse Electric Corporation. Personnel from other contractors may be utilized as required by the Startup Manager. \
The Startup Test Department is responsible for (1) the overall scheduling, administration and technical direction of the initial test program; (2) coordination of systems and equipment turnover at completion of construction; (3) development of initial test procedures; (4) direction of test procedure performance; and (5) coordination of systems and equipment turnover to the station staff.
During the preoperational test program, the station staff will accept system operating, maintenance, and design control respon-sibilities in increasing degrees as the test program progresses.
By the start of initial fuel loading, the station staff will have
- total responsibility for necessary plant equipment.
During test Phaces 4, 5 and 6, the Startup Test Department will be formed from personnel within the NHY organization and person-nel from other organizations as required by the Station Manager.
The Startup Test Department will be formed during periods of Personnel within the Stattup initial startup test activities.
Test Department will be designated by the SLation Manager.
The remainder of this section describes the responsibilities of the Startup Test Department and Station Staff during the Startup Test Program.
I l
l l
- u. .
~
.STPD REV. 2
/ Page 10-of 24-
.3 1.-'STARTUP.~ TEST' DEPARTMENT 3 1. 1- Startup Manager The Startup Manager has overall responsibility for
.the initial startup program and reports to the Station Manager.
L 3 1.2 Reactor Startup Supervisor-The_ Reactor Startup Supervisor is responsible for-detailed coordination of startup test program including scheduling of. tests, preparation and per-formance of test procedures, analysis of results, and preparation of the startup report. He interfaces-with station staff, YAEC Nuclear Services Division, and Westinghouse for Phases 4, 5, and 6 and reports to the Startup Manager. l 3.2 STATION STAFF Each department within the station staff has its normal' responsibility with regard to plant operations'widh the ad-ditional duty of supporting the startup test program as requested by the Reactor Startup Supervisor. The station
' Reactor Engineering Department will also provide shift support for actual performance of test ~ procedures and will coordinate'the analysis of certain test data and results.
33 STATION OPERATIONS REVIEW COMMITTEE / STATION MANAGER SOHC will review all test procedures used during the startup test program, and will also review all test results and reports. The Station Manager will approve all startup test procedures and test results. The Startup Manager will serve
- as an advisory member of SORC during the review and approval of Startup Test procedures.
4.0 PROGRAM ADMINISTRATION NOTE: In all cases where specific titles are mentioned, a designated (by the Startup Managert alternate may fulfill the duties when required individuals are unavailable.
= _ - r -__ r r_r r_r
- r--m - -- -- - --
. j STPD REV. 2 i Pago 11 of 24 i
4.1 PROCEDURES ]
Administrative control of startup test procedures (ST's) is l accomplished through the use of two appendices to this l document. Appendix A, Preparation of Startup Test i Procedures, details the guidelines that are used to prepare a startup test. Appendix B, Review, Approval, and Revisions l -
to Startup Test Procedures, outlines the process used to review and approve a test procedure for use in the field.
I 4.2 TEST RESPONSIBILITIES 4.2.1 SHIFT TEST DIRECTOR The Shift Test Director reports to the Reactor Startup Supervisor, and shall be regarded as the equivalent of the Shift Superintendent with respect to testing matters. The Shift Test Director's responsibilities include:
- 1. On-shift coordination of Startup testing activities.
\
- 2. Insure that Startup testing activities are con-ducted in accordance with the STPD.
3 Provide guidance or resolution for administra-tive problems not within the scope of those addressed in the STPD.
- 4. Coordinate the resolution of technical problems where the assistance of personnel not on-shift is required.
- 5. Coordinate overall plant operations with the
- Shift Superintendent / Unit Shift Supervisor to insure required test conditions are established in a safe and prudent manner, and maintained as necessary for test performance.
- 6. Insure that on-shift surveillance activities (NRC, QC, etc.) are conducted in a manner that is not disruptive to the activities of the Test Directors.
- 7. When the Reactor Startup Supervisor is not on-site or is otherwise unavailable, the Shift Test Director shall act as his designated alternate.
I 8.. Perform the functions of Test Director or Test i
Engineer on a limited basis.
l
__ _ .-- -.._ ~-. -.- - - _
_. ; _=
I STPD REV. 2 Fege 12 of.24 E,
4.2.2 ' TEST DIRECTOR The Test Directors report to the Shift Test Director and are responsible for the following:
1 Performance of individual Startup tests.
- 2. Direction of Test Engineers and other test'per-sonne 1.
3 Insure that any required special test l equipment is available and is properly calibrated.
L 4.- Insure that the test activities-are conducted in-accordance with the STPD. ~
Insure that timely notification is provided to 1
- 5. .
surveillance organizations (NRC, QC, etc.) for pre-determined test observations and " witness points".-
If a test extends over more than one shifb multiple Test Directors may be assigned.with one de,ignated s as the Lead Test Director. The Lead Test Director is responsible for the completion (to the maximum extent practical) of-procedure Sections 2.0, 3.0, 4.0 and 5.0. Additionally, he is responsible for the analysis of test results and the preparation of the .
Test Critique.
4.2.3 TEST ENGINEERS AND OTHER TEST PERSONNEL Test Engineers and other test personnel perform func-tions as assigned by the Test Director or Shift Test Director. This may include data acquisition, log entries, in.*tallation and removal of jumpers and setup and checkout of special test equipment.
4.2.4 STATION STAFF Station Staff will perform its normal job functions as required to support plant operations and the startup test program. Although the Test Director has the primary responsibility for the execution of the test, the Station Staff has the responsibility for the proper operation of equipment, systems, and the plant and reserves the right to take appropriate corrective actions whenever unsafe or unsatisfactory conditions exist. Temporary assignment of station personnel to the Startup Test Department may be done as required, with the agreement- of the affected department head.
_ _ 1 __ _ _ __ _ _ _ __ _ _ _
STPD REV. 2 Page 13 of 24 4.3 CONDUCT OF TESTING 4.3 1 TEST COMMENCEMENT The test is considered to commence when actions are The being taken to satisfy the test prerequisites.
Test Director should make an entry in the Chronological Log indicating commencement of the test. Certain long lead-time items may be initiated without formal test commencement, but should be
. ; entered in the log.
. s[-IndividualstepswithintestSections2.0,
.and 5.0 can be performed in any order. All steps in 3.0, 4.0 these sections shall be initialed and dated prior'to 1
commencing Section 6.0 unless otherwise stated in the.
test.
A pre-test briefing will normally be conducted as 4 part of Section 3 0. The Test Director will discuss
'%'Ns the content of the test with all participants including assigned Operations personnel. Individual duties and responsibilities should be reviewed.
Abnormal plant conditions or system configurations to be encountered during the test should be discussed.
If a test extends over more than one shift, the briefing should be repeated following shift turnover.
Test equipment utilizied to collect data during test performance shall be recorded on the " Test Equipment Data Sheet" (Figure 3 of Appendix A), if the proce-dure does not include an attachment for this purpose.
Key test personnel, i.e., Shift Test Director, Test Director, Test Engineers, shall be listed on the
- " Test Personnel" Log (Form 3 of Appendix C).
4.3.2 TEST PERFORMANCE The test shall be performed in accordance with the test procedure. All steps in'the Test Instructions section of the procedure shall be performed in numerical order unless the procedure explicitly states otherwise. The Test Director or Test Engineer shall initial and date each step after it is per-formed. Steps in Sections 7.0 and 8.0 need not be performed in order. Failure to obtain expected results shall be reviewed by the Test Director and Shift Test Director as a possible test exception.
- a. ._--,--__-----__------_h.--_~ _ _ _ - - - - .
STPD REV. 2 Page 14 of 24 4.3.2 TEST PERFORMANCE - Continued The Chronological Log will be maintained and will document significant events during the test. Log entries should be noted with the date, time and initials of the person making the entry. All entries in the test will be made in indelibla black ink and, with the exception of data recording, usually will be made by the Test Director or Test Engineer.
Data will be recorded in the procedure or on separate I data sheets per the requirements of the tests. If a separate data sheet is used, the individual actually recording the data should be clearly identified. In those instances where a number of items must be recorded at separate locations, a number of sheets may be utilized. This information may be transcribed to a common sheet provided the individual originally obtaining the data is clearly identified.
All data sheets, " scratch sheets" used foricalcula-tions or data reduction, or other-test-related material should be retained for possible inclusion in the completed test package.
Any erroneous entries in the test must be corrected by drawing a single line through the incorrect entry, initialing and dating the deletion, and entering the correct entry.
If a procedure specifically instructs the Test Director to repeat certain steps, he may at his option, either repeat the steps even though pre-viously signed-off, or insert " clean" pages allowing the steps to be signed-off on each repetition. If used, the " clean" pages will be appropriately anno-The steps will be tated to indicate their purpose.
performed in the order written. Any " clean" pages used should be reviewed to insure that required QA witness points are properly identified.
{..* -
V STPD REV. 2 Page 15 of 24 4.3.2 TEST PERFORMANCE - Continued Certain tests may refer to the use of an appendix, special test procedure (STP), or an operating proce-dure to perform a specific task. In the case of an appendix or STP, a completed copy should be" attached to the test. If either of these documents has a series of steps requiring initials, a copy should be included each time the document is used. If no ini-tials are required, only one copy of the body of the document need be attached 'in addition to the data sheets from each time it is used. Operating proce-dures need not be attached unless specifically '
required by the test procedure. , ,
All startup test procedures implicitly assume that equipment. operations and instrument recalibrations are performed using the appropriate station proce-dures. The startup tests will provide general guidance and instructions concerning what needs to be accomplished. The station procedures will provide the detailed instructions describing how tk accomplish the required task.- There are limited exceptions to this assumption. For these exceptions, the startup test procedure will provide the detailed instructions necessary to perform the task. These exceptions will generally'be confined to manipula-tions and recalibrations that are outside the scope of the routine operating and maintenance procedures.
4.3 3 FIELD CHANGES TO TEST PROCEDURES During the testing program it may become necessary to change an approved procedure because of system
. changes or other factors. The mechanisms used to make such changes are the procedure Revision and the test procedure Field Change. The choice of method is its largely dependent upon the nature of the change, magnitude, and the time frame in which it is to be completed. This choice should be carefully evaluated to ensure the change is made in the most efficient
- manner. Revisions to test procedures are discussed in Appendix B, Paragraph II.B.
Errors discovered in the procedure, or portions of the test which must be changed because of other fac-tors should be controlled by a Field Change. Once it has been determined that a Field Change will be issued, a further determination as to the nature of the change, i.e., intent or non intent, must be made.
.O STPD REV. 2 Pago 16 of 24 4.3 3 FIELD CHANGES TO TEST PROCEDURES - Continued A CHANGE OF INTENT is defined as any change which alters the original objectives or acceptance criteria of the test procedure. Thus, any change to the pro-cedure which varies from L 9 stated objectives of the
-test, be it in the objectives, instructions, or acceptance criteria, shall be reviewed for a change of intent. Any change that would invalidate pre-viously acquired data or cause such data to be suspect should also be reviewed for a CHANGE OF l INTENT. Such a change may be grounds for repea, ting previously performed portions of the test.
ORIGINATION The Test Director or a Test Engineer shall originate Field. Changes using Form 7 of Appendix C. The Engineer will complete the upper portion of the form The Field Change with the appropriate information.
number should be assigned sequentially from "1" for a particular revision of a test procedure. The i
" Description of Change" must include the step number and the exact wording of the change. If thh change is extensive, continuation sheets or " clean" proce-dure pages can be attached as required. The change should~be reviewed to insure that required QA witness points are properly identified. The " Reason for Change" should clearly and concisely describe the necessity for changing the procedure. Multiple changes may be included in a single field change pro-vided each specific item is clearly listed along with its specific reason. The Test Director or Test Engineer shall sign and date the Field Change in the
" Originator" blank.
APPROVAL The Engineer originating the change will submit the Field Change to the Reactor Startup Supervisor for approval. It is permissible for the Reactor Startup Supervisor to both originate and approve a Field Change. The Ceactor Startup Supervisor will:
- 1. Determine if the change involves a CHANGE OF INTENT;
- 2. Answer the four questions for " Determination of 10CFR50.59 Applicability", and; 3 Review the change to ensure that it is justified and correct.
I l
l f
-.n_-. -_ - - . . . __ .
__ _A
-n- _ _ _ _ -
~
s Y
, %. l -
e- STPD~ REV. 2 Page 17 of 24 4.3 3 FIELD CHANGES TO TEST PROCEDURES - Continued Non-Intent Field Changes will then be submitted to the' Unit Shift Supervisor'(or another SRO) for review.
and approval. .When the Unit Shift Supervisor has signed and dated the form indicating approval, the field change is acceptable for implementation. All
-non-intent changes must tHe reviewed .by SORC within 14 days of implementation.
If a CHANGE OF INTENT is involved, Station Manager approval will be required prior to implementation of the change. It may then become necessary'to interrupt _the test.until SORC review and Station Manager approval are obtained.
The Reactor Startup Supervisor shall contact the SORC.
chairman and arrange for a meeting to review and-approve the change. Once Station Manager approval is obtained, the change is available for implementation.
On an INTENT Field Change, the Unit Shift Supervisor approval blank will be marked "N/A". j It is' preferable to have the above personn'el present to-review and approve the field changes. It is per-missible to obtain a verbal authorization for the Field Change by means of the telephone if there The is no -l one on-site who can fulfill this function.
Reactor Startup Supervisor will make an entry in the appropriate approval space identifying the person called along with the time and date.
If any of the 10CFR50.59 questions were answered "YES", a Safety Evaluation must be conducted per NHY Procedure 11210 prior to implementation of_the change. It may then become necessary to interrupt the test until the evaluation is completed, and the Field Change approved'. I DOCUMENTATION I After the Field Change has been reviewed and approved, the Test Director will reference the Field Changa at the appropriate points in the affected pro-l cedure and will attach the Field Change to the proce-dure. The Field Change will be documentedininthe the Field Change Log and should be documented Chronological Log.
zL 2 T~~_--_::r ry3 _ _
- _.~,. .
L' STPD REV. 2 Page 18 of 24 4.3.4 REPETITION OF PORTIONS OF A TEST If it becomes necessary to reperform steps within a procedure an entry in the Chronological Log will be made noting which steps were reperformed and the reasons why. If desired, the Test Director can insert additional " clean" pages containing the necessary steps. The procedure page(s) containing the reperformed steps shall be annotated to reference the log entry.
- If the repetition is lengthy, complex or of a; nature that could not be adequately documented in the Chronological Log, a Field Change will be issued to reperform the steps. A Field Change issued under these circumstances will generally include " clean" pages containing the necessary Whenever "
steps, clean" plus pages any are addi-used tions or deletions.
for repetition of portions of a test, the original field. copy should be. reviewed to insure that required QA witness points are properly identified.
The Test Director'must consult with the Rea tor Startup Supervisor and/or the Shift Test Director to determine which of the above methods is applicable in a given situation. .The above Chronological Log entry shall be initialed by both the Test Director and Shift Test Director if the Field Change option is not chosen.
4.3 5 TEST INTERRUPTION The following are examples of events which might constitute a test interruption:
- 1. Inability to maintain plant conditions as spe-citied in a Startup test.
- 2. Equipment or system problem affecting test per-formance and requiring support from individuals /
organizations not presently on site.
3 Insufficient number of test or operations per-sonnel present on-shift to conduct a test.
4 A determination by the Shift Superintendent or Unit Shift Supervisor that a test would place the plant in an unacceptable condition.
- 5. Awaiting SORC review and Station Manager appro-val of an INTENT Field _ Change.
f .n _ - - . . _ _ . - - - _
n ._ -
STPD REV. 2 Pego 19 of 24 4.3 5 TEST INTERRUPTION - Continued The Reactor Startup Supervisor or Shift Test Director will determine when a test is to be interrupted. The Shift Superintendent or Unit Shift Supervisor will be notified of the interruption. The Test Director will make an entry in the Chronological Log stating the reason for the interruption.
I Before continuing with the test the Test Director
- will reverify those prerequisites and intial con-ditions which apply based on the Test Director's judgement. This review shall be noted in the Chronological Log.
4.3.6 TEST TERMINATION The following are examples of events which might constitute a test termination:
- 1. Test procedure incorrect and/or incapable of ;
determining if objectives and/or accep'tance criteria can be met.
- 2. Performance of a test procedure reveals design or equipment defiencies which prevent the objec-tives and/or acceptance criteria from being met.
The Startup Manager, Reactor Startup Supervisoris or to Shift Test Director will determine when a test be terminated. The Shift Superintendent or Unit Shift Supervisor will be notified of the termination.
The Test Director will make an entry in the Chronological Log stating the reason for the ter-mination and any operations performed to place the plant in a safe, stable condition.
A terminated test will not be resumed until the I
problem has been corrected and authorization obtained from the Reactor Startup Supervisor. A terminated
' test will generally be repeated in its entirety.
l l
l t .- - . ~ . - . _ _ , . _ , . . ,
(..
~ ~ '
d' STPD REV. 2 Pego 20 of 24 1
4.3.7 TEST EXCEPTIONS
~A test exception shall be used.to document and resolve the following:
- 1. Failure to meet acceptance criteria.
' 2. Other situations or events as determined by the Reactor Startup Supervisor or Shift Test Director.
Test exceptions shall not be used to change a proce-dure.
Each exception will be numbered sequentially (for a given test) and entered on the Exception Log (Form 2 of Appendix C). The affected procedure step (s) shall be annotated with the exception number. The preparer shall sign and date the Exception Log.
The Test Director will ensure that all test excep-tions have been written and resolved prior.to l releasing the test for review per Section 414.
The resolution entry should describe the action taken to close out the exception or should refer to a spe-cific document which has been generated to close out the item.
4.4 TEST COMPLETION 4.4.1 DOCUMENTATION RESPONSIBILITY The Test Director will be responsible for the ensuring that the test has been completed, all
' required data collected, and all analyses completed.
The Test Director shall review the test results for preliminary acceptance and shall make the appropriate recommendation to the Reactor Startup Supervisor and Stcrtup Manager. The Test Director is also respon-sible for ensuring that all test exceptions are properly resolved and documented. The documentation package for a test shall include, in addition to the required data and analyses, the Chronological Log, Exception Log, Test Personnel List, Test Critique and Field Change Log. The forms for these logs are attached as Appendix C. The Test Equipment Data Sheet (Figure 3 of Appendix A) shall be included where non-permanent plant equipment was used to collect data if the test procedure does not contain an attachment for this purpose.
c . -s-w~e -, _e,- . .. _ __
- _ _ - - - - _ ~ _ _ _ _
I' '
l i4L.. " c REV. 2
"- STPD Page 21 of 24 V
4.4.2 . TEST CRITIQUE l The Test Director shall prepare a Test Critique (Form 4 of Appendix C) which should summarize test perfor-mance. The critique should discuss any problems encountered (either equipment or procedure related) outstanding exceptions, and.any suggestions.for improving the test. Any changes to controller para-meters or setpoints should be documented in the cri-tique.- The test critique shall be included in the documentation package for a test.
4.4.3 REVIEW AND' APPROVAL OF RESULTS The review and approval of test results generally fall'into three categories: preliminary acceptance,
~
partial acceptance and final acceptance. At the completion of testing at a specific plateau, the Reactor.Startup Supervisor will assemble all completed tests and analyses as well as any tests requiring preliminary or partial acceptance. These tests and results will all be listed on the appropriate startup test completion log (see ST-1).
Those tests requiring preliminary or partial accep-tance will be appropriately designated in the comple-tion log. At certain plateaus a number of analyses that previously received preliminary acceptance must be completed prior to escalating power. These analy-ses are listed in the Power Escalation Guidelines appendix of ST-1. The power escalation guidelines shall be used by the Startup Test Department and the SORC as a guide in insuring that all requirements for The completion log an escalation are fulfilled.
sheet,-together with the completed tests and any pre-liminary and partial analyses will be presented to the SORC for review.
The Station Manager shall make the final acceptance of all startup test results and associated prelimi-nary and/or final data analyses. Each progression from one major plant evolution to another will be This will consist approved by the of a review of all preliminary, Station Manager. partial and/or final test data analyses for all tests done during thebepre-vious evolution plus any other items which must completed prior to the change of plant conditions.
The Station Manager shall sign the test completion log and the results review sheets where. appropriate to signify acceptance of those tests and analyses presented and to authorize the startup test program to proceed. In the following paragraphs, any references to Station Manager approval refer to the approval process at the completion of a plateau.
Station Manager approval is not required at the completion of any individual test during a plateau.
s .
__.m__.-.m_ ___
w y -_ , _ - . __ . . . _
?
. w'
} vj REV. 2 STPD Page 22 of 24 l'
4.4.3 REVIEW AND APPROVAL OF RESULTS - Continued Those tests which are partially performed at a series of different plant conditions shall have each step or section performed signed by the Test Director, reviewed by the Reactor Startup Supervisor l and Startup Manager, and submitted to SORC for partial acceptance. The criteria.used for partial acceptance shall be that all required operations and data collection have been completed and that any applicable acceptance criteria have been' satisfied.
- Results review by _the Reactor 'Startup Supervisor and Startup. Manager will be documented on the Test Results Review Form (Form 5 of Appendix. C) with l appropriate comments signifying which sections are The testing program will recommended for acceptance.
then proceed. Final acceptance will be made at the completion-of the entire test using the applicable acceptance criteria. Attachment 9.2 of ST-1 will record this final acceptance.
Those tests that are performed in their entirety at each of several plateaus will be reviewed als a completed procedure at each plateau but may be listed as partially completed on Attachment 9 2 of ST-1.
These tests are listed as partially completed because-the FSAR commitment.is not considered fulfilled until performance at the last plateau. The Test Results Review Form will be completed for each performance of these tests.
A number -of the startup tests require extensive data analysis. For these tests a preliminary enalysis and evaluation may be made in order to allow After the test an program to proceed without undue delay.
- initial review of the test data, the Reactor Startup Supervisor will make the recommendation (again using the Test Results Review Form) to the Startup Manager and SORC that a preliminary acceptance be made. SORC Will review the test and, if satisfied that the plant is in a safe condition and no apparent problems will result from a change in plant conditions, will recom-mend that the Station Manager accept the results on a preliminary basis. The final analysis should nor-mally be completed prior to exceeding a specific power level. ST-1 contains further guidelines on this subject.
Test Exceptions shall be classified as Open "Open" test or
" Closed" prior to submittal to SORC.
exceptions shall be tracked on the Open Items List by Technical Support. Any open test exceptions will be discussed on the Test Results Review Form.
g .
____._~'_'g_ ._________
i
.e.N
1*
~. 1; e
~
' STPD REV. 2 Page 23 of 24 l
4.4.3 REVIEW AND APPROVAL OF RESULTS - Continued Whenever supplemental information must be added to approved test results, the Startup Test Supplemental Information Form (Appendix C, Form 8) should be completed. Additionally, the Startup Test Supple-mental Information Form must be used to close "Open" Test Exceptions to approved test results.
4.4.4 STARTUP REPORT The Reactor Startup Supervisor will be responsible for preparing a Startup Report in compliance with USNRC Regulatory Guide 1.68, Revision 2, Section C.9, and USNRC Regulatory Guide 1.16, Revision 4, Section C.1.a.
5.0 QUALITY ASSURANCE 5.1 PERSONNEL QUALIFICATIONS Personnel assigned in startup tests as' Test Directpr, or l Shift Test Director will have a Bachelor Degree inleast two Engineering or related sciences and will have at Individuals who do years of nuclear power plant experience..
not possess the formal educational requirements will not be automatically eliminated where other factors These provide suf-other fac-ficient demonstration of their tors'will be evaluated on a case-by-case basis and approved abilities.
and documented by the Startup Manager. All personnel will have their qualification documented and appr-oved by the Startup Manager.
5.2 PERSONNEL TRAINING Personnel assigned as Test Director or Shift Test Director will also receive training in the following areas:
A. General Employee Training as administered by the Seabrook Station Training Department.
B. Startup Test Program administrative program training in those aspects of the program applicable to procedure compliance, test performance, and test documentation.
This training will be administered by the Reactor Startup Supervisor.
C. Transient Analysis Training on selected transients which might be expected as casualty occurrences during various startup tests. This training will The be administered by Reactor Startup the Reactor Startup Supervisor. individuals from this training Supervisor may exempt based on their previous experience or the limited nature of tests that they may perform.
- STPD REY. 1
- Pcgo 24 of 24 1
- 5.2 PERSONNEL TRAINING - Continued Individuals designated as Shift Test Director will also receive either' Detailed Systems training from the Training Center staff, the PWR Information course from the Seabrook Station Training Department, or equivalent training from the Startup Test Department if the individual has not been pre-viously certified as Shift Test Director according to Start-up Test Department. instruction TPI-81.
5.3 QUALITY ASSURANCE PROGRAM The startup test program will be conducted using the New Hampshire Yankee Operational Quality Assurance Program as outlined below.
The startup test program will be administrative 1y controlled as outlined in this program description.
I The procedures will be reviewed for quality requirements by the Nuclear Quality Group.
Surveillance of Startup Tests will be conducted bh the Nuclear Quality Group and witness points will be. inserted.
l t
I