Standards List

"his 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 exist and can complement the ISO 26262 series of standards 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.
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.
This document specifies the requirements for supporting processes, including the following:
— interfaces within distributed developments;
— overall management of safety requirements;
— configuration management;
— change management;
— verification;
— documentation management;
— confidence in the use of software tools;
— qualification of software components;
— evaluation of hardware elements;
— proven in use argument;
— interfacing an application that is out of scope of ISO 26262; and
— integration of safety-related systems not developed according to ISO 26262.

In addition to the guidelines in ISO 19011, this document provides guidelines to organizations that contribute to the achievement of road vehicle cybersecurity throughout the supply chain on:
— managing an audit programme for a cybersecurity management system (CSMS);
— conducting organizational CSMS audits;
— competencies of CSMS auditors; and
— providing evidence during CSMS audits.
Elements of the CSMS are based on the processes described in ISO/SAE 21434. This document is applicable to those needing to understand or conduct internal or external audits of a CSMS or to manage a CSMS audit programme.
This document does not provide guidelines on cybersecurity assessments.

This document introduces basic common underlying concepts related to driver performance and state in the context of automated driving. The concepts in this document are applicable to all levels of automated driving functions that require a human/driver to be engaged or fallback-ready (SAE level 1, 2 and 3). It can also be used with levels that enable a driver to resume manual control of the vehicle (a compatible feature for SAE levels 1 to 5).
Common underlying concepts can be applicable for human factors assessment/evaluations using driving simulators, tests on restricted roadways (e.g. test tracks) or tests on public roads. The information applies to all vehicle categories.
This document contains a mixture of information where technical consensus supports such guidance, as well as discussion of those areas where further research is required to support technical consensus. These common underlying concepts can be also useful for product descriptions and owner manuals. The contents in this document are informative, rather than normative, in nature.

This document focuses on system-initiated and human-initiated transitions (Clause 6) from a higher level to a lower level of automated driving. Human factors and system factors that can influence takeover performance are included (Clauses 7 and 8). Although some are still under investigation, there is a need to appropriately set these factors as variables to better understand their effects or to better control/eliminate their influence. This approach will aid research design by ensuring that important factors are considered and support consistency across studies enabling meaningful comparisons of findings. This document also includes information on considerations in test scenario design (Clause 9), common measures for human takeover performance (Clause 10) and considerations in choosing a testing environment (Clause 11) to help readers design experiments comparable to other studies.

This document defines the terms which are used in the ISO 21111 series and provides an overview of the standards for in-vehicle Ethernet including the complementary relations to ISO/IEC/IEEE 8802-3:2017[7] and its amendments, the document structure in accordance with OSI reference model specified in ISO/IEC 7498-1[1] and ISO/IEC 10731:1994,[2] type of physical entities, in-vehicle Ethernet specific functionalities, and so on.

This document specifies the following items to complement ISO/IEC /IEEE 8802-3:
— interface between reconciliation sublayer and physical entity including reduced gigabit media independent interface (RGMII);
— common physical entity wake-up and synchronised link sleep functionalities independent from physical media and transmission bit rate.
The optical and electrical component requirements and test methods for optical and electrical transmission of in-vehicle Ethernet are not in the scope of this document.

This document provides supplemental specifications to a physical layer capable of transmitting 1 Gbit/s over plastic optical fibre compliant with ISO/IEC/IEEE 8802-3:2017/Amd 9:2018, with specific application to communications inside road vehicles.
Additionally, there is a test plan specified for conformance testing. The test plan includes test cases to assure compliance of an IUT with the functionality specified in this document.
ISO/IEC/IEEE 8802-3:2017/Amd 9:2018 is considered indispensable for the application of this document.
The supplemental specifications include wake-up and synchronised link sleep functionality. The specification includes the sublayers, service interfaces, and state diagrams that support the functionality. The supplemental specifications are collected in protocol implementation conformance statement (PICS).
The requirements specified in ISO/IEC/IEEE 8802-3:2017/Amd 9:2018 and in this document constitute the complete PICS that specifies the GEPOF physical entity functionality.
The optical component requirements and test methods for optical 1-Gbit/s transmission of in-vehicle Ethernet are not within the scope of this document.

This document specifies the optical components requirements and test methods for optical gigabit transmission of in-vehicle Ethernet. Safety (electrical safety, protection, fire, etc.) and electromagnetic compatibility (EMC) requirements are outside the scope of this document.

This document specifies:
— requirements on the physical layer at system level,
— requirements on the interoperability test set-ups,
— interoperability test plan that checks the requirements for the physical layer at system level,
— requirements on the device-level physical layer conformance test set-ups, and
— device-level physical layer conformance test plan that checks a set of requirements for the OSI physical layer that are relevant for device vendors.
The interoperability test plan checks the physical layer system requirements specified in this document and in ISO/IEC/IEEE 8802-3:2017/Amd 9.
This test plan is structured in four different test groups, attending to the kind of system requirements that covers:
— link status, that includes the tests that check the status of the link by using the content of the available registers and its accuracy with the real status of the link,
— link-up, that includes the tests that check the time that the IUT reaches a reliable link status from certain state,
— channel quality, that includes the tests that check the quality of the optical channel by using the content of the available registers and its accuracy with the real quality of the optical channel, and
— wake-up and sleep, that include tests that check that the transmission and reception of the wake-up and sleep events.
The device-level conformance test plan checks the device-level requirements specified in the ISO 21111 series and in ISO/IEC/IEEE 8802-3:2017/Amd 9.
This test plan is structured in four different test groups, attending to the test set-up required:
— high-attenuation channel,
— low-attenuation channel,
— optical IUT transmitter measurements, and
— wake-up and synchronised link sleep.

This document specifies advanced features of an ISO/IEC/IEEE 8802-3 automotive Ethernet PHY (often also called transceiver), e.g. for diagnostic purposes for automotive Ethernet PHYs.
This document specifies:
— advanced PHY features;
— wake-up and sleep features;
— PHY test suite;
— PHY control IUT requirements and conformance test plan;
— PCS test suite;
— PCS IUT requirements and conformance test plan;
— PMA test suite; and
— PMA IUT requirements and conformance test plan.