How Conduce Delivers Seamless Version Upgrades

In aviation, efficiency is everything. Time is not just money; it is fuel, passenger satisfaction, carbon impact, and operational reputation. At Conduce, we see this every day through the mission-critical role of eTechLog8. That is why, unlike many aviation software solutions, eTechLog8 is designed and maintained on a zero-downtime principle.

Digitisation has transformed aviation, creating both challenges and opportunities. The shift to paperless systems has improved efficiency many times over. Real-time data captured by eTechLog8 means faster, more informed decision-making, allowing airlines to return aircraft to service as quickly as possible. Yet greater reliance on software also introduces new risks. According to Oxford Economics, over half of global Aircraft on Ground (AOG) events now involve a cybersecurity or IT component. The CrowdStrike outage of 2024 is a stark reminder of the potential scale of such disruption.

When an aircraft is unexpectedly grounded, costs accumulate rapidly. Boeing estimates each hour lost during an AOG event can cost between USD 10,000 and 150,000 depending on aircraft type and route. This figure excludes knock-on issues such as missed connections, crew reassignments, and reputational damage. It is little wonder airlines become cautious when they hear the phrase: “Software update required.”

Keeping software current is essential for security, compliance, and functionality. However, many legacy aviation systems still require downtime (sometimes several hours) to apply an update. At Conduce, we believe airlines should not have to choose between staying secure and staying online.

How Conduce Does It Differently

Our approach to updates is simple: no hassle, no disruption, and no downtime.

First, it helps to clarify terminology:

• Major Version – a significant software release, often every few years.

• Minor Version – more frequent, often what we mean when we say ‘version upgrade’.

• Patch – small fixes applied to correct issues in existing code.

In eTechLog8, version information appears in the bottom right corner of each device. For example:

This contains all the version information about this specific device.

Patches are managed by Conduce, while version upgrades follow a structured process. Importantly, we never break existing functionality.

Our Three-Step Update Process

Step 1: Feedback & Planning
Every update begins with feedback from customers, internal teams and looking at our strategic roadmap. And our Quality Manager working closely across departments to prioritise improvements that deliver operational value.

Step 2: Build & Test
Our developers design, build, and refine the update collaboratively. Rigorous testing follows in a controlled, non-live environment, simulating real-world conditions to identify any bugs or edge cases. Only once stability and effectiveness are assured does the release move forward.

Step 3: Seamless Deployment
Updates are deployed quietly via eCentral8. Users experience no disruption. Changes are downloaded when a device next syncs with eCentral8. If the connection is interrupted, the system retries automatically. When the user navigates back to the main menu, the eTechLog8 logo flashes for a few seconds, installing the update. The user continues working as usual – most of the time they don’t even notice!
No hassle, no disruption, and no downtime.

At Conduce, we understand that efficiency in aviation is non-negotiable. By designing eTechLog8 around resilience and reliability, we ensure airlines stay up to date without ever missing a beat.

Interested in finding out more?

Request a demonstration of our software here.