ML20134A773
Text
.
PROJECT INSTRUCTION PI 3201. 001
SUBJECT:
Engineering tvaiuation Preparation and Control i
REV.: 3 DATE: 7/15/83 n
PREPARI APPROVED BY-
/
PAGE I of 8 l.0 GENERAL 1.1 Purpose The purpose of this instruction is to establish the requirements for i
preparation and control of engineering evoluotions required for the Midland Independent Design and Construction Verification (IDCV)
Program.
l.2 Scope Engineering evoluotions are the principal means of documenting the IDCV review process and the bases for conclusions. As o minimum, at least one engineering evoluotion shall be required for each topic within the scope of the program. It may be necessary to have several supporting engineering evolvations serving as input to the final 3
resolution of a particular topic. The scope of individual engineering evaluations and the combinations of engineering evoluotions which form the basis of the final report depend upon the technical scope which is appropriate for the particular topic and review crea and the crea of expertise of the assigned individuals. As a minimum, each engineering evoluotion shall clearly indicate the topics and review creas within its scope. The Project Manager and the Design and Construction Verification Managers shall be jointly responsible for assuring that all reviews are appropriately documented in engineering evoluotions.
8508150415 850703 F0 / A-SM93 PDR FDIA LEIGHTOB4-293 PDR
e PROJECT INSTRUCTION PI 3201.
001
SUBJECT:
Engineering Evaiuation Preparation and Control REV.: 3 DATE: 7/15/83 PREP APPROVED BY:
p PAGE la of 8 2.0 PREPARATION Evoluotions shall be complete and orderly and shall include sufficient sketches, notes, and explanatory information to allow any person not f amiliar with the work, but technically qualified, to understand it without extensive additional inquiry and research. Collectively, these documents should be sufficiently detailed so that a qualified engineer who is unassoci-oted with the project could write the final report using only these inputs.
PROJECT INSTRUCTION
~
PI 3201.
001
SUBJECT:
Engineering tvaiuation Preparation and Control REV.: 3 DATE: 7/15/83 b
D j APPROVED BY:
/
2 8
PREPAREQw a 1's &(L x
c
-n-PAGE of
, u -
Engineering evoluotions are the principal means not only of documenting 3
the bases of the conclusions but of collectively providing the required history necessary to support on auditable review process. Thus, special requirements and guidance are laid forth below for their preparation and content.
2.1 Engineering Evaluation Cover Sheet An Engineering Evaluation Cover Sheet (Attachment A) shall be completed considering the following specific guidance.
While the title indicates the general subject of the evaluation, the entries for
" primary" and " supporting" and topic number and title will more specifically define the evaluation. The block for " purpose" should be used to describe the specific purpose of supporting evaluations. The purpose of primary evaluations is defined in this procedure. The
" contents" checklist is provided for guidance to the originator and as a convenient overview of the contents.
These categories are described below.
l 2.2 Abstract l
An obstract of one page or less should summarize the evaluation and its major conclusions, as well as identify related topics and refer to 3
related OCRs, Findings, and Finding Resolution Reports.
l 2.3 Overview of Review Process l
All engineering evoluotions shall contain on overview of the review process within the scope of the evoluotion. This shall include, as I
1 0
4 PROJECT INSTRUCTION PI 3201. 001
SUBJECT:
Engineering tvaiuation REV.: 3 DATE: 7/15/83 g
PREPARE APPROVED BY:
PAGE 3
of a opplicable, on explanation of the review approach and a chronology of events such as major discussions and meetings, requests for infor-motion, and associated reporting. Supporting evoluotions document the disposition of the review process and sum norize the history of that process to date.
Primary evoluotions document on overall summary of the review process and the ' history of that process as applicable to final topic resolution.
2.4 Bases for Sample Selection in view of the fact that the IDCV does rot include a 100% review of the three systems within the project scope, the program must rely upon sampling. Therefore, sampling selection criterio and imple-mentation is extremely important. It is essential that the bases for sample selection of specific plant components or elements be docu-mented as thoroughly as possible, and include on analysis of the degree to which the selected items meet the sample selection criteria attributes documented in Sections 3.1.2 and 3.2.2 of the Engineering Program Plan. Attachment D outlines the steps in the l
sample selection prccess. This may be completed within this section l
of the engineering evoluotion or in separate engineering evoluotions that broadly oddress sample selection making reference to the primary and supporting evoluotions when appropriate.
I 2.5 Sources of Information and References Sources of information and references shall be listed separately using Attachment B or a similar format. References shall include, when opplicable:
PROJECT INSTRUCTION Pl 3201 001
SUBJECT:
cngineering tveiuation REV.: 3 DATE: 7/15/83 l
g PREPARED APPROVED BY:
PAGE 4
of g
o Originating organization or author o
Document number and date or revision o
Title o
Type of document (specification, drawing, let-ter, etc.)
l3 o
Where/how located (e.g. from records center, Bechtel engineer 'X', calculation file, etc.)
2.6 Background Data Background dato include inputs, assumptions, data, and related engi-neering evaluations, calculations, and computer analyses. Sources of this material and associated references must be identified, os appli-cable.
2.7 Acceptance Criterio Acceptance criterio, upon which checklists and evaluations are based, shall be explicitly stated. These include design criteria contained in the FSAR and regulations or the guidance contained in the Standard Review Plon, Regulctory Guides, industry codes and standards.
2.8 Evoluotion Each evoluotion shall be prepared by performing and documenting a point-by-point comparison of the topic being evaluated using design and construction evaluation checklists os oppropriate. These check-lists shall be developed by the reviewer considering the generic
I PROJECT INSTRUCTION PI 3201,. 001
SUBJECT:
Engineering Evaluation Preparation and Control REV.: 3 DATE: 7/15/83 APPROVED BY: j PREPAR
{
PAGE 5
of 8 checklists issued for each review scope category, the design criteria contained in the FSAR and regulations, and, os applicable, the l3 guidance contained in the Standard Review Plon, Regulatory Guides, industry codes and standards.
Each modified checklist shall be 3
reviewed and opproved by the Lead Technical Reviewer (LTR) and Monoger, Design or Construction Verification before being used by For further discussion of the preparation and use of the reviewer.
design and construction verification checklists see PI-3201-006 and PI-3201-007, respectively. Checklists used in the evoluotion shall always be oppended thereto.
2.9 Conclusions Conclusions as well as the bases for conclusions should be summarized. Conclusions shall be written considering whether there are items which are open items, confirmed items, findings, and resolved findings.
Conclusions for Engineering Evoluotions for Which e
There Were No Findings and No Current items Exist
- The conclusions shall state that the subject matter described on the Engineering Evoluotion Cover Sheet has been reviewed and been found to be consistent with the evoluotion criteria. A summary statement of the bases for this statement shall be included. The conclusions shall otso state that there are no potential open items or open items which remain unresolved and that no findings for the scope of review exist.
I Conclusions for Evoluotions for Which There Are e
Findings or Currently Open items - The conclusions shall state that the subject matter described on the Engineering Evoluotion Cover Sheet has been reviewed and found to be consistent with the evoluotion criterio except as documented in l
PROJECT INSTRUCTION PI 3201. 001 SUMCT-Eng.ineering Evaluation eparati n and control REV.: 3 DATE: 7/15/83 PREPARg -
APPROVED BY:
PAGE Sa og 8 J
referenced OCRs and Findings. The conclusion shall further state that the engineering evoluotion shall be considered complete by the issuance of Resolved item Reports or Finding Resolution Reports. The Engineering Evoluotion may be revised in accordance with Section 5.0 of this Project instruction offer these reports are issued if deemed appropriate by the Project Manager.
3.0 VERIFICATION AND APPROVAL 3.1 Engineering evaluations shall be designated as preliminary until 3
approved by the Managers, Design and Construction Verification, the Project Manager or his designated representative.
Preliminary evaluations not upgraded to final status shall be maintained in a 3
separate file for reference purposes.
}
PROJECT INSTRUCTION PI 3201.
001
SUBJECT:
Engineering tvaluation REV.: 3 DATE: 7/15/B3 g
PREPARED APPROVED BY:
PAGE 6 of 8
3.2 Eoch final engineering evoluotion shall be verified by the review of on individual who has qualifications at least sufficient to originate the evoluotion. The reviewer shall not be the originator but may be 3
the Project Manager, Managers, Design and Construction Verification or on LTR. After reviewing, the reviewer shall sign and date the engineering evoluotion cover sheet. To provide a basis for future traceability and approval, the extent and method of review shall be clearly described on the Engineering Evoluotion Cover Sheet. Any comments shall be resolved with the originator prior to signoff.
3 3.3 The Managers, Design and Construction Verification, the Project Manager, or his designated representative shall indicate opproval by signing only the cover sheet when the evoluotion and its review have been completed.
4.0 DOCUMENT CONTROL 4.1 Identification Af ter all approvals have been obtained, the final engineering evolu-otion shall be assigned a control identification number by the Project i
Manager or his designated representative in the following format:
l 3201-001-XXX l
JL JL JL Sequence Number
- Subject File Identifier Project identifier 1
PROJECT INSTRUCTION PI 3201. 001
SUBJECT:
Engineering Evaluation Preparation and Control REV.: 3 DATE: 7/15/83 i
APPROVED BY
}
PREPARED PAGE 7 of 8
To facilitate reference between engineering evoluotion packages, the originator may call the project Administrative Manager in Bethesda, to reserve o Control I.D. No. This number is not final or officially recognized until all approvals have been obtained and the date of revision entered on the Engineering Evoluotion Register (Attachment C).
4.2 Retention 3
Each final engineering evoluotion shall be indexed using the Engineer-ing Evoluotion Register (Attachment C) and filed in the appropriate project engineering evoluotion file. Distribution of originals shall not be made unless specific written instructions are issued to the contrary. All final engineering evoluotions shall be maintained by the Project Manager or his designated representative.
5.0 REVISIONS 5.1 Engineering evoluotions may be revised to clarify misinformatio, (e.g., inputs). Supporting engineering evoluotions will not require revision to update the latest status of the review since these documents do not generally serve as design documents nor os vehicles to document the disposition of the current review process.
To simplify internal control and preserve the history of evolving reviews, new supporting engineering evoluotions should be written as appro-priate. These evoluotions, along with the reporting process docu-mented in PI-3201-008 will collectively provide the required history necessary to support on auditable review process. As discussed, the primary evoluotion will tie all of the supporting evoluotions together.
1' s
r PROJECT INSTRUCTION pl 3201. 001
SUBJECT:
Engineering Evaluation Preparation and Control REW 2 DATE: 4/21/83 l
l APPROVED BY:
,7 PAGE 8 W
8 PREPARED BY:
f1 A#
' ) ett m, /s g
y 5.2 Revisions to final engineering evoluotions shall be made, verified, and approved in the same manner as the original engineering evaluation.
5.3 Supersede'd final engineering evaluations shall either be identified as such on each page or shall be securely bound with at least the cover page so identified. The engineering evaluation register shall note this action by making reference to the new revision of the evaluation. In order to preserve the history of the review process, superseded evaluations shall be maintained in the some file as final evaluations.
6.
GA AUDIT CHECKLIST 6.1 Audits of the implementation of this procedure shall be conducted by the PGAE using Audit Checklist PI-3201-0010A (Attachment D).
0 0
L
j n
ATT ACHMENT A. Pl.3201 0C f. RE V 2 ENGIEERING EVALUATION COVER SKET CONT. ID. NO. 3201-001-TITLE NO. OF SHTS.
PROJECT: CON",UMERS POWER COMPANY MIDLAND IDCV SUPERSEDES ENC. EVAL. NO.
REV. NO, REVISION ORIGINATOR DATE REVIEWED BY DATE APPROVED BY DATE D PRIM ARY EVALUATION O SUPPORTING EVALUATION TOPIC NUMBER TOPIC TITLE METHOD / EXTENT OF REVIEW PURPOSE l
CONTENTS (SEE SECTION 2., PI-3201-001)
O ABSTRACT O OVERVIEW OF REVIEW PROCESS O BASES FOR SAMPLE SELECTION O SOURCES OF INFORM ATION/ REFERENCES O BACKCROUND DATA (INPUTS, ASSUMPTIONS, REL ATED CALCULATIONS)
O ACCEPT ANCE CRITERI A (CODES, ST ANDARDS, FSAR, NRC GUIDANCE, REGULATIONS)
O EVALUATION (DOCUMENT ATION OF REVIEW ACAfNST CHECK LIST,( ACCEPT ANCE CRITERIA)
O CONCLUSIONS TERA CORPORATION
2 V
4 T
f, N
1 EE 00 MP UY 1
CT 02 F E I
O T O
3-A D
P D
(
f T
N I
W E
t C
G V W
A A E OD T
P R T
HE A
O N
N O
O
.D N
I I
T C
A I
T P N M
O O T C RO FN E
I L
F TI O
T SECRUO S
/SECN E
L R
T A
E D
FER V
ER
/
N IOTR AE CB I M FI U TN N
N E
O D
I I
TAU L
/.
A G
VE RO G
R N
GO E
I N H L
T R
I E
TT I
T E
AU NA c N I
i I
G P G I
O N R
T E
O
$OOn UZ l
l
2 e
V 6
E R,
10 0
1 5
0 7
3 I
P.
E 4
C T
T A
N D
EM N
3 H
O f
I C
S I
T V
T E
A R
2 I
R O
ETS I
G ER N
O ITA U
LA E
V I
L T
E T
G N
IR E
EN I
G N
E D
ED E
SW R
EPU S
.O N.
D I
LO<
~.NOC
> 8, ha
r PI-3201-001, Attachment D, Rev. 3 STEPS IN THE SAMPLE SELECTION PROCESS The following steps are to be followed in determining the initial sample selection of AFW, SEP, and CR-HVAC subsystems, components, and structures.
l.
Review of FSAR, P&lDs, Equipment Location and Archi-tectural Drawings, Isometrics, and other pertinent docu-ments to obtain on overview of the functional and physical aspects of the system (s).
2.
Identify subsystems, components, and structures of porti-cular importance to safety. The criteria for design of these items should generally be representative of the other items important to safety to facilitate later extro-polation of results. List these items on the attached table by nome and I.D. in groups or categories according to major disciplines. Identify the type, function, and loco-tion in the oppropriate column.
Mark the column "importance to Safety." Ensure that major design and construction interfaces are included by identifying these in the column " Interfaces" (e.g., Bechtel-vendor (Grinnell) or Bechtel-service contractor (e.g., Cygno).
3.
Assess balance in number within each of these groups of items, and ensure o representative distribution (e.g., type, function, location, et c.).
Modify the sample, either adding or subtracting as appropriate.
4.
Review each group of items by discipline to evoluote diversity of type and function.
Mark the appropriate columns on the table. Modify the sample os appropriate.
5.
Obtain Design Verification, Construction Verification, and Physical Configuration / Testing Verification sompte matrices and take a first cut at identifying items to be reviewed.
Mark oppropriate columns on the matrices.
Note that the Physical Configuration / Testing matrix requires qualifying statements within the matrix to provide o more detailed specification of what is within the sample. Particular ottention should be paid to moin-toining a logical link or chain through the design / con-struction process for individual components selected.
Review for balonce.
r
~
2 6.
Conduct detailed review of drowings to determine the occessibility of the items selected, noting potential physi.
col constroints.
7.
Verify physical constroints vio o cursory field walkdown noting on the ottoched table in the column marked
" Physical Constroint" any areas that are inaccessible and those that may require additional scoffolding.
8.
Review the status of construction completion and any scaffolding requirements with CPC site management and internally determine where these constraints worront a rescheduling of planned activities or resompting to enable physical verification or testing.
At this point, the sample should be opproximately 75% complete.
9.
Obtain input from the Project Manager relative to industry and project design / construction / operating experience to identify any odditional items that should be odded to complete the remaining 25"6 of the sample selection.
Mark the appropriate column labeled
" Experience. industry or project" on the ottoched table to indicate the bases for including the items in the sample. Particular emphasis should be placed on arcos within the project that experienced repeated problems or creas which may not have received extensive prior review. Portions of steps 6 through 8 may need to be repeated; however, less sensitivity to these constroints is acceptable given the importance of this item.
l
F O
y9
.4 em iV
.M.
.hi e
m 2
1 is fiu 5=
b 5
e
-U
.I U
1 W
Y 3
e a
8 t
5 w a s
g e
d C g.
-as 5:o 8a m
Q
_I