This standard gives the elements of the reliability program and provides guidance on how to select work items so that the product meets the specified reliability requirements. It is cross-referenced with GB/T 19004.1 and is a supplement to GB/T 19004.1. It is applicable to both hardware and systems containing software. This standard explains the various elements of the reliability program and gives the application guidelines in IEC 300-3 and other IEC standards on reliability management related to each work item, but does not include the detailed application programs required to implement these work items. The writing method of this standard is mainly aimed at the relationship between suppliers and customers who provide products and maintenance services. The parts of the product can be purchased by the supplier through other channels (such as through subcontracting). The names of "first-level supplier" (direct relationship with the customer) and "second-level supplier" (sub-supplier, direct relationship with the first-level supplier) are used when it is necessary to clarify. The actual user (end user) of the product may be the customer itself or a third party. GB/T 6992.2-1997 Dependability Management Part 2: Dependability Program Elements and Work Items GB/T6992.2-1997 Standard Download Decompression Password: www.bzxz.net
This standard gives the elements of the dependability program and provides guidance on how to select work items so that the product meets the specified dependability requirements. It is cross-referenced with GB/T 19004.1 and is a supplement to GB/T 19004.1. It is applicable to both hardware and systems containing software. This standard describes the various elements of the dependability program and gives the application guidelines in IEC 300-3 related to each work item and other IEC standards on dependability management, but does not include the detailed application programs required to implement these work items. The writing method of this standard is mainly aimed at the relationship between suppliers and customers who provide products and maintenance services. Product parts can be purchased by suppliers through other channels (such as through subcontracting). The names "first-tier supplier" (direct relationship with the customer) and "second-tier supplier" (sub-supplier, direct relationship with the first-tier supplier) are used when clarification is necessary. The actual user of the product (end user) may be the customer itself or a third party.

CB/T6992.2
This standard is equivalent to the International Electrotechnical Commission, IFC300-24 Dependability Management Part 2: Dependability Outline Elements and Work Items.
This standard is the first-level standard in the series of standards of the International Electrotechnical Commission (IEC.) in the field of dependability. In specific implementation, it is used in conjunction with GB/T19000.4 (equivalent to IEC300-1). Appendix A of this standard is the appendix of the standard; Appendix B and Appendix C of this standard are both suggestive appendices. This standard was proposed by the Ministry of Electronics Industry of the People's Republic of China. This standard is under the jurisdiction of the National Technical Committee for Standardization of Reliability and Maintainability of Electrical and Electronic Products. The drafting unit of this standard: the Fifth Institute of the Ministry of Electronics Industry. The main drafters of this standard are Ma Huaizu and Hu Xianghong. GB/T 6992.2—1997
IEC Foreword
1) IEC (International Electrotechnical Commission) is a worldwide standardization organization that includes national electrotechnical committees (IEC National Committees). The purpose of IEC is to promote international cooperation on all issues related to standardization in the fields of electrotechnical and electrical engineering. Through this cooperation and other activities, IEC publishes international standards. The formulation of international standards is entrusted to technical committees, and any IEC National Committee interested in the relevant items can participate in the formulation of standards. International organizations, government agencies and non-governmental organizations that have ties to IEC can also participate in the formulation of standards. IEC works closely with the International Organization for Standardization (ISO) in accordance with the agreement between the two organizations. 2) Since each technical committee has representatives from national committees interested in the relevant items, EC's formal decisions on technical issues are made. 3) The documents issued by IEC are published in the form of standards, technical reports or guidelines, which are recommended for international application. In this sense, the national committees accept these documents.
4) In order to promote international coordination, the IEC national committees of various countries have the responsibility to adopt IEC standards in their national and regional standards as much as possible. When there are inconsistencies between national and regional standards and TEC standards, the differences should be clearly pointed out in the national and regional standards.
5] IFC: does not provide any trademark registration and is not responsible for any product claiming to comply with a certain [EC standard. 6) It must be noted that some parts of this standard may involve patent rights, and IEC does not assume the responsibility for determining such patent rights. IEC300 was formulated by IFC, TC56 "Credibility". This standard version is based on the following documents:
56/437/FDIS
All the voting approval information of this standard is in the above voting report. This standard is composed of the following "-parts":
IEC3001 Credibility Management
IEC300-2: Credibility Outline Requirements and Work ItemsIEC300-3: (A series of application guidelines) Appendix A is the appendix of the standard
Appendix H and C are the suggested appendices.
Voting Report
56/488/RVI
GB/T 6992.2—1997bZxz.net
For those responsible for developing new products and for the use and operation of products, the following three factors are important: Performance
Does the product's performance (including reliability) meet the expectations and needs of the end user? Cost
How much does it cost (not only to develop and produce the product, but also to operate, maintain, and ultimately dispose of it)? In other words, what is the life cycle cost?
Mean Time
Can the product be delivered when needed and brought to market at the right time? User satisfaction with the product and the reputation of the product and the manufacturer play a large role in determining the product's performance. The reliability of a product depends on how the above three factors are managed and coordinated at each stage of the product life cycle.
The term reliability encompasses reliability, maintainability, availability and maintenance assurance. Reliability, availability and maintainability are themselves basic performance characteristics of a product and are often listed in product specifications as important product requirements. Maintenance assurance is the ability to provide the resources needed to maintain the product. The reliability characteristics of a product have a significant impact on the overall ability of the product to meet user requirements and may be the basic determinant of quality. Reliability also has a significant impact on the operating and maintenance costs of the product during use and whether acceptable life cycle costs can be achieved. The initial cost of the product The cost of use or purchase is usually the main factor influencing the user's choice, but it is important to realize that the purchase cost is only part of the total cost of ownership of the product. If the product can be designed to be reliable and easy to repair, the operating and maintenance costs can be greatly reduced. Improving and developing products with this idea in mind will usually increase the acquisition cost, but this part of the increase in cost will be offset by the significant reduction in operating and maintenance costs. It is important to weigh the cost of improving reliability and maintainability against the expected cost reduction over the entire life of the product. It is important for both suppliers and customers to realize that reliability characteristics will affect the performance, cost, and maintenance of the product. The reliability requirements are often very complex, and in order to achieve the reliability requirements, careful planning and coordination are required, and appropriate resources are allocated through the reliability program. The purpose of the reliability program is to ensure that all reliability, maintainability, availability and maintenance support requirements are met. Suppliers need to implement the reliability program to ensure that the reliability and maintainability requirements are met, and users need to implement the reliability program to ensure that the maintenance support requirements are met.
The various reliability programs (such as the reliability management program and the maintainability management program) should be fully integrated into the overall product program and product quality program.
The specified reliability requirements are often the main characteristics of product design and product maintenance support, so relevant specifications should be developed before the design work begins.
This standard provides general guidance for the establishment of reliability programs, applicable to hardware products and systems containing components. The elements selected for a specific product program should be tailored according to the applicable requirements, environment and conditions. The selection of elements, the emphasis of each element and the size of the overall dependability programme should take into account market conditions, user requirements and expectations, the contractual environment and the overall requirements for product and quality assurance. The individual programme elements may also need to be adjusted at different life cycle stages. 1 Scope
National Standard of the People's Republic of China
Dependability management
Part 2: Dependability programme elements and tasks GB/T 6992: 2-1997
idt IEC 300-2:1995
This standard gives the elements of a dependability programme and provides guidance on how to select work items so that the product meets the specified dependability requirements. It cross-references and supplements GB/T 19004.1 and is applicable to both hardware and systems including software. This standard describes the various key items of reliability management, provides the application guidelines in IEC300-3 related to each work item and other IEC standards on reliability management, but does not include the detailed application programs required to implement these work items. This standard is written in a way that focuses on the relationship between suppliers and customers who provide products and maintenance services. Product parts can be purchased by suppliers through other channels (such as through subcontracting). When it is necessary to clarify, the names of "first-tier supplier" (direct relationship with the customer) and second-tier supplier (sub-supplier, direct relationship with the first-tier supplier) are used. The actual user (end user) of the product may be the customer itself or a third party.
2 Referenced standards
The provisions contained in the following standards constitute the provisions of this standard through reference in this standard. The versions shown are valid at the time of publication of this standard. All standards will be revised. Parties using this standard should explore the possibility of using the latest versions of the following standards. IEC and ISO members hold currently valid international standards. GB/T 6583-94 Quality and quality assurance terms (idtISO 8102:1994) GB/T14733.3-93 Telecommunications spectrum reliability, maintainability and service quality (idl1IEC50(191):1990) GB/T19000.3-94 Quality management and quality assurance standard Part 3: G/T190011 Guide for the use of ISO9001 in software development, supply and maintenance (idtIEC300-1/ISO9000-3:1991) GB/T19000.4--1995 Quality management and quality assurance standard Part 4: Guide for reliability program management (idt300-1/IS090001:1993)
GB/T19001—94 Quality system Quality assurance model for design, development, production, installation and service (idtIS09001:1994) GB/T19004.1:04 Quality management and quality system elements Part 1: Guidance (icllISC)9004-1:1991) 3 Definitions
This standard adopts the terms and definitions given in GH/T14733.3, GB/T19000.4 and GB/T6583. In addition, the following terms are used:
3.1 Dependability programme dependability programme a series of activities related to product dependability. 3.2 Dependability programme element dependability programme element applies to a series of dependability programme work items in a specific area. Approved by the State Administration of Technology Supervision on October 24, 1997
Implemented on September 1, 1998
3.3 Life cyclelifecycle
GB/T 6992. 2: 1997
The time interval from the conception of a product to its final disposal. 3.4 Concept and definition phaseconcept and definition phaseThe phase in the product life cycle in which product requirements are determined and (usually) product specifications are specified. 3.5 Design and development phasedesign and developmentphaseThe phase in the product life cycle in which the hardware and/or software of the product are formed and the detailed manufacturing specifications of the hardware, the writing specifications of the software and other product documents (such as operating and maintenance instructions) are compiled. 3.6 Manufacturing phasemanufacturingphaseThe phase in the product life cycle in which the product is produced, the software is configured and the product is assembled. 3.7 Installation phaseinstallationphaseThe phase in the product life cycle in which the product is installed. 3.8 Operation and maintenance phaseoperation and maintenancephaseThe phase in the product life cycle in which the product is used and maintained and maintained. 3.9 disposal phase
The phase in the product life cycle after the operation and maintenance phases when the product is removed from the place of use, dismantled, decommissioned, destroyed and, if necessary, stored in a protected environment.
4 Overview of the Dependability Program
4.1 General
The purpose of the dependability program is to ensure that adequate and effective work is done on dependability as an important quality measure at all stages of the product life cycle (from definition through design, commissioning to the end of working life), and to ensure that activities that affect dependability are properly integrated with other contract and specification activities. At all stages of the project, the requirements of the dependability program should be continuously studied qualitatively and quantitatively, the dependability assessment should be continuously updated, and the specified requirements should be verified. The various elements of the dependability program should be integrated with other elements of the development, production and operation program. See Appendix A (Standard Appendix). The extent and content of the dependability program should be determined based on the special needs of the next project and any specific constraints and the importance of the actual product dependability.
For many projects, There is no clear demarcation between the definition, design and development, production and operation phases. However, for the sake of clarity, these phases are divided in this clause. Appendix B (suggestive appendix) lists the reliability outline work items to be selected in each phase of the product life cycle. This clause also explains in words the activities related to the overall project management responsibilities and schedule. The preparation of the reliability outline should take into account the connection with other outlines related to the project or product. The appendix (suggestive appendix) gives the national standards and international standards applicable to each work item. Figure 1 shows an example of the relationship between the life cycle phases and the reliability outline elements and work items. Note: Figure 1 and Appendices A, B, and C all show a general reliability outline, but from different angles. A reliability outline can be composed of appropriate elements and work items according to the tailoring process described in Chapter 5 of this standard to suit specific Needs and Environment
The reliability activities to be implemented at each stage of the product life cycle should be selected taking into account the context of the entire life cycle. Decisions made at any moment will have an impact on the product reliability and cost at that moment and in subsequent stages of the product life. It must be noted that the laws and regulations of both the user's location and the manufacturing facility's location should be taken into consideration, and compliance with this standard does not imply exemption from legal liability.
4.2 Product Life Cycle
4.2.1 Concept and Definition Stage
The concept and definition stage refers to the stage in the product life cycle where product requirements are determined and the requirements for the product are formulated into specifications. This stage lays the foundation for the product's reliability and life cycle cost. Decisions made at this stage have the greatest impact on the product and its recommended life cycle cost.
GB/T6992.2.1997
This The reliability activities in the first stage are mainly to put forward correct requirements, including requirements for products and their future guarantees, as well as the requirements of the reliability plan as the basis for the reliability requirements of subsequent stages. 4.2.2 Design and development stage
The design and development stage refers to the stage in the product life cycle stage in which the product hardware and software and related documents (such as detailed production specifications, software coding specifications, use and maintenance instructions, etc.) are formed. The main purpose of the reliability activities in this stage is to ensure that: the requirements of the reliability specifications are fully considered in the design process; analysis and prediction are carried out to obtain product reliability; the procedures and criteria for verification, confirmation and testing are specified and implemented according to the reliability requirements; the reliability of the components provided by the secondary suppliers or customers is consistent with the reliability requirements assigned to the components; the maintenance guarantee planning and engineering activities are coordinated and synchronized with the product design to ensure compliance with the reliability requirements; and the requirements for handling are specified.
4.2.3 Manufacturing stage
The manufacturing stage refers to the stage of producing products, configuring software and assembling products during the product life cycle. The purpose of the reliability activities in this phase is to maintain the product reliability performance achieved in the design and development phase without degradation in the manufacturing phase. To ensure that the reliability does not drop below the specified level, the reliability outline should describe the process procedures to be followed during the production of the system and equipment.
The main reliability activities in this phase include
Reliability and maintainability testing;
Production testing;
Reliability stress screening.
Standard number
Key points or work items
Policy and management
Reliability planning
Project decision-making philosophy
Reliability management
Technical status management
Contract review and coordination||tt ||He Shang Review
Specialized Accounting Table
Reliability Requirements
Reliability Requirements Specification
Reliability Requirements Specification
Reliability Requirements Allocation
Reliability Engineering
Reliability Engineering
Maintenance and Assurance Process
Testability Process
Reliability Engineering Requirements
Products Provided by Others
Subcontracted Products
Products Provided by Customers||tt| |Analysis, Planning and Design Review
Failure Mode and Effects Analysis
Failure Tree Analysis
Stress and Load Analysis
Human Resources Analysis
Trade-off Analysis
Risk Analysis
Formal Design Review
Verification, Validation and Testing
Verification, Validation and Test Planning
Life Testing
Reliability Testing
Reliability Proof of Service Testing
Production test
Acceptance test
Learnability stress screening
Periodical personnel
Operation and maintenance support planning
Maintenance support planning
Support waist
Support engineering
Spare parts should
Intake and refinement
Improvement group
Reform control
Experience backflow
Data acquisition framework
Data analysis
GB/T 6992. 2—1997
Design and concurrent
Concept, benefit is the meaning
Life idle stage
Operation and promotion: treatment
Figure 1, the relationship between the life cycle stage and the reliability outline work items 4.2.4 Installation stage
GB/T6992.2—1997
The installation phase refers to the phase in which the product is installed during the product life cycle. The reliability activities in this phase are carried out to ensure that the availability of the product will not be reduced during installation. Provide procedures and guidelines for acceptance inspection and testing to verify that the system and components meet the initial specifications and design. The main reliability activities in this phase are: trial operation, acceptance test:
-Reliability growth test;
-Reliability and maintainability verification:
Data collection and analysis!
. Early failure control
4.2.5 Operation and maintenance phase
The operation and maintenance phase refers to the phase in the product life cycle when the product is put into use and maintained and guaranteed. During this phase, necessary preventive and corrective maintenance measures should be taken and, if necessary, the performance of the product should be monitored. In order to ensure that the required reliability level is continuously achieved, during this phase, the following must be provided: Operating instructions Maintenance instructions Warning instructions Training Spare parts The useful life of the product ends when continued use becomes uneconomical due to increased maintenance costs or other factors or when the product is technically unsuitable. 4.2.6 Disposal phase The disposal phase is the phase after the operation and maintenance phase of the product life cycle, during which the product is removed from the place of use, dismantled, destroyed or, if necessary, stored in a protected environment. This phase may also include the analysis of the product in order to complete the following activities: - Aging and aging analysis Feedback of data to suppliers for improving reliability and maintainability Recovery of reusable materials.
5 Criteria for tailoring the reliability outline
5.1 General
The reliability outline elements and work items specified in this standard are universal. The outline should be appropriately tailored after considering relevant aspects of the specific product or project. When citing this standard, the relevant parties should reach an agreement on its applicability and record it. The agreement should be documented. For those clauses or parts of clauses determined by the agreement, their contents vary from recommendations (\should\) to requirements ("must\"). In order to compile an effective reliability outline at any stage of the product life cycle, it is necessary not only to understand the reliability principles, methods and requirements, but also to understand the product itself and common technologies, its intended use and various related cost factors. In order to obtain effective results, reliability activities should be closely coordinated with the management of other activities, rather than being unrelated. When tailoring the reliability outline, managers should consider the following factors: the application of the product by the user (see 5.2), - actual or expected contract situation (see 5.3) - applicability of all or part of the product life cycle (see 5.4): product-related characteristics (see 5.5);
historical situation of similar products;
- cost-effectiveness of each outline work item; hardware/software trade-off analysis.
5.2 User application situation
GB/T 6992.2—1997
Whether it is necessary to specify reliability requirements and implement a reliability outline for the product and its support depends on the market (end user) conditions in each case. Reliability can be specified by various factors such as safety and effectiveness, or by economic factors related to different market situations. For example, aviation systems, nuclear power plants, medical equipment, process control equipment, military products, communication systems, consumer products, etc. Obviously, the importance of reliability is different in various situations, so the reliability outline should be adjusted accordingly. 5.3 Contract environment
Whether a specific reliability outline is implemented depends on the contract environment, including the supply and demand relationship of a specific engineering project, which can include the following situations:
The supplier shall determine the reliability of the product based on the requirements of the contract environment, including the supply and demand relationship of the specific engineering project, which may include the following situations:
The supplier shall determine the reliability of the product based on the requirements of the contract environment, including the supply and demand relationship of the specific engineering project, which may include the following situations: Product planning and development according to customer requirements; the supplier manufactures products according to existing specifications agreed by both parties, and the supplier is responsible for final inspection and testing;
The supplier installs products developed and manufactured according to other contracts according to the widest possible working purpose; the supplier performs product maintenance according to the given maintenance policy. Note: The provisions of this standard are also applicable to non-contractual environments, that is, when there is no contract when the product is designed and developed but it is carried out according to the needs of potential customers and users, and then manufactured and brought to the market. The recommendations on tailoring are also suitable for this environment. 5.4 Application of life cycle stages
For a given engineering project/contract environment, the elements and work items that should be included in the credibility outline should correspond to the relevant life cycle stages.
Figure 1 Appendix B gives the activities applicable to different phases. 5.5 Product-related characteristics When tailoring the dependability outline, the characteristics of the product itself must be considered, such as: - the novelty of the product! - the effectiveness criteria of the product:
the required reliability level.
5.6 Software
In general, the principles of this standard apply to all parts of the system, including software. When software is involved in the tailoring process, the type of software application can be divided into the following categories: safety-critical!
- real-time;
- military!
- process control
commercial, etc.
The type of software application and other factors such as size, complexity, and the impact of failures determine the tailoring requirements. For further guidance on software dependability, please refer to IE0300-3-6.6 Product or project specific outline elements and work items6.1 Planning and management
6.1.1 Dependability plan
The dependability outline requires appropriate planning and management. CB/T 6992. 2—1997
As a basic management, planning and control document, the reliability plan governs the implementation of the reliability program. The preparation of the reliability plan should be considered together with the preparation of other plans and formally reviewed before starting a new project or planning a new or modified product.
The plan should cover all activities that affect product reliability and clearly define the obligations of managers to implement the plan. It should propose ways and methods suitable for the implementation and control of work items and ensure the effective implementation of work items. The reliability plan should include:
--Confirmation and description of the reliability work items/elements selected for the project;--Confirmation and description of the audit and review work items required to ensure that the planned work items are properly implemented and properly coordinated with other activities;|| tt||---Confirmation and description of the duties, responsibilities, authority and interrelationships of personnel who manage, implement and inspect work items;--Details of the procedures for completing tasks, such as time schedules, milestones and descriptions of design review, verification and validation criteria;--Specifications of the resources required to complete the various work items identified in the outline in a timely manner;--Specifications of the products or documents to be delivered at each milestone and confirmation of the organization responsible for developing, selecting and using the required documents;--Specifications of the document preparation and technical status management system;--In order to ensure the coordinated transmission of relevant data, the establishment of information links between reliability and related disciplines;--Subcontractor control:
1 The customer shall take necessary measures in its reliability plan to ensure compliance with the specified product operation and maintenance conditions. 2 The customer shall help the supplier prepare its reliability plan and shall provide any information needed to determine the operation and maintenance conditions, 6. 1.2 Engineering Project Decision Management
Engineering project decision management is part of engineering project management, and its main content is about the control of engineering progress. The nodes of the credibility outline should be established. They should be coordinated with the nodes of the product life cycle. 6.1.3 Traceability Management
An effective method should be provided to ensure traceability, including the necessary arrangements for monitoring the progress of credibility activities and tracing back to their initial requirements.
An organization should establish an appropriate corrective action system to solve the confirmed credibility problems according to the requirements of Chapter 15 of GB/T19001.1-94. The customer shall provide the necessary guarantees to establish the connection between customer requirements and on-site performance evaluation. 6.1.4 Technical Status Management
Since it may be necessary to modify the product and its maintenance support at any stage of the life cycle, a technical status management system shall be established in accordance with the requirements of 8.8 in GB/T19004.1 and 6.1 in GB/T19000.3-91 - changes in the product and its maintenance support shall be systematically controlled and documented, and the reliability specification shall be used as the first baseline in the technical status management system. 6.2 Contract Review and Liaison
6.2. 1 Contract Review
The contract review shall be conducted in accordance with the specified reliability requirements. This review shall comply with 1.3. Typical reliability contract requirements that need to be evaluated include:
-Scope and schedule of reliability activities;
-Specified delivery targets and delivered products;
-Specified documentation requirements;
-Specified test verification clauses;
-Guarantee, fines and specific reward details;
-Product use environment conditions.
6. 2.2 Management representative
GB/T6992.2—1997
In order to provide effective collaboration for the relevant parties, the management representative should have sufficient understanding of the product and its guarantee, reliability principles and practices. On certain issues, they can seek support from experts. See 5.2.2 of GB/T19004.1—94 for details. Management representatives should have the authority to make decisions on the relationship between the supply and demand parties in the following areas: - Specification, review and modification of reliability requirements; - Agreements with other parties on reliability data, documents, collaborative procedures and design evaluation; - Ensure that the reliability agreements signed by various organizations are recognized: Specifications of reliability confirmation, acceptance procedures and criteria. 6.3 Reliability Requirements
6.3.1 Reliability Requirements Specification
The reliability specifications of products and their components and product assurance should be prepared by the supplier and/or customer. This work item should include the analysis and establishment of the following aspects: certain product reliability and maintainability requirements, product functions, failure criteria, environmental and operating conditions, and regulations for product life that meets expected requirements:
Quantitative requirements for measuring performance such as reliability, maintainability and availability (such as total failure rate, mission reliability, and mean downtime). The preparation of reliability inputs to system specifications and the identification and assurance requirements are part of this work item; - Testability requirements (test functions and procedures, test accuracy of each product level, etc.); - Qualitative and quantitative requirements (or conditions) for maintenance assurance. The Dependability Specification provides the basis for mutual understanding between the supplier and the demander and between the various groups of people involved in the design and use of the product.
The basis of each Dependability Specification is the definition of the types of failure environments that may affect the effective use of the product. The development of any Dependability Specification should start here.
The requirements specified should be clear, verifiable, consistent and traceable. NOTE The interdependencies between the requirements must be clearly stated and the definition of each requirement should also state the methods and procedures (analysis methods, simulation, testing, etc.) and life cycle stages that must be verified for consistency.
For details, see IEC300-3-4. For applications related to electronic components, see GB5990 and SJ/Z9007. 6.3.2 Dependability Requirements Description
The requirements description shall include an analysis of the conditions and constraints that are typical of the intended use of the product and that will affect its reliability, including: - Operation and maintenance conditions, including mission types and durations; - Confirmation of the loads and working cycles imposed on the product during its intended use; - Determination of the environmental and operating conditions experienced by the parts or components of the product during each stage of use and during maintenance and support activities (including storage, transportation, etc.);
- Determination of the impact of manufacturing, testing, storage, packaging, transportation, handling and maintenance. Constraints caused by maintenance policies, personal skill levels, etc. shall be confirmed and proposed changes when applicable. The interpretation of the agreed-upon requirements specification clauses shall be documented and attached to the dependability specification. 6.3.3 Allocation of Reliability Requirements
The reliability requirements shall be allocated to the various components of the product based on the product structure and maintenance arrangements, the possibility of verifying and validating the reliability requirements, and the design progress process.
Note that in allocating reliability characteristics, it may be necessary for some parts of the product and some life cycle stages to use other methods than those specified in the reliability specification (for example, the number of failures found in various test activities may be used as a criterion for reliability control during the design and development phase).
The allocation shall be included in the specification of any subcontracted components of the final product and used as the basis for the definition and design of verification, validation and test procedures.
GB/T 6992.2—1997
Note: As the design process progresses, the allocation may have to be reconsidered, for example based on the conclusions of trade-off studies. 6.4 Engineering
6.4.1 Reliability Engineering
The required reliability is achieved by using design techniques that prevent failures from occurring (fault avoidance) or eliminate their effects (fault tolerance techniques).
Such design activities usually include the following aspects: Applying fault-breaking techniques (redundancy, parallel programming, structural reorganization, restart) and fail-safe techniques - Applying design methods such as top-down design, modular programming, and component derating design; Eliminating fatal single-point failure modes:
- Controlling the stress acting on components and components: - Controlling the load that has a destructive effect on the software; Reducing the impact of parameter changes (such as aging) on ​​design performance: Using preferred and proven components and technologies; Specifying methods to reduce the sensitivity of manufacturing processes: - Complying with safety standards:
- Special techniques to ensure that the software is fault-free, such as code inspection, code review and preliminary inspection processes. When the design work is based on an existing product, the reliability of the product should be clearly described in documents, and any known problems should be corrected during the development stage.
Reliability engineering should also include identifying components that play a key role in reliability and establishing controls and special treatments for key components according to specific hazard criteria and regulations from the design and development stage to the manufacturing and safety stage. Note: Reliability engineering should maintain a close working relationship with maintenance engineering, maintenance support engineering, human factors engineering, test engineering, analysis, prediction and design review activities, and component and software engineering. 6.4.2 Maintainability Engineering
Good maintainability can be achieved by making the product easy to maintain and repair. For example, an automated maintenance technology that automatically restarts when software causes a failure can be used.
This work item should include the preparation of detailed maintainability design criteria based on the specific maintainability requirements of the product and regular review. By implementing these methods and techniques, the following items should be minimized: Maintenance complexity:
-Frequency of preventive maintenance activities specified by product design: -Unavailability time caused by the particularity of the product, -Maintenance support costs specified by product design; -Requirements on the technical level of maintenance personnel; -Potential maintenance errors.
When the design work is based on an existing product, the maintainability of the product should be clearly described in documents, and any known problems should be considered during the development stage.
For details, see GB9414 and IEC706.
6.4.3 Maintenance Support Project
Maintenance support may be required during the installation, operation and maintenance phases of the product. It requires resources and instructions, based on the prescribed maintenance policy, methods, tools, test equipment, documents and other facilities required by the support policy, training outlines for maintenance personnel, etc. This work project should include the confirmation and preparation of the following items: ...data collection, analysis, evaluation steps and required resources related to fault and maintenance reports - steps and required resources for product changes and improvements;1. Dependability Requirements Specification
The reliability specifications for the product, its components and product support should be prepared by the supplier and/or the customer. This work item should include the analysis and establishment of the following aspects: certain product reliability and maintainability requirements, product functions, failure criteria, environmental and operating conditions, and provisions for product life that meet expected requirements:
Quantitative requirements for measuring performance such as reliability, maintainability and availability (such as total failure rate, mission reliability, and average downtime). The preparation of the reliability input of the system specification and the identification and assurance requirements are the "-part" of this work item; -Testability requirements (test functions and procedures, test accuracy of each product level, etc.); -Qualitative and quantitative requirements (or conditions) for maintenance support. The reliability specification provides a basis for mutual understanding between the supplier and the demander and between the various groups of personnel (of both the supplier and the demander) involved in the design and use of the product.
The basis of each reliability specification is the definition of the types of failure environments that may affect the effective use of the product. The development of any reliability specification should start from here.
The requirements specified should be clear and verifiable. , consistency and traceability. Note that the interdependencies between the requirements must be clearly stated, and the provisions of each requirement should also state the methods and procedures (analysis methods, simulation, testing, etc.) and life cycle stages that must be verified for consistency.
For details, see IEC300-3-4, and for applications related to electronic components, see GB5990 and SJ/Z9007. 6.3.2 Description of reliability requirements
The requirements description should include an analysis of the conditions and constraints that are typical of the intended use of the product and that will affect its reliability, including: - Operating and maintenance conditions, including task types and durations: - Confirmation of the loads and working cycles applied to the product during its intended use: Determination of the environmental and operating conditions experienced by the parts or components of the product during each stage of use and during maintenance and support activities (including storage, transportation, etc.); Determination of the impact of manufacturing, testing, storage, packaging, transportation, handling and maintenance. Constraints due to maintenance policies, personal skill levels, etc. should be confirmed and changes proposed when applicable. The interpretation of the consensus on the requirements specification clauses should be documented and attached to the reliability specification. 6.3.3 Reliability requirements allocation
should be based on the structure and maintenance arrangements of the product. , the possibility of verifying and confirming the reliability requirements and the design progress process to allocate the reliability requirements to the various components of the product.
Note that when allocating reliability characteristics, it may be necessary to use other methods than those specified in the reliability specification for some parts and certain life cycle stages of the product (for example, the number of failures found in various test activities can be used as a criterion for reliability control in the design and development stage).
The allocation should be included in the specification of any subcontracted components of the final product and used as the basis for the definition and design of verification, confirmation and test procedures.
GB/T 6992.2—1997
Note: As the design process progresses, such as based on the conclusions of trade-off studies, the allocation may have to be reconsidered. 6.4 Engineering
6.4.1 Reliability Engineering
The required reliability is achieved by using design techniques that prevent failures from occurring (fault avoidance) or eliminate their effects (fault tolerance techniques).
Such design activities usually include the following aspects: Apply fault-tolerant techniques (redundancy, parallel programming, structural reorganization, restart) and fail-safe techniques - Apply design methods such as top-down design, modular programming, and component derating; Eliminate fatal single-point failure modes:
- Control the stresses acting on components and components: - Control the loads that have a destructive effect on the software; Reduce the effects of parameter changes (such as aging) on ​​design performance: Use preferred and proven components and technologies; Specify methods to reduce the sensitivity of manufacturing processes: - Meet safety standards:
- Special techniques to ensure that the software is fault-free, such as code inspection, code review and preliminary inspection processes. When the design work is based on an existing product, the reliability of the product should be well documented and any known problems should be corrected during the development phase.
Reliability engineering should also include the identification of components that are critical to reliability and the establishment of controls and special treatments for critical components from the design and development phase to the manufacturing and safety phases according to specific hazard criteria and regulations. NOTE: Reliability engineering should have a close working relationship with maintenance engineering, maintenance support engineering, human factors engineering, test engineering, and analysis, prediction and design review activities as well as with component and software engineering. 6.4.2 Maintainability Engineering
Good maintainability can be achieved by making the product easy to maintain and repair. For example, this can be achieved by using automated maintenance techniques such as automatic restart when software causes a failure.
This work item should include the preparation of detailed maintainability design criteria based on the specific maintainability requirements of the product and regular review. By implementing these methods and techniques, the following items should be minimized: Maintenance complexity:
-Frequency of preventive maintenance activities specified in product design; -Unavailability caused by the particularity of the product; -Maintenance support costs specified in product design; -Requirements on the technical level of maintenance personnel; -Potential maintenance errors.
When the design work is based on an existing product, the maintainability of the product should be clearly described in documents, and any known problems should be considered during the development phase.
See GB9414 and IEC706 for details.
6.4.3 Maintenance support engineering
Maintenance support may be required during the installation phase, operation and maintenance phase of the product. It requires resources and instructions, based on the prescribed maintenance policy, methods, tools, test equipment, documents and other facilities required by the support policy, training outline for maintenance personnel, etc. This work item should include the confirmation and preparation of the following items: ... Steps and resources required for data collection, analysis and evaluation related to faults and maintenance reports - Steps and resources required for product changes and improvements;1. Dependability Requirements Specification
The reliability specifications for the product, its components and product support should be prepared by the supplier and/or the customer. This work item should include the analysis and establishment of the following aspects: certain product reliability and maintainability requirements, product functions, failure criteria, environmental and operating conditions, and provisions for product life that meet expected requirements:
Quantitative requirements for measuring performance such as reliability, maintainability and availability (such as total failure rate, mission reliability, and average downtime). The preparation of the reliability input of the system specification and the identification and assurance requirements are the "-part" of this work item; -Testability requirements (test functions and procedures, test accuracy of each product level, etc.); -Qualitative and quantitative requirements (or conditions) for maintenance support. The reliability specification provides a basis for mutual understanding between the supplier and the demander and between the various groups of personnel (of both the supplier and the demander) involved in the design and use of the product.
The basis of each reliability specification is the definition of the types of failure environments that may affect the effective use of the product. The development of any reliability specification should start from here.
The requirements specified should be clear and verifiable. , consistency and traceability. Note that the interdependencies between the requirements must be clearly stated, and the provisions of each requirement should also state the methods and procedures (analysis methods, simulation, testing, etc.) and life cycle stages that must be verified for consistency.
For details, see IEC300-3-4, and for applications related to electronic components, see GB5990 and SJ/Z9007. 6.3.2 Description of reliability requirements
The requirements description should include an analysis of the conditions and constraints that are typical of the intended use of the product and that will affect its reliability, including: - Operating and maintenance conditions, including task types and durations: - Confirmation of the loads and working cycles applied to the product during its intended use: Determination of the environmental and operating conditions experienced by the parts or components of the product during each stage of use and during maintenance and support activities (including storage, transportation, etc.); Determination of the impact of manufacturing, testing, storage, packaging, transportation, handling and maintenance. Constraints due to maintenance policies, personal skill levels, etc. should be confirmed and changes proposed when applicable. The interpretation of the consensus on the requirements specification clauses should be documented and attached to the reliability specification. 6.3.3 Reliability requirements allocation
should be based on the structure and maintenance arrangements of the product. , the possibility of verifying and confirming the reliability requirements and the design progress process to allocate the reliability requirements to the various components of the product.
Note that when allocating reliability characteristics, it may be necessary to use other methods than those specified in the reliability specification for some parts and certain life cycle stages of the product (for example, the number of failures found in various test activities can be used as a criterion for reliability control in the design and development stage).
The allocation should be included in the specification of any subcontracted components of the final product and used as the basis for the definition and design of verification, confirmation and test procedures.
GB/T 6992.2—1997
Note: As the design process progresses, such as based on the conclusions of trade-off studies, the allocation may have to be reconsidered. 6.4 Engineering
6.4.1 Reliability Engineering
The required reliability is achieved by using design techniques that prevent failures from occurring (fault avoidance) or eliminate their effects (fault tolerance techniques).
Such design activities usually include the following aspects: Apply fault-tolerant techniques (redundancy, parallel programming, structural reorganization, restart) and fail-safe techniques - Apply design methods such as top-down design, modular programming, and component derating; Eliminate fatal single-point failure modes:
- Control the stresses acting on components and components: - Control the loads that have a destructive effect on the software; Reduce the effects of parameter changes (such as aging) on ​​design performance: Use preferred and proven components and technologies; Specify methods to reduce the sensitivity of manufacturing processes: - Meet safety standards:
- Special techniques to ensure that the software is fault-free, such as code inspection, code review and preliminary inspection processes. When the design work is based on an existing product, the reliability of the product should be well documented and any known problems should be corrected during the development phase.
Reliability engineering should also include the identification of components that are critical to reliability and the establishment of controls and special treatments for critical components from the design and development phase to the manufacturing and safety phases according to specific hazard criteria and regulations. NOTE: Reliability engineering should have a close working relationship with maintenance engineering, maintenance support engineering, human factors engineering, test engineering, and analysis, prediction and design review activities as well as with component and software engineering. 6.4.2 Maintainability Engineering
Good maintainability can be achieved by making the product easy to maintain and repair. For example, this can be achieved by using automated maintenance techniques such as automatic restart when software causes a failure.
This work item should include the preparation of detailed maintainability design criteria based on the specific maintainability requirements of the product and regular review. By implementing these methods and techniques, the following items should be minimized: Maintenance complexity:
-Frequency of preventive maintenance activities specified in product design; -Unavailability caused by the particularity of the product; -Maintenance support costs specified in product design; -Requirements on the technical level of maintenance personnel; -Potential maintenance errors.
When the design work is based on an existing product, the maintainability of the product should be clearly described in documents, and any known problems should be considered during the development phase.
See GB9414 and IEC706 for details.
6.4.3 Maintenance support engineering
Maintenance support may be required during the installation phase, operation and maintenance phase of the product. It requires resources and instructions, based on the prescribed maintenance policy, methods, tools, test equipment, documents and other facilities required by the support policy, training outline for maintenance personnel, etc. This work project should include the confirmation and preparation of the following items: ... Steps and resources required for data collection, analysis and evaluation related to faults and maintenance reports - Steps and resources required for product changes and improvements;1 Reliability Engineering
The required reliability is obtained by adopting design techniques to prevent failures from occurring (fault avoidance) or eliminate their effects (fault tolerance techniques).
Such design activities usually include the following aspects: Apply fault-breaking techniques (redundancy, parallel programming, structural reorganization, restart) and fail-safe techniques-Apply design methods such as top-down design, modular programming, and component derating design; Eliminate fatal single-point failure modes:
-Control the stress acting on components and components:-Control the load that has a destructive effect on software; Reduce the impact of parameter changes (such as aging) on ​​design performance: Use preferred and proven components and technologies; Specify methods to reduce the sensitivity of manufacturing processes:-Meet safety standards:
-Special techniques to ensure that the software is trouble-free, such as code inspection, code review and preliminary inspection process. When the design work is based on an existing product, the reliability of the product should be clearly described in documents, and any known problems should be corrected during the development stage.
Reliability engineering should also include the identification of components that are critical to reliability and the establishment of controls and special treatments for critical components from the design and development phase to the manufacturing and installation phases according to specific hazard criteria and regulations. Note: Reliability engineering should maintain a close working relationship with maintenance engineering, maintenance support engineering, human factors engineering, test engineering, analysis, prediction and design review activities, and component and software engineering. 6.4.2 Maintainability Engineering
Good maintainability can be achieved by making the product easy to maintain and repair. For example, an automated maintenance technology that automatically restarts when software causes a failure can be used.
This work item should include the preparation of detailed maintainability design criteria based on the specific maintainability requirements of the product and regular review. By implementing these methods and techniques, the following items should be minimized: Maintenance complexity:
-Frequency of preventive maintenance activities specified by product design:-Time of unavailability caused by the special characteristics of the product--Maintenance support costs specified by product design;-Requirements on the technical level of maintenance personnel;-Potential maintenance errors.
When the design work is based on an existing product, the maintainability of the product should be clearly described in documents, and any known problems should be considered during the development phase.
See GB9414 and IEC706 for details.
6.4.3 Maintenance support engineering
Maintenance support may be required during the installation phase, operation and maintenance phase of the product. It requires resources and instructions, and is based on the prescribed maintenance policies, methods, tools, test equipment, documents and other facilities required by the support policy, training outlines for maintenance personnel, etc. This work item should include the confirmation and preparation of the following items: ... the steps and resources required for data collection, analysis, and evaluation related to faults and maintenance reports - the steps and resources required for changes and improvements to the product;1 Reliability Engineering
The required reliability is obtained by adopting design techniques to prevent failures from occurring (fault avoidance) or eliminate their effects (fault tolerance techniques).
Such design activities usually include the following aspects: Apply fault-breaking techniques (redundancy, parallel programming, structural reorganization, restart) and fail-safe techniques-Apply design methods such as top-down design, modular programming, and component derating design; Eliminate fatal single-point failure modes:
-Control the stress acting on components and components:-Control the load that has a destructive effect on software; Reduce the impact of parameter changes (such as aging) on ​​design performance: Use preferred and proven components and technologies; Specify methods to reduce the sensitivity of manufacturing processes:-Meet safety standards:
-Special techniques to ensure that the software is trouble-free, such as code inspection, code review and preliminary inspection process. When the design work is based on an existing product, the reliability of the product should be clearly described in documents, and any known problems should be corrected during the development stage.
Reliability engineering should also include the identification of components that are critical to reliability and the establishment of controls and special treatments for critical components from the design and development phase to the manufacturing and installation phases according to specific hazard criteria and regulations. Note: Reliability engineering should maintain a close working relationship with maintenance engineering, maintenance support engineering, human factors engineering, test engineering, analysis, prediction and design review activities, and component and software engineering. 6.4.2 Maintainability Engineering
Good maintainability can be achieved by making the product easy to maintain and repair. For example, an automated maintenance technology that automatically restarts when software causes a failure can be used.
This work item should include the preparation of detailed maintainability design criteria based on the specific maintainability requirements of the product and regular review. By implementing these methods and techniques, the following items should be minimized: Maintenance complexity:
-Frequency of preventive maintenance activities specified by product design:-Time of unavailability caused by the special characteristics of the product--Maintenance support costs specified by product design;-Requirements on the technical level of maintenance personnel;-Potential maintenance errors.
When the design work is based on an existing product, the maintainability of the product should be clearly described in documents, and any known problems should be considered during the development phase.
See GB9414 and IEC706 for details.
6.4.3 Maintenance support engineering
Maintenance support may be required during the installation phase, operation and maintenance phase of the product. It requires resources and instructions, and is based on the prescribed maintenance policies, methods, tools, test equipment, documents and other facilities required by the support policy, training outlines for maintenance personnel, etc. This work item should include the confirmation and preparation of the following items: ... the steps and resources required for data collection, analysis, and evaluation related to faults and maintenance reports - the steps and resources required for changes and improvements to the product;
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.