2 nd UIC RailTopoModel and railml Conference

Transcription

1 2 nd UIC RailTopoModel and railml Conference Towards a Universal Topology Model for Railways and Data Exchange Format for Infrastructure Session A: Results from UIC s ERIM activity: UIC RailTopoModel UIC Paris; April 8th, 2014

2 Agenda 1 Welcome and keynote speeches 2 Results from UIC s ERIM activity: UIC RailTopoModel 3 The railml 3 Prototype for Railway topology 4 The usage of railml for the RINF project of ERA 5 Project plan and next steps Session A Page 2 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

3 Reminder from Sept 2013: Our challenge Based on the positive results of UIC feasibility study > Propose to the railway community A powerful and strong object model A structured and evolutionary exchange format internal partners Session A Page 3 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

4 Reminder from Sept 2013: our commitment > Finalize the foundation of UIC RailTopoModel > Build the first layers of railml 3 > Propose the first bricks for railml tool box > Build a railml translator for RINF Session A Page 4 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

5 UIC RailTopoModel Basics: Users The main aim of the UIC RailTopoModel is - to provide a structure for the description of a rail network - that supports the needs of the two main categories of rail network users - Asset Management (mainly use the positioning functions) - Traffic Management (mainly use the routing capabilities) Object Reference Axis Axis Session A Page 5 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

6 UIC RailTopoModel Basics: Referencing I Many ways to reference an event, in space or along a line : Km 31,515 Km m 30 0,7754 X, Y l, f Session A Page 6 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

7 UIC RailTopoModel Basics: Referencing II ,7754 We chose the percentage of the edge (trail, section of line, ) as the Master system for storing and transmitting position data, because -of its independence from Spatial Referencing system (Works in schematics as well as geographic), -of its independence from the units (miles, km, m, degrees ), physical references or measuring tapes they are usable at any level -Every other system can easily fall back to this one -Every other system can be deduced from it Coordinate transformations functions will be offered to translate from this system to more user-friendly referencing (GPS, XYZ, Mileage, Mileposts ) Session A Page 7 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

8 UIC RailTopoModel Basics: Relations We want to model a network. Every element of the network is related to others. These relations happens at one of their extremities (0 or 1) These links may be navigable or not C 0 D0 C C 1 A A 1 D D 1 F Session A Page 8 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

9 UIC RailTopoModel Basics: Multilevel I The users does not see the network in the same way: Micro : Detail infrastructure Meso : connections between stops, sidings and junctions Macro : connections between major cities Session A Page 9 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

10 UIC RailTopoModel Basics: Multilevel II Those visions of the network describe the same network! We have to ensure: - Data consistency The network should really model the same reality, whichever the level - Ease of data maintenance The data must be managed at the level where it is collected 1! time. It should then be manipulated to fit its uses Multiple usages. Example: Gauge reduction: happens at a specific location - managed as a located event Usage: Gauge capability on the segment = minimum gauge for this segment Session A Page 10 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

11 UIC RailTopoModel Basics: Aggregation Micro : Meso : Macro : The aggregation mechanics ensures that -network definition stays coherent from one level to the other and -information can be transmitted from one level to another. Session A Page 11 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

12 UIC RailTopoModel Basics: Common Path We defined 3 common aggregation levels, along one aggregation path ; The model allows the definition of any number of other levels Along this path or another. Micro Micro for Micro+ Micro for X Micro+ Micro for Meso X Micro+ for Meso X for Y Disaggregation Aggregation Meso Y A Virtual Level Meso for Macro Y for Macro Y for Z B Persistent Level Macro Common Path Z Session A Page 12 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

13 UIC RailTopoModel Basics: Objects I We have identified three types of objects/events which occur on the railway network : Punctual object : Signals, boundaries, beacons, Linear object : Route, slope profile, speed profile, ballast renewal, platform edge Areal object : Track circuit, catenary zone, Station, bridge Session A Page 13 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

14 UIC RailTopoModel Basics: Objects II Punctual object : Transmitted as a position on a line s Linear object : Transmitted as an ordered list of objects Areal object : Transmitted as an unordered list of objects, forming a subnetwork Session A Page 14 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

15 Future common extensions to the UIC RailTopoModel Next steps after establishment of the UIC RailTopoModel Concept: >Topology = kernel (carrier) of railway objects and data. Metaphors of the Christmas tree and the flowerbud. Session A Page 15 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

16 Christmas tree metaphor Kernel = treestem + branches = network topology (macro, meso, micro) carrier of garlands, birds, bells and balls = decoration (all types of objects) Session A Page 16 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

17 Flower bud metaphor Kernel = bud; origin of leaves Jellow cone = generic extension on the bud Leaves = application domains Railway topology = kernel Future kernel extensions ERTMS, timetabling, asset management, etc. = application domains Session A Page 17 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

18 Some possible generic extensions on the topology 1. Always present (at a certain level) on railways: interlocking 2. Always valid for each object: Locations 3D a set of safety rules and their methods a set of coordinates for the location of objects, network-nodes, area demarcations 3. Always relevant for any data item or object: Time validity 4. Any set of generic (gauges, gradient, ballast type ) time interval of existence Utilization restrictions Session A Page 18 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

19 Generic extensions: Concentric circles around the kernel: Session A Page 19 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

20 Norwegian Experiences: Jernbaneverket Tools and data available for development National asset DB Session A Page 20 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

21 Norwegian Experiences: Jernbaneverket Need for an integration hub yyy xxx yyy -> RDF RDF RDF RDF -> csv RDF RDF SQL xxx -> RDF RDF RDF RDF -> SQL RailML RailML National infrastructure assets db (RDBMS) SQL -> RDF Integration hub (RDF format: Flat structure) RDF RDF -> RailML RailML RINF Session A Page 21 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

22 Swiss experiences: BLS / SBB Status Quo Source: Markus Giger/ Network- Reference Gleispunkt GP Signaling System in Inventory Gleisanfang/ende GAE Beginning in 2005, SBB has created a unified topology database called UNO serving several operational business cases such as timetable-planning or traindisposition. It's base concept is a Node/Edge Graph Model where other data such as signalisation can be easily linked. Topology information changes over time and therefore the concept and implementation requires a solid time dimension approach, which has been implemented. Gleisknoten GKn Gleiskante GKa Network-Topology The following analysis has been made having the concepts of UNO in mind which has been industry proven over the last 7 years. Session A Page 22 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

23 Swiss experiences: BLS / SBB Possible Domains Exchange format SBB / BLS / regulation authority / third parties Asset-Management with a common topology ONE topology serving several business cases Session A Page 23 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

24 Swiss experiences: BLS / SBB Compatibility Check UIC RailTopoModel could be (to be verified) generated from existing Swiss applications. UNO already uses a node/edge graph-model. Intrinsic positioning system as base reference system to avoid anomalies in linear positioning. Open Issues Time dimension / integrity Status information / integrity Distinct definitions Univeral identifiers Define what specific objects should be modeled on which level (by example) Based upon one MICRO level, several MESO - and if required even more MACRO levels -can be implemented. Image source: Session A Page 24 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

25 Swiss experiences: BLS / SBB Summary In Switzerland there is a need for a common exchange format Even with some important open issues, the UIC RailTopoModel has a high level of maturity Relevant stakeholders should participate on defining a standard and must finally commit to it Image source: Session A Page 25 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

26 Austrian experiences: ÖBB Infra UIC RailTopoModel and ÖBB data models I Targets RailTopoModel and railml as a building block of IT-Strategy? Contribution to development of UIC RailTopoModel Context Urgent need: improve quality of combined permanent way & track geometry data Introduce topology into construction and maintenance centered business processes Promote integrated view of railway Actions Analyse and choose relevant datasets Understand UIC RailTopoModel Derive and implement a relational table design Import existing data Implement example functionality Results Working pilot on the line level Model related feedback Integration of track level data in preparation Session A Page 26 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

27 Austrian experiences: ÖBB Infra UIC RailTopoModel and ÖBB data models II Context Urgent need: improve quality of combined permanent way & track geometry data New technical regulation of track layout Schwerpunkttrassierung barycenter track layout Safety considerations require precise switch data in track layout environment data quality improvement necessary Testbed for compatibility check Permanent way dataset contains topology information on track level Navigation in user interface requires topology information on line level Session A Page 27 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

28 Austrian experiences: ÖBB Infra UIC RailTopoModel and ÖBB data models III Short digression Topology can be used to improve documentation quality systematically Session A Page 28 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

29 Austrian experiences: ÖBB Infra UIC RailTopoModel and ÖBB data models IV End of short digression Session A Page 29 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

30 Austrian experiences: ÖBB Infra Actions I Analyse and choose relevant datasets ÖBB dataset Content UIC RailTopoModel IOS igleislagemessung Line and track designation framework Configuration data for high performance measurement car MACRO and MESO MICRO / MESO ioberbau Permanent way MICRO (NANO) Session A Page 30 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

31 Austrian experiences: ÖBB Infra Actions II Understanding UIC RailTopoModel Micro Nano Permanent way detailed view (one switch has three connection points) Micro Micro Permanent way; Timetable Macro Meso Meso Macro Routeplanning for measurement car Standard lines ÖBB RailTopoModel Test Macro Standard Path Macro 2 ÖBB full-size Aggregated lines (e.g. two lines on one railway embankment) Session A Page 31 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

32 Austrian experiences: ÖBB Infra Actions III Implement example functionality Functionality Description Concept of UIC RailTopoModel Station, stop and junction navigation jurisdictional areas Alternative line names Present adjacent stations, stops and junctions and allow direct jump to one of the neighbouring sections Show appropriate service region and service center Allow user to choose line naming system and present correct line code and name NetElement and Relation Network NetEvent Session A Page 32 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

33 Austrian experiences: ÖBB Infra Results Working pilot on line level Jurisdictional areas Flexible naming systems Navigation functionality for user interface Session A Page 33 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

34 Austrian experiences: ÖBB Infra Results II Model related feedback Issue Description Action References Vertical navigation Using existing standards Lifecycle Allow references in RailTopoModel to backlink to existing datasets How to navigate between different levels of a layered network (Micro, Meso, Macro) e.g. OGC GML (Geography Markup Language) How to model the lifecycle of a layered network Extension of model Clarify preferred modelling approach Discussion Discussion Session A Page 34 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

35 Austrian experiences: ÖBB Infra Conclusions UIC RailTopoModel has the potential to become the relevant reference model for topology components of integrated railway IT Systems UIC RailTopoModel will allow to streamline interfaces between infrastructure and operating business processes UIC RailTopoModel will allow to rectify existing systems and will be a good starting point for new developments railml is perfectly positioned to implement UIC RailTopoModel as central part of a comprehensive exchange format for all aspects of railways Session A Page 35 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014

36 Business Uses case: European Corridors > Challenge: 6 corridors, crossing more than 10 countries Each Corridor has build its own Information System/GIS. All concerned IM s have to provide fine and up-to-date infrastructure description of each segment of network. Some IM s might have to feed 3 or 4 different Corridors IS > Proposal: railml 3 shall be the standard format for all topology and infrastructure data exchanges between IMs and Corridor IS Session A Page 36 2 nd UIC RailTopoModel and railml Conference; Paris, April 8 th, 2014