1 / 31

Communications-Based Train Control Conference London, 2014

Communications-Based Train Control Conference London, 2014. A Recipe for Success in Implementing CBTC on an Operating Transit System Presented by: Dr. Alan F. Rumsey, P.Eng , FIRSE March 12, 2014. Why implement CBTC on an Operating Transit System?. CBTC Enabling Technology. Line Upgrade.

gerry
Download Presentation

Communications-Based Train Control Conference London, 2014

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Communications-Based Train Control Conference London, 2014 A Recipe for Success in Implementing CBTC on an Operating Transit System Presented by: Dr. Alan F. Rumsey, P.Eng, FIRSE March 12, 2014

  2. Why implement CBTC on an Operating Transit System? • CBTC Enabling Technology • Line Upgrade • Step-change Increase in Operational Performance • Control Centre Modernization • Infrastructure / Systems Upgrades • New Vehicles • Upgrade Signalling and Train Control Systems

  3. Recipe for Success ….. How do we define “Success” for a CBTC upgrade project …..

  4. Success ….. Success is: Deliver anticipated benefits (scope) on schedule and within budget …..

  5. Success ….. • Minimum Service Impacts Success is: Deliver anticipated benefits (scope) on schedule and within budget ….. … with minimum service impacts

  6. Success ….. • Service- Proven Product • Minimum Service Impacts Success is: Deliver anticipated benefits (scope) on schedule and within budget ….. … with minimum service impacts … and service proven product

  7. Standard “V-Curve” System Requirements System Integration & Acceptance Verification and Validation Construction and Integration Planning and Design Sub-System Requirements Construct / Inspect/Test Design Fabrication

  8. Real-World “V-Curve” • Service- Proven Product System Requirements System Integration & Acceptance Verification and Validation Construction and Integration Planning and Design Sub-System Requirements Construct / Inspect/Test Design Fabrication

  9. Real-World “V-Curve” • Service- Proven Product System Requirements System Integration & Acceptance Verification and Validation Construction and Integration Planning and Design Sub-System Requirements Construct / Inspect/Test Design Fabrication

  10. Real-World “V-Curve” • Service- Proven Product • Minimum Service Impacts System Requirements System Integration & Acceptance Verification and Validation Construction and Integration Planning and Design Sub-System Requirements Construct / Inspect/Test Design Fabrication

  11. Real-World “V-Curve” • Service- Proven Product • Minimum Service Impacts System Requirements System Integration & Acceptance Verification and Validation Construction and Integration Planning and Design Sub-System Requirements Construct / Inspect/Test Design Fabrication

  12. Recipe for Success –System Requirements • Service- Proven Product • Minimum Service Impacts System Requirements System Integration & Acceptance Verification and Validation Construction and Integration Planning and Design Sub-System Requirements Construct / Inspect/Test Design Fabrication

  13. Recipe for Success –System Requirements • e.g. IEEE 1474.1 • Line Characteristics • (fixed) • Core System Requirements • (fixed) • Site-Specific Requirements • (variable) • Keep it Simple!

  14. Adaptation Risk ….. • Adaptation Risk • System Requirements for Service-Proven Product • Site-Specific • Requirements • Service-Proven Product Design • New/Modified • Requirements • Site-Specific • Design

  15. System Requirements “… you can't always get what you want, but if you try sometime, you just might find you get what you need …” Mike Jagger/Keith Richards (Rolling Stones)

  16. System Requirements • Focus on the core business “needs” such as: • Improved service delivery • Capacity • Trip times • Operational flexibility • State-of-good-repair • Higher system availability • Reduced maintenance • Enhanced safety • Increased levels of automation

  17. System Requirements • Challenge site-specific “wants” • Agency-specific adaptations and new developments • E.g. requirements for “secondary” train detection/ protection (“fall-back” systems) • E.g. ATS-level functions • Agency-specific historic processes and practices • E.g. “we’ve always done it this way”; “it’s part of our culture” • Agency-imposed systems integration risks

  18. Recipe for Success – Migration Plan • Service- Proven Product • Minimum Service Impacts System Requirements System Integration & Acceptance Verification and Validation Construction and Integration Planning and Design Sub-System Requirements Construct / Inspect/Test Design Fabrication

  19. Recipe for Success – Migration Plan • Cost of Service Impact • Cost of avoiding Service Impact • Migration Plan • Test & Commissioning • Installation

  20. Migration Plan The Migration Plan defines a staged cut-over of the new signalling and train control systems both geographically and functionally Start with the “end-state” railway and work back, driven by business need priorities

  21. Migration Plan • Minimize Service Impacts • Prioritize Business Needs • For example: • Stage n (final stage): • Full geographic limits cut-over • Full functionality • Stage n-1: • Full geographic limits cut-over • Core functionality only • Stage n-2: • Core geographic limits cut-over only • Core functionality only • Stage n-3: • Etc.

  22. Migration Plan • Equipment to be installed • Vehicles required • Tests that must be conducted • Impacts to safety case • Etc. • Minimize Service Impacts • Stage “r-1” • (To be defined) • Stage “r” • (Defined) Given Stage “r”, how should Stage “r-1” be defined to get to Stage “r” with minimum Service Impacts?

  23. Migration Plan • Train-borne and wayside processors • Vital ATP functions, • Non-vital ATO and ATS functions • Software-based • Database-driven • Data communications network • Train-borne train location determination Understand the three key characteristics of CBTC systems:

  24. Migration Plan -Train-borne train location determination • The train is key – start here! • Recognize that to fully commission a CBTC system requires running multiple CBTC trains on revenue track • Minimize revenue track access requirements through prior integrated factory testing and use of a test track

  25. Migration Plan – Data Communications • Verify the performance, availability and stability of the CBTC data communications networks prior to CBTC functional testing/commissioning (e.g. “shadow-mode” testing) • Include analysis of worse-case conditions that cannot be easily duplicated in the factory or in the field

  26. Migration Plan – Distributed Vital/Non-Vital Processors Verify the overall stability of the CBTC distributed computer network, including ability to switchover between redundant sets of wayside and/or train-borne CBTC equipment Final functional testing can only be performed at a systems level with all major CBTC subsystems operational

  27. Migration Plan – Software-based and Database-driven • Application-specific infrastructure data and train- data has to be verified as an element of the functional test/commissioning process • Software development process does not end until the system is verified to be operating correctly in the field • Multiple software releases typically required and need to be planned for

  28. Migration Plan - Functional Testing of CBTC Systems • e.g. IEEE 1474.4 • Factory testing • Exhaustively test every CBTC function/sub-function in the factory • Test internal and external interfaces • Simulate a realistic range of message latencies and equipment response times • Perform system stress testing with fully integrated CBTC system • Run a wide range of operating scenarios • Simulate failure modes

  29. Migration Plan - Functional Testing of CBTC Systems • e.g. IEEE 1474.4 • For a CBTC upgrade project, a CBTC test track is mandatory to: • Confirm vehicle interfaces/characteristics • Confirm wayside interfaces/characteristics • Verify vehicle/wayside data communication links • Dry-run tests to be performed on revenue track • Test cut-over strategies between legacy and new systems

  30. Migration Plan - Commissioning CBTC Systems • Minimize Service Impacts • CBTC Functional Tests • Factory Tests • Test Track Tests • CBTC Data Comm Network • CBTC Computer Network • Fixed Equipment • CBTC Network Stability • Mobile Equipment • Revenue Track Tests • “Shadow Mode” Tests

  31. Recipe for Success ….. • Minimum Service Impacts • Service- Proven Product System Requirements System Integration & Acceptance Verification and Validation S U Construction and Integration Planning and Design Sub-System Requirements Construct / Inspect/Test C C Design Fabrication E S S

More Related