Models Meeting Automotive Design Challenges Dr Henrik Lnn Volvo - PowerPoint PPT Presentation

Models Meeting Automotive Design Challenges Dr Henrik Lönn Volvo Technology Gothenburg, Sweden henrik.lonn@volvo.com 1

Employees ~100 000 Volvo Group Total sales ~25 000 MEUR Financial services Aero Penta The Volvo Group is one of the Construction Equipment world’s leading supplier Trucks of commercial transport solutions Buses Models Meeting Automotive Design Challenges. Henrik Lönn, Volvo Technology 2

MAENAD Project: maenad.eu Model-based Analysis & Engineering of Novel Architectures for Dependable Electric Vehicles Purpose: Refine EAST-ADL Language, tools and methodology to support Electrical Vehicle development OEMs: Volvo Technolgoy, Centro Recherche FIAT SE, IT Suppliers: Continental, Delphi/Mecel, 4S Group DE, SE, IT Tools: MetaCase, Pulse-AR, Systemite FI, SE, FR Research: CEA LIST, KTH, TU Berlin, U Hull FR, SE, DE, UK Kind: FP7 STREP Budget: 4 MEUR Duration: 2011-2013 Coordinator: Henrik Lönn, Volvo Technology Models Meeting Automotive Design Challenges. Henrik Lönn, Volvo Technology 3

Outline  Automotive Challenges  Need for Modelling  EAST-ADL  AUTOSAR  Conclusions Models Meeting Automotive Design Challenges. Henrik Lönn, Volvo Technology 4

Evolution of Vehicle Electronics Models Meeting Automotive Design Challenges. Henrik Lönn, Volvo Technology 5

Challenges from two sides  Product Aspects - Functionality increase - Complexity increase - Electrification - Quality and Safety implications  Development Aspects - Supplier-OEM relationship - Multiple sites & departments - Product families - Componentization - Separation of application from infrastructure - Rules and Rigor (ISO26262, SPICE, CMM, etc.) 6

Complexity Increase  Infrastructure-induced complexity  Multiple ECUs  Multiple network segments/domains  Componentization  HW-SW Dependencies  Application-induced complexity  Functionality growth  Infrastructure interaction  Vehicle-to-vehicle interaction  Increased coupling between vehicle functions Models Meeting Automotive Design Challenges. Henrik Lönn, Volvo Technology 7

Need for Flexibility  Late Changes  Reduced time to market  Changes come late due to changed top level requirements  Changes come late due to distributed development  Integration is late  Mechanichal Constraints enforce early decisions  ECU locations  Wiring Locations  Sensors and actuators Models Meeting Automotive Design Challenges. Henrik Lönn, Volvo Technology 8

Need for Harmonization  Different Brands from the same architechture  World top 10 Car manufacturers  58 Brands  Different Vehicles from the same architechture  Volvo Cars: P2 platform – ”4” vehicles  Volvo Group: TEAx platform – ”∞” vehicles  Different Specification Levels from the same architechture  Electronics content vary from Basic to Luxus, from China to Europe, etc. Models Meeting Automotive Design Challenges. Henrik Lönn, Volvo Technology 9

Need for Harmonization, Cont’d  Multiple Domains one architechture  Body  Telematics  Chassis  Powertrain  …  Multiple Departments one architechture  >1 department for each domain, Function development vs. Software vs. Hardware, Testing, Integration, Prototyping, Product Planning, …  Multiple Companies one architechture  Alliances, mergers, supplier-OEM  Multiple Locations one architechture  Global industry Models Meeting Automotive Design Challenges. Henrik Lönn, Volvo Technology 10

Need for Federated Architechture (Modularization of HW)  Testing  Development  Divide-and-conquer  Self-contained units  Fewer integration issues  Pre-assembly  Safety  Fewer dependencies between components  Fault containment  Procurement  Fault independence  Self-contained units  Fewer integration issues Models Meeting Automotive Design Challenges. Henrik Lönn, Volvo Technology 11

Need for Integrated Architechture  ECU count  Wiring  Each ECU has a large initial  Wiring can be optimized cost  Quality & Safety  Flexibility  Hardware and Connectors are (Over time and over vehicle error prone variants)  Advanced development  Functionality is less hardware methods enforced dependent Models Meeting Automotive Design Challenges. Henrik Lönn, Volvo Technology 12

Outline  Automotive Challenges  Need for Modelling  EAST-ADL  AUTOSAR  Conclusions Models Meeting Automotive Design Challenges. Henrik Lönn, Volvo Technology 13

System Specifications - State of Practice  Formats and specification styles are informal  Formats and specification styles are textual  Formats and specification styles are company specific  Formats and specification styles vary over time  Different tools and approaches depending on Domain Models Meeting Automotive Design Challenges. Henrik Lönn, Volvo Technology 14

Modelling Needs  Capture Specifications of Automotive Electronic Systems Architecture Description Language An information model that captures engineering information in a standardized way 15

Potential of an Architecture Description Language • • Multiple aspects/abstraction levels Integrated Information Handling • • Separation of Concerns Multi-user opportunity • • Early System Integration Effective Documentation management • • Traceability Requirements Engineering • Tool Integration • Tracing between Requirements • Validation and Synthesis • Allocation of Requirements to System Elements • Simulation • V&V Information Support • Analysis • • Basis for Variability Modelling Synthesis • Product Families • Variability propagation Models Meeting Automotive Design Challenges. Henrik Lönn, Volvo Technology 16

EAST-ADL Elements  EAST-ADL Metamodel  UML2 Profile  XSD Schema  EAST-ADL Methodology  Tooling  EATOP Eclipse Platform  Papyrus UML  Proprietary (MentorGraphics VSA, Arcticus Rubus, MetaCase ME+, Systemite SystemWeaver) Models Meeting Automotive Design Challenges. Henrik Lönn, Volvo Technology 17

EAST-ADL Overview SystemModel EAST-ADL defines an VehicleLevel Engineering information structure TechnicalFeatureModel  Feature content  Functional content Environment Model  Software architecture AnalysisLevel FunctionalAnalysisArchitecture  Requirements  Variability DesignLevel  Safety information FunctionalDesignArchitecture  V&V Information HardwareDesignArchitecture  Behavior ImplementationLevel  Timing AUTOSAR AUTOSAR Basic AUTOSAR  … Application SW SW HW Data exchange over ports Allocation Models Meeting Automotive Design Challenges. Henrik Lönn, Volvo Technology 18

EAST-ADL+AUTOSAR Representation TechnicalFeatureModel Features SystemModel Extensions … Chassis of the vehicle Steer Cruise Brake VehicleLevel TechnicalFeatureModel <<AnalysisArchitecture>> DemonstratorAA <<FunctionalAnalysisArchitecture>> DemoFAA Abstract <<FunctionalDevice>> BrakePedal VehicleSpeed Environment Model <<ADLFunction>> Requirements <<ADLFunction>> <<FunctionalDevice>> AbstractABSFrontLeft functions BrakeAlgorithm BrakeFrontLeft AnalysisLevel Dependability <<FunctionalDevice>> WheelSensorFrontLeft FunctionalAnalysisArchitecture Variability Timing FunctionalDesignArchitecture Hardware topology , <<LocalDeviceManager>> <<BSWFunction>> <<HWFunction>> DesignLevel BrakePedal PedalIO BrakePedal VehicleSpeed <<DesignFunction>> <<DesignFunction>> <<LocalDeviceManager>> <<BSWFunction>> <<HWFunction>> concrete functions , ABSFrontLeft BrakeActuatorFL BrakeIO BrakeFrontLeft BrakeController FunctionalDesignArchitecture <<LocalDeviceManager>> <<BSWFunction>> <<HWFunction>> WheelSensorFL WSensIO WheelSensorFrontLeft allocation to nodes HardwareDesignArchitecture HardwareDesignArchitecture <<Sensor>> <<ECUNode>> <<ECUNoder>> <<Actuator>> Pedal PedalNode WheelNode Brake ImplementationLevel <<Realize>> AUTOSAR AUTOSAR Basic AUTOSAR Software Architecture Application SW SW HW SWComposition <<SensorSWC>> as represented BrakePedal VehicleSpeed <<SWC>> <<SWC>> <<ActuatorSWC>> ABSFrontLeft BaseBrake Brake by AUTOSAR Data exchange over ports Allocation <<LocalDeviceManager>> WheelSensorFL Models Meeting Automotive Design Challenges. Henrik Lönn, Volvo Technology 19

EAST-ADL Extensions SystemModel Extensions … VehicleLevel TechnicalFeatureModel Environment Model Requirements AnalysisLevel Dependability FunctionalAnalysisArchitecture Variability Timing DesignLevel FunctionalDesignArchitecture HardwareDesignArchitecture ImplementationLevel AUTOSAR AUTOSAR Basic AUTOSAR Application SW SW HW Data exchange over ports Allocation Models Meeting Automotive Design Challenges. Henrik Lönn, Volvo Technology 20