1 / 30

SB09Q3ss01-MTL

Systems Engineering of GM’s Global EE / SW Product Line. Dr. Joseph D’Ambrosio. ECS Process, Methods , & Tools GLOBAL RESEARCH & DEVELOPMENT. SB09Q3ss01-MTL. Outline. Introduction Embedded Systems Development at GM Product Line Engineering Additional Topics.

ryo
Télécharger la présentation

SB09Q3ss01-MTL

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Systems Engineering of GM’s Global EE / SW Product Line Dr. Joseph D’Ambrosio ECS Process, Methods, & Tools GLOBAL RESEARCH &DEVELOPMENT SB09Q3ss01-MTL

  2. Outline • Introduction • Embedded Systems Development at GM • Product Line Engineering • Additional Topics

  3. About Me – Dr. Joseph D’Ambrosio • Automotive Industry 25+ years • GM, Delphi • Research, Advance Development, Product Development • Model-Based Sys. & SW Development, Safety-Critical Systems, Cyber Security, By-Wire Systems, Vehicle Control Systems, VLSI Design & Tools, Testing • ISO Technical Expert – ISO 26262 Automotive Functional Safety Standard • PhD University of Michigan – EE Design Methods / Optimization • 50+ publications, 7 patents

  4. Warren, MI SHANGHAI, CHINA Palo alto, ca HERZLIYA, ISRAEL

  5. BIG THINGS ARE COMING… There Has Never Been A Better Time To Be An AUTOMOTIVE EMBEDDED SYSTEM ENGINEER AND WE HAVE A FRONT ROW SEAT!

  6. CURRENT DNA NEW DNA Energized by Petroleum Energized by Biofuels,Electricity, and Hydrogen Powered Mechanically by Internal Combustion Engine Powered Electrically by Electric Motors Controlled Mechanically Controlled Electronically Stand-alone “Connected” Totally Dependence on the Driver Semi/Full Autonomous Driving Vehicle Sized for Max Use – People and Cargo Vehicle Tailored to Specific Use

  7. CADILLAC DRIVER ASSISTANCE / ACTIVE SAFETY Package1 – “Driver Awareness Package” Package2 – “Driver Assist Package” Cadillac ATS Cadillac XTS Cadillac SRX Cadillac ATS Cadillac XTS Cadillac SRX Long/Mid Range Radar Front Camera Short Range Radars Ultrasonic Sensors Front Camera Short Range Radars Rear Camera Ultrasonic Sensors • Lane Departure Warning • Forward Collision Alert • Side Blind-Zone Alert • Rear Cross-Traffic Alert • Haptic Safety Alert Seat Feedback • Also includes: • Rear Vision Camera • Front & Rear Park Assist Short Range Radars Short Range Radar Safety Alert Seat Rear Camera • Package 1 plus: • Full Speed-Range ACC (Stop w/Go Notifier) • Auto Collision Preparation (includes Collision Imminent Braking) • Low-Speed Front/Rear Automatic Braking (Emergency Braking to Avoid Contact) 7 7

  8. Improving Safety with V2V/V2X COMMUNICATIONS + “Warning” “Warning”

  9. AUTONOMOUS DRIVING Forward Vision System – Lane tracking – Object detection – Far IR Capability Short-RangeSensors Short-RangeSensors Long-Range ScanningSensor Long-RangeSensors Enhanced Digital Map System Rear Vision System – Object detection – Far IR Capability Forward Vision System Ultrasonic Sensors Ultrasonic Sensors Dedicated Short-Range Communication + GPS (V2V)

  10. En-v Video

  11. Outline • Introduction • Embedded Systems Development at GM • Product Line Engineering • Additional Topics

  12. OUR CONTRIBUTION…

  13. History of GM Automotive Computing • First Embedded Controllers • 1977 – First GM production automotive microcontroller • Electronic spark timing • 1981 – All GM North American vehicles use microcontroller-based engine controls • 3.9M vehicles total, 22K ECMs per day manufacturing rate • 50,000 lines of assembly code, MC6800 – 8-bit 2 Mhz, • Comparison against PC industry • Today • 40-70 microcontrollers per vehicle • 400K Lines of C Code for an engine control application • 64Mb flash file system for infotainment application PC Sales (in 1000s)

  14. GM Embedded Software History Model-based Development Assembly Language Modula-GM (Ada-like) ANSI C 1985 1990 1995 2000 2005 2010 #include <stdio.h> struct vehicle { char make[15]; long miles; float operating_costs; }; void show_vehicle(struct vehicle *); void main() { struct vehicle car[] = {“Chevrolet: 100000L, 3456.78, Ford, 11000L, 5000.00}; show_vehicle (car) } void show_vehicle(struct vehicle *vehicle_ptr) { . . . DEFINITION MODULE Buffer; VAR nonempty, nonfull:BOOLEAN; PROCEDURE put (x:INTEGER); PROCEDURE get (VAR x:INTEGER); END Buffer. IMPLEMENTATION MODULE Buffer; CONST N=num_lines; VAR in, out: [0..N-1]; n: [0..N]; PROCEDURE put (x:INTEGER); BEGIN IF n<N THEN buf[n]:=x; . . . LDAA #ACPRESUR JSR ADCON STAA ACPRES BRCLR INPUTS,IACREQ,ACPR050 BRESET DIAGMW3,M66DET,ACPR050 BRCLR INPUTS,INOAC,ACPR060 ACPR050 BCLR TBIMW,ACPRESHI JMP IMNRO060 . . .

  15. Classes of Embedded Systems • Deeply Embedded • Real Time, Possibly Safety Critical • Examples: Electronic Power Steering, Electronic Brake Controls, Powertrain, Active safety • Development Tools: Simulink/Stateflow • Future SW Architecture: AUTOSAR • Moderately Embedded • Loosely Real Time • Example: Body Control, Instrument Panel, Heating/Cooling • Development Tools: e.g., Rhapsody • Future SW Architecture: AUTOSAR • Lightly Embedded • Non Real Time, but may include data streaming; Security is important • Example: Infotainment Systems • Future SW Architecture: e.g., QNX/Linux, ANDROID, …

  16. Classes of Embedded Systems • Closed-Loop Control Systems • Based upon control system theory (e.g., PID control) • Examples: Steering systems, braking systems, propulsion systems • GM Tools: Simulink/Stateflow • State-Based Systems • Based upon state transition diagrams • Example: Body control • GM Tools: Rhapsody

  17. Classes of Embedded Systems • Non Safety Critical – no potential to cause harm • Detect fault, save diagnostic trouble code, possibly alert driver • Tools: DFMEA, Requirements-Based Testing, … • Safety Critical – potential to cause harm; timing properties are important • Fail Safe – detect fault, shut down within required fault response time, warn driver • Fail Operational – detect fault, continue to operate, possibly in a degraded mode, warn driver • Tools: Preliminary Hazard Analysis, Safety Concept, DFMEA, Fault Tree Analysis, Requirements Analysis, … Safety Case

  18. Model-Based Development Environment • Algorithms: Simulink / Stateflow, Rhapsody • Plant modeling: Simulink, Saber, GT Power, AmeSim, CarSim, … • Non Functional System Properties • Timing / Utilization: SymtaS • Electrical: Design Architect, Siemens NX • DOORS, Gears, Rhapsody, RTC, Synergy

  19. Outline • Introduction • Embedded Systems Development at GM • Product Line Engineering • Additional Topics

  20. GM has one of the most complex systems and software product line engineering challenges in the world 3000 contributing engineers 300 hierarchical subsystems Thousands of variant features Millions of product instances per year Tens-of-thousands of unique product variants Dramatic increase in variation due to new propulsion systems and active safety Global diversity in legislative regulations Extreme economic and competitive pressures Product line and feature set evolves annually 15 concurrent development streams General Motors Electrical, Controls and Software

  21. System Design Motivation Speed Cost Quality Reuse Standardization Understanding Volume Global Footprint Safety and Security Growing Complexity

  22. GM Enables massive Reuse through Software Product Lines • A Product Line is a set of systems sharing a common, managed set of features that are developed from a common set of core assets in a prescribed way • Why Product Line over Products for GM Embedded Software? • As much as an 85% reduction in effort for a second (third, fourth, etc.) application • As much as a 70% reduction in field claims overall

  23. Macro Engineering MethodA System of Systems of Systems Cloud of Standard Solutions (The Product Line) Change dialog to expand product line to fill gaps R &D / Advanced Best Fit Selection Standardized Set of Deployments Each Deployment Applied to Multiple Vehicles

  24. Vehicle Control System Development ACC LDW LXC CTD KLE VRP EngCyc IMC DFI ACC-v1 ACC-v1 ACC-v1 ACC-v1 ACC-v1 ACC-v1 ACC-v1 ACC-v1 ACC-v1 ACC-v1 ACC-v1 ACC-v1 ACC-v1 ACC-v1 ACC-v1 ACC-v1 ACC-v1 ACC-v1 DFI-v1 KLEC-v1 LXC-v1 LDW-v1 IMC-v1 CTD-v1 ACC-v1 VRP-v1 EngC-v1 ACC-v3 ACC-v1 KLEC-v5 KLEC-v2 LXC-v3 LXC-v3 VRP-v2 VRP-v1 EngC-v1 EngC-v1 DFI-v5 DFI-v3 CTD-v1 Buick Chevrolet

  25. Software Product Line - Single Vehicle View Vehicle Controller Increasing level of integration Assembly SW Components Requirements Decreasing level of abstraction Subsystems – Chassis Engine, etc. Vehicle

  26. Software Product Line - Single Component View Controllers 1-n Assembly Increasing level of integration SW Component Decreasing level of abstraction Requirements Subsystems – Chassis Engine, etc. Vehicles

  27. Software Product Line - Components X Vehicles Represents all builds in the Product Line Represents all components in the Product Line Represent all vehicles supported by the Product Line

  28. Outline • Introduction • Embedded Systems Development at GM • Product Line Engineering • Additional Topics

  29. Additional Topics • AUTOSAR • Multicore systems • Cyber Physical System • Virtual Development • Multi Domain Models • System Optimization • Safety-Critical Systems • SysML, AADL, East ADL, SystemC

  30. Thank You!

More Related