Upload
others
View
2
Download
0
Embed Size (px)
Citation preview
3rd UIC RailTopoModel and railML®
Conference
UIC, Paris October 7th, 2014
Towards a Universal Topology Model for Railways and Data Exchange Format for Infrastructure
Page 2 3rd UIC RailTopoModel and railML conference / Paris, October 2014
Agenda
1 Welcome and keynote speeches
2 UIC RailTopoModel
3 Practical examples and benefits from a shared model
4 A first railML® 3 version; especially for infrastructure
5 Evolution of the railML.org business model
Page 3 3rd UIC RailTopoModel and railML conference / Paris, October 20142nd UIC’s RailTopoModel and railML conference
Page 4 3rd UIC RailTopoModel and railML conference / Paris, October 20142nd UIC’s RailTopoModel and railML conference
GLOBAL IS ARCHITECTURE
A Powered by ArianePowered by Ariane
1. Shared Repository2. Service Oriented Architecture (SOA), 3. Decoupled applications (ODS / ESB)
Feeding and Broadcast Services AESB
3 main bricks, based on Ariane Model
BI DWHA
2- Historical analysis on DataWareHouse (DWH)1- Operational piloting on ODS
Feeding and Broadcast Services
A
Operational Data Store
A
Business events and data, - pushed by source domain applications - to be shared with other domains thru servicesESB
Bus
ines
s A
pplic
atio
ns
& s
ervi
ces
Services Library
Services Library
Capa PlanCapa PlanTraffic
MngtTrafficMngt MaintenanceMaintenance
…… Business Applications and services Communication restricted to Repositories and ODS
Shared Reference data
•In memory national repository
•> 100 REST Services
A
Enterprise Repository (GAÏA)
Page 5 3rd UIC RailTopoModel and railML conference / Paris, October 20142nd UIC’s RailTopoModel and railML conference
UNIVERSAL INFRASTRUCTURE REPOSITORY
GAÏASCOPEPortal
Internal users / RUs / Partners
A
Infrastructure Repository(GAÏA)
A
A Powered by ArianePowered by Ariane
The unique and mandatory repository for all new IT development
Content : Line/track topology and characteristics, elementary routes,…geometry, geography,schematics,… all facilities and equipment,… down to track joint,
Display and Diffusion, of infrastructure Data
New Soft
HistoricalSoft
Software Applications(internal / RUs / Partners)
Web Services
A
New Soft
A
New Soft
A
New Soft
A
HistoricalSoftHistorical
SoftHistoricalSoft
FilesA
>100 services+ 20 Geographic services
Services : direct access to each object and properties, transformation services (properties oflinear elements, routes, distances, linear to geo,…)
Page 6 3rd UIC RailTopoModel and railML conference / Paris, October 2014
One example of implementationPlanning & Scheduling - Traffic management - CC
Planning & Scheduling
Control Command
Traffic and OperationManagement
TPS XYZ… InterlockingSystem(SIL4)
Softw
are Software package
ODS
A
MDM
Library of shared services (SOA) (route and speed calculation, graphic viewers,…)
Dat
a
Engineering Department
A Powered by ArianePowered by Ariane
A
A
Page 7 3rd UIC RailTopoModel and railML conference / Paris, October 20142nd UIC’s RailTopoModel and railML conference
2014 2015
ONGOING PROJECTS (ALL BASED ON ARIANE)
2016
SOAService Library
Infrastructure services
GIS, EDM,… services
A
A
Capacity Planning
ODS Traffic Management
Assets & Works Management
A
A
A
MDM (GAÏA) InfrastructureA
Ariane Object Model
Infrastructure
Circulation
Works
A
A Powered by ArianePowered by Ariane
Planning and Scheduling
Business Domains Incidents mngt
Works & Resource Planning
Traffic management
A
A
A
A
Page 8 3rd UIC RailTopoModel and railML conference / Paris, October 2014
ProRail’s practical implementation of topology as foundation.
Gerben Schut, ProRail
October 2014
Page 9 3rd UIC RailTopoModel and railML conference / Paris, October 2014 9
Dutch rail infrastructure:
Operational points andConnecting sections of lines
Page 10 3rd UIC RailTopoModel and railML conference / Paris, October 2014
Operational points:
• Onnen zuid (Onz)
• Assen (Asn)
• Beilen (Bl)
Page 11 3rd UIC RailTopoModel and railML conference / Paris, October 2014
Node-edge concept
X red cross à internal-node-link = N (false)Ѵ green mark à internal-node-link = Y (true)
Page 12 3rd UIC RailTopoModel and railML conference / Paris, October 2014
Bl OnzAsn
Node Node Node
Edge Edge
EdgeEdge
Page 13 3rd UIC RailTopoModel and railML conference / Paris, October 2014
Nodes and edges can be extended with:Ø weights (network analysis)Ø utilization properties (like max speed, electrification, limitations)Ø objects like signalsØ geographic features
Page 19 3rd UIC RailTopoModel and railML conference / Paris, October 2014
If the model is usable at Operational point level (macro)
and at switch level (micro)
why not at country level (super macro)?
Page 22 3rd UIC RailTopoModel and railML conference / Paris, October 2014
Nodes and edges can be extended with:Ø weights (network analysis)Ø utilization properties (like max speed, electrification, limitations)
ØUseful for International corridors
Page 23 3rd UIC RailTopoModel and railML conference / Paris, October 2014
All levels are data: ØPresentations are derivedØExport can be anything in any formatØAll data can be combined with all other dataØIdentification:
not on location, but with unique ID’s
Page 24 3rd UIC RailTopoModel and railML conference / Paris, October 2014
Data exchange for EU’s Rail FreightCorridor N° 2
Page 25 3rd UIC RailTopoModel and railML conference / Paris, October 2014
Data exchange for EU’s Rail FreightCorridor N° 2
Page 26 3rd UIC RailTopoModel and railML conference / Paris, October 2014
Data exchange for EU’s Rail FreightCorridor N° 2
The Corridor Web interface will provide information on how to use the corridor resources.
ØPAP (Pre-Arranged Paths, where the path has already been processed)
-
ØCustom Paths (where the feasibility and timetabling are done on demand)
Page 27 3rd UIC RailTopoModel and railML conference / Paris, October 2014
Data exchange for EU’s Rail FreightCorridor N° 2 (RFC2)
As the GIS workgroup for RFC2, our given mission is to integrate cartographic data to the web interface, to improve the exchange of data.
As a group, we want to deliver §the most reliable data, §with the least effort on IM side.
Page 28 3rd UIC RailTopoModel and railML conference / Paris, October 2014
Data exchange for EU’s Rail FreightCorridor N° 2
Our first Recommendation :ØWhy develop a specific interface for Corridor 2,
as all corridors share the same goals and issues?
LetLet’’s try to build a common (GIS) interface to all the corridors. s try to build a common (GIS) interface to all the corridors.
§To allow the client to see which corridors he may chose for each path§It will lessen development costs.§It will lessen data collection costs.
ØBut it implies a centralization of the corridor GIS interfaces and data management.
ØThis recommendation has been approved by the RFC2 board.
Page 29 3rd UIC RailTopoModel and railML conference / Paris, October 2014
Data exchange for EU’s Rail FreightCorridor N° 2
We want to be able to assemble data with the least possible effort.
Solution : Solution : Describe corridor paths as function of our timetabling applicatiDescribe corridor paths as function of our timetabling applications segments.ons segments.
Using the UIC RailTopoModel approach, we mapped the corridor segments on the Train operation segments
Page 30 3rd UIC RailTopoModel and railML conference / Paris, October 2014
Data exchange for EU’s Rail FreightCorridor N° 2
We obtain a coherent topologic Networkcoherent topologic Network
Properties of each segment may be computed from our train operation data
§Max Gauge, §Max axle load§…
Page 31 3rd UIC RailTopoModel and railML conference / Paris, October 2014
Data exchange for EU’s Rail FreightCorridor N° 2
Data are at Macro-Level : we need a Macro-to-Corridor transformation.
By mapping corridor on macro we discovered inconsistencies in the published documents:
Page 32 3rd UIC RailTopoModel and railML conference / Paris, October 2014
Data exchange for EU’s Rail FreightCorridor N° 2
Still in order to lessen the IM’s efforts, our Second Recommendation :
ØWhy develop a specific file format for Corridor 2 data transfer?
LetLet’’s all the corridors try to use a common data transfer format.s all the corridors try to use a common data transfer format.
As we are using the UIC RailTopoModel to build data, railML® is the best choice.
Page 33 3rd UIC RailTopoModel and railML conference / Paris, October 2014
Data exchange for EU’s Rail FreightCorridor N° 2
Those two recommendations have been approved by the RFC2 board,
But as they imply coordination between corridors, the final decision will be taken at meetings between corridor executives.
So far, the preliminary discussions with Corridor 1 seemed positive.
Page 34 3rd UIC RailTopoModel and railML conference / Paris, October 2014
Data exchange for EU’s Rail FreightCorridor N° 2
In the meantime we are building the datasets and sample cartographic applications