Go North East: Service Suggestions v2
Go North East: Service Suggestions v2
(12 Dec 2016, 9:01 am)Andreos1 Part of the problem with the OK1, was its lack of connections with GNE customers and the existing network. Buzzfare passengers are at a minimum in that part of the world and there's very few reasons why someone would have been exclusively loyal to the OK1, over the larger network of ANE services that could have been used
That's why this proposed X22 would connect and shadow the existing network. It wouldnt be a standalone, isolated service across vast tracts of its route, like the OK1 was.
I maybe should have been clearer with regard the interworking patterns too.
As an example:
X21 - X22 - X21
X9 - X22 - X10
X10 - X22 - X9.
Obviously not all of the boards would interwork with the X22 either. The frequency on the X22 would be ridiculous otherwise.
Obviously layover and the actually timetable would be an important factor. Whilst this undoubtably creates a bigger PVR, on some routes, its the only way it can work. Just look at the 20 - services often run in pairs on common sections of route, but the layover at Shields enables one to leave there on its next run, on time. However when it comes to the 21, it doesnt get that freedom (Saturday saw them running in 4's well in to the evening southbound and still in pairs towards 9pm).
Just as an example of the suggestions (timings on a clock face timetable in this case).
Board 1:
Arrives Mbro 0900 on X9.
Departs Mbro 0915 on X22.
Arrives Bishop 1015 on X22.
Departs Bishop 1030 on X22.
Arrives Boro 1130 on X22.
Departs Boro at 1145 on X10.
Board 2:
Arrives Bishop 0945 on X21.
Departs Bishop 1000 on X22.
Arrives Mbro 1100 on X22.
Departs Mbro 1115 on X22.
Arrives Bishop 1215 on X22.
Departs Bishop 1230 on X21.
Whilst that's just an example and doesn't represent actually journey times, it shows how the services can interwork and offer a layover at the same time.
(12 Dec 2016, 9:01 am)Andreos1 Part of the problem with the OK1, was its lack of connections with GNE customers and the existing network. Buzzfare passengers are at a minimum in that part of the world and there's very few reasons why someone would have been exclusively loyal to the OK1, over the larger network of ANE services that could have been used
That's why this proposed X22 would connect and shadow the existing network. It wouldnt be a standalone, isolated service across vast tracts of its route, like the OK1 was.
I maybe should have been clearer with regard the interworking patterns too.
As an example:
X21 - X22 - X21
X9 - X22 - X10
X10 - X22 - X9.
Obviously not all of the boards would interwork with the X22 either. The frequency on the X22 would be ridiculous otherwise.
Obviously layover and the actually timetable would be an important factor. Whilst this undoubtably creates a bigger PVR, on some routes, its the only way it can work. Just look at the 20 - services often run in pairs on common sections of route, but the layover at Shields enables one to leave there on its next run, on time. However when it comes to the 21, it doesnt get that freedom (Saturday saw them running in 4's well in to the evening southbound and still in pairs towards 9pm).
Just as an example of the suggestions (timings on a clock face timetable in this case).
Board 1:
Arrives Mbro 0900 on X9.
Departs Mbro 0915 on X22.
Arrives Bishop 1015 on X22.
Departs Bishop 1030 on X22.
Arrives Boro 1130 on X22.
Departs Boro at 1145 on X10.
Board 2:
Arrives Bishop 0945 on X21.
Departs Bishop 1000 on X22.
Arrives Mbro 1100 on X22.
Departs Mbro 1115 on X22.
Arrives Bishop 1215 on X22.
Departs Bishop 1230 on X21.
Whilst that's just an example and doesn't represent actually journey times, it shows how the services can interwork and offer a layover at the same time.
