Quote:
Originally Posted by aberdeen5698
If they were really unable to do that then the entire Expo and Millenium lines would have been shut down far more frequently and extensively than they have been when switches stopped working or there were communications or other issues at a particular station or track area. All they have to do is declare a portion of the track "out of service" and "short turn" the trains at Burquitlam.
|
The difference between an operational line and a non-operational line, is that the non-operational line isn't providing feedback on it's state. You're not going to put in a bunch of patches to "ignore this track segment state, ignore this station state, ignore manually driven vehicles between X and Y switches" only to have to remove them later at an additional cost. Every rail system is build-to-order, not off-the-shelf parts and software, so someone needs to be paid to change the software, someone needs to be paid to QA the software.
If Thales already installed the computer systems and they're ready to go, they can probably flag everything beyond Burquitlam as not-in-service, and the existing trains won't try to fly past it under computer control. But if they can't put the Evergreen line VCC into service without the line being complete, then Burquitlam can only be reached under manual control.
Like my argument is less about trying to shoot down Queetz's obsession with seeing Burqitlam opening early, and more about Translink wanting to control the message when people start asking why Burquitlam remains closed even though they see trains going to it. Ever wonder why it takes months to test trains and not days?