Canada Spends Logo

Explorez notre analyse du budget 2026

Grant: Collaborative Research and Development Grants

McMaster University

$336,873.00

Safety assurance at GM and using model management to support it

EF 2019-20

Résumé
When a vehicle is designed, the car maker - the Original Equipment Manufacturer (OEM) - makes every effortto ensure that the vehicle will be safe and reliable. As vehicles have increased in complexity with the additionof software-enabled hybrid powertrains and Advanced Driver Assistance Systems, the system design and safetyprocesses have had a corresponding increase in required effort and difficulty. Recently, seemingly minorincremental changes in the vehicle's software and/or physical design have resulted in safety recalls because ofunforeseen subsystem interactions that have reduced vehicle safety and/or reliability to unacceptable levels. Tohelp address these issues, OEMs and their suppliers collaborated to produce the standard ISO 26262 RoadVehicles - Functional Safety, which prescribes processes and their outputs that should be produced as part ofthe system, software and safety processes for vehicle features that require different Automotive Safety IntegrityLevels. As OEMs and suppliers strive to be consistent with ISO 26262, an increasingly important questionarises: when can design and safety assurance artefacts be safely reused and when do the processes and theresulting work products have to be redone? Automotive companies must address this key question if they wantto remain competitive and be able to deliver ever safer vehicles at a purchase cost that the public is willing topay. To help the Canadian automotive industry address this issue, this project will model the design and safetyartefacts and their relationships with explicit safety assurance arguments known as a (safety) assurance case.We will provide model management processes and tools to analyze the models and determine the impact of adesign change on the assurance case. This will help engineers determine which parts of the assurance case canbe safely reused and where it requires further engineering effort to demonstrate that the new system isacceptably safe. The work will be extended to manage models of safety assurance for entire product lines tohelp OEMs deal with the reality of manufacturing for global product development.
Programme
Collaborative Research and Development Grants
Bénéficiaire
Emplacement
Ontario, Canada
Type de bénéficiaire
Academia
Type
Grant
Source
NSERC's Awards Data

Tel que publié

Application id
515486-2017
Name nom
Lawford, Mark
Department département
Computing and Software
Organization id
27
Institution établissement
McMaster University
Province en
Ontario
Province fr
Ontario
Country en
CANADA
Country fr
CANADA
Fiscal year exercice financier
2019
Competition year année de concours
2017
Award amount
336873
Program id
CRDPJ
Program name en
Collaborative Research and Development Grants
Program name fr
Subventions de recherche et développement coopérative
Group en
RESEARCH PARTNERSHIPS
Group fr
PARTENARIATS DE RECHERCHE
Committee code
141
Committee name en
University/Industry
Committee name fr
Universités/industrie
Area of application code
801
Area of application group en
Information and communication services
Area of application group fr
Services d'information et de télécommunications
Area of application en
Computer software
Area of application fr
Logiciel
Research subject code
2706
Research subject group en
Information technology
Research subject group fr
Technologie de l'information
Research subject en
Software engineering
Research subject fr
Génie logiciel
Installment
inst:3 - 3
Partie
3
Nb partie
3
Application title
Safety assurance at GM and using model management to support it
Keyword
NSERC
Application summary
When a vehicle is designed, the car maker - the Original Equipment Manufacturer (OEM) - makes every effortto ensure that the vehicle will be safe and reliable. As vehicles have increased in complexity with the additionof software-enabled hybrid powertrains and Advanced Driver Assistance Systems, the system design and safetyprocesses have had a corresponding increase in required effort and difficulty. Recently, seemingly minorincremental changes in the vehicle's software and/or physical design have resulted in safety recalls because ofunforeseen subsystem interactions that have reduced vehicle safety and/or reliability to unacceptable levels. Tohelp address these issues, OEMs and their suppliers collaborated to produce the standard ISO 26262 RoadVehicles - Functional Safety, which prescribes processes and their outputs that should be produced as part ofthe system, software and safety processes for vehicle features that require different Automotive Safety IntegrityLevels. As OEMs and suppliers strive to be consistent with ISO 26262, an increasingly important questionarises: when can design and safety assurance artefacts be safely reused and when do the processes and theresulting work products have to be redone? Automotive companies must address this key question if they wantto remain competitive and be able to deliver ever safer vehicles at a purchase cost that the public is willing topay. To help the Canadian automotive industry address this issue, this project will model the design and safetyartefacts and their relationships with explicit safety assurance arguments known as a (safety) assurance case.We will provide model management processes and tools to analyze the models and determine the impact of adesign change on the assurance case. This will help engineers determine which parts of the assurance case canbe safely reused and where it requires further engineering effort to demonstrate that the new system isacceptably safe. The work will be extended to manage models of safety assurance for entire product lines tohelp OEMs deal with the reality of manufacturing for global product development.