ML20202J323
| ML20202J323 | |
| Person / Time | |
|---|---|
| Site: | Comanche Peak  |
| Issue date: | 12/17/1985 |
| From: | Hansel J, Ross G EVALUATION RESEARCH CORP. |
| To: | |
| Shared Package | |
| ML20202J051 | List:
|
| References | |
| CPP-004, CPP-4, NUDOCS 8607170059 | |
| Download: ML20202J323 (11) | |
Text
s Paga 1 of 5 EVALUATION RESEARCH CORPORATION I
COMTROLLED COM com@t *#
COMANCHE PEAK RESPONSE TEAM PROJECT PROCEDURE FOR QA/QC ISSUE-SPECIFIC ACTION PLANS PROCEDURE NO: CPP-004 REVISION: 2 ISSUE DATE: 12/17/85 PROJECT WORKING FILES q
e Prepared by: Date: /2!/)
Approved by: . Date: /M'/[~7[
On-Site QA Representative Approved by: Date: /1 (, 81~
c R. vie.1e_ t.. der - ,
= = m.
A PDR
CPP-004 Revision: 2
'( ) 1.0 PURPOSE To establish the methods and responsibilities for the management of QA/QC Review Team records. Specifically, this procedure provides the method to identify, collect, index, and maintain project I records.- It also provides for the establishment, control, and turnover of Project Working Files to the Comanche Peak Response Team (CPRT) Project Central File.
2.0 APPLICABILITY This procedure applies to the documents required to be turned over to the Comanche Peak Response Team (CPRT) Project Central File.
~
3.0 REFERENCES
None 4.0 GENERAL 4.1 Responsibilities 4.1.1 The Records Administrator has overall responsibility for the identification and collection of project O records, the establishment of the Project Working Files and their subsequent turnover of documentation to the Project Central File.
4.1.2 Issue Coordinators are responsible for the collection, filing, and maintenance of documentation under their control.
4.2 Policy 4.2.1 Project Working File records shall be legible, in good physical condition, and complete.
4.2.2 Alterations to approved QA/QC Review Team records by means of white-out, correction tape, scribbling-out information, marking over data, etc. , are prohibited.
Revisions to complete QA/QC Review Team records shall be in accordance with applicable procedures.
Otherwise, corrections shall be made by lining-out the information, making the correction, then initialing and dating near the correction.
Changes to approved documents shall be reviewed and approved by the same organization / discipline that performed the original review and approval.
O 2
e CPP-004
- Revision: 2 t-(~') 4.2.3. Pertinent documentation /information shall not be added ,
/ to the reverse side of a QA/QC Review Team record. !
Additional sheets may be used to provide any l supplemental information. The continuation sheets I shall reference the document to which it is attached, y and be controlled to the same requirements as that !
document.
4.2.4 The use of felt tip pens, or markers to highlight or color code QA/QC Review Team records is normally unacceptable and should be avoided. Felt tip pen ink is usually soluble and highlighting may obscure the material during reproduction.
4.3 Definition 4.3.1 Project Working File A collection of records received or generated as a result of QA/QC Review Team activities which contains l all material, or references to material in other controlled files upon which the conclusions of Action
., Plan Results Reports and/or the Final Results Report l are based.
I\
J 5.0 PROCEDURE The activities described in Sections 5.2, 5.3, and 5.4 are performed by the responsible QA/QC Issue Coordinator / Supervisor for l records under their control.
5.1 Identification of QA/QC Review Team Records The Records Administrator shall establish and maintain a Records File Index (Attachment 6.1) for each Project Working File and review issued CPRT Project Procedures (CPPs), Quality Instructions and Issue Specific Action Plans (ISAPs) for impact on the Action Plan Indexes, then upgrade the indexes as necessary.
5.2 Collection of Records 5.2.1 QA/QC Review Team members shall forward QA/QC Review Team Records to the Records Administrator as required by applicable CPP's.
5.2.2 CPSES controlled documents may be included in the Project Working File by copy, or by reference which includes the document name, number and revision.
NOTE: It is acceptable to copy only the appropriate O' pages from the sources by clearly marking the description of the source on the excerpted pages and including them in the Project Working File.
3
CPP-004 Revision: 2 i Should copies of excerpted CPSES documents be included in the Project Working File, a Document Excerpt Cover Sheet (Attachment 6.2) shall also be prepared.
[
5.3 Receipt of Documentation for Project Working Files i 5.3.1 The Records Administrator shall review each document received for filing for physical quality (e.g.,
reproducibility, legibility, condition) and completeness (e.g., number, file location, sequence of attachments, etc.).
5.3.2 The Records Administrator shall coordinate with the t appropriate QA/QC Review Team personnel to correct any deficiencies in the physical quality and completeness of the records.
5.3.3 Upon completion of satisfactory review, the Records Administrator shall log the document received on the appropriate File Content Log (Attachment 6.3).
Should a document be applicable to more than one ISAP,
., separate copies are placed in applicable file locations. Otherwise the documents are filed in one l
location and cross-referenced on a File Content Log reserved for that purpose.
1 O 5.3.4 The Records Administrator shall file documents consistent with the assigned File Index numbers.
l 5.4 Maintenance and Control of Project Working Files 1
The Records Administrator shall maintain and control the Project Working Files as follows:
Restrict access to the files.
Ensure that an "Out Card" is completed and filed in place of each document borrowed from the Project Working File.
Ensure the timely return of all borrowed records to the
- files and their completeness.
Ensure that the Project Working Files are secured at
! the end of each workday or when unattended.
! 5.5 Turnover of Project Working Files to CPRT Project Central l
Files The Project Working File for each Action Plan shall be
()
transmitted to the CPRT Project Central File within 5 working days after the SRT approved the Results Report for the Issue-Specific Action Plan. Issue Coordinators shall advise the Records Administrator of Results Reports approved by the SRT.
4
CPP-004 Revision: I As applicable, other Project Working Files, e.g., the l f) Certification and Qualification files maintained by the QA/QC Certification Administrator, are transmitted to the CPRT Project Central File within 5 working days after the SRT approved the Final Results Report. The QA/QC Review Team Leader shall advise the Records Administrator and other appropriate QA/QC Review Team members, e.g., the QA/QC Certification Administrator, when the Final Results Report is approved by the SRT.
5.5.1 Prior to the records turnover, the responsible QA/QC Review Team personnel shall review the file to ensure
! that all records needed to support the reports are included and that all of the documents have a specific 4
relationship with the activity involved with completing the QA/QC activity.
I 5.5.2 Prior to Turnover, the Issue Coordinator should
- complete a Document Use Coding Sheet (Attachment 6.4)
' for each document or group of documents within a Project Working File to ensure their applicability to the specific ISAP and its completion.
! 5.5.3 Upon notification from and with the responsible QA/QC t
Review Team personnel, the Records Administrator shall review the files to ensure that they are orderly and complete, then complete the OA/QC Review Team Records Turnover Index (Attachment 6.5) as required.
4 i 5.5.4 Finally, the Records Administrator prepares a letter to transmit the complete Project Working File to the
- custodian of the Project Central File and obtains l
. acknowledgemer.t of receipt.
)
6.0 ATTACHMENTS 6.1 QA/QC Review Team Records File Index (Sample) 6.2 Document Excerpt Cover Sheet (Sample) 6.3 File Content Log (Sample)
I
. 6.4 Document Use Coding Sheet i 6.5 QA/QC Review Team Records Turnover Index (Sample) r
- O 5
i
Attachnent 6.1 l CPP-004 Revision: 2 Page 1 of 1
) QA/QC REVIEW TEAM RECORDS FILES INDEX f (Sample Page)
Y Primary Prefix File # Subfile # Content VII.b.2 1 1A Action Plan IB Issued Plans VII.b.2 2 Qualifications and Training of Personnel VII.b.2 3 Specific Procedures VII.b.2 4 Calculations and Evaluations 4A Calculations 4B Engineering Evaluations 4C Root Cause and Generic Implications Evaluations
, 4D Evaluations of Safety Significance O
VII.b.2 5 Inspections SA Inspection Procedures SB Certifications of Inspection Personnel SC Inspection Results Documentation VII.b.2 6 Testing 6A Testing Procedures 6B Certifications of Testing Personnel 6C Test Results Documentation VII.b.2 7 Records Reviews 7A Review Procedures (Including Sampling) 7B Review Results Documentation VII.b.2 8 Results Reports O
Attrchment 6.2
- CPP-004 Revision: 2 Page 1 of 1 DOCUMENT EXCERPT COVER SHEET I
L Doct' MENT EXCERPT COVER SHEET The attached is an excerpt from the following document:
Title:
Document Number
- Revisinnt Date of revistent Source of document (DCC. CPRT Library, etc.
Date obtained from sources A y 1he above is the latest visto o th controlled document The above ie not the c nt tes ton of the controlled
- document. However. It 9 - appropriate revision for analyzing the re u tar 'e 9 feature (s) for which it was uned.
rages or sheet numb a > e in the excarpt:
O
Attcchment 6.3
- CPP-004 Revision: 2 Page 1 of 1
~ ,r's U FILE CONTENT LOG f
5 U
E M
\l g v>
c n
%9 u <s x<>i le < NS :
aa s
s , s N'% )N > !
$ kh
\<f
(<>
\7~
GD
=
h N
i, G
Attscheent 6.4
.- CPP-004 Revision: 2 Page 1 of 2 O
DOCUMENT USE CODING SHEET This sheet or its equivalent is to be used to indicate how a document or group of documents pertain to the respective Action Plan.
ACTION PLAN NUMBER: Applicable Section:
The attached document (s) were used in completing the above Action Plan in the following way:
Provided engineering or construction details used in the implementation of the Action Plan.
Examples: Controlled drawings, specifications, or procedures Served as randomly selected samples used to determine the a
adequacy of the design, construction or conformance to a procedure.
Examples: Construction records, as-builts drawings, design documents Provided the basis against which the design or construction was inspected or tested.
Examples: Design criteria (FSAR), design specifications, design drawings, design or construction procedures, codes or standards (ASTM, ACI, IEEE, etc.)
Document the completion of an inspection or test conducted in conformance with thw Action Plan.
Examples: CPRT QA/QC inspection reports, independent testing, contractor test records.
Document calculations performed as part of the Action Plan to check or verify the adequacy of the design or to check existing CPSES calculations.
Examples: Cal.:21ations performed by CPRT personnel Used to establish the population from which random samples were selected.
Examples: Lists of documents or CPSES elements (conduits, concrete placements, pipe hangers, etc.) which comprise the population.
Document the communication among the participants in the O Action Plan.
Examples: Letters, Memoranda, Telephone notes, Meeting notes
4 Atttchment 6.4 CPP-004 Revision: 2 A
d DOCUMENT USE CODING SHEET (Example)
(Cont'd)
Summarize the results of the inspections and test conducted in conformance with the Action Plan.
Examples: Lists that correlate data from several sources Provide as-built information analyzed for conformance with design documents.
Examples: As-built drawings or sketches developed by the CPSES project team, photographs or video tapes Other:
o O
O 2
a Att chment 6.5 CPP-004 Revision: 2 Page 1 of 1 v
QA/QC REVIEW TEAM RECORDS TURNOVER INDEX B
UE
- s ud 5$ ^
r e
(N(D *p k
o_ s
- 9) f 38 e
e
$h $5 1 k<h li:
3:
3
- AQ\
s >
os /,\ q\>
\%N (L\f )
m<s G
E ta
' s C) o