ML20137Z016

Independent Corrective Action Verification Program Millstone Unit 2 Sys Vertical Slice Review Svsr Checklists

ML20137Z016
Person / Time
Site:	Millstone
Issue date:	04/21/1997
From:	External (Affiliation Not Assigned)
To:
Shared Package
ML20137Z003	List: ML20137Z000 ML20137Z006 ML20137Z016
References
PROC-970421, NUDOCS 9704230311
Download: ML20137Z016 (38)

Text

<

b

E3

? >

PARSONS l

i 4

1 i

4 i

j i

j INDEPENDENT CORRECTIVE ACTION VERIFICATION PROGRAM i

i i

?

MILLSTONE UNIT 2 l SYSTEM VERTICAL SLICE REVIEW i

1 SVSR CHECKLISTS i

a k

3 i

i 1

I l

- PAR 8058 POWER GROUPINC.

SVSR Che klists 9704230311 970421 AprU 21,1997 PDR ADOCK 05000336 P PDR

MILLSTONE UNIT 2 SYSR CIECKLISTS TABLE OF CONTENTS f

Section Titlf East

' INTRODUCTION 1 1.0 SCOPE AND BOUNDARY CIECKLIST 9 1.1 Purpose 9 1.2 Prerequisites / Documents 9 1.3 Actions / Requirements 9 2.0 LICENSING AND DESIGN BASIS REVIEW CIECKLIST 12 2.1 Purpose 12 ,

2.2 Definitions 12 2.3 Prerequisites / Documents 13 I 2.4 Action / Requirements 14 3.0 MODIFICATIONS CIECKLIST 18 3.1 Purpose 18 3.2 Prerequisites / Documents 18 3.3 Action / Requirements 18 4.0 CORRECTIVE ACTION PLAN REVIEW 23 4.1 Purpose 23 4.2 Prerequisites / Documents 23 4.3 Action / Requirements 23 5.0 TESTING CIIECKLIST 24 5.1 Purpose 24 5.2 Prerequisites / Documents 24 5.3 Action / Requirements 24 6.0 PROCEDURES REVIEW CIECKLIST 27 6.1 Purpose 27 6.2 Prerequisites / Documents 27 6.3 ~ Action / Requirements 27

- PAR 88N8 MNR BROUP BC.

SVSR Checklists i Apn121.1997

l MILLSTONE UNIT 2 SVSR CIIECKL.ISTS TABLE OF CONTENTS

{

Section Iillt East  !

7.0 WALKDOWNS CIIECKLIST 30 t 7,1 Purpose 30 7.2 Prerequisites /Doctiments 30 l 7.3 Action / Requirements 30 l

Exhibits Exhibit 1 OVERVIEW OF SVSR CHECKLIST DEVELOPMENT 2 Exhibit 2 SVSR CHECKLIST REQUIREMENTS - CONFIRMATORY ORDER 3 Exhibit 3 SVSR CHECKLIST REQUIREMENTS NRC OVERSIGHT PLAN 4 Exhibit 4 SYSTEM SCOPE AND BOUNDARY DESCRIPTION 11 Exhibit 5 SYSTEM MODIFICATION SCREENING

SUMMARY

REVIEW 22 A'ITACHMENT 1 MECHANICAL DISCIPLINE CONSIDERATIONS 32 ATTACHMENT 2 ELECTRICAL REQUIREMENTS CONSIDERATIONS 34

- PAR 88R8 P8WER GR88PIRC.

SYSR Checklists li April 21,1997

, a e

4 DEVELOPMENT OF SYSTEM VERTICAL SLICE CHECKLISTS Introduction This instruction provides a generic framework based on checklist modules that can be

used to develop a system specific checklist to support System Vertical Slice Reviews

(SVSRs).

Exhibit 1 provides an overview of the generic SVSR checklist development process.

System specific checklist development is based on the process outlined in Exhibit 1, system specific cequirements, and the generic checklist modules in this instruction.

The generic checklist modules are based on the requirements of the Confirmatory Order, the NRC Oversight Inspection Plan, and NRC Inspection Guidelines. Exhibit 2 and 3 provides matrices to cross reference of Confirmatory Order and NRC Oversight Plan requirements to the generic checklist modules included in this instruction.

All checklist modules contained in this instruction are generic and applicable to a variety of systems. After identification of SVSR systems by the USNRC, the genecic modules are used as the framework to incorporate system specific considerations. The attachments at the end of this instniction provide examples of system specific considerations for mechanical systems (Attachment 1) and electrical systems (Attachment 2) that could be incorporated during system specific checklist preparation.

The SVSR checklist development process noted in Exhibit 1 is used to prepare a system specific checklist by defining system boundaries, identifying licensing and design requirements, and identifying configuration management considerations. Generic checklist modules guidance provided in this instruction that supports checklist development includes:

1. Defme System Scope and Boundary

2. Identify Licensing and Design Requirements

3. Evaluate Configuration Management

• Modifications

• Corrective Action Plan

. Testing

• Procedures e Operations and Maintenance Practices e Physical Plant Verification

-Passessrowseseurme.

SVsR Checklist 1 April 18,1997

A EXHIBIT 1 OVERVIEW OF SVSR CHECKLIST DEVELOPMENT DEFINE SYSTEM SELECTION SYSTEM FROM NRC BOUNDARY i C"" "" """ l l

y De(me System + [

N Scope / Boundary &

Corinderations

+ Deasons difreema

______________________________________ y____________.

U Y Regulatory V

LICENSING AND Requirements + V DES!ON y Current Licensms Basis 4 Onginal Design Basis REQUIREMENTS Programmane 4 Review Review Regulatory Inputs 4

l Critical Deip h Design Basis

[ l Requirements Checklist

_______________________4__. _______________

EVALUATE t Y v i CONFIOURATION Input to System Mod is the Correcuve Achoa Osfine Other MANAGEMENT Review Necessary? Plan of CMP !nvolved? Configurauon AllMads Management Revient Un wried CONSDERATIONS y List

%g um syman l

System Mod " I '

' " CAP Review Procedures,Tesung, Review l Walkdouns,etc.

Problem Reviews Y List I System Mod System CAP System Requirement Checklist Requirement Checkhst Configuration Checklist Y Y Y V INSPECTION ACTIVITIES BASED ON CHECKLIST REQUIREMENTS Mecharucal Training otherDisciplines irgerviews Walkdomus Electncal Pmeurement and TechnicalReps 1&C Civil as Required

- PABk3ESPOWG BBWWC, SVSR Checklist 2

APfil18'1997 s, __

l e

Exhibit 2 SVSR Checklist Requiremems AREA

.a'$

• a o,. E b Confirmatory Order Actions 3 $ 3 <

ec 3

5 3 jf g

1. }e j o.

Licensee committed to the scope of the ICAVP review encompassing modifications to the selected systems since initial licensing, including

• Review engineenng design X X Review configuration control processes X X X Verify current as modified plant conditions against design basis X X X Verify current as-modified plant r,onditions against licensing basis documeritation X fX X Verify that design requirements are translated into operating procedures X Verify that design requirements are translated into maintenance procedures X Verify that design requirements are translated into test procedures y Verify that licensing bases is translated into operating procedures y Verify that licensing bases are translated into maintenance procedures j Verify that licensing bases is translated into test procedures X Verify system performance through review of specific test records X Verify system performance through y

observation of selected testing of particularI,ystems Review proposed and implemented corrective actions for Licensee-identified design deficiencies X l

- PasseelPOWB GOOOP 30, 3

SVSR Checklist April 18,1997

~

9 Exhibit 3 SVSR Checklist Requirements AREA

.e $ m Oversight inspection Plan Actions

'E$

E m

E a E $

< 5 O o "8 3 e

52 2 w

$oa 2 3 Design modifications are adequate X Control of the design has been maintained since issuance of the initial operating X license Control of the design bases has been maintained since issuance of the initial X X operating license System's current configuration conforms to its licensing bases and will be capable of X X X

performing its intended function System's original design that has ncit been modified conforms to its licensing bases and X X X will be capable of performing its intended function System modifications made since issuance a

of the initial operating licence conform to its X X X licensing bases and will be capable of performing its intended function Verify that the licensee's design engineers had sufficient technical guidance to perform X X I

assigned engineering functions.

Verify that the regulatory requirements are correctly implemented and the system can X X X perform its specified functions Verify that the licensing-bases are correctly

, implemented and the system can perform X X X its specified functions The updated Final Safety Analysis Report (FSAR) accurately reflects the current X X licensing bases, The updated Final Safety Analysis Report (FSAR) accurately reflects the current plant X X configuration The updated Final Safety Analysis Report (FSAR) accurately reflects the operational X X X characteristics The analyzed facility configuration in the design bases is consistent with the current X X plant configuration of the unit The analyzed facility configuration in the design bases is consistent with the current X X X plant operational characteristics of the unit 4

4

- M BSEESP9WER GBO W BC.

SVSR Check. list 4 April 18,1997 t

.~

A AREA eU w 3Eh

• e E b Oversight inspection Plan Actions e 3 < 5 3 3 E9 2 O e g a

$UQ E 3 The correct licensing-bases information has been reflected in the maintenance X procedures The correct licensing bases information has been reflected in the responsible X engineering procedures The correct iicensing-bases information has y

been reflected :n the operations procedures System design changes have not invalidated precoerational testing. X X System design changes have not invalidated startup acceptance X X Design controls have been applied t X X temporary modifications design changes Design controls have been applied to design y

procedure changes

{

Design controls have been applied to y I change the configuration of the facility. I Design controls have been applied to X X change the operation of the facility.

Verify the adequacy of the licensee's corrective actions as part of the CMP and in X X response to the ICAVP findings.

Assess the adequacy of the licensee's efectiveness ofimplementation of the X X corrective actions developed as part of the CMP and in response to the ICAVP findings.

Review of procedural controls for modifying or changing the facility operational X X characteristics.

Verify the current configuration accurately reflects the licensing-bases, including the X X updated FSAR.

The calculations and analyses were performed using recognized and acceptable X X analytical methods. _

The assumptions made in calculations supporting the change are technically X X sound.

The assumptions made in analysis supporting the change are technically X X sound.

- PARISBB PgWEB BRIEP BC.

SVsR Checklist 5 Apn! 18,1997

AREA

$ e Oversight inspection Plan Actions e$

E ye E e a E $

15 3 I

)

g 8y 2 O y 2 y 38 '

The results of calculations supporting the unmodified portions of the original configuration and design changes are X reasonable (based on engineering ,

Judgement) for the scope of the change.

The results of analysis supporting the i unmodifad portions of the original configuration and design changes are X reasonable (based on engineering a judgement) for the scope of the change.

The licensee considered the effect of a  !

X X change on design margins.

The appropriate level of engineering and management review existed during tho X X l design phase and prior to implerrentation.

The licensee considered the effect of a change on pre-operational acceptance test X X results.

The licensee considered the effect of a y y change to startup acceptance test results.

The licensee considered the effect of a  ;

change to system baseline acceptance test X X l results. ]

Design changes were accomplished in i accordance with the licensee's approved X X procedures. '

Design changes are accurately reflected in X X operating procedures.

Design changes are accurately reflected in X X maintenanco procedures.

Design changes are accurately reflected in y y test procedures Design changes are accurately reflected in y y training materials.

Proposed design changes, subsequently cancelled, were not replaced by procedural X

changes that imposed excessive burdens on plant operators.

The walkdowns will be multi-disciplinary reviews including, as a minimum, Mechanical systems, X Mechanical components, X Electrical power, X Civil and structural design, and X instrumentation and control. X

- Passeusreumisecurluc.

sVsR Checklist s April 18,1997

- . - - - - . _ . ~ _ - . - .- - .- - .. .~. . .-. . . - . .

s a

AREA eU m 4 Eh

• 1  ? $

Oversight inspection Plan Actions je 3 < 5 E 8g 2 O y }5 g w l

33 a 3 '

Walkdowns will verify adequate control of surveillance procedures y Walkdowns will verify adequate control of operating procedures, X Walkdowns will verify adequate control of maintenance procedures, Walkdowns will verify adequate control of test procedures, Walkdowns will verify adequate control of operator training, i

Walkdowns will venfy adequate control of plant simulator configuration. y Verify that the current configuration is :

consistent _with the licensing bases at the.

level of detail contained in < l Piping and instrumentation diagrams X X X (P&lDs)

Verify that the current configuration is consistent with the licensing bases at the '

y y level of detail contained in piping isometric drawings  !

Verify that the current configuration is i

consistent with the licensing bases at the X X level of detail contained in electrical single-line diagrams ,

l Verify that the current configuration is consistent with the licensing bases at the level of detail contained in emergency, X X X abnormal, and normal operating procedures.

j Verify the licensing-bases information contained in the updated FSAR. X Verify the licensing-bases information y

contained in docketed correspondence.

Verify the analyzed configuration is consistent with the current plant X X i configuration. l Verify equipment location and identification numbers are as indicated on the P&lD X Verify equipment name plate data is consistent with design specifications.

y Verify equipment name plate data is consistent with enalyses. X

-Passessrestaesserus.

SVSR Checklist 7 April 18,1997

i I e AREA

.a U m Oversight inspection Plan Actions

• h m 3 <

a.  ? b h

'he 3

'5 g 3 8R s e 3 S

3y c.

Verify that the location of pipe supports, snubbers, and other pipe restraints are X consistent with design specifications.

Verify that the location of pipe supports, snubbers, and other pipe restraints are X consistent piping stress analyses.

Verify that divisional separation of safety-related systems, sinJctures and components, seismic II/l, and other topics addressed by the licensee's hazards X analyses are reflected in the current plant configuration.

Modifications that appear to have been completed recently will be screened to X assure adequate documentation

- reassesreuseesserlue.

SYSR Checklist 3 April 18,1997

s a

1.0 Scope and Boundary Checklist i

1.1 Purpose Provide a process for systematically defining the selected system scope and l boundary conditions through the use of system functions and critical design 1 characteristics of the selected system.

1 The completion of this checklist shall be documented on the attached " System Scope and Boundary Checklist Form" I l

1.2 Prerequisites / Documents l

1

• ICAVP Tier 2 Input, (Critical Design Characteristics Team). I e SER l e Technical Specifications e FSAR e P&ID l

• System Elementasy Drawings

• System logic diagrams

• System Specifications

• Manufacturers Performance Test Data 1.3 Action / Requirements Interfaces with, and portions of, other systems may be included within the boundary of the selected system to the extent they are necessary to support the functional requirements of the selected system.

System boundaries may be defined at appropriate components that provide physical isolation, as long as the selected boundary does not split the component between systems.

All passive devices such as supports and restraints, within the system boundary are included within the scope of the SVSR 1.3,1 Determine System Functional Requirements Determine the functional requireracnts for the system and each active component during normal, accident and abnomal conditions. Functional requirements must be determine for each mode of syste n operation

-russesreueesserme.

SVsR Checklist 9 April 18,1997

O Identified System Functions must have the basis used for the determination identified. (System Functions and the appropriate basis document are to be noted on Exhibit 4.)

1.3,2 Obtain the Tier 2 list of Critical Design Characteristics for the system and add to Exhibit 4.

NOTE Assessment of the selected system in the area of Critical Design Characteristics  !

shall not be delayed pending receipt of a complete list. Action shall commence as

)

soon as sufficient data is received to support the inspection effort. However, this j checklist requires all Critical Design Characteristics to be evaluated in order to be complete.

l l

1.3.3 Identify the supporting system interfaces.

1.3.4 Prepare a System Scope and Bounday Description using the system functions and the identified critical design characteristics. The description shall be in the format shown in Exhibit 4. Marked-up drawings supporting the narrative description are required.

1.3.5 Verify that the configuration of the system supports the Critical Design Characteristics.

1.3.6 Compare with Millstone Unit 2 System Bounday. Resolve differences prior to proceeding with the balance of Tier 1 activities.

-rensessreussesorme.

SysR Checklist Is Apnl 18,1997

1 A

Exhibit 4 System Scone and Boundary Description System Name:

l 1 System Scope

Description:

\

l l' The following information is required to complete the System Scope and Boundary Checklist. Additional pages (in addition to the required marked up drawing (s) may be

used if necessary. If additional pages are used, indicate below the total number of i

attached pages for each category ofinformation

System Functions

5 Critical Design Characteristics (Tier 2):

?

Supporting System Interfaces:

i.

t k

i a

a Prepared By: Date:

k i

- NBIMBFSMB M WB.

SVsR Checklist 3 11 April 18,1997 4

4

- - - . - - - -,ve,ww.

i

}

A 2.0 Licensing and Design Basis Review Checklist

2.1 Purpose

Provide a process for the systematic review and assessment of compliance with the Licensing and design bases ofMillstone Unit 2. This checidist includes an assessment the' maintenance of the Licensing and Design bases and the conformance of Millstone Unit 2 with the design and licensing basis information since initial operation to the present.

The review will follow the following general outline:

. Identification of Regulatory Requirements e Identification of UFSAR Commitments e Identification of Design Inputs and Requirements e Evaluation of Design Inputs e Calculation and Specific Measurements '

• Other Configuration Management Measurements as appropriate 2.2 Definitions Current Licensing Basis (CLB) is the set of NRC requirements applicable to a specific plant and a licensee's written commitments for ensuring compliance with and operation within applicable NRC requirements and the plant-specific design basis (including all modifications and additions to such commitments over the life of the license) that are docketed and in effect. The CLB includes the NRC regulations contained in 10 CFR Parts 2,19, 20, 21, 26, 30, 40, 50, 51, 54, 55, 70, l

72, 73,100 and appendices thereto; orders, license conditions; exemptions; and

]

1 technical specifications. It also includes the plant specific design-basis information '

defined in 10 CFR 50.2 as documented in the most recent final safety analysis I report (FSAR) as required by 10 CFR 50.71 and the licensing correspondence i I

l l

- NESIEBPOWB EROW WB. '

SysR Checklist i 12 April 18,1997

e such as licensee responses to NRC Bulletins, generic letters, and enforcement actions, as well as licensee commitments documented in NRC safety evaluations or licensee event reports.'

Design Basis That information that identifies the specific functions to be performed by a structure, system, or component of a facility and the specific values l or ranges of values chosen for controlling parameters as reference bounds for design. These values may be (1) restraints derived from generally accepted state-of-the-art practices for achieving functional goals or (2) requirements derived from analysis (based on calculation and/or experiments) of the effects of a postulated {

accident for which a structure, system, or component must meet its functional goals.2 l l

l 2.3 Prerequisites / Documents

• Design Specifications

• Design Input Documents

. System Scope and Boundary Documentation e Critical Design Characteristics Documentation e Original Design Specifications

• ICAVP Regulatory Requirements / Commitments Documentation e

List of all system modifications since the issuance of the Operating License.

. List of architect engineer identified design deficiencies issued at initial startup e Performance Calculations

. License amendments e Technical Specifications, revisions, and SERs e UFSAR

' 10 CFR 54.3 (a) 2 10 CFR50.2

- NBSOBEP9WB GBOEP WB.

SVsR Checklist 13 April 18,1997

> l Applicable Codes, Standards, and Regulatory Guides

• Accident Analysis Calculations e Performance Calculations '

• Equipment Specifications 2

• Instrument Setpoints Surveillance Tests and Procedures

. Technical Specifications e

Design Guides / Design Standards etc. prepared by or for NNECo.

Design Basis Documentation as defined by NNECo 2.4 Action / Requirements 2.4.1 Identification of Regulatory Requirements e Prepare a summary of the licensing' basis for the system that were applicable at the time the operating license was issued.

Prepare list of post-operating license commitments applicable to the system , including those in correspondence that modify the licensing basis.

• Prepare list of other changes since initial operating license such as license amendments and technical specifications that modify the '

4 licensing basis.

2.4.2 Identification of Commitments

• Review list of all system modifications since the issuance of the Operating License, establish order ofimplementation or inspection  !

l process. l l

e Have the architect engineer identified design deficiencies issued at initial startup been addressed and corrected?

4 4

- PasssesroutsesserInc.

SVsR Checklist 14 April 18,1997 J

1 A

e Review those portions of the system that have not been modified from initial operation to the present to verify:

e conformance to the licensing basis.

. that they are capable of performing their intended functions.

4' '

Does the system design incorporate and meet the licensing basis commitments?

2.4.3 Identification of Design Inputs and Requirements

.

• Is there a Design Input for the system? If"YES" review against the Design Input Checklist for adequacy.

• Prepare a Design Input checklist basect on ANSI N45.2.11 requirements.

2.4.4 Design Input Evaluation

. Are applicable Codes, Standards and Regulatory Guides referenced in the Design Input, Performance Calculations and Specifications?

e Verify that the calculations, specifications, and design specifications incorporate the original licensing basis (as modified).

• If the original design was based on any assumptions are these i

assumptions still valid.  !

• Does the UFSAR reflect the Current Licensing Basis Does the Design Basis Documentation, as defined by NNECo, identify design define the Design Basis 7 e

Determine if the System design basis is in accordance with the licensing and regulatory requirements (licensing basis) for the system.

• Is the Design Basis Documentation adequately controlled and revised l as required to reflect changes to the Design Basis.

- Passessrousiesserme.

svsa checklisi 15 Apnl 18,1997

i J

2.4.5 Calculation and Specification Measurements l

Do the Calculations conform to the Design Inputs ?

)

Are any assumptions used in the calculations technically sound ?

e Verify that the system design / performance calculation results envelope 1

any performance requirements used or assumed in the Chapter 14 Accident Analysis. Where more than one flow path alignment is used ' i for the system each alignment should be checked Are appropriate margins used for establishing the design basis of equipment.

e Were system calculations and analysis performed using recognized and acceptable methods?

l e

Are the results of the calculations reasonable and consistent with the I design input 7 j e Is data in the UFSAR consistent with the plant design calculations and

]

analysis?

e Do the system calculations / analysis reflect the current plant configuration and operation?

2.4.6 Other Configuration Management Measurements e

Verify the seismic and safety classification of those components and portions of a system that perform a critical function.

Verify that non-safety ponions of the system are isolated by automatic valves meeting single failure criteria or that calculations are available demonstrating that any loss of flow to the non-safety branch will not effect the required operation.

Verify that safety grade power and control signals are provided to the critical components.

- PassessPsWEB eteerme.

SVsR Checklist 18 April 18,1997

, , , , . , , . - .- ,,, ~ ,-

A e

Review the control logic, interlocks, power supply, and manual controls associated with pumps and valves for required operation to -

support system design basis.

For instrumentation that provides initiation or permissives for system operation verify the range, set point, and set point calculations are adequate.

Does the system design incorporate and meet the licensing basis commitments?

e Does the data in the UFSAR reflect modifications or changes in the licensing basis?

l i

- PARIABBPOWER EBOW BB.

SVsR Checklist g {

April 18,1997

1 1

3.0 Modifications Checklist  !

3.1 Purpose

Provide a mechanism for the systematic review and assessment of all modifications I for the subject system, determination of major or significant modifications 1

requiring further review, and to validate the status of modifications made to the

{

system configuration since original hcensing.

i 1

1 3.2 Prerequisites / Documents 1 e List ofModifications e Design Control Procedure e Configuration Management Plan

• Configuration Management Procedures i

e Copies of Modifications and all Attachments 3.3 Action / Requirements Record the results of the System Modification Summary Review Form (Exhibit 5) 3.3.1 Modification Package Initial Screening

• Was the modification to correct a Performance Deficiency

• Was the modification to correct a Regulatory Requirement?  ;

• Review the modification to determine if any unreviewed safety questions were introduced.

• Is a 10 CFR 50.59 Safety Evaluation required for the Modification?

• Has a 10 CFR 50.59 Safety Evahiation been performed for the Modification?

• Does the package indicate plant documents that will require revision as a result of the modification? (Documents would include: Calculations, Drawings, ASME Design Specifications, UFSAR, Plant Procedures.)

• Is a UFSAR change required as a result of the modification?

• Is the Design Input defined or referenced in the package?

• Does the package document the effect of the modification on other systems?

- rasseusreumenewus.

sVsR Checkist Is April 18,1997

,-~ .__ . _ . . - - .

_ _ . . _ _ _ _ _ _ . . _ _ _ . _ _ . . _ ~ . . .

4 J

• Is there an Interface Reviews by other groups such as Operations, Training, Testing, Mamtenance, etc.?

3.3.2 Detailed Modification Review

• ' Was the modification performed in accordance with an Approved Design Control Program?

• Does the program provide proper controls for verification and approvals (including Plant Operations)?

• Did the modification consider " Holds" or " Design Change notices" for plant documents to alen the design and operating staff to In-Process modifications.

• Does the design input incorporate the critical function requirements :Ur the system?

• Are assumptions used in the design input technically sound?

• Does the modification meet the design input requirements?

• Does the design confirm the accuracy of any assumptions contained in the Design Input?

5 Does the modification have the potential to change the design basis or licensing basis?

• If the modification has the potential to change either bases, does the as-modified system meets the design / licensing basis?

• If the modification has the potential to change either bases, was the as-modified design / licensing basis correctly revised as pan of the modification process?

• Is the Safety Evaluation complete and adequate?.

• Has the modifications, if adding non safety equipment or modifications to stmetures, considered and evaluated seismic class 2-over-1 concerns?

• Are the cumulative effects of modifications on support systems, such as i

Cooling Water, HVAC, Electrical Power Supply etc. adequately addressed and reviewed as part of the modification process ?

l

- MPOW MEW W.

SVSR Checklist IS April 18,199*i

i 3

i

• Verify the seismic ana Afety classification of those components and portions j

of a system that perform a critiuti function.

? .

(

• Verify that non-safety portions of systems are isolated by automatic valves

meeting single failure criteria, or that calculations are available demonstrating  ;

that a failure in the non-safety branch will not affect the system to perform its screty function.

• Verify that safety-grade IE electrical power and control signals are provided to critical components. ,

• Review the modification and prepare a list of Configuration control documents and databases that could require revision as a result of the modification. The following is a list of typical documents to be considered:

+ P&ID Drawings

+ Operating Procedures

+ FSAR text, figures and tables e Surveillance Test Procedures

+ Elementary Diagrams I

+ ASME Design Specifications

+ One Line Diayans

+ Training and/or Simuk=.

+ Instrument Set Points

+ Fire Protection Evaluation Report (FPER)

+ Calculations i

+ System Descriptions l

+ Maintenance Procedures  ;

+ Classification /EQ lists  !

• Did the modification correctly identify the documents requiring revision?  :

• Have the critical configuration-control documents and databases been correctly revised to incorporate the modification?

l 1

-MMWK SysR Checklist IS April 18,1997 I l

• For new or revised calculations that were performed for the modification did i 1

they use recognized analytical methods?

• For new or revised calculations that were performed for the modification all l assumptions technically sound?

Does Post-Modification testing demonstrate that the modified system meets the performance requirements? I Does Post-Modification testing validate the Pre-Operational acceptance l l

testing?

• Have modifications that may reduce the design margins for a system been adequately reviewed and approved. l Did the modification contain any " temporary" changes? Were these changes analyzed and controlled?

• If a proposed modification was canceled did it result in procedural changes that could impose an excessive burden on the plant operators during normal or I emergency operating conditions?

• What controls were used to accept and incorporate the design documents any differences between the as-built and as-designed configuration.

• Has the modification been installed in accordance with the Modification package design?

• Were any deviations between the as-designed and the as-built modification adequately resolved?

• Are the original design analysis, applicable to the unmodified portions of the system, conservative and reasonable for supporting the design basis of the modified system?

• Have the program requirements been followed for " temporary" modifications?

-Passessroseseserme.

SysR Checidst 21 Apnt 18,1997

,. . __- - . - . - ~ - - . ~ . - . - .-

l l

l 1

a l

\ ,

l System Modification Screening Summary Review Form Exhibit 5 l

System: Modification Number:

Brief description of Modification:

Modification Required for:

Regulatory Requirement Performance Deficiency Other:

Safety Evaluation Required?

yes no l

l UFSAR change required? l yes no l

Design Input defined or referenced?

l yes no Plant Document changes identified?

I yes no Interface reviews specified?

yes no Detailed Modification Review Required?

yes no Comments:

l Engineer: Date:

1 Team Leader: Date:

- FMESN FEME MEW M.

SVSR Checklist l

22 April 18,1997 l

. _ . . . ~ . . . . . . . _ _ . _ . _ .

.. . - . - - . .-. - . - -. . _. . . ~- ..

0 4.0 Corrective Action Plan Review

4.1 Parpose

Review the proposed and implemented corrective actions for design deficiencies identified by the NNECo during the implementation of the Configuration Management Corrective Action Program.

4.2 Prerequisites / Documents

• NRC Significant Action List

• Conective actions identified by NEECo 4.3 Action / Requirements

• Is the problem clearly identified?

• Does the solution identify the root cause?. .

Does the root cause identify any generic or prograr.imatic issues?

e Have the corrective actions been adequately document <,d and any required configuration control document changes made? I Is the corrective action technically and programmatically acceptable?

l

- Passessroutsassur me.

sysn checkiist 23 April 18,1997

s 5.0 . Testing Checklist .!'

5.1 Purpose

Provide a process for the systematic review and assessment of testing requirements for the selected system by evaluating:

• Test Acceptance Criteria and Basis

• Testing Conditions, and System Boundary Considerations Test Performance and Documentation e Post Testing Review and Evaluation The Testing Checklist is grouped into two types of tests:

• Pre-operational and Post Maintenance  ;

• Surveillance and Periodic 5.2 Prerequisites / Documents

• Pre-Operation Test Procedures e Pre-Operation Test Results e Maintenance Tests

• Maintenance Test Results e Surveillance Testing Procedures e Surveillance Testing Results e Calculations related to testing

• Completed Critical Function Checklist 5.3 Action / Requirements 5.3.1 Pre-operational and Post Maintenance

. Verify that the Pre-operational or post maintenance test acceptance criteria demonstrated that the System met the required critical performance / functional requirements. Verify the system alignment and test conditions demonstrate performance functional / requirements.

-prmrsuessoeurme.

SVsR Checklist 94 Apnl 18,1997

I

}

i e d to establish test results acceptance criteria for Review calculations use~ i

- acceptable analytical approach and correct testing configuration.

Verify that the Design Basis information was correctly incorporated into the pre-operational testing procedures with appropriate acceptance criteria.

The reviewer should determine if the system has been adequately tested to demonstrate that it can perform the intended safety function. This review should include initial tests performed by the manufacturer, start-up testing and preoperational testing.

.. Review the program for post maintenance testing of components prior to declaring them operable. The post modification testing should demonstrate that the system functional capability has been restored / maintained.  !

e Review the measuring and test equipment requirements to ensure the equipment can measure the parameter to the accuracy necessary to assure proper operation.

1 e Review the testing procedures to ensure that the method for measuring the parameter is appropriate for the physical condition of the plant.

}

• Review post test data reduction and analysis. Are the results of the analysis consistent with test conditions / assumptions and recognized analytical methods?  !

Does the post test analysis satisfy test acceptance criteria?

i I

5.3.2 Surveillance ar.d Periodic i e Review the Technicti Specification surveillance procedures and Inservice test procedures for technical accuracy and adequacy. Compare the testing alignment with the DBE alignment as part of tf determination of adequacy.

• Verify that surveillance test procedures correctly incorporate performance criteria and response requirements contained in the licensing basis and DBE analysis.

. - Verify that the surveillance test procedure acceptance criteria are adequate to ,

demonstrate continued operability.

I

- MM M M.

Sv5R Checklist N April 18,1997

4 e

e Are the Technical Specification performance requirements correctly incorporated into the surveillance testing procedures?

e Have the Surveillante test procedures been revised to reflect modifications?

e

_Are Engineering and Technical Support personnel involved in the revision of test procedures and do they review test results?

e Have the effects of design changes and modifications been incorporated into i

the testing program including the need to examine the impact on the original pre-operational and acceptance test data?

e Use surveillance test data, instrument set point data, manufacturers test data, pre-operational test data or calculations to verify that the critical performance parameters can be met. Also note margins.

• Do the testing conditions correctly consider the actual plant conditions during system critical function operation?

e Do the Technical Specifications reflect the current plant configuration?

e Review the measuring and test equipment requirements to ensure the equipment can measure the parameter to the accuracy necessary to assure proper operation.

Review the testing procedures to ensure that the method for measuring the parameter is appropriate for the physical condition of the plant.

Review post test data reduction and analysis. Are the results of th> analysis consistent with test conditions / assumptions and recognized analytical methods?

Does the post test analysis satisfy test acceptance criteria?

-PAssessPaulsegeurme, sysR Checklist 28 Apnl 18,1997

a x w. -A +w 4 a - - - J 4 a.aa e

6.0 Procedures Review Checklist l

6.1 Purpose Provide a process for the systematic review and assessment of the system related operation, maintenance and training procedures.

6.2 Prerequisites / Documents

• Operating Prccedures e Abnormal Operation Procedures e Emergency Procedures

• Alarm Response Procedures e Maintenance Procedures

• Surveillance Testing Procedures e Pre , Post-Operating Testing Procedures e Training Procedures

. Op Critical Diagrams e Functional / Logic Diagrams 6.3 Action / Requirements 6.3.1 Operations Procedures Does the operating procedure reflect the present plant configuration?

Does the operating procedure reflect the Design Operating Alignment for the system?

e Review the adequacy and accuracy of the alarm response procedures and operating procedures for normal, abnormal and emergency system operation.

• Walk down the system operating procedure to ensure that the procedure can be performed using the Main Control Panel and alternate shutdown controls.

2 1

PsRasesPOWEBesserme.

l SVSR Checklist l

U April 18,1997 l

i

} e u Walk down the system operating procedure to ensure that equipment is 4

accessible for operation. '

4 . If any special equipment is required for operation under DBE 1

conditions determine ifit is available and in working order, i

. Determine if the system operating procedures are consistent with the design and licensing basis. .

i 6.3.2 Maintenance Procedures

• Does the maintenance procedure reflect the present plant equipment?

l

. Review the adequacy and accuracy of the procedure relative to the l

ensuring the critical characteristics of the component are not reduced 3 due the maintenance procedure.

• Review the maintenance procedure for technical completeness.

e Ensure that the maintenance procedures incorporate applicable system ,

i modifications.

e Determine if the maintenance procedures compromise the design and a

I i

j licensing basis.

i e Verify that Vendor manuals are the latest version and reflect what is in '

the field.

. Review maintenance procedures for technical adequacy and for .

)

conformance with Vendor manuals for the equipment.

• Does the procedure reflect the precautions and limits for the equipment per the vendor documents?

e Determine if maintenance personnel receive adequate training for the system and if the training is consistent with the level of detail in the maintenance procedures.

6.3.3 Training Procedures

• Do the training procedures reflect the present plant configuration?

e Do the training procedures reflect the current plant configurations and equipment of the system?

- rassessreusasserus. --

SVSR Checklist 2s Apnl 18,1997

l e ~

o Review the operator training procedure for the system for technical completeness. Ensure that the training procedures incorporate system ,

modifications and that the operators are trained on the modifications.

Determine if maintenance personnel receive adequate training for the system and if the training is consistent with the level of d etail in the maintenance procedures.

l i

L i

l l

l l

l l

l 1

l t

i

- M M M M.

SVSR Checklist i 29 April 18,1997 i

A 7.0 Walkdowns Checklist Walkdowns Checklist 7.1 Purpose; Provide a process for the systematic identification of requirements for syste' m walkdowns to verify the physical plant installation, Primary Drawing information, and the implementation of the configuration management program, j

7.2 Prerequisites / Documents

• P& ids e One Line Diagrams I e Specifications

)

• Requirements / commitments list from other Primary checklists and discipline checklist requiring verification 7.3 Action / Requirements

1. Does the UFSAR reflect the system "as-built" configuration, including the current configuration and operational characteristics?

2. Is the current plant configuration consistent with the analyzed configuration?

3. Verify that equipment nameplate data is consistent with specifications and analysis.

4. Verify the location and type of pipe restraints installed against the piping analysis and Design Specifications.

S. Confirm Physical separation of systems

6. Confirm Electrical and Contrc 1 channel separation of systems.

7. Note any Modifications that appear to be a recent activity for further screening per the Modification Checklist.

-ranssesreseseseme.

SVsR Checklist 3s April 18,1997

l l

i e i

8. Verify that the current latest revision of P& ids, One Line Diagrams, Elementary and other critkal drawings are available for reference by plant I operations.

9. Verify that critical control room drawings reflect partially installed I

-1 modifications which are turned over to operations.

10. Verify that the current configuration of the system is in accordance with the design basis and licensing basis.

I1. Review the system configuration as installed in the plant and determine if the drawings which reflect the as-built design are consistent with the current design and licensing basis, regulatory requirements and commitments for the plant.

12. Verify the capability to perform local operation of equipment and the availability ofindication for local operation is in accordance with the l operating procedures. Environmental conditions that will exist in the area l under post accident conditions should be considered in determining the capability to perform local operation.

13. Perform a detailed verification to assure that the system as-built configuration agrees with the P&ID. The verification should include a review of the following characteristics of the system:

• Access to system components requiring local operation and are components accurately labeled.

• Are motor operated valves and check valves installed in the orientation required (or qualified as an active component) by the manufacturer. '

) Sv5R Checklist 31 April 18,1997

t Attachmr.nt 1 4

Mechanical Discioline Considerations l

Are the design pressure and temnerature correctly selected in accordance with the l

applicable piping code?

Are the system design conditions correctly stated in the ASME Design Specifications e

Have the code requirements for overpressure protection been correctly applied in the 1

design.

e Review valves and orifices in the systems for operating conditions with excessive (flashing er cavitation) pressure drops Review the pipe size and flow in the system for Excessive fluid system velocities (erosion) e 4 Do Valve, Flanges and other piping system components have adequate pressure- ,

i temperature ratings l l

Review the structure (s) housing the system for seismic design in the areas containing j i

safety class system / comp 3 neats. j e

Review the structural design for adequate load capacity of floor and roof designs to support piping and component !oads (dead and live) 1 Control valve operating conditions are i wnded by procurement Specifications or valve vendors as-manufactured data i

e Review piping and equipment support interfaces for adequate capacity for piping l reaction loads.

e Check required (as-built) heat exchanger duty with design requirements.

Check Surveillance testing procedures for testing to monitor heat exchanger fouling

• Review application of structural seismic response data to piping analysis and equipment seismic qualification.

• Review Seismic qualification data for operability of active components

- Passesre u ssuserum.

Sv5R Checklist 32 April 18,1997

.~ - . . . . . . ~ . . -. - _ . - . . . - - . - -

e Has minimum flow protection been provided for pumps that are subject to operation at zero or reduced flow ?

e- Is there adequate isolation valving provided in any cross connections between redundant fluid trains ?

e Are piping code / code class boundaries clearly identified and correctly applied to the system ?

e Does the design provide instru.nentation for performance testing and monitoring ?

e Has the design considered the potential transient fluid loadings which may occur in the system ? I e Has adequate NPSH been provided for pumps under all operating conditions and alignments ?

e Have the effects of flooding and pipe rupture been considered in the design ?

I l

I

- reusessesu m ansur me.

SvSR Checklist 33 Apnl 18,1997

. . - . -.- . - . . ~ . - - . . - - . . -. .. . - ..._ .. - - .-. ..

)

l

e 3 -

l Attachment 2 Electrical Requirements Considerations i )

1 1

l

' Are the AC and DC electrical systems design bases / inputs including applicable codes, standards, criteria and regulatory requirements identified?

Are the AC and DC electrical systems design bases /mputs complete and i

l adequate to define the design base?

i e Are the AC, DC and EDG design base calet:lations and analyses identified?

e Were the electrical system design base calculations and analyses performed using organized and accepted methods?

Are the assumptions used in the system calculations or analyses technically

j. sound and do they consider all operational modes and conditions that the AC or DC systems or components or EDG will experience?

e

Are the calculations or analyses results consistent with the design inputs?

.; e Do the design base electrical calculations identify available margins?

Are the AC and DC one line diagrams consistent with the supporting analyses?

e Do the electrical calculations and analyses support the rating of major safety related equipment / components including but not limited to:

• EDG's e medium voltage switchgear

.- low voltage switchgear a power center transformers e batteries and chargers e inverters e distribution panels e motor control centers e cables 1

e electrical penetrations

- PasseeBreulstenur NB.

SVsR Checklist M April 18,1997

~

4 Do the AC and DC calculations and analyses represent the current plant I configuration?

Test the informaion system to determine if modification could impact a design l

' l base electrical calculation?

l

• Is 'there a process in place to evaluate the impacts of a modification to the -

~

design base electrical calculations and available margin prior to implementing i the modification? l i

e Are the cumulative effects of modifications to design base electrical l

1 calculations effectively monitored and controlled?

j l

I I

-unuseummarme.

SVSR Checklist M April 18,1997