UC:IS:DriverAdvisorySystem: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[unchecked revision][unchecked revision]
(insert of content)
 
(insert of content)
Line 6: Line 6:
'''Description / {{Deu|Beschreibung}} / {{Fra|Description}}'''
'''Description / {{Deu|Beschreibung}} / {{Fra|Description}}'''


The Driver Advisory System (DAS) is an on-train driver support system which advises a driver on the most energy-efficient speed profile with which to meet the train’s current schedule.  The DAS receives as input the current schedule (which may be updated at any time) together with a range of static or near-static data relating to the track, namely: topology, topography, asset locations and speed restrictions; and various parameters relating to the vehicle itself.
The Driver Advisory System (DAS) is an on-train driver support system which advises a driver on the most energy-efficient speed profile with which to meet the train’s current schedule.  The DAS receives as input the current schedule (which may be updated at any time) together with a range of static or near-static data relating to the track, namely: topology, topography, asset locations and speed restrictions; and various parameters relating to the vehicle itself.  
   
   


'''Data Flows and Interfaces / {{Deu|Datenflüsse und Schnittstellen}} / {{Fra|Flux de données et interfaces}}'''
'''Data Flows and Interfaces / {{Deu|Datenflüsse und Schnittstellen}} / {{Fra|Flux de données et interfaces}}'''


<u> Data inputs </u>
<u>Data inputs</u> <br>
<ul>
Track attributes (<i>Infrastructure</i>):
<li> Track attributes (Infrastructure):
* Track Centre Line (as a polyline)
<ul><li> Track Centre Line (as a polyline)
* Track altitude (polyline)
    <li> Track altitude (polyline)
* Geometry: Track curvature  
    <li> Geometry: Track curvature  
* Topology: Node-link model  
    <li> Topology: Node-link model  
* Route IDs
    <li> Route IDs
* Track IDs
    <li> Track IDs
* Mileposts / kilometre posts id, location
    <li> Mileposts / kilometre posts id, location
* Junctions id, location
    <li> Junctions id, location
* Loop ends id, location
    <li> Loop ends id, location
* Platform ends platform ids, location
    <li> Platform ends platform ids, location
* Tunnels id, location (,envelope)
    <li> Tunnels id, location (,envelope)
* Signals id, location, signal type
    <li> Signals id, location, signal type
* Permissible speeds including permanent speed restrictions (PSRs), qualified by direction of travel and train type
    <li> Permissible speeds including permanent speed restrictions (PSRs), qualified by direction of travel and train type
* Temporary speed restrictions (TSRs), qualified by direction of travel and train type
    <li> Temporary speed restrictions (TSRs), qualified by direction of travel and train type
* Emergency speed restrictions (ESRs)
    <li> Emergency speed restrictions (ESRs)
* Locations of the following may also be required in the future (TBD):
    <li> Locations of the following may also be required in the future (TBD):
** Signal berths id, location  
  <ul><li> Signal berths id, location  
** Bridges id, location
      <li> Bridges id, location
** Road crossings id, location
      <li> Road crossings id, location </ul> </ul>
Schedule attributes (Timetable):
<li> Schedule attributes (Timetable):
* Train Service Id
<ul><li> Train Service Id
* (Sequence of) scheduled locations
    <li> (Sequence of) scheduled locations
** location name  
  <ul><li> location name  
** location as Track attribute
      <li> location as Track attribute </ul>
* For each passing location
    <li> For each passing location
** passing time and tolerance (before and after)
  <ul><li> passing time and tolerance (before and after)</ul>
* For each stopping location
    <li> For each stopping location
** arrival and departure times  
  <ul><li> arrival and departure times </ul> </ul>
Vehicle attributes (Rollingstock):
<li> Vehicle attributes (Rollingstock):
* Formation or consist
<ul><li> Formation or consist
* (mass, length) profile
    <li> (mass, length) profile
* Maximum speed
    <li> Maximum speed
* Braking parameters (braking curve, brake delay, brake build-up)
    <li> Braking parameters (braking curve, brake delay, brake build-up)
* Traction parameters
    <li> Traction parameters
* Coefficients of resistance
    <li> Coefficients of resistance </ul></ul>


 
<u>Data outputs</u> <br>
<ul> <u>Data outputs</u><p>
DAS operating logs
DAS operating logs
* Train id
* Train id
Line 58: Line 56:
* Train actual speed
* Train actual speed
* Advised speed
* Advised speed
* Driver entered parameters </ul>
* Driver entered parameters




'''Interference with other railML<sup>®</sup> schemas / {{Deu|Interferenz mit anderen railML<sup>®</sup>-Schemen}} / {{Fra|Interaction avec autres schemas railML<sup>®</sup>}}'''
'''Interference with other railML<sup>®</sup> schemas / {{Deu|Interferenz mit anderen railML<sup>®</sup>-Schemen}} / {{Fra|Interaction avec autres schemas railML<sup>®</sup>}}'''


* rolling stock
* timetable
* timetable
* rolling stock




Line 73: Line 71:
<u>How often do the data change (update)?</u>
<u>How often do the data change (update)?</u>


* static (not changing)
* Track attributes: nearly static except for TSRs and ESRs (weekly/daily)
* yearly
* Schedule attributes: daily, with realtime changes
* monthly
* Vehicle attributes: occasional changes (event-driven)
* weekly
* daily


<u>How big are the data fragments to be exchanged (complexity)?</u>
<u>How big are the data fragments to be exchanged (complexity)?</u>
Line 85: Line 81:
<u>Which views are represented by the data (focus)?</u>
<u>Which views are represented by the data (focus)?</u>


* Train regulation
* Energy
* Energy
* Train regulation

Revision as of 12:43, 5 October 2015

Use case / Anwendungsfall / :

Driver Advisory System (DAS); Fahrerassistentsystem;


Description / Beschreibung /

The Driver Advisory System (DAS) is an on-train driver support system which advises a driver on the most energy-efficient speed profile with which to meet the train’s current schedule. The DAS receives as input the current schedule (which may be updated at any time) together with a range of static or near-static data relating to the track, namely: topology, topography, asset locations and speed restrictions; and various parameters relating to the vehicle itself.


Data Flows and Interfaces / Datenflüsse und Schnittstellen /

Data inputs
Track attributes (Infrastructure):

  • Track Centre Line (as a polyline)
  • Track altitude (polyline)
  • Geometry: Track curvature
  • Topology: Node-link model
  • Route IDs
  • Track IDs
  • Mileposts / kilometre posts id, location
  • Junctions id, location
  • Loop ends id, location
  • Platform ends platform ids, location
  • Tunnels id, location (,envelope)
  • Signals id, location, signal type
  • Permissible speeds including permanent speed restrictions (PSRs), qualified by direction of travel and train type
  • Temporary speed restrictions (TSRs), qualified by direction of travel and train type
  • Emergency speed restrictions (ESRs)
  • Locations of the following may also be required in the future (TBD):
    • Signal berths id, location
    • Bridges id, location
    • Road crossings id, location

Schedule attributes (Timetable):

  • Train Service Id
  • (Sequence of) scheduled locations
    • location name
    • location as Track attribute
  • For each passing location
    • passing time and tolerance (before and after)
  • For each stopping location
    • arrival and departure times

Vehicle attributes (Rollingstock):

  • Formation or consist
  • (mass, length) profile
  • Maximum speed
  • Braking parameters (braking curve, brake delay, brake build-up)
  • Traction parameters
  • Coefficients of resistance

Data outputs
DAS operating logs

  • Train id
  • Time
  • Train location
  • Train actual speed
  • Advised speed
  • Driver entered parameters


Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen /

  • rolling stock
  • timetable


Characterizing Data / Charakterisierung der Daten /

This section serves to specify the required data regarding certain aspects.

How often do the data change (update)?

  • Track attributes: nearly static except for TSRs and ESRs (weekly/daily)
  • Schedule attributes: daily, with realtime changes
  • Vehicle attributes: occasional changes (event-driven)

How big are the data fragments to be exchanged (complexity)?

  • huge (region)

Which views are represented by the data (focus)?

  • Train regulation
  • Energy