RTM use cases and application examples: Difference between revisions

From railTOPOMODEL® Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
mNo edit summary
No edit summary
Line 3: Line 3:
<strong>This page will concentrate on the RTM Use Cases and Application Examples.</strong>
<strong>This page will concentrate on the RTM Use Cases and Application Examples.</strong>


The following use cases were identified and structured in a general framework.
{| class="wikitable"
|-
! Interfaces\Field !! Technical !! Operational !! Legal
|-
| '''Internal''' between departments
|| Standardised data exchange between technical departments (e.g. engineering + capacity allocation) often using different IT technologies and definitions<br />
&rArr; synergy effects
|| Standardised data exchange between planning and monitoring of operations e.g. timetabling and real-time circulation tracking<br />
&rArr; synergy effects
|| Improved monitoring of the network condition, via dedicated 'Dashboards' providing network data summaries<br />
&rArr; easier & faster data transfer and processing
|-
| '''National/Business''' between partners
|| Standardised data exchange between IMs and their business partners, such as ETCS suppliers and maintenance sub-contractors<br />
&rArr; savings in data production and transmission<br />
&rArr; less vendor lock-in
|| Standardised data exchange between IMs and RUs (e.g. for track possessions).<br />
&rArr; reduced operational costs<br />
<br />
Standardised <u>inter</u>modal communications<br />
&rArr; enhanced railway market share
|| Ability of RUs to determine permissible train characteristics (esp. braking) on any infrastructure, as required by EU legislation (esp. TSI OPE)<br />
&rArr; time savings, less errors<br />
<br />
Standardised data provision to national administrations such as land registers, regions, ministries. (Example: multiannual MS-IM contract as per 2012/34, art. 8 and 30)<br />
&rArr; improved quality; scalable level of detail; improved credibility of rail
|-
| '''International''' between countries, organisations, EU
|| Standardised data model/exchange on which ETCS-, IT- and other industries can design their products<br />
&rArr; from taylor-made to <u>in</u>expensive mass market solutions
|| Standardised data exchange within corridors and between organisations (RNE, ...)<br />
&rArr; no need to develop multiple data conversion interfaces<br />
<br />
Information exchange concerning station accessibility<br />
&rArr; contribution to TSI PRM objectives
|| Standardised/unique data provision to legal obligations; NS, RINF, Inspire, EU Freight corridors, TEN-T network<br />
&rArr; Savings in data conversions and reduction of administrational burden
|}
== railML (Data Exchange) ==
== railML (Data Exchange) ==
[[railML (Data Exchange)]]
[[railML (Data Exchange)]]

Revision as of 16:35, 29 March 2016

UnderConstruction blue.png This page is a draft and under construction. Sorry for temporary problems. See the discussion page to find a summary of the tasks and to coordinate the work on this page. Recognize that the content of this page may change quickly. If you find any copyright infringements, please contact us: Christian.rahmig@dlr.de.


This page will concentrate on the RTM Use Cases and Application Examples.

The following use cases were identified and structured in a general framework.

Interfaces\Field Technical Operational Legal
Internal between departments Standardised data exchange between technical departments (e.g. engineering + capacity allocation) often using different IT technologies and definitions

⇒ synergy effects

Standardised data exchange between planning and monitoring of operations e.g. timetabling and real-time circulation tracking

⇒ synergy effects

Improved monitoring of the network condition, via dedicated 'Dashboards' providing network data summaries

⇒ easier & faster data transfer and processing

National/Business between partners Standardised data exchange between IMs and their business partners, such as ETCS suppliers and maintenance sub-contractors

⇒ savings in data production and transmission
⇒ less vendor lock-in

Standardised data exchange between IMs and RUs (e.g. for track possessions).

⇒ reduced operational costs

Standardised intermodal communications
⇒ enhanced railway market share

Ability of RUs to determine permissible train characteristics (esp. braking) on any infrastructure, as required by EU legislation (esp. TSI OPE)

⇒ time savings, less errors

Standardised data provision to national administrations such as land registers, regions, ministries. (Example: multiannual MS-IM contract as per 2012/34, art. 8 and 30)
⇒ improved quality; scalable level of detail; improved credibility of rail

International between countries, organisations, EU Standardised data model/exchange on which ETCS-, IT- and other industries can design their products

⇒ from taylor-made to inexpensive mass market solutions

Standardised data exchange within corridors and between organisations (RNE, ...)

⇒ no need to develop multiple data conversion interfaces

Information exchange concerning station accessibility
⇒ contribution to TSI PRM objectives

Standardised/unique data provision to legal obligations; NS, RINF, Inspire, EU Freight corridors, TEN-T network

⇒ Savings in data conversions and reduction of administrational burden

railML (Data Exchange)

railML (Data Exchange)

Railway Infrastructure Manager Database

Railway Infrastructure Manager Database