{"id":53613,"date":"2021-05-04T03:00:19","date_gmt":"2021-05-04T10:00:19","guid":{"rendered":"https:\/\/www.jamasoftware.com\/?p=53613"},"modified":"2023-01-12T16:49:12","modified_gmt":"2023-01-13T00:49:12","slug":"automotive-engineering-and-management-methods-for-modern-vehicle-development-addressing-functional-safety","status":"publish","type":"post","link":"https:\/\/www.jamasoftware.com\/legacy\/blog\/2021\/05\/04\/automotive-engineering-and-management-methods-for-modern-vehicle-development-addressing-functional-safety\/","title":{"rendered":"Automotive Engineering and Management Methods for Modern Vehicle Development \u2013 Addressing Functional Safety"},"content":{"rendered":"

\"functionalMy last blog post covered why and how the automotive sector is changing fast over the last few years \u2013 you can find that post here<\/a>. A common expectatio<\/span>n is that our future cars will be connected, automated, shared, and electric. In a current Motional Consumer Mobility report<\/a>, Americans were asked what is their most important consideration to use a self-driving vehicle. Nearly two-thirds of Americans (65 <\/span>percent) say safety is the most important consideration when deciding to use a self-driving vehicle.\u00a0So let\u2019s take a closer look at automotive functional safety and how to deliver a safe product.<\/span>\u00a0<\/span><\/p>\n

Safety Considerations for Product Design<\/span><\/b>\u00a0<\/span><\/h2>\n

Modern cars are a complex piec<\/span>e of technology. They are connected, have sophisticated Infotainment Systems (IVI) and Advanced Driver Assistance Systems (ADAS). You will be surprised about the amount of software used in the 30 to 70 electronic control units in a car. There are up to 100<\/span> million\u00a0lines of code deployed in a modern high-end car today. System complexity will increase even more when we move beyond ADAS-supported driving to Automated Driving Systems (ADSs) in the future. <\/span><\/p>\n

The challenge for the industry is that new potential haz<\/span>ards may arise with the increasing use of electronics and software in cars. Apart from complex technology and consumers\u2019 expectations, we will get regulations covering the safety of future cars. In the U.S., this is the responsibility of the National Highw<\/a><\/span>ay Traffic Safety Administration (NHTSA). <\/span><\/p>\n

Defined by the Vehicle Safety Act in 1966, the NHTSA has the sole authority to make final decisions on rules and safety standards for future road vehicles. Once the NHTSA establishes a standard, the Agency is requi<\/span>red to ensure that manufacturers comply when producing new vehicles. <\/span><\/p>\n

In 2016 the NHTSA published “Vision for Safety,” a non-regulatory approach to automated vehicle technology safety. <\/span>\u201cEntities are encouraged to follow a robust design and validation proces<\/span><\/i>s based on a systems-engineering approach to design ADSs free of unreasonable safety risks.\u00a0<\/span><\/i>The overall process should adopt and follow industry standards, such as the functional safety process standard for road vehicles…\u201d<\/span><\/i><\/b>\u00a0<\/span><\/p>\n

Which industry standard is the<\/span><\/b>\u00a0NHTSA referring to?<\/span><\/b>\u00a0<\/span><\/h3>\n

The mentioned standard is the ISO 26262 standard. First issued by International Organization for Standardization (ISO) in 2011 and later updated in 2018. The ISO 26262 is titled \u201cRoad vehicles – functional safety,” the first comprehens<\/span>ive voluntary industry standard for safety\u00a0<\/span>engineering of Electrical and Electronic Systems (E\/E) in road vehicles. This standard recognizes that safety is a system attribute and can be addressed using systems engineering methods. ISO 26262 emphasizes the\u00a0<\/span>importance of implementing a safety engineering management and fostering a safety culture.<\/span>\u00a0<\/span><\/p>\n

What is functional safety and how to comply?<\/span><\/b>\u00a0<\/span><\/h4>\n

Functional safety is defined as the \u201cabsence of unreasonable risk due to hazards caused by malfunctioning behavior of el<\/span>ectrical\/electronic systems.” The goal of ISO 26262 is to ensure safety from the earliest concept to the point when the vehicle is retired. <\/span>To ensure vehicle safety, the standard outlines an automotive safety life cycle that describes the entire production<\/span>\u00a0life cycle.\u00a0<\/span>\u00a0<\/span><\/p>\n

Specific steps are required in each phase of the safety life cycle. One of the most important steps at the beginning of the safety life cycle is the Hazard & Risk Analysis of potential hazards (HARA). The result is an Automotive Safety\u00a0<\/span>Integrity Level (ASIL) classification of the hazard and the formulation of an overall safety goal. Safety goals are basically the level of safety required by a system or component to function without posing any threats to the vehicle.<\/span>\u00a0<\/span><\/p>\n

An ASIL is\u00a0<\/span>assigned\u00a0<\/span>by evaluating three risk parameters,\u00a0<\/span>severity, exposure, and controllability. Severity defines the consequences to the life of people due to the failure that may occur.<\/span>\u00a0<\/span>Exposure is the likelihood of the conditions under which a particular failure would res<\/span>ult in a safety hazard.<\/span>\u00a0<\/span>Controllability determines the extent to which the driver will be able to control the vehicle should a safety goal be breached due to the failure or malfunctioning<\/span>. An ISO 26262 method provides guidance on how to assign the ASIL for<\/span>\u00a0a hazard once severity, exposure, and controllability are determined.\u00a0<\/span>\u00a0<\/span><\/p>\n

In the next step, a functional safety concept is developed for each safety goal. The functional safety concept defines functional safety requirements wit<\/span>hin the context of the vehicle<\/span>\u00a0architecture, including fault detection<\/span>\u00a0and failure mitigation mechanisms, to satisfy the safety goals. Then the technical safety concept is developed to specify the technical safety requirements within the system architecture. The technical safety concep<\/span>t is the basis for deriving the hardware and software safety requirements that are used for developing the product. These safety requirements\u00a0have to\u00a0be traced, managed and validated through product development to assure the delivery of a safe product.<\/span>\u00a0<\/span><\/p>\n

\n

RELATED:<\/strong> <\/span>Watch a demonstration of the Jama Connect for Automotive Solution<\/a><\/span><\/b><\/h4>\n
\n

Why<\/span><\/b>\u00a0is functional safety important?<\/span><\/b>\u00a0<\/span><\/h3>\n

Functional Safety describes a risk-based system engineering approach to avoid unreasonable risk. From a business aspect, using ISO 26262 as a guideline helps you to avoid costly product recalls due to safety hazards. Tesla\u00a0<\/span>recalled roughly 135,000 Model S and Model X vehicles over Touch-Screen failures in February 2021. The move came after the National Highway Traffic Safety Administration requested a safety recall. NHTSA asked for the recall because the center display in so<\/span>me models can fail when a memory chip runs out of storage capacity, affecting safety functions such as windshield defogging and defrosting controls, exterior turn signal lighting, and rearview backup camera display.<\/span>\u00a0<\/span><\/p>\n

Following the standard minimizes the ri<\/span>sk of harm to people and non-acceptance of your products by the market.\u00a0In particular, a<\/span>utomobile\u00a0manufacturers have a legal responsibility to design their vehicles to guarantee driver, passenger, and pedestrian safety.\u00a0As a consequence, automobile manufac<\/span>turers can be named as defendants in a product liability suit. For example,\u00a0<\/span>Toyota Motors agreed to pay $1.2 billion to settle the Justice Department\u2019s criminal investigation into whether the company hid safety defects related to unintended acceleration in<\/span>\u00a02014.<\/span>\u00a0<\/span><\/p>\n

Takeaway<\/span><\/b>\u00a0<\/span><\/h3>\n

Functional safety is an essential part of product development and needs to be addressed early in the concept phase and considered through the full product\u00a0life-cycle. ISO 26262 offers an engineering guideline and methods to avoid or at leas<\/span>t mitigate systematic failures and random hardware failures of Electrical and Electronic Systems. The derived functional safety requirements\u00a0have to\u00a0be implemented at the lowest level up to the system level, both from a hardware and software perspective. T<\/span>his offers the ability to prove that the added E\/E-systems\u00a0are free of unreasonable safety risks.<\/span>\u00a0<\/span><\/p>\n

The pragmatic engineering approach is to use existing knowledge,\u00a0<\/span>or how I call it, to use the industry\u2019s memory. You should look at the ISO 26262 series as t<\/span>he\u00a0framework, and\u00a0set of guidelines and methods. ISO 26262 can help you with system engineering methods for a safe product and still give you some flexibility in the development process. T<\/span>his is especially helpful for newcomers to the automotive industry,\u00a0<\/span>who may lack specific automotive safety engineering experience.<\/span>\u00a0<\/span><\/p>\n

Let’s put it that way, using existing engineering methods and knowledge is like standing on the shoulders of a giant \u2013 you can see further. This is even more true for automotive <\/span>product safety because there is no room for trial and error.<\/span>\u00a0<\/span><\/p>\n

Stay tuned<\/span><\/b>: T<\/span>he next blog post in this series will give real-life advice on how to implement functional safety in your organization and products, and a glance at the evolution of functional safety for autonomo<\/span>us driving.<\/span>\u00a0<\/span><\/p>\n

\n

<\/p>\n

<\/div>\n