<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="client.xsl" type="text/xsl"?>
<article article-type="other">
<front>
<journal-meta>
<journal-id/>
<issn/>
<banner>
<href>banner.jpg</href>
<size width="100%"/>
</banner>
</journal-meta>
<doi>0124-cd</doi>
<article-meta>
<title-group>
<article-title>Development of an Extended RAMS Framework for Railway Networks</article-title>
</title-group>

<author>Jack Litherland<sup>1,a</sup>, Gareth Calvert<sup>1</sup>, John Andrews<sup>1</sup> and Andy Kirwan <sup>2</sup></author>

<aff><sup>1</sup>Resilience Engineering Research Group, University of Nottingham, United Kingdom.</aff>
<email><a href="mailto:jack.litherland@nottingham.ac.uk"><sup>a</sup>jack.litherland@nottingham.ac.uk</a></email>
<aff><sup>2</sup>Safety, Technical and Engineering Directorate, Network Rail, United Kingdom</aff>




</article-meta></front>
<body>
<abstract>
<title>ABSTRACT</title>
<p>Railway asset managers have finite resources which requires them to make strategic decisions on where, when and how the available budget will be spent on the railway, while ensuring safety limits are maintained and a high level of performance is delivered for customers. The purpose of this research is to develop a suitable framework, which can be used by railway asset managers, to quantify asset performance in a way that enables comparisons between different parts of the railway and enables the asset manager to make key decisions on how the railway can be improved. A frequently used assessment tool is RAMS (Reliability, Availability, Maintainability and Safety) analysis. In recent years RAMS analysis has been extended to include additional parameters such as: security, health, environment, economics and politics (SHEeP). This research proposes an extended RAMS framework, which considers 12 parameters in a four level hierarchy, specifically for use on railway networks by railway asset managers.</p>
<p><italic>Keywords: </italic>Asset Management, Performance, Railway, RAMS, RAMSSHE&#8364;P.</p>
</abstract>
<fpdf>
<href>pdflogo.jpg</href>
<hpdf>0124</hpdf>
</fpdf>
</body>
</article>