Tutorials

The tutorials are scheduled on Wednesday morning 26 November. The second and third tutorial are in parallel with the first tutorial.

• Günther Siegel and Jair Gonzales (Ansys, France): EN 50716 in Practice: New Requirements and Practices for Safe Railway Software
  Abstract: The first part of this tutorial will cover the key differences between EN 50716 and EN 50128. Emphasis will be placed on advancements in software development methodologies, including the recognition of Model-based techniques, Agile development, and an expanded focus on formal methods. Additionally, we will touch upon AI and Machine Learning, highlighting how the guidance aligns with the rail industry's careful, safety-first approach while still fostering innovation.
  The second part of the tutorial will use two representative rail systems, Slip-Slide Detection and Interlocking, to illustrate how EN 50716 can be implemented using SCADE. This part will start with a quick introduction to understand the fundamentals of SCADE and its applications in rail systems and will cover agile Model-Based Design, integration in DevOps workflows and leveraging formal verification. Each topic will be illustrated on the examples and the compliance with the standard clearly explained.
• Arne Borälv (Prover Technology, Stockholm, Sweden): AC/DC and GO: An Ontology-based Approach to Requirements Validation
  Abstract: This tutorial will describe an ontology-based approach to validation of standard principles and requirements for a made-up version of ETCS Level 3 trackside, inspired by the Moving Block Specification, and based on recommended processes for Formal Methods application. The essential purpose is to enable definition of precise and verifiable requirements in terms of ontology concepts, to promote the use of standard V&V processes (e.g., for automated authorization of system implementations). The basic idea is simple: the ontology is the interface for defining different types of requirements (e.g., for configuration, design, test, and safety), and sharing this interface for all requirement types that apply helps to (i) detect problems in coherence and consistency (ii) resolve interpretation issues, and (iii) converge on an ontology that is of good quality and meets the needs. Here, the ontology is divided into an upper ontology (universal, system-independent concepts) and a lower ontology (domain-specific concepts), with further categorization into Architecture Concepts, Design Concepts and Global Objects (AC/DC and GO). The ontology is defined using a prototype framework developed: this provides type checking, and backends to generate the ontology interface as an API in python and as a formal model in HLL (Many-Sorted First Order Logic). This tutorial will describe the main ingredients in this approach, example instantiation of the lower ontology obtained from automatic conversion of Trafikverket’s railway infrastructure data (in the semantic web formats RDF/Turtle), and example usages of the ontology interface for execution-based testing (using python) and formal verification (using HLL).
• Thierry Lecomte (CLEARSY, France): Advancements in the CLEARSY Safety Platform: From Academic Research to Industrial SIL4 Certification
  Abstract: Since its introduction as an academic project at the RSSRAIL Conference 2017, the CLEARSY Safety Platform has undergone significant advancements, achieving SIL4 certification and successful deployment in operational environments. This session will provide a comprehensive overview of the journey from an academic platform to a robust industrial solution. We will delve into the technical enhancements, certification challenges, and real-world applications that have shaped the CLEARSY Safety Platform into a reliable tool for the railway industry. Attendees will gain practical insights into the platform's capabilities, its role in enhancing railway safety, and the lessons learned from its implementation in industrial settings.