Scheme description / Schemenbeschreibung / Description du schéma
Position of vehicle in the XML-Tree / Position von vehicle im XML-Baum / position de vehicle dans l’aborescence XML
- Parent: <vehicles>
- Children: <additionalName> (introduced with version 2.1), <classification>, <curvingLimitation>, <engine>, <loadLimitMatrix>, <maintenanceIntervals> (introduced with version 2.3), <wagon>, <vehicleBrakes>, <states> (introduced with version 2.5)
Multiplicity / Anzahl / Multiplicité
Semantics / Bedeutung / Sémantique
The element <vehicle> contains all data, which are related to a single vehicle or a vehicle family. The item is referenced via its attribute id. In case of a vehicle family all data can be stored, which are common for all vehicles of this family. The data set of a single vehicle can refer to the common values and define more or deviating characteristics valid only for this particular vehicle.
In dem Element <vehicle> werden alle Fahrzeug bezogenen Daten aufgenommen, um individuelle Fahrzeuge oder ganze Fahrzeugfamilien in informatorischer, organisatorischer, betrieblicher und technischer Hinsicht zu beschreiben. Die einzelnen Datensätze können über das Attribut id referenziert werden. Für eine Fahrzeugfamilie können die Daten einmal aufgeführt werden, die für alle Mitglieder der Familie gleich sind. Die Daten für ein Einzelfahrzeug können dann auf diesen Stand referenzieren. Die Applikation muss sicherstellen, dass bei abweichenden Daten diejenigen des Einzelfahrzeuges zur Anwendung kommen.
Attributes of vehicle / Attribute von vehicle / Attributs de vehicle
- id: XML-file-wide unique, machine-interpretable identity, required for later referencing that element internally. For a detailed explanation see Dev:identities.
XML-Datei-weit eindeutige, maschineninterpretierbare Identität, die für die spätere interne Referenzierung dieses Elements erforderlich ist. Für eine detaillierte Erklärung siehe Dev:identities.
- code (introduced with version 2.1): Machine-interpretable string (e.g. an abbreviation) used for identification of the object across exchange partners, usecase specific uniqueness constraints may apply. Please see our description of the differences between id, code and human-readable identifiers.
Maschineninterpretierbare Zeichenkette (z.B. Abkürzung), die zur Identifizierung des Objekts auch bei Austauschpartnern verwendet wird, wobei spezifische Eindeutigkeitsbeschränkungen gelten können. Bitte beachten Sie unsere Erläuterung zu den Unterschieden zwischen id, code and menschenlesbaren Kennzeichnungen.
- name: Established, human-readable short string, giving the object a name. Not intended for machine interpretation, please see our notice on human interpretable data fields.
Etablierte, menschenlesbare kurze Zeichenkette, die das Objekt benennt. Nicht zur maschinellen Interpretation bestimmt, siehe Hinweise zu menschenlesbaren Datenfeldern.
- description: Human-readable, more detailed description as addition to the name. It should give additional explanations or hints to the contents of this element. Not intended for machine interpretation, please see our notice on human interpretable data fields.
Menschenlesbare, detailliertere Beschreibung als Ergänzung zu name. Sie soll zusätzliche Erläuterungen oder Hinweise auf den Inhalt dieses Elements geben. Nicht zur maschinellen Interpretation bestimmt, siehe Hinweise zu menschenlesbaren Datenfeldern.
- xml:lang (introduced with version 2.1): This is a unique identifier of language. It uses basically the language standard IETF BCP 47 (external link) which may be different to ISO 639-1 (external link) or ISO 639-2 (external link). For mapping hints see relation to other standards (external link).
This defines the language used for name and description. Use <additionalName> to provide a name and/or description in other languages.
- vehicleFamilyRef: This refers to the id attribute of the associated <vehicle> element.
The referenced vehicle data are used as definition of common features for several vehicles.
The application has to ensure that the data of the current vehicle are formed from the referred family first. The content of the vehicle data set shall than overwrite any features with the values from the own data set. Thus the particular can have a subset of characteristics deviating from the common one of the vehicle family. In the data set of the single vehicle all values taken from the family definition can be omitted here.
- vehicleCategory (introduced with version 2.2): This is a basic categorisation of vehicle type for easy use in train formation planning. The user must ensure that the value is consistent with the vehicle data. The following values should be selected:
- coach non-driven coach for passenger use
- motorCoach passenger coach with motors for traction
- controlCabCoach coach with controlling cab at one end (might be with motors)
- motorVehicles vehicle with traction engine, not for passenger use
- freightWagon non-driven wagon used for transport of any goods
- other:anything Any value that does not fit any value from the previous enumeration list, fulfilling the constraint: at minimum two characters, whitespace is not allowed.
- axleSequence: This is the description of the vehicles axle sequence. As there a several semantics for the axle sequence in use this can be only an informative string. There is no restriction with regard to particular patterns.
- numberDrivenAxles: This is just the number of axles of the vehicle used to apply the tractive effort onto the running rails.
- numberNonDrivenAxles: This is just the number of axles of the vehicle not used for propulsion purpose.
- trackGauge: This represents the track gauge the vehicle is designed for. This optional value shall be given as decimal in metres.
At the moment not more than two values can be given per vehicle. In case of vehicles with interchangeable track gauge the value for the gauge mainly used shall be given. Additional information may be inserted in description.
- trackGaugeAlternative: This represents the alternative track gauge in case the vehicle is designed with interchangeable wheelsets. This optional value shall be given as decimal in metres.
- adjustableWheelSet: This is a flag, whether the vehicle comprises adjustable wheelsets. If 'true' the value for trackGauge and trackGaugeAlternative shall be given.
- length: This represents the length of the vehicle over couplers. This optional value shall be given as decimal in metres.
The vehicle length will be used to calculate the entire length of a formation consisting of several vehicles in order to get the needed length of tracks or platforms for this formation. The total length is also required for simulation when modelling the train as band of masses.
- speed: This is the maximum speed in kilometres per hour the vehicle is permitted to run in normal operation.
- towingSpeed: This is the maximum speed in kilometres per hour the vehicle is permitted to be towed. This applies to motored vehicles when towed by other vehicles.
- bruttoWeight: This comprises the total weight of vehicle with full payload in metric tons.
- nettoWeight: This comprises the total weight of the vehicle payload in metric tons.
- tareWeight: This comprises the total weight of the empty vehicle in metric tons.
- bruttoAdhesionWeight: This comprises the portion of total vehicle weight with full payload resting on the motored axles in metric tons. This so-called adhesion weight is used to calculate the possible tractive effort which can be transmitted onto the running rails for a fully loaded vehicle and a particular adhesion factor.
- nettoAdhesionWeight (deprecated with version 2.1): This comprises the portion of total weight of the vehicle payload resting on the motored axles in metric tons. This so-called adhesion weight is used to calculate the possible tractive effort which can be transmitted onto the running rails for a vehicle and a particular adhesion factor.
- tareAdhesionWeight: This comprises the portion of total weight of an empty vehicle resting on the motored axles in metric tons. This so-called adhesion weight is used to calculate the possible tractive effort which can be transmitted onto the running rails for an empty vehicle and a particular adhesion factor.
- axleLoad: This is the load per axle in metric tons.
- resistanceFactor: This simple value represents the running resistance of vehicle in N/kN, which may be used in conjungtion with the <trainResistance> element.
It is just a rather simple estimation for the complex physics of any vehicle's running resistance. As there are dependencies of speed which becomes dominating at higher speeds, say above 100 km/h, this values shall only be used for slow vehicles like shunting units or so. In all other cases the more detailed possibilities of the <trainResistance> element shall be used, which is defined per train as a composition of vehicles.
- onTrainHead: This is a flag, whether the vehicle may run at the train head in normal operation.
- onTrainTailOnly: This is a flag, whether the vehicle shall only run at the end of any train.
Syntactic Constraints / Syntaktische Beschränkungen / Contraintes syntactiques
- id: xs:ID, required
a string, starting with a letter (a..zA..Z) or an underscore (_),
followed by a non-colonized and non-spaced string consisting of letters, digits, points (.), dashes (-) or underscores (_)
- code: xs:string, optional
- name: xs:string, optional
- description: xs:string, optional
- xml:lang: xs:language, language identification, optional
- vehicleFamilyRef xs:IDREF, optional
- axleSequence xs:string, optional
- numberDrivenAxles xs:nonNegativeInteger, optional
- numberNonDrivenAxles xs:nonNegativeInteger, optional
- trackGauge xs:decimal, 6 fraction digits, length value measured in meter, optional
- trackGaugeAlternative xs:decimal, 6 fraction digits, length value measured in meter, optional
- adjustableWheelSet xs:boolean, optional
- length xs:decimal, 6 fraction digits, length value measured in meter, optional
- speed xs:decimal, 5 digits and 1 fraction digit with minimum value 0, speed value measured in km/h, optional
- towingSpeed xs:decimal, 5 digits and 1 fraction digit with minimum value 0, speed value measured in km/h, optional
- bruttoWeight xs:decimal, 3 fraction digits, weight value measured in metric tons, optional
- nettoWeight xs:decimal, 3 fraction digits, weight value measured in metric tons, optional
- tareWeight xs:decimal, 3 fraction digits, weight value measured in metric tons, optional
- bruttoAdhesionWeight xs:decimal, 3 fraction digits, weight value measured in metric tons, optional
- nettoAdhesionWeight xs:decimal, 3 fraction digits, weight value measured in metric tons, optional
- tareAdhesionWeight xs:decimal, 3 fraction digits, weight value measured in metric tons, optional
- axleLoad xs:decimal, 3 fraction digits, weight value measured in metric tons, optional
- resistanceFactor xs:decimal, optional
- onTrainHead xs:boolean, optional
- onTrainTailOnly xs:boolean, optional
Best practice & Examples / Empfohlene Anwendung & Beispiele / Bonnes pratiques & exemples
Especially with EMU/DMU the question arise what is "one vehicle"? Basically there are two ways of modelling:
- One vehicle is the carriage with an individual ID (number) of the operator, i.e. which is handled as an individual vehicle in asset management.
- One vehicle is the complete EMU/DMU which operates always as one carriage.
Subsequently the first variant is to be preferred whenever there is need for kind of asset management or the vehicle has to be considered for a reservation system. The discrimination which variant is used can be derived only indirect from the description or name of the vehicle vs. the ones in the formation using this vehicle.
In this example the vehicle can be modelled as five individual cars ("BMb75", "BPb75", "BCMU75", "BPa75", "BMa75") or as a single vehicle ("type 75"). In consequence the first variant would give a formation with five vehicles forming the "type 75" train. The second variant would result in a formation with only one vehicle of "type 75".
Vehicle class vs. specific vehicle
In case a single (specific) vehicle shall be described there are two <vehicle> elements needed. The first one is the description of the vehicle class with all common characteristics. The second one contains only the specific charactistics of this vehicle , e.g. vehicle register number. The relation is built with the attribute vehicleFamilyRef used in the second <vehicle> element to refer to the first <vehicle> element with the common characteristics.
Notes / Anmerkungen / Notes
Not yet described. / Noch nicht beschrieben. / Pas encore décrit.
Open issues / Offene Punkte/Pendenzen / Questions ouvertes
Not yet described. / Noch nicht beschrieben. / Pas encore décrit.