ML12284A445
| ML12284A445 | |
| Person / Time | |
|---|---|
| Site: | Diablo Canyon  |
| Issue date: | 10/16/2012 |
| From: | Joseph Sebrosky Plant Licensing Branch IV |
| To: | |
| Sebrosky J | |
| References | |
| TAC ME7522, TAC ME7523 | |
| Download: ML12284A445 (70) | |
Text
~"I\\ REGU{
UNITED STATES
~~(j"
-iro.,.
NUCLEAR REGULATORY COMMISSION g
~
WASHINGTON, D.C. 20555-0001 of 0
~
~
~
~
~
October 16, 2012
~o
- i' LICENSEE:
Pacific Gas and Electric Company FACILITY:
Diablo Canyon Power Plant, Unit Nos. 1 and 2 SUB~IECT:
SUMMARY
OF SEPTEMBER 19, 2012, TELECONFERENCE MEETING WITH PACIFIC GAS AND ELECTRIC COMPANY ON DIGITAL REPLACEMENT OF THE PROCESS PROTECTION SYSTEM PORTION OF THE REACTOR TRIP SYSTEM AND ENGINEERED SAFETY FEATURES ACTUATION SYSTEM AT DIABLO CANYON POWER PLANT (TAC NOS. ME7522 AND ME7523)
On September 19, 2012, a Category 1 teleconference public meeting was held between the U.S. Nuclear Regulatory Commission (NRC) and representatives of Pacific Gas and Electric Company (PG&E, the licensee) at NRC Headquarters, One White Flint North, 11555 Rockville, Maryland. The purpose of the teleconference meeting was to discuss the license amendment request (LAR) submitted by PG&E on October 26, 2011, for the Digital Replacement of the Process Protection System (PPS) Portion of the Reactor Trip System and Engineered Safety Features Actuation System at Diablo Canyon Power Plant, Unit Nos. 1 and 2 (Agencywide Documents Access and Management System (ADAMS) Accession No. ML113070457). A list of attendees is provided in Enclosure 1.
The teleconference meeting is one in a series of publicly noticed teleconference meetings to be held periodically to discuss issues associated with the NRC staff's LAR review. Preliminary issues that the NRC staff identified during the initial review, and the licensee's responses to these preliminary issues, were discussed during the teleconference meeting. The list of preliminary issues is provided in Enclosure 2.
The NRC staff and licensee confirmed that the next meeting on this topic would be held on October 17, 2012. Highlights from the meeting include the following:
The NRC staff and PG&E discussed the cyber security review and question 52 of. It was agreed that the response to question 52 would not be amended by PG&E and any follow-up concerns related to this question would be addressed during an audit. The audit plan, which the staff will issue publicly prior to conducting the audit, will reflect issues that the staff would like to discuss in this area.
The NRC staff indicated that it was in the process of finalizing the audit plan for an audit of Invensys Operations Management facilities in Lake Forest, California.
The staff and PG&E indicated that the audit was tentatively scheduled for the November 2012 time frame. If the audit is to include cyber security discussion pursuant the discussion above, the audit plan will reflect this expectation.
- 2 The NRC staff and PG&E discussed the information found in Enclosure 3, associated with Eagle 21 Technical Specification (TS) applicability to the replacement PPS. The issue is whether or not a justification for the applicability of the Eagle 21 TSs needs to be developed for the replacement PPS. There was agreement that such a justification is needed and that it will be reviewed by the staff as part of its review of the LAR. The staff took an action to add a new open item to the open item tracking table to track the issue.
The NRC staff and PG&E discussed several of PG&E's proposed responses found in Enclosure 2. Based on interactions during the meeting, PG&E took an action to modify some of the responses to address issues that the staff identified.
PG&E will provide the revised response to the staff prior to the next meeting.
The revised responses and any new issues identified by the staff will be updated in the master open item tracking table and will be discussed at the next public meeting tentatively scheduled for October 17, 2012.
Please direct any inquiries to me at 301-415-1132 or at~=~=::::.:...::=..Llo::::~~~
Docket Nos. 50-275 and 50-323
Enclosures:
- 1. List of attendees
- 2. Staff identified issues
- 3. Information related to Eagle 21 TS Applicability cc w/encls: Distribution via Listserv
LIST OF ATIENDEES SEPTEMBER 19, 2012, TELECONFERENCE MEETING WITH PACIFIC GAS AND ELECTRIC COMPANY REGARDING DIABLO CANYON POWER PLANT DIGITAL UPGRADE DOCKET NOS. 50-275 AND 50-323 NAME Michael Richardson George Hough John Prehn John Hefler J. Rengepis J. Basso W. Odess-Gillet G. Andre Roman Shaffer Rich Stattel Bill Kemper Rossnyev Alvarado Shiattin Makor Darryl Parsons George Simonds Tim Harris Michael Shinn Joe Sebrosky Cimberly Nickell Michael Snodderly Kristy Bucholtz Gordon Clefton Ken Thompson ORGANIZATION Pacific Gas and Electric Pacific Gas and Electric Pacific Gas and Electric Altran Altran Westinghouse Westinghouse Westinghouse I nvensyslTriconex U.S. Nuclear Regulatory Commission U.S. Nuclear Regulatory Commission U.S. Nuclear Regulatory Commission U.S. Nuclear Regulatory Commission U.S. Nuclear Regulatory Commission U.S. Nuclear Regulatory Commission U.S. Nuclear Regulatory Commission U.S. Nuclear Regulatory Commission U.S. Nuclear Regulatory Commission U.S. Nuclear Regulatory Commission U.S. Nuclear Regulatory Commission U.S. Nuclear Regulatory Commission Nuclear Energy Institute Avila Valley Advisory Council
001
- b.
September 18, 2012 DCPP PPS Open Item Summary Table No I SrcJRI rlssue Description IP&GE response:
IStatus I RAI No.
(Date Sent)
- lISG..O~ EnclosureB,Jterrt~/.31Deterministic Nature of S~ftware:
- ~Piablo Canyon Speci~cApplication 'should identify tneboard ac~ss se~uence and provide (;Orre~ponding analysis associated with digital response time perform~FJce..... THis analysis should be of sufficient detail to
.~nable the NRC staff tcjdeterminethat the logic-cycle;
- a. has been implemented,inconformance with the A4STopical Repo.rt design basis, is deterministic,and........
the response tim~;.i$qe[iv~dfromplant safety an.lysj~performance requiremen1s.anci*1~*.ft;.U~n~Id~r~tion ofCQmmunl~ljon errors that haye been (,~qdyrlngequipmentqualifrcation.*
As stated in theLAR;ihf~pn'~tiJ~pertainingto response:{irne,performance wilt be.submitted as a.Phase2 document. Please ensureJHis.matteris addressed accordingly..
P&GE response:
AlS ptablo,Canyon PPS d~quO'lE'"t~t16..00011... AlS$ysternC>Elsign Specification", Se~oq7J5.i?entifies.theAlS board access,~~uence and pr()viges an analysis a.()ci~!idV'lith(frgitatfesponseUme.performJPce.
~':~,;'<):'ij.
- a.... The Diablo Canyon RP5 ALS system i$configure~inaccordance with the quatifica1Ionr~ui~'~nts ofthe AlSplatform topical report, b,
. The analysis in*.. OiaoJOeanypnPPS docurnent6t16..Q0011, "ALS Sy~tem. Design Specmcation".sedion 7,describe$a 10QiGe~~e.tbat is detefministic;
../.....
c,
.. Thefequirem~fl!sfortp~reseonse timeet~he PflS'er0ges~ing instn.ll'l1entation.~f~~~jnputcobditlqper toconctitioned out~ut~igna\\) is specifj~.as nottP<ex~ectO~_~9 secondsin.. Se~ion3.24.. 10ofthe "Diablo C<inyoJ1Po.erPI~nttJnits 1 &2rroce~~Prot,~ion S~~n1R,eplacement F\\Jncr~nal Re~lItftnfil1~~$~reation {FRS)",.~isjon4subinitt$das Attaotl~nt7 ofJtl:e LAR. r~.,~(ftion t.5.&_tfJ~.:'Ol~QloCanyon.P~er Plant llnits 1 & ~ Proqess pr.~onSystemReflaeementtnterface*.
Requirements S~cation{IRS}", Revisic)fl.4i;~UDmittedasAttacHfllent 8 oftheLAR, theOA09 secondsPPSprocessing.instrumentation respOnse IRAI
Response
Comments (Due Date)
- ""Staff re~te~time
,..~~~~cafc on S~~rEt:~~tand agr~~}that this is t~e eQlTsCt Respon~~
recei~~.~pnI29!
- 2012.*SfaffwiU...
.review'hd*,qj~cuss turtherif needed at sUlJ$eq\\J~nt terecom,.*~eit'Jl9.
Resp()nse aceep~a~Je;waiting
.onP~&Etcfl.
pfovid~thetime respon~~
~tcutatjoh'fQr the V10 TricOn'PPS R~Placertlent arcnitei;t"e by April 16, 2fl1a.
Page 1 of 64
September 18, 2012 DCPP PPS Open Item Summary Table No I SrclRI I Issue Description P&GE response:
IStatus IRAI No.
tim~~S~llP~t~'between the ALS and Jrioon. as follows:
AlS:J~5rfrlSforRTD processing Tricon:~2~~~s Conting~.y,;.3tJms Th~*** q.~~:'~nds PPS processing instrgmentation value.is the Same as thev21!1Je?~atis~lJrrentty allocated to PPSprC>CeSSinsinstrumentation. As 10n~~~~;,,;~Ssecond PPS proce~ing~tfl.,lmentation value is not eX~t:)d~~~he.tOialresponse time.va,ues;~s~umedin the plant safElW ana'vses;c(jmai.~in FSAR Table 15.1-~rlWillnotbe exceeded;.1s~~~(is IqreaT RTandOver~erif;RTfunctionsi2sec6 ;"'n *.*.*
rpi~ssureRT, Low pressu~~rpressjJre RT, andlO\\lliLowSG waterl~~J'~T;fUn¢tions,1 second for Low'reactorcoOlant flowRT runction,25
~ntfs ~;!-9~. J)Tf3ssurizer pressure, Highconlainment pressure,and*lpw stea:~Un~pr~$ure.Safety Injection initiatj~n!~.secQnds for Low lowgGwater tevelau~ili.~feeQw~ter initiation, 1B~np~;for Ijighcontainmentpressu~e,..
L~pr~~SUtiier'PrtlsSure.and lO'V~fltJlnrl~d1)resstlre PhaseACOf]ltainrl1~qt isolation.~8;is,e~0J1dSfor HjghHighcontaiflment flressure contain~~ntse~Y initiatiQJJi~i~~6rn:tsf9rHigh High.contsinmentpressufestearntine.{~I8tion,<~
l~,~G wate"level.. ~1J~irtary*f,~~ter.isotation*..*andB
- ~amline pressure steam lin&isolation.
the~~~i~(9'timewiUbevef"ifiedasPart.of the FAT and the t~ultswfltbe incwde(t!ijJh~F~T summary repmttobesubmitted by 12131/12.
Tricon.
Invea~,&>pr9~ided~tailed inform~tionon thedeterministjCope[~tiono~.t~e
~10I~f;()n in;~rv~nsysLetterN~. NRC. y'o-11..Q01, d~tedcdanlJary' 5~'201:*1.
trl~P~.of"tne V1Cflriconsafew evatU,tion, fnvensy~submitte(f<>~'
c;I~l11~nt~6f).01¥-731, Maximum ~e$poflse;nrne C~Ja!io.1.$1~~Ct1tiiflg il)e~~t-ca~ireS~()nse timefo~i..th6V10Iriconaualification S~n}~>
fnc'hl(f~~inqfCument 9600164-731..ar~th~standardegUati~~;:for '..i.*.*. **
~fqu!~!lrg.WCnt-cas~r~ponse time ()fa'giv~nV10 Tri~n"CO~~IJ~~~tion:.
- Th~ ti,...resf:><lnse.f8ftUlationf"r the V1~ Irfean F'PS Repl~11'1~flt*...... >
Is.*su,bmiJteq on APr,i130,20~2.*.:fhe. Sy.m~es~ns~r(~
.p~{t~.~~754"143~.8,WiU:tbe;sUbmjtted to the ~affl:ls;...rt,of SG':ge~~~~e2submittarsCJfthecdtllpteti()flof factoryac~ptan~
oftheV10Tricoh PPSReplacernent.
(Date Sent)
Response
(Due Date)
Page 2 of 64 Comments Res.pon~eti~calc receiv~d Letter:
(ML 12 1'311\\513)
Calc:
{ML1~1,~1~~2
I September 18,2012 DCPP PPS Open Item Summary Table Page 3 of 64 Comments Licensee r~presentatives state~J that PG&E WlllpJDVidethe.
Trlooril'ime r$$M~seCalcls in a
~01.;ument supmittedon the dock~t.
4/2312612..... Staff his.oonfirmed.that t~~~ewversj;otl of ttija:AI;,S SWPis aV~iI~ble for review RefJJ1lonse re~ived April 29, 2012: <Staff will rEl~wan(tdiscuss
~rttler if needed at
~~b~<Juent t~Je~m meeting.
ivedthe No I SrclRI I Issue Description P&GE response:
I Status I RAI No.
RAI The Triqlnwre$p~~$etime will be verifieda~,parto;1f.eFATand the resurtswill be includedintti~,FAT summary report tOQesiJPmltedby 12/31112,
[ISG~06 Enc1?~tJre;~B,ltem1Al SoftwareMan~~ent Plan:Regulatory(3uicl~(~G) 1,168, Revision.1,
Vermcation,Vali~tionl Reviews and Auditsf~~Pi9ital Computer Software Used inSafeW:'S~$t~!JlS of Nuclear P~P!~~'~ated.February 2004
~ndors~st8§r£:<'I~$titllte.ofeJeytricalan~.el~~rcgnl~ EnQineers) 1 01 ~~
19ge,"IE~ESt@ijdarcdror SOlt\\yareV~tmca~t)d~'\\I~H?ation,,, and IEEE 102e"1997I~~~.~tandard for:Sotlwa,reR~s.*ahdAu~its,B with the exceptions sta~inthe Re~l.lIatory POSltion.~"~~.1.,16e'*IiG 1.168 describes a met,hod acceptabletothEt.*~~~~.for~plying withpartsot*
theN~Cls..r~~ti()ns *for.promotin9.~ig~*flln~i~!;r~f:tallility.and.. de§ign
'guafityjns0ftw~r~~lJS~inSafetYS'~~llls;'~St~£Ki~~~evieWPlan(SRP)
Ta.ble. 7-1~~~ppendix 7.1 c.AiclentifYR~UI!toWGUide 1.168 as SRP.
a~ptanceCriteria for reactor. tripsystems'.{Atp)and forengineered§afefy features W~ir"lghq~~~lS~116-OO000 [)jablo
.*. ~!gu~?-2,jshow§tneVerifjcation.$ndV~lfdaloP*(V~\\l)0']lan~ation r~rtingto~~.l?roj~Mana~r. ~Thi~!~.ln~Of'ISis\\~ntwithth~. information deScribed inihe AtS ManagemenfPlan.{or the* generic system platform, (Date Sent) I Response (Due Date)
.(~Ell'i1per 411 ~112)
~~gonse
- 'itable; the
September 18, 2012 DCPP PPS Open Item Summary Table Page 4 of 64 No I SrclRI I Issue Description I P&GE response:
I Status I RAt No.
I RAI 3
where the V&Vl)rg~niz~tlonis independent fOrtntherip~9i~,Mafl,ger. This is also inoonsistentwith,tpecriteria of RG 1,168 and wiUfleed to be reconcileddudog the tAR and AlSLTR reviews, P&GE respon~~:
ALS.
.ii The/eps~~BI~~fl'l~z~t~J~refe~enced westingnot.l~Qocum~nr~J1~
0(l~/Oiafjr9~~~~¥R~i~$,Management Plan.~ab3(j..*JUIY.2r,,20~j.;*ttiat w,aszpasm.t\\on~~ldRi~'P~nt6002~00003 ALS Verification ~nd Validation Planf,ReVisIO!1~ct{~.SS~~\\':'~tion,ssubsequentlysubmifted.a revisedV&V plah,"§P~2~0~~'~~i\\feriflcation and ValidationPlan"-;Revisiorl5,.*on Nov~ber,t1,?01t,t~~frex~edfhe required V&Vo"~~iZatjon;;tructure sugntn~**,~.nJ~Q~ert?~tl~~th~. ~ification*p~fSO~n~l.l~.sep~rateat;l~
indepen~~f:l~..()ttl1~*m!~~merfof the *developmentPersQnn.el~ *. ~nEf We~tirtg~U$~.$11e,"QQOOO,Qlablo'Canyon PPSMan~~meht'Planwa$
rev~ to~Mi~e,,~.v~'l~1i9~niz~tion structure in wnich~tbemanagem~Dt of th~~~riI~tl()P1(~qf_l~~*separate and independe~of1nemana9.ement Of~9!~f~'~ntc1?~~t'ln~J:. PG&E;submitt,ed the>re\\li~WEf$~~bouse 6~*~t?;o~.l?i~l)IQ.q~"y()nflPSManagementgPlan, R~vi$i(Jn1. 'q~ument onAf)nl.2;2(l1' '.."
[lSG..06 En9Iosureaf*ttem1.9~
So~~re V&V:f'!at'l:.~lh!.,Al:§ V&VpJan,statesthat.Pr?j~OtMa,qagerof the supplieris re~Jl~sjbJ~fOrPl\\oviding., ~irectiollsi~lBitlg~plem,ntatic)rlofV~V actbllt{es..Ats9;t~eij~~fli2:ationchart in theQi~bIO~nY~i1~Ps Managem6f'ltPt~!'lSt1()~.the lW manager reporting.\\tC)~h~~.M;.
T6tf.AlSV$~PJ.f1d~~griEledin ISG-6 matri~forj~il~pl~ormand"the Di'lPloOat1J~nrp~Ma~ement Plan do not.Flf:0vide'tsUffjcientinformation a~ut tbeEl~i,ttestdbf;l.pefformed dUring* V&V.Fore~arpple,.theAtS V&V' Plan*.. ~tate~;~af'!9f'*Flf:oj~~sl?ecif~.. $ystemstV&V.;activit~*..~~. determined on2;apro,te~,~',prOj~.~~i;$.!and~re descrjbe~ln thefp(9je~.Managernent PlaQ.,!irl:thi~'~~e, &11e:ooOOO,"Di;~bIO CanYOr P?S "Aanagement* Plan."
However; tl1ea~1&OOOOO OiabloCanyon PPS:ManagementPlan states:
(Date Sent)
Response
(Due Date)
Comments revi~dvv/AlS PP$:rylPOl1iAprjl' 2, 2012{;and will re~jeWfor conSistency with RO.1.168.
Resmlnse r~iVed Aprif2, 2()1~.~~taff~1 r~~~and'4isQuss fU~'t~~*~~aed at su~~.~en~
tel,~m [Jleeting, Stat~~ifig:.~*.of.*tne e~~:~~(pg, 161~§)indicat.es
I
~
September 18, 2012
~,
No I SrclRJ I Issue Description P&GEresponse:
ALS V&V.
T~n "See the ALS V&VPlan for nJofe>1nform$tioh.and theinterfa~g~etW~rt;;the
~IV&V team and thePPS Replacementpr~jectteam."
The Triconex V& Vplan states that t~e;Gngin~ering proj7ct~lar"ji;;d~fi.oesthe soope for V&Vactivities. As m~.ntionei:t~efQre.the Tric6nex lepiis not listed in the ISG-6 matrix.
~~
i.'
- ii These items will needfurther.cI9rificatiof) during theLAR:i~vieW to demonstrate compliance ¥ttl'Regul~tory Guide~RG)1.168,R~visjon1,
.~erification. Valt<:JtittiOfl, RE;v~~al'}d A~<:J~s forDigitalCornpyter SoftWare in Safety SY~~l1'Jsof N~(lleareQ~rPt~nfS,"
~
The Westingl10use 6t16-ooq~,
~revised tojncfudedettitilsonho~
o<<Janizationalrept1rting ;struct~.~~.~
the scottsdale O~J'8tjQps Di,~............~.,.'.
~..'
p,r~or report to 9.lffere(lt W~stiJ19hou~;;.Vice President~.
.~. "iarl~g~randS~ltsd~~~rati()q~ O~ectorboth repQrt.tothe~titrne I W~houseVi~Pl'esidel;ft~ bttviairtdependent repQrti(lgS~rUctures, dplio.n.of 611(3~~O '~f~b~'QCiQt~n,pPS.M~nag~~e.~fgRl~.n**V&v.was revised to add informationorrltreactivities' beihgperfo""edfor the PG&E.~l,Ibmitted t~ere~isedWe~tingh()use611 e-q99060ia~J()Cany()n
~RP$Mallagement Pt~ that inCf¥tii~~:>ttreabove ch~l'nge~ 0!lAPrif ~2,2012.
.i'
.'~".
- the PrQ.anizatrona'. structure ofh'~~nsYs Qper~tionsManag~rtlent*~
~ II'} ~art,Eng!neerirtga~<:J{;.NuGl~rDel~ry...r;ach9T~hese n$'l?IaY~{.flspecific r()l~i~ttl~.\\t.1Q.*J"fic'lt1:~Plt~ti()~pr~ject fwe
~n~n$ysEl'lgil;f~ngis '~~~nsitllef()r de$~gnl~g a(lQrtlCihit<iining t~ei?~1q,lri(lOrJpratfOrl1'Jl and NUclearDelj~eryJsresppnsiblf! for working with nuclear customers on safety-relatedV10 Tric;::oo systemint~ration ~
DCPP PPS Open Item Summary Table P&GE response:
IStatus Page 5 of 64 IRAJ No.
I RAJ Comments (Date Sent) suffiCient
'orga!'l~ionat;
\\idCt~pendert&t between the Nuclear Delivery (Design)
Organization and the IV&V
°rgtitnization, Fi~h'3 ofthePPS P~P (9937~';1~
~$)'(pg. 22181) also. denotes the<;f OGPP PPS project:.
organization, and.
prq\\lides suffiqent'~~
inde~ndenQe ~
betW:een the NO aftdf\\l&V Organizations.
Gtose the Invensys
.pa~dttheOl.
W/A~S response
~ac~able; (lS~rtlPer 4112112)
.~;~!ffreceive~
- the;
- ~"isedWIALS
~f>~~'P on April 2.
September 18, 2012 DCPP PPS Open Item Summary Table Page 6 of 64 No I SrC/RI I Issue6escription I P&GEresponse:
IStatus I RAJ No.
RAJ Comments (Date Sent) I Response (Due The PMP describes the PPS Replacement Project management activities O,\\iem,ys lingitleeringdepartment procedures
- Erigineerln'g Proj~~ Pla~s(Epp);>l whereas Nuclear pr~dure$reqQir~"Proj~ctPtans." Invensys Eng il"l~()~$din system i!'lt~~tion, but Nuclear Delivery may Engil"leeringon technicalJssuesrelated to the V10 TheNRGappliecj ISG-06 totheV1.0Triconsafety C¥tJIUtJt' submittedanumbef"Ofd~ments pertaining to the design
. asp'rooess support of the PG&E tAR for the DCPP PPS Replacement, Invensys Nuclear Delivery is required to submit the application design documents as defined in ISG-06. These project documents are preceded by document number 993754. The Phase 1 submittal under Invensys Project Letter 993754-026T, dated October 26, 2011, contained, in part, the following:
PPS Replacement Project Management Plan (PMP), 993754-1-905.
"Project Management Plan" was used to more closely match BTP 7-14 with regard to "management plans"; and PPS Replacement Software Verification and Validation Plan (SWP),
993754-1-802.
within the Invensys scope of supply. The guidance documents BTP 7-14 and NUREG/CR-6101 were used as input during development of the PMP.
With regard to compliance with RG 1.168, the PPS Replacement PMP and SWP both describe the organizational structure and interfaces of the PPS Replacement Project. The documents describe the Nuclear Delivery (NO) design team structure and responsibilities, the Nuclear Independent Verification and Validation (IV&V) team structure and responsibilities. the
I September 18,2012 DCPP PPS Open Item Summary Table No I Src/RJ I Issue Description P&GE response:
I Status 4
interfaces between NO and Nuclear IV&V, lines of reporting, and degree of independence between NO and Nuclear IV&V. In addition, the PMP describes organizational boundaries between Invensys and the other external entities involved in the PPS Replacement project: PG&E, Altran, Westinghouse, and Invensys suppliers. The combination of the PMP and SWP demonstrate compliance of the I nvensys organization with RG 1.168.
[ISG"'06 EnclostJre B,ltem1.10]
SOft\\¥are Configuration Managemen~ltlan:iTh~I,.AR*inCludes PG&E C~f~IQ2, "~pfuvare Configuration.Maiffag~m~t"ltforpl~ntOperations.and............*
Oper~ionsSupl!rt,.. i?~achmem)12;...~~ver,thedocumentprovja~iD\\
Atts,.cflmflnt 12 only proyides a guidelin~if9tjb~~t'!S>SoftWare.'.. '....'.u.'\\K.s.
Corlf~uration Manag~ril~nt* (SCM)~~!~A\\7J:;!lat"l~~1tou9h. it is unClerstood.. >
that the licensee will notperform deyel?Pl!l~ntof$()ftwaref PGE personnel will become responsible for maintaining~g~rationcontrol over software upon delivery from the vendor.
Thestaffrequirestheac\\~1 planto.be q~c"by ~De licensee for maintaining*.
coqti~lIration co~troloyerPPSs()~~dt"lo~9~r£~Q evaluate. against the ac~pta~ Criter;a{)f;~~S~p.. For~mpl~;*thePLSiConfiguration ManagemeQt (~.M1Plat"l(90P2"()OOO~).s~~~lnltial 9esign. act.ivities tOiAtS.Q~ned?})()ar<is, *Tqj.~;;plal1~o~d~~cdpethe.configllration man.mentacCivlfie$.tobeU$~~:forthedey~l()ertt~tandapplicaCionof the AlS. platformfortfleOiablo CanY9ttSP~'SY$tem, Th~ staff reql!ires th~t~onfiguration management for thisdesign~ descri~d in the *.DGPP pf()jectspecifjc plan. These itemS.YiillneedfOt:theT Clarification duftogthe LA~ review to demoO$trate ~()~/'I1elial'J~e with.BTP-14.
P&GEresponse:
PG,~E dev~lopeqa SCMP pro~reto~~dr~ssconfig.uration cont~ol after shiT-l;~entofequipment fromtheVendqranq.~(.ftJrnittedth~ SCMPonJune(;,
2012,in Attachment 4<to the Ene1osureofP.Gil;*Letler 00:L-12-050.
Page 7 of 64 RAJ No. IRAJ Comments (Date Sent)
Response
(Due Date)
N/A CI(J$8*ft)e Invensys ipart oft.heOL aradO (6/13/12):
.;..-.,.~~viPIa¢eda
- copy;~t
$yC~SeM 36-01
.in~~~~a~~Point.
The staff will review this information and JdeJ:1tify*questions, if
I September 18, 2012 DCPP PPS Open Item Summary Table No I SrclRI I Issue Description IP&GE response:
IStatus 5
Aft (RA)
[tSG,,06EneIO~r.B,ltem 1.11J
~oftware T~~fpl~V~iThe V10 platform documents identified in JSG6 matrix:;
sta!e th~thei~tri;~feilletween the.NGJO ~Ne>¢Q~neratipn Input Output)
Care..Saftwa~l!~q~<'I~specific software will nPt~~ested; It is not Clear...:~'\\
wh~rlandhQwthf$ifl!~dacewill be tested,and Wrw~\\thiS test is not partaf thesoftwareulilitte~r.ngand integration testing activities.
. Further, the'9~1¥;1:'813Diablo Canyon Tricon~~PPSValidation Test,.
Plan statesi~h~t~~1~Cf>P1$t:SAP will not.I:)e'loadedpn the,system; instead ne~ will.9\\~~tber't~~Pforthe valr~tian*<~st..ltis not:cl~rwhJ'~'
'7.
Fl';~s;:fSt\\~f'~\\lj!~n~!l~i~$eOfQr the<valj~a~~\\~est*orwhentheDCP~!.!i~.
TSAPwin'be~~~if~9ri"tf'le,~~$!emand vaJj~t~a!Q~£?theiDiablo Canyon,"
PPS S¥t\\tem, iIbfJ§~;~enisW')'l~eedfurthercl~rifjCall90dUring the l)\\R revlew'todemon~trate'complancewith BW"-t4;'
Tricon
',>iii;t~'ii i..
i i.i
~qe>next,~ne~;tt,I~gir~utlQutput.(l/q).. modules* qlIijliftedfoftheV1QTri~~>~'
ar~,e3721tJzI...~.!~{~,.PQint.. ar:1aIO~ioet.Jt.(I\\l~jmOdUle, ~ndthe362~N.,
~~ V~p;~"Pqin~~ft~10utput(D9lmotule: Te~nicaldata on thesetw,b
- madul~.waspr~~~dto the NRC in.supportQ~.the V1 0 Tric(msafety evaluation*. :'Copfj~wationand ft.,Jnctional t~stin@ is'performedwhen U,e."Q
~9dul~(hal"dvl<lre.,~d~mbedcie9 corefirmwartl~aremanuf~ured.Fr()m, the factol)t~ 1I0i~ul;sareshippedtolnvensY$Nuctear'0eIiveryfo'r
.~ ill; ",~I~~r sY§te,minf~rationprojects17i.e~,applicationspecific
.cpnfigurati~~s.~ca~se the maQUlehardware and embedded core firmwate.. are y.'ithifl\\the..~~oftheV10fricons~fe~evalua~on, the i.v:rifiG~~lqn~nd val~~atj?60f*theell1peddeQco~e firmware wiUnotbe
!~peate9a~'f>artofi*~ppl~tiorf.sp~~e s¥stenrjnt(iJg~on projects.
.~~
Therea~~rtainpeSiS~itemsthatmusfbeCJonewith?friStation 1131 (TS1131}.$uch as speCifying which l/Qmodule is installed in a particular N/A Page 8 of 64 IRAI No. IRAI Comments (Date Sent)
Response
(Due Date)
- 'WandQi~cuss
... rifneeded at used for
I September 18, 2012 ocpp PPS Open Item Summary Table Page 9 of 64 NolSrC/RI I Issue Description P&GE response:
rStatus IRAI No. I RAI Comments (Date Sent)
Response
(Due Date)
Invensysstate'd TheOfaD10 CalJyon Applicatt9ri"Wlllbe loaded onto plant systemflar"dware during FAT.
Staffre.-examined tnvensysdoc.
"Validation rest Ptan(YIP~,
99S7~"'1~~t3;:
SeetiQn1~i;2,bT the Vlli~i~eS~bes thijfjardWare Valktatioo'Test activiti_and
.~itin1.3;3' of the
\\~
.. '... "'..'....',.'>.'... ':.i.i;,.
vu""an\\il d6termi~ed that fhe a~l~ti~rfpf:ogram
~S!\\P'!"f;beused
. fQr'~~~~~t (SEJ!,Qrt.?>~i$fA1)
... ils:wrtion oi~~91,;'.
'physical slot of the Triconchassis, resultin~.ineachm()dUleha\\ling a unique
<hardware address in tne.system.Atsa, TS11ati~u:~eQtaspecifYwhich
.appU~tion program parameters (i.e., program~ari!~le)agnames) are a$sighed to a particular point ona givenI/O'rrt~tJle~/Zh~desi9n items c('.)l"lfttl.uredin TS1131 willbe within the scope ~tva~!t49n.ctMties conQucted by Invensys Nuclear IV&V for appfjcauon.os;~cific.system integration projects. The necessary coflateral(syst$t:li:builddopuments, r **90nfiQuration tables,t~t procedures, te$t ~~ult$let~r)<~IIQesubmitted to
'~f\\JRC t~~upport thesiaffstechnicat* revi~wot~he<~I?SR~Placement
~<inacco,dance WithIS~J6.
..tL."
.TIle ~ 1.Ubmlttal~1~nSY$.PniJl!tll~~~6T, dated OctoQer~6,2011, contained. in part, the Validati9!ll'eStPISI1,{VTP),
993754-1~13. This document ~~criQestne scOpe~approach, and res~UfCElsofthe testinga~htities thatar~ required for validation testing of
.theVt9Tricon portion of thePPSReptacemel')t, *including:
Ptijp~ring for and conductin~system lnt~~ti()Rtest~
',~~i~t~ch~~1 inp~~ro validation p'~pnitf~ "';;"<r<>L.'
~finiI19t~~ test tools. c:1ncfenvironment ~,$sarY~t<<$yst~ validation
~~~ng.'
/..,
,iic;hedufif;l9. (and resource loading of the schedUle)
Se.*ction., 1..3;2* of theVTPdescribes the Hardware Vatidatioll,,:(est a ctivities
,-,n "
)/ ".<<"
c:1ndSectian 1.3.3 of the VTP describestheV10Tri~~PCJrtt;onOfthe
~~()ry ~ptanceTestaaMtI(!s-fdr the V10Tficofipol1tiQ~ ~Uhe. PPS
.~~placemettt.. Details on the application. pr09ralll~re pro~~tary and need fo,peprovided to the staff separately.
that
September 18, 2012 DCPP PPS Open Item Summary Table Page 10 of 64 No I SrclRI I Issue Description I P&GE response:
IStatus IRAI No. IRAI (Date Sent)
Response
6 7
[tSG"OI3 E::nclosi.Jret3r Item1A4]
>,1 Closed I Develop<,
Equipment a~~lifl98tio~TestingPlan$ - TheLARSectioms~A.6,4.10.2.4 and 4.~ t..t.2 provid~li~I.:jnf()rrnation on.the plant specifica~pti~tion en\\lir~~~[lt~lf~ors'; ;:n,eTricon V10 Safety Evaluat.io~;;i~~.U?98A246~
~cti~~ 6:2IistsJ~:.~~[jcat1on ~cfficactions Items (A~~f!~)t~atthe licensee Shourg~ddressforplantspeciflc applications. Th~iHcensee should address.eachofth$§e.fQrTclconportion of the PPSrel)la~m~nt< Similar information for the.AlSS.pof'tionofthe PPS repiacement will also;be reguired.
ALB..
PG&E wilrresP9ndtoALS~SAI~swhen they are available:
Tricon INPROGR~s'§** 'A.IIOf tl':)e Application Specific ActionltemswHl*be0;'
addre~sedb)l.March21,201.2.
AR I £'SG-06Encl~Ure~.,ltemLt61 (BK)
... f.)~4~j'l~.A.Q~I~~i~~p0tts:.**.Ihe*~qeesnot;appear t~~~'~ v.1ttrt~/
8RP<IS~~~~.~c(iJ;lg thEl~n[le~lyity9f the MaintenanceWdrkstation *to*
th~;PPS..Tp,.;rriStati()o ytOplatformreliesonsoftwaretoeffect dj$~n~Ati~r1:~ftheTriSfatlon's~~abifity to modify thesafetys:i.....................
'9~~re. ~~..on tl)einfarmatj~*provided in* the* LTR.,theNR~;~taff det~rmi~gt~litt~.T~~ ¥'0p1atformdoes not cOr[lts'X;witht~NRC glJidlir1~*J;?foVi9~Jnl;$<3~4,.... l-1ilnIV.,lpl~edControl.. Rp~mS:-:,....
Com111lJni~rl~;.f~$LI$§~*. ~A.f)AM~A6~ionNo. MLO~331at1t35}~:.Staff Posit/ant, pqint.. 'f~;.. ~!n~!>tne DCPP.PPSconffguratiqh~~~tfully compl,;with**tnisguidance{
(Due Date)
Comments ii/Response reCeived April.2,*:;*
29;2012. Staff subsequent telecom meeting4{;
~ffagreedjhaf PG&E should this 01 matrix.
(Kemper 4~12*12)...
~sponse RlQewed Aeril2,;~
- 29f.2012.St~ff....
r,Elvlewed tbI§it~"*'"
.and.stiU need a<jditional....... <i.E'"
il'!formationt()~,....
this..:item.The.
Wi'rpeed to revieW this item further
September 18, 2012 DCPP PPS Open Item Summary Table No I SrclRl I Issue Description P&GE response:
l"order forfh£iNRC stafUo. accept this' keY~witeh fu['1ctiOO~S an'acceptable deViation to this staff position, the staffwiflfiav~tQ*~~J~~ethElPCPP PPS
~Qf!cificsystemcomn:u.mi~tion~.contrpl confiQt1ra!i.Qn-:-i~~lIdil'1gt~e..... ".;
(),:>eration.pfthe ke~itch,th~ sl!)ftware.. affect~lyt~f5ey~wit~Di. and;:any
- .~til'1gperformec! onfail~s.oftf1ehar<:l~~ream:f.~o~~~!.a~~ciat~d With th~keyswitch. The sta~l.lsofthe ALS Pla£formQcnttis:~~tt.ri~ uncl$8fat tl'1is time and witl be resolved as the ALS LTR reviewlsf~~plet8d.
".:::'/,I':'/!¥:',
Moreo~er,.ttJ,*,.~icqlJ*¥.1()system** OQf!ratj9naIMocJelh~nge.{OM(;)*
'itcfl.~~"aJlI~~~"rr~tj~na.'.m~.*.**pf**~73()p~~t.MPs.andenaMes
.1l!"i~tatiQfl1131f~toJ~CJngE:!.. p~r~TE:!f~~~~~
r$f~t()t~E:!*.6tPP#ca~~QnprQgll1(fJof tMest:lfety,.~ar:m~l.
- or*(tjV:isiOA~jllJin'f.lYfla~sor in trip. As..st~~l T~nV1(l.~efi.t~.TriStatron1131 fl
'WhiJethe Tricof.lV10isoperatlQniiland lj.owever,it.*iSphy$t~IY.~$ibte.for.the TtIStatfQpcP~~~~~~t1ecf~at.all
. tim~ and'thi$ sbould\\qe>$trictlycontrolled~i\\ld~iniJt~tive)CQntrols{e,g.*
pl~~therespec:tiveCh.a~nelout Qf servi~ Whn~ch;:ang~tlg~~esoftware,
<,,~r~et~~¢;et~).,.~.,0~dQ8S'not m~ntion<a~y'a~.ir!ts~t~~~2polltf7g'~
- .~~h a~~!li~~t§'!~~t~2.t;~?~~ign,.oftne8MC;~9:~_1lr~()tI~~~ge) ke~~~~.. r~nermf!e~cfmdr(iEf~toleav~.~*~en~~t4f~ij'*~~~ftionlf*1.~1"'PC
~Cbed'*ftl;m~~~*lri~p**""0~Y'~rp..~n~w~.~i_.f~*~ris',,~..~YN position,f~ll~dE:M~'ofthe TnStation'~~rpC!;~J$t~'Will~reqUired t~,a~~il'ff~~'P9teflti~t~ffectsthts non~f~i~~~~Y'9~vepn~~e
~x~9ufronOf"e,sa~ty!~ppli~ti()flpr0graflll~bil~"efJne.~.I'l"'el or division..** These issues nlustbeaddressediAor.derfor<itbeNAC;.staff 7to ti**... *.*...*****...**..i."
. "..**.7
.... **.c*'>;>.:..~.'.i".. **.:ii.;:.<,
.*;tI~~inet~tpeQqPPPPS~.~h~~NFre*St~.'~q~ce*
PrQvidec!1in StaffPosition 1, Point 11. The.*sta~/of the:ALSpf.orm.of'l this
- $unetea~.~nbis time.'
............... " **,v A.i *
.:.............../;
~fv19~~¥~Wit~n.* CXlO~rol~ only}~~ m~~~>~5~heV~(J-r;ri~:i~NMPs.
N;.poSi~i~~tqe3.008N>MPs.*.igrore* aff~~Jl)anr4s;ftYm:eit~m.al d~V'~s~ wh~~r WRtTEcommancisfrOm.* ext~r9al o~r$to~fnt~ifaees.*or
'--_---'-__--', prb§ram..relat~d cOmmandS fromTS1131.*
I Status I RAI No.
RAI (Date Sent)
I Response (Due Date)
Comments 121J12 update: it
.J~~greed that
$i~nvensys d'>
~alngfor theV10 portiol'lof
.' S ent to be
- edto'NRC iy 2012.
Page 11 of 64
September 18,2012 DCPP PPS Open Item Summary Table Page 12 of 64 No I SrclRI I Issue Description IP&GE response:
IStatus IRAI No.
RAI Comments (Date Sent)
Response
(Due Date)
.0 aPpropriate.
it.
The keyswitcn is~f()ur-~itiQ~fthree.ganged switch so that the three ~ain Proce.ssor (MP)rnQcJlI.l~s~nmonitor the position of theBwit~
i~d~pendently. T1lePp~~~tln~,SystemExecutive (ETSX).~xecutingon<the..'..
I\\tfP.. applicat!onprQ~sspttn0flito,rs the position'oflhe k~y,sw~...The, thre.e*
""P5 votethepo~ition,()fi~~'~~~WitCh. The voted position of thekeyswitch
.. ~:x~I~t:l~tionof how is available as ar~~?t)'lfc.~Y~em variable that can be ffl()nit()red by the tb$-MP3008N TSAP. This allows~Jarrni~~ekeyswitch position When itis taken out,of the RUN position.r&j.1~;>.,~~~.gesto and from theTricon/(Le., ETSX p~~ge~sor actually
~ecutingon *~~~~j,"~!9f;J~:i~figed,fOrmat. T81131 ~E$~gesfor
~f}9J!~all
'¢ontrolprograJ11(~~~i\\~~~,~ft~~t;is.... ~etherdo'Nf1!~~.()~~eWC0rttr()1 l~~ands when in
'ams org1AAttr~~~~()~4~~~x~~ing.controJ prog(flli'l7~elJnique'y SlLad(Jress the fole.Such,m~~~~,~~r~cel*edby.~TSX anCt'apPEppriate
..,~~~~is..in the 01.
response provide~.e~~~~~g*qPo~,ar:nongotherthings, th~flQSition.ofthe
'4J~!~!2 Update:
keyswitch.. Wtiena~u~~.f~om.;;rS1131 is received QyETS%.to download f\\J~~dto explain a new control pr~~aQ'1'~rt1BcJ~!heexecuting cpntrol* pr9Qram,ETSX h9WJhis message
'accepts or reject$'hf'r§p~~~a$ed on the voted keyswitct:rposifion, If the keyswitchis inRWN,3It'~lIflm~ssages are rejected.. lUhe keyswitchis in,
'fOflTIaiworks to PROGRAM, th~J;~~~t'lil;~t9P~!d,~reQ oUt ofservice. and ETS~ runs thropgh
'.' ~*messages the. sequence of~p$t~~&Wr1f~~q the new or modifiedcan~tof"progtaRlI\\~s the Tristation
.E \\
~.;
in RUN??
Mu'tiplehardWa~~~~~t8f~ilureswould h;;iveJo oCCljron tbe\\'1B Tricon(in combibation.~th~t.lrn~n:performance errors lnthe control room and at thecomp~~vvf~tS'~1,~')nstalled)in order for the application program to bejn~RY:~~f'1~'yJ~~ogrammed. Therefore,tbereis no credible
~. single faifureon~~\\Y~G;Tri~)nat wottldallow the<safety;;related application prog~m t~""ip~.vertentIY pr9SJrag1rned,e,g~. asaresult Of unexpected operatklno.fthercbnnected compUter with TS1131 installed on The ~bovecorn;:{USi9rL!'iR9~~~ed(fQrttle \\y10TriCO~ portiol1ofJQe P~SRepl~cement).i~)~$Fa~~re**~odesa~d Effects. Analysis,. an.,stj..oo..
Phase 2 dOCurl1entp!~~p~'(?r'sUbmittalt()?NRC in MeW 2012.Addi~;(mally, p~~J$ellnvensys Invensys Operation~Mahag~rtient will support the staffs review of the
8 September 18, 2012 DCPP PPS Open Item Summary Table Page 13 of 64 I No I SrclRI I Issue Description IP&GE response:
IStatus RAI No.
RAI Comments (Date Sent)
Response
(Due Date)
~~rdV\\r~re and software a$sociate<iwiththe OMC keyswitdtiby"makrng all ttff~'/t~t"hnil"~l data available for audit.
contains functionblQcJ(Sl:f;t~~t~Uow.WRITE..a~~(~fij(;~(:jjV1ited set prOiram~dint~;~l~~~P~1ication sOfty,fa~~lg~f'I"IIYfor a after whidtith~~P~bl~,~yis disabletiU~t'r:~~rre,;.ac~~sis
. However, with~l.I~t_~~efqt1ptionOlocks pr<<il'~~i~Jo tbe program nejthertl1~ippi.~~9nprogramnor<:lF~ipatioll prqgram
~m:eters can be. modifiedwitfirtne 9MC keyswitch in~(Rl:J"'(Position.
fQtN.\\tl\\le conttl',)ls.of1useof~eysWitch will beprovid~diith to include in prQCequres in response.*......
is not used tochatlgesetpoints and proteption ss;tis keyswitchis notinR\\JN position.
stat~(~fiatP<iE.* plans.to.slbmit;*.~*separ~te;;;t;AR 493. The NRC canpot(~~ptthis d9;pendencyonan
~rtUfed future licensing action. lhestaffthereforeex~ct$;t~e licensee a summary of setpoint,~Jcutations which *lncludi$~!!;Us,CUS$f~nOf AthAnQ used fordetermi...Jnsas-found and as-left tQte~~s.ThiS
.~_... _".._.. satisfyatlGf~jnfomultionalreql,lire~~~ forth. in seetionD.9.4.3.8 without~'~CPJ'ldition of'FSTF 493~g.~pprov~1
I September 18,2012 DCPP PPS Open Item Summary Table Page 14 of 64 I SrclRI I Issue Description IP&GE response:
I Status IRAI No. I RAI Comments (Date Sent) I Response (Due Date) lJ~guestingaddR.ional information and d~mQJ'1stratethat the uncertainties used in I:).~i.na statisticaUysufficitent qusntijy RC staff has i:Jddi~i6oal,data and analysis
~etpG'tlt calculation have 9fsaIllPt~d~ato bound th(i)
(to justify the <<fraffdfmce l~yel
!eCent\\Alestingh~use*llfPl!cts Significant;lnfQ~~ti61lisrequired from Ipe transmitter
~inAti before. to~upeort setpoint;~va1ues.
3flt12 Upd13te:
PQ~Estatef.lth~t all setpoinl$
deterrTIini:Jtjons will be!.9, P~rt;Of>lIi1Si.tAR
"\\\\........~,;......'..
a~d.bJPT,su~p1R.t~d a$ s>IS,TF-493 Ii~nsint action.
3121112lJpc::t$:
T~'~'lrnaY..
qH.~*s&tt!fr~view tht=l' Wte.tlngh9use calClJ~ations..CJ~.*the
"\\Al~ngf)Ouse
September 18,2012 DCPP PPS Open Item Summary Table Page 15 of 64 No SrclRJ I Jssue Description P&GE response:
Status I RAJ No.
(Date Sent) I RAJ
Response
(Due Date)
Comments depenq~nton the~e ~Iculations, the~ tr,esetpoint calculations will be reqoi~d to be submitted on the dock~ per NRC 1icen~ing procedur~s 9
AR (BK)
LTB'~Safety C9nclusion Scope and Applicability -Manyjmportant sections of th~";~CPp PP~ LARrefer the reader to,ttre ALSlicensiog topical report (LTR}to demoJlstrate compliance of th~system with y~ric)usClaus~ of IEEE 603':'1991,. IEEE 7-4.3.2-203, and1SG~04i However, many important sections "of the ALS L TR state that compliance with various Cfau~~ of theseJFEE'St~s ~ndISG-04 are application specific and refer the reader to an~pp!ication.~pecific license amendment submittal (i.e" the DCPP PPS LARin this ca~e). The staff has not yethadlime to,ev~luateafl.the LAR" iI11qff;nati<)O in.~~etai,l"and compare this infq~atiQn \\iVjththatprovided in the
~I..S" LT~[to ~j1sI.Jre.'therels no missing 'it;110rfhatJon. HQ'fVever, PG~E and its contractors a~~ encouraged to review th~setwoJicensing submittals promptl~'19'l~rifY that compliance with these IEEE Stdsand ISG-04 are adequateJ*~~dtessed within both licensing documents.
t Closed No speqfic RAt needed for this
- 01. RAI
- 4 addresse sthis item as noted below in 0115.
complian ce"matrix for the ALS platform.
(Kerr)per4;'12-:.12)
.Resp~nse;
,\\'{~
fe~iied April 2."'
129,2012. The' ~
PG&Ei response to thiS;i\\~m address
- the Of Close this
- j
- 01...i\\~ *.~
~'\\ ~;
-f~.
P&GE respo(lse:
PG&I;~11~"Westinghouse have reviewed the LAR 11-07 and the AL:StoPiealfeporttctverifyinformattoniscprovidecHo justify complfi:lngewithIEEE 603-1991, IEEE 7-4.3.2-2003, and ISG-04 in eithedheLAFfor the ALS topical report. Asa result of the review, it was identified that neither the LAR. nor the ALS topical report contain a matrix that documents compliance with ISG-04 Table 5-4 for the DCPPALS platform. PG&E will submit a matrix that documents comp1iancewithISG-04 Table 5-4 for the DCPP ALS platform by May 31,2012.
September 18, 2012 DCPP PPS Open Item Summary Table Page 16 of 64 No I Src/RJ IUTssueDescripf;on P&GE response:
I Status IRAJ No.
I RAJ (Date Sent)
Response
10 RS ptanty~ria~PPS Scope - In the Descripti§n~~onofthe LAR, section 4.1.3,'Oine~rcjnt variables.are defined as~fig'required forRTSand section 4~1,.!llists seven plant Variables~th~Sre requiredfor the ESFAS.
Three aqd~io~~1 plant variables werealso~;q~d in sectjQn 4.1 0.3.4.
',;. '\\ ;<l
,'}fF Some vari,ables are not listed in se~io\\ri ~10~3A as being PPS monitored plant parameters.. Itis therefore aS$umecUh$t these parameters are provided a~ direct inputs to theSSPS anel thatthePPS is. not rel.ied upon for the'~Pletio~;Of:reqUI"~ f$l~ortrip.or saf~tyfunctions associated with th~m;*~a$$~rlflrmttijt ~ ~~flt parstfjeters and a~(lCiated safety*
fundio~w~t,~il'1ue t~'p~ei~~~n~ntIYfrom th~>ePSand that the rePlac!meQt;!~~~.\\NiU ri~tadverseIY'impactthe'SY!tem'$ability to reliably perforintl1~'t~ctions.
The Pfi~0#ElP~~rn~t'LA~.se~I~'~'1~~i~h~4,1.4deScribe the ptant variable:sfi"0ri'rwhipnRT~arldeSIf~Spr~iV~flJnctionS are generated.
Theiflitiationijigrtal~outpLits tQthe.SSPSooiflCidC!l'lCe lOgic aregener~ted in the PPS or other, indePfllrldentsyst!ms,or in some cases, by discrete devices, Se~iQn4.. 1.$it~ms 6 (RCPbus UF, UV, and breaker position, 8
(~~j~~Uffiif'1~ki1?JI~~J)~~~~r~a,nQ.,!tc?P.\\{~~I,,~~p()f)ition}a,nd 9 (seismic
~1~tation) ~. g~ted by discrete devlce$Qutside the PPSand provij~di~e<;:t&ootaetinputs totheSSPS.. Section.1.4 itemS 6
.\\".,.:'
'<':'>:)">"'{~':X,);~:' <t M
'"V (Co~inmen~exhil~ Radiation}.and7 (RT breaker position Permissive P 4)ar~~a~o~~~~.'oUtSide thePPS an~.arEldirect contact inputs to the Ssg$, ~iQitia~~$ign~lsasSOC?iat~ with.th~ plantparam~ters Qperatejfld~Fld8~iY:from the;.BP$. ThereP'~mentPPSwiflnot adversely affeCt t~'~i~ble performance of'tIlEJsarety functions associated with these plant. pa~ers.
(Due Date)
RAI02 Comments Neutron Flux is an input to Tricen bulll is not listed in
.*Table4~2."ProcesS*
Variabl.e inputs to*;'
Tricon" Signals not associateclwith PPS functi~ns will b!9 designated as such in the SE and
September 18, 2012 DCPP PPS Open Item Summary Table Page 17 of 64 I No I SrclRI I Issue Description I P&GE response:
The three signals (W:~e Range RCS Temperature T urbinelmpulse ChamberPressure)* not listed in ~AMjilnQ..d are fT!Prlitored by thePPS per Section 4.10.3.4.
Pr~~sure andTelT!p~raturesignals are used to generar; d~$(:;ribed in oCPP FSARSection 5. The PPS uses Chamber Pressuretq:senerateanjnitiation signal that coincidence Jogicto develop Permissive P..13 as UH'VUOO.~
Neutrorl F1~sQpul~<be added to Section 4.2 TableA-I I Input toQve
.1"emperatute(
Input to.Ovei Temperatttre:;'c(
I Status RAI No.
RAI Comments (Date Sent)
Response
(Due Date) they.wi.llnot be described.lf'1Ge theya~'~tin sco~.~~.
for 03
September 18, 2012 DCPP PPS Open Item Summary Table Page 18 of 64 P&GE response:
I Status I RAI No. IRAI (Date Sent)
Response
No I SrC/RI I Issue Description performed by the PPS or ifthe pPS\\~iUonly be providing inputtoextemal systems that in tum perform the permissive logic described in.th~::LAR Qistablecomparators usedJ~
att~SteCi b1..the PPS Replacemel1lPf6je~JI.
nAt'Tr'ii~~i\\lA functions are performed by is still unclear if thisstatem~*
throughout the LAR.iflt Pfeaseprovide additional to dearly define what the ReactorTrip Intermediate Rang~
low Power ~i~i\\(e, LOIiSS ofFI.ow P~rmi$liSive
..............~.....
Powerpe~issive<****.****.***\\.;.*. /..... ;.
e.. 10Po~rRange PqW$rLOW" P"11 LovlPreliSsurizer Pressurl P~12 No-LoadLow-LoWT~TI P-13 Turbine Low Power,P
.P'::14 Hi-Hi Steam Generator Level to Pressurizer Pressure: it is also pel'formed~y the~)CI$ting repl~cement'sy~tem~nd>
replacemel1t proje~~.
reactor trip} *
- jhe LAR states thatuThese~iQ'nal~a~igenerated in fhePPS";
P&GE response:
"fe~iSSive function initi_o!1fSignals~~nerated within the existing PPS. will
.9~~tinue to be performed bythef~flj.~~EtntePSa~~.therefOreremair01l<nOt aff~"by thePPSrepl~~tllent~roject'..~ermissive*function ir1itiati~n Iisthatare generatedindepe~gE)ntlyqf'.1h~existing. PP$ wi!' continue neratedindependently.
(Due Date)
Comments
September 18, 2012 DCPP PPS Open Item Summary Table Page 19 of 64 I Status IRAI No.1 RAI Comments (Date Sent) I Response (Due Date)
N/A No uTSrclRTI/ssue Description IP&GE response:
13 RS Permissive P6, P-8" P-9, and P¥l() initiation signals are c,omparl;ltoroutputs from theind~pef:l~entNIS to the
- i. ~ace with the PPS.
issive P~4 initiation signat~at~directcontact SSPScoincidence logic generat~from contacts in Bte~kers (R'TB). There is no interface wittrthe PPS.
f>~rm'ssiveP-11, P-12, p-t$,andP-14 initiation signal$~
.* 9~~~~tet\\f:byt)jstal:jtecompara,toroijtputs nQnQr~tAtiin
...'..the**SSPS.;
~ivep-7 is 9,eneratedintgeSSPS'from 3 out tift,¢hannels (from N1S-P~1()Jbelow setpoint and impotse chamber pressure channels below setpoint (From Pt~).
if1itiatioh>sign.als *. *describedia.hov~are*monitored. by ner~thePermi~$i~ve*~e.~. appropriate c~incide, No SSPs,PeIJ:1lissive or safety fun e>gi~;;is.changeclby;the PPs..~placementprojecl.
pe'mli~iivesp-6,p-7, P-8, P..9, P-10, andP.:;,13 are functionally de.i~<!h FS~tl,JaQle7.2':;'2. Permissives P-4, pooH, P-12, and P-14 are des.iedinFSAFfTable 7.3-3.
September 18, 2012 DCPP PPS Open Item Summary Table Page 20 of 64
-"-1-RA---:-I---'---CC:-o-m~menis--
I No I SrC/RI 1Issue Description IP&GEresponse:
I Status I RAI No.
followino statement;
--.",,-,- \\
~hese valves are not safety-related, buta,re:i6.t~rtoGked with the P-12 from theSSPS. I t '
Inccmjunctioriwith tr,e response to RAla,PI contradiction in section 4.1.20 oftheLAR.
cOfTIpaft:ltor outpijts ootg~flerate. the P-1:2
_at~by the SSPS detected. The SSPS
.......~~S; P13 Turbine tr.~()rLevelhigh-high SSF?Sbased on
~~91nthe ref)pgnse to als and logic 7.3;3 (ESFAS).
and does not (Date Sent) I Response (Due Date)
September 18,2012 DCPP PPS Open Item Summary Table Page 21 of 64 No ISrdRi IIssue Description IP&GEuresponse:
I Status IRAJ No.
I RAJ (Date Sent)
Why would the'ppS status need to be transmitted to thePPS as the sentence suggestsin,the last phrase?
PG&Erespo,s~:
titled to the control board tf:>ScontlTIoIboard tf(P~) bywayofttl~
means "PPS
~.ystem~s not sub~itted Jdorm.instead thef$G::04
','C, //;>>". _.
(4rea~r.tQtne"AlS LTRior
.' 'tne'LAR in~eate variou$
I-.t~~Pt~sott~~g.,
oonlOl,*port a99re9ator,.. a~.4-2tOCmat~ij1~~~.;~.hil.toirf(cQn;,roCessor). Thtese are aU appli~lion'~pecifiC featur~t'fthf!PP~"~Jhestaff.expects a W/CSI.ALS~~fJ'Ientto 'beSubmitledll!l~mil,r:i~fscope apd~c;tetail' to the Invensys"PAGlfIC.~S &ElECTR1G.GP~p.";.,,,r N~CleAR SASE1¥ RELJ\\Tf30p.e~PROjEe1]2!'f$~~~.~PlZACEMENT Ol~ale*
C.*
.* A..... y.O**.*N.*..*.*p........**
..*lAN.*.*T D.'.I&C.. I:S.l3.*.:.u.*
- . '4.... ***.*.CONB
.*.....*MA
.. **. N. CE.'R.E
........*....... N
....WE.R.*.....p...
..a
....OR.*.*
- PORT OOcuij1entNQ:993754-~-912 Revision9.!P~'*$Ubmittedon the docket, whiCh explains.how*theALS portionof.tij,:,?p$ apptiOCition conforms with the guidance of IPG-04.
Comments
- '~il!lcussion
~tt0ofiil
<14/4/12 update: The
araft ALS 18'&04 cOfl'\\piiance matrix optne ALTRAN
'arepoiniwebsite
.not detailed en~ghfor the staff to use in approving
- ~.ALS portion of
~PPS" cOfJ'ltrlunications
September 18, 2012 DCPP PPS Open Item Summary Table INo I SrclRI I Issue Description I P&GEresponse:
I Status I RAI No.
I RAI (B'K) sdeveloping the ISG-04.cQmpliance matrixTabte for the AlS and PG&Ewi!l submittheTabte by July 31,2012.
(Date Sent)
Response
(Due Page 22 of 64 Comments design. oU~l:::l~Ot PG&E review'the Invensys ISG..()4' Doc.DocumentNQ.
993754-1-912ker.
ReVision 0, and provide guidance foranALS
~eleVeIOf<
detail.
papersdiscu~in"r~
integration plans for PPS,
.system. The~e papers were discussed at 411812011 ce.
The staff agrees.i that the analog....
RTD signal loops ntay be te$ted separatelyatfl;'le.
Tricon FAT and at theAlSFAT to satisfy integrayon test requiremellts~;
some*CQncems over~eState~ent that "There is no ital data
September 18, 2012 DCPP PPS Open Item Summary Table Page 23 of 64
,~-~--
I RAI No.
RAI Comments (Date Sent) I Response (Due Date)
No I SrC/RI I Issue Description
.'P&GE response:
I Status
September 18. 2012 DCPP PPS Open Item Summary Table Page 24 of 64 Comments No I Srclk/TTssue Description I P&GE response:
I Status I RAJ No. IRAJ (Date Sent)
Response
(Due Date)
Section'S.1A.3, Hardware Valid~tion Tests, (pg. 27/38) of document I CloseQ IRAfo6 993754-1...a13*Dia~()panyonTriconex PPS Validation TestPlan.(VTM) states that the ALSeql,l.Jpment wi" not be included in the F~t. Where, when, and what procedures Wiit.be.used to fully test the.lntegrated.PPS system (both Tricon V10 andALSplatfo~s together) be subjected to FAT.
PG&E respomse:
aSllng:
'ormation on the PPStestingis being provideg*to thes'
.. 1need to be.updatEld bas~;~ntf1e additionalinforrn t1'lhe updated \\/TMwillbesuljJJ1itted witt be providedaftElI" ~
lthe staff is received on the additional informationontheP'
P&GE response:
I Status Closed September 18. 2012 DCPP PPS Open Item Summary Table Page 25 of 64
~~---~~,
No I SrclRI I Issue Description Comments I RAI No.
RAI (Date Sent) I Response (Due Date)
September 18, 2012 DCPP PPS Open Item Summary Table Page 26 of 64
- ------:-:-:----------.=-c:--=---= response:
I Status I RAI No.
I RAI No... I SrelRl1 Issue Oesenpclon 1\\)
PG&E r~~PQnse:
Westin~~Ol,Jseincorporated the.IEEE-1012 compli~n V&V pl~fldocumel"lt8116-00003 in AppendixA Table
~1il9r:n1~~d.the ALSV&V plan document 6116-00003to i012;:inAttachment 7to the EnclQsure of'PG&E LetterPyL,
..***r15*ofthe' aefJP'FSAR'doe5':notusethetertnsAbnorm~I,,'.
~~rCittol'lC!.!.Occurrence(AOO) o~ Design Basis A~dent(D~j.'Instead, theacqldScl"lt analysis in chapter 15 identifies conditi(msasTollo~;
GQ~DITION.JI.- FAULl'S OF MODERATE FREQUENCY CONOffiON III-INFREQUENT FAULTS (Date Sent)
Closed
Response
(Due Date)
--~
Comments staff ~.fwo*
thro.,.gh. thisaslhe SwP;is'revi~wed and ~val~CJt~for appn:}val***elease sU.n'litt~e document*dn**tbe dock~t ThisorXViIl~main open~d~flg a~rE!pOjn't,*'T' WSl5si~efo~:~~fO revie~:eF'~d,sign draw1ng~that will addresS tbis.*lsstJe as wellas.0120 ancJ~1. NRC,staff wlUdeterfT1.iq~<,i they~e~edto be submitted?onthe d~ket.P<;?I~wlll*
'slie
September 18, 2012 DCPP PPS Open Item Summary Table Page 27 of 64 IStatus IRAt No. IRAt Comments (Date Sent)
Response
(Due Date)
NOI u
SrclRt IIssue Descnptlon
--:::::---::-:------------r'P&GE response:
CONDITION IV - LIMITING FAULTS As such, the statementthat AOO'sand D8E*s~~.~~~crme~intheFSAR
~ppetarsto"be inaccurat~..Please;expiainth~~~~tionbetween the Conditlo.l'ls described in FSAR chapter 15 andtt1~;~b(lo~al Operational Occurrences,and Design Basis Events describag:,iriWLAR.
.::I;~IEr~Of1se:.TJ;Je AC!0'S8tereferred.toai~S<90ndition I w_perationaITransients" inFSAB.Chapt~r t5,~~:~~~,~~sed in FSAR Chapter 15.1. The deSignbasi~ accide~sare re~'toasANS Condition II "faults of moderatefreque,ncy,': ANSCO?~ion~J~~'i~!~uentfaultsl and ANS Condition IV "limiting faults" and*areaddr.;ls~i;!i~"SAR Chapter 15.2, 1~,3,and 15.4 respectively.
20 September 18, 2012 DCPP PPS Open Item Summary Table Page 28 of 64 RAI No I SrclRI Iissue Description IP&GE response:
IStatus I RAI No.
Comments (Date Sent) I Response (Due Date)
RS N/A (12.update:
- ir ated for NRC to revl~WIefS~desjgn dra~gsthatwUI afJdfStJSthis issue.
NRqzi~taff \\'(ill de~ioeifthey
~'~cled tc;)tre fotthlsitem.
7/02112 - Clos~
nemi.. 'Llnformatlon sum9!~~fforNRC
~s¥stemdesCription proyicl~jn ~ioriL40fthe.LA
'OrmedtRyother pro1ectiYtsvstems>at DCPP in.al...
- Inmanycas~,t,her~is "? eJ(planatiOf:l of,
....~. the,funct!0~sdeScrib~*Aor is;there a garifj"
'desQribedJunotions are bei~ performed by the PPS.
Jircludes "functions tothePPS
'stem is of whether the As.'o e~mple. Secti~n4.1~.~ed~sctibes a bypassfuncti0l11o'support
~~~n9~;;*he high-hjgh?Ori~iAmentpressure channel tOirn~~trequirements oUE~!f>279 andIEEE6f.l3.~he description oUhis fUl0lctlQll aoes not iy~r;,state,Y41ethey;tni~datch feature is being impfem~Qted within the
,Scyst~m orinthe.SGFI.
"'0';"'"'
Iffrieeds tOHav~a
- .tullde~~anding.OftIJefun9tion~sCOpe. ofthe system.being.. moQ~
QrQeft9maf(e its r~u~0f'¥i\\~pJiance d~!~iJ.l~tions.. ~lea~\\P
~,rams to helpthe'slaff p~rfQrmedby.other eXtemal
.. '.. "',f~liItjftformatioo SUC11'8S*peS function PPSf'unctJonsfromfuntttons Closed qnJ~~.
F'~8ff§~I:
h~i~b$ite isil'lf!fuafKjois ol'lly,applicable to thj$'licensing
- action,
\\,,:::-<
ectt6at60 ben~
s.is to dt!ierminePPS functionality.
September 18, 2012 DCPP PPS Open Item Summary Table No I SrclRI 17ssue Jescription iP&GEreSPOnse 21 RA Westi Test P Syste requirl Ighouse/CSI document 6116-00005, "Diablo Canyon PPS System lan," states that the ALS-1 02 FPGA design is changed for the DCPPS
- n. Further, Section 5.3.3 states: "Test as many of the ALS-102
!ments as possible."
Pleas board
! identify what document describes the design verification test for this PG&E for the Speci PPSW Septe
~sponse: The documents that describe the design verification tests LS-102 are 6116-70140, "Diablo Canyon PPS System Test Design 3tion," submitted June 6,2012, and 6116-10216, "Diablo Canyon Simulation Environment Specification" that will be submitted by
)er 30, 2012.
Status Open (Hold)
RA/ No.
(Date Sent)
RAI10 Not used RA/
Response
(Due Date)
Page 29 of 64 Comments 6-13-12 update (Kemper):
PG&E understands that they need to provide an update to this response. In the meantime, PG&E andALS have provided 2 design specifications that will address this 01.
These documents are placed on the PG&E sharepoint website. Doc. No 6116-10740 was submitted on June 6,2012, which describes ALS system test design specification. Doc.
No 6116-00005 was also submitted on June 6,2012, which describes ALS system test plan.
Doc. No. 6116 10216ALS W Simulation Environment Specification will be provided in the future.
3/21/12 update:
September 18, 2012 DCPP PPS Open Item Summary Table Page 30 of 64 No SrclRI Issue Description P&GE response:
Status RAI No.
(Date Sent)
RAi-
Response
(Due Date)
Comments PG&E has created a share point website for NRC to review PPS design drawings that will address this issue.
NRC staff will determine if they are needed to be submitted on the docket. PG&E will ensure the website is information is only applicable to this licensing action.
NRC-the response provided does not address the question.
7/13/12 rjs Deleted RAI 10 pending review of revised response.
Also decided to hold item open.
~-------
22 BK Tricon VtO;sm:t.AL$platforiJls together) besubjeetijd't9;fAT.
PG~res~:
September 18,2012 DCPP PPS Open Item Summary Table Page 31 of 64 No ISrclRJ I Issue Description I P&GE response:
I Status IRAJ No. IRAJ Comments (Date Sent)
Response
(Due Date)
ClesU\\j"RAI 5 Section 1);:1;(pg, 12138} states "The netWQrkeq~ipmenJ. including media conv~rter'fSfc!ID~cs.Network Aggregatofl"tJP,qflcfgateway hub, and the MWS will. nQtbe withiFJ;,lhe test scope of tliisl';UP ~l"heNu~leaf Delivery rqup'yViUcoordinCitewith Pacific Gas&~lectl'ic fQrsystem staging
.(am.over to Nuclear IV&V. The Nuclea~IV&Vgr9t~P will confirm prope~i!~peratiQf'lofnetwork communicationssyste~int~ces before beginnlng.~~~~tjng addre$sed lnthis VTP." When, Where;: and what pro~dur~Ii.'! beus~dJqtest the. network*~uipment??*
AlsQ, se9tt~*:~.~ :4,(3)HardWare Validation Tests state~ that the ALS equlpn:tef*Wilf:l1ot '~.*'i~9Iudedif1 the. FAT (pg.~7/38).Where, When, and whCl~pr()tEI~r~~~t~u~~*tOfully!test the'ftte{;J~!ted PPSsystem (both I FQllov.'ongl#5 question pertaining to.~.h,e PP$ VTF\\i Ad<ttiQnal{t1f~.non the PR~ testingtt!ping~rovided!tothestaff.. The VTPwHt.need'to be updated based on the additional* information. A date thatthe u~~~ Vl"P ~Jlbesubmittedwill be provided after feedback from the Staff is~cei~~onthe additional information on the PPS testina.
September 18, 2012 DCPP PPS Open Item Summary Table Page 32 of 64
-NO! Src/RI ! Issue Description I P&GE response:
I Status I RAI No.
RAJ 23 BK
!Se<?1lPn 1.2.13, 101 theLAfr(liag~JS5)~~at~;"Figure 4-13 onIY)ShOW~~~
. Tt'!;MinStalled in the Tricon Majn~~a~sis*(stot 7L), the PPS r~~~m~Af<'*
ilize twoTCM cards \\n ~aotltn~irlc;haSSis (Slots 7L and 7~);Tni~~tl
.............. etwo non-safety-relat~~~rnuni~~npathsto the MWSa!1~tf;Je
,?PCGfJlteway Computer from. eaCf{*Proteption.Set to ensure conti~u*3~:.
PQ{1lO'lunicationsifa single TCMi'sils,.
...i**t" Th~N~tOpt~csM()del PA-CUlPAD-gU1.PA-CU.port aggregatorn~o~{t~P\\
.~approvedpreviouslybyNRCforasimilarapplication in theOcpnee.".
R,~s,{ S:~RSecti~n3.1.1.4.3 [181:T~NRC;staff determinedthatstut:rto;th~
~I~ctrical iscnafion providedbyus~offjber.opticcables and the d~~~.. '
..*!~oj~j~~prQVid(i!d.bY the PortTal?a~~theMaintenaooe and ~~ *.'..
lln~~ff!~*(~SOl~the Oconee.R,e-9;t~ef~wasreasonable assurarr~.1hataP
.f~utt:Br!faifu~Erwithin the Ocon~.~at~~aycomputer or theOperat~ril\\ld; Comp,.rter!'iUnotadversely.. ffeptthetlf:jjlity oUhe Oconee RPS,cs"':
ilisW*1tss~tyfunctions.jp '..
,e~AT,~~&Ewill~ttbfa~r~t~fon.$etcommunicat{t;)'
t:i,:1n!F.igqre 4-13 to~~~h~itt1~iSno inbound COO'lJ'n
........ </
t(i!d,~ithpqRagg~~!ot~~~()tktap Port 1. That istf'!G,&6';'~\\
~mmljflic~tions fr()tl)P9.rt'.1.tgeltherthe TeM on P9rt>Aiqr.th~.
otlP9rtB ()ftheport ~g~6g~JOf network tap are not ~rmit1e.d.
- flfft.Jistest will be documeptEldin'final System VerificatiolJ.~llQ
~~eport.. *.PQrt Clgg~~~()r~ual;n..linepackage (DIP) swi~~
onswfllbe controfled by OOP~cofifiguration management Pr:ct~SS!!$,;;'
'\\'.,',','
lnofderfortheStaff to approv*3 the'J.~t~rated configuration of ttt~PI?S, prior~shipment.9f thePPSequif;lrtlenpoDCPPsite, a"commulli~ations paUls will. re<:iuiretestingonorbefontfAT,. and before comptet4og;ofthe
.~tSEtf)tlljstestin~fiityp~IJfCijmRJ~~d(fllringolbe1orEJthePPS'qF~";~'
ot~~~se,fhe SER will notI>eCOm~~teduntilafter the SAT.. Ple~~'......
prov,idea test* SChemelpro~dur~~t~t~s1ies aU regulatory rElguireO'l~nfs,;
prior to*prouring the FA 1: Oth~~is~,.iftl1istesting will beCornplet~<<;t.cJW'iJ'lg theSAT,as stated in~LAR. p(~Cl~J)rovideaoetailed scheduJeJortl1lS '.'
tE)stin~ so the NRC canrevI1Se~I?PSLAR Review Plan accordingly.
(Date Sent) I Response (Due Date)
RAl11 Comments 1 The NetOptics Model PAD-CU has two one-way output ports but is otherwise identical in function to the PA-CU.
September 18, 2012 DCPP PPS Open Item Summary Table Page 33 of 64 P&GE response:
I Status I RAI No.
RAI Comments No I SrclRI I Issue Description 4.1.17 paragraph associated with HiQh - High discussion it is stated that the SI funclions (Turbine Trip and rd~n,tion()f thi;~in section 4.
perr:n.issi~e.fp'easeconfinn
'-;t'i~,SG;Level,r by initiationd Tfiis same section also stat~s
~rVe~tocomply\\Yith IEEE "
P~S systemls not being Instead,tEEE B(}3..1991 is contained in section 5.2 ofJEEe'E understand lhatthe criteria Trip can beinitiated ~J;C-":"
pf'ijtiPlion function OR by
$ectIon 4.1.1'l describes the
~tQteCtiOn functionP-14.
the.PPSgenerqtes an initiation
.th~~urbine trip signal and init~tes qoi~~~nce of 2 of 33 high-hi9tl
- isdetected.
t?~6tl~n4t1.9 describes Pre~~nri7'll!f'
~t~:.iSinitjationof Safety
'~jtj9i~~pe3 of4 Pressurizer f'.~is detected. The 81 actuatiol v' ;~nd.~uxlliary Feedwater
.. Steam Generator levell-hnn_Hlmn The'P-14 (Date Sent) I Response (Due forAlS is
\\I'mation will be is received on the functions or P-14. In this atesme same two however, there is
~~v~~ion of the P-14
~initiated by either Higll' le!t~rLeve1High-Hjgh
,steamgeneratorlevel, t:~S$PS,which generate.s F~water when insnY stearogenerator
25 September 18, 2012 DCPP PPS Open Item Summary Table Page 34 of 64 No I SrclRJ I issue Description I P&GE response:
IStatus I RAJ No.
RAJ Comments (Date Sent) I Response (Due level High--High. Through the SSPS, P-:14 will trip the turbine and actuale.A,uxiUary Feedwater. A SI.signalwill also actuate Turbine b;JP~nq}\\t.&iUary Feedwater, amongqtheractions. Pressurizer
~ro~cti(:inf\\jnctions do not. initiate P'-14 and Steam Generator uevel Aigh-HigbE@-14 does not initiate SI.
- b.
...,..'tUf~actIV~ when 2 of 4 PowerRa~g,NIchannels are above Ois combined with l"urbin~;'P0Vl!er Permissive P-13
~Qxim~tel!1Q~ tufbint;toadlto provide inp.IJf to ItatJows blocking severanowP9wer reaaoftiips~ -...-C~-
eWect}!"~rrt)i~$.iYe P:tOis the "Power Range~tPower - Low"pe.rmisslve" P~sslv~hP..9Isthe Power Range at Power-High" permissive. This consjst~Wlttrthe response to 01 #12, above.
September 18, 2012 DCPP PPS Open Item Summary Table Page 35 of 64 No I SrclRI I Issue Description IP&GE response:
I Status IRAI Comments
Response
(Due Date)
SyOAP defines Supplier tasks
$oftWare quality fofeachOfthe following phase$QfQev~lopment; Projectlnitiation~nd Planning
- ConceptucU*De,slgn
- Requirements
- Design
- Implementertion Integration
- Test Th~.se phases dQrtotil~l1W:ithttl~ phases U$~*i~*tr devel()pmentlifecyCI~$.<<~orinstance. theTriC(:)rl a~R~quireme~*.DesiS~~.'~plementatton,av~.
Pftflis;/itis not(,QI~ar:~Q~f8.SSlJrance 0.1 task C~~~'(-'~"~;;i';;'... ;:'
>~~~lished,*... *Oq.png(~hichTricon Phases.WOLJf(f'~hO~~:t~slisted under
- .*ll'lt~J'$tIQn*.lMl~tion~I:l~.elaQning, and'Concept~atY~$!Q@beperformed?
.'::' ":>>{/!"
- l1)e.**A[~s9APcfoesrnot*.~.efltion*.Phases.but.. ~;~~~
defines the develop~eotpn~ses as; Planning')!iPEJ,!~~~~fi~'"
Manufacturimg, System Test,andlnstal'ation.
yvouldlt bePos$ib{e.fQtP~~Jo.. prQvidea mapp~I.~......,
Sy~f()tne Phases Qftf'j~AtS*and-Tricorr~~n.l?~
proces.s so.that the staff can.correctly identify an~f;L, theseQAtasks?
I IRAI No.
(Date Sent) 26 RJS The PG~
of
- Iterr'f lij!iiaf&<.fon 4125/2Q"fl V\\filln~~lormat respq~~~ for this item.' t~erefo/e thiswiJl,oean RAI.
September 18, 2012 DCPP PPS Open Item Summary Table Page 36 of 64 No I SrciRI I Issue Description IP&GE response:
I Status I RAI No.
RAI respQf1~~ j...
PGEwiflprovide~mapping of Phases definedim*ttlJ~~~P to the Phases of the AlS*anQ.t~90fl~lstem development P~o~~~.. JhedetermInation of theJopationof.tpemapping information and*date:t~'be.*...submittedis IN.
~
~
-~
PROGRESS.
~.;*projedwere disc~S$edin~~i~,4;~.11,
~Rthat djscH$~the;~PP.~lJ~ti~Y
'~.~l'lcfP'()CQr~ment.ControlvPtog~tn~i~il~tat~that r-l.,ntr-wll*altditlQ~~n~<::Slduringthe manutact'ilrir'lgp~~eiundJrthe P;;QclJrement*PrOQramand associated di(~e~,
f'ollowlno the"perf~ance ofthe pap audits,audit reports Will be created AudjtSummarvReDort will be created. PG&Ewillsubmit the the staff at the time the vendor hardware is (Date Sent) I Response (Due RAI13 Comments
28 29 t~tAR,Attachment 3, states*tha~PG&E. isresponsitlJefor.the.. f~U9Wjng
. ~~~'lJ.lt~enf6c~cle:.proJectj~~ation~rld p1anningPl'la~l~!1~tual
- .. ~er req~iremef'lt~pJi~~,lnstaflation,..anct9~~ot.dPt:tas~J l~~.<:andmain~e~n~*.p~a~e:.*fH'Y1er~~~on*.3.1*. ~10.. states
~iU.f~119wtheactivi~~;d~~91'i~~fOfeJor.~ftw~e......... *....... >....
jlions..*p!eas.e..eXpiainh~.P~~JF;v6n;~Qtrns:~arf#**'n1!djficati~$.....
f~YJeTriconana ALSplatformscmce>¥GFS 'I"SP,cen'tjntprojectis~ '.'
oompteteq.
T~~,~~,..(\\tta.cnrnent 3tstate~ thatt~e.PG&e*Project Manager will share tne!'re~P9n~ibUityJor m~eting the s~are,quality goals and for imPlemef'ltii:1gtl:le software quality management throughout the project
'PJEiasedescri~what responsibilities are (J0ingto be shared and h~wthiSi~f 9Ringto be perf,ormed, September 18, 2012 DCPP PPS Open Item Summary Table Page 37 of 64 No I SrclRJ I issue Description I P&GE response:
I Status Comments
__-+1-*-.-.'
'.' I d~livered toPG&E. The vendor tlardWare iscurrel1tJye~~cted tq~
de1JveredtoPG&E in Spring 2013.
ThepgP~tJdit.reports wiJI not be sOb'nlitted but willbe llJadeavaUable to the NRC staff for review.
RA Software Management Plan Closed IRAJ No.
RAJ (Date Sent) I Response (Due Date)
I N/A RAI13
September 18, 2012 DCPP PPS Open Item Summary Table Page 38 of 64 fJOIuSrclRI I Issue Description I P&GE response:
PG&E response:
The<PG&EProject Managerwitlshare t~e responsibifityformeeting the
. sot'tWarequalitygoals with the PG&E quality Verification organization personnet TO!tn~ement th~ ov~rsight*ac:iivities,the<PG&EQuaUty Verification otgan~ation witfissueaef;~jectAuality Pial) (PQP) that wiUdefine the oversigHt activities tO~i'~rf~ed,inc:tudrng technical audits, cyber
. security audits,..and sof'tWarequalftyassuranceaydits.
I Status IRAI No.
I RAi Comments (Date Sent) I Response (Due Date)
I Open IRAI 14 (Hold)
Not used 7/13/12 - rjs:
Decided to not use the RAI and hold this item open pending review of updated phase 2 submittals.
30 RA Software Development Plan Section 7 of the Invensys Nuclear System Integration Program Manual (NSIPM) requires that non-conforming procedures shall be used to control parts. components, or systems which do not conform to requirements.
Invensys documents 993754-1-906, Software Development Plan, and 993754-1-905, PPS Replacement DCPP Project Management Plan, do not identify non-confirming procedures to be followed when deviations are identified and how deviations should be corrected.
Please provide this information.
PG&E response:
The Project Management Plan (PMP), 993754-1-905, is the overarching project management document for the Invensys scope of the PPS Replacement Project. It references other Invensys planning documents that discuss procedures to follow when deviations are identified and how they are corrected. The Software Development Plan, 993754-1-906, describes the software development process for the Invensys scope of the PPS Replacement Project. 993754-1-906, has been revised to Revision 1, to include new Section 3.2.6 that discusses problem reporting and corrective action. 993754-1-906, Revision 1, was submitted by PG&E on August 2, 2012.
I 31 Page 39 of 64 September 18, 2012 DCPP PPS Open Item Summary Table No I Sfc}RI IIssue Description IP&GE response:
I Status In addition, the Invensys Software Quality Assurance Plan, 993754-1-900, Section 8, and the Invensys Software Configuration Management Plan, 993754-1-909. Section 3.2, both provide reference to procedures to follow when deviations are identified and how deviations are corrected.
RJS l§offware Quality Assurance Plan:
I Closed
.eE?~"l30 2002stipu1atesin s~t:tion 4 that "The SOAP<shall be approved by "9~p~erofe~cttoftt1e orgapi:z:ation~ having~p(){lSibUities.in the ifi'>.*1f)ePGE.*$X9AF?ha~~napproy;edb~:tn,~~*[)iablo.PPS G;Jldepr?j~~Mana~~!.!fl~!~~tanP~ie~~~~;;iipq~f3ver,** there are ir~liothero~~an~!ion~.th~t~~Ye>respon$ibi'~~~~~ated*in*the
<+;~~P..Themanagers.ofthes.e.. Bfganizatlofls.ha~f!rj~~pp:rov:edthe
.... ~e. o.*.rgani:z:atio PGe Project Engineering Team ltlTes.6ftMtarequslity assl;Jrance. FlJ,anwas dis~usSediiIH~ption 4.11.A.1.1 of t~\\~,l..AR. whiehdi.d notcommit to I BEE 730"2002:miteriain devetoping the:
~~p,IEE~Stand~rd 7-4.3.2-2003 [76] qau$e 5:3:J)~ferences IEEE Std
'730~tS9afor9uiaance.but does notrequire ittoberriet P~~)isgeter:mifljng,hOW to address thecorn~itmer1tlrom all organizations oontajpedh'lthe SyQAP as reque$ted by thestaffin.thEt5l16 meeting.
.ii~t9AP..The fotl.owingor:ganiz~o~are a~klnedi*rol~and.
~.,$ponsibillties within Seemon 3,-4 of.the SYI
- <...I*..**.*.~....**.e
.. sbywb.lch the
.. nshave ooFh
..*......*...... a!l
';regulrementsstated In the SYQAP.
Ve~q()rNYProjects.Managers
~OCD~sigO~hangePackage Team
- QAOrganization..
Testing and Integration Team V&V Organization RAI No.
I RAt (Date Sent)
I Response (Due Date)
I RAt 15 Comments
- the.5/t6
, the staff inad that PGE Jlye ~pme
~ntfrom have Irrthe T6isoould
~.ator haclivities (it::!Iit1eat~
ventior
32 September 18,2012 DCPP PPS Open Item Summary Table Page 40 of 64 Comments 0 '1 Src/RI IIssue Description IP&GE response:
IStatus RAI No.
RAI (Date Sent)
Response
(Due Date)
Se~i9!'1 4.2.7 "Power Supply"oftheLAR d~sgribeshow poweris supplied to I CiosedtRAI16 RJS PGE R~PQ!'lse, thePPS, *'n this description,the480VAG vilal supply is* described in the accePt$~~
foiloWing ways.
- Firstit is described* a~~a~~yp C()Olrnon bus to the 120", distribution toth~'JdPS~nd.r~etlfied< ***:';w~*/
2 Rectifier.. outputis*fed,t6 theJri~iitterand.~verted to 12QVAC.
. '::.,::.("'):/f:':C-
,"_:.::",';<>'>;:/:':::<>-£<Y:"'-:,;,:;;'{<,,,',, '"
- 'i',~
- :.,-_
~
/',,',"
3 Safety related vitafOC.* QU~.~~eriSXt;ld;.W<UPS as.irnme9iatebilckup supply, ThErvitat.oebUSI~..~edUPbythe safety.,retateq, 125 VDC
- .!)t~tj$ID batt~~~lc:1l1S~!(~f~vita}480 VAG.
l~yer1eroutput JS,fe~thrQugl'l~l;\\st~~cSWitCh wiih:int$Q~~',niliiiu~
b~fjassswitChtO~it!l'in$tl:U~(i)Pt'~c.p¢)wer distributionp~f'leIS, Qnlo~sof invert~r OU~Ptl( the $tatic sWitchwiflselec:t backup*.regulating
., trarl$former outpu,t<~to\\tP.C)t()distributionpanels.
T~~.t)a?kup r~f~ti~,t~~f~~err~i~~ input fro~tlie:'OVAC
. stlPPl~.The ba~U~r~g~l~tin~J;~nSforrner may be ali~l"e~yia'a.
tranSfer SWitChto~ii~efofn;vo/~80VAC busses; the norfJlafsupplyor analt~mate suppl¥~'jhealt7n1!tesUppIY circuit breaker is/normally opento prevent inferconnectiotrofredundantpower supplies due toa pallels. We cannot tetf1f.t~($1S lhf01J9h a transformer,or*ifthis refers to.the alternate supplyto,~Re*i~verters.
.It is.~lso described a~~sM~' tQ.anlnverter.
Itis. then described assuppfY!Qthe battery charger i\\e'f<illo~ingaescriptiondafifi~5 ttle120.v~ital instrument AC pOwer supply to
- th.~PS:
- S~fetr4~1~~MfO
- "~~*fro~.,~(il:'Acrnotor controJ center~CC) is fed
_u 4
5
33 September 18, 2012 DCPP PPS Open Item Summary Table Page 41 of 64 No SrclRITTssue Description Ip&GE response:
I Status RAI No. I RAI Comments I
(Date Sent) I Response (Due Date)
)'!~!l6dt{anSfer switch. Thetr~nsfer sw.itchmay not be used uoder load.
f{~Etft9 the attached block diagram for additional detail.
Open Item initiated on development process. The staff therefore considers these tools to be a key (ALS SOAP) Software tools are used extensively during the FPGA (Hold) 6/5/12.
component to the assurance of quality in the ALS system development process. The ALS SOAP states that "no additional tools, techniques, or 6-13-12 update methodologies have been identified" for the ALS system. The staff (Kemper): W/ALS considers the development tools, as well as the techniques and agrees with NRC's methodologies used during system development to be relevant to the position on tools assurance of quality for the ALS system. Please provide information on the and will revise the tools, and methodologies used during system development to ensure quality document (Doc.
of the ALS system products.
No. 6002-00001) accordingly to address this matter.
PG&E response: Westinghouse agrees that Section 8, Tools, Techniques, And Methodologies of the ALS OA Plan (6002-00001) should be revised to Placed this item on reference document 6002-00030, "ALS Design Tools." This document hold pending describes the tools used and how they are used in the design process. This review of revised document is also on the ALS docket. Westinghouse will submit a revision of OA plan.
the ALS OA Plan on the ALS docket.by October 30,2012.
34 RJS I(Sp~flrelnteQ{ation Plans)The integration pla[lningdocumentation.
I Closed I RA.20
~~If~g~dinsection 4~5A ofth~1ARdoes notineJude anYin~gration of SUQ~y$tems (ALS if'1tegrat~dwith Triooo). The F'(3~.papers
..* that;~J~qijss.howFAT'sw.nlbe perfOrmed m~y,,~~~thi~PlJt
- paper~w~!Jld. ha~.!obe (jocketed asinte@ration planp!119 documents
!p~oUr~E;V\\f~illso neetltocomeJo sqmeag~~enton thE) scope
.ofintegr~tlon to be accomplished prior to Issuance onneSE:
.t~~13-12up~te (l(etTIPef}zll1iS
'$~ms dltplicate Of
~I J6 &23.
RJS
-**t~ifladequ~cles.of J~Yintegralion September 18, 2012 DCPP PPS Open Item Summary Table Page 42 of 64
-::--:-:-:----------,-,-:=P:-:::&-=GE response:
IStatus IRAI No. IRAI Comments (Date Sent)
No I siriiRil Issue DescrIptIon
Response
(Due Date)
PG&E response: I N PROGRESS 1..;7102/12.... RJ§;Th1s isrelateg to0!QI'16 and 23, hovv~ver,
. this speclf"teaflr addresses tm; softwareinte,gration planning
~
documents ~ing assessed. 1Qe current so integ~io"
!,'fI$CUSseg;irhii};*
segiion 4.5.{of the LARandtne documents
- referenced from. i.
here*do/not
..~
adequately address thisaspeCtpf system.ir:tf$gration.
A$such7Die
- 'qfegrafior\\PlanWiIl tf~ve, lobe.reVised.
Justincludtog integrationin the FAT.Will not resolve
- pl~q~'ng.i............
dQ1::ument$~..
ipattJ:tl:tat a er)taf
,..... A~J~r
.i~O(;q~~Jl.twm*leed tQbEnwbmftfed in
September 18, 2012 DCPP PPS Open Item Summary Table Page 43 of 64 No SrclR!
Issue Description P&GE response:
Status RA! No.
(Date Sent)
RA!
Response
(Due Date)
Comments i
I QrQfJr for PG~'to.
re$Oh/fJtfils.
N~w AAl.*add~d and 01.*dIOsed.
35 RA Follow up of Item 21 - Software Test Plan In the response provided for Item 21, PG&E explained that a new revision (Rev. 1) of ALS document No. 6116-00005 was provided. The scope of Revision 1 is slightly different from the scope described in Rev. O. For example, Section 1.2 in both revisions states that test coverage includes all ALS modules, backplane, license sense modules (LSM), and ALS service unit (A TU). However Section 2, Test Items, for these revisions are different.
Revision 1 only focuses on ALS-1 02 and backplane assemblies. This section does not include other ALS modules, LSM and ATU. Please explain why these other ALS modules are not included in section 2 of the new revision.
Further, Table 1-2 identifies "Diablo Canyon PPS Test Plan" as document No. 6116-00005, which is the same number than "Diablo Canyon PPS System Test Plan". Please clarify if this is referring to a different document.
OPEN PG&E Response: The scope of both revisions are the same. Revision 1 changes added more detail into the overall scope. The details are broken down into 2 main parts: 1-The individual components, 2 - The System components. Both parts equal the entire ALS based Diablo Canyon system which includes all ALS modules, Backplane, ASU (incorrectly stated as ATU in the open item), LSM, ALS-102A1B specific to Diablo and full ALS sub system test which includes the testing of ALS slave cards required by the DCPP configuration.
The entry in Table 1-2 for the Diablo Canyon PPS Test Plan, 6116-00005 is the same document as Diablo Canyon PPS System Test Plan 6116-00005.
September 18, 2012 DCPP PPS Open Item Summary Table Issue Description No SrclRI IP&GE response:
36 Software Test Plan RA Section 5.3.6 of ALS Document No. 6116-00005 refers to a "Test Team" to perform system level testing. However, the "Test Team" is not defined in ALS Document No. 6116-00000, "Diablo Canyon PPS Management Plan,"
which defines roles and responsibilities for the PPS Replacement Project.
Please clarify who is the Test Team and where their roles and responsibilities are defined.
PG&E Response: The Test team and its responsibilities are described in the ALS Test Plan, 6116-00005. The management plan describes the role of the IW manager. The test team falls under the responsibility of the IW manager. The DCPP PPS V&V Plan, 6116-00003 will be revised to explain that the test team is part of the IV&V team reporting to the IW manager.
This plan will be released by 30 September 2012.
~-
Software Management Plan 37 RA PG&E "PPS Replacement Concept, Requirements, and Licensing Phase 1 Project Plan" does not address reporting mechanisms and controlling changes to the system. The only reference is that PG&E states that they will follow the activities describe before for software modifications. After reviewing the of PG&E's SyWP, we found that Section 6 states that Anomaly Resolution and Reporting shall be performed per the respective PG&E and 1 OCFR 50 Appendix 8 supplier control procedures. However, this statement does not identify the document to follow to report anomalies.
Please identify and describe the process that PG&E will follow for reporting mechanisms.
PG&E Response: PG&E administrative procedure OM7.ID1, "Problem Identification and Resolution," provides guidance for identification and resolution of both equipment and non-equipment problems, including vendor software problems. The OM7.ID1 procedure provides the process for documenting, reporting, evaluating, trending, and tracking the resolution of problems at DCPP. PG&E administrative procedure X11.ID2, "Regulatory Reporting Requirements and Reporting Process," provides the instructions
~~ ~~~
Status OPEN OPEN RA/ No.
(Date Sent)
~-
Page 44 of 64 RA/
Comments
Response
(Due Date)
September 18, 2012 DCPP PPS Open Item Summary Table Page 45 of 64 No SrclRI Issue Description P&GE response:
-Status RAI No.
RAI Comments for reporting facility events and conditions to the NRC. This procedure applies to plant problems, including software anomalies, and provides a list of regulatory reporting requirements applicable to the DCPP, including those contained in the NRC regulations (including 10 CFR), the plant operating license (including associated Technical Specifications), license amendments, and regulatory correspondence. The procedure summarizes the types of reporting requirements and references the source of the requirement, time-frame for reporting, reporting method, lead responsible organization, primary regulatory agency recipient, and implementing procedures.
(Date Sent)
~
Response
(Due Date) 38 RA Software Management Plan OPEN Section 2 of the PG&E "PPS Replacement Concept, Requirements, and Licensing Phase 1 Project Plan" does not describe the activities to be performed by the Engineering of Choice Design Change Package Team.
It is also not clear what the roles and responsibilities of this team are.
Please clarify and provide the applicable PG&E control document that describes PG&E roles and responsibilities specifically for the Engineering of Choice Design Change Package Team.
i-=
PG&E Response: IN PROGRESS 39 RA Software Management Plan Figure 2-1 of the PG&E "PPS Replacement Concept, Requirements, and Licensing Phase 1 Project Plan" and Figure 3-1 of the SyQAP identify Altran under the PG&E Project Engineering box. However. Figure 4-1 of the SyWP identifies PG&E project team under the PG&E Project Engineering box. Please explain the role and responsibilities for Altran during the PPS Replacement Project.
OPEN
I September 18, 2012 DCPP PPS Open Item Summary Table No SrclRI Issue Description IP&GE response:
PG&E Response:
09/17/2012:
- 1. The PPS Organization Chart shown in SyWP Figure 4-1 is a simplified rendering of the organization charts in Project Plan Figure 2-1 and SyQAP Figure 3-1. The latter figures show an Altran Project Team under PG&E Project Engineering and a team of three PG&E individuals directly under PG&E Project Engineering.
The slight inconsistency between SyWP Figure 4-1 and the other figures may be resolved thus:
lPG&E Projed j
Engineering I
1 I
Lpl'Oj~~ea~
LAHran+
I
[- JOhn~
~ran_~
___.-t=I]
~tt J Il~e~ QUinnll I
Gregg u __ Clarlt.on r--L~
- 2. Altran is acting as a subcontractor providing engineering support to the PG&E Project Team as shown above in the revised figure.
Altran supported LAR preparation and is providing continuing support through the LAR review process. Altran's work is governed by the Altran Engineering Procedures Manual. Documents submitted to PG&E are prepared in accordance with Altran EOP 3.3 (reports) and 5.4 (specifications). All Altran documents are verified in accordance with Altran EOP 3.4. In addition, PG&E accepts Altran documents under PG&E CF3.ID17 as noted in the Altran
~rification Report.
~-.-.-
RAI No.
Status (Date Sent)
Page 46 of 64 RA/
Comments
Response
(Due Date)
---~--
September 18, 2012 DCPP PPS Open Item Summary Table Page 47 of 64
,-----r-:c~ --~
~--r~ --~
No SrC/RI Issue Description r----~
~-
P&GE response:
~-
Status RAI No.
(Date Sent)
~-~
Response
(Due Date)
Comments 40
~-~
RA Software Tools OPEN I
In the ALS Progress Update 2012-08-01 provided to the staff, Westinghouse/CSI described that they are replacing Automated Test Environment (ATE) from IW credited tools with a LabView based ALS Board Test System (ABTS). Also, in this presentation, Westinghouse/CSI noted that they are performing additionallV&V and equipment qualification tools.
Since this information needs to be reflected in the software planning documents, please identify how these items will affect Westinghouse/ALS documents related to PPS replacement project. Also, identify what document will be revised to include description of these modifications.
PG&E Response: The ALS Design Tools 6002-00030 requires revision to replace the ATE with the ABTS. The date for the release of this revision will be provided by September 7,2012.
41 RA 09/17/2012: Forecast release date 9/14112 for the ALS Design Tools 6002 00030.
Software V&V and Test Plan OPEN Westinghouse/ALS document 6116-0005, section 8.2 identifies the software tools to be used in the PPS replacement project. However, this list is not consistent with the list of IV&V tools identified in Section 3.6 of ALS W Plan 6002-00003. Specifically, the test tools identified in 6002-00003 are not listed in 6116-00005 and vice versa. For example, the W Plan (6002 00003) identifies ATE tool for IV&V, but this tool is not listed in 6116-0005 Rev. 1. Furthermore, the staff reviewed 6116-0005 Rev. 0, and found that the ATE tool was listed in this version. Please clarify what software tools will be used and what document describes them.
~~
~-
September 18, 2012 DCPP PPS Open Item Summary Table Page 48 of 64 No SrciR/
r~-~
'42 RA
~-~
43 RA Issue Description P&GE response:
PG&E Response: A new revision of the ALS V&V Plan 6002-00003 identifies the ABTS and the ISE as the IV&V test tools. This new revision is being docketed the week of September 3 on the ALS platform docket. The ATE is removed from the set of IV&V test tools. The tools listed in document DCPP PPS Test Plan 6116-00005 section 8.2 and the tools listed in DCPP PPS W Simulation Environment Specification, 6116-10216, (to be released by 30 September 2012) encompass the IV&V test tools in the new revision of the ALS V&V Plan, 6002-00003.
Software V&V PG&E "PPS System Replacement System Verification and Validation Plan (SyWP)" does not describe the V&V activities to be performed during the Operation Phase and Maintenance Phase. This document states that these activities are covered by approved DCPP procedures. Please identify these DCPP procedures.
PG&E Response:
09/17/2012: PG&E procedure CF2.ID2 is applicable to the Operations and Maintenance Phase per Section 5.16.10.
Software V&V PG&E "PPS System Replacement System Verification and Validation Plan (SyWP)", Section 5.1.1, explains that during the Concept Phase, PG&E will verify system requirements in accordance with PG&E procedure CF2.ID9, "Software Quality Assurance for Software Development." However, Procedure CF2.ID9 is for in-house development of software applications.
Please explain how this procedure is going to be used for the PPS replacement project.
Further, Section 5.1.2 of the CF2.1D9 states that and independent review of the functional requirements prepared during the concept phase would be performed. The PG&E SyWP does not identify this review, and thus there is no specific V&V product for this phase. Please identify who will perform this review and if this is considered a V&V product.
Status
~-~
OPEN
~-
OPEN RA/ No.
(Date Sent)
RA/
Comments
Response
(Due Date)
~-
'---~
I
September 18,2012 DCPP PPS Open Item Summary Table Page 49 of 64 No SrciR/
Issue Description P&GE response:
Status RA/ No.
(Date Sent)
RA/
Response
(Due Date)
Comments PG&E Response:
09/17/2012: Altran developed the PPS Replacement FRS during the Concept phase in accordance with Altran EOP 5.4, and verified it in accordance with Altran EOP 3.4. Altran used PG&E procedure CF3.ID16 for additional guidance. PG&E accepted the FRS under CF3.ID17, which constituted verification of system requirements. This was a design activity rather than a V&V activity and there is no specific V&V product for this phase.
44 RA Software V&V Invensys prepared Document No. 993754-1-813, "DCPP PPS Validation Test Plan". It states that the Test Review Board and PG&E will review all validation testing documents. Please describe the composition of the Test Review Board, since its role/responsibility is not described in the Invensys V&V Plan or in the Validation Test Plan (Section 4.4)
OPEN PG&E Response: IN PROGRESS 45 RA Follow up of item 18 - Software V&V RG 1.168 identifies five of the activities in IEEE Std.1012-1998, Annex G, "Optional V&V Tasks," as being considered by the NRC staff to be necessary components of acceptable methods for meeting the requirements of Appendices A and B to 10 CFR Part 50 as applied to software. These tasks are:
- 1. Audits
- 2. Regression Analysis and Testing
- 3. Security Assessment
- 4. Test Evaluation
- 5. Evaluation of User Documentation Westinghouse/ ALS Document No. 6002-00003, "ALS W Plan" describes the following techniques for V&V: reviews, testing, traceability analysis, inspection/analysis, and IV&V regression (change) analysis. This plan does not include any of the optional V&V activities identified in IEEE Std.1 012 OPEN I
September 18, 2012 DCPP PPS Open Item Summary Table Page 50 of 64 No SrclRI Issue Description P&GE response:
Status RAI No.
(Date Sent)
Response
(Due Date)
Comments 1998, Annex G. Please explain if these activities are performed.
PG&E Response: The DCPP W Plan will be revised to include these optional V&V tasks required by RG 1.168 by September 30, 2012 to align with the new ALS W Plan for the Optional Tasks.
46 RA Software V&V OPEN Several sections in the Invensys Software Verification and Validation Plan (SWP) reference "applicable Project Procedure Manual (PPM)" to perform certain activities. The reference section in this plan identifies PPM (Reference 2.4.4). It is not clear if the PPM is constituted by several procedures or if it is only one procedure. For example, Section 1.1, states the SWP was prepared in accordance with PPM 7.0 (Ref. 2.4.4), and then Section 4 states that V&V activities will be planned and scheduled in accordance with the applicable PPM. Please describe what the PPM is, and explain how this is going to be used in the PPS replacement project.
PG&E Response: IN PROGRESS 47 RA Software V&V OPEN Invensys Document No. 993754-1-802, "Software Verification and Validation Plan" requires the use ofV&V metrics to evaluate software development process and products. This section does not explain what methods and criteria will be used for software safety metrics. This information is required by section B.3.1 of BTP 7-14, RG 1.152, RG 1.173 and IEEE Stds. 1061 and 1074. Also BTP 7-14 Section B.3.1.1.2. Please provide this information.
September 18, 2012 DCPP PPS Open Item Summary Table Page 51 of 64
-~
RAt No.
RA/
Comments (Date Sent)
Response
(Due Date)
No SrC/Rt Issue Description IP~&GE response:
Status
~-~~-
PG&E Response: IN PROGESS 48 RA Software V& V PG&E SyWP, Section 6, requires that anomalies detected are identified, documented, and resolved during the V&V activities. This section states that anomaly reporting and resolution requirements are defined in the respective PG&E control procedures. Section 2 "Control Procedures does not include a reference for an anomaly reporting procedure. Please identify the PG&E control procedure used for anomaly reporting.
Further, Section 7 of the SyWP states that the PG&E authority responsible for approving deviations from SyWP is the PG&E Project Manager, who will document his/her approval a Change Notice or equivalent formal PG&E document. Please identify where the responsible PG&E authority will docum~nt its approval.
PG&E Response:
- 1. The PG&E control procedure for anomaly reporting is OM7.ID1, "Problem Identification and Resolution." This procedure governs the PPS replacement after it has been turned over to PG&E by the suppliers. The suppliers' anomaly reporting procedures are applicable prior to this turnover.
- 2. IN PROGRESS OPEN 49 RA Software V&V OPEN Invensys Document No. 993754-1-802, "Software Verification and Validation Plan", Section 6.3 states that the Invensys personnel prepared System Deficiency Integration Report (SDIR) to document non-conformances and corrective actions during testing; the SDIR is prepared in accordance with PPM 10.0. Please explain what PPM this is.
Further, the Invensys "Validation Test Plan", Section 5.4.2 states that the Test Review Board and PG&E shall review SDIRs, but this is not indicated in the Invensys V&V plan. Please explain why this review activity is not identified as a V&V task in the V&V Plan..
September 18, 2012 DCPP PPS Open Item Summary Table Page 52 of 64 No SrclRI Issue Description P&GE response:
Status RAI No.
RAI Comments (Date Sent)
Response
(Due Date)
PG&E Response: IN PROGRESS 50 RA Software V& V OPEN The Invensys Validation test plan, Section 8.2, states that the Narrative Test Logs are used to document conduct of testing and any anomalies that occur. Please explain if this is only used during validation, and why this is not mentioned in the Invensys SWP. Further, please explain how is this used in conjunction with Document Review Comment Sheet (ORCS) and System Deficiency Integration Report (SDIR)?
PG&E Response: IN PROGRESS 51 RA Software Configuration Management See Attachment 2.
OPEN PG&E Response:
09/18/2012:
- 1. Configuration Process
- a. ALS-102 Configuration The FPGA installed on the ALS-1 02 board and therefore the ALS 102 board itself is specific to the PPS Protection set and the ALS subsystem in which it is installed. PG&E will not have the capability to alter the FPGA. Any change to the FPGA must be made by CS Innovations under their V&V program. Therefore, ALS-102 FPGA configuration management activities are covered by the ALS Configuration Management Plan. PG&E capability to change ALS 102 configuration will be limited to board-level replacement.
September 18,2012 DCPP PPS Open Item Summary Table Page 53 of 64 No I SrclRI I Is sue Description IP&GE response:
Status RAI No.
'RA/
Comments (Date Sent)
Response
(Due Date)
- b. NVRAM Configuration ALS 110 boards are generic; that is, each board is configured using its NVRAM for the specific function it is to perform. This activity is described in SCM 36-01 Section 1.2.8, which states that the configuration of the NVRAM is changed by removing the subject board from the ALS chassis and inserting it into a special test fixture. This would be performed as part of a maintenance activity, such as replacing a failed board. If the functionality of an 110 board required modification as a result of an application change, all required NVRAM configuration alterations would be performed by CS Innovations under their ALS Configuration Management Plan.
As with the ALS-102 FPGA discussed above, PG&E will not have the capability to alter the NVRAM configuration itself. PGE capability to change the NVRAM configuration for a specific 110 board will be limited to loading NVRAM images that are under CS Innovations configuration control and that have been previously verified and validated at the system level by CS Innovations.
Configuring the NVRAM in order to replace an 110 board will be performed by PG&E under an approved plant maintenance procedure.
- c. Invensys SCMP
[IN PROGRESS]
- 2. Organization
- a. SCMP Inconsistent with CF2.I02
[IN PROGRESS]
- 3. Changes and Problem Identification
- a. PROG POCM Notification Process
[IN PROGRESS]
September 18,2012 DCPP PPS Open Item Summary Table Page 54 of 64 No SrclRI Issue Description P&GE response:
Status RAI No.
(Date Sent)
Response
(Due Date)
Comments
- b. Tracking changes in SAP
[IN PROGRESS]
- 4. Document Repository
- a. SourceSafe vs. SC-I-36-M
[IN PROGRESS]
- b. Control of Access to PPS Replacement Documentation
[IN PRGOGRESS]
52 RJS NSIR Security:
PG&E stated in its letters DCL-11-123 and DCL-11-1 04 that the PPS replacement will be fully compliant with the 10 CFR 73.54 cyber security requirements, including RG 5.71, Revision 0, "Cyber Security Programs for Nuclear Facilities," dated January 2010, and is being reviewed to comply with 10 CFR 50.73, the DCPP Cyber Security Plan, and NEI 08-09, "Cyber Security Plan for Nuclear Power Reactors," Revision 6, dated April 2010.
The cyber security program that PG&E is implementing per its NRC approved cyber security plan includes provisions applicable to all phases of a systems' life cycle, including the digital upgrade or modification of critical digital assets.
Please explain how the provisions outlined in the PG&E's NRC-approved cyber security plan were considered, and/or implemented, as part of the PPS replacement. The provided explanations should include how all of the management, operational, and technical security controls contained within the plan. especially security controls associated with Configuration Management and System and Service Acquisition, are being addressed.
The provided explanations should also include any issues associated with partial implementation of the PPS replacement and full implementation of the cyber security plan for the site, and processes to identify and resolve Open
~ -
....-..-.-.......~ -
September 18, 2012 DCPP PPS Open Item Summary Table Page 55 of 64 No SrclR/
Issue Description P&GE response:
Status RA/ No.
(Date Sent)
RA/
Response
(Due Date)
I Comments any such issues.
I PG&E Response:
The Gyber Security program manager and other members of the GSA T (Gyber Security Assessment team) met with the Process Protection System (PPS) Upgrade design engineer beginning in 2011. Many options were discussed.
The Gyber Security program manager and project manager have met with the procurement group to discuss cyber security principles that should be written into the procurement procedures, and what steps will help to ensure a secure supply chain.
The Gyber Security Assessment Team (GSAT) was formed in accordance with section 3.1.2 of the cyber security plan, and Milestone a, on 10/31/2011. A list of critical digital systems and assets was created in accordance with section 3.1.3 of the cyber security plan and Milestone b on 10/31/2011. The GSAT looked at scheduled digital upgrades, and added the future equipm~nt to the list of critical digital systems. The GSAT determined the PPS equipment will be a critical system, with several GDAs.
From July 9-12 2012, the cyber security project manager accompanied members of the Quality Verification group to examine the design and production facilities of Invensys, and examined the code production practices and the development environment, and determined that Invensys has an SDE, and ensures their employees are reliable and trustworthy.
Activities planned for the future.
In December of 2012, the network that the PPS will eventually reside on will
September 18, 2012 DCPP PPS Open Item Summary Table Page 56 of 64 No Src/RI Issue Description P&GE response:
Status RAI No.
(Date Sent)
Response
(Due Date)
Comments be isolated from internet connected networks by a deterministic network device, per milestone c of the DCPP Cyber Security Plan. Thus many network attacks, including many that depend on a back door created by a vendor, will not be possible.
Also by December of 2012, DCPP will have taken steps to lessen the likelihood of an attack initiated by a portable electronic device, or portable media such as a thumb drive per Milestone d, and section D 1.19 of NEI 08
- 09. This will mitigate portable media based attacks that depend on a back door created by a vendor.
The DCPP Cyber Security Team will interface with NUPIC (Nuclear Procurement Issues Committee) and the NEIINITSL counterfeit parts task force to address digital equipment supply chain security.
The Cyber Security Implementation Project Manager has developed a detailed project plan, with several tasks and schedules. Several existing plant procedures will be revised. The PPS will inherit the controls implemented by these procedures. Many of the procedures will have been changed/created before the PPS is installed.
The CSA T is collecting design information as it becomes available. The collected design documentation is being reviewed as it is collected. The collected documentation will be reviewed in a formal desktop evaluation per the cyber security plan, section 3.1.5 prior to the PPS installation. The test set up in the offsite test lab near the plant will be visited on occasion by the CSAT, the system will be walked down repeatedly during installation, and the final walkdown will be performed when the system is ready to return to operations, per section 3.1.5 of the security plan.
The CSA T will make recommendations to enhance the cyber security posture of the PPS upgrade throughout the project, and will make their final
53 54 September 18,2012 DCPP PPS Open Item Summary Table Page 57 of 64
~-~
~~
No Status RAt No.
RAt SrC/RI Comments (Date Sent)
Issue Description IP&GE response:
Response
(Due Date)
--~
reci mmendations after the system walkdown, per section 3.1.6 of the cyber sec ty plan.
Disl o ;ition of all controls will be documented in the cyber security ass
,ment tool, CyberWiz. Recommended mitigation will be documented in Cy erWiz, and the Corrective Action Program.
RJS WEK Sec m 4.10.2.6.3 of LAR:
Ate c 1 specification change resulting from the recent Eagle 21 failure that affeC' ed the operability of the AFW control system is being reviewed by the staf As part of this review PG&E has stated that the Independence be~ !en safety systems and other systems clause is not being met for all con tions of operation. If this is the case, then why does the PPS LAR not ider t fy any exceptions to IEEE 603 clause 5.6.3? Even if the replacement PP~ joes not have an equivalent failure mode to the Eagle 21 system, the TS lange would still apply after the upgrade is completed. The staff will need to confirm that the potential for this failure mode has been eliminated in tt e new design or that the criteria of IEEE 603 is otherwise beeing sati ed.
PG4
- Response: None Required PG4
- Letter DCL-12-050, Phase 2 Documents, Attachment 2 FSAR Ch;: nges, Insert 1 for FSAR Section 3.10.2.1.3 states that "The Pro iSS Protection System Trieon subsystem has been seismically qualified by I rensys Operations Management (see Reference 40) in accordance with equirements from Reference 44 that is endorsed by Reference 33."
Wh, t is reference 44 and where is this documented in the FSAR?
PGc
- Response: Reference 44 IEEE 344-1987, the current Reference 44 in it e FSAR. See FSAR page 3.10-40 that was included in the FSAR cha les in PG&E Letter DCL-12-050, Phase 2 Documents, Attachment 2.
~-~
Closed 9/11/12 - Per CC with PG&E, the position on compliance with IEEE 603 5.6.3 is being revised and there is no plan to take exception with this or any other criteria of IEEE 603.
OPEN New L-~~
September 18,2012 DCPP PPS Open Item Summary Table Page 58 of 64 No SrciR/
/ ssue Description P&GE response:
Status RA/ No.
RA/
Comments (Date Sent)
Response
(Due i--.
55 WEK PG&E Letter DCL-12-050, Phase 2 Documents, Attachment 2 FSAR OPEN
. Date)
Changes, FSAR Section 7.1.2.5, Conformance With Other Applicable New Documents (page 7.1-13) does not indicate the NRC Safety Evaluation that will be produced to approve the PPS. The staff's SER should become part of the DCPP Unit 1&2 licensing basis once it is issued. How will this be documented within the FSAR??
PG&E Response: Reference to the staff SER will be included in FSAR Section 7.2.1.1.6 for the reactor trip portion of the process protection system and to Section 7.3.1.1.4.1 for the engineered safety features actuation system portion of the process protection system.
56 WEK PG&E Letter DCL-12-050, Phase 2 Documents, Attachment 2 FSAR OPEN Changes, FSAR Section x.x.x.x, (page 7.2-23) states that the evaluation for New the common mode failure in the PPS is pre.sented in References 37 [DCPP PPS D3 L TR] and approved in Reference 38 [the staff's SER approving the DCPP PPS D3 L TR]. However, it is noted that in the staff's SER it was stated in several sections that the D3 design features were approved based on "... confirmation that the proposed built-in diversity of the ALS sub-system is found to be acceptable." This confirmation will be provided in the DCPP PPS SER, therefore, the staff's SER should also be referenced in this section.
~E Response: Reference to the staff SER for LAR 11-07 will be included in FSAR Section 7.2.2.1.2 in addition to the staff SER for the DCPP D3 LTR.
57 WEK PG&E Letter DCL-12-050, Phase 2 Documents, Attachment 2 FSAR OPEN Changes, FSAR Section 7.2.2.9.2, IEEE 603-1991 Clause 5, Clause 5.12 New (page 12) states that"... the communication path between the maintenance workstation and the ALS subsystem is normally disabled with a hardwired switch... " Also, Attachment 3, PG&E PPS Interface Requirements Specification (IRS), Rev.6 to PG&E Letter DCL-12-069 dated August 2, 2012 states in section 1.5.6 "... TAB communications between the ALS and MWS takes place via RS-485 data link. The TAB is physically disconnected from the MWS when the TAB is not in use.... the TAB is open at all times unless maintenance is being performed on the ALS... " Please identify administrative controls and design features associated with the PPS that explains how the MWS is disconnected/disabled from the PPS (Le., a means of physical c~ble disconnect, or a safety-qualified hardware switch
58 September 18,2012 DCPP PPS Open Item Summary Table Page 59 of 64
--:-:~~
~-~
No Issue Description P&GE response:
SrclRI that either physically opens the data transmission circuit or interrupts the connection by means of hardwired logic. "Hardwired logic" as used here refers to circuitry that physically interrupts the flow of information, such as an electronic AND gate circuit (that does not use software or firmware) with one input controlled by the hardware switch and the other connected to the information source: the information appears at the output of the gate only when the switch is in a position that applies a TRUE or "1" at the input to which it is connected. Provisions that rely on software to effect the disconnection are not acceptable. It is noted that software may be used in the safety system or in the workstation to accommodate the effects of the open circuit or for status logging or other purposes) that demonstrate how this hardwired switch disconnects the ALS maintenance workstation from the ALS safety processor.
r-pG&E Response: For the ALS subsystem, instead of using a hardwire keyswitch, the ALS subsystem will be administratively controlled by physically disconnecting the communication link to the ALS MWS computer when the Test ALS Bus (TAB) is not being used for surveillance testing, maintenance, and trouble-shooting. This is a PPS replacement design change described in the response to NRC request for additional information in PG&E Letter DCL-12-083 and will be included in a sup~lement to LAR 11-07.
RJS ALS FMEA - There are several failure modes identified in Table 4-4 of the FMEA where the System Effects entry provides a description of functions that are not affected by the failure mode instead of stating what the effects of the failure mode are. For example, the System Effects in the ETT failure in line 5b of table 4-4 are that the Alarm Function remains operational.
Though this may be the case, it does not state what the effects of the failure mode are. Examples of this can be found in lines 5b, 6a, 6b, 7a, 9h, 9i, 11 b, 11c, and 11d.
Status Open New RAI No.
(Date Sent)
RA/
Comments
Response
(Due Date)
PG&E Response:
09/17/2012: ALS response forecast 09/30/2012
September 18, 2012 DCPP PPS Open Item Summary Table Page 60 of 64
,------~
No Src/RI Issue Description P&GE response:
Status RA/ No.
RA/
Comments (Date Sent)
Response
(Due Date)
~-~
59 RJS ~-
r---~
Open ALS FMEA Some of the identified failure modes of the ALS system are New detectable only by operator observations, or by means that are not necessarily performed during routine operation or during surveillance I
testing. See lines 10c, and 12a, What measures will be implemented to ensure that these failure modes would not occur and remain undetected for an indefinite period of time?
It is the staffs understanding that all failure modes which are not detectable through normal means such as surveillance tests or channel checks would need to be considered present for the purpose of satisfying single failure criteria for the system.
~-~
PG&E Response:
~-~
0~/17/2012: ALS response forecast 09/30/2012 t---~ ~--~~
PG&E Response:
~-~
~-~
PG&E Response:
~-~
PG&E Response:
~-~
PG&E Response:
~-~
September 18, 2012 DCPP PPS Open Item Summary Table Page 61 of 64 No SrclRI
--~
Issue Description P&GE response:
Status RAI No.
(Date Sent)
RAI Respofl'se (Due Date)
Comments PG&E Response:
PG&E Response:
September 18, 2012 DCPP PPS Open Item Summary Table Page 62 of 64 Figure 1 DCPP 120 Volt Vital Instrument AC System (Simplified) 5D11 (21)
.. j
[~..s;A.~.;.I;~cll..//!
IS~T:Lt Transfer Switch DC DC Transfer 5D13 (23)
To Protection Set IV BUS 1H (2H)
SWItch T
[AC~~..
~~
DC I r Transfer SwitCh To Protection Set I To ProteCtiOn Set 11 To Protection Set III Legend:
IY:
UPS and DC-AC Inverter PY:
120 VAC Distribution Panel SD:
125 VDC Distribution Panel TRY:
480 VACI120 VAC Transformer and Regulator Normal Power Flow (N)
Bypass (120 VAC)/Backup (125 VDC) Power Flow Alternate Bypass Power Flow (A)
Unit 1 Component ID's are shown; Unit 2 Component ID's are in parentheses. For example, PY11 is Unit 1 Vital Instrument AC Distribution Panel 1; PY21 is Unit 2 Vital Instrument AC Distribution Panel 1.
September 18, 2012 DCPP PPS Open Item Summary Table Open Items Related to Software Configuration Management Plan
- 1)
Configuration process a) In open item 4, the staff requested description of the software configuration management activities for configurable boards (e.g., ALS FPGA-102 board). Since the ALS FPGA-102 board is customer specific, its configuration management activities are not covered by "ALS Configuration Management Plan."
Even though item 4 is closed, this request was not addressed in the response for item 4.
b) The PG&E SCM 36-01, item 1.2.8, states that ALS board has two sets of NVRAM. Further, it explains that the configuration of the NVRAM can be changed only by removing the subject board from the ALS chassis and inserting it into a special test fixture. It is not clear who will control this process and configuration of the NVRAM. Please explain.
c) Section 1.2 of the Invensys Document No. 993754-1-909, "Software Configuration Management Plan,"
states that this plan controls operating system of the computers used to run TriStation 1131 and the signal simulation software used for testing purpose. However, the description provided throughout the plan only focuses on the configuration activities for the TSAP (e.g., Section 2.3 states that the SCM procedures are for the TSAP). Further, this same section (later on) identifies the software configuration to be managed, and this list does not include operating system of the computers used to run TriStation 1131 and the signal simulation software used for testing purpose. Please clarify the scope of this plan.
- 2)
Organization a) The organization and responsibilities described in Section 4 of CF2.ID2 is not consistent with the information presented in Section 2 of SCMP 36-01. For example, Section 2 of SCMP 36-01 identifies system coordinator, application sponsor, and system team, who are not identified in Section 4 of Cf2.ID2. Further these descriptions are not identified in the project organization described in PG&E PPS Replacement Plan (Attachment 3 of the LAR). Please clarify the roles and responsibilities for SCM, and provide a cross reference of the PG&E organizations described in these documents.
- 3)
Changes and Problems Identification a) PG&E SCMP36-01 states that software, hardware, and configuration problems are reported in accordance with PG&E OM7.ID1 and that software and/or configuration problems are reported via a PROG PDCM Notification. Please clarify when and how these are used. For example, for software problems does one have to report the problem using both PG&E OM7.ID1 and PROG PDCM Notification. Note that PG&E CF2.ID2 states that all problems associated with plant computer system should be reported and document per OM7.ID1 (See section 5.11 and 5.16.10 (b) of CF2.ID2)
Further, Section 3.2.1 states that all PPS modifications should be initiated and tracked per plant procedures or CF4.ID1. Section 3.2.2 states that the implementation of the change is documented in the associated Change Package and a SAP notification and order. And Section 3.2.10 states that all identified problems and corrective actions using a notification, which is not specified.
So should.software modifications require reporting and tracking using OM7.ID1, CF4.ID1, PROG PDCM Notification, Change Package, and SAP Order?
Please explain PG&E procedures for different changes and the documenting and tracking system used for all types of modification.
b) Please clarify the means to track changes. Section 3.2.4.7 of the SCM 36-01 states that this is done using a SAP order, but Section 3.2.4.7 states that Change Package and SAP order are entered in the
September 18, 2012 DCPP PPS Open Item Summary Table Record Management System, and Section 3.3 describes a Configuration Status Account I which is used to track changes of configuration items.
- 4) Document Repository a) SCM 36-01, Section 2.3.3 identifies the Digital Systems Engineering SourceSafe as the repository, but Section 3.2.5.5 identifies http://dcpp142Iidmws/home/asp, and Section 3.29 states that the files necessary for recovery of the baseline are maintained in the PPS database in SC-I-36M, Eagle 21 Tunable Constants." It is not clear if these two sections are referring to the same document reporsitory or if it is the same. Please clarify b) PG&E has implemented restrictions to access files and documents associated with PPS replacement project. Further, PG&E requires user authentication and access to edit configuration, software, and data. It is not clear if these restrictions apply for access to the Digital Systems Engineering SourceSafe or the repository in http://dcpp142/idmws/home/asp.
Approach to Justify the Applicability of WCAP-14333 and WCAP-15376 Technical Specification Changes to the Triconex/AlS System at Diablo Canyon Issue: The Technical Specification changes to the process protection system justified in WCAP-14333 and WCAP-15376, and approved by the NRC, apply only to currently operating process protection systems (7100, 7300, Eagle 21). A justification for the applicability of these changes to the Triconex/ALS system needs to be developed.
Background:
WCAP-10271-P-A; WCAP-10271, Supplement 1-P-A; WCAP-10271-P-A, Supplement 2, Rev. 1; WCAP-14333-P-A, Rev. 1; and WCAP-15376-P-A, Rev. 1 (References 1-5) provide the justification for extending completion times, bypass test times, and surveillance test intervals for components in the reactor protection system. The reactor protection system components include the analog channels, logic cabinets, master and slave relays, and reactor trip breakers. The analysis supporting these changes is based on the Westinghouse 7300 process protection system. A justification was previously developed that extended the applicability of these changes to the Westinghouse Eagle 21 Process Protection System.
The NRC's Safety Evaluation associated with WCAP-15376 specifically stated "For future digital upgrades with increased scope, integration and architectural differences beyond that of Eagle 21, the staff finds the generic applicability of WCAP-15376-P, Rev. 0 to future digital systems not clear and should be considered on a plant-specific basis." Based on this statement, it is concluded that the applicability of the TS changes justified in WCAP-15376-P-A, Rev. 1 to digital systems other than Eagle 21 needs to be justified. Similar statements are not included in the NRC's Safety Evaluations for WCAP-10271-P-A with Supplements 1 and 2 or for WCAP-14333-P-A, Rev. 1, but it would be prudent to provide such a justification to cover all the changes justified in these WCAPs.
Approach to Justification: A qualitative approach will be used to assess the applicability of the WCAP changes to the Triconex/ALS system. This assessment will involve a comparison of the Triconex/ALS system to the Eagle 21 system. The idea is to demonstrate qualitatively, based on system design, signal development, backup systems, etc., that the Triconex/ALS system is equal to or better than Eagle 21 with regard to the reliability of protection signal development. Since the WCAP changes are applicable to the Eagle 21 system, and if the Triconex/ALS system is equivalent to or better than the Eagle 21 system, then the WCAP changes should be applicable. This assessment will include a detailed review of the Triconex/ALS and Eagle 21 system designs with regard to structure and architectural differences, protection signals, common cause failures, and self-check features, and will include, as necessary, available failure modes and effects analyses and reliability assessments.
References
- 1.
"Evaluation of Surveillance Frequencies and Out of Service Times for the Reactor Protection Instrumentation System," WCAP-10271-P-A, May 1986.
- 2.
"Evaluation of Surveillance Frequencies and Out of Service Times for the Reactor Protection Instrumentation System, Supplement 1," WCAP-10271, Supplement 1-P-A, May 1986.
- 3.
"Evaluation of Surveillance Frequencies and Out of Service Times for the Reactor Protection Instrumentation System," WCAP-10271-P-A, Supplement 2, Revision 1, May 1989.
- 4.
"Probabilistic Risk Analysis of the RPS and ESFAS Test Times and Completion Times,"
WCAP-14333-P-A, Revision 1, October 1998.
- 5.
"Risk-Informed Assessment of the RTS and ESFAS Surveillance Test Intervals and Reactor Trip Breaker Test and Completion Times," WCAP-15376-P-A, Revision 1, March 2003.
- 3 The NRC staff and PG&E discussed the information found in Enclosure 3, associated with Eagle 21 Technical Specification (TS) applicability to the replacement PPS. The issue is whether or not a justification for the applicability of the Eagle 21 TSs needs to be developed for the replacement PPS. There was agreement that such a justification is needed and that it will be reviewed by the staff as part of its review of the LAR. The staff took an action to add a new open item to the open item tracking table to track the issue.
The NRC staff and PG&E discussed several of PG&E's proposed responses found in Enclosure 2. Based on interactions during the meeting, PG&E took an action to modify some of the responses to address issues that the staff identified.
PG&E will provide the revised response to the staff prior to the next meeting.
The revised responses and any new issues identified by the staff will be updated in the master open item tracking table and will be discussed at the next public meeting tentatively scheduled for October 17, 2012.
Please direct any inquiries to me at 301-415-1132 or at Joseph.Sebrosky@nrc.gov.
IRA!
Joseph M. Sebrosky, Senior Project Manager Plant licensing Branch IV Division of Operating Reactor licensing Office of Nuclear Reactor Regulation Docket Nos. 50-275 and 50-323
Enclosures:
- 1. List of attendees
- 2. Staff identified issues
- 3. Information related to Eagle 21 TS Applicability cc w/encls: Distribution via Listserv DISTRIBUTION:
PUBLIC RidsNsirDsp Resource SAchen, RIVlDRS/EB2 LPLIV Reading RidsOgcRp Resource ELee, NSIRIDSP/CSIRB RidsAcrsAcnw _MailCTR Resource RidsRgn4MailCenter Resource DParsons, NSIR/DSP/CSIRB RidsNrrDeEicb Resource SKennedy, EDO RIV GSimonds, NSIR/DSP/CSIRB RidsNrrDorl Resource TWertz, NRR THarris, NSIRIDSP/FCTSB RidsNrrDorlLpl4 Resource WKemper, NRR/DE/EICB MShinn, NRC/CSO RidsNrrDraApla Resource RStattel, NRR/DE/EICB CNickell, NRR/DLR/RAPB RidsNrrDssStsb Resource RAlvarado, NRR/DE/EICB MSnodderly, NRR/DRAIAPLA RidsNrrLAJBurkhardt Resource WMaier, RIV KBucholtz, NRR/DSS/STSB RidsNrrPMDiabloCanyon Resource SMakor, RIV/DRS/EB2 ADAMS Accession Nos. Meeting Notice ML12240A075; Meeting Summary ML12284A445
- via email OFFICE NRRlDORULPL4/PM NRRlDORULPL4/LA NRRlDE/EICB NSIRIDSP/CSIRB NRRlDORULPL4/BC NRR/DORULPL4/PM NAME JSebrosky JBurkhardt*
RStattel DParsons*
MMarkley JSebrosky DATE 10/15/12 10111112 10/12112 10/15/12 10/15/12 10/16/12 OFFICIAL RECORD COpy