This is a great opportunity to meet with the railway industry and to get better insight in the needs of rail control software solutions. At RSSI 2022 on 16-18 May we will put our solutions on display and look forward to getting back to face-to-face dialogues with colleagues in the business again.
Since the last RSSI exhibition, prior Covid, several steps towards a digitalized railway have been taken. Prover’s solutions contribute to the digitalization and automation of signaling engineering tasks. With our Digital Twin concept, Prover will take part in the transformation from existing technologies towards a modern signaling system with control over the lifecycle of rail control systems.
Prover offers Signaling Design Automation solutions for automated coding, documentation, simulation and formal safety verification of application software, targeting major interlocking system platforms such as ElectroLogIXS, iVPI, Microlok II and Westrace. Users of the Prover iLock Process include major railroads and transit agencies such as Canadian Pacific, NYCT and the Paris Metro (RATP), as well as signal systems suppliers.
Looking forward to meeting you at RSSI 2022! Read more about the event.
Share this article
Learn to build a solid safety case for rail control systems using formal verification
Fill out your information here.
More News & Articles
When replacing relay interlockings, most conversations start with technology. The better starting point is governance: how do you make sure you can still change parts of the system 20 years from now? We look at what Open Signaling means in practice, and how our Stockholm Metro pilot was designed for replaceability from day one.
Prover, RATP and Systerel publish the unified HLL 4.0 specification, keeping the rail industry's formal verification language open and free of dialects.
Generative AI has entered railway software engineering ahead of the standards governing it. A new CENELEC draft amendment to EN 50716 doesn't add requirements. It clarifies which existing rules apply when AI drafts specs, writes code, or generates test cases, and why those rules are harder to satisfy with generative models than teams might assume.
+46 (0)8 617 68 00