Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
2009 CTs, to IRSE CT format
#8
(29-08-2011, 08:31 PM)Peter Wrote:
(29-08-2011, 12:21 PM)SARVESH KUMAR Wrote: Respected PJW/Peter sir,

please check my route control table and commented

with regards
sarvesh kumar

OK. You have got several points right that you struggled with before - Aspect sequence is better (although indication missed for the call on and for the main, you have got your lines out of place so it appears that you have 365 ay R when 403 at Y etc!), the presentation of the route locking release is better.

You have put different release conditions for the approach locking of the different classes. Not sure whether this was deliberate. Some practices use first and second track rather than berth and first, but you should be consistent.

Significant points to look at.

You have tried to show the point conditions for the swinging overlap in the "points detected or free to go" col. They should not be shown here.

237 would be needed N for flank protection.

242 is not part of the route for the call on.

You have omitted several of the conflicting routes 378, 374 and 376 all have routes up to 366 which have conflicts which are not resolved by point lie (albeit only by the last track (CE) but they must be shown). You have included 371A(S) which, as discussed before, is a route in the same direction and so should not appear.
416, 412 and 414 should all be there.
More subtle - you have included 408A(S), but from the tracks in the release, you have identified that the overlap goes via 238N which means that the conflict is resolved by the lie of the points.
Another subtle point is 418C(S). It conflicts with the overlap for 365A(M).
You got the line for 382A(S) and its release correct.

Showing 242 in the N or R column is correct for the main and you have correctly not shown swinging O/L for the warner.
You have shown 243 called, locked and detected N. 243 is only required thus w 242R, and 245 w 242N. Similarly the entry in the R column for 246 and 248 should have the other point positions which must be there for this to be required.

There are several confusing bits in your "tracks" section for the aspect (col 12). You have AK w 202N and then AK w 202R. First, take care, I think you mean 242 - avoid silly writing errors. Second, think! You are requiring AK whatever the position of the points. Therefore, AK with no conditions listed is what is required. The way you have then written BP and BN means that they are there without condition, whereas these are only relevant with 242R. Use brackets to group together the conditions that apply together eg in your case:
.....AJ, AK, [(AL, AN)w 242N], [BP, BN, BL, (DHw246R)w 242R].

The tracks occupied section (col 13) us for the tracks that are needed occupied to release the aspect. Not sure why you have put the platform tracks in there. There is nothing required for the main and both the W and C will be approach released, likely to be CB. The route level for the call on will require that one of the platform tracks is occupied. This format of table does not make provision for this, so I suggest using the special controls column to record this.

I hope this is helpful. Please let me know if you have any questions.

Peter

Thanks sir for help and above obsevation understood than attached the other route control table

with regards
sarvesh kumar
Reply


Messages In This Thread
2009 CTs, to IRSE CT format - by SARVESH KUMAR - 26-08-2011, 01:31 PM
RE: 2010 CTs, points 137 & 148 - by Peter - 26-08-2011, 10:13 PM
RE: 2010 CTs, points 137 & 148 - by SARVESH KUMAR - 27-08-2011, 06:42 AM
2009 CT to new format - by SARVESH KUMAR - 27-08-2011, 07:25 AM
RE: 2009 CT to new format - by PJW - 27-08-2011, 03:37 PM
RE: 2009 CT to new format - by SARVESH KUMAR - 29-08-2011, 12:21 PM
RE: 2009 CT to new format - by Peter - 29-08-2011, 08:31 PM
RE: 2009 CT to new format - by SARVESH KUMAR - 30-08-2011, 01:39 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)