Not all systems within a train perform the same function. But many share something important: they operate under demanding conditions and cannot fail.
In this context, functional safety standards such as SIL2 (Safety Integrity Level 2) have become a benchmark for designing systems capable of responding safely, even when something doesn’t go as expected. So far, nothing new.
What is interesting is how the way this knowledge is applied is evolving.
When challenges repeat themselves
For years, the common approach has been to develop specific solutions for each subsystem. Each project would start almost from scratch, adapting to its context, requirements, and particularities.
However, when you take a step back, many of these systems share more than it might seem: harsh environmental conditions, the need for high reliability, integration with other equipment, and a very specific regulatory framework.
In other words, different problems… built on a very similar technical foundation.
This leads to an increasingly relevant question:
does it still make sense to develop everything from scratch?
SIL2 solutions beyond a single system
Working under SIL2 criteria is not just about compliance. It represents a way of designing: analyzing risks from the outset, anticipating how a system will behave in case of failure, and validating that everything works as expected under real conditions.
This approach does not belong to a single subsystem. It can be applied across many areas of the train.
That’s why more and more projects are embracing an approach that, when done properly, makes a lot of sense: leveraging solutions that have already been designed, tested, and validated in SIL2 environments—and adapting them to new applications.
Reuse is not replication
This is worth clarifying, as it often leads to confusion.
Reuse does not mean copying. It means starting from a solid foundation, understanding which elements are applicable, and adapting them to a new context without losing sight of specific requirements.
When done correctly, this approach reduces uncertainty, shortens development timelines, and relies on solutions that have already proven their performance under real conditions.
In other words: greater efficiency without compromising safety.
From isolated solutions to transferable knowledge
This shift also changes how technological development is understood within the sector.
Previously, the focus was on the specific solution. Today, increasing importance is placed on the knowledge behind it: how it was designed, how it was validated, and how it can evolve.
This is what enables the same technological foundation to be applied across different parts of the train—always with the necessary adaptations.
A natural evolution
As trains incorporate more electronics and systems become increasingly interconnected, this approach is no longer just an interesting option—it is becoming almost essential.
It’s not about doing the same thing everywhere, but about leveraging what already works to better address new challenges.
From our experience in developing electronic systems for critical environments, this approach is part of the natural evolution of engineering at Triple E: applying proven knowledge where it can deliver value. Because when safety is a requirement, starting from scratch is not always the best decision.
Methodology as a key differentiator
This evolution also opens up a clear opportunity within the sector. There are systems with SIL2 requirements developed by highly specialized manufacturers in other disciplines, such as mechanics, which often rely on external software solutions.
In this context, not only technical capability matters—the methodology behind it is equally critical.
Certifying a system under SIL2 involves rigorous processes: risk analysis, structured development, full traceability, and validation under criteria audited by accredited entities. While each solution is different, they all share a common foundation in terms of procedures, tools, and quality approach.
This is where accumulated knowledge makes the difference.
At Triple E, we rely on a well-established development methodology, along with the tools and processes required to address new critical systems with confidence. This allows us not only to design solutions tailored to each application, but to do so on a solid foundation that reduces risk, shortens development time, and ensures the required level of reliability.
It’s not just about developing new systems—it’s about doing so by leveraging experience already validated in environments where demands are at their highest.
