ML20199E110

From kanterella
Jump to navigation Jump to search
Draft B,Rev 0 to Guide on Assembly of Project Central & Working Files
ML20199E110
Person / Time
Site: Comanche Peak  Luminant icon.png
Issue date: 02/28/1985
From:
TEXAS UTILITIES ELECTRIC CO. (TU ELECTRIC)
To:
Shared Package
ML20199D912 List: ... further results
References
FOIA-86-36 PROC-850228-02, NUDOCS 8606230187
Download: ML20199E110 (8)
v • d • e


Text

,- *.. .

Cuids on A;:c e bly of DRAFT: 3 Projcct C:ntrol cnd Working Files Revision: 0 02/28/85, Page 1 of 7

,1. 0 PURPOSE

  • This Guide describes an acceptable manner for the assembly of the CPRT Project Central and Working Files. The SRT Support Group and Review Team Leaders may use this Guide or develop an alternative provided that the requirements of the Program Plan are met.

2.0 PROJECT CENTRAL FILE The SRT Support Group should prepare a file index for the Project Central File in accordance with Section 4.0 of this guide. The SRT Support Group will ensure that required documents are placed in the Project Central File. As a minimum the Project Central File will contain:

Copies of each revision of the CPRT Program Plan as submitted to the NRC.

Copies of each revision of Issui-Specific Action Plan as submitted to the NRC.

Copies of Policies, Guides, memoranda and other

  • SRT-originated documents affecting the CPRT.

Copies of each revision of Action Plan Results Reports

( as submitted to the NRC. .

The Project Working File for each completed Issue-Specific Action Plan.

Other information as defined by the SRT and SRT Support Group.

The Project Central File may be divided into as many primary files and subfiles as deemed appropriate by the SRT Support Group. Within each file or subfile a file content log is to be maintained using sequential numbers as defined in Section 4.0 of this guide.

3.0 PROJECT WORKING FILES Each Review Team Leader will prepare a Project Working File for the Issue-specific Action Plans for which he is responsible. A file index is to be Nepared for each Project Working File in accordance with Section 4.0 of this procedure. Each Review Team Leader ensures that required documents are placed in the Project Working File. The Project Working File contains:

The Action Plan for which the file provides documentation including Action Plan revisions.

Personnel gus11fications and training records for personnel as required by the Program Flan. ,.

M.ms-u a ' 9 8 W m' ' ' ' .

n

\ .

Guida cn A cembly of DRAFT: B Project Central and Revisicn: 0 Working Files 02/28/85 Page 2 of 7 3.0 PROJECT WORKING FILES - (Cont'd)

Certification records for inspection and test personnel as required by the Program Plan.

Procedures used in the implementation of the Action Plan including inspection and testing procedures.

Check lists, inspection reports, and other documentation of

,- the results of the implementation of procedures.

Calculations and evaluations including evaluations of root cause, generic implications, and safety significance.

Action Plan Results Report for the Action Plan including any interim or approved preliminary reports.

The above requirements include copies of letters, memoranda, and reports associated with the types of documentation listed above.

The Project Working File contains copies of inspection reports and test data for inspections and tests performed as part of an Action Plan.

~

In general the Project Working File should contain copies of all.

drawings, documents, reports, and other materials relied upon by the Review Team Leader in implementing the Action Plan. Materials

( used in Action Plan implementation and referenced in the Action Plan Results Report or supporting documents, that are excessively bulky (e.g. the FSAR, lengthy computer printouts, large quantities of drawings without CPRT markups) may be excluded from the Project Working File provided that the document can be uniquely identified, is controlled by CPSES procedures, and can be retrieved within a reasonable period. Additionally, documents such as personnel certifications and procedures that affect more than one Action Plan may be placed in the Working File for one Action Plan and referenced in other files. Alternatively the Review Team Leader may establish a single file for documents common to multiple Action Plans. Such a common file may then be referenced by each Action Plan as applicable.

4.0 FILE NUMBERS, FILE INDEX, AND FILE CONTENT LOG Each file (both the Project Central File and the Project Working Files) should have a primary file number and an optional subfile identifier. For Project Working Files a file prefix, identical to the Action Plan number, should be used. The Project Central File and the Project Working Files should have file indexes. Examples of Project Central File primary and subfile numbers organized into a file index are shown in Attachment 5.1. Examples of Project Working File primary and subfile numbers organized into a file index are shown in Accachment 5.2. Each primary or subfile shown

' on the file index contains a file content log. Attachment 5.3 is an example file content log. The file content los contains a sequential number (starting with 1) for each file /subfile and a

.s G

i Guida en Asoc;bly of DRAFT: B Project C:ntrol cnd Working Files Revision: 0 02/28/85, Page 3 of 7 4.0 FILE NUMBERS, FILE INDEX, AND FILE CONTENT LOG - (Cont'd)

{

brief description of the item. Where applicable, drawing numbers, inspection report numbers; etc. should be used in the file content log to adequately identify the item. The file number and content

  • log sequential number are to be placed on the first page of each document contained in the files. Attachment 5.4 provides the format for these numbers.

. (NOTE: The example file indexes do not illustrate use of the alternative of a common file for material applicable to multiple Action Plans within a Review Team Leader's scope.)

5.0 ATTACRMENTS 5.1 Example File Index for Project Central File 5.2 Example File Index for Project Working File 5.3 Example File Content tog 5.4 Fo rma t for Document Identification a

O f

4 f

9

, _ _ _ _ _ . _ _ . _ - ._ - - - - ~ ' ' ~ ' ~ '

Grida cn A:sembly cf DRAFT: B Pr2jcce C : tral and Revision: 0 Working Files 02/28/85,-

l Page 4 of 7

{, ATTACHMENT 5.1

  • EXAMPLE FILE INDEX FOR PROJECT CENTRAL FILE PROJECT CENTRAL FILE

, File i Subfile i Content 1 CPRT Program Plan and Action Plans as filed with NRC 2 Correspondence to NRC (re: TRT/CPRT) 3 Correspondence from NRC (re: TRT/CPRT)

! 4 CPRT Policies and Guides 5

Resumes of SRT and Review Team Leaders 6 .

Meeting Minutes and Transcripts 6A SRT Meetings

( 6B Meetings with NRC (transcripts) 6C Other Meetings 7 Action Plan Results Reports 8 Other Reports and Evaluations 9 Miscellaneous 10 Closed Working Files Transferred to Project File 1

i o

4 O

  • _b__._________#______
  • Guid3 en Ass chly of DRAFT: B Projcet Ccntral cnd Revision: 0 Working Files 02/28/85 Page 5'f7 o

ATTACHMENT 5.2 -

EXAMPLE FILE INDEX FOR PROJECT WORKING FILE PROJECT WORKING FILE

. Primary Prefix File # Subfile # Content I.a.1 1 Action Plan I.a.1 2 Qualifications and Training of Personnel I.a.1 3 Specific Procedures I.a.1 4 Calculations and Evaluations 4A Calculations 4B Engineering Evaluations 4C Root Cause and Generic Implications Evaluations 4D Evaluations of Safety Significance I.a.1 5 Inspections SA Inspection Procedures SB Certifications of Inspection Personnel 1

SC Inspection Pasults Documentation I.a.1 6 Testing 6A Testing Procedures 6B Certifications of Testing Personnel 6C Test Results Documentation I.a.1 7 Records Reviews 7A Review Procedures (including sampling) 78 Review Results Documentation I.a.1 8 Results Reports i

I.a.1 9 Niscellaneous (including references not  ;

generally avaiJable ,

. , I o_ . . .

1

Guids en Assembly of DRAFT: B Projcet Centrel and Rsvision: 0 Working Files 02/28/85 Page 6'of 7 ATTACHMENT 5.3 -

[.

EXAMPLE FILE CONTENT LOG FILE CONTENT LOG

. PREFIX: FILE: SUBFILE: -

Log Number Description 1

2 3

4

(

.i ~

e 6

.,b Guida en As embly of DRAFT: B Pr:j;ct Ccntral cnd Revision: 0 Working Files 02/28/85, Page 7 of 7

[ ATTACHMENT 5.4 ,

FORMAT FOR DOCUMENT IDENTIFICATION NUMBERS PROJECT CENTRAL FILE DOCUMENTS N A . nnn

~~

sequential number (from file content log) optional alphabetic character for subfile identification file number (from file index)

Examples:

1.003 4.017 6A.027 6C.153 l

PROJECT WORKING FILE DOCUMENTS X.x.n - N A . nnn -

sequential number (from file content log) optional alphabetic character for subfile identification file number (from file index) file prefix (identical to TRT issue number)

Examples:

I.a.1 -

1.003 I.c - 4A.017 II.b -

8.001 III.a.2 - 4B.003

... e , ,

(

0FFICE MEMORANDUM TO: Review Team Leaders SRT Support Group FROM: ' Senior Review Team DATE: January 30, 1985

SUBJECT:

Guide on Central and Working Files The attached is a guide for the assembly of the Project Central and Working Files that are required by the Program Plan. As stated in the Program Plan the SRT Support Group is responsible for the Central File. Review Team Lsaders are responsible for establishing a Working File for each Action Plan. The attached guide presents an acceptable manner for those files to b2 assembled. Review Team Leaders and the SRT Support Group may use this guide or develop alternatives to suit their needs provided that Program Plan requirements are met.

9 9

S S +

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