Search Results

Electrification calls for a range of system components, that need to be developed and tested. Execution of tests on real batteries is typically time- and cost-intense, and includes considerable risks, leading to safety hazards. In this paper, we introduce a novel development and test approach for battery systems, that is driven by a unified, standardized interface between hardware- and software components and physical devices alike. Whereas established Hardware-in-the-Loop (HiL) systems are built on proprietary systems and environments, our approach is based on both open-source and industrial simulation software solutions. The Distributed Co-Simulation Protocol (DCP) is used to encapsulate and virtualize these components, as shown in a demonstrator use case. A "DCP master" is used for effective configuration and re-configuration of so-called "DCP slaves".

Although the ISO 26262 provides requirements and recommendations for an automotive functional safety lifecycle, practical guidance on how to handle these safety activities and safety artifacts is still lacking. This paper provides an overview of a semi-formal safety engineering approach based on SysML for specifying the relevant safety artifacts in the concept phase. Using specific diagram types, different views of the available data can be provided that reflects the specific needs of the stakeholders involved. One objective of this work is to improve the common understanding of the relevant safety aspects during the system design. The approach, which is demonstrated here from the perspective of a Tier1 supplier for an automotive battery system, covers different breakdown levels of a vehicle. The safety workflow presented here supports engineers' efforts to meet the safety standard ISO 26262 in a systematic way.

The standard ISO 26262 stipulates a “top-down” approach based on the process “V” model, by conducting a hazard analysis and risk assessment to determine the safety goals, and subsequently derives the safety requirements down to the appropriate element level. The specification of safety goals is targeted towards identified hazardous events, whereas the classification of safety requirements does not always turn out non-ambiguous. While requirement formalization turns out to be advantageous, the translation from natural language to semi-formal requirements, especially in context of ISO 26262, poses a problem. In this publication, a new approach for the formalization of safety requirements is introduced, targeting the demands of safety standard ISO 26262. Its part 8, clause 6 (“Specification and management of safety requirements”) has no dedicated work product to accomplish this challenging task.

Automotive electric and electronic (E/E) systems are key drivers for innovation in today's vehicles. While new functions are delivering eco-friendliness (hybrid and pure electric vehicles, etc.), assistance/comfort (drive-by-wire, park-assist, etc.) and active safety (electronic stability control, lane-change-assist, brake-assist, etc.) their inherent complexity is challenging manufacturers and suppliers. At the same time, functional safety of the product is a key issue: During the whole car's product life cycle, there are many potential risks for physical injuries, or even worse, fatalities. Therefore, these potential sources of harm should strictly be avoided. In this work, we focus on a powerful method for verification and validation activities during early phases of the development, namely simulation. Simulation is one of the main methods for verification stated by the functional safety standard ISO 26262.

Functional safety of automotive embedded systems is a key issue during the development process. To support the industry, the automotive functional safety standard ISO 26262 has been defined. However, there are several limitations when following the approach directly as defined in the standard. Within this work, we propose an approach for the integration and test of safety-critical systems by using system modeling techniques. The combination of two state-of-the-art modeling languages into a dedicated multi-language development process provides a direct link between all stages of the development process, thus enabling efficient safety verification and validation already during modeling phase. It supports the developer in efficient application of requirements as defined by ISO 26262, hence reducing development time and cost by providing traceable safety argumentation.