Not necessarily, the 701s include a couple of dual voltage variants for initial type approval purposes, (just as the 707s did), the rest will be fitted “for but not with” dual voltage capability.
701s are effectively dual voltage with the pantograph equipment removed, some of the 710 are also dual voltage.
And some are DC-only are they not?
Not quite; the 710/1s are AC-only, while the 710/2s and 710/3s are dual-voltage. The 345s, 720s and 730s are all AC-only.
Ah yes, you're right.
Rewriting software from scratch is significantly more expensive, time consuming and risky than adapting and extending existing software.
The Belgium/Dutch gave up on Ansaldo Breda V250 so its possible but more than likely the rolling stock owners will take all the compensation due under the contract and SWR will just plod along with it as they have no urgency to change the stock and are saving the govt expensive leasing charges.
The difference there was that they had big mechanical/structural issues.
Indeed the Aventra is sound mechanically and electrically and i said this is a waiting game with the only loser being Alstom if they didn't factor in the costs for dealing with the issues and compensation to Rock rail who are the owners when they bough Bombardier Rail. SWR leasing bill has been kept down over the last 12 months so Dept of Transport have had to find less to keep it running. The passengers that are about aren't in overcrowded trains currently so not really missing the benefits of the air con.
Agreed except on the last point. A hot train is a hot train, whether it's crowded or not!
Indeed its fair to say ventilation on the York build EMUs wasn't the best and i was fortunate that on my regular commute we we went from slam doors to Electrostars so only had to suffer them occasionally which was especially bad on stock stabled all day and bought out for a peak duty.
Yes, but still unpleasant. I was on a 458 during the recent very brief hot spell. It was a quiet train, but the aircon had failed and all the windows were open. It was very unpleasant.
Not rewriting from scratch forces you to be burdened with years of technical debt. It has to be done sooner or later for each component of your software. We tend to call them major revisions, of which Linux has had several. Don't forget MITRAC has been around for more than 20 years.
Tech debt has a clue in the name though
It tends to impact those writing the software, rather than those using it (until it slows down delivery - at which point you have some spikes to deal with the tech debt).In the agile world it's just another iteration
Our agile iterations are rarely breaking changes. We have specific mitigations to avoid them at all costs. In the past year we only had one!Tech debt has a clue in the name though
Point remains that tech debt can be known and quantified - in the backlog. Whereas, new software is completely unknown.
In the agile world it's just another iteration
I think it is not to be taken literally. More implies occasional trips to Basingstoke/Haslemere probably first/last thing or weekends depending on diagramming.
To be fair, they'll probably last a lot longer than the pigs would have.!And we on the Pompey direct will gladly accept the hand-me-downs…as long as they have 2x2 seating
Yes, we had a quick discussion of that map/diagram last June, the consensus was it‘s definitely not representative of likely real life services:
www.railforums.co.uk
Funnily enough I managed to get a shot on a train back - not the best visibility-wise but it's pretty summery View attachment DSC01867.jpg
www.realtimetrains.co.uk
