Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Route Control Tables 2004
#3
Here are the comments on the routes.

The surprise is that you used Merlin's suggested format, but he didn't! I do think that the format is a good one for the exam; becasue it is so compact however it does make it a bit of a squeeze for me to insert comments.

In general I think that you used the format very well.
One of the main drawbacks with the column format is that it is easy to run out of space, particularly if you later want to add stuff having started the next route. Suggest that you only put two or at most three routes per page and always leave space in all rows- just in case. However the proportions of the CT column width seems pretty good- although the "aspect shown" could be narrower and space used for "route locking tracks" or perhaps the "tracks clear" columns. The acid test will be when you actually handwrite on full size sheets

I have marked with a large red dot those things that I think you'll recognise as silly slips- if you don't then let me know.
For the other additional entries / deletions I have attempted to put a # ref and noted in the margin a summary; in some of these cases I think you may need more explanation so ask away as needed. In essence:
#1 GK/RT0044 can wait for now until the basics are secure.
#4 Comprehensive A/L is something that we'll tackle shortly; perhaps I need to revisit the Study Pack as both of you have difficulty in the same area.
#7 Look at Merlin's answer and ask if you need more info
#8 Overrun protection; again this can wait for now.
#9 Swinging overlaps; perhaps a subject after Comp A/L; it'll be good to get you able to do this but don't get hung up as you'll easily pass the exam without it!

So it may look a lot of red, but really this is certainly a "half decent" attempt; I suppose that the most important things to make sure that you see where you went wrong are:
a) the opposing route locking that you missed (but actually not too much of that)
b) foul tracks.

It'll probably be best for me to use Merlin's sheets for explaining the #4 and #9 just because there is more space; that is not however to say that you need to change from your CT format- if you leave enough space then it can be shown equally satisfactorily.

There was a little more space on your 2nd sheet to add comments directly.
a) Similar issues with last wheel replacement as Merlin.
b) You will need to be consistent between different standards- given that you are following RRI practice then there would almost certainly only be one A/L release timer per signal and thus for all classes of routes to all destinations would be set for the greatest of all time requirements. In SSi etc it is only data; in RRI it is hardware, space and money to provide and install!
c) I notice that you (and indded Merlin more so) have often missed out the odd track, usually where it is on a track cct over a point and you are considering a route that passes over that track but the name hasn't been placed on that portion. This is a common fault- you need to be a little more careful at looking at the extent of all TCs, not just track ID name spotting!
PJW
Reply


Messages In This Thread
Route Control Tables 2004 - by interesting_signal - 14-03-2010, 02:11 PM
RE: Route Control Tables 2004 - by PJW - 14-03-2010, 11:45 PM
RE: Route Control Tables 2004 - by PJW - 15-03-2010, 10:15 PM
RE: Route Control Tables 2004 - by PJW - 15-03-2010, 10:34 PM
RE: Route Control Tables 2004 - by PJW - 16-03-2010, 09:46 PM
RE: Route Control Tables 2004 - by greatnessjason - 05-09-2014, 04:35 AM
RE: Route Control Tables 2004 - by merlin89 - 16-03-2010, 11:45 PM
RE: Route Control Tables 2004 - by greensky52 - 09-09-2010, 12:50 PM
RE: Route Control Tables 2004 - by PJW - 09-09-2010, 10:39 PM
RE: Route Control Tables 2004 - by greensky52 - 11-09-2010, 01:37 PM
RE: Route Control Tables 2004 - by PJW - 11-09-2010, 02:36 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)