ML17054B539
| ML17054B539 | |
| Person / Time | |
|---|---|
| Site: | Nine Mile Point  |
| Issue date: | 03/19/1985 |
| From: | NIAGARA MOHAWK POWER CORP. |
| To: | |
| Shared Package | |
| ML17054B538 | List: |
| References | |
| PROC-850319, NUDOCS 8504090159 | |
| Download: ML17054B539 (30) | |
Text
~4 k)d"l 6e't ~
ee'i')
" He.'e fi e i "',>>'iC4.'*'"'"."" <<,:.e'4e<<">> '~'fA ieee>> i 0 e i" 4, <>id</ ".i'(e4 ei 4 4i',4~ '..de@-.;i r.i e>>>>e"
%; >',j" ".e
~ ~
3/19/S5 OVERALL AUDIT PLAN QUALITY ASSURANCE AUDITING DIVISION AUDIT OF AS-CONSTRUCTED CONDITION OF REACTOR CORE ISOLATION COOLING SYSTEM AND ASSOCIATED STRUCTURES NINE MILE POINT 2 PROJECT NIAGARA MOHAWK POWER CORPORATION 8504090159 850403 t
PDR ADOCK 050004i0 A
(
I' I
3/lg/85 PURPOSE The purpose of this audit is to assess the program for control of inspection and construction by evaluating the as-constructed condition of the Reactor Core Isolation Cooling System (ICS) and associated structures and interfaces.
OVERALL SCOPE AND APPROACH The audit will be conducted in conjunction with the EA technical audit and will cover the same system, components and structures.
The systems, components and structures will be reviewed to determine if:
The as-constructed condition reflects the design as shown on drawings and specifications.
As-built documentation used for design verification purposes (e.g.,
as-built piping drawings/isometrics) accurately re-flect the as-built conditions; The audit will encompass review of specific
- areas, equipment and components such as:
~
Piping Components 8 Supports
~
Instrumentation
~
Electrical Equipment, Cable and Raceways
~
Structural Concrete 8 Steel
0 f
3/19/85 The specific areas, equipment and components will be based on input from the EA audit team.
The review will include as appopriate, but is not limited to, verifica-tion of:
Essential equipment/system characteristics (designated by EA audit
, team)
~
As built configuration utilized in design verification
~
Adequacy of welded and mechanical joints
~
Location, orientation and configuration
~
Cable routing and termination
~
Separation and clearances Above verifications will normally be based on physical review of the installation.
Where this is not possible documentation will be utilized.
Tentative schedule (see Attachment 1)
I
3/19/85 AUDIT TEAM The team will function under the direction of SWEC guality Assurance Auditing Division Boston.
The team will be composed of Niagara Mohawk Power Corporation and SWEC personnel.
The team members will be certified auditors with experience in the installation and/or inspection activ-ities to be audited.
The SWEC personnel will have not been associated with the project other than to audit it.
(See Attachment 2)
PREPARATION
~
Review applicable construction and inspection procedures and gen-eral installation specifications.
~
Review scoping information (identification of system boundaries, components, structures) package from EA audit team and the specific applicable installation instructions.
~
Develop detail audit plans.
~
Based on supplemental information from EA audit team (key drawing and specification requirements) finalize detail audit plans.
PERFORMANCE
~
Audit plans shall be utilized during the audit as a guideline to ensure all necessary activities are reviewed and as the principal method or collecting the audit results.
3/19/85
~
Incomplete installation will be noted and controls on remaining work evaluated for impact on audit results.
~
During the performance of the audit the audit team will inform the project of potential concerns or requests to provide needed information using an "Action Item" form (See ).
The project will be expected to promptly respond to each "Action Item" providing the information requested or a response to the potential concern.
These "Action Items" will be tracked.
~
Hardware deficiencies identified will be documented on an unsatis-factory Inspection Report
( IR) or Nonconformance and Disposition Report (NED) as appropriate.
Periodic status meetings will be held between the audit team
- leader, gA, gC and Construction to discuss the progress of the audit and the status of any open action items.
~
Engineering concerns wi 11 be turned over to EA team for in-vestigation, reporting, follow-up as appropriate.
~
gAAD audit team will investigate, report and follow-up gC/Con-struction concerns turned over to gAAD by EA team.
REPORTING A post audit conference will be held at the end of the audit to discuss the findings with the management of the audited organizations.
\\
3/lg/85 The audit report will be structured as indicated.
~
Purpose
~
Scope
~
Overall Conclusions An attachment containing for each discipline:
~
A summary description of the scope extent, findings and conclusions of the audit of each discipline.
~
Numbered observations discussing in detail any findings requiring further investigation, corrective or preventive action.
3/19/85 ATTACHMENT 1 TENTATIVE SCHEDULE Obtain scoping information package from EA audit team, establish gA team.
4/1/85 Begin audit preparation:
define scope, develop audit plans 4/15/85-4/26/85 Obtain supplemental information from EA audit team (key drawing and specification requirements) and refine detail audit plans.
4/29/85-5/3/85 NRC review of scope and audit plans 4/29/85-5/3/85 Audit Start 5/6/85 NRC Review of Implementation Audit Completion 5/17/85 Exit Meeting 5/17/85 Audit Report Issue 7/19/85 NRC Review of Reports
0 F
I
3/19/85 ATTACHMENT 2 TEAM MEMBERS AUDIT AREA/ACTIVITY NAME Piping Components and Supports Instrumentation II Electrical Equipment, Cable and Raceways Structural Concrete and Steel Nondestructive Examination
'h
3/19/85 ATTACHMENT 3 GENERATION OF ACTION ITEMS An Action Item can be generated to identify deficiencies or to request information.
It is difficult to define precise criteria to apply in determining if an Action Item should be generated.
Three considerations are:
significance of individual discrepancies, number of discrepancies, and the urgency of needed information by the evaluation team member.
An Action item is to be written when one or more of the following needs exist:
1.
Need to identify a technical, construction or inspection concern.
2.
Need to identify a potential concern and there is no information readily available to substantiate or alleviate the concern.
3.
Need to identify a significant program aspect or practice that is, or appears to be, incorrect or inadequate.
4.
When it is deemed necessary for the project to investigate to determine cause and extent of discrepancies.
5.
When it is deemed appropriate to evaluate the project's proposed actions to correct discrepancies and prevent recurrence.
II'
3/1 9/85 It is generally not necessary to generate an Action Item if a minor discrepancy is observed and the discrepancy appears to be isolated or random.
Several minor discrepancies,
- however, would generate an Action Item.
NOTES 1.
Detailed observed Item was decision based on fairness Audit Plans (Check Lists) must indicate all discrepancies regardless of significance or number and even if an Action not generated.
The Audit Team Leader will make the final for when an Action Item is written.
His decision will be the above written guidance, as well as, objectivity and to the issue in question at that time.
2.
Generation of, and obtaining a response to, an Action Item does not necessarily negate the need for an Audit Observation.
ACTION ITEM NO.
TITLE/
SUBJECT:
TEAM MEMBER POTENTIAL CONCERN/ UESTION ACTION ITEM REV.
DATE:
DISCIPLINE:
PROJECT REPRESENTATIVE:
Page I of
0
p 4 <<4
~
E 8>> 4 b (I I
4 A&4,147 N'%WE.,'L441 REV.
PROJECT RESPONSE
- 0 0
Response
should be provided within 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> if possible.
Prospect should provide any specific information that is requested or any other information the Project may have that could alleviate the concern.
Each of the following items should be specifically addressed in the response if it is determined that a concern exists:
l.
2 ~
3.
4 ~
5 ~
Probable root cause as to why the concern exists.
Extent of concern, and how determined, should be stated and if bounded why it is bounded should be stated.
Action necessary to correct concern, including date when action will be completed.
Action necessary to prevent recurrence, including date when action will be implemented.
Significance of concern and basis of significance.
CAUSE:
EXTENT:
ACTION TO CORRECT:
DATE ACTION TO BE COMPLETE ACTION TO PREVENT RECURRENCE:
DATE ACTION TO BE IMPLEMENTED SIGNIFICANCE:
DATE PREPARER:
QA/CONSTRUCTION >
DATE:
or PROJECT ENGINEER
- Include as attachments a copy of all references mentioned in the PROJECT RESPONSE.
Page of
'I
~ 4 f44
~I'0 f'<<<<<<) p<<4 <<L,a<<'<<<<<<
' <<,'."+'4 ~ << '<<)
<'t14v <<<<<<<<
a
<<<<<<<<<<j )p <<)<<)<<',<<<<+ <<V /PE>> ~<<'y <<<<,C...)
~'<<<<>> )","<<<<<<<<g
~
ACTION ITEM N REV.
RESPONSE
EVALUATION This sheet is used to document"%he" eva1uation of the response to verify that a11
'tems are addressed,.
corrective action is commensurate with the concern and the
- extent, and the preventive action is consistent with the identified.,cause.
TEAM MEMBER TEAM LEADER DATE Page of.
0
~'
>>>> i (> ai,>>>1 CS 4>> '4'<
~>> >vf >>>>>> J <<M>>>> w>>>>>>e>>
e
><>> s>>
ACTION ITEM REV.
ADDITIONALREVIEWS AND COMMENTS OF VALID CONCERN 0
0 0
Perform reviev of valid
- concern, project
- response, and team member evaluation of project response.
Provide any additional background information.
Provide concurrence to the resolution of the concern.
DIVISION CHIEF DATE Page of
~
~
ACTION ITEM REV.
FOLLOW-UP ACTION This sheet is used to document auditor follow-up on action items including verification of corrective and preventive actions.
TEAM MEMBER DATE TEAM LEADER DATE Page of
V-
~