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

A Recipe for Success in Implementing CBTC on an Operating Transit System

Presented by:

Dr. Alan F. Rumsey, P.Eng, FIRSE

March 12, 2014

Communications-Based Train Control Conference London, 2014

Why implement CBTC on an Operating Transit System?

Step-change Increase in Operational Performance

Control Centre Modernization

Infrastructure / Systems Upgrades New Vehicles

Upgrade Signalling and Train Control Systems

CBTC Enabling

Technology

Line Upgrade

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

Recipe for Success …..

Scope

CostSchedule

Success …..

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

Scope

CostSchedule

Success …..

Minimum Service Impacts


… with minimum service impacts

Scope

CostSchedule

Success …..

Service- Proven Product



… with minimum service impacts

… and service proven product

Standard “V-Curve”

System Requirements

System Integration & Acceptance

Sub-System Requirements

Design Fabrication

Construct / Inspect/TestP

lanning and Design

Verification and Validation

Con

stru

ctio

n an

d In

tegr

atio

n

Real-World “V-Curve”

System Requirements



Design Fabrication

Construct / Inspect/TestP

lanning and Design


Con

stru

ctio

n an

d In

tegr

atio

n



System Requirements



Design Fabrication

Construct / Inspect/Test

Planning and D

esign


Con

stru

ctio

n an

d In

tegr

atio

n



System Requirements



Design Fabrication


Planning and D

esign


Con

stru

ctio

n an

d In

tegr

atio

n




System Requirements



Design Fabrication


Planning and D

esign


Con

stru

ctio

n an

d In

tegr

atio

n



Recipe for Success –System Requirements

System Requirements



Design Fabrication


Planning and D

esign


Con

stru

ctio

n an

d In

tegr

atio

n



Project Complexity

CostSchedule

Recipe for Success –System Requirements

Line Characteristics

(fixed)

Core System Requirements

(fixed)

Site-Specific Requirements

(variable)

Keep it Simple!

e.g. IEEE

1474.1

Adaptation Risk …..

Site-Specific

Requirements

Service-Proven Product Design

System Requirements for Service-Proven

Product

Adaptation Risk

New/Modified

Requirements

Site-Specific

Design

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)

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

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

Recipe for Success – Migration Plan

System Requirements



Design Fabrication


Planning and D

esign


Con

stru

ctio

n an

d In

tegr

atio

n



Minimizing Service Impacts

CostSchedule

Recipe for Success – Migration Plan

Migration Plan

Cost of Service Impact

Cost of avoiding Service Impact

Test & Commissioning

Installation

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

Migration Plan

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.

Minimize Service Impacts

Prioritize Business

Needs

Migration Plan

Given Stage “r”, how should Stage “r-1” be defined to get to Stage “r” with minimum Service Impacts?


Stage “r-1”

(To be defined)

• Equipment to be installed

• Vehicles required• Tests that must be

conducted• Impacts to safety

case• Etc.

Stage “r”

(Defined)

Migration Plan

Understand the three key characteristics of CBTC systems:

Train-borne train location determination

Train-borne and wayside processors• Vital ATP functions, • Non-vital ATO and

ATS functions• Software-based• Database-driven

Data communications

network

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

Migration Plan -Train-borne train location determination

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

Migration Plan – Data Communications

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

Migration Plan – Distributed Vital/Non-Vital Processors

Way

sid

e &

Sta

tio

ns

TR

AC

K

PROFIBUS

Op

erat

ion

Co

ntr

ol C

entr

e

CBI(Sicas)

Beacons

Operator Room

Em

erge

ncy

Con

trol

Pan

el

OCC Ethernet LAN

WCC(Cell Controller)

ATC Ethernet Dual Network

PSDauxiliaries

StationLocalPanel

DrivingControl Panel

Train ControlMonitoring

System

CCTV Controller

B Reader


PassengerEmergency Call

Box

Train Network

Train Line

Radio Controller(Voice & CCTV)

PublicAddress

CarborneRadio Unit Carborne

Radio Unit

CC Carborne Controller

Recording(option)

EventRecorder

SCADATractionLightingPowersubstation

CCTV SystemPublic Address

System

CCTV Monitor

PassengerInformation

System

Passenger InformationDisplay

Emergency CallBox

Call box

FireFighting

Fire AlarmPanel

IntruderAlarm

SCADAFacilities

SupervisionSystem

Ventilation...etc

GPS -Time server

Depot

Space forEmergency OCC

VCP

Operator &SupervisorConsoles

Eth

ern

et

10

0B

ase

Tx

OP phoneset1 2 3

4 5 6

7 8 9

* 8 #

OP mic

SMO LAN Ethernet 100BaseTx

7 56

121110

8 4

21

9 3

Clock Display

Fare Collection

Mimic Panel

OPEmergency

Phone1 2 3

4 5 6

7 8 9

* 8 #

Visitor Console

VisitorGallery

TrainingServers

TraineesConsole(s)

TrainerConsole

Training Room

EPABX

Printers Printers

Server SystemATS

SCADA_elec + Power

ServerCOMMisc.

Farecollection

Server

Technical Room

ATC NMSWCN supervision

SCADA

Communication(MSN

supervision)

NetworkManagement

Operator CentreMaintenanceConsoles &Printer

TimetableGenerator

MaintenanceCentre

ZoneController

(ZC)

WC

N E

the

rne

t L

AN

WREWRE

Ra

dio

Ne

two

rk M

M F

O

Eth

ern

et

10

0B

ase

Tx

CCTV Monitor

RemoteECC

TrackVacancyDetection

ObstacleDetection

Facilities &PSD

Server

SMO Console

Recording(Voice - CCTV - Fire alarm)

MMS

PSD

CCTVWayside

Unit

RadioNetwork & CCTV

Station MasterOffice (SMO)

Phoneset IP

LP/TP_SS

Multiservice Network(MSN)

ATC Ethernet Network (WCN)

EmergencyLogic Unit

UPS

UPS

UPS

BLS

1 2 3

4 5 6

7 8 9

* 8 #

FIRE

BLS

1 2 3

4 5 6

7 8 9

* 8 #

PSDController

Odometer

Signalling EquipmentRoom (SER)

CCTV - PA -Radio etc.

To Bus OCC& Road OCC

VCP: CCTV

Track & power network

To CCTV(in technical room)

BLS

1 2 3

4 5 6

7 8 9

* 8 #

Radio NetworkWayside Unit

Way

sid

e &

Sta

tio

ns

TR

AC

K

PROFIBUS

Op

erat

ion

Co

ntr

ol C

entr

e

CBI(Sicas)

Beacons

Operator Room

Em

erge

ncy

Con

trol

Pan

el

OCC Ethernet LAN

WCC(Cell Controller)

ATC Ethernet Dual Network

PSDauxiliaries

StationLocalPanel


Train ControlMonitoring

System

CCTV Controller

B Reader


PassengerEmergency Call

Box

Train Network

Train Line

Radio Controller(Voice & CCTV)

PublicAddress

CarborneRadio Unit Carborne

Radio Unit

CC Carborne Controller

Recording(option)

EventRecorder

SCADATractionLightingPowersubstation

CCTV SystemPublic Address

System

CCTV Monitor

PassengerInformation

System

Passenger InformationDisplay

Emergency CallBox

Call box

FireFighting

Fire AlarmPanel

IntruderAlarm

SCADAFacilities

SupervisionSystem

Ventilation...etc

GPS -Time server

Depot

Space forEmergency OCC

VCP

Operator &SupervisorConsoles

Eth

ern

et

10

0B

ase

Tx

OP phoneset1 2 3

4 5 6

7 8 9

* 8 #

OP mic

SMO LAN Ethernet 100BaseTx

7 56

121110

8 4

21

9 3

Clock Display

Fare Collection

Mimic Panel

OPEmergency

Phone1 2 3

4 5 6

7 8 9

* 8 #

Visitor Console

VisitorGallery

TrainingServers

TraineesConsole(s)

TrainerConsole

Training Room

EPABX

Printers Printers

Server SystemATS

SCADA_elec + Power

ServerCOMMisc.

Farecollection

Server

Technical Room

ATC NMSWCN supervision

SCADA

Communication(MSN

supervision)

NetworkManagement

Operator CentreMaintenanceConsoles &Printer

TimetableGenerator

MaintenanceCentre

ZoneController

(ZC)

WC

N E

the

rne

t L

AN

WREWRE

Ra

dio

Ne

two

rk M

M F

O

Eth

ern

et

10

0B

ase

Tx

CCTV Monitor

RemoteECC

TrackVacancyDetection

ObstacleDetection

Facilities &PSD

Server

SMO Console

Recording(Voice - CCTV - Fire alarm)

MMS

PSD

CCTVWayside

Unit

RadioNetwork & CCTV

Station MasterOffice (SMO)

Phoneset IP

LP/TP_SS

Multiservice Network(MSN)

ATC Ethernet Network (WCN)

EmergencyLogic Unit

UPS

UPS

UPS

BLS

1 2 3

4 5 6

7 8 9

* 8 #

FIRE

BLS

1 2 3

4 5 6

7 8 9

* 8 #

PSDController

Odometer

Signalling EquipmentRoom (SER)

CCTV - PA -Radio etc.

To Bus OCC& Road OCC

VCP: CCTV

Track & power network

To CCTV(in technical room)

BLS

1 2 3

4 5 6

7 8 9

* 8 #

Radio NetworkWayside Unit

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

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

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

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

Migration Plan - Functional Testing of CBTC Systems

e.g. IEEE

1474.4

Migration Plan - Commissioning CBTC Systems


CBTC Functional Tests

Revenue Track Tests

Factory Tests

Test Track Tests

CBTC Data Comm Network

CBTC Computer Network

Fixed Equipment

Mobile Equipment

CBTC Network Stability

“Shadow Mode” Tests

Recipe for Success …..

System Requirements



Design Fabrication


Planning and D

esign


Con

stru

ctio

n an

d In

tegr

atio

n



S

S

U

C

C

E

S

Documents

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