ML120590119
| ML120590119 | |
| Person / Time | |
|---|---|
| Site: | Diablo Canyon  |
| Issue date: | 02/29/2012 |
| From: | Joseph Sebrosky Plant Licensing Branch IV |
| To: | |
| Sebrosky J, NRR/DORL/LPL4, 415-1132 | |
| References | |
| TAC ME7522, TAC ME7523 | |
| Download: ML120590119 (51) | |
Text
~p.l\\ REGu(
UNITED STATES
~~c."
.q"o.,.
NUCLEAR REGULATORY COMMISSION
~
WASHINGTON, D.C. 20555-0001
°
~
~
~
~
~
1-') ****1<,..0 February 29, 2012 LICENSEE:
Pacific Gas and Electric Company FACILITY:
Diablo Canyon Power Plant, Unit Nos. 1 and 2 SUB~IECT:
SUMMARY
OF FEBRUARY 23, 2012, PHONE CALL 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 February 23,2012, the U.S. Nuclear Regulatory Commission (NRC) staff and representatives of Pacific Gas and Electric Company (PG&E, the licensee) had a phone call 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 purpose of the phone call was to address preliminary questions that the NRC staff had associated with the review. Prior to the phone call, a list of issues was provided to the licensee.
The licensee provided high-level responses to these issues. The issues and the licensee's responses are provided in Enclosure 2. The first nine issues are the issues that were identified in the January 13, 2012, acceptance review letter of the PPS LAR (ADAMS Accession No. ML120120005). As appropriate, the staff will issue requests for additional information based on interactions with the licensee.
The NRC staff indicated that it intends to have phone calls every 2 weeks with the licensee to discuss issues and the status of the review. These future phone calls will be noticed as public meetings. The staff expects that these phone calls will be held for the next several months.
The issues found in Enclosure 2 will be updated to reflect the status of the staff's review and will serve as the agenda for these publicly noticed phone calls. This process is similar to the process that was followed for the Watts Bar Unit 2 digital instrumentation and control review.
During the phone call, the licensee asked if the NRC staff had updated the matrix associated with DI&C-ISG-06, "Task Working Group #6: Licensing Process, Interim Staff Guidance, Revision 1," dated January 19, 2011 (ADAMS Accession No. ML110140103). The staff indicated that it had updated the matrix as it applies to the Diablo Canyon PPS review. The licensee requested a copy of the draft matrix that the staff was using. Subsequent to the phone call, the staff provided Enclosure 3 to the licensee. Enclosure 3 is a spreadsheet with 61 rows and 25 columns. Because of the number of columns, not all of the columns could fit on one sheet of paper. Enclosure 3 splits the matrix into three parts, with new columns beginning on pages 1, 10, and 23. The row number to the far left of the document provides a reference that can be used to align the different portions of the matrix.
- 2 Please direct any inquiries to me at 301-415-1132 or at~==!..!.:.:::=!4£::JE;U.l~~~
(
Docket Nos. 50-275 and 50-323 \\//
Enclosures:
- 1. Ust of attendees
- 2. Staff identified issues
- 3. DI&C-ISG-06 review matrix for Diablo Canyon cc w/encls: Distribution via Ustserv
LIST OF ATTENDEES FEBRUARY 23,2012, PHONE CALL WITH PACIFIC GAS AND ELECTRIC COMPANY REGARDING DIABLO CANYON POWER PLANT DIGITAL UPGRADE NAME Ken Schrader Bob Lint John Hefler Bill Petrick Edward Quinn G. Clarkson K. Brandt J. Basso Warren Odess-Gillett Roman Shaffer Joe Sebrosky Bill Kemper Rich Stattel Bernard Dittman ORGANIZATION Pacific Gas and Electric Altran Altran Altran Altran Altran Altran Westinghouse Westinghouse Invensys U.S. Nuclear Regulatory Commission U.S. Nuclear Regulatory Commission U.S. Nuclear Regulatory Commission U.S. Nuclear Regulatory Commission
No SrclRI Issue Description P&GE response:
Status RAINo.
(Date Sent)
Response
(Due Date)
Comments 001 AR (80)
[ISG-06 Enclosure 8, Item 1.3] Deterministic Nature of Software:
The Diablo Canyon Specific Application should identify the board access sequence and provide corresponding analysis associated with digital response time performance. This analysis should be of sufficient detail to enable the NRC staff to determine that the logic-cycle;
- a. has been implemented in conformance with the ALS Topical Report design basis,
- b. is deterministic, and
- c. the response time is derived from plant safety analysis performance requirements and in full consideration of communication errors that have been observed during equipment qualification.
As stated in the LAR, information pertaining to response time performance will be submitted as a Phase 2 document. Please ensure this matter is addressed accordingly.
Open N/A P&GE response:
ALS Diablo Canyon PPS document 6116-00011, "ALS System Design Specification", Section 7.5, identifies the ALS board access sequence and provides an analysis associated with digital response time performance.
a)
The Diablo Canyon PPS ALS system is configured in accordance with the qualification requirements of the ALS platform topical report, b)
The analysis in Diablo Canyon PPS document 6116-00011, "ALS System Design Specification", Section 7, describes a logic cycle that is deterministic.
c)
The requirements for the response time of the PPS processing instrumentation (from input conditioner to conditioned output signal) is specified as not to exceed 0.409 seconds in Section 3.2.1.10 of the "Diablo
-2 No SrclRI Issue Description P&GE response:
Status RAI No.
(Date Sent)
Response
(Due Date)
Comments Canyon Power Plant Units 1 & 2 Process Protection System Replacement Functional Requirements Specification (FRS)", Revision 4 submitted as of the LAR. In Section 1.5.8 of the "Diablo Canyon Power Plant Units 1 & 2 Process Protection System Replacement Interface Requirements Specification (IRS)", Revision 4, submitted as Attachment 8 of the LAR, the 0.409 seconds PPS processing instrumentation response time is allocated between the ALS and Tricon as follows:
ALS: 175 ms for RTD processing Tricon: 200 ms Contingency: 34 ms The 0.409 seconds PPS processing instrumentation value is the same as the value that is currently allocated to PPS processing instrumentation. As long as the 0.409 second PPS processing instrumentation value is not exceeded, the total response time values assumed in the plant safety analyses contained in FSAR Table 15.1-2 will not be exceeded; 7 seconds for Overtemperature AT RT and Overpower AT RT functions, 2 seconds for High pressurizer pressure RT, Low pressurizer pressure RT, and Low Low SG water level RT functions, 1 second for Low reactor coolant flow RT function, 25 seconds for Low pressurizer pressure, High containment pressure, and Low steam line pressure Safety Injection initiation, 60 seconds for Low low SG water level auxiliary feedwater initiation, 18 seconds for High containment pressure, Low pressurizer pressure, and Low steam line pressure Phase A containment isolation, 48.5 seconds for High High containment pressure containment spray initiation, 7 seconds for High High containment pressure steam line isolation, 66 seconds for High High SG water level auxiliary feedwater isolation, and 8 seconds for Low steam line pressure steam line isolation.
The ALS response time will be verified as part of the FAT and the results will be included in the FAT summary report to be submitted by 12/31/12.
I
- 3 No SrclRI Issue Description P&GE response:
Status RAI No.
(Date Sent)
Response
(Due Date)
Comments Tricon Invensys provided detailed information on the deterministic operation of the V10 Tricon in Invensys Letter No. NRC V10-11-001, dated January 5,2011.
In support of the V1 0 Tricon safety evaluation, Invensys submitted document 9600164-731, Maximum Response Time Calculations, describing the worst-case response time for the V10 Tricon Qualification System. Included in document 9600164-731 are the standard equations for calculating worst-case response time of a given V1 0 Tricon configuration. The Design Phase calculations for the V10 Tricon PPS Replacement architecture will be available for audit, and the System Response Time Confirmation Report, 993754-1-818, will be submitted to the staff as part of the ISG-06 Phase 2 submittals at the completion of factory acceptance testing of the V1 0 Tricon PPS Replacement.
The Tricon response time will be verified as part of the FAT and the results will be included in the FAT summary report to be submitted by 12/31/12.
[ISG-06 Enclosure B, Item 1.4]
Software Management Plan: Regulatory Guide (RG) 1.168, Revision 1, "Verification, Validation, Reviews and Audits for Digital Computer Software Used in Safety Systems of Nuclear Power Plants," dated February 2004 endorses IEEE (Institute of Electrical and Electronics Engineers) 1012-1998, "IEEE Standard for Software Verification and Validation," and IEEE 1028 1997,"IEEE Standard for Software Reviews and Audits," with the exceptions stated in the Regulatory Position of RG 1.168. RG 1.168 describes a method acceptable to the NRC staff for complying with parts of the NRC's regulations for promoting high functional reliability and design quality in software used in safety systems. Standard Review Plan(SRP) Table 7-1 and Appendix 7.1-A identify Regulatory Guide 1.168 as SRP acceptance criteria for reactor trip systems (RTS) and for engineered safety features Open NIA We~!inghouse/ALS 6116-00000 Diablo Canyon PPS Management Plan,
- 4 No SrclRI Issue Description P&GE response:
Figure 2-2, shows the Verification and Validation (V&V) organization reporting to the Project Manager. This is inconsistent with the information described in the ALS Management Plan for the generic system platform, where the V& V organization is independent form the Project Manager. This is also inconsistent with the criteria of RG 1.168 and will need to be reconciled during the LAR and ALS L TR reviews.
Status RAINo.
(Date Sent)
Response
(Due Date)
Comments 3
P&GE response:
ALS The Westinghouse/ALS 6116-00000 Diablo Canyon PPS Management Plan will be updated to address identified issues and PG&E will submit the revised document by TBD.
[ISG-06 Enclosure B, Item 1.9]
Software V&V Plan: The ALS V&V plan states that Project Manager of the supplier is responsible for providing directions during implementation of V&V activities. Also, the organization chart in the Diablo Canyon PPS Management Plan shows the IW manager reporting to the PM.
The ALS V&V plan described in ISG6 matrix for the ALS platform and the Diablo Canyon PPS Management Plan do not provide sufficient information about the activities to be performed during V&V. For example, the ALS V&V Plan states that for project specific systems, V&V activities are determined on a project by project basis and are described in the project Management Plan, in this case, 6116-00000, "Diablo Canyon PPS Management Plan."
However, the 6116-00000 Diablo Canyon PPS Management Plan states:
"See the ALS V& V Plan for more information and the interface between the Open N/A
- 5 No SrclRI Issue Description P&GE response:
IV&V team and the PPS Replacement project team."
The Triconex V&V plan states that the Engineering Project Plan defines the scope for V&V activities. As mentioned before, the Triconex EPP is not listed in the ISG6 matrix.
These items will need further clarification during the LAR review to demonstrate compliance with Regulatory Guide (RG) 1.168, Revision 1, "Verification, Validation, Reviews and Audits for Digital Computer Software Used in Safety Systems of Nuclear Power Plants,"
P&GE response:
ALS CS Innovations submitted a revised V&V plan, "6002-00003 ALS Verification and Validation Plan", Revision 5, on November 11, 2011, that revises the V&V responsibilities to address the above issue. The Westinghouse/ALS 6116-00000 Diablo Canyon PPS Management Plan will be updated to address identified issues and PG&E will submit the revised document by TBD.
Tricon The organizational structure of I nvensys Operations Management comprises, in part, Engineering and Nuclear Delivery. Each of these organizations plays a specific role in the V10 Tricon application project life cycle. Invensys Engineering is responsible for designing and maintaining the V1 0 Tricon platform, and Nuclear Delivery is responsible for working with nuclear customers on safety-related V10 Tricon system integration projects.
Invensys Engineering department procedures require "Engineering Project Status RAI No.
(Date Sent)
Response
(Due Date)
Comments
-6 No SrclRI Issue Description P&GE response:
Status RAI No.
(Date Sent)
Response
(Due Date)
Comments Plans (EPP)," whereas Nuclear Delivery department procedures require "Project Plans." Invensys Engineering is not directly involved in system integration, but Nuclear Delivery may consult with Engineering on technical issues related to the V1 0 Tricon platform.
The NRC applied ISG-06 to the V10 Tricon safety evaluation. Invensys submitted a number of documents pertaining to the design of the V10 Tricon platform as well as process and procedure documents governing Invensys Engineering activities, including the EPP. In most cases, these platform-related documents are preceded with document number 9600164. The platform-level documents reviewed by the staff during the V1 0 Tricon safety evaluation will not be resubmitted by Nuclear Delivery during'application specific system integration projects.
In support of the PG&E LAR 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.
The PMP describes the PPS Replacement Project management activities 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.
- 7 No SrC/RI Issue Description P&GE response:
Status RAI No.
(Date Sent)
Response
(Due Date)
Comments 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 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 Enclosure B, Item 1.10]
Software Configuration Management Plan: The LAR includes PG&E Open N/A CF2.102, "Software Configuration Management for Plant Operations and Operations Support," in Attachment 12. However, the document provided in 2 only provides a guideline for preparing Software Configuration Management (SCM) and SQA plans. Though it is understood that the licensee will not perform development of software, PGE personnel will become responsible for maintaining configuration control over software upon delivery from the vendor.
The staff requires the actual plan to be used by the licensee for maintaining configuration control over PPS software in order to evaluate against the acceptance criteria of the SRP. For example, the ALS Configuration Management (CM) Plan (6002-00002) describes initial design activities
- 8 No SrclRI Issue Description P&GE response:
related to ALS generic boards. This plan does describe the configuration management activities to be used for the development and application of the ALS platform for the Diablo Canyon PPS System. The staff requires that configuration management for this design be described in the DCPP project specific plan. These items will need further clarification during the LAR review to demonstrate compliance with BTP-14.
Status RAI No.
(Date Sent)
Response
(Due Date)
Comments P&GE response:
PG&E will develop a SyCMP procedure to address configuration control after shipment of equipment from the vendor and will submit the document by May 31,2012.
[ISG-06 Enclosure B, Item 1.11]
Software Test Plan: The V1 0 platform documents identified in ISG6 matrix state that the interface between the NGIO Core Software and IO-specific software will not be tested. It is not clear when and how this interface will be tested, and why this test is not part of the software unit testing and integration testing activities.
Open N/A Further, the 993754-1-813 Diablo Canyon Triconex PPS Validation Test Plan states that the DCPPls TSAP will not be loaded on the system; instead Triconex will use another TSAP for the validation test. It is not clear why the DCPPls TSAP will not be used for the validation test or when the DCPPls TSAP will be loaded on the system and validated for the Diablo Canyon PPS System. These items will need further clarification during the LAR review to demonstrate compliance with BTP-14.
- 9 No SrclRI Issue Description P&GE response:
Status RAI No.
(Date Sent)
Response
(Due Date)
Comments P&GE response:
Tricon The next-generation input/output (1/0) modules qualified for the V1 0 Tricon are the 3721 N 4-20 mA, 32-point analog input (AI) module, and the 3625N 24 Vdc, 32-point digital output (DO) module. Technical data on these two modules was provided to the NRC in support of the V1 0 Tricon safety evaluation. Configuration and functional testing is performed when the 1/0 modules (hardware and embedded core firmware) are manufactured. From the factory the 1/0 modules are shipped to Invensys Nuclear Delivery for use in nuclear system integration projects, i.e., application specific configurations.
Because the module hardware and embedded core firmware are within the scope of the V1 0 Tricon safety evaluation, the verification and validation of the embedded core firmware will not be repeated as part of application-specific system integration projects.
There are certain design items that must be done with TriStation 1131 (TS1131). such as specifying which 1/0 module is installed in a particular physical slot of the Tricon chassis, resulting in each module having a unique hardware address in the system. Also, TS1131 is used to specify which application program parameters (i.e., program variable tag names) are assigned to a particular point on a given 1/0 module. The design items configured in TS1131 will be within the scope of validation activities conducted by Invensys Nuclear IV&V for application-specific system integration projects. The necessary collateral {system build documents.
configuration tables, test procedures, test results, etc.} will be submitted to the NRC to support the staff's technical review of the PPS Replacement LAR
-10 rNo SrC/RI Issue Description P&GE response:
Status RAINo.
(Date Sent)
Response
(Due Date)
Comments I
in accordance with ISG-06.
The Phase 1 submittal under Invensys Project Letter 993754-026T, dated October 26, 2011, contained, in part, the Validation Test Plan (VTP), 993754 1-813. This document describes the scope, approach,,and resources of the testing activities that are required for validation testing of the V1 0 Tricon portion of the PPS Replacement, including:
Preparing for and conducting system integration tests Defining technical inputs to validation planning Defining the test tools and environment necessary for system validation testing Scheduling (and resource loading of the schedule)
Section 1.3.2 of the VTP describes the Hardware Validation Test activities and Section 1.3.3 of the VTP describes the V1 0 Tricon portion of the Factory Acceptance Test activities for the V10 T ricon portion of the PPS Replacement Details on the application program are proprietary and need to be provided to the staff separately.
[ISG-06 Enclosure B, Item 1.14]
Equipment Qualification Testinq Plans - The tAR Sections 4.6,4.10.2.4 and 4.11.1.2 provide little information on the plant specific application environmental factors. The Tricon V10 Safety Evaluation, ML11298A246, Section 6.2 lists 19 application specific actions Items (ASAI's) that the licensee should address for plant specific applications. The licensee should address each of these for Tricon portion of the PPS replacement Similar information for the ALS portion of the PPS replacement will also be required.
Open N/A
- 11 No SrC/RI Issue Description P&GE response:
Status RAI No.
(Date Sent)
Response
(Due Date)
Comments P&GE response:
ALS PG&E will respond to ALS ASAI's when they are available.
Trieon IN PROGRESS. Each of the Application Specific Action Items will be addressed by end of February 2012.
7 AR (BK)
[ISG-06 Enclosure B, Item 1.16J Design Analysis Reports: The LAR does not appear to comply with the SRP (ISG-04) regarding the connectivity of the Maintenance Work Station to the PPS. The TriStation V10 platform relies on software to effect the disconnection of the TriStation's capability to modify the safety system software. Based on the information provided in the L TR, the NRC staff determined that the Tricon V10 platform does not comply with the NRC guidance provided in ISG-04, Highly Integrated Control Rooms-Communications Issues, (ADAMS Accession No. ML083310185), Staff Position 1, Point 10, hence the DCPP PPS configuration does not fully comply with this guidance.
In order for the NRC staff to accept this keyswitch function as an acceptable deviation to this staff position, the staff will have to evaluate the DCPP PPS specific system communications control configuration--including the operation of the keyswitch, the software affec;t~<:II:>Y the keyswitch. and any Open N/A
- 12 No SrclRI Issue Description P&GE response:
Status RAI No.
(Date Sent)
Response
(Due Date)
Comments
~~~~~~~~~~~
testing performed on failures of the hardware and software associated with the keyswitch. The status of the ALS platform on this matter is unclear at this time and will be resolved as the ALS L TR review is completed.
Moreover, the Tricon V1 0 system Operational Mode Change (OMC) keyswitch does change operational modes of the 3008N MPs and enables the TriStation 1131 PC to change parameters, software algorithms, etc, related to the application program of the safety channel without the channel or division being in bypass or in trip. As stated in Section 3.1.3.2 of the Tricon V10 SER, the TriStation 1131 PC should not normally be connected while the Tricon V10 is operational and performing safety critical functions.
However, it is physically possible for the TriStation PC to be connected at all times, and this should be strictly controlled via administrative controls (e.g.,
place the respective channel out of service while changing the software, parameters, etc). The LAR does not mention any administrative controls such as this to control the operation of the OMC (operational mode change) keyswitch. Furthermore, in order to leave the non-safety TriStation 1131 PC attached to the SR Tricon V10 system while the key switch is in the RUN position, a detailed FMEA of the TriStation 1131 PC system will be required to ascertain the potential effects this non-safety PC may have on the execution of the safety application program/operability of the channel or division. These issues must be addressed in order for the NRC staff to determine that the DCPP PPS complies with the NRC Staff Guidance provided in Staff Position 1, Point 11. The status of the ALS platform on this point is unclear at this time.
P&GE response:
Tricon I
- 13 No SrclR/
Issue Description P&GE response:
Status RAI No.
(Date Sent)
RA/
Response
(Due Date)
Comments The OMC keyswitch controls only the mode of the V1 0 Tricon 3008N MPs.
In RUN position the 3008N MPs ignore* all commands from external devices, whether WRITE commands from external operator interfaces or program-related commands from TS 1131. Multiple hardware and software failures would have to occur on the V1 0 Tricon (in combination with human performa nce errors in the control room and at the com puter with TS 1131 installed) in order for the application program to be inadvertently reprogrammed. Therefore, there is no credible single failure on the V1 0 Tricon that would allow the safety-related application program to be inadvertently programmed, e.g., as a result of unexpected operation of the connected computer with TS1131 installed on it.
The above conclusion will be confirmed (for the V10 Tricon portion of the PPS Replacement) in the Failure Modes and Effects Analysis, an ISG-06 Phase 2 document planned for submittal to NRC in May 2012. Additionally, Invensys Operations Management will support the staff's review of the hardware and software associated with the OMC keyswitch by making all of the technical data available for audit.
- TS1131 contains function blocks that allow WRITE-access to a limited set of parameters programmed into the application software, but only for a limited duration after which the capability is disabled until WRITE-access is re-enabled. However, without these function blocks programmed into the application program neither the application program nor application program parameters can be modified with the OMC keyswitch in the RUN position.
PG&E Administrative controls on use of keyswitch will be provided with commitment to include in procedures in response.
Note, TS 1131 is not used to change setpoints and protection set is
- 14 No SrciR/
Issue Description P&GE response:
Status RAI No.
RA/
Comments (Date Sent)
Response
(Due Date) inoperable when keyswitch is not in RUN position.
8 AR (RS)
[ISG-06 Enclosure B, Item 1.21J Setpoint Methodology: The NRC staff understands that a summary of SP (setpoint) Calculations will be provided in Phase 2, however, section 4.10.3.8 of the LAR also states that PGE plans to submit a separate LAR to adopt TSTF 493. The NRC cannot accept this dependency on an unapproved future licensing action. The staff therefore expects the licensee to submit a summary of setpoint calculations which includes a discussion of the methods used for determining as-found and as-left tolerances. This submittal should satisfy all of the informational requirements set forth in ISG6 section 0.9.4.3.8 without a condition of TSTF 493 LAR approval Open N/A P&GE response:
A summary of the setpoint calculations will be submitted by May 31,2011 including the as-found and as-left setpoints.
9 AR (BK)
L TR Safety Conclusion Scope and Applicability - Many important sections of the OCPP PPS LAR refer the reader to the ALS licensing topical report (L TR) to demonstrate compliance of the system with various Clauses of IEEE 603 1991, IEEE 7-4.3.2-203, and ISG-04. However, many important sections of the ALS LTR state that compliance with various Clauses of these IEEE Stds and ISG-04 are application specific and refer the reader to an application specific license amendment submittal (i.e., the OCPP PPS LAR in this case).
The staff has not yet had time to evaluate all the LAR information in detail Open N/A I
- 15 No SrclRI Issue Description P&GE response:
Status RAINo.
(Date Sent)
Response
(Due Date)
Comments I
I and compare this information with that provided in the ALS L TR to ensure there is no missing information. However, PG&E and its contractors are encouraged to review these two licensing submittals promptly to verify that compliance with these IEEE Stds and ISG-04 are adequately addressed within both licensing documents.
I i
P&GE response:
IN PROGRESS, review by Westinghouse and PG&E to date has not found a clause where no justification is provided in LAR.
10 RS Plant Variable PPS Scope - In the Description section of the LAR, section 4.1.3, nine plant variables are defined as being required for RTS and section 4.1.4 lists seven plant variables that are required for the ESFAS. Three additional plant variables were also listed in section 4.10.3.4.
Open 1
Some variables are not listed in section 4.10.3.4 as being PPS monitored plant parameters. It is therefore assumed that these parameters are provided as direct inputs to the SSPS and that the PPS is not relied upon for the completion of required reactor trip or safety functions associated with them. Please confirm that these plant parameters and associated safety functions will continue to operate independently from the PPS and that the replacement PPS will not adversely impact the system's ability to reliably perform these functions.
P&GE response:
IN PROGRESS
- 16 No SrclRI Issue Description P&GE response:
Status RAINo.
(Date Sent)
Response
(Due Date)
Comments 11 RS Power Range NIS Function -_Section 4.1.7 describes the Existing Power Range NIS Protection Functions and it states that the Power Range nuclear instrumentation provides input to the OTDT, and OPDT protection channels.
It is not entirely clear whether any of the described NIS protection functions will be performed by the PPS system. Please clarify exactly what the role of the PPS system is for these NIS Protection functions.
Open 2
P&GE response:
IN PROGRESS 12 RS Permissive Functions - Several Permissive functions are described within the LAR. It is not clear to the staff whether any of these functions are to be performed by the PPS or if the PPS will only be providing input to external systems that in turn perform the permissive logic described in the LAR.
Section 4.1.9 states that "Settings of the bistable comparators used to develop the permissives are not affected by the PPS Replacement Project",
which implies that all of these permissive functions are performed by systems other than the PPS. However, it is still unclear if this statement applies to all permissive functions described throughout the LAR or if it applies only to those permissives relating to Pressurizer Pressure. It is also possible that the permissive functions are being performed by the existing PPS and will continue to be performed by the replacement system and therefore remain "not affected" by the PPS replacement project.
Open 3
- 17 No SrclRI Issue Description P&GE response:
Status RAINo.
(Date Sent)
Response
(Due Date)
Comments Please provide additional information for the following permissive functions to clearly define what the role of the PPS system will be for each.
P-4 Reactor Trip P-7 Low Power Permissive (Bypasses low Ppzr reactor trip)
- P-8 Loss of Flow Permissive P-9 Power Permissive P-10 Power Range Power Low Permissive P-11 Low Pressurizer Pressure SI Operational Bypass P-12 No-Load Low-Low Tave Temperature Permissive P-13 Turbine Low Power Permissive
- P-14 Hi-Hi Steam Generator Level
IN PROGRESS 13 RS P12 Permissive Contradiction - The second paragraph of section 4.1.20 describes the P-12 interlock and states that "These signals are developed in the PPS". This statement is then contradicted in the third paragraph by the following statement; "These valves are not safety-related, but are interlocked with the P-12 signal from the SSPS,"
Open 4
- 18 No SrclRI Issue Description P&GE response:
Status RAI No.
(Date Sent)
Response
(Due Date)
Comments In conjunction with the response to RA13, please provide a resolution for this contradiction in section 4.1.20 of the LAR.
P&GE response:
IN PROGRESS
DI&G*ISG*06 Rev 1 (Phase1) 1101;;,
2""
2 I 3 I 1
Document Section 3
X X
X Summary Description Enclosure E 4
2.1 X
X X
No Significant Hazards Determination I Enclosure E 5
2.1 X
X X
Safety Analysis/Justification for the Proposed Change Enclosure E 6
Hardware Architecture Descriptions 1.1 X
X X
- 1. Describe individual channels D.1.2
- 2. Descnbe overal system, includIng any hardware Items not included in the channel description 7
1.2 X
Quality Assurance Plan for Digital Hardware D.2.2 8
Software Architecture Descriptions:
- 1. Platform software
- 2. Application software
- 3. Software functions 1.3 I X I X I X I 4. Software relationships D.3.2
- 5. References to previous NRC software evaluations
- 6. Software being used in individual channels
- 7. Overall system description, including software not included in the channel description
- 2 BD - Per the AlS Topical Report, there is no embedded microprocessor or executable software within any standard board FPGA logic nor is it proposed for the application-specific FPGA logic. The application-specific FPGA logic controls the equipment operational sequence.
Per the AlS Topical Report, the sequence is typicailly 1) input, 2) application-logic, and 3) output. Input and output includes internal instrument communications over the AlS bus using the AlS protocol. The proposed protocol is consistent with the MSFIS precedent, and has been made more reliable through redundatn communicaiton paths.
Individual input and output boards independently process signals in dual-core logic. Input boards use field sensors to provide status data to the applicaiton-Iogic FPGA. Output boards use status data from the application-logic FPGA to actuate outputs.
The exact equipment operational sequence and the required board set are defined at design time for each application specific instrument and cannot be modified in the field. The applicatoin-Iogic FPGA configuration can access individual input and output boards at different pre-defined intervals, and each access verifies successful communications. Dual core logic within each FPGA protects against an undetectable single*event upset failure. The application-logic asserts a failure whenever a board does not respond as required by the AlS protocol.
The Diablo Specific Applicaiton should identify the board access sequence and provide corresponding analysis associated with digital response time performance. This analysis should be sufficient for the staff to determine that the logic-cycle has been implemented in conformance with the AlS Topical Report design basis, is deterministic, and that the response time is derived from plant safety analysis performance reQuirements and in full consideration of communication errors that have been observed during equipment Ql DI&G-ISG-OS Rev 1 (Phase1)
Document Section 2
3 9
BTP 7-14, B.3.3.2
- 1. Software operation D.4.4.3.2
- 2. Deterministic nature of softwre Software Management Plan:
BTP 7-14, Section B.3.1.1 10
- 1. Interface between licensee and vendor D.4.4.1.1 checking groups 1.4 x
x X I 2. Relationship between software development and quality
- 3. Secure development environment
- 4. Resource allocation Software Development Plan:
BPT 7-14, B.3.1.2 1.5 D.4.4.1.2 RA - acceptance review done. See comments to the right. 1/10/2012 x
X I 1. Careful and deliberate development process x
- 2. Pointers to other plans (SWP, SCMP)
- 1. Identify QA procedures applicable to programming Section 4.5.3 of the LAR identifies SyQAP for software QA. However. this plan is the PG&E SYSTEM QA plan, Which is X
X 1.S X I processes D.4.4.1.3 provided in Attachment 4. The SyQAP describes project organization and QA organization. The SyQAP describes the
- 2. Methods chosen to implement QA procedural roles and responsibilities associated with software QA, and describes SW audits and reviews. This plan states that equirements
- 3 DI&G-ISG-06 Rev 1 (Phase1)
J I IICI I
Section 2
3 Do,"mo" I
I The SyQAP mentions a PG&E Procedure, IDAP CF2.109, Software Quality Assurance Plan Software Development, I 1. Creation of conceptual design which is provided in A ITACHMENT 13. The SQAP describes the in-house process for development of new power
- 2. Translation of the concepts into specific system plant related software applications. Not clear who this is used for this project. it does not seem relevant.
requirements 0.10.4.2.3.1 14 I 1.7 I X I X I X 0.4.4.1.4 16 RA See comments in documents' cells "I 1.8 1 X 1 X 1 X 0.4.4.1.9 WK - Section 3 of the SSP describes the organization and who does what when SW safety issues are discovered.... this is fairly typical of what we have seen in the past. Also, the SSP should address SW safety issues during development of the SW verses installation, maintenance, etc... recommend deleting this item.
17 RA Software V&V Plan The PG&E V&V plan does not clearly identify organizational independepende. Also, this document states that PM of BTP7-14 supplier is responsible for providing directions during implementaiton of V&V activities. Need to confinm that this does I X I Section B.3.1.10, SWP 1.9 I X I X 0.4.4.1.10 not violate independence.
Section B.3.2.2, Acceptance Criteria for software V&V activities RS - PGE will not be developing softwor perfonming SW activities for either platfonm of the PPS system therefore the Reg Guide 1.168 endorses IEEE 1012 level of independence requirements do not apply to PGE personnel.
RA Software Configuration Management Plan This document provides uniform, minimum acceptable requirements for preparing SCM and SQA plans - it is just I X I BTP 7-14 1.10 I X I X 0.4.4.1.11 guidelines!
Section B.3.1.11, SCMP Need the SCM plan for this project - how this plan was implemented (i.e., Each plant system SCMP/SQAP will include Section B.3.2.3, Acceptance Criteria for SCM activities details for handling vendor or contractor supplied software.)
- 3. Using requirements to decelop a detialed system design
- 4. Implement design into hardware and software functions
- 5. Test functions to assure correct implementation of requirements Software Integration Plan BTP 7-14, Section B.3.1.4
- 1. Analysis of SRS and SOD to determine order for I combining software components
- 2. Documentation of integration methods
- 3. Describe integration tools, techniques, methodologies
- 4. Schedules
- 5. Resources I.,....,."...... -,.~............-'........'.' 0,0'.'"
I
- 4 2
2 3
19 1.11 x
X x
1.12 X
X X
22 1 I I I 1.13 I X I X I X 23 1.14 X
X 24 1.15 I X X
X DI&G-ISG-06 Rev 1 (Phase1)
Software Test Plan BTP 7-14 Document Section B.3.1. 12, Software Test Plan Section B.3.2.4, Acceptance Criteria for Testing Activities Software Requirements Specification BTP 7-14, Section 8.3.3. 1
- 1. Reg Guide 1.172 endorsement of IEEE 830
- 12. Additional guidance in NUREG/CR-6101 Software Design Specification BTP 7-14, Section B.3.3.3 I 1. Code accurately refiects software requirements
- 2. Detailed enough to allow reviewer to check requirements and follow them through the code Equipment Qualification Testing Plans (IncJudlng EMI. Temperature, Humidity. and Seismic)
BTP 7-19. Rev 6, Section 0.6.3:
- 1. Describe and analyze diversity credited within the system or backup systems
- 3. HFE analysis and integrated system validation for Section 0.4.4.1.12 0.4.4.3.1 0.4.4.3.3 0.5.2 0.6.2 RA - acceptance review done. See comments to the right.
SM - The tAR Sections 4.6. 4.10.2.4 and 4.11.1.2 are attached. Diablo Canyon provided little information on the plant specific application.
The Tricon V10 Safety Evaluation. ML11298A246. Section 6.2 lists 19 Items that the licensee should address for plant specific applications. Diablo Canyon should address them for Tricon portion of the PPS replacement They should provide similar information for ALS portion of the PPS replacement.
- 5 2
25 26 28 DI&G-ISG-06 Tier 2
3 1.16 I X' I X' X'
DI&G-ISG-06 Rev 1 (Phase1)
Document Design Analysis Reports:
- 1. Interdivision communication description
- 2. ISG-04 Compliance analysis IEEE 603 5.6.1 Independence betweem redundant portions 5.6.2 Effects of Design Basis Event 5.6.3 Independence form other systems IEEE 7-4.3.2:
- 1. Data communication between safety and non-safety systems
- 2. Separation of protection and control systems
- 3. Documentation of compliance with ISG-04 Identification of any and all deviations to the system.
hardware. software or design lifecycle methodology from a previous NRC approval of a digital system or digital I&C system topical report.
Section 0.7.2 D.9.4.2.6 0.10.4.2.6 D.S.2 BK - The LAR does not appear to comply with the SRP (ISG-04) regarding the connectivity of the Maintenance WorK Station to the PPS. The TriStation V10 platform relies on software to effect the disconnection of the TriStation capability to modify the safety system software. Based on the information provided in the L TR, the NRC staff determined that the Tricon V10 platform does not meet the NRC Staff Guidance provided in Staff Position 1, Point 10, hence the DCPP PPS configuration does not meet ISG-04 guidance. All other ISG-04, Staff Position 1 points have been addressed for the Tricon Platform. The ALS protion of the PPS communications ISG-04 compliance documentation appears to be contained within the Tier 3 ALS platform documentation and will be addressed within the Platform SER-need to verify that this is all the ISG-()4 compliance information required to review the communiciations design features of the ALS portion of the PPS.
In order for the NRC staff to accept this keyswitch function as compliant with this Staff Position, the staff will have to evaluate the DCPP PPS specific system communications control configuration-induding the operation of the keyswitch, the software affected by the keyswitch, and any testing performed on failures of the hardware and software associated with the keyswitch. The status of the ALS platform on this matter is undear at this time and will be resolved as the AlS L TR review is completed.
Moreover, the Tricon V10 system Operational Mode Change (OMC) keyswitch does change operational modes of the 300SN MPs and enables the TriStation 1131 PC to change parameters, software algorithms, etc, related to the application program of the safety channel without the channel or diviSion being in bypass or in trip. As stated in Section 3.1.3.2 of the Tricon V1 0 SER. the TriStation 1131 PC should not normally be connected while the Tricon V1 0 is operational and performing safety critical functions. However, it is physically possible for the TriStation PC to be connected at all times, and this should be strictly controlled via administrative controls (e.g., place the respective channel out of service while changing the software, parameters, etc). The LAR does not mention any administrative controls such as this to control the operation of the OMC keyswitch. Furthermore, in order to leave the non-safety TriStation 1131 PC attached to the SR Tricon V10 system while the key switch is in the RUN position, a detailed FMEA of the TriStation 1131 PC system will be required to ascertain the potential effects this non-safety PC may have on the execution of the safety application program/operability of the channel or division. These issues must be addressed in order for the NRC staff to determine that the OCPP PPS complies with the NRC Staff Guidance provided in Staff status of the ALS olatform on this ooint is unclear at this time.
- 6 DI&G-ISG-06 Tier J I I 2
I 3
1.17 I X I X I X I 31 I I I I I 1.18 X
x 1.19 I X X
X DI&G-ISG-06 Rev 1 (Phase1)
Document System Description (To block diagram level)
- 1. Provide sufficient infonnation to support the assertion that the proposed digital I&C system meets the requirementds of IEEE 603-1991.
- 2. A document that points to other documentation where the infonnation may be found may be used
- 3. Information necessary to address the various clauses of the standard are elaborated in Section 09.4
- 1. Provide sufficient infonnation to support the assertion that the proposed digitall&C system meets the requirementds of IEEE 7-4.3.2-2003
- 2. A document that points to other documentation where the information may be found may be used
- 3. Information necessary to address the various clauses of the standard are elaborated in Section 010.4 Design Report on Computer integrity, Test and Calibration, and Fault Detection System Response Time Analysis Report IEEE 603 Clause 5.4 Confirm that the safety system equipment is designed to meet the functional performance requirements over the range of normal, abnormal, and accident conditions for the area in which it is located.
Section 0.9 0.10 I 0.9.4.2.5[5.5]
0.9.4.2.4
- 7 2
2 3
38 39 40 41 42 43 1.20 X
X 44 45 46
~
49 I
I I
sol 1.21 I X Ix I X 51 1.22 X
52 1.23 X
X DI&G-ISG-06 Rev 1 (Phase1)
Document Theory of Operation Description I'""ojm M~hodology IEEE 603 Clause 6.8 II any TS setpoints are changed, document the methodology that determines the allowance lor uncertainties between the process analytical limit and the device setpoint I Technical SpeCifications
- 1. Document the effect 01 the digitall&C system on Surveillance Requirements, channel checks, channel calibrations.
- 2. II changes will be made later to the digital I&C system programming or system settings without prior approval,
reler to the appropriate development methodologies in the adminstratvie section 01 the TS Vendor Software Plan Software Tool Verification Program Section 0.9.4.2.8 0.9.4.2.9 0.9.4.2.10 0.9.4.2.11 0.9.4.2.13 0.9.4.2.14 0.9.4.3.2 0.9.4.3.5 0.9.4.3.6 0.9.4.3.7 0.9.4.4 0.9.4.3. 8 0.11 0.10.4.2.3.1 0.10.4.2.3.2 RS* Summary 01 SP Cales will be provided in Phase 2, however, the licensee also plans to submit a separate tAR to adopt TSTF 493. We do not have a schedule for submittal or review 01 this tAR and it may impact our ability to complete this SE.
- 8 2
53 54 58 59 DI&G*ISG-06 Tier 2
3 1.24 I X X
X 1.25 X
X DI&G-ISG-06 Rev 1 (Phase1)
Document Software Project Risk Management Program IEEE 7-4.3.2 Clause 5.3.6
- 1. Identify potential problems
- 2. Assess their impact
- 3. Determine which potential problems should be addressed to achieve project quality goals Commercial Grade Dedication Plan Vulnerability Assessment 1.26 I X X
X I Identify vulnerabilities during all phases of the project including development and operations 1.27 X
X X
ronment Controls Identify deficiencies that could lead to degradation in reliable system operation due to inadvertent access or undesirable behavior of connected
- 1. Identify measures taken to secure the requirements and requirements development process.
- 2. These measures may be induded with the platform andlor application software requirements document.
- 1. Identify design phase activities aimed at precluding introduction of unwanted, unneeded and undocumented design features.
- 2. The measures may be induded in a separate document of s part of one or more other documents
- 1. Identify measures aimed at precluding introduction of unwanted, unneeded and undocumented features during the implementation phase.
- 2. Identify measures taken to protect the developed code
- 3. The measures may be included in a separate document of s part of one or more other documents Section D.10.4.2.3.6 D.10.4.2.4.2 D.12.4.1 D.12.2.1 D.12.2.2 0.12.2.3 D.12.2.4 TM-Description of Security Controls to be implemented in the CD PPS As of 11/18/11, awaiting the licensee submittal under 2.390 (See page 204 of the LAR)
RS - PGE Letter DCL-11-123 transmits security related information to support PPS replacement. This document is now in the PGE Documents folder on the G drive.
TM - As of 12123/11 - I read through this licensee and vendor (via licensee) submissions. Assuming that all these documents do hit the official docket, I believe that there is sufficient material to initiate the review. I do anticipate having some RAI questions, but nothing that needs to hold up acceptance. [Interestingly, the licensee points to several of their cyber plan controls... since the 73.54 cyber plans are new, this will be a new wrinkle to these reviews.]
- 9 DI&G*ISG*06 DI&G*ISG*06 Rev 1 (Phase1)
Tier 2
3 Document Section
~
- 1. Verify and validate secure operational environment design feature criteria
- 2. Be secure from inadvertent manipulation of test environment and test results
- 3. Address test phase vulnerabilities identified in 0.12.2.5 vulnerability assessment
- 4. The measures may be included in a separate document of s part of one or more other documents X I X I X I References Enclosure E
- 10 I=-ra_ 3.1.8 PG&E Documents to be Submitted with LAR Westinghouse/CSI Documents to be Submitted with LAR LAR Document Proprietary I
I Tier 3 Platform LAR Section I Document Title Notes Review Document Title Proprietary I Delivered I PO Notes Title I
I LAR Section 1 Summary 1 Summary Description I Description 4
LAR Section 2 No 2 No Significant Hazards Significant Hazards Determination Determination 5
LAR Section 3 Safety Analysis/Justification for the Proposed Change.
3 Safety Chapter 3 of the LAR does Analysis/Justification for the not provide sufficient Proposed Change information to address this. Software Safety wi" be provided
- 2.
6 I 6116"()()011 Diablo ALS Platform New Revision Part of LAR Section 4.2 Yes
4.2 System Description
Specification (Rev Yes exists from Rev 6 Canyon PPS ALS Point to Vendor ML11277A152 (4.2.1 -4.2.11) 810/31/11)
MLl1 320A101 2124111
System Design
Documents ML11277A152 6002-00011 ML110600695 Specification I
7 I
CSI Quality LAR Section 4.2.11, 4.3 Assurance Point to WEC/ALS Manual (Rev 6 New Revision 900Q,,()()OOOQA Yes 4.3 Hardware Development I Hardware Development I Yes Iexists from Rev 4 11/11/1 1 )
Process Process description in ML11320A102 719110 I
Manual ML102160471 (Relaled to lier 3 submittal ML102160484 Appendix B documentation Program)
I I
8 6116-10201 Diablo I
I ALS Platform New Revision LAR Section 4.4 Canyon PPS ALS Yes Specification (Rev Yes exists from Rev 6 4.4 Software Architecture I Point to Vendor FPGA ML11277A151 I~
3.1.7 810/31111)
ML11320Al01 2124111 Documents Requirements ML11277A152 6002-00011 ML110600695 Specification
- 11 Westinghouse/CSI Documents to be Submitted with LAR PG&E Documents to be Submitted with LAR 2
Tier 3 Platform LAR Document Notes Notes Document Title Proprietary Proprietary Delivered PO LAR Section Revl_
Title Document TlUe 9
WNA-DS-02442 PGEDCPPPPS Yes ALSSystem ML11279A161 Requirements ML11279A159 Specification 10 C8nyon PPS Management Plan LAR Section 4.5.1, 4.5.3 ALS Management This document Project Plan and SyQAP Plan (Rev 4 covers phase 1 10131111) support Diablo Point to vendor topicals Canyon LAR. A 6002-00000 and documents as later reviSion will needed.
(There \\8 a be created to Previous Rev 2, describe mgmt DCPP Program Directive but used Rev 4)
New Revision activities for CF2 [49] and procedures Yes exists from Rev 2
- design, CF2.ID2 [50] and CF2.ID9 4.5 Software Development This plan states ML11320A107 1126111 Implementation, Yes
[51] control software 3.1.3 that for an ML110410328 testing and Process No ML112nA153 development throughout manufacturing of application, there ML11320A051 and the remaining life cycle will bean ML110410381 (NP) the ALS-based phases (i.e., Operations, chassis that will be application Maintenance, Retirement) specific installed by PG&E under the control of PG&E management plan after development and to document The organization delivery of software activities beyond chart shows the and/or systems to PG&E the generic V&V reporting to from the 10 CFR 50 platform the PM, which Appendix 8 Suppliers.
seems to contradict the platform document.
Need to clarify this.
PG&E Documents to be Submitted with LAR Westlnghouse/CSI Documents to be Submitted with LAR 2
I I
Tier 3 Platform I I
I LAR Document LAR Section Document Title Notes Review Proprietary Notes Title Proprietary PO L
Document Title 11 I
LAR Section 4.5.2 SyQAP Point to vendor topicals 6116~0000 Diablo and documents as Canyon PPS needed.
Management Plan ALS Management New Revision Risk management for the Plan (Rev4 Yes exists from Rev 2 The organization ALS platform is a part of 10/31/1 1)
ML11320A107 1126111 chart shows the Yes the SVP. This is included 6002-00000 No ML110410328 V&V reporting to ML11277A153 3.1.3 as part of the Life Cycle ML11320A051 and the PM. which and is documented in the Previous Rev 2 ML110410381 (NP) seemslo DCPP ALS Management contTadlct the Plan. The ALS Life Cycle platform document.
Management Process is Need to clarify this.
described in Section 6 of ALS Topical Report Submittal 12l ALS Quality Assurance Plan (Rev 6 11/11/11) 6002-00001 LAR Section 4.5.3 Reviewed Rev 6.
This is the New Revision platform specific Yes exists from Rev 4 6002~OOO1 ALS Yes QA plan. This ML11320A074 8/12110 Quality Assurance ML102570793 3.1.5 pia n rerers to the No ML102570793 No Point to vendor topicals ALS MGMT plan ML11320A049 and Plan ML102570787 and documents as needed.
for project ML102570787(NP) organIZatIon.
This plan works under the umbrella of the CSI Quality Assurance I Delivered I
.~
MIl
2
- 13 PG&E Documents to be Submitted with LAR Westinghouse/CSI Documents to be Submitted with LAR TIer 3 Platform LAR Document Proprietary Proprietary Delivered PO Document Title Notes Notes LARSection Title 00000.
Not clear about the spec if1c process for the Diablo Canyon project
- 14 PG&E Documents to be Submitted with LAR WestinghouselCSI Documents to be Submitted with LAR 2
TIer 3 Platform LAR Document Document TItle Notes Proprietary Proprietary Delivered PO LARSection Notes Review Title Document Title 14 FPGA Development 9000-00313 FPGA Yes Yes NA Procedure (Rev 2 Development ML102160486 ML102160486 7/12110)
Procedure Point to Vendor LAR Section 4.5.4 9000-00313 TopicalsiDocumentation 15 as needed Electronics 9000-00311 Development Yes Yes Electronics Procedure (Rev 4 NA ML102160485 ML102160485 Development 7/29/10)
Procedure 9000-00311 16 CanyonPPS Management Plan.
Section 5.11 This plan covers
- planning, development, manufacturing, and system test.
Additional LAR Section 4.5.5 activities are the Point to Vendor responsibility of Topicals/Documentation the licensee.
as needed ALS Security Plan Yes Yes (Rev 0 7/29/10)
It does not include 3.1.10 PG&E needs to develop a ML102160479 ML112nA153 6002-00006 sBfety orga n izati on plan for Software safety
- it may be project concerns during speCific.
installation, maintenance, operation, and retirement.
Reference ALS security plan - still no identification of salety organization.
A detailed report covering the results of an AlS*
based chassis*
level failure mode and
- 15 PG&E Documents to be Submitted with LAR Westlnghouse/CSI Documents to be Submitted with LAR 2
Tier 3 Platform LAR Document Notes Proprietary Delivered PO LAR Section Document Title Notes Proprietary Review Title performed on the project's ALS*
based chassis can be found In Diablo Canyon PPS Reliability and Failure Mode and Effects Analysis, document #6116*
00029. This document Is not avajlable In the G drive for acceptance review.
17 6002-&0003 ALS W Plan The ALS V&V Plan states that for project spesiflc systet,ls, the W activities Is determined on a project by project basts and Is LAR Section 4.5.6 described In the
New Revision ALS V&V Plan Management Plan*
Yes for the PPS Replacement Yes eXists from Rev 4 (Rev 5 9/2811 1)
ML110410380 3.1.12
- 6116-&0000, ML11320A075 1124111 Project"
- Attachment 5 6002-&0003
- Olablo Canyon ML110410319 t'o'IL 110410319 PPS Management TopicalslDocumentation Pla.n". However, the as needed 6116-&0000 Diablo Canyon PPS Management Plan:
- See the ALS V&V Plan for more Information and the interface between the IV&V team and the PPS Replacement team."
- 16 Westinghouse/CSI Documents to be Submitted with LAR PG&E Documents to be Submitted with LAR 2
Tier 3 Platfonn LAR Document Notes Proprietary Notes Proprietary I Delivered I PO Document TItle LAR Section Review Title The organization chart In 6116 00000 Diablo canyon PPS Management Plan shows the IW manager reporting to the PM.
The W& plan does not address the requirements In IS0#6.
6002-00002 ALS Configuration LAR Section 4.5.7 Management Plan, PG&E CF2.ID2, "Software Rev 4 Configuration ALS Management for Plant Yes Yes This ALS CM Plan Configuration Operations and ML102570794 ML102570794 Management Plan Is for Initial design No Operations Support" No activities related to (Rev 4 8111/10)
ML102570788 2 ML102570788 ALS boards.
Need SCM plan for 6002-00002 TopicalslDocumentation development and as needed application of the platfonn.
- 17 PG&E Documents to be Submitted with LAR 2 T LAR Section Document Title Notes I
19 T LAR Section 4.5.8 Point to Vendor Documents as needed I'
Tier 3 Platfonn Review Document Title ALS Test Plan (Rev 2 11/3111) 6002-00005 Reviewed Rev 2.
This plan describes the process of test planning, test Specification, and test reporting for the generic AlS platfonn.
System Integration testing, factory acceptance testing, installation and site acceptance testing are application specific and will be addressed in application-specific test plans.
Requirements Specification (Rev 9 10/5/11)
Westinghouse/CSI Documents to be Submitted with LAR LAR Document Proprietary Notes TItle Proprietary 611 6~OOO5 Diablo canyonPPS System Test Pian Site Acceptance Testing (SAn will be perfonned by the end customer and will not be covered in this document.
V&Vand EQ testing are described In other New Revision documents.
Ves exists from Rev 0 Ves Ml112nA153
- ~
3.1.11 ML102160478 Ml11320A078 7129111 The ALS*102 FPGA design Is changed for the DCPPS System. Thus, there should be a design verification test ofthis board.
Where Is thIS described? Section
5.3.3 states
-Test as many ofthe ALS-102 requirements as possible." It doesn't seem as fonnal testing 6116-10201 Dia~
New Revision Canyon PPS AlS Ves Ves exists from Rev 7 FPGA Ml112nA151 I~':."~ 3.1.7 Ml11320A080 2/24111 Requirements Ml112nA152 Ml110600691 I Delivered I PO r~ '~
- 18 PG&E Documents to be Submitted with LAR Westinghouse/CSI Documents to be Submitted with LAR 2
I LAR Section Document Title I
21 I LAR Section 4.5.9 Point to Vendor Documents as needed
~
LAR Section 4.5.10 Point to Vendor Documentsas needed 23 LAR Sections 4.6, 4.10.2.4,4.11.1.2 4.6 System Qualification I Point to Vendor TopicalslDocumentation 4.10 Communications (Point to Vendor TopicalS/Documentation as needed)
ML102160477 as needed) 24 PG&E 03 Topical Report-TR Approved ALS Diversity 4.7 Defense-in-Depth &
ML102580727 Received SE Analysis (Rev 1 Yes 6002-00031 ALS Diversity Letter - Ml102580726 4119/11 7/29110)
ML102160483 Diversity Analysis CSI Topical Report ML110480845 6002-00031 25 LAR Sections 4.7, 4.9, ALS Platform New Revision 6116-00011 Diablo 4.10 Notes Tier 3 Platform Review Document Title ALS Platform Specification (Rev 810/31/11 )
6002-00011 ALS EQ Plan (Rev 6 1118/11) 6002-00004 Specification (Rev 810/31/11) 6002-00011 Proprietary Yes ML11320A101 Yes ML102160477 Yes ML11320A101 Notes New Revision exists from Rev 6 2124111 ML110600695 New Revision exists from Rev 5 7/30/10 exists from Rev 6 2124111 ML110600695 LAR Document Title WNA-DS-02442*
PGE DCPP PPS ALSSystem Requirements Specification 6116-00011 Diablo Canyon PPS ALS System DeSign Specification I 6002-00004 ALS EQ I Plan Canyon PPS ALS
System Design
Specification Proprietary I Delivered I PO Yes SRS*
ML11279A161 Letter*
ML11279A160 Yes I'~' ''I 3.1.8 ML11277A152
~.-...:*.
Yes I~~
ML102160477 3.1.6 NA Ml10~~0483 I~;y'd Yes ML11277A153 1~1.:.! ;:'.* 1 3.1.8 ML11277A151
- 19 PG&E Documents to be Submitted with LAR WestinghouseJCSI Documents to be Submitted with LAR 2
Tier 3 Platform LAR Document Document Title Proprietary Delivered PO LAR Section Notes Proprietary Notes Review Title 26 4.10 IEEE 603 Conformance 27 4.11 IEEE 7-4.3.2 Conformance 28 Part of LAR Section 4.9 New Revision Point to Vendor Yes ALS Management exists from Rev 2 Documents describing 6116-00000 Diablo 4.9 Design Methodology Plan (Rev 4 ML11320A107 1126/11 deviations to the system, Canyon PPS 3.1.3 Modifications 10/31/1 1 )
No ML110410328 hardware, software or Management Plan 6002-00000 ML11320A051 and design methodology from ML110410381(NP) prior NRC approval\\
Part of LAR Section 4.10 Conformance with IEEE 6116-00011 Diablo Yes 603 4.10 Conformance with IEEE Canyon PPS ALS ML11277A152 Point to applicable 3.1.8 603
System Design
ML11277A152 sections of Vendor Specification TOpical Reports as needed)
ALS Platform New Revision Requirements Yes ellists from Rev 7 Specification ML11320A080 2124111 Part of LAR Section 4.11 (Rev 9 1015111)
MML110600691 Conformance with IEEE 7 6002-00010 6116-00011 Diablo 14 3 2 4.11 - Conformance with Canyon PPS ALS Point to applicable 3.1.8 IEEE 7-4.3.2
System Design
sections of Vendor Specification Topical Reports as needed)
Part of LAR Section 4.10 ALS Platform New Revision 6116-00011 Diablo Conformance with IEEE Yes 4.10 Conformance with IEEE Specification (Rev Yes e)Cists from Rev 6 Canyon PPS ALS 603(Point to WEC/ALS ML11277A152 3.1.8 603 ML11320A101 2/2411 1
System Design
810/31 /11)6002 TopicalslDocumentatlon ML11mA152 00011 ML110600695 Specification in Tier 3 submittal IMm'!alIiH I.Wi!iWJWI I'
37
- 20 PG&E Documents to be Submitted with LAR 2
I Notes LAR Section I Document Titie as needed!
35 4.11 - Conformance with 36 IEEE 74.3.2 4.10 Conformance with IEEE 603 38 39 40 41 4.10 Conformance with IEEE 603
---I 45 46 47 48 49 4.10 Conformance with IEEE 603 Part of LAR Section 4.11 Conformance with IEEE 7 4.3.2 (Point to WEClALS TopicalslDocumentation in Tier 3 submittal documentation as needed)
LAR Section 4.2.12, 4.10.2.4 POint to Vendor TopicalslDocumentation as needed Phase 2 will provide response time confirmation report LAR Section 4.10 Conformance with IEEE 603 Point to Vendor TopicalS/Documentation as needed ILAR S f 41038 ec Ion...
Westlnghouse/CSI Documents to be Submitted with LAR Tier 3 Platform LAR Document Proprietary Notes Proprietary I Delivered Review Title I
I Document Title ALS Platform New Revision 6116-00011 Diablo Yes Specification (Rev Yes exlslS from Rev 6 Canyon PPS ALS ML11277A152 810131/11)
ML11320A101 2124111
System Design
ML11277A152 6002-00011 ML110600695 Specification ALS Platform New Revision 6116~0011 Diablo Yes Specification (Rev exists from Rev 6 Canyon PPS ALS Yes ML11277A152 810/31/11)
ML11320A101 2124111
System Design
ML11277A152 6002~0011 ML110600695 Specification 6116~0011 Diablo ALS Platform New Revision Yes exists from Rev 6 Canyon PPS ALS Specification (Rev Yes ML11277A152 Ii
System Design
8 10/31/1 1)
ML11320A101 2124111 ML11277A153 6002~001 1 ML110600695 Specification I
PO
~
3.1.8 I I 3.1.8 3.1.8
- 21 2
50 51 PG&E Documents to be Submitted with LAR LAR Section Document Title 4.12 Technical Specifications SyQAP LAR Section 4.11.1.1.1, 4.11 - Conformance with 4.11.1.1.2 IEEE 7-4.3.2 Point to Vendor Topicals/Documentation as needed Notes Tier 3 Platform Review Document Title ALS Management Plan (Re... 4 10131/ 11 )
6002-00000 ALS Desfgn Tools (Rev 6 11/9/11) 6002-00030 WestinghouseiCSI Documents to be Submitted with LAR LAR Document Proprietary Notes Title Proprietary New Revision Yes exists from Rev 2 6116'()0000 Diablo ML11320A107 1/26111 Canyon PPS Yes No ML110410328 Management Plan ML11277A15 ML11320A051 and ML110410381(NP)
New Revision Yes Yes exists from Rev 5 6002-00030 ALS ML11320A104 1128111 Design Tools ML110410380 ML110410312 ML110410312 I Delivered I I~"]
PO NA 53 54 4.11 - Conformance with IEEE 7-4.3.2 LAR Section 4.11.1.1.6 Point to Vendor Topicals/Documentation as needed.
Specifically, 4.11.1.6 points to the Vendor SMP's via reference to 4.5.1 of the LAR. (All proprietary)
ALS Management Plan (Rev 4 10/31111 )
6002'()oOOO Section 5.4 (All proprietary)
Yes ML11320A107 No ML11320A051 New Revision exists from Rev 2 1/26/11 ML110410328 and ML110410381 (NP) 6116-00000 Diablo Canyon PPS Management Plan Yes ML11277A153 3.1.3 4.11 - Conformance with IEEE 7-4.3.2 (5.4.2)
[LAR Section 4.11.1.2.2, &
4.11.1.2.3]
LAR Section 4.11.1.2.2 Point to WEC/ALS Topicals/Documentation as needed None Diablo Canyon ALS Dedication Plan (The ALS Platform does not have any parts that need dedication, but the application will most likely have some parts (relays, isolators, etc) that do require dedication)
No Diablo Canyon-specific document
- required, current scope of supply delivers onlyAlS chassis NA 1 ~!.-'",at'J 3.1.3 I~'~
-".I
- 22 PG&E Documents to be Submitted with LAR Westinghouse/CSI Documents to be Submitted with LAR 2
LAR Section Document Title Notes Tier 3 Platfonm Review Document Title Proprietary Yes ML102160479 Notes LAR Document Title 6002-00006 ALS Security Plan Proprietary Yes ML102160479 Yes ML102160479 I Delivered I PO 55 56 57 59 60 4.13 Secure Development and Operational Environment SyQAP SyWP LAR Section 4.13 Point to Vendor Topicals/Documentation as needed PGE Letter DCL-11-123 ALS Security Plan (Rev 0 7129110) 6002-00006 ALS Security Plan (Rev 0 7129/10) 6002-00006 Yes ML102160479 6002-00006 ALS Security Plan 61
- 23 2
5 6
7 8
9 10 Triconex Documents to be Submitted with LAR Tier 2 Platform Review Document Title V10 Platform Document (s):
- 9100042-002 (P) [NRC Submittal Ltr: NRC-V10-10-003)[NRC Ref ML101110707]
- 6200152-002 (P) [NRC Submittal Ltr: NRC-V10-10-003)[NRC Ref ML101110707]
NotApplicable for Tier 2 V10 Platform Document(s):
- 6200106-001 (P) [NRC Submittal Ltr: NRC-V10*10-003)[NRC Ref ML101110707]
V10 Platform Document(s):
- QPM 13.2 (P) [NRC Submittal Ltr: NRC*V10-10-003][NRC Ref ML101110707]
- EDM 12.00 (P) [NRC Submittal Ltr: NRC-V10-10-003][NRC Ref ML101110707]
QPM 13.2 is for identifying product discrepancies. This is used to initiate a revision to a product, this is the input to the requirements phase described in EDM12.0 Proprietary Yes Yes EDM 12.0 describes product development process. It states that additional features are Yes described in the Engineering Project Plans for the specific product. The EPP defines all key parameters of the project. It provides a statement of work, project deliverables, and schedule milestones, including all phase completion reviews.
EDM 12.10 describes engineering project planning. all product development efforts which result in a new release of software or hardware will have an EPP. The EPP is a summary of the scope, objectives, costs, and execution steps associated with a project.
Notes LAR Document Title Proprietary Delivered Notes
12
- 24 Triconex Documents to be Submitted with LAR Proprietary Tier 2 Platform Review Document Title Notes LAR Document Title Proprietary Delivered Notes V10 Platform Document(s):
- EDM 12.00 (P) [NRC Submittal Ltr: NRC-V10-10.oo3)[NRC Ref ML101110707)
This document refers to the EPP, which defines all key parameters of the project. It Yes provides a statement of work, project deliverables, and schedule milestones, including all phase completion reviews.
The EPP is a summary of the scope, objectives, costs, and execution steps associated with a project.
V10 Platform Document(s):
- EDM 11.03 (P) [NRC Submittal Ltr: NRC-V10-10.oo3)[NRC Ref ML101110707)
- QPM 2.1 (P) [NRC Submittal Ltr: NRC-V10-10-003)[NRC Ref ML101110707)
- 9600164-537 (P) (NRC Submittal Ltr: NRC-V10-09-006)[NRC Ref MbQ9337Q293 ML093370299)
EDM 11.03-Process and Product Quality Assurance _. this defines the Process and Product Yes Quality Assurance for a project. This EDM states that an EPP is created for the project as defined by EDM 12.10. This document said that PQP can be a part of the EPP.
QPM 2.1-Quality Planning - process to develop QA plan.
Note EDM 12.00 addresses the overview of the entire lifecycle of product development and release.
The SQAP defines the quality assurance measures to be applied to the Tricon V10 software TSAP. This SQAP describes measures for TSAP for generic platform qualification and testing -the TSAP is one-time usage test software. Not applicable for Diablo Canyon.
V10 Platform Document (s):
(NA - Same as V9 SER)
Yes
- 25 Triconex Documents to be Submitted with LAR 2
Tier 2 Platform Review Document Title Proprietary Notes LAR Document Title Proprietary Delivered Notes 16 V10 Platform Document (51:
[NA - Same as V9 SER]
V9 and V10 provided sufficient information for the generic platform For plant-specific configurations utilizing the Tricon Vi 0, the development process for safety related application software will be controlled under the 10M NSIPM. Invensys will work with the Yes Licensee to identify applicable Tricon V10 security performance requirements that should be incorporated, and, in accordance with the 10M NSIPM, provide traceability of these requirements into the plant-specific implementation of the application software.
In addition to the NSIPM, the Nuclear Delivery Programming Guide, Invensys document 9600380.Q01, provides guidance on Tricon Vi0 application programming for nuclear system integration projects.
[NSIPM ML i02040078.pdf] Included on G drive.
17 V10 Platform Document(sl:
- EDM 90.00 (PI [NRC Submittal Ltr: NRC-V10-10.Q03][NRC Ref ML101110707]
- EDM 90.10 (PI [NRC Submittal Ltr: NRC-V10-10.Q03][NRC Ref ML101110707]
Yes The verification plan states that a System Integration and Verification Plan for the prodcut is created. Not sure if this is the same that the Diablo Canyon V&V plan.
The validation plan states that a System Validation Plan shall be created.
Also, scope of V&V is identified in the Engineering Project Planning.
18 I V10 Platform Document(sl:
- EDM 20.00 (PI [NRC Submittal Ltr: NRC-V10-10.Q03][NRC Ref ML101110707]
- EDM 24.00 (PI [NRC Submittal Ltr: NRC-Vi 0-10.Q03][NRC Ref ML101110707]
Yes V10 Platform Document(sl:
- 6200159.Q01 (PI [NRC Submittal Ltr: NRC-V10-10.Q03][NRC Ref ML101110709, Page 869]
- 650015S.Q00 (PI [NRC Submittal Ltr: NRC-V10-10.Q03][NRC Ref ML101110709, Page 789]
6200159.Q01 describe the plan for testing the NGIO Core Software. It covers the software Yes unit testing and integration testing activities. This document states: The interface between the Core Software and IO-specific Software will not be tested. Where Is this covered?
6500155.Q00 specifies the overall Verification activities that must be performed to release the OPC Embedded Tricon Communication Module TCM 2.0.
20
- 26 2
21 22 24 Triconex Documents to be Submitted with LAR Tier 2 Platform Review Document Title V10 Platform Document(s):
- 6200106-001 (P) [NRC Submittal Ltr: NRC-V10-10-003][NRC Ref ML101110107]
- 6200155-001 (P) [NRC Submittal Ltr: NRC-V10-10-003][NRC Ref ML101110107]
- 6200152-003 (P) [NRC Submittal Ltr: NRC-V10-10-003][NRC Ref ML101110107]
- 6200033-001 (P) [NRC Submittal Ltr: NRC-V10-10-003][NRC Ref ML101110107]
- 6200033-002 (P) [NRC Submittal Ltr: NRC-V10-10-003][NRC Ref ML101110107]
- 9100042-002 (P) [NRC Submittal Ltr: NRC-V10-10-003][NRC Ref ML101110107]
- 9100098-001 (P) [NRC Submittal Ltr: NRC-V10-10-003][NRC Ref ML101110107]
- 9100098-002 (P) [NRC Submittal Ltr: NRC-V10-10-003][NRC Ref ML101110107]
V10 Platform Document(s):
- 6200106-001 (P) [NRC Submittal Ltr: NRC-V10-10-003][NRC Ref ML101110101]
- 6200156-001 (P) [NRC Submittal Ltr: NRC-V10-10-003][NRC Ref ML101110107]
- 6200152-004 (P) [NRC Submittal Ltr: NRC-V10-10-003][NRC Ref ML101110107]
V10 Platform Document(s):
- EDM 74.00 (P) [NRC Submittal Ltr: NRC.V10*10-003][NRC Ref ML101110107]
- EDM 21.30 (P) [NRC Submittal Ltr: NRC*V10*10-003][NRC Ref ML101110107]
- 9600164*500 (NP) [NRC Ref ML093280228]
V10 Platform Document(s):
- NTX*SER-09*10 (NP) [NRC Ref ML110140449]
V10 Platform Document(s):
- NTX-SER-09*10 (NP) [NRC Ref ML110140449]
- 9600164-535 (NP) [NRC Ref ML092810126]
- 9600164-539 (P) [NRC Submittal Ltr: NRC*V10-09-003][NRC Ref ML092810627]
V10 Platform Document(s):
- 9791007-013 (NP) [NRC Ref ML093290424j V10 Platform Document(s):- 9600164-539 (P) [NRC Submittal Ltr: NRC-V10-09-003][NRC Ref ML092870627]. 9600164*731 (P) [NRC Submittal Ltr: NRC*V10-09-007][NRC Ref ML093280198j* 9600164-534 (NP) [NRC Ref ML101110108]* 9600164-531 (NP) [NRC Ref ML093280223]
Proprietary Yes Yes PINP as Indicated PINP as Indicated Notes LAR Document Title N/A (Provided by Platform)
N1A (Provided by PG&E 03 Topical Report)
N1A (Provided by Platform)
Proprietary Yes Letter ML11301A261 SRS PS1 ML11301A268 SRSPS2 ML11301A269 SRS PS3 ML11301A210 SRS PS4 301A211 Delivered Notes
- 27 1
Triconex Documents to be Submitted with LAR 2
Tier 2 Platform Review Document Title Proprietary Notes LAR Document Title Proprietary Delivered Notes 34
"""35 36 P/NP as Indicated 37 V10 Platform Document(s):
- 9600164-731 (P) [NRC Submittal Ltr: NRC-V10-09-007j(NRC Ref ML093280198]
Yes NIA (Provided by Platform) 38 39
--;w 41
""'42
~
r:w
~
"46 r:v
~
V10 Platform Document(s):
- 9700077-012 (NP) [NRC Ref ML093290420]
- 9100112-001 (P) [NRC Submittal Ltr: NRC-V10-10-003][NRC RefML101110707]
(
P/NP as Indicated N/A (Provided by Platform) 1 49 V10 Platform Document(s): Not applicable for platform 50 NA - Not in Invensys Scope V10 Platform Document(s): Not applicable for platform Triconex Documents to be Submitted with LAR 2
Tier 2 Platform Review Document Title 51 V10 Platform Document(s): Not applicable for platform 52 V10 Platform Document(s):
- EDM 90.30 (P) [NRC Submittal Ltr: NRC-V10-10.()03][NRC Ref ML101110707]
53 V10 Platform Document(s):
- EDM 12.10 (P) [NRC Submittal Ltr: NRC-V10-10.()03][NRC Ref ML101110707]
- 9100046'()01 (P) [NRC Submittal Ltr: NRC-V10-10.()03][NRC Ref ML101110707]
54 V10 Platform Document(s):
- EDM 76.00 (P) [NRC Submittal Ltr: NRC-V10-10.()03][NRC Ref ML101110707]
- 9100055-001 (P) [NRC Submittal Ltr: NRC-V10-10.()03][NRC Ref ML101110707]
- 9100055-103 (P) [NRC Submittal Ltr: NRC-V10-10.()03][NRC Ref ML101110707]
- 9100055-105 (P) [NRC Submittal Ltr: NRC-V10-10.()03][NRC Ref ML101110707]
- MDM 12.1 (P) [NRC Submittal Ltr: NRC-Vi 0-1 0'()03][NRC Ref Ml1 0111 0707]
- Dedication Package 022110 (P) [NRC Submittal Ltr: NRC-V10-10-003][NRC Ref ML101110707]
55 V10 Platform Document(s):
. NTX-SER-10-14 (NP) [NRC Ref ML102040062]
Proprietary Yes Yes Yes Notes Notes LAR Document Title Proprietary Delivered Not Applicable for Tier 2 N/A N1A (Provided by Platform)
V10 Platform Document(s):
Yes
- NTX-SER-10-14 (NP) [NRC Ref ML102040062]
- 29 Triconex Documents to be Submitted with LAR 2
Proprietary Tier 2 Platform Review Document Title Notes LAR Document Title Proprietary Delivered Notes 60 61
- 2 Please direct any inquiries to me at 301-415-1132 or at Joseph.Sebrosky@nrc.qov.
IRN 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. DI&C-ISG-06 review matrix for Diablo Canyon cc w/encls: Distribution via Listserv DISTRIBUTION:
PUBLIC LPLIV Reading RidsAcrsAcnw_MailCTR Resource RidsNrrDeEicb Resource RidsNrrDorl Resource RidsNrrDorlLpl4 Resource RidsNrrLAJBurkhardt Resource RidsNrrPMDiabloCanyon Resource RidsOgcRp Resource RidsRgn4MailCenter Resource WMaier, RIV CSteger, NRR WKemper, NRR/DE/EICB RStattel, NRR/DE/EICB BDittman, NRRlDE/EICB.
LChang, EDO RIV ADAMS A ccesslon No.
S ummary ML120590119
- via email OFFICE NRRlDORULPL4/PM NRRlDORULPL4/LA NRRlDE/EICB/BC NRRlDORULPL4/BC NRRlDORULPL4/PM NAME JSebrosky JBurkhardt WKemper*
MMarkley JSebrosky DATE 2/29/12 2/28/12 2/28/12 2/29/12 2/29/12 OFFICIAL RECORD COPY