ML11242A231
| ML11242A231 | |
| Person / Time | |
|---|---|
| Site: | San Onofre  |
| Issue date: | 11/01/2010 |
| From: | Southern California Edison Co |
| To: | Office of Information Services |
| References | |
| FOIA/PA-2011-0157 | |
| Download: ML11242A231 (8) | |
Text
.,
.E Unit C System Status: ATCO NOCO NOPT
.User Status:
CRTD STA ACRC ENRC SONGS Notification:
NN 201181864 III I
IIIIIIIIIII
==
Description:==
NRC Contact and Questions Created on: 11/01/2010 Reported By:
(b)(6)
Responsible: Lb)_6 i
Priority: 4 Medium Required Start: 12/20/2010 21:34 End: 04/18/2011 21:34 Order No:
Code:
Task Exists?
[Y]
Func.Loc.: S SONGS Equipment:
Assembly:
Quality Class:
Location:
Room:
Elevation:
Column:
Planner Group: Maint I&C WorkCenter: O0OM Manager - Plant Operations Plant: 1000 SONGS - Services Reliability Classification:
ARC Review Status: C Completed Feedback Req'd?
[X]
M Rule:
Sig Level:
4 Low Level Problem, Take Action/Trend Breakdown
[]
Malfunction Start:
Breakdown Duration:
H End:
==
Description:==
11/01/2010 17:59:34 i(b)(6)
Phone (b)(6)
- 1. Problem description Contacted by NRC resident.
The following questions / concerns were directed to the U3 CRS:
Concerning NN 20116801, what is the operability status of 3Y004.
Concerning the requirments for fuel movement, what are the requirements for 1E inverter Operability during refueling and SFP fuel movement.
How LCOs 3.8.8 and 3.8.10 interpretted during the preparation for fuel moves (how do you ensure minimum operability requirements are met (specifically for Invertors, but generically for other required equipment.
The NN 201168011 (affecting 3Y04) indicates that Y04 is
- INOP, an Extent of condition assignement exists, but is not scheduled to start till 11/30/, this doesnt seem tofollow procedural guidance for EOC completion in a timely manner.
- 2. Impact or consequence Informed NRC inspector (after research) that 3Y04 is inoperable.
SRO Print Date: 02/22/2011 Page 1 of 8
S-"
Notification Continued SONGS Notification:
NN 201181864
==
Description:==
NRC Contact and Questions Description Continued:
was unaware of this status.
Informed the NRC that current plant configuration would not be affected for SFP fuel moves, since FHIS would have to be operated in the ISOLATE mode.
Also informed NRC inspector that I was unable to quickly ascertain the configuration during Core Alts.
A reportability assignment should be assigned to assess if TS and LCS requirments were met due core alts (specifically due to equipment configuration and Inoperability).
- 3. Describe what happened See above contact info and support requests, including reportability request.
- 4.
Immediate actions taken Provided above answers, contacted NRA and provided with Email and voice discussion with NRC concerns.
- 5.
Extent of Condition (as applicable)
N/A
- 6.
Cause (if known)
- 7.
Recommended Actions Research and provide requested information to NRC expeditiously.
-- (b)(61 Additions to -Supervisor Review Comments-:
agree (b)(6)
Additions to -6.
Cause (if known)-:
none Additions to -Supervisor Review Comments-:
agree Print Date: 02/22/2011 Page 2 of 8
'"Task Summary SONGS Notification:
NN 201181864 Func.Loc.: S SONGS Location:
Room:
Elevation:
Column:
Task No.:
0001 Task No.:
0002 Code Group:N-SPT General Support Record Short Text: Address NRC concerns Task Code: ST04 SPT Complete WorkCenter: '-PwW4_w.nk Week SRO -4 Responsible (b)(6)y i
Code Group:N-RPT Reportability Assessment Short Text: Evaluate for reportability assessment Task Code: RP65 RPT Complete Not Reportable WorkCenter: R C Requlatory Compliance Responsible: i(b)(6)
Print Date: 02/22/2011 Page 3 of 8 Print Date: 02/22/2011 Page 3 of 8
Trending Worksheet SONGS Notification:
NN 201181864 Func.Loc.: S SONGS Part:
Damage:
Cause:
Activity:
Part:
Damage:
Cause:
Activity:
Part:
Damage:
Cause:
Activity:
Part:
Damage:
Cause:
Activity:
Print Date: 02/22/2011 Page 4 of 8 Print Date: 02/22/2011 Page 4 of 8
Task Details SONGS Notification:
NN 201181864 Func.Loc.: S SONGS Location:
Room:
Elevation:
Column:
Tank nptnilg Task No.:
0001 Code Group: N-SPT General Support Record Short Text: Address NRC concerns Task Code: ST04 SPT Complete WorkCenter: OWW4 Work Week SRO -4 Responsible:
(b)(6)
Status:
TSC C '
Planned Start:.11/3072010 11:57 Planned End: 12/01/2010 Complete: 11/30/2010 11:57 Task Long Text:
Nddress NRC concerns 3PT (General Support Record)
Describe the General support request:
Ihis same issue was raised and resolved in NN 201183395.
Refer to that (b)(6)
Sperations, Equipment Control SRO 11/30/10 Print Date: 02/22/2011 Page 5 of 8
Task Details SONGS Notification:
NN 201181864 Func.Loc.t S SONGS Location:
Room:
Elevation:
Column:
Tank fnatai4a.
Task No.:
0002 Code Group: N-RPT Reportability Assessment Short Text: Evaluate for reportability assessment Task Code: RP65 RPT Complete Not Reportable WorkCenter: R C Regu1atoy Compliance Responsible:['(b)(6)
Status:
TSCO Planned Start: 12/15/2010 Planned End: 12/15/2010 Complete: 12/10/2010 05:47 Task Long Text:
Evaluate for reportability assessment TECHNICAL ASSESSMENT TEMPLATE NOTE:
ENGINEERING JUDGEMENT may be used to answer questions.
However
< (>,<) >
the basis for the judgment needs to be documented to validate the judgment.
For the purposes of determining REPORTABILITY, it is only necessary for the individual responding to these question to identify a single occurrence within the previous three years where the SPECIFIED (SAFETY)
FUNCTION was incapable of being fulfilled (i.e.,
both trains of redundant systems were INOPERABLE OR NON-FUNCTIONAL).
When the requested questions in SECTION 2 are answered, then the assigned individual should reassign the N-RPT to an RP25 status.
ONLY an NRA PQS 270QC7 qualified individual may reassign an N-RPT task to a status RP30 or higher.
SECTION 1 - Initial Reportability Assessment (RP10)
[To be completed by a PQS 270QC7 Qualified Individual.]
Not immediately reportable, this is.a question about plant configuration requirements for refueling.
Unit is currently defueled.
See below, no engineering support required.
Prepared By:
I1 Date: 11-3-10 SECTION 2 - Technical Assessment (RP20)
[The REPORTABILITY ENGINEER will Print Date: 02/22/2011 Page 6 of 8 Print Date: 02/22/2011 Page 6 of B
p.
I"..
Task Details Continued SONGS Notification:
NN 201181864
==
Description:==
NRC Contact and Questions determine which questions are to be answered.]
- 1. Describe the condition being evaluated for reportability:
- 2.
Would the SSC have been able to fulfill all its intended safety function(s) as defined in the UFSAR (reference specific sections) since the failure (Operable)?
Consider all plant operating Modes, mission time, and the status of other equipment.
If yes, why?
- 3.
If the conclusion of step 2 is Yes, mark steps 4, 5 and 6 as #Not Applicable,# document task performance/peer check, advance the Task to RP25 and assign to Reportability Compliance for completion of step 7.
If the conclusion of step 2 is No, complete steps 4, 5 and 6.
- 4.
When did the SSC fail or first become degraded (break, code not met
< (., <)>
out of SR range, etc.)?
If the specific time of failure is not known
< (>,<c) is there any compelling evidence of prior failure?
- 5.
What was the apparent cause of the failure or degraded condition?
(use engineering judgment to determine, if necessary - but also describe the basis for your judgment).
If appropriate, generate a cause evaluation assignment.
- 6.
Did the failure or failure mode affect or potentially affect another SSC or the other unit?
- 7.
[Additional Questions as indicated by the REPORTABILITY ENGINEER.]
Prepared By:
Date:
Peer Reviewer Comments:
Peer Reviewer:
Date:
After the peer review is completed, the Advance the RPT Task to RP25 and assign to Reportability Compliance for completion of step 7.
Print Dates 02/22/2011 Page 7 of 8 Print Date: 02/22/2011 Page 7 of 8
I Task Details Continued SONGS Notification:
NN 201181864
==
Description:==
NRC Contact and Questions SECTION 3 - Compliance Review and Management Approval (RP25 and RP30)
B. Reportability assessment summary (include references as appropriate.
(To be completed by qualified individuals only - see Encode 270QC7:
kssessing Events for Reportability).
got Reportable.
This was an administrative issue raised by NRC inspector enquiring how configuration of the inverters was established.
At the time, there were two inverters in service.
rechnical Specification 3.8.8 "Inverters -
Shutdown," requires operation to support TS 3.8.10 "Distribution Systems--Shutdown."
A review of the Jnit 3 control room log shows inverter Y04 was placed in service on 10/26, and Y03 was placed in service on 10/28.
Two inverters were in service and adequate to support the distribution requirements, therefore no report is required under 50.73(a)(2)(i)(B) "Any operation or zondition which was prohibited by the plant's Technical Specifications,"
Dr 50.73(a) (2) (v) "Any event or condition that could have prevented the fulfillment of the safety function of structures or systems that are needed to:
(A) Shut down the reactor and maintain it in a safe shutdown condition; (B) Remove residual heat; (C) Control the release of radioactive naterial; or (D)
Mitigate the consequences of an accident."
Prepared By:
(b)()
Date:12-9-0
- 1anagement Reviewer Comments: None 4anagement Reviewer:
(b)(6)
Date: 12/10/10 Print Date: 02/22/2011 Page 8 of B