<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Aspect Sequence &#8211; Railway Signalling Concepts</title>
	<atom:link href="https://www.railwaysignallingconcepts.in/tag/aspect-sequence/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.railwaysignallingconcepts.in</link>
	<description>Information About Axle Counter,Track Structure Point &#38; Crossing,Cable Schematics,CBTC Equipment,Overlaps,Core Plans,Earthing,ERTMS,Headway Calculation,Hot Axle Box Detectors,Interface Design,Level Crossing,Markers &#38; boards,Bonding Plan Electrical Lockings,Route locking,Automatic Warning Systems AWS,Point Circuit,Equipment Treadle,Track Layout,Track Circuit Interrupters,Train Protection Warning System (TPWS),Slip Siding &#38; Catch Siding.</description>
	<lastBuildDate>Wed, 01 Jun 2022 08:00:09 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.0.11</generator>
	<item>
		<title>Railway Control Table</title>
		<link>https://www.railwaysignallingconcepts.in/railway-control-table/</link>
					<comments>https://www.railwaysignallingconcepts.in/railway-control-table/#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Wed, 01 Jun 2022 08:05:53 +0000</pubDate>
				<category><![CDATA[Indian Railway Signalling]]></category>
		<category><![CDATA[Thales]]></category>
		<category><![CDATA[Approach locking]]></category>
		<category><![CDATA[Aspect Sequence]]></category>
		<category><![CDATA[Automatic Warning system (AWS)]]></category>
		<category><![CDATA[Control Table Conventions]]></category>
		<category><![CDATA[Control Table For Signal/Routes]]></category>
		<category><![CDATA[Purpose of control table]]></category>
		<category><![CDATA[Railway Control Table]]></category>
		<category><![CDATA[SIGNAL CONTROL REQUIRES]]></category>
		<category><![CDATA[Signal Stick Circuit]]></category>
		<category><![CDATA[What is control table]]></category>
		<guid isPermaLink="false">http://www.railwaysignallingconcepts.in/?p=2267</guid>

					<description><![CDATA[Railway Control Table What is a control table? A control table is a formal tabulation of the signal, point, and other controls associated with an electrical or electronic signalling system, showing the interlocking and other dependencies between those controls. Safety is dependent on the readability of control tables and on their interpretation by competent persons. [&#8230;]]]></description>
										<content:encoded><![CDATA[<h1><span style="font-size: 14pt;"><b>Railway Control Table</b></span></h1>
<h3><span style="font-size: 14pt;"><strong>What is a control table?</strong></span></h3>
<p><span style="font-size: 14pt;">A control table is a formal tabulation of the signal, point, and other controls associated with an electrical or electronic signalling system, showing the interlocking and other dependencies between those controls.</span></p>
<ul>
<li><span style="font-size: 14pt;">Safety is dependent on the readability of control tables and on their interpretation by competent persons.</span></li>
<li><span style="font-size: 14pt;">The control table should always be read in conjunction with the scheme plan or signalling plan.</span></li>
<li><span style="font-size: 14pt;">Their production should use the information depicted on the scheme/signalling plan, together with the associated table of signal routes and aspect sequence chart.</span></li>
<li><span style="font-size: 14pt;">Other requirements may be obtained from OPS and associated documentation.</span></li>
<li><span style="font-size: 14pt;">The scheme plan shall be developed from the client remit and OPS or equivalent.</span></li>
</ul>
<h2><span style="font-size: 14pt;"><b>Railway Control Table &#8211; Purpose</b> <b>of</b> the <b>control</b> <b>table</b></span></h2>
<p><span style="font-size: 14pt;"><strong>1.</strong> Control table should fulfill the following purposes</span></p>
<p><span style="font-size: 14pt;"><strong>2.</strong> Submitting for HMRI statutory approval.</span></p>
<p><span style="font-size: 14pt;"><strong>3. </strong>Deriving information for signallers, such as signaller’s route cards.</span></p>
<p><span style="font-size: 14pt;"><strong>4. </strong>Production of engineering details, such as circuit diagram and data.</span></p>
<p><span style="font-size: 14pt;"><strong>5.</strong> Function and control table testing.</span></p>
<p>&nbsp;</p>
<h4><span style="font-size: 14pt;"><b>Railway Control Table Conventions</b></span></h4>
<ul>
<li><span style="font-size: 14pt;">It is essential that clear and consistent conventions are used for all Control Tables.</span></li>
<li><span style="font-size: 14pt;">Some of the Standard conventions which should be used within control tables are as follows</span></li>
</ul>
<p><span style="font-size: 14pt;"><strong>“$” References &#8211;</strong> These are a set of standard notes, which are defined in this Code of Practice. (RT/E/C/11202)</span></p>
<p><span style="font-size: 14pt;"><strong>“#” –</strong> These should be treated in the same fashion as dollar references but are specific to a particular Control table or set of tables.</span></p>
<p><span style="font-size: 14pt;">Any unusual controls required for a particular function not directly required by the layout of the scheme plan or by signalling standards should be explained on the control table using a # reference.</span></p>
<p><span style="font-size: 14pt;"><strong>Quotes “</strong>When defining alphanumeric route indicator characters, these should be shown in quotes. e.g.’ M’</span></p>
<p><span style="font-size: 14pt;"><strong>Plus “+”</strong> This should be used to denote two aspects or indications alight together, e.g. Y+G.</span></p>
<p><span style="font-size: 14pt;"><strong>Comma “,”</strong> Commas should be used to separate controls where their relationship is “and” e.g. AA, AB</span></p>
<p><span style="font-size: 14pt;"><strong>“or”</strong> The word “or” should be used to separate controls where their relationship is “one or the other or both”</span></p>
<p><span style="font-size: 14pt;"><strong>“N” and “R”</strong> To suffix point identifications to indicate their position where this is not stated in the column or box heading. E.g. 718R, 765N.</span></p>
<p><span style="font-size: 14pt;"><strong>“Nor” &#8211;</strong> This abbreviation should follow route numbers to indicate a route and its route locking and approach locking are normal where this is not stated in the column or box heading.</span></p>
<p><span style="font-size: 14pt;"><strong>“Occ” &#8211;</strong> This abbreviation should follow track circuit identifications to indicate that the track in question is occupied where this is not stated in the column or box heading. E.g. “AB occ”</span></p>
<p><span style="font-size: 14pt;"><strong>“Set”</strong> when following a route identification, should mean that a route is set e.g. [1B(M) after 9A(M)set]. A route will only cease to set when the route is normal.</span></p>
<h5><span style="font-size: 14pt;"><strong>Control Table Classifications </strong></span></h5>
<ol>
<li><span style="font-size: 14pt;">CONTROL TABLE FOR SIGNAL/ROUTES</span></li>
<li><span style="font-size: 14pt;">CONTROL TABLE FOR POINTS AND GROUND FRAMES.</span></li>
<li><span style="font-size: 14pt;">CONTROL TABLE FOR LEVEL CROSSING</span></li>
<li><span style="font-size: 14pt;">CONTROL TABLE FOR TPWS</span></li>
<li><span style="font-size: 14pt;">CONTROL TABLE FOR STAFF PROTECTION SYSTEMS (TOWS)</span></li>
<li><span style="font-size: 14pt;">CONTROL TABLE FOR BLOCK SYSTEMS &amp; ELECTRO-MECHANICAL.</span></li>
</ol>
<h5><span style="font-size: 14pt;"><b>Railway Control Table For Signal/Routes</b></span></h5>
<ol>
<li><span style="font-size: 14pt;">This section relates to route selection and routes releasing</span></li>
<li><span style="font-size: 14pt;">Route Requires:</span></li>
</ol>
<h6><span style="font-size: 14pt;"><strong>Points set or Free</strong></span></h6>
<h6><span style="font-size: 14pt;"><strong>All points serially from the signal</strong></span></h6>
<p><span style="font-size: 14pt;"><strong>i.</strong> Overlap points</span></p>
<p><span style="font-size: 14pt;"><strong>ii.</strong> Flank points</span></p>
<p><span style="font-size: 14pt;"><strong>iii.</strong> Soft call points</span></p>
<p><span style="font-size: 14pt;">These should be written in a separate line</span></p>
<h6><span style="font-size: 14pt;"><strong>Track circuit</strong></span></h6>
<ul>
<li><span style="font-size: 14pt;">Platform Track Circuit clear (Main) or occ for (Call-on) routes only in case of Call on associated with the main signal.</span></li>
</ul>
<h6><span style="font-size: 14pt;"><strong>Route disable control provided</strong></span></h6>
<ul>
<li><span style="font-size: 14pt;">This box should contain either YES or NO</span></li>
</ul>
<h6><span style="font-size: 14pt;"><strong>Route and sectional Route locking normal</strong></span></h6>
<ol>
<li><span style="font-size: 14pt;">Conflicting Routes in ascending order.</span></li>
<li><span style="font-size: 14pt;">All Routes starting from the same signal which is not prevented from being set by differing point conditions.</span></li>
</ol>
<ol>
<li><span style="font-size: 14pt;">If the routes are of the same signal, then the order is M, W, C, S</span></li>
<li><span style="font-size: 14pt;">Routes for pre-set shunt signal within this route which are not prevented from being set by differing point condition.</span></li>
<li><span style="font-size: 14pt;">All routes from back-to-back signals.</span></li>
<li><span style="font-size: 14pt;">All directly opposing routes.</span></li>
<li><span style="font-size: 14pt;">All indirectly opposing routes. (routes which may be initially locked out by points, but become directly opposing as a train transverses the opposing route and releases the sectional route locking behind it)</span></li>
</ol>
<ol>
<li><span style="font-size: 14pt;">Sectional route locking released by Track circuit clear:</span></li>
</ol>
<p><span style="font-size: 14pt;">These columns should be used to specify the conditions for releasing the controls applied under “Route and sectional Route Locking Normal” when the routes are normal.</span></p>
<p><span style="font-size: 14pt;">Or Occupied …For Time $46</span></p>
<p><span style="font-size: 14pt;">This should show the control required to release the sectional route/overlap locking when the train on the set route has been brought to a stand at the exit signal or other appropriate place, as indicated by track occupation for a specified time period.</span></p>
<p><span style="font-size: 14pt;">Special Controls/Remarks:  This should contain any other control required for route selection. like</span></p>
<p><span style="font-size: 14pt;">$2, $3, $4, $17, $21 etc.,</span></p>
<p><span style="font-size: 14pt;">SGRC (Signal Group Replacement Control)</span></p>
<p><span style="font-size: 14pt;">Lockout Normal</span></p>
<p><span style="font-size: 14pt;">Bi-directional Controls</span></p>
<p><span style="font-size: 14pt;">Dead two Reds Rule etc.</span></p>
<h6><span style="font-size: 14pt;"><b>SIGNAL CONTROL REQUIRES</b> </span></h6>
<p><span style="font-size: 14pt;">This section should define the controls required by the signal aspect. It implies that the route is set.</span></p>
<p><span style="font-size: 14pt;"><strong>a)</strong> Point Set, Locked, and Detected.</span></p>
<p><span style="font-size: 14pt;"><strong>i.</strong> Route Points</span></p>
<p><span style="font-size: 14pt;"><strong>ii.</strong> Overlap Points</span></p>
<p><span style="font-size: 14pt;"><strong>iii.</strong> Flank points</span></p>
<p><span style="font-size: 14pt;">    Supplementary detectors on points shall be shown</span></p>
<p><span style="font-size: 14pt;">    Special Controls of the points on signals to be shown</span></p>
<p><span style="font-size: 14pt;"><strong>b) Point Set and Detected N or R.</strong></span></p>
<ol>
<li><span style="font-size: 14pt;">Overlap swing points</span></li>
</ol>
<p><span style="font-size: 14pt;"><strong>c) Track Circuit clear</strong></span></p>
<ul>
<li><span style="font-size: 14pt;">All the track circuits shown in this box are required to clear before the signal can clear. Track circuit should be listed in a logical format, e.g. line of route, overlap, foul, and flank protection track circuits.</span></li>
</ul>
<p><span style="font-size: 14pt;"><strong>d) Track Circuits Occupied</strong></span></p>
<ul>
<li><span style="font-size: 14pt;">This should list the track circuits that are required to be occupied. Where required, the minimum time the track must be occupied should also be stated. The temporary approach control track should be listed here. ($7)</span></li>
</ul>
<p><span style="font-size: 14pt;"><strong>e) Signal Alight</strong></span></p>
<ul>
<li><span style="font-size: 14pt;">This should show the exit signal, the limit of shunt signal, Banner repeating signal, etc. which is required to be proved alight as required. An entry qualified by $50 indicates that this proving also includes TPWS operating correctly when the signal is on.</span></li>
</ul>
<p><span style="font-size: 14pt;"><strong>f) Track Circuit Occupied for $40 to Inhibit Replacement</strong></span></p>
<p><span style="font-size: 14pt;">Where last wheel replacement has been provided, the first track circuit and berth track circuit should be listed in this column. </span></p>
<p><span style="font-size: 14pt;"><strong>g)</strong> Aspect Disable Control/Link Provided This should contain either YES or NO according to whether the control/link is provided.</span></p>
<p><span style="font-size: 14pt;"><strong>h)</strong> Stick control applied when Signal Off and Track Circuit Occupied ($40) This should show the track circuits used to apply the signal stick control. Normally this should be the berth track &amp; first track circuit past the signal.</span></p>
<p><span style="font-size: 14pt;"><strong>i)</strong> Automatic Working facility provided This should contain either YES or NO.</span></p>
<h2><span style="font-size: 14pt;"><strong>Signal Stick Circuit</strong></span></h2>
<p><span style="font-size: 14pt;"><a href="http://www.railwaysignallingconcepts.in/wp-content/uploads/2019/04/Signal-Stick-Circuit.jpg"><img loading="lazy" class="aligncenter wp-image-2269" src="http://www.railwaysignallingconcepts.in/wp-content/uploads/2019/04/Signal-Stick-Circuit-300x190.jpg" alt="Railway Control Table" width="561" height="355" srcset="https://www.railwaysignallingconcepts.in/wp-content/uploads/2019/04/Signal-Stick-Circuit-300x190.jpg 300w, https://www.railwaysignallingconcepts.in/wp-content/uploads/2019/04/Signal-Stick-Circuit.jpg 539w" sizes="(max-width: 561px) 100vw, 561px" /></a></span></p>
<p><span style="font-size: 14pt;"><strong>j)</strong> Special Controls/Remarks This should contain any other controls required for the signal aspect which is not covered above.</span></p>
<p><span style="font-size: 14pt;">i.Lockout Normal</span></p>
<p><span style="font-size: 14pt;">ii. Preset Shunt Off</span></p>
<p><span style="font-size: 14pt;">iii.TPWS special control</span></p>
<p><span style="font-size: 14pt;">iv.2 Reds Rule</span></p>
<p><span style="font-size: 14pt;">v.Any other aspect level control</span></p>
<p><span style="font-size: 14pt;"><b>Aspect Sequence</b></span></p>
<ul>
<li><span style="font-size: 14pt;">This section shows the aspect displayed by the route entry signal, once the “ SIGNAL CONTROLS REQUIRE” conditions are satisfied.</span></li>
<li><span style="font-size: 14pt;"><strong>Route Indication Alight</strong></span></li>
</ul>
<p><span style="font-size: 14pt;">The type-and position/character of the route indication to be displayed, which must be proved alight before the signal can display a proceed aspect.</span></p>
<ul>
<li><span style="font-size: 14pt;"><strong>Aspect to be shown</strong></span></li>
</ul>
<p><span style="font-size: 14pt;">If the signal displays a position light aspect for this route, PL should be shown in the first line of this box.</span></p>
<p><span style="font-size: 14pt;">All aspects that this signal will display for this route should be shown in this box alongside the aspects which are required to be shown at the next main signal.</span></p>
<ul>
<li><span style="font-size: 14pt;"><strong>Next Main Signal:</strong></span></li>
</ul>
<p><span style="font-size: 14pt;">The number of the next main signal should be shown in the space provided.  If the aspect to be displayed for this route is a position light, the number should be replaced with a dash.</span></p>
<ul>
<li><span style="font-size: 14pt;"><strong>Route Set (under Next Main Signal)</strong></span></li>
</ul>
<p><span style="font-size: 14pt;">This is only used to show flashing yellow. The identification of the route set from the exit signal, which is required to be set, should be listed here.</span></p>
<ul>
<li><span style="font-size: 14pt;"><strong>Banner aspect (under Next Main Signal)</strong></span></li>
</ul>
<p><span style="font-size: 14pt;">This should contain the word “OFF”, relating to the aspect of the exit signal’s banner repeating signal (if provided) when the banner is required to be proved in the OFF position</span></p>
<ul>
<li><span style="font-size: 14pt;"><strong>Track Circuit Occupied:</strong></span></li>
</ul>
<p><span style="font-size: 14pt;">This should list the track circuits required for approach control from yellow, used for free yellow, or approach control from yellow with flashing yellow aspect in the rear.</span></p>
<p><span style="font-size: 14pt;"><b>Automatic Warning System (AWS</b>)</span></p>
<ul>
<li><span style="font-size: 14pt;"><strong>Permanent Magnet</strong></span></li>
</ul>
<p><span style="font-size: 14pt;">This should contain Yes, No, or Suppressed</span></p>
<ul>
<li><span style="font-size: 14pt;"><strong>Electro-Inductor</strong></span></li>
</ul>
<p><span style="font-size: 14pt;">This should contain Yes or No</span></p>
<p><span style="font-size: 14pt;"><b>Approach Locking</b></span></p>
<ul>
<li><span style="font-size: 14pt;"><strong>Approach Locking applied</strong></span></li>
</ul>
<p><span style="font-size: 14pt;">If approach locking is provided on clearance of the signal including the cases where the signal is approaching controlled from red this box should contain the words “When Cleared”.</span></p>
<ul>
<li><span style="font-size: 14pt;">Where Comprehensive approach locking is provided, this box should contain a list of all track circuits in the rear as for as the sighting points of the signal furthest in the rear, to show the change of aspect if the route entrance signal is replaced to danger.</span></li>
</ul>
<ul>
<li><span style="font-size: 14pt;"><strong>Signal ON &amp; Free of Approach Locking</strong></span></li>
</ul>
<p><span style="font-size: 14pt;">If comprehensive approach locking is provided &amp; if some of the track circuits listed in the previous column can be “conditioned out” when other signals are ON &amp; Free of Approach Locking, the relevant signal numbers should be shown in this column.</span></p>
<ul>
<li><span style="font-size: 14pt;"><strong>Approach locking released by</strong></span></li>
</ul>
<p><span style="font-size: 14pt;">Track circuit controls required for the release of approach locking.</span></p>
<p><span style="font-size: 14pt;">(1st TC clear, 2nd TC occ)</span></p>
<p><span style="font-size: 14pt;"> after (1st TC occ, 2nd TC occ)</span></p>
<ul>
<li><span style="font-size: 14pt;"><strong>Special Controls / Remarks</strong></span></li>
</ul>
<p><span style="font-size: 14pt;">This should contain any special control or notes relating to approach locking controls.</span></p>
<ul>
<li><span style="font-size: 14pt;"><strong>TORR requires Approach locking free &amp; tracks</strong></span></li>
</ul>
<p><span style="font-size: 14pt;">This should list any track circuits which are required to be proved clear or occupied in order for the TORR to operate.</span></p>
<p><span style="font-size: 14pt;">  (BTC clear, 1ST  TC occ)</span></p>
<p><span style="font-size: 14pt;">   after (BTC occ, 1ST clear)</span></p>
<p><span style="font-size: 14pt;">   If BTC cannot be proved clear then second and third are used.</span></p>
<ul>
<li><span style="font-size: 14pt;"><strong>TPWS Fitted</strong></span></li>
</ul>
<p><span style="font-size: 14pt;">This should contain Yes, No, or Special</span></p>
<ul>
<li><span style="font-size: 14pt;"><strong>TPWS Indicated</strong></span></li>
</ul>
<p><span style="font-size: 14pt;">This should contain to specify the method of failure reporting of TPWS installations at the signal.</span></p>
<p>&nbsp;</p>
<p><a href="http://railsigintl.com/Control%20Tables/">Selection table in railways</a><br />
<a href="https://ieeexplore.ieee.org/iel7/6979/4358928/09099447.pdf">What is a route control chart</a><br />
<a href="https://en.wikipedia.org/wiki/Control_table">Signalling control tables</a><br />
<a href="https://asq.org/quality-resources/control-chart">Point control table</a><br />
<a href="https://en.wikipedia.org/wiki/Railway_signalling#:~:text=Railway%20signalling%20is%20a%20system,them%20uniquely%20susceptible%20to%20collision.">Basic concept of railway signalling</a></p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.railwaysignallingconcepts.in/railway-control-table/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Page Caching using Disk: Enhanced 
Minified using Disk

Served from: www.railwaysignallingconcepts.in @ 2026-08-01 14:36:21 by W3 Total Cache
-->