Peregrine 4903
Established Member
Someone like @The Planner might be able to explain it better but I'll give it a shot.An interesting discussion going on here: could you please explain this particular point though because I'm baffled? Thank you!
Basically you have sectional running times (SRT's) and Theoretical Running Times (TRT's). Section Running Times are the time it takes for a Model Train to travel between two timing points. So for example model train of a class 375 has a 1 minute Sectional Running Times for a Stop to Pass between East Croydon and Windmill Bridge Junction. You get SRT's for Stop - Stop, meaning the train is stopping at both of the timing points, pass to pass meaning the train is passing through both of the timing points, pass - stop and stop - pass which means the train is stopping at one of the timing points bot not stopping at the other. SRT's have been got in theory by doing timing runs on the network travelling on that specific class of train, e.g. a class 375 and then collected and inputted into a system. Once they are in that system it allow Network Rail to publish the schedules into the Downstream systems such as TRUST, and basically allows the public to see them on booking wbebsite, departure boards, realtime trains and so forth.
The issue have is that for various timing loads particuallry freight ones, there often is no Sectional Running Time between two timing points as the train may be doing a move that that model of train doesn't usually do and means that no one has gone out onto the network and got an official SRT for it. This means that the train cannot be published by Network Rail into the downstream systems. This means if you want to publish the train, you have basically two option. You can either request an SRT for that particular move, but that can sometime take a long time to do and also if its for a freight train/engineering haulage train doing a one off move at a junction say that it is unlikely to do again anytime soon, your not going to be the top priority to get an SRT request.
The other option is to use Theoretical Running Times. This is when you use the Model Train SRT's of similar class of train that does say have an SRT for that move between the two timing points. That will get rid of the Data error and allow you to publish the train downstream. The issue is of course, is that it may take the class of train you are trying to run between the two timing points longer than the model train that is running your specific train, which can cause delays.
There is lots more to it, and I probably have't explained it very well, but that is sort of the basic explanation behind it.
Last edited: