WSO2Con EU 2015: A Quick Startup in Transportation – Inter-Company Data Exchange in Railway Operations Train operations in an open-access railway network is a complex process which involves multiple companies and which is governed by many regulations, traditions and restrictions. The WSO2 ESB was studied in the application of railway production processes, namely train path ordering, delivery, production and fulfillment. The railway infrastructure managers in Switzerland decided to migrate the current set of interfaces, which are heavily anchored in the public transport landscape. The new interface protocols have to be implemented before the end of 2016 and this creates a demanding timeline for the involved railway undertakings. This sessions presents how the WSO2 ESB was evaluated, and how a Quickstart was carried out to to validat the necessary use cases. Presenters: Thomas Goetz Head of Enterprise Architecture, BLS AG André Bally Business Analyst, BLS AG Matthias Günter Project Lead, BLS AG

1. A
Quick
Startup
in
Transporta1on
Inter-­‐Company
Data
Exchange
in
Railway
Opera1ons
Thomas
Goetz,
André
Bally,
MaHhias
Günter
BLS
AG
Switzerland

2. Content
1. Context
2. Project
3. Interfaces
in
Detail
4. Architecture
and
PaHerns

3. BLS
Switzerland‘s
second
largest
railway
company

4. BLS
150,000
passengers
per
day

5. BLS
35,000
metric
tons
of
freight
per
day

6. BLS
operates
since
2007
the
35-­‐km
Loetschberg
tunnel

7. Business
Context
Train
path
procurement
process
Train
operating
company
Railway
infrastructure
operator
Path
request
Path
provision
Train
composition
Actual
and
forecast
times
Invoice

8. Content
1. Context
2. Project
3. Interfaces
in
Detail
4. Architecture
and
PaHerns

9. The
project
scope
at
BLS
• Enterprise
Service
Bus
(ESB)
Pla[orm
- Requirements
- First
pilot
(product
based
on
JEE
applica1on
server)
- Re-­‐evalua1on
of
product
- Proof-­‐of-­‐concept
with
WSO2
Quickstart
Program
- Pla[orm
installa1on
and
development
of
the
interface
applica1ons
(s1ll
in
progress)
• Coopera1on
between
train
and
infrastructure
opera1ng
companies
- Governance
(joint
specifica1ons)
- IT
roadmap
- Funding

10. Timeline
for
ESB
pla[orm
re-­‐evalua1on
and
implementa1on
Task
Timeframe
Start
of
re-­‐evalua1on
Dec
2014
Pre-­‐evalua1on
(4
products,
based
on
general
criteria)
Dec
2014
Cost-­‐benefit
evalua1on
(reduc1on
to
1
or
2
products)
Jan
2015
Proof-­‐of-­‐concept
with
the
best
product
Feb
-­‐
Mar
2015
Decision
for
WSO2
Apr
2015
Build-­‐up
of
pla[orm
May
-­‐
Jul
2015
Implementa1on
of
interface
applica1ons
Aug
-­‐
Dec
2015
Produc1on
Dec
2015

11. Cost-­‐benefit
analysis
Criteria
assessed
by
4
experts
Company
- Strengths,
Weaknesses
- Analyst
ra1ng
- Cloud
integra1on
- Por[olio
- Partners
- Company
health
Product
- Price
- Development
model
- Number
and
type
of
developers
/
contributors
- Architecture
/
components
- Func1onality
- License
- Consul1ng
/
support
Community
- References
in
Switzerland
- User
groups
So6
factors
Individual
opinions
of
the
experts
on
- Architecture
- Integra1on
- Development

12. Content
1. Context
2. Project
3. Interfaces
in
Detail
4. Architecture
and
PaHerns

13. Train
path
procurement
process
Resource
planning
Train
operating
company
Train
operations
Railway
infrastructure
operator
Route
planning
Train
composition
Path
provision
Path
request Path
request
Path
planning
Production
Customer
information
Path
price
Train
planner
Train
path
planner
new
interfaces

14. Content
1. Context
2. Project
3. Interfaces
in
Detail
4. Architecture
and
PaHerns

15. Standardized
integra1on
Integration
problem
Integration
solution
characterize
analyze
design
build
Set
of
non-­‐functional
properties
Set
of
non-­‐functional
properties
Weighted
decision
matrix
Non-­‐functional
requirements
Candidate
integration
pattern
Software
architecture
Implementa1on
guidelines

16. Decision
matrix
Entscheidmatrix - Integrationsmuster
Attribute Werte x
Business-Motivation Durchgängigkeit von Geschäftsprozessen 1 1 1 1 1 1 1 1
Konsistenz von Geschäftsdaten x 1 1 1 1 1 1 1 0.5
Mehrfachverwendung Benutzerschnittstelle 1 5 5
Architekturprinzipien D1, G2 Services / Anwendungen 1 1 1 1 1 1
Datenbestände x 1 1 1 1 1 1 1 0.5
Kontrollierte Weiterentwicklung Ablösung von Altsystemen, Sanierung von Problemen 0.5 5 1 1 1 1 1 1
Architekturprinzip U12 Wartbarkeit und Erweiterbarkeit 1 1 1 1 1 1 1 1 1 1
Granularität der ausgetauschten Datensätze wenige Datensätze (<10) 1 1 1 1 1 1 1 1
viele Datensätze x 1 1 1 1 1 1 1 1 1 1
komplette Datenbestände 1 1 1 1 1 1 1
Grösse der ausgetauschten Datensätze klein <1 KB 1 1 0.5 0.5 0.5 1 1 1 1 1 1 1 1 1 1
mittel 1 KB - 1 MB x 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
gross (>1 MB) 1 1 1 1 1 1 1 1 0.5 0.5
sehr gross (>100 MB) 0.5 1 1 1 1 1 1
Zeitnähe des Datenaustausches zeitgleich (synchron) 1 0 0 1 1 0.5 0 1 1 1 1
zeitnah (asynchron) x 1 1 1 1 1 1 1 1 1 1 0 0
zeitfern (Batch) 1 1 1 1 1 1 0 0 0
Periodizität des Datenaustausches einmalig 1 0.5 1
bei Bedarf 1 1 1 1 1 1 1 1 1 1 1
periodisch < minütlich x 1 1 1 1 1 1 1 1 1 1
periodisch minutlich - stündlich 1 1 1 1 1 1 1 1 1 1
periodisch täglich, wöchentlich, jährlich 1 1 1 1 1
Verhältnis von Quell- zu Zielsystemen n:1 (Aggregator) 0 0 0 1 1 1 1 1 1 1
1:1 (Punkt-zu-Punkt) x 1 1 1 1 1 1 1 1 0 1 1
1:n (Distributor) 0 0 0 0 1 1 1 0 0
n:m (Kombination von Aggregator und Distributor => Mediator) 0 0 0 0 0 1 1 0 0
Datenflussrichtung Quelle zu Ziel x 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Ziel zu Quelle 0 0 0 0 1 1 1 1 1 1 1
Integrations-Distanz sehr nah (anwendungs-intern) 0 1 0 1 0 1 1 1 0
nah (anwendungsgruppen-intern) x 1 1 1 1 1 1 1 1 1 1 1 1 1
mittel (anwendungs-übergreifend) 0 1 1 1 1 1 1 1 1 1 1 1 1
weit (domänen-übergreifend) 1 0 1 1 1 1 1 1 1 1 1 1 1
sehr weit (unternehmens-übergreifend) 1 0 0 0 0 1 0 1
Daten-Transformation keine x 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Datentyp (Format, Benennung der Attribute) 0 1 1 1 0.5 1 1 1 1 1 1 1
einfache Abbildung von Datenwerten (Mapping von Konstanten, Selektionen) 0 0 1 1 1 1 1 1 1 1 0.5 0.5
komplexe Abbildung von Datenwerten (allgemeine Funktionen auf Einzelwerte) 0 0 1 1 0.5 0 0
analytische Funktionen (Aggregatfunktionen auf alle Datenwerte) 0 1 1 0 0
Integrationsfunktionalität direkte Kommunikation (Funktionsaufruf, Datenaustausch) 1 0 0 0
indirekte Kommunikation x 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Auslieferungsgarantie (at-least-once, exactly once) 1 1 1 1 1 1 1 1 1 1
Logging / Auditing / Archivierung 1 1 1 1 1 1 1 1 1 1
Verschlüsselung der Kommunikation 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Authentisierung und Autorisierung 1 1 1 1 1 1 1 1 1 1 1 1 1
Routing (Adress- oder Inhalt-basiert) 0 0 0 0 0 5 1 1 1 1 1
Prozess-Orchestrierung - ohne Benutzer-Interaktion (indirekte Kommunikation) 1
Workflow - mit Benutzer-Interaktion (indirekte Kommunikation) 0 0 0 0 1 0 0
Serviceaufruf 0 0 0 0 0 0.5 1 1 0.5 1 1 1 1
Datenstrukturierung Texte (schwach strukturiert) 1 0 0 1 1
Ausmodellierte Daten (stark strukturiert) x 1 1 1 1 1 1 1 1 1 1 1 1 1
Ressourcennutzung Gemeinsame Nutzung der physischen Ressource (sharing) 1 1 1 1 1 1 1 1
Gemeinsame Nutzung einer virtuellen Ressource (federated view) 1
Getrennte Nutzung einer physischen Kopie der Ressource (copying) x 1 1 1 1 1 1 1
Anbindungsart DB-Schnittstelle 1 1 1 1 1 1 0 0 0 0
Files x 1 0 1 1 1 0 0 0 0
Messaging 0 0 0 0 1 1 1 1 1 0 0
Service 0 0 1 0.5 0.5 0.5 1 0 0
User Interface 0 0 1 1 1
physikalische Integrationsdistanz gleicher Provider x 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
providerübergreifend (schweizweit) 1 0.5 0.5 0.5 0.5 1 1 1 1 1 1 1 0.5
providerübergreifend (international) 1 1 1 1
0 0
0 0 0 0 0
0 0 0 0 0
0 0 0 0 0 0 0 0
Summe Bewertung 11 13 15 11 13 9 11 7 1 3 8 3 1 1 1
Mögliche Integrationsmuster ü ü ü ü ü û ü û û û û û û û û
Empfohlenes Integrationsmuster:
SharedDB
Messaging
Prozessorchestrierung(ohneUI)
IntegrationBroker:EventPropagation
AggregierenvonDatenbanken:MasterData
Management(MDM)
RemoteProcedureInvocation
=> Kopieren von Massendaten (ETL): Datenpropagation operativ zu operativ
Datenintegration Funktionsintegration
Workflow(mitUI)
KopierenvonMassendaten(ETL):
Datenaggregationoperativzuoperativoder
analytisch(DWH)
IntegrationBroker:Gateway
Portal(Web,RichClient)
UI-
Integration
PortalmitSession(Web,RichClient)
FileTransfer
KopierenvonMassendaten(ETL):
Datenpropagationoperativzuoperativ
DB-Copy
KopierenvonMassendaten(ETL):Datenmigration
operativzuoperativ
Broker
ETL
Non-­‐func1onal
requirement
e.g.
data
volume
OUTPUT
Recommended
integra;on
pa<ern
e.g.
File
transfer
Value-­‐benefit
analysis
mul1ple
aspects
taken
into
account
simultaneously
Contribu1on
of
the
paHern
in
solving
this
requirement
(yes,
somewhat,
no)
Integra1on
paHern
e.g.
file
transfer
INPUT
value
of
each
non-­‐func;onal
requirement
e.g.
1
GB
per
day

17. 0.
Ini1al
solu1on
3. Process
2. Transac1on
/
master
data
1. Media1on
Train
path
provision
service
analysis
and
design
Master
data
Transac1on
data

18. Thank
You!
We
thank
Igor
Berchtold
from
SUVA
for
the
reference.
We
thank
our
QuickStart
team
from
WSO2:
• Suhothayan
Sriskandarajah
(Technical
Lead)
• Nirmal
Fernando
(Associate
Technical
Lead)
• Dassana
Perera
(Architect)
We
thank
also
our
BLS
team:
• Reto
Zaugg,
• CharloHe
Bachmann
• Michael
Zaugg
They
made
the
Quick
Startup
possible.