PTC
Deploying I-ETMS:
“What do I need to know???”
1
Agenda • “Why
should I care?”
• I-ETMS Overview • “How hard can it be?”
2
“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 (236.1005(a)(1)(i))? – Deploy PTC on locomotive(s) – Possible Office integration, servers, training, & configuration management – PTCSP submittals
3
I-ETMS Overview- Data Flow PTC Server
4
PTC Information exchanged with the I-ETMS Locomotive Office
Wayside
•
Crew Information
Authorities (TWC)
Report Location
Signal aspect
•
Train Consist
Track Data updates
Report Violations
Switch position
•
Bulletin Orders
Software updates
Report Events
Other devices
–
Speed Restrictions
–
Work Zone Limits
Security Key updates
Challenge: System Integration and Interoperability. Each Railroad has different systems but the locomotive interface must be standard
5
5
I-ETMS Architecture and Interoperability Paradigm Yellow RR Dispatching and Back Office Systems
Interoperability Scope PTC Back Office Server
PTC Back Office Server
Orange RR Dispatching and Back Office Systems
IETMS Onboard System
Train Crew
Wayside Interface Unit (WIU)
Black RR Dispatching and Back Office Systems
PTC Back Office Server
PTC Back Office Server
IETMS Interoperable/Specified Interface IETMS Specified Behavior Non-Interoperable Interface
6
Blue RR Dispatching and Back Office Systems
I-ETMS Interoperability Scenario PTC Onboard System maintains unique conversation with each governing Back Office Server and applicable WIUs along track segments on its route. Blue BOS 1 Sub A, B
M03
Green Road Train Crew
Blue Road Dispatching System
WIU
Red Sub-A
WIU
WIU
Red Sub-B
WIU
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
M03
Red Road Dispatching System
7
M03
Green Road Dispatching System
“How hard can it be?” • • • • • •
Integration Testing Installation Training Configuration Management FRA Compliance- PTCSP
8
Integration- PTC System Segments Office
NS Example: 20+ PTC components and systems that have to integrate and come together for testing system
TCSM
UTCS CAD
MDM
WSRS
KES
GIS
220 Base
Cell
WIFI
Communication PTC MR
ITCMS
MPLS
Locomotive TMC/ CDU
GPS/ Sensor
IETMS
CHM
EM
9
BOS
LMS
Wayside 220 Radio
OBN
WIU
Cell
220 Radio
WMS
Cell
WIFI
NS PTC Integration Test Lab- Atlanta
CAD/BOS
LOCOMOTIVE PTC/LEADER
COMM
WAYSIDE
10
PTC System Segments Office BOS
TCSM
UTCS
MDM
WSRS
KES
GIS
220 Base
Cell
WIFI
Communication PTC MR
ITCMS
MPLS
Locomotive TMC/ CDU
GPS/ Sensor
IETMS
CHM
EM
11
LMS
Wayside 220 Radio
OBN WIU
Cell
220 Radio
WMS
Cell
WIFI
PTC - Ongoing Testing Segment (vendor)
Nearest Neighbor
Deployment
(RR, Vendor)
NS LAB
12
Field Tests
End to End
(RR)
(RR)
I-ETMS Architecture and Interoperability Paradigm Yellow RR Dispatching and Back Office Systems
Interoperability Scope PTC Back Office Server
PTC Back Office Server
Orange RR Dispatching and Back Office Systems
IETMS Onboard System
Train Crew
Wayside Interface Unit (WIU)
Black RR Dispatching and Back Office Systems
PTC Back Office Server
PTC Back Office Server
IETMS Interoperable/Specified Interface IETMS Specified Behavior Non-Interoperable Interface
13
Blue RR Dispatching and Back Office Systems
PTC Architecture
Back Office
CSXT
TCSM IP
XML JMS/MQ
XML JMS/MQ
IDS
XML RBA SOAP/HTTPS
à 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
Logging
Alerting
MDM BOS
GD BOS (1)
GD BOS (2)
XML SOAP/HTTPS
PTCMR Legend
Auditing
XML Class D
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
Monitoring
XML Class D
IP
XML Class D
Wi-Fi (802.11)
Security
XML SOAP/HTTPS
IP CELL
Management
Messaging (Local Queues)
XML Class D
OBN
Transformation
EMP Class D
Satellite
ITC BackOffice Messaging
220
LMS ITCM
XML SOAP/HTTPS
PTCMR
IP
TMC
MIS
220
Routing
Locomotive
XML JMS/MQ
WSRS
XML SOAP/HTTP XML SOAP/HTTPS
WMS ITCM
CAD
XML SOAP/HTTPS XML SOAP/HTTP
WIU
TCP/IP
XML JMS/MQ
220
Codeline
XML SOAP/HTTPS
EMP JMS/AMQP
Base Station
Wayside
UTCS
ATCS
SA BOS
XML JMS/MQ
EMP
ITCM Railroad A
CI BOS
GIS
Domain Name Server(s) Network Time Server(s)
à Queue (jms, persistent) à Queue (jms, non-persistent)
VisioDocument
© Norfolk Southern Corp.
April 26, 2013
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
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
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
17
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
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
Locomotive: CDU Display Installation
Some are easy Some are more difficult
19
Locomotive: Space Constraints Some units accommodate additional PTC technology onboard
20
Locomotive: Space Constraints Some do not
21
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
Configuration Management Overview • Common Safety Plan: Configuration Management Overview • Development/Deployment/Track Data Change • I-ETMS System Configuration Items
• Industry Coordination
23
Safety Plan: Configuration Management § 236.1015 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
Change Management Processes Development Change
Deployment Change
Track Data Change
25
Supports management of proposed I-ETMS system changes, both Interoperable & Non-Interoperable, which impact the functional or non-functional behavior of the system.
Supports safe and reliable implementation of approved Interoperable Development Changes into an operational train control environment.
Supports safe and reliable implementation of changes to Track Data, utilizing the railroads Track Data Verification and Validation processes.
I-ETMS System Configuration Items EMP AMQP
Onboard Software Version
Class-D
Config Parms Common
Class-C
Config Parms Railroad
PTC AppsComms Interface
ITC-Net CAI Base Station Location Wayside Location RF Propogation Results
Onboard PTC System
ITCM Remote Locomotive
220 Network Onboard PTC Comms
ITC Onboard Radio Config Parms Common
PTC Office Apps
BOS Software
Wayside Comms
BOS MDM Software
MPLS Extranet
Interoperable PTC Network
I-ETMS PTC System
Config Parms Common ITCM Remote Wayside WIU
Track Database Structure Boundary Coordination
Geographic Data
Intra Consist Network Onboard Energy Management
Wayside Signals
ITC Wayside Radio
Interop 802.11
Interop TNB Lead / Train Radio Function Lead / Trail CDU Function Intra Consist Addressing Energy Mgmt Onboard Software
ITC Systems Management Office
Office Comms WSRS Office ITC Base Radio
E-bonded Ticket Systems
Asset Subscriptions Railroad Mgmt System
ITCSM Gateway
ITCM Office Config Parms Common
Key Exchange Service
Changes to many (but not all) of the components of the I-ETMS system require Industry Coordination 26
Successful CM requires coordination
Hazard Notification
FRA
RFA, Hazard & Deployment Change Notification
Track Data Coordination Development Change Hazard Notification
Industry Committees
Interoperability Coordination
I-ETMS Railroads Development Change
Deployment Change
Vendors Hazard Notification Deployment Change
27
Tenants and Interchange Railroads
Thank you!
28
“What do I need to know???”
1
Agenda • “Why
should I care?”
• I-ETMS Overview • “How hard can it be?”
2
“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 (236.1005(a)(1)(i))? – Deploy PTC on locomotive(s) – Possible Office integration, servers, training, & configuration management – PTCSP submittals
3
I-ETMS Overview- Data Flow PTC Server
4
PTC Information exchanged with the I-ETMS Locomotive Office
Wayside
•
Crew Information
Authorities (TWC)
Report Location
Signal aspect
•
Train Consist
Track Data updates
Report Violations
Switch position
•
Bulletin Orders
Software updates
Report Events
Other devices
–
Speed Restrictions
–
Work Zone Limits
Security Key updates
Challenge: System Integration and Interoperability. Each Railroad has different systems but the locomotive interface must be standard
5
5
I-ETMS Architecture and Interoperability Paradigm Yellow RR Dispatching and Back Office Systems
Interoperability Scope PTC Back Office Server
PTC Back Office Server
Orange RR Dispatching and Back Office Systems
IETMS Onboard System
Train Crew
Wayside Interface Unit (WIU)
Black RR Dispatching and Back Office Systems
PTC Back Office Server
PTC Back Office Server
IETMS Interoperable/Specified Interface IETMS Specified Behavior Non-Interoperable Interface
6
Blue RR Dispatching and Back Office Systems
I-ETMS Interoperability Scenario PTC Onboard System maintains unique conversation with each governing Back Office Server and applicable WIUs along track segments on its route. Blue BOS 1 Sub A, B
M03
Green Road Train Crew
Blue Road Dispatching System
WIU
Red Sub-A
WIU
WIU
Red Sub-B
WIU
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
M03
Red Road Dispatching System
7
M03
Green Road Dispatching System
“How hard can it be?” • • • • • •
Integration Testing Installation Training Configuration Management FRA Compliance- PTCSP
8
Integration- PTC System Segments Office
NS Example: 20+ PTC components and systems that have to integrate and come together for testing system
TCSM
UTCS CAD
MDM
WSRS
KES
GIS
220 Base
Cell
WIFI
Communication PTC MR
ITCMS
MPLS
Locomotive TMC/ CDU
GPS/ Sensor
IETMS
CHM
EM
9
BOS
LMS
Wayside 220 Radio
OBN
WIU
Cell
220 Radio
WMS
Cell
WIFI
NS PTC Integration Test Lab- Atlanta
CAD/BOS
LOCOMOTIVE PTC/LEADER
COMM
WAYSIDE
10
PTC System Segments Office BOS
TCSM
UTCS
MDM
WSRS
KES
GIS
220 Base
Cell
WIFI
Communication PTC MR
ITCMS
MPLS
Locomotive TMC/ CDU
GPS/ Sensor
IETMS
CHM
EM
11
LMS
Wayside 220 Radio
OBN WIU
Cell
220 Radio
WMS
Cell
WIFI
PTC - Ongoing Testing Segment (vendor)
Nearest Neighbor
Deployment
(RR, Vendor)
NS LAB
12
Field Tests
End to End
(RR)
(RR)
I-ETMS Architecture and Interoperability Paradigm Yellow RR Dispatching and Back Office Systems
Interoperability Scope PTC Back Office Server
PTC Back Office Server
Orange RR Dispatching and Back Office Systems
IETMS Onboard System
Train Crew
Wayside Interface Unit (WIU)
Black RR Dispatching and Back Office Systems
PTC Back Office Server
PTC Back Office Server
IETMS Interoperable/Specified Interface IETMS Specified Behavior Non-Interoperable Interface
13
Blue RR Dispatching and Back Office Systems
PTC Architecture
Back Office
CSXT
TCSM IP
XML JMS/MQ
XML JMS/MQ
IDS
XML RBA SOAP/HTTPS
à 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
Logging
Alerting
MDM BOS
GD BOS (1)
GD BOS (2)
XML SOAP/HTTPS
PTCMR Legend
Auditing
XML Class D
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
Monitoring
XML Class D
IP
XML Class D
Wi-Fi (802.11)
Security
XML SOAP/HTTPS
IP CELL
Management
Messaging (Local Queues)
XML Class D
OBN
Transformation
EMP Class D
Satellite
ITC BackOffice Messaging
220
LMS ITCM
XML SOAP/HTTPS
PTCMR
IP
TMC
MIS
220
Routing
Locomotive
XML JMS/MQ
WSRS
XML SOAP/HTTP XML SOAP/HTTPS
WMS ITCM
CAD
XML SOAP/HTTPS XML SOAP/HTTP
WIU
TCP/IP
XML JMS/MQ
220
Codeline
XML SOAP/HTTPS
EMP JMS/AMQP
Base Station
Wayside
UTCS
ATCS
SA BOS
XML JMS/MQ
EMP
ITCM Railroad A
CI BOS
GIS
Domain Name Server(s) Network Time Server(s)
à Queue (jms, persistent) à Queue (jms, non-persistent)
VisioDocument
© Norfolk Southern Corp.
April 26, 2013
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
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
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
17
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
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
Locomotive: CDU Display Installation
Some are easy Some are more difficult
19
Locomotive: Space Constraints Some units accommodate additional PTC technology onboard
20
Locomotive: Space Constraints Some do not
21
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
Configuration Management Overview • Common Safety Plan: Configuration Management Overview • Development/Deployment/Track Data Change • I-ETMS System Configuration Items
• Industry Coordination
23
Safety Plan: Configuration Management § 236.1015 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
Change Management Processes Development Change
Deployment Change
Track Data Change
25
Supports management of proposed I-ETMS system changes, both Interoperable & Non-Interoperable, which impact the functional or non-functional behavior of the system.
Supports safe and reliable implementation of approved Interoperable Development Changes into an operational train control environment.
Supports safe and reliable implementation of changes to Track Data, utilizing the railroads Track Data Verification and Validation processes.
I-ETMS System Configuration Items EMP AMQP
Onboard Software Version
Class-D
Config Parms Common
Class-C
Config Parms Railroad
PTC AppsComms Interface
ITC-Net CAI Base Station Location Wayside Location RF Propogation Results
Onboard PTC System
ITCM Remote Locomotive
220 Network Onboard PTC Comms
ITC Onboard Radio Config Parms Common
PTC Office Apps
BOS Software
Wayside Comms
BOS MDM Software
MPLS Extranet
Interoperable PTC Network
I-ETMS PTC System
Config Parms Common ITCM Remote Wayside WIU
Track Database Structure Boundary Coordination
Geographic Data
Intra Consist Network Onboard Energy Management
Wayside Signals
ITC Wayside Radio
Interop 802.11
Interop TNB Lead / Train Radio Function Lead / Trail CDU Function Intra Consist Addressing Energy Mgmt Onboard Software
ITC Systems Management Office
Office Comms WSRS Office ITC Base Radio
E-bonded Ticket Systems
Asset Subscriptions Railroad Mgmt System
ITCSM Gateway
ITCM Office Config Parms Common
Key Exchange Service
Changes to many (but not all) of the components of the I-ETMS system require Industry Coordination 26
Successful CM requires coordination
Hazard Notification
FRA
RFA, Hazard & Deployment Change Notification
Track Data Coordination Development Change Hazard Notification
Industry Committees
Interoperability Coordination
I-ETMS Railroads Development Change
Deployment Change
Vendors Hazard Notification Deployment Change
27
Tenants and Interchange Railroads
Thank you!
28
