Skip to main content
Concept guide · EN 50126 / EN 50129 / EN 50716 · 15 chapters

Functional Safety in Railway

The CENELEC framework read by an automotive engineer: from the physics of the wheel-rail contact through THR, SIL, RAMS, fail-safe construction and ETCS to the authorization decision, and an honest comparison with ISO 26262.

Chapters
15
Chapters
RAMS lifecycle phases
12
RAMS lifecycle phases
EN 50159 message threats
7
EN 50159 message threats
Safety case parts
6
Safety case parts
Included inExpert
The short version

Quick answers

Is SIL 4 the same as ASIL D?
No, and the guide devotes a section to why the equals sign fails. A railway SIL is allocated to a safety-related function against a quantitative integrity target, a tolerable functional unsafe failure rate expressed per operating hour. An ASIL is assigned to a safety goal associated with a hazardous event, derived from severity, exposure and controllability, and it scales development rigor without attaching a probability target to the hazard. The two labels therefore classify different objects, arrive by different derivations, and are backed by different evidence packages. What is genuinely comparable is the idea of grading rigor with consequence, and the fact that both domains express rate targets in events per hour. Reuse across the aisle is legitimate, but it means re-arguing the evidence against the receiving objectives, not presenting a certificate.
Which railway standards do what?
EN 50126 carries the RAMS process and the twelve-phase lifecycle, telling you when a hazard analysis, an apportionment or a validation happens. EN 50129 is the safety-acceptance standard for safety-related electronic signalling systems: it defines the six-part safety case structure, technical safety evidence, random hardware fault control and the THR, TFFR and SIL framework. EN 50716:2023 is the railway software standard, merging the earlier EN 50128 for control and protection software with EN 50657 for rolling stock software. EN 50159 governs safety-related communication over transmission systems that are not themselves trusted. EN 50155 covers electronic equipment on rolling stock and is deliberately not a functional safety standard: it says the box survives the environment, not that its function is safe.
Why this course

Why it pays for itself

A second safety grammar, learned properly

THR, TFFR, SIL, RAMS, wrong-side failure, SRAC and authorization for placing in service explained from the physics up, so an automotive engineer can read a railway safety case and hold a conversation without translating badly.

The comparison done honestly

Three full chapters compare risk models, metrics and mechanisms, and process and ecosystem. They show exactly why the tidy ASIL to SIL mapping table fails as an engineering claim, and what an honest cross-domain reuse argument looks like instead.

Ideas worth importing

Explicit risk acceptance, exported assumptions tracked as numbered obligations with owners, and safety cases written for a competent independent reader are railway habits that improve automotive work, and the guide names them alongside what railway should take back.

After the course

What you’ll be able to do

Read the CENELEC Family Correctly

Know which standard owns which question, which layer is law and which is engineering practice, and why the edition cited in a contract matters as much as the number.

Follow a Risk Target from Hazard to Function

Trace risk acceptance through barrier crediting to a tolerable hazard rate, apportion it into per-function targets, and read the resulting SIL for what it does and does not buy.

Explain Fail-Safe Construction and Its Price

Distinguish wrong-side from right-side failures, compare inherent, reactive and composite fail-safety, and argue the exposure window between fault and enforced restrictive state.

Handle Safety Data Over Untrusted Networks

Apply the grey channel assumption, map each EN 50159 message threat to the defenses that catch it, and size a safety code against message traffic and the allocated failure budget.

Navigate the Safety Case and Approval Chain

Structure evidence into the six EN 50129 parts, track safety-related application conditions across generic and specific cases, and know which body decides what and when.

Compare Railway and Automotive Without Fooling Yourself

Explain why SIL and ASIL classify different objects, what is genuinely comparable across the aisle, and how a cross-domain reuse argument is rebuilt against the receiving standard.

The curriculum · 15 chapters

Chapter by chapter

  1. 01

    Why a Train Cannot Swerve

    The two freedoms a train does not have, the adhesion and energy arithmetic behind them, and the consequence that shaped everything since 1889: movement by authority granted by the infrastructure, not by the driver.

    • Adhesion and kinetic energy
    • The block principle
    • Precursors instead of accidents
  2. 02

    The Rulebook: CENELEC and the Railway Standards

    Why railway adapted IEC 61508 into its own family, what EN 50126, EN 50129, EN 50716, EN 50159 and EN 50155 each govern, and how EU law, CENELEC standards and the ETCS subsets stack into three layers.

    • Five core standards, one paragraph each
    • The 50128 and 50657 merge into 50716
    • Legal layer versus voluntary layer
  3. 03

    The Risk Model: THR and Risk Acceptance

    Individual and collective risk, the precursor discipline, the three national traditions ALARP, GAME and MEM, the CSM-RA acceptance routes, and the harmonised design targets introduced in 2015.

    • Three acceptance principles compared
    • CSM-RA and significant change
    • Risk matrices used honestly
  4. 04

    From Hazard to SIL

    The chain from hazard through credited barriers to a tolerable hazard rate, the apportionment of THR into per-function TFFR, the EN 50129 SIL bands, and what Basic Integrity below SIL 1 actually means.

    • Event-tree barrier crediting
    • THR to TFFR apportionment
    • Why there is no SIL 5
  5. 05

    The RAMS Lifecycle

    Why availability lives inside the safety standard, the twelve phases of EN 50126-1 drawn as stations rather than a V, the hazard log as the living spine, and the thirty-year service reality behind every decision.

    • Excessive fail-safety creates hazard
    • The hazard log and its two exit doors
    • MTBF and MTTR as the two levers
  6. 06

    Fail-Safe by Construction

    Wrong-side and right-side failures, inherent fail-safety through the closed-circuit principle and the automatic continuous brake, reactive and composite patterns, and where standstill is not simply safe.

    • Failure direction as first question
    • Detection and negation window
    • Fault exclusions carry obligations
  7. 07

    Hardware: Proving the Numbers

    How a signalling channel earns its failure rate: the evidence stack behind a quantitative claim, the three vital computing shapes, the scaling that makes comparison pay, and the independence it rents.

    • 2oo2, 2oo3 and coded mono processor
    • What the squared term assumes
    • Proof tests inside the quantitative case
  8. 08

    Software Under EN 50716

    Software integrity handled through process rather than rate: technique tables graded by integrity level, named roles with graded independence, tool classes T1 to T3, and where formal methods genuinely pay off.

    • Technique tables by SIL band
    • Roles, independence and the compiler question
    • Formally validated interlocking data
  9. 09

    Safe Communication: EN 50159

    Treating the transmission system as a grey channel with no credited safety properties, the seven named message threats, the defenses that ride in the message, and the residual error budget against the TFFR.

    • Three transmission system categories
    • Seven threats and their defenses
    • Sizing safety codes against traffic
  10. 10

    Train Control in Practice

    The interlocking as a machine that proves propositions before a signal clears, track circuits versus axle counters, fixed and moving block headway, the ETCS levels, and braking curve supervision onboard.

    • Route setting, flank protection, approach locking
    • ETCS Level 1 to Level 3 concepts
    • Level crossings and SPAD defense in depth
  11. 11

    The Safety Case and Approval

    The six mandatory parts of an EN 50129 safety case, the generic to specific reuse machine held together by safety-related application conditions, the assurance roles, and what an authorization actually covers.

    • Six parts, one dependency chain
    • SRACs as exported obligations
    • ISA, AsBo, NoBo, DeBo and the authority
  12. 12

    Railway vs Automotive: Risk Models

    THR and SIL held against HARA and ASIL: what each grammar classifies, where probability lives, why controllability has no direct railway counterpart, and the three reasons the equals sign between them fails.

    • One scenario, two derivations
    • Individual versus collective risk
    • How honest cross-domain reuse is argued
  13. 13

    Railway vs Automotive: Metrics and Mechanisms

    What each domain counts and why: TFFR and the single-fault principle against SPFM, LFM and PMHF, the two deadline clocks, and how maintenance credit and safe states diverge between the two ecosystems.

    • Both ladders on one log axis, with scope tags
    • FTTI versus detection plus negation
    • Number literacy in FIT
  14. 14

    Railway vs Automotive: Process and Ecosystem

    Who is allowed to say the work is good, two safety case cultures, why the software cultures diverged for economic and mathematical reasons, and two supply ecosystems compared on one timeline.

    • External chain versus internal confirmation measures
    • Per-change ceremony versus audited update process
    • SRACs versus SEooC assumptions and the DIA
  15. 15

    The One-Page Story

    One worked section-clear function traced from hazard through THR, TFFR, architecture, software, telegrams, safety case and authorization, plus a reference card, the comparison table and twelve terms to keep.

    • Eleven stations, one thread
    • Six self-test questions
    • What each side should steal
Built for

Who this guide is for

  • Automotive safety engineers meeting CENELEC evidence in a cross-domain project
  • Suppliers offering a SIL-rated platform into an ASIL item, or the reverse
  • Engineers moving between rail and automotive who need the vocabulary to transfer cleanly
  • Safety managers evaluating claims that a certificate in one domain satisfies the other
  • Anyone building an argument for fail-operational behavior who wants proven redundancy patterns
  • Assessors and trainers who need the two frameworks contrasted without hand-waving

Frequently Asked Questions

Common questions about Functional Safety in Railway

A tolerable hazard rate is the rate at which a hazardous state may occur such that, after the credited barriers do their statistical work, the resulting harm stays inside the risk acceptance criteria. It belongs to the hazard. Because engineers build functions rather than hazards, the target changes hands: EN 50129 uses the tolerable functional unsafe failure rate, the TFFR, as the per-function target. Where a single function guards the hazard the handover is direct; where several independent functions can each cause it, the THR is apportioned into slices that sum to it, and that apportionment is only legitimate if the independence, including independence from common systematic faults, is justified. The SIL is then a lookup from the resulting TFFR band, and it buys both a rate target and a package of measures against systematic faults.
Because the physics permits it. A train follows the track and cannot evade, so route-conflict hazards are largely controlled by preventing or holding movement, and a century of engineering made the restrictive reaction the one the construction falls into: the closed-circuit principle, gravity return in signalling relays, and the automatic continuous brake that applies when pipe pressure drops. It does not always hold. A train stopped in a long tunnel with a fire aboard, on a viaduct, or across a level crossing can be in a worse place than one still moving. The safe state is therefore a defined term per function and per operating context, recorded with the hazard analysis, and where a residual risk remains the operating rules carry part of the argument.
The guide argues that the divergence is economic and mathematical rather than cultural. Formal proof pays when the specification can be completed, the behavior is discrete, the volume is low and the change rate is slow. An interlocking is all four: safety logic over a finite track topology, with site configuration data that is a finite discrete structure with exact required properties, which is why formally validated interlocking data is routine industrial practice. A perception and driver assistance stack is the opposite on all four counts, so testing and process carry more of the weight there. Neither choice is a failure of nerve; each culture optimized honestly for its own problem shape.
Fifteen chapters: the physics that shaped the discipline; the CENELEC and EU legal rulebook; risk acceptance with ALARP, GAME, MEM and the CSM-RA routes; the derivation from hazard to THR, TFFR and SIL; the EN 50126 RAMS lifecycle and hazard log; fail-safe construction; the quantitative hardware argument and the vital computing architectures; EN 50716 software with technique tables, roles and tool classes; EN 50159 safe communication; interlocking, train detection, headway and ETCS; the six-part safety case and the assessment and authorization chain; and three comparison chapters on risk models, metrics and mechanisms, and process and ecosystem, closing with one worked function traced end to end plus a reference card and glossary.

Start the course today

A free account unlocks one full concept guide, 3 work product templates, 1 guided process, the Markov simulator, and 5 practice exams per month. The Pro and Expert plans unlock more of the 78-guide library. No credit card required.