| Ticket#77: vehicle services [message #891] |
Mon, 19 November 2012 11:00 |
Andreas Tanner
Messages: 52
Registered: March 2012
|
Member |
|
|
Dear all,
I would like to draw the forum's attention to ticket#77 and the related
presentation of Christoph Jobmann at the last meeting
http://www.railml.org//index.php/veranstaltungsarchiv.html?f ile=tl_files/railML.org/documents/events/slides/2012-11-14_d b_jobmann-db_wartungsintervalle.pdf
Christoph's proposal is
- to introduce a new child element of vehicle, called "treatment" to
define an interval for a vehicle service, with attributes id,
description, maxDuration, onlyActiveDays (boolean), maxDistance and a
child element "contains" with a reference to another treatment.
maxDistance and maxDuration are intended to define the intervals.
onlyActiveDays specifies whether for duration, days where the vehicle
does not move do count towards the interval.
Now a "major" service may comprise the services of a "minor" one and
reset those intervals. The "contains" subelement models this idea.
I think this is a good proposal and would like ask coordinators to
change the ticket priority from "low" to "normal" with the hope to
implement it for 2.3 latest.
Christoph's proposal goes even further and does also cover maintenance
workshop capacities. This looks also interesting but it touches also
concerns of staff duty scheduling which currently are not part of the
railML domain.
Best, --Andreas.
|
|
|
|
Members
Search
Help
Login
Home
