ML20140F840

From kanterella
Jump to navigation Jump to search
Rev 1 to Project File Index
ML20140F840
Person / Time
Site: Millstone Dominion icon.png
Issue date: 04/28/1997
From: Neri A
SARGENT & LUNDY, INC.
To:
Shared Package
ML20140F736 List:
References
PI-MP3-12, NUDOCS 9705050363
Download: ML20140F840 (4)
v • d • e


Text

- - . - - . . - .- -_- . . .

PROJECT

~

INSTRUCTION PI-MP3-12 INSTRUCTION .

REV.1 E

Client: Northeast Utilities Staflon: Millstone Unit 3

Title:

PROJECT FILE INDEX

! .. E' f elated Non-Safety-Related i

i j i

i i

j Reviewed By: Approved By:

I System Lead Programmatic O&M Lead Accident QA Engineer Intemal Review Verification Team Lead Mitigation Committee Manager Lead Chairman I '

. - 4 . _ _ .

/ , Date: Y'A )

NANaA Ykb $ 90 $$bl15 f$bA: hd &W &% ~

(/

~

]

Description (/ W / f Rev.1 Revised Attachment 7.2 f

Page 1 of 4 l 9705050363 970429 PDR ADOCK 05000423

, p P DR

l r

PROJECT "~

INSTRUCTION PI-MP3-12 I INSTRUCTION .

REV.1

{ 1.0 PURPOSE i

i This project instruction supp!ement9 S&L Procedure GQ-6.01 for the implementation of the Project File !.$dex for the Northeast Utilities Millstone Unit

} 3 Independent Corrective Action Verification Program (ICAVP).

d j

)

n 2.0 REFERENCE i

2.1

[

i GQ-6.01, " Project Distribution List and Project File Indexes."

2.2 GOP 17.02, " Quality Assurance Records Control System" 3.0 DEFINITIONS

3.1 Project File index - A project file index is a listing of document categories

! with location referencee for the wntral consolidated project file.

3.2 Central Consolidated Project Files - Central consolidated project files i

include documents pertaining to a project or group of projects for a single l client and are maintained by a project team, usur.lly under the direction of j

the Project Manager or his designee. Central consolidated project files

!- are interdepartmental and are the source fram which the Records Center

} receives documents for long-term st0: age.  ;

3.3 Project Documents - Project documents are defined in the applicable j project instructions. Examples of these documents are listed on Attachment 7.1.

3.4 Internal Project Correspondence - Internal project correspondence

includes documents generated within S&L which are not distributed j outside of S&L Internal project correspondence includes, but is not j limited to, the documents listed in Attachment 7.1.

i

{ 3.5 External Project Correspondence - External project correspondence

' includes documents generated within S&L and distributed outside of S&L, as well as documents generated outside of S&L. External project

[ correspondence includes, but is not limited to, the documents listed in i

Attachment 7.1.

!O ;

i 1

Page 2 of 4 l

.-,y

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

1_

1 t'

! PROJECT " " '

INSTRUCTION Pl-MP3-12 INSTRUCTION REV.1

) 3.6 Special Project Documents - Some project documents, such as purchase orders and contracts are normally filed with the Project Manager i rather than the central consolidated project file. Files containing these j

documents are considered part of the central consolidated project file and i shall be referenced in the project file index.

I i

j 4.0 RESPONSIBILITIES 4.1 The Verification Team (VT) Manager shall be responsible for establishing the central consolidated project file, and ensuring the transmittal to file of documents per Subsection 5.2.1.

L 4.2. Verification Team (VT) Group Leads shall be responsible for ensuring the transmittal to file of documents per Subsection 5.3.

1 <

l '

i 5.0 PROCEDURE

( ,

! 5.1 The VT Manager shall establish a central consolidated project file for I j the filing of documents.

?

] 5.2 Project documents shall be filed in the central consolidated project file i

in accordance with the project file index (Attachment 7.2). There are two general categories of project docue ents - generic project j

documents and task-specific documents.

5.2.1 The project file index contains the subcategories of the files for the generic project documents. It also indicates the person responsible l for sending each subcategory of document to the central consolidated project File.

i

! 5.2.2 Task-specific documents shall be filed by Verification Team identity, i

Verification element (system or program) and applicable review j

checklist. The project file index lists the subcategories and l responsibilities.

j 5.3 All project personnel shall clearly indicate the appropriate project file j number from the index when submitting documents to the central

] consolidated project file. The DPD personnel assigned to maintain the central consolidated project file shall file the documents j chronologically in appropriate subcategory of the file system. If there

! i

Page 3 of 4 l

.- ,. ~

L 1 4

PROJECT ""

INSTRUCTION PI-MP3-12 INSTRUCTION REV.1

) are questions about the file number or no file number is shown, the j DPD personnel shall resolve this with the person submitting the

document or their supervisor. ,

i '

' 5.4 Project documents shall be submitted to the project file as soon as possible after receipt / issue to keep the files current. Project personnel

' may keep working files in their own work areas as necessary in the performance of their work. The use and number of working files should be minimized. The individual is responsible for ensuring that

{

l the documents in the working file are current before relying upon them '

l for quality related decisions.

1 5.5 External project correspondence shall be filed in two places. [ Note:

l This is the only instance of permanent duplicate files on the project.]

} A copy of the correspondence should be filed under generic project j files, and a copy should also be filed under the task-specific file when i related to a task. The recipient, or addressee, is responsible for i

' directing incoming external correspondence to the generic file and the task-specific file. The person signing the external correspondence is j responsible for submitting outgoing correspondence to the generic j

project file and to the task-specific files. '

i 3 5.6 A submittal schedule for QA records which shall be retained by S&L i

shall be ' developed in accordance with procedure GQ-17.01. These j records shall be transmitted to storage in accordance with procedure

! GQ-17.02. Project-related documents which are not QA records shall i not be sent to storage until the project has been completed and the j transmittal has been authorized by the VT Manager."

l

} 6.0 REVISIONS

. The project file index (Attachment 7.2) may be revised by the VT Manager. The i

issue of a new or revised project file index shall not require retraining in this Pl

! unless the VT Manager determines that, in a particular case, retraining is necessary.

l

[ 7.0 ATTACHMENTS 1

1

< O 7.1 7.2 Types of project-related documents (1 page)

Project File index (2 pages) i i I Page 4 of 4 l l

PI-MP3-12 v/ Rev.1l Attachment 7.1 TYPES OF PROJECT-RELATED DOCUMENTS INTERNAL PROJECT CORRESPONDENCE e Interoffice Memoranda e Meeting Notes

  • Internal Status Reports Internal Schedules, Lists, Estimates, and Budgets
  • Internal hand-written or PC-generated Documents e Telephone Memoranda Issued Internally EXTERNAL PROJECT CORRESPONDENCE
  • Correspo.3dence sent to S&L by Northeast Utilities , NRC and Others Correspondence sent by S&L to Northeast Utilities, NRC and Others e Notes ofmeetings between S&L and Northeast Utilities, NRC and Others e Schedules or Status Reports
  • Telephone memoranda issued externally PROJECT DOCUMENTS  !
  • DiscrepancyReports
  • System Review Checklists e Modification Review Checklists O&M&T Review Checklists
  • Programmatic Review Checklists
  • Accident Mitigation Review Checklists
  • Walkdown Checklists
  • Project Instructions e Final Report O

l (q) PI-MP3-12 Rev.1l l Attachment 7.2 MILLSTONE UNIT 3 ICAVP PROJECT FILE INDEX I

1. GENERIC PROJECT FILES File No Iitle Position Title Responsible for Submitting - Project Files i MP3-1.0 Contract and Supplements VT Mamger MP3-1,1 CommercialCorrespondence VT Manager  :

MP3-1.2 ICAVP Requirements VT Manager {

MP3-1.3 Public Meeting Materials & Notes VT Manager l l 1

MP3-2.0 Project Manual VT Manager MP3-2.1 Training Records VT Manager MP3-2.2 PersonnelIssues -Conflict of VT Manager Interest Statement MP3-3.0 Status Reports VT Manager MP3-4.0 General Quality Assurance Auditor MP3-4.1 Internal Audits Auditor i

MP3-4.2 External Audits Auditor MP3-5.0 Project Team Meeting Notes VT Manager MP3-5.1 Other Internal Meeting Notes VT Group Lead MP3-5.2 External Project Meeting Notes VT Manager (Not Specific to a Task)

MP3-6.0 Manpower Planning and Overall VT Manager Project Schedules MP3-7.0 External Correspondence to NU or NRC VT Manager MP3-8.0 Correspondence from NU or NRC VT Manager MP3-9.0 Discrepancy Reports VT Manager MP3-10.0 Differing ProfessionalOpinions VT Manager Page 1 of 2

l p).

( PI-MP3-12 Rev.1l Attachment 7.2 MILLSTONE UNIT 3ICAVP PROJECT FILE INDEX II. TASK-SPECIFIC PROJECT FILES File No Iitle Position Title Responsible for Submittina - Project Files SRG-XXX-YY-ZZ System Review Files SRG Lead CRG-XXX-YY-ZZ Configuration Review Files SRG Lead ORG-XXX-YY-ZZ O&M&TReviewFiles ORG Lead N ARG-XXX-YY-ZZ Accident Mitigation Review Files (O ARG Lead PRG-AAA-YY-ZZ Programmatic Review Files PRG Lead Where: XXX = 3 Letter System Designator Assigned by ARG or SRG Lead.

YY-ZZ = Last 4 Digits ofChecklist Number (Example: Use 02-01 for CK-MP3-02-01)

AAA = 3 Letter Program Designator Assigned by PRG Page 2 of 2

'O

Retrieved from "https://kanterella.com/w/index.php?title=ML20140F840&oldid=2860259"