Search results

to use cases. CO Use Cases – IL Use Cases – IS Use Cases – RS Use Cases – TT Use Cases View/edit list on the separate source page   If you want to reactivate

This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further

This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further

This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further

This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further

This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further

This element does not appear in railML® 3.1 within the TT subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further

separate parts for vehicles and for train parts or complete trains possible specification of vehicle families and individual vehicles using the common features

Adopt vehicle working scheduling to timetable changes; Umlauf an Jahresfahrplan anpassen The importing system holds timetable and vehicle working data

TT:platformEdgeRefs TT:previousActivities TT:referencePoint TT:reserve TT:reserves TT:routeRef TT:routeRefs TT:rule TT:startPoint TT:stop:activities TT:stop:announcements

Infrastructure is referenced: from <ocpTT>.ocpRef to <ocp>.id (mandatory) Rolling stock is referenced: from <formationTT>.formationRef to <formation>.id (optional)

not recommended. <vehicle>s and <formation>s If the supply of vehicles is component of the competition, often there are neither vehicles nor formations given

be a sequence of vehicles, at least one vehicle. Typically, vehicles of such formations are not specific vehicles but rather vehicles of a certain type

the following data: the composition of <operationalTrainSectionPart>s of <vehicle>s (using <formation>s) <validity>s of <operationalTrainVariant>s commercial

Concatenation of vehicle workings to multi-day sequences of trains served by the same (abstract) vehicle depot runs vehicle standbys vehicle accounting for

specific vehicles to journeys is to be exchanged. Instead, an assignment based on vehicle types is to be described, whereby abstract vehicle types are

Autoexport from the XML-Schema for element TT:activityTrainReverse of railML® version 3.2 UML-visualization of TT Documentation Allows to specify that the

Autoexport from the XML-Schema for element TT:activityOther of railML® version 3.2 UML-visualization of TT Documentation Represents activities that cannot

Autoexport from the XML-Schema for element TT:activityLoad of railML® version 3.2 UML-visualization of TT Documentation Represents (commercial) loading

Autoexport from the XML-Schema for element TT:activityRollingStock of railML® version 3.2 UML-visualization of TT Documentation Allows to describe that at

Autoexport from the XML-Schema for element TT:activityTripDependency of railML® version 3.2 UML-visualization of TT Documentation Allows to specify a dependency

Autoexport from the XML-Schema for element TT:activityCrewDependency of railML® version 3.2 UML-visualization of TT Documentation Allows to specify a dependency

<vehicleSystem>ATB</vehicleSystem> <vehicleSystem>ATBEG</vehicleSystem> </validFor> </trainProtectionSystem> <trainProtectionSystemsOnVehicle>: Container for train protection

Infrastructure <ocpTT> Ordered stops Rolling stock <formationTT> Loco types Weight Length Maximum speed Infrastructure restrictions As a minimum the <ocpTT> elements

system-> consumers of study information (i.e. authorities) VLTP system-> VLTP vehicle rostering The frequency of this data flow is not defined by any process

(orderNumber, vehicleRef, vehicleCount) vehicle (ID, name, length, speed, bruttoWeight, tareWeight/nettoWeight, bruttoAdhesion), engine (propulsion-ID, rotationMassFactor

elements for motored vehicles: propulsion (voltage, frequency, power, tractiveCurrent[valueTable], totalTractEfficiency/tractiveVehicleEfficiency[valueTable]

<trainPartSequence> <trainPartRef> <trainPart> <formationTT> <operatingPeriodRef> <ocpsTT> <time> <sectionTT> <runTimes> <connections> <stopDescription> <stopTimes>

REDIRECT UC:TT:ImportCompleteTimetableForVehicleWorkingSchedulingAndVehicleWorkings

REDIRECT UC:TT:AdoptVehicleWorkingSchedulingToTimetableChanges

locations and speed restrictions; and various parameters relating to the vehicle itself. Data inputs Track attributes (Infrastructure): Track Centre Line

identical formation, but in reversed order (if it has more than one vehicle) and vehicle orientation (if it is given). reversal with the engine coupled to