Matt Schroeder Executive Director, Vehicle Systems 7 th AUTOSAR Open Conference

Size: px
Start display at page:

Download "Matt Schroeder Executive Director, Vehicle Systems 7 th AUTOSAR Open Conference"

Transcription

1 Matt Schroeder Executive Director, Vehicle Systems 7 th AUTOSAR Open onference

2 Keynote Address: 7 th AUTOSAR Open onference Introduce new organization within General Motors focused on Vehicle Systems Engineering The complexity of future E/E Systems drives the need for a holistic approach to vehicle design by OEMs Look for AUTOSAR Development ooperation to continue to meet the challenges of Managing the E/E complexity Integrating new technologies

3 Global Product Integrity Organization A new organization has been created at General Motors - Global Product Integrity, or GPI. This team is accountable for system integration and oversight across the Vehicle and Powertrain functions to ensure delivery of award-winning vehicles with consistent safety and compliance performance. Within GPI, The Global Vehicle Safety Organization was strengthened by establishing single point accountability. The Systems Engineering organization was created to increase focus on systems interactions.

4 Methodology: Systems Thinking Vehicle Level Requirements Drive Vehicle Environment System Global Product Integrity Systems Engineering Subsystem 2 Subsystem 1 Subsystem 4 Subsystem 3 omponent & Subsystems Subsystem omponent 1 omponent 2 omponent 3

5 Importance of System engineering GM believes that robust system engineering is foundational for execution of sophisticated, complex distributed control systems These are the dominant systems of the future active safety, semi-autonomous,. Functional safety requirements also drive the need for robust tools, process for system engineering

6 Systems Engineering -> Features Feature Technical Specification Feature Functions Requirements for Feature Allocation of Feature to Domain Systems System Technical Specification Allocation of Feature Requirements to SMT Subsystem SE Domains FTS F FTS F STS STS S S SSTS SSTS TS TS omponent where Subsystem does not exist Entity Specification FTS F STS S SSTS Feature Domain System Sub-System omponent F S SS FTS STS SSTS TS FTS FTS F F STS STS S S SSTS

7 AUTOSAR Vision Supports GM s Goals! AUTOSAR aims to improve complexity management of integrated E/E architectures through increased reuse and exchangeability of SW modules between OEMs and suppliers. OEM b OEM a Platform b.1 Platform b.2 Platform b.n Exchangeability between suppliers OEM c solutions Platform a.1 Platform a.2 Platform a.n Exchangeability between manufacturers applications OEM f Platform f.1 Platform f.2 Platform f.n Supplier A hassis Safety Body/ omfort OEM e Supplier Platform e.1 Platform e.2 Platform e.n Supplier B hassis Safety Telematics Body/omfort Powertrain Telematics Platform c.1 Platform c.2 Platform c.n OEM d Platform d.1 Platform d.2 Platform d.n Exchangeability between vehicle platforms AUTOSAR Guided Tour (Part 1) Motivation and Principles

8 GM urrent Position on AUTOSAR AUTOSAR 4.x forms the cornerstone of our next global Electrical Architecture We know that AUTOSAR can form the foundation of automotive systems that deliver the features our customers want with high quality We have a long (20 year) experience with internally developed SW and the importance of strong architectures, process and tools for robust system development

9 omplexity of GM Software Landscape GM Developed Application Software Deeply Embedded GM Developed Application Software Externally Developed Application Software GM Developed Application Software Lightly Embedded Externally Developed Application Software (AUTOSAR BSW) (GM BSW) (AUTOSAR BSW) (Infotainment-based BSW) (Infotainment-based BSW) Standardized Interactions Safety Systems Safety (ommunication, Systems Safety, Security, V2V, etc.) Due to our scale and global reach, we need to have a comprehensive solution across our internally/ externally developed software space. Stable, standardized interfaces to BSW (integrations with non- AUTOSAR systems) are key

10 hallenges for the Auto Industry Dramatically increasing functional requirements active safety, new fuel consumption / GreenHouseGas regulation while maintaining an excellent value for our customers Increased expectations for functional safety of embedded systems. Potential threats from hackers leading to new demands for cybersecurity Speed of new feature deployment to customers accustomed to consumer electronics industry product cycle times

11 GM s Priorities - Required Support from AUTOSAR System Safety ybersecurity Ethernet and Diagnostics Automated Driving onnected Vehicles

12 SMT Feedback loop Formal ombined Peer Reviews For Each Phase Upon definition, each feature will be examined for its influence on System Safety. If the feature contains safety hazards, a formal System Safety ase become part of the systems engineering deliverables for that feature Systems Engineering Feature Definition oncept PHA, SEFA, SS System Safety oncept Phase System Definition System DFMEA Safety Requirements Requirements Phase System Design (Subsystem, omponent) Design Safety onfirmation Design Phase Implemented System Implementation Safety onfirmation Implementation Phase Validated System alibrated System Safety onfirmation Validation Phase System Engineering System Approved for Production

13 Feedback loop Systems Engineering provides a framework to allow for the secure end to end design, development and testing of connected and critical vehicle systems. Systems Engineering Architecture Definition Architecture oncept ybersecurity Architecture Requirements ybersecurity Architecture Threat Modeling Subsystem Definition Subsystem oncept ybersecurity Subsystem Requirements Subsystem Threat Modeling System Design (Subsystem, omponent) Design ybersecurity omponent Requirements omponent Security Assessment Implemented System Implementation omponent Security Testing Feedback omponent Security Testing Validated System Secured End-to-End System ybersecurity Testing Feedback ybersecurity Testing Systems Engineering System Approved for Production omponent Teams ybersecurity

14 Future Needs in Ethernet and Diagnostics urrent State of the Industry Typical subnets still designed around AN or AN-FD bandwidth capacity Ethernet is of interest for specific applications requiring high capacity, high speed, time sensitive networks (High End Infotainment and Active Safety) Legacy point-to-point diagnostic strategies with off-board test tools Vehicle Flash Programming data sizes measured in Megabytes Ethernet - Future of Automotive Electrical Architecture? Significant number of applications requiring high bandwidth, time sensitive, and most importantly - secure networks Flat, self-healing architectures with significant shared data and redundancy Big data in the vehicle with multiple test tools and continuous monitoring Vehicle Flash Programming data sizes measured in Gigabytes

15 Key hallenges for AUTOSAR Defining standardized interfaces with non- AUTOSAR systems, AUTOSAR enables GM to stay focused on our system-engineering based approach Maintaining AUTOSAR as a relevant, vital global standard is in the best interest of the global automotive industry Finding ways to accelerate the pace of new technology introduction while preserving the stability of the standard