Imagine a train weighing thousands of tons, moving at 200 km\/h – and hundreds operating simultaneously across a network, guided only by software and signals. When everything works as intended, operations are seamless. However, if something goes wrong, the consequences can be catastrophic, including lives at risk, infrastructure damage, and service disruption.<\/span><\/p>\n Over the past decades, railway control systems have grown increasingly complex. Testing and manual reviews remain essential, but they can no longer ensure full coverage. The number of possible system states is simply too vast. In many cases, billions of combinations that no test suite could ever exhaust. Traditional methods show the <\/span>existence<\/span><\/i> of bugs, not their <\/span>absence<\/span><\/i>.<\/span><\/p>\n Formal Safety Verification (FSV)<\/span><\/i> is a breakthrough approach that utilizes mathematical proof to ensure a system meets its safety requirements in every possible state. Instead of relying on selected test cases, engineers use models and automated verification tools to prove that no unsafe scenarios can occur exhaustively.<\/span><\/p>\n Prover\u2019s Solution Formal Safety Verification<\/i> makes this process industrially viable. It integrates proven formal methods with efficient tooling to verify complex rail control systems at scale, across all Safety Integrity Levels (SIL 0-4) and in compliance with CENELEC standards EN 50716, EN 50126, EN 50128, and EN 50129.<\/span><\/p>\n In EN 50126, safety is an independent process that starts with the identification of all potential hazards that can affect your system. Then, provided the likelihood of these risks is high enough, some mitigation is added as an extra requirement to the development of the system, with a dedicated SIL level. <\/span><\/p>\n F<\/span>or instance, a function of the control system will be tagged as SIL4, and the means to address this criticality is to develop this function following the EN 50716 process, with testing and reviews, and even formal proof to verify that the requirements are correctly implemented. The safety case then collects evidence that the whole process covers these risks, by the book. <\/span><\/p>\n Traditional verification relies heavily on reviews and test campaigns that are both labor-intensive and prone to human error. Engineers spend valuable time ensuring coverage and tracking potential corner cases: test scenarios are based on the experience or imagination of the test team.<\/span><\/p>\n Formal Safety Verification<\/span><\/i> changes the paradigm. Instead of ensuring that the requirements are implemented as they should be, the new process begins with the hazards themselves, utilizing a model of the system design in a formal language to create a <\/span>digital twin<\/span><\/i> of the control system. Automated model checkers then verify that the model fully satisfies all hazards, independently of their mitigation. If issues exist, they are presented as high-level scenarios, such as train movements or route conflicts, enabling engineers to pinpoint and resolve potential hazards early.<\/span><\/p>\n The result: complete coverage, faster verification cycles, and certified safety evidence generated automatically.<\/span><\/p>\n At the heart of Prover\u2019s solution lies <\/span>Prover Diagnostic<\/b> – a packaged, hazard-based formal verification tool that identifies and eliminates potential safety risks before deployment.<\/span><\/p>\n Prover Diagnostic integrates:<\/span><\/p>\n Together, these components form a rigorous verification process in which hazardous states are either proven impossible or clearly reported for review. Prover Diagnostic ensures 100% coverage, a feat no test-based approach can match.<\/span><\/p>\n Formal Safety Verification<\/span><\/i> isn\u2019t theoretical – it\u2019s field-proven for many years.<\/span><\/p>\n These projects demonstrate the maturity and scalability of Formal Safety Verification<\/i> in real-world railway environments. In many cases, the process reveals and allows for the correction of critical bugs missed by traditional testing.<\/span><\/p>\nA new era of railway safety verification<\/b><\/h3>\n
How safety is usually handled<\/b><\/h3>\n
From traditional testing to formal proof<\/b><\/h3>\n
Introducing Prover Diagnostic<\/b><\/h3>\n
\n
Proven in leading railway projects<\/b><\/h3>\n
\n
Formal Safety Verification: a summary of the benefits<\/b><\/h3>\n