AUTOSAR (AUTomotive Open System ARchitecture) is an open and standardized automotive software architecture, jointly developed by automobile manufacturers, suppliers, and tool developers. bat365 is an AUTOSAR Premium Member and actively participates in the development of the standard with focus on how to use Model-Based Design with an AUTOSAR development process.

The AUTOSAR standard provides two platforms to support the current and the next generation of automotive ECUs. The first is the Classic platform, used for traditional applications such as powertrain, chassis, and body and interior electronics. The second is the Adaptive platform, used for compute-intensive applications such as highly automated driving, Car-to-X, software updates over the air, or vehicles as part of the Internet of Things. The Foundation AUTOSAR standard enforces interoperability between the AUTOSAR platforms.

Simulink natively supports AUTOSAR. AUTOSAR Blockset lets engineers map Simulink models to either AUTOSAR Classic or Adaptive specifications. And you can also generate production C and C++ AUTOSAR code using Embedded Coder. Simulink, AUTOSAR Blockset, and Embedded Coder support round-trip integration with AUTOSAR architectures as illustrated below.

• Fiat Chrysler Automobile: Leveraging Model-Based Design, Automatic Code Generation, and AUTOSAR to Architect and Implement an Engine Control Application for Series Production
• LG Chem: Developing AUTOSAR-Compliant Software for a Hybrid Vehicle Battery Management System with Model-Based Design
• IDNEO: Developing and Testing AUTOSAR Software Components and Complex Device Drivers with Model-Based Design 
• Ford Motor Company: Software Development Applying Model-Based Design Process & Tools (14:55)
• A123 Systems: Continuous Integration within a Model Based Workflow (10:29)
• Navistar: Enhanced Data Dictionary for Model Based Automotive Production Software Development (11:11)

• Autoliv: Development of Integrated Vehicle Safety Applications Through Model-Based Design (19:47)
• VALEO E.E.S.: Automatic Code Generation of AUTOSAR Software Components for Mass Production Application of Engine Management Systems: Process and Benefits (26:03)
• KPIT: KPIT Establishes an End-to-End Process for AUTOSAR-Compliant Software Development with Model-Based Design
• Vector: The Evolution of E/E Architecture and the Impact on Future Software Development (20:02)
• Elektrobit: A Model-Based Design Approach Applied to a Driver Monitoring System (20:50)
• Continental: Model-Based Development with AURIX PiL Target (20:16)

• KPIT: Model-Based Development Approach: AUTOSAR + Functional Safety + Aspice (27:08)
• Magneti Marelli: Development of a Semi-active Suspension System Using Model-Based Design with AUTOSAR and Compliant with the A-SPICE Standard
• Delphi Technologies: AUTOSAR Software Architecture Modeling of Multicore Electric Powertrain Software (18:52)