Functional Safety

In recent years, the increasing advancement and proliferation of automated driving have brought about a need for standards such as ISO 26262 that defines functional safety along with functions that contribute to the prevention of accidents in the event of an emergency. As such a growing number of companies are promoting functional safety not only among automotive manufacturers (OEMs), but Tier 1 electronics equipment suppliers as well, making it an increasingly important requirement worldwide.
The 1st Edition of ISO 26262, a functional safety standard for automotive electronics and electrical systems, was published in November 2011, then after several revisions the 2nd Edition was released in December 2018.

ROHM’s Approach to Functional Safety

ROHM began establishing an ISO 26262 process in 2015 then subsequently acquired ISO 26262 process certification from 3rd party certification body TÜV Rheinland in March of 2018, approx. two and a half years later. As a result, ROHM’s ISO 26262 process is recognized to be compliant with the ISO 26262 standard. And while it is common to build a process by receiving advice from consultants, ROHM took the extra step of attending workshops to better understand and study the standard to successfully achieve a standard-compliant process.

ISO 26262 process certification

Available Functional Safety-Related Forms

ROHM has identified 3 functional safety product categories

FS Process Compliant
A product that has been developed based on an ISO 26262 design process compliant to the ASIL level described in the datasheet.
FS Mechanism Implemented
A product that has implemented safety mechanism to meet ASIL level requirements described in the datasheet.
FS Supported
A product that has been developed for automotive use and is capable of supporting safety analysis with regard to the functional safety.

Provided Materials List

PS Process Compliant FS Mechanism Implemented FS Supported
IATF16949
Process Compliant
ISO 26262
Process Compliant
FMEA
FIT
FMEDA ✓*
Safety Manual

*FMEDA does not include analysis such as hardware architecture metrics.