Interoperable CBS – Project Review and Update for RESC

1. Interoperable CBS – Project Review and Update for RESC RESC October 1, 2008 Bill Petit www.billpetit.com

2. Topics • Update RESC on Communication-Based Signaling (CBS) Activities • Birds Eye View • What we set out to do, What we did, What we would like to do • AREMA Committee 37 Manual Parts on Interoperability • Background • Manual Parts and Status • Basic System Architecture • Test Environment • Overview of Critical Link • Test Environment, Simulators, Equipment • Demonstration

3. What we set out to do • Define Interoperability for a PTC system based on signaling principles • Complete system providing stand-alone ability to set and protect routes, deliver onboard authorities in terms of aspects, enforce onboard authorities. • Focus on train control • Work with interoperable comms system per RESC • Basic system defined with ability to add additional functionality as needed.

4. What we did • Agreed to and published architecture and interoperability recommended practices through a Professional Industry Association (AREMA) • Through FRA and Private (supplier) funding • Defined Test Layout to incorporate multiple suppliers • Developed Communications Router and Simulators for Test Environment • Substituted 1st set of suppliers equipment for one of the simulators • Other suppliers well on their way in integrate equipment in next couple months

5. What we would like to do (subject to available funding) • Maintain Test Site • Upgrade to include revisions suggested through initial testing • Upgrade test site to include additional functionality defined in Manual Parts • e.g. database changes, Temporary Speed Restrictions • Use equipment in field environment (TTC?)

6. Back to a lower level view

7. Background • Roundtable discussions at 2005 AREMA C&S Conference generated request for interoperability guidelines for radio-based cab signal systems • Manual Parts approved for 2009 AREMA Manual of C&S Recommended Practices

8. Approved Manual Parts • 23.2 CBS System Requirements • 23.3 CBS System Design Guidelines • 23.4 CBS System Interoperability Requirements • 23.5 CBS Infrastructure Database

9. Section 23.2 • 23.2.1 Recommended Functional Requirements of a CBS System. • Define the recommended system functional requirements. • 23.2.2 Recommended RAMS, Environmental and Other Requirements for Signaling Systems Using CBS Architecture. • Define the recommended reliability, availability, maintainability, and safety (RAMS), environmental, electromagnetic compatibility, and quality assurance requirements.

10. Section 23.3 • 23.3.1 Recommended Design Guidelines for a CBS System • Define the recommended system architecture and interfaces based on conventional signaling principles.

11. Section 23.4 • 23.4.1 Recommended Communications Protocols for a CBS system • Define the recommended system communication protocol (based on ATCS addressing and datagram) • Capable of being transported over a variety of communications channels (e.g. IP, ITP) • 23.4.2 Recommended Communications Messages for a CBS System • Define the recommended standard messages for communications between CBS subsystems

12. Section 23.5 • 23.5.1 Recommended Onboard Database Guidelines for a CBS system • Define the recommended structure and content of the onboard database

13. Basic System Architecture

14. What is CBS? Defined Communications Based Signaling as ‘a radio based cab signal system’. • Operate the same as a conventional Cab Signal System with enforcement. Onboard aspect display instead of wayside signals • “Virtual” Block Occupancies used instead of physical track circuits. • Train location determination done by on-board equipment (Definition of how to indicate a block is occupied, not how position is determined). • Communication, including cab signal aspect transmission from wayside to trains, via a digital data communications network.

15. What is CBS? • CAD operation (i.e dispatching) is the same as in conventional CTC system. • Signal Logic Processor (SLP) does all the vital logic and sends controls to wayside appliances and signal aspect info to the On Board Logic Processor (OBLP). • OBLP provides signal aspect and speed limit info to train operators, and performs vital overspeed protection and signal enforcement. • SLP also processes Bulletins received from CAD via Form Translator, and communicates them to various OBLPs. • Communication follows ATCS protocols over a wide variety of transmission media

16. Control Office Existing cTc Territory Controls and Indications Wayside Bungalow Cab Signal sent through rails

17. Control Office CBS in existing Dark Territory Controls and Indications Proceed Aspect Occupying Block 123

18. Interoperability Demo

19. Project Administration • Funded by FRA Office of RR Development • Administered through Railroad Research Foundation through a Cooperative Agreement with FRA

20. Project Administration • Railroad Research Foundation subcontracts for • Project Management – Bill Petit (www.billpetit.com) • Test Environment – Critical Link (www.criticallink.com) • Participating suppliers • Alstom (participating independently, not under contract) • GETS Global Signaling • Safetran Systems • Union Switch and Signal

21. Project Goals • Demonstrate overall architecture and interoperablity through adherence to AREMA Manual Parts (and suggest modifications as needed) • Cooperate with other groups (e.g. AAR Railway Electronics Standards Committee) • Part of pathway towards fully interoperable systems

22. Critical Link Overview John Fayos, President

23. ICBS Test Environment – Goals 23 • Provide the infrastructure to verify interoperability between multiple supplier’s CBS equipment • Verify compliance with the AREMA standard • Data logs • Support incremental integration of supplier equipment • Long term test facility

24. Critical Link Background 24 • Critical Link designs & builds customized embedded processing systems • Hardware, software, firmware • From concept inception thru production management • Work in a number of different industries • Underlying technologies remain the same • 25 engineers, located in Syracuse, NY

25. Transportation & Standards Work 25 • Communication Based Train Control • Data communication system design and implementation • FIS System (Interface between UP office and Safetran Field Equipmemt) • IEEE 1570-2002: Highway-Railway Interface • APTA TCIP (Transit Communications Interface Profiles) Standard Development • Software support tools, including simulators

26. ICBS Interoperability Configuration 26

27. Test Environment Requirements 27 • Provide communications between components • No radios • Simulate delays and drop-outs • Log communication messages • Enable incremental integration of supplier components • Drives the development of component simulators

28. Test Environment Architecture 28

29. Test Environment Communications 29

30. Test Environment Simulators 30 • Communications Router • WA Simulator • Vehicle Display Simulator • OBLP Simulator • SLP Simulator • US&S Office

31. Test Environment Simulators 31 • All simulators implemented as PC applications • Multiple instantiations of each simulator can be invoked • Simulators can be replaced with supplier equipment on a piece-by-piece basis • Enables single supplier’s equipment checkout prior to interoperation with other supplier’s equipment • Interoperability with simulators is demonstrated first

32. ICBS Demo System 32

33. ICBS Demo – Physical Configuration 33

34. Basic Territory for each supplier to simulate

35. Overall Territory with Each Supplier covering One Section GETS Safetran US&S Alstom

37. Representation of Overall Test Layout

39. Project Status • Test Environment defined and developed • Test Drivers / Simulators developed for all subsystems • Safetran SLP and WA integrated into System • Uses simulated OBLP • CAD Office System integrated into test environment

47. Project Plan • October • GETS WA, SLP and OBLP integrated into system • US&S WA and SLP integrated into system • November • Alstom SLP, WA and OBLP; US&S OBLP integrated into system • December - January • Full interoperability display in Syracuse • March • Final reports, etc

48. GETS SLP Equipment Rack • SLP (GETS VHLC) • Interfaces to Genisys Control Office • Processes Signaling Logic • Interfaces to SLP Protocol Converter • Receives Block Statuses • Transmits Switch & Signal Statuses • Interfaces to WA for Switch Control Diagnostic Terminal • SLP Protocol Converter • Converts Between GE and ICBS Messaging • Uses ICBS Database for Status Mapping • Transmits Block Statuses to GE SLP • Receives Switch & Signal Statuses from GE SLP • Interfaces to Comm. Router (ICBS Network) • WA (GETS VHLC) • Interfaces to SLP • Receives Switch Control Statuses from SLP • Transmits Switch Position Statuses to SLP

49. GETS OBLP Equipment Rack • OBLP (GETS ITCS Onboard Computer) • Location Determination Using ITCS Equivalent Database • Enforces Targets • Interfaces to OBLP Protocol Converter • Transmits Block Statuses • Receives Switch & Signal Statuses • Interfaces to Vehicle Simulator & Loco Interface Panel GETS ITCS Locomotive Display Vehicle Simulator & Diagnostic Terminal • Locomotive Interface Panel • Acknowledgement Input • Reverser Handle Input • In/Out Mode Switch • OBLP Protocol Converter • Converts Between GE and ICBS Messaging • Uses ICBS Database for Status Mapping • Receives Block Statuses from OBLP • Transmits Switch & Signal Statuses to OBLP • Interfaces to Comm. Router (ICBS Network)

50. Alstom ICBS SLP and WA Equipment Rack Ethernet Hub VPI Power and VRD Relays VPI2 SLP WA Local Panel VPI2 WA Power Supply