Difference between revisions of "RTM Model Extensions"

From wiki.railtopomodel.org
Jump to navigation Jump to search
(Änderung Navi)
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Under Construction}}
{{Overview|text=This page will concentrate on the {{rtm}} Model Extensions.}}<br />
<br />
{{Overview|text=This page will concentrate on the RTM Model Extensions.}}<br />
== Planned extensions ==
== Planned extensions ==
[[Planned extensions]]
{{main|Planned extensions}}
The model will be progressively enriched to support business usages.
== Open issues ==
The next version will include:
{{main|Open issues}}
* Multiple times (horizons, creation and modification dates, validity dates,…)
* Projects, versions and life cycle management
* Requirements for Signalling and Interlocking
* …
Following versions will also include:
* Operational events
* Traffic Management (commercial routes,…)
* Asset Management
* …
=== Time Management aspects ===
'''Definitions of the time aspect:''' <br />
The time aspect in RailTopoModel is defined at the class “BaseObject” and refers to the time period for which a certain information object is valid in respect to availability for usage for train operations.<br /><br />
The attribute '''“validFrom”''' defines the point in time where the object in question is available for usage for train operations.<br /><br />
The attribute '''“validTo”''' defines the point in time where the object in question is no longer available for functional usage. The attribute “validTo” can be empty.<br />
'''Handling time dimension:''' <br />
The handling of the time dimension manifests during input of new-, adjusted- or deleted data and then storage and export of (subsets) of data. Especially the export functions can focus on specified time frames of specified subsets (topological areas) which can be (even partly) affected by different time validities of values for the same objects.<br />
Time related dependencies can be handled on the level of:
* Individual (data) objects: from birth to dismantling, both for the functional placeholder of an object (designed existence)  and its physical realization(s) (reality outside in the field).
* Coherent data sets on group- or area level of the topology (usually demarcated on the micro-topology)
* Connectivity in time and space of data-entities (e.g. to secure overall referential integrity)<br />
The last issue is secured the best if new topologically coherent datasets with a common time validity are inserted as a whole, with special care for ravel relationships with its topological environment. At the storage phase of data, this corresponds with the handling of precise demarcated and identified excisions in the original dataset in which the modifications will be applied.<br />
'''Time granularity:'''<br />
The granular size of the time dimension has to be chosen in accordance with the frequencies of the design-, data maintenance-, and placing into service processes. In general this will be a calendar day.<br />
'''Ravel connectivity:'''<br />
|chapter={{RTM}} Model Extensions
Ravel connectivity is the issue where changed objects/phenomena or topology constituents inside an area (and its dataset) will need restored relationships with unchanged objects in their direct environment outside that area (in the drawing these areas are shown as demarcated excisions).
|chapterlink=RTM Model Extensions
|pchapter={{RTM}} Use Cases and Application Examples
|pchapterlink=RTM Use Cases and Application Examples
== Open issues ==
[[Open issues]]
|next=Planned extensions

Latest revision as of 14:47, 13 March 2017

This page will concentrate on the RailTopoModel® Model Extensions.

Planned extensions

→Main Article: Planned extensions

Open issues

→Main Article: Open issues

What you should have learned
Please, enter a summary!
Chapter RailTopoModel® Use Cases and Application Examples RailTopoModel® Model Extensions
Section Planned extensions