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.
| Term | The question it answers | How a specification usually expresses it |
|---|---|---|
| Reliability | How 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 |
| Availability | How much of the time is it ready to do its job? | A percentage, or a limit on delays and cancellations caused by the item |
| Maintainability | How 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 |
| Safety | Is 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.
- Concept, and definition of the system and the conditions it will operate in.
- Risk analysis and evaluation.
- Specification of system requirements, including the RAMS requirements.
- Architecture, and the sharing out of the requirements to subsystems and components.
- Design and implementation, then manufacture.
- Integration, system validation and system acceptance.
- 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.
| Deliverable | What it is | What to check in the request |
|---|---|---|
| RAMS plan | How the supplier will organise RAMS work on this project: tasks, responsibilities, methods and dates | Whether the customer supplies a template and when the first issue is due |
| Reliability prediction | An estimate of the failure rate of the unit, built up from its parts or from service data | The method or data source the customer accepts, and the failure categories it wants reported |
| FMECA | Failure modes, effects and criticality analysis: each way a part can fail, what follows and how serious it is | The level of detail wanted, the severity scale and whether the customer's spreadsheet format is mandatory |
| Hazard log inputs | The supplier's contribution to the customer's record of hazards: hazards arising from the unit, their causes and the measures taken | Who owns the log, the format of the inputs and how safety requirements passed back to the customer are recorded |
| Maintainability data | Preventive maintenance tasks and intervals, repair and replacement times, tools, access and skills | Whether times must be demonstrated on hardware, and at which milestone |
| Life-cycle cost inputs | Spare parts prices, consumption rates, overhaul intervals and labour hours | The cost model the customer uses and whether the figures become commitments |
| Safety evidence for safety-related functions | A document set showing how the safety requirements placed on the unit are met | Which functions are classed as safety-related and whether an independent assessment is required |
| In-service reliability reporting | Failure reports and analysis during the warranty or a reliability demonstration period | The 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.
| Check | Why it matters | Where to look |
|---|---|---|
| Which edition of EN 50126 and its companions is cited | The 2017 edition is structured differently from the older one, and the software standard has changed | The standards list and the RAMS section |
| Every numerical target, with its unit | Hours, kilometres and operating cycles are not interchangeable | Technical specification, RAMS specification and the contract terms |
| How a failure is defined and counted | A target means little until you know which events count against it | Definitions section and any failure category table |
| The operating profile behind the figures | A failure rate depends on duty, climate and annual mileage | Operating conditions and environment clauses |
| The list of RAMS deliverables and their due dates | Each one is work to price and schedule | Document list, RAMS specification, project programme |
| Mandatory templates and methods | Reworking an analysis into the customer's format takes time | Annexes to the RAMS specification |
| Which functions the customer classes as safety-related | They bring extra evidence and sometimes independent assessment | Safety requirements section and interface documents |
| Software in the product | A software standard and its documents then apply | The specification's software clauses and your own product description |
| Reliability demonstration and penalties | A missed target can carry a commercial consequence | Warranty, reliability growth and liquidated damages clauses |
| Maintainability demonstration | Timed tasks on real hardware need a unit, tools and people | Maintainability clauses and the test plan requirements |
| Data the customer must give you | You cannot answer without the apportioned targets and the hazards passed down | Interface documents and the list of customer inputs |
| Requirements you must pass to your own sub-suppliers | Your figures depend on theirs | Flow-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.
