ISO 26262 Edition 3: Three Big Things to Watch
ISO 26262 Edition 3 is taking shape to address today’s software-defined, automated, and highly connected vehicles. The standard is still under development, but the direction is already becoming clear. The main themes include closer alignment with ISO 21448 (SOTIF), the use of predictive maintenance as a safety mechanism, and clearer guidance for software reuse. With publication widely expected around 2027, now is a good time to prepare.
1. Closer alignment with ISO 21448 (SOTIF)
One major change in ISO 26262 Edition 3 is a closer link with ISO 21448, also known as SOTIF. SOTIF addresses hazards caused by functional limitations or performance issues, even when no fault is present.
Edition 3 is expected to define the boundary between the two standards more clearly. It should also harmonize terminology and highlight lifecycle touchpoints. This will help teams build a more consistent safety case across Functional Safety (FuSa) and SOTIF activities.
For companies developing advanced driver features, this alignment should reduce confusion and improve coordination between safety teams.
2. Predictive maintenance as a safety mechanism
Another important topic in ISO 26262 Edition 3 is the growing role of predictive maintenance (PdM). PdM helps detect degradation before it becomes a failure. In practice, it can support diagnostics, health monitoring, and remaining useful life (RUL) estimation.
Traditional Functional Safety focuses on random hardware faults and systematic failures. Predictive maintenance adds a more proactive layer. It helps teams identify wear, drift, and environmental stress early. As a result, engineers can reduce exposure time and improve system availability.
This approach is especially useful in systems that require fail-operational behavior. It can also support graceful degradation, derating strategies, and redundancy management in real vehicle fleets.
3. Clearer guidance for software reuse
ISO 26262 Edition 3 also appears to move toward a more practical framework for reusing existing software. This includes software already developed internally, as well as OSS and COTS components.
Edition 3 discussions suggest clearer expectations for evidence and integration. These expectations may include safety requirements, ASIL capability, and freedom from interference. This could reduce some of the friction teams face when applying Edition 2 guidance.
This matters because modern vehicle platforms are changing fast. With centralized and zonal E/E architectures, automotive hardware increasingly resembles traditional computing platforms. That trend makes software reuse more attractive, especially in domains such as infotainment and shared platform services.
A clearer and more auditable safety case can help organizations reuse software without reducing safety integrity.
ISO 26262 Edition 3 remains a work in progress
It is important to remember that ISO 26262 Edition 3 is still under development. The final content may change during the ISO process. However, the overall direction appears consistent. Industry discussions continue to point to stronger SOTIF alignment, broader recognition of predictive maintenance, and better support for software reuse.
Together, these changes aim to make the standard more practical for automated and software-defined vehicles. Most discussions still point to a publication window around 2027.
Will ISO 26262 Edition 3 impact your organization ?
These changes should benefit the automotive industry by providing clearer guidance for modern vehicle development. They are especially relevant for organizations working on advanced driver features, connected platforms, and mixed-criticality software environments.
If your team already works with FuSa or SOTIF, you may need to consider how the other framework fits into your process. A more integrated approach can reduce duplication and improve traceability across safety activities.
Predictive maintenance also creates new opportunities. By estimating remaining useful life and detecting degradation early, teams can define better mitigation strategies for hardware faults. This can improve both safety and availability.
For OEMs and suppliers that want to reuse OSS or COTS software, Edition 3 could offer a clearer path forward. In many cases, reuse may become more efficient than starting from scratch, provided the safety case remains robust and well documented.
At CS Group Canada, we help organizations combine FuSa and SOTIF workflows, deploy predictive maintenance strategies, and evaluate software reuse in line with evolving automotive safety standards.
CS NEWS
Recent Posts
Categories
ALSO READ
DO-178C Brochure
Aeronautics Brochure
