Case Study · Automotive

1,600 tickets resolved and 38 features developed on two instrument cluster projects.

For a global automotive Tier 1 supplier, rinf.tech worked with the client's mirror team on instrument cluster projects for two of the biggest global brands of a top manufacturer in individual mobility. The work covered embedded C development, AUTOSAR module integration, and hardware bring-up.

IndustryAutomotive
ClientGlobal automotive Tier 1 supplier
PlatformAUTOSAR, C/C++, OSEK RTOS, Green Hills Integrity RTOS
ProcessAgile, V-cycle, ASPICE
Executive summary

The two projects came with 1,600 defects to solve and more than 28 features to implement, in a fully distributed environment. At kickoff, the specifications and the technologies in use were unclear.

rinf.tech and the client's mirror team took responsibility for delivering the next generations of instrument clusters for one of the largest global brands in automotive. The work was organized in three teams: applications, RTOS, and drivers.

Over 1,600 tickets were resolved and over 38 new features developed. Deployment was 50% faster, and the transition caused no delay, which let the client focus on more pressing deliverables.

1,600+

Tickets resolved
The projects started with 1,600 defects to solve.

38+

New features developed
The scope at kickoff was 28+ features to implement.

50%

Faster deployment
Due to fast ramp-up and prioritized knowledge transfer.

Chapter 1 · The challenge

Two projects, 1,600 defects, and unclear specifications

The client, a global automotive Tier 1 supplier, had instrument cluster projects for two of the biggest global brands of a top manufacturer in individual mobility. It had also acquired more business than it could focus on alone.

The situation at kickoff
  • 1,600 defects to solve.
  • 28+ features to implement.
  • A fully distributed environment. Communication and constant synchronization with other teams were the key elements for success.
  • Unclear specifications. There was no clarity on the specifications or the technologies used.
Chapter 2 · What rinf.tech worked on

Applications, RTOS, and drivers for the next generation of instrument clusters

rinf.tech worked with the client's mirror team on the next generations of instrument clusters, with a focus on quality in development and integration. The work covered embedded software development in C, AUTOSAR module integration, hardware bring-up for new instrument cluster hardware, and Vector tools for AUTOSAR. It was split across three teams.

What rinf.tech worked on

# 01 — Applications team

Illumination (PWM control for the LEDs), pointers (speed, RPM), input from the board computer button, check controls (fault indicators), dimming, the odometer (trip and total kilometers traveled), time, the board computer (consumption, trip info, range), and adaptive and dynamic cruise control.

# 02 — RTOS team

The CAAM crypto driver for iMX6, AVB stack, RDA encryption, MOST communication, IPsec certificates, SOME/IP components, NAND, NOR, and filesystem code, Integrity OS, DLT, IPC encryption, HUD, HMI, video decoder and renderer updates, core dump implementation, car model code, and bootloader code.

# 03 — Drivers team

Complex device drivers (MCU, head-up display, real-time clock, sound, input/output controller), the safety controller, the CAN wrapper, diagnostics, power management, inter-processor proxies between the control and graphics processors, AUTOSAR core component integration and configuration, and hardware bring-up.

The clusters use an AUTOSAR architecture with software developed in C/C++. The hardware is a two-MCU system with ARM cores and inter-processor communication (IPC), in a two-board APX design (intelligent and front end). The operating systems are OSEK RTOS and Green Hills Integrity RTOS, with support for separate virtual address spaces and memory protection. The system includes safety-related functions, a MOST (Media Oriented System Transport) connection to the infotainment system, a high-speed CAN connection, and OpenGL ES graphics.

How the work was run

Engineers from different specialties worked together in an Agile methodology, using the V-cycle process and following ASPICE policies. The work followed the client's tools, standards, processes, and methodologies.

Chapter 3 · Results

What the work delivered

Over 1,600 tickets resolved.

The projects started with 1,600 defects to solve.

Over 38 new features developed.

The scope at kickoff was 28+ features to implement.

50% faster deployment.

Due to fast ramp-up and prioritized knowledge transfer.

No delay in the transition.

rinf.tech took on the two major projects quickly, which let the client focus on more pressing deliverables.

Compliance with the client's way of working.

The work complied with the client's tools, standards, processes, and methodologies.

The work also secured the stability and scalability of the two projects.
What it shows

Two projects taken on without slowing the client down

The client had more business than it could focus on. rinf.tech and the client's mirror team took on two instrument cluster projects in a distributed setup, with unclear specifications at the start, and delivered them with no delay in the transition.

Industry
Automotive
Client
Global automotive Tier 1 supplier
Scope
Embedded C development, AUTOSAR module integration, hardware bring-up, Vector tools for AUTOSAR
Platform
AUTOSAR, C/C++, OSEK RTOS, Green Hills Integrity RTOS
Process
Agile, V-cycle, ASPICE
Tools
RTC, Rhapsody, Jenkins, QNX, DaVinci, Ansys, VectorCAST, DOORS, GHS Compiler, Lauterbach, CANoe, OrCAD, MATLAB Simulink