GB/T 34590.9-2022 PDF English
Search result: GB/T 34590.9-2022 English: PDF (GB/T34590.9-2022)
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Name of Chinese Standard | Status |
| GB/T 34590.9-2022 | English | 410 |
Add to Cart
|
0-9 seconds. Auto-delivery.
|
Road vehicles - Functional safety - Part 9: Automotive safety integrity level(ASIL)-oriented and safety-oriented analyses
| Valid |
| GB/T 34590.9-2017 | English | 145 |
Add to Cart
|
0-9 seconds. Auto-delivery.
|
Road vehicles -- Functional safety -- Part 9: Automotive Safety Integrity Level (ASIL) -oriented and safety-oriented analyses
| Obsolete |
PDF Preview: GB/T 34590.9-2022
PDF Preview: GB/T 34590.9-2017
GB/T 34590.9-2022: PDF in English (GBT 34590.9-2022) GB/T 34590.9-2022
GB
NATIONAL STANDARD OF THE
PEOPLE’S REPUBLIC OF CHINA
ICS 43.040
CCS T 35
Replacing GB/T 34590.9-2017
Road Vehicles - Functional Safety - Part 9: Automotive
Safety Integrity Level (ASIL)-oriented and Safety-oriented
Analyses
(ISO 26262-1:2018, MOD)
ISSUED ON: DECEMBER 30, 2022
IMPLEMENTED ON: JULY 1, 2023
Issued by: State Administration for Market Regulation;
Standardization Administration of the People’s Republic of China.
Table of Contents
Foreword ... 4
Introduction ... 8
1 Scope ... 12
2 Normative references ... 13
3 Terms and definitions ... 14
4 Requirements ... 14
4.1 Purpose... 14
4.2 General requirements ... 14
4.3 Interpretations of tables ... 15
4.4 ASIL-dependent requirements and recommendations ... 16
4.5 Adaptation for motorcycles ... 16
4.6 Adaptation for goods vehicles, buses, special vehicles, and trailers ... 16
5 Requirements decomposition with respect to ASIL tailoring ... 16
5.1 Objectives ... 16
5.2 General rules ... 17
5.3 Inputs to this chapter ... 17
5.4 Requirements and recommendations ... 18
5.5 Work products ... 22
6 Criteria for coexistence of elements ... 22
6.1 Objectives ... 22
6.2 General rules ... 22
6.3 Inputs to this chapter ... 23
6.4 Requirements and recommendations ... 23
6.5 Work products ... 24
7 Analysis of dependent failures ... 24
7.1 Objectives ... 24
7.2 General rules ... 24
7.3 Inputs to this chapter ... 26
7.4 Requirements and recommendations ... 27
7.5 Work products ... 29
8 Safety analyses ... 29
8.1 Objectives ... 29
8.2 General rules ... 30
8.3 Inputs to this chapter ... 31
8.4 Requirements and recommendations ... 32
8.5 Work products ... 34
Appendix A (Informative) Overview of Automotive Safety Integrity Level (ASIL)-
oriented and safety-oriented analyses ... 35
Appendix B (Informative) Example architectures for Coexistence of elements and
Decomposition of requirements ... 38
Appendix C (Informative) Framework for Identifying Dependent Failures ... 40
References ... 45
Foreword
This document was drafted in accordance with the rules provided in GB/T 1.1-2020
Directives for Standardization - Part 1: Rules for the Structure and Drafting of
Standardizing Documents.
This document is Part 9 of GB/T 34590 Road Vehicles - Functional Safety. GB/T 34590
has issued the following parts:
-- Part 1: Vocabulary;
-- Part 2: Management of Functional Safety;
-- Part 3: Concept Phase;
-- Part 4: Product Development at the System Level;
-- Part 5: Product Development at the Hardware Level;
-- Part 6: Product Development at the Software Level;
-- Part 7: Production, Operation, Service and Decommissioning;
-- Part 8: Supporting Processes;
-- Part 9: Automotive Safety Integrity Level (ASIL)-oriented and Safety-oriented
Analyses;
-- Part 10: Guideline;
-- Part 11: Guidelines on Applications to Semiconductors;
-- Part 12: Adaptation for Motorcycles.
This document serves as a replacement for GB/T 34590.9-2017 Road Vehicles -
Functional Safety - Part 9: Automotive Safety Integrity Level (ASIL)-oriented and
Safety-oriented Analyses. In comparison with GB/T 34590.9-2017, apart from
structural adjustments and editorial modifications, the main technical changes are as
follows:
-- The scope of application of the standard is revised from “mass-produced
passenger cars” to “mass-produced road vehicles other than mopeds” (see
Chapter 1; see Chapter 1 of the 2017 edition);
-- The adaptation requirements for motorcycles are added (see 4.5);
-- The adaptation requirements for goods vehicles, buses, special vehicles, and
trailers are added (see 4.6);
-- The objectives of requirements decomposition on ASIL tailoring are changed
(see 5.1; see 5.1 of the 2017 edition);
-- The general rules of the requirements decomposition on ASIL tailoring are
changed (see 5.2; see 5.2 of the 2017 edition);
-- The contents that the initial safety requirements shall be decomposed into
redundant safety requirements are changed (see 5.4.3; see 5.4.3 of the 2017
edition);
-- The contents that each decomposed safety requirement shall comply with the
initial safety requirement by itself are changed (see 5.4.4; see 5.4.4 of the 2017
edition);
-- The content “If the violation of an initial safety requirement cannot be prevented
by switching off the element, then adequate availability of the sufficiently
independent elements implementing the decomposed safety requirements shall
be shown” is deleted (see 5.4.8 of the 2017 edition);
-- The general rules of the criteria for the coexistence of elements are changed (see
6.2; see 6.2 of the 2017 edition);
-- The content “the safety requirements shall be assigned to sub-elements of
elements before the application of this chapter” is deleted (see 6.4.2 of the 2017
edition);
-- The contents “If sub-elements implementing requirements with different ASILs
coexist in the same element” are changed (see 6.4.4; see 6.4.5 of the 2017
edition);
-- The objectives of dependent failure analysis are changed (see 7.1; see 7.1 of the
2017 edition);
-- The general rules of dependent failure analysis are changed (see 7.2; see 7.2 of
the 2017 edition);
-- The prerequisites for dependent failure analysis are changed (see 7.3.1; see 7.3.1
of the 2017 edition);
-- The “repair error” is changed to “service failure” [see 7.4.4 e); see 7.4.4 e) of the
2017 edition];
-- The content “ageing and wear” is added [see 7.4.4 i)];
-- The requirement for the level of detail and rigor of dependent failure analysis is
added (see 7.4.8);
-- The verification basis requirements for dependent failure analysis are added (see
7.4.9);
-- The dependent failure analysis verification report is added (see 7.5.2);
-- The objectives of safety analysis are changed (see 8.1; see 8.1 of the 2017
edition);
-- The requirements and recommendations for safety analysis are changed (see
8.4.1; see 8.4.1 of the 2017 edition);
-- The safety analysis verification report is added (see 8.5.2).
This document is modified in relation to ISO 26262-9:2018 Road Vehicles - Functional
safety - Part 9: Automotive Safety Integrity Level (ASIL)-oriented and Safety-oriented
Analyses.
The technical differences between this document and ISO 26262-9:2018, and the causes
for these differences are as follows:
-- The description of T&B vehicles is changed from “trucks, buses, trailers, and
semi-trailers” to “goods vehicles, buses, special vehicles, and trailers” (see 4.6;
see 4.6 of ISO 26262-9:2018), so that the vehicle types are consistent with that
specified in GB/T 3730.1-2022 Terms and Definitions of Motor Vehicles,
Trailers and Combination Vehicle - Part 1: Types.
This document also makes the following editorial modifications:
-- The order of paragraphs in the Scope is adjusted;
-- The normatively referenced GB/T 34590.12-2022 is included in the list in
Chapter 2;
-- The addresses of the terminology database maintained by ISO and IEC for
standardization in Chapter 3 of ISO 26262-9:2018 are deleted;
-- The clause number 6.5.1 in ISO 26262-9:2018 is deleted.
Please be noted that certain content of this document may involve patents. The
institution issuing this document does not undertake the responsibility of identifying
these patents.
This document was proposed by the Ministry of Industry and Information Technology
of the People’s Republic of China.
This document shall be under the jurisdiction of the National Technical Committee of
Auto Standardization (SAC/TC114).
Road Vehicles - Functional Safety - Part 9: Automotive
Safety Integrity Level (ASIL)-oriented and Safety-oriented
Analyses
1 Scope
This document specifies the requirements for Automotive Safety Integrity Level
(ASIL)-oriented and safety-oriented analyses, including the following:
-- requirements decomposition with respect to ASIL tailoring;
-- criteria for coexistence of elements;
-- analysis of dependent failures; and
-- safety analyses.
This document is intended to be applied to safety-related systems that include one or
more electrical and/or electronic (E/E) systems and that are installed in series
production road vehicles, excluding mopeds.
This document does not address unique E/E systems in special vehicles such as E/E
systems designed for drivers with disabilities.
NOTE: Other dedicated application-specific safety standards can complement this document or vice
versa.
Systems and their components released for production, or systems and their
components already under development prior to the publication date of this document,
are exempted from the scope of this edition. This document addresses alterations to
existing systems and their components released for production prior to the publication
of this document by tailoring the safety lifecycle depending on the alteration. This
document addresses integration of existing systems not developed according to this
document and systems developed according to this document by tailoring the safety
lifecycle according to this document.
This document addresses possible hazards caused by malfunctioning behaviour of
safety-related E/E systems, including interaction of these systems. It does not address
hazards related to electric shock, fire, smoke, heat, radiation, toxicity, flammability,
reactivity, corrosion, release of energy and similar hazards, unless directly caused by
malfunctioning behaviour of safety-related E/E systems.
This document describes a framework for functional safety to assist the development
of safety-related E/E systems. This framework is intended to be used to integrate
functional safety activities into a company-specific development framework. Some
requirements have a clear technical focus to implement functional safety into a product;
others address the development process and can therefore be seen as process
requirements in order to demonstrate the capability of an organization with respect to
functional safety.
This document does not address the nominal performance of E/E systems.
Appendix A provides an overview on objectives, prerequisites and work products of
this document.
2 Normative references
The following documents contain the provisions which, through normative reference in
this document, constitute the essential provisions of this document. For the dated
referenced documents, only the versions with the indicated dates are applicable to this
document; for the undated referenced documents, only the latest version (including all
the amendments) is applicable to this document.
GB/T 34590.1-2022 Road Vehicles - Functional Safety - Part 1: Vocabulary (ISO
26262-1:2018, MOD)
NOTE: There is no technical difference between the quoted content of GB/T 34590.1-2022 and the
referenced content of ISO 26262-1:2018.
GB/T 34590.2-2022 Road Vehicles - Functional Safety - Part 2: Management of
Functional Safety (ISO 26262-2:2018, MOD)
NOTE: There is no technical difference between the quoted content of GB/T 34590.2-2022 and the
quoted content of ISO 26262-2:2018.
GB/T 34590.3-2022 Road Vehicles - Functional Safety - Part 3: Concept Phase (ISO
26262-3:2018, MOD)
NOTE: There is no technical difference between the quoted content of GB/T 34590.3-2022 and the
quoted content of ISO 26262-3:2018.
GB/T 34590.4-2022 Road Vehicles - Functional Safety - Part 4: Product Development
at the System Level (ISO 26262-4:2018, MOD)
NOTE: There is no technical difference between the quoted content of GB/T 34590.4-2022 and the
quoted content of ISO 26262-4:2018.
GB/T 34590.5-2022 Road Vehicles - Functional Safety - Part 5: Product Development
at the Hardware Level (ISO 26262-5:2018, MOD)
NOTE: There is no technical difference between the quoted content of GB/T 34590.5-2022 and the
quoted content of ISO 26262-5:2018.
GB/T 34590.6-2022 Road Vehicles - Functional Safety - Part 6: Product Development
at the Software Level (ISO 26262-6:2018, MOD)
NOTE: There is no technical difference between the quoted content of GB/T 34590.6-2022 and the
quoted content of ISO 26262-6:2018.
GB/T 34590.8-2022 Road Vehicles - Functional Safety - Part 8: Supporting Processes
(ISO 26262-8:2018, MOD)
NOTE: There is no technical difference between the quoted content of GB/T 34590.8-2022 and the
quoted content of ISO 26262-8:2018.
GB/T 34590.12-2022 Road Vehicles - Functional Safety - Part 12: Adaptation for
Motorcycles (ISO 26262-12:2018, MOD)
NOTE: There is no technical difference between the quoted content of GB/T 34590.12-2022 and the
quoted content of ISO 26262-12:2018.
3 Terms and definitions
The terms and definitions defined in GB/T 34590.1-2022 apply to this document.
4 Requirements
4.1 Purpose
This chapter describes how:
a) to achieve compliance with the GB/T 34590;
b) to interpret the tables used in the GB/T 34590; and
c) to interpret the applicability of each clause, depending on the relevant ASIL(s).
4.2 General requirements
When claiming compliance with the GB/T 34590, each requirement shall be met, unless
one of the following applies:
a) tailoring of the safety activities in accordance with GB/T 34590.2-2022 has been
performed that shows that the requirement does not apply; or
b) a rationale is available that the non-compliance is acceptable and the rationale
has been evaluated in accordance with GB/T 34590.2-2022.
analysis is to be performed: system, hardware, or software in accordance with
7.5.2 in GB/T 34590.4-2022, 7.5.1 in GB/T 34590.5-2022, or 7.5.1 in GB/T
34590.6-2022.
NOTE: The architectural information is used to determine the boundaries of the safety analyses.
8.3.2 Further supporting information
The following information can be considered:
-- fault models (from external sources).
8.4 Requirements and recommendations
8.4.1 The safety analyses shall be performed in accordance with appropriate standards
or guidelines and the defined objectives, for instance in the safety plan.
NOTE 1: The level of detail of the analysis is appropriate to the level of detail of the design. The fault
models depend on the description level of the design on which the analysis is based (System, Hardware,
Software), and on the safety requirements being implemented. For semiconductor failure modes, 4.3.2
of GB/T 34590.11-2022 can be considered.
NOTE 2: Such standards and guidelines can include criteria for defining the depth and rigor of a safety
analysis. These criteria can depend on the ASIL, complexity or experiences with a specific item, and its
field of application.
NOTE 3: The objectives and scope of the safety analyses depend on the sub-phase and the level of
granularity at which it is applied.
8.4.2 The results of the safety analyses shall indicate if the respective safety goals or
safety requirements are complied with or not.
8.4.3 If a safety goal or a safety requirement is not complied with, the results of the
safety analyses shall be used for deriving prevention, detection, or effect mitigation
measures regarding the faults or failures causing the violation.
8.4.4 The measures derived from the safety analyses shall be implemented as part of
the product development at the system level, at the hardware level, or at the software
level, in accordance with GB/T 34590.4-2022, or GB/T 34590.5-2022, or GB/T
34590.6-2022 respectively.
8.4.5 Hazards newly identified by safety analyses during product development which
are not already covered shall be included in an updated hazard analysis and risk
assessment according to Chapter 6 of GB/T 34590.3-2022. The corresponding changes
shall be managed in accordance with Chapter 8 of GB/T 34590.8-2022.
8.4.6 The fault models used for the safety analyses shall be suitable for the level of
detail being analysed in a given development sub-phase and shall be used consistently
......
Source: Above contents are excerpted from the PDF -- translated/reviewed by: www.chinesestandard.net / Wayne Zheng et al.
|