kevin_roche
Member
- Joined
- 26 Feb 2019
- Messages
- 930
The minutes of the November Crossrail Sponsor Board are also on the TfL web site: http://content.tfl.gov.uk/sponsor-board-minutes-part-b-15-november-2019.pdf
They confirm some of the things we have discussed above about 345s on services to Heathrow and the possibility that 9-car trains will be used from April:
On Software there is again no clear separation between that for the train and that for the signalling infrastructure:
It looks (from other posts above) as if the transition testing between CBTC and TPWS and between TPWS and ETCS is well underway. I am keeping my fingers crossed that P_D+11 continues to prove usable for services to Reading and later to Heathrow. If not, waiting for the delivery of P_D+12 will likely be at least 3 months away.
They confirm some of the things we have discussed above about 345s on services to Heathrow and the possibility that 9-car trains will be used from April:
Sponsors questioned CRL on the plans to put the 9-car trains in service. CRL stated that this was predicated on addressing two technical issues before being approved by MTR’s Safety Validation Panel for service. CRL estimated the swapping out of the 7-car train with 9 car trains by early Spring 2020. CRL updated that they were expecting to commence driver training with a 9-car at Heathrow from December 2019. Once a functioning train was approved for passenger service, it is likely to operate on services to Reading as part of a phased introduction, before being deployed to operated to Heathrow.
On Software there is again no clear separation between that for the train and that for the signalling infrastructure:
Rolling Stock and Signalling Software
CRL highlighted that although train software development is on the critical path, progress is being made with release of the next version (P_D+11), due in December 2019. Sponsors challenged CRL on whether P_D+11 would be adequate to commence Trial Running. CRL stated that a view would need to be taken on the functionality and reliability of the software but that P_D+11 could be suitable for building reliability and that P_D+12 would build on functionality necessary to enter [Trial] Running. Sponsors requested an update on the P_D+11 software development and the requirement for version P_D+12 for Trial Running [redacted] to provide a collective focus on a date. Sponsors asked CRL to provide an update on a realistic target date for Trial Running once they had completed their due diligence.
It looks (from other posts above) as if the transition testing between CBTC and TPWS and between TPWS and ETCS is well underway. I am keeping my fingers crossed that P_D+11 continues to prove usable for services to Reading and later to Heathrow. If not, waiting for the delivery of P_D+12 will likely be at least 3 months away.
Last edited: