kEiThZ
Superstar
^ VIA has said service would be maintained on the existing line. "Trade" implies it would disappear.
I'm referring to places like Perth along the HFR route.
^ VIA has said service would be maintained on the existing line. "Trade" implies it would disappear.
Would there not be an opportunity to do an express version. Ie. Toronto -> Peterborough -> Ottawa -> Montreal for example to cut those times down and try to win some of the business class from the airlines. While also having a more commuter based train that goes to the hamlets. Almost like Amtrak does with an Acela express that goes to limited stations and is business oriented and then a more regional rail approach. I'm sure that would likely involve more tracking (passing tracks) and what not.
There's not even a shovel in the ground and we're already down to single track. Multiple services is not possible.
^ VIA has said service would be maintained on the existing line. "Trade" implies it would disappear.
I am far more worried about what the prevailing top speed will be. The nominal figure is 177 km/hr, but if that is only reached in spots with many slowdowns for curves etc, the end to end trip times will be less attractive even if no stops are made. Can’t wait until some of that detailed design reaches the public domain.
Thats why im adamant they need to purchase the same cars as being used on the Acela corridor, as they tilt further than any other trainset and can increase speeds around curves up to 20%.
Also, as per @Urban Sky this whole thing is being designed for as little capital as practical. So the kind of opportunity investment that most of us here are hoping for is probably not happening.
Which is probably the most practical approach if you want to see any of this built in the near future. Having worked several large scale provincial and federal procurement bidding processes (not in transit, but in IT infrastructure), it's always prudent for the bidders to go in with an offer on the lower end of the spectrum to get in the door. Once the project is started, it's far easier to include add-ons via change orders (since you are bypassing the usual procurement process).
Which is probably the most practical approach if you want to see any of this built in the near future. Having worked several large scale provincial and federal procurement bidding processes (not in transit, but in IT infrastructure), it's always prudent for the bidders to go in with an offer on the lower end of the spectrum to get in the door. Once the project is started, it's far easier to include add-ons via change orders (since you are bypassing the usual procurement process).
Ideally, the add-ons would get approved by a parliament vote before construction starts. Drawing from experience from back home in Germany and elsewhere, many of these add-ons are required by local politicians and communities, not the projects’ promoters. Therefore, I wonder what the objection is if the promoters present the minimum project scope which achieves the desired operational and commercial benefits and negotiate their share of these minimal construction costs before politicians add all the noise protection measures into their shopping carts.In other words, cost overruns, which means more money from taxpayers, which means one more thing the public will be pissed off about.
In my limited experience as a provincial civil servant, the government is a horrible IT consumer. Often, overruns are necessary simply to get the original project to work in the first place because they didn't properly articulate what it wanted or understand their own environment and/or didn't fully understand what they were buying. When what they wanted isn't delivered by what they bought they will pay more to get there because the alternative - legal action - is lengthy and bad karma, and the vendors know this.