OdysseyGPT

Standards explainer

EN 50126 explained: RAMS for railway applications and what a component supplier is asked to deliver

A plain-English overview of EN 50126 for bid, RAMS and quality engineers at rail component makers, ending with a checklist for the RAMS requirements in a tender.

By Ademola Afolabi, Founder, New Odyssey Ltd · Last reviewed:

The short answer

EN 50126 is the European standard for specifying and demonstrating reliability, availability, maintainability and safety, known as RAMS, in railway applications. Part 1 sets out a generic RAMS process that follows the system life cycle. Part 2 covers the systems approach to safety. It gives a process to follow. It sets no RAMS targets for any product.

Key Takeaways

  • RAMS stands for reliability, availability, maintainability and safety. EN 50126 treats the four together because they affect each other.
  • EN 50126-1 describes a process tied to the life cycle. It is meant to be tailored, and it sets no numbers.
  • The targets, the analyses and the delivery dates a supplier must meet come from the customer's specification and contract.
  • EN 50716 covers railway software and EN 50129 covers safety-related electronic systems for signalling. Both refer back to EN 50126.

See how OdysseyGPT reviews a tender. Tell us how your team reviews tenders today. We can walk through an example together. Book a call

What does RAMS mean?

RAMS is short for reliability, availability, maintainability and safety. In a railway contract the four words have working meanings that a bid engineer can use.

The four RAMS terms in working language (own summary, not the standard's definitions)
TermThe question it answersHow a specification usually expresses it
ReliabilityHow often does the item fail?A failure rate, or a mean time or distance between failures, often split by how badly the failure affects service
AvailabilityHow much of the time is it ready to do its job?A percentage, or a limit on delays and cancellations caused by the item
MaintainabilityHow quickly and easily can it be kept in or returned to working order?Repair times, access and tooling rules, maintenance intervals and the skills needed
SafetyIs the risk of harm acceptably low?Safety requirements for named functions, hazards to be controlled and evidence to be delivered

The four are handled together because a change to one moves the others. A design made safer by shutting down on any doubtful signal is less available. A unit that is hard to reach takes longer to repair, and availability falls. EN 50126 asks the parties to manage these trade-offs openly. The RAMS glossary entry has a shorter definition.

What is EN 50126 and what does it cover?

EN 50126 is a CENELEC standard titled Railway applications: The specification and demonstration of reliability, availability, maintainability and safety (RAMS). The current edition is in two parts, both dated 2017, and both were amended in 2024.

  • EN 50126-1, Generic RAMS process. It explains RAMS and how the four elements interact, and it sets out a life-cycle process for managing RAMS, specifying RAMS requirements and showing they are met.
  • EN 50126-2, Systems approach to safety. It deals with the safety side of the same life cycle, including methods for deriving safety requirements.

Part 1 applies across the railway: command, control and signalling, rolling stock and fixed installations. It can be used at any level, from a complete railway system down to a subsystem or a component, and that includes items containing software. It is written for both the railway duty holder and the supplier.

What it leaves out matters as much. Part 1 does not set RAMS targets, quantities or solutions for any application, and it does not lay down rules for certification or an approval process. It is a framework. The numbers and the evidence required for your product come from the customer and, for safety, from the applicable regulations.

Tailoring is expected

The process in Part 1 is meant to be scaled to the item. A supplier of a seat frame and a supplier of a brake control unit do not owe the same RAMS programme. A well-written specification says which activities and deliverables apply. Where it only says "RAMS to EN 50126", ask the customer to list them.

The life-cycle approach

EN 50126-1 organises RAMS work around a life cycle of twelve phases, usually drawn as a V. The left arm runs down from the idea to the detailed design. The right arm runs back up through building, testing and acceptance, with each step on the right checked against its partner on the left. In broad terms the phases run in this order.

  1. Concept, and definition of the system and the conditions it will operate in.
  2. Risk analysis and evaluation.
  3. Specification of system requirements, including the RAMS requirements.
  4. Architecture, and the sharing out of the requirements to subsystems and components.
  5. Design and implementation, then manufacture.
  6. Integration, system validation and system acceptance.
  7. Operation, maintenance and performance monitoring, and finally decommissioning.

This is a grouped overview in our own words, not the phase list from the standard. Use your licensed copy for the phase names, their numbers and the tasks in each.

A component supplier meets the life cycle part-way down. The train builder has already done the system-level work and shared out its targets. Your failure-rate target, your repair-time limits and your safety requirements are the result of that apportionment. Your own evidence then travels back up: the train builder uses your analyses and test results as inputs to the vehicle-level case. That is why the customer fixes the format and the dates of your RAMS documents so firmly.

What is a component supplier usually asked to deliver?

EN 50126 does not hand a supplier a fixed list of documents. The list comes from the customer. The table shows requests that appear in many rolling stock component specifications. Treat it as a guide to what to look for and not as a requirement of the standard.

Typical RAMS requests to a rail component supplier (own summary of common practice)
DeliverableWhat it isWhat to check in the request
RAMS planHow the supplier will organise RAMS work on this project: tasks, responsibilities, methods and datesWhether the customer supplies a template and when the first issue is due
Reliability predictionAn estimate of the failure rate of the unit, built up from its parts or from service dataThe method or data source the customer accepts, and the failure categories it wants reported
FMECAFailure modes, effects and criticality analysis: each way a part can fail, what follows and how serious it isThe level of detail wanted, the severity scale and whether the customer's spreadsheet format is mandatory
Hazard log inputsThe supplier's contribution to the customer's record of hazards: hazards arising from the unit, their causes and the measures takenWho owns the log, the format of the inputs and how safety requirements passed back to the customer are recorded
Maintainability dataPreventive maintenance tasks and intervals, repair and replacement times, tools, access and skillsWhether times must be demonstrated on hardware, and at which milestone
Life-cycle cost inputsSpare parts prices, consumption rates, overhaul intervals and labour hoursThe cost model the customer uses and whether the figures become commitments
Safety evidence for safety-related functionsA document set showing how the safety requirements placed on the unit are metWhich functions are classed as safety-related and whether an independent assessment is required
In-service reliability reportingFailure reports and analysis during the warranty or a reliability demonstration periodThe counting rules, the period, and what follows if the target is missed

Most customers tie these documents to design reviews. A first issue is due before the preliminary review and an update before the final one. A late RAMS document can hold up a design review, and with it a payment milestone.

What to check in a tender's RAMS requirements

Use this list when a technical specification, a RAMS specification or the contract sets RAMS requirements. It is our own checklist, not an extract from the standard.

Tender checklist for RAMS requirements (own summary)
CheckWhy it mattersWhere to look
Which edition of EN 50126 and its companions is citedThe 2017 edition is structured differently from the older one, and the software standard has changedThe standards list and the RAMS section
Every numerical target, with its unitHours, kilometres and operating cycles are not interchangeableTechnical specification, RAMS specification and the contract terms
How a failure is defined and countedA target means little until you know which events count against itDefinitions section and any failure category table
The operating profile behind the figuresA failure rate depends on duty, climate and annual mileageOperating conditions and environment clauses
The list of RAMS deliverables and their due datesEach one is work to price and scheduleDocument list, RAMS specification, project programme
Mandatory templates and methodsReworking an analysis into the customer's format takes timeAnnexes to the RAMS specification
Which functions the customer classes as safety-relatedThey bring extra evidence and sometimes independent assessmentSafety requirements section and interface documents
Software in the productA software standard and its documents then applyThe specification's software clauses and your own product description
Reliability demonstration and penaltiesA missed target can carry a commercial consequenceWarranty, reliability growth and liquidated damages clauses
Maintainability demonstrationTimed tasks on real hardware need a unit, tools and peopleMaintainability clauses and the test plan requirements
Data the customer must give youYou cannot answer without the apportioned targets and the hazards passed downInterface documents and the list of customer inputs
Requirements you must pass to your own sub-suppliersYour figures depend on theirsFlow-down clauses in the supplier quality requirements

Customer Specification Review (beta) lists the RAMS obligations in a tender package as separate lines, each with its clause, so the targets and the deliverables are not missed in a long specification. Document Review checks those lines against your RAMS plan and offer text and quotes both sides for each finding. VDRL/MDR Tracker (beta) keeps the due dates of the deliverables. OdysseyGPT does not perform RAMS analysis. It does not predict a failure rate, build an FMECA or assess a hazard, and it is not a requirements management system. The wider enquiry is covered on the rail component manufacturers page.

Talk through your tender review

See how OdysseyGPT reviews a tender

Tell us how your team reviews tenders today. We can walk through an example together.

Book a call

Frequently asked questions

Does EN 50126 set reliability targets?

No. It describes a process for specifying and demonstrating RAMS. The targets for a product come from the customer's specification and contract.

Does EN 50126 apply to mechanical components?

Yes. Part 1 can be applied from a complete railway system down to a component, whatever the technology. How much of the process applies to a given item is a matter of tailoring, which the customer's specification should state.

Is EN 50128 still the railway software standard?

EN 50716, published in 2023, supersedes EN 50128 and EN 50657. Older contracts and products may still refer to the earlier standards. Use the one your contract names.

Does OdysseyGPT write an FMECA or a reliability prediction?

No. It reads the customer's RAMS requirements and your documents and shows which requested items, figures and dates your documents do not address. The analysis is done by your RAMS engineer.

References

EN 50126-1:2017 Railway applications. The specification and demonstration of reliability, availability, maintainability and safety (RAMS). Part 1: Generic RAMS process

Estonian Centre for Standardisation and Accreditation (EVS)

Paid standard. Catalogue page used for the scope: what the part covers, who it is for and what it excludes. Read 15 Nov 2026.

Visit source

EN 50126-1:2017+A1:2024 (consolidated)

Estonian Centre for Standardisation and Accreditation (EVS)

Catalogue listing of the 2024 amendment to Part 1.

Visit source

EN 50126-2:2017 Railway applications. The specification and demonstration of RAMS. Part 2: Systems approach to safety

Estonian Centre for Standardisation and Accreditation (EVS)

Paid standard. Catalogue page used for the title and scope.

Visit source

EN 50716:2023 Railway applications. Requirements for software development

Genorma

Catalogue listing used for the title, date and the standards it supersedes (EN 50128 and EN 50657).

Visit source

EN 50129 Railway applications. Communication, signalling and processing systems. Safety related electronic systems for signalling

Genorma

Catalogue listing used for the title and scope, and for the fact that a 2026 edition follows the 2018 one.

Visit source

Related Pages