<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[IRSE Exam Forum - Specific topics]]></title>
		<link>https://irse.signalpost.org/</link>
		<description><![CDATA[IRSE Exam Forum - https://irse.signalpost.org]]></description>
		<pubDate>Thu, 16 Apr 2026 13:18:32 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[Technical Specification of Railway Signalling System]]></title>
			<link>https://irse.signalpost.org/showthread.php?tid=2163</link>
			<pubDate>Thu, 29 Dec 2016 13:31:26 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://irse.signalpost.org/member.php?action=profile&uid=3699">soylemezv</a>]]></dc:creator>
			<guid isPermaLink="false">https://irse.signalpost.org/showthread.php?tid=2163</guid>
			<description><![CDATA[<span style="color: #336633;" class="mycode_color">Hi,</span><br />
<br />
<span style="color: #336633;" class="mycode_color">I have been working on technical specifications. In basically , Which informations should be included in a technical specification for a new  line? I only consider informations that to be written quantitative, such as headway, dwell time, maximum speed , temporary speed restrictions etc. I exclude the interfaces between signal system and other systems. </span><br />
<br />
<span style="color: #336633;" class="mycode_color">What can be written about the following topics?(From the railway administrator perspective) </span><br />
<br />
<span style="color: #336633;" class="mycode_color">Interlocking</span><br />
<span style="color: #336633;" class="mycode_color">Track circuits&amp;Axle counters</span><br />
<span style="color: #336633;" class="mycode_color">Switches </span><br />
<span style="color: #336633;" class="mycode_color">Signals</span><br />
<span style="color: #336633;" class="mycode_color">Train-wayside communication </span><br />
<span style="color: #336633;" class="mycode_color">ATP and ATO </span><br />
<span style="color: #336633;" class="mycode_color">Reliability,availability,maintainability and safety</span><br />
<br />
<span style="color: #336633;" class="mycode_color">Especially ,about the track circuits &amp; axle counters, signals and point machines Can you share with me If you have technical specification? Happy New Year to all! Thanks.<br />
</span>]]></description>
			<content:encoded><![CDATA[<span style="color: #336633;" class="mycode_color">Hi,</span><br />
<br />
<span style="color: #336633;" class="mycode_color">I have been working on technical specifications. In basically , Which informations should be included in a technical specification for a new  line? I only consider informations that to be written quantitative, such as headway, dwell time, maximum speed , temporary speed restrictions etc. I exclude the interfaces between signal system and other systems. </span><br />
<br />
<span style="color: #336633;" class="mycode_color">What can be written about the following topics?(From the railway administrator perspective) </span><br />
<br />
<span style="color: #336633;" class="mycode_color">Interlocking</span><br />
<span style="color: #336633;" class="mycode_color">Track circuits&amp;Axle counters</span><br />
<span style="color: #336633;" class="mycode_color">Switches </span><br />
<span style="color: #336633;" class="mycode_color">Signals</span><br />
<span style="color: #336633;" class="mycode_color">Train-wayside communication </span><br />
<span style="color: #336633;" class="mycode_color">ATP and ATO </span><br />
<span style="color: #336633;" class="mycode_color">Reliability,availability,maintainability and safety</span><br />
<br />
<span style="color: #336633;" class="mycode_color">Especially ,about the track circuits &amp; axle counters, signals and point machines Can you share with me If you have technical specification? Happy New Year to all! Thanks.<br />
</span>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Environmental Conditions, EN50125]]></title>
			<link>https://irse.signalpost.org/showthread.php?tid=1116</link>
			<pubDate>Mon, 05 Nov 2012 18:24:18 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://irse.signalpost.org/member.php?action=profile&uid=8">PJW</a>]]></dc:creator>
			<guid isPermaLink="false">https://irse.signalpost.org/showthread.php?tid=1116</guid>
			<description><![CDATA[EN50125-3 considers three situations:<br />
T1 (warm temperate, warm dry) <br />
T2 (Cold temperate) and <br />
TX (Cold)<br />
<br />
Gives information about the environment in which equipment should be able to perform-<br />
<br />
·  Pressure (altitude, pulse pressure due to tunnel etc)<br />
<br />
·  Temperature (extremes, rate of change)<br />
<br />
·  Humidity (ambient, in cubicle, in shelter, in building, sudden rate of change)<br />
<br />
·  Wind (natural, passing trains)<br />
<br />
·  Rain (also considered combined with wind)<br />
<br />
·  Snow and Hail (all types of snow, driven snow by wind / vehicles passing and on board)<br />
<br />
·  Ice<br />
<br />
·  Solar radiation<br />
<br />
·  Lightning  <br />
<br />
·  Pollution (chemical, biologically active, mechanically abrasive, electrically conductive)<br />
<br />
·  Fire protection<br />
<br />
·  Vibration (energy level, distribution across frequency range)<br />
<br />
·  Shocks (for mounting: on rail, on sleeper, in ballast, trackside)<br />
<br />
·  Electromagnetic Compatibility (victim, source)<br />
<br />
·   Power Supply (spec, tolerance of voltage and frequency)]]></description>
			<content:encoded><![CDATA[EN50125-3 considers three situations:<br />
T1 (warm temperate, warm dry) <br />
T2 (Cold temperate) and <br />
TX (Cold)<br />
<br />
Gives information about the environment in which equipment should be able to perform-<br />
<br />
·  Pressure (altitude, pulse pressure due to tunnel etc)<br />
<br />
·  Temperature (extremes, rate of change)<br />
<br />
·  Humidity (ambient, in cubicle, in shelter, in building, sudden rate of change)<br />
<br />
·  Wind (natural, passing trains)<br />
<br />
·  Rain (also considered combined with wind)<br />
<br />
·  Snow and Hail (all types of snow, driven snow by wind / vehicles passing and on board)<br />
<br />
·  Ice<br />
<br />
·  Solar radiation<br />
<br />
·  Lightning  <br />
<br />
·  Pollution (chemical, biologically active, mechanically abrasive, electrically conductive)<br />
<br />
·  Fire protection<br />
<br />
·  Vibration (energy level, distribution across frequency range)<br />
<br />
·  Shocks (for mounting: on rail, on sleeper, in ballast, trackside)<br />
<br />
·  Electromagnetic Compatibility (victim, source)<br />
<br />
·   Power Supply (spec, tolerance of voltage and frequency)]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Functional Testing v Principles testing, Verification and Validation]]></title>
			<link>https://irse.signalpost.org/showthread.php?tid=994</link>
			<pubDate>Thu, 22 Mar 2012 18:21:14 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://irse.signalpost.org/member.php?action=profile&uid=8">PJW</a>]]></dc:creator>
			<guid isPermaLink="false">https://irse.signalpost.org/showthread.php?tid=994</guid>
			<description><![CDATA[I was asked privately to explain the difference between Principles Testing and Functional testing.  The question was asked in the context of Australia.<br />
<br />
Thought it worth copying my answer here as I expect this may be helpful to others.  Also I have never even been to Australia can only assume that it follows current UK terminology, so perhaps someone else can comment from that perspective.<br />
<br />
<span style="font-style: italic;" class="mycode_i">  I just got a doubt what is the difference between functional testing and Principle testing. Can you please tell me and what is this verification and validation testing. </span><br />
<br />
I can tell you what it now means in a UK context; I guess that Australia would be the same, HOWEVER I should also tell you that when I started of the Western Region of British Rail in 1981 then what we THEN called "functional testing" is precisely what NOW is called "Principles testing"! Hence beware- usage can vary.... <br />
<br />
Functional testing is testing that checks out individual parts of a system, involving the application of power to exercise the circuits etc. So getting points to throw in response to a call, measuring that the voltages and currents are correct, making sure that the clutch slips appropriately and that the timer cuts off after 7.5seconds is an example. Similarly the fact that the point contactor relays operate in response to the interlocking and have the correct voltage and polarity and use the correct cable cores fed from the specified fuse. <br />
<br />
So is the circuit testing in the interlocking that proves contact A1/A2 of AE TPR is a front contact and is effective at cutting the feed to 361GR so that the signal goes back to danger. The key thing is that each test done is ticked off or otherwise recorded on the design details another copy of which was used during installation to produce the product being tested. It is VERIFICATION that we have built correctly what the designer designed. "Did we built it right"<br />
<br />
<br />
Principles testing is about VALIDATION; is what we have built "fit for purpose"?   "Did we build the right thing?"<br />
So the tester looking only at the Signalling Plan and signalbox diagram DECIDES FOR THEMSELVES what locking would be appropriate in order that a set of points should be allowed to move or a route to be set or for a signal to show a particular aspect. They then "functionally" investigate to see whether the actual implementation agrees with their expectation and only when satisfied then asserts that the locking exists. They are NOT LOOKING AT THE CONTROL TABLES, but call out to someone else who is looking so that it is then recorded by ticking entry on the Control Tables. The tester calls out the locking that they expected and had found to be effective. <br />
<br />
Hence if the designer has made an error and omitted a control, the Principles tester will discover the error because he is not relying upon the designer (as has made up their own mind first); The functional tester however won't have discovered the error as what they have proved is that the installer has correctly wired the circuit as designed, the relay is of the correct spec, there is enough voltage for the relay to pick and then no residual voltage when it should drop. <br />
<br />
Principles testing (at least in theory) is undertaken on the completed entire system whereas the functional occurs little by little on increasingly larger assemblies (e.g.test point machine in factory, test prewired location odff-site,, test from location to point machine locally, test relay room interlocking circuits, test between interlocking and location, test panel circuits, test between panel and interlocking etc. <br />
<br />
In practice, particularly with Solid State Interlocking some of the distinction (in terms of which grage of staff do what) is a bit blurred; rehearing the operation of points from the control centre to the point machine is technically Verification rather than involving any Validation, yet generaly the activity is led by a "Principles tester", oartly because there may be a need on the same shift to do some Principles, but often just because they are the more experienced people who can <br />
a) get things to work when there are problems and others would flounder, and <br />
b) just might see something very important that the less experienced would miss. <br />
<br />
Hope that helps. <br />
<br />
PJW <br />
]]></description>
			<content:encoded><![CDATA[I was asked privately to explain the difference between Principles Testing and Functional testing.  The question was asked in the context of Australia.<br />
<br />
Thought it worth copying my answer here as I expect this may be helpful to others.  Also I have never even been to Australia can only assume that it follows current UK terminology, so perhaps someone else can comment from that perspective.<br />
<br />
<span style="font-style: italic;" class="mycode_i">  I just got a doubt what is the difference between functional testing and Principle testing. Can you please tell me and what is this verification and validation testing. </span><br />
<br />
I can tell you what it now means in a UK context; I guess that Australia would be the same, HOWEVER I should also tell you that when I started of the Western Region of British Rail in 1981 then what we THEN called "functional testing" is precisely what NOW is called "Principles testing"! Hence beware- usage can vary.... <br />
<br />
Functional testing is testing that checks out individual parts of a system, involving the application of power to exercise the circuits etc. So getting points to throw in response to a call, measuring that the voltages and currents are correct, making sure that the clutch slips appropriately and that the timer cuts off after 7.5seconds is an example. Similarly the fact that the point contactor relays operate in response to the interlocking and have the correct voltage and polarity and use the correct cable cores fed from the specified fuse. <br />
<br />
So is the circuit testing in the interlocking that proves contact A1/A2 of AE TPR is a front contact and is effective at cutting the feed to 361GR so that the signal goes back to danger. The key thing is that each test done is ticked off or otherwise recorded on the design details another copy of which was used during installation to produce the product being tested. It is VERIFICATION that we have built correctly what the designer designed. "Did we built it right"<br />
<br />
<br />
Principles testing is about VALIDATION; is what we have built "fit for purpose"?   "Did we build the right thing?"<br />
So the tester looking only at the Signalling Plan and signalbox diagram DECIDES FOR THEMSELVES what locking would be appropriate in order that a set of points should be allowed to move or a route to be set or for a signal to show a particular aspect. They then "functionally" investigate to see whether the actual implementation agrees with their expectation and only when satisfied then asserts that the locking exists. They are NOT LOOKING AT THE CONTROL TABLES, but call out to someone else who is looking so that it is then recorded by ticking entry on the Control Tables. The tester calls out the locking that they expected and had found to be effective. <br />
<br />
Hence if the designer has made an error and omitted a control, the Principles tester will discover the error because he is not relying upon the designer (as has made up their own mind first); The functional tester however won't have discovered the error as what they have proved is that the installer has correctly wired the circuit as designed, the relay is of the correct spec, there is enough voltage for the relay to pick and then no residual voltage when it should drop. <br />
<br />
Principles testing (at least in theory) is undertaken on the completed entire system whereas the functional occurs little by little on increasingly larger assemblies (e.g.test point machine in factory, test prewired location odff-site,, test from location to point machine locally, test relay room interlocking circuits, test between interlocking and location, test panel circuits, test between panel and interlocking etc. <br />
<br />
In practice, particularly with Solid State Interlocking some of the distinction (in terms of which grage of staff do what) is a bit blurred; rehearing the operation of points from the control centre to the point machine is technically Verification rather than involving any Validation, yet generaly the activity is led by a "Principles tester", oartly because there may be a need on the same shift to do some Principles, but often just because they are the more experienced people who can <br />
a) get things to work when there are problems and others would flounder, and <br />
b) just might see something very important that the less experienced would miss. <br />
<br />
Hope that helps. <br />
<br />
PJW <br />
]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Earthing & Bonding; dc traction]]></title>
			<link>https://irse.signalpost.org/showthread.php?tid=933</link>
			<pubDate>Wed, 19 Oct 2011 18:49:42 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://irse.signalpost.org/member.php?action=profile&uid=8">PJW</a>]]></dc:creator>
			<guid isPermaLink="false">https://irse.signalpost.org/showthread.php?tid=933</guid>
			<description><![CDATA[See<br />
<a href="http://irse.org.au/images/stories/Knowledge/Power/IRSE%20Presentation%20on%20Electrolysis%20May%202010%20v2.pdf" target="_blank" rel="noopener" class="mycode_url">http://irse.org.au/images/stories/Knowle...0%20v2.pdf</a>]]></description>
			<content:encoded><![CDATA[See<br />
<a href="http://irse.org.au/images/stories/Knowledge/Power/IRSE%20Presentation%20on%20Electrolysis%20May%202010%20v2.pdf" target="_blank" rel="noopener" class="mycode_url">http://irse.org.au/images/stories/Knowle...0%20v2.pdf</a>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Human Factor Considerations and Human Error assessment]]></title>
			<link>https://irse.signalpost.org/showthread.php?tid=896</link>
			<pubDate>Sat, 27 Aug 2011 16:54:34 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://irse.signalpost.org/member.php?action=profile&uid=8">PJW</a>]]></dc:creator>
			<guid isPermaLink="false">https://irse.signalpost.org/showthread.php?tid=896</guid>
			<description><![CDATA[This seems to be a subject of which knowledge is generally weak judging my some answers I have seen recently.  It is relevant to many of the IRSE Exam modules and in particular module 7 and to a lesser extent module 1.<br />
<br />
I am no HF expert, but I have gathered together what I hope should be useful material re <br />
a) the role of ergonomics within signalling design generally<br />
b) in particular considerations relating to the interface with specific reference to Control Centres<br />
c) Human Error- categories, causes, estimating error rates etc.<br />
<br />
It does not seek to answer any particular exam question, although certain sections could form a lot of the content to various elements within such.]]></description>
			<content:encoded><![CDATA[This seems to be a subject of which knowledge is generally weak judging my some answers I have seen recently.  It is relevant to many of the IRSE Exam modules and in particular module 7 and to a lesser extent module 1.<br />
<br />
I am no HF expert, but I have gathered together what I hope should be useful material re <br />
a) the role of ergonomics within signalling design generally<br />
b) in particular considerations relating to the interface with specific reference to Control Centres<br />
c) Human Error- categories, causes, estimating error rates etc.<br />
<br />
It does not seek to answer any particular exam question, although certain sections could form a lot of the content to various elements within such.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[EMC / EMI; Electromagnetic Compatibility & Immunity]]></title>
			<link>https://irse.signalpost.org/showthread.php?tid=825</link>
			<pubDate>Tue, 12 Jul 2011 19:07:50 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://irse.signalpost.org/member.php?action=profile&uid=8">PJW</a>]]></dc:creator>
			<guid isPermaLink="false">https://irse.signalpost.org/showthread.php?tid=825</guid>
			<description><![CDATA[The London Study Group had a talk from an EMC expert recently on this topic; note that two of the 2010 module 7 questions were closely related to this subject.<br />
<br />
I am hoping that he may permit me to share his Powerpoint presentation on this forum.  In the meantime I am attaching a document that I was inspired to produce; I found that I didn't need all the time I had set aside last weekend for reviewing answers for the forthcoming mod2/3 Signet event, which gave me the opportunity to do this.<br />
<br />
It is not directly aimed at answering any specific exam question, but hopefully will provide a resource useful for tackling some of these; I have gathered together information from a range of documents and my own experience to attempt to shed some light onto an area of mystery for many.  For the IRSE exam you only need an appreciation of the overview, so I have spared you 3 dimensional Maxwell equations- divs, grads, curls and all the rest of university maths that in truth I have all but forgotten]]></description>
			<content:encoded><![CDATA[The London Study Group had a talk from an EMC expert recently on this topic; note that two of the 2010 module 7 questions were closely related to this subject.<br />
<br />
I am hoping that he may permit me to share his Powerpoint presentation on this forum.  In the meantime I am attaching a document that I was inspired to produce; I found that I didn't need all the time I had set aside last weekend for reviewing answers for the forthcoming mod2/3 Signet event, which gave me the opportunity to do this.<br />
<br />
It is not directly aimed at answering any specific exam question, but hopefully will provide a resource useful for tackling some of these; I have gathered together information from a range of documents and my own experience to attempt to shed some light onto an area of mystery for many.  For the IRSE exam you only need an appreciation of the overview, so I have spared you 3 dimensional Maxwell equations- divs, grads, curls and all the rest of university maths that in truth I have all but forgotten]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[About track circuit]]></title>
			<link>https://irse.signalpost.org/showthread.php?tid=658</link>
			<pubDate>Thu, 23 Sep 2010 12:16:49 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://irse.signalpost.org/member.php?action=profile&uid=508">oxfordjack</a>]]></dc:creator>
			<guid isPermaLink="false">https://irse.signalpost.org/showthread.php?tid=658</guid>
			<description><![CDATA[Where I can referrences for the below question?<br />
<br />
how track circuit affects the design nof traction current supply and return?<br />
<br />
Thank you.]]></description>
			<content:encoded><![CDATA[Where I can referrences for the below question?<br />
<br />
how track circuit affects the design nof traction current supply and return?<br />
<br />
Thank you.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[SAFETY CASES: Application and Application Specific]]></title>
			<link>https://irse.signalpost.org/showthread.php?tid=649</link>
			<pubDate>Sat, 18 Sep 2010 05:54:36 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://irse.signalpost.org/member.php?action=profile&uid=508">oxfordjack</a>]]></dc:creator>
			<guid isPermaLink="false">https://irse.signalpost.org/showthread.php?tid=649</guid>
			<description><![CDATA[Hello,<br />
<br />
Can someone let me brain storm on what different of Generic Application Safety Case and the Application Specific Safety Case??<br />
<br />
Thank you.]]></description>
			<content:encoded><![CDATA[Hello,<br />
<br />
Can someone let me brain storm on what different of Generic Application Safety Case and the Application Specific Safety Case??<br />
<br />
Thank you.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Specifications]]></title>
			<link>https://irse.signalpost.org/showthread.php?tid=369</link>
			<pubDate>Thu, 08 Apr 2010 18:50:25 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://irse.signalpost.org/member.php?action=profile&uid=30">adikarina</a>]]></dc:creator>
			<guid isPermaLink="false">https://irse.signalpost.org/showthread.php?tid=369</guid>
			<description><![CDATA[Hi all,<br />
I am struggling to find some information regarding the different types of specifications and when which type should be used. <br />
<br />
Please provide some guidance as where to find it.<br />
<br />
Thanks <br />
Aditi<br />
<br />
Not surprised; I can't immediately put my finger on one good source.  Sure there are several references but I'll need some time to get a selection together; also I think they'll be a need to derive what you need from a composite of sources as background reading rather than a ready written comparison.<br />
<br />
In the meantime to get you thinking on the right lines, I suggest you consider what you would do in your own life re a variety of possible purchases.  For each of the following categories, how would you decide between a range of items on sale when looking to purchase :<br />
a) a house <br />
b) a car <br />
c) a pair of shoes<br />
d) ingredients for cooking a meal<br />
e) a book to read on a long flight<br />
f) a torch battery<br />
g) a replacement cartridge for your inkjet printer<br />
<br />
How would your criteria for making a selection differ in each case?<br />
Which items would you feel appropriate to make "sight unseen" over the internet rather than experiencing the item in person?<br />
Suppose you were a very busy and affluent person and you had a "personal shopper" either actually to make a purchase for you  or at least make a shortlist of items for you to choose between; how would you instruct them in your selection criteria? <br />
If you start to appreciate what the differences in your approach may be in the various cases, you'll get some feeling of why different types of specification are appropriate in different scenarios.]]></description>
			<content:encoded><![CDATA[Hi all,<br />
I am struggling to find some information regarding the different types of specifications and when which type should be used. <br />
<br />
Please provide some guidance as where to find it.<br />
<br />
Thanks <br />
Aditi<br />
<br />
Not surprised; I can't immediately put my finger on one good source.  Sure there are several references but I'll need some time to get a selection together; also I think they'll be a need to derive what you need from a composite of sources as background reading rather than a ready written comparison.<br />
<br />
In the meantime to get you thinking on the right lines, I suggest you consider what you would do in your own life re a variety of possible purchases.  For each of the following categories, how would you decide between a range of items on sale when looking to purchase :<br />
a) a house <br />
b) a car <br />
c) a pair of shoes<br />
d) ingredients for cooking a meal<br />
e) a book to read on a long flight<br />
f) a torch battery<br />
g) a replacement cartridge for your inkjet printer<br />
<br />
How would your criteria for making a selection differ in each case?<br />
Which items would you feel appropriate to make "sight unseen" over the internet rather than experiencing the item in person?<br />
Suppose you were a very busy and affluent person and you had a "personal shopper" either actually to make a purchase for you  or at least make a shortlist of items for you to choose between; how would you instruct them in your selection criteria? <br />
If you start to appreciate what the differences in your approach may be in the various cases, you'll get some feeling of why different types of specification are appropriate in different scenarios.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Design life Cycle]]></title>
			<link>https://irse.signalpost.org/showthread.php?tid=106</link>
			<pubDate>Wed, 10 Sep 2008 13:29:17 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://irse.signalpost.org/member.php?action=profile&uid=109">KenD</a>]]></dc:creator>
			<guid isPermaLink="false">https://irse.signalpost.org/showthread.php?tid=106</guid>
			<description><![CDATA[There have been a number of questions in Mod 7 and some in Mod 1 about the design lifecycle. from concept to decommission and disposal. What I would like to now is where I can read up on the cycle particulaly the middle bit ensuring the design is effeciently maintained and modifying any elements due to improvments etc.]]></description>
			<content:encoded><![CDATA[There have been a number of questions in Mod 7 and some in Mod 1 about the design lifecycle. from concept to decommission and disposal. What I would like to now is where I can read up on the cycle particulaly the middle bit ensuring the design is effeciently maintained and modifying any elements due to improvments etc.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[RAMS]]></title>
			<link>https://irse.signalpost.org/showthread.php?tid=38</link>
			<pubDate>Sat, 05 Apr 2008 21:28:48 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://irse.signalpost.org/member.php?action=profile&uid=8">PJW</a>]]></dc:creator>
			<guid isPermaLink="false">https://irse.signalpost.org/showthread.php?tid=38</guid>
			<description><![CDATA[Many talk of RAMS but don't know the distinction between the terms- make sure you do.<br />
<br />
Also see <a href="http://www.irseexam.co.uk/showthread.php?tid=173&amp;pid=2799#pid2799" target="_blank" rel="noopener" class="mycode_url"> this module 5 thread </a>for information regarding Fault Trees which is at least as applicable to module 7 and closely related to this topic]]></description>
			<content:encoded><![CDATA[Many talk of RAMS but don't know the distinction between the terms- make sure you do.<br />
<br />
Also see <a href="http://www.irseexam.co.uk/showthread.php?tid=173&amp;pid=2799#pid2799" target="_blank" rel="noopener" class="mycode_url"> this module 5 thread </a>for information regarding Fault Trees which is at least as applicable to module 7 and closely related to this topic]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Railway System]]></title>
			<link>https://irse.signalpost.org/showthread.php?tid=37</link>
			<pubDate>Sat, 05 Apr 2008 21:26:42 +0000</pubDate>
			<dc:creator><![CDATA[<a href="https://irse.signalpost.org/member.php?action=profile&uid=8">PJW</a>]]></dc:creator>
			<guid isPermaLink="false">https://irse.signalpost.org/showthread.php?tid=37</guid>
			<description><![CDATA[Powerpoint 2003+ presentation]]></description>
			<content:encoded><![CDATA[Powerpoint 2003+ presentation]]></content:encoded>
		</item>
	</channel>
</rss>