Deploying I-ETMS: What do I need to know???

Transcription

1 Deploying I-ETMS: What do I need to know??? 1

2 Agenda Why should I care? I-ETMS Overview How hard can it be? 2

3 Why should I care? Do you have to deploy PTC? Are you a Class 1 railroad? Required to deploy PTC on track and locomotives Do you host passenger traffic? Required to deploy PTC on track and locomotives Are you a tenant on track that is PTC required or operate over a diamond where PTC is required ( (a)(1)(i))? Deploy PTC on locomotive(s) Possible Office integration, servers, training, & configuration management PTCSP submittals 3

4 I-ETMS Overview- Data Flow PTC Server 4

5 Office PTC Information exchanged with Crew Information Train Consist Bulletin Orders Speed Restrictions Work Zone Limits the I-ETMS Locomotive Authorities (TWC) Track Data updates Software updates Security Key updates Report Location Report Violations Report Events Wayside Signal aspect Switch position Other devices Challenge: System Integration and Interoperability. Each Railroad has different systems but the locomotive interface must be standard 5 5

6 I-ETMS Architecture and Interoperability Paradigm Yellow RR Dispatching and Systems PTC Server Interoperability Scope PTC Server Orange RR Dispatching and Systems Wayside Interface Unit (WIU) IETMS Onboard System Train Crew Black RR Dispatching and Systems PTC Server PTC Server IETMS Interoperable/Specified Interface Blue RR Dispatching and Systems IETMS Specified Behavior Non-Interoperable Interface 6

7 M03 M03 M03 I-ETMS Interoperability Scenario PTC Onboard System maintains unique conversation with each governing Server and applicable WIUs along track segments on its route. Blue BOS 1 Sub A, B Green Road Train Crew Blue Road Dispatching System WIU WIU WIU WIU Red Sub-A Red Sub-B Blue Sub-A Blue Sub-B WIU Red BOS 1 Sub A Red BOS 2 Sub B Green BOS 1 Sub A Green BOS 2 Sub B WIU Red Road Dispatching System Green Road Dispatching System 7

8 How hard can it be? Integration Testing Installation Training Configuration Management FRA Compliance- PTCSP 8

9 Integration- PTC System Segments Office BOS TCSM UTCS CAD NS Example: 20+ PTC components and systems that have to integrate and come together for testing system Communication Locomotive TMC/ CDU ITCMS MDM GPS/ Sensor PTC MR 220 Radio MPLS OBN WSRS 220 Base Wayside KES Cell WIU GIS WIFI Cell IETMS EM CHM LMS Cell WIFI 220 Radio WMS 9

10 NS PTC Integration Test Lab- Atlanta CAD/BOS LOCOMOTIVE PTC/LEADER COMM WAYSIDE 10

11 PTC System Segments Office BOS TCSM UTCS MDM WSRS KES GIS Communication ITCMS PTC MR MPLS 220 Base Cell WIFI Locomotive Wayside TMC/ CDU GPS/ Sensor 220 Radio OBN WIU Cell IETMS CHM Cell 11 EM LMS WIFI 220 Radio WMS

12 PTC - Ongoing Testing Segment (vendor) Deployment Nearest Neighbor (RR, Vendor) NS LAB Field Tests (RR) End to End (RR) 12

13 I-ETMS Architecture and Interoperability Paradigm Yellow RR Dispatching and Systems PTC Server Interoperability Scope PTC Server Orange RR Dispatching and Systems Wayside Interface Unit (WIU) IETMS Onboard System Train Crew Black RR Dispatching and Systems PTC Server PTC Server IETMS Interoperable/Specified Interface Blue RR Dispatching and Systems IETMS Specified Behavior Non-Interoperable Interface 13

14 PTC Architecture CSXT TCSM Wayside Railroad A IP Base Station 220 ITCM EMP JMS/AMQP EMP WSRS SA BOS SOAP/HTTPS ATCS TCP/IP JMS/MQ JMS/MQ UTCS Codeline CAD JMS/MQ JMS/MQ JMS/MQ SOAP/HTTPS MIS IDS RBA SOAP/HTTPS WIU WMS ITCM 220 PTCMR Routing Transformation Management Locomotive TMC PTCMR Legend LMS ITCM OBN BOS Notes SA -Switch Awareness GD -Geographic District CI -Crew Interaction MDM -Mobile Device Manager SA, GD, CI & MDM are logical functions of BOS One or more BOS functions may be collocated physically à Adapter (Class D, JMS, SOAP, ) Inbound only -shape inside PTCMR block Outbound only -shape outside PTCMR block Inbound/Outbound -shape half inside & half outside PTCMR block à Queue (jms, persistent) à Queue (jms, non-persistent) 220 Satellite CELL Wi-Fi (802.11) IP IP IP ITC BackOffice Messaging EMP Class D Class D SOAP/HTTPS MDM BOS Security Auditing Class D SOAP/HTTPS Messaging (Local Queues) SOAP/HTTP Logging SOAP/HTTP SOAP/HTTPS Class D GD BOS (1) GD BOS (2) Monitoring Alerting Class D SOAP/HTTPS CI BOS GIS Domain Name Server(s) Network Time Server(s) VisioDocument Norfolk Southern Corp. April 26, 2013

15 Locomotive I-ETMS Installation NS is installing: TMCs- Runs I-ETMS software CDUs- Crew interface to I-ETMS Cut-Out switches- Provides for failure bypass Sensor cabling- Provides loco data to TMC ITCMS- Provides interoperable message routing Onboard Network- Provides IP Cell/Wifi devices and CDUs 220 MHz Radio- Provides office/wayside interoperable communications Antennas- 2xGPS, Cell, WiFi, 220MHz 15

16 Locomotive I-ETMS Installation Requires: Trained work-force (employee or contractor) Installation procedures for various loco types FRA witnessed installation PTC commissioning Maintenance standards Configuration Management 16

17 Locomotive: Multiple Models & Configurations Norfolk Southern has more than 250 different configurations of locomotives. Same model locomotives vary by year, previous owner(s), modifications made during the life of the locomotive, and by FRA standards at the time of manufacture or previous modification Locomotive Model SD40-2 D9-40CW GP38-2 ES40DC SD60 D8-40CW SD70M-2 D9-40C GP40-2 D8-40C SD70 SD70M GP60 SD60I D8-32B SD60M GP38-3 GP59 ES44AC SD40-E 17

18 Locomotive: CDU Display Installation NS Objectives for CDU Installation Must be readable from seat position Must be able to reach buttons from seat position Must not block view out windows Must not block other required information Must be maintainable Must not cause an unsafe condition, knee knocker NS & BLE cab committee 18

19 Locomotive: CDU Display Installation Some are easy Some are more difficult 19

20 Locomotive: Space Constraints Some units accommodate additional PTC technology onboard 20

21 Locomotive: Space Constraints Some do not 21

22 Locomotive: Antenna Arrays Each locomotive has its own array of antenna that must be installed. This array must also be retouched to add yet more antennae. 22

23 Configuration Management Overview Common Safety Plan: Configuration Management Overview Development/Deployment/Track Data Change I-ETMS System Configuration Items Industry Coordination 23

24 Safety Plan: Configuration Management PTC Safety Plan content requirements Section (d)(9) A complete description of the configuration or revision control measures designed to ensure that the railroad or its contractor does not adversely affect the safety-functional requirements and that safety-critical hazard mitigation processes are not compromised as a result of any such change; Development Change Deployment Change Track Data Change Each railroad develops their own CM plan, which integrates with these processes 24

25 Change Management Processes Development Change Supports management of proposed I-ETMS system changes, both Interoperable & Non-Interoperable, which impact the functional or non-functional behavior of the system. Deployment Change Supports safe and reliable implementation of approved Interoperable Development Changes into an operational train control environment. Track Data Change Supports safe and reliable implementation of changes to Track Data, utilizing the railroads Track Data Verification and Validation processes. 25

26 I-ETMS System Configuration Items EMP Onboard Software Version Config Parms Common Config Parms Railroad ITCM Remote - Locomotive ITC Onboard Radio Config Parms Common BOS Software BOS MDM Software ITC Wayside Radio Config Parms Common ITCM Remote - Wayside WIU Track Database Structure Boundary Coordination Onboard PTC Comms PTC Office Apps Wayside Comms Class-D Class-C Onboard PTC System Wayside Signals AMQP Geographic Data PTC Apps- Comms Interface I-ETMS PTC System ITC Systems Management - Office E-bonded Ticket Systems ITCSM Gateway ITC-Net CAI Base Station Location 220 Network Interoperable PTC Network Office Comms Intra Consist Network Onboard Energy Management Asset Subscriptions Railroad Mgmt System Key Exchange Service Wayside Location RF Propogation Results Interop Energy Mgmt Onboard Software WSRS Office MPLS Extranet Interop TNB Lead / Train Radio Function Lead / Trail CDU Function Intra Consist Addressing ITC Base Radio ITCM Office Config Parms Common Changes to many (but not all) of the components of the I-ETMS system require Industry Coordination 26

27 Successful CM requires coordination FRA Hazard Notification RFA, Hazard & Deployment Change Notification Development Change Hazard Notification I-ETMS Railroads Interoperability Coordination Track Data Coordination Development Change Tenants and Interchange Railroads Industry Committees Deployment Change Hazard Notification Vendors Deployment Change 27

28 28 Thank you!