CIS interface between operators

[whole diary]

[JayMac]

I was at Cheltenham earlier today (Sat 01/09/2012) and the FGW^▸ (First Great Western) operated CIS^▸ (Customer Information System) was struggling to cope with the delays to southbound CrossCountry services caused by a signal failure in the Longbridge/Barnt Green area.

Speaking with the staff on the ground, I learnt that FGW's CIS only picks up CrossCountry services in the Abbots Wood Junction area (the point where the Birmingham to Bristol line is joined by the line from Worcester).

Consequently, XC^▸ (Cross Country Trains (franchise)) services were only showing as 'Delayed' on the screens at Cheltenham until they were picked up by FGW's CIS at Abbots Wood.

Is it beyond the wit of man for a FGW human to liaise with CrossCountry and Network Rail to ensure that the CIS is updated with the expected arrival times, rather than just displaying the totally useless 'Delayed'?

Another consequence of having services shown as 'Delayed' is that they appear out of sequence on the rolling displays. Once a service passes the Abbots Wood timing point it shows up with an 'Expected' arrival, but the 'Delayed' services are still prioritised based on their timetabled arrival. So you get....

1st: 1252 Paignton. Delayed
2nd: 1225 Bristol TM^▸ (Train Manager, or possibly Ticket Machine, depending on context). Expected 1253

... and the Bristol TM train, not surprisingly, is the one that rolls in Cheltenham first. Which, if you're not clued up can cause unnecessary confusion.

[Louis94]

Is it beyond the wit of man for a FGW^▸ (First Great Western) human to liaise with CrossCountry and Network Rail to ensure that the CIS^▸ (Customer Information System) is updated with the expected arrival times, rather than just displaying the totally useless 'Delayed'?

Nothing to do with Network Rail, Its FGWs CIS system so its down to them to liaise with XC^▸ (Cross Country Trains (franchise)) to get the information, which really they don't need to do - a simple look up on Trust will sort this.

The only issue with adding a manual delay is that the system will not change it if it does get further delayed, even after it does pass Abbotswood Junction, it will have to be manually changed again - something I think FGW CIS might not have time to do all the time.

Slightly off topic - but was the PA^▸ (Public Address (broadcast loudspeaker announcements) or Passenger Assist (railway staff providing physical assistance to passengers with mobility issues), depending on context) reflecting what the screens showed? Also was it announcing on the correct platforms, last time I was there P1 trains were announced on P2 and vice versa!

[JayMac]

The automated PA^▸ (Public Address (broadcast loudspeaker announcements) or Passenger Assist (railway staff providing physical assistance to passengers with mobility issues), depending on context) was noticeable by it's absence. Manual announcements were being made, but the bloke at Cheltenham doing them was only referring to the information about services once they passed the Abbotswood* Junction timing point.


*Apologies. On consulting my rail atlas, I note it is one word.