ML14029A450

From kanterella
Jump to navigation Jump to search

Summary of 12/18/13 Meeting with Pacific Gas and Electric Company to Discuss Digital Replacement of Process Protection System at Diablo Canyon Power Plant, Units 1 and 2
ML14029A450
Person / Time
Site: Diablo Canyon  Pacific Gas & Electric icon.png
Issue date: 12/10/2014
From: Siva Lingam
Plant Licensing Branch IV
To:
Benney B
References
TAC ME7522, TAC ME7523
Download: ML14029A450 (16)


Text

LICENSEE: Pacific Gas and Electric Company FACILITY: Diablo Canyon Power Plant, Unit Nos. 1 and 2

SUBJECT:

SUMMARY

OF DECEMBER 18, 2013, 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, UNIT NOS. 1 AND 2 (TAC NOS. ME7522 AND ME7523)

On December 18, 2013, 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 Pike, Rockville, Maryland. The meeting notice and agenda, dated November 25, 2013, is available in the Agencywide Documents Access and Management System (ADAMS) at Accession No. ML13312A646. 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 (DCPP) (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.

Highlights from this meeting on December 18, 2013, include the following:

  • The project plan for the review of the LAR (Enclosure 3) was discussed and the major upcoming milestones were confirmed. The project plan will be updated as appropriate and discussed at the next public meeting.
  • The NRC staff discussed reduced review efforts until the next planned submittals in March or April 2014, following the DCPP planned refueling outage in February.
  • The NRC staff discussed the development of an audit plan for TRICOM in M<;~y and ALS in June 2014.
  • The revised* document submittal schedule was discussed and NRC staff informed the licensee that revisions to the Software Design Description documents will not

need to be submitted to the NRC as long as the staff has access to the current versions of these documents on the Share Point site. All other planned Share Point availability and submittal dates are acceptable to the staff.

  • The licensee agreed to provide support for the upcoming Office of the Advisor-Y Committee on Reactor Safeguards (ACRS) subcommittee meeting on
  • February 18, 2014. A draft copy of the staff's presentation is available to the licensee on the SharePoint site. A presentation to the full ACRS committee is scheduled for March 2014.
  • A third request for additional information (RAI) letter will be sent to the licensee in January with an expected response in March of 2014. These RAis are being derived from Open Items that have been previously discussed. References to these RAis are being added to the open items table.
  • The NRC staff and the licensee agreed that the next periodic teleconference public meeting on this topic would be held during the seQond week of February 2014. .

Please direct any inquiries to me at 301-415-1564 or at Siva.Lingam@nrc.gov .

Siva P. Lingam, Project Manager Plant Licensing Branch IV-1 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 That are Open
3. Project Plan cc w/encls: Distribution via Listserv

LIST OF ATTENDEES DECEMBER 18, 2013, TELECONFERENCE MEETING WITH PACIFIC GAS AND ELECTRIC COMPANY REGARDING DIGITAL UPGRADE FOR DIABLO CANYON POWER PLANT, UNIT NOS. 1 AND 2 DOCKET NOS. 50-275 AND 50-323 NAME ORGANIZATION K. Schrader Pacific Gas and Electric S. Patterson Pacific Gas and Electric A. Wilson Pacific Gas and Electric .

J. Hefler Altran R. Lint Altran K. Durinsky Westinghouse D. Head lnvensys R. Stattel Nuclear Regulatory Commission (NRC)

R. Alvarado NRC

  • B. Benney NRC G. Clefton Nuclear Energy Institute Enclosure 1

-February 4, 2014 DCPP PPS Open Item Summary Table Page 1 of 9 No Src!RI Issue Description P&GE response: Status RAI No. RAt Comments (Date Sent) Respons e

(Due Date) 60 RJS Technical Specifications: Open RAI39 12/12/13 - RJS sent (STSB/A draft evaluation PLA) In order for the staff to make a determination that the existing technical write-up to Karl for specifications and surveillance intervals remain acceptable for the review.

replacement PPS system, an evaluation to compare the ALS/Tricon PPS system reliability and performance characteristics with those of the Eagle 21 10/24/13- RJS system must be performed by PG&E. Reviewed the evaluation Please provide an evaluation summary report to support the application of document.

existing technical specification and surveillance test intervals to the upgraded ALS/Tricon based PPS system. This summary report is expected Carl Schulten is to include a quantitative analysis to demonstrate the new system's ability to taking over for perform its required safety functions between established surveillance test Christy. Information intervals. This report should also include a qualitative (i.e., deterministic) sent to Karl.

analysis which describes the self diagnosis and fault detection features of. Awaiting _feedback.

the replacement PPS. In addition, this summary report should address the staff's previous findings in Section 4.3, "Applicability of WCAPs to DCPP," of Amendment No. 179, dated January 31,2005 (ML050330315).

PG&E Response: An evaluation summary report to support application of the exiting TS and TS surveillance test intervals is contained in the Westinghouse Document, "Justification for the Application of Technical Specification Changes in WCAP-14333 and WCAP-15376 to the Tricon/ALS Process Protection System" that was submitted in Attachment 9 to the Enclosure of PG&E Letter DCL-13-016 dated March 7, 2013. The document provides. a qualitative comparison of features important to the reliability of the Tricon and ALS subystems and the Eagle 21 system, evaluates the applicability of the WCAP-14333 P A, Revision 1, and WCAP-15376-P-A, Revision 1, analyses to the PPS replacement configuration, and evaluates the compliance with the staff conditions and limitations contained in the NRC safety evaluations for WCAP-14333 and WCAP 15376 and Section 4.3 of the Amendments 179 and 181.

Enclosure 2

February 4, 2014 DCPP PPS Open Item Summary Table Page 2 of 9 No Src!RI Issue Description P&GE response: Status RAJ No. RAJ Comments (Date Sent) Respons e

(Due Date) '

I 93 RJS (ALS Audit Item) 12/12/13- RJS I Open Current version of The RTM for the ALS subsystem was prepared using Westinghouse 6116-00059 on document WNA-DS-02442 to trace PG&E requirements. The IV&V team sharepoint is "0."

found that Westinghouse document WNA-DS-02442 does not capture all This does not PG&E requirements (see descriptions for Tickets #4787 and #4800). Please establish traceability 1 I

provide a description of how this issue is being resolved. to the Core FPGA I PG&E Response: Design The 6116-00000 Diablo ALS Management Plan, revision A, specifies an Specifications.

updated document structure that has all PG&E Customer Requirements feeding directly into the 6116-00011, which will flow down into all ALS Diablo 10/16/13- RJS-New sub-ordinate requirement and design specifications. Westinghouse RTM still does not

  • I I

document WNA-DS-02442 has been removed from the document establish traceability hierarchy. 6116-00000, revision 4, 6116-00011, revision 1, and the 6116- to the 6116-10203, 00059 RTM, revision 0, are all reflective of this new document structure. and 6116-10204 Documents 6116-00011, revision.1, was submitted under PGE Letter DCL- Core FPGA Design 13-087 dated September 17, 2013. The next revision of the 6116-00059 Specifications.

RTM, Revision 1, will include traceability to the Core FPGA Design Specifications, and is expected to be submitted in June 2014. Also A new revision of 6116-00059 will need to be docketed due to the significance of.

changes made since the original document was submitted.

(

6116-00011, ALS SDS, revision 1 6116-00059 ALS RTM, revision 0 They are both

February 4, 2014 DCPP PPS Open Item Summary Table Page 3 of 9 No Src/RI Issue Description P&GE response: Status RAI No. RAI Comments (Date Sent) Respons e

(Due Date) available in the Sharepoint SDS Rev. 0 is already on docket.

[ML11277A152]

RTM to be submitted on Docket.

94 RJS The ALS T apical Report Plant Specific Action Items will be made available to Open RAI59 12/12/13- RJS A Westinghouse. When these are available, PG&E should prepare a version of the ALS document to identify how each applicable PSAI is being addressed for the TR I SE is now PPS project. This document should include references to the LAR and available and being supporting documents where PSAI's are addressed. reviewed.

PG&E Response: . .

The response to the ALS ASAis requires input from Westinghouse and a contract has been created to supply the required information. The response is expected to be submitted by 3/31/13.

101 RJS Phase 2 Environmental Qualification Documentation: Open RA161 12/11/13- RJS Seismic Reports Per ISG 6 Section 0.5.1, the NRC staff needs to review the information posted on provided to determine if the PPS equipment has been demonstrated to be sharepoint. Further able to operate within the specified environment. In order to do this the plant specific staff needs to have plant specific environmental data for the plant and information including specifically for the cable spreading room. The ISG 6 matrix (item 2.12) ping tests of PPS states that this information has been provided in the two vendor topical cabinets is still reports, _however, these reports do not contain any plant specific data. needed for evaluation.

The NRC requires plant specific environmental condition data for normal operating conditions and the worst conditions expected during abnormal and 11/1/13-RJS accident conditions where the PPS equipment is expected to perform its Waiting for additional safety function. testing to be completed.

  • Range of temperature and humidity conditions that are expected in the cable spreading room. PG&E to provide

February4, 2014 DCPP PPS Open Item Summary Table Page 4 of 9 No Src!RI Issue Description P&GE response: Status RAI No. RAI Comments (Date Sent) Respons e

(Due Date)

  • Seismic*data for the Diablo Canyon OBE and SSE estimate of

. earthquakes including frequencies and acceleration values. completion for next

  • EMI I RFI data for areas where *PPS equipment is to be call .

installed.

6/26/2013: during The FRS section does specify the ranges of temp and humidity but for this call the following seismic environment, it refers to documents DCM C-17, DCM C-25, DCM C- clarifications were 30, DCM C-28, and DCM T-10. provided:

- Describe specific Note: The required information may also be contained in the UFSAR. The conditions for the staff is reviewing design basis information in the UFSAR, however specific room where the environmental conditions applicable to the PPS equipment remain unclear to system will be the staff. installed.  !

- Is there any PG&E Response: PG&E provided seismic information in the document titled "Westinghouse Seismic Test Report EQLR-2248, Rev. 1" on the Sharepoint restrictive I requirement for this on 12/3/13. Additional testing is required for the PPS cabinets to be used '

room?

that is expected to be completed in May 2014.

-What is the relationship between the system specification requirement and environmental conditions?

108 RJS Phase 2 Document Status Assessment: Open 12/11/13- RJS Tricon Reliability The staff performed an assessment of the phase 2 document matrix and Analysis document is would like to discuss several items in the table. on sharepoint.

Schedule for We recognize that some of these items will not be available until after the submittal of all FAT is performed, however, there are several other phase 2 documents that documents still should be available now. We have identified the following documents that needs to be should not require completion of the design or FAT that have not yet been provided.

submitted. We will need a revised schedule for submittal of these documents by November 301h in order for us to proceed with the safety evaluation.

February 4, 2014 DCPP PPS Open Item Summary Table Page 5 of 9 No Src!RI Issue Description P&GE response: Status RAJ No. RAJ Comments (Date Sent) Respons e

(Due Date)

WSR's for phases of development beyond Planning/Req. (Both Vendors)

Tricon 993754-1-819, Reliability Analysis Tricon 993754-1-811, Project specific platform FMEA (IEEE 352)

PG&E System level FMEA Tricon 993754-1-812, Validation Test Specification (Integrated System)

Tricon 993754-1-868, Software Verification Test Plan PG&E Response:

PG&E is working with each Vendor to determine the submittal dates for the remaining Phase 2 documents not related to FAT testing that still need to be submitted. The schedule for the outstanding lnvensys documents was provided on the Share point on 12/17/13.

109 RJS Audit Preparation: Open NoRAI 11/1/13- RJS 6116-00050 to be put on In preparation for the follow-up audits at lnvensys and at Westinghouse, the sharepoint. Tricon staff would like to have access to the configuration status accounting doc will be made documents. Can the following documents be put onto the share point site? available prior to second audit.

1. 6116-00050, Diablo Canyon PPS Configuration Status Accounting,
2. Triconex Master Configuration List PG&E Response: The 6116-00050, Diablo Canyon PPS Configuration Status Accounting was put on the Sharepoint on 12/3/13.

February 4, 2014 DCPP PPS Open Item Summary Table Page 6 of 9 No Src/RI Issue Description P&GE response: Status 1 RAJ No. I RAJ Comments (Date Sent) Respons e

(Due Date) 110 RJS Defined "Safe States" Open RA164 12/12/13- RJS Need to e~tablish Part a. whether fail safe Section 4.2.5.2 of the LAR (Page 64) states that "the redundancy checker status applies to compares outputs and critical internal states from the two cores and will channel level or to drive the board to a safe state if the outputs of the cores do not agree." board level.

The staff reviewed the FRS and IRS documents to determine what the "safe 11/1/13-RJS state" is for any given ALS function, but was unable to identify specifications Discussed during that define what these safe states are. Please provide a list of "Safe States" 10/31 conference for each of the ALS functions below and describe how requirements for call. Asked licensee these states are established in the system design. If the system safe states to reconsider the are not defined by PG&E, then please explain the basis used by the vendor part b response.

to determine what the safe states are for each ALS function. The NRC does not consider the fail safe ALS Function: states of analog

  • Pressurizer Pressure High Reactor Trip -. unpredictable since
  • Pressurizer Pressure Low-Low ESF - the FPGA
  • Pressu-rizer Pressure Low P:-11 ESF Block- specification.
  • Containment Pressure High ESF -

See Audit

  • Containment Pressure High High-High ESF Requirement 2.d.
  • PORV Actuation on High PZR Pressure -

10/24/13- RJS I Part b.

have determined that Please explain what the "safe states" are for the ALS analog output signals.

the fail safe states If a redundancy checker detects a discrepancy between the two cores, then are defined in the do these analog outputs fail to some pre-determined value or do they fail as-FPGA specifications, is? The FRS or IRS documents do not seem to specify this level of system however, it is still not functionality.

clear how these determinations were

  • RCS Narrow Range Temperature Output-made if not derived
  • Pressurizer Vapor Space Temperature from licensee input
  • RCS Wide Ranae Temperature Output-

February 4, 2014 DCPP PPS Open Item Summary Table Page 7 of 9 No Src!RI Issue Description P&GE response: Status RAt No. RAt Comments

~

(Date Sent) Respons

~

(Due Date)

PG&E Response: * (i.e. FRS and IRS).

FRS 3.2.1.16 defines Part A: Additional information is being provided in the Functional Failure Mode

  • Requirements Specification (Rev. 9), Sections 3.2.1.16.3 thru 3.2.1.16.6 that Requirements.

provide the requirements.

For Deenergize to Trip comparator outputs (which includes all except Containment Pressure High-High ESF):

[3.2.1.16.3] Deenergize to Trip comparator outputs shall be designed such that upon loss of electrical power, the resultant output is the tripped (deenergized) condition.

[3.2.1.16.5] Detectable failures that could result in loss of ability to perform a required safety function should result in affected Deenergize to Trip comparators being placed in the tripped (deenergized) condition. This '

requirement does not apply to functions that are out of service.

For the Energize to Trip Comparator Functions (Containment Pressure High- J High ESF):

[3.2.1.16.4] Energize to Trip comparator outputs shall be designed such that upon loss of electrical power, the resultant output is the non-tripped (deenergized) condition. i (3.2.1.16.6] Detectable failures that could result in loss of ability to perform a required safety function should result in affected Energize to Trip comparators being placed in the non-tripped (deenergized) condition. This requirement does not apply to functions that are out of service.

Note that 3.2.1.16.5 and 3.2.1.16.6 are "should" and not "shall" since the type of failure is undefined. Some failures could result in the inability of the affected system to place the output in the desired mode.

Part 8: The Functional Requirements Specification does not specify any particular failure mode for analog outputs. If the failure is a loss of power, they will fail low. Other failures are unpredictable making it difficult to assign a fail state that would be applicable in all cases. -- ----

February 4, 2014 DCPP PPS Open Item Summary Table Page 8 of 9 No Src/RI Issue Description P&GE response: Status RAt No. RAt Comments (Date Sent) Respons "

' e (Due Date) 111 RJS ALS Manual Alarm Bypass Function - Open RAI65 12/13/13- RJS Request PGE In the FPGA Requirements Specification (page 4-14) R4082 states that the provide explanation Bypass alarm logic will be bypassed when the channels logic enable is not of channel not in use set. The rational provided is that the trip command is not being calculated so configuration. This there would presumably be no need to actuate the alarm. This requirement is Audit item g.

seems to contradict requirement R4130 as well as Clause 5.8.3 of IEEE 603.

11/1/13- RJS This

  • Please provide an explanation of the benefit of providing this means of item was discussed defeating this alarm? The staff feels that operators should be aware of the at the 10/31 bypass status of each safety channel regardless of whether the safety conference call.

function is operable or nqt. The staff is also concerned that situations could exist when the operator could be misled into believing that a channel is not This will require an bypassed (because of the cleared alarm) when in fact the channel bypass RAI in order to switch is in bypass. provide clarification PG&E Response: In progress to the rational for maintaining this

. bypass of bypass alarm function when channel is not used.

Also ne.ed clarification that bypass alarm will never be disabled for an active channel and will always provide alarm when in bypass condition.

10/28/13- RJS-This will be an Audit Item. See Audit Requirement 2.g.

February 4, 2014 DCPP PPS Open Item Summary Table Page 9 of 9 No Src!RI Issue Description P&GE response: Status RAJ No. RAJ Comments (Date Sent) Respons e

(Due Date) 112 so PG&E staff had discussed having the option of connecting a thumb drive to New the MWS, in addition to connecting a printer, in order to allow technicians to print-to-file. Please clarify if a thumb drive will be connected to the MWS, and if so, what procedures will be implemented to maintain a secure the thumb drive.

PG&E staff also discussed the possibility of having only one printer connected to all MWSs (one printer connected to four Tricon MWSs and four ALS MWSs), instead of one printer per protection set (one printer connected to one Tricon MWS and one ALS MWS). Please explain if the design for connecting a printer to the MWSs will change from what is in the LAR, so that only one printer for all protection sets is used.

PG&E Response: In progress

Project Plan for Diablo Canyon Replacement of Digital RPS and ESFAS (PPS) - LAR Review (Rev. 16)

Step Planned Task Actual Date Date 1 Oct. 26, PG&E LAR Submittal for NRC approval. Submittal includes all Oct. 26, 2011 Phase 1 documents needed to be docketed prior to acceptance 2011 for review per ISG-06, "Digital Licensing."

2 Jan. 12, Acceptance Review complete. LAR accepted for detailed Jan. 12, 2012 technical review. Several issues identified that, could present 2012 challenges for the staff to complete its review. Scheduled public meeting with PG&E to discuss the results of the acceptance review.

3 Jan. 13, Acceptance letter sent to licensee. Jan. 13, 2012 2012 4 Jan. 18, Conduct Public Meeting to discuss staff's findings during the LAR Jan. 18, 2012 acceptance review. Staff proceeds with LAR technical review. 2012 5 March 18, PG&E provides information requested in acceptance letter. Initiate April2, 2012 bi-weekly telecoms with PG&E and its contractors to discuss 2012 potential RAI issues. Open Items spreadsheet will be maintained by NRC to document staff issues and planned licensee responses.

6 May 30, PG&E provides partial set of Phase 2 documentation per June 6, 2012 commitments made in LAR. 2012*

  • PG&E provided a subset of the Phase 2 documents on June 61h See step 14 which is a milestone for submittal of all remaining Phase 2 documents.

7 July First RAI sent to PG&E on Phase 1 documentation (e.g., August 07, 2012 specifications, plans, and equipment qualification). Continue 2012 review of the application. Request 45 day response.

(ML12208A364) 8 June SER for Tricon V1 0 Platform issued final. This platform becomes May 15, 2012 a Tier 1 review of the LAR. (ML12146A010) 2012 8.1 June SER for Westinghouse ALS Platform issued final. This platform 2013 a becomes Tier 1 review of the LAR.

9 September Receive answers to first RAI. (ML12256A308) Sept. 11, 2012 2012 10 November Audit trip to lnvensys facility for thread audit; audit the life cycle Nov. 13-2012 planning documents and outputs, with particular emphases on 16, 2012 verification and validation, configuration management, quality Assurance, software safety, the lnvensys application software development procedures, and application software program design.

10.1 December Audit report provided to PG&E. February 2012 21,2013 11 February Audit trip to Westinghouse/CSI facility for thread audit; audit the February 2013 life cycle planning documents and outputs, with particular 21, 2013 emphases on verification and validation, configuration management, quality Assurance, software safety, the W/ALS Enclosure 3 Page 1 of 3

Project Plan for Diablo Canyon Replacement of Digital RPS and ESFAS (PPS) -. LAR Review (Rev. 16) application software development procedures, and PPS ALS application software program design.

11.1 April Audit report provided to PG&E and its contractor. April 11, 2013 2013 12 March Second RAI Letter to PG&E on Phase 1 documentation March 20, 2013 2013 12.1 April Receive responses to Second set of RAI's May 9, 2013 2013 13 April LAR revision and all supporting documentation associated with April30, 2013 the change in ALS and Tricon V1 0 workstation designs for the 2013 PPS are submitted.

14 August NSIR Cyber Security audit at Diablo Canyon site. August 8 2013 2013 14.1 December Cyber Security Audit Report provided to licensee 2013 EICB Letter sent to PM 9/2/13- ML13242A078

? NSIR Report-15 December PG&E provides remaining set of Phase 2 documentation per 2013 commitments made in LAR. To include ALS PSAI related.

documents. See step 6 for initial submittal of Phase 2 documents.

16 December All Documentation for DCPP W/CSI ALS and IOM/Triconex V1 0 2013 processors applicable to the DCPP PPS LAR.are submitted.

17 TBD Follow-up audit trip to lnvensys facility for thread.audit; audit the life cycle planning documents ~nd outputs, with particular

  • emphases on verification and validation, configuration management, quality assurance, software safety, the lnvensys application software development procedures, and application software program design.

17.1 TBD Second lnvensys audit report provided to PG&E.

18 December Third RAI Letter to PG&E on Phase 2 documentation 2013 (e.g., FMEA, safety analysis, RTM, EQ test results, setpoint calculations.)

18.1 February Receive responses to third set of RAI's.

2014 19 TBD Audit trip to W/ALS facilities for additional thread audit items; audit hardware and software installation plans, configuration management reports, detailed system and hardware design, completed test procedures, V&V actfvities,* summary test results (including FAT) and incident reports, and application code listings.

Page 2 of 3

Project Plan for Diablo Canyon Replacement of Digital RPS and ESFAS (PPS) - LAR Review (Rev. 16) 19.1 TBD Audit report provided to PG&E.

20 TBD (Optional) Audit trip to lnvensys facilities for additional thread audit items; audit hardware and software installation plans, configuration management reports, detailed system and hardware <

design, completed test procedures, V&V activities, summary test results (including FAT) arid incident reports, and application code listings.

21 TBD (Optional) Audit trip to DCPP test facilities for additional thread audit items.

February 18 I 22 Presentation to ACRS Subcommittee/Full ACRS Committee on March 2014 DCPP 'pps LAR Safety Evaluation.

23 March 20.14 Complete draft technical SER for management review and approval.

24 March 2014 Issue completed draft technical SER to DORL 25 March 2014 Draft SER sent it to PG&E, lnvensys, and W/CSI to perform technical review and ensure no proprietary information was included.

26 April 2014 Receive comments from PG&E and its contractors on draft SER proprietary review.

27 May 2014 Approved License Amendment issued to PG&E 28 -September Inspection trip to DCPP for PPS Site AcceptanceTesting (SAT),

2014 training and other preparation for installing the new system. To be (tentative) coordinated with regional visit. Date based on receipt of new PPS system at the site in preparation for September 2015 Unit 1 Refueling Outage (1R19).

29 -September Inspection trip to DCPP for PPS installation tests, training and 2015 other system installation activities for the new system. To be coordinated with regional visit. Date based on September 2015 Unit 1 Refueling Outage (1R19).

Page 3 of 3

Meeting Notice ML13290A227; Meetlf!9_ Summary ML14029A450

  • via email OFFICE NRR/DORLILPL4-2/PM NRR/DORL/LPL4-1/LA NRR/DE/EICB NRR/DORL/LPL4-1/BC(A) NRR/DORL/LPL4-1/PM NAME BBenney JBurkhardt RStattel
  • EOesterle SLingam DATE 2/10/14 2/4/14 2/12/14 12/10/14 12/10/14