ML20236Q932

From kanterella
Jump to navigation Jump to search
Rev 4 to PP-01, Sys Vertical Slice Review
ML20236Q932
Person / Time
Site: Millstone Dominion icon.png
Issue date: 06/25/1998
From:
External (Affiliation Not Assigned)
To:
Shared Package
ML20236Q930 List:
References
PP-01, PP-1, NUDOCS 9807210128
Download: ML20236Q932 (24)


Text

..

\

I l

P3 O = PARSONS PP-01 MILLSTONE UNIT 2 ICAVP PROJECT PROCEDURES

Title:

System Vertical Slice Review REVISION 4 l Prepared by: Date: 48 Approved by: / # Date: 2Y dva 4#

er, Compen I ram l Approved by: , - Date:

M6 '

Project Director l REVISION HISTORY REVISION DATE REVISION DESCRIPTION O 04/03/97 Procedure initiation 1 06/09/97  ! corporation of NRC Comments 2 06/27/97 incorporation of NRC Comments 3 10/2/97 Reissue as Revision 3 Incorporation of Pl41 & Sample Plan References 4 06/26/98 Reissue as Revision 4 l

"J7"A8a!" M8u'm P PDR

i

!!) MILLSTONE UNIT 2 ICAVP PP-01 M PROJECT PROCEDURES TITLE: SYSTEM VERTICAL SLICE REVIEW REVISION: 4 DATE: 06/26/98 PAGE 2 OF 23 l t

l l

LIST OF EFFECTIVE PAGES l Page No. Revision No. Page No. Revision No. Page No. Revision No.

1 4 10 4 19 4 2 4 11 4 20 4 3 4 12 4 21 4 4 4 13 4 22 4 5 4 14 4 23 -

4 6 4 15 4 7 4 16 4 8 4 17 4 9 4 18 4 TABLE OF CONTENTS 1.0 PURPOSE ........... ... .. ..... ... .. .. ... . ..... ... .3

1.1 BACKGROUND

.. . . . . . . . . . . . .. . . . . . . . . . . . . .. 3 b 1.2 APPROACH. .. . . . . . . . . . . . . . .. .. .. . . . . . . . . . . . .. . 4 2.0 DEFINITIONS . .. . .. . . .. .. .. .. .. .. . .. .. 5 3.0 PREREQUISITES ... . ... . .. . .,.. . . . ..... . .. 6 4.0 PROCEDURE. . .... .... ... .. . . .. ... . 7 4.1 INSPECTION PREPARATION.... . . . . . . . . . . . . . . . . . . .. . . . .. ....9 4.2 CONDUCT OF INSPECTION.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .... . .. 11 4.3 INSPECTION ASSESSMENT AND REPORT . ... . . . ... . . . . . . . . . . . .. . . . . .. 16 4.4 TEAM MEETINGS / REVIEWS ... . .. ... . . . . . . . . . . .. .. .. .I8 4.5 SYSTEM ASSESSMENT. . . . . . . .. .... . ..... . . . . . . . . . .18

5.0 REFERENCES

......... ..... .. .. .. . . .. .. . .... ............... ...... .... 19 APPENDIX A . .. .. .. ......... ... ..... ......... .. ... ..... ... ... ........ .. . 2 0 APPENDIX B . . .. ......... .... . ...... .. .... . . ...... ...... .. ... 21 APPENDIX C .. .... . ... .. . . . .. . .. ... . .. ... .... ........... ... 23 s

< 'PI MILLSTONE UNIT 2 ICAVP PP-01 M .

PROJECT PROCEDURES TIT 1.E: SYSTEM VERTICAL SLICE REVIEW REVISION: 4 DATE: 06/26/98 PAGE 3 OF 23 1.0 PURPOSE This procedure establishes the overall objectives, scope, and general approach for conducting the System Vertical Slice Review (SVSR) for Mdistone Unit 2. The purpose of the SVSR is to confirm that the selected system's physical and functional characteristic.s are in conformance with its licensing and design bases. The SVSR will provide independent verification, beycod Millstone Unit 2's quahty as.mrance and management oversight, that they have identified and satisfactorily resolved existing nonconformances with the design and licensing bases and documented and utihzed the licensing and design bases to resolve nonconformances

1.1 BACKGROUND

On August 14,1996, the Nuclear Regulatory Commission (NRC) issued a Confumatory order directmg the licensee to contract with a third party to implement an Independent Corrective Action Verification Plan (ICAVP) to verify the adequacy ofits efforts to establish adequate design bases i

and design controls. The ICAVP is to employ a review of selected Millstone Unit 2 systems to l provide indapandent verification that, for the selected systems, the Millstone Unit 2 Configuration Management Plan (CMP) has identified and resolved existing problems, documented and utihzed I i

licensing and design bases, and established programs, processes and procedures for effective l

configuration in the future.8 The corrective action verification program was ordered to include:

e an in-depth review of selected systems which will address control of the design and design basis since issuance of the operatmg license for each unit; e selection of systems for review based on risk / safety based criteria similar to those used in implementing the Maintenance Rule (10 CFR 50.65);

e development and documentation of an audit plan that will provide assurance that the quality of results of the Licensee's problem identification and corrective action programs on the selected systems is representative of and consistent with that of other systems; O

' NRC Confirmatory Order, Page 11, Item II

s.

E3 MILLSTONE UNIT 2 ICAVP PP-01 i

PROJECT PROCEDURES

( TIT 1.E: SYSTEM YERTICAL SUCE REVIEW REVISION: 4 DATE: 06/26/98 PAGE 4 OF 23 l

. procedures and schedules for parallel reporting of Gndings and reco...r.#r.dations by the l

ICAVP team to both the NRC and the Licensee; and l e procedures for the ICAVP team to comment on licensee's proposed resolution of the 6ndmgs 1

I and remnendations.

l The ICAVP audit will be a multi-tiered approach using different and distmet mspection math ~h for each of a total of three tiers. This procedure covers Tier 1. In Tier 1, four systems will be inspected using a system vertical slice review process to test the thoroughness of the NNECo's l reviews in identifying potential nonconformances with the design and licensing bases.

1.2 APPROACH The ICAVP SVSR will review the configuration of the selected system through a combination of l

l inspectmg techniques including hmant reviews, calculation reviews, and plant walkdowns.

The SVSR will assess the CMP as it applies to the selected sptems through:

e a review ofplant records; e verification of current, as-modified plant conditions agamst design basis and licensing basis dommantation; e verification that design and licensing bases requirements are translated into operatmg procedures and maintenance and test prowdus, e verification of system performance through review of test records and/or obsenstion of testing of particular systems; and e review of proposed and implemented corrective actions for Licensee-identified design deficiencies.'

2 NRC Confirmatory Order, Page 12, Item III & Page I4, Item IV 8

NRC Coia atory Order, Page 13, Iteo III & Page 14/15, Item IV

e P.) MILLSTONE UNIT 2 ICAVP PP-01 E .

PROJECT PROCEDURES TITLE: SYSTEM VERTICAL SUCE REVIEW REVISION: 4 DATE: 06/26/98 PAGE 5 OF 23 Any discrepancies identified during the review, coupled with the type of discrepancy and its relative importance on the stmeture, system or components regulatory requirements, will provide the basis for SVSR reporting.

2.0 DEFINITIONS

. Design Basis ... that mformation that identifies the specific functions to be performed by a stmeture, system, or component of a facility and the specific values or ranges of values chosen for controlling parameters as reference bounds for design. These values may be (1) restramts derived from generally accepted statxf-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.'

. Licensing Basis, for purposes of the SVSR, the licensing basis for Mdistone Unit 2 consists of that set ofinformation upon which the Commission, in issuing an initial operathig license, based its comprehensive detemunation that the design, construction, and proposed operation of the facility satis 6ed the Commission's requirements and prosided reasonable assurance of adequate protection to public health and safety and common defense and security.8 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 dmkM and in effect.

The CLB includes the NRC regulations contamed in 10 CFR Parts 2,19,20,21,26,30,40, 50, 51, 54, 55, 70, 72, 73,100 and appendices thereto; orders, license conditions; exemptions; and 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 report (FSAR Amendment #48) as required by 10 CFR 50.71 and the licensing correspondence such as

Source: NRC Letter of October 9,1996 On Maintaining Plant Design

E3 MILLSTONE UNIT 2 ICAVP PP-01 E -

PROJECT PROCEDURES TITLE: SYSTEM YERTICAL SL:CE REVIEW REVISION: 4 DATE: 06/26/98 PAGE 6 OF 23 licensee responses to NRC Bulletins, generic letters, and enforcement actions, as well as l licensee commitments docummted in NRC safety evaluations or licensee event reports.'

. Engineering Design Bases (EDB) - The set of design constraints that are not included in the Licensing Basis but are implemented to achieve economies of operation, maintenance, procurement, installation, or construction. Such as:

. Infonnation that describes a system, stmeture, or component Operatmg values or parameters that are not reference bounds for design Information that identifies functions important for economic, maintenance, incta11ation, or other non-safety function of design basis systems, structures, or components Information and operating values describing the functions ofnon-safety systems e Calculations, descriptions, and other " outputs" Design Verification - The process ofindependently reviewing, confirnung, or substantiating the design by one or more methods to provide assurance that the design meets the specified design criteria and design inputs. The extent of design verification may range from a detailed check of the to'. I design to a check of the d: sign approach and the results obtamed.

3.0 PREREQUISITES e NRC announcement of the system (s) to be inspected

. ICAVP Audit Plan O ' 10 CFR 54.3 (r.)

ED MILLSTONE UNIT 2 ICAVP PP 3 PROJECT PROCEDURES TITLE: SYSTEM VERTICAL SLICE REVIEW REVISION: 4 DATE: 06/26/98 PAGE 7 OF 23 1'

4.0 PROCEDURE Resources Responsibilities SVSR Group Leader

. Reviews and approves the System Specific Instructions and Checklists

  • Supervises the overall SVSR Inspecuons e Directs the course of the SVSR and mamtams review focus j e Periodically reviews functional plens and system review progress
  • Reviews the da-ting and reporting of any discrepancies noted during the review.

SVSR System Lead e Coordmates the admmistration of the overall system specific inspection O

V e Defines system boundaries and amipts to be evaluated NOTE Interface with, and portions of, other systems will be included within the bo(mdary i

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 l boundary does not split the component between systems. All passive devices such  !

as support and restraints, within the system boundary are included within the scope of the SVSR.

Support system boundaries will be defined as:

Mechanical - the first level of support system interface.

l As an example, at a heat exchanger, the interface will be data associated with the temperature and flow rate of the cooling media. The interfacing system equipment / data / design will be reviewed to the extent that the input parameters can be validated with respect to a verified calculation or vendor document.

O Electrical - Electrical power will be verified from the actuating component or power V supply to the ultimate on site source required for the component to perform its intended function. All selected system loads and their design parameters will be reviewed. Review will focus on the review ofloads associated with the selected l

e E) MILLSTONE UNIT 2 ICAVP PP-01 E >

PROJECT PROCEDURES TITLE: SYSTEM VERTICAL SUCE REYlEW REYlSION: 4 DATE: 06/26/98 PAGE 8 OF 23 l system. Design documents will be reviewed to the level confirmmg that the l intended function can be accomplished.

Instrumentation and Control -I&C will be verified from the individual field sensor to the component or device required to perform an intended function. Review will l include any portion of the instrument loop, power supplies, circuitry, interfacing hardware and range / set point required to assure the intended, function is accomplished. The SVSR will concentrate on verifying (1) signals associated with the selected system, and (2) that the instrument loop performs its primary function.

Design documents will be reviewed to the level of confirming that the inteMed l function can be accomplished.

Piping - will be reviewed to the point of interface with the component and/or supporting structures. Supporting structures will not be considered within the system boundary.

. Directs the developmmt of the sptem specific review instructions, cWklict3 and observation / question forms e Defines necessary resourcea to facilitata the review

. Provides orientation and trauung to team members on the approach, matMlogy and overall project eg+Adons e Reviews and approves system specific review instructions, cWklicts, and supplements.

  • Develops a summary report of each system specific review and a wupJensive report of the mspection results SVSR Team Members
  • Develop system specific review instructions and checklists
  • Conduct the system reviews in accordance with this review plan and the system specific mstructions and cWklict=
  • Develop system specific reports and make appropriate presentations on the status of the system specific reviews to Team Supervision, Deputy Project Director, Project Director.

O

'!D E

MILLSTONE UNIT 2 ICAVP PP-01 PROJECT PROCEDURES O - =r -uceucE-REVISION: 4 DATE: 06/26/98 PAGE 8 OF 23 l system. Design documents will be reviewed to the level confirming that the l

, intended function can be accomplished.

Instrumentation and Control - I&C will be verified from the individual field sensor to the component or device required to perform an intended function. Review will l include any portion of the instrument loop, power supplies, circuitry, interfacing hardware and range / set point required to assure the intended, function is accomplished. The SVSR will concentrate on verifying (1) signals associated with the selected system, and (2) that the instrument loop performs its prim _ary function.

Design documents will reviewed to the level of confirming that the intended function can be accomplished.

Piping - will be reviewed to the point of interface with the component and/or supporting structures. Supporting structures will not be considered within the ,

system boundary.

. Directs the development of the system specific review instructions, checklists and obsenation/ question forms e Defines necessary resources to facilitate the resiew e Prmides orientation and trammg to team members on the approach, methodology and overall project expectations

. Reviews and approves system specific review mstructions, checklists, aM supplements.

  • Develops a summary report of each system specific review and a comprehensive report of the mspection results SVSR Team Members
  • Develop system specific resiew instructions and checklists

. Conduct the system reviews in accordance with this resiew plan and the system specific mstructions and checklists Develop system specific reports and make appropriate presentations on the status of the system specific reviews to Team Supervision, Deputy Project Director, Project Director.

O

E3 MILLSTONE UNIT 2 ICAVP PP-01 E PROJECT PROCEDURES TITLE: SYSTEM VERTICAL SUCE REVIEW REVISION: 4 DATE: 06/26/98 PAGE 9 OF 23 4.1 INSPECTION PREPARATION 4.1.1 _ Staff Trainine and Mobilization Resources Deputy Project Director SVSR Group Lead Aetion 4.1.1.1 Assess Project personnel needs based on selected system 4.1.1.2 SVSR Group Lead revises Team discipline composition as required to cover the selected system inspection

{ 4.1.1.3 Develop mobihzation and trammg schedule for Deputy Project Director approval 4.1.1.4 Complete SVSR mobihzation and trammg completed in accordance with approved schedule Action Output Trained Personnel 4.1.2 Identify System Specific Inspection Scope and Documents Resources System Leads System Team Members Action 4.1.2.1 Determme the selected System Inspection boundary including interfacing systems that are i necessary to support the functional requirements of the selected system. Use PI-01 "SVSR Implementation Checklists and Workbook" to determine system boundaries.

O l

l

<  !!) MILLSTONE UNIT 2 ICAVP PP-01 E >

PROJECT PROCEDURES TITLE: SYSTEM VERTICAL SUCE REVIEW REVISION: 4 DATE: 06/26/98 PAGE 10 OF 23 4.1.2.2 Identify a list of documents and other information asso::iated with the system. Typical information to consider.

  • Details of system boundariedmterfaces e Identified system deficiencies or operating problems

~ i e Regulatory documents ceaining requirements specific to selected system j e Modifications made to the selected system

. System Drawings e Calculations j e System related actions from the Corrective Action Program e Design changes iI 1

. Design Basis Documents l

. Licensing changes e Procedure changes

. Original designinfonnation

. System operational and test data

{

. Operatmg procedures

. Maintananna procedures

  • System regulatory requirements such as emironmental qualifications, fire protection, seismic quahfications NOTE:

The demant list initiated in Step 4.1.2.2 will be completed for all applicable parameters and functions the team can identify for the selected system. A list of typical document types is provided in Appendix A.

O

e E3 MILLSTONE UNIT 2 ICAVP PP-01 8

PROJECT PROCEDURES TIT 1.E: SYSTEM VERTICAL SUCE REVIEW REVISION: 4 DATE: 06/26/98 PAGE 11 OF 23 l 4.1.2.3 Using the list of hmmts developed in Step 4.1.2.2, develop a system speci6c design basis and configuration management assessment checklists. Use the generic checklist framework provided in PI-01 "SVSR Implementation Checklists and Workbook".

NOTE 3ampling plans may be used for selected repetitive component group evaluations. The sample plan and its rationale will be proposed and submitted to the NRC for their review and oversight.

4.1.2.4 Develop list of orgam rations (internal and external) associated with the items identified.

4.1.2.5 Develop schedule for inspection.

Action Outout

. System boundary and interface definition

. System specific checklist and workbook

. Document retrieval requirements

. Detaded Schedule for resource plannmg 4.2 Conduct OfInspection Detailed instructions to be used by the SVSR team for conduct of the inspection are provided in PI-01 "SVSR Implementation Checklists and Workbook" PI-01 is intended to supplement this ~j project procedure. The inspection will be conducted in multiple phases, combining in-office document review and verification and in-plant walkdowns. Walkdowns will be used to obtain additional information, clarify information, verify commitments, and answer working questions.

l A review of the system against licensing and design bases shall be performed during Tier 1.

The review will include (but not be limited to) mechanical, electrical, I&C, and l civil / structural requirements such as calculations, analysis, assumptions, and conclusions.

Appropriate design documents and data for the selected system and the system l

< B) MILLSTONE UNIT 2 ICAVP PP-01 E PROJECT PROCEDURES TITLE: SYSTEM VERTICAL SUCE REVIEW l REVISION: 4 DATE: 06/26/98 PAGE 12 OF 23 l

components will be reviewed to the extent necessary to verify 100% of the selected system l

l requirements.

l l

For repetitive or identical component groups the verification will include a screening process to confirm that the components are repetitive and identical followed by validation of the licensing or design basis requirement using a component group process.

4.2.1 Evaluate Documents Resources l

System le,ad System Team Members Action 4.2.1.1 Retrieve necessary documents 4.2.1.2 Review sycem hments and record the results of the evaluation. He review should datermine whether:

  • He system current configuration accurately reflects the licensing-bases, including the updated FSAR.

1 e The system calculations and analyses were performed using recogmrrd and acceptable analyticalmethods e The assumptions made in any calculations or analysis supporting the change are tachnir-ally i sound.

  • The results of calculatm or analysis supporting the unmodified portions of the original configuration and design changes are reasonable (based on engineermg judgment) for the scope l of the change. j i

e NNECo considered the effect of a change on design margms and the design changes received the appropriate level of engiammg and management review during the design phase and prior to implementation.

< ' F.3 MILLSTONE UNIT 2 ICAVP PP-01 E PROJECT PROCEDURES TITLE: SYSTEM VERTICAL SUCE REVIEW REVISION: 4 DATE: 06/26/98 PAGE 13 OF 23

  • NNECo considered the effect of a change on pre-operational, startup, or system baseline acceptance test results.
  • Design changes are accurately reflected in operatmg, maintenance, and test procedures.

NOTE Procedures will be reviewed in detail to verify that correct licensing and design bases information have been incorporated into the procedures and that modifications, corrective actions, and changes in system licensing bases have not invalidated preoperational and/or startup acceptance.

  • Proposed design changes, subsequently canceled, were not replaced by procedural changes that unposed excessive burdens on plant operators.

4.2.1.3 As hm nts are reviewed, prepare walkdown checklists demng items needmg additional information or clanfication.

Action Output A list ofinspection walkdown requirements A record of documents reviewed and their disposition NOTE:

Typical design input requirements to be used in evaluatmg system documents are listed in Appendix B.

Typical design review questions to be used in evaluatmg system documents are listed in Appendix C.

O V

~

'P)

E MILLSTONE UNIT 2 ICAVP PP-01 PROJECT PROCEDURES TITLE: SYSTEM VERTICAL SUCE REVIEW REVISION: 4 DATE: 06/26/98 PAGE 14 OF 23 l

4.2.2 Plant Walkdowns Resources System Lead .

System Team Members Action 4.2.2.1 Develop Walkdown Package. Typical contents will be:

  • System components and/or area to inspect during the walkdown e Specific modification package elements to inspect
  • System specific Corrective Actions identi6ed by the Millstone Unit 2 Configuration Management Program to inspect and evaluate e Measurements / observations to make e System procedures to walkthrough e Location of components or stmetures

. Marked up drawings showing walkdown requirements 4.2.2.2 Obtain clearance and/or access permits. Examples:

  • Radiation work permit
  • Specialoperational requirements O

E3 MILLSTONE UNIT 2 ICAVP PP-01 E PROJECT PROCEDURES TITLE: SYSTEM VERTICAL SUCE REVIEW REVISION: 4 DATE: 06/26/98 PAGE 15 OF 23 i

4.2.2.3 Conduct the walkdown, emphasizing:

NOTE The system vertical slice reviews will be focused on licensing and design bases requirements and will utilize appropriate level documentation (drawings, calculations, design documents, etc.) to the inspection detail necessary to verify and validate conformance to the requirements.

e Control ofoperational procedures, maintenance procedures, test and surveillance procedures, and control of the plant simulator configuration.

  • Con 6guration control consistency with the licensing bases at the level of detail contained in piping and instrumentation diagrams (P& ids) or system flow diagrams, piping isometric drawings, electrical single-line diagrams, and emergency, abnormal, and normal operating procedures.

. Verification ofcurrent, as-modified plant conditions agamn design basis and licensing basis documentation; e

Verification that design and licensing bases requirements have been and are being translated into operatmg procedures and maintenance and test procedures; e Verification of system performance through review of specific test records and/or obsenstion of selected testing of particular systems; and e

Review of proposed and implemented corrective actions for Millstone Unit 2 identified design deSciencies.

Action Outent Completed Walkdown Package O

l E3 E

MILLSTONE UNIT 2 ICAVP PP-01 l -

PROJECT PROCEDURES i TTTLE: SYSTEM VERTICAL SLICE REVIEW REVISION: 4 DATE: 06/26/98 PAGE 16 OF 23 4.2.3 Conduct Structured Data Gatherine Resources SVSR Team Members ,

1 SVSR System Leader I Action l 4.2.3.1 Prepare a list of specific information to be obtained based on a need for clarification, l information that the SVSR team can not find, or further investigation into answering a working question. This will help ensure that the information requirement is focused.

4.2.3.2 Identify the orgamration orjob function that may be able to supply the specific information. Arrange for a data gathering conference to obtam needed information.

NOTE All data gathering conferences will be conducted in accordance with the ,

l Communication Plan (PLN-02).

Actan_ Output l

  • Guidance and clarifications regarding NNECo positions or decisions l

. Additionalinformation 4.3 INSPECTION ASSESSMENT AND REPORT Ess9mssa Deputy Project Director SVSR Group Leader SVSR System Lead l SVSRTeam Members 1

0 l

< T.) MILLSTONE UNIT 2 ICAVP PP-01 M PROJECT PROCEDURES TITLE: SYSTEM VERTICAL SLICE REVIEW REVISION: 4 DATE: 06/26/98 PAGE 17 OF 23 l l

l

! Action l

l 4.3.1 Collect and assess the results of the inspection preparation and system inspections from each of theinspection teams 4.3.2 Prepare a draft report of the SVSR activities, results, and conclusions. The report is to )

consist of, as a nununum:

)

l

  • Input to an executive summary,
  • A summary description of the methods used, e A summary ofwhat was reviewed, e Results of the vertical slice reviews, and e The conclusions that can be drawn from the results of the resiews.

l The conclusions are to include a Mamunation of whether: l

  • The current con 6guration accurately reflects the licensing-bases, including the UFSAR, at

)

the level of detail enntained in piping and instrumentation diagrams (P& ids) electrical single-line diagrams, and plant operatmg procedures.

!

  • Calculations and analyses were performed using rwngnired and acceptable analytical l methods and that assumptions made in calculations or analysis supporting changes are technically sound.
  • The results of calculations or analysis supporting the unmodified portions of the original configuration and design changes are reasonable (based on engineeringjudgment) for the scope of the change.
  • NNECo considered the effect of a change on design margms and that the design changes received the appropriate level of engmeenng and management review during the design phase and prior to implementation.

O V e NNECo considered the effect of a change on pre-operational, startup, or system baseline acceptance test results.

1 I

l 1

~

E) MILLSTONE UNIT 2 ICAVP PP-01 E PROJECT PROCEDURES TTTLE: SYSTEM VERTICAL SUCE REVIEW REVISION: 4 DATE: 06/26/98 PAGE 18 OF 23 e Design changes are accurately reflected in operatmg, maintenance, and test procedures, as well as in tramme matenals.

Proposed design changes, subsequently canceled, were not replaced by procedural changes that imposed excessive burdens on plant operators.

4.3.3 Support internal ICAVP reviews of the draft report as necessary.

4.3.4 Resolve comments and finahre the repon for issue.

Action Output Final Report Project backup documentation 4.4 TEAM MEETINGS / REVIEWS During the SVSR, meetmgs and status reviews will be held periodically. The following guidelines shall govern the regularly scheduled meetings.

  • Meetmgs of the system teams shall be held daily.

The daily meetmgs shall be chaired by the System lead and shall cover inspection status, progress, working questions under resiew, and discrepancies to date.

. Combined Team meetmgs shall be held at least weekly.

The weekly meetmgs shall be chatred by the SVSR Group Lead or the Deputy Project Director and shall cover the overall progress of the inspection including working questions under review and discrepancies to date in all areas.

4.5 SYSTEM ASSESSMENT System Assessment As Working Questions are identified by the SVSR Team Members, they are to be documented for O

9

'P) MILLSTONE UNIT 2 ICAVP PP-01 E >

PROJECT PROCEDURES TITLE: SYSTEM VERTICAL SUCE REVIEW REVISION: 4 DATE: 06/26/98 PAGE 19 OF 23 Follow up by SVSR Team Members will deternune that either 1) upon obtammg further l information, no question exists, or 2) it is an identified discrepancy with a documented basis.

Discrepancies are evaluated per Project Procedure PP-07. Each discrepancy forwarded for PP-07 review will be provided with a complete description, including all pertinent background information.

5.0 REFERENCES

NRC Inspection Procedure 93801, Safety System Functional Inspection (SSFI)

NRC Inspection Manual Chapter 0350, " Staff Guidelines for Restart Approval" NRC Inspection Manual Chapter 2535, " Design Verification Programs" Mdistone Unit 3 Restart Assessment Plan NRC Confirmatory Order to Northeast Utilities Energy Company dated August 14,1997 NRC ICAVP Oversight Guideline Document NRC ICAVP OversightInspection Plan O

< !D MILLSTONE UNIT 2 ICAVP PP-01 8 J PROJECT PROCEDURES n

l C) TITLE: SYSTEM VERTICAL SUCE REVIEW REVISION: 4 DATE: 06/26/98 PAGE 20 OF 23 l l

l APPENDIX A TYPICAL DOCUMENT REVIEW / SAMPLE TOPICS FOR INSPECTION

1. System Design Review - Fluid and Material Handhng Systems -
2. Fluid System Diagram; System Description; for complex systems, I.ogic and loop Diagrams l
3. System Design Review - Stmetural
4. Bracing Arrangement and Stability Analysis l l

S. System Design Review - Electrical System l

6. One-line Diagram and System Description
7. System Design Review - Information Processing / Control Philosophy
8. Description of Control Philosophy
9. System Design Review - Facilities Design Systems
10. HVAC, Fire Protection, and Architectural
11. Layout Design Review
12. Layout Drawing, Layout Description, Code Reviews, and Life Safety Analysis
13. Site Arrangement Resiew
14. Ultimate Site Development Plan
15. Cooling Water Source
16. Emironmental Constramts
17. Common or Shared Facilities
18. Railroad Access
19. Foundation Type Resiew
20. Geotechnical Limitations
21. Soil Bearing Capacity
22. Water Table Considerations
23. Altemative Methods
24. Transmission and Distribution Design Resiew
25. Modification Packages t

~

E3 MILLSTONE UNIT 2 ICAVP PP-01 E .

PROJECT PROCEDURES TIT 1.E: SYSTEM VERTICAL SLICE REVIEW REVISION: 4 DATE: 06/26/98 PAGE 21 OF 23 l APPENDIX B TYPICAL DESIGN INPUT REQUIREMENTS

1. Scope / Basic functions of structure, system or component
2. Performance requirements, input services (air, electricity) as well as outputs (capacity, rating)
3. Codes Standards, and regulatory requirements including applicable issue and/or adAmda
4. Design Conditions such as temperature, pressure, fluid, chemistry and voltage
5. Loads such as seismic, wind, thermal and dynamic
6. Environmental conditions anticipated, such as pressure, temperature, humidity, corrosiveness, site elevation, wind direction, nuclear radiation, electromagnetic radiation, and duration of exposure including 10CFR50.49 application
7. Interface requirements and constructability including defmition of the functional and physical interfaces including structures, systems, and components
8. Material requirements such items as compatibility, electrical insulation properties, protective coatmg, and corrosion resistance
9. Mechanical requirements such as sibration, stress, shock and reaction forces
10. Structural reqmrements covering such items as equipment foundations and pipe supports
11. Hydraulic requirements such as NPSH, allowable pressure drops, and fluid velocities
12. Nmi=try requirements such as provisions for sampling and limitations on water chenustry
13. Electrical requirements such as source of power, voltage, raceway requirements, electrical insulation, motor requirements, load / voltage studies and EDG loading
14. Layout and arrangement requirements
15. Operational requirements under various conditions such as plant start-up, normal plant operation, plant shutdown, plant emergency operation, special or infrequent operation, and system abnormal or emergency operation
16. Instrumentation and control requirements including indicating instruments, controls and alarms required for operation, testmg and maintenance
17. Access and admmistrative control requirements required for plant security O 18. Redundancy, diversity, and separation requirements
19. Failure effects requirements including of those events which taey must withstand

.. 1 E) MILLSTONE UNIT 2 ICAVP PP-01 m

PROJECT PROCEDURES l

l V 0 TITLE: SYSTEM VERTICAL SUCE REVIEW l REVISION: 4 DATE: 06/26/98 PAGE 22 OF 23 l l

20. Test requirements including pre-operational and subsequent periodic in-plant and the condition l

l 1

under which they must operate

21. Accessibility, maintmanm, repair and in-senice inspection requirements
22. Personnel requirements and limitations
23. Transportability requirements such as size and shipping weight
24. Fire protection or fire resistance requirements I
25. Handling, storage, clnnmg and shipping requirements
26. Other requirements to prevent undue risk to the health and safety of public
27. Materials, processes, parts, and equipment suitable for application
28. Safety requirements for preventmg perscuuel injury
29. Quality and quality assurance requirwsts
30. Reliability requirements including their interactions, which may impair safety I

p 31. Interface requirements between plant equipment and operation and maintenance personnel

32. Requirements for criticality control and accountability of special nuclear materials
33. Special ALARA considerations
34. Special human factors considerations
35. High Energy Line Breaks are affected
36. Floodmg
37. Missiles 38.10CFR50 Appendix R, including Safe Shutdown Analysis
39. Seismic Category II over I
40. SpecialHVAC requirements
41. Station Blackout Analysis
42. Post Accident Monitoring Requirements
43. OTHER requirements, as necessary I

O V

E) MILLSTONE UNIT 2 ICAVP PP-01 E PROJECT PROCEDURES l

TTTLE: SYSTEM VERTICAL SUCE REVIEW 1

l , REVISION: 4 DATE: 06/26/98 PAGE 23 OF 23 i

APPENDIX C TYPICAL DESIGN REVIEW OUESTIONS l

1

1. Were the inputs correctly selected and incorporated into design?

l

2. Are assumptions necessary to perform the design activity adequately described and reasonable?

Where necessary, are the assumptions identified for subsequent reverification when the detailed design activities are completed? l l

3. Are the appropriate quality and quality assurance requirements specified?
4. Are the appropriate codes, standards, and regulatory requirements specified?
5. Have applicable operatmg and constmetion experiences been considered?
6. Have the design interface requirements been satis 6ed?

l 7. Was an appropriate design meaod used?

8. Is the output reasonable compared to the inputs?
9. Are the specified parts, equipment, and processes suitable for the required application?
10. Are the specified matenals compatible with each other and the design environmental conditions to which the material will be exposed?
11. Have adequate maintenance features and requirements been specified?
12. Are accessibility and other provisions adequate for performance of needed maintenance and repatr?
13. Had adequate accessibility been provided to perform the in-senice inspection expected to be required during the plantlife?
14. Has the design properly considered radiation exposure?
15. Are the acceptance criteria incorporated in the design documents sufficient to allow verification that design requirements have been satisfactorily accomplished?
16. Have adequate pre-operational and subsequent periodical test requirements been appropriately l specified? l
17. Are adequate handimg, storage, cleanmg, and shipping requirements specified? Are adequate identification requirements specified?

l

' 18. Are requirements for record preparation, review, approval, retention, etc., adequately specified?

l

.