TBTC Testing

I suspect that many of the ways they've saved money in the short term will cost much more in the long term. That's usually the way it goes anyway.

No, PPP was set up in such a way that the only people that the private partner had to care about were their shareholders. This is one of the many reasons why PPP failed.

Do other LU ATO lines have bi-directional capability?

So would it be a not-so-simple software upgrade or a quite-hard-at-the-lineside upgrade to get bi-di on the Jub?

Simon

Why is it an issue then?

Apparently the Jubilee line trains have developed a habit of repeating the onboard train announcements twice due to the Train Management System still working alongside the TBTC testing. Has anyone noticed this?

Source: londonreconnections.blogspot.com/2011/02/status-of-underground-upgrades.html

Yup, have also noticed at a few stations (namely Swiss Cottage) the trains would just say "this train terminates at Stratford" and not the name of the station.

I think it's getting embarrassing at how many delays and suspensions are happening on the Jubilee... There seem to be so many faulty trains and service suspensions (as I type this it is part suspended with severe delays elsewhere).

I don't think we were informed sufficiently at how early in development the new signaling system is... The passenger service shouldn't be used as a guinea pig... So many weekend closures just to have a worse service.

People might say that I'm short minded...

But when you consider all the closures which have happened, it seems like a bit more then 'bedding in' and 'teething problems' to have so many service suspensions and faulty trains. True the service recovers reasonably quickly when things are restored but still....

From what I know, it's the trains refusing to communicate with the TBTC servers.

Well severe delays might be being advertised but I just had an amazing run from Green Park to Canada Water. It managed it in 11 mins with absolutely no sign of slow running. I therefore think the comments about slow running previously must've occurred when there was a preceding train triggering the distance to go to keep it slow.

When it works (and to fair it hasn't disrupted me yet) this TBTC is awesome !

Suspended again on Tuesday due to axle-counter failure at St. John's Wood (Plus trains "not communicating" at the east end.) All this when the "Brit Awards" were going on at the O2.

Will this ever work, and wouldn't conventional driving with old-fashioned multi-home auto signals, plus the semis operated by signal boxes, have provided a more intensive and reliable service?

As with all these systems, especially when you can't test the system continuously for weeks without interruptions, problems (particularly software) takes weeks to resolve. Safety critical software requires a huge amount of testing, typically 2 to 3 months from finding a fix to implementing. As this has only been in full daily use for around 6 to 7 weeks, I am sure the issues found since switch on are already being fixed and tested off the railway and will soon been implemented to address issues being experienced.
I would imagine various tweaks and updates will be rolling off the Thales production line shortly.
I think we'll just have to grin and bear it a bit longer to get over these issues.

Its still better than the JLE was when that first opened with fixed block, and TBTC is also working better than it did on DLR when the same system was introduced in the 90's

Seeing another faulty train just now at London Bridge. Is it the same trains that are always having the TBTC comms issues or is it all of them? Curious if there are a few bad apples or if it's the whole fleet.

Team in the office here in Canary Wharf are all still speaking about Tuesday night. One of the issues seems to be a focus at the centre on operating the trains rather than serving the passengers, and not being able to understand the difference. I know you good people who run the stations understand this, but do the upper management?

There were big long gaps from Canary Wharf towards Stratford, quite a lot of people still around although mid-evening, after more than 10 minutes a train, very full, arrived now only going to North Greenwich. People waiting stepped politely back (aren't we nice) to let many get off, who now stood in front of those who had been waiting! Another 6 minutes or more before the next train to Stratford came in, this one was so packed that few could get in, and certainly none of those who had been waiting a long time.

Many more trains seemed to be going back into London than coming from there, and we wondered why some trains were only going to North Greenwich. There may be a belief that the trains are running so things are alright, but they are no use if when they turn up at infrequent intervals the people waiting cannot insert themselves into them.

In the end we went out of the Jubilee Station, walked across The Wharf, and got in our usual DLR, round to Poplar and eastwards. Now did we have our Oyster cards charged for going into the Underground but coming out again? I can't tell, because the new ticket machines put on the DLR a year or so ago, although they finally allowed Oysters to be topped up, can't tell you any history on your card. I wonder how we are meant to know, when the stations we use most days are fully automated DLR ones.