AutoSAR Architecture Implementation

ARi worked closely with a leading fortune 500 heavy automotive, earth moving, agricultural and construction company to develop the AUTOSAR architecture. With a unique requirement to fetch the legacy software as well as develop the new software for number of variants of ECUs.

Project Scope

With increasing number of OEMs jumping on the AUTOSAR bandwagon, there is a niche demand to migrate the existing software and develop the new using the standard AUTOSAR architecture. Since the inception of the AUTOSAR, ARi has been associate partner of its consortium closely formulating the standards and parallelly working on the development projects in house. In addition, we work closely with various other OEMs to implement the new architecture encapsulating expertise in various developmental, testing, and process defining tools for AUTOSAR.

ARi’s Solutions

Recently, ARi worked closely with a leading fortune 500 heavy automotive, earth moving, agricultural and construction company to develop the AUTOSAR architecture. With a unique requirement to fetch the legacy software as well as develop the new software for number of variants of ECUs, ARi provided a unique solution by commonly implementing the base software one for single core (Aurix T23x) and another for multi core processors (Auric T27x). In addition, we streamlined the developmental process using the IBM’s Application Life cycle management tools and plethora of Vector tools like PReeVision, DaVinci Developer, Developer, CaNoe, CANalyzer, Altium’s Tasking compiler, and Green Hills debugger. In order to configure all the I/Os for all the different variants, we also developed a common Complex Device Driver Suite. To facilitate the software testing before the hardware procurement, virtual target testing was implemented to accelerate the development and reduce the cost of functional testing.

ARi’s Value Proposition

Utilize new functions across all their variants of equipment at a better value than the competition.

Standardization provided them a wide choice on integrating their hardware with various supplier software to possess the best functionality.

Efficient management and distribution of work which reduced the developmental time, effort, and costs; for example, each ECU took only 1500 Man hours to fully configure and implement.

The scalability of the BSW software along with the various automated testing scripts on NI and ETAS HILs across various other platforms of the OEM, provided them with extra functionality.

The improved Agile and AUTOSAR methodology set a new standard of process improvement during a typical quarterly process auditing exercise at the OEM.

Due to the rapid development of the ECUs, our customer is currently putting into the production vehicles implementing various new functionalities, thereby increasing the sales figures of the OEM.

Less time for development and more rigorous automated, functional, and virtual testing means the final software obtained is very high in quality and reliability.