ML20113A080
| ML20113A080 | |
| Person / Time | |
|---|---|
| Site: | Millstone  |
| Issue date: | 05/24/1996 |
| From: | Paulantonio T NORTHEAST UTILITIES |
| To: | |
| Shared Package | |
| ML20113A046 | List: |
| References | |
| NUC-PI-5, NUDOCS 9606240047 | |
| Download: ML20113A080 (33) | |
Text
.'
D NORTIIEAST UTILITIES NUCLEAR'. -
PROJECT INSTRUCTION . l v
$ l jr m - e -
p g ?;, " :, # j i,, .
j;' i ~
q~7 q, ,
'~/ ' c ': :+ y y' w-OP'
,s
(
HINK'. -
~
'~%
.s
'DT' s ' , EVIE\su
, j Ull%Q , yi7,; %., .- l::^'N,s..
e ,
e[f%h,1 .
w *.,., ,N# .[?
~ V. 4 . > . .. . . .
Millstone Usiit? System Rsadiness Review ,
c w- .
q ;
~
NUC PI 5 jf Rev.1 This Project Instruction (PI) is part ofimplementation of the Configuration Management P1 n(CMP)
' /
Approval: /
/ linit D' c PORC Mtg. No: 3-M/ OJ' Date: 532P%
Effective Date: Ib1 l4L 9606240047 96M20 ADOCK 05000423 PDR l P PDR Responsible Individual:
Level of Use T. Paulantonio Information Subject Matter Expert:
9606)(/0/) t/ 7 T. Paulantonio
)
.- )
t I
. 1 MP3 l 1
Project Instruction Millstone Unit 3 System Readiness Review 1
TABLE OF CONTENTS 1
IN STRU CTI O N S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.
1.1 Tra in i ng . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.2 System Readiness Review Process . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
- ~
1.3 Preparation and Processing of Unresolved Item Reports *. . . m . : 16- -
1.4 Preparation of Preliminary System Readiness Report . . . . . . . . . . . 18 1.5 System Readiness Review Team Status Reports .............. 19 1.6 Preparation of Final System Readiness Report . . . . . . . . . . . . . . . 20 j 1.7 Preparation of System Readiness Memo . . . . . . . . . . . . . . . . . . . . . 21 22
- 2. REFEREN CES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
- 3. CO MMITMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
- 4.
SUMMARY
OF CHANGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 ATTACHMENTS AND FORMS Attachment 1, " System Readiness Checklist" . . . . . . . . . . . . . . . . . . . . . . . 23 Attachment 2, " Unresolved Item Report" ......................... 24 Attachment 3," Preliminary System Readiness Report Format" ....... 26 Attachment 4, " System Readiness Report Format" . . . . . . . . . . . . . . . . . . 27 Attachment 5," System Readiness Memo Format" . . . . . . . . . . . . . . . . . . 28 Attachment 6, "D efinitions" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 i i
l l
NUC PI 5 Level of Use . . ~ m. .. .,
-c - > REVIEW Rev.1
- 'STOP" TH!NK 4ACT" ,
lnformation
,,, < 1 of 29
_. _ __._. _ _ __ _ _ . _ = . . _ _ . _ . _ _ _ _ .. . .
1 1
- 1. INSTRUCTIONS This PI defines the process for assessing and documenting the readiness of a system or subsystem to support plant operation or mode change as part of the unit's restart effort. This PI applies to systems designated in the CMP.
Goals of the System Readiness process for a system or subsystem are:
i
- All unresolved items are dispositioned by the Plant Verification and Readiness Team (PVRT).
- System or subsystem will not experience any events during plant startup.
- System or subsystem will have an 0% unplanned unavailability for the first l 120 days of an operating cycle.
This PI also provides guidance on documenting and processing discrepancies identified during the walkdown or the system readiness process. This reporting process shall also be used to document discrepancies identified by review processes required by t.he CMP.
The following attitudes and actions apply throughout performance of this PI:
- SOLICIT support from all site departments.
- RESPECT and RESPOND to allinputs to the process.
- PROVIDE feedback on the applicability of inputs provided.
Additionally, personnel involved with implementing this PI are to perform self-assessments of effectiveness of this PI as designated by the UPM, and provide feedback on needed improvements to the System Readiness Administrative (SRA) group.
All walkdowns shall be attended by one of the following:
- UPM or alternate as designated
- SRT Coordinator
- Supervisor, Technical Support Engineering
. i . , . _.. S NUC PI 5 Level of Use .- . . -
Rev.1 STOP -THINK' REVIEW lnformation .(ACT 2 of 29
~
7 ;
- _~ - -. - .. - ..- - _--.-- . ._ -__
Roles and responsibilities for this PI include:
- Unit Project Manager (UPM)
. Approves all UIRs generated
. Approves System Readiness Reports. Submits the System Readiness Memo to the Management Quality Corrmittee (MQC) for approval.
- SRT Coordinator - Participates in system walkdowns and reviews System Readiness Reports and UIRs generated. l
- Supervisor, Technical Support Engineering - Substitutes as needed for the Coordinator, SRT for systems under his or her cognizance.
i
- System Readiness Team (SRT) - Performs the review process of documents and plant equipment. Each SRT includes the following members as determined by SRT Leader:
- SRT Leader (System Engineer)
- Design Engineer
- Operations (as required) ;
1
- I&C (as required)
- Electrical Maintenance (as required)
- Mechanical Maintenance (as required)
- Chemistry (as required)
. Health Physics (as required)
NUC PI 5 STOP"
' THiAK ' 2 CU REV F3/ Rev.1 g
g , aof29
!
- SRT Leader _(System Engineer) - Performs the following: l
- Reviews each discrepancy generated on the Unresolved Item Report (UIR) for his or her system.
l
. Performs system walkdown on each assigned system and performs l l System Readiness Review Process outlined below.
l
- Prepares and presents Preliminary System Readiness Report to l the PVRT.
- Documents assessment results on 'Final' System Readiness Report l
~'
for presentation to UPM.' ^
- Plant Verification and Readiness Team (PVRT) - Performs the following:
- Verifies the validity of the Unresolved Item Report (UIR),
1
- Assigns the UIR to the proper category (FSAR, procedure, etc.) !
- Assigns the proper completion milestone (Startup, next RFO, etc.) ;
i
- Assigns the priority (non-startup items) l
- Develops recommended resolution to the UIR.
The PVRT forwards the UIR package to the UPM for final disposition I and approval. Once approved, the UIR is returned to the SRA.
PVRT members are identified in NUC PI 8," Plant Verification and Readiness Team."
- System Readiness Administrative (SRA) Group - Maintains the status of UIRs. Processes the necessary reports and forms associated with the readiness effort. Provides documents needed to perform system readiness
- reviews. Ensures each final disposition document for each UIR is identified on the UIR.
- Management Quality Committee (MQC)
- Approves specific design changes that will be walked down as a l result of SRT review.
- Approves each System Readiness Memo.
. Reviews UIR summary.
- NUC PI S Level of Use .. - , _ - . . -
Rev.1 TTOP~ TH!NK ' cAC 'REMEW f Information 4 of 29
1.1 Training NOTE The SRT Leader and SRT Design Engineer have completed initial engineering qualification. Based on their current job descriptions and assi,gned duties and responsibilities, they are generally qualified to perform design basis document reviews. Specific traimng in this PI ensures their ability to meet the stated objectives. Other assigned SRT members require only those skill sets related to their specific job descriptions.
" OBTAIN training required to enable the SRT members to- -
SRT Leader 1.1.1 and Design achieve the following objectives as applicable to their specific job Engineer descriptions:
- Apply the system readiness review process to identify readiness discrepancies.
. Understand all terms used in the system readiness review process.
. Identify necessary input, format, and routing of system readiness review.
. Understand what documents constitute the plant design.
. Determine that FSAR change requests are in place and spelled out in PDCR.
- Determine that design changes are incorporated into plant design.
. Determine when a system, subsystem, train, component, or device is OPERABLE.
. Evaluate materiel conditions as specified in NUC PI 4, "Walkdowns."
. Determine that PDCR field implementation is complete as specified in NUC PI 4," Millstone Unit 3 Walkdowns."
NUC PI 5 Level of Use 1. .
. STOP' ..."THINK #ACT _..' REVIEW Rev.1 Information 3of29 )
~
b
1.2 System Readiness Resiew Process The System Readiness Review Process centers on performing a comprehensive review of the attributes listed on Attachment 1," System Readiness Checklist," from the perspective of materiel condition and the following design change issues:
- Design changes for the system have been incorporated in appropriate Licensing documents. l
. Walkdowns of plant design (performed as specified in NUC PI 4, "Walkdowns") demonstrate proper field installation.
,. . _ __ ._ ~
- PDCR testing (performed by IST, surveillance, special, or preoperational test) ensures system readiness and functionality of the design changes affecting Licensing documents. l Any discrepancy found during any phase of the process shall be documented on Attachment 2," Unresolved Item Report (UIR)."
Preparing and processing UIRs are described in Section 1.3 of this PI.
As the initial review of each category is completed, the "R" (Review) box l on Attachment 1 is marked off. As each category assignment is completed, the SRf Leader marks off the "C" (Completed) box, signifying l the following:
- Review of the category is complete.
- All unresolved items that may affect the ability of the system to achieve its intended mission have been dispositioned (completed, closed out, evaluated for impact on declaration of operability of availability, deemed administrative in nature, or deemed to have no impact on startup of the unit, as applicable).
When each review team completes the document review phase and a preliminary system walkdown, a Preliminary System Readiness Report (Attachment 3) is generated and submitted to the PVRT. The PVRT identifies the completion milestone associated with each open item and approves the report. This preliminary report is then submitted to the UPM for approval.
When all open items required for startup are completed, the Final System Readiness Report (Attachment 4) is generated, approved by the PVRT and UPM, and presented to the MQC, NUC PI 5 Level of Use - _ < . - . _ [ _ i. Rev.1 VOP ~ 'TH!N.K ' (ACT" " REVIEW Information p s 6 of 29 3 - .
i NOTE
- 1. Actions are the responsibility of the SRT Leader unless otherwise noted.
- 2. Bulleted items correlate to headings presented in Attachment 1. Some efforts (such as reviews) may be performed concurrently. ,
The scope of the final walkdown may be expanded at the discretion of the l
- 3. '
SRT Leader to address special issues such as verification of separation criteria, HELB or EQ requirements, etc.
1
- AWO Review . ... ..
- a. PERFORM comprehensive review of closed AWOs (except PM- and SV-type AWOs) to identify where design l changes may have occurred and PERFORM the following for l those AWOs which could affect Licensing documents: l
- 1) IDENTIFY whether the associated design change is !
reflected in the Licensing documents. The design change may be defined in the following documents as appropriate: PDCR, DCN, PDDS, RIE, PMR, DDR, E&DCR, Unsat items, DMR, PDCE, DCR, design calculation, setpoint change, MEPL, etc. l
- 2) REVIEW post-modification test plan as specified in this PI under " System Testing."
- b. ASSESS all open backlog AWOs with scheduled start dates prior to the plant startup date plus 120 days, and PERFORM l the following for those AWOs:
I
- 1) REVIEW database listing of the backlog AWOs.
- 2) DISPOSITION each AWO with the appropriate actions to be taken (reschedule, cancel, etc.) and reason for l actions.
- 3) INCLUDE the backlog review and action taken on the System Readiness Report.
- c. IDENTIFY to WP&OM any open AWOs that may affect system readiness which should be scheduled for completion now. l
- d. For AWOs that are not needed prior to startup, LIST and briefly STATE the AWO problem description, including an evaluation of why there is no impact on system readiness.
- c. MARK block on Attachment 1 to signify review completion.
^
NUC PI 5 Level of Use Rev.1 STof "TH!$K '~ ^ [ACf MEVef lnformation ,
7 of 29
4
- f. UPDATE PMMS as required to reflect recommended actions l
[WP&OM f in open AWOs.
- g. CLOSE AWOs upon completion.
l l . Design Changes
- a. PERFORM comprehensive review of design change j i documents implemented against the system, as a result of AWO review process.
- b. IDENTIFY those design changes that may affect the FSAR and PRESENT the list to MQC for walkdown approval. ,
- c. REVIEW the list of design changes affecting the FSAR and lMac f APPROVE the list for SRT review and walkdown.
- d. PERFORM the following with approved design change list:
l SRT f
- 1) REVIEW identified documents to ensure the design l
change is incorporated.
- 2) REVIEW the test plan and VERIFY the plan validates the functionality of the design change at the component, l
system, and intrasystem level as applicable.
- 3) Refer To NUC PI 4," Millstone Unit 3 Walkdowns," and PERFORM a complete walkdown of each design change. l
- c. IDENTIFY plant design discrepancies.
- f. MARK block on Attachment 1 to signify review completion. !
- NCR Review
- a. PERFORM comprehensive review of NCRs with dispositions of "use-as-is," " repair," or " admin," and IDENTIFY those NCRs that may have changed plant design documents or procedures as applicable.
- b. REVIEW each affected design document or procedure to ensure NCR is reflected.
- 1) 1E any dispositioned NCR is not reflected in affected l design document or procedure, IDENTIFY as a ,
l discrepancy using Attachment 2," Unresolved Item Report."
I NUC PI 5 Level of Use I .
- p. 7g ggy gey,1 Information ~ ^-
j m
8 of 29 1
l 4
- c. VERIFY there are no undispositioned NCRs for the system open greater than 60 days.
- d. VERIFY there are no open NCRs that affect system readiness.
- e. MARK block on Attachment 1 to signify review completion.
- Trouble Reports
- a. REVIEW open TRs to determine impact on system readiness.
- discrepancy using Attachinent 2, " Unresolved Ite'm ' ~ ~
Report."
- b. MARK block on Attachment 1 to signify review completion.
- Maintenance Rule Implementation
- a. EVALUATE system for compliance with Maintenance Rule.
- b. REVIEW action plans for Al systems for startup completion l requirements. l
-. c. IDENTIFY issues that could cause the system to not be AVAILABLE for the entire fuel cycle and VERIFY corrective actions are takeifoy responsible department.
- d. MARK block on Attachment i to signify review completion.
- EWR Review
- a. PERFORM comprehensive review of open EWRs and EVALUATE the effect of not implementing the requst prior to startup.
- b. ASSESS the current applicability of each EWR.
- d. IE EWR is not needed prior to startup, ROUTE to Resource l Allocation Committee (RAC) for processing. '
- e. MAT K blod un Attachment 1 to signify review completion.
NUC PI 5 Level of Use . - - x.- ..- . ..- , _ . . _
STV' THiNK *- :ACT ' REVIEW Rev.1 lnformation 9 of 29 3 y , 3
, n- ~ - - - - - - , ,
Jumper Bypass Review
- a. EVALUATE the impact of each installed jumper bypass on system readiness.
- b. VERIFY any jumper bypass that may impact system readiness is removed.
- c. LIST all remaining jumper bypasses, PROVIDE evaluation of why there is no aggregate impact on system readiness on the system readiness report.
d.. MARK block on-Attachment 1-to signify review completion ~
- Operability Determinations or JCOs
- a. REVIEW all outstanding Operability Determinations against the system.
- b. VERIFY one of the following:
- Allidentified actions requiring work or correc:ive action are complete and full qualification is restored.
In-place compensatory actions are still appropriate and operator burden has been reviewed.
- c. RECOMMEND closure of unnecessary ODs.
- d. MARK block on Attachment 1 to signify review completion.
- Control Room Paael Deficiencies
- a. EVALUATE remaining open deficiencies to ensure they will not impact readiness goals.
- b. MARK block on Attachment 1 to signify review completion.
- Operator Burdens:
- a. REVIEW Operator Burdens for impact on system readiness.
- b. MARK block on Attachment 1 to signify review completion.
i 1
l WCm Level of Use we w wm
. _. -. . - . . . ~ .
Rev.1
. . .S7or Information 10 of 29
. - -. ._. - __ - . . - _ _ - . . . - - = - ----- . ._. ._ _-. _
- Pre-outage Work List
- a. REVIEW Engineering " Pre-outage Work List."
- b. VERIFY all work or commitments are resolved.
- c. MARK block on Attachment 1 to signify review completion.
- Work Not Performed (Rejected OSCRs)
- a. PERFORM comprehensive assessment of system work or design items not performed during the outage, including work or PMs
~'
deferred to a later time.
- b. DETERMINE impact of not performing the work or item on system performance and system OPERABILITY.
- c. IE any work or item should be completed now, PREPARE an OSCR and PROVIDE recommendation for completion outlining the potential risk involved with delaying the work.
- d. MARK block on Attachment 1 to signify review completion.
A/R Review
- a. REVIEW the Open A/R List for items that:
- Are required to be completed prior to startup.
- Were generated to close a ACR that is required to be completed prior to startup.
- b. PERFORM comprehensive assessment of A/Rs that may affec1 system readiness.
- c. For A/Rs that are not needed prior to startup, LIST and PROVIDE evaluation of why there is no aggregate impact on system readiness on the system.
- d. MARK block on Attachment 1 to signify review completion.
NUC PI 5 Level of Use S , ..M. ,
Rev.I STOP" "THINK " JACT5 REVIEW Information y< 11 of 29
- ACR Review
- a. PERFORM comprehensive assessment of the effect of each open ACR on system readiness.
- b. IDENTIFY any items required to be resolved prior to startup.
- c. EVALUATE ACRs that have been dispositioned but whose disposition is not implemented for impact on system readiness.
- d. MARK block on Attachment I to signify review completion. l
~ ~
- ~ Punchlist Evaluation ~
- a. REVIEW the following punchlists as applicable:
- Fut.1 Load NRC Inspection Items Startup
- Abnormal Plant Conditions
- b. DETERMINE the effect of punchlist items on system readiness,
- c. VERIFY items that affect system readiness are dispositioned,
- d. MARK block on Attachment 1 to signify review completion.
NOTE The preliminary system walkdown will satisfy the regi ' ements of final walkdown unless additional system work is performed.
SRT Leader
- Preliminary System Walkdown and Design Engineer a. Refer To NUC PI 4,"Walkdowns," and PERFORM a
" Preliminary" system walkdown for materiel condition /
housekeeping,
- b. DOCUMENT each discrepancy on Attachment 2,
" Unresolved Item Report."
- c. MARK block on Attachment 1 to signify review completion.
i S. ! NUC PI 5 Level of Use STOP^ ' TH!N K' .ACT' Rev.1 lnformation 'R,EVIEW
, / 12 of 29
I
- Surveillances l
- a. VERIFY the responsible department has completed all required surveillances,
- b. For Tech Spec systems, CHECK that the remaining interval between surveillance performance will not be impacted by the duration of the upcoming cycle, to ensure systems will be I OPERABLE instead of AVAILABLE during the cycle, j
- IE any surveillance is required prior to startup to ensure l' system OPERABILITY during the cycle, LIST by surveillance number.
~* lE any open surveillance will not impact system -
OPERABILITY during the cycle, LIST by surveillance number and PROVIDE justification of why system '
readiness is not impacted.
- c. MARK block on Attechment 1 to signify review completion.
NOTE For routine maintenance and minor modification activities, the ISI, IST, and surveillance test p,rograms suffice. However,if there is a concern regarding system readmess due to an extended shutdown duration or as deemed necessary by the SRT Leader, a system preoperational test may be required to validate system functionality and demonstrate system ability to meet readiness goals.
- System Testing
- a. EVALUATE PDCR test plans from MQC approval list for l adequacy,
- b. PREPARE UIR as necessary to document any discrepancies. l
- c. DETERMINE the extent of system testing to be performed, depending on the scope of work, design changes performed on the system, and duration of the outage,
- d. DETERMINE and DOCUMENT whether test is to be performed during unit startup.
- e. VERIFY required system testing is performed and results are satisfactory,
- f. MARK block on Attachment 1 to signify review completion.
- !* NUC PI 5 Level of Use 11. -
. _ _c ,Acy mm
_'mW sToP. Rev.1 Information -
7 ; y3 13 of 29 3 ,
f 1 l
- LER Review
- a. PERFORM comprehensive assessment of LER commitments ;
or open items for impact on system readiness. l
- b. MARK block on Attachment 1 to signify review completion. i 1
l
- Long-standing System Issues l l a. IDENTIFY all outstanding issues on the " Top 10" listing or Operator Burdens that impact system readiness.
~ '
- b. ASSESS impact on system readiness. l
- c. MARK block on Attachment 1 to signify review completion.
l
- Other System Issues I a. ADDRESS review of special issues specific to this system as determined by SRT Leader.
- b. MARK block on Attachment 1 to signify review completion.
l
- Final System Walkdown
- a. IE any of the following apply, a " Final" system walkdown is performed by the SRT:
- Work was performed on the system as a result of an identified discrepancy.
- Work was outage related.
- Specific walkdowns are requested (from NUC PI 15,
" Selected Millstone Unit 3 System Reviews," vertical slice review, etc.).
- b. Refer To NUC PI 4,"Walkdowns," and PERFORM a " Final" system walkdown.
- c. DOCUMENT discrepancies noted on Attachment 2,
" Unresolved Item Report." -
{ d. ASSESS impact of each item on system readiness.
l l
NUC PI 5 Level of Use . . . n .-
. SToP' . . ." THlNIC *ACT' " REVIEW. . . . Rev.1 lnformation 14 of 29
- e. IE any item requires action prior to startup, INITIATE an OSCR.
- f. SUMMARIZE any open items or items noted during either the " Preliminary" or " Final" system walkdown.
- g. MARK block on Attachment 1 to signify review completion.
n l
i l
4
- f NUC PI 5 Level of Use S oP %)W sAcf'y@@T Rev.1 Information _ ; v' , g p5 < 15 of 29
l l
1.3 Preparation and Processing of Unresolved Item Reports l originator 1.3.1 COMPLETE Block #1 except for Log #.
f 1.3.2 PROVIDE discussion of item in Block 2.
1.3.3 IE known, PROVIDE recommended disposition in Block 3.
f 1.3.4 REVIEW UIR.
l SRT Leader 1.3.5 IE known, PROVIDE recommended disposition in Block 3.
I
' 1.3.6 PRESENT UIR to PVRT.
)
1.3.7 IDENTIFY UIR disposition category from the following: l l PVRT l l
- Materiel Condition - walkdown-related l
- Configuration - Design Basis, DCM, Licensing
- Admin - Programs and Procedures
- Training - Industry and internal issues
- VOID - Item is not a discrepancy 1.3.8 Refer To WC 1," Work Control" (Att) and ASSIGN priority.
1.3.9 IDENTIFY completion milestone from the following:
- Startup (for all Priority 1 and Priority 2 items and other items as desired)
- Other (as appropriate with milestone schedule) 1.3.10 DETERMINE and RECORD final disposition of UIR. l l
l l
NUC PI 5 Level of Use Rev.1 SIoP
- THIN K' (ACTS 55V(EVT Information - 6 - ' , 16 of 29
I 1.3.11 PERFORM applicable action:
. IE action is required, IDENTIFY final disposition document l required to close UIR from the following:
- ACR
- TR
- NCR A/R (other)
- IE no action is required, MARK N/A. l 1.3.12 FORWARD UIR to UPM for approval.
1.3.13 REVIEW UIR and dispositions, and APPROVE.
lUPM l 1.3.14 FORWARD to SRA for processing.
1.3.15 GENERATE required final disposition document.
lSRA l 1.3.16 SEND copy of UIR to Originator or Supervisor.
1.3.17 FILE signed original UIR in System Readiness file.
(
NUC PI 5 Level of Use _ . . . .. . . . . . . _ . . _ . . . .
- SToP' THINK' = ACT ' REVIEW Rev.1 Information -
4 17 of 29
, y
, 1.4 Preparation of Preliminary System Readiness Report j NOTE Preliminary System Readiness Report format is shown in Attachment .
This report is prepared after all"R" boxes of Attachment I are marked completed, 1.4.1 PREPARE Preliminary System Readiness Report package, which j SRA l" includes the following: i
- ~ ~
l
- UIR Summary Report
- UIRs
- Walkdown Checklists ,
= Summary Report of Review Items i 1.4.2 PRESENT Preliminary System Readiness Report (Attachment l SRT Leader }"
and package) to PVRT.
t l" 1.4.3 REVIEW Preliminary System Readiness Report and PERFORM l l PVRT the following:
- a. DISPOSITION any open UIRs in package. l
- b. IDENTIFY applicable category,
- c. IDENTIFY completion milestones.
- d. INDICATE the disposition document required.
- e. APPROVE Preliminary System Readiness Report (Attachment and package) and PRESENT to UPM for approval.
lUPM }" 1.4.4 APPROVE Preliminary System Readiness Report package and FORWARD approved package to SRA.
lSRA l 1.4.5 UPDATE UIR database to reflect approval of UIRs in l Preliminary System Readiness Report package.
1.4.6 FILE Preliminary System Readiness Report package in System Readiness file.
NUC PI 5 Level of Use . .. [ . . . . , ,. .
Rev.1 STOP ' W!N K" ACT ' EVIEW lnformation 18 of 29
1.5 System Readiness Review Team Status Reports 1.5.1 REQUEST status reports of open items.
lUPM l" 1.5.2 Routinely PREPARE status reports (unless otherwise noted) for lSRA l" the following:
- Open items
- Startup open items (by system)
- Other reports as requested by UPM ..
1 NUC PI 5 ,
Level of Use . f ,
'.TH!NK
. R.. .' I _. _,*_$ .- ..
'STOP'
- ACT'I REVIEW' Rev.1 {
lnformation <
^
., f' 19 of 29
1.6 Preparation of Final System Readiness Report NOTE Final System Readiness Report format is shown in Attachment 4. This report is generated based on Attachment 1 information.
l* 1.6.1 VERIFY all"C" boxes on Attachment 1 are marked and allitems l llSRT Leader required for startup are resolved.
1.6.2 PROVIDE brief"Overall Summary" of the following-
- System OPERABILITY or AVAILABILITY status
- Major factors affecting system readiness
- Aggregate assessment of all open items 1.6.3 PROVIDE summary of review results for each issue.
1.6.4 PROVIDE detailed assessment of the aggregate of all open items.
1.6.5 PRINT the System Readiness Report and SIGN.
1.6.6 PRESENT Final System Readiness Report to SRT Coordinator for approval.
1.6.7 REVIEW and APPROVE Final System Readiness Report. ,
SRT Coordinator l 1.6.8 PRESENT Final System Readiness Report to UPM for review and approval.
l l
l NUC PI 5 Level of Use : .. _
STOP THINK' j ACT'- ..~ REVlFW Rev.1 l
lnformation 20 of 29 i
I
-. .. .. - . - - ~ _ - - - -- _, . . _ _-
- 1.7 Preparation of System Readiness Memo I
NOTE l System Readiness Memo format is shown in Attachment 5. This memo is a generated based on Attachment 1 information.
1 1.7.1 WHEN the System Readiness Report is approved, PREPARE a l ,
HSRT Leader l l
" System Readiness Memo" as follows:
tl
- 1
- IDENTIFY the system being turned over. l i - IDENTIFY system OPERABILITY or AVAILABILITY status.
- PROVIDE summary of findings and evaluation results.
- PROVIDE assessment of the aggregate of all open items.
1 l
- IDENTIFY any open items that will be tracked on the startup i
punchlist to support startup, including an analysis of the significance of each item and why it is considered a hold.
UPM &
1.7.2 PRINT the memo and SIGN.
4 SRT Leader 1.7.3 SUBMIT System Readiness Memo to MQC for review and i lUPM f approval.
l 1.7.4 DISTRIBUTE the memo.
l SRA l 1.7.5 TRANSMIT the following to Nuclear Records: l
- Original System Readiness Memo
- Final System Readiness Report
- Contents of System Readiness file, including:
- 1) Approved UIR originals j l
- 2) NUC PI 4 Walkdown Checklists (applicable Atts)
REVIEW Rev.1
...SToP . THINK ' i ACT 7-Information 21 of 29
9
- 2. REFERENCES 2.1 Configuration Management Plan (CMP) 2.2 WC 1," Work Control" 2.3 NUC PI 4, "Walkdowns" 2.4 NUC PI 8," Plant Verification and Readiness Team" 2.5 NUC PI 15," Selected Millstone Unit 3 System Reviews,"
~ -
- 3. -COMMITMENTS -
None 4
SUMMARY
OF CHANGES l
4.1 Amplified instructions for performing System Readiness Reviews. Added Operator Burdens to Attachment 3 and added associated instructions, j 4.2 Deleted references to integrated database, t
i 4 NUC PI 5 Level of Use m. _
.,,_2.~_
-STOP ,
THINK' **ACT' ' REVIEW Rev.1
[nformation ;gg) 22 of 29
Attachment 1 System Readiness Checklist (Sheet I of 1)
SYSTEM NO.
C* Activity Description R*
AWO Review Design changes to ensure the following:
O Implementationis complete.
O Retesting method is adequate.
NCR Review TR Review
" Maintenance Rule Implementation EWR Review Jumper Bypass Review Operability Determinations or JCOs Control Room Panel Deficiencies Operator Burdens Pre-outage Work List Work not performed (rejected OSCRs)
A/R Review ACR Review Punchlist Evaluation j
Preliminary System Walkdown l
Surveillances System Testing LER Review Abnormal Plant Conditions Long-standing System Issues Other System Issues Final System Walkdown
- R = Reviewed; C = Completed SRT Leader: Date:
NUC PI 5 Level of Use . . - . . . -
..TH!NK '
ACT' REVIEW ~ Rev.1 STOP Information 23 of 29
Attachment 2
> Unresolved Item Report (Sheet 1 of 2)
~
SUBJECT FOR RESOLUTION UNIT 1 2 3 CY l UIR LOG NUMBER ORIGINATOR DATE SYSTEM 1 SOURCE DOCUMENT )
Primary Secondary Reference Date DESCRIPTION OF UNRESOLVED ITEM O CONTINUATION SHEET l DISCUSSION DETAILS 2
O CONTINUATION SHEET DISCUSSION BY Lead Engineer Review RECOMMENDED DISPOSITION DETAILS 3
O CONTINUATION SHEET DISPOSITIONER DATE CATEGORY O MATERIAL CONDITION O CONFIGURATION O ADMIN O TRAINING O VOID COMPLETION MILESTONE PRIORITY O START-UP O OTHER 1 2 3 4 4 FINAL DISPOSITION PVRT APPROVAL DATE UPM APPROVAL DATE FINAL DISPOSITION DOCUMENT DOCUMENT COMMENTS GENERATED O N/A NUMBER O ACR S O TR O FSAR CR O NCR O AR (other)
FINAL ROUTING DISTRIBUTION: 10 Data Base Clerk 10 Initiator 10 NDS UIR REVIEWED & CLOSED (Original) lDATE i
A ! NUC PI 5 Level Of USe ...~1_..-"
y ., REVIEW Rev.1
_XCTJ.x
" THINK
< STO P '"
nformat,On l ya r p; 7I( 24 of 29
Attachment 2 Unresolved Item Report Continuation Sheet (Sheet 2 of 2)
Continuation Sheet for: O Description O Discussion O Disposition I
i 1
1 l
1 I
v i
1 1
- l j
l j
Page of NUC PI 5 j Basis .. . _
l STOP ' THIN K ;ACTT ' REVIEVe/ Rev.1 Document 25 of 29 l
Attachment 3 Preliminary System Readiness Report Format (Sheet 1 of 1)
SYSTEM NO.
UIR Summary:
AWO Review:
Design Changes (PDCRs):
NCR Review:
TR Review:
Maintenance Rule Implementation:
1
. EWR Review: . ._ - -
Jumper Bypass Review:
Operability Determinations or JCOs:
Control Room Panel Deficiencies:
Operator Burdens: l Pre-outage Work List:
Work Not Performed (Rejected OSCRs):
A/R Review:
ACR Review:
Punchlist Evaluation:
Preliminary System Walkdown:
Surveillances:
System Testing:
LER Review:
Walkdown Checklist:
SRT Leader:
PVRT Approval: l UPM Approval:
. NUC PI 5 Basis _, ...~m. . . _
Rev.I STOP'.. ' THINK ' ";ACT - 'REMEW Document
- s y 26 of 29
Attachment 4 System Readiness Report Format (Sheet 1 of 1)
SYSTEM NO.
Overall Summary:
AWO Review:
Design Changes (PDCRs):
NCR Review:
TR Review:
Maintenance Rule Implementation:
EWR Review:
Jumper Bypass Review:
Operability Determinations or JCOs:
Control Room Panel Deficiencies: l
)
Operator Burdens: l Pre-outage Work List:
Work Not Performed (Rejected OSCRs):
A/R Review: 1 ACR Review: l Punchlist Evaluation:
Preliminary System Walkdown:
Surveillances:
System Testing:
LER Review:
Abnormal Plant Conditions:
Long-standing System Issues:
Other System Issues:
Final System Walkdown:
SRT Leader:
SRT Member:
SRT Member:
SRT Member:
PVRT Approval:
UPM Approval:
.; NUC PI 5 Basis m . . _ . _ . , - . , , . . - - . . .
Rev.1 STOP' ~ THINK ' ~-- ACT ~ ' REVIEW Document i
~I
^
27 of 29
,, -- __ r ,
m - - , -gr.- ,y - -
Attachment 5 System Readiness Memo Format (Sheet 1 of 1)
TO: Date:
MQC Chairperson FROM: Memo No.
Unit Project Manager SRT Leader
SUBJECT:
[ System Description]
l This memo documents an independent assessment of the readiness of the[ subject system] to support plant operation. This memo also presents a status of open items and provides a summary of changes to the system due to shutdown activities.
[Present here the major open items of the system so as to capture system statusfrom a readiness perspective. Include the "Over 211 Summary"sectionfrom the readiness report, which presents the status of open items arainst the system and why those items do not affect system readiness. Also provide a summary ofdesign changes that have been incorporated into the system.]
If there are any question on the status of the [ subject system 1, please contact me at
[ extension].
Approved by: Date:
MQC Chairperson (Unit Director) cc: Unit Director Director, Nuclear Engineering Manager, Operations Manager, Work Planning Manager, Design Engineering Manager, I&C Manager, Maintenance ,
Manager, Technical Support l Shift Manager System Readiness File Nuclear Records NUC PI 5 Basis Rev.1 Document STOP' ' THiNi[ $ACT "REVIEvT 28 of 29
Attachment 6 Definitions l (Sheet 1 of 1)
- A/R - Action Request
- AVAILABLE - Status of a system, subsystem, train, component, or device that is in service or can be placed in a functional or OPERABLE state within a time frame needed for prevention or mitigation of an accident.
- AVAILABILITY - A system, subsystem, train, component, or device has AVAILABILITY when it is AVAILABLE.
- EWR - Engineering Work Request ,
- OPERABLE or OPERABILITY - A system, subsystem, train, component, or device shall be OPERABLE or have OPERABILITY when it is capable of performing each ,
of its specified functions, and when all necessary attendant instrumentation, controls, ,
electrical power, cooling or seal water, lubrication, or other auxiliary equipment that are required for the system, subsystem, train, component, or device to perform its functions are also capable of performing their related support functions.
OSCR - Outage Scope Change Request
- System Readiness - Term used to describe system OPERABILITY or AVAILABILITY status.
NUC PI 5 Basis , ._ _ -.. .. .. _
STOP' *THINK ' REVIEW. _ . Rev.1 Document ? A.CT' y s 29 of 29
A
,, g
? N-NORTIIEAST UTILITIES NUCLEAR,: CY - I NU COMMON PROCEDURE \ UA1 $9%
l l
n ,
p
+ ,
v . + h I ib,o [
, h ffi,
, _ _ . . , .. . J. L . ,.:, .5.
l
. 4- -
T.; ,' " . ,
A .. ., . . .:- . .
,,.q',: s. ,_s,,...
ny;:t . : c:
TdF'. ,.y,-_*g~'t HIN Kf, f4.CT>9-/,
_ ~EVIEW 4 ,-
a g-w~ s n -n!_
D' li-:;;y:%gNgg Sy'~ %;.2 p&v , w~ '3-' :
y?:'I' l
p -
Nhk,,z ,
Licensing Reviews NUC PI 6 Rev.O This Project Instruction (PI) is part of implementation of the Configuration Management Plan (CMP)
Millstone Connecticut Yankee Seabrook soRC. httg. No.: PORC. httg. No.: SORC. httg. No.: M Date: Date: Date:
EtTective Date:
l l
l I
i I
Responsible Individual:
Level of Use s. Strout Information Subject Matter Expert:
\
-94cf6Secu<F D 3g, s. strout 1
1
MP1, MP2, MP3, CY NU Common Procedure Licensing Reviews 4
TABLE OF CONTENTS
- 1. INSTRU CTI O NS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1 Quality and Training Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.2 Development of Unit-Specific Positions on Regulatory Guidance . 3 1.3 Identification of Commitments and Verification of Compliance . . 7 1.4 D e live rabl e s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
- 2. R E FE R E N C E S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
- 3. CO M M ITM ENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
- 4. S U M MA RY O F CHANG ES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . , . . . 15 l'
A'ITACHMENTS AND FORMS Attachment 1, " Process Flow for Identification and Consolidation of Regulatory Requirements " . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Attachment 2, " Process Flow for Identification of Commitments and Verification of Compliance" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Attachment 3, " Proposed Format for Position Papers" . . . . . . . . . . . . . . . 19 Attachment 4, " Threshold for Commitment Identification" . . . . . . . . . . . 20 l
l 1 A A 5 NUC PI 6 Level Of Use , "AST.O,..P
- m.,c -7 ,MACT";b,A~
^THINK REVIEW Rev.O nformat.lOn jp.; jp; pg yn%( 1of22
- 1. INSTRUCTIONS This PI provides a structured methodology for compiling two elements of the Licensing Basis (LB) for Millstone Units 1,2, and 3; and Connecticut Yankee.
1.1 Quality and Training Requirements l ~. NOTE l
The LIST database is not QA controlled; however,it does have network j controls and cannot be modified by users. Since this database was ,
developed from controlled files and is fully searchable, it will be used for '
identifying documents related to any selected issue. Hard copy of all correspondence is available for review.
Unit Project 1.1.1 ENSURE all personnel involved in implementing this PI are Manager trained in the following:
- Configuration Management Plan l Use of LIST software (demonstration)
Regulatory Compliance Manual, Chapter 4, " Current Licensing Basis"
- NEI " Guideline for Managing NRC Commitments" 1.1.2 Licensing team members shall have general knowledge of regulatory correspondence, plant design change processes, and plant procedures. Specific unit familiarity is not required.
NOTE that is, not Section 1.2 guidance all regulatory and Section 1.3papers position need not needbe to performed be developedsequentially;ior pr to identifying commitments contained in other docketed correspondence or verifying compliance with those commitments.
1.1.3 Go to applicable section:
- IE developing position papers: Section 1.2 IE identifying commitments or verifying compliance with commitments contained in other docketed correspondence:
Section 1.3 Level Of Use [ d { NUC PI 6 nf0fmat,On Ngger Sgr ggpr'lEViWT' Rev.O l
gpt;g g gg ; 2 of 22
1.2 Development of Unit-Specille Positions on Regulatory Guidance NOTE Unless othenvise noted, the term " Licensing personnel" is used generically to indicate any licensing team personnel assigned to any unit.
1.2.1 DEVELOP a list of topics and regulatory guidance documents which require position papers. The regulatory guidance document list shall include:
- General Design Criteria (as applicable to the unit)
. Control Room Design Review f
EEQ
. Erosion / Corrosion
- External Events / Hazards (Tornado, EQ, Flood)
=
HELB/MELB
= Inservice Inspectior.
. IPEEE
- Master Equipment and parts List (MEPL)
- Regulatory Guide 1.97 Compliance
- Safe Shutdown /10CFR50 Appendix R Compliance l
- Separation / Independence / Diversity 1
I Setpoint Control
- Single Failure ,
- Station Blackout
. 10CFR50 Appendix J Compliance
- USI A46 ,
- Heavy loads I A A 4 NUC PI 6 Level of Use ~ e --- ..u , - . .
a..,
Information )If y %
Y,A 'IN-y .
eN p4
,o"f22
}
b
l Unit ucensing 1.2.2 DETERMINE which documents of the following document types Lead require position papers for each individual unit and INCLUDE appi! cable documents on the Regulatory Guidance Documents List for that unit:
4 Code of Federal Regulations (CFR)
Division 1 Regulatory Guides
- TMIitems specified in Unit Orders Source document for all key topical areas listed in the CMP Standard Review Plan Selected Generic Letters
Other TMI items Selected codes and standards .
Issues unique to the unit 1.2.3 ROUTE completed Regulatory Guidance Documents List to the applicable Unit Project Manager (UPM) for review and approval.
lUPM l 1.2.4 REVIEW and APPROVE Regulatory Guidance Documents List.
Ucensing 1.2.5 WHEN the Regulatory Guidance Documents List is approved by personnel the UPM, IDENTIFY unit documents which address each guidance document as follows:
- a. PERFORM searches of LIST database using key words selected from the document name and subject.
- b. DETERMINE the set of documents to be reviewed, using the results of the searches.
- c. IDENTIFY the key words used for each search, PRINT and MAINTAIN the results of the searches.
- d. PROVIDE the list of documents to be reviewed for each l guidance document to the Design Engineering Team (DET).
Level of Use k 8 8 / NUCPI6 Information _5fof iNF MCFTsMWT Rev.0 p4 p4 jf%( jd4 g 4 of 22
1.2.6 DETERMINE commitment to a guidance document as follows:
l DET l
- a. REVIEW each referenced document and DEVELOP other references as needed to determine the level of commitment to the guidance document.
NOTE ,
Section 1.8 and Section 3.0 of the MP3 UFSAR provides examples of the minimum level of detail required for th.: position papers. Attachment 3 contains additional information on recommended format. For MP1 and CY, the SEP provides a starting point for the position papers. a 1
- b. PREPARE a position paper on the guidance document and the application of the document to the unit, including:
- Name of the guidance document
- l
- Whether or not the unit is committed to the document, in ;
- whole or in part i 1
- Primary discipline affected: l f - Mechanical j
- Electrical
- Operations
- Administration l
- Structures
- Chemistry
. Radiological /HP
- Special
- List of applicable source documents
- c. SIGN the position paper and FORWARD to a Second Reviewer.
A A A *. NUC PI 6 Level of Use _.A , a
~. -.
"STOP' r ,K"
' THIN 4 ACF ' REVIEW Rev. 0 lnfOrmatlOn 7; ;Q4, . eg ;.4a p@6s
,s 5 of 22 s
.- I Second 1.2.7 REVIEW the position paper for adequacy, completeness, and Reviewer correctness.
- a. E acceptable, SIGN position paper and FORWARD to UPM.
- b. E not acceptable, RETURN position paper to preparer with comments.
Unit Proj ct 1.2.8 REVIEW the position paper for adequacy, completeness, and 1 Manager correctness, a E acceptable, SIGN position paper and FORWARD to Design Engineering Manager..
- b. E not acceptable, RETURN position paper to preparer with ,
comments. l Design 1.2.9 REVIEW the position paper for adequacy, completeness, and Engineering correctness.
Manager
- a. E acceptable, SIGN position paper and FORWARD copy to ;
MQC. j
- b. E not acceptable, RETURN position paper to UPM with
! comments.
" VERIFY the position papers for each unit are assembled into a Design 1.2.10 Engineering single controlled document.
Manager 1.2.11 E at any time this document requires change or revision, !
VERIFY a 10 CFR 50.59 evaluation is performed on the proposed change or revision.
NOTE It is recommended that an independent review or assessment be performed on approved position papers before the position papers are used as part of the NUC PI 7 review, 1
A k & 8 NUC PI 6 l Level of Use ,_rL,..
. "STOP" y"THINW2 n, 4ACTc/LREVIEW , m; 1- Rev. O nformation j p4; j;L jt' [N 6 of 22
i 1.3 Identification of Commitments and Verification of Compliance
- NOTE 1
Attachment 4 provides a definition of" commitment" and descrioc how this definition is to be implemented at each NU Connecticut unit.
ucensing 1.3.1 DEVELOP the potential source documents list as follows:
personnel
- a. COMPILE a listing of all source documents for the selected i
, calendar year as follows- I l
i 1) SEARCH on <date YY> for all four units (all four
" Unit" buttons pressed).
, 2) SORT on date.
t
- 3) PRINT comprehensive potential source documents list.
i lt
+ r 1 J' ..H El c NUC PI 6 Level of Use . . . _
Information SToP 'iACFhivsf Rev.0 l 4
y ~st p y 'y pg. 7 of 22
l l
i NOTE j t
i The following list may not be comprehensive, and may be expanded as ,
reviews are performed and other types of documents are identified that are I clearly not commitment documents. l l ;
- b. ELIMINATE documents on the potential source documents 1
-, list that are not commitment documents as follows:
- 1) REVIEW each listed document, and MARK through and INITIAL any document that is clearly: l
- Fee invoices or payments
. Operator qualification or requalification test schedules or results ;
l l
Fitness for duty reports (annual or individual) l l .
Requets for site access for NRC employees or contractors
. Notices of meetings or workshops
. Proposed rules and comments on proposed rules l
- Property inswance correspondence i - Annual cubrt tal of QA Topical, Security Plan, or Emert ency Pin Other typeo , acuments, as directed by the UPM or l
Licensing Lead
- 2) PERFORM an on-line screening review of the remaining documents to determine whether any additional documents may be eliminated.
- 3) On the printout, MARK through and INITIAL any document that is eliminated by on line review.
- 4) REQUEST confirmatory review of the potential source documents list by a Second Reviewer.
I second 1.3.2 VERIFY only noncommitment documents on the potential source l Reviewer documents list are marked ough and initialed, and FORWARD
] the source documents list to appropriate Licensing Lead.
i I A h h- 4 NUC PI 6 Level of Use - -
' TH!NK';_ .\ ACU l 'STOP'
- REVIEW Rev.0
- lnformat. ion v m-y '.q 4
y3 : s y , 8 of 22 4
NOTE Each unit team shall review all documents specifically assigned to its unit.
The multi-unit documents shall be distributed as work load permits.
Ucensing 1.3.3 SEPARATE remaining documents on the source documents list Lead ., into logical" working set lists" and ASSIGN sets to Unit Licensing personnel.
Unit ucensing 1.3.4 REVIEW documents listed on the assigned " working set list" and personnel IDENTIFY all commitments contained in each document as follows:
- a. OBTAIN a copy of the document.
- b. Refer To Attachment 4 and NOTE the threshold on the document.
1
- c. REVIEW the document and IDENTIFY (by circling) each .
l commitment made within the document as follows:
- Refer To Attachment 4, IDENTIFY the commitment -
type and NOTE on the document.
- IDENTIFY each unit the commitment affects and NOTE on the document.
- Based on the threshold, DETERMINE whether a commitment record is needed and NOTE on the docament.
NUC PI 6 Level of Use 60 #
lnformation I j; 9 0f 22 e . v -
I NOTE For commitinents that affect multiple units, a separate commitment record is prepared for each affected unit. THE COMMITMENT RECORD DATABASE HAS NOT YET BEEN DEVELOPED, SO THIS PI REFLECTS USE OF A PROCESS THAT DOES NOT SPECIFICALLY REQUIRE A DATABASE.
a g*
Ucensing d. IE applicable (as determined in step 1.3.4.c.), PREPARE a personnelor commitment record for each commitment, containing the Data Entry Technician following:
Unit number
=
Identifier information (from, to, subject, and date)
=
Text of the commitment and all necessary information from the source document to provide an understanding of the commitment by an individual who does n6t have the source document available, using the following guidelines:
=
COPY the commitment as close to verbatim as possible.
PLACE all clarifying text in square t rackets.
Example: [ clarifying text] :.ctual commitment [ clarifying text]
=
System name or number (if known)
=
Commitment owner (either system engineering or appropriate supervisor if other department)
=
Preparer's name
- e. REQUEST confirmatory review by a Second Reviewer.
1 Level of Use i A ,
NUC PI 6 Information 6# N~ NK' ' pct" sav5V/' Rev.0 y3 y g p, 10 0f 22
l
'I 1
NOTE For multi-unit source documents, the Second Reviewer shall be from a different unit team than the preparer.
1 i
second f. VERIFY that a commitment record is prepared for each Reviewer identified commitment and for each unit affected by a
~
commitment; and that each commitment record contains required information for each commitment.
- g. VERIFY status of commitment record is "OPEN" and RELEASE commitment for compliance verification.
NOTE The following list may not be comprehensive, and may be expanded as reviews are performed and other types of potential closure or '
incorporation processes are identified.
Unit ucensing 1.3.5 EVALUATE compliance with each commitment identified in personnel step 1.3.4 as follows:-
- a. REVIEW text of the commitmen' record and DETERMINE how the commitment may have been closed or incorporated, including the following potential closure or incorporation i processes: l Later correspondence Procedure change or revision or new procedure (including procedures that, in the reviewer's opinion, should aridress the commitment)
Training changes Hardware changes (PDCR)
. Maintenance activities
- b. EXAMINE each potential closure or incorporation document to determine whether the commitment is adequately addressed.
? a
- NUC PI 6 Level of Use ' .. -. -- -
- m. -
SToP ' THINK :ACT~ REVIEW Rev.O lnfoMah.on
, , , f 11 of 22
i l
- c. E adequately addressed, PERFORM the following:
NOTE in the commitment record how the commitment is addressed.
E the commitment is addressed by one or more procedures, AND the reference is properly identified as a commitment in each procedure, CHANGE status of commitment record
,. to " ACTIVE."
NOTE Procedure changes are initiated using the applicable procedure:
For Millstone: DC 2," Initiating and Revising Mi!btone Procedures and Forms"
- For CY: ACP 1.2-6.5," Station Procedures" f
- E the commitment is addressed by one or more procedures,
! AND the reference is not properly identified as a commitment in any of these procedures, PERFORM the following:
i Refer To applicable procedure and INITIATE a change to each procedure that does not contain the reference to add the commitment reference to the Basis Document.
j -
CHANGE status of commitment record to
" WORKING."
I E the commitment is closed or superseded by later correspondence, PERFORM the following:
NOTE the closure or superseding correspondence in the commitment record.
CHANGE status of commitment record to " CLOSED."-
i i
, ? A L
- NUC PI 6 Level of Use ~ . . - . . A-r-..- -
Rev. O
'STOP' THINK' .~ " ACT '
REVIEW Information -
a ja
. - g --
y w g 12 0f 22
l e
- d. IE not adequately addressed, PERFORM the following:
i VERIFY status of commitment record is "OPEN."
NOTE Resolution of discrepancies is addressed in NUC PI 14, " Project Process
_,. Administration."
IE required, Refer To the applicable procedure and INITIATE an ACR for each identified discrepancy:
RP-4," Adverse Condition Resolution Program" (for Millstone)
ACP 1.2-16.5," Adverse Condition Report Process Implementation" (for Connecticut Yankee)
- e. REQUEST confirmatory review of the commitment record by Second Reviewer.
second f. VERIFY the commitment record for each commitment Reviewer contains applicable information, based on review results.
Commitment 1.3.6 REVEW each assigned commitment and DETERMINE owner adequacy and completeness of references. ACCEPT commitment if adequate, ucensing 1.3.7 REPEAT steps of 1.3.5 as needed to resolve unaccepted Lead commitments.
NOTE It is recommended that an independent review or assessment be performed for commitments at this time.
l l
l I
1 l
l z .
f':
NUC PI 6 Level of Use .. - . . . - - . - -
~ STO.P ' ' TH!NK ~_ _I- ACT ' ' REVIEW Rev.O lnformat. ion ,,
,3, .,
, ,4, m 13 of 22
1 1.4 Deliverables ucensing 1.4.1 VERIFY the following deliverables result from implementation Lead of this PI:
Controlled document for each unit containing position papers on all selected regulatory guidance documents !
4 Database of all active commitments for each unit Listing of all commitments no longer in effect (for historical I purposes)
Discrepancies for commitments for which compliance could ;
not be identified.
1 1
l t
1 1
l l
l 4
Level of Use .,.$ ~ , d _ . $k . _ b . . ., NUC PI 6 Information
's w p' .
pr
- 9
- ACF 5;
RE e Rev. 0 14 0f22
l l
- 2. REFERENCES 2.1 Configuration Management Plan (CMP) 2.2 RP-4, " Adverse Condition Resolution Program" 2.3 ACP 1.2-16.5," Adverse Condition Report Process Implementation" (for Connecticut Yankee) 2.4 NUC PI 14," Project Process Administration" 2.5 Regulatory Compliance Manual, Chapter 4," Current Licensing Basis" 2.6 NEI " Guideline for Managing NRC Commitments" 2.7 MP3 UFSAR, Sections 1.8 and 3.0
- 3. COMMITMENTS None
- 4.
SUMMARY
OF CHANGES 4.1 Original Issue i
Level Of Use . I . , ,, $ . " "~ I8
- STOP' ~' THIN K . <ACT'.
$1 "REVIEv/
NUC PI 6 Rev.O nfOrmation j
,) -
4( 15 of 22
l 1
Attachment 1
. Process Flow for Identification and Consolidation of i Regulatory Requirements )
(Sheet 1 of 1) l l
l DEVELOP unit-specificlist of guidance. l 1r l IDENTIFY correspondence regarding this guidance. l 1P REVIEW all identified documents and i DETERMINE commitment to the guidance.
1r l PREPARE position paper. l 1r second Nn L MMN to l REVIEW position paper. l Acceptable? -
T preparer.
Reviewer Ye)
A 1
w L Nn L RETURN to l REVIEW position paper. i y Acceptable? r preparer.
UPM J Yes 1
Desip I yn A RETURN to
, L Enpneering l REVIEW position paper. i y Acceptable? F UPM. 1 Manager Yes 9P ,
ASSEMBLE position papers )
i into controlled document and MAINTAIN control of l J
position papers.
1 e-A NUC PI 6 Level of Use .
Rev.O "STOP ~ TH!NK -ACT - - . REVIEW Informat. ion .
ggg
1 Attachment 2 Process Flow for Identification of Commitments and Verification of Compliance (Sheet 1 of 2)
Identification of Commitments I
Licensing DEVELOP 4-unit potential source documents list.
Pe.r.sonnel l
l ELIMINATE documents that are clearly not commitment sources.
I Second I VERIFY only noncommitment documents are Reviewer eliminated from source documents list.
I Licensing SEPARATE source documents list into " working set lists" Lead and ASSIGN sets to Unit Licensing personnel.
for each document Unit IDENTIFY all commitments, type, and threshold in Licensing each document on assigned working set list.
Personnel I
IDENTIFY which units are affected by each commitment.
I Licensing personnel or Data Entry Tech PREPARE a commitment record for each commitment and for each unit to which the commitment applies.
Second Reviewer VERIFY commitment record is prepared for each relevant commitment in assigned working set list; and each commitment is adequately described in commitment record.
RELEASE record for verification of compliance.
l
^
- _. ._ dn NUC PI 6 l Level of Use _4 .
.c _ y v, Rev.0 l
VACV ' REVIEW STOP' THINK 1nformation -- -
t7 + "
17of22 r -
v % v' R .
l
Attachment 2 Process Flow for Identification of Commitments and Verification of Compliance (Sheet 2 of 2) I l
For each commitment Verification of Compliance Unit Licensing DETERMINE potentialclosure personnel or incorporation documents.
Commitment No adequately INITIATE resolution.
VERIFY status '4 addressed?
i3 OPEN."
Yes Commitment No appropriately INITIATE change to CHANGE status annotated in add commitment to to 'd document? document. " WORKING."
Yes Commitment yes NOTE closure or CHANGE status .y closed or superseding document to " CLOSED."
superseded? in commitment record.
No 4 ,
y i CHANGE status to " ACTIVE."
+
Second '
Reviewer VERIFY commitment status.
l
+
Commitment Owr . er ACCEPT commitment.
A is NUC PI 6 Level of Use , _ . . -.- -
' STO P ' TH!NK ' ':ACT' REVIEW Rev.0 Information 4g ,,
- ,' 18 of 22
, x a , ,
1 Attachment 3 Proposed Format for Position Papers (Sheet 1 of 1)
Guidance Document Identification Information:
l PROVIDE document number, name, and revision or date (if applicab!e). 1
- Examples
- GDC 14," Reactor Coolant Pressure Boundary" l R.G.1.27, " Ultimate Heat Sinks for Nuclear Power Plants" -l l ,, Rev. 2, January 1976 ;
Synopsis of Guidance:
PROVIDE a one or two paragraph synopsis.
Unit-specific Position on Guidance:
DESCRIBE level of commitment to guidance, using the following phrases where possible:
Complies with . . .
l Meets the intent by . . .
l Provides equivalent . . .
. Is committed to . . . ;
l
- Is committed to except for . . .
Is not committed to . . . ;
1
- Is committed only to . . . l l
ADDRESS recognized system variations (if stated). l ADDRESS time variations (if stated).
IDENTIFY the primary discipline affected by the guidance.
Source Documents:
LIST all documents used to develop the position. !
Signo!Ts: i i
VERIFY position paper is signed and dated by the the following:
Preparer
- Independent Resiewer 2
Unit Project Manager 1 . Design Engineering Manager i - >
i [ NUC PI 6 Level of Use ~ . . - - ..--
x., s ~ REVIEW
'STOP THIN K' "ACT' Rev.0 lnformat. ion D i; ; Es - /1~ ,? , r o,. 19 of 22
Attachment 4 Threshold for Commitment Identification (Sheet 1 of 2)
NGP 4.01," Communications with the Nuclear Regulatory Commission," defines a commitment as:
'An explicit statement to take a specific action agreed to or volunteered by NU that has been submitted on the docket to the NRC, by designated Nuclear Group management in writing."
Tlis definition leaves substantial room for interpretation. For example, does a statement that an action has been completed constitute a commitment?
NOTE f
, If a question exists as to which category a commitment belongs, the
- commitment is treated as a Type 'A' commitment for identification.
l Statements regarding action taken in scheduled established programs are
, not commitments.
1 i
l For this Project Instruction, the following are considered commitment types:
)
i . Type 'A': Stated action taken (or promised to be taken) that changes the design or operation of the unit; or stated actions taken relied upon by the NRC Staffin an SER (that is, commitments that potentially change the LB or DB)
- Type 'B': Stated action taken (or promised to be taken) that restores the unit design or operation to the condition bounded by the LB or DB at the rime the statement was made, excluding statements regarding actions taken sia established programs.
Type 'C': Promised or requested submittal of information to the NRC or other agency
)
1 I
I e
4
_.r n NUC PI 6 Level of Use . a '- , . . . _
- STOP" ~'THtNK 'r CACT' ' REVIEW Rev 0 Information m p q - N p 20 0f 22
1 Attachment 4 l' Threshold for Commitment Identification (Sheet 2 of 2)
Examples of commitment types:
Type 'A':
1
- We have installed a higher capacity . . .
. We will revise Technical Specification Section . . . l
- We have initiated a procedure upgrade program.
- We will establish administrative controls until the modification can be installed.
1)pe 'B':
- The leaking valve will be repaired during the next outage.
- The system was restored to OPERABLE status.
- The drawing was corrected.
Type 'C':
. Please provide a response to this Notice of Violation in 30 days.
. We will submit the results of our analysis prior to startup.
All " types" of commitments shall be identified on the documents during the review.
However, commitment records are created only for commitments which exceed the following thresholds:
l 1
A, A 6 NUCPI6 '
Level of Use .
m ._, A.- A, ._:n.m. 1 STOP' T HIN K' <ACT'
' REVIEW Rev.O gnformat. ion jpg p, j;" f4!\. 21'of 22 8
. , . , . ~ __ m ._
l
- For correspondence dated back to 1/1/94: Threshold 1:
- Any commitment which meets any of the above " type" definitions
- - For correspondence dated from 12/31/93 back to 1/1/84: Threshold 2:
l
. All Type 'A' and Type 'B' commitments except those Type 'B' commitments which have a completion date or associated event that has passed
^'
- Any Type 'C' commitment with a completion date of 1996 or later
- For correspondence dated from 12/31/83 back to initial licensing: Threshold 3:
l All Type 'A' commitments except those which have a completion date or associated event that has passed l
Any Type 'B' and Type 'C' commitment with a completion date of 1996 or later f
(
l I
I 1
l s
1 1
~
t j$ NUC PI 6 Level of Use .v 6 . , _ . /t ',
HIN MCT EEVIE [ Rev.0 Information FOP ' }y .K 1 y% ,; ,,. y g7 y i
.' <k p
b l, v ICY --
NORTIIEAST UTILITIES NUCLEAID "
UE1 @?1 ,
PROJECTINSTRUCTION . . =
g A . .:.y.y h.
gh o[,
f s ,
/u\
_ e -
. i
.Acvy ,yR;eview any
--x.:;;h~ TOP'7 ~<xksy; s: w HINKt.?. . 8, i
e %
,- w['., j I :$h; w j
., ,,, ; j Giaded' System Review NUC PI 7 1
Rev.0 This Project Instruction (PI)is part of implementation of the Configuration Management Plan (CMP).
Approval Effective Mtg. No. Date Date Millstone SORC pf gy y gg4f, CYPORC MP1 PORC MP2 PORC MP3 PORC a
Responsible Individual:
Level of Use '
E Mattioli Subject Matter Expert:
lnformation
[(pdka_SO O W d rf /s E Mattioli/J. Scarfoss
MP1, MP2, MP3, CY _
Project Instruction l Graded System Review .
, TABLE OF CONTENTS i
l
- 1. I NSTRU CTI O N S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
'., 1.1 Training Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 l
1.2 Este.blishing System Review Team . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.3 Licensing Basis Determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.4 Design Basis De termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.5 S elf- Assess men t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.6 Valid atio n Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.7 System Package Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1.8 D isc rep an cie s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
- 2. R E FE R EN C E S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
- 3. C O M M ITM E NTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
- 4.
SUMMARY
OF CHANG ES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 ATTACHMENTS AND FORMS i i.
! Attachment 1, " Documentation of System LB and DB" . . . . . . . . . . . . . . 16 Attachment 2, " Typical Attributes to Determine DB" . . . . . . . . . . . . . . . . 20 i
Attachment 3, " System LB and DB Package" . . . . . . . . . . . . . . . . . . . . . . 24 l
l Attachment 4, " System Review Matrix" . . . . . . . . . . . . . . . . . . . . . . . . . 25 Attachment 5, " System Review Process" . . . . . . . . . . . . . . . . . . . . . . . . . . 27 l
i i _
l A A A 4 NUC PI 7
- Level of Use -,x. _ . ,'a;w,- m~._ w .REVIEW. ._..
'" SToP ' THINK ' 4ACF Rev.0 lnformat. ion - ' -
4 jr .'4 p -q y3 ps 1of28 J
.- 1. INSTRU(XIONS _
The objectives of this Project Instruction (PI) are:
. Determine the Licensing Basis (LB) and Design Basis (DB) for systems as identified in the Configuration Management Plan (CMP).
. Categorize NUC PI 1," Document Identification and Retrieval,"
information in order to support preparation of documents in accordance with NUC PI 9," Design Basis Documents," and NUC PI 13,"UFSAR
-' Changes."
= Review appropriate system design data (i.e., NUC PI 1 information) to ensure the system meets DB requirements.
This PI provides a consistent approach to determine and/or confirm the LB and DB for each system reviewed. This system review is accomplished using results from performance of the following:
. NUC PI 1," Document Identification and Retrieval"
- NUC PI 6, " Licensing Reviews"
. Other PIs as noted throughout Attachment 5 contains a flow chart of the system review process.
The term " system" as used in this PI includes the systems committed to in the unit-specific CMP Implementation Plans and Topical Areas defined in the CMP attachments.
& NUCPI7 Level of Use ,_ %*
A m
)iw mm, 34
!' ~
Rev. 0 -
" STOP- THINK VACT" REMEW gnfOrrnat.lOn ppag pp J 2of28 Q
.. 1.1 'Iraining Requirements Unit Project 1.1.1 ENSURE all personnel involved in implementing this PI are i Manager trained in the following:
- Configuration Management Plan
- RP-4," Adverse Condition Resolution Program" (for Millstone)
- ACP 1.2-16.5," Adverse Condition Report Process Implementation" (for Connecticut Yankee)
- NUC PI 1," Document Identification and Retrieval"
- NUC PI 6, " Licensing Reviews"
= NUC PI 8," Plant Verificatio ad Readiness Team"
- NUC PI 10, " Configuration Management" l
- NUC PI 14," Project Process Administration" l l
= NUC PI 16," Licensing Basis and Design Basis Walkdowns" oesign 1.1.2 ENSURE all personnel involved in implementing this PI are Engineering qualified (based on their resume or current job description) and -
Manager - - - -
are provided specific training on this PI to ensure their ability to meet procedure objectives.
1 1 4 ^ NUC PI 7 Level of Use g pr. , g 7 , g y ,.ggfjgy7 g,y, g Information jag j;g y j- 3 of 28
_ __ _ _ 1 _ . ____
1.2 Establishing F fstem ReviewTeam Jesign 1.2.1 Refer To the unit-specific CMP Implementation Plans En neering attachments within the CMP and ASSIGN a System Review Team Le (SRT) Lead to each listed system.
1.2.2 REVIEW each assigned System and/or Topical Area and l SRT Lead l DETERMINE which disciplines need to be part of each SRT.
Design . 1.2.3 ASSIGN members to SRTs based on disciplines required for each Engineering System or Topical Area.
Lead i
1 l
1 i
Level of Use $! $ #+ j NUCPI7 Infdrmat,oni
~vgjgpr r
wggy v
x:MdI, y"5MT a, ; ,
Rev. O p". . ;;ya%, p '3 y q_ A of28
l.*
j, 1.3 Licensing Basis Determination i _
. NOTE
! 1. Specific instructions are contained within this PI to ensure that 1 additionalinformation is properly reviewed as the information l
becomes available.
I 2. Attachment 1 provides a documentation outline for reviews performed j by this PI. Associated procedure steps are noted in Attachment 1 for
- each documentation requirement in the outline.
^'
- 3. Those NUC PI 6 items identified as applying only to a s accific System or Topical Area are not required to be reviewed for app icability by other System Review Teams.
- 4. If at anytime during performance of this PI a discrepancy is found, Section 1.8 provides mstructions for handling the discrepance 1.3.1 OBTAIN documentation resulting from NUC PI 6, " Licensing l SRT Lead }"
Reviews."
1.3.2 REVIEW NUC PI 6 results to determine the following:
l SRT l
= Which unit LB requirements are applicable to the system being reviewed and the reason why the requirement is applicable.
. Which unit LB requirements are not applicable to the system being reviewed and the reason why the requirements are not applicable.
1.3.3 INITIATE an Attachment 1 and DOCUMENT results of step 1.3.2 for each LB document reviewed.
NOTE The system LB is defined as that portion of the unit LB that is applicable to the system under review.
1.3.4 ASSIGN system LB to the appropriate SRT member for DB
[* determination.
- a. DOCUMENT assignments on Attachment 1.
i
{
NUC PI 7 Level of USe Ay f,^~
Information y?g _37, ,]A. ph yn AcT_ ._'Rgew pmz Rev. 0 ,
1 jry 5 og 2g
1
[
I i
l . .
1 1.3.5 Using the system LB, PERFORM a group review to accomplish
~. l SRT the following for each LB document reviewed and DOCUhENT results on Attachment 1:
- ESiABLISH communication among the SRT members.
IDENTIFY " hand-offs" between SRT members (such as i discipline).
- ELIMINATE duplication of efforts (such as screening for l l ,,. topical issues).
t l
i
)
i l
l i
l l
l l
l \
l l
l I i i
.i J
) A & A NUC PI 7 Level of Use .a
- STOP-y 'THINK
.A - m. A , _- ~-
Rev.0
- 4ACT" 'RMEW lnformat. ion gn ;~ ;-
pag .
y 4,
, g 9 je %. 6 cf 28 i
3 o
' ~
1.4 Design Basis Determination NOTE Design Basis consists of:
- System Design Basis
- Component Design Basis
- Structure Design Basis
- Portions of supporting systems required to meet a System Design Basis 1.4.1 EVALUATE each assigned system LB (from step 1.3.4) to l SRT Member j" establish DB.
- a. DOCUMENT results on Attachment 1.
1.4.2 Using the DB from each assigned system LB, PERFORM a group l SRT l" review and ENSURE DB determination has fully captured all discipline or' generic issues.
- a. DOCUhfENT results on Attachment 1.
1.4.3 Refer To NUC PI 1," Document Identification and Retrieval,"
I SRT Lead l" and OBTAIN documentation pertaining to the System or Topical Area being reviewed.
1.4.4 REVIEW System or Topical Area documentation and lSRT l CATEGORIZE information as follows:
- Information that is DB (Category 1)
Information that is EDB (as defined in the C.dP) which supports the DB (Category 2)
- Remaining EDB information (Category 3) 1
- Other information (Category 4) i i
A A A NUC PI 7 ,
Level of USe .; n. , m~/ w .va. . ,
,r .,,.
STOP' m"THINK" 4! ACT' REVIEW Rev. 0 s - u -
lnformat. ion v 3 l
p3 p s.g p< g %, 7 of 28 i
l
l 1
.- l l
.~
l 1.4.5 OBTAIN the following from UPM:
. Categories to be reviewed (from step 1.4.4) l l
- Depth of review required for each category as specified within the CMP
. IE applicable, any actions resulting from NUC PI 2,
" Unit-Specific Assessments" NOTE Category 1 and Category 2 information support the Design Basis. When l documentation that sup s the DB has been identified, the Desi (as described in the NO before step 1.4.1) has been determinec'gn Basis 1.4.6 REVIEW information contained in Category 1 and Category 2 lSRT l#
for the following and DOCUMENT results on Attachment 1:
. Does the information support the DB?
. Does the information identify additional DB or modify DB?
1.4.7 IE review of information contained in category 1 and Category 2 identifies additional or modified DB, IDENTIFY additional or modified DB on Attachment 1 and Go To step 1.4.2.
Level of Use ,
7s !g,., 7 .w r ;
lnformatton pgj jpg jpk .
8of28 l
l
1.5 Self-Assessment 3RT Lead l" 1.5.1 IE directed by UPM, Refer To NUC PI 14," Project Process Administration," and PERFORM a self-assessment to ensure consistency and completeness among systems.
l l
6 9
A- , A
. ,A,, __ . ._nc.,_. NUC PI 7 Level of Use '-,A.,n g ST.oP'7. ,THINK", ,%_,,ACT. ,,REVIEv/ Rev. O lnformat. ion g en n ~ ::
f, pag p g; pp;( f j;pRjk 9 of 28
}
.- 1.6 Validation Process 1 1.6.1 Refer To NUC PI 16, "Walkdowns," and PERFORM the 3RT Member l" following to confirm the plant configuration supports the DB developed for the assigned System or Topical Area:
REVIEW walkdown checklists completed to date.
=
. IDENTIFY need for new and/or additional walkdowns.
" . WHEN complete, REVIEW new and/or additional walkdown checklists.
NOTE Validation of DB may be accomplished using either the ACCESS database or the hardcopy method, as specified in NUC PI 8.
1.6.2 REQUEST performance of NUC PI 8," Plant Verification Readiness Team," to validate DB determined in step 1.4.6.
l SRT Lead f 1.6.3 COLLATE information from SRT members.
1.6.4 E applicable, DOCUMENT any additions or modifications to the DB noted in Section III of Attachment 1.
1.6.5 DETERMINE whether additional information has been generated from NUC PI 6 and NUC PI 1.
1.6.6 E additional information has been generated, DOCUMENT l additionalinformation on Attachment 1 and PERFORM applicable action:
- For Licensing Basis information, Go To Section 1.3.
- For Design Basis information, Go To Section 1.4.
A A A A NUC PI 7 i
Level of Use lnformation ygpr gnF MM7'OW Rev.0
/P9 JP% /E% /PM, 10 of 28
1 1.7 System Package Documentation SRT l 1.7.1 REVIEW each completed Attachment 1 and PERFORM the following:
- a. DETERMINE all DB associated with the System or Topical Area under review.
- b. INITIATE Attachment 4 for the System or Topical Area under review. l l ~-
- c. LIST DB on Attachment 4. '
l NOTE Review or performance of items shown on Attachment 4 is considered complete only after all of the following are resolved:
Identified discrepancies l
=
Required procedure changes Required document changes (other than ' procedures) 1.7.2 COMPLETE Attachment 4 for each DB identified in step 1.7.1 as follows:
l a. For each item reviewed and/or performed and completed, INITIAL the appropriate box.
- b. For each item reviewed and/or Nrformed but not completed (open issues), PERFORM th t# wing:
l 1) INDICATE a numerical value in the appropriate box.
- 2) IDENTIFY the numerical value and each associated l open issue on Sheet 2 of Attachment 4.
- c. For each item not required to be reviewed and/or performed, ENTER "N/A"in the appropriate box.
l l SRT Lead l* 1.7.3 REVIEW all open issues identified on Sheet 2 of Attachment 4 ;
and PERFORM the following for each item: j l
- a. IDENTIFY and RECOMMEND action on those open issues 1 I
which must be completed prior to completion of this PI.
i I._..j NUC PI 7 i
Level of Use ,"STOP
d _ o" THIN -
d ,K' ,NACT"' ' REVIEW Rev. O u lnformat. ion 4 jp
. b. ENSURE all open issues are being tracked as specified in NUC PI 14," Project Process Administration."
1.7.4 REVIEW Attachment 4 and PERFORM the following:
I
] DEL f
- a. ENSURE Attachment 4 is complete.
- b. IDENTIFY those open issues which must be closed prior to completion of this PI.
! - c. ENSURE necessary resources are available to support timely closure of open issues.
- d. ENSURE all open issues are being adequately tracked as specified in NUC PI 14," Project Process Administration."
1.7.5 PREPARE a System LB and DB Package, consisting of the
. System LB and DB Package Cover Sheet (Attachment 3)
. System Review Matrix (Attachment 4)
- All Attachment 1 information, consisting of the following:
- 1) Verified and Validated System LB
- 2) Verified and Validated Component, Structure, and .
System DB I
- 3) Verified and Validated System or Components required to support the DB 1
- 4) Description of supporting design information that has been reviewed
- 1.7.6 SUBMIT system package to Unit Project Manager (UPM).
l I
- NUC PI 7 Level of Use A~
'" STOP K' ~<ACT"
. _1. .-
" REVIEW Rev.O gnformat. ion ' THIN, yAy.?
p g / .
p 12 af 28 l
l
NOTE The UPM approved System Pab.ge is a controlled document and is controlled as specified in NUC M 14, " Project Process Administration."
lUPM l 1.7.7 REVIEW and APPROVE System Package.
1.7.8 ENSURE Sistem LB and DB Package are available as QA
.,,. documentation as required to support implementation of the following:
i j
j . NUC PI 9," Design Bases Documents" i
4 -
i i
i 1
i i
i 1
)
l l
a i
4 1
j d #
A
^
NUC PI 7 4
Level of Use ,A._y. . ,A , ,,. a t ..,~._ 2...,
+ STOP - ~THINK' '%ACT' ' REVIEW Rev. 0 Information st gg w--
y3 y S; y x::sq y 13 of 28
1.8 Discrepancies NOTE Discrepanciesare tracked and remain as open items until resolved.
Resolution of discrepancies is addressed in NUC PI 14," Project Process Administration."
l SRT Member f 1.8.1 IE required, Refer To the applicable procedure and INITIATE an ACR for each Jentified discrepancy:
RP-4," Adverse Condition Resolution Program" (for Millstone)
ACP 1.2-16.5," Adverse Condition Report Process Implementation" (for Connecticut Yankee) h Level of Use l
--s .~~ -A- _e? m ,rl-h NUC PI 7
'STOP' "THINK' N ACT1- REVIEW Rev. O lnformat. ion p'
~
p.:4.
ft ;Lg p .
14 of 28
1
- 2. REFERENCES i 2.1 Configuration Management Plan (CMP) 2.2 RP-4," Adverse Condition Resolution Program" (for Millstone) 2.3 ACP 1.2-16.5," Adverse Condition Report Process Implementation" (for Connecticut Yankee) 2.4 NUC PI 1," Document Identification and Retrieval" 2.5 NUC PI 2," Unit-Specific Assessments" l 2.6 NUC PI 6, " Licensing Reviews" l
l 2.7 NUC PI 8," Plant Verification and Readiness Team" l l
l l
2.8 NUC PI 9, " Design Bases Documents" l
l 2.9 NUC PI 10," Configuration Management" i 2.10 NUC PI 13,"UFSAR Changes" i
2.11 NUC PI 14," Project Process Administration" 2.12 NUC PI 16," Licensing Basis and Design Basis Walkdowns" ,
l 3, COMMITMENTS l
None l
- 4.
SUMMARY
OF CHANGES 4.1 OriginalIssue l
l l
- 4 A I NUC PI 7 Level of Use Information
,ggr y 7 ,qg7.*M5T Rev. 0 pm33 399.s yg o ,s y%3 15 0f 28
' - Attachment 1 Documentation of System LB and DB (Sheet 1 of 4)
System or Topical Area:
System No. (if applicable):
i
! LB ' Document reviewed (documentation from NUC PI 6):
4 Appficability Determination and Reason (from step 1.3.2): !
- O Yes Q No Not Sure (White Paper required to determine applicability) i i
i i
4 Applicable Discipline (from step 1.3.4):
Prepared By: Date:
A A A 6 NUC PI 7 Level of Use .,qgg ,qg7 mg7ygg7 Rev.0 Information j y;.4 pg jtu;I /PQ 16 of 28
Attachment 1 Documentation of System LB and DB (Sheet 2of 4)
System or Topical Area:
System No. (if applicable):
NOTE If similar topics are being covered, multiple documents may be listed below.
I, LIST LB documents reviewed and group review results for each (step 1.3.5):
NOTE Attachment 2 attributes are used to help develop the DB.
II. LIST DB from assigned System LB (step 1.4.1 and step 1.4.2) and IDENTIFY each DB as a system, component, structure, or support:
Prepared By: Date:
6 i A & NUC PI 7 Level Of Use a , , A r 'TbHK m .. " . . . sACT
. . .' REVIEW.. Rev.0
STOP '
gnformat.lOn gp?. p,i 'pp jp3 17 of 28
Attachment 1 Documentation of System LB and DB l (Sheet 3 of 4) l System or Topical Area:
System No. (if applicable):
III.' LIST documentation from NUC PI 1 or other sources that supports DB identified in Section II of Attachment 1 (step 1.4.6):
Document Remarks
. . DB l
l IDENTIFY below any new DB added to Section III and any DB from Section II which has been modified as a result of the NUC PI 1 review (step 1.4.7):
t 1
1 Prepared By: Date:
/ ^ ^
NUC PI 7 Level of Use . .
gg y ,, r ,g7 yggy. Rev. 0 Information jg- p j; :i f4 . ,
18 of 28
Attachment 1 Documentation of System LB and DB (Sheet 4 of 4) .
System or Topical Area: __
System No. (if applicable):
IV. ATTACH the following:
= NUC PI 16 walkdown checklists (step 1.6.1)
- NUC PI 8 requests and results (where applicable) (step 1.6.2)
IV.A. DOCUMENT any additions or modifications to the DB noted in Section III of this Attachment (step 1.6.4):
r IV.B. DOCUMENT additional information from NUC PI 1 or NUC PI 6 which affects the System LB or DB (step 1.6.6):
Prepared By: Date:
A A A ta NUC PI 7 Level of Use ,ggggpr ,qggr sqqp vggg7 g,y,g Information jpg p;q psq pa( 19 0f 28
. . . .=
Attachment 2 Typical Attributes to Determine DB
[
(Sheet 1 of 4)
The following is alist of typical design attributes and controlling design parameters that could form the Design Basis:
Electrical ,
1
- Diesel Generator sizing
- Safety-related power cable sizing 6afety-related system voltage profile l
I
- Safety-related system short circuit analysis
- Diesel generator performance
- Safety-related bus transfer analysis e 480V MCC and switchgear protection and coordination l
- Class 1E battery sizing
- Uninterruptible power supply sizing
- Low voltage and DC cable sizing !
l
- Class 1E AC/DC system protection and coordination i i
l = Safety-related instrument setpoint and accuracy calculations
= Controlloop response time calculations fi l l
- Electrical separation analysis
- Raceway fill and loading
(
Nuclear j
- Control Room toxic gas l
. l
- Tornado loadings and external missiles
- External flooding effects
- Pipe break effects (pressure, temperature, flooding, rupture)
- Equipment environmental qualification (harsh and mild environments) a Systems required to mitigate design bases accidents (DBAs)
= Radiation source terms for DBAs i
- Containment analytical mode; I
- Post-accident conditions
- Offsite dose analys" for normal operation and DBAs l
1.
- A 4 NUC PI 7 Level of Use , q j g y y g g ,q g'Ay,7g7 Rev. 0 lnformatlon jpgq jpg ppq pygsg 20 of 28
Attachment 2 Typical Attributes to Determine DB (Sheet 2 of 4) i Nuclear (Continued)
- Control Room shielding and operator doses
- Personnel radiation doses during DBA recovery activities
- Airborne radioactivity transport from a fuel handling DBA
- Loss of Spent Fuel Pool cooling
" Ultimate heat sink capacity analysis
- Control Room habitability during blackout (air temperature)
- Pipe break discharge flow l
- Secondary containment air pressure control analysis l
- Heat load determination analysis
- Heating, ventilation, and air conditioning (HVAC) system failure modes and effects analysis
- HVAC instrumentation setpoints
- Control Room enclosure air infiltration l
f
- Battery compartment hydrogen accumulation 1
(
- HVAC design analysis
- Reactor transient analytical models
- Reactor Coolant System transient analysis
- Pipe flow hydrodynamic loads analysis
- Piping network dynamic flow analysis ,
- Valve operability analysis l
- AShE Code of record calculations
- Computer code certification documents
- Thermal analysis of components, supports, and structures
- Component minimum wall thickness calculations
! A A i NUC PI 7 Level of Use ,egjggxyppymy[sp~yyggf nev, o Information jpg JP% f( r3 21 of 28
.~-.a. ..w--_.- .a a- - -n.-.-..,a-~.u- - o ..a- s. a , - -- - - <-.a.- -- ..- . .- . - . .-
1 l
Attachment 2 Typical Attributes to Determine DB i (Sheet 3 of 4) l Civil f . Category I reinforced concrete structures analysis
! . Category I steel structures analysis
- Civil structure dynamic / earthquake analysis l
- Dynamic / stress analysis of substructures
- ~ tynamic/ stress analysis of containment nozzles, etc.
i
. Tornado analysis of structures
- Category I weld evaluations
- Category structure block walls
- Component seismic / structural qualification
- Pipe rupture restraints
. Bolt anchorage in Category I structures
- Probable maximum flood analysis
- Platform steel, cranes, monorails, doors, ladders
- Heavy loads analysis i
- Category I piping analysis
- Seismic analysis of electrical conduit ,
- Instrument line analysis
- Category 1 supports (pipe, duct conduit, tray and instrumentation, and NSSS supports) 1
- Penetration qualification
. Earthquake ground motions a Category I foundation analysis l
)
i l@
A A NUC PI 7 i Level of Use , g g y Q ? g ,- y g!g.,RNM Rev. O Information jpg jp:q pp 4 jp, *( 22 of 28
~
Attachment 2 !
1 i
Typical Attributes to Determine DB (Sheet 4 of 4)
Mechanical
= Piping minimum wall thickness )
- Pump net positive suction
+ Pump total system head
. Valve pressure drops (Cv)
.~ " Tank nozzle / branch line reinforcement
- Heat transfer (sizing of heat exchangers, condensers, heaters, etc.)
- Pump! system performance
. Pressure / vacuum relief valve sizing
. Sump capacity
. Cooling water flow rates
- Equipment performance calculations
- Corrosion / erosion allowances
- Tanks (volume, wall thickness, etc.)
- Pipe sizing / flow 6,
- System design / operating pressures and temperatures
= Pump brake-horsepower requirements
- Valve actuation times and check valve closure Instrumentation and Controls
- Safety-related instrument range and span
- Safety-related instrument setpoint and uncertainty calculations
- EMI/RFI analysis
- Instrument time
- Safety-related to nonsafety-related equipment isolation
- Safety train separation A 4 A 4 NUC PI 7 Level of Use jg, Q, 'MMYSGT Rev.o Information gp;g g;qsr
,p q% Vg' g< r s , 23 of 28
Attachment 3 System LB and DB Package I (Sheet 1 of 1)
! Cover Sheet 1
System or Topical Area:
System No. (if applicable):
SRT Leader:
J SRT Member Discipline l
[
1
! l l
l 1
Package contains the following (CHECK applicable colurnn):
Description Yes No Attachment 4, System Review Matrix J All Attachment 1information, including: $$$j((@y j
- a. Verified and Validated System LB l 1
- b. Verified and Validated Component, Structure, and System DB ,
- c. Verified and Validated System or Components required to support the DB
- d. Description of supporting design information that has been reviewed
- e. Documentation of NUC PI 8 and NUC PI 16 results related to LB and DB issues Reviewed By DEL: Date: )
l Approved By UPM: Date:
l
- ?
h NUC PI 7 Level of Use .,s.-...,' .A-me 'VACT ,"..
v'THINK'
- w ,-
' REVIEW Rev. O
'STOP nformat. ion % y 74 ;c 24 of 28 i
m Atta .sent 4 ,
System Review Matrix 1
(Sheet 1 of 2) ,
System or'Ibpical Area: System No. (if applicable):
Desi tn Basis Consistency License Basis Consistency Ptant Documentation Agreement 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 Design Basis 1 2 l I 1 I l l l l l l l l l 1 1 I I I I I I I I l l l Prepared By: Date:
Reviewed By- Date:
Apploved By DEL: Date:
Column Codes:
1 - Performance Reqmts 6 - Equipment Certs 11 - Drawings 16 - PDCRs 21 - NRC Insp Findings 26 - Tbch Reqmts Manual 2 - Regulatory Reqmts 7 - Safety Analysis 12 - Specifications 17 - Other
- 22 - GLs, ins, IE Bull's . . 27 - Tbmporary Mods 3 - Codes 8 - Stress Reports 13 - System Description 18 - FSAR 23 - Other
- 28 - Walkdowns 4 - Standards 9 - Vendor Information 14 - DBDPs 19 - Tech Specs 24 - Procedures 29 - Tbch Specs 5 - Calculations 10 - Evaluations 15 - Equipment list 20 - License Commitments 25 - Sury. Tests & Insp*s 30 - Other *
- If"Other" box is used, IDENTIFY document reviewed or function performed.
' 5 NUC PI 7 Level of Use .,
"STOP'
, m i . y'.
'THINK
,,,g ACT
- , _ : . . ~
' REVIEW Rev 0 Information 25 0f 28 4 ,, , .,
r -
e b _
m
_ u 7 N I P 8 _
y O 2f c -
n C .
a p Uvo e6 e
r c
NR2 _
i s
D .
r _
e
. b _
m _
u N
_ y c
n a
p e
r c
s ,
i
_W D E d AaIV-e _E
- ,R-t .
a i
x i c
r o s
-)
t s , 4 a a T 4 k C:,A: "--
t M) n wf2 ht e
, f e eo , "6^
d
- n. vt i 2 n ,
. e ee t a .
K RhS n _
e :
e e 3lyp Am._Nq _
A em(
t t
m t a
t a Tj h .' _
t s
c a e D D _
y t u ,
t s S s A I n
m,P' i
ht s e p [O.T O "
f o mS 1
t e
e h
S n
o d
i e
f i
t n
e
) d i
- l e e a b u e
r a s -
c s A i l
p i
n en l
i a
c p
a e
p o :
so Ui t -
p f i
y y f a Tr o (
o h
c a
B B d lomr -
o N T
e d e
r e
w eo vf m
e m
e S
I .
a p i e
v en Ll t
s t
s L e r e -
y y . P R S S I
Atti .nent 5 System Review Process (Sheet I of 2)
OBJECrlVES g
+ Determine LB and DB for system as identified in CMP.
- Filter and sort NUC PI 1 information in order to facilitate performance of NUC PI 9 (DBD) and NUC PI 13 (UFSAR).
- Review appropriate design data to ensure the system meets DB requirements.
DEL S]E SYS/FOPIC DEL Sys/ropic Lead : LB
---> Establish make-up ---> NameSRT > Review unit LB and determine Assign Sys/ i Members. I applicability to Sys/Ibpic LB. DETERMINED Topic Lead of SRT.
I Document results.
I Refer'Ib NUC PI 14 for guidance NUC PI 6 g w/ discrepancies during this process. Jl Provide uni! LB.
4 UPM -
SEI __, SIE - Determine: .
SIE 4 Sys/ Top DB Screen & filter
. Establish communication between SRT. Component DB --> NUC PI 1 info. reviewed and depth of review.
+ Identify handoffsbetween disciplines. . Structure DB Identify NUC PI 2 issues.
. Ehmmate duplication of efforts. System / Components req'd to meet DB UC PI 1 Provide appropriate sys design data. >
SIE -
Review designated NUC PI 1 info. "
Sheet 2 +- . Review any applicable NUC PI 2-generated issues.
+ Ensure data supports DB.
A NUC PI 7 eeo se _g , v r< ;f Rev. 0
Att: .ent 5 System Review Process (Sheet 2of 2) .
- Self-assessment
- ' ---- E I*
- stee 1 t-SYSTEM OR SEE SEE - Complete SEE - Complete
- review and evaluation 1 ,
TOPICAL > Validation > System Review Matrtx.
AREA DB Process 3 oflicense commitments
" " for system against DB.
DETERMINED RESULTN 3r REQWTs REQUESTS SRT Lead -
3r 3r = Recommend open issues to be NUC PI 8 NUC PI 16 NUC PI 6 and NUC PI 1 - closed prior to completion of this Pl.
Review DB to Review DB to plant Identify any additional
- Ensure all open issues are tracked.
plant processes. configuration. documentation generated by these PIs ir del,- Ensure the following:
UPM - Attachment 4 is complete.
SRT I ead -
- Review and approve System Package.
Prepare LB and DB p = All open issues required to be closed pior a Ensure System Package is availatte as to completion of this PI are identified, System Package and a OA document for implementation submit to UPM- = Open issues can be closed.
of NUC PI 9 and NUC PI 13. . Open issues are tracked.
Y b
- NUC PI 7 Levelof Use ..
.3, A s A. . _._
7.< . m,.,,. ,MACT)y.,_4.._,, Rev.0
~g_$ TOP ' ' REVIEW Informat, ion TH!NK^ ~~
28 of 28 l"Q h *~.
, m' 4
4 [ ::.
~:a S(;;
n *
- NORTHEAST UTILITIES NUCLEAR' % CY -
NU COMMON PROCEDURE .. '3 UP 1 97 9-e[ ;a as
, ' m rc; l -
'~~~ % $eb V
eyc?.: ,
'A ,
9.49 < tx.ti %wwyggmemnmm m www
- b:l* m-usnewwwy&l' l.$::s ...:.: p,
- " +-
n[.
ik nx, s. ,, e . , ,a. n #..f7 ,
'q *kqir uniyl"HINKi3%%WRiiy*E"%EEV ~
q *$.$,ar OP 4 'GT EVIEW m 2yw -
. m: ... 3 .,e . ,*4
- $tb @ k ~ L ssd@%
pljgft%~~g4,pry 44 yW$%z ) g, 6g4
.t :-
- y. a
.~
x ... v Plant Vefificiition and Readiiless Team .
NUC PI 8 Rev.O is part of im This ProjectManagement Configuration Instruction (PI) Plan (CMP)plementation of the l
Millstone p4h 3 $0nnecticut Yankee SoRC. Mtg. No.: k$'8k PORC. Mtg. No.:
Date: 8' O b'N Date-I Effective Date:
Responsible Individual:
Level of Use . D. Reed Information Subject Matter Expert:
ci-,
Tv wo U5vu 3 9
(%[ 7 D. Reed.
MP1, MP2, MP3, CY -
,i NU Common Procedure l Plant Verification and Readitiess Team TABLE OF CONTENTS
- 1. . , IN STRU CTI O N S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1 Te am Make up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 i Team Reviews Using ACCESS Database . . . . . . . . . . ......... 5 1.2 l
1.3 Review of Existing Operational Controls Using ACCESS Database 6 1.4 Design Engineering Activities Using ACCESS Database . . . . . . . . 9 l
1.5 System Record Disposition Using ACCESS Database . . . . . . . . . 10 1.6 Team Reviews Using Hardcopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 l
1.7 Review of Existing Operational Controls Using Hardcopy . . . . . . 13 l 1.8 Design Engineering Activities Using Hardcopy . . . . . . . . . . . . . . . 14 l
1.9 System Record Disposition Using Hardcopy . . . . . . . . . . . . . . . 15 REFERE N CES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 2.
CO MMITMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 3.
1
SUMMARY
OF CHANGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 4.
l <
ATI'ACHMENTS AND FORMS 1 Attachment 1, " Plant Verification and Readiness Team Review Process Flow Chart" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 i
- A A A & NUC PI 8
- Level of Use ,JL-rmA "STOP" ~THINW
- ,%, ACT' Aim'REVfEW ,A ,. Rev. O gnformat. ion jgg jpg jf44 j;ag 1 gg 17
- 1. INSTRUCTIONS _
This Project Instruction provides details for the Operations Plant Verification and Readiness Team (PVRT) evaluation of the adequacy of existing operational controls (programs and procedures) with respect to the Licensing Basis (LB) and Design Bases (DB) of the unit.
Each Unit Project Manager (UPM) has the authority to decide the vehicle used for documenting and maintaining LB and DB information for the unit in accordance with NUC PI 14," Project Process Administration." It is acceptable to use either one or a combination of the following documentation vehicles on the unit:
- ACCESS database method - The ACCESS database developed for this project is a QA database controlled by Northeast Utilities (NU). This database is subject to quality requirements, including complete documentation and a Verification and Validation process.- Software security exists such that when a record is entered, it cannot be mcdified without management approval.
- Hardcopy method - Based on the scope and level of detail required for an individual unit, the UPM may decide to use a hardcopy method for documenting the LB and DB, and for tying operational controls to the LB and DB.
s d A A d NUC P18 Level of Use a- a "STOP>y.
_m y A7 .,gAiACT>y THINK ,'x REVieN Rev.O gnformat. ion jg7 'gg jp jpa0 2 of 17
1.1 Team Makeup -
NOTE Step 1.1.1 delineates PVRT membership. Names in boldface type ar,e mandatory members, who may act as chairperson for the review session.
denotes mandatory members who may not act as An asteriskA(*)ll other titles are optional members.
chairperson.
" 1.1.1 ASSEMBLE a PVRT consisting of the following UnitProje t Manager
- Two Operations personnel from the following options:
- Two with a current SRO-license on the specific unit
- One Shift Manager / Unit Supenisor (SM/US) and one previously-licensed SRO with greater than 18 months of unit-specific Operations experience
- One Shift Manager / Unit Supenisor (SM/US) and any other person authorized by the UPM
. One I&C representative
- One Maintenance representative l
- One Generation Test representative
. One responsible System Engineer *
- Responsible Design Engineering Lead *
- One NSSS site vendor representative
. One representative with both Engineering and Operations background (such as Unit STA)
. One Operations Training Representative i A I A NUC PI 8 Level of Use .ygpr sgr mgr.ggy7 .Rev.0 Information 4 g; peg j.?.g 3 gg 17
~
NOTE l It is acceptable to use eith'er one or a combination of documentation l vehicles on any unit.
1.1.2 SELECT documentation vehicle to be used and DOCUNENT decision in project file.
~- 1.1.3 Go To applicable section:
- IE design information for review by PVRT has been entered into ACCESS database: Section 1.2
- IE design information for review by PVRT consists of hardcopy records: Section 1.6 i
s I
i
~
l l
u A A A NUC PI 8 Level of Use ,c g 7 g g 7 sq g 7 'K N E07 Rev.0 Information j g ;. jgy pd f% i 4 of 17
1 1.2 Team Reviews Uting ACCESS Database i
~
NOTE l
- 1. Section 1.2 through Section 1.5 of this PI utilize the ACCESS database. Reviews and actions are documented in the appropriate fields unless otherwise noted.
- 2. A system design entry consisting of a single sentence which does not identify the system component (design review item) being discussed is
~
not acceptabfe.
" 1.2.1 PROVIDE system LB or DB requirements using the ACCESS Design Engineering database " System Description" fields as follows:
- VERIFY each entry (paragraph or sentence) contains sufficient detail to ensure the following:
- Design review item is readily identifiable.
. Any assumptions (such as valve or switch lineup, operating bounds, etc.) are clearly noted.
- VERIFY LB or DB requirements that require operational controls are clearly identified. Examples:
. IDENTIFY differences in component applications, such as an alarm that provides component protection vs. one that is relied on to meet LB or DB requirements.
- SPECIFY that a piece of equipment is expected to be operated in a certain way, NOTE .
)
The Responsible Design Engineering Lead is an individual assigned by the Unit Design Engineermg Manager to coordinate activities for the CMP on ;
an assigned system.
l Chairperson 1.2.2 WHEN design information is ready for review, COORDINATE ,
l* ,
the responsible Design Engineering Lead (DEL) and System Engineer (SE) for a presentation to the PVRT.
f5 A A i NUC PI 8 Level of Use qg. NM "dhrME Rev.0 Information ,g y, p4pg, g.g x ,
RA e <
S of 17
3 i
I 1.2 Team Reviews Using ACCESS Database is ~
l NOTE 1
l 1. Section 1.2 through Section 1.5 of this PI utilize the ACCESS l
database. Reviews and actions are documented in the appropriate fields unless otherwise noted.
l
- 2. A system design entry consisting of a single sentence which does not
! identify the system component (design review item) being discussed is not acceptable, i
Design 1.2.1 PROVIDE system LB or DB requirements using the ACCESS Engineering database " System Description" fields as follows:
- VERIFY each entry (paragraph or sentence) contains sufficient detail to ensure the following:
. Design review item is readily identifiable.
. Any assumptions (such as valve or switch lineup, operating bounds, etc.) are clearly noted.
. VERIFY LB or DB requirements that require operational controls are clearly identified. Examples:
. IDENTIFY differences in component applications, such as an alarm that provides component proaction vs. one that is relied on to meet LB or DB requixements.
. SPECIFY that a piece of equipment is expected to be operated in a certain way.
1 I
NOTE , j The Responsible Design Engineering Lead is an individual assigned by the Unit Design Engineermg Manager to coordinate activities for the CMP on an assigned system.
1.2.2 WHEN design information is ready for review, COORDINATE l Chairperson l" the responsible Design Engineering Lead (DEL) and System Engineer (SE) for a presentation to the PVRT.
l l
^
! 2 i' A A & 8 NUC PI 8 I
Level of Use .g p-,' g.7'dNF Y Er Rev.0 Information ,g g gg. .,gg\ ,;;4r S of 17
,. , m
r -
t .
NOTE Examples of other operations-focused experts to be involved in team reviews include Chemistry, Health Physics, Emergency Planning, etc., as deemed necessary by the Chairperson.
I 1.2.3 Prior to convening a team review session, IDENTIFY any other operations-focused experts needed to aid in interpreting and investigating adequacy of existing operational controls, and REQUEST each group send a representative to the meeting.
1.2.4 WHEN team review session is convened, VERIFY at least the minimum team is present.
i 1.2.5 Using an LCD video projector or computer terminals, DISPLAY cach record for review and discussion by the PVRT.
1.2.6 Throughout the review process, using the " Discussion" field in
[pyrg f ACCESS database, RECORD key discussions and decisions relative to the item.
1.2.7 Refer To Attachment 1," Plant Verification and Readiness Team Review Process Flow Chart," and REVIEW record.
i l
A A ? NUC PI 8 l
Level of Use yfgp wggr sg!*7,gg. Rev. 0 Information 74 pq j;( / 6 cf 17 _
-r , . _ , , .
NOTE i
The term "DBVT" denote's a field in ACCESS database used by the Plant .
l Verification and Readiness Team. ,
1.2.8 PERFORM applicable action:
[ Chairperson f
- IE the record is determined to be a design statement of fact
- (no operational controls exist or are required), CHECK
" Closed" radio button under DBVT Status. No further review is required.
IE the record contains sufficient information such that a member of the PVRT can conduct research and determine the adequacy of operational practices, ASSIGN resolution to PVRT member and CHECK "Open" radio button under DBVT Status.
IE the record does not contain sufficient information such that a PVRT member can conduct research and determine the adequacy of operational practices, PERFORM the following:
l
. ROUTE record to Design Engineering for additional detail.
. CHECK "New" radio button under DBRT Status.
- IE the record does not reflect current operational practice or plant configuration, PERFORM the following:
- CHECK "New" radio button under DBRT Status.
. CHECK "Open" radio button under DBVT Status.
- DOCUMENT concern or question in " Discussion" field of ACCESS database, to be answered by Design Engineering.
~
A A A i NUC PI 8 Level of Use ,gpr ygg7 syg7,@;r Rey,o lnformation jpg pq jpg fpa 7 of 17
1.3 Review of Existing Operational Controls Using ACCESS Database - -
l
!. l
. >VRT f 1.3.1 WHEN assigned a record for review, PERFORM the following: i
- b. IE procedure reference exists, IDENTIFY and RECORD the following in ACCESS database for each reference:
" . Procedure Number i . Revision number reviewed
- Change number reviewed
- c. RECORD whether existing procedures adequately address the LB or DB requirement in the " Disposition" field of ACCESS database.
- d. JE operational reference does not exist .QR existing procedures -
do not adequately address the LB or DB requirement, IDENTIFY the need for procedure development or the recommended procedure or plant modification in the
" Discussion" field of ACCESS database.
! 1.3.2 WHEN assigned record review is complete, CHECK l
" Completed" box in ACCESS database.
l l
l l
l t
4 s 4 A A NUC PI 8 Level of Use
'Yr NNr 9#h"'8T Rev.0 lnformation j;q jq jq jpak 8 of 17
1.4 Design Engineering Activities Using ACCESS Database ,
NOTE The term "DBRT" denotes a field in ACCESS database used by the l Design Basis Review Team.
1.4.1 On a daily basis, RUN a " Query by Example" (QBE) of ACCESS .
l DEL l database for assigned systems to look for all "New" records in the l "DBRT" field.
1.4.2 For each new record found, PERFORM the following: I
- a. READ the specific question or comment identified by the PVRT in the " Discussion" field.
- b. ASSIGN a System Design Team member (SDTM) as the lead for answering the PVRT question or comment.
- c. ESTIMATE the number of man-hours to resolve the question and CHECK the appropriate "LOE" box in ACCESS database.
SDTM 1.4.3 DEVELOP response to each assigned record.
l*
1.4.4 WHEN response is complete, CHECK " Complete" box in ACCESS database.
1.4.5 IE record needs Operations verification, CHECK" Returned" i radio button under DBVT Status and CHECK the "Open" radio i button under DBRT Status.
. I l
t l 4 g i NUC PI 8 l Level of Use ,ggy wg%re sqgy,cgg7 gey, o Information fdh pM( [ pg 9 of 17 t
1.5 System Record Disposition Using ACCESS Database t*
1.5.1 WHEN PVRT and Design Team work is complete for all records
/ vat Lead .I associated with a given system, PERFORM the following:
i
- a. I'ERFORM a cursory review of system records for completeness and detail.
- b. VERIFY system is ready for discussion by PVRT.
s 4*
- c. SCHEDULE a system acceptance presentation meeting with the PVRT, DEL, and SE.
1.5.2 REVIEW each record in ACCESS database for system under lPVRT }"
review.
1.5.3 DEVELOP the final team disposition for each record and DOCUMENT in the " Disposition" field.
NOTE System disposition requires closure of all Log Number Items associated with a System / Program Number, 1.5.4 WHEN system is dispositioned AND the disposition is acceptable to the PVRT, NOTIFY the Unit Project Manager.
l l
l i
Level of Use ,.y 7 y.7 7 ,.c r .'
57' 0 Information peg {4 jp6 M4 10 of 17
__ 34 1.6 Team Reviews Using Hardcopy _
NOTE
, A system design entry consisting of a single sentence which does not identify the system component (design review item) being discussed is not acceptable.
" 1.6.1 PROVIDE system LB or DB requirements as follows:
Design Engineering
- VERIFY each entry (paragraph or sentence) contains sufficient detail to ensure the following:
. Design review item is readily identifiable. l l
. Any assumptions (such as valve or switch lineup, l operating bounds, etc.) are clearly noted. ;
. Reference can be made to the location of the LB or DB requirement in the document (such as page number, section number, step number, etc.)
- VERIFY LB or DB requirements that require operational controls are clearly identified. Examples:
. IDENTIFY differences in component applications, such as an alarm that provides component protection vs. one that is relied on to meet LB or DB requirements.
. SPECIFY that a piece of equipment is expected to be operated in a certain way.
. ASSIGN a unique ID number to each record and MAINTAIN log.
j" 1.6.2 WHEN design information is ready for review, COORDINATE l Chairperson the responsible Design Engineering Lead (DEL) and System Engineer (SE) for a presentation to the PVRT.
^ $ NUC PI 8
~
$/ A Level of Use ,qggy yg7 og7 ggg Rev.0 pq
^
Information ,p 4, , , , N., e t 110g 17
I NOTE !
~
i Examples of other operations-focused experts to be involved in team '
reviews include Chemistry, Health Physics, Emergency Planning, etc., as
- deemed necessary by the Chairperson.
1.6.3 Prior to convening a team review session, IDENTIFY any other operations-focused experts needed to aid in interpreting and investigating adequacy of existing operational controls, and REQUEST each group send a representative to the meeting.
1.6.4 )VHEN team review sessio'n is convened, VERIFY at least the
, minimum team is present.
1.6.5 PROVIDE sufficient hardcopies of each record to PVRT l DEL or SE l" members for review and discussion.
1.6.6 Throughout the review process, RECORD key discussions and lPVRT l" decisions relative to the item.
1.6.7 Refer To Attachment 1," Plant Verification and Readiness Team l Review Process Flow Chart," and REVIEW record.
l l
1.6.8 PERFORM applicable action:
l cnairperson F
- IE the record is determined to be a design statement of fact, i STATE "No operational controls exist or are required." No l
further review is required.
IE the record contains sufficient information such that a member of the PVRT can conduct research and determine the adequacy of operational practices, ASSIGN resolution to PVRT member and DOCUMENT name of PVRT member.
IE the record does not contain sufficient information such th PVRT member can conduct research and determine the adequacy of operational practices, PERFORM the following:
. ROUTE record to Design Engineering for additional detail.
- IDENTIFY problem or concern.
- IE the record does not reflect current operational practice or plant configuration, DOCUMENT concern or question, to be answered by Design Engineering.
.i .
& A 4 A NUC PI 8 i Level of Use *STOP"A '*THIN _ A ,K' *4ACT'L ' REVIEW Rev. O nformatiOn p% jfpsat ' 12 of 17 jgu$
- - -- - - . _ . - - ~ - _
i 1.7 Review of Existing Operational Controls Using Hardcopy 1.7.1 WHEN assigned a record for review, PERFORM the following:
'.kVRT f
- a. DETERMINE whether one or more specific procedures exist l that address the LB or DB requirement. l
- b. IE procedure reference exists, IDENTIFY and RECORD the following for each reference:
. Procedure Number
. Title l i
+ Revision number reviewed l
- Change number reviewed RECORD whether existing procedures adequately address l c.
1.7.2 IE operational reference does not exist OR existing procedures do not adequately address the LB or DB requirement, PERFORM the following:
- a. IDENTIFY the need for procedure development or RECOMMEND procedure or plant modification using the Project discrepancy database addressed in NUC PI 14,
" Project Process Administration."
NOTE Procedure change, new procedure, or plant design change must be either complete or dispositioned prior to a complete system review by the PVRT.
- b. IE procedure change or new procedure is required, VERIFY change or new procedure is completed.
- c. IE plant modification is required, VERIFY Engineering and RAC review and disposition are completed.
1.7.3 WHEN assigned record review is complete, INITIAL document and ROUTE to the PVRT Lead. .
t A 4 NUC PI 8 Level of Use A fi Rev.O N hf[ ENYllEII/'
lnformation F[% #N M %Sdf PN 13 of 17
1 I
l 1.8 Design Engineering Activities Using Hardcopy - l 1.8.1 On a daily basis, CONTACT PVRT Lead and OBTAIN any new
-i OEL l" records for review.
1.8.2 For each new record, PERFORM the following:
- a. READ the specific question or comment identified by the j
PVRT. l
-s
- b. ASSIGN a System Design Team member (SDTM) as the lead f for answering the PVRT question or comment.
1.8.3 DEVELOP response to each assigned record and DOCUMENT.
{ soTM l" I 1.8.4 WHEN response is complete, INITIAL document and ROUTE to the DEL.
1.8.5 REVIEW response and PERFORM applicable action:
[ DEL l"
. IE response is acceptable, SIGN record.
- IE response is not acceptable, INITIAL record and RETURN to originating SDTM.
l 2
A' A 4 NUC PI 8 Level of Use .gpr ,g7 se rw@dg7 Rev.0 lnformation jp:4 jpg pp jp%s 14 of 17 I
- 1.9 - System Record Disposition Using Hardcopy 1.9.1 WHEN PVRT and Design Team work is complete for all records i PVRT Lead l" associated with a given system, PERFORM the following
- a. PERFORM a cursory review of system records for completeness and detail,
- b. VERIFY system is ready for discussion by PVRT.
~-
- c. SCHEDULE a system acceptance presentation meeting with the PVRT, DEL, and SE.
- d. VERIFY unique ID numbers for records match log index maintained by Design Engineering.
1.9.2 REVIEW each record for system under review.
l PVRT f 1.9.3 DEVELOP the final team disposition for each record and DOCUNENT.
1.9.4 RECORD minutes of meeting for system disposition.
1.9.5 WHEN system is dispositioned AND the disposition is acceptable to the PVRT, NOTIFY the Unit Project Manager.
l
' A A A 7 ysA, d k s-.
NUC PI 8 Level of Use 'STOP"A# e'THINK WACP 'R EVIEW Rev.O nformat. ion jjgg g jgnh /P 15 of 17
[ l i; .
', 2. REFERENCES 2.1 Configuration Management Plan (CMP) 2.2 RP-4," Adverse Condition Resolution Program" (for Millstone) 2.3 ACP 1.2-16.5," Adverse Condition Report Process Implementation" (for Connecticut Yankee) l
' -' 2.4 NUC PI 14," Project Process Administration"
- 3. COMMITMENTS None
- 4.
SUMMARY
OF CHANGES 1
4.1 OriginalIssue
\
l I
i i
Jg 'A NUC PI 8 I 4 f3 Level of Use I
,fgyr wrygr wqqpr'$p7' Rev.O 16 of 17 Information jpmig pPQ [#44g JP**4; I
l
Attachment 1 P'lant Verification and Readiness Team Review Process Flow Chart (Sheet 1 of 1) t Engineering PVRT No or Potential Needs UFSAR tem correct Verification ANNOTATE Ye NOTE item ENTER DB item & per current ' discrepancy, change FORWARD to PVRT for .- F . status, OPS concern, or question orOPS initial review. d 6 practice 7 in " Discussion." impact? go k JL No Yes RP
- . Yes m
PROVIDE input (proposed UFSAR rewrite, PVRT procedure concern j
, associated 9P change, e tc.).
with Kr 9P issue? NOTE item status y
" Closed" jg for PVRT.
NOTE item status "Open" 'I for PVRT.
NOTE dispositionin ASSIGN item to
" Disposition" section ResolutionTeam and RECORD vote. (gr),
P Jw No or Needs Surveillance
( Verificatioor testing adequate?
l Yes wr N
~
\oN RESEARCHto determine appropriate surveillance or Resolution l OBTAIN spplicable procedures. complete testing to assure component readiness to
'l NOTE action in " Discussion- (unanirnous F section.IDEN11FY procedure in fulfill safery function. PVRT vote
" Procedure'section.
NOTE action in
' Discussion" section.
IDENTIFY procedure in j 7
" Procedure" section.
INITIATE revision or change MP to procedures as needed. Ready NOTE disposition in
" Disposition" section, s for
' MOC l l and CLOSE item r
'*d**
DETERMINE finaldisposition.9>
I l
b RETURN item for PVRr review.
1 J
1 4 5 e NUC PI 8 i
a- e-Level Of Use -. A y' v'.a _ ~NACT' v5 TOP THINK' ~' REVIEW Rev.0 nformat,On \
j; yp [" Jl 3y 97 gy
4.m.se.w.-a---aaaam- -s w ,.ma. -a we m - m--4--aa . . - -.== ,.a so e m m .a i
l PI9 DESIGN BASIS DOCUMENTS lATER
7 O
I 5
a 58 m$,
f%.
sp NORTHEAST UTIIJTIES NUCLEARM % CY n -
NA; gf2-PROJECT INSTRUCTION ffhh.n. hhik
- [g
- b'dkliM5 P4 '^
!$if@2&;;jQy{i:@fi!M' d{$a%m 36$ ,,>m
}
- 'IS- $0 X- .
Is.. /M. .
m::;g'Y/ W' 'L' ,',hffb' w,>.s p l . %r :<' y{yggg'/*gh--gQ:-s .
g"c *qf>r ...
q{';pnesp&w4yj- % :gj :gy ;p>MSN:4
- kv.;<sYs@25% .is. p'dfib
n:04 d
%g$:>Mu se:w 'T*be,o A *7!Cr dr&
t m&r
??
qq 9 _
y~
Qghfh$b*
- -54A %meyggpe m .
ne your. . ,,s am%eeuen sgenes emmudwenemmun.
_Ey" .' &m
% ::1CW:)g% }4k.k:,
fi Con.1;$dtLf_f' up.gura non Man.m,..agement s,mg g
fis#yg>-NUC PI 10 9*4%
Rev.O f
~
This ProjectManagement Configuration Instruction (PI) Plan (CMP).is part ofimplementation of the t
A royal Effective
. . ; , . ,' 0 Mtg. No. ate Date Millstone SORC f-f f g-g-ff g jg.pf CY PORC ;
Responsible Individual:
Level of Use B. Cox Information ,n>-i wo w~ m~ >>-f9/P Subj.ect Matter Expert:
B. Cox
Documentation of Training Requirements [comm a.2) r (Sheet 1 of 1) bSection
%. :..s w o1m oA..,:a
. Doi:ume~nt'inforniationWWMWWC=s w w. m e, - a s s G4 % uc h d m e x A m a m m c %k WMw
- w
& m a^;b.;;;gd;;s 1
O Document Number: N1 o c_ T#Tm Revision No. Change No. _; -
1 Document
Title:
wm;a MTr - w p uaan USi6tl6n"2.ani.in!6fC66sidifit!6Hsj;yu%$$n$aw!is5MMM.,,:;9WipBEEE EE ma, ysgym "M k Requirements of TQ-1," Training and Quali5 cation"
$' Knowledge level of personnel performing procedure VPrevious training of personnel performing procedure
/
Quali5 cation of personnel performing procedure l 1
" Procedure Level of Use Difficulty of procedure or task L ' Consequence of incorrect procedure performance
/ Advice of Nuclear Training Department f Name of person contacted at Training Departroent: qC C'Q Cl, g(,
Required for new documents and revuions only
-:.....g. exy .n- e .m. ~.,. r~. , . .u o, ag.y.g .
- g. , , ,
- Sectio n. 3.....~ ,. am 4 y.Ng @.q.
- b. %;yJe$f h e y T.2ws,W,is,d i,-**
3Tr.aining wh or F.uuu,iliariz,atio,n'Requirsments
.u.u.w. .m w.ea s di &ggy.,.m E =mh m a amm:-
Training to be done by Nuclear Training before effective date.
l 8 Training to be done by Department or Nuclear Training Department within 60 days of Effective Date and prior to performance of procedure.
Familiarization required Methods to Provide Familiarization:
prior to Effective Date. . Department meeting Familiarization required, no a Pre-shift briefing impact on Effective Date. .
Pre-work briefing No familiarization or . Document Acknowledgernent Sheet training required.
l - _ _ _ _ _ _ - _ _ _ _ _ _ - - _ _ - - - - - - - - - - - - - - - - - - - - - - - - - - -
Target Group Requiring Training or Familiarization: Enter information pertaining to who requires training or familiarization, which parts of the procedure are applicable, special instructions, etc.
! I 8
i _ _____ __ ______________ ._ ____.
' Approved By: b&- ; M Yb -
/
Department Head or Responsible Individual date d , g'THINK',d
-v._ k ns -< $
,NACT*
.,n-DC 1 Attachment 5 y ~OP' ST 'REV!Ew Rev. 4 k 04 Of 09
l 1' MP1, MP2, MP3, CY NU Common Procedure l
Configuration Management -
i i
l t
! TABLE OF CONTENTS 1
l 1. INSTRU CTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1*
Q uality Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1
1.2 Training Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 1.3 Instructions for Phase 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.4 Instructions for Program Continuation (Phase 2) . . . . . . . . . . . . . . 5 l
! 1.5 Revi e w s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.6 Discrep ancie s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1.7 Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 1.8 Monitoring and Reporting Short-Term Performance . . . . . . . . . . 13 l
- 2. REFE REN CES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 j l 3. CO MMITMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 l r ,-
i
\
- 4.
SUMMARY
OF CHANGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 l l
ATTACHMENTS AND FORMS l
l Attachment 1, " Configuration Management Model" . . . . . . . . . . . . . . . . . 15 Attachment 2, " Configuration Management Review Report" . . . . . . . . . . 16 I l Attachment 3, "D efinitions" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 1
i I
l l
l l
l l
4 A A A 4 NUC PI 10 Level of Use _ht- .A, fL_ e.-
.* STOP" 'THINK ' ' TACT # "REV!EW Rev. 0 t Informat, ion uc - ny c:r. sw age y s,s y .g y3 pq 1 of 17 I
- 1. INSTRUCTIONS l
This Project Instruction provides a consistent approach for review and evaluation of programs, processes, and procedures that ensure configuration control.
l l
l This PIis used to:
Develop a list of programs, processes, and procedures to be evaluated l
l
- Evaluate the adequacy of programs, processes, and procedures.
Report evaluation results and recommendations for improvement.
- Provide a means of tracking those recommendations.
l l
l l
t l
l I
l l
i 2
l -
l A A A / NUC PI 10 Level of Use _.A.
"STOP' y' THINK'm - ,, w ,REMEW "ACT- . c a- Rev.O nformat. ion jp ju ig jp*% jP4 2 of 17 a____. . _ . -
1.1 Quality Requirements l CM Manager j 1.1.1 ENSURE the following:
The Designated Reviewer (DR)is familiar with the specific program, process, or procedure being evaluated.
Program, process, or procedure improvements recommended as a result of PI implementation are accomplished using an approved change control process.
1.2 Training Requirements l CM Manager l 1.2.1 ENSURE all personnel involved in implementing this PI are:
. Trained in Configuration Management Goals in NGP 3.2,
" Configuration Management."
. Trained in use of the five-box Configuration Management Model presented in Attachment 1.
. Familiar with NUREG 1397, "An Assessment of Design Control Practices and Design Reconstitution Programs in the
,( Nuclear Power Industry."
. Familiar with NUMARC 90-12, " Design Basis Program Guidelines"
~
1 A A A NUC PI 10 Level of Use ,q h 'c N ' "9$$F T d W7 Rev.0 Information pq pq jN gm3( 3 of 17
d 4
1.3 Instructions for Phase 1 configuration 1.3.1 SELECT those programs, processes, and procedures that support Management the safe operation of the plant for review during completion of Team (CMD Phase 1 of the CMP.
1.3.2 EVALUATE and LIST those NRC inspection items and results from NUC PI 2, " Unit-Specific Assessments," which involve CM issues.
1.3.3 IE an NRC inspection item or root cause analysis item is not readily identifiable to an existing program, process, or procedure, LIST the item under " Unidentified Programs, Processes, or Procedures."
1.3.4 EVALUATE list and DETERMINE the following:
Which existing programs, processes, or procedures require review for potential CM control weaknesses.
What new programs, processes, or procedures are required to address items identified under " Unidentified Programs, Processes, or Procedures."
(
1.3.5 Go To Section 1.5 for Phase 1 continuation.
A A A A NUC PI 10 Level of Use ,ggg, x74j7 ,q7pg77gg97 Rev. 0 Information gq pq( pq gqq 4 of 17
i 1 1
9 1.4 Instructions for Program Continuation (Phase 2) -
lCMT l 1.4.1 OBTAIN a comprehensive list of all programs, processes, and i procedures for each department from Nuclear Document Services.
1.4.2 SELECT those additional programs, processes, and procedures for review during completion of Phase 2 of the CMP.
1.4.3 DETERMINE whether all programs, processes, and procedures l needed to meet the requirements of 10 CFR 50 Appendix B are L
listed as follows: i 1
- a. IDENTIFY the processes needed to meet the requirements of 10 CFR 50 Appendix B.
- b. IDENTIFY and LIST corresponding Nuclear Group procedures that produce outputs using Appendix C of the NU Quality Assurance Program.
1.4.4 EVALUATE the list and DETERMINE the following:
- Which existing programs, processes, or procedures require review for potential weaknesses.
~
- What new programs, processes, or procedures are required to address items identified under " Unidentified Programs, Processes, or Procedures."
1.4.5 Go To Section 1.5 for Phase 2 continuation.
L l
& A h. A mu-NUC PI 10 Level of Use e,'
'STOP v4-
'THWK' v%saACT' REVIEW Rev. O gnformation pj jjpg pp ff"% 5 of 17
i 1 l \
i l
1.5 Reviews NOTE 1
l 1. Attachment 2 presents the required format for the log used to track l the review process.
l l 2. Both internal and external reviews are performed by individuals knowledgeable in the assigned programs, processes, and procedures.
l lDR l 1.5.1 PERFORM Internal Review as follows:
- a. LOG the title and DESCRIBE the purpose of the program processes or procedure in one or two sentences.
l l b. REVIEW the program, process, or procedure to determine whether any of the following internal configuration control
! process discrepancies exist, and MARK each communication l
link:
i j . Communication links are missing.
l lg
. Internal product transitions (hand-offs between y individuals, groups, databases, etc.) are unclear or not I defined.
. Service support (centralized data entry, drafting, reproduction, etc.) is unclear.
. Requirements to finalize products (independent reviews, approvals, etc.) or to transmit products (for use or to storage locations such as trend database or Nuclear Records) are unclear.
. The reviewer believes a process activity may jeopardize configuration control requirements.
l
- c. IDENTIFY all external inputs to and outputs from the program or procedure for evaluation in step 1.5.2.
1
.l 1
~
i l A & 3 i NUC PI 10 Level of Use Information .vM2p W e ' M ' M Es Rev.0 j;O f% y 6 of 17
i ,
i.
- d. DOCUMENT the following information on Attachment 2 for any internal discrepancies (from step 1.5.1.b.) and external inputs or outputs (from step 1.5.1.c.):
- Type (internal or external)
. Input or output (I/0)
! = Configuration Management Communication Links description
. Communication format (drawing change, data base, etc.) i
. Transmittal mechanism (E-mail, AITTS, phone, etc.)
1
. Input or output timing requirements (1 week,72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />, ,
etc.) !
- Input or output source or destination (including l document identification number, step number, etc.) l Should it exist (is it needed?) )
1 I
i:(
- Does it exist?
- Is the communication link effective as evaluated by the review criteria on the form?
- Recommended corrective action l e. PRINT name and DATE Attachment 2. 1 l
t i
l
~
l A & 4 NUC PI 10 Level of Use gp r , g/s- mgy.M.5f Rev. 0 lnformation y.g jygg gj;xg jpe 7 of 17
. 1 NOTE External reviews are performed using a table-too process by a team of at least three individuals knowledgeable of the Condguration Management Model presented in Attachment 1. One individual shall be a Desi Reviewer in the program, process, or procedure being evaluated. gnated Additionally, the team shall have the expertise required to evaluate the communications links against each attribute of the Con 5guration Management Model.
1.5.2 PERFORM External Review as follows:
lDR f a. PROVIDE the program, process, or procedure overview, including information contained in Attachment 2 and the reviewed copy of the program, process, or procedure.
lCMT f b. Refer To Attachment 1," Configuration Management Model,"
and IDENTIFY communications links that should exist.
- c. REVIEW the program, process, or procedure and PERFORM the following:
- 1) IDENTIFY existing communications links.
- 2) COMPARE to communications links that should exist (from step 1.5.2.b.).
- 3) LIST any discrepancies (both needed communications links and existing communications links not identified as needed) on Attachment 2.
~
5 4
A NUC PI 10 Level of Use g., y:gg7 yg .%d Rev. 0 Information p ,p 7, ,Y -
,+ rpt, ,
8 of 17
~ _ _ - - . - _ . - - __
! l 1
- d. IE communications links exist AND are identified as needed (from step 1.5.2.b.), CONSIDER the following and EVALUATE link effectiveness;
= For Outputs:
l l
- Is the destination clearly identified by the program, process, or procedure?
. Does the destination accept and provide receipt l information (feedback) to the program, process, or procedure?
. Does the destination provide receipt instructions?
. Is the transfer mechanism acceptable?
. Are there timing requirements? Should there be?
l Arc stated timing requirements appropriate? !
l
- For Inputs: l
- Does the program, process, or procedure provide information receipt instructions?
. Is the source clearly identified by the prograni, l process, or procedure?
. Does the program, process, or procedure accept and provide receipt information to the source?
l
. Is the transfer mechanism acceptable?
l
- Are there timing requirements? Should there be?
l Are stated timing requirements appropriate?
- e. IE communications links are not effective, IDENTIFY (for each discrepancy) actions required to support the short-term
_fix or actions that are long-term recommendations.
1
^
A A 4 NUC PI 10 Level of Use N N. 'ddP"dNYThEG7 Rev.0 l lnformation 3-jrq y jpg 9 gf 37
- f. E a communications link should exist AND does not exist, !
PERFORM the following for each discrepancy:
1
- 1) IDENTIFY required acti6n and whether the action should ;
i be a short-term fix or long-term recommendation. l l
l 2) Refer To the applicable procedure and,if required, INITIATE an ACR for each identified discrepancy:
RP-4, " Adverse Condition Resolution Program" l (for Millstone) l
- ACP 1.2-16.5," Adverse Condition Report Process
- Implementation" (for Connecticut Yankee)
- g. E a communications link exists AND is not identified as
- needed (from step 1.5.2.b.), PERFORM the following for each discrepancy
- 1) EVALUATE the value added and RECOMMEND whether the link should be continued or deleted.
- 2) IDENTIFY whether the action should be a short-term i fix or long-term recommendation.
1.53 PRINT names of team members and ENTER date review was completed on Attachment 2.
I CM Manager l 1.5.4 VERIFY all discrepancies are documented for resolution and are properly identified as either a short-term fix or a long-term recommendation.
l L
1 l
l 1
i i
gh 5 A NUC PI 10 Level of Use ~
wr g y v g y m RNvis7/
, ,3gp Rev.0 lnformation -
u4p'g
+1 p~g' jar
~
lo ot 17 jr g
(
l .
\
l l
l
~
1.6 Discrepancies 1
NOTE -
l Reporting, tracking, and resolution of discrepancies are addressed in NUC PI 24, " Project Process Administration."
I l [CMT I 1.6.1 TRANSFER Phase 1 (short- cmn fix) and Phase 2 (long-term l recommendation) items to the ACCESS database. l l
l 1.6.2 For Phase 1 (short-term fixes), PERFORM the following:
l l
- a. DEVELOP a Procedure Action Request (PAR) or Change Request (CR) to huplement each short-term fix.
- b. DOCUMENT PAR or CR initiation in the ACCESS l database.
l 1.6.3 For Phase 2 (long-term recommendations), PERFORM the l following:
l
- a. INITIATE a CM AITTS assignment for each long-term
! recommendation and DOCUMENT corresponding Action Request number in the ACCESS database " Disposition" field.
- b. DEVELOP CM recommendations to ensure CM requirements l l are adequately maintained, based on the following:
a Performance monitoring criteria developed and presented l in CMP-95-085," Configuration Management Program l Performance Indicator Report Transmittal" l
l
- Additional information presented in NUREG 1397, i "An Assessment of Design Control Practices and Design l
Reconstitution Programs in the Nuclear Power Industry" l
l
- 4 .
^ 4 NUC PI 10 evel of Use
' M r " d W '~ ' d .W
.~ ~~
Rev. 0 nformation go. pq j;;;d /#% 11 of 17
1.7 Recommendations 1.7.1 COLLECT all long term configuration recommendations and REVIEW for the continuation of Configuration Management activities.
1.7.2 DEVELOP long-term configuratica management recommendations, such as:
. To ensure configuration management requirements are adequately maintained, the Configuration Management Team recommends adopting the performance monitoring criteria developed and presented in CMP-95-085," Configuration Management Program Performance Indicator Report Transmittal".
l
- In summary, these criteria utilize existing processes (ACR and AITTS) and the assignment of key words in the trending area of ATITS to monitor ACRs written against any of the five boxes (Attachment 1) associated with configuration management.
l ,-
l(
i i
A i 4 6 NUC PI 10 Level of Use ,,g." "n 'ENPYWT Rev. 0 Information R-l ped fi ##4 s 12 of 17
l i
l l
l 1.8 Monitoring and Reporting Short-Term Performance h
l l [ Cia Manager j 1.8.1 Refer To NUC PI 14," Project Process Administration," and PERFORM Quality Controlinspections or audits as required.
l CMT Leader l 1.8.2 Periodically REPORT on the following:
l Short-term corrective actions identified versus resolved
- Input / outputs identified versus time 1
! l t
l
? l
! 1 l i t
l i i l
j
)
l i i ?% 4 NUC PI10 Level of Use . e _ .-
- e_
" THIN K *'a _- , LACT'e., .*NEVIEWRev. O
- srOP~
lnformat. ion jne. jwl 13 of17
/EN
- 2. REFERENCES 2.1 10 CFR 50, Appendix B 2.2 NUREG 1397,"An Assessment of Design Control Practices and Design Reconstitution Prograrns in the Nuclear Power Industry" 2.3 NGP 3.2, " Configuration Management" 2.4 ACR 7007, " Event Response Team Report" 2.5 NUQAP Topical Report 2.6 Configuration Management Plan (CMP) 2.7 RP-4," Adverse Condition Resolution Program" (for Millstone) 2.8 ACP 1.2-16.5," Adverse Condition Report Process Implementation" (for Connecticut Yankee) 2.9 NUC PI 2," Unit-Specific Assessments" 2.10 NUC PI 14," Project Process Administration" 2.11 CMP-95-085," Configuration Management Program Performance Indicator Report Transmittal" 2.12 NUMARC 90-12," Design Basis Program Guidelines"
- 3. COMMITMENTS None
- 4.
SUMMARY
OF CHANGES 4.1 OriginalIssue T
I. A & 4: NUC PI 10 evel of Use ., g .7 ,gy syg7"TgEST Rev.O nformation jg
~ -
p.; ;g M of 17
. Attachment 1 Configuration Management Model (Sheet 1 of 1)
As Designed As Licensed Configuration Configuration W \
1 Design drawings UFSAR Calculations TechnicalSpecifications Specifications TechnicalRequirements Manual Component Lists State and Local Permits Design Basis Documents (g Commitments i l
l I I Communications %
Y A M
Physical Plant V Configuration A As Built As Operated Configuration (Hardware) Configuration (Software)
Plant MOV Program Design Drawings Lifted Leads and Erosion / Corrosion Program Calculations Jumper Bypasses Operations Procedures Specifications Setpoints Maintenance Procedures Component Lists Valve Lineups Surveillance Erocedures Fuse control Fumple of Communications Within a Function l
l Regulatory .
~
l UFSAR' , Commitments l l As Licensed .
l l Configuration '
i .. T Tech Specs & l l TRM, -
Requirements l i A d i NUC PI 10 Level of Use a:1 - Ju c-
~ STOP ' vTHINK
. ac- _NACT " REVIEW Rev. 0 Informat. ion
. a sq g ,f Q, ,s. fee, 15 of 17
Attachment 2
. Configuration Management Review Report (Sheet 1 of 1)
I Ih 1'
l1 a3 ,
I :
! Y}
11
-l 'i,
! . , ,1 2 -
2 g
e '.1
}-,{
ji-=
f j
I l
' l
[ <
l
,3, c f. J l AE !
J- ,
1 j'
\
l 5 = l ila J 11
- .. . ,.=== ., ,
f(.
)
t 1 1 1 1
1Q l 2
JJ2-
= 1 1
} E 1
i ,!
! 1 .:
1 ii #:
g :lh 1 l j l' 7-pj 2 g s i v .
I - l !
I ..i l 1
! [ l i 2 e li :
- s d] a I f; I! g l J 4m ] }i
! sil 1 i : . -
llwi$!u !i fM
>I
.: c =e . ., .
1 m .
A l' A NUC PI 10 Level of Use x;g.y ygg sqgg,W$s/ Rev.0
. Information w' p .,y j;;;.4 jpgh, 16 of 17
, Attachment 3 Definitions (Sheet 1 of 1) l Communications link - 1) A complete configuration management interface between individuals, departments, or databases including output, input, transmittal instructions, I
receipt acknowledgement instructions, and timing requirements; or 2) an exchange of information or data.
Configuration Management - An integrated management process to ensure a nuclear unit's physical and functional characteristics are maintain ~ed in conformance with the unit's Licensing Basis (LB) and Design Bases (DB); that operating, training, modification, and maintenance processes are consistent with the LB and DB; and that the plant is operated and maintained within the LB and DB.
External Review - A review of configuration management communications links that cross single program or single procedure boundaries.
Input - The portion of a configuration management communications link that !
receives actions or information (engineering calculation, drawing, licensing commitment, etc.) from another individual, department, or database.
1 Internal Review - A review of configuration management communications links that do not cross single program or single procedure boundaries.
7 Phase 2 (Long-term Recommendation) - Activity or recommendation that enhances configuration management effectiveness or correct deficiencies not needed to support ;
the 10 CFR 50.54(f) response effort. Not required prior to unit restart. !
NGP - Nuclear Group Procedurs I
Output - The portion of a configuraGen rc.gement communications link that passes actions or information (engineering calculation, drawing, licensing l commitment, etc.) to another individual, departm mt, or database.
Procedure - A set of formalinstructions used to implement a process or activity.
Process - A set of formal instructions.
Program - Engineered program that addresses generic solutions for nuclear units and !
evolving industry issues as specified in NGP 2.32, " Engineering Programs."
Phase 2 (Short-term Fix) - Activity or recommendation required to support the 10 CFR 50.54(f) response effort. Must be completed prior to unit restart. -
l 50.54(f) effort - Efforts required to respond to NRC letters addressed in the CMP.
A A 4 -
NUC PI l0 Level Of Use A
,NSTOP' s^
'THINK' 4- y. L
"%ACT" REVIEW Rev. O gnfOrmat.lOn gy4 pc 4 g gg
l d
i i .
A, g.
! 108A l, NORTHEAST UTIIIFIES NUCLEAR $ CY -
PROJECTINSTRUCTION UP 1 S?1
,j f,, ./ ' ,
- y
.< g' so s e s ss a vp v v ee,< a s:5.e -w + <m <, ~e~ , ' , +s.-,<.-" s ,.s My 'J' , (J '. 's , "[ ,, / , ,j' t,
- q' ',','.' " ~s O.,,'t ;:~^.*:/ ',,: jy s^> s q
s .. .-- : : . .
- . p.,. . /
a ~ s /
ri;n.
' ~? , : ^'? y% ;,' :;!!;;.',*,,!kk rs 'h"N ,
?$?.yy?W,??'#"
- 7
'6'tk? s> &~:y'
'~
OP 141NKD:;' ' %~
s<r et ry: '<. : . u a e,4 CT7 EVIEW sy A , ** w <
'v Ap d lY y[?%6* ^.;.
^ R. "' ~ ,'C'~t':" Gilt::( ^ :y~ ~ \% A v ,,~ ,~ ,
9 u - ~,, ~v
~~ -"
c.. -
y&b5('~; ' ^ f_ _ -- - =:: z. ~
- Sh&fyfhf5tk$hp'%g f ;:
99"' NUC PI11 %,.
Rev.0 is part ofimplementation of the This ProjectManagement Configuration Instruction (PI) Plan (CMP for the Design Bases Component of the Nuclear Excellence Plan for Nort east Utilities (NU).
- (( .
"" 4
- A royal Effective Mtg. No. ate Date Millstone SORC g,g pg,g CYPORC- --- ~
^~
~
1 .
i i
t.
l Responsible Individual:
Level of Use W. Merritt Information Subject Matter Expert:
%of 403FoVO /'pp w. Merritt
Applicable Units Project Instruction
[ Independent Assessment TABLE OF CONTENTS
- 1. INSTRUCTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1 Assignment of Independent Assessment Tasks . . . . . . . . . . . . . . . . . 3 1.2 Independent Assessment Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.3 Discrep ancies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.4 D elive rabl e s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
- 2. REFERENCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
--- - -3. ._ COMMITMENTS . . . . . .. . . . . . . . . . -. . . . . .m . . . . . . .. . . . . . . . . . . . -7 - - -
- 4.
SUMMARY
OF CHANGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 A'ITACHMENTS AND FORMS Attachment 1, " Independent Assessment Team Organization" . . . . . . . . . 8 Attachment 2, " Independent Assessment Forra" . . . . . . . . . . . . . . . . . . . . . 9 Attachment 3, " Review Elements to be Considered" . . . . . . . . . . . . . . . . . 10
((
Attachment 4, "D efinitions" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 i
l
-. _ . . .=. - .
1 4
(- Level of Use
$_. 'THINK'3
'STOP~
1 N ACTA,,.#A-..
L REVIEW NUC PI 11 Rev. O Informat. ion -
wg g um pg y3 p %a pag 1ofil
- 1. INSTRUCTIONS
. This Project Instruction provides a method to perform an independent technical assessment (peer evaluation) of the activities performed as specified in the CMP.
An Independent Assessment Team (IAT) shall assess the quality and completeness of NU activities to assure that discrepancies and vulnerabilities are identified for disposition. The IAT may review specific work products and resolution activities as assigned, and assess progress of activities against the schedule.
NU requested the formation of the IAT to assure the highest quality of deliverables for the CMP in accordance with NU requirements. The IAT reports to the Director of Nuclear Design Engineering and Program Services.
Organization of the IAT is presented in Attachment 1. The IAT shall be comprised of staff with appropriate experience and training, as documented in !
Quali:ication Records. -
. . . . : .. .. .--.-.. _ .- . .F -
A A A & NUC PI 11
~
Level of Use A' A_.
'STOP
,c THINK'myx-_4ACT
."NEVIEW Rev.O gnfOrmatIOn g jpq( jje p4 2 of11
I 1.1 Assignment ofIndependent Assessment Tasks b NOTE Activities that are identified in step 1.1.1 as Hold Points must be l completed prior to proceeding to the next activity.
l l l IAT Leader l: 1.1.1 OBTAIN a list of activities to be included in the Independent Assessment process from the Director of Nuclear Design Engineering and Program Services, and the Unit Project Managers.
. 1.2 Upon receipt of the NU work product and review schedule, SELECT and ASSIGN a Lead Engineer for each work product, based on the following criteria:
- Engineer has' experience and required qualifications in the ~~
- - - -- -~
design orlicensing requirements for the assigned work product.
1
- A Qualification Record is complete for the Engineer. l t
1.1.3 Refer To step 1.1.1 list and DEFINE the Hold Points in the schedule requiring assessment.
. i
- 1.1.4 DOCUMENT the following information for the assignment on (1- l LeadEngineer the Attachment 2 Assessment Form:
. Description of the assigned task
. Estimate of time required for the assessment
- NU interface person to be contacted . . _ .
. Schedule for completion Results of subtasks and assessments 1
l l
i i fi A NUC PI 11
(-
1 Level of Use Information sehr ,ggr yg7.~#NWT Rev.0 jp4 p% [N f^ 3 of 11
s 1.2 Independent Assessment Process Lead 1.2.1 COORDINATE the independent assessment process as required.
l Engineer NOTE The Attachment 3 list is not all-inclusive. Technical judgement is needed to assure adequate depth of assessment.
l IAT Member l 1.2.2 Refer To Attachment 3 as required and PERFORM an assessment of the assigned work product as follows:
- a. REVIEW the assigned work activity.
1
_ _ . _ . - _ _--b.- -INTERVIEW-NU-first _l_in_eteviewers.
- c. EVALUATE work product and piocess for technical adequacy and completeness.
Lead 1.2.3 DOCUMENT the following assessment information and results on Engineer the Assessment Form and ROUTE the form to the IAT Leader:
- Documentation reviewed
\.
- Personnel interviewed
. Comparison results
. Progress against the schedule
- Recommendation on whether to proceed beyond the Hold Poirt
~
1.2.4 PREPARE a report (including a recommendation on whether to l I
proceed beyond the Hold Point) and INFORM the NU interface of assessment results at an exit meeting.
t c A 4 NUC PI 11
- Level of Use egy mg, yg7.'dssf Rev.0 lnformation 4 jy. g;j jg eq( 4gg33 l
J
- 2. REFERENCES 2.1 Configuration Management Plan (CMP)
(l '
2.2 RP-4," Adverse Condition Resolution Program" (for Millstone) 2.3 ACP 1.2-16.5," Adverse Condition Report Process Implementation" (for Connecticut Yankee) 2.4 NUC PI 14," Project Process Administration"
- 3. COMMITMENTS None l
.-..,4_
SUMMARY
OF CHANGES .. . -
=.. --- -
4.1 OriginalIssue
,(
1,- '
l l . _ _ . . . . _ _ - . .
~
. . . . - -- --. : ~~- .-- -.
l l
i.
t J
4 A gh A h NUC PI 11 Level Of Use e:~ c .. .e
,,"STOP' A-r v HINK"r
'T wet wACT
- . ~ REVIEW Rev. 0 l lOfOrmat.lOn p;( jjpg y J4 p;g 7ggyy
l
. Attachment 1 -
Independent Assessment Team Organization
., (Sheet 1 of 1)
C!.
NOTE Yankee staff from specialty departments (Nuclear Engineering, Environmental Engmeering, Radiological Engineering, Engineering Services, Plant Support, etc.) are available for support on an as-needed basis.
Team Leader 1
7 QA Representative ll MP1 MP2 MP3 CY Review Review Review Review Team Members: Team Members: Team Members: Team Members:
'~ ' ~'
~~ - -~
~-~ VY Er6 ject MY Project ~~ Seabrook - Yankee ~ Rowe "
Project l
5 8 8 NUC PI 11 f- ,e-.h Level Of Use " y 4 e.. -
I
- STOP~ THINK" *EACT' " REVIEW Rev. O ;
gnfOrmat.lOn p ,. gMg };5.. p.T 8 of 11 !
l 1
Attachment 2 Independent Assessment Form
, (Sheet 1 of 1)
Independent Assessment Form Unit: Assigned Lead Engineer:
Task:
Estimated Effort (days): NU Interface:
Schedule: Work Order:
Results
- Reviewed:
Integiesd: _ , _ m_ ___. _
l l
)
Evaluated:
(
i Comments:
1 l
l Recommend proceeding beyond the Hold Point?' Yes O No O Schedule Status: .
Exit Meeting
Contact:
Signoffs .-
Lead Engineer Signature and Date
- Team Leader Review Signature and Date i
- ATTACH additional sheets as necessary. . Page of l
NI II k
Level Of Use gnfOrmat.lOn
.y STOP 77 y. d-m
' THIN K'
,,%ACT '.ML,,..m_
' REVIEW Rev. L_ O jf.:i pg ;;: ;g g 9gg i
r Attachment 3 Review Elements to be Considered n . (Sheet 1 of 1)
This list is not all-inclusive. Technical judgement is needed to assure adequate depth of review during either independent assessment.
- Definition of the review process (program, procedure, instructions)
- Review of past NRC or NU commitments, including disposition
- Resolution of previous outstanding issues ,
- Independence of first-line reviewer
- Depth and results of first-line review
_ . Reports _or inputs considered or verifi_ed _ _____ __
- Basis for the design
. Impact of Technical Specification limits
- Revision level or issue date for each Code used and for each calculation or specification used
- Procedural or design changes identified and implemented I
(( l
- Schedule adherence .
. . . . _L . _ . . . _
l 4 A A A NUC Pill
(.- Level Of Use ,_ E- ,7m_ ,VACF ma_TEVIEw .
rE_
"STOP" THINK" Rev.O nf0Tmat.lOn jj;q j;:a jp %( 10 of 11
Attachment 4 t
l Definitions f8 . (Sheet l of i)
Independent Assessment - An evaluation of specific activities relating to review of activities to assess work practices, depth of review, and management controls; and to -
identify any areas needing corrective actions. This is an in-process function that may be initiated at any point in the overall CMP completion process and may include Hold Points.
Independent Assessment Team (IAT) - That group of individuals that provides the independent technical assessment or peer evaluation of activities performed as specified in the CMP.
Work Product - Any process related to activities perfonned as specified in the CMP that requires independent assessment as specified in this PI.
l 1
l
. = . . . -~ _ . ..
l a
,( Level of Use ~
k
.d ,. -,,THINK'- .- ,7 d , .~d
.- ._ NUC PI ll
,c*STOP ' 4ACT" ' REVIEW Rev. 0 lnformat. ion en wm m=> gm p g jeg p~g ,j2\ 11of11 1
sa nn---cu.ama.m-=-maa mmma-__mman st a m,wqem..su-.a-_sA-m.aus2m,,,.. mas--MuxhaasA.m4 A nn M .&A, m m e&e% m s_, 0 s a n sse___.,s a . ,aa _a 3 .
1 4
a 4
PI12 t
t 1
i i
i i
i SHORT TERM AND LONG TERM COMMUNICATION i
4 f
i l
t i
a 1
?
LATER
PI 13 I i
UFSAR CHANGES l l
l
)
i i !
i lATER i
?
x i
NORTHEAST UTILITIES NUCLEAR < [< CY .-
PROJECT INSTRUCTION [ . UPyh g?%
.( p
- ~ ,
svrss rx ? e t e1 ht%vog g.st r 4,9 . t y yry y, y mesm. ,ms.
, s vzy p x
-<m<
m~ , , -
<+\
s ..
- w :
1 p'<Jq.
y a
s;s, -
s mo
~ , ' / tm ?
< > ~ yA +k < W-n <p<
r, , w. ._7
.,n ~e,.
gyc.;ah4- w, (~~u:r*o w.4, .
a
- < c - - % s +cuy ..
.,q;: ' g~
w yA N[pn:r:.
%. ~,
~
. w ,.-a i c ,4;;;
s-vs
.~ EVIEW z:.::4.u~t fs"< s^,%,)), pq,r- .m.$4:, N:( ',7'(?'['p/p%3 : ?y~Qq.
! > 's**,
- .,. .;;m,,97 %y , . . a 2 ConfigurationiMdiisgemenOlsWProject Process Adniiiiistration InstimEtion p*" ^*g NUC PI 14 i
Rev.0
,. This Project Instruction (PI)is part ofimplementation of the
( Configuration Management Plan (CMP).
Mtg. No. A roval Effective
. i ate P$ Date Millstone SORC g/o _cp j g g.jy pgo g.jg,pg CY PORC
- e MP1PORC MP2 PORC t
MP3 PORC l
1 l
j Responsible Individual: Bob Cox !
Level of Use Subject Matter Expert: Pete Austin Information l i
NO803064 C( lA f_ f':__ ' l i i
Documentation of Training Requirements (comm a.2) l (Sheet 1 of 1)
~ Section 1. Document Information .
l l
Document Number: NUC Pl 14 Revision No, O Change No.
Document
Title:
Configuration Management Plan Project Process Administration instruction
~
LSection 2 }Trainirig Considerationsl. e,,. 9
! - s s = m s , ,
l 1
Requirements of TQ-1, " Training and Quali5 cation" Knowledge level of personnel performing procedure Previous training of personnel performing procedure Qualification of personnel performing procedure Procedure Level of Use Difficulty of procedure or task Consequence of incorrect procedure performance Advice of NuclearTraining Department Name of person contacted at Training Department: hg."t[ [erw/S C Required for new documents and revisions only
~
-Section. 31 'haining or Familiarization Rdquirements :
. . _ _ ... m
. m m:x. ms
(
Training to be done by Nuclear Training before effective date.
~
i 3/ Training to be done by Department or Nuclear Training Department ,
[ within 60 days of Effective Date and prior to performance of procedure. l Familiarization required Methods to Provide Familiarization:
prior to Effective Date. . Department meeting Familiarization required, no - Pre-shift briefing impact on Effective Date.
- Pre-work briefing l
No familiarization or . Document Acknowledgement Sheet training required.
l Target Group Requiring haining or Familiarization: Enter information pertaining to who requires training or familiarization, which parts of the procedure are applicable, special
- instructions, etc.
NC Aa- &
4 jm neu e.skj)s wL L m(
_ _4_ _ _W_ __ __ A_______________________.
Approved By: I~ # s ' '
96 8
Departthent Head or Responsible Individual Date b +
^
_;. DC 1 Attachment 5
' STOP ' 'THINK "
?ACT ~ _ \..,
REVIEW Rev. 4 l
64 of 69
1 1
. 1 s q l
l l
1 i
r' MP1, MP2, MP3, CY l Project Instruction )
l Configuration Management Plan Project Process Administration Instruction TABLE OF CONTENTS I i
- 1. INSTRU CTI O N S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1 Co mmunications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2 Personnel Qualification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.3 Discrepancies, Reporting and Tracking . . . . . . . . . . . . . . . . . . . . . . . 5 1.4 Project Progress Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 1.5 Project Self-Assessment .................................. 7 1.6 CMP Performance Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 )
1.7 Approval and Responsibility of CMP Documents . . . . . . . . . . . . . . 9 1.8 Control of CMP Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
- 2. REFERENCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
- 3. CO MMITMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 i k, 4.
SUMMARY
OF CHANGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 l l
l 1
l l
1 4
- A A NUC PI 14 ,
Level Of Use , = - sc~a- m_, _"riEVIEW n- i
- STOP ^ THINK' ' RACT~ Rev. O j gnfOrmatiOn y g Iq q gpq3 1of10
- 1. INSTRUCTIONS
[-
This Project Instruction provides a consistent review and approach for administrative control of the Configuration Man'agement Plan (CMP).
This Project Instruction defines the requirements and provides the instructions for the administrative control of the CMP.
The scope of this Project Instruction includes the following:
. Communications Personnel Qualifications
. Discrepancies, Reporting and Tracking
- Project Progress Reports
- Project Self-Assessment I
- Project Performance Measurements
= Approval and Responsibility of CMP Documents
'
- Control of Project Documents and Data Bases l 1
i A f 4 NUC PI 14 Level of Use y;g.pryg&geyggg,'Edd[ EFT Rev. 0 Information ;4 juh f1 jF% 2 of 10
l l
l 1.1 Communications 1.1.1 Project Communications .
lUPM l; a. Refer To Nuclear Group Policy NGP 5.2, " Communications,"
and DC 2, " Developing and Revising Millstone Procedures,"
and APPLY communications guidance,
- b. Refer To Section 1.4 and COMMUNICATE project status.
l WP&OM l: c. DEVELOP Level 1 Schedule using the following criteria:
- INCLUDE major milestones l
SPECIFY milestones as status points for each of the units <
involved to complete the CMP effort j l
1.1.2 Internal Communications This effort is intended to provide ongoing information so unit personnel can see progress being made. Units should use the available communications tools (e.g., daily unit status, Power of
,~ Five, etc.).
(
i
- UPM f a. PROVIDE status updates as project milestones are complete.
1.1.3 Documentation Each Unit Project Manager is responsible for retention of documentation for those activities specific to that unit. In order to provide retrievability, CMP documentation should be clearly identified as part of the CMP effort and should include subject information. 1 Project a. IDENTIFY documentation as part of CMP effort.
Parsonnel
- b. ENSURE subject information is included in documentation. l l
[UPM j; c. RETAIN documentation in project file and SUBMIT to l Nuclear Document Services at conclusion of project.
1 l
l 1
A i 6 5 NUC PI 14 Level of Use Information
'N g-P " $ F " G r 's d iv7 Rev.O p -
'g;p.% :/ 3ofl0
l i
lf'~ 1.1.4 Project Information Book !
l A Project Information commencement, Book (PIB)ilar to a standard outag and should be sim j handbook.
lUPM l
- a. At project commencement, DIRECT Project Personnel to develop Project Information Book.
Project b. DEVELOP PIB and INCLUDE the following minimum .
Pzrsonnel information' i I
. Organizational charts l l
l . Scope of unit CMP efforts l
l Listing and locations of unit project groups including phone numbers l
Direction for external and internal concerned parties point of contact for project information input
- Level 1 Schedule with major milestones highlighted
(-
l
. Personnci quali5 cation documents l
l 1.1.5 Information Release Unit Project Managers, or their designees, are responsible for the
! release of information from The Project Group to other groups l under the Northeast Utilities operational control.
l
! Northeast Utilities Nuclear Information Services Group is responsible for the release of any information from Northeast l Utilities Group to external groups which may include, but is not i limited to, members of the general public, the media, and l shareholders and investors.
l UPM or a. _ RELEASE information to groups under Northeast Utilities Responsible operational control.
Individual Nuclear b. RELEASE information from any Northeast Utilities Group
. Information to any external group which may include, but is not limited to, l gypes members of the general public, the media, and shareholders and mvestors.
A A f $ NUC PI 14 Level of Use Information
.'NF 'M'~ mfd 5T Rev.0 pF4 [9 f3 f 4 of 10 t
L
4
( 1.2 Personnel Qualification The Unit Project Manager is responsible for the overall review and approval of project personnel based on a technical background as required to implement individual Project Instructions.
lUPM l 1.2.1 Refer To NGP 2.26, " Departmental Training" and ENSURE project personnel, including contractor personnel, are trained and qualified to specified requirements, which include maintaining records.
1.3 Discrepancies, Reporting and 'Itacking lUPM l 1.3.1 DETERMINE and ASSIGN priority to discrepancies as follows:
Priority 1 - Those discrepancies required to be resolved before completion of the CMP Phase 1 effort. Those corrective actions considered necessary to suppo'rt the safe operation of the plant, to demonstrate sufficient progress in 4
weak performance areas, or to correct significant discrepancies. 1
. - Priority 2 - Those discrepancies which will be resolved in k Phase 2 of the CMP effort. Corrective actions identify 5
additional improvements to areas which are functionally satisfactory now or which when completed achieve the desired cultural environment, or corrective actions involving
~
longer-term enhancements to programs / processes which are considered currently satisfactory.
I NOTE All discrepancies must be evaluated in accordance with RP 4 or ACP 1.2-16.5.
Rasponsible 1.3.2 SCREEN and TRACK discrepancies for safety significance, and ;
individual resolution using the following process:
- a. IDENTIFY discrepancies as specified in CMP Project Instructions. I
- b. ENTER record for discrepancy into a database and ASSIGN j a unique " Log" number.
Level of Use ,
w Sh w v gr o lnformation gA( jpg jw JM4 5 of 10
c NOTE Database controls prevent deletion of records. ,
- c. Once entered, ENSURE discrepancy record and unique log number is not deleted,
- d. ENTER the following discrepancy status information into database as a minimum:
. Current Status - open/ closed / fixed disposition
- Potential Operability Issue - Yes/No
. Follow-up Action Required (e.g. procedure change, calculation revision, or plant modification required)
- Priority 1 or 2 l
- e. ENTER information and logic discussion used to resolve discrepancy into database. ,
( 1.4 Project Progress Reports l Project Lead l 1.4.1 Weekly, PERFORM the following for inclusion in Weekly Project l Progress Report:
1
- a. MAINTAIN listing of deficiencies (ACRs, NCRs, LERs) generated and identified as a result of the CMP.
i
- b. MAINTAIN listing of activities worked during the week l period including, but not limited to, the following: l
- Calculations completed
. Procedures revised or written a DCNs written I A b A NUC PI14 Level of Use lnformation
, egg y g y g 7 . M W Rev.0
- J4 ;wp; 7 /#9( 6 of 10
& c. MAINTAIN listing of deliverables completed including the
(
following:
Description of deliverabl6 Deliverable completion date
. Responsible manager i d. REVIEW Action Item Tracking & Trending System (AITTS) for items which may have been completed as part of the CMP item. AITTS shall be updated to reflect the item completed.
- e. PROVIDE input to UPMs for schedule variances occurring, and variances which may be coming in the future.
l i f. PROVIDE input to UPMs for planned activities for the next I i reporting period, j 1
- g. On a weekly basis, PERFORM the following to the project l schedule
- UPDATE pertinent items
' . ADD pertinent items a DELETE pertinent items.
j 1.4.2 On a weekly basis, SUBMIT required information to UPM in l- support of Friday issuance of Project Progress Report.
l l
lUPM l 1.4.3 On each Friday, ISSUE Project Progress Report.
1.5 Project Self-Assessment Foundation of the self-assessment process is a candid aad objective assessment of the project performance with the belief that performance can be improved i
lUPM l 1.5.1 DEVELOP a unit self assessment plan and schedule to determine adequacy of projects activities as follows:
! a. SELECT unit as.sessment personnel.
- b. ENSURE assessment personnel obtain, review, and complete
- , qualifications in the Millstone Self-Assessment Manual.
i Level of Use _dy. yd
'" STOP' THINK*
d
,_T_XdYT.MEWb. Rev. 0 NUC PI14 lnformation l fF i f%g. pMfg [9( 7 of 10 l - .. -- . - .. ._. . --
4 c. REVIEW and APPROVE project activities self-assessment plan.
UPM or d. IMPLEMENT project activiti.es self-assessment plan.
Responsible Individual 1.6 CMP Performance Measurements PI for the project a'etivities must develop performance standards.
Performance standards must be translated into tangible, measurable and observable requirements that apply directly to the long-term quality of products related to the LB and DB activities and to identifying both positive and negative trends. Such measurements can be personnel surveys, ACR trends, operability determination tools, etc.
Project Managers will be responsible for periodic reports.
( l 1
l
~
A , 8.s., A NUC PI 14 Level of Use .g)~, . M
.g%W,K' ,N ACT,, ._.x,_
yo? " REVIEW_ Rev. 0 lnformation jsag j;lik y s:4 g
y3 8 of 10
1 4
p 1.7 Approval and Responsibility of CMP Documents Doc. Type Approval Responsibility CMP VPORS/WPTS/ MP1UPM VPOS/PORC/SORC Attachment 1 MP1PORC MP1UPM Attachment 2 MP2 PORC MP2 UPM Attachment 3 MP3 PORC MP3 UPM Attachment 4 CY PORC CY UPM PI 1 SORC/PORC (CY) MP1UPM PI 2 SORC/PORC (CY) MP2 UPM PI 3 SORC/PORC (CY) MP2 UPM PI 4 PORC (MP3) MP3 UPM PI 5 PORC (MP3) MP3 UPM PI 6 SORC/PORC (CY) MP1UPM PI 7 SORC/PORC (CY) MP2 UPM PI 8 SORC/PORC (CY) MP1UPM PI 9 SORC/PORC (CY) MP1UPM k PI l0 SORC/PORC (CY) CM MGR PI11 SORC/PORC (CY) MP1UPM PI 12 SORC/PORC (CY) MP1UPM PI 13 SORC/PORC (CY) MP1UPM PI 14 SORC/PORC (CY) CM MGR PI 15 PORC (MP3) MP3 UPM PI 16 SORC/PORC MP1UPM 1.8 Control of CMP Documents Responsible units above have the responsibility of ensuring that the CMP documents are distributed and maintained current. An index of project documents shall be made available to the end user so it can be verified
_ that the latest revisions are in use.
- ^
d A NUC PI 14 evel of Use .,,g.. -gg7 mgg. .I Rev.0 nformation ;~ '
g: [N 9 of 10
i .; 2. REFERENCES l,
2.1 Communications 2.1.1 Northeast Utilities Nuclear Group Policy 5.2, " Communications,"
Rev.1, dated 4/14/94.
i 2.1.2 Millstone Nuclear Power Station, Station procedure DC 2,
" Developing and Revising Millstone Procedures and Forms."
2.1.3 Station Procedure (CY) ACP 1.2-6.5.
l 2.1.4 RP 4," Adverse Condition Resolution Program."
l l 2.1.5 ACP 1.2-16.5," Adverse Condition Report Process
! Implementation" (for CY).
I 2.1.6 Configuration Management Plan (CMP).
I ~
l 2.2 Self-Assessment L
i 2.2.1 NU Millstone Self-Assessment Manual, Revision 1, dated l January 1,1995.
l(
l 3. COMMITMENTS l
! 3.1 None i
- 4.
SUMMARY
OF CHANGES
! 4.1 Original issue.
i l
l l
l l
i l l
1 i
A A A # NUC PI 14 Level of Use ,ggpr ygg;7 ygg7.'dWT Rev.0 Information gpq jjg; jp9 fi%k. 10 of 10