Markus Schupfner of Qorix, speaks with EFY’s Nitisha Dubey about the company’s middleware solutions for software-defined vehicles and modern electrical/electronic (E/E) architectures. He also underscores Qorix’s focus on delivering high-performance, safety-certified middleware tailored for next-generation automotive computing systems.
Q. Can you tell us about Qorix and its background?
A. Qorix is a newly established 50%/50% joint venture between KPIT and ZF Friedrichshafen that originated as a 100% subsidiary of KPIT and was founded last year. Qorix is dedicated to developing cutting-edge functional safety middleware for the next generation of software-defined vehicles (SDVs) and the new electrical/electronic (E/E) architecture. Our mission is to deliver a world-class middleware solution tailored for the new E/E architecture, high-performance computers, centralised computing systems, and zonal gateways. Qorix has also inherited valuable intellectual property (IP) from KPIT and ZF, including solutions related to AUTOSAR Classic, AUTOSAR Adaptive, and our newly branded Qorix Performance middleware. Our product portfolio comprises three distinct product lines. As we expand our reach, we are transitioning existing customers from KPIT to Qorix, strengthening our market presence.
Q. Why is middleware so crucial in the automotive industry right now?
A. Middleware is crucial because carmakers need more than just SOC-level software components. When purchasing a SOC and high-performance compute, it typically comes with a basic software layer called a BSP (board support package). However, this layer is not sufficient for running applications, especially in terms of functional safety. This creates a gap between the hardware layer (SOC and BSP) and the upper application layer.
Currently, OEMs (original equipment manufacturers) face challenges in integrating various software components from different suppliers. This complex process can lead to issues with interfacing and functionality. Achieving ASIL D, the highest level of automotive functional safety certification, is particularly challenging when software is sourced from multiple vendors.
Middleware is essential for ensuring performance, functionality, and safety, even though it is not a differentiator for the end consumer. OEMs expect middleware to perform well, be safe, and provide the necessary APIs to run applications. A natural outcome of these challenges is the need for a company to develop a full-stack solution that integrates middleware and provides functional safety certification. Qorix was founded to fulfil this need, leveraging years of experience from KPIT and ZF to create middleware that supports high-performance computing while ensuring safety and performance.
Q. What obstacles are emerging for the automotive industry in transitioning to middleware and software-defined vehicles?
A. The transition from classical to SDV architecture presents several challenges, particularly in centralising computing power while maintaining functional safety and performance. Migrating legacy systems to this new architecture is a significant challenge, as millions of lines of code have been developed over the years. Qorix aims to facilitate this transition by enabling fast migration from legacy systems to centralised computing.
Another challenge is ensuring that the software in a SDV is always up to date, which includes functional safety-related software. Currently, only non-critical systems like infotainment can be updated, but we are also working to enable continuous updates for critical systems.
The industry is also moving towards a hybrid approach that integrates service-driven and signal-driven designs. Existing standards like AUTOSAR Adaptive have limitations in handling signal-driven data, which is crucial for ADAS systems. We have developed the Qorix Performance stack to address this, which supports continuous updates and incremental feature enhancements while maintaining cybersecurity and functional safety compliance. Virtualisation and cloud-based development are also becoming increasingly important. Developing and testing software in a virtualised environment allows for faster iteration and more efficient deployment.
Q. What actions are you taking to enhance middleware optimisation?
A. We work with SOC providers to gain timely access to the latest SOCs, which allows us to optimise our middleware for new hardware. We also collaborate with OS providers like QNX to ensure our middleware runs efficiently alongside their hypervisor solutions. Access to the BSP layer is crucial for enhancing our middleware’s performance and precision.
Q. How does the middleware improve ADAS performance, flexibility, and support automated software development?
A. Our middleware offers a robust solution for ADAS systems by providing a scalable communication framework that ensures efficient data transport through seamless inter-process and inter-node communication, addressing the performance issues typically caused by memory copies and message handling. It also supports end-to-end application execution with deterministic, cyclic, and threat-level functional scheduling, ensuring tasks are completed within specific time frames. Our middleware allows for flexible and efficient data processing by accommodating signal-driven and service-oriented applications. Furthermore, it includes a comprehensive set of foundation services that maintain compatibility with AUTOSAR APIs while extending beyond them to address functionalities not covered by the standard, ensuring high reusability and flexibility. Designed to integrate within a CI/CD environment, our middleware supports continuous integration, testing, and development in a virtualised infrastructure, facilitating automated software configuration and orchestration, which is crucial for SDVs.
Q. Who is the target audience for Qorix?
A. Our target audience includes OEMs, SOC providers, and Tier 1 suppliers. OEMs are the primary focus of our new performance stack. However, we are also considering packaging our solutions with SOC providers as a reference implementation, allowing them to offer Qorix software pre-installed on their HPCs and SOCs. Additionally, our classic AUTOSAR solutions are in demand from Tier 1 suppliers. So, our portfolio serves a broad range of customers, including OEMs, SOC providers, and Tier 1 suppliers.
Q. Which regions are currently using Qorix’s software-defined applications?
A. Qorix’s portfolio, including AUTOSAR products, has customers across North America, Asia (including Japan), and Europe. While we do not have an entity in North America, we have sales support there. We are also exploring opportunities in China, a market we have not yet entered but plan to target soon.
Q. How did you set up your business?
A. Our business setup is guided by strategic decisions on where to expand. Our parent company is in Munich, and we have recently opened our first office in Bengaluru, with plans to open another in Pune soon. We currently have a sales presence in North America, particularly around Michigan, and we plan to grow further in the US.
Q. Can you tell us about your operations in India?
A. We have established our first office in Bengaluru, with Pune as our entity location. Our strategy is to focus R&D efforts in India, with Pune and Bengaluru as our main hubs. We are also exploring opportunities with Indian OEMs like Tata and Mahindra, who want to enable SDVs for four-wheelers, two-wheelers, or trucks. Centralised computing is critical in reducing costs, particularly in mid-size and high-end vehicles, where ECUs and wiring harnesses are significant cost drivers. India represents a future market for us, with its combination of skilled talent and cost advantages, particularly in functional safety and cybersecurity.
Q. Are there any plans or announcements you would like to share?
A. As a newly founded company, we want to join key consortiums important for middleware development in the automotive market. We are preparing announcements about our participation in these consortiums, including AUTOSAR, where we plan to play a significant role. In July, we joined the SDV Working Group at the Eclipse Foundation to contribute to the advancement of SDV technologies. This move reflects our commitment to addressing the challenges of increasing software complexity in the automotive industry. While Qorix may appear to be a startup, it is more of a demerger from KPIT and ZF, bringing together experienced R&D teams under a new entity. We are also expanding our non-R&D team and looking to impact the industry by being fast and innovative. Furthermore, we will attend the ELIV Conference, an international conference for automotive electronics in Germany, to showcase our latest innovations in middleware technology. Visitors at booth 34 will have the opportunity to gain experience more about how our solutions advance SDV technologies.
Q. How do you plan to manage after-sales services?
A. Providing engineering services is critical in the automotive software industry. It is not enough to deliver software products off the shelf; we must also offer maintenance and customisation services. Maintenance ensures that our products remain secure and functional over time, while customisation allows us to tailor our solutions to the specific needs of OEMs, ensuring smooth integration into their architectures. Fast reaction times and close collaboration with customers are essential in delivering these services effectively.
