ML20203L016
| ML20203L016 | |
| Person / Time | |
|---|---|
| Site: | San Onofre  |
| Issue date: | 05/30/1997 |
| From: | SOUTHERN CALIFORNIA EDISON CO. |
| To: | |
| Shared Package | |
| ML20203K553 | List: |
| References | |
| 90400, 90400-ROO, NUDOCS 9803050305 | |
| Download: ML20203L016 (50) | |
Text
{{#Wiki_filter:_ - _ _ _ _ _ _ _ _ _ _ _ _ _ _ - - - - - - l l l r ENCLOSURE 12 SOFTWARE EVALUATION REPOR1
~
9803050305 9a0302 PDR P ADOCK 05000761 PbR
SOFTWARE EVALUATION REPORT mn w JUN 161997 SITE R!.E COW DIGITAL RADIATION MONITORING SYSTEM SAN ONOFRE NUCLEAR GENERATING STATION Section Eage f Executive Summary 2 p 1.
- 2. Table of Contents 5 3 Introduction 7
- 4. References 8
- 5. Definitions & Abbreviations 11
- 6. Background 16
- 7. Evaluation Methodology 20
- 8. Evaluation 24
- 9. Results and Cone'usions 45
- 10. Recommendations 48
- 11. Lessons Learned 51
- 12. Appendices 52 QC 11 UI.lTS 2 & 3
~
SAN ONOFRE NUCLEAR GENERATING STATION SOFTWARE EVALUATION REPORT SOUTHERN CALIFORNIA 0 ie mii..e. DESCRIPTION e ca e RE IRE GS DM OTHER
- s. " "
DATE EDISON 90400 REVO REVISIONS
~
\
soFTV!ARE EVALUATICN REPORT DOCUMENT No. SC400 REvlsloN O EXECUTIVE
SUMMARY
This report provides the results of an evaluation performed by Southern Califomia Edison (SCE) on the MGP Instruments Digital Radiation Monitoring System (DRMS) software. The intent of this sycluation was to:
. Identify areas in the MGP inctruments Verifi::ation and Vslidation (V&V) process that might be viewed as problems, issues, or deficiencies by a quality assurance or Nuclear Regulatory (NRC) audit.
. Correct and/or resolve all major operability problems, issues, or deficiencies.
. Qualitatively assess the MGPl DRMS software development process, the DRMS software in general, and the individual DRMS channel operability.
The evaluation can be divided into two parts:
- 1. The evaluation of the MGPI V&V process, which is the primary focal point of the evaluation.
- 2. The analysis of the software design used by MGPl to implement the DRMS software.
Tha evaluation of the MGPl V&V process consisted of taking each system / functional / performance requirement from SCE's equipment specification (Supplier Scope of Work, or SSOW) and drtermining if the requiremer.t has been adequately addressed in the supplier submitted documents. Tna evaluation of the DRMS software design considered nine (9) specific aspects of the software for entlysis:
- 1. Review of the channel architecture
- 2. Review of the software architecture / design-
- 3. Review of the software complexity
- 4. Analysis of the software unit operating experience
- 5. Analysis of the numbar and nature of recorded software failures and a comparison with the established criteria
- 6. Fault density
- 7. EMI/RFI affects on software
- 8. Human Machine Interface effects
- 9. Probability failure assessment 2
SOFTWARE EVALUATloN REPORT DOCUMENT No 90400 REVistoN 0 Results Tha main focus of the evaluation process performed by SCE on the MGPl DRMS was a review of MGPl documentation and a thread / fiber analysis using SCE's System / Functional / Performance requirements matrix. During this evaluation process, one hundred fifty (150) Software Evaluation Anomaly Reports (SEARS) were issued to address process concems. Fifty-seven (57) Open items
.wera created to track general deficiencies with the software documents. The large number of problems / discrepancies that were found is not acceptable, especially for a system that has und:rgone a V&V process and performs si safety-related function it also indicates that a low level of traceability analysis was performed as part of the SW portion of this project. The quality of the documents reviewed was below average due to fragmentation, spelling and grammar, language
. translation, and adequacy of technical content. Many irt.portant system and perfoiTnance requirements were not addressed or considered during the DRMS software development and V&V process, it is also apparent that MGPl project management did not ensure that SCE requirements l wers conveyed to the software supplier, MGPI-SA.
l Criteria for satisfactory software design and performance were established for each of the nine software aspects, as listed on the previous page. The results of the evaluation show that the software ri. sets or exceeds these established criteria. By meeting the criteria, the software is considered to be of moderate to high quality and to have been implemented in such a way to minimize the likelihood of a Common Mode Failure (CMF). Conclusions M!!PI's Execution of SVVP The Reviewers found the degree to which MGPl succescfully executed '5e SWP to be minimal. As the SCE traceability matrix was filled out by the Review Team, many holes were found as the requirements were ' traced from the specification through the design to the testing phase.- Over two hundred areas were found where the documentation / testing was inadequate or incorrect. As a result of the review, the Team believes that MGPl did not adequately complete the DRMS V&V process as documented in their SWP (SO123-606-1-15-1). i I f 3
SOFTWARE EVALUATl0N REPORT
. _ ..=
D0cVMENT No. 90400 Revision 0 Likelihood of Saccessful System Operation Giv:r all tne above information, it would prt.bab'y seem reasonable to assume that the Team feels that the DRMS should not be installed at SONGS. However, the opposite is in fact true. The Team believes that the PRMS may be placed'into operation if the recommendations as defined in Section 8 of this document are carried out. Additionally, the Team believes that the likelihood of successful , DRMS system operation is favorable for the following reasons:
- Operational history. The MGPI DRMS has an excellent operational history as shown in Section 6.3.4.
. Additional testing done by SCE. Prior to the equipment being declared operationa!,
extensive aquipment testing will be done by SCE.
. Results of this evaluation study. Many deficiencies were corrected by MGPl due to the results of this effort. This has made the documentation much clearer and should aid in system maintainability. Addithnally, other tasks were identified that will be completed before DRMS operational turnover. The completion of these tasks will result in a DRMS V&V that meets SCE requirements.
4
SOF'vWARE EVALUATlDN MPORT DOCUCENT NO. 90400 REVISION 0 TABLE OF CONTENTS
- 1. INTRODUCTION m. - . _. ~ 7 1.1 PU RP05 E . . . .. ...... .. .. .. . .. .... .. .....m.... .... ..... ... ....... . . . . . . . . . . . . . . . . . . . - - . . . . . . . . . . . . . . ... ..o 7 1.2 SCOPE ... . .... ..... ..m .........................o.....................~...... ....m...............m -7 1.3 OBJ ECTIVES . .. _..... ... . .... . ..... . 4 ....... .. .. . . . . . . . . . . . . . . . . . . . . . . . ............4 ..........7
- 2. REFERENCES . - - .8 2.1 REOULATORY REFEPENCES : . . . . . . . . . . . . . . . . . . . . . . . ............ . . . . . . . . . . . . . . . . . . . . ......,.8
- 2.2 EPRl/ INTERNAT10NR STANDARDS ........ ... . . ... ......... . ... . . . . . . . . . . . .~..............................8 23 INDUSTRIAL.............................~............................................................................4. . . . . . . . . . . . .. 9 2.4 VENDOR DOCUMEMS ......... ,.. .. ..... -- .... . . . . . . . . . .............................. .-m...........~ ..... .9 l 2.5 SCE DOCUMEMS ... .. ... ..... .... ......... ...... ... ... ... .. ...... . ..._. 4... ............... . . . . . . . . . . . . . . . . . . . .............._.........10
- 3. DEFINITIONS AND ABBREVIATIONS .
_ . - 11 3.1 DEFINITIONS ... ..m.. m. .... ..... .. .. ...o ... .. .... .. . ....... ......m .. . ....... .. .4..............m............... -11 3.2 ABBREV!ATIONS ............ .... ............................... ....m. . . . . . . . .....................................................I4 l
- 4. BACKGROUND . --
16 1 l 4.1 PROJECT OVEv.V1EW. ..... ...........m.~......... _..........................m..-......... . . . . . . . . . . . . . . ... . I 6 l 4.2 SYSTEM DESCRIPTION .. .... ...... .... . ... .........~. ...~........... . ........................................._.. z......... ... .... . . . I 6 4.2.I Detign Basis, ... . . . ... . . . . . . . . - . . . - . . .16 43 SYSTEM AkCHITEC1 URE.. .. ...m.. .. .............. o . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...m.........-. .. . . 17 4.3.1 Existing . ,.. . . . . . . . . . . . . .. . .. I 7
- 4. 3.2 New.. . ~. .. .. ....... , .. .... ... . ... . . 17
- 5. EVALUATION METHODOLOGY . . 20 5.1 G ENERAL .. . . .....m. .. ... ....... .............................................. . . . . . . . . . . . . . . . . ......,... 2 0 5.2 SV&V PROCESS EVALUATION . .... . . .~. ...m. ...... ............ .. ...~................._ .... .m... .....4...... .21 3.2.I Team . . .- . ... . . . . . . . . . .. .... 21 3.2.2 Documentation . - . . . . . . . . . . . . . . . . . . . . .. ... .. . ... . . . . . . . . . . . . 21 3.2.3 SCE Softwwe Requirements... , . ., . . . . . . . . . 21 3.2.4 Traceability Matrix..... ... ... . . . . . . .~. 22 3.2.3 ProNem Peporting... . . .... .. . . . . . . . . . . . . .. .. . . . . . . . . . 22 3.2.6 Method OfAnalysis (Thread Path).... .... . . . . . . -22 53 SOFTWARE DESIGN EVALUAilON... . . .m. ..-.. ... ... m.... ...........m.........~... . . . . . . . . . . . . . . . . . . . . ... . . . ..... ... .m 23 3.3.1 General.. . .. . . . . . . . . . . . .. . .. . . . . . . 23 3.3.2 Evaluation Criteria. . . . . . . . . .................. .. . . . . . 23
- 6. EVALUATION 24 6.1 TEAM.................................................. _ .... . 24 6.2 SOFTWARE VERIFICATION AND VALIDATION PROCESS...... ... .. ... ... ...... .. . ,...m..... ...... . .. - 25 6.2.I Documentation .-.. . ........... ..... . .. . . . . . . . . . . . . ..... . . 23 6.2.2 Softwre Requirements . . .. . . . . . . . . =23 6e2.3 TraceabCity Analysis.. .... ... . . . . . . . . . - . . . . . . . .. . 23 63 SOFTWARE DESIGN EVALUATION .. . . .. ... . ... ..... .~...._..... .... ... . ..... . . . ..4........... .............-......30 6.3.1 Channel Architecture . . . . . . , . . . . . . . . . . . . 30 6.3.2Softwwe Architecture / Design-- . . . 31 6.3.3 Compiexity .. . ... . . . . . - . . . . . . ,. 33 6.3.4 Operating History;- ...... 38 6.3.3 IdentifledFailures.. . .. _ . ..... . .. . . .. . . 39 6.3.6 Fault Density.. . . . . . . . ... ;40 6.3.7 EM1/RFI Afects on Software.. . _42 5
1 SOFTWARE EVAL.UATION REPORT - DOCU'.2ENT NO 90400 MEVISION 0 m 6 3.8 Human. Machine Interface (HM1) Efects , ... . . . . . . .. 42 6.3.9 Probability Failure Assessment.. . . .. . . . . . . . . . .42
- 7. RESULTS AND CONCLUSIONS - .- 45 71 SOFTWARE VERIFICATJON & VA'.lDATION PROCESS Rc.Stp.Ts. . . ............~... ... . .. . ... .... 4 5 .
7.1.! Adherence to SCE Requirements.. . . . . . . . . . . . . . . . . . . . . . . . 43 7.1.2 Quality ofSystem Documentation . . . . . . . . . . 43 7.1.3 Adequacy and Clarity ofSoftware Va!'dation Testing .. . . . .43 7.2 SOFTWARE DESIGN RESULT 3.. ...... .. ...... ... .. . . . . .......~.. ............... ;46
7.3 CONCLUSION
S ..... .. .... . ...... ..... ..... .. .. ... .......... .. .. . . . . . . . . . . ~ . . . . . . . - - . . . . . . . . . . . . . - . - 47 7.3.1 MGPI's Execution ofSVVP.... . . . . . . . . . . . . . . . - . ;47 7.3.2 Likelihocd ofSuccessfulSystsm Operation . .. . . . . . . . . . . . . . . . . . . . .. . . . . . 4 7
- 8. RECOMMENDATIONS - .
_ 48 8.1 P.ECOMMENDATIONS TO COr.tPLETE THE SOF FWARE V&V PROCESS - . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 8.2 RECOMMENDA11ONS FOR OVERALL SYSTEM MAINTAINABILITY .. .... ....... ..... .. . . - . . - ... 49 8.3 RECOVERY PLAN ._................................ .. . . . . . . . . . . . . . . .... .. .... 50
- 9. LESSONS LEARNED -
. 51 APPENDICES _ _ . . _ _ .52 l-6 d
E I i , i l 6 l l l 1
SOFTWARE EVALUATION REPORT DocuMEi!T NO. 90400 REVistoN 0
- 1. INTRODUCTION 1.1 Purpose The parpose of this raport is to document the work activities performed by the Southern Califomia Edison-(SCE) San Onofre Nuclear Generating Station (SONGS) Digital Radiation Monitoring System (DRMS) Verification and Validation (V&V) Team. This Team was assembled to accomplish two primary tasks:
- 1. Evaluate the MGP Instruments (MGPI) DRMS V&V process to verify that the SCE system, functional, and performance requirements have been met in accordance with Topical Quality Assurance Manual (TQAM) 1J.
- 2. Perform a software evaluation that examines the nature ci the software design structure, the testing and control of the software, and the software operating experience (reliability). The primary thrust of this evaluation is to assess the ability of the software to meet the definM functional requirements.
This Report also con +ains the Team's findings and recommendations along with supplementary information provided by other SCE personnel. These findings and recommendations will be used to support license change submittals, to support Nuclear Regulatory Commission (NRC) and SCE quality assurance audits / reviews, and to determine DRMS equipment operability prior to system startup. 1.2 Scope The work activities described in this document were limited to MGPl DRMS equipment and software delivered and installed in accordance with OCP 2&3 6926.01SJ and DCP SYF 7022.00. It is not within the scope of this project to evaluate the Data Acquisition System (DAS) and wireless area monitors that are associated with these DCPs. No evaluation was performed on the operating system, editors, compilers, etc. used by MGPl to develop the DRMS software. The outputs of these so*Nare development tools were tested during V&V testing. 1.3 Objectives The CRMS V&V Audit Team was chartered to address the following issues:
. Identify areas in the MGP instruments V&V process that might be viewed as problems, issuas..
or deficiencies by a quality assurance or NRC audit.
. Correct and/or resoive all major operability problems, issues, or deficiencies.
. Qualitatively assess the MGPl DRMS softwarc development process, the DRMS software in general, and the individual DRMS channel cperability.
7
SOFTWARE EVALUATION REPORT DOCUMENT No. 90400 REVisloN 0
- 2. REFERENCES ,
2.1 Regulatory References
- 1. 10CFR50, Appendix A; General Design Criteria for Nuclear Power Flants
- 2. 10CFR50, Appendix B; Quality Assurance Criteria for Nuclear Power Plants and Fuel Reprocessing Plants
- 3. 10CFR100; Reactor Site Criteria
- 4. R.G.1.45 Reactor Coolant Pressure Boundary Leakage Detection SyMems; May 1973
- 5. R.G.1.109 Rev.1, Calculation of Annual Doses To Man from Routine Releases of Reactor Effluents for the purptae of Evaluating Compliance with 10CFR50 Appendix I
- 6. Reg. Guide 1.152,1985 Criteria for Programmable Digital Computer System Software in Safety-Related Systems of Nuclear Power Plants
- 7. Rog. Guide 1.153,1985 Criteria for Power, Instrumentation, and Control Portions of Safety Systems
- 8. NRC Generic Letter No. 95-02; S. A. Varga,"Use of NUMARC/EPRI Report No. TR-102348 in determining the acceptabi;ity of performing Analog-to-Digital replacements under 10CFR50.59"; April 26,1995 E. NUREGICR.4640; Handbcok of Software Quality Assurance Technologies Applicable to the Nuclear Industry,1987
- 10. NUREG/CR-6018; Survey and Assessment of Conventional Software Verification and Validation Methods; April 1993
- 11. NUREG-0800; USNRC Standard Review Plan July 1981 2.2 EPRilInternational Standards
- 1. NUMARC/EPRI Report TR-102348 " Guideline on Licensing Digital Upgrades" ; Dec 1993
- 2. EPRI Topical Report, TR-102323; " Guidelines for Electromagnetic Interference Testing in Power Plants"
- 3. ISO 9000-31991, Quality Mar 2gement and Quality Assurance Standards- Part 3:
Guidelines for the Application of ISO 9001 to the Development, Supply and Mainienance of Software
- 4. EPRI Topical Report TR-102348; " Guideline on Licensing Digital Upgrades"
- 5. EPRI Topical Report TR-103291s-V1-3; " Handbook for Verification and Validation of Digital Systems
- 6. IEEE Transactions on Sortwue Engineering, SE-9,1983
- 7. Proceedings of Eighth International Conference on Software Engineering, London,1985 l
8
$oFTWARE EVALuATloN REPORT DOCUMENT No. 90400 Revision 0 2,3 Industrial
- 1. IEEE Std 7-4.3.2 - 1993; Criteria for Dgital Computers in Safety Systems of Nu:: lear Generating Stations
- 2. IEEE Std 279-1971; Criteria for Protection Systems for Nuclear Power Generating Stations
- 3. IEEE Std 603-1991; Criteria for Safety systemt, for Nuclear Power Generating stations
- 4. IEEE Std 730.1-1969; Standard for Software Quality Assurance Plans
- 5. IEEE Std 830-1984; Guide to Software Requirements Specifications
' 6. IEEE Std 982.2-1988; Guide for the Use of IEEE Standard Dictionary of Measures to Produce Reliable Software
- 7. IEEE Std 983-1986; Guide for Software QLality Assurance Planning
- 8. IEEE Std 1012-1986; Standard for Software Verification and Validation Plans
- 9. IEEE Std 1016.1-1993; Guide to Software Design Descriptions
- 10. IEEE Std 1023-1988; Guide for the Application of Human Factors Engineering to Systems, Equipment, and Focilities of Nuclear Power Generating stations
- 11. ANSI X3.159-1989; Programming Language-C s.. ANSI /ANS 10.4-1987; Guidelines for the Verification and Validation of Scient fic and Engineering Computer Programs for the Nachd r Industry 2.4 Vendor Documents
- 1. SCE VPL No. SO123-606-1-9-0, Rev. 0; RMS Protocol Technical Specifications
- 2. SCE VPL No. SO123-606-1-316-0, Rev. O, User's Manual, LDU/RDU
- 3. SCE VPL No. SO123-606-1-317-0, Rev. O, User's Manual, Local Processing Unit (LFU)
- 4. SCE VPL No. SO123-606-1 359-1, Rev.1, Electromagnetic Interference (EMI) Test Report on the Radiation Monitoring System
- 5. SCE VPL No. SO123-606-1-210-0, Rev. O, Letters Jean-Paul Guillemot (MGPI) to D.
Beauchaine (SCE), Feb 20 & 22,1996,
Subject:
RMS software in LPU and DU/Line numbers
- 6. Wyle Laboratories Test Procedure No. 44356-10, Test Procedure for Electromagnetic interference (EMI) Testing on the Radiation Monitoring System for MGP Instruments, Inc.
- 7. SCE VPL No. SO123-606-1-303, Rev.1, LPU/lO Software Test File
- 8. SCE VPL No. SO123-606-1-67, Rev.1, LPUllO Software Requirements Specification
- 9. SCE VPL No. SO123-606-1-367, Rev. O, DRMS Software Verification and Validation Final Report 9
1 .
. _ . J
SOFTWARE EVALUATloN REPCRT DOCUMENT No. 90400 REVisloN 0 2.5 SCE Documents
- 1. Topical Quality Assurance Manual, Book #262
- 2. .SO123-XXIV-5.1; Engineering,~ Construction, and Fuel Services, Software Quality Assurance
- 3. Design Change Packege DCP 2&3 3926.01SJ, Obsolete Equipment; Radiation Monitoring System Replacement Project, Revision 0
- 4. Design Ch inge Package DCPSYF 7022.00, South Yard Facility (SYF); Revision 0
- 5. SCE VPL No. SO123-606-1-12-2, Rev 2; Radiation Monitoring and Sampling System Replacement, Supplier Scope of Work
- 6. Software Reliability Assessment of Radiation Monitoring System, NSG-97-001; February 25, 1997
- 7. N56-97-001, Software Reliability of Radiation Monitoring System l
l 10 l
SOFTWARE EVALUATloN REPORT DOCUMENT No. 90400 Revision 0
- 3. DEFINITIONS AND ABBREVIATIONS 3.1 Definitions o Common Mode (Causes) Failures Failures of equipment or systems that occur as a consequence of the same cause. The term is usually used with reference to redundant equipment or systems. Common cause failures can occur due to design, operational, environmental, or human factor initiators. They can compromise redundancy if they are concurrent failures, that is, failures which occur over a time interval during which it is not plausible that the failures would be corrected, j o Jamming Failure I An anomaly that can affect the function of the software o LocalDisplay Unit Each field unit includes a Local Display Unit (LDU) which provides display and control ,
capabilitics at the monitor (s). The LDU provides access to real time and archived data, indication of alarm conditions, equipment status, control capabilities, and limited configuration capbilities. The LDU also provides communications for remote and externa! data display, contrcl and acquisition, o Local Processing Unit The LPU is the main processor for any given RMS channel. It amplifies, shapes and processes the signals generated by the associated detector using practical algorithms and detector specific software. The resultant data is transmitted to Display Units via RS485 network connections. The LPU also provides storage for the configuration, setup and historical parameters for each detector channel, o MASS Maintenance and Setup Software: PC software used to maintain the monitor parameter table and display monitor information. o Non -Jamming Failure An anomaly that does not affect the function of the software. For example, a specific configuration that does not work as expected. 11
SOFTWARE EVALUATION REPORT DOCUMENT No. 90400 REVisloN 0 o PIPS Passivated, implanted, Plenar Silicon: technology used in the fabrication of large surface semiconductors used as detectors. o Portable Maintenance Computer The Portable Maintenance Computer (PMC) is 6 portable notebook computer running a software moduis called Maintenance and Setup Software (MASS). The PMC can be taken t into the field and connected to a DU via the RS-232 interface or directly to an LPU using a 232/485 converter. The PMC can then be used to perform high level parameter configurations, data analyses, system diagnostics, troubleshooting or failure recovery. < o Quality AMecting Activities Activities of people or equipment which either do, or could influence, quality of safety-related items or work, including designing, purchasing, construction, fabricating, handling, shipping, storing, clean ~,ng, preserving, erecting, installing, inspecting, testing, operating, maintaining, repairing, refueling or modifying. This also dictates activities required by the Station Technical Specifications or otherwise licensed by the NRC. o Real Time Pertaining to a system or mode of opemtion in which computation is performed during the l actual time that an extemal process occurs, in order that the computation results can be used .. l to control, monitor, or respond in a timely manner, within six seconds or less, to tne extem31 process, o Remote Dispiny Unit The RDU performs similar functions as the LDU. The RDUt are located in the Control Room area where centralization of the information from the districuted field units is required. The cabinets can contain one or two RDU chassis, with each chassis holding up to 5 RDUs each. o RS-485 Computer communication standard whose characteristics are particularly suited to the industrial context. o SAS Spectrum Analysis System: system added to certain types of LPUs al'owing a spectrum analysis of pulses coming from the detecior, o Safety-Related Applies to the prevention or mitigation of the consequences of postulated accidents that could cause undue risk to the health and safety of the public. 12
SOFTWARE EVAL.UATioN REPORT DOCUMENT No. 90400 REVisloN 0 o Safety Systems Those systems that are relied upon to remain functional during and following design basis events to ensure the integrity of the reactor coolant pressure boundary, (ii) th., capability to shut down the reactor and maintain it in a safe shutdown condition, or (iii) the capability to prevent or mitigate the consequences of accidents that could result in potential off site exposures comparable to the 10 CFR Part 100 guidelines, o SIIIcon Term used to identify detectors using this crystalline technology with the detector external to the LPU, o Software Requirement Specification l A document that specifies the requirements for a system or component. Typically included are l functional requirements, performance requirements, interface requirements, design requirements and de/elopment standards, o Software Design Document A document that describes the design of a system or component. Typical contents incitde system or component architecture, control logic, data structures, input / output formats, interface descriptions, and algorithms. o Verification And Validation The precess of determining whether the requirements for a system or component are comp! ate and correct, the products of each development phase fulfill the requirements or conditions imposed by the previous phase, and the final system or component complies with the specified requirements. - 13
sOFTWAPE EVALUATION REFORT DoCUMERT NO. 90400 REVislON 0 E. 3.2 Abbreviations a ALARA As Low As Reasonably Achievabl6
= CES Computer Engineering Services, Inc.
- a CFM Common Failure Mode s DAS Data Acquisition System a DCP Desigr Change Package a DRMS Digital Radiation Monitoring System a DU Display Unit a EMI Electromrgnetic Interference a ESFAS Engineered Safety Features Actuation System a FAT Factory Acceptance Test s HMI Hr an Machine Interface
= 1/O Input / Output a LDU Local Display Unit a LPU Local Processing Unit a LPUllO Local Processing Unit,10 Version a LPU/ PIPS Local Processing Unit, PIPS Version a LPU/SAS Local Processing Unit, SAS Version a LPU/Si Local Processing tanit, SiVersion a MGPl MGP instruments s MTBF Mean Time Between Failures a NRC Nuclear Regulatory Commission a NSSS Nuclear Steam Supply System a PIPS Passivated implanted Planar Silicon a RFI Radio Frequency Interference a RTM Requirements Traceabi!ity Matrix e 3AS Spectrum Analysis System a SCE Southem Califemia Edison a SDD Software Design Description a SDR Supplier Deviation Request a SEAR Software Evaluation Anomaly Report 14
SOFTWARE EUALUATION REPORT DOCUMENT NO, 90400 REVislON 0 m Si Silicon
. SONGS San Onofre Nuclear Generating Station a SOAP Software Quality Assurance Plan
, . SRS Software Requirements Specification a SSOW Supplier Scope of Work
. STF Software Test File . STR Software Test Report . SV&V Software Verification and Validation >
a SV&VFR 60'tware Verification and Validation Final Report a SWP Software Verification and Validation Plan e SYF South Yard Facility a TAITS Team Action item Tracking System a TQAM Topical Quality Assurance Manual a V&V Verification and Validation 15
SOFTWARE EVALUATION REPORT DOCUMENT No. 90400 REVisloN 0
- 4. BACKGROUND 4.1 Project Overview The existing analog type Radiation Monitoring System (RMS) at the San Onofre Nuclear GeneraFng Station (SONGS) Units 2 and 3 is twenty-five to thirty years behind the current technology. This equipment is obsolete ano can no longer be adequately maintained. Changing NRC regulations, coupled with an increasing focus on excellence in plant operations, have placed m:ra stringent requirements on the detection, measurement, data acquisition and reporting functions performed by radiation detection and measurement systems. This focus has resulted in a corresponding need for significantly greater performance capabilities and functional characteristics than the existing analog system is capable of delivering.
Tha maintenance and operability difficulties associated with the obsolete analog equipment have r:sulted in an average system availability of cNy reventy three (73) percent The manual sampling and measurement necessary due to this low availability has resulted in higher RMS operational l costs. To recolve these issues, a Design Change Package (DCP) has been developed to provide for l the replacement of the majority of the obsolete analog radiation monitors with state-of-the-art digital equipment.
4.2 System Description
4.2.1 Design Basis R diation monitoring / sampling systems at commercial nuclear power plants are important tools used to cnsure that radiation exposure to the plant personnel and the general public is below the regulatory limits and is as low as reasonably achievable (ALARA). The radiation monitoring / sampling system at SONGS is an integral part of the radiation protection program and consists of four basic categories of permanently installed monitors. They are: e process radiation monitors e effluent radiation monitors e area radiation monitors e post accident radiation monitors. A radiation monitor can be classified in more than one of these categories depending on us design functions. The design basis of the existing radiation monitoring system is to provide information to plant personnel conceming radiation levels in plant process systems, effluent paths, and areas The sy tem measures radiation levels and furnishes corresponding indications, alarm signals, and 16
SOFTWARE EVALUATION REPORT DOCUMENT No. 90400 Revision 0 (if appropriate) generates actuation signals for control of radioactive material. The system consists of permanently installed monitoring / sampling devices, together with a program end provisions for specific routine sampiir g collections and analysis. The overall system is designed to assist plant personnelin qualitatively evaluating the radiological conditions of the plant and in controlling the radiological consequences of normal plant operations, anticipated operational occurrences, and postulated 7ccidents such that the resultant radiation exposure and releases are maintained as low as reasonably achievable and within regulatory limits. 4.3 System Architecture 4.3.1 Existing Each existing channel consists of a detector, preamplifier, and indicating transmitter. The Radiation Transducer (detector) detects incident radiation and converts these incidences into electrical pulses. The preamplifier amplifies and shapes the pulses for transmission to the indicating transmitter. The indicating transmitter counts the pulses received, provides an alarm signalif the number of pulses per minute exceed a predetermined level, indicates the current pulses per minute, and converts the , counts per minute to a standard analog output signal. These components are electrically connectcJ by dedicated cables. The cables are not shared by other channels and the components are physically separated. 4.3.2 New in the new DRMS, the channel architecture is essentially the same as the existing design. The hardwcre and software modules located at, or close to, the measurement point in the process are the Local Processing Unit (LPU) and the Local Display Unit (LDU) as described in section 6.0. The centrally located Remote Display Unit (RDU) is connected to the local units via RS-485 serial communication lines. The output of the RDU produces the control relay contact opening. E%h saiaty function has redundant channels operating in a simple (one out of two) controllogic. The proposed design modification will replace the existing analog Process and Effluent Radiation Monitoring / Sampling System, manufactured by Nuclear Measurements Corporation (NMC), installed at the SONGS Units 2 and 3, with a state of the art microprocessor based system. A total of nineteen (19) radia. ion monitors consisting of twenty three (23) analog channels will be replaced with digital equipment. Of the analog channels being replaced, fourteen (14) are Safety-Related and eleven (11) are Non-Safety Related. In addition to replacing the radiation monitors, eight (8) isolation devices (LPUllO) will be installed to allow information transfer from Safety-Related radiation monitors not being replaced under this DCP to the newly installed DAS. 17
p\ as> k IMAGE EVALUATION g++4 Y h/ N /o % A 7/7 %e n#' TEST TARGET '(MT-3) / 0 <& # , 4
%?' 9? /Q, h i
1.0 'fM EE y ll ILE ll l m iiL4 1;[ l.8 l.25 1.4 1.6 4 150mm >
< 6" *
+
[**%
- gy 8t////
/ !b h PHOTOGRAPHIC SCIENCES CORPORATION 770 BASKET ROAD P.O. BOX 338 WEBSTER, NEW YORK 14580
+%4 Mk g e 44 gag %(t ' !
4 - (716) 265-1600
. . _ . . . . . l- .
SOFTWARE EVALUATION REPORT DOCUMENT NO. 90400 REVislON 0 l Safatv Related Radiation Monitors j 2(3)RE7804G CONTAINMENT TR A AIRBORNE l 2(3)RE7807G CONTAINMENT TR B AIRBORNE 2(3)RE7804P CONTAINMENT TR A AIRBORNE 2(3)RE7607P CONTAINMENT TR B AIRBORNE 2(3)RE7822G FUEL HANDLING BUILDING TR A AIRBORNE i 2(3)RE7823G FUEL HANDLING BUILDING TR B AIRBORNE i 2/3RE7824G CONTROL ROOM INTAKE AIR TR A I 2/3RE7825G CONTROL ROOM INTAKE AIR TR B l Non-Safety Related Radiation Monitors 2/3RE7808G PLANT VENT WIDE RANGE 2/3RE7812 RADWASTE CONDENSATE RETURN i 2/3RE7813 RADWASTE DISCHARGE LINE l 2(3)RE7817 BPS NEUTRAllZATION SUMP DIS' CHARGE l 2(3)RE7819 CCW NON-CRITICAL LOOo l 2(3)RE7821 TURBINE SUMP DISCHARGE SYFRE7904 SOUTH YARD FACILITY EFFLUENT SYFRE7905 SOUTH YARD FACILITY DECON EFFLUENT Safetv Related Isolation Devices 2(3)RJY7820-1 DAS INPUT ISOLAT!ON 2(3)RJY7865-1 DAS INPUT ISOLATION 2(3)RJY7870-1 DAS INPUT ISOLATION 2(3)RJY7874A1 DAS INPUT ISOLATION The proposed upgrade to a digital radiation monitoring system does not change the basic architecture of channel independence that currently exists (detector, preamplifier, indicating transmitter). Each channel wi!l consist of a detector, local microprocessing unit, local display unit, and a remote display unit that are physically and electrically independent from each other. All of the fourteen (14) safey related radiation monitors under consideration for replacement are Non-NSSS Engineered Safety Features Actuation System (ESFAS) radiation monitors. Existing channel cable will used for interconnection betwean components and the ESF actuation logic will remain the same. The channel replacement components will satisfy the same independence and separation requirements as the existing channel architecture. The new channel components consist of a radiation transducer, an LPU, an LDU, and an RDU. Each of these channel components contain the necessary microprocessor (s) and software to perform their intended function. The radiation transducer performs the same function as the existing design and transmits a signal to the digital LPU. The LPU and radiation transducer are normally an integral assembly, but may be separated by a few feet if required by the design. The LPU provides power to the detector, amplifies the generated signal, shapes the signal into standard pulses, and processes the signal using proven algorithms and 18
SOFTWARE EVALuATloN REPORT DOCUMENT No. 90400 REvlsioN 0 l software adapted to the type of radiation transducer being used. Automatic background subtraction
!s provided by the LPU that takes into consideration contamination buildup. Algorithms that ignore pulses that do not represent the phenomena being monitored are also used when required. The calculated radiation values are compared against preset thresholds, and alarms are generated if necessary and transmitted to the LDU and RDU for display and/or relay actuation. Data communication is provided via two RS-485 data links: one to the LDU and one to the RDU.
The LDU is connected to the LPU for local display and control functions. The data is displayd through the use of a simple digital display. Audio (born) and visual (lights) indications are provided as warning devices that are actuated when preset levels are exceeded or by system error status (hardware fault, software fault, parameter fault, test in process, etc.). When extemal information (for cxample, flow or pump status) is needed for data processing in the LPU, these signals are acquired by the LDU and transmitted to the LPU. The LDU is an independent device used to provide local display and control functions at or near the radiation transducer, its failure will not cause the subsequent failure of the channels. The RDU is located in the main control room hallway panels and communicates directly with the LPU via an RS-485 data link. The RDU displays the radiation levels detected, actuates front panel LEDs, g;nerates 4 to 20 mA analog output signals, actuates relays when preset levels have been cxceeded, and generates communication messages for transmission to the DAS. The LDU and RDU perform the same functional requirements but are housed in physically different instrument panels. For the sake of clarity, these two devices are normally referred to as display units (DU). This convention will be adhered to throughout this document unless it is required to make a specific different reference. D 19
h S@FTWARE EVALUATION REPORT l DOCUMENT NO. 90400 REVistoN 0
- 5. EVALUATION METHODOLOGY This Section of the document provides a detailed description of the methodology used for the DRMS V&V process and software design evaluation. l l
501 General The evaluation methodology can be divided into two parts: 1
- 1. The evaluation of the MGPl Verification and Validation process, which is the primary focal point of the evaluation. '
- 2. The analysis of the software design used by MGPl to implement the DRMS software.
The evaluation of the MGPI Verifica' m and Validation process consisted of taking each system / functional / performance requirement from SCE's equipment specification (Supplier Scope of Work, or SSOW) and determining if the requirement has been adequately addressed in the supplier , submitted documents (SQAP, SV&VP, SV&VFR, SRS, SDD, STF, STR, FAT). After all of the system / functional / performance requirements provided in the SSOW were evaluated against the supplier documents and all resulting SEARS evaluated, th's Report was prepared and issued by the DRMS Software V&V Audit team. The evaluation of the DRMS software design considered nine (9) specific aspects of the software for anclysis:
- 1. Review of the Channel architecture
- 2. Review of the software architecture / design
- 3. Review of the software complexity
- 4. Analysis of the software unit operating experience
- 5. Analysis of the number and nature of recorded software failures and a comparison with the established criteria
- 6. Fault density
- 7. EMI/RFI affects on software
- 8. Human Machine Interface (HMI) effects
- 9. Probability failure assessment i
20
~ . _ - -
sCFTWARE EVALUATION REPORT DOCUMENT MO. 90400 Revision 0 5.2 SV&V Process Evaluation This Section of the document providea a description of the work performed during the SV&V cv luation. 5,2.1 Team A qualified, experienced team was assembled to exclusively evaluate the MGPl DRMS V&V process
- cnd the MGPl DRMS software design. The Team performed its duties independently from the Nuclear Design Organization (NEDO) design project group. The members were selected baseo on the following criteria
. Technical evaluators shall have high level of software engineering experience.
. Technical evaluators shall not have had any involvement with the MGPl software design or verification and validation process.
. With the exception of the Team lead, no team member may have been involved in the DRMS replacement project.
5.2.2 Documentation Tha latest revision of the DRMS software documentation submitted to SCE by MGP Instruments was css;mbled for the Team's use. The documents assembled consisted of :
. Software Quality Assurance Plan (SOAP)
. Software Verification and Validation Plan (SV&VP)
. Software Verification and Validation Final Report (SV&VFR)
. Software Requirements Spe.J' stions (SRS) i
. Software Design Descriptions (SDD)
. Software Test Files (STF) i
. Software Test Reports (STR)
- Software Source Code (hard copy)
I in addition, a list of all of the softwcre products covered by these documents were assembled for the Tc m's reference. 5,2.3 SCE Software Requiremeu l The SSOW (SO123-606-1-12, Appendix A) was reviewed and the DRMS software requirements were identified and categorized as system, functional, or performance requirements. This set of DRMS software requirements were then compiled into a listing for use by the evaluation Team. 21 i
SOFTWARE EVALUATION REPORT DOCUMENT No. 90400 REVistoN 0 x 3 5.2.4 TraceabilityMatrix A RrquirementsTraceability Matrix (RTM) was developed by the Team to faci'itate the evaluation of th3 supplier's verification and validation process (See Volume 2 of this document). The matrix columns consisted of the MGPl software documents as listed in section 5.2.2. The matrix rows consisted of individual SCE software requirements (requirement threads) that were taken from the SSOW, Appendix A. An additional column will be added to the matrix which will track the design requirements to the source code. See Section 8.1 for additional information on the scope of this work. 5.2.5 Problem Reporting Th:re are three methods that were used to track issues, deficiencies, problems, and anomalies during the DRMS software evaluation:
- 1. Anomalies identified during the analysis process were captured and docum'ented in SEARa.
An anomaly is defined as anything observed in documentation or operation of software that deviates from expectations based on previously verified software products or reference documents.
- 2. Open items that identify other software documentation issues were also captured and recorded. Open items are software evaluation issues not considered by the evaluators to be anomalies, but still must be tracked to ensure proper disposition.
- 3. Action items are those tasks that are required to disposition and close SEARS and open items. These items are listed in Appendix H.
A computer database application, the Team Action items Tracking System (TAITS), was used to track all issues, deficiencies, and problems identified during the evaluation, including all SEARS and Opsn items that were issued by the Team. The TAlTS shall be used during the Action items disposition effort to track and document the work performed. Th3 procedure used by the Team to identify and track problems is provided in Appendix A. This cppendix also includes a flow chart of the procedure. 5.2.6 Mathod Of Analysis (Thread Path) Th3 technique that was used for this software evaluation is called the ' thread path' analysis method. This technique was chosen for Team use because the MGPl software will be audited by the Nuclear R gulatory Commission at some time in the near future and this analysis technique is used extsnsively by the NRC in auditing safety software systems. The ' thread path' analysis takes, as its starting point, each system software requirement (called a thread) which is then traced (path) through the software documentation. The purpose of this thread p:th analysis is to confirm that each of the system requirements has been adequately addressed by the software development documents, in the process of verifying each of the requirement paths, the DRMS software documents were also assessed to determine if they met the minimum requirements for their document type (SRD, SDD, Test). If a requirement had not been adequately addressed in 22
SOFTWARE EVALuATloN REPORT DOCUMENT No. 90400 REVistoN 0 th) software documen'J tion, or if taere was some doubt about how the requirement was handled in tha documentation, a SEAR was issued to track the concern. In addition, as the V&V process was completed, other documentation issues identified by the Team that were not specifically related to the V&V process were categonzed as Open items for later review and analysis. D;monstration of traceability of software requirements from the system specification through the various software development phases and corresponding software documents is a key element in d:tsrmining the quality and confidence of the software and its ability to be operated and maintained reli:bly throughout the software product life cycle. S.3 Software Design Evaluation This Section of the document provides a description of the work performed during the DRMS software design evaluation. 5.3.1 General Th3 gcVerning documents that describe the required steps in designing, testing, controlling, m:intaining and enhancing the safety-related software used in an analog to-digital conversion program are: Reg. Guides 1.152 and 1.153 and NRC Generic Letter 95-02, which endorses EPRI TR-102348, which in tum references IEEE 603 and IEEE 7 4.3.2. The recommended software quality assurance program for safety-related software is defined by NUREG/CR-4640, in accordance with 10CFR50 Appendix B. Other IEEE standards referenced by these documents establish the software development process requirements for safety-related software app'ications. These regulatory guides, topical reports, and industry standards have been written to assist software dsvelopers in minimizing the probability of occurrence of a Common Mode Failure (CMF). The DRMS software design was evaluai... sing the criteria provided in these documents. 5.3.2 Evaluation Criteria in evaluating the DRMS software used in the SONGS safety-related monitoring channels, the following nine (9) specific aspects of the DRMS software design were examined:
. Channel architecture
. Software architecture / design
. Software complexity
. Operating experience
. Number and nature of recorded failures
. Operational software fault density
. EMI/RFI affects on software
. Human Machine Interface (HMI) Effects
. Probability failure assessment 23 d
Mikk
SOFTWARE EVALUATION REPORT DOCUMENT No. 90400 Revision 0 4 l 6. EVALUATION
'6.1 Team
! A group of highly skilled and trained individuals were gathered to form a high performance team. The i Tccm members united around the following Team charter: 1
- 1. Evaluate the supplier's softwe:e verification and validatiw y ocess for the DRMS equipment to verify SCE's requirements have been met. Issue a formk! sport that cor.tains the Team's
, findings and recommendations,
- 2. Establish and implement a software configuration management plan to control DRMS software
. pnor to station tumover, and
- 3. Reso ve emergent issues relevant to the SCE DRMS verification and validation, analyses and l
i testing process. 4 l The Team was empowered to implement consensus decisions in an independent environment. The l Term structure enebied members to work together, share responsibility for identified tasks, and rely F en cach other to successfuily and efficiently complete the requirements of the charter, i The Team consisted of the following members:
. . Ashmun, Dan: SeniorTechnical Specialist - responsible for software configuration development and testing, and Team document reviews.
. Beauchaine, Barbara: Analyst - responsible for independent software evaluation, reports, and finthed documents.
- Hall, Jo t: Analyst - responsible for Team Action item Tracking System and software configuration special procedure.
. Hazlett, Pam: Analyst - responsible for all Team document deliverables, meeting minutes,
! and references.
. Kusenda, Steve: CES Senior Software Engineer - responsible for independent software evaluation, SEAR dispcsition, and report development.
- Martin, Ben: CES Senior So%are Engineer - responsible for independent software evaluation, SEAR disposition, and report development.
. Nadaud, Julien: MGPl Software Technical Manager - responsible for responding (on behalf i ~o f MGPI) to SEARS, open issues, and evaluation questions.
. Beauchaine, Dennis: Team Lead in addition, Mr. S.H. Chien provided a Software Reliability Assessment of Radiation Monitoring
. System Report, the results of which are described in section 6.3.9. 24 l
SOFTWARE EVALUATION REPORT DOCUMENT No. 90400 REVistoN 0
-6.2 Software Verification And Validation Process 6,2.1 Documentation The evaluation Team gathered and assembled fifty-nine (59) MGPl software documents needed for tha evaluation. These documents are listed in this report as Appendix S, Sc,ftware Documents.
The Team performed a preliminary review of the software documents to determine if they in fact were the latest revisions. Documents that did not meet current revision levels were requested from MGPI-
- Atlanta. The Team did not evaluate documents that were not the current revision levels. A more detailed review of each document was performed during the traceability analysis, in addition to document gathering, a table was generated to identify the software products and associated ' documents. This table is contained in this report as Appendix C, Software Products. During the period from May 1995 through November 1996 the software documents were submitted, reviewed and approved by SCE.
6.2.2 Software Requirements There were seventy-four (74) software requirements (threads) identified by the Team. These requirements were selected from Appendix A of the SSOW document, SO123-606-1-12, and given a unique matrix identifier. These requirements are listed in this document, along with their respective matrix identifier, in Appendix D, Software Requirements. The fifty-nine (59) assembled documents were grouped into document types and the types placed into a matrix. The traceability analysis was c - performed and the results for each thread and path were entered into the matrix. The completed matrix is contained in Volume 2, which is listed in this report under Appendix E as Traceability M;trix. A total of three hundred forty-six (346) thread paths were followed in the performance of the svaluation. 6.2.3 Traceability Analysis 6.2.3.1 Background
>The software products used in the Digital Radiation Monitoring System must be of high quality and reliability. NUREG/CR4640, Handbook of Software Quality Assurance Techniques Applicable To the Nuclear Industry, clearly states that "The basic need for SQA [ software quality assurance] concems the potential for latent defects or errors in software. One of the main thrusts of an SQA program is to reduce the likelihood of defe::ts ever getting into the executable code by applying appropriate, systematic techniques throughout the software life cycle. Latent defects are not the only problem, however. Many computer programs do not do the job that they were specified to do.- A program that b poorly documented or reflects complex rather than straightforward programming techniques is hard to understand, test, or ' debug'. The list of problems that confront software development, operation and maintenance also include unreliable' software; difficult to maintain software; poor requirements specifications; insufficient use of resources; lack of conclusive testing; and poor documentation.
- SQA results in a program of planned and systematic activities to achieve the required software qualities. These actions ensure that materials, data, supplies, and services conform to established technical requirements, and that they perform satisfactorily. The essence of SQA is to prevent problems, remove defects as they are found, and to contribute to the usability and maintainability of 25
SOFTWARE EVALUATION REPORT DOCUMENT No. 00400 REVisloN 0 the software. In other words, a documented and planned systematic pattem of all actions necessary to provide adequate confidence that the software products conform to established technical requirements is soft ...re quality assurance. The Software Quality Assurance Plan (SQAP) and the SV&VP are two key documents in implementing software quality assurance. 6.2.3.2 General MGP instruments initially submitted the SQAP, SO123-606-1-8, and the SV&VP, SO123-606-1-15, in June 1994. Both of these documents were rejected because they were of poor quality and did not meet the intent of the IEEE standards that they were to be based on. In July 1995 MGPl resubmitted these documents which were subsequently approved and accepted by SCE. During the DRMS software evaluation, the MGPI-SA representative stated that MGPI-Atlanta was s:lely responsible to provide customer requirements to the MGPI-SA software development group. MGPI-SA, upon receipt of the requirements, was to review and incorporate the requirements into the software development process and provide the software product to MGPI-Atlanta. MGPI-Atlanta was then responsible for ensuring and yalidating that the software product meets all of the customer requirements. if the requirements were not met, MGPI-Atlanta was to notify MGPI-SA, who was to provide a response. 6.2.3.3 Criteria The evaluation was based upon the Software supplier's adherence to the following general criteria, which were developed based upon established software engineering principles:
- 1. The functional and peiformance technical requirements specifitKi in the contract.
- 2. The IEEE standards in the development of software documents.
- 3. The Software Quality Assurance'and Software Verification and Validation Plans.
- 4. The performance of verification and validation throughout the life cycle.
- 5. _ The ability to trace all verification and validation tasks back to the software requirements.
- 6. The requirement that the software product is scrutable by independent evaluation and testing.
- 7. The requirement that MGPI's verification and validation group was independent from developers.
6.2.3.4 Resulta As a result of the evaluation one hundred fifty (150) SEARS were issued to address process concems. Fifty-seven (57) Open items were created to track general deficiencies with the software documents. A summary of SEARS is provided in Appendix F. The document open items are listed in this report under Appendix G, Open items. 26
SOFTWARE EVALuAT;oN REPORT DOCUMENT NO. 90C.#0 REVislON 0 6,2,3.4.1 Software Verification & Validation Process As a result of the Team's review of documentation and the thread / fiber analysis using SCE's System / Functional / Performance requirements matrix, it became apparent that MGPl had not adequately comp!eted the DRMS V&V process as documented in their SWP (S0123-606-1-15-1). A 1:rge number of SEARS and Open items were prepared by the review Team that document many ( V&V discrepancies. While the review of any software system probably would result in some V&V discrepancies, this large number of issues indicated to the Reviewers that the V&V process was not performed as SCE intended (and expected). The Reviewers acknowledge that when a thorough r; view is performed on a system, problems / discrepancies will be found. However, in the opinion of l the Team more problems / discrepancies were found than is acceptable, especially for a system that l hrs undergone a V&V process and performs a safety-related function. ( in cddition, the Final SWP Report is only a final report in the sense that the generic software testing his been completed by the MGPI-SA France company. As defined by the MGPl SWP, cdditional SW tasks for the installation and check-out phases of the project are to be completed by the MGPl Atlanta offices. SCE should receive an additional" Final" SWP Report when these work phases are finished. 1 In the opinion of the Team, issues such as those described above indicate that the QA program / Software Quality Assurance used by MGPl for the DRMS project is flawed. 6.2.3.4.2 Traceability Analysis There is a lack of documented traceability analysis in the V&V process. The large number of SEARS cnd Open items produced by the Team indicated thtt a low level of traceability analysis was parformed as part of the V&V portion of this project. Also, even though the SWP specifically requires some form of overall traceability documentation as part of the V&V process, no such documentation has been provided by MGPl. In some of the supplied documents (SRS/SDD/STF), traceability tables are provided that attempt to demonstrate that system functions are addressed. These traceability tables are poorly designed and provide a minimum of information that could be used to determine the adequacy of traceability analysis. No overall traceability information has been provided by MGPl that demonstrates requirements traceability from system definition through testing cnd checkout. However, the requirements traceability matrix completed by this Team does provide a trcceability analysis from the system definition through the MGPI-SA integration testing phases. 1 27
30FTWARE EVAL.uATioN REPCRT DOCUMENT NO. 90400 REVislON 0 6.2.3.4.3 Documentation Quality The quality of the docunients reviewed is below average due to fragmentation, spelting and grammar, language translation, and adequacy of technical content as listed below:
- 1. The overall software system can be described in a series of subsystem documents. These documents contain meny references to one another, which often requires a User to access several documents at once to gather information about a subject, in many cases the inter-uocument references are inconsistent, vague, or incorrect, which requires a User to perform an in-depth analysis of large portions of the referenca document just to research a single item or reqtiirement. The breakup of the system documentation, in the opinion of the Team, was designed to assist the developer in the long-term maintenance of the software documentation, it appears that the neads of an end-user such as SCE to understand the documentation for software maintenance or operability tasks was not a major consideration in the documentation hierarchy design. In addition, the fragmented set of documents makes V&V activities much more difficult, and has resulted in some functions not being fully tested.
- 2. The poor grammar and spelling quality of the documents makes the work required to understand the technical nature of the software much hQher than other documents the Team has examined.
- 3. Poor language transIntion from the original French version to the supplied English version of the documents. Wording is often incorrect or difficult to understand. Since technical documents are by nature difficult to comprehend, the inadequate language translation -
makes this task much more difficult. Furthermore, many times French terms are retained in the English documents. When the documents were translated, in many instances terms were translated differently in different documents or sometimes even in different sections of the same documents, making it impossible to track functions of the system. " Output . emulation" was sometimes translated as " profile generation", "extemal test" was sometime translated as " source test", " degraded mode" was sometimes trans'ated as " downgraded mode", and " Release Relay Latch" was translated as " Alarm Acknowledgment".
- 4. In a design or requirements document, in many cases, when a specific requirement is described, references to higher level documsnts are provided (backwards references) instead of including specific details regarding the requirement.
- 5. Inconsistent formats for similar documents, such as the LPU/SAS SDD versus the LPU/Si SDD.
- 6. Inconsistent use of document names and references from one document to another.
- 7. Some features of the system were not delivered. For example in the System SRS (SCE Document SO123-606-1-10-1 Section 3.1.8.3.1) it statet that "the DU... has 3 relay outputs to command check sources." This functionality does not exist in the supplied software.
28
SOFTWARE EVALUATION REPORT DOCUMENT No. 90400 REVisloN 0 6,2.3.4.4 Software Testing The adequacy and clarity of the software validation testing was found to be poor. The ten lacked sufficient detail to allow SCE to set up the test environments and execute the test steps in order to successfully repeat the tests, in many cases, the test acceptance criteria was not specified in enough detail to allow SCE to determine whether a test was run successfully. , The MGPl representative on the Team stated that the tests were written for intemal use by qualified MGPl software and engineering personnel, and that the tests were not intended for use by the customer for maintenance or validation purposes. In the opinion of the Reviewers, without modifications, the tests may not be used by SCE to demonstrate repeatability after software modifications. 6.2,3.4.5 Performance Requirements Many important system and performance requirements were not addressed or considered during the DRMS Software development and V&V process. None of the reviewed documents contsined r;fIrences to these system requirements. More importantly, none of the tests reviewed incorporated tha system requirsments into the testing program. The system requirements include:
. Minimum sensitivity requirements at a 95% statistical confidence level is +/- 25% for 1
process channels (Section 1.6.2.3 of the SSOW).
. Minimum statistical accuracy and confidence level for process channels (Section 1.6.2.3.4 of the SSOW).
- RCS Leak Detectior esponse time,1 GPM within 1 hour (Section 1.6.2.3.5.1 of the SSOW).
- Channel accuracy of +/- 25% (Section 1.6.2.3.5.2.1 of the SSOW).
- Channels should be of non-saturating design from normal range upper limits to 100 times the normal range upper limits; (Section 1.7.4.6 of the SSOW).
. For Particulate and 1-131 channels, time delay from minimum detectable level to remotellocal display and indication shall be 15 minutes or less (Section 1.11.5.3 of the
- SSOW).
In some instances the performance criteria of the system changed from SRS phase to test phase. An example of poor traceability occurred in the LPUllO SRS (SCE Document SO123-606-1-67-1 Section 3.3) stated that the total analog input accuracy shall be better than 1%. In the LPU/lO STF (SCE Document SO123-606-1-303-1 Section 4.4.2.3 Test 5) the acceptance criteria was 5%. 6.2.3.4.6 ProjectManagement MGPl project management did not ensure that SCE requirements were conveyed to the software supplier, MGPI-SA. Through performing the document review and having discussions with MGPl
- ptrsonnel as part of the review, the Team believes that the DRMS Supplier Scope of Work (SO123-606-1-12-2) requirements were not properly identified by MGPl Project Management and communicated to the software developers. The software developers, in turn, did not make efforts to ensure that the generic product software satisfied the SCE requirements as outlined in the SSOW 29
s0FTWARE EVALUATION REPORT DOCUMENT NO. 90400 Revision 0 document. The software develooer's representative has stated that the SSOW requirements were n:t specifically taken into consideration during the software design / development / testing process. Therefore, due to this type of Project Management, it is understandable why the requirements traceability audit has found that several of the SSOW requirements have not been successfully d: signed, implemented, and tested in the DRMS software. These requirements were not fully considered as part of the software development process. 6,2.3.4.7 Source Code As a result of a partial examination of the source code, the Team found that a large amount of Fr:nch language comments and descriptions have been retained. Software maintenance for this source code may require special language skills as well as computer skills. l 6.3 Software Design Evaluation 6,3.1 Channel Architecture i Tha architecture for each of the channels is essentially the same. The hardwart and software modules, which are located at or close to the measurement point in the process are the LPU and the LDU The centrally located display unit RDU, is connected to the local units via RS-485 serial . communication lines. The output of the RDU produces the control relay contact opening. l ! 6.3.1.1 Criteria Tha minimum requirements stated in standard IEEE 279 Criteria for Protection Systems for Nuclear Pswer Generating Stations and IEEE 603 Criteria for Safety Systems for Nuclear Power Generating Stations are the basis for the software architectural design criteria. IEEE 603 references IEEE Std. 7-4.3.2 which provides the specific software criteria. 6.3.1.2 Results The independence and redundancy of the designs, per IEEE 279, meets the same criteria as the pr;vious hardware design. There are no inter-connections from any of these systems that could compromise the integrity of channel independence, in other words, information is not transferred or sh red between channels, common databases are not used by channels, and each channel I component (LDU, LPU, & RDU) has an independent, dedicated microprocessor and clock that perform component functions. This design is valid for safety and non-safety related channels. l l I 30 1
SOFTWARE EVALUATION REPORT -
- OCCuMENT No. 90400 REVistoN 0 6.3.2 Software Architecture / Design The MGP instrument software is designed around the functional requirements for each of the channel components, LPU and DU. The channel software is divided into three software hierarchical modules:
e the RAMSYS Common, e ' the DU Common, and e the LPU Common. 6.3.2.1 Program Structure Refer to Figures 6-1 and 6-2 for software interconnection diagrams. The RAMSYS Common module-resides in both the LPU and DU channel components. This module pedorms jobs and techniques that are standard features in these channel components. The module consists of 19 units containing 93 software functions. This module calls either the DU Common sub-module (if built for the DU), or the LPU General Sub-module (if built for the LDU), depending on the device type. . The DU Common module resides in both the LDU and RDU channel components, operates independently, and performs typical processes specific to the DUs. This module consists of 12 units containing 40 software functions. This module calls sub-modules DU Base and DU Appli. The DU 8;3e module is comprised of 3 units censisting of 30 functions and procedures. The DU Appil module is comprised of 27 units containing 253 functions and procedures. - The LPU Common module resides in the LPU channel component, operates independently of other LPUs, and performs typical processes specific to the LPUs This module is comprised of 3 units containing 14 software functions. This module calls sub-modules LPU Base and Appli Common. The LPU Sase is comprised of 5 units containing 20 functions and procedures. The Appil Common module is comprised of 13 units containing 127 functions and procedures, it may call any one of 4 2 sub-modules depending on the functional application being used for the LPU. The four application specific sub-modules that Appli Common may call are: 1) LPUllO, 2) LPU/ PIPS, 3) LPUISAS, and 3 4) LPU/SI. 6.3.2.2 Data Structures R2 view of the MGP instruments software documentation (see reference section) and telephone conversations held with MGPI-SA Software Development division, indicated that the data structures
- used were based on typical structures allowed within the high level program language of 'C'. Data =
structures were controlled by the program development compiler used which strictly complies and meets the requirements of ANSI X3.159-1989, American National Standard for Programming Ltnguages - C. Since software design is constrained by the physical capacity for storage, channel functional demands and the language capabilities, the complexity and organization of these data structures was left primarily to the software engineer's ingenuity. This development practice is good software engineering practice because the engineer can then concentrate design efforts on the requirements and criteria described in the SRS and SDD. 31
SOFTWARE EVAt.UATISN REPORT DOCUMENT NO. 90400 REVISION 0 LEGEND: uooute NAus RAMS...YS c,# . . .:.. COMMON.- v. tw#*"'.M '# * :m: . . .: :- " SUS-MODULES FUNCTIONS 19 LINES OF COD 93 2783 y
* ;LPU' COMMON "-
,-+,,c w.w = w w :
3 14 236 l l l APPLI COMMON. !-F';LPU BASE ^
*~ - -m-
- a .... n..n. x. ~g 5
13 20 127 821 6171 I e e 6 . . . . ... 3 . . . . . . . . . . . . . . . . . . . . . . ,
- i e i I 4 8 3
i . . i.:d;5LPU-PIPS;Ngi S'YJtLRU nxmdk v u- a.a. ;.- v . . W u a v a-S A 3 ? d 2 ZykyyLPU s is+.aen:.u= SIE,SS mc femw.wa nce PW2REPU40':'Un.
- 3 10 15 15-77 113 '421- 13 5620 -7133 1423 1048 Figure 6 LPU Software Modules 02
SGFTWARE EVALUATION REPORT DOCUMENT ND. 90400 REV1813N 0
- ~ - LEGEND-
@MSYS COMMON uoova ,,,
i6&*TMTV5%lii?? SUS-MODULES 19 FUNCTIONS LINES OF CODE 2783 [gDUpOMMON. ', _ 12 40 2208 Qty;DU'APPLI J. : > i.f@~lDU BASEj.T. ._'r.
.. g _. _, . .
27 3 253 .30 15533 2021 Figure 6 Display Unit Software Modules 4 33
s0FTWARE EVALUATION REPORT DOCUMENT NO. 90400 REVisloN 0. I i. I 423.2.3 Critoria Architecture and design are the bases for software reiiability, it is a documented fact that reliability
- cannot be tested into software systems. Programs that are well designed and developed around solid architectural features in both data structures and hierarchical control structures are the first i defense against errors. Therefore, the two most important characteristics of the software architecture cre :
- . l
- 1. The hierarchical structure of procedural components or modules :
l
. The design should exhibit a hierarchical organization that makes intelligent use of control ,
among components of software. ! l . The design should be modular; that is, the software should be logically partitioned into i components that perform specific functions and sub functions. ; ! . The design should develop modules that exhibit independent functional characteristics.
-. The design should lead to interfaces that reduce the complexity of connections between
> . modules and the extemal environment,
- The design should be oeveloped using repeatable methods that are driven by information obtained during the software requirements evaluation.
~
- 2. -The structure of data
. The design should contain distinct and separable representations of data and procedures.
! l 1 34
s0FTWARE EVALUATION REPCRT DoCUUENT No. 90400 REVisloN 0 6.3.2.3.1 Results The following results were obtained based on a review of software documentation and source code listing submitted by MGPl. 6.3.2.3.1,.1 Program Structure The RAMSYS Common module is the highest level module in the program structure and declares all submodules that are global. The module controls 1g sub-modules and 1 subordinate module when used in the LPU or 2 subordinate modules when used in the DU. Figures 6-1 and 6-2 show the - htrarchical organization of the main and subordinate modules for the DU and LPU. Each of the subordinate modules has its sub-modules structured in a hierarchical organization. The organizatior, makes rational use of control between software modules and reflects a logical partitioning of specific functions and sub-functions into modules and sub-modules. Each of the modules $nd sub-modules developed in this program represent autonomous fur,sional attributes. Functional independence and ' low complexity interface connections have been schieved by developing the modules with moderats to high cohesion and moderate to low coupling characteristics. During the conceptual and d;velopment process methods were identified for use in several areas of the program. These proven methods were then designed into sub-modules and repeated in superordinate modules. The use of these practices reflect good software engineering judgment and design methods. 6,3,2.3.1.2 Data Structures The data structures used throughout the design reflect logical relationship among individual elemems of data. These structures adhered to the requirements of industrial standard ANSI X3.15g-198g, American National Standard for Programming Languages - C. l 6.3.3 Complexity The complexity of a software design can be used as a measure of the likelihood of a fault or failure occurring during Hs operational life. The influence of sofbuare complexity on fault occurrence can be reduced by the increasing levels of V&V activities. V&V levels are determined based on the complexity and the integrity requhed from the software (Ref. NUREGICR-6018 Table 2.4.3-1), integrity, h this context, refers to the consequences resulting from the failure of the software. 6.3.3.1 Criteria To further examine the complexity of the safety software, it was necessary to em.olish a set of criteria to define the level of complexity. A set of criteria relating to complexity of software is established la NUREG/CR-6018, Survey and Assessment of Conventional Software Verification and Vclidation Methods (Ref. Table 2.4.2-1). This document cCegorizes software as having low, medium or high levels of complexity in six areas of software design. Table 6-1 provides these criteria. 35
s0FTWARE EVALUATION REPORT DOCUMENT NO 90400 REVislCN 0 Table 6-1 Software Complexity Criteria Complexny Fedor Low Level Medium Lovet High Level
- t. PhysealControl None No dwect control but provides Can dwoctly rnanipuste control Capabikty decision data into control system elements inodutos Advoory funden
- 2 Processing Not Real Tsme Near realtano Real tune Srquentet N/A Cooperstmg Single processor Muttiple processors Concunenttmutaple heterogeneous processors Synchronous N/A Asynchronous Centralmed Central /detnWied Highly detnbuted Batch / interactive Interactive Interecuve
) Interactivity wan Other Stand alone Embedded / Attached Embedded Lystems Smg8e User interface Continuous /intermanent data Continuous Data input input No date-interfaces Data interfaces Mutsp6e Channels
- User-dnven usualty data drrson Usualty data driven No interrupt handimg Possete winerrupt handimg Possene interrupt handimg
- 4. Knowledge / Data Homogeneous Homogeneous / Heterogeneous Structures & Storage . heterogeneous Centrahaed Centraluted/Detreuted Centralmed/Detnbuted Denved from codrhed Denved from codshed sources Denved from codified sources sources or expert or invented sources
- 6. Deceon Procedure Backward (top.1own) or Backward, forwere and mixed AH types of chainmg Forward (Bottom up) chaining Breadth first or Breadth first or Breadth first or De.,th first Depth f1st Depth first Tl59.sion Procedure Monotonic reasoning Hounsto reasoning, Constraint Model Based inferencmg plus (cord'd) based reasoning all other types Belief.revis'en, truth maintenance
- 6. Uncertamty Handhng None Fuuy reasoning, reasonmg Comp 6ex funy logic and under uncertainty uncertainty reasontrp.
Multiple hypothesis evulation Note:
- Interpreted as multiplexed inputs 6.3.3.2 Results Each aspect of the design has features that are used to determine the level of complexity cf the system. Table 6-2 summarizes the review of the safety software with respect to the software complexity criteria, it can be seen that the software complexl?! falls into the low-medium category, i
36 , i s
S3PTWARE EVALUATION REPORT. D3CUMENT NO. 00400 REVISION 0 - -
- Table 6-2 Software Complexity Complexity Factor Software Feature Assessed Level Comments -
- 1. PhysicalControlCapabit;ty None Low No closed loop control
- 2. Processmg Near Real Time . Modum Penodic iw-:-:: 7 of input dets Sequential Low Timed seqier.co for data
. ;g_:_--- ,;;
Muluple processors Medium Processors in LPU & Deploy Units Synchronous Low Clock dnven Contralmed/ Medium Processmg in LPU & RDU/LDUs distributed interschve Medium Contmuous measurement
- 3. Inleiectivity with Other Attached Medium DAS socesses system d&[~
Systems Conunuous/ Medium intermittent requests for date. Intermittent data input READ only Datainterfaces Medium DAS access
- 3. Interactivity with Other - User driven (polled) Low Primarily a polled request for !
Systems (cont'd) date. Periodic user requests Possible interrupt Medium Polled or usei requests for data, hanoling require interrtpts to main system program 4, Knowledge / Data Structures Homogeneous Low Data situcture uniform
& Storage throughout system Centralmed/ Medium LPU & DUs have separate Distributed storece h from codified Low. Instruchons from program set sources only. C laneteos used
- 6. Deasion Procedure Backward (top down) Low Std Clanguage
- Breadth first Low Std C language Monotonic reasonmg Low Std C language
- 6. Uncertamty Handling None Low No artificialintelhgence used in logic decisions 37
SOFTWARE EVALUATICN REPORT DOCUMENT NO.- 90400 REVislCN 0 6,3,4 Operating History MGP instruments, the supplier of the DRMS replacement system, has a long history of supplyir g RMS systems to the nuclear industry. They began producing analog based systems for the French nuclear program in 1962 and continued producing this type of equipment until the 1980's. In the mid 1970's they produced their first digital electronic modules, in 1980 they designed their first Microprocessor Based Processing and Display Units. A second generation microprocessor-based design was introduced in 1985. This design incorporated multi-channel detector capability using a single LPU. New detector technologies were designed at this time as well. A third generation digital system began development in 1993. This system was developed using the emerging European Standards, the ISO 9000 series, as the basis for the system design. This is the software design that b used for this DRMS project. 6,3.4.1 Criteria There are no specific industry criteria for the required operational experience for software modules to be used in a nuclear safety application. 614.2 Results The current MGPl operational digital systems that use the latest software design are installed at eight plants around the world. The largest installed system is located at the Swedish plant, Ringhals, Units 1,2 and 3. Table 6-3 provides the unit-days and unit-years for each software as of June 1996. 38
l-SCFTWARE EVALUATION REPORT
- DOCUMENT NO.- 90400 REVislON 0 Table 6 3 Operational Experience of Software Modules thru 6/96 Plant Site LPU/ base' LPU/ PIPS LPU/SAS . DU Base &
(FMIS & CPIS) (CRIS) Appil' Ringhals 24054- 4695 7525 34962 Berseback 657 0 438 219 Technicatome 515 0 0 0 Loviisa 5556 0 5556 0 - Kosloduy $32 0 532 1064 - Olkiluoto 326 0 0 326 PAKS- 412 0 0 412 North Anna 626 0 626 626 5otal unit-days 32678 4695 14677 37609 Total unit-years 89.5 12.9 40.2 103.0 Notes: 1 -LPU base includes RAMSYS Common, LPU Common, Appli Ccmmon and LPU Base 2 -DU Base & Application includes RAMSYS Common, DU Common, DU Base and DU Appli. The placement of active radiation measurement channels into operation has occurred on a continuing basis over the last'5ree years. The mah LPU base and DU base and application modules have operational experience from 89.5 to_103 unit years. The PIPS detector application module has only been used at the Ringhals plant and therefore has not had the same level of operational experience as the other software modules. These operational sxperience levels are considered sufficient to provide a good level of confidence in this software module's design. Each software module that is used in the design has had revisions applied to it. The nature of these revisions have been relatively minor. Revisions to all software modules (since the inception of the V&V program in 1993), are documented in the SV&VFR, SO123-606-1-367, 6.3.5 IdentlRedFailures Fcilure data was obtained from the software supplier based on reported failures from operational equipment (See SV&VFR ). The number and type of failures are important in comparing this software with other industrial software projects. 39
SOFTWARE EVALUATION REPORT DOCUMENT No. 90400 REVi$loN 0
~
4 8 ,3.5.1 C rite ria The criteria for software failures is that the failures be identifiable and be non common mode in nature, ideally, the failure data would be separated into faults of various degrees of severity and tima tagged from the time of introduction into' operation. However, data with this degree of insight is not i available. The results of this evaluation are shown in the following section, 6,3.6.2 Results The following statements give totals for the number of errors found for each device type: Total reported LPU w/SAS detector software failures = 64
- (Jamming & non-jamming faults)
Total reported LPU w/ PIPS detector software failures = 54 , (Jamming & non-jamming faults) l Tctal reported DU failures = 102 1 (Jamming & non-jamming faults) j None of these failures were the common mode type. All failures were readily identified. 3 6,3.6 FaultDensity l Fcutt density is the number of inherent faults per the number of lines of code. The number of cverage inherent faults is linearly related to the prmram size and uniformly distributed across the code (see IEEE Transactions on Software Engins " 9, pp. 664-672,1983 and Proceedings Eighth Intemational Conference on Goftware Engin6en c London,pp. 330-336,1985). Fault d nsity values are used in the development process and vary dependent on the software life cycle ph se. Typically values for fault density _ are estimated at the following stages: coding, unit test, subsystem test,- system test and operation. From measured fault density values based on industrial l . sxperience, it is possible to use these industrial values to compare against the DRMS software fault l d:nsities to establish whether the software is performing within normal industrial performance ranges. 8.3.8.1 Critoria F The SV&VFR provides operationel fault history data and number of lines of code for the LPU and DU software.' Data has been collected for industrial systems on various software life cycle phases. In l l
. the operational life cycle phase 50 systems were analyzed and average fault density values given. '
These systems had an average operational time of 11 months and source lines of code ranging from 4.1K to 523.8K lines. The range of fault densities in this operational mode were O to 10.95 faults per } 1000 lines of source code (see Software Reliability Measurement Prediction Application, Table 5.2 & ] 5.3. pp.116-118, by John Musa,1990). 4 , 40 !
, . - , - - - - . - . , , . , ,- ,7,. . ,,.,,.-m,,-,e m -- m ,
s3FTWARE EVALUATION REPORT DOCUMENT NO. 90400 REVisiCN 0 _ 6,3.6.2 Results i Examination of the RMS software modules provides the following information given in Table 6-4: Table 6 4 Software Source Code Lines Function Module Source Code Lines LPU RAMSYS Common 2783 LPU Common 236 LPU Base 821 t LPU AppilCommon 6171 t/O analog 511 Common Subtotal 10522
~
LPU/ PIPS 5620 Total PIPS 10522 + 5620 =16142 LPU/SAS 7133 Total S/.S 10522 + 7133 = 17655 DU RAMSYS 2783 DU Common 2208 DU Base 2021 DU Appli 15533 Total 22545 The total number of faults given in Section 6.3.t. :or both LPU detector types (PIPS, SAS) are dividad by the number of code source lines given in Tabl6 6-4. Fault densities are given in Table 6-5: , Table 6-5 Fault Densities SoftEare System No. Faults Source Code in Klines Fault Densty in faults /K lines LPU PIPS 54 16.142 3.3 PU SAS 64 17.655 3.6 DU 102 22.545 4.5 average fault density 3.8 The average fault density is 3.8 faults per 1000 lines of code which falls well within the range of the comparable industrial study. 41
soF*tWAME EVALUATION REPORT ! DOCUMENT No. 90400 REVislCN 0 L 6.3.7 EMURFI AWects on Software ! Electro-Magnetic Interference (EMI) and Radio Frequency Interference (RFI) tests have been
; performed on ESFAS radiation monitor prototypes in accordance with a Wyle Laboratories Test '
Procedure No. 44356-10 " Test Procedure for Electromagnetic Interference (EMI) Testing on the Rcdiation Monitoring System for MGP instruments, Inc." This procedure is based on EPRI Topical ! R2 pori,,TR 102323, " Guidelines for Electromagnetic Interference Testing in Power Plants" Tests for emtsions and susceptibility were applied. I The results of these tests are summarized in Wyle EMI Test report (VPL #SO123-606-1-359). All i tests were successfully completed, ' i 6.3.8 Human-MachineInterface(HMI) Effects ! Tha new design presents measurement values to the user in unambiguous, engineering units with no conv6rsions or translations required. The values are displayed in a digital format relioving the user of ' . interpolating from an analog scale. Operator interfaces are used to change conversion values, set points and other data base items sssociated with detector and process parameters. The incorrect entry of a database item may cause
- crroneous readings from a given channel, however there are no shared databases that would cause a common mode error in all other channels.
Acoess to change database items is restrir4ed through password protection. Four levels of access , exists. To produce a common mode software error, unauthorized software changes would have to i be inserted separately into each channel. L l 6.3.9 ProbabilityFailure Assessment ! 6.3.9.1 Review Of Failure Assessment Approach l In document NSG-97-001, Software Reliability Assessment of Radiation Monitoring System, an assessment was made of the probability of each of the ESFAS radiation monitor systems failing to l perform its function. The assessment compared the existing analog systems with the replacement digital systems. l Ecch system has been designed for redundant trains to measure radioactive concentrations in each l of the airbome pathways. The function of ti.rae monitors is to lnitiate an isolation function after L Exceeding the setpoint. The current Technical Specifications for SONGS state that only one monitor ! his to be active for the system to be operational. The probabilistic estimate of system failure was [ svaluated for the cases where both trains are operational and for the case where only one train is l operational.
, +
4 42 f
SOFTWARE EVALUATION REPORT ooCuMENT NO. 9040V REVistoN 0 MTBF data for the existing analog systems was obtained from SONGS plant Maintenance Order records. Generally, different failure rate values were obi.alned for the train A and train B monitors. Fcr the 1 out of 2 logic analyses, the values for an 'AND" logic function is determined by the product of the individual train values. For the one out of one logic case, the lowcat value of the two monitors is chosen as the active monitor.- , The replacement digital systems failure data was obtained from vendor documents. The data r:ceived from the vendor was a combination of hardware and software failure probabilities. Estimates of the feilure rates were made by dividing the failures that have occurred since placing the equipment into operation by the total number of hours of operation for each software module. Software failure rates were obtained by this method. Hardware failure rate data was determined by Extracting the software failure rate data from the combined hardware and software data.- For the 1 out of 2 logic, logic trees were configured to account for tne redundant hardware paths but no credit was taken for redundant software pathways. This implies that if a software failure occurs, thin it will be c common mode failure. The softwaro failure values that are used ar's derived from the single software failures. This adds s level of conservatism to the overall failure probabilities. 43
s0FTWARE EVALuATIDN REPORT DOCUCENT NO. 90400 Revision 0 6.3.9.2 Failure Probabilities-One out of Two Logic The results of a failure probability assessment for a 1 out of 2 logic configuration, from Saction 2.5, reference 6, are given in Table 6-7. Table 6-7 Summary of System Failure Probabilities (1 out of 2 logic) System Failure Rate in failures /hr MTBF in hrs / failure (Section 2.5 Ref. 6) Table 3 Calculated Dighal(new) Arialog (existing) Digital (new) Analog (existing) CPIS 2.6'E-5 2.2E-4 3.85E4 4.55E3
. CRIS 1.5E-5 1.2E-4 6.67E4 8.33E3 FHIS 1.7E-5 1.4E-4 5.88E4 7.14E3 6.3.9.:s Failure Probabilities-One out of One Logic The results of a failure probability assessment for a 1 out of 1 logic configuration, from Section 2.5, reference 6, are given in Table 6-8.
Table 6-8 Summary of System Failure Probabilities (1 out of 1 logic) System Failure Rate in failures /hr MTBF in hrs / failure (Section 2.5, Ref. 6) Calculated Attachment 3 Digital (new) Analog (existing) Digital (new) Analog ! (existing) CPIS 1.3E-4 2.64E-3 7.69E3 3.79E2 CRIS 8.59E-5 8.11E-4 1.16E4 1.23E3 FHIS 8.36E-5 1.96E-3 1.2E4 5.1E2
- 6.3.9.4 Summary of Failure Probability Assessment The prediction of software failures is an imprecise science and therefore, the margin of error cssociated with generated MTBF values is likely to be large. However, by comparing the calculated analog to digital system failure rates, the results of this assessment show that for DRMS replacement, MTBF is an improvement of approximately a factor of ten.
44
SOFTWARE EVALUATloN REPORT DOCUMENT Ho. 90400 REVisloN 0
- 7. RESULTS AND CONCLUSIONS in this sectinn the findings of the evaluation study of the MGPl DRMS software project which was performed by Southern Califomia Edison will be summarized, in particular, the results regarding the adherence of the system to the requirements as defined in the SCE Geope of Work for this project, the quality of the produced system documentation (SRSs and SDDs), end the adequacy and clarity of the software validation testing will be provided. Additionally, conclusions will be provided regarding the degree to which MGPl successfully completed its Software Verification and Validation Plan, and the like" hood that the MGPl software product will fulfill its intended purpose in the proposed SCE configuration. .
7.1 Software Verification & Validation Process Pesults 7.1.1 Adherence to SCE Requirements it doas not appear that an effort to fully address SCE's specific system requirements was made, in a letter from Mike Edelman of MGPl to Ray Baker of SCE (dated Nov 25,1996), it is said that "all the SRS, SDD, STF, and STR documents are generic in nature and were not develoned for any snecific customer." Since these documents should completely describe the functions and capabilities of the DRMS, it follows that the DRMS itself is a generic product. Since specific SCE requirements were not addressed (for example, that an operating system be used, that the software be easily portable to other computer systems, that a database manager be provided, etc.) and no SDRs for these issues were provided, it appears that the SCE specific requirements were ignored in favor of developing a generic product. 7.1.2 ' Quality of System Documsntetion The overall quality of the system documentation was found to be poor. The translation of the documents from French to English introduced far too many errors in the documents to o ' e acceptable. The MGPl scheme of generating many separate documents and then cross-referencing sections from one document to another produced a document set that was fragmented and hard to follow. Finally, poor traceability was enforced between the Software Requirements Specificaticas and their respective Software Design Documents and Software Validation Tests. Too many discrepancies were found where requirements were established and then were not designed or tested. 7.1.3 Adequacy and Clarity of Software Validation Testing The adequacy and clarity of the software validation testing was found to be poor. There is a fundamental disagreement between SCE and MGPI as to the amount of detail that is required in the validation tests. MGPl believes that only enough detail is necessary to enable a MGP' software engineer to reproduce the test, and that is all that was provided. SCE believes that enough information should have been provided to enable SCE personnel to perform and duplicate the tests. Since obviously there is a large gap in experience and capabiiities between the two possible 45
sCFTWARE EVALUATloN REPORT DsCuMENT No. 90400 Revision 0 groups of testers, there is a large gap between the detail of the tests as provided and the detail of the t:sts as desired. Instructions on setup snd use of hardware tools and software utilities was found to be particularly lacking. Additionally, MGPl used a testing scheme that allowed taking credit for t: sting that vfss not performed in the section that the criteria was defined in the Softwa:a Test File. For example, in Section 2.11 of the DU Software Test File (Communication and slave scanning management) there are 13 generic features to be tested. One of these features is "the DU can mask some of its slaves to avoid access confilets"). Later in the DU STF (Section 4.3.2.7, Communication end scanning managemsnt), where the detailed plan to test the generic features as defined in Suetion 2.11 is defined, the slave masking feature is missing. Somehow the slave masking is tested in Section 4.1.4, Test 3 of the DU STR, which is titled Command Management. Slave masking is not discusse Nne Command Management generic testing section of the DU STF (Section 2.4). It is believed inst th5 somewhat haphazard testing approach led to tests that should have been pe! formed and werc not. 7.2 Software Design Results in evaluating the DRMS software used in tae SONGS safety related and non safety related monitoring channals, the following nine (9) specific aspects of the DRMS software design were cxamined:
. Channel architecture
. Software architecture / design c
. Software complexity
. Operating experience
. Number and nature of recorded failures
. Operational software fault density
. EMI/RFI affects on software
. Human Machine Interface
. Probability failure assessment The DRMS channel architecture complies with IEEE standards and continues to reflect a non-complex cad independent channel design. In addition, there are no interconnections between channm introduced as a reuult of this new design. The software is considered to fallinto a low to-medium enge complexity level. The program organization and data structures reflect good software cngineering judgment and design niethods. MGPl software products are in operation throughout the world and have operational experience from 89.5 to 103 unit years. Of the ;dentified software faults, all of them were readily identifiable and have been coveted. None of these faults lead to a software common mode failure. The fault density value de~ strates that mature so'tware products are in s rvice. The MGPl equipment and software
- w .ssed all EMI/RFI qualification tests. Access to 6
change parameters is restricted through passwr 4rotection. Four levels of access exists. To produce a common mode snftware error, unaur azed software changes would have to be inserted s:parately into each channel. Finally, in comr ng the calculated analog to digital system failure r;tes, the results of this assessment show the ior DRMS replacement, MTBF is an improvement of approximately a factor of ten. 46
SOFTWARE EVAt.UATION REPORT DCCUCENT NO. 90400 REVl31GN 0 7.3 Conclusions 7.3.1 MGPI's Execution of SWP The Reviewers found the degree to which MGPl successfully executed the SWP to be minimal. As the SCE traceability matrix was filled out by the Review Team, too many holes were found to believe a serious effort was made by MGPl to ensure that the requirements were traced from the specification through the design to the testing phase. Over two hundred areas were found where the documentationhesting was inadequate or incorrect. 7.3,2 Likellhsod of Successful System Operstion Given all the above information, it would probably seem reasonable to assume that the Team feels that the DRMS should not be installed at SONGS. However, the opposite is in fact true. The Team believes that tha DRMS may be placed into operation if the recommendations (as defined in Section 8 of this document) are carried out. Additionally, the Team believes that the likelihood of successful DRMS operation is favorable, for the following reasons:
. Operational history. The MGPl DRMS has an excellent operational history as shown in Section 6.3/
. Additional testing dons by SCE. Prior to the equipment being declared operational, extensive equipment testing will be done by SCE.
- Results of this evaluation study. Many deficiencies were corrected by MGPl due to the results of this effort. This has made the documentation much clearer and should aid in system maintainability. Additionally, other tasks were identified that will be completed before DRMS operational turnover. The completion of these tasks will result in a V&V on the system that meets SCE requirements, 47
sCFTWARE EVALUATION REPORT DGCuMENT NO. 90400 REVisl0N 0
- 8. RECOMMENDATIONS As a result of the work performed for the DRMS Software Evaluation project, the evaluation Team -
recommends additional work that must be performed by SCE in the short term (prior to DRMS equipment operation and tumover) and over the long term (6 9 months from the date of this repori) to complete the DRMS software V&V. The short term work items are required to complete the DRMS SV&V process, while the long term work items are intended to improve overall system maintainability by SCE. Appendix E, the Software Evaluation Anomaly Report Summary, provides a list of the recommended tasks (Action items) related to each SEAR. 8.1 Recommendations to Complete the Software V&V Process The recommended tasks that SCE must complete prior to DRMS equipmant operation and turnover are categorized as follows'.
- 1. Prepare DCNs to conect the MGPl supplied DRMS software documentation, make tne documents consistent with one another, and add additionalinformation needed to fully implement the software V&V process,
- 2. Successfully execute new tests to complete the software V&V testing process. These tests include:
. New or modified tests that MGPl provided as updates to the DRMS documentation resulting from the software evaluation project
. New tests that SCE must develop to complete the software V&V process
- 3. Evaluate the DRMS algorithms and related software to determine if the SSOW performance criteria are adequate' met.
- 4. Audit the MGPl Software V&V Process to determine its adequacy for use on this DRMS project. This audit shallinclude a review of the intemal MGPl software development standards. The audit shallinclude the following activites:
. Verify the completeness of check lists per ANSI /ANS 10.4 e Review the V&V phase documentation, folders, and reports. This review must include a determination of requirements traceability documentation,in both a forward and reverse direction (reverse direction to include SDD to SRS at a minimum) e Review of MGPI's software life cycle configuration management process with special emphasis on maintenance and enhancement activities e Review of MGPI's program and procedures to satisfy 10CFR21 requirements for hardware and software e Verify that unused portions of the software cannot cause an adverse effect on the used software 48
SOFTWARE EVALUATION RiiPCRT D0cVMENT NO. 90400 REVislON 0
- 5. Develop a V&V Plan for the MASS software. This software was not included by MGPl as part of the DRMS software V&V plan and associated processes. SCE considers the MASS to be an integral part of the DRMS. Therefore, the MASS software must be analyzed by an approved software V&V program.
- 6. Ensure that administrative programs are in place E.t SONGS to control the modification of DU ar.d LPU parameters from the MASS.
- 7. Ensure that administrative programs are in place at SONGS to clear the DU trend memory whenever the DU is restarted after a period of downtime.
- 8. Ensure that SONGS users of the DRMS understand the method of data collection and averaging provided by each monitor.
- 9. Request that MGPl provide a schedule for the SV&V work associated with the installation and checkout phases of the project. In addition, MGPl must provide a schedule for the delivery of the SVVFR.
- 10. Compare SDD requirements to the supplied source code (high level comparison), and add new source code column to matrix.
- 11. Complete the project Requirements Traceability Matrix with the results of this audit. Update the matrix entries with new document references, new SCE test references, new MGPl test references etc. and remove all SEAR references to the matrix.
9.2 Recommendations for Overall System Maintainebility l The recommended tasks that SCE should complete in order to improve overall DRMS software maintainability are categorized as follows:
- 1. Restructure / rewrite the DRMS SRSs and SDDs to provide software information in a better organized format than the current documents. This work effort would result in " user-friendly" software maintenance documents.
- 2. Restructure / rewrite the DRMS STRs supplied by MGPl to add test configuration detail, specified acceptance criteria, and unambiguous test steps. These new tests would be repeatable and could be used for system validation after software modifications are implemented by SCE (or other) personnel.
- 3. Obtain Supplier Deviation Requests (SDR) from MGPl to document DRMS software deviations from the SPOW.
- 4. Validate the DRMS source code as supplied by MGPl to SCE against the installed and operable software. The supplied source code should be able to be built and verified that it completely matches the running software. The work should include the compilation of all source code using MGPl procedures, the production of new PROMS, and the comparison of the software on these PROMS'vith the software in the installed DRMS PROMS.
49
y, SOFTWARE EVALUATloN REPORT . DOCUMENT NO. 90400 REVISloN 0 L 8.3 Recovery Plan Appendix / provides a preliminary version of a plan to implement the recommendations diset. ed in Sections 8.1 and 8.2 This recovery plan was approved for implementation by Mike Wharton, Manager of NEDO, on May 13,1997. 50
f f)!7 SOFTWARE EVALUATION REPORT DOCUMENT No. 90400 REVisloN 0
- 9. LESSONS LEARNED The wo,k performer
- for the DRMS Software Evaluatico project has resulted in some general statements about how the issues and concerns identitled during the project po!!sibly could have been avoided. These Lessons Learned are summarized as follows:
1
- 1. Periodic oversight of cupplier's software development and software V&V processes should be performed in order to monitor a software vendor's work progress. Experienced persons (SOA, engineering, and maintenance) should visit development and V&V sites on some periodic basis (such as monthly) to gauge the vendor's progress, the quality of software code produced, and the quality of software documentation. This SCE group should ask specific detailed questions to let the vendor know that SCE is interested in the software development
} process and has certain high expectations for the end product. SCE should Trust but verify" the vendors software development and V&V processes. Problems identified early are much easier to resolve than those found later on in the software development cycle, r 2. From a Project Management perspective, take steps to ensure that all system requirements 3 (high-level and detailed) are adequately addressed in the vendor's software design, k development, and testing process, in the case of subcontractors or sub-vendors, require that the prime contractor provide evidence that the system requirements have been adequately conveyed to the subcontractor (s) and that the prime contractor has procedures in place to control the work progress and products of the subcontractor (s).
- 3. SCE should ensure that translated documents are thoroughly reviewed for correctness by Vendor Project Management prior to submittal to SCE.
51
SOFTWARE EVALUATION REPORT D3CUMENT NO. 90400 REVisl0N 0 I 1 I SOFTWARE EVALUATION REPORT APPENDICES 4 4
~
52
l l SOFTWARE EVALUAT!aN REPORT DCCU::ENT NO. 90400 REVISION 0 i TABLE OF CONTENTS
- i._ . . A.2 APPENDIX A.OPEN ITEM / SEAR RESOLUTION PROCEDURE
-- . . . B2 APPENDIX B. SOFTWARE DOCUMENTS- . .
...: -C2 APPENDIX C. SOITWARE PRODUCTS- _-.
.. D.2 APPENDIX D. 50FTWARE REQUIREMENTS
..E.2 APPENDIX E. TRACEABILITY MATRIX. . ... .
. . .. F.2 APPENDIX F. SOFTWARE EVALUATION ANOMALY REPORTS
SUMMARY
. ~. . . . G.2 APPEND 1X G . OPEN ITEM
SUMMARY
APPENDIX H. SEAR ACTION ITEMS ..._............H.2
- . .. . 12 APPENDIX 1. RECOVERY PLAN . - .
53
4 e APPENDIX A OPEN ITEM / SEAR RESOLUTION PROCEDURES A -1 i
SCFTWARE EVALUATION REPORT DOCUCENT NO. 90400 REVISICN 0 APPENDIX A - OPEN ITEM / SEAR RESOLUTION PROCEDURE OPEN ITEM R3 SOLUTION PROCEDURE whenever a noviewer wentw. en open hem ossue, eenc6ency, or probiom), the sonowing procedurei steps are tonoe.d a . . g .. r;, nJinJ ame , wgjej;d p j.jgist;@g e. jp;..s $ge; m, n ,3
- % <*[T-Y.67E. w.,.gu.4
, _ . ....%-Q.u, v u s W n/$ aegy W .vy9%o 9r ,M
@M.4G.977.w;QGw;5g.j G. y. ,,.tA..u.,G, q% g ,, j 5 b }*A
,, m, %e._ _p. ::,m : , _'
W f*gw g B._ m set;4.4;9ggn
..- ' .ze
. g % q,,, .., g*g+
- 1. The Open item 6s provioed to the adminstrator of the TAITS, and the Open hem is assgned an Aden hem sequence number.
1he Open hem 6s assigned to a Team member for resolution and closure. (23. The individual responsib6e for Achon hem closure comp 6etes an work required to resolve the Acton hem.
- 4. The responsib6e 6ndtvidual obtems Team agreement on Action hem closure. If the Team does not agree that the hem can be closed, the Open hem resoluten process retums to stop 3. Otherwise, the process proceeds to the nort step.
6 i The TAlTS record is now cAosed and the Action hem has been wT@;ed.. A .2
4 SDFTt'!ARE EVALUATlGN REPSRT r
! DSCU' DENT NO. 00400 REVl810N 0 1
i
- SEAR RESOLUTION PROCEDURE
Whenever a Reviewer identdles en anomey, a SEAR is created and the fonowirg procedural steps are fonowed to resolve the SEAR: i
- g i. - ..j.e
- 2
.c ;r % y c.4f n . . k,B ug..cy. ; p tmp%pL % %~l. p'".:~
s r.T .
'~, *,"
1
~ w ,. , 4.. yl%
,a ' 'l:
s.Qp. 4'c a -f3* T '. 'y M a. a&.I . &
.m c.4 ' . .
- 1. . The SEAR a prevaled to the admmistrator of the TAITS, and the SEAR is essagned en Acton hem esquence number.
, 2. A sepy of the SEAR a prweded to the MOPi repmeentetsve, along wth any supplementelinformaten ! a ~ that could neslet in the Eliscussion et resolutioP JI the SEAR.
- 3. Nant, the MOPl representouve snelyses the SEAR and provulos to the Revower a written response
! esideoneing the conoom(s) isonuAed in the SE,*,R.
- 4. Tle Revower then revows the MOPl toepense to detemune N the response is vossonable end seceptable
- 6. N the response e not -af* to the Revower, the Revower requests that the MOPi
! __. ; provide adenenelinformehon regartling the SEAR. l 6. If the MOPl representative egmes to pavede additionelInformaten regardmg the SEAR, the mooluuon pooses row poes teck to step 3. W the representspve dochree to prwide additenal bWormecon. the resoluten process proceeds to the nest stop.
- 7. The Revower now evoluetes the software anomaly and the MOPl response to agemst the followeg nine (9) artierie:
- Requise Operabluty Assosoment?
e Requires Source Code Evolueten? e Requires Document Changes? e Requires Testing?
+ Requies Analysis of Softwem? '
- e Requise Aude of Suppled Documents?
e Requires Admwntrouve controis? !' + Requires SDR? i e Requime NOO4.loonsing NotlAcetion? l 4. The roovies of this eyeiuoten are entomd by the Revower onto the SEAR form. Explanetens for
- each of the 9 ortierte em provided, along wth e *yes or no' enower to the questens. For et orMorte
! tated with a yes enewer, schone that should be taken to resolve the issue are provided.
- 9. The Revower oblems en todepenslent Revesw and Evolusten (IRE) on the SEAR from another l
l . evalusten Team member l 70 If there are comments generated by the IRE, the Revower then incorporates the comments into en updeled SEAR. Then the resoluuon process contmuss by retuming to shp 9. This work wiu be continued unta e5 IRE comments are incorporated into the SEAR.
- 11. Next, the Reviewer schedules a meetmg with members of the evolueten Team to perform a TEAM IRE on the SEAR. '
- 12. N there oro comments generated by the TEAM IRE, the 8teviewer then incorporotos the comments into en updated SEAR. Then the vosolution process contmuss by retuming to stop 11. This work 1
4edl be conhnued untd el TEAM comments are incorporated into the SEAR. - I 13. 11 the SEAR has boon evolueted and conisms Acton hems, the end6vuluel Acton hems are then edded to the TAITS. W there are no Action items, the resolubon process proceeds to stop it. ( After roosevmg TAITS task moord numbers for seoh of the SEAR Assen items, the Revenwor 14. upeetes the SEAR with the reconi nurrders it. -- The Revenwor now obtems the resolution signatures from the TEAM IRE partes. The SEAR Acton hems now wlE be trocked in TAfTS untN completen
- 16. VEn et the Achon hems are secocoted with a SEAR ere completed or there are no SEAR Acton Items, the Revtewer obtains the ' Action hems Congnete' signature and the ' Anomaly Closed
- l eignature (from the Team leader), and submits the SEAR for closure.
l t 7. The TAfTS record le now closed and the SEAR has been . _ ' A -3 l l
- . - - - - . . . . . - _ - - , - - - , . . - - - - - .- --. _ . . . . . . , - ~ . - . _ - , . . . . - - - -
2 t Sof tware Requirements Matrix Evaluation Trace cach requirement through SVVP, SOAP, SRSs, SDDs, STFs, STRs and SVVF Rs START I I I Issues /Denciencies/ Anomaly identified Problems identified Assernble SCE controlled 4 DRMs software " documentation and related Issuo SEAR project correspondence Add Action items to
=
i TAITS T Heview the 655W and decompose into SCE Add Action item to requirements for DT'Ms TAITS (ulegorire as functional, parf ormance, s ystem) 4
} PAGPl notified about Evaluate Anomaly /Responso Agains Using the software anomaly (SEAR) Each of the FollowinO items:
documents. determine columns for DRMs software Ny requirements matrix 1. Anomaly / Response requires PAGPl responds to operapy assessmend anomaly (SEAR) Yos o No a
- 2. Anomaly / Response requires sourco scE e alua . , , es ua re Q"
codo validation? YesO No O results in SEAR
- 3. Anomaly /Responso requires documo changes? Yes O No O MGPi r s onse Yes -> 4. Anomaly / Response rcquires testing?
Yeso No O
- 5. Anomaly / Response requires analynh
", of software? Yesa No O
' 6. Anomaly / Response requires audit of inform t$ n s o*rn yl supplied documents? YesO No O y
- 7. Anomaly / Response requires administrative controls?Yeso No O iG Pl agrees to provido No . 8. Anomaly / Response requires SDR7 Information? Yosa No O
\ 9. Anomaly / Response requires NOD /
Licensing notification? Yeso No O y,, _ ,
-v
.. . I i
M U SOUTIlERN CALIFORNIA M EDISON : An EDISON INTERNATIONAL Company
, Assign responsibility to close itern TITLE: Software Requirernents Matrix Evaluation l
__y DATE: 05/08/07 i 70t.po rTsiblo-~ ~ i
-> Individual cornr.tetes Action,1.teni i
No Tearn concurs I ,_ with closuro? e i' l' Close Open Iten) {
- IRE SEAR ANSTEC
+
APERTURE END r CARD i Yes l lite comments? O Avdable on ,t Aperture Card Updalo SE AR with anomaly / response results. Include No
~4- > reasoning in SEAR f or.i. ach --
itoni(Yea or No). For all
'Yes', list action to be taken Team IRE SEARS !
I Incorporato IRE comments 4 ye, TeamIRE ; comments? ' i ; No 4_ incorporate Team comments 4 Actb o > Close SEAR Yes v l-Add Actbi. nems Close TAITS to TAITS Closo record
~
4 Action Update SEAR with eS y TAfTS task record number ENO Obtain tesolution ; signatures -
. - ~ ~ . ~
9l A
* * * * * ~
w e %. , . Nwa+====e- w.
APPENDIX B SOFTWARE DOCUMENTS k B-1
sCFTCARE EVAt.UATION REPORT D0cV*'ENT ND. 90400 REVislCN 0 j APPENDlX B - SOFTWARE DOCUMENTS l SO1234061 81 RMS Software Quality Assurance Plan SO123-606 1-10 1 RMS System Software Requirements Specifications l SO123 606 1-15-1 Software Verification and Validation Plan SO123-606-1 16 2 LPU PIPS Software Requirements Specification S O123-806 1-17 3 LPU PIPS Parameter Table SO123-606-1 18-2 MASS Software Requirements Specification SO173-606-1-19 2 LPU SAS Software Requirements Specification SL 23-606138-0 Software Verification and Validation Tool Plan SO123-606 1 62-1 LPU/SAS Parameter Table SO123 606-1 63 2 LPU Parameter Table I S O123-606-1-64 1 Display Unit Parameter Table SO123-606-1-65 2 LPU Si Parameter Table S O123-606-1-66-1 SDU/lO Software Requirements Specifications S O123-606-1-67-1 Display Unit Software Requirements Specifications S O123-606-1-68-1 LPU Si Software Requirements Specification SO123-606-1-69 1 LPU/SAS Software Design Description SO123-606-1 70 1 LPU General SofNyare Requirements Specification SO123-606-1 75 3 User's Manual for MASS S O123-606-1-87-1 LPU I/O Software Design Description S O123-606-1-97-1 LPU/ PIPS Software Design Description SO123-606-1-98 1 DU General Software Design Description SO123-606-1-99 1 LPU/SAS Software Test File S0123-606-1 210 0 Software Used in LDU and LPU S O123-606-1-300-2 LPU/ PIPS Software Test Report - S O123-606-1-301 1 LPU Base Software Test Report S O123-606-1-302 1 LPU General Software Test File SO123-606-1 303-1 LPU/lO Software Test File SO123-606-1-304 2 LPU/ PIPS Software Test File S O123-606-1-305-1 LPU Application Software Test Report S O123-606-1-308 LPU/lO Parameter Table B2
SOFTWARE EVA1.UATION REPORT DOCUMENT NO. 90400 REVislGN 0 SO123 606 1 321 1 DU Software Test Report S O123-606 1-323-1 MASS Software Test File S O123 606 1 324-0 LPUISI Software Test Report SO123-606-1 325-0 LPUISAS Software Test Report S O123-606 1-328-1 LPU/lO SoftwareTest Report SO123-606 1 329 0 LPU/SI Software Test File SO123-606 1 330 1 LPU/ Application Software Test File SO123 606 1 331 1 RMS Algorithm Intarface Software Design Description S 0123-606-1 333-0 LPU/31 Software Design Description SO123-606-1 334 1 MASS Software Design Description S O123-606 1-339 1 MASS Software Test Report S O123 606 1-340 1 RMS Algorithm Interface Software Requirement Specification S O123-606-1 346-0 LPU General Software Design Description S O123 606-1 347-1 DU Software Test File S O123-606-1-357-0 Technical Manual for the ReLGIAd Algorithm S O123-606-1-363 0 Technical Manual for the Gas / Liq Algorithm S O123-606-1-365 0 Technical Manual for the Si Algorithm S O123-606-1 377-0 RMS Software in LPU and DU - Fax Information from MGPl S O123-606-1-378-0 RMS Software in LPU and DU/Line Numbers Fax information from MGPl S O123-606 1-379-0 DRMS System Integration Test Report S O123-606-1 380-0 DRMS System Integration Test File S 0123-6-6-1 381-0 DU Base Software Source Listing SO123-6-6-1-382-0 DU Software Source Listing S O123-6-6 1-383-0 LPU Base Softwara Source Listing S O123-6-6 1-384-0 LPU Si Software Source Listing S O123-6-6-1 385-0 LPU PIPS Software Source Listing S O123-6-6-1-386-0 LPU SAS Software Source Listing S O123-6-6-1 387-0 LPU 10 Software Source Listing B-3
i , j jI 'ii !l. l ll l' fj R1 s s s s s s o se s e e e e e e e s VF 1 Y Y l Y Y Y Y N t r Vw Y l l l l l e Sr l l l l l l m_ u s s s s s s o
- c. P1 s s ek ek ek e k e e k N ko o Vt e e Y o Y o Y o Y o V Y o D. Vw Y Y l l l l l t
n St l l l l l l l l e, r a P l s s se s e s e s e o P A s e e Y N ek Y Y Y Y Y O Y o S [
' l l
is s tun a a 4 4 4 4 4 4 4 4 Sm t lI 2- 1 1
- 4 2- 0 -
1 1 1 5 3 4 0 5 1 9 F o 0 0 2 2 0 2 3- , 2 3-3 3-T N 3- 3- 3- 3- 3-S n 1 1 1 1 1 1 1 u4 1 1 1 4 cu 1 6 3 1 6 4
- 1 6
1 6 M 6 2 6 g 0 6 i 6 u 4 2 0 v 0 A 70 et 2 3 0 A 40 0 0 4 0 pp 0 4 0 1 D0 43 AE t0 0 4 A - 4 3 A 1 C 0 342 As0 4B 0 3 00 43 S r-a 4 4B - 4 Et 3 2 7 0 2 8 0 - 29-3B 3 7 0 D 2 064 a 2 1 4 4 4 s D 2 E 93 Dw 2 3 5 0 D0-7 C 3 D 36 D 4 D 6 D 1 1 1 t 1 1 1 1 S 5 0
- =01 G O6 G 6 G OeG 00 G 01 G 1 1 S 06 S 4 P S 4 P G 06 G S 1 P S 4 P 'S 4 P S d P S 4 P S 1 P is s
tun s. 4 ko 4 ko k a a s 4 o k 4 o k 4 o k 4 o k 4 ok 4 o
^;
Sm t lI C 1 i t e 1 1 1 4 2- 1 1
- - 1 o 2 0 3 9 4 - 7 3 2
F W t 0 3 0 2 0 3-9 4 3- 3-
.a t
T n 3- 3- 3- 3- 9-S cN e 1 1 1 1 1 1 1 0 1 1 1 1
- 1 1
- 1 1 TO et n 6 4
6 3 e 6 5 6 2 6 8 6 1 6 7 6 5 RN pp e 0 2 0 4 0 A 21 0 4 0 2 0 2 0 3 0 A 30 Sna _ 4 CA0 4 A C 1 0 4 DA1 4 A 0 4C3 0 c 5 O C o 6 A1 9FA 000 4B 3 B 0 0 3 3 o 0 4 32 u00 3 0 3 Et 3 Ev 0 .o PI EC C D
; 2 aD 4 2- 1 3
6 D s 2 4 1 9 D 2 l 1 3 D4 2 4 1 3 6 D 0 2 1 oD 1 0 oeG 01 0 G P uD 2 22 D4 1 0 ocG 1 0 oG 1 S 0 mG 01 1 G O6 G RV m 3 e s P 03 5 4 P G s 5 1 P 3 s P S 4 P 3 . P o 3 a P 3 1 NE % OR /ss I T A4 0 0 t t un ae Sm 1 k o 1 k o m 1 k o 1 k o 1 k o 1 k o 1 k o 1 k o 4 U0 L9 lt B A . 0 1
- 0- 1 S
VO D D e o 6
- 1 3
1
- 3 1
- 2- 1
- 4 C
EC S f 4 3-3- 7 8-3 7 9-9 4 6 9-3 3- I L 1 3- A ET sm 1
- 4 6
- 1 1
1
- 1 0- 1 1
- 1 1
- 1 1
1 1-8 T RO ce t 6 6
]
0 4 4 6 0 A 9 1 6 5 4 6 0 6 2 6 9 6 6 0 7 2 5 I AE 0 u 4 A 0 0 0 & Sn 4A 0 48 1 10 4A0 4 A 1 4 A 0 4A1 NA 0 WZ Eam 3 2 B 00 3 3 C 0 3 G 0u 23 3E- 0 2 5B- 0 D Ts C 3 D 2 1 8 D O75 w 1 9 D 3 2 9 4 D4 2 B 5 0 8 D 0 - 2 1 7 4 8 D 2 99 D O1 1 8 D 0 1 2 D L O S 1 1 1 1 FC O15 G S 5 G 01 1 G S P O5 1 G O1 5 G 05 G 3 4 P 1 S 4 P 5 G O2 S 45 P G B OO S 4 P 4 P 1 S 4 P S 4 P t s SD #
/s s v e up k k k k k k k k e d t a a 1 1 o 1 o 1 o 1 o 1 o 1 o 1 o 1 o R a t ,
Sm - - m n
. o J t i
1 1 2- 2- 2- o a S o 0 1 1
- 0 1 1
1
- t h
c R 0 4 6 8 6 9 7 8 1 n N 1 - 6- P S A99 7 3- 6- 6- 1 1 1
- e tw et 1
6C0 0 9 u 1 6 1 1
- 1 6
1 9 1 6 1 6 1 6 1 1
- 1 6
1 8 1 6 1 7 7
- 1 6
1 7 o 1 6 1 0 0 e d G M v o po 6176 0 0 7 0 A 8 0 6 0 6 A 0 7 0 0 0 o R
- n.
Sna 3 5O 4 A 4C 0 4A0 4 A 0 4A E0 4A1 C 0 3 C 2 69G0 0 3- G00 Es 24G 321 0F8 3 0 3 0 00 3 F 4 4 0 3 2 2 w 3 2 4 0 E 0 F V t 2 8 -0 2 9 - 2 6 - - s ;F 4A6 C 2 V R V S 1 0 P O5 1 5 7 D 1 4 D 1 8 1 D 1 81 O 1 1 D 1 3 D 1 1 2 2 D u S F V 5 1 05 G 01 1 GP 05 G 05 G 05 G 05 3 4 P G 05 5 4 P G t a V S S 4 5 4 P 5 1 3 4 P 3 4 P 5 4 P t s V S v S m o R M . r R R R R R R R R R S D c s f R S ,S S S S S S S S S N C e p v ; N s S c s o m. d E e p e C S O s a S E f o C f h A B o N / 1 6 h S n N 2 2 . 3 4 5 9 c f a o 1 W 6 6 e 3 6 6 6 5 f 6 t o i S 5 5 5 6 5 5 5 0 5 h s s 6 m c h 5 o t a c x n m e s s s 4 .
. t e e te
~ o t o o
@ 5 :
n e n ne l. S S d e rr p : iy .v p A U S d d t e C A 0 8 S S S T E ** - - m 1 e y S k
/
c e U U
/
U U J A A T T O- o 7 s ts P P P P t P t P U - - i t y L L L L L L D M S N . 5 U S {fi
SCFTWARE EVALUATICN REPORT DOCUT. LENT N3. 90400 REVISION 0 4 l 4 i j 9 APPENDIX C SOFTWARE PRODUCTS 4 4 4 C-1
1 SOFTWARE EVALCATION REPORT DOCUME'.:T NO. 98400 REVISION O APPENDIX C -SOFTWARE PRODUCTS
@$ N d$$$ $ N N 7dd1 M N M Jxi((M 3=) M M d[fdh Y M Ni 2% .
LPU/ BASE ub N ib$h WMI M% [NN E M kkN E b SS2 E 110520 E LPU/SI-PIPS-SAS-lO
-o .
563 F 599 46680 F LPUISI t
)g2g LPUISI 564 G 6018 46685G LPU/ PIPS gl LPU/ PIPS LPUISAS 565 H 602 B 46700 H
.:a 4 6 LPUISAS
%AL LPUllO 631 B 648 A 111499B gg}g
- t. .,
LPUllO 560 C 110535 C LDU/RDU
% 665 DU/ BASE
.m s= LDU/RDU p= < DU/APPLI 5011 603 C 46707i
-- .s I
l C -2
SOFTWARE EVALCATION REPCRT DOCUMECT NO. 90499 REYtslON O _. b mmramumasi9e ' LPU/ BASE 46630 EA 45181 DA spRsteam 110520 E 46637 CA
- p 1 J 1
(SO1234%1-4
. - , _ _ , (SO123-606-1-302) (SO123406 (RMSSYS Q$ghipgg 346) cv.m..on) 301)
;U46179 CMii 110516G wynmwa@~sk.
X 8 0 h h,a.n l0 n1 (LPU Corrmon) m~,
'e ANkk'h. (LPU Bm) ki
. m,aw- m _h
)
C -3
.._i........_..........._
COFTWACE EVALUATION REPORT DOCUME".N NO. 90400 REVISION O wws w e re im
>:+ 9 ;'45180 wwwr FA "M 45504 FA 46631 DA
- mawmRe 45181 DA 110512 G em 46638 BA
- i t
3 (S O123-606-1-63) (S O123-606-1-330) (S O123-606-1-346) (RMSSYS (SO123-606-1-305)
%.%..%difMMQa ~ , .? cm..e 0 M d467 45506 CA 46633 CA 45759 AA
- 110516G y4 m 58 BA.* , .cw
-(9012N1 aw 5 a .,.
(SO123406-1-65) (S O123-606-1-329) (S O123-606-1-331) (LPU Cw....cs) 4 45185 BA 110519 H u,. [w5 e -e n-Y M.184F,AM"$V 148)p (S O123-606-1-333) (LPU Appli) _ m a
"%j:3[~Mifhx g
h n;$[.C '- 46679 F , _M. m-, (LPU SI) w g:ppf it @;M 'cl% Q $M4S/a;4;g g-${f-]{Q,"pjyp i I f I i i C -4 l
COFTWARE EVALCATION REPORT DOCC'MECT NO. 90400 REYlSION O 7
- w:a gys gr~ Q*;g ry g g+W ,% p%y +;.
w L 6n;$7A",AEttsimum_3%.9MSUM
^W: ~c y =+ / ,s 1 a :a :. . ~ c . .#PSWpg!MFC
~ -pae x- ::
gxdNn. ' TF'QNCM:i wh:en
&,M;MfML:Ng:..fy mwnwSxn;a:M 7$h.-Ufs@
6 % w w :fjd wrzmax+%% h CZff9PN$ n dm;::am:m udM M G@d $ w@ yt a-k~,; 7; -t&X==X #3== & :D: &- r ^= rest:
;j$R$ [ M" PARAhRuan% ;5Gr^-TW,tnG TEST % MI2 % SDO
- NNg$ 7;i4+
"VI " 0 1-M.gw gi.c 7 .jgg
[gn y ,
+$ M ; %
Sd cs% ;h%$gg[;2ilhj 3/hPgomw[pMdN
$+R iP-?N{pg,g3;USfJ
@Wl;i 4 %.3_ 7 gypp g::gg: AyS$$$p. Q: -
%Q w a 46631 DA
- 45181 DA 110512 G 46638 BA
- Wd45190 fay h 45504 FA 5M;.#womms;c%:
.,.~..e.0sNO)[
S.4 re . . . . (SO123-606-1-63) (S O123-606-1-330) (S O123-606-1-346) (RMSSYS (S O123-606-1-305) Common) p;.qy m .gg7-~ ,wp mW 110516G 46641 BA *
.si45768 BA *pF 45507 DA
- 46634 BA
- 45759 AA
- ps,7s xmyg (S O123-606-1-300)
(S O123-606-1-304) (S O123-606-1-331) (LPU Cuiininxi) 80123 .: 1,mem.8084-340); w~ . (SO123-606-1-17) 45187 AA
- 110519 H 6:45186 GA A-(LPU AppH) p(nMa;~'g;).,j tg.861,23405,1-16.,
- . ~
(S O123-606-1-97) 46695 G sc45179. gg p ~ CAA m
.P<.3-606-N,ym[
- k. (LPU P!PS)
,4.L-'
, 4;Q[-[2- (
_f_igh'T_'".I,1% 7@.'" x,._ QQ ' ll*& ])l Y
*s
SOFTWARE EVALCATION REPORT DOCUME"3 NO. 90499 REVISION 9 l i I l ' i . s I 3 w 45504 FA 46631 DA
- 45181 DA 110512 G 46638 BA
- 1._
j i (_ g= _
=
(SO123-606-1-63) (SO123 6 1-330) (S O123-606-1-346) (RMSSYS Common) , (SO1ZMm6-1-305) 46636 BA
- 45759 AA
- 110516 G 46643 C I' - 45511 DA
- jgpi g (1; (SO123-606-1-325)
" 4 ' ' $ j (SO123-606-1-62) (SO123-606-1-99) (SO123-806-1-331) (LPU Common)
~
45199 AA* 110519 H .
?gi - r' s
& ;. 1;w;14
.I . ~ _ _ , sk
, , . "- 46699 G
! TsW, ,C+ ,,944 a
ac_,_w_ ___t::j. .< : l (te u SA S)
"-AA-dM' 'D n
- ~ , . l I !
C -6 l l l
COFTWARE EVALC^ATION REPORT DOCUMEM NO. 99499 REVISION O i r i I messere inem rainstreia swa
>;i il i
^
- 45504 FA 46631 DA *
(SO123-606-1-330) 45181 DA (S O123-606-1-346) 110512 G (RMSSYS 46638 BA
- 123-606-1-305) i (S O123-606-1-63)
Co ...v6)
] 110516 G 111497 BA
- g 11492 BA 111496 BA 45759 AA*
(LPU Common) (S O123-606-1-328) l (S O123-606-1-308) (SO123-606-1-303) (S O123-606-1-331) ,
%m+r .caawcssie ~
111491 AA
- 110519 H gl:g,
}r __ n- _.-
(S O123-606-1-87) (LPU Appli) l i (LPU 0) j ~ j M 3% % : i p hswem mgg ag; g .; r-~m. & _ _ _ I i i i
! 4 l
1 ? 1 i J I C -7
i SOFTWARE EVALCATION REPORT DOCUMECT NO. 94499 REVISION O ; i i i I t i
--P--, -
. .r. . m,u- - - _ _ -
.n zzi 1.
9 ; tn;klD
$$Nai to
.e t
r '- e 45505 BA
- 46632 CA
- 45183 CA
- 110512 G 46639 DA
- n &vW 2.m (RMSSYS Common) {S O123-606-1-321) t 1._ap - 2_ (S O123-606-1-64) (SO123-606-1-347) (SO123-606-1-98) ,
i agMatanti I 110514 E ! (DU Common)
- _n .. --
110518 C j i 'T.~ )s?G@if.g d$8bY.I:Y$325 (DU Base) a- _ .--p ___. ~. _. ~__.- g g g ______= l l l insamerma l l l i i f C -8 t
SOFTWARE EVALC*ATION REPORT DOCUME'3T MO. 90499 CEVISION O p, yg_, e
,wmag, gw , = _ x p
%RKNGE$A@gyr_--[N4 fLWdP
+_
lateaut_i 57
~"
M N. 45505 BA
- dW551ME8EDM 46632 CA
- 4'i183 CA
- 110512 G 46639 DA *
(SO123406-1-98) (RMSSYS Cu.. .,on) (S O123-606-1-321) p (S O123-606-1-64) (S O123-606-1-347)
.w_; ,.g .ewgm .
110514 E 0 ig46179M. m C ...w 7,_omiis. ..
.[.e ' _ um 'v .:e 8
i _ b.
+9mN._3 Fann-me
,!ggal(gMWqg%'d4
- a. ceca C -9
- . ^ - . . . . - - . . . . . ._.
- _ . _ _ _ _ . - - - - - _ = _ - - . _ _ . _ _ _ - _ _ . - . _ - = _ . . - . . ~ . . . . . _ _ _ . . . .
SOFTWARE EVALUATION REPORT DOCUCENT NO. 90400 REVISION 0 APPENDIX D SOFTWARE REQUIREMENTS l 4 o., l
SOFTWARE EVALUATION REPORT l DOCUMENT NO. 90400 REVisl0N 0 4 APPENDIX D - SOFTWARE REQUIREMENTS 1.7.7 SOFTWARE REQUIREMENTS Th'3 section describes the software requirements for the DRMS, Due to the various design approaches used by system suppliers, it is not intended to list a!' software characteristics of the software supplied. The Supplier shall, however, provide all software necessary to satisfy the DRMS functional and performance requirements described in this scope of work. 1.7.7.1 General Characteristics The following paragraphs specify the required general characteristics applicable to all software ; pr;vided to support DRMS. 1 1.7.7.1.1[S1] The software provided shall comply with current industry standards produced by national or international organizations, such as IEEE, NRC, and ANSI. 1.7.7.1.2[52] Au software shall accommodate the potential DRMS growth as defined in the Supplier Scope of Work. Radiation monitors may be added to or removed from
' the configuration without requiring re assembly or recompilation of the sonware.
1.7.7.1.3 [S3] All appilcation software shall be modular to minimize the time and complexity involved in making changes to any programs. The modularity required shall be as follows: 1.7.7.1.3.1 Hardware interface modules shall be separate from other software modules. 1.7.7.1.3.2 Logic and data shall be organized as distinct modules. 1.7.7.1.3.3 Communication among programs for data or program control shall be symbolic rather than absolute so that all programs are essentially independent units. 1.7.7.1.3.4 Each program, subroutine, or function module shall be designed with one entrance, one normal exit, and an error exit, consistent with structured programming. 1.7.7.1.4 [S4] The software shall be completely maintainable by Edison personnel using the software services and the documentation provided with the DRMS. No Suppiler support shall be necessary. All tools used to develop and maintain the software shall be delivered with the DRMS. D -2
s0FTWARE EVAL.UATioN REPORT - DOCUMENT No. 90400 Revision 0 - 1.7.7.1.5 [S5] All sokware shall conform to codin2 standards as ref;rsnced in this dccument. The Supplier shall enforce coding standards for all Supplier-produced software and custom DRMS software supplied by its subcontractors. 1.7.7.2 [S6] Software Source Code Management Tha Project software implemen% tion shall include formal procedures for management of all program sturce ende used in the Project. From the beginning of the software implementation, an on-line source code management directory shall be provided for maintaining a history of all revisions to all proj2ct programs. This directory shall assist in the orderly control of the revision process. The Supplier shall ensure that the directory is properly maintained and is current throughout the dsy:lopment phase of the project. Authors of proposed program revisions shall be able to make sntries into the directory from processor workstations, if the program revisions are accepted after r; view by the lead programmer, they will be kept in the directory, if the revisions are rejected, they will be removed. The following information shall be incorporated into the directory: 1.7.7.2.1 The full name, abbreviated name, and a short functional description of the program. 1.7.7.2.2 Other programs used by this program. 1.7.7.2,3 Other programs using this program. 1.7.7.2.4 Program author, Tha current and all previous revision levels back to and including the revision level at the time this program was first installed in the DRMS. Revision information shall include the revision number and 4 date, revision author, and a short but informative description of the revision. 1.7.7.2.5 [S7] Programming Languages Tht. computer programming languages provided by the Supplier shall include a high-level language End, if necessary, assembly language. The application functions programmed shall be easily transportable to other Edison-owned computer system and workstations using the same standard language. Hardware platform independence, device-independent input / output servers, and - prcductivity enhancements shall be provided. The applications shall be written in Edison-approved industry standard programming languages such as Pascal or C and shall run under industry standard operating systems.- High-levellanguages shall be utilized whenever possible, if the C programming language is utilized, it shall comply with ANSI Standard X3.159-1989 (Ref ). The use of C is . prsferred because of its portability. The Supplier's use of assembly language shall be restricted to time-critical or hardware device-handling applications. D -3 D
SOFTWARE EVALUATION REPORT DOCUMENT No. 90400 Revision 0 1.7.7.2.6 [S8] System Level Software The system-level software shall include a real-time operating system and device input / output controi modules. The real-time operating system shall be device-interrupt driven and software event-driven cnd respond to demands for service resulting from an event in the system or from a user. The cperating system shall be able to assign resources and process simultaneous events according to priority levels, both dynamically assigned and those fixed by user definition. The Operating system shall provide access to executive services by the programming language. 1.7.7.2.7 [S9] Date Time Funt; tion Th3 time of day and date shall be maintained for use by other software. The time of the day shall be
- m:intained in military times in hours, minutes, and seconds. The date shall be maintained as month, day, and year. Leap years and century rollover shall be recognized. Manual adjustments for the time changeovers between standard and daylight saving time on system reports, hourly files, and eth;r time-oriented functions shall be made, accommodating 23-hour and 25-hour days.- The programmer or other authorized user shall be able to alter the system time and date.
1.7.7.2.8 [S10] Network Software Tha DRMS software shall provide interface ports that allow for providing DRMS data to the DAS. These interfaces shall include both a standard serial RG232 type interface alon0 with an RS485 intsrface. 1.7.7.3 [Sii) Database and Database Management [S11A] A database shall be provided that contains all structure definitions and data for the functional requirements of the channel. The channel shall be provided with consistent coordinated procedures to manage this database. The database shall include all data required by the data acquisition and user interface functions provided by the Supplier. The database can be modified such as security access passwords, (passwords are used to allow selected personnel, such as maintenance and operations to make changes) by selecting the appropriate options and entering the required information when prompted. 1.7.7.3.1[S11B] All real-time scanned or calculated data, and other monitored system data, such-as device status, shall be identified in the database by symbolic point names when the database points are defined. All subsequent references to any point shall be by use of these symbolic references. This applies to database linkages used for reports, displays, and application programs. Each database point name shall be unique. D -4
SOFTWARE EVALUATION REPORT D@CUMENT No. 90400 Revision 0 1.7.7.3.2 [S11C) A database manager shall be provided that controls the generation, modification, access to, and retrieval from all the data structures in the database. The database manager shall define the structure of the database; locate, sort, retrieve, update, insert, and delete; ensure data integrity; provide a common interface for all applications that use the database; provide a user interface for all applications that use the database; provide a user interface for workstations and/or processor terminals; and provide for backup and recovery of database files. The database manager shall be capable of generating and modifying all channel data by interfacing with all database structures. Execution of the database manager shall not interfere with the on-line functions of the channel,
' including the normal updating of the real-time database. Database generation and editing shall operate interactively, using full-screen entry displays that shall permit multiple database entries. Data entry validation checks shall be made to filter out initial data entry errors. When errors that cannot be detected at data entry time are encountered during later stages of database mainienance, the database management software shall flag and reject the error, but attempt to continue processing the database in an effort to detect all existing errors before stopping. The user shall not be required to re-enter data not cauung an error, whether entered before or after data causing the error (s).
1.7.7.3.3 [S11D) The user shall be guided to enter new data or confirm existing data. All required entries for any database item selected for changes shall be presen'.ad to the user. The database manager shall be hierarchical such that when parameters are entered that require other parameters to be specified, the additional queries, prompts, and display areas required to define the additional parameters shall be automatically presented. 1.7.7.3.4 [S11E) Audit trailinformation denoting the database change information shall be included within the Event Log file. 1.7.7.4 [S12] Diagnostics and Software Utilities Diagnostics shall be provided for testing the hardware components in the proposed configuration. This hardware includes processor, memory, peripherals, user interface hardware. D-5
s3FTWARE EVAL.UATioN REPORT D3CUMENT No. 90400 REVisl3N 0 1.6.1 GENERAL DESIGN CRITERIA The following general design criteria apply to the digital radiation monitoring / sampling system. 1.6.1.4 [F1) The radiation monitoring / sampling system is to be designed so it can be checked on a daily basis, tested periodically, and recalibrated during refueling shutdowns, or as system operation may require. 1.6.1.5 [F2) A remotely operated long half-life NIST traceable radiation check source will be furnished, if appropriate, in each char,nel. The energy emission ranges are to be similar to the radiation energy spectm being monitored. The source strength is to be sufficient to cause a response approximately one decade above background. Electronic channel check source functions will be used where appropriate. 1.6.1.7 [F3) Radiation monitoring equipment shall incorporate High, High-High, fail alarms, continuous indication and trending information with the exception of the wireless area monitors. All audible alarms shall have a tone that sounds in the middle of the human speech range (not to exceed 90 db at 3'), where the alarm is located. 1.6.1.10 [F4) The alarm setpoints for each channel shall be adjustable over the entire range of the channel. 1.6.1.14 [F5] Each Safety-Related and non-safety-related channel shall be capable of performing automatic, continuous, and stand alone operation in the event that all communication links with the associated DAS are lost or local control is deliberately taken. This capability shallinclude: 1.6.1.14.1 [F5A) [P1) Continuous acquisition and storage of radiation parameter data and any other information normally stored within the field unit microprocessor, who exception of the wireless area monitor. Data storage capacity for this purpose shall provide for complete storage, with no overflow or loss of data, of at least the preceding - twenty-four 10 minute averages, twenty-four hourly averages, and thirty-one daily averages, of radiation level and the complete files of critical parameters for all channels within the FU. 1.6.1.14.2 [F5B) Continuous control of all Field Unit (FU) functions normally controlled by the LPU including the automatic controls as specified in Appendix B of this Scope of Work. D -6
SOFTWARE EVALUATION REPORT DOCUMENT No. 90400 REVisloN 0 1.6.1.15 [F6) Communication ports shall be provided where a Portable Maintenance Computer Subsystem can be attached for complete local operation of DAS functions. 1.6.1.17.6 [F7] Occurrence of any random single failure in a DAS or FU shall be annunciated and indicated on the operable DCU display (s) and logged on the unit event
- recorder.
1.6.1.21 [F8) [P2] The FU shall perform all of the real time control, data acquisition, display, and short term storage functions of the DRMS, Data shall be eutomathally transferred to the DAS periodically, on a real time basis, for long term storage and report generation. Non-processed radiation data will be collected for all DRMS monitors and sent to the DAS computer systwi within 6 seconds with the exception of the wireless area monitor which is 40 seconds or less. The central building blocks of the DRMS shall be microprocessors, 1.6.2.3 [P3) Minimum Sensitivity Sensitivity is the minimum detectable activity / concentration for the specified isotope that the detector is capable of detecting and measuring with the statistical confidence level of 95 percent for all liquid process and gaseous monitors and 95 percent for all airbome iodine and particulate channels. The minimum sensitivity requirements shall be specified in terms of the following parameters: 1.6.2.3.1 Activity concentration in microcurie per milliliter of sample at standard temperature and pressure (STP). 1.6.2.3.2 The control isotope, for which the monitor is calibrated, and for which it must be able to detect the minimum concentration. 1.6.2.3.3 The background radiation level in which the monitor must detect the minimum activity / detectable concentration, with an extemal background radiation field of 2.5 mR/hr (Cs-137). 1.6.2.3.4 The minimum statistical accuracy and confidence level for which the minimum activity concentration is detected for process channels shall be displayed as activity concentration level, accurate to within *25 percent of the actual steady state activity concentration level present at the active window of the detector given sufficient time for statistical accuracy. D 7
SOFTWARE EVALUATION REPORT DOCUMENT No. 90400 Revision 0 1.6.2.3.5 [P4) Minimum Channel Response Time 1.6.2.3.5.1 For the Reactor Coolant System leak detection radiation monitors response time shall be 1 GPM within i hour to allow for compliance with NRC Regulatory Guide 1.45 (Ref ). 1.6.2.3.5.2 [P5] Accuracy (Liquid and Gaseous Channels) 1.6.2.3.5.2.1 The overall accuracy of each channel with recpect to the actual steady state activity concentration shall be within 125 percent. 1.7.1.3.4 [F9) Smart 1/0 devices shall be used to isolate safety related General Atomics /Sorrento Electronics equipment from the DAS. The Smart 1/O (LPUllO) shall be an interface device that converts analog and discrete inputs into a RS485 data link. The LPU/lO will accept up to eight (8) 4 - 20 thA analog signals and up to eight (8) digital inputs. The output shall conform to RS485 DRMS protocol. This device shall be safety related quality class 11, seismic category 1. 1,7.4.5 [F10] Control room visual high radiation level alarm indications, actuated by a high level trip on any channel, shall be provided by the Supplier. This indication will be provided for each unit on a Display and Control Unit located in the common control room panel 2/3 CR066. All DRMS alarm outputs that are on the DAS, will drive the main control room annunciator via a relay contact output from the primary and secondary SCADA NODE RTP I/O chassis. All General Atomics (GA) and MGPl radiation monitors which annunciators in the control room will have their annunciation driven by DAS. This includes all Safety Related and Non Safety Related MGPl monitors installed by DCP 6926, and all GA monitors located in panels 2L405 and 3L405. There will be ten DAS driven Unit 2 annunciator windows associated with Unit 2 and Common monitors. There will be seven DAS driven Unit 3 annunciator windows associated with Unit 3 and Common monitors. Indication ar.d control will also be located at the Control Room DRMS cabinets in the Control Room hallway. 1.7.4.6[F11][P6] Each DRMS radiation channel shall be of a non-saturating design and will indicate actual radiation levels in the range from its normal design range upper limit to a level 100 times this upper design limit. Exception is noted in the wireless area monitor, which are 10 times the upper design limits. 1.7.4.7 [F12] Local sample flow indication and high and low sample flow alarms, and the channel failure alarms which actuate local alarms shall be provided by the Supplier. D -8
SOFTWARE EVAt.UATION REPORT DOCUMENT NO. 90400 REVisl0N 0 1.11.2 FUNCTIONAL REQUIREMENTS The functional performance requirements for the radiation monitoring systems are to: Wam of radiation health hazard to operating personnel. 1.11.2.1 [F13] 1,11.2.2 [F14] Monitor the amount of radioactivity released in effluent. 1.11.2.3 [F15] Provide alarms for operators and/or automatically isolate lines containing liquid or gaseous activity when the activity level reaches a preset limit. 1.11.2.4 [F16] - Provide CRT displays and retain information necessary to manage the amount of radioactivity released from the plant for up to thirty-one (31) days. 1.11.2.5 [F17] Monitor for leakage of radioactivity in normally non-radioactive systems, and specifically for fuel element failure, primary to secondary leakage, and primary to - atmosphere leakage. 1.11.2.6 [F18] Provide specific engineered safety feature actuation signal (ESFAS) control 4
' functions for containment purge isolation, fuel Hand!ing building essential ventilation actuation, and control room essential filtration.
1.11.2.7 [F19] Monitor performance of processing equipment. 1.11.2.8 [F20] Provide suitable activity level information for computer processing with meteorological data for atmosphere release calculations. 1.11.3 CONFIGURATION The Digital Radiation Monitoring System, (DRMS), is compo:od of three major subsystems; Unit 2 DRMS, Common 2/3 DRMS and Unit 3 DRMS. Each major subsystem is composed of two subsystems, the Data Acquisition Subsystem (DAS) and the Field Unit (FU). The DAS consists of the CRT display, mass storage device, event recorder, communication loops to the various FUs and the network interface. The FUs shall be either Quality Affecting or Safety Related for Units 2/3. The FUs consist of, Radiation Detection Unit (RU), and Remote Display Unit (RDU). The radiation monitoring / sampling system is an integral part of the radiation protection program, it consists of four basic categories of permanently installed monitors: 1) Process,2) Effluent, 3) Area, and 4) Post Accident radiation monitors. A radiation monitor can be classified in more Wian one of these categories depending on its functional requirements. i D -9
sSTWARE EVALUATION REPORT - DOCUMENT No. 90400 Revision 0 1.11.3.1 [F21] Each FU shall provide the required inputs to the DAS and PMCs to allow the functions specified in Appendix B of the Supplier Scope of Work. 1.11.3.2 [F22A] - The RDUs shall display all monitor parameters, control these parameters, and control the FU functions. The RDUs are located in the control room hallway cabinets. [F22B] Parameter changes to the Safety-Related FUs shall not be alterable by DAS download. The RU is the skid and consists of main sub-components: the detector assembly, sample flow controllers, sampling system, and the flowrate meter. 1.11.3.3 [F23) The LPU, a single channel unit, is used by the FU to interpret the data collected by the detector. Each RDU receives messages from the LPU or LDU except for 7808 whose LDU receives input from 2 LPUs, These signals include, but are not limited to, radiation leve's from radlation detectors, equipment status's such as pump on or off, channel check activation, detector failure or saturation indication, high voltage failure, high or low flow conditions, and filter failures. Each RDU sends data to the DAS for indicating FU status while the LPU stores radiation activity. The LDU, and RDU interface with the PMCs in a similar functional manner as the DAS acquisition and control functions when a PMCs is connected to the LPU, LDU, or RDU. The RDU sends output signals to control FU equipment and functions. .1.11.3.4 [F24) The FU shall include microprocessor (s), PMCs receptacle (s), and other equipment necessary to receive the signals from the LDU or RDU and - communicate them to the associated DAS. 1.11.3.5 [F25A] The LDU and the RDU have the capability to display parameters, to control these parameters, and to control field functions. Parameter changes to the LPU shall be made by DCU download (non-safety related) after local contrcl is tuma off, then the FU is put back into service with the original parameters stored in ine DAS. [F25B) Each channel shall have two input / Output Interfaces (101). The IOls are the isolation devices from the safety-related FU and the Non-Safety Related DAS. The input / Output Interface device shall be capable of transmitting the output through a twisted shielded pair (TSP) cable length of a minimum of 1000 ft. The input / Output Interface shall provide for the DAS communication loops connections. D - 10
sCFTWARE EVALUATION REPCRT DOCUMENT No. 90400 REVIStoN 0 1.11.3.6 [F26) Each channel shall provide hard copy capability of all monitor radiation levels. 1.11.3.7 [F27] The following five output control signals from the RDU shall be available to the EDISON supplied ESFAS equipment (HI Radiation Level and Channel Operate / Failure shall be wired to the Booster relay and the required contacts from the Booster are to be wired to the terminal board): 1.11.3.7.1 HIGH-HIGH RADIATION LEVEL 1.11.3.7.2 HIGH RADIATION LEVEL 1.11.3.7.3 ALERT RADIATION LEVEL 1.11.3.7.4 CHANNEL OPERATE / FAILURE 1.11.3.7.5 CHANNEL TEST 1.11.3.8 [F28) POWER FAILURE AND RECOVERY MODES in order to protect data normally stored in the field unit microprocessors, minimize system downtime f llowing power failure, and to minimize the impact of power failures on the real time performance, each channel shall meet the following requirements: 1.11.3.8.1 [F28A] Loss of power shall result in an actuation of the channel affected with the exception of the wireless area monitors. 1.11.3.8.2 [F288) Voltage drops to 0 Volts for a period of up to 150 milliseconds shall not affect the performance of the item in any manner. The wireless area monitors are not subject to this functional requirement. 1.11.3.8.3 [F28C) For short term, less than four hours, sustained loss of all Edison Representative power to a FU, DAS or PMCS microprocessor the affected microprocessor shall: 1.11.3.8.3.1 Sense the loss of power and conduct an orderly shut down, with the exception of the wireless area monitors. 1.11.3.8.3.2 [F28D) Upon restoration of power, restart immediately and automatically, and function in accordance with the requirements of Section, without loss of any data stored in the memory at the time of power loss. D - 11
SOFTWARE kVAluATION REPORT DOCUMENT No. 90400 REVisloN 0 1.11.3.8.4 [F28E] For long term (four hours or greater) sustained loss of all Edison Representative supplied power, loss of data stored in the read write memory is permitted. For field unit microprocessor, sufficient programs shall be located in the (read only memory) non volatile circuits, so that, upon subsequent restoration of power, - recovery to full functional status can be effected, either remotely at the associated unit, or, if local control is taken, at the field unit itself using a PMC unit. For the microprocessors, sufficient programs shall be located in the read-only memory circuits so that upon subsequent restoration of power, recovery to full functional status is automatic, by rebooting. 1.11.3.9 [F29A] The PMCs shall be a TOSHIBA T1950CT laptop computer with an Active-Matrix Color VGA display, internal 210 MB Hard Drive, internal 8 MB of RAM or equivslent computer. The unit shallin-'ude sufficient hardware and software to perform all DAS functions when plugged into communication port. 1.11.3.9.1 [F291Q The PMCs shall be able to request and receive indication of the currently stored value of any critical parameter or radiation level information, for any channel operated by the connected microprocessor. 1.11.3.9.2 [F29C) The DAS shall receive the same information as displayed on the locally connected PMCs. 1.11,4 [F30) DETECTION CAPABILITY The RU process channels shall have the capability to detect and display radiation levels over a minimum of five decade range. The lower boundary of which shall be the required minimum dstectable activity / concentration, or sensitivity for each channel. DRMS area channels shall detect cnd display radiation levels, over the specified design range. Detection and display capability at levels above and below these ranges shall be provided to the extent practicable, without significant increase in price. 1.11.4.1 Required minimum detectable levels for all process channels shall be detected under sample conditions of standard temperature and pressure. 1.11.4.2 Required minimum detectable levels for all process channels shall be detected in the presence of a Cesium 137 extemal radiation field of a level specified for each process channel. 1.11.4.3 All detectors shall be designed to detect radiation au Jities, with lead shielding as applicable, at the steady state level specified in Sections and 1.13 in a 2.5 mR/hr (Cs-137) extemal field. D - 12
SOFTWARE EVALUATION REPORT DOCUMENT NO. 90400 REVislCN C 1.11.4.4 [P7] Required minimum detectable levels for all process channels shall be detected at a minimum statistical confidence f avel above background of 95 percent. 1.11.5 SYSTEM RESPONSE TIME 1.11.5.2 [P8] For liquid and gas channels, the time delay between actual introduction of the required minimum detectable level (5x10-6 pCl/cc) of activity concentration to the sampler and the start of a remote display and/or local indication of this changing level shall be one (1) minute or less. 1.11.5.3 [P9] For Particulate and 1-131 channels, the time delay between actual introduction of the required minimum detectable level of activity concentration to the sampler and remote display and/or local indication of this level shall be fifteen (15) minutes or less. 1.11.5.4 [P10] Response time of every channel shall be approximately inversely proportional to actual radiation level at the detector, for levels greater than the required minimum detectable concentration / activity. 1.11.6 SYSTEM ACCURACY 1.11.6.2 [P11] For process channels, displayed activity concentration level shall be accurate to within i 25 percent of the actual steady state concentration level present in the sampler through the range specified in, active window of the detector. 1.11,6.3 [P12] The DRMS radiation channel shall be of a non-saturating design so that it indicates a level higher than its normal design range upper limit when exposed to a radiation Level up to 100 times this limit. With the exception of the wireless area monitors which are 10 times the upper design range limit. -1.11.7 SAMPLING ASSEMBLY SUB-SYSTEM 1.11.7.11.4 [F31] Airflow and filter feed alarms. 1.11.7.11.8 [F32] The particulate monitor sample flow shall be maintained within the normally expected range of filter paper differential pressure by an automatic control system. Local flow indication, and high and low flow alarm signals shall be provided. These signals actuate local alarms and the channel failure alarm. 1.11.7.11.9 [F33] A flow-integrating elapsed sample volume indicator shall be provided downstream of each particulate and/or iodine channel. It shall have a local digital readout and be re-setable to zero. D - 13
sCFTWARE EVALUATION REPORT D3CUMENT No. 90400 REVisloN 0 1.11.7.11.16 [F34] The particulate monitor sample flow shall be maintained in the normally expected range of filter paper differential pressure by an automatic control system. Local flow indication and high and low flow alarm signals shall be provided. These signals shall actuate local alarms and the channel failure alarm. 1.11.7.11.17 [F35] A flow-integrating elapsed sample volume indicator shall be provided
- downstream of each particulate and 1-131 sampler. It shall have a local digital readout and be resetable to zero.
1.11.9 [F36] PROCESS AND SAMPLE FLOW METERING The RU shall provide flow indication of the sample flow where applicable. D - 14
SOFTWARE EVALUATI@N REPORT DOCUMENT NO. 90400 REVISION 0 APPENDIX E . TRACEABILITY MATRIX 9 e E -1 s - - _ _ . - -
SDFTWARE EVALUATISN REPORT D3CUMENT NO. 90400 REVISION 0 APPENDIX E - TRACEABILITY MATRIX See Volume 2 4 E -2 ( _ - - - - - - -
SOFTWARE EVALUATION REPORT DOCUMENT NO. 90400 REVislON O APPENDIX F SOFTWARE EVALUATION ANOMALY REPORTS
SUMMARY
s F- 1
SOFTWARE EVALUATION REPORT DOCUMENT NO. 90400 REVISION 0 APPENDIX F - SOFTWARE EVALUATION ANOMALY REPORTS
SUMMARY
SEAR Descrtpuon Status Action item (s) Acuon item Number Required? Number (s)
- 1. MICROTECH "C' Closed Nr et
- 2. Edson Approved industry closed None Standard Programming Language
- 3. 'Real Time' Measurements SCE Actions DCNs to System SRS.
LPU General SDD. and DU SDD SCE request that MGPl submit SDR on auto transfer to DAS SCE request that MGPl submit SDR on Industry standard RT OS
- 4. DRMS Growth Documentaten SCE Actions DCN to System SRS to Requirement as Described in include SCE data on Supplier Scope of Work DRMS growth and reconfiguration
- 6. -Softwarc Toots for Mamunance' SCE Acuons SCE request info from Requirement MGPl Atlanta on how maintainability was addressed in software development process.
Obtain tools / code from MGP1
- 6. SSOW Requwement for SCE Actions SCE run DAS-DRMS Collection of Non-processed response time test Radiation Data SCE request that MGPl submit SDR explaining deviation
- 7. SSOW Suppher Devoton SCE Acuons SCE request SDR Requests
- 8. Trendmg Informaton SCE Actions DCN to DU SDD Requirement as identfed in the SOW
- 9. Trendmg informaton Closed None Testeg/ Evaluation in Software Test Files / Test Reports
- 10. Testing /Evaluaten for Alarm Closed None Management SEAR Desertpuon Status Action item (s) Action item Number Required? Numberts)
- 11. LPU/ Common SDD Functonal SCE Actions DCN against LPU Requirement General SDD
- 12. Detection of Power Fadures Closed None (LPU/ Common SDD)
- 13. LPU/ Common SDD Functon Closed None Requirements as Described in LPU/ Common SDD F- 2
S$FTWARE EVALUATIDN REPORT D3CUMENT NO. 90400 REVISION 0 SEAR Description Status Action item (s) Action item Number Required? Number (s) 14 Power Suppty, Temperature Closed None Montoring Requirements Mesing In the LPWCommon SDD ~
- 15. Montonng Running of Program Closed None Functional Requirements Mesing in the LPU/ Common SDD it. SenalImk Checking not included SCE Actions DCN against LPU in LPUR.ommon SDD, Missing General SDD Test Reports DCN against DU SDD 17, Acquenion Faut Management SCE Actions DCN against LPU/SAS not included in the SRS LPU/ Common SDD, Masing Test Reports DCN against LPU/SAS SDD DCN against LPU/SAS STR DCN against LPU/SAS PT DCN against LPU/Si SDD DCN against LPU/Si PT DCN against LPU/ PIPS SDD DCN against LPU/ PIPS PT SCE run new tests described in revised LPU/SAS STR
- 18. MonNonng Processor Load not Closed None included in the LPU/ Common SDD, Masing Test Reports
- 19. DU Software Requuements SCE Actions DCN to DU SRS Specsfication as it relates to Document 5
- 20. SEAR s's 11,12,14,15,16,17 Closed None and 18 _ _ _
F- 3
SOFTWARE EVALUATICN REP 3RT D3CU"ENT NO. 90400 REVISION 0 SEAR Descrtpuon Status Atuon item (s) AcDon item Number Required? Numberts)
- 21. Perfornance Requirements by SCE Actions SCE evaluate Vendor as they relate to Minimum operability of effected Sensitivtry monitors that are scheduled for tumover SCE perform analysis of algorithms and software to determine if requirement is met After evaluation and testing, SCE evaluate need to update documents and update as required SCE write and perform tests proving regtis met
- 22. Performance Requwernents by SCE Act60ns SCE evaluate Vendor as they relate to operability of affected
- Minimum Channel Response monitors that are Time" scheduled for tumover SCE perform analysis of algorithms and software to determine if requirement is met After evaluation and testing, SCE evaluate need to update documents and update as required SCE write and perform tests proving regtis met
.c F- 4
SOFTWARE EVALUATIBN REPORT DOCUMENT NO. 90400 REVl813N 0 SEAR Descripuon Status Act60n hom(s) Act6on item Number Required? Numberts)
- 23. Performance Requwements by SCE Actions SCE evaluate -,
Vendor as they relate to operability of aNocted
'Accurscy (Liquid and Caseous monitors that are '
Channels) scheduled for turnover SCE perform analysis of algorfthms and
- software to determine if requirement is met After evolustion and testing SCE evaluate need to update documents and update as voquired SCE wette and perform tests proving togt is met
- 24. Definmon of RAD LEVEL Aange SC' : .t6ons SCE evoluete Functon and Performance operability of aNected monitors that are scheduled for turnover SCE perform analysis of algorithms and software to determine if foquirement is met After evaluation and testing, SCE evaluate need to update documents and update as required SCE write and perform tests proving togt is met
- 26. Clarthcaton of UODBUS SC3 Actions DCN against System Protocol SRS
- 24. Missing Document 45355, Senal SCE Actions DCN against DU SRS Links Names
- 27. System Queck Operabilty Test's Closed None Function Desenption 24, Acronym Lwnnitions SCE Accons DCN against DU SOD
- 29. Contraccton/Duphcaten of Closed None Modu'es in System Software and Appication Software
- 30. Output Emuisten Mode SCE Actions DCN against System Requirement SRS F. 5
SCFTWARE EVALUAHON REPORT D3CUMENT N3. 90400 REVISISN 0 SEAR Descriphon Status Ac")? 'tdin(s) Action item Number Reovirt,d? Number (s)
- 31. DRMS System SRS Securdy SCE Actioen DCN ogehst System Accese Passwords SRS at RTM Desgnator F8, P2 1,CE Actions DCN to DU SRS Meche:Am to show Mesing Data in Histoncal File DCN to DU STF DCN to DU STR SCE tun new DU tests DC'se to LPU/Appi STF DCN to LPUIAppi STR DCN to LPU/Appi STR
- 33. $11D-Database User interface SCE Actions DCN Against System Required Functions SRS Implementaten into DRMS System SRS .
- 34. 311E Defintons of the SCE Actions DCN Against System Parameter Table Fields SRS Supplier Deviation Report Evaluation of Procedures
- 36. RTM Daegnator F1 Swachmg SCE Achons investigate reworking DU into Maintenance doce to bring up to SCE standards
- St. RMS St-update of Document SCE Actions Evaluate MOP 1 Doc References and Audt of References Software Development Process DCNs against many Docs Audit MOPI S/W Dev Process
- 37. RTM Desgnator F1-LPU Test SCE Actions DCN against LPU File Reference of LPU lock up in General SRS Maintenance Mode
- 34. RTM Designator F1-Du Swach SCE Actions DCN against DU SRS to Maintenance Mode DCN age!nst DU SDD St. RTM Designator F1. Test 2 of SCE Achons DCN against Du STF DU Software Test Report DCN against DU STR SCE run new DU tests
- 40. RTM Designator F1-System SCE Actions DCN against LPU Quick Operstey Tests General SRS
- 41. RTM Designator f1 Secuon SCE Actions DCN against DU SRS
- 2,11 of the DU Software Test File DCN against DU STF DCN against DU STR SCE run new DU tests
- 42. RTM Desgnator F1 Switching a SCE Actions DCN against LPUAppi LPU from Normalto STF Maintenance Mode (Test File)
F- 6
SCFTWARE EVALUATION REPCRT DOCUMENT NO. 90400 REvlsiCN. O SSAR C:: m :- Status Action item (s) Ac#on Item Number fleeutrod? Number (s)
- 43. USAS St SW Fenal Report of the SCE Actions Roquest SWFR Acomptance Test Activites Audit IAGPl SW Procedures
- 44. RTM P :;u^:: F1 Sendmg a Cleoed None Command to Retum DU to NormalMede from Maintenance Mode
- 45. RMS 52e440DSUS versus SCE AeGens DCN Against System Special Protoosi Sesed on SRS MODSUS
- 45. RMS52 C _J. e SCE Actions DCN Agennet System Measumment Cycle Ovemm SRS I versus Moesuring leie CPU Time Supplier Deviation Report Record loadin0 during Pro oes
- 47. RMS 52e-Dynamic Memory as GCE Acuens DCN AgainstLPU e Percentage of Aveliebte General SDD Cepecity
- 45. RMS 52e4Aeximum Closed None Cordguration for a 56n0le Loop
- 49. Software V & V FR,50123-805- SCE Actions DCN Against SW Tool 1387 0 Phase Summary Report Plan Request SW Phase Reports
- 50. RTM E ;u :: F1 Output SCE Actions DCN against LPUI Emuleben Testing Appliestion STF DCN against LPut Appilaation STR SCE eun now LPulAppi teste
- 51. RMS St insumeent DRMS SCE Actions DCN Agelnet LPU Documentation to Demonstrate General SDD Trecembety Requirement DCN Agennet LPU Generei SDD DCN ogelnet SW Final Report
- 52. RMS 52t>MODSUS/JSUS SCE Actions DCN Against System Protocol SRS (work with 45)
- 53. RMS S20 Comrn Speed - SCE Acuens DCN AgelnetSystem umnabens SRS
- 54. RMS 5" : z_u ^ Unks SCE Acuens DCN Against LPU General SRS T~ RMS S2t>DU Duplay CapetMisty SCE Ac#ons DCN Against DU SRS F- 7
SOFTWARE EVALUAT13N REPORT DOCU"ENT NO. 90400 REVl810N 0 SEAR Descripuon Status Action item (s) Action item Number Required? Number (s)
- 84. RMS $2t> Deployed Channels Closed None (items in $1)
- and Screen Layouts
$7. RMS S2b4AAS$ interface SCE Acuens DCN Age 6nst DU SMS Information SCE Update DU SRS/SDD St. RMS S2t> Relay Output SCE Acdons DCN Against DU Capabliny General SDD St. RTM Desgnator F24ource Test SCE Act6ons DCN age 6nst LPU Furcion in Design Documents General SRS
- 60. RMS Sh-Control Command SCE Acuons DCN Agnanst DU Modue General SDD For :r; 2.,i. support.
rewrite documents
- 61. RMS S2b-Screen Layout Detans SCE Act60ns SCh Update DU SRSiSDD (work with
- 54) to add Information.
DCN Against DU Generei SDD (work with SG) DCN Against DU General SRS (work . with 54)
- 62. RMS S2eAxtemal PCMASS or SCE Actions DCN Agains.DU DAS Functions General SDD
- 43. RTM Desenator F8, P2 SCE Acuens DCN against LPU Function of Averaging Software General SRS SCE evaluate missing dato conditions
- 64. RMS $2a-DU STF Equement SCE Actions DCNs Against DU STF Requirement and DU STR SCE run riew Du tests DCNs against STFs/STRs to inccrporate SCE required test detail SCE tun new tests SS. RMS S2a-LPU Communicatens Closed None Requirements
- 44. RTM Desgnator F8, P2-State Closed None Machine Diagrams with Undeflned Funchons
- 47. RTM Desenator F8. P2 SCE Acuens DCN agelnet DU STR Incomplete Screen Testing Re-test in DU STF F- 8
SOFTWARE EVALUATION REPORT DOCUMENT NO.'90400 REVISION 0 _
. I SSAR E:::f ^r- Status Acton item (e) Aethm item Number Required? Number (s)
St. RTM Doognetor Ft. P2 84 eve Closed None LPU Event Fee Messages St. RMS 52e40/LPU Cloeod None Commurucotions Requirements
- 70. DU/LPU 8 slave creerte test Closed None comes
- 71. Extemel PC connection with SCE Actions DCN to LPU Ooneral MASS /Entemel connation with 300 DAS in LPU 800
- 72. Extemel PC connection weh SCE Actions DCNe egelnet MASS /Entemel connochon with STFedSTRs te -
DAS in DU STR . Incorporate SCE requiend use ofIAASS test detail SCE run new mad 8 tests
- 73. Sample flow eigortthm, low /hgh Closed - None flow eierms testing
- 74. Extemel DAS knk tossing in SCE Actions Request DAS 16nk test DRMS System integration Test from MGPl Atlanta File
- 75. Spectrum Acquisiten Soards Closed None testing
- 78. Operaten of SYPASS mode SCE Actions DCN oge6nst DU SRS DCN ogainst DU STF DCN ogelnet DU STR SCE tun now DU tests
- 77. LPU/ PIPS SDD reference for 16 SCE Act6ons DCN To LPU General measurement channels 800 SCE Update does to provkle eeWeestion
- 75. Operaten of Retey Lotu SCE Actions DCN ogeenet DU SDD
- 79. Susser condemn test.Du STR SCE Actions DCN ogelnet DU STR 80123 60613211. Sechon 4.2.5 Tests 1 & 2 SCE run newtests
- 80. Analog Output test. Du STR SCE Aseens DCN egainst DU STF S0123 606 1 321 1 Secten 4.2.9 Test 5 DCN ogainst DU STR Re test es in DU STF -
F- 9
l SCFTWARE EVALUATION REPORT D3CUMENT NO. 40400 REVISION 0 l ) SEAR D6scrtpoon Status Act6on item (s) Act6cn item Number Required? Numberts)
- 81. Worst case testing for LPU SCE Act6ons DCNs against LPUAO condaions . LPU/I/O SDD STRISTF SO12H061346 Sechon 4.1.6 SCE run now LPUAO tests SCE evoluete SRSs and SDDs and use DCNs to update doce to provide PT refs
- 82. Extemet mput testing in STF . SCE Act6ons DCNs aga6nst LPU/SAS LPU/SAS SDD SO123 606-1 STF/STR 68 2 Sechon 3.1.7 SCE run new LPUISAS tests 83, LPU extemal tolsys testing in Closed None STF . LPU General SRS SO1234061 701 Section 2.1
- 44. LPU analog outputs testmg in SCE Actions DCN to LPU General STF *.PU General SRS SO123 SDD 6061701 Section 2.1
- 84. Worst case conAguraten in SCE Actions DCNs to System SR$
Integrebon Test System SRS to remove DU loading SO12M06-1 101 Sect'on 3.3.3 regt DCNs to update individual LPU - STFs/STMs with new Load Regts DCN to updele LPU/ Application STF/STR with new CPU load tests Run new Load testa
- 44. Du, SDD, STF or STR dynamic SCE Actions DCN to Du SDD to memory limit criteria System include memory str.ing SRS SO123 606-1 10-1 data Section 3.3.3 DCN to System SRS to remove DU CPU load regt (worked under 88)
- 87. LPU Apphcatens STFicynamm Closed Actions worked under memorylimitcrtiene Section 885 3.7.3.11 St. Displayed measurements on SCE Actions integration test to output devices-SSOW SO123- prove DASAAASS 606-1 12 trende match Secten 1.11.3_9.2 F- 10
) SOFTWARE EVALUATION REP *RT GCCUMENT NO. 90400 REYlSION 0 SEAR Doocr6puon Status AcGon item (s) Act6cn item Number Required? Number (s)
- 99. MASS performance of DAS Closed None fundens . SSOW SO123406-1 12
- Secten 1.11.3 9 M. Logs and cata as estanct SCE Act6ons DCN to System SRS modules . DRMS SSOW Seaton 1.7.7.1.32
- 91. Symbotc communcaten among SCE Acuons LCN to System SR$
programs
- DRMS SSOW Secten f 7.7.f.3.2
- 92. Entrar ,m, ema and error exa for SCE Actens Eval MOPl S/W each program.DRMS SSOW Dev Standards Seden 1.7.7.1.3 4
- 93. Coding standards for Suppher SCE Accons Eval MOPt S/W produced software. DRMS Onv Standards SSOW 1.7.7.1.5
- 94. Cn:':, . nt methodology. SCE Act6ons Evel MOPl S/W Dev DRMS SSOW Sechon 1.7.7.2. Standard 1.7.7.2.1.1.7.7.2.2,1.7.7.2.3 &
1.7.7.2.4 M. Deleton of requwoment SCE Actens SCE losue SDR tensport to ta=' Edison owned computers *. DRMS SSOW Section 1.7.7.2.5 M. Hardware platform SCE Act6cns SCE issue SDR independence.DRMS SSOW Secten 1.7.7.2.5
- 97. Programmme language for SCE Accons SCE produce tables of modules. DRMS SSOW module written in C, Sechon 1.7.7.2.5 - written in assembler, or combination DCNs to DU SDD and LPU SDD to include the above tables M. Realtrne clock function. SCE Act6ons DCNs against Du SRS System SS Secten 3 4.1 00 SDD, DU STF. DU STR DCNs against LPU SDD, LPUIAppl STF.
LPUlAppi STR SCE tun leap yearI Y2K tests. M. DU SDD tune fioso requvement. Closed (Worti done #M and DU SRS Section 3.3.4.5.4 999) F- 11
SOFTWARE EVALUATION REP 3RT DOCUZENT NO. 90400 REVISION 0 - SEAR E::: ;^ Status Acuen item (s) Aouon item Blumber __..r Numberts) 100. Cloclung or temng of everages. SCE Acuens DCN to DU General DR SMS . SDD Seshon 3.3.11.3 DCN to LPU General SOD
.191.. 6 TASS contgurshon and - SCE Aceons DCN to LPU General
. oonnection instruchone in LPU SRS STF & STR. System SRS Section 2.2 102. RS485 and RS232 knks . SCE Actions DCN to LPU General System SRS Section 3.1.3 UAS l 103. MASS witerfees with LPU and SCE Aouons DCN to LPU General SDD. DRMS System SMS .
SRS and LPU General 301234061101 Section 22 SDD to insiude StOPl and SCS Infonnetton 104. MASS DUs and LPUs into SCE Action DCN to DU SDD meintenance mode
- DU System SMS 30123406147 Somon 3.3.9 106, User interface with LPU for Closed (Work done in #102) opershone and fault ir,lormobon
. DRMS System SRS 30123-0061701 Seapon 2.3 108. LPU SRS, SDD and STF 'Sth - SCE Actions DCNs to LPU General sucosesive reboot fault". LPU SRS and LPU General General SRS SDD S0123406 1 70-1 Sachon 3.2.3.6 -
197.- DU, SRS, SDD & STF self tests - SCE Acuens DCNs to Du SDD and
. DU S00 Section 2.2.1.20, DU DU STF/STR STF S0123406134871 Seeon 2.17 CCNs to LPU STFiSTR SCE run now self tests 108. DU, SRS, SDD & STF soff tests SCE Actone DCNs to DU SDD and in degraded mode.DU SRS LPU SOD S01234061471 Sechon 33.1.3 100. Du,STF&STR* FLASH' SCE Actions DCNs to DU STF and toeling . DU SRS STR 80123406-147 1 Sechen 3.3.1.3 Assoas lack of FLASH test on Operability SCE run FLASH tests before startup 110. Reestbng the flow rate noteiners Closed None test.SSOW S0123406112 Sachon 1.11.7.11.9 111. LPU, STF & STR degraded SCE Actions - DCNs to mode seguirement.LPU LPUIApplicadon STF General Sl'tS and STR 80123406 1 701 Section 3.2.3.6 SCE run new LPUIAppi tests F.12 O
SCPTWARE EVALUATION REP 3RT D3CUCENT NO. 90400 REVISION 0 WEAR U f Status AeSen hom(s) Action inom Number Roeutrod? Numberts)
. 112. LPU,800. ETF & 5TR YLASH SCE Actions DCN to DRtR5 SR5 g copf seevirement.DRMS SRS 801234061101 Seaton DCN to LPU General 3.1.633 800 113. DU,500, STF & STR 7 LASH Closed None
, esp / and degraded mode seeutrement. DRMS SRS 801234061101 Seehon 3.1.E.3.3 114. LPulPIP5 3DD *no detector" SCE Actior e DCN to LPulPIPS SDD tault seguirements.DRMS SRS 301234061101 Seehon 31.5.3.3
-115. DR 3R5 seN tests performed by Cleoed None DU.DRMS SRS 80125408
- 10 1 Sechen 31.8.3.3 til. DU 5TF set test solemnces. Cleoed None DRMS SMS 801234061101 -
Sechen 3.1.5.3.3 117. LPulla 500 document SCE Aetions DCN to LPutti 500 selevenne.LPUISI SRS 80123 006144-1 Seehon 3.3 4 115. DulLPU wetehdog requaements Closed None
.DRMS SRS 801234061471 Sochon 3.2.2.4 119. Trip point values essenment. SCE AeSons DCN ogainst LPU BR5 SSOW S0123406-112 Section 1.11.3.1 ftequest SDR from 100P1 120. ItDUILDU monitor parameter SCE Actions Request 3DR from display.SSOW S01234061 IBGPl 12 Seehon 1.11.3.2 _
121. Algonthm status fleid definthon. SCE Acuens DCN to LPU PT Seehon 4.2.5 LPU General SRS 801234061 701 DCN to DU PT-DCN to LPU General SRS-122. Powerfoil and welchdog tests SCE Acuens DCN to DftM5 SRS not run Seehon 4.22 and 43r LPU STR . DCN to LPU General 301234081 3061 800
'XCN to LPUiAppi STF DCN toLPulAppi STR SCE nm new LPulAppi F- 13
SCFTWARE EVALUATION REPORT DOCUMENT NO. 90400 REVISIGN 0 NR Descrtpuon Status Achon ltomts) Action item Number Required? Numberts)
. 123. Testmg for detMor vohage SCE Achons DCN age 6n64 LPU inut, invalid gam faut in Common PT arvr*%n faut statusCuick counting variation flag, Saturated DCN apelnst LPU/SAS counang,invahd measurement SDD in algortthm status LPU General SRS SO1234061701 DCN against LPUISl 300 DCN agelnet LPU/SAS PT -124. Teenne in LPu!SAS, LPU/ PIPS, Closed None LPU,Si, LPullO test reports .
SSOW S0123406 1 12. Sechon i 11.3.1 125. Du low votage power testeg - SCE Actions DCN to DO SRS SSOW S0123406 1 12 DCN to DU SDD Sochon 1.11.3. 2 Request MGPl provide internel power test 124. Toshng for DU orderty shutdown Closed None LSOW SO1234 06-1 12 Section 1.11.3 8.3.1 127. Storage mquwoment and DU Closed None capabihty for temporary historicaldata storage and cakadatio.s for DU screen dispieys . S012234061 10-1,80123406 147 1,80123-006-1 70-1 Secton 3.1.3.3 124. Maxwnum measurement screen SCE Actons DCN to DU SRS
. S0123406-147 1,SO123-606-1-88-1, S O123 406-1-347 1, Sechon 3.3 4.5 129. Teston savmg parameters on SCE Acuons DCN to MASS SRS the DAS after chuging MASS .
SSOW SO123406-1 12, DAS Tests for DU/LPU Sechen 1.11.3.5 Change Flag SCE procedures for parameter changee from MASS 130. Du or MASS functionahty to SCE Actions DCN to System SRS control DU relay outputs . SSOW SO123406-1 12 DCN to DU SRS Section 1.11.3.2 DCN to DU SDD DCN to DU PT F- 14
SOFTCARE EVALUATIEN REPORT DSCU"ENT ND. 90400 REVISION 0 SEAR DescMppon Status Act6cn hom(s) Action item Number Required? Numbette) th. Requeod menanum seteaab6e SCE Act6 ens SCE evoluote levels for all promoss channels e operebility of affected 80123406 1 12 2, monitore that are 801234061101, scheduled for tuinover Secten 1.11.4 4 SCE perform analyste of algorithms and softwere to determine if requiremord is met After evolustion and testing, SCE evaluate need to update documents and update se required SCE wrtte and perform tests proving regt le met 133. Hgtilevel system performance SCE Act6one SCE evoluate requirement for DRMS hardware operability of effected and software specifcatent and monitore that are design (partculate and 1131 ocheduled for tumover channels)
- S0123406112 1, SCE podorm analyste Sucten 1.11.6.3 of algorithms and software to de.orm'n:
If reqv6 ment is met Afler evolustion and testing SCE evaluate ) - need to updata documents and update as required SCE write and perfumi teste proving togt le met 132. Hgtilevel system performance SCE Actione SCE evaluese requirement for DRMS hardware operebility of affected and software specifcat6ons and monitors that are 6esign (nquid and pas channels) scheduled for tumover 801234061 12 2. SCE perform analysis Seden 1.11.6.2 ol algorithms and software to determine if requirement is met After evolustion and testing, SCE evaluate need to update docu'nents and update se required SCE write and perform teele Proving regt is met F.16 _m___. _ _ . _ . _ . _
SOFTWARE EVALUAT13N REP $RT DOCUMENT NO. 90400 CEVl81;N 0 Desenpuon Status AoWon hom(s) Acton hem SEAR Number Reevnted? Numberte) iM. Heph level system performance SCE Aetions SCE evoluete requirement for DRM8 hardware operabletty of aflected and software speedcatens and monitors that are dungn (response time) . 8012> etteduled for tumover 6061122, Sectte 1.11.6 4 SCE perform analysle ' of algoetthms and software to determine if requirement is enet After evolueo6on and test 6ng, SCE evaluate need to update documents and update se required SCE wrfte and perform teste prov6as regt is met 135. High level system performance SCE Actic,ns SCE evaluate requirement for DRMS hardware operability of effected and software specdicatums and monitors that are design (Deployed souvity scheduled for tumover or,ncentreten levet). 50123-6061122. SCE perform analysis Section 1.11.6.2 of elecetthms and software to determine if requirementis met After evaluation and testing, SCE evoluete need to update documents and update as required SCE write and perform toets proving regt is _ iM. High level system performance SCE Ac#one SCE evoluete requirement for DRMS hardware operability of effected and software specacet6cos and mos.Itors that are design (Non naturet6ng). scheduled for tumover 30123406 1 12 2, Section 1.11.6.3 SCE perform analyons of algorithms and software to determine if r--d ;z: Mis met After evolust6on and testing, SCE evaluate need to update documents and upsete as required SCE wene and perform tests proving reg'le met 137. Detebase access through SCE Ac#ons SDR to remove symbouc roterence. 80123- symbolic references 6061122, Section 1.7.7.3.1 F.16
SOFTWARE EVALUATICN REPORT DOCU"ENT NO. 90400 REVISION 0
' SEAR Descrtpuon Status Acuon hom(s) Acuon item Numiner Required? Numberts) 1H. Hysterne vetue to the tre poent SCE Acuene DCN to LPU General 4 SO12M061701. Seden SDD 3631 139.~ Appliceton eesign documents Closed None (RELEASE Algont'wn).
SO12M06112 Secton 1.11.2 2 140. Appliceton test files or repons Closed None (RELEASE Algorthm). 501234061 12 Section 1.11.2.2 141. Atmosphere release Closed None calculetons . 80123406112. Section 1.11.2 8 142. Power up testing . SCE Accone DCN to DU SRS 80123406-1 12. Section 1.11.3 8.3.2 DCN to MASS SRS DCN to DU STF DCN to LPU STF SCE run new DU and LPU toete DCN to tAASS STF SCE run new MASS teste Check DAS Int Test for
" missing" LPU date test canoe SCE develop admin controle to clear DU trend memory on restert eher dowr time 143. Asyvnthm mometch SCE Actions DCN to DO 800 SO12H06149 2. S0123406 132M. DCN to DU STF SO12M061."
Seate 1,11.9 DCN to DU STR SCE run new DU test 144. Recaleration requ*ement. SCE Achone DCN to LPU General 8012M061 12, SRS Secten 161.4 146. Total ensk1p 6nput act.uracy. SCE Act6one DCN to LPU/lO STF SO1234061471, Secton 0 3. 801234061-3031, section DCN to LPullo STR 4 4.2.3, tost 5 SCE run new LPullO teste F 17
l SOFTWARE EVALUATICN REPORT DOCU'.'ENT NO. 90400 REVISION 0 l l SEAR Doocrtpuon Status Aot6on leem(s) Accon item Number Required? Numberts) 144. A arm setpoint syntactic SCE Actione DCN to DU SRS , corredness and semente pieusiblity 801234061141, DCN to DU STF Secten 2.3 SCE run new DU test DCN to MASS SRS DCN to MASS STF h BCE tun new MASS teste 147. V & V process fo' MASS Cloeod None 144. Test setup and contguration of SCE Actions SCE investagste devloes ' fossibility of developing est of detalkd beteilne toets for future modmcations 149. Software tools used for testing Closed None l i DRMS (Net. Spy, MODSUS) 150. Test ornene for operabday of SCE Actions DCNs against DRMS STFe/wTRs to 801234061101 incorporate SCE , required test criterte detail SCE tun new teste F.18 _.. ,- _- .. ,c--__- 7,.,,--w_. - _ , , _ . . _-
-ma ,_
83FTWARE EVALUATION REPORT D3CUMENT NO. 90400 REVISIGN 0 APPENDIX G OPEN ITEM
SUMMARY
i G- 1
COFTWARE EVAL.UATION REPORT DOCURREUT NO. 99440 REVIOION O APPENDIX G -OPEN ITEM
SUMMARY
S; . _. rf AcWows Saeews C__ ,__ 10kMor Dehr Latef Far asochment Closed D. 1 15-Aug-96 AWCROTECH 'C' ~ Closed
....y D. 1 N/A l 15-Aug-96 Edson Approved " .J-4,f Standertt Frvy
+ ;+ Beaucheme L 45179DA D. 3 Add statement in SCE 15-Aug-96 ' Rest Ta' ne" Afeesurements D. 1 Note about program SCE J as 15-Aug-96 DRAfS Growfft Documentaton R@.. rpemory growth Desen6edirr % a A.-g of Mbrk Beaucheme D. 1 Note SCE 15-Aug-96 M Toots for Atomtenance'Rm, .... ..: SCE
.. ,.. forCoseceanof Data D. 1 Note 19 Aug-96 SSOWR SCE D. 1 Note 19-Aug-96 SSOwsepterDeweton Roguests SCE 45183FA12 D. 3 Conect DurSDD 20-Aug-96 T.. T-4 Ardormeeor Rs;n, 4 as irt the SOW Closed D. 3 Note 20-Aug-96 T,. ;.g frdormatort at Test.%' Test Reports Closed D. 3 None 20-Aug-96 T ^ .i,,1: . _ _ ^ -, forAdorm i.^.4 .~..
SCE D. 3 Note 26-Aug-96 LPU/Commorr 300 Func90 net R9;__... .J Closed D. 3 Note 26-Aug-96 Defecton of PowerFadures (LPUG,.....,,i SDDJ Closed D. 3 Note 26-Aug-96 LPU/ Common S00 Funceon RK, ... .45 as Described h LPUC,.....urt SDO Besucheme D. 3 Note Closed 26-Aug-96 PowerSgpfy. T. -@. .. Afondonny Rm,
.. 25 ANssingin she LPE...~.i SDD Beaucheme D. 3 Note Closed 26 Aug-96 Afondonng Runtry of Fmy.e- Fursctoner K--{- ..._. 'e AEssmgirt the LPUC,.....,,i SDO Besucheme 3 Add into in LPU SDD. SCE 45181E&EA 45183F&FA Senater.k Checiangnot Mcfudedert LPUG ... i D.
26-Aug-96 Du SDD SDO. Anssmg TestReports eeeucheme 3 Updeled LPUISAS SCE 45196HA.45199HA. Acquiston Faut .- 4 ......:not Mciudsd ni fhe D. 26-Aug-96 SRS. SDD. PT. STR. 45511GA 46643E&EA. LPI.hCommor SDD. AGsshgTestReports Besucheme LPutSi PT.SDD 45506DA.45185CA D. 3 Note Closed 26-Aug-96 Afondonny Processor Load not inciuded in the LPUC,.....,,, S00. A4 sang Test R,,~45 Besucheme C; ,.: DU SRS SCE 45182F&FA DU SRS asit redefes to Document 5 D. 1 19-Sep-96 Closed D. 3 Related to other 19-Sep-96 SEAR s's 11.12.14.15.16.7 7 and 18 Algo B. 3 Note 10-Oct-96 Performance Gm,.,--, 45 by Verador as they seiste
- fo Aenwnum S, Cl3f Beaucheme B. 3 Note Algo 13-Oct-96 Performance Rog ...~. 25 by Yendoras they redsfe fo Asnnnum Channet Respons, rnne- Beaucheme B. 3 Note Algo 13-Oct-96 Performance R , ...~.. 5 by Vendor as they redsfe fo
- Accuracy (Loquod and Gaseous Channels) Beaucheme G -2
COFTWAIE EVALC'ATION REPORT DOCUME'3T NO. 90400 REVISION O De6rwbon of RAD LEVEL Range FuncDon arxf B. 3 Note Algo i 24-Nov-56 Pedwi w & Beauchame S. Kusenda 1 Sra..SRS SCE 451790A 274an-97 Clan 6cahon of MOGBUS Protocot C1a .TA,w . Missmg Document 45355, Senal Links Names S. Kusenda 1 DU SRS igniam SCE 45182F&FA 27-Jan-97 System Ourck OperaMsty Tests Funcfm Desenphon S. Kusenda 3 Added info in LPU Closed 45180G&GA 284an-97 Acronym De6nrDons S. Kusenda 2 Add G4. vow to SCE 45183F&FA 284an-97 DUISDD 284an-97 Cwi,,wanauDrg+ calm of Mothnes in System -- S. Kusenda 2 Note Closed SoMware and Ay,G"iwi SoMware On*wA Emutata Mode Regurrement S. Kusenda 3 Clanfy SSRS SCE 451790A 284an-97 DRMS System SRS Secun*y Access Passwonfs B.E. Marte 2 Add statement in SCE 451790A 284an-97 8-Fet>97 RTM Desegnator F8, P2-Mecharmsm to show Messmg S. Kusenda 3 Note + DU SRS SCE 45182F&FA Data in NisforicalF#e update Sf fD-Database UserInterface Regured Functsons B.E. Martm 1 Add statement in SCE 45179DA TFet>97 Inplemer%honinto DRMS System SRS SSRS S11E-DeGrutas of the Parameter Table Frekts B.E. Marte 2 Note SCE 3-Feb-97 3-Feb-97 R TM Desognator f f-Swstchog DU into Mantenance S. Kusenda 1 Note SCE 3-Feb-97 RMS St-Update of Dmm m d References and Au6t of B.E. Martwa 3 Note SCE SoMware C 4.u.- ; Process RTM DesignatorF7-LPU Test Fs8e Refertnce of LPU S. Kusenda 3 Clanfy LPU SRS+ Note SCE 45180GA 3-Fet>97 lock opin Marntenance Mode 3-Feb-97 RTM DesignatorF1-DU Swetch to Mantenance Mode S. Kusenda 3 Cw& DU SRS SCE 45182FA.45183F&FA translabon and add funcbon in DU SDO 3-Fet>97 RTM DesignatorF1-Test 2 of DU Software Test Report S. Kusenda 3 tycWie DU STF and SCE 46632E&EA.46639G&GA STR 3-Feb-97 RTM DesignatorFf-System Ourck Operab4ty Tests S. Kusenda 3 Note SEAR 27 SCE l 4-Feb-97 RTM DessgnatorFf-SecDon 2.f f of the DU ScMware S. Kusenda 3 Add testin DU STF SCE 46632E&EA.46omeF&FA. Test FJe and STR Changed DU 45182F&FA SRS R TM Designator F 7-SwMcfung a LPil horn Normal 10 S. Kusenda 3 Correct LPU STF SCE 46631G&GA 4-Fet>97 Mamtenance Mode (Test File) 4-Feb-97 RMS Sf-SWFinalReport of the Acceptance Test B.E. Martin 3 Note SCE AcDvihes 4-Feb-97 RTM Designator F f-Sendog a Command to Retum S. Kusenda 3 Note Closed i DU fo Normat Mode from Mamtenance Mode RMS S2a-MODBUS versus Specraf Protocot Based on B.E. Martu 1 Note SEAR 25 SCE 451790A 4-Feb-97 MODBUS G -3
COFTWACE EVALUATION REPORT DOCUidECT NO. 90400 REVI2 TON O 4-Feb-97 RMS S2a-Detectag a Measuree,.ent Cyde Overrun B E Marte 2 SSRS Change SCE 451790A Versus MeasunngIde CPU Tane 4-Feb-97 RMS S2a-Dynarruc Memory as a Percentage of B E. Mastet 2 Add statement in LPU SCE 4518TE&EA AvsRable Capaaty SDD 4-Feb-97 RMS S2a-Maxunum Connguration for a Segre Loop B.E Marta 1 Note Closed 4-Feb-97 Sothvare V & V FR, SO123-606-1367-0-Phase B.E Marta 3 Note SCE i SummeryReport 4-Feb-97 RTMDesignatorF1-OutputEmutaban Testag S. Kusenda 3 Corred transtabort in SCE 46631 GAGA 46638F&FA LPU STF and STR 4-Feb-97 RMS St-insufficrent DRMS Documentation to B.E Marte 3 Update LPU SDD SCE 45181E&EA Dernonstrate TraceabRityRequerement 4-Feb-97 RMS S2b-MODBUSfJBUS Protocol B E Marte 2 Note SEAR 25 SCE 5-Feb-97 RMS S2b-Comm Speed Limrfahans B.E Marte 1 SSRS danficahort SCE 45179DA 5-Feb-97 RMS S2b-Network Links B.E. Marte 1 Corred transtaban in SCE 45180GA LPU SRS 5-Feb-97 RMS S2b-DU Orsplay Capab#rty B.E Marte 1 Corred DU SRS SCE 45182F&FA 6-Feb-97 RMS S2b-Drsplayed Channets and Screen Layouts B.E Marte 2 Add info m DU SDD Closed 45183F&FA 6-Feb-97 RMS S2b-MASS interface information B.E Marte 2 Add info in DU SRS SCE 45182F&FA 6-Feb-97 RMS S2b-Relay Output Capsbeirty B.E Marte 2 Add info in DU SDD SCE 45183F&FA 6-Feb-97 RTM Des #gnator F2-Source Test FuncDon in Design S. Kusenda 3 Corred LPU SRS SCE 45180GA Documents transta6on 6-Feb-97 RMS S2b-Control Corrrnend Module B.E. Marte 2 Added ret to DU SDD SCE 45183F&FA 6-Feb-97 RMS S2b-Screen LayoutDetads B.E Marte 2 Note SEAR 56 SCE 7-Feb-97 RMS S28-Extemat PCAtASS or DAS Funcbons B.E Marte 3 Added info in DU SDD SCE 45183F&FA l I 8-Feb-97 RTM Designser FS, P2-Functron of Averagog S. Kusenda 3 Add info in LPU SRS SCE 45180G8GA Sothvare 8-Feb-97 RMS S2a-DU STF Equepment Requwement B.E Martm 3 Ctanficaton in DU SCE 46632E&EA.46639F&FA STF&STR 8-Feb-97 RMS S2a4PU Cw,mam.a^vus Requwements - B.E Marta 3 Note C30 sed 8-Feb-97 RTM DesignatorFS, P2-State Machme Dragrams swth S. Kusenda 3 Note Closed Undefined Funcbons 8-Feb-97 RTM Des #gnatorF8, P2 ^ n.v4.". Screen Teseng S. Kusendt. 3 Added testin DU STR SCE 46639F&FA 8-Feb-97 RTM Designator FB, P2-Slave LPU Event Fde S. Kusenda 3 Note Closed Messages 8-Feb-97 RMS S2a-DutPU Commurwcahons Requweme9ts B_E Marbn 2 Note Closed 10-Feb-97 DU feshng swth 8 stave LPUs B E. Marte 2 Note Closed 10-Feb-97 Extemal MASS or DAS connectron in LPU SDD B.E Marte 3 Added info in LPU SCE 45181E&EA SDD i 10-Feb-97 Extemal MASS or DAS connechan in LPU STF/STR B.E. Marte 3 Note SEAR 71 SCE 10-Feb-97 Flow EAy4,,,,, testrng S. Kusenda 3 Note Closed G4
COFTWARE EVAt_UATION CEPORT DOCUMECT NO. 90400 CEVIZION O ExtemalMASS orDAS w ,ed,wiin SITF B E. Marte 2 Note SEAR 71 SCE 10-Feb-97 10feb-97 LPU/SAS boards testeg B.E Martm 2 Note Ckised 12feb-97 Bypass mode in the DU S. Kusenda 3 Added inic m DU SRS SCE 45182F&FA.45183F&FA. i
& SDD. test in DU 46632E&EA.46639G&GA STF&STR 12feb-97 LPtNPIPS with 76 charmets inrssmg.c doc B.E. Marte 1 Added mfo in LPU SCE 45181E&EA SDD 12-Feb-97 Latetr relay drscussen m DU SDD S. Kusenda 1 Added info n DU SDD SCE 45183F&FA 12-Feb-97 ACK test forburrerrnrssmg S. Kusenda 3 Added test in DU STR SCE 4 W &FA S. Kusenda 3 Added test in DU SCE 46632E&EA. goo wF&FA 12feb 97 No test for twgher charmel analog output STF&STR LPtNtO wrth loadmg test for 16 channels B.E. Marte 2 Changed LPU/iO STF SCE 111496CA,111497CA 12-Feb-97
& STR Externalanaloginputin the LPU/SAS B.E Martm 3 Added tests in SAS SCE 400 joe &EA.4SS43E&EA 134eb-97 STF&STR 134eb-97 Mussing test forthe relaysin the LPU B.E Marte 2 Note Closed 13-Feb-97 Mrssmg test foranalog outputs B.E. Martm 2 Note SEAR 83 SCE 13-Feb-97 No test forCPUormemoryfoodm 51TF B.E. Marto 3 Add info in DU SDD SCE 45183F&FA 13-Feb-97 No test for CPU orspemory load in the DU B.E. Martm 3 Note SEAR 85 SCE 18-Feb-97 No test for CPU or memory load in the LPU B.E Marte 3 Note SEAR 85 Closed 154eb-97 Test to compare data between the MASS and the DU S. Kusenda 3 Note SCE 15feb-97 MASSis not p,fwn-4 aE DAS funct>ons S. Kusenda 3 Note Closed 19-Feb-97 Logsc and data shaE be drstect B.E. Marts 1 Note SCE 19-Feb-97 Symboec commurwcahon between data andlogic B E. Marte 1 Note SCE 19feb-97 Subroutme requrrements B.E Marte 1 Note SCE 19feb-97 Codng standards B.E. Marte 1 Note SEAR 92 SCE 194eb-97 Source code management B.E Martm 1 Note SCE I
194eb-97 Prograrn shaR be transporfable B.E Marta 1 Note SCE 19-Feb-97 Hardware platform independence B.E Marte 1 Note SEAR 95 SCE , i 19-Feb-97 Use of assemetylanguage B.E. Martm 1 Note SCE 20feb-97 Date and Dme management B.E. Martm 2 Add info in DU SRS & SCE 45182F&FA.45183F&FA. SDO LPU SDD. Add 45181E&EA.46638F&FA. testin LPUfAppil STF 46632E&EA.46639G&GA
& STR. DU STF &
STR 21-Feb-97 Time esplay formatin the DU B.E. Marte 2 Note SEAR 98 Closed 21-Feb-97 Messmg average tarwng mfo forthe DU B.E Marte 2 Added info in DU SDD. SCE 45183F&FA.45181E&EA LPU SDD 21-Feb-97 DAS shaR beincludedin LPU testing B.E. Mar 1m 2 Conect LPU SRS SCE 45180GSGA
- Gw.
-u G -5 1
COFTWARE EVALUATIOC REPORT DOCUMENT CO. 90400 REVillON O B E Marta 2 C1.:.e4 LPU SRS SCE 45180G&GA 21-FetF97 Missmg reference to RS232 or 485 in LPU SDD BE Martn 2 Added info in LPU SCE 45180G&GA 21-FetF97 E g MASS ftnu,wis M LPU SRS and SDD B E. Martn 2 Add % in DU SRS SCE 45182F&FA 214etF97 Ea-g MASS references m DU doca...c.-as C;v5M , BE Martn 2 Note 224etF97 ' *M-4 mfo on LPU -4miace Cv.,a Ied LPU SDD 45181E&EA BE Martn 3 SCE 22-FetF97 Mrssmg successrve reboot Jmd,v , m LPU SRS BE Marte 3 Added info in DU SDD SCE 45183F&FA.4en OE&EA. 22feb-97 Massmg Self-fest regurrements n DU SRS and DU STF & STR 46639G8GA BE Martn 3 Aceed info m DU SDD SCE 45183F&FA.45181E&EA 22-FetF97 Traceabelety pb on cnicat parameter d,m.A.W and LPU SDD BE Martn 3 Added test in DU SCE son UE&EA.46639F&FA 24fetF97 Traceab#ety between SRS andSTF on DU STF&STR S. Kusenda 3 Note Cbsed 24-Fet>97 E gtestforresettmgtotaArer B E Martn 3 Modified LPUls? :- SCE 46631G&GA 46637E&EA. 24-Fet>97 Missmg fest on LPU degraded rnode STF. LPU/ Base STF & 46630F&FA STR , BE Martn 3 Added mfo in SSRS SCE 45179UA.45tS1E&EA 24fetF97 Traceabetify between SRS and STF on LPU and LPU SDD 3 Note C;v5M 244etF97 Misa.g info on FLASH backup use B E. Marte BE Martn 3 Note SCE 24fetF97 Pb on seWfest referencesin the DU SRS C;usM 45187D&DA BE Martn 3 Added nfo in 25fetF97 Missmg probe presence m Pfr5 SDD PIPS /SDD BE Marte 3 Note Closed 2SfatF97 Ea-9 rest forenticat pararnin the DU SCE 45185CA BE Martn 3 C3.J ed Si/SDD 25-Feb-97 B d-e-d.Jerence in the LPU Sa SDD BE Martin 3 Note C30 sed 26-FetF97 Eans waf hdogfedus S. Kuse.-4E. 3 Cv..nled LPU SRS SCE 45180G&GA 27-FetF97 Lmu,.44mey in the LPU SRS about inp puer 45 S. Kusenda 1 Note SCE 25-Fet>97 The ROU shat controt a6 LPU parameters S. Kusenda 1 Cv..udd LPU SRS. SCE 45180G&GA 45504HA. 28-Fet>97 Contfrct in algonthrn status desenpban 4550 SEA LPU PT and DU PT S. Kusc 4a 3 C dedSSRS LPU SCE 451790A,45181E&EA. 28+et>97 Powerfad test not run 4S631G&GA.46638F&FA SDD. LPU/ Base STF&STR S. Kusei4. 3 Cviea. ice LPU PT. SCE 45504HA 45199HA. 1-Mar-97 Status testeg. 4v.,if Jea,y.md SAS SDD. Si SDD 45185CA 3 Note C;cace 1-Mar-97 Miss of radration fed,9 S. Kusenda S. Kusenda 3 Co.icded UU SRS SCE 45183F&FA.45182F&FA 3-Mar-97 Powerfa#mrssmg oformeDon on the DU and SDD S. Kusenda 3 Add test in DU STF & Closed *on:GF&EA 4echG&GA 3-Mar-97 Miss of shuth testin the DU STR , H:4va.4 trend references in the system SRS B E. Marin 3 Note Closed 4-Mar-97 S. Kusei4. 1 Add into in DU SRS SCE 45182F&FA 6-My-97 Mass of rnar rnesso.v.. .-4 screen in the DU SRS G -6
SOFTWARE EVAt.UAY10M REPORT DOCUMECT NO 90409 REVISION O 6-Mar-97 MASSOAS parameserchange S. Kusende 3 Add irdo in MASS SRS SCE 45224FA (M4ar-97 Check source refer notin MASS S. Kusends 3 Corrected System SCE 451790A 45182F&FA. SRS.DU SRS. PT and 45505EA. 45183F&FA 7-Mar-97 ;&p.-O.;f con 6dence pedbrmance speedca6on B.E. Martn 3 Note A;go 7-Mar-97 ;&p. % ;" response eme perfbrmance speoncaton
- B.E. Marte :' Non e SEAR 131 Algo 7-Mar-97 ;&p,-O.;" response eme performance zweufA, B.E. Martn 3 Note SEAR 131 Algo 7-Mar-97 ;&p, O.c response ame performance spec 6caton B.E Marte 3 Note SEAR 331 Algo 7-Mar-97 ;Ap.-O.;l accuracy performance speedcaban B.E Marbn 3 Note SEAR 131 Algo 7-Mar-97 ; AprO.4 saturaton speoncaton B.E Marte 3 Note SEAR 131 (Jgo 7-Mar-97 Database access through symbote references B.E. Martm 1 Note SCE IHear-97 Hysserests on storm notdesenbed S. Kusenda 1 Add info in LPU SDD SCE 45181E&EA '
8-Mar-97 Refease afgonewn not desenbed S. Kusenda 3 Note Closed 8-Mar-97 Msseg release adganfhmin SAS STF S. Kusermi.= 3 Note + SEAR 143 Closed 4 6-Mar-97 SCE SSOWrefeese spec #cs S. Kusenda 1 Note Closed 18-Mar-97 Power off behewor anrssmg informaeon S. Kusenda 3 Added info in DU SRS. SCE 45182F&FA.45224FA, STF &STR.LPU STF 46632E&EA.46635G&GA.
& STR. MASS SRS- 46631G&GA.46638F&FA 20-Mar-97 Msmatch between SAS SDD and STR on afgos S. Kusenda 3 Added into in SAS SCE 45199HA.46636E8EA.
SDO.STF&STR 46643E&EA 20-Mar-97 Mrssmgrecameraban SSOWapeoncaton S. Kusenda 3 Add info in LPU SRS SCE 45180G&GA 20-Mar-97 LPtA90 accuracydfFers hem SRS fo STF S. Kusende 3 Updated 10 STF&STR SCE 111 9eGA.111497CA 21-Mar-97 Tippomt vandWy d-G-,y S. Kusenda 3 Add into in DU and SCE 45132F&FA.45224FA MASS SRS 9-Apr-97 MASS not onder VSVprocess 5. Kusends 3 Note Closed 1 9-Apr-97 Lack of defa# m fest docurnentspan S. Kusenda 3 Note SCE 9-Apr-97 Queston about foofs usedIbrfesteg S. Kusende 3 Note Closed 10-Apr-97 Mssmg detaded acceptance enema e fest doc B.E. Marte 3 Note :SCE G -7
SDFTWARE EVALUATION REPORT DOCUMENT NO. 90400 MEVisl0N O 1 APPENDIX H SEAR ACTION ITEMS H -1
SCFTWARE EVALUATISN REPSRT DOCU*2ENT NO. 90400 REVisl3N 0 APPENDlX H - SEAR ACTION ITEMS SEAR - ACTION ITEMS . I 30 Metgi RECORD # TITLE AND DESCRIPil0N: ACTION ITEMS: TERM J SHONT/LONO: I 31 SEAR No. 003 Acton # VAV Yeom %gh* Level Anomaty: The SS0W,8012340 1) SCE prepare DCNs against the LPU Short 1 31 12, sections 1.7.7.2 6 and 1.6.1.21, requires General SDD (501234061346 0) and the DU that "Ttw system level software than indude a re SDD (SO123406146-1) to include the MGPl clartficateons on the 'reaMema design
- of the software.
Acton f V&V Team *Hgh* Level Anomaty: The SS0W, S012340 2) SCE prepare DCN against the DRMS SRS Short 61 12, sodions 1.7.7.2.6 and 1.61.21, requires (801234061101)to indude the MGPl that 'The system level software that indude a to clarifications on the 'real time des 6gn* of the software. V4V Team *High* Level Anomaty: The SSOW,6012340 3) SCE request a SOR from MGPl to remove Long Aden # 61 12, sectons 1.7.7.2.6 and 1.6.1.21, requires the ' industry standard reaMeme operating that 'The system level software shallinclude a re system
- requirement from the SS0W.
32 SEAR No. 904 Acton # V4V Team ' Low" Level Anomaly: The SS0W ($0123406 1) SCE Prepare DCN against the DRMS SRS Short 4 1 12), section 1.7.7.1.2 describes the following (501234061101)to include detail on requtrement 'All software shan secommodate the pot the DRMS requirements for system growth and reconfguration. 33 $EAM No. 00t V&V Team
- Low
- Level Anomaty: The $$0W (S0123406 1) SCE submn request to MGPl Atlanta to Long Acton s 1 12) in secten 1.7.7.1.4 requires that 'The sof provide informaton describing how the SCE tware shall be comp'etely maintalnable by Edison p maintainability requirement was addressed for the DRMS system design, implementaten, and test.
V&V T6am' Low
- Level Anomaty: The S$0W(S0123406 2) SCE to get the softwarsiools from Long Amon#
1 12) in secten 1.7.7.1.4 require
- that "The sof MGPi necessary to be fuNy tware sha8 be comnietely maintainable by Edison p vendor-independent.
NOTE: Shorf-term . Prior to DRM3 eqvpment operationsVumover Long-:erm . Sh to nho months from the de:e of this H .2
. . _ .-___. _~ __.. _ _ _ - _._ . _, . _ . . _ . . _ _ _ _ _ _ _ _ _ _ _ _ . SOFTWARE EVALUATION REPORT DCCUMENT NO. 90400 REVISION 0 RECORDf TITLE AND DESCRIPTION: ACTION ITEMS TERM SHORT/LONG: 34 SEAM No. 000 Amen # V&V Team *LW Level Anomay. The SSOW(50123406 1) If such a test does not already esist, Short
+1 12) sect 6on 1.6.1.21 in part requ6tes that *Non wrtle and execute a test to verify the processed ltn6tantaneous y) tadiaten dets will be system throughput requ6rement (6 seconds).
Aden8 V&V Team *LW Level Anomo y: The SS0W(60123406 2) MGPl prov6de a disevoslon of why the Long
.1 12) secten 1.6.1.21 in part requires that *Non
- send" instantaneous data lo the DAS was processed (metantaneounty) tadiaten data will be not implemented.
Acton # V&V Team *LW Level Anomaty: The 350W(80123406 3) MGPl request a SDR changing the $$0W Long 1 12) section 1.6.1.21 in part requires that *Non requirement. processed (instantaneounty) rad;ation data will be 38 SEAR No. 007 Action # V&V Team *LW Level Anomaty: The SSOW(50123406 1) SCE request a SDR from MGPl to remove Long 1 12) secten 1.6.1.21 in part regulros that *Dat the
- automat 6c transfer of data to the DAS e shall be automatically transferred to the DAS pe for long term storage and toport genersten* requirement from the SSOW.
30 SEAMNo. 000 Act6on # V&V Team *High* Level Anomaly: The DU/ Common SRS 1) DCN must be writte"> gainst the DU SDD Short (S0123406147) describes the regulroment, in sec (SPE Documen* reMr S01234061961) to tion 3.3.10 and 3 3.11, for trendog information a include the revkwe w described in the attached MGPl response. 30 SEAR No, 011 Action # V&V Team *High* Level Anomaly: The LPU/ Common SDD 1) SCE prepare DCN against the LPU Short (S01234061346) secten 2 417 does not include General SDD (801234061 346 0) to include the functonal requirements desenbod in the LPU/ the MGPl clanficaten on the
- differences between critcal parameter checks and parameter range validity.' l 44 SEAR No. Of t Acton # V&V Team "High* Level Anomaty: The functional req 1) SCE prepare DCNs against the LPU Short utrements, test link checking. described in the General 500 (S01234061 346-0) to the DU LPU/ Common SRS ($0123406170) section 3.7.3.12 h SDD (S0123406196-1) to include the MGPl clarifications on the ' software welchdog*
communicatens checking. NOTE: Short4erm . Ptnt to DRMS equipment operatonsVumover Long term . Six to rune months kom the date of this H .3 i l l 4
, - . - . , --,,w. - - .- .,--4 --
SDFTWARE EVAL.UATION REPORT DOCUMENT NO. 90400 REVISISN 0 RECORD # TITLE AND DESCRIPTION: ACTION ITEMS TERM SHORT/LONO: i 49 SEAR No. 011 Amonf V4V Team Hgh' Level AnomaY: The functonal req 1) DCN rnust tie wrmen against the Short utrements, acquisRon faut management, described LPU/SAS SRS (Document No. M the LPU/ Common SRS (60123406-170) sedun 3. 801234061 19 2) to include the revisions as descrited in the attached MGPl retponse. ; Aden8 V&V ioam High" L..et Anomay: The functonal req 2) DCN must be written against the Short utrements, acquisition faut management, described LPUISAS SDD (Document No. In the LPU/ Common SRS (50123406-170) secten 3. 50123406-149 2) to include the revislons as described in the attached MGPl response. i Amon f V8V Team Hgh* Level Anomay: The functeenal reg 3) DCN must be wrmen against the Short , ulroments, acquistion fault management, descrited LPU/SAS STR (Document No. M the LPU/ Common SRS (SO123406170) seden 3. 801234061325-0) to include the revis;3ns as descrited in the attached
- MGPl response.
Aden s V&V Team 'Hgh" Level Anomaly: The fundeonal req 4) DCN must be wrmen against the Short uwoments, acquisiten faut management, described LPU/SAS PT (Document No. 501234061421) in the LPU/ Common SRS (50123406170) secten 3. to incivde the revis6ons as described in the attached MGPl response. Actton # V&V Team Ngh' L svol Anomay: The functional req 5) DCN must be wrmen against the LPU/Si Short ulrements, acquisiten fault management, described SDD (Document No. 801234061333 0) to in the LPU/ Common SRS (50123406170) secten 3. Include the revtsions as descrited in the attached MGPl response. Acton # V&V Team Hgh' Level Anomay: The funchonal reg 6) DCN must be written agannat the LPU/Si Short utrements, acquisiteon fault management, described PT (Document No. SO123406145 2) to in the LPU/ Common SRS (50123406170) sodion 3. Include the revisions as descrited in the attached MGPl response. 41 SEAM NG. Ofg i 4 Achon# V&V Team ' Low
- Level Anomay: The DU Software Requ 1) Prepare DCN against the DU SRS Short trements Specmcation (50123406147) secten 3. (SO1234061471) to incorporate the 3.12.3 states *Only tests specmc to the DU will document reference changes provided by the MGPl response to this SEAR.
NOTE: Shorthrm Prior to DRMS equpment operetonstumover Lorgterm . Sex to nine months hom the date of this H -4
-- - - . _ _ _ _ - - - - - . _ ~ _ - . . . . . - ,- - -. - - - - . _ . - - . -
SGFTWARE EVALUATl3N REPORT DOCU:'ENT NO. 90400 REVISICN 0 RECORD 8 TITLE AND DESCRIPT10N: ACTION ITEMS: TERM SHORTILONO: 40 SEARNo. 021 i Action # ANOMALY DE3CRIPTION/ IMPACT: 1) SCE shau evaluate the operabilty of Short any monitor that are scheduled for S$0W $012M%1 12, Sodion 1.6.2.3 through 1.6.2 tumover and are afleded by this SEAR. Acton 8 ANOMALY DESCRIPTIONilMPACT: 2) SC7 shed review and anatyre the DRMS Short elgorithm documentation, including the 580W S01234061 12, Sedion 1.6.2.3 through 1.6.2 French *alponthm performance specincetens' and algorthm technical manuals, to determine if the DRMS has teen designed and implemented to meet the SS0W regurrement for minimum sonsthrity. Action 8 ANOMALY DESCRIPTION /lMPACT: 3) SCE shen develop test Short procedures / reports that verWy that the SSOW S01234061 12 Section 1.6.2.3 through 1.6.2 DRMS meets this minimum sensnivey ^ requirement at SONGS. I Action f ANOMALY DESCRIPTION / IMPACT: 3) SCE shab develop test Short 1 procedures / reports that ver#y that the SS0W S01234061 12, becten 1.6.2.3 through 1.6.2 DRMS meets this minimum sensnivity requirement at TONGS, - Action f ANOMALY DESCRIPTION /lMPACT: 4) After evaluation and testing Short adiviles have teen completed. SCE shall SS0W S01234061 12, Secten 1.6.2.3 through 1.6.2 evaluate the nood to update the DRMS software documentation and shall update the documents as required. Action 8 ANOMALY DESCRIPT10NilMPACT: 1) After the evaluation and letting Short actwRes have teen completed, SCE shall SS0W S0123406-1 12, Secten 1.6.2.3 through 1.6.2 evaluate the need to update the DRMS software documentatson and shau update the documents as required. NOTE: Short-term . Prior to DRMS squpment operetensVumont LongHerm . Six to nine monens ham the date of this i I H5 l '^
SOFTWARE EVALUATICil REPORT DCCUZENT NO. 90400 REVISION 0 RECORD # TITLE AND DESCRIPTION: ACTION ITEMS: TERM . SHORTILONG: O SEAR No. 022 Acton 8 ANOMALY DESCRIPTION / IMPACT: 1) SCE shall evaluate the operability of Short any monitors that are scheduled for S$0W SO12M061 12, Sect on ).6.2.3 6 through 1.6 tumover and are affected by this SEAR. Action s ANOMALY DESCRIPTION / IMPACT: 2) SCE shnu review and anatyze the DRMS Short algortthm documentaten, including the SS0W SO12M061 12, Secten 1.6.2.3.6 through 1.6 French *algortthm performance specifications
- and algorithm technical manuals, to determine if the DRMS has been designed and implemented to meet the SS0W requirement for Leak Detecton.
Adion s ANOMALY DESCRIPTION / IMPACT: 3) SCE shall develop test Short procedurestreports that vertfy that the SS0W SO12M061 12 Secten 1.6.2.3.5 through 1.6 DRMS meets this minimum sensitivity requirement at SONGS. Action 8 ANOMALY DESCRIPTION / IMPACT: 4) After the evaluaton and testing Short actMtes have been completed SCE shall SSOW SO12M061 12, Secton 1.6.2.3.5 through 1.6 evaluate the need to update the DRMS software documentaten and shall update the documents as requbad. NOTE: Short term . Pnor to DRMS eavipment onoratronsvumover Long-term . Six to r ine months from the date of this 6f SEAR No. 023 Adone ANOMALY DESCRIPTION / IMPACT: 1) SCE shan evaluate the operability of Short any monitors that are scheduled for SSOW S012M06-1 12, Secton 1.6.2.3.5.2 through 1 tumover and are affected by this SEAR. Acton s ANOMALY DESCRIPTION / IMPACT: 2) SCE shan review and analyze the DRMS Short algortthm documentaten, including the SS0W SO12M061 12, Section 1.6.2.3.5.2 through 1 French *algonthm performance specsfications* and algortthm technical manuals, to determine if the DRMS has been designed and implemented to meet the S$0W requirement for accuracy. Action s ANOMALY DESCRIPTION / IMPACT: 3) SCE shan develop test Short procedures / reports that verify that the SSCW SO123-606-1 12, Section 1.6.2.3.5.2 through i DRMS meets this accuracy requirement at SONGS. Acton s ANOMALY DESCRIPTION / IMPACT: 4) After the evaluat6on and testing Short activttes have been completed, SCE shan SS0W SO12M061 12, Secton 1.6 2.3.5.2 through 1 evaluate the need to update the DRMS software documentaten and shall update - the documents as required. H -6
SCFTWARE EVALUATloN REPORT DOCUMENT NO. 90400 REVISION 0 RECORD # TITLE AND DESCRIPTION: ACTION ITEM $t TERM SHORT/LONG: St SEAR No. 036 Ador. # ANOMALY DESCRIM10N / NPACT: Sed 6on 3.1.7.1 of 1) DCN must be wrnten against the System Shoft the System Software Requirements Specificatens (S SRS (SCE Document Number 01214061 101), says that RMS dev6ces do not use (501234061101) to include the revisions as described in the attached MGPl response. 83 SEAR No. Off Adion # AN0wtALY DESCRIPTION / NPACT: In many instances 1) DCN must be written against the DU SRS Short refemnces are made to documents that are not a per (SCE Document Number S01234061471) to t of the dehvored RMS document set. A specific e include the rev6slons es described in the attached MGPl response. SS SEAR No. Ott Action # ANOMALY DESCRIPTION / NPACT: There la e perenc 1) DCN must be wrttten speenst the DU SDD Shoft problem whh the use of undefined acronyms in the (SCE Document Nutnber S01234061 g61) to documents. Th6s makes reading / understanding very include the rev6slons as described in the attached MGPl response. NOTE: Short term . Pnot to DRMS equipment operatensvumont Long-term . Six to nbe months from the date of this 87 SEAR No. 030 Act6on # ANOMALY DESCRIPTION / IMPACT: In Sedion 31.7.3 1) DCN must be written against the System Short 3 of the System SRS (SO1234061 101) R states : SRS (SCE Document Number
*By running the output emulation mode, you can si $01234061 101) to include the revisions as described in the attacheo MGPl response.
\
O SEAR No. 03f Aden# ANOMALY DESCRIPTION / NPACT: 1) Prepare a DCN against the DRMS System Short in the SSOW, Secten 1.T.7.3, requirements are sta SRS (801234061 101) to incorporale the 2d that the modrheatens to the DRMS database er modifr.atens provided in the attached MGPl response to this SEAR. NOTE: Simt-term . Prior to DRMS equipment operatonsvum.nor Lorpserm . Six to nho months kom the dere of this H -7
SCFTWARE EVALUATION REPORT DOCUMENT NO. 90400 REVISISN 0 ' 4 RECORD # TITLE AND DESCRIPTION: ACTION ITEMS: ?tRM = SHORTAONG: fu SEARNo. 22 Aden8 ANOMALY DESCRIPTION / IMPACT: During testing of i 1) DCN must be written against the DU SRS Short he hetoncet management function (sw S01234061 (SCE Dooumont Number 80123406J 471) to
, 441 Sedens 4 4.26 through 4 4.29), R is veri include the revis60ns as descrited in the attached MGPl response.
Action # ANOMALY DESCRIPTION / IMPACT: During letting ofi 2) DCN must be wrtiten against the DO STF Short he hotorcel management funct6on (see 601234061 (SCE Document Numter 8012340613471) 3S1 Sectons 4 4.26 through 4.4?g), R is vert to include the follow 6ng step in Sedson 4.3.2.6, Test no. 22 and 12.
'6nstantaneous measurament wth h6 story wth LPU/DU link. deconrectod' Adeon # ANOMALY DESCNPTION / IMPACT: Dunng testing of t 3) DCN must be wetiten against the DU STR Short he hotoncal management funcien (see 801234061 (SCE Document Numter 301234061321 1) 3301 Sections 4 4.26 through 4 4 2g), R is vert SeWon 4.2.6 22 to include the resuts of Test no. 22, Step 12 as deserted teloer:
Acton no. 6. Deplay the instantaneous measurement with history screen, then deconnect the LPU/DU hnk. Resuhs no. 6
.Ver$ that the measutomonts are left shlhed, leaving a hole in the histortcal curve.
Adion # ANOMALY DESCRIPTION / IMPAC1: During testing of t 4) DCN must be written agalnst the LPU Short he historical management functon (see 801234061 Apphcation STF (SCE Document Number 3301 Sections 4 4.26 through 4 4 2g), it is vert 8012340613301) Seden 4 4.2g, to 3 vertly 60 days of history instead of 2. Acton 8 ANOMALY DESCRIPTION / IMPACT: Dunne testig of t 6) DCN must be written against the LPU Short he histoncal management function (see 801234061 Application STR (SCE Document Number 3301 Sectens 4.4.26 through 4 4.2g), R s vert S012340614061) Secten 4.2g to vertfy t that 60 days are deplayed instead of 2. Action 8 ANOMALY DESCRIPTION / IMP ACT; Dunne testing of t 6) The test as described in 2 and 3 above Short be histoncal management funcfen (see 801234061 must be run. (NOTE: Aden items 2 of 3) 3301 Sections 4 4.26 througn 4.4.2g), it ta vert Acton 8 ANOMALY DESCRIPTION / IMPACT: During testeng ofI 7) The test as described in 4 and 6 above Short he histoncal management funden (ses S01234061 must be run. (NOTE: Actions 4 or 6) 3301 Sections 4 4.26 through 4.4.2g), t is vert NOTE: Short term . Prer to DRMS equtwnent cperationstumont Long-term . Six to nine months kom the date of this l l I 1 H8
SOFTWAQE EVALUATION REPORT DOCUMENT NO. 90400 REVISION 0 QECORD8 TITLF AND DESCRIPflDN: ACTION ITFMS: TERM SHORT/LONG: 120 SEAR No. 33 Acton 8 ANOMALY DESCRIPTION / IMPACT: 1) Prepare a DCN against the DRMS System Short in the SSOW (5012344-121), requirements for the ORS (SO1234St.101) to incorporate the database user interface are spectfed. Even thou modrrications pro'Aded ln the attached MGPl response to this SEAR. 120 5EARNo. 34 Acton # ANOMALY DESCRIPTION / IMPACT: 1) Prepare a DCN ogelnst the DRMS System Short The SCOW, Section 1.7.7.3 4, (801234%12.?) sper' SRS (50123451 101) to incorporate the efes that an sudd trail for database changes the modWicatens recommended by the Reviewer. Acton 8 ANOMALY DESCRIPTION / IMPACT: 2) Reques; that MGPl submit a Suppher Long The SSOW, Secten 1.7.7.3 4, (SO1234S121) spec Dev6aten Report starting that the afies that an audit trail for database changes sha catabase change logging functon has not been implemented in the DRMS and that a MGPl softwara snomaly report to add this functon has been issued. Act6on 8 ANOMALY DESCRIPTION / IMPACT: 3) Evaluate the DRMS Software Short The SSOW, Secten 1.7,7.3 4, (SO1234%121) spec Configuration and Maintenance procedures Ifes that an audit trail for database changes the to ensure that setpoint changes from the DU are adequately controlled and documented 130 SEAR No. 35 Acton 8 ANOMALY DESCRIPTION iIMPACT:In Secten 2.2.1.3 1) SCE to investigate the feasibility of Long of the DU General SDD (SO1234St.98-1)It says t reworking the entire document set to bnng hat the Supervision of Commands module, common to it up to SCE Standards, 907E: Short-term . Poor to DRMS equipment cperatonsvumont % term . Six to nine rnonths from tne date of this H -9
SCFTWARE EVALUATION REPORT DOCUCENT NO. 90400 REVISION 0 RECORD 8 TITLE AND DESCRIPTlON: ACTION ITEMS: TERM , SHORTAONG: 131 SEAR No. 38 Acton # ANOMALY DESCRIPTION / IMPACT: 1) Evaluate the References secten of the Long The SSOW, Secten 1.7.7.3 4. (5012H06121) spec major DRMS Software documents to identify ifes that the software shall compty wth current changes to these references in order to make the documents consistent. Acton 8 ANOMALY DESCRIPTION / IMPACT: 2) As a result of the evaluation, prepare Short The $$CW, Secten 1.7.7.3 4, ($0123406121) spec DCNs against any major DRMS software Ifiss that the software shall compty with current document (SRS, SDO, STF, STR) that requires changes in order to make the references consistent. This work should include DCNs against the Srstem SRS (S01234061101), DU SRS ($01234061471) DU SD0 (501234061961), LPU General SDD (301234061346 0), and LPU/Applicaton STF (S01234061 3301) to incorporate the modsfcations provided in the attached MGPl response to this SEAR. Action # ANOMALY DESCRIPTION / IMPACT: 3) Aindst the MGPi software development Long The SSOW, Secten 1.7.7.3 4, (50123406121) spec process and procedu? to determine if the Ifet that the software shall comply with current development process meets the required standards for safety-related software used in nuclear power facilites 132 SEAR No. 31 Action f ANOfAALY DESCRIPTION / IMPACT: The followinp state 1) DCN must to wntten against the LPU Short ment is made in the LPU Co TrnM SRS(SO123406170 SRS (SCE Document Number 801234051701)
- 1) *A secunty funcion allows to L ck up the LPV to .3clude the revtslons as desenbed in the rttached MGPl response.
133 SEAR No. 38 Action # ANOMALY DESCRIPTION / IMPACT: A reference 6s made 1) DCN must be wnttei against the Du SRS Short 6n the DU Software Test Fue (S0123406-13471) (SCE Documer.1 Number 501234061471) to Secton 2.1; and also the DU Software Test Report ( Indude the revislons as desenbed in the attached MGPl response. I Acton 8 ANO.V ALY DESCRIPTION / IMPACT: A reference is made 2) DCN must be written against the DU SDD Short I in the DU Sofware Test File (SO12340613471) (SCE Dement Number SO123-6001981) to l Secten 2.1; and also the DU Software Test Report ( include the revisions as .teseribed in the 4 attached MGM response, j NOTE: Short4erm . Pnor to DRMS equrpment operatonsvurrover Lory-term . E's to tune ononths / rom the date of this l 1 H .10 l l l
SOFTWARE EVALUATION REPORT DOCUCENT NO 90400 REVISION 0 RECORD 8 TITLE AND DESCRIPTION: ACTION ITEMS: TERM SHORT/LONO: 134 SEAR No. 30 Aden# ANOMALY DESCellPTION / IMPACT: in Section 4.2.13, 1) DCN must be writen against the DU STF Short Test 2 of the DU Stftware Test Report (Document SO (SCE Document Number S0123406 2 3471) 1234061321 1) two of the tests were not run, Ac to include the rev6sens is described in the attached MGPl response. Acton # ANOMALY DESCRIPTION / IMPACT: In Secten 4.2.13, 2) DCN must be wrtten against the DU STR Short Test 2 of the DU Software Test Report (Document SO (SCE Document Nsmber SO1234061321 1) 12340613211)two of the tests were not run; Ac to include the revisions as described in the attached MGPl response. Action 8 ANOMALY DESCRIPTION / IMPACT:In Section 4.213, 3) The DU tests as described above must Shut Test 2 of the DU Software Test Report (Document 60 be run. 12340613211)two of the tests were not run, Ac 135 SEAR No. 40 Action # ANOMALY DESCRIPTION / IMPACT: In Section 3 8 2 of 1) DCN must be wntten against the LPU Short the LPU General SRS (S0123406-1701) the follow Common SRS (SCE Document Number ing tests are hated as compitsing the System Ouic SO12%061701) to include the revisions as descrited in the attached MOPl response. 130 SEAR No. 41 Action # ANOMALY DESCRIPTION 1 IMPACT: In Section 2.11 of 1) DCN must be written against the DU SRS Short the DU Software Test File (SO123406-13471) (SCE Document Number SO1234061471) to there is a table listing the funcbons to be tested as include the revisions as described in the attached MGPl response. Action e ANOMALY DESCRIPTION / IMPACT:In Section 2.11 of 2) DCN must be written against the DU STF Short the DU Software Test F6le (SO12340613471) (SCE Document Number SO123406-13471) there is a table hsting the functions to be tested as and DU STR (SCE Document Number S012340613471) and DU STR (SCE Document Number SO12340613211) to include the prionty test (as described in the attached MGPl response, modifed to load both RS485 links instead of just one). Acton 8 ANOMALY DESCRIPTION / IMPACT: In Section 2.11 of 3) Run the DU test as desMbed above. Short the DU Software Test File ($O123406-13471) there is a table hstmg the fundtons to be tested as NOTE: Short term . Prior to DRMS equtwnent operatonsvumover Long-term . Sh to nine months from the data of this l ! H - 11 l
_ . _ _ - . _ - _ _ _ . _ _ _ _ . _ _ _ _ _ _ _ . _ _ _ _ _ . ~ . _ SOFTWARE EVALUATION REPORT DOCUMENT NO. 90400 RIVISION 0
- MSCORDe TITLE AND DSSCRIPTION: ACTION ITSMS: TERM SNORT /LONG:
l 121 SEAR No. 42 Action # ANOMALY DESCRIPTION / NPACT: Tlem is no test in 1) DCN must be wrtmen seeinst the LPU Short i l the LPU Common Schwere Test File (8012H06130 Appleostion STF (SCE Document Number
- 21) for ownching a LPU from normal to maintenance 8012340613301) to include the I revisions es deoortted in the attached
- MOPlresponse 4
i
- f38 SEAM No. 43 Action # ANOMALY DESCRIPTION /NPACT
- 1) Centeet MOPi Attente to determine when Short The SWP process and the associated estivities/ rep the SWP Final Report wWl be outwnstied i
orts stop at the completon of the integreten To Request en outhne of the Report for , evalueton by SCE. SCE shed evbluste the content of the Report outhne to j determine whether the report wtN setofy 1 the equirements outhned in the SWP. Acuon 8 ANOMALY DESCRIPTION /NPACT: 2) SCE should audit the MOPl Atlante SWP Long i The SWP process and the estooisted actMtes/ rep and assosoleted precedures and documents orts stop at the W.a of the integreten To to ensure that the SSOW requirements have j been edeoustely addressed and setened.
- 140 SRAM No. 40 i
j Acton s ANOMALY DESCRIPTION /NPACT: 1) Propero e DCN against the DRMS System Short ; SRS (801234061 101) to incorporate the ~ in the System SRS (801234061 101), Secten 3.1. modehoottons provided in the attached MOPl response to this SEAR. l
- NOTE
- Short fenn e Prior to DMMS equ> ment operesonsvumont Long.cerm. Sin to nine monks kom the dele of this t
I 14f SEAM No. 44 ' Action 8 ANOMALY DESCRIPTION /NPACT: 1) Prepare e DCN opeinst the DRMS System Short in the System SRS (801234081 101), Socsion 3.3. SRS (801234061 101) to incorporate the 2 -The total CPU load theR not exceed 40% in - modincetions provided in the attached
- MOPi toeporee to this SEAR.
l Action # ANOMALY DESCRIPTION /NPACT: 2) SCE request that MOPl submit a Long in the System SRS (801234061 101), Secten 3.3. Suppier Deviation Report that includes A 2 - The total CPU load then not exceed 80% in the System SRS change. Includes the { 4 rationale for the change, and describes hcw sner making this change the DRMS
- software stiN setenes the SSOW requirement for sys'em expansion.
Action 8 ANOMALY DESCRIPTION /NPACT: 3) As part of the DRMS pre operstonal Short In the System SRS (80123 806-1 101), Section 3.3. testing program, SCE should record the 2 - The total CPU load shou not exceed 60% in
- worst case
- CPU loading values for each indMouel system components. These loading vclues should be considered when future enhancements or modehostens are made to the DRMS component software.
t H .12 L. . . - . . . - . - .-. - -. . - - - . - - - - . - . - - ..- . . - . . - - - . _ -._ -
SSPTWARE EVALUATION REPORT DSCUMENT NO. 90400 REvlsl0N 0 RECORDf TITLE AND DSSCRIPfl0N: ACTION fTEMS: TERM SHORTILONO: fu SSAM No. di Aehen # ANOMALY DESCRIPTION / IMPACT: 1) Propere a DCN ogemet the LPU General Short in the System SRS (8012H061 101), Seehon 3.3. 800 (8012H0814464) to incorporate the 3 - The dyneme momery ultimeten as e percente modehootone provided in the etteched MGPl response to this SEAR. 1dd SSAM No. 40 Aeten e ANOMALY DESCRIPfl0N/NPACT: 1) Propero e DCN egoinet the Schwere V4V Short The l#GP SWP (8012H061 161), Sootion 6.2, stat Tool Plan (8012H061464)to correct es tSet 'A phone Summary Report theN summettre th the document header tale closenpten as dosottled in the eleve Response eneYels. Achone ANOMALY DESCRIPTION / IMPACT: 2) Request the SW Phase Summary reports Short The MOP SWP (8012H061 161), Section 6.2, stat from MOPI Review the reports and et that *A phate Summary Report eheb oummettre th supportmg documentaten to determine if the SW program was adequate 4 completed by the MOPl software deveispment group.
. NOTE: Short-term . Prior to DRMS eMpment operetwavurwor Long-term . She to rune months ham the date of this tei SSAM No. 80 Acton 9 ANOMALY DESCRIPTION IIMPACT: There is no test in 1) DCN must te wetlan egennet the LPU/10 Short the LPU Apphcoton Software Test Report (8012H STF (SCE Document Nur. tor 0614051) of the output emulaten mode test. Ou 8012340614031) to include the revisions as desertted in the attached MGPlresponse Acten e ANOMALY DESCRIPTION I NPACT: There is no test in 2) DCN must to wrtmon epomet the LPUSO Short the LPU Mphesten Software Test Report (8012H STR (SCE Document Number 0614061) of the o/,put emulation mode test ou 8012340614261) to include the revelone as desonbod in the attached MGPiresponse 140 SSAMNo. 81 Achonv ANOMALY DESCRIPTIONINPACT: 1) Propero DCNs egennet the LPU General Short in the IEEE Standard for Software Venhostion and 800 (8012H0614464) and DU SDr.
Vehdation Plans, the need for a trocoabiley one (8012H081461)to incorporate the revoions provuled in the MOPi respones to this SEAR. Achon8 ANOMALY DESCRIPTION / NPACT: 2) Propero e DCN against the SWFR Short in the IEEE Standard for Software Verthosten and (8012H06-13674) to incorporate the Volulaten Plans, the need for a traceability one RAMSYS software traceabilty metrix when lwovided by MGPl. H - 13
4 BCFTWARE EVAL UATION REPORT ! DOCUi"ENT NO 90400 REV(blDN 0 l RECORD # TITLE AND DESCRIPTION: ACTION ITEMS: TERM l SHORT/LONG: i 1:1 SEAM No. 82 Achon # ANOMALY DESCRIPTION $MPACT: 1) Prepare a DCN agamn t.e DRMS System Short SRS (S01234061 101) to incorporate the moddications provided in the attached MGPl response to thrs SEAR. l tet SEAM No. Et ANOMALY DESCRIPTION / IMPACT: 1) Propero e DCN spelnst the DRMS System Short Achon# in the System SR$ (801234061 101), Section 3.1, SRS (801234061 101) to incorporate the 11 - Limnahon on communicatens hnks to: modrhcations provided in the attached MGPl response to this SEAR. i 100 SEAR No. S4 ANOMALY DESCRIPTION / IMPACT: 1) Prepare a DCN spainst the LPU General Short Acson 8 in the LPU General SRS (SO1234061701), Secten SRS (801234061 701) to incorporate the 2.1 - Diagram shows 2 network knks and note o modthcottons provided in the attached MGPl response to the SEAR. NOTE: Short term . Prer to DMMS equ>nent operatensVumover Long-term . Six to nine months kom the dele of this 180 SEAR No. 88
- 1) Prepare a DCN ogelnet the Du SRS Short Acton # ANOMALY DESCRIPTION / IMPACT:
In the LPU General SRS (601234061701), Secten (SO1234061471) to incorporate the 2.1 '16 measurement channels (4 main and 12 e modrhcations provided in the attached _MGPl response to this SEAR. fSt SEAR No ST
- 1) Prepare a DCN oga6nst the DU SRS Short Acton f ANOMALY DESCRIPTIONilMPACT:
in the DU SRS (SO1234061471) - Trom the PC (801234061471) to incorporate the and the MASS, the user may configure the DU ...acc modificatens provided in the attached MGPl response to this SEAR.
- 2) Recommend that SCE prepare DCNs Short Achon # ANOMALY DESCRIPTION / IMPACT:
4 in the DU SRS ($01234061471) - Trom the PC ogainst the DU SR3 (801234061471) and and the MASS, the user may configure the DU . . soc the DU General SDD (801234061 96-1) to add the information suggested by this ' SEAR, SCE to provide the avinonal information. 153 SEAR No. S8
- 1) Prepare a DCN against the DU Joneral Shurt Achon8 ANOMALY DESCRIPTIONIIMPACT:
in he System SRS (SO1234061101) *DU has 5 SD0 (SO1234061461) to incorporate the relay outputs to command ertomal alarms? No sp modthcatens provuled ln the attached MGPl response to this SEAR. H 14
SOFTWARE EVALUATlGN REPCRT DSCU"ENT NO. 90400 REVISION 0 RECORDf itTLE AND DESCRIPTION: ACTION ITEMS: TERM SHORT/LONO: fN SEAR No. 89 Acton 8 ANOMALY DESCRIPTIONINPACT: A description of th 1) DCN must be wrthen egelnet the LPU Shoft e source test function is gwn in the LPU Comnen SRS (SCE Document Numbet 80121406-1701) SMS (501234061701). However, this function is to include the rev6s6one as deserted in the attached MGPt response. 13 SEAMNo. 80 Acton 8 ANOMALY DESCRIPTION /NPACT: 1) Prepare a DCN against the DU General Sht,rt , in the System SRS (801234061 101) *DU has 1 SDD (501234061 98-1) to incorporate the
$ possible power outputs to manage *, The DU SRS ( modihostens provided in the attached MGPl tosponse to this SEAR.
Acton 8 ANOMALY DESCRIPTIONINPACT: 2) For long term DR*48 software support, Long in the System SRS (801234061 101) *DU has 1 towette the DRMS SRSs/DDs to provide ali 6 possible power outputs to manage
- The DU SRS ( informaten about a DU/LPU in a single document for each device. Eleninete multple references to many supporting documents.
N07E: Shorthem e Prw to DRMS eoulpment operatensuumont Long-term . sk to rune months from the date of this 106 SEAR No. 81 Aclen 8 ANOMALY DESCRIPTION /lMPACT: 1) Prepare a DCN agelnet the DU General short The DU SRS (5012344471) provides much detall o SDD (801234061 961) to incorporate the n the capabilites of the DU to perform logic calc modrheations provided in the attached MGPl resporse to this SEAR. Acton 8 ANOMALY DESCRIPTION 1 IMPACT: 2) Recommend that SCE prepare DCPs and Short The DU SMS (S012544471) provides much detail o modrPy the DU SRS (80123406-1471) and n the capabilites of the DU to perform logic celo the DU SDD (801234061461) to incorporate the changes identthod this SEAR. 187 SEAR No. 82 Acton # ANOMALY DESCRIPTIONINPACT: 1) Prepare a DCN apelnst the DU General Short No detailed information togardin0 the use of the 800 (801234061461) to incorporate the eviemal PC connecten with MASS software or the ex modthcotions provided in the attached MGPl response to this SEAR. H - 15
SOFTWARE EVALUATION REPOR1 DUCUMENT ND. 90400 REVislCN 0 RECORD # flTLE AND DESCRIPTION: ACTION ITEMS: TERM SHORTILONG: fSC SEAR No. 63 Action # ANOMALY DESCRIPTION / IMPACT:In the LPU 1) DCN must te wrnten against the LPU Short SRS (801234061701 Seolen 3.g.3 2)It is mentio Common SRS (SCE Document Number red that a measurement is not valed if the syttern 50"34061701) to include the revelons as deserted in the attached MGPl temponse, Action # ANOMALY DESCRIPTION / IMPACT:In the LPU 2) SCE to evaluate suitability of the Short common SRS (501234061701 Sedion 3 g.3 2) fact that only one valed reading is needed
.t is mentep ned that a measurement is not valed if the to make an average.
eystem 100 SEAR No. 64 Action # ANOMALY DESCRIPTION / IMPACT: 1) Prepare a DCN aga6nst the DU STF
- Short Even though the Du STF (5012*4061.M71) appears (SO1234061.M71) and ')U STR to test vaness MASS functions through an RS2321 (SO12340613211) to incorporate the mod 6 cations provided in the attached MGPl response to th66 SEAR.
Action # ANOMALY L ESCRIPTION / IMPACT: 2) SCE evaluate the specific needs for Long Even though the DU STF (SO1234061.M71) appears long-term support testmg needs and to test varcus MASS fur ctons through an RS2321 prepare DCNs to modh the required tests to de6cribe test equipment setup, w6 ring, test equipment use, analys6s of test resulta while considenng the test acceptance crtions. SCE re-run tests as required. NOTE: Short. term e Pnor tu DRMS equipment etnerstensvamover Long-term . Shu to nine months kom the date of this 102 SEAR No. 67 Action # ANOMALY DESCRIPTION / IMPACT: The testing of the 1) DCl4 must be wntten assinst the DU STR Short screens leled in the DU SRS (S01234061471)is (SCE Document Number 501234061321 1) incomplete, For enample, all the tests in the Vi to include the revisions as described in the attached MGPl response. Action # ANOMALY DESCRIPTION / IMPACT: The testing of the 2) Run Test 22 of Secten 4.3.2 4 h the Short ) screens Bested in the DU SRS (SO123406-1471)is DU STF (SCE Document SO1234061.M71) i incompicie. For example, all the tests in the Vi ) 107 SEAR No. 71 Amon # ANOMALY DESCRIPTION / IMPACT: 1) Prepare a DCN against the LPU General Short I No detailed information regarding the use of the e SDD (SO1234061.M6-0) to incorporate the xtemal PC connection with MASS software or the ex mod 6catens provided in the attached MGPl response to this SEAR. H 16 l
, sol'TC/ARE EVALUAT10N REPORT j DDCUMENT NO. 90400 REVISl0N 0 t RECORD # TITLE AND DESCRIPT60N: ACTION ITSMS: TEpaa SHW.*/LONO: i: 100 SEAMNo. Y2 $ e
- Aeten # ANOMALY DESCRIPTION /NPACT: 1) 9CE evaluate the spoodc needs for Long
]i No detailed informaten regardene the use of the e long-term support looting noods and r$emal PC conneoien with MASS soliwore or the es propero DCNs to mod @ the required tests to desorias how the MASS is setup to run the tests, the use of the MASS during the tests, and the use of the MASS to analyse the test results. SCE re-run tests as l required. l - 300 SEAM No. F4 4 i
~
Acton # ANOMALY DESCRIPTION /NPACT: 1) SCE request that MOPl /Jianta provide Short No testing of the entomal DAS hnk is performed I the DAS/DrW4 hnk toot. n the DRMS System integreton Test File (80123406 i i i N07E: Short-serm . Pnor to DMMS eeukoment operehensVumover Lonp-t>rm . Seu to nho months hom the date of Ns 302 SEAM No.10 4 Aden# ANOMALY DESCRIPTION / IMPACT: Operaten of 1) DCN must be wrteen agahst the DU SRS Short
- SYPASS mode is not docussed in the DU SDD (SCE Document Nutrber 801234061 101) to (801234061961), the DU STP (SO1234061.M71), include the sovisions se desertted in the or the attaued MOPl reegn,ase.
d Acton # ANOMALY DESCRIPTION / IMPACT: Operation of 2) DCN must be wntlen against the DU STF . Short SYPASS mode le not docussed in the DU 800 (SCE Document Numter 8012340613471) (801234061951), the DU STF (8012340613471), to include the revisions as descrited in or the tr.e enached MOPl response 1 Acton # ANOMALY DESCRIPT;ON / IMPACT: Operation of 3) DCN must be written against the DU STh Short SYPASS mode le not docussed in the DU SDD (. (SCE Document Numter 301234061321 1) 4
- 80123406196-1), the DU STF (8012340613471), to include the revisions as descrited in or the the attached MOPl response Acton # ANOMALY DESCRIPTION / IMPACT: Operation of 4) The DU test as desertted in 2 and 3 Short SYPASS mede is not docussed in the DU SDD - above be run.- !~ (8012$4061941), the DU STF (8012340613471),
of the 303 SEAMNo. 77 4 l Acten 8 ANOMALY DESCRIPTION / IMPACT: 1) Prepare a DCN against the LPU/ PIPS Short From the LPU General SRS (801234061701), Semi SDD (801254061971) to incorporate the on 3.1.4.1 - The LPU is able to process up to 1 modecations provided in the attached MOPi response to this SEAR. Adeon s ANOMALY DESCRIPTION / IMPACT: 2) Recommend that SCE update the Long
; From the LPU General SRS (801234061701). Sedi documents to provide accurate document l on 3.1.4.1 - The LPU is able to process up to 1 ' references and include sodions in the documents where the cierthcoton may be fou d
- H - 17 }
SOFTWARE EVALUATION REPORT DOCUMENT NO. 90400 REVISION '. . RECORD # TITLE AND DESCRIPTION: ACTION ITEMS: TERM SHORTILONG: 204 SEAR No. 70 Acton 8 ANOMALY DESCRIPTION / IMPACT: Operation of relay 1) DCN must be written against the DU SDD Short LATCH is not docussed in the DU SDD (SO1234061 (SCE Document Number SO123-606195-1) to 98 1). Include the revisions as described in the attached MGPl response. NOTE: Short-term Prbr to DRMS eyaipment operationsvumoser Lorgterm Six to nine months from the date of this 205 SEAR No. 79 Acton 8 ANOMALY DESCRIPTION / lMPACT: The test 1) DCN must be wntten against the DU STR Short (DU STR SO 12340613211 Secten 4.2.5 Tests (SCE Document Number SO123406-1321 1) 1 and 2) for buzzer acknowlerigement does not test to include the revisions as described in the attached MGPl response. Action # ANOMALY DESCRIPTION / IMPACT: The test 2) The 00 test as described above must be Short (DU STR SO 123406-1321 1 Secten 4.2.5 run. Tests 1 and 2) fa o u;cter acknowledgement does not test this cono.'.( 206 SEAR No. 80 Action 8 ANOMALY DESCRIPTION ! IMPACT: The test 1) DCN must be written against the DU STF Short P'J O *O 123406-13211 Secten 4.2.9 Test 5) (SCE Document Number SO123406-13471) Vs Miot > utput does not test the conddion of to include the revisions as described in etW/ b.7 the attached MGPl response. Acton # ANOMALY DFSCRIPTION IIMPACT: The test ( 2) DCN must be written against the DU STR Short DU STR SO 12M0613211 Section 4.2.9 Test 5) (SCE Document Number SO1234061-321 1) for analog o utput does not test the condition of to indude the revisione as described in 4 outputing the the attached MGPl response, 4 Acton 8 ANO** ALY DESCRIPTION / IMPACT: The test 3) Run Test 5 of Section 4.3.2.9 in the Short (DU T M SO 12340613211 Section 4.2.9 Test 5) DU STF (SCE Document SO123406-13471). for r alog o utput does not test the condaten of outputing the 207 SEAR No. 31 Action # ANOMALY DESCRIPTION / IMPACT: 1) SCE prepare DCNs against the LPUAO Short LPUA/O SDD (S0123406-1-346), Section 4.1.6 - CTF and LPUAO STR to indude the MGPt The modules InnMesCycle, ResultsAnalysis, Dis clartfcatens on LPUAO testing. Acton 8 ANOMALY DESCRIPTION / IMPACT: 2) SCE evaluate the SRSs/SDDs to Short LPUA/O SDD (SO123406-1346), Section 4.1.6 - determine required PT references, The modules initMesCyde, ResuttsAnalysis. De induding sections in the pts where clartfcations may be found. Prepare DCNs to update the system documents (including pts as necessary) to describe how/why the requirements erw addressed in the pts. NOTE: Short-term . Pnor to DRMS equipment operationsttumover Long-term Sbr to nine months from the date of this H - 18
SOFTWARE EVALUATION REPOri? OCCUMENT NO. 004C0.V.V!SiCN 0 RECORDf- TITLE AND DESCRIPTION: Ar,' TION ITEGRS: TERet SNORT /LONG 200 SEAM No. 82 Achon#-- ANOMALY DESCRIPTIONIlWPACT: 1) SCE propero DCNs against the LPU/SAS Short LPU/SAS SDD (80123406149-2), Section3.1.7 discu STF (80123406199-1) and LPU/SAS STn sees the opbonal extemal analog input in the L (80123406-1326 0) to include the tests and modincetior.J provided in the attached response Achon # ANOMALY DESCRIPTION /NPACT: 2) SCE tun the tests successfully prior Short LPU/SAS SDD (80123406146 2), Section3.1.7 discu to DRMS startup sees the opbonel extemal analog input. In the L i 210 SEAR No. Sd Acaion# ANOMALY DESCRIPTION / IMPACT: 1) Propero a DCN against the LPU General Short LPU Common SRS (801234061701), Section 2.1 - SDD (80123406-1 346 0) to incorporate the opbonelly equipped with 2 analog outputs with recommended modincation, 81f SEAR No. 88 3 Achon # ANOMALY DESCRIPTIONiIM*ACT: 1) SCE propero DCN against the DU SRS to Short } In the System SRS (80123406-1 101), Secten 3.3. move the DU CPU loodmg requiremenM < 3 -The dynamic memory utilisation as a percents Action 8 ANOMALY DESCRIPTION / IMPACT: 2) SCE propero DCN't against the Short in the System SRS (801234061 101), Secten 3.3.- LPU/Apphoeuon STF/STR to include the 3 - The dynamic memory utilization as a percenta provided LPU CPU loading tests. Action # ANOMALY DESCRIPTION /NPACT: 3) SCE must successfuNy execute the new Short In the System SRS (80123406-1 10-1), Sechon 3.3. LPU processorloedmg tests. 3 -The dynamic memory ubilaabon as a percenta Action e ANOMALY DESCRIPTION /NPACT: 4) SCE review the itwiividual monitor LPU Short in the System SRS (80123406-1 101), Sechon 3.3. STFs/STRs and propere DCNs to update the 3 -The dynamic memory utNaabon as a percenta ' documents with the new LPU CPU loodmg critaris. r 312 SEARNo. 80
~ Action 8 ANOMALY DESCRIPTION /NPACT: 1) SCE propero DCN against the System SRS Short in the System SRS (80123406-1 101). Sechon 3.3. (80123406110-1)to remove the DU CPU The dynamic memory utultaten as a percente load requirements (worked under SEAR 865)
Action 8 ANOMALY DESCRIPTION /NPACT: 2) SCE prepare DCN against the DU SDD Short in the System SRS (S01234061 101) Section 3.3. (SO123406-1-961) to include the DU 3 - The dynamic memory utilaston as a percenta memory string information provided in the response to this SEAR. NOTE: Shryt4erm . Pr\iorlo DRRfS equpment opernhonsuumover Long. term . Six to nine morths hem the date of this H - 19
1 SOFTWARE EVAL.UATION REP 3RT DOCUCENT NO. 90400 REVISION 0 M. RECORD # TITLE AND DESCRIPTION: ACTP3N ITEMS: TERM f.40RTILONG: 214 SEAR No. 80 Acton # ANOMALY DESCRIPTION / IMPACT: There aren1 any te 1) Ensure that the DAS/ MASS historical Short sts that venfy that the ersplayed measurements on trends match. This testing should be done all the output devices (Ch'.S. MASS. panel on DU) a during DAS Integraten testing. 216 SEAR No. 90 Acton # ANOMALY DESCRIPTION / IMPACT: 1) Prepare a DCN aganst the System SRS Short in the DRMS SSOW, Sect on 1.7.7.1.3.2 " Logic a (80123-6061 100) to incor;,arate the nd data shad be organtred as distmet modules ." recommended mod (cation. 211 SEAR No. 91 Action # ANOMALY DESCRIPTION / IMPACT: 1) Prepare a DCN against the System SRS Short in the DRMS SSOW, Section 1.7.7.1.3.2 "Communi (SO123-606-1 10-0) to incorporate the cation among programs for data or programs control recommended modrTeaten. 210 SEAR No. 92 Acton # ANOMALY DESCRIPTION / IMPACT: 1) Request that MGPl provide programming Short in the DRMS SSOW, Secten 1.7.7.1.3 4 "Esch p standards referenced in the SQAP and then rogram, subroutine, or function module shall be de SCE shall evaluate the standards to detemiine whether the SSOW requirements are met. (Complete simulaneously with SEAR #93). Ett SEAR No. 93 Action # ANOMALY DESCRIPTION / IMPACT: 1) Request that MG91 provide the Short in the DRMS SSOW,1.7.7.1.5: programming standard referenced in the SQAP, MGPt 45880, and then SCE shall evaluate the standard to Ostermine whether the SSOW requirement is met. (Completed simultaneoushr with SEAR #92). 220 SEAR No. 94 Acton # ANOMALY DESCRIPTION / IMPACT: 1) Request that MGPi provide the Short in the DRMS SSOW, Configuration and Management Plan, MGPl 110405, referenced in the SEAR response and then SCE shall evaluate the Plan to determine whether the SSOW requirement is met. (Completed simultaneously with SEAR
#52 and SEAR #93).
NOTE: Short-term . Prior tc DRMS equipment operationsVumover Long. term - Six to tune months from the date of this H -20
SOFTWARE EVALUATION REPORT DCCUMENT NO. 90400 REVISION 0 RECORD # TITLE AND DESCRIPTION: ACTION ITEMS: TERM SHORTILONO: 22f SEAR No. OS
- 1) SCE shallissue a SDR to remove the Long Acton # ANOMALY DESCRIPTION / IMPACT:
in the DRMS SSOW, Section 1.7.7.2.5: software transportabiltty requirement from the SSOW. 222 SEAR No. 96 ANOMALY DESCRIPTION / IMPACT: 1) SCE shan .ssue a SDR to remove the Long Adion # in the DRMS SSOW, Secten 1.7.7.2.5. hardward indepenoence requirement from the SSOW. 222 SEAR No. 97 Acton # ANOMALY DESCRIPTION / IMPACT: 1) SCE revtw the software modules to Short in the DRMS SSOW, Secten 1.7.7.2.5: determte what programming language used, prepare tables of software modutos versus programming language used for the modules, and prepare DCNs to incorporate the tables into the DRMS SDDs. 224 SEAR No. 96 Acton # ANOMALY DESCRIPTION 11MPACT: 1) SCE to prepare DCNs againstthe DU Short in the System SRS, Section 3.4.1 - Provides a r STS, DU SDD, and DU STFfdTR to include the oference to a real tirne clock function. However, MGPL provided informaten about how the SSOW reaLbme clock function is defined, implemented, and tested in the DU. (include leap year and century rollover tests.) Also, include the updates to Secton 5 for test performance information. Acten # ANOMALY DESCRIPTION / IMPACT: 2) SCE to prepare DCN against the IPU SDD Short in the System SRS, Secten 3.4.1 - Provides a r and LPU/ Application STF/STR to include oference to a real trne clock function. However, the MGPL provided informaten etW how the SSOW reaktime clock fuNibn b defined, implemented and lested in to LPU. (includes leap year and century rollover tests.) Achon# ANOMALY DESCRIPTION / IMPACT: 3) SCE must successfully execute the new Short in the System SRS, Secten 3.4.1 - P c mes a r leap year and century reinover tests for eierence to a real trne clock fundion. However, the DU and LPU that are provided in the new SEAR response. NOTE: ShorHerm - Prior to DRMS equtunent operationsuumont Long-term She to tune months from the date of this H 21
SOFTWARE EVALUATION REPORT DOCUMENT NO,90400 REVISION 0 RECORDf TITLE AND DESCRIPTlON: ACTION ITEMS: TERM SHORT/LONG: 226 SEAR No.100 Achon# ANOMALY DESCRIPTION / IMPACT: 1) Prepare a DCN against the DU SDD Short in the DU SRS, Section 3.3.11.3 *Once every mi (SO123406196-1) to incorporate the nute, (synchronized on the DU ekx,k), the average modrficatens provided in the attached MGPl response to tNs SEAR. Achon# ANOMALY DESCRIPTION / IMPACT: 2) Prepare a DCN against the LPU General Short in the DU SRS, Secten 3.3,11.3 "Once overy mi SDD (801234061 346-0) to incorporate the nute, (synchronsed on the DU clock), the average modificatens provided in the attached MGPl response to this SEAR. 227 SEAR No.101 Action # ANOMALY DESCRIPTION / IMPACT: 1) Prepare a DCN against the LPU General Short in the System SRS, Section 2.2 - RMS . . central SRS (SO123406-1701) to incorporate the tres all measxurements into a DAS system. In the rnodificatens provided in the attached MGPl response to this SEAR. 228 SEAR No.102 Acton 8 ANOMALY DESCRIPTION / IMPACT: 1) Prepare a DCN against the LPU General Short in the System SRS, Secten 2.4 - System has to SRS (501234061 961) to incorporate the lmplemer,t standard communisten interfaces as RS4 modem use cianfutions provided in the attached MGPl response to this SEAR. 229 SEAR No.103 Acton # ANOMALY DESCRIPTION / IMPACT: 1) Propero a DCN against the LPU General S %rt in the DRMS System SRS (S0123406-1 101) - Esc SRS (SO123406-1701) to incorporate the ten 2.2 - The MASS funcbons are listed and in rnodifications provided in the attached MGPl response to this SEAR. Acton 8 ANOMALY DESCRIPTIONiIMPACT: 2) Prepare DCNs against the LPU General Short in the DRMS System SRS (SO1234061 10-1) - Sec SRS (50123406-1101) and the LPU General ten 2.2 - The MASS funcbons are listed and in SDD (SO123 4061-346 0) regarding the use of the MASS with the LPU and to include MASS document references. 230 SEAR No.104 Action # ANOMALY DESCRIPTION / IMPACT: 1) Prepare a DCN against the DU SDD Short in the DU System SRS (SO123406147) - Section (SO1234061-96-1) to incorporate the 3.3 g - provides descriphon of DU commands, in modifications provided in the attached MGPl response to this SEAR. NOTE: Short-term Prior to DRMS equ>nent operationsttumover Long-term Six to nine months kom the date of this H -22
SOFTWARE EVALUATION REPORT DOCUMENT NO. 90400 REVl81CN 0 TITLE AND DESCRIPTION: ACTtFN ITEMS: TERM RECORDf SHORT/LONG: m 232 SEAR No.106 , ANOMALY DESCRtPTIONilMPACT: 1) Prepare DCNs against the LPU General Short Action # in the LPU General SRS (SO123406170-1)l, Secho SDD (S01234061701) and LPU General SDD n 3.2.3 6 "A security functon allows to lock (SO1234C3-1346 0) to 6ncorporate the *5 successive reboot
- modWcations provided in the attached MGPl response to this SEAR.
233 SEAR No.101 Action # ANOMALY DESCRIPTION / IMPACT: 1) Prepare DCNs against the DU SDD Short in the DU SDD, Section 2.2.1.20 - References the (SO123406196-1) DU STF
- LPU General SDD for tests cornmon to the DU and LP (SO12340613471), and DU STR (SO123406-1 321 1) to incorporate the self-tast enteria mod (catens provded in the attached MGPl response to this SEAR.
Acton # ANOMALY DESCRIPTIONiiMPACT: . 2) Prepare DCNs against the Short in the DU SDD, Secten 2.2,1.20 - References the LPU/Applicaten STF (SO123406-13301) LPU General SDD for tests common to the DU and LP and LPU! Appl 6caton STR (S01234061-305-1) to incorporate the self-test criteria modificatens provided in the attached MGPl response to this SEAR. Acton # ANOMALY DESCRIPTIONilM"ACT: 3) SCE must successfully execute the new Short in the DU SDD, Section 2.2.1.20 - References the DU and LPU self-tests prior to DRMS LPU General SDD for tests common to the DU and LP startup. 234 SEAR No.106 Acton # ANOMALY DESCRIPTION / IMPACT: 1) Prepare DCNs against the DU SDD Short in the DU SRS (SO123406-1471), Section 3.3.1.3 ($O123406-196-1) and LPU SDD
- 1f a fault in RAM, Base Software, Applicaten (SO1234061 346-0) to incoiporate the "crthcal parameter:: placing the DU/LPU into degraded mode
- criteria that has been provided in the attached MGPI response to this SEAR.
NOTE: Short-term Pnor to DRMS equipment opersbons\tumover Long-term Six to rune rnonths kom the date of this m H -23
SOFTWARE EVALUATION REPORT DOCUMENT NO. 90400 REVISION 0 RECORDf TITLE AND DESCRIPTION: ACTION ITEMS: TERM SHORT/LONG: 230 SEAR No.100 Acton f ANOMALY DESCRIPTION /NPACT: 1) Prepare DCNs against the DU STF Short in the DU SRS (S01234061471), Secten 3.3.1.3 (8012340613471) and DU STR
- 1f a faut in RAM, Base Software, Applesten (8012340613211)to incorporate the FLASH memory testing creerte that has been prov6ded in the attached MOPl response to this SEAR.
Act'on 8 ANOMALY DESCRIPTION /NPACT: 2) SCE shou perform an operability Short in the DU SRS (801234061471), Section 3.3.1.3 eseessment to determine how the lack of -
- 1f a faut in RAM, Bene Software, Appleosten FLASH memory testing under the SWP might impact the DRMS.
Acton # ANOMALY DESCRIPTION /NPACT: 3) SCE shaR successfuNy execute the new Short in the DU 6MS (801234061471), Esction 3.3.1.3 FLASH memory testa pnor to placing the
- If" a faut in RAM, Bees Software. Appimation DRMS into service.
337 SEAR No.11f
- Acton # ANOMAL) DESCRIPTION /NPACT: 1) Propero DCNs against the Short in the LPU General SRS (80123406170-1), Secten LPU/Apphosten STF (801234061300-1) 3.2.3.6 *lf a cnteel parameter faut occurs and the LPU/ Application STR (8012340613061)to incorporate the
" critical parameter fouR* creerte that has been provided in the attached MOPl response to this SEAR.
220 SEAR No, f f2 Acton 8 ANOMALY DESCRIPTIONINPACT: 1) Propero DCN ogainst the DRMS SRS Short in the DRMS SRS (801234061 101). Secten 3.1.5. (80123406110-1)to correct the 3.3 - Crtical parameters are not valid . . Dog transisten error identified in the SEAR restense. Acton 8 ANOMALY DESCRIPTION /NPACT: 2) Propero DCN against the LPU General Short in the DRMS SRS (801234061 101), Secten 3.1.5. SD0 (80123406-1346 0)to provide the 3.3 - Criticalparameters are not valid .. Deg ciertfications identitled in the SEAR response 380 SEAR No.114 Action e ANOMALY DESCRIPTION /NFACT: 1) Propero DCN ogainst the LPU/ PIPS SDD Short in the DRMS SRS (SO1234061 10-1), Secten 3.1.5. (80123 606-1471) to provide the "No 3.3 - The crtical parameters are checked perio detector fouR" cierthcotens provided in the SEAR response NOTE: Short-term . Pr\ior to ORMS equpment operationstumover Long tenn - Shr to nine months hom the date of this H -24
SOFTWARE EVALUATION REPORT DOCUMENT NO. 90400 REVisl0N 0 RECORD 8 - TITLE AND DESCRIPTION. ACTION ITEMS: TERM SHORT/LONO: 223 SEAR No.122 Achon f ANOMALY DESCRIPTION / IMPACT:.in Sechon 4.22 and 1) DCNs must be wrtiten against the Short 4.23 of the LPU STR (80123406-1306-1) two tests System SRS (SCE Document Number (powerfall and watchdog) that were specihed in th 80123406-1 101) to include the revisions , as described in the attached MOPi response. Action 8 ANOMALY DESCRIPTION / NPACT: in Seeon 4.22 and 2) DCNs must be written against the LPU Short 4.23 of the LPU STR (8012340613051) two tests Common SDD (SCE Document Number (powerfoil and watchdog) that were speelhed in th _ 801234061346-1)to include the revisions as described in the attached MOPl response Action 9 ANOMALY DESCRIPTION / NPACT:.in Section 4.22 and 3) DCNs must be written against the LPU Short 4.23 of the LPU STR (8012340613051) two tests Apphootion STF (SCE Document Number (powerfoil and watchdog) that were speciRed in th 80123406-13031)to include the revisions as desenbod in the 4.*tached MGPl response Achone ANOMALY DESCRIPTION / NPACT:.In Sechon 4.22 and 4) DCNs must be written against the LPU Short 4.23 of the LPU STR (8012340613051) two tests Apphcohon STR (SCE Document Number Covertail and watchdog) that were speelhed in th SO1234061305-1)to indude the revisions as described in the attached MGPl response, after the test has bosn run. NOTE: Short4erm . Prior to DRMS equemerst operehensttumover Long4erm . Six to nine months hom the date of this 33d SEAR No.123 A eon # ANOMALY DESCRIPTION / NPACT;.in the LPU General 1) DCN must be written against the PU Short I
- SRS (501234061701) Section 4.2 there are 5 cet Common PT (SCE Document Number egories of statuses (Hardwere Fault, Software Faul S0123406-143-2) to include the revisions as desenbod in the attached MOPl response Action # ANOMALY DESCRIPTION / NPACT:.in the LPU General 2) DCN must be written against the Short SRS (S01234061701) Sechon 4.2 there are 5 cet LPU/SAS SDO (SCE Document Number egories of statuees (Hardware Fault, Software Faul SO123406146-2) to include the revisions as described in the attached MGPl soeponse Acton8 ANCMALY DESCRPTION / NPACT:.in the LPU General 3) DCN must be written agemst the LPU/Si Short SRS (S0123406-170-1) Sechon 4.2 there are 5 cet SDD (SCE Document Number egones of statuees (Hardwate Faut, Software Faul S0123406-1 330) to include the revenons as described in the attached MGPl response Acton 8 ANOMALY DESCRIPTION / NPACT: in the LPU General 4) DCN must be wrttlen against the Short SRS (SO123406-170-1) Section 4.2 there are 5 cat LPU/SAS PT (SCE Document Number epones of statuses (Hardware Faut, Software Faul 501234061421) to include the revisions as described in the attached MGPl response H -26
SOFTWARE EVALUATICN REPORT DOCUMENT NO. 90400 REVISION 0 RECORD # TITLE AND DESCRIPTION: ACTION ITEMS: TERM SHORT/LOklG: N3 SEARNo. t17 Action # ANOMALY DECCRIPTION/ IMPACT: 1) Prepare DCN against the LPU/Si SDD Short LPU/Si SRS (SO123406-1661). Sodion 3.3.4 ($O12340613334)to provide the Before each algorithm execution the LPU checks th
- measurement validtf clarincation prov6ded in the SEAR response MS SEAR No.110 Action # ANOMALY DESCRIPTION I NPACT:. In Sedion 3.3.2 o 1) DCNs must be wrttlen against the LPU Short f the LPU General SRS (SO1234061701) t states Common SRS (SCE Document Number that the three bip po;nt '.shc3 m be etsytd $O123406-170-1) to inchxte the revisions as described in the attached MGPI response.
246 SEAR No.120 Action # ANOMALY DESCRIPTION / IMPACT:. In the Supplier Sc 1) A Supplier Deviation Report concoming Long ope of Work It is specified that "the RDU shall di the inabihty of the RDU to display all splay all monitor parameters, control these parame monitor parameters must be obtained from MGPl. 322 SEAR No.121 Action # ANOMALY DESCRIPTION / NPACT: In Section 4.2.5 of 1) DCNs must be wntion against the LPU Short the LPU General SRS (SO123406-1701) the algori PT (SCE Document Number SO123406143 2) thm status Gold is defined. This does not match to include the revisions as desenbod in the attached MGPI response Action # ANOMALY DESCRIPTION 1 NPACT: In Sechon 4.2.5 of 2) DCNs must be written against the DO Short the LPU General SRS (SO1234061701) the algort PT (SCE Document Number S0123406-144-1)
, thm status field is denned. This does not match to include the revisions as desenbod in the attached MGPl response Action # ANOMALY DESCRIPTION /NPACT: In Sechon 4.2.5 of 3) DCNs must be written against the LPU Short the LPU General SRS (SO123406-170-1) the algori SRS (SCE Document Number SO123406170-1) thm status field is denned. This does not match to include the revisions as described in the attached MGPl response.
NOTE: Short-term . Prior to DRMS equnpment operabonsvumowr Long term . Six to nine months kom the date ofit;is H -25
SOFTWARE EVALUATION REPORT DOCUMENT NO. 90400 REVISION 0 RECORD # TITLE AND DESCRIPTION: ACTION ITEMS: TERM SHORT/LONG: 326 SEAR No.125 Adeon # ANOMALY DESCRIPTION / lMPACT . This is the DU ver 1) DCN must be written against the DU SRS Short slon of SEAR #122. Once again, it appears that th (SCE Document Number SO123406-1471) to ere are two ddlerent types of power suppy testin include the revisions as described in the attached MGPl response. Action # ANOMALY DESCRIPTION / IMPACT:. This is the DU ver 2) DCN must be written against the DU SDD Short sion of SEAR #122. Once again, it appears that th (SCE Document Number S01234061961) to ere are two drflerent types of power supply testin incFJ de the revisions as described in the attached MGPl response. Acton # ANOMALY DESCRIPTIOu PACT:. This la the DU ver 3) Request DU/ Base-ITF-46704 document Short sion of SEAR #122. Once vin, R appears that th from MGPl and then translate Section 4 3. are are two drfferent types of power supply testin Evaluate test. 329 SEAR No.128 Action # ANOMALY DESCRIPTION / IMPACT: In the DU SRS ther 1) DCN must be v.
- against the DU SRS Short e is no deettssion of the maximum measurement scre (SCE Document b aer SO1234061471) to en in Secten 3.3 4.5. This screen is in the DU S include the revisions as described in tne attached MGPl response.
NOTE: Short-term Prior to DRMS equipment operations \tumover Long-term . Sa to nine rnonths from the date of this 330 SEAR No.129 Action # ANOMALY DESCRIPTION IIMPACT:.The requirement for 1) DCN must be wntten against the MASS Short parameters being saved on the DAS after changing SRS (SCE Document Number SO1234061471) by MASS is not tested. Netther is it clear what p to include the revisions as described in the attached MGPl response. Action 8 ANOMALY DESCRIPTION IIMPACT:.The requirement for 2) DAS testing must be checked to ensure Short parameters being saved on the DAS after changing proper use of parameter change counter by MASS is not tested. Nether is k clear what p (when parameters are changed via the MASS, they are uploaded to the DAS). Acbon # ANOMALY DESCRIPTION / IMPACT:.The requirement for 3) SCE procedures must be in place to Short parameters being saved on the OAS after changing change all necessary DRMS parameters using by MASS is not tested. Nether a R clear what p the MASS. H - 27
SCFTWARE EVALUATION REPCRT DOCUMENT NO. 90400 REVISION 0 RECORD # TITLE AND DESCRIPTION: ACTION ITEMS: TERM SHORT/LONG: 331 SEAst No.130 Acton # ANOMALY DESCRIPTION / IMPACT;. As demissed in th 1) DCN must be written agalnst the System Short e System SRS the DU had 3 relay outputs to command SRS (SCE Document Number check sources. Although these relay outputs exis SO123406-1 1CA) to include the revisions as described in thu attached MGPl response. Action # ANOMALY DESCRIPTION IIMPACT:. As discussed in th 2) DCN must be written arisinst the DU SRS Short e System SRS the DU had 3 relay outputs to command (SCE Document Number 6012A06-1471) to check sources. ARhough these relay outputs exis hc%de the revisions as described in the attached MGPl response, u Acton # ANOMALY DESCRIPTION / IMPACT:. As discussed in th 3) DCN must be written against the DU SDD Short e System SRS the Du had 3 relay outputs to command (SCE Document Number SO123406198-1) to check souas. Although these relay outputs exis include the revisions as described in the attached MGPl response. Action # ANOMALY DESCRIPTION 11MPACT:. As discussed in th 4) DCN must be written against the DU PT Short e System SRS the Du had 3 relay outputs to command (SCE Document Number SO123406-164-1) to check sources. Although these relay outputs exis include the revisions as described in the attached MGPl response. NOTE: Short-term . Prict to DRMS equipment operations \tumover Long-term . Six to nine months from the date of this , 332 SEAR No.131 Acticn # ANOMALY DESCRIPTIONiIMPACT: 1) SCE shall evaluate the operability of Short in the Suppler Scope of Work (SO123406-1 12 2), any monitors that are scheduled for Section 1.11.4.4 " Required minanum detectable tu never and are affected by this SEAR. Arson # ANOMALY DESCRIPTION 1 IMPACT: 2) SCE shall review and analyze the DRMS Short s in the Suppler Scope of Work (SO123406-1-12 2), algorithm documentation, including the Secten 1.11.4.4 " Required minimum detectable French *alpnthm performance specifications
- and algorithm technical manuals, to determine if the DRMS has been designed and implemented to meet the SSOW requirement for minimum detectable confidence level.
Action # ANOMALY DESCRIPTION / IMPACT: 3) SCE shall develop test Short in the Suppier Scope of Work (SO123-606-1 12-2), procedures / reports that verify that the Section 1.11.4.4 " Required minirnum detectabis DRMS meets this minimum detectable confidence level requirement at SONGS. ( Action # ANOMALY DESCRIPTIONIIMPACT: 4) After the evaluation and testing Short in the Suppler Scope of Work (S0123406-1-12 2), actrvities have been comnteted, SCE shall Sechon 1.11.4.4 " Required minimum detectable evaluate the need to update the DRMS software documentation and shall update the documents as required. NOTE: Short-term . Prior to DRMS equipment operabonstturnover Long-term . Six to none months from the date of this H -28
l 1 SOFTWARE EVALUATION REPORT DOCUMENT NO. 90400 REVISION 0 RECORDf TITLE AND DESCRIPTION: ACTION ITEMS: TERM l SHORT/LONG: ' 333 SEAR No.132 Achon # ANOMALY DESCRIPTION / IMPACT: 1) SCE shan evaluate the operabilrty of short in the Suppler Scope of Work (SO123-6061 12-2), any monitors that are scheduled for
- . Sechon 1.11.5.2 "For Iquid and gas channels turnovct and are affected by this SEAR.
Acton 8 ANOMM DESORIPTION/ IMPACT: 2) SCE shall review and analyze the DRMS Short In the Suppler Scope of Work (SO12S4061 12 2), algorithm documentation, including the Sechon 1.11.5.2 *For liquid and gas channels French *algorthm performance specifications" and algorthm technical manuals, to determnine if the DRMS has been designed and implemented to meet the SSOW requirement for gas /lquid channel 1 minute response time. Acbon # ANOMALY DESCRIPTION / IMPACT: 3) SCE shan develop test Short in the Suppher Scope of Work (SO123406-1 12 2), proceduresheports that venfy that the Secten 1.11.5.2 *For Iqub and gas channels DRMS meets gas /lequid channel 1 minute response time requnement as SONGS. Action # ANOMALY DESCRIPTION / IMPACT: 4) After the evaluation and teshng Short in the Suppler Scope of Work (SO1234061 12 2), actrvites have been completed, SCE shall Section 1,11.5.2 *For hquid and gas channels evaluate the need to update the DRMS softtvare documentation and shall update the documents as required. NOTE: Short-term . Pnor to DRMS equpment operationsvumover Long-term . Six to tune months from the date of this i l i i 1 I H -29 J
l SCFTWARE EVALUATION REPORT l DOCUMENT NO,90400 REVISION 0 l l TITLE AND DESCRIPTION: I RECORDS ACTION ITEMS: TERM SHORT/LONG: 1 l i i 334 SEAM No.133 l Actbn s ANOMALY DESCRIPTION / IMPACT: 1) SCE shan evaluate the operabilty of Short in the Sepp;ier Scope of Work (SO123-606-1 12-2), any rnonitors that are scheduled for Secten 1.11.5.3 - Yor Particulate and 1-131 c turnover and are affected by this SEAR. J Acten # ANOMALY DESCRIPTION / IMPACT: 2) SCE shan review and analyse the DRMS Short in the Suppler Scope of Work (SO123-606-1 12-2), algorithm documentaten, including the Section 1.11.5.3 "For Particulate and 1-131 c French
- algorithm performance spec 6catens* and algorithm technical manuals, to determine if the DRMS has been designed and implemented to meet the SSOW requirement for particulate /l-131 channel 15 minute response tane, Acten # ANOMALY DESCRIPTION / IMPACT: 3) SCE shall develop to.t Short in the Suppler Scope of Work (SO123 606-1 12 2), procedures / reports ti.at verify that the Section 1.11.5.3 "For Particulate and 1-131 c DRMS nwets the partculate/1 131 channel
< 15 minute response time requirement at SONGS. Acton # ANOMALY DESCRIPTION / IMPACT: 4) After the evaluation and testmg Short in the Supplier Scope of Work (SO123 606-1 12 2), activities have been completed, SCE shall Secten 1.11.5.3 "For Particulate and 1-131 e evaluate the need to update the DRMS software documentaten and shall update the documents as required. NOTE: Shorthem . Ptnt to DRMS equipment operatonsVumowr Long-term She to nine monms kom me date of Ws 4 1 4 H -30
SOFTWARE EVALUATICN REPORT D3CUMENT N0. 90400 REVISION 0 RECORDS TITLE AND DESCR!PTION: ACTION ITEMS: TERM SHORT/LONO: 336 SEAR No.134 Acton s ANOMALY DESCRIPTION / IMPACT: 1) SCE shan evaluate the operabiiny of Short in the Suppher Scope of Work (801234061 12 2), any montors that are scheduled for Section 1.11.5 4 " Response tune of every chan turnover and are aflected by this SEAR. Acton F ANOMALY DESCRIPTION / IMPACT: 2) SCE shall review and anatyre the DRMS Short in the Supplier Scope of Work (S01234061 12-2), algorithm documentation, including the Section 1.11.5.4
- Response tune of every chan French *siporthm performance spect:ations" and algotthm technical manuals, to determine if the DRMS has been desi0ned and implemented to meet the SSOW requirement for inversely proportional response tsme.
Action 8 ANOMALY DESCRIPTION / IMPACT: 3) SCE shall develop test Short in the Suppher Scope of Work (SO123406-1 12 2), procedureshoports that verWy that the Section 1.11.5 4
- Response tune of every chan DRMS meets the inversely proportional response trne requirement at SONGS.
Action # ANOMALY DESCRIPTION / IMPACT: 4) After the evaluation and testing Short in the Supplier Scope of Work (SO123406-1 12 2), activites have been completed, SCE shall Section 1,11.5.4 *Resoonse time of every chan evaluate the need to update the DRMS software documentation and shaR update the documents as required NOTE: Short term . Pnor to DRMS eouipment operabonsttumover Long term . Scr to nine anonms kom the date of Ws H - 31
SCFTWARE EVALUATION REPORT D3CUMENT NO. 90400 REVISION 0 RECORD s TITLE AND DESCRIPTION: ACTION ITEMS: TERM SHORTILONO: 336 SEAM No.135 Acton s ANOMALY DESCRIPTION / IMPACT: 1) SCE shan evaluate the operabarty of Short > In the Suppler Scope of Work, Sectson 1.11.6.2 any monitors that are scheduled for Y For process channels, deplayed activity conce tumover and are affected I;y this SEAR. Acton s ANOMALY DESCRIPTION / IMPACT: 2) SCE shan review and analyze the DRMS Short in the Suppler Scope of Work Section 1.11.6.2 algorthm documentations, including the
. For process channels, deplayed activity conce French
- algorithm performance specificatons* and algorithm technical manuals, to determine if the DRMS has been designed and implemented to meet the SSOW requirement for 25% accuracy for process channels.
Acton s ANOMALY DESCRIPTION / IMPACT: 3) SCE shall develop test Short in the Suppier Scope of Work, Section 1.11.6.2 - procedures #eports that verify that the
. For process channels, deployed activity conce DRMS meets the process channel 25%
accuracy requirement at SONGS. Acton s ANOMALY DESCRIPTION / IMPACT: 4) After the evaluation and testing Short in the Supplier Scope of Work, Section 1.11.6.2 - activities have been comieted, SCE shall For process channels, desplayed activity conce evaluate the need to update the DRMS software documentation and shall update the documents as required. NOTE: Short-term . Pnor to DRMS equipment operntoons\tumover Long-term . Six to tune months kom the date of this 337 SEAR No.136 Action # - ANOMALY DESCRIPTION / IMPACT: 1) SCE shall evatus;e the operability of Ghort i in the Supplier Scope of Work, Section 1.11.6.3 - any monstors that are scheduled for The DRMS rateten channel shall be of a nonsa tumove," and are affected this SEAP Acton # ANOMALY DESCR'PTION/ IMPACT: 2) GCE thaH review and an styze the ORMS Short in the Supplier Scope of Work, Section 1.11.6.3 algorithm documentation, including the
- The DRMS redetion channel shad be of a nonsa French
- algorithm performm.nce specificatens* and algorithm technical manuals, to determine if the LRMS has been designed and implemented to meet the SSOW requirement for nonsaturating design.
Acton s ANOMALY DESCRIPTION / IMPACT: 3) SCE shall develop test Short in the Suppler Scope of Work, Secten 1.11.6.3 - procedures / reports that verify that the "The DRMS radiation channel shall be of a nonsa DRMS meets the nonsaturating design requirement at SONGS. Action s ANOMALY DESCRIPTION / IMPACT: 4) After the evaluation and testing Short in the Suppler Scope of Work, Section 1.11.6.3 activites have been completed SCE sha:1
- The DRMS radiaten channel sha!! be of a nonsa evaluate the need to update the DRMS software documentation and shall update the documents M required.
H -32 1 _ _ _ _ _ _ _ _ _ _ _ _ l
l 1 SOFTWARE EVALUATION REPORT D@CUMENT NO. 90400 REVISION 0 RECORD # TITLE AND DESCRIPTION: ACTION ITEMS: TERM SHORT/LONG: 338 SEAR No.137 Acton # ANOMALY DESCRIPTION / IMPACT: 1) SCE should issue a SDR to remove the Short in the Suppher Scope of Work, Secten 1.7.7.3.1 ( ' database symbohc references" requirement S11B] "All real-trne scanned or calculated dat from the SSOW. 339 SEAR No.138 Acton # ANOMALY DESCRIPTION / IMPACT:.In the LPU General 1) DCN must be wrttten against the LPU Short SRS the following statements are made: *lt is poss Common SDD (SCE Document Number ible to apply a hysterisis value to the trip point S0123 6061346-0) to include the revisions as described in the attached MGPI response. NOTE: Short-term . Pnot to CRMS equipment operatensuumont Lorgterm . Sbr to nine months from the date of this 343 SEAR No. 24 Acton # ANOMALY DESCRIPTION / IMPACT: Related to 1) SCE shall evaluate the operability of Short SOW SO1234061 12. Section 1.7.4.6, which states: any monitors that are scheduwd for "Each DR MS radiaton channel shall be of a tumover and are affected by this SEAR. nonsaturating d Action s ANOMALY DESCRIPTIONAMPACT: Related to 2) SC81 shall review and analyze the DRMS Short SOW SO123406-1 12, Secten 1.7.4.6, which states: documentation, including the French
*Esch DR MS rad.ation channel aball be of a *algortthm performence spe.meations* and nonsaturating d algonthm technical manuals, to determine if the DRMS has been designed and implemented to rneet the SSOW requirement for nonsaturating design.
Action # ANOMALY DESCRIPTIONAMPACT: Related to 3) SCE shall develop test Short SOW SO123400-1 12, Seebon 1.7.4.6, which states: procedures / reports that venfy that the
*Each DR MS radiaten channel shall be of a DRMS meets this nonsaturating design nonsaturating d .Dquirernent at SONGS.
Action # ANOMALY DESCRIPTIONAMPACT: Related 4) After the evaluation and testing Short to SOW SO123-606-1 12, Secten 1.7.4.6, which states: a::tivities have been completed, SCE shall "Each DR MS radiation channel shall be of a evaluate the need to update the DRMS nonsaturating d software documentation ant shall update i the documents as required. NOTE: Short-term . Pnor to CRMS equipment operationsVurnover Lorgterm . Six to nine months from the date of this H -33
- _ _ _ _ _ _ _ _ A
4 SOFTWARE EVALUATION REPORT DOCUMENT NO. 90400 REVISION 0 RECORDS TITLE AND DESCRIPTION: ACTION ITEMS: TERM SHORT/LONG: 344 SEAR No.142 ANOMALY DESCRIPTION / IMPACT: The power-up testin 1) DCN must be wntten against the DU SRS Short Acton 9 g ts incomplete. Two specife areas are uncovered: (SCE Document Number SO1234061 101) to , include the revisions as described in the attached MGPl response. ANOMALY DESCRIPTION / IMPACT: The power up testen 2) DCN must be wrttten against the MASS Short Acton 8 g is incomplete. Two specife areas are uncovered; SRS (SCE Document Number SO1234061 18-2) to include the revisions as described in the attached MGPl response. ANOMALY DESCRIPTION / IMPACT: The power up testin 3) DCN must be wntten against the DU STF Short Acton # g is incomplete. Two specife areas are uncovered: (SCE Document Number SO1234061671) and DU STF (SCE Document Number SO123406-1-981) to include the revisions as described in the attached MGPl response. Action # ANOMALY DESCRIPTION IIMPACT: The powru, me s) Run the DU test as described in 3 Short g is incomplete. Two specife areas are uncovered: above. Action # ANOMALY DESCRIPTION / IMPACT: The power-up testin 5) DCN must be written against the LPU Short g is incomplete. Two specife areas are uncovered: STF (SCE Dopcument Number SO1234061340-1) and LPU STR (SCE Document Number SO123406-1331 1) to include the revisions as described in the attached MGPl response, and the test must be run. Action # ANOMALY DESCRIPTION / IMPACT: The power-up testin 6) Run the test as described in 5 above. Short g is incomplete. Two specific areas are uncovered. Action # ANOMALY DESCRIPTION IIMPACT: The power-up testin 7) DCN must be wrttten against the IMSS Short 4 g is incomplete. Two specific areas are uncovered. STF (SCE Document Number SO123406-1 101) and MASS STR (SCE Document Number SO123406-1-10-1) to add a test for
- missing" LPU data.
Action 8 ANOMALY DESCRIPTION IIMPACT: The power-up testin 8) Check the DAS integraten testing to Short g is incomplete. Two specrfc areas are uncovered: ensure a test has been wittten to check for" missing" LPU data. If no test exists wrtte one. NOTE: Short-term Prbeto DRMS equipment operatonsVumover Long-term Six to nine vnonths from the date of this Action s ANOMALY DESCRIPTION ilMPACT: The power-up testin g) Add an administrative control to clear Short g is incomplete. Two specific areas are uncovered: the historical memory on the DU after power outages or maintenarte mode. H - 34
SCFTWARE EVALUATION REPCRT DOCUCENT NO. P0400 REVISIGN 0 ) RECORD # TITLE AND DESCRIPTION: ACTION ITEMS: TERM SHMTILONG: 34s SEAR No.143 Acton # ANOMALY DESCRIPTION / IMPACT: There 6s a mismate 1) DCN must be written against the DU SDD Short h between the algortthms listed as being implement (SCE Document Number S01234061961) to ed in the LPU/SAS SDD (S0123406149-2) and the o include the revisions as described in the attached MOP! response.
' ction #
. ANOMALY DESCRIPTION / lMPACT: There is a mismate 2) DCN must be written against the DU STF Short h between the algorithms listed as being implernent (SCE Document Numaber SO12340613471) ed in the LPU/SAS SDD (SO123406-149-2) and the o to include the revisions as desenbod in the attached MGPl response.
Action # ANOMALY DESCRIPTION IIMPACT: There is a mismate 3) DCN must be written against the DU STR Short h between the sigorithms listed as being implement (SCE Document Number SO1234061321 1) ed in the LPU/SAS SDD (SO123406-149-2) and the o to include the revisions as described in the attached MGPl response. Action # ANOMALY DESCRIPTION / IMPACT: There is a mismate 4) Run the test as descnbod in 3 above. Short h between the algortthms listed as being implement ed in the LPU/SAS SDD (SO123406-149-2) and the o 348 SEAR No.144 Acton # ANOMALY DESCRIPTION IlMPACT: As stated in the 1) DCN must be wettten against the LPU Short SS OW; the RMS is to be designed so a can be "recati Common SRS (SCE Document Number brated.. as system operation may require? This SO1D603-1701) to include the revisions as describad in the attached MGPl response. 347 SEAR No.145 Aden# ANOMALY DESCRIPTION 1 IMPACT:The LPU/lO SRS 1) DCN must be wr'2 ten against the Short (SO123406-1471 Section 3.3) states thei the total LPullo STF (SCE Document Number analog input accuracy shah be better than 1%. In SO123406-1-303-1) to include the revisions as described in the attached MGPl response. Acton # ANOMALY DESCRIPTION / IkiPACT: The LPU/lO SRS 2) DCN must be written against the LPUllo Short (SO123406147 1 Section 3.3) states that the total STR (SCE Doc 6 ment Number analog input accuracy shau be better than 1%. In SO123406-13261) to include the revisions as described in the attached MGPl response. Adion # ANOMALY DESCRIPTION / IMPACT:The LPullO SRS 3) Run the tests as desenbod in 1 end 2 She t (SO123406-147-1 Sechon 3.3) states that the total above. analog input accuracy shau be better than 1%. In NOTE: Short-term Prior to DRMS equipment operationstrumover Long-term . Six to nine r:wnths from the date of this H -35
SOFTWARE EVALUATION REPORT DOCUMENT NO. 90400 REVISICN 0 RECORD # TITLE AND DESCRIPTION: ACTION ITEMS: TERM SelORT/LONO: 340 SEAR No.146 Acton # ANOMALY DESCRIPTION / IMPACT: The System SRS 1) DCN must be written against the DU SRS Shod (SO123406-1 10-1 Secten 2.3) states "The computer (SCE Document Number SO123406-1 101) to system (maintenance computer and supervisor) checks include the revisions as described in the attached MGPl response. Acton # ANOMALY DESCRIPTION / IMPACT: The System SRS 2) DCN must be wrttten against the MASS Short (SO1234061 101 Sedon 2.3) states "The computer SRS (SCE Document Number SO1234061 18 2) system (maintenance computer and supervisor) checks to include the revisions as described in the attached MGPl response. Action # ANOMALY DESCRIPTION / IMPACT: The System SRS 3) DCN must be written against the DU STF Short (SO123-606-1 10 1 Secten 2.3) states "The computer (SCE Document Number S012340614' i) system (maintenance computer and supervisor) checks and DU STR (SCE Docuuent Number SO123406-1961)to add a test to check that the setpoint ordonng la honored. Acton # ANOMALY DESCRIPTION / IMPACT: The System SRS 4) Run the DU test as desenbed in 3 Short (SO123406110-1 Section 2.3) states "The computer above. sy stem (maintenance computer and supervisor) checks Acton # ANOMALY DESCRIPTION / IMPACT: The System SRS 5) DCN must be written against the MASS Short (SO123406-1 101 Section 2.3) states "The computer STF (SCE Document Number SO1234061 10-1) sy stem (maintenance computer and supervisor) checks and MASS STR (SCE Document Number SO1234406-1 1010 to add a test to check that the setpoint ordering is honored. Action # ANOMALY DESCRIPTION / IMPACT: The System SRS 6) Run the MASS test as described in 5 Short (SO1234061 101 Section 2.3) states "The computer above, system (maintenance computer and suoervisor) checks 349 SEAR No.147 Acton # ANOMALY DESCRIPTION / IMPACT: There is concem th 1) Develop a V&V plan for the MASS. Short at the development of the MASS was not done under the MGPl V&V process. Since the MASS is such an i 360 SEAR No.148 Acton # ANOMALY DESCRIPTION / IMPACT: The testing 1) SCE must investigate the feasibihty Long documen tation is so sketchy that the tests are virtually of developing a detailed set of b'seline unrepeatable. Not nearty enough information is gi tests to use for future modifications. NOTE: Short-ce m - Pnor to DRMS equipment operatons\tumover Long-term . Six to nine months kom the date of this H -36
SOFTWARE EVALUATION REPORT DOCUMENT NO. 90400 REVISION 0 RECORDS TITLE AND DESCRIPTION: ACTION ITEMS: TERM SHORTttONG: 352 SEAR No.150 Acton # ANOMALY DESCRIPTION / IMPACT: 1) SCE evaluate the specFe needs for Long in the op6nion of the Revewer, most of the DRMS long-term support testeg needs and Test Flies and Test Puns do not contain specsc prepare DCNs to modify the required tests to provide the required test acceptance criteria. SCE re-run tests as required. NOTE: Short-term . Pnor to DRMS equipment operatenstumont Long-term . Six to nine rnonths from the date of this 1.- H -37
e-SOFTWARE EVALUATl8N REPORT DOCUMENT NO. 90400 REVISION 0 APPENDIX l RECOVERY PLAN l-1 D _ _ _ _ _ _ _ . _ _ _ _
SOFTWARE EVALUATION REPORT DOCUMENT NO. 90400 REVISloN 0 APPENDIX l- RECOVERY PLAN MGPl SOFTWARE EVALUATION RECOMMENDED ACTIONS
- 1.
SUMMARY
Th3 evaluation report recommended two categories of actiens that need to be addressed. Short term activities are those requiring completion prior to making the equipment operable. Activities listed in the long term category need to be completed in 9 months or less. The following table lists the activities in each category. RECOMMENDED ACTIVITIES SHORT TERM LONG TERM o SOFTWARE DOCUMENT . REVERSE CODE ENGINEERING CHANGES o SOFTWARE TESTING e DOCUMENTATION REVISION o SOFTWARE ANALYSES
- SOFTWARE MATRIX UPDATE o MASS V&V PROGRAM o SOURCE CODE COMPARISON o SDR REQUEST o ADMINISTRATIVE CONTROLS o AUDIT REQUEST The next table summarizes the estimated hours to complete the activities in each category.
ACTIVITIES HOURS , SHORT TERM (F/C 10/1/97)* 1603 LONG TERM (F/C 12/1/97)* 672 GRAND TOTAL 2275
- Forecast to Complete dates are based on retaining the existing team.
I-2
sCFTWARE EVALUATloN REPORT D0cVMENT No. 90400 REVisloN 0 I 2.3 SOF1 WARE ANALYSIS K:y system performance requirements were not adequately addressed during the software dev21opment process, 22 analyses / simulation tests need to be performed to reduce or eliminate this high risk area to SCE. ACTMTIES HOURS Define tools / procedures 40 Prepare simulation tools 80 Prepare Test procedures 48 Review & comment 24 Incorporate comments 16 issue procedures 8 Perform Testing 80 Prepare Test report 48 Review & comment 24 incorporate comments 16 lasue report 8 Total 392 2.4 MASS VERIFICATION AND VALIDATION The MASS software is being used by SCE to perform quality affecting activities. In accordance with Chapter 1J of the TQAM, the MASS must have a SV&V program implemented either by the supplier er SCE. The MASS was not developed under a SV&V program. . AC1 miles HOURS Prepare V&V Plan 48 R; view & comment 24 incorporate comments 16 lasue procedures 8 PIrform Traceability Matrix 80 a repare V&V Report 48 Review & comment 24 incorporate comments 16 issue report B Total 272 1-3
SOFTWARE EVALUATION REPORT DoCuCENT NO. 90400 REVIS10N 0 2,5 SOURCE CODE COMPARISON MGPl did not perform a traceability analysis during the development process. The evaluation team has compiled a traceability matrix that lacks one element to be complete. The source code needs to be compared, on a high level, with the software design description documents. The results enter into the SCE traceability matrix update. I ACTMTIES HOURS P rform comparison 160 Prepare matrix update 40 R:; view & comment 24 incorporate comments 16 issue update 8 Total 248 2.6 REQUEST SDRs 7 distinct SCE requirements were not met by MGPI, which require Supplier Deviation Requests to close out the issues. A letter to MGPl requesting submittal of these SDRs is needed. Draft & issue letter 16 hrs 2J ADMINISTRATIVE CONTROLS The team identified 2 areas of concern in the operation of the equipment. Management in Station Tcchnical, Operation, and Maintenance need to be notified of these concems and appropriate administrative controls applied. Draft & issue letter 16 hrs 2.8 AUDIT MGPl-SA The team noted 5 areas in the software development process that require an SCE audit MGPI-SA. A request for Nuclear Oversight to schedule and assemble the audit team needs to be made. Draft & issue lette. 16 hrs I-4
SOFTWARE EVALUATION REPORT
. DOCUMENT NO. 90400 REvlsl0N 0 4
j 3. LONG TERM ACTIONS: I-3.1 REVERSE CODE ENGINEERING Presently SCE can not validate or confirm that- MGPl source code listings and equipment prograins match, This represents a serious hole in configuration control in addition, SCE is totally dependent ! on MGPl to recover from a loss of software in the equipment. This situation is contrary to SSOW
. requirements that state SCE shall be completely independent of t:?e supplier for software
[ maintenance and operation. - Reverse code engineering resolves by,2 issues. l ACTlWTIES tlOURS Scan code listings 24 32 V;rify Scan Compile code - 16 Dcwnload Executable 16 Compare to MGPl master 16 R: solve differences 8
- Pr
- pare Test procedure 48 Rtview & comment 24 i'
incorporate comments 16
- - Issue procedures 8 Vclidation Testing ' 40 Prepare Test report 40 Rtview & comment - 24 i incorporate comments 16 issue report 8
. l Total 336
- 3.2 REVISE ALL SOFTWARE DOCUMENTS
! _ The team identified numerous problems with the documentation and recommended that they be l completely revised, i
, ACTlWTIES HOURS R; vise documents 160 Rcview A comment ,
40 4 incorporate comments 32 lasue updated matrix 8
- Total 240 i5 l
sSFTWARE EVALUATION REPORT D3cUMENT NO. 90400 REVislON 0 3,3 UPDATE TRACEABILITY MATRIX MGPl did not perform a traceability analysis during the development process. The evaluation team h:s compiled a traceability matrix. After all of the short term activities are completed the SCE traceability matrix needs to be updated to reflect the results. This will psovide an extremely powerful tool for use during NRC/OA audits and equipment operation. ACTIVITIES HOURS Pr: pare Matrix 48 R: view & comment 24 incorporate comments 16 lasue updated matrix 8 Tctal 93 I-6 l
.am m ~
Juni l July l Al 1D N**e E/1 l (gj_, l 6 M $ l E 22.l (f24 l 7/6 l 2/11 l 7/JO l 7/27 I_) d d _ 7 -u 1 SV6V Eve.',UAT]ON ACTIV!T I ES I I
-M 2 SOFTWARE DOCUMENT CHANGES { - - - -
3 Prepare DCNs ggggg:ggggg 4 IPE DCNB pQ
$ Review & Comment DCNa QKQSpyq]
6 Incorporate comments [g gregj 7 laeue DCNs g** 8 SOFTWARE TESTING 9 Prepare Test Procedures ggg 10 Review and Comment g]
'l Incorporate Comments y 12 Issue Procedures y 13 Perform Testing gg 14 Prepare Test Report g'mg 15 Review and Comment gg 16 Incorporate comments {
17 lasue R e po rt . N--- -------w------ umma 18 1:',FTWARE
. ANALYS ES 19 Define Tools / Procedures Q'{ {
20 Prepare Simulation Tools pygg?q 21 Prepare Test Procedures p'ggj 22 Review And Comment gp 23 Incorporate Comments y 24 Issue Procedures y 25 Perform Simulation / Testing { 26 Prepare Test Report 27 Review And comment 28 Incorporate Comments 29 Issue Py ort 30 MASS V&v 31 Prepara V&V Plan 32 Review And Comment 33 Incorporate Comments 34 Issue Vsv Plan 35 Perform Traceability Analysis 36 Prepare Yav Report 37 Review and Commer t Project: MGPI DRMS Sof tware
- Critical Mddd$tdd Noncritical E M N N M Progress E Datet 5/30/97 Page I m f* '"}
l kust I Lept:mbot l Octpt$f l November l% m I 1Q412 l i o/1,1 10 /26_ l 11/2 l 11/9 I 11/16 111/23 l 11/10 M/17 I 8/24 I e/ 1 I 9 /7 l 9/14 I 9/21 l 1/2e l 10/S - g i
~7 ANSTEC a APERTURE e CARD 7
Also Available on Aperture Card esame LT::MW M5M j E V _./ ED V ;
/
k can D EU l ts w ea m en WM5 LES Milestone $ summary h Rol, led Up h
-7
*'~
no Juni l . _ July l 7 _ lP_ . NJ n* 64 l ktt_,[_6/ls _ l gg2 l jd9 .I 7 d I7W l 7/.20 I . 7F I to I sh 38 Incorporat e Conments i 39 leaue V6Y poport 40 source Coot: COMPARICON 41 Feriorm Conipe rison pee.'.w.M. M .w.e. 7 ..a:mt.m..<.3 woA. e..t. a) g47" gmwM; 42 Psepare Het ris Jrdate gg 43 Review a id Coppent 44 Incorporate Comnente g
$$ Iseue tipdate 46 t DR ..t:QUfst 47 Draft Letter 48 Review and Coneent 49 Incorporate Coupents
- f.0 1scue f.etter
$) ADMIN CON 1 POLS 1,tT71.R
. . ~
, Draf t Letter
$3 Review ana Consent
$4 Incorporat e Connetit s
$$ Issue f.etter
$6 " ' " " D' Yi ' i"J " "i " " " " " " " " " " " ' S
$7 t raf t 1etter g
$8 Review and Connent l
$9 Incorporate Coneente l 60 losue f.etter j 61 ptVt:RS C CODE I:NGINFF. RING 62 Scan CodeListing 63 , verify scan 64 Compile 1 6$ Download Executable 66 corepare To MCPI Master 67 Resolve Differences 68 Prepare Test Pocedures 69 Review And Comment 70 Incorporate Connents 71 leaue Procedures 72 Validation Testing 73 Prepare test Peport 74 Review andCommerit Project: MPI DRMA sof tware .
Dats: $/30 f97 Cr!tical W3fAId.M Noncritical N E N . T M Progress 8 Page 8
..waas;
,. ~~ - . . - ~- -- -
-\
C-_~, f.eptemtwr l Octot+t_ l November l hit I fe/it I BULL.BdLL.JOALi tal I 9/2e I to/t I IN12 l ten, I 1U26.l._11d I 11/9 I11/16l11/23I11/10 E D D ANSTEC APERTURE CARD Also AvalleNc on Aperture Card V 7
% - 0 00 o 5 yl) a UTG D
IEED E 10 D IEET21 E72El IES
+ so m.ry V '7 .oii 4 up O f an.. ton.
.-gmW- MON e -- *m@ 9 + ** 4,_ ,,gre _
'**% e
.- IN
1 m av _ I u ,3 I " ur I. Z _ [D NJ3e G1 l Ug {yj{,{jggg,fjfg9.l ?/C yy,{g 7/P l 9d l 9 M) 7b Incorretate Commente l 76 leaue Deport 77 pttVIS E SOFTWAkt DOCUME N78 70 pevise Docuniente 79 Feview and Consent 80 Iticorporate concents 81 fesue Documents
$2 TPACEAS!!.17Y HATRIA DPDAft 83 Prepare Mattir 84 Daview and connent 85 Incorporate comments 86 leaus Updated Matrim a
Projset HOPI DRMS sof tware
- Datet 5/30/97 Critical fdMMWl3 Nonctitical b M Progress Page !
.~
- -- + - - - ~ ~
-- ~
_l r,+. ,r.t.., I ocw +e i Novemtie t Y ' up I anLL und u13He Lun Lwt.Lun L1uuhun Lipw I un I un L1uu Luiu L1un. D D 4 i 7 13"EIEEE"J"ZT"J LG3El (M'd~l D V 7 EET] D3 13 l ANSTEC APERTURE y CARD Also Available on Aperttere card i P
~
O - lentone h Summa ry 5 2 Rolled Up O m_ ,_ -- m e := --m- 4 -*- sn pwm w w w _. m,s m, __,-
e om. anse see i 1 , l j . . . p p p a % % v v s.a . s.' e.b f s' .c p y n - ** M @ #' #
. . N N W 9 M y , D D
** e4 N. . . . e* M > k E 5 $ $ . M.
.H e4 - -
l .H . $ n g 8 . F . f ti N. N. > >
. b c m f. c & H. & & 4 E 4
- A. E *
- k g e - o 1 . h. *.* b. .
r c e e m in m s. a v . . c . E u h E
. 4' e. * * *
- s. U p
y y e b 6 9 s' sh sa sh - - - M - e4 e4 c n ;
. C 6 $ W y - e4
.ee - . .c . .
a m . m e
. . . . . . . s.a Me. -a. . M. N. . e.4 M. e.n a . m . es
+4 M et E E E E E E p p p 5 r p p 6 p 9 E 9 -Q N
i
- b. y b N
- b. es as k >
y b b g N,
. . N. N. . . . c l' C C . e a 3, as c e a p: . gg .
a E o m a g c g .f $ .t - C ~4 -4 f. - .c4 L
. - . si 4, &
- f
- k P .L 6 0 > > c > * > c > > > b c
f . E F . F A- *
. m . m i
. m f
m . m 6 .a h c . . c . . c. t @ t C o o o k e . m . c . . x .- . c . .mc . . m e v y a c b . O l c . v . e b . 6 U V % U 5 . 5 o
$. U 5 > V 6 O. $4 b, p 4- - b- b. p p p r p - p %. e4 p =e4 %. A p- . c v c c m,. p m. in. s J. h. p
. e4
- c. -
ce . C. e e c .e C c c c , p F. c c p H.
.> c c c ,
,J c , i s . g e . c c . c c u'
, - . . - . - . m . . m.. - . - . - . - . - .
. . E. . . .
-4 g .
j e T c a m t. -c a e p m
- t. i. ,. l. lt. l. m .
a l i. t a .m m t. nm a. .ml. t f c
.m x a
- t. -m t. t. t. t. -*.t.
x = x s r m
=
- t. -*m x
t a e,"l' at. .c xt. -e a
- t. -.
x a m
- - x < a . . . .mx < r 4 4 r .
c c c c e s e c > c c c c c p
- c. c. c. t c. c.
f r e >cs: c . a.g
&. r. c t t
- c. t. c. g c. t. c. ps F. - 1 c. , t_ E e. m. e. t. h.
. o . . c. . . . e. c. t- e. 1 t- . o m s s g s> > a_ aa p % $
h V g s h a O k O t O O m o b H O D s o 6 0 0 ts 6 su & 6 m M L _ E i . . - N m w e .b . - N m w b . e . N m w n T o - N m . . . n o - N m w e . b m m m m m m m = w w w w w w w e o e e n m e n w e s c* w e4 e4 H N r4 N to r4 m N N to ** w{ l m _A.. e ho f. r r f. f f E e4 s. c4 E s= s. E r. t___a t t r. E E E F E _m_ E t E t L g g E y _r e. n L
.g
-._g- y r r
. 4 . h . . E. . .
y y r E ' C e 4 b h h 4 . . .F._ L . .y L b . I. .r . L . .t . . . F. t. . . . . . .t . b . . . . o o o o o o o o o o o o o o o ci o o o - c, c, o o o o o o o n o o o o e, o o o n o o o o c o o es o o c o o o o c o c. o o o o o o o o o m o o c> o o** m o o o o m ' ~4 c o o m m m m o o m o o o e o o o o o o o o~ o o o o o o o o o o o o o o o '~ ti< - b' .' am"N' N' N N' m.' m ." ." W
. . ' 'w'-.' . ' '." ." ." . w. ' 'G"D.' . ' '.~ ." . ' '." ." ."
.' W." .' . ' '." . ' ~*P . ' ' . '. '. ' 'w' t'P' ." N
H o" r4 e't o" w e'4'o" o" o" o N"-l e4 e4 N e4 e4 et
- e. e-H e-e4 e- r= b b t- e e- r= e- b r- r- e- e- r- 6 6 6 6 6 t- r- c- t- e- .. b b b b t- 6 P- t- b c- 6 6 6 t- b ** P. t- c- l
% P P P
% w N. c N
) .
H p ce w 0 N e4 e % s>. % k b % .% .e o e M . e4 o . m . o N . f4 % e4 e4 N m % eo ce N N e= N m e4 W N M M M M . e f4 O . N @ H b o M . W N b
% M M N e4 % %. M e4 N % N N e . e M N
@ N O . w e4 H e4 H N NNm N o N' .N. .
N N \i m N N (4 m N. o { r4 M . ib % % % % $8 % % .% .% P % % % % o o % %% ed % % % .N N. N , @ N N t-
. .N > t- t- e. .% ei .% .%. .N .N .% e e e - e4 e4 o oo d c4 e4 ee - .% r- .Ni ep .N, n e% N N n % m % % % w e
** c n .N % b e4 e4 e4 e4 H e4 e4 O O O O O O U e4 @ t e m
$ 8 E E F f F E E fi E F g g g e E
. . F. f. . . f. E. F. F. . E. F. E. E. . E. . E. E. E. . [.
t F t E F F g F g g t. f. f. . . Q
=.
F t o. of.. o1 oE- o. o. ef. o.I o. o.E L.. o. o. o. o.F o o.F o. oF. o. o.E o. o oE. o oE. o o o o o o o o o o o o o o oo o o o o D ooo o o o oer o o o m o o o o o} e o
. .o. .o o. .o.. o..o..o.. o. .o..o. .o. .o. o. .o. .o. .
O o o o. .o. o. .o. .o. - e. .o. o. o . ..o.. o..o. . H" o o.. o. o.. o.. o. .o.. o.. o. .o.. o..o. .o..o.. o.. o.. o.. o. .o. . o.. o. o. ..
. . o e o
~ m .o . . . . . . . . . . . . . .. . . . .o . . . . .o . . . . . . .o . . . . . . . . .o .o . . . . . . .o N . . r ,o
~ ~
1
)g $ $ r-$ $
r- c- e. e- e- e- e e-
$ $ $$ $ $ $. $r4 $,
t- e- c- e- e- 3 e-
$ $ .$. e$$
t- e- e- e- e- o t- e e- t- 6 c. e= e- e- c. e. e- e- e- p- 6 6 c- e- o e- e- e- e-
$ $$ b$ $ $$$$$ $$ $$$ $$$$ $$$$ $$ $ $ $. $ $
e- c- 6 6 e e-m m e n t- e-e o k k"$ l ( e4 o e w $. o a c4 e4 o w . e m 4 c4 m wN N w e o e e mm N n w e t- m . H e< o b m # e c N ., f4 m o o N
=. % % % r4 % e4 e4 r4 c4 e ce c4 N % , c4 e4 N % e4 H % % m e4 e4 N N N N f4 (4 NN y' c4 % % N % m % b% % e4 ee c4 N m % e N. % % N N N % o o % % % H %. % t" t- % .% % % % %, N NN N N m m N' N w w % % . b % % % % % as b e-v w t-b b t- b t- N. .
t-t- %.. % .% > . s e e s > m m o co o e4 NH e4 H H M M t- %. .% v %. c c c c c c e c c % O
%w M
g
~ ,
' Nc c c r c c c z c e c c c x x c c c c c e c a c c xc c a c c c a c x c x e c x n .sd e
.c c c w N x
w N e* - e.
- e A. . n, . w e c. b o e w ci e c. o . x.ew . o ., c. # c. c. v e x. No ow Ne # . Nw .
- e4 r4 wN .c w n N m m
.r vi
- v. e4 n. N e r4 w m . . N e4 , w et c. e w .o = N . w N s N N c. .o
- N - e-e.
s 8 j
% o . n e4 N w m N c l b $
e p > c m - e.4
. . e m. a m
c
. . o 6 4 y .
e u p e a u o n p H 'p a
- m m > m a a e a e a y e m y M m.sa +c> g a c sa
- v. c v
sa v c c g e c a e e c .e4 a c E c v. a c y c p c se M g C c o c b c o oA 'e if c ,i e4 1>. c v o c . % a > c n < > h c- W > p g e i, c u
's o
- e. p .n ; .s a,
-4 a n.
, m.
h u. m.i:.
.,s i;
,. e. .g ,
i-
. 'c
,s
- o
- c. 6. .< ,
?' l 3
) o 8 w "m m y .' .
3 o
,l l ,
9 a o wcm A . > e. ;
. .- . O f3 ,
a 9 0 g 4 e x.4 g y a y
& 4 0 . e.
- U , V 9 O s -
se u 9 U $ N-# a
) O p -
ss U O O's U v v Q .,uu . ,. v k A u.u . e%. k V U C1 =e > . Q v. U . 11 s.a . e.. - i! e. ,u . *.v F m . t > . e.4 . , O %. . . . ev o e y e. . m. y o - e - - . v n . u . . v o . e , s o e , , < p 0 9 . b e e a. c a om e a m e c e. > c a. > p > > U p r s . p p s. .; Pn .s
.c
. w .n g e < m .E .c .c .I " u . " . .c .
3c lw< m - g . w < w < ~ ,. .
" d 3 E3
.a l c E. t.t E g > go -
E bt E, ,. R e e
., ,. t. -! Eo '.n E o t. . E,.
, . ". Eo t. ,. E "., ,
E, ".E t. E
- t. . . mo a - mo .r t
o t. ,. m . D ot E.", . , t E... g .~t .,
< m.a m
v ,, v e n - o > u - m . - . n O m n
- - n o - U .
W . > 0 m ** . n ou ,t -, -e n C a
,. m , e h a. > v e . u . . > . m b . > U e w b > i e @- > e .?.
Ja t . M r w. s ~ a -
~ a,s i t u 8 -
m . u . c m
<. a. m. - -
w w 8 a. n u. - m.. u . c m >
- ss w - - , .u. .t. - ue m . m . c .
s s a - - v u. s ,. . - - m s .e.. o . e. - m w h O j m b g g p O o . o m o m o p ai m m m E 4
>=e
.t > j Rm n +
O , o c4N m w c . r- . e o - N d w n e e- . e o ce N e, e c # e- . e o N e c . e- . , o - ,, , ., d.o , ' ,,
,. ,n , , n . n , - - - - - - - - - - N N N N N N N N N N m m m m m m mm m m , w m, w w w w w w _ . . ,
3 es %
. - . . . . ~ . _ _ _ _
m -
1l i!I)lli1 ll li' i e M e s u e t e K t d M e n e e l e v s r s e u e u t e K M F S. M a s e e e v o v 9 s e e 1 u e e P. a t S, _e! ss dd e d-
- M s a d-t S, t h
t N e t l ~ n a M a e M - t t w t vs t l e e e e s s e e t e ee e W e s s s s u e u u u K F u s s u u l e r l r S e *h_ , gi l n K F M K e e K E e e M s y i m s e e e e v v v v v e e e e e t t v e a e v v e e n W i a = i m e m s n e _agg r e e t t J, dn S, S, t t S. S, t t S e c P,
- P, _ _t h,
- S, S, t t t S, S, u P, t l D, l t _ce 1 t - n e n n n n t n t t n n s n t l n l t n s 1 t i s i i i i e i e e i i e i e e i a e i e 1 e - t c tt t t l t l l t t P t l W t P l t B F 1 r E rr r r : r t r r r r z r z r !
e a s a e 9 ae e a a s a a n e n s e s n s W F e 's M M F 9 MF s P M i t n M F i m F i
=
M F i n m i w n n n n n n = n m m
- n n n = s o
- s w n n s m e e e e e e e e e e e a e a e e e e a
&,tS ' e i e e I S B 9 I1 i B P P P P P P P D B P J B J P B D J P 5 D2f)4m0 2 3 4 5 6 7 9 9 0 1 2 3 4 5 9 9 0 3 4 h t 6 6 6 i 6 6 Ii 6 6 l i 6 7 7 7 7 tI 7 7 7 7 9 tl 9 9 8 l 6 f-
%:=i
=l
- a m = m - m m a a = m n m
- m = m = m m = = = e
- 0 0
e e e e e e e e 0 0 0 0 0 0 0 0 0 0 0 0 0 0 e ne e e e e e a e a e e p 0 00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0: 0 0 0 0 0 0 0 p s p p 0 0 0 0 0 0 0 0 Tm24C3m - O>3Q 9 9 9 9 9 9 9 9 9 9 9 8 9 8 9 9 8 9 9 9 9 4 4 9 4 4 u 7 7 7 0 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 1 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9
- / / / / / / / / / / / / / / / / / / / / / / / / / / -
1 5 2 7 9 3 4 2 7 9 0 6 3 9 0 1 3 6 4 1 3 23 7 1 2 f n2 2 / / / 1 1 2 2 r / / 0 0 0 / / / / 2 3 / 1 1 2 2 / 1
/ / 1 / / / / 0 /
2
/
/ /
0 0 g1/ 1
/ / /
2 2 e8 >6iE$=
- 1 , 1 9 1 1 1 0 00 1
t 1 t! 1 1 1 tI 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 9 9 1 1 00 1 1 0 0 0 1 1 1 J 415* D& . 3 l
- a ml - !i * = m = m 9 = = m m m r = m , m a
m
- m a p e as m m e e e
=
-,- 0a 0 0 0 0 0a 0a 0a 0a 0e 0e 0a 0a 0e 0e 0e 0e 0s e e e e 0 0 0 00 0 0 0 0 0 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 0 0 0
- : : - : : : : 0: 0: 0: : : 0: : - : : - : : : :
w 9 9' 9 9 9 9 9 9 9 9 9 9 9 9 9 9 8 9 9 9 9 9 8 9 9 7 ~ 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 r, 79 9 9 9 9 9 9 9 9 9 9 9 9 9 9
- 9 9 9 9 9 9 99 9 9 1 / / / / / / / / / / / / / / / / / / / / / /4 // / /
2
- 2 2 6 3 7 9 3 4 2 7 9 0 6 3 9 0 9 9 7 5 2 4 4 9 2 2 2 / / / 1 1 2 2 2 3 / 1 1 2 1 1 1 2 / / / 1 1 2 9 / / /0 0 C / / / / / /1 / / / / / / / 0 0 0 / / /
9 9 9 1 1 I 0 0 0 0 0 0 1 1 1 1 9 F 9 9 1 1 1 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 s li i : - t h hh h h h h hh h h 5 5 h h h h h h h h h h h h ah44 4 2 3 26 1 6 1 1 6 9 9 4 4 4 2 1 9 c 0 4 6 8 6 C 0 2 t 6 8 4 6 S e 4 2 1 5 6 4 3 9 4 2 1 3 2 1 i : !ii iij1 i i r s E S T e e T A sr G t r s s N s D N e s s a t t t E t P t i I l e e d t n g r n t n U t e r \ R n o t e M n t EE -n r bM c a t I e n ce n_ o -. s si e t e- m p n U s - C t s II n. s P ' d h On v
*r a : P r P c r s 9 -. o w t t x \
O I t e e m C u e C De v C n 1T i -_ C d t E mc r O e C r e 'v E i.n s l a c M x E o i f f ts C e e e d t c n e d t o 9 d T t c s c e r u c e m A t u M a t d t e t e a ( u T n s o io T n a p W A o M a c Y P n a d
! de Se d T D A r r a r a D e r o T a r p A O O o e a e e e o P t e oPT o D I e o U C yl o r v ra we rp e da rawe rp e OF es we p r e L r
a w e p r e e C f i l l S i i I u E n i p n t o p i o u i p i o u o u B p i o u r e w ms e v c s l e v c s E v v c s A er v c s S a s e n s n s E s?E eS ev Co oD Co Fe i r e n s a r e n s S e e P F I I v P F I I 1 F F I I C P M I I V v A P E E P p T 1'
- 1 2 3 4 5 6 7 9 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
= 6 6 6 6 6 6 6 6 6 7 7 7 7 7 7 7 7 7 1 9 8 3 9 9 9 8
~
II"
)
- i. ,i
,t ;3 j jf,j fIl \
,! . lt1}}