From Model Year to Always Up-to-Date

How Software Is Redefining the Car’s Lifecycle

But that logic is changing. With the right software architecture, the car can become a platform for continuous improvement – a product that evolves, refines, and optimizes over time, even after it leaves the factory.

This shift requires a new mindset: about products, organizations, and business models.

Decoupling That Changes the Game

At the heart of this change is the decoupling of software from hardware. In traditional vehicle platforms, functions are often tightly integrated with specific ECUs, sensors, and electronics. This makes every component replacement costly in development time and often requires rewriting the same function multiple times.

Being able to develop software independently of the hardware’s product cycle enables a shift from sequential to continuous development. This allows for shorter development cycles, greater scalability, and better use of resources.

But the point isn’t always about adding new functions later – it’s about not having to recreate existing ones. A large share of development time today goes into porting existing functionality to new hardware, often due to discontinued or replaced components. With the right architecture, application logic can be decoupled from the hardware, drastically reducing rework and enabling a more robust development chain. It also allows for more frequent model launches and shorter cycles – challenging the traditional model-year mindset.

From Distributed to Centralized Electronics

Traditional vehicle architectures consist of a large number of distributed ECUs, where each control unit manages a specific function. This has led to fragmented systems, complex troubleshooting, and limited reuse.

Modern Software-Defined Vehicle (SDV) architectures are shifting toward centralization – consolidating functions into fewer, more powerful computing units that can manage multiple systems in parallel. This can simplify wiring, reduce physical redundancy, and improve conditions for resource sharing between functions.

However, centralization doesn’t necessarily reduce complexity – it redistributes it, often shifting it from hardware to software and architectural levels. With fewer but more powerful nodes, there’s a growing need for clear architecture for isolation, real-time performance, redundancy, and safety-critical functions. For example, new patterns for partitioning, fallback handling, and quality assurance of software running on shared hardware are required.

The design of zonal architectures and the transition from classic AUTOSAR to, for instance, Adaptive AUTOSAR is crucial in this shift – especially to enable dynamic software deployment and future OTA updates of entire subsystems.

What Does It Take to Get There?

Decoupling is not just a technical detail – it’s a strategic choice that affects the entire development model. A well-designed base software, combined with clearly defined interfaces and a thoughtful component architecture, enables high code reuse across different models and generations.

This requires:

  • A clear software architecture that defines responsibility, dependencies, and isolation between functions
  • CI/CD pipelines that support both vehicle-specific verification requirements and continuous integration
  • Cross-functional teams capable of owning entire functions – from development to in-field operations

Middleware plays a key role here. It acts as a hub between hardware and application, abstracting the complexity of diverse hardware platforms. By managing resources, providing standardized APIs, and enabling virtualization, middleware forms a technical backbone for portability and reuse at a scale previously hard to achieve.

With increased connectivity, OTA updates, and external APIs comes increased responsibility. Cybersecurity and data protection can no longer be added at the end of development – they must be embedded in the architecture from the start.

Safety-critical functions must be isolated, updates signed and validated, and all data handling must comply with strict regulations – including GDPR and industry-specific standards such as UNECE R155 and ISO/SAE 21434. The ability to secure systems over time is key to building both trust and technical resilience.

Organizational Transformation in Practice

Technical transformation must be supported by organizational structures. OEMs that break down function-based silos and create teams with end-to-end responsibility – from idea to OTA update – report improved development speed and product quality.

At the same time, the relationship with suppliers is changing. Instead of linear chains, platform-based collaborations are emerging, where OEMs, Tier 1s, and tech companies co-develop around shared APIs, data models, and lifecycle strategies. This demands new levels of technical leadership and openness across the ecosystem.

The Car of the Future Is Always Current

The strategic business benefits are clear: faster time-to-market, shorter update cycles, and better scalability of innovation across product lines. At the same time, new revenue models emerge through service-based offerings, subscription features, and extended vehicle lifespans.

But with longer vehicle lifespans come new demands. Managing the full software lifecycle – from initial development to support, updates, and decommissioning – becomes a new challenge for the industry.

OEMs need strategies for maintaining compatibility with legacy hardware, handling component obsolescence, and ensuring that even vehicles on the road for ten to fifteen years can still receive critical updates and security patches.

In the end, the value of tomorrow’s vehicle won’t just lie in what’s built into it – but in its ability to continuously improve after delivery.
Data becomes an asset. APIs become business interfaces. The product becomes a platform.

Final Thoughts

The shift to software-defined vehicles is not just about technology – it’s about architecture, systems thinking, and collaboration. To succeed, organizations need the ability to navigate both deep technical complexity and broad business impact.

And it is precisely in this intersection – between system architecture, agile development, and strategic tech capabilities – that strong development partners make all the difference.

Want to know how HiQ can support you on this journey?
Let’s talk – we’d love to share more.

Contact

Region

You want to know more? Let’s get in touch!

hello@hiq.de
HiQ offers companies customized solutions for reliable device management and over-the-air firmware updates.

How to optimize your time to market with FOTA

Time to market (TTM) is a key factor in the product development process. It describes the time span from the initial idea through product development to market launch. The length or brevity of the time to market can give companies a decisive competitive advantage: The faster a product reaches the market, the faster it generates sales and establishes itself before the competition can catch up.

FOTA (Firmware Over-the-Air) updates offer an excellent opportunity to speed up this process considerably – whether in the development phase of a product, when solving problems or after the product launch. 

Faster market launch with just in time software updates

Launching an unfinished product on the market? Doesn’t sound very smart at first, but it can actually be a clever strategy! 

In an ideal world, the hardware and software of a device are always ready at the same time and products can be launched directly onto the market without expensive intermediate storage or waiting times. Is this the case in your company? Then congratulations, you have established highly optimized processes. 

If not, I still have good news: The software does not have to be finalized at the same time as the hardware: While the finished device is already packaged and on its way to the customer, developers can still finalize the last lines of code or the QA department can use additional time to thoroughly test all software functions. 

All that matters is that the product receives a wireless firmware update when it is first switched on to provide all the required functions. 

This allows you to start production and delivery of your product early, saving valuable time and costs. Missing features can be added at market launch (or at a later stage). It is important that the FOTA system is able to orchestrate and process all updates smoothly so that the launch day is a complete success.

Reducing risks: Bugs, security, compliance

In addition to the fundamental reduction in time to market through F-OTA updates, it is crucial to recognize potential complications at an early stage and react accordingly in order to avoid unnecessary delays and stay ahead of the competition. 

Such complications can arise as a result of changed framework conditions, for example new security standards that are not met. Or serious problems discovered by the QA department, like a feature not working properly or even spyware in purchased hardware.

If a company does not have a FOTA system, software problems can be updated manually by hand and plug – provided that the devices are not on the market or with the customer. However, if this is no longer possible, you hopefully have a competent marketing team to cushion a recall – or a really well-functioning FOTA system. 

Such a FOTA system must not only be highly scalable in order to update a very large number of devices simultaneously (and later be scalable down again to save costs). It should also offer various rollout strategies and backup plans in order to carry out all updates efficiently and risk-free in an urgent situation. This ensures that bug fixes, security and compliance updates are applied quickly and without unnecessary costs.

Interested in learning more about FOTA in the context of IoT?

Then read part 1 of our article series: Firmware Over-the-Air: We explain FOTA.

Flexible feature updates to match the market situation 

Months and years often pass between the planning, development and final release of a product. In the days before the Internet and FOTA updates, companies were forced to plan a product from start to finish and bring it to market completely ready. Today, it is possible to deliver new features as and when required.

If your company’s product is a market leader and customer satisfaction is high, it can make strategic sense to save resources and development costs. If your competitor suddenly surprises you with an innovative feature, you can reinvest in development or roll out a reserved update. 
Unforeseeable events, such as a pandemic or an economic crisis, can also lead to your company having to reassess its priorities. In such cases, it may be advisable to reduce development costs, gather valuable customer feedback and data or attract investors. 

Thanks to wireless firmware updates, it is possible to flexibly develop, roll out or hold back new functions after the market launch. This allows you to adapt your product strategy to changing company and market situations in the optimum way.

Conclusion

Whether it’s a product launch, solving problems during use or updating devices that have already been delivered: Updates over the air are an effective way to shorten the time to market of your product in various phases. 

For this, it is crucial to have a robust FOTA system. A good firmware-over-the- air-system must be scalable, customizable and reliable. This allows you to meet the dynamic requirements of today’s markets.

Contact

Region

Katja Grünewald

Katja has been working as a software developer at Scandio since 2022. She strives to support companies on their path to Industry 4.0 with her experience in FOTA and her passion for digital solutions.

hello@hiq.de
HiQ offers companies customized solutions for reliable device management and over-the-air firmware updates.

Firmware Over The Air: We explain FOTA

In the dynamic landscape of industrial manufacturing, digitization plays a key role for success. Terms such as Industry 4.0 or IoT (Internet of Things) are no longer concepts for the future, but have been firmly established worldwide — both for modern production and for a smartly connected everyday life. Almost everyone uses technologies that are attributed to these terms, whether directly or indirectly.

Firmware over the air (FOTA) updates are a key tool in this constantly growing digital repertoire. They make it possible to comply with the latest (security) standards, bring features to market faster and even help protect the environment.

In this article, we explain the various terms associated with FOTA updates in an easy-to-understand way. 

We also provide a concise overview of why FOTA is so essential not only for software developers, security managers and device manufacturers, but also for end users.

Key terms around FOTA

Internet of Things

The Internet of Things, or IoT for short, refers to the communication between different machines, systems and devices. The technology used for communication is irrelevant. From Bluetooth to 5G to the classic Internet, everything is included.

This type of communication allows automatic workflows to be defined and executed between different devices at different locations without the need for human intervention.

One example: Many homes now have smart devices that communicate with each other. Sensors measure the position of the sun, for example, and automatically close the shutters. This automatic shading allows the amount of light and heat to be directed into the various rooms. If there is also a link to an intelligent heating installation, the result is an extremely sustainable and energy-efficient system.

Hardware/Firmware/Software

IoT devices usually consist of several parts, which are assigned to three categories: Hardware, software and firmware. 

Hardware refers to the physical component, the body of a device, so to speak. This can be touched, but can also be broken. 

Firmware, on the other hand, describes the ‘invisible’ part (to be imagined as the electrical impulses of the brain) — so the code that communicates directly with the hardware and orchestrates which part performs which task and when. 

Software describes the part of the code that no longer interacts directly with the hardware, but only with the firmware. Firmware is generally also referred to as embedded software. 

Cyber Security

The (embedded) software described above is usually extremely complex and consists of thousands of lines of code written by different developers. This makes it almost impossible to keep firmware or software completely free of security vulnerabilities. These can be exploited to access the data stored on a device or to render the device unusable by  hackers. 

According to a recent report by Cybersecurity Ventures, the consequential costs of cyber crime amounted to just under USD 8 trillion in 2023 and will rise to USD 9.5 trillion in 2024. The trend is rising, even for 2025.

FOTA

To stay in the context of cyber security: If a security gap is found, it must be closed as quickly as possible to prevent criminals from exploiting it (if this is not already the case).

In the best case scenario, the gap will be closed in a few hours. However, the latest, secure version of the firmware still needs to be installed on the end device. This is known as an update. If the device is not connected to another device, such as a computer, this is known as a wireless update or OTA update (over the air update).

FOTA update therefore means nothing other than Firmware Over The Air Update and describes the wireless update of the firmware.

As described, these can be updates to solve security issues, but also other firmware adjustments; for example, to add current functions or to optimize device performance and service life.

FOTA updates are essential for modern IoT and enterprise environments as they ensure security, efficiency and scalability in device management.

Curious why OTA Firmware Updates and device management are essential for modern IoT and enterprise environments?

Here you can read more insights and download our free 1-pager on Device Management.

What’s next?

Now that the terminology has been clarified, our upcoming blog posts will focus on the F-OTA process: 

  • What added value does the FOTA process have for companies and end users? 
  • What technologies and processes are behind the term?
  • What can an XXL FOTA system look like? 
  • What is the Cyber Resilience Act? 
  • And above all: how do you get such a system?

We answer these and other questions in the Scandio article series Revolution in the IoT age: Firmware over the Air.

Contact

Region

Katja Grünewald

Katja has been working as a software developer at Scandio since 2022. She strives to support companies on their path to Industry 4.0 with her experience in FOTA and her passion for digital solutions.

hello@hiq.de