IE$E Standard

IEEE Standard Requirements for
STANDARDS
Reliability Analysis in the Design
and Operation of Safety Systems for
Nuclear Power Generating Stations
and Other Nuclear Facilities
IEEE Power and Energy Society
Developed by the
Nuclear Power Engineering Committee
IEEE Std 577™-2022

(Revision of IEEE Std 577-2012)
Authorized licensed use limited to: University of Central Lancashire. Downloaded on March 17,2023 at 08:42:42 UTC from IEEE Xplore. Restrictions apply.
IEEE Std 577™-2022
(Revision of IEEE Std 577-2012)

Developed by the
Nuclear Power Engineering Committee

of the
IEEE Power and Energy Society
Approved 9 February 2022
IEEE SA Standards Board
Abstract: The minimum acceptable requirements for the performance of reliability analyses for
safety systems when used to address the reliability considerations discussed in industry standards
and guidelines are set forth in this standard. The requirement that a reliability analysis be performed
does not originate with this standard. However, when reliability analysis is used to demonstrate
compliance with reliability requirements, this standard describes an acceptable response to the
requirements.
Keywords: IEEE 577™, nuclear facilities, reliability analysis, safety systems
The Institute of Electrical and Electronics Engineers, Inc.

3 Park Avenue, New York, NY 10016-5997, USA
Copyright © 2022 by The Institute of Electrical and Electronics Engineers, Inc.

All rights reserved. Published 22 April 2022. Printed in the United States of America.
IEEE is a registered trademark in the U.S. Patent & Trademark Office, owned by The Institute of Electrical and Electronics Engineers,
Incorporated.
PDF: ISBN 978-1-5044-8448-0 STD25250

Print: ISBN 978-1-5044-8449-7 STDPD25250
IEEE prohibits discrimination, harassment, and bullying.

For more information, visit https://www.ieee.org/about/corporate/governance/p9-26.html.
No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission
of the publisher.
Important Notices and Disclaimers Concerning IEEE Standards Documents
IEEE Standards documents are made available for use subject to important notices and legal disclaimers.
These notices and disclaimers, or a reference to this page (https://standards.ieee.org/ipr/disclaimers.html),
appear in all standards and may be found under the heading “Important Notices and Disclaimers Concerning
IEEE Standards Documents.”
Notice and Disclaimer of Liability Concerning the Use of IEEE Standards

Documents
IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating
Committees of the IEEE Standards Association (IEEE SA) Standards Board. IEEE develops its standards
through an accredited consensus development process, which brings together volunteers representing varied
viewpoints and interests to achieve the final product. IEEE Standards are documents developed by volunteers
with scientific, academic, and industry-based expertise in technical working groups. Volunteers are not
necessarily members of IEEE or IEEE SA, and participate without compensation from IEEE. While IEEE
administers the process and establishes rules to promote fairness in the consensus development process, IEEE
does not independently evaluate, test, or verify the accuracy of any of the information or the soundness of any
judgments contained in its standards.
IEEE makes no warranties or representations concerning its standards, and expressly disclaims all warranties,
express or implied, concerning this standard, including but not limited to the warranties of merchantability,
fitness for a particular purpose and non-infringement. In addition, IEEE does not warrant or represent that the
use of the material contained in its standards is free from patent infringement. IEEE standards documents are
supplied “AS IS” and “WITH ALL FAULTS.”
Use of an IEEE standard is wholly voluntary. The existence of an IEEE Standard does not imply that there
are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to
the scope of the IEEE standard. Furthermore, the viewpoint expressed at the time a standard is approved and
issued is subject to change brought about through developments in the state of the art and comments received
from users of the standard.
In publishing and making its standards available, IEEE is not suggesting or rendering professional or other
services for, or on behalf of, any person or entity, nor is IEEE undertaking to perform any duty owed by any
other person or entity to another. Any person utilizing any IEEE Standards document, should rely upon his or
her own independent judgment in the exercise of reasonable care in any given circumstances or, as appropriate,
seek the advice of a competent professional in determining the appropriateness of a given IEEE standard.
IN NO EVENT SHALL IEEE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO: THE
NEED TO PROCURE SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE PUBLICATION, USE OF, OR RELIANCE
UPON ANY STANDARD, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE AND
REGARDLESS OF WHETHER SUCH DAMAGE WAS FORESEEABLE.
Translations
The IEEE consensus development process involves the review of documents in English only. In the event that
an IEEE standard is translated, only the English version published by IEEE is the approved IEEE standard.
3
Copyright © 2022 IEEE. All rights reserved.
Official statements
A statement, written or oral, that is not processed in accordance with the IEEE SA Standards Board Operations
Manual shall not be considered or inferred to be the official position of IEEE or any of its committees and shall
not be considered to be, nor be relied upon as, a formal position of IEEE. At lectures, symposia, seminars,
or educational courses, an individual presenting information on IEEE standards shall make it clear that the
presenter’s views should be considered the personal views of that individual rather than the formal position of
IEEE, IEEE SA, the Standards Committee, or the Working Group.
Comments on standards
Comments for revision of IEEE Standards documents are welcome from any interested party, regardless of
membership affiliation with IEEE or IEEE SA. However, IEEE does not provide interpretations, consulting
information, or advice pertaining to IEEE Standards documents.
Suggestions for changes in documents should be in the form of a proposed change of text, together with
appropriate supporting comments. Since IEEE standards represent a consensus of concerned interests, it is
important that any responses to comments and questions also receive the concurrence of a balance of interests.
For this reason, IEEE and the members of its Societies and Standards Coordinating Committees are not able to
provide an instant response to comments, or questions except in those cases where the matter has previously
been addressed. For the same reason, IEEE does not respond to interpretation requests. Any person who would
like to participate in evaluating comments or in revisions to an IEEE standard is welcome to join the relevant
IEEE working group. You can indicate interest in a working group using the Interests tab in the Manage Profile
and Interests area of the IEEE SA myProject system.1 An IEEE Account is needed to access the application.
Comments on standards should be submitted using the Contact Us form.2
Laws and regulations
Users of IEEE Standards documents should consult all applicable laws and regulations. Compliance with
the provisions of any IEEE Standards document does not constitute compliance to any applicable regulatory
requirements. Implementers of the standard are responsible for observing or referring to the applicable
regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in
compliance with applicable laws, and these documents may not be construed as doing so.
Data privacy
Users of IEEE Standards documents should evaluate the standards for considerations of data privacy and
data ownership in the context of assessing and using the standards in compliance with applicable laws and
regulations.
Copyrights
IEEE draft and approved standards are copyrighted by IEEE under US and international copyright laws. They
are made available by IEEE and are adopted for a wide variety of both public and private uses. These include
both use, by reference, in laws and regulations, and use in private self-regulation, standardization, and the
promotion of engineering practices and methods. By making these documents available for use and adoption
by public authorities and private users, IEEE does not waive any rights in copyright to the documents.
1
Available at: https://development.standards.ieee.org/myproject-web/public/view.html#landing.
2
Available at: https://standards.ieee.org/content/ieee-standards/en/about/contact/index.html.
4
Photocopies
Subject to payment of the appropriate licensing fees, IEEE will grant users a limited, non-exclusive license to
photocopy portions of any individual standard for company or organizational internal use or individual, non-
commercial use only. To arrange for payment of licensing fees, please contact Copyright Clearance Center,
Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; +1 978 750 8400; https://www.copyright
.com/. Permission to photocopy portions of any individual standard for educational classroom use can also be
obtained through the Copyright Clearance Center.
Updating of IEEE Standards documents
Users of IEEE Standards documents should be aware that these documents may be superseded at any time
by the issuance of new editions or may be amended from time to time through the issuance of amendments,
corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the
document together with any amendments, corrigenda, or errata then in effect.
Every IEEE standard is subjected to review at least every 10 years. When a document is more than 10 years old
and has not undergone a revision process, it is reasonable to conclude that its contents, although still of some
value, do not wholly reflect the present state of the art. Users are cautioned to check to determine that they have
the latest edition of any IEEE standard.
In order to determine whether a given document is the current edition and whether it has been amended through
the issuance of amendments, corrigenda, or errata, visit IEEE Xplore or contact IEEE.3 For more information
about the IEEE SA or IEEE’s standards development process, visit the IEEE SA Website.
Errata
Errata, if any, for all IEEE standards can be accessed on the IEEE SA Website.4 Search for standard number and
year of approval to access the web page of the published standard. Errata links are located under the Additional
Resources Details section. Errata are also available in IEEE Xplore. Users are encouraged to periodically
check for errata.
Patents
IEEE Standards are developed in compliance with the IEEE SA Patent Policy.5
Attention is called to the possibility that implementation of this standard may require use of subject matter
covered by patent rights. By publication of this standard, no position is taken by the IEEE with respect to the
existence or validity of any patent rights in connection therewith. If a patent holder or patent applicant has
filed a statement of assurance via an Accepted Letter of Assurance, then the statement is listed on the IEEE
SA Website at https://standards.ieee.org/about/sasb/patcom/patents.html. Letters of Assurance may indicate
whether the Submitter is willing or unwilling to grant licenses under patent rights without compensation
or under reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfair
discrimination to applicants desiring to obtain such licenses.
Essential Patent Claims may exist for which a Letter of Assurance has not been received. The IEEE is not
responsible for identifying Essential Patent Claims for which a license may be required, for conducting inquiries
into the legal validity or scope of Patents Claims, or determining whether any licensing terms or conditions
provided in connection with submission of a Letter of Assurance, if any, or in any licensing agreements are
3
Available at: https://ieeexplore.ieee.org/browse/standards/collection/ieee.
4
Available at: https://standards.ieee.org/standard/index.html.
5
Available at: https://standards.ieee.org/about/sasb/patcom/materials.html.
5
reasonable or non-discriminatory. Users of this standard are expressly advised that determination of the
validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility.
Further information may be obtained from the IEEE Standards Association.
IMPORTANT NOTICE
IEEE Standards do not guarantee or ensure safety, security, health, or environmental protection, or ensure against
interference with or from other devices or networks. IEEE Standards development activities consider research
and information presented to the standards development group in developing any safety recommendations.
Other information about safety practices, changes in technology or technology implementation, or impact
by peripheral systems also may be pertinent to safety considerations during implementation of the standard.
Implementers and users of IEEE Standards documents are responsible for determining and complying with
all appropriate safety, security, environmental, health, and interference protection practices and all applicable
laws and regulations.
6
Participants
At the time this IEEE standard was completed, the Reliability Working Group had the following membership:
Khoi Nguyen, Chair

George Ballassi, Vice Chair
John Beatty Kirklyn Melson Philip Ward

Tom Crawford Ed Mohtashemi Khadijah West
Jacob Kulangara Clint Pierce Yvonne Williams
James Liming Kiang Zee
At the time this standard was completed, Subcommittee 3 (Operations, Maintenance, Aging, Testing, and
Reliability) (SC-3) of the Nuclear Power Engineering Committee had the following membership:
Tom Crawford, Chair

Rebecca Steinman, Vice Chair
George A. Ballassi James K. Liming Philip Ward

John Beatty Kirklyn Melson Khadijah West
Suresh Channarasappa Ed Mohtashemi Yvonne Williams
Jacob Kulangara Khoi Nguyen Kiang Zee
Clint Pierce
At the time this recommended practice was completed, the Nuclear Power Engineering Committee (NPEC)
had the following membership:
John White, Chair

Mark Bowman, Vice Chair
Robert Konnik, Secretary
Michiaki Akiyama Jason Gasque Edward Mohtashemi

Rufino Ayala Dale T. Goodney Warren Odess-Gillett
George A. Ballassi Daryl Harmon Gene Poletto
John Beatty David Herrell Iftikhar Rana
Jason Bellamy Ayodele Ishola-Salawu Mitchell Staskiewicz
Keith Bush Gary Johnson Richard Stattel
Suresh Channarasappa Wolfgang Koenig Rebecca Steinman
Jonathan Cornelius Thomas Koshy Marek Tengler
Tom Crawford Jacob Kulangara Sudhir Thakur
David Desaulniers Chris Lamb Masafumi Utsumi
John Disosway J.Scott Malcolm Yvonne Williams
Stephen Fleger Singh Matharu Tamatha Womack
Kenneth Fleischer Kenneth Miller Richard Wood
The following members of the individual Standards Association balloting group voted on this standard.
Balloters may have voted for approval, disapproval, or abstention.
S Aggarwal Stephen Fleger Robert Konnik

Robert Aiello James Gleason Thomas Koshy
George Ballassi Dale Goodney Jacob Kulangara
John Beatty David Herrell Mikhail Lagoda
Jason Bellamy Lee Herron Benjamin Lanz
Suresh Channarasappa Werner Hoelzl Tapan Manna
Neal Dowling Yuri Khersonsky Andrew Nack
7
Khoi Nguyen Jan Pirrong Rebecca Steinman
Warren Odess-Gillett Bartien Sayogo John Vergis
James Parello P. Sivaraman Yvonne Williams
Bansi Patel Kiang Zee
When the IEEE SA Standards Board approved this standard on 9 February 2022, it had the following
membership:
Gary Hoffman, Chair

Vacant Position, Vice Chair
John D. Kulick, Past Chair
Konstantinos Karachalios, Secretary
Edward A. Addy Howard Li Mehmet Ulema

Doug Edwards Daozhuang Lin Lei Wang
Ramy Ahmed Fathy Kevin Lu F.Keith Waters
J.Travis Griffith Daleep C. Mohla Karl Weber
Thomas Koshy Chenhui Niu Sha Wei
Joseph L. Koepfinger* Damir Novosel Howard Wolfman
David J. Law Annette Reilly Daidi Zhong
Dorothy Stanley
*Member Emeritus
8
Introduction
This introduction is not part of IEEE Std 577-2022, IEEE Standard Requirements for Reliability Analysis in the Design
and Operation of Safety Systems for Nuclear Power Generating Stations and Other Nuclear Facilities.
This standard was first published in 1976 to standardize the application of reliability techniques in the design
and operation of nuclear power generating station and nuclear facilities. This standard is intended for nuclear
generating stations and other facilities related to the nuclear fuel cycle, from fuel processing to reprocessing
and waste facilities, all referred to as “facilities” in this standard. The standard was revised in 2004 to delete
obsolete information, and to update the standard to current references and practices within the nuclear industry.
The 2012 revision was prepared to continue the updating of the standard to current references and practices
within the nuclear industry, and to conform to the revised style manual and formatting for standards. The
standard is directed towards those systems in the nuclear facility that perform protective functions and fall
within the scope of IEEE Std 603™ and IEEE Std 308™. However, the requirements of this standard may be
applied to other systems within a nuclear facility if appropriate. This standard may also be used as a guide to
establish periodic testing programs.
— IEEE Std 352™ supplements this standard by providing guidance in the application of reliability

techniques.
— IEEE Std 338™ requires that programs are established for periodic testing that are based, in part, upon
the minimum acceptable analyses described in this standard.
This revision has been prepared to change the title, clarify definitions, update references and bibliography, and
other minor clarifications. This revision also has modified the wording (previously applicable only to nuclear
power generating stations) to reflect its use for other nuclear facilities as well.
Reliability analysis is a method that can be used to demonstrate compliance with reliability requirements
stated in industry standards and guidelines. When reliability analysis is used for this purpose, this standard
describes an acceptable response to the requirements. The requirement that a reliability analysis is performed
does not originate with this standard.
IEEE Std 379™ [B8] describes the application of the single-failure criterion.6
6
The numbers in brackets correspond to those of the Bibliography in Annex A.
9
Contents
1. Overview�� 11
1.1 Scope�� 11
1.2 Purpose�� 11
1.3 Word usage�� 12
2. Normative references�� 12
3. Definitions,�� 12
4. Requirements�� 13
4.1 General�� 13
4.2 Qualitative analysis�� 13
4.3 Quantitative analysis�� 14
4.4 Evaluation�� 16
Annex A (informative) Bibliography�� 17
10
1. Overview
1.1 Scope
This standard sets forth the acceptable and minimum requirements for the performance of reliability analyses
for safety systems when used to address the reliability considerations discussed in industry standards and
guidelines.
The methods of this standard may also be applied to other systems, including the interactions, if any, between
safety and non-safety systems. The requirements should be applied during the phases of design, fabrication,
testing, maintenance, and repair of systems and components in nuclear power generating stations and other
nuclear facilities. The timing of the analysis depends upon the purpose for which the analysis is performed.
This standard applies to the facility owner and other organizations responsible for the activities previously
stated.
1.2 Purpose
The purpose of this standard is to provide uniform, minimum, acceptable requirements for the performance of
reliability analyses for safety systems found in nuclear facilities, but not to define the need for an analysis. The
need for reliability analysis has been identified in other standards (e.g., IEEE Std 379™ [B8], which describes
the application of the single-failure criterion).
IEEE Std 352™ provides guidance in the application and use of reliability techniques referred to in this
standard.
11
IEEE Std 577-2022
IEEE Standard Requirements for Reliability Analysis in the Design and Operation of Safety
Systems for Nuclear Power Generating Stations and Other Nuclear Facilities
1.3 Word usage

The word shall indicates mandatory requirements strictly to be followed in order to conform to the standard
and from which no deviation is permitted (shall equals is required to).7,8
The word should indicates that among several possibilities one is recommended as particularly suitable,
without mentioning or excluding others; or that a certain course of action is preferred but not necessarily
required (should equals is recommended that).
The word may is used to indicate a course of action permissible within the limits of the standard (may equals
is permitted to).
The word can is used for statements of possibility and capability, whether material, physical, or causal (can
equals is able to).
2. Normative references

The following referenced documents are indispensable for the application of this document (i.e., they must
be understood and used, so each referenced document is cited in text and its relationship to this document is
explained). For dated references, only the edition cited applies. For undated references, the latest edition of the
referenced document (including any amendments or corrigenda) applies.
IEEE Std 338™, IEEE Standard for Criteria for the Periodic Surveillance Testing of Nuclear Power Generating
Station Safety Systems.9,10
IEEE Std 352™, IEEE Guide for General Principles of Reliability Analysis of Nuclear Power Generating
Station Systems and Other Nuclear Facilities.
3. Definitions,
For the purposes of this document, the following terms and definitions apply. The IEEE Standards Dictionary
Online should be consulted for terms not defined in this clause. 11
availability: The probability that an item or system will be operational on demand.
reliability: The characteristic of an item or system expressed by the probability that it will perform a required
mission under stated conditions for a stated mission time.
7
The use of the word must is deprecated and cannot be used when stating mandatory requirements; must is used only to describe
unavoidable situations.
8
The use of will is deprecated and cannot be used when stating mandatory requirements; will is only used in statements of fact.
9
The IEEE standards or products referred to in Clause 2 are trademarks owned by The Institute of Electrical and Electronics Engineers,
Incorporated.
10
IEEE publications are available from The Institute of Electrical and Electronics Engineers (https://standards.ieee.org/).
11
IEEE Standards Dictionary Online is available at: http://dictionary.ieee.org. An IEEE Account is required for access to the dictionary,
and one can be created at no charge on the dictionary sign-in page.
12
IEEE Std 577-2022
4. Requirements
4.1 General
The purpose of reliability analysis is to assist in assuring that the nuclear facility safety systems within the
scope of this standard will perform their required functions with an acceptable probability of success. The
actions required to perform a reliability analysis and evaluate results of the analysis include one or more of the
following elements:
— Establish availability goals

— Establish reliability goals
— Evaluate system designs
— Evaluate equipment qualification records
— Establish testing intervals that meet system goals
— Evaluate the operational performance of installed equipment
— Identify any necessary corrective action
4.1.1 Qualitative use
When required, qualitative analysis shall be performed in accordance with 4.2 to assess conformance of safety
systems to applicable design criteria.
4.1.2 Quantitative use
When required, quantitative analysis shall be performed in accordance with 4.3 and 4.4 to establish initial
periodic testing intervals for safety system equipment, and to provide a means for evaluating operational
performance against requirements.
4.1.3 Standardized design
Wherever standardized designs are used for multiple applications, the analyses performed for the standardized
portion of the first design shall fulfill the requirements of subsequent designs, provided that the initial analyses
are verified to be applicable.
4.1.4 Design changes
Reliability analyses shall adequately account for design changes. As a minimum, an analysis shall exist that
reflects the final design. Partial analyses may be performed to account for changes to critical portions of a
design. A partial analysis shall consider system interactions, including software interactions, caused by the
design change.
4.2 Qualitative analysis

4.2.1 Document for review
Any qualitative analysis shall be documented in a manner suitable for review.
13
IEEE Std 577-2022
4.2.2 Documentation criteria
The minimum documentation for a qualitative analysis to satisfy applicable criteria (e.g., single failure,
independence, channel integrity) shall include the following:
— Boundary of analysis. The area of design included within the scope of the work and germane to the
analysis.
— Level of analysis. The basic level of the system at which the faults of interest are investigated, including
a list of components, modules, or devices included in the analysis.
— System diagram. A logical arrangement of components basic to the system’s primary function or
operational mode for which the analysis is performed (e.g., schematics, process diagrams).
— Failure modes. All identified manners of failure for each class of component, module, or device.
— Results. The output of the analysis (e.g., cause of failure, method of detection, effects of the failure,
such as in a FMEA worksheet).
4.2.3 Complex failures
The analysis shall consider multiple failures attributable to a single cause and cascade failures, where failure
events occur in chain-like fashion. Analyses performed using the methods described in 5.6 of IEEE Std 352-
2016 are acceptable to fulfill this requirement.
4.2.4 Expected and initial conditions
Expected normal and abnormal environmental conditions and initial conditions assumed in the analysis shall
be stated.
4.3 Quantitative analysis

4.3.1 Document for review
Quantitative analyses may consist of any of the methods described in Clause 6 or Annex B of IEEE Std 352-
2016. The analysis shall be documented in a manner suitable for review. The analytical model should be
capable of being expanded into a higher level system model as suggested in Annex B of IEEE Std 352-2016.
4.3.2 Required calculations
A quantitative hardware analysis is performed to calculate the predicted availability or reliability (or both)
of the various safety systems in the facility. The use of a reliability or availability model (or both) shall be
selected in terms of the functions of the system in the operational mode being analyzed. This analysis shall
include pertinent system interactions and shall include sufficient detail to establish testing intervals consistent
with the goals for the system. For digital systems, software reliability shall be based on the quality software
development process utilizing industry consensus standards (e.g., IEEE Std 7-4.3.2™ [B9] and IEC 60880
[B7]).
Examples of acceptable model formats include the following:
— Fault tree
— Reliability block diagram
— Truth tables (or other appropriate tabular model)
14
IEEE Std 577-2022
Appropriate calculational techniques for quantification of the reliability or availability (or both) for the above-
mentioned model formats include the concepts and methods of the following:
— Boolean algebra
— Probability theory
— Conditional probability
— Minimal cut sets (appropriate bounds shall be specified)
— Monte Carlo simulation (calculational uncertainties should be evaluated)
— Markov matrices
Combinations of any of the preceding model formats and calculational methods may be supplemented or
replaced by a simple comparison with similar systems that have been analyzed in detail. Any differences
between the similar systems shall be defined; analyses of each difference shall be performed, including system
interactions to demonstrate that the existing detailed analysis is applicable. Annex B of IEEE Std 352-2016
illustrates an acceptable method of analysis.
4.3.3 Analysis goals
Quantitative analyses shall be used to determine if a design can meet a specified goal. Goals for the safety
systems shall be determined by the organizations responsible for the designs. Determination of the goals shall
consider the following, as appropriate:
— Overall facility goals

— System performance requirements
— Rate of demand on the system
— Complexity of system design
— Consequences of system failure
— Testing limitations
— Risk requirements
— Owner’s requirements
— Regulatory requirements
4.3.4 Documented failure data
All component failure data sources and assumptions used in the analysis shall be documented. When practical,
actual facility-specific failure data should be used.
4.3.5 Credible sources
Failure data shall be obtained from credible sources. Standard failure data shall be modified by the application
of appropriate adjustment factors when such application reflects experience in a significantly different
operating environment from that to which the standard failure data are being applied.
4.3.6 Treatment of uncertainties
Failure rates based on judgment may be used, provided the basis for the judgment is described and documented
in the analysis. Uncertainties shall be propagated through the analysis or approximated by sensitivity analyses.
15
IEEE Std 577-2022
4.3.7 Uses of analysis
Quantitative hardware analysis is intended to be one of the bases for the facility technical specifications
minimum surveillance requirements and limiting conditions for operation. The testing intervals shall be
determined in this manner to meet the requirements of Clause 5 of IEEE Std 338™-2012, considering the
methods provided in Annex B, Annex C, and Annex D of that standard. For digital systems, software reliability
analysis shall be based on the quality software development process utilizing industry consensus standards
(e.g., IEEE Std 7-4.3.2 [B9] and IEC 60880 [B7]).
4.4 Evaluation
4.4.1 General
Periodic testing programs are required to be established to verify that safety systems function with high
availability. The following requirements modify or complement those of IEEE Std 338:
a) If operational data reveal that the goals are being achieved with wide margins, the testing interval may
be lengthened or limiting conditions for operation may be relaxed. Redundancy requirements driven
solely by reliability considerations may be reduced if other considerations also support reducing
redundancy (for example, during safety train testing).
b) If actual performance falls significantly short of the goal, actions shall be taken to verify that the goals
can be attained. These actions include investigation for systematic causes, such as design deficiencies
or maintainability problems, shortening the test interval, requiring more stringent limiting conditions
for operation, or reassessment of the goal.
4.4.2 Changes to tests or limits
The requirements of IEEE Std 338, complemented by the methods of IEEE Std 352, shall be adhered to for
changes in test intervals or operating limitations.
16
IEEE Std 577-2022
Annex A
(informative)
Bibliography
Bibliographical references are resources that provide additional or helpful material but do not need to be
understood or used to implement this standard. Reference to these resources is made for informational use
only.
[B1] ANSI/ANS-2.27-2008 (R2016), Criteria for Investigations of Nuclear Facility Sites for Seismic Hazard
Assessments.12
[B2] ANSI/ANS-2.29-2008 (R2016), Probabilistic Seismic Hazards Analysis.
[B3] Apostolakis, G. and S. Kaplan, “Pitfalls in risk calculations,” Reliability Engineering, vol. 2, pp. 135–
145, 1981, http://dx.doi.org/10.1016/0143-8174(81)90019-6.
[B4] ASME/ANS-RA-Sb-2013, Standard for Level 1/Large Early Release Frequency Probabilistic Risk
Assessment for Nuclear Power Plant Applications.13
[B5] EPRI TR-105396, PSA Applications Guide, Electric Power Research Institute, True, D. et al., August
1995.14
[B6] EPRI SPID, Seismic Probabilistic Risk Assessment Implementation Guide, Electric Power Research
Institute (3002000709)
[B7] IEC 60880, Nuclear Power Plants—Instrumentation and Control Systems Important to Safety—Software
Aspects for Computer-Based Systems Performing Category A Functions.15
[B8] IEEE Std 7-4.3.2™, IEEE Standard Criteria for Digital Computers in Safety Systems of Nuclear Power
Generating Stations.16,17
[B9] IEEE Std 379™, IEEE Standard for Application of the Single-Failure Criterion to Nuclear Power
Generating Station Systems.
[B10] NUREG-1150, “Severe Accident Risks: An Assessment for Five U.S. Nuclear Power Plants,” Vol 1,
“Final Summary Report,” U. S. Nuclear Regulatory Commission, December 1990.18
[B11] NUREG/CR-1278, Handbook of Human Reliability Analysis with Emphasis on Nuclear Power Plant
Applications, (THERP), U. S. Nuclear Regulatory Commission, Swain, A. D. and Guttmann, H. E., August
1983.
[B12] NUREG/CR-2300, PRA Procedures Guide: A Guide to the Performance of Probabilistic Risk
Assessments for Nuclear Power Plants, U.S. Nuclear Regulatory Commission, 1983.
12
ANSI publications are available from the American National Standards Institute (https://www.ansi.org/).
13
ASME publications are available from the American Society of Mechanical Engineers (https://www.asme.org/).
14
EPRI publications are available from the Electric Power Research Institute (https://www.epri.com).
15
IEC publications are available from the International Electrotechnical Commission (http://www.iec.ch).
16
The IEEE standards or products referred to in Clause 2 are trademarks owned by The Institute of Electrical and Electronics Engineers,
Incorporated.
17
IEEE publications are available from The Institute of Electrical and Electronics Engineers (https://standards.ieee.org/).
18
NUREG publications are available from the U.S. Nuclear Regulatory Commission (https://www.nrc.gov/).
17
IEEE Std 577-2022
[B13] NUREG/CR-4550, Volume 1, Rev 1, Analysis of Core Damage Frequency: Methodology Guidelines
for Internal Events, U.S. Nuclear Regulatory Commission, Sandia National Laboratories, January 1990.
[B14] NUREG/CR-4840 / SAND88–3102, Procedures for the External Event Core Damage Frequency
Analyses for NUREG-1150, U.S. Nuclear Regulatory Commission, Sandia National Laboratories, Bohn, M.
P., and Lambright, J. A., 1990.
[B15] NUREG/CR-5032, Modeling Time to Recover and Initiating Event Frequency for Loss of Offsite-
Power Incidents at Nuclear Power Plants, U.S. Nuclear Regulatory Commission, March 1988.
[B16] NUREG/CR-6823, Handbook of Parameter Estimation for Probabilistic Risk Assessment, U.S. Nuclear
Regulatory Commission, Sandia National Laboratories et al., September 2003.
[B17] NUREG/CR-6928, Industry-Average Performance for Components and Initiating Events at U.S.
Commercial Nuclear Power Plants, U.S. Nuclear Regulatory Commission, Idaho National Laboratory,
February 2007.
[B18] NUREG/CR-6997, “Modeling a Digital Feedwater Control System Using Traditional Probabilistic Risk
Assessment Methods,” U.S. Nuclear Regulatory Commission, Brookhaven National Laboratory September
2009.
[B19] NUREG/CR-7233, “Developing a Bayesian Belief Network Model for Quantifying the Probability
of Software Failure of a Protection System,” U.S. Nuclear Regulatory Commission, Brookhaven National
Laboratory et al., January 2018.
[B20] NUREG-0800, Standard Review Plan for the Review of Safety Analysis Reports for Nuclear Power
Plants: LWR Edition, U.S. Nuclear Regulatory Commission. Chapter 19 Probabilistic Risk Assessment and
Severe Accident Evaluation for New Reactors.
[B21] Regulatory Guide 1.174, An Approach for Using Probabilistic Risk Assessment in Risk-Informed
Decisions on Plant-Specific Changes to the Licensing Basis, U.S. Nuclear Regulatory Commission.
[B22] Regulatory Guide 1.200, An Approach for Determining the Technical Adequacy of Probabilistic Risk
Assessment Results for Risk-Informed Activities.
[B23] WASH-1400, (also known as NUREG-75/014), Reactor Safety Study, An Assessment of Accident
Risks in U.S. Commercial Nuclear Power Plants. U.S. Nuclear Regulatory Commission, 1975.
18
RAISING THE
WORLD’S
STANDARDS
Connect with us on:
Twitter: twitter.com/ieeesa
Facebook: facebook.com/ieeesa
LinkedIn: linkedin.com/groups/1791118
Beyond Standards blog: beyondstandards.ieee.org
YouTube: youtube.com/ieeesa
standards.ieee.org
Phone: +1 732 981 0060

IE$E Standard

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IE$E Standard

Uploaded by

Copyright:

Available Formats

IEEE Standard Requirements for

IEEE Power and Energy Society

IEEE Std 577™-2022

IEEE Standard Requirements for

Nuclear Power Engineering Committee

Approved 9 February 2022

IEEE SA Standards Board

Keywords: IEEE 577™, nuclear facilities, reliability analysis, safety systems

The Institute of Electrical and Electronics Engineers, Inc.

Copyright © 2022 by The Institute of Electrical and Electronics Engineers, Inc.

PDF: ISBN 978-1-5044-8448-0 STD25250

IEEE prohibits discrimination, harassment, and bullying.

Notice and Disclaimer of Liability Concerning the Use of IEEE Standards

Comments on standards should be submitted using the Contact Us form.2

Laws and regulations

Updating of IEEE Standards documents

Khoi Nguyen, Chair

John Beatty Kirklyn Melson Philip Ward

Tom Crawford, Chair

George A. Ballassi James K. Liming Philip Ward

John White, Chair

Michiaki Akiyama Jason Gasque Edward Mohtashemi

S Aggarwal Stephen Fleger Robert Konnik

Gary Hoffman, Chair

Edward A. Addy Howard Li Mehmet Ulema

— IEEE Std 352™ supplements this standard by providing guidance in the application of reliability

IEEE Std 379™ [B8] describes the application of the single-failure criterion.6

1.3 Word usage

2. Normative references

availability: The probability that an item or system will be operational on demand.

— Establish availability goals

4.1.1 Qualitative use

4.1.2 Quantitative use

4.1.3 Standardized design

4.1.4 Design changes

4.2 Qualitative analysis

Any qualitative analysis shall be documented in a manner suitable for review.

4.2.2 Documentation criteria

4.2.3 Complex failures

4.2.4 Expected and initial conditions

4.3 Quantitative analysis

4.3.2 Required calculations

Examples of acceptable model formats include the following:

4.3.3 Analysis goals

— Overall facility goals

4.3.4 Documented failure data

4.3.5 Credible sources

4.3.6 Treatment of uncertainties

4.3.7 Uses of analysis

4.4.2 Changes to tests or limits

[B2] ANSI/ANS-2.29-2008 (R2016), Probabilistic Seismic Hazards Analysis.

You might also like