Search results
Jump to navigation
Jump to search
- 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 reactivate7 KB (287 words) - 16:17, 13 May 2024
- 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 further523 bytes (38 words) - 21:55, 25 April 2022
- 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 further515 bytes (38 words) - 21:55, 25 April 2022
- 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 further516 bytes (38 words) - 21:55, 25 April 2022
- 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 further523 bytes (38 words) - 21:55, 25 April 2022
- 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 further525 bytes (38 words) - 21:55, 25 April 2022
- 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 further525 bytes (38 words) - 21:55, 25 April 2022
- Main Page (section Timetable and Rostering (TT))separate parts for vehicles and for train parts or complete trains possible specification of vehicle families and individual vehicles using the common features10 KB (1,041 words) - 10:56, 2 May 2024
- UC:TT:AdoptVehicleWorkingSchedulingToTimetableChanges (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)Adopt vehicle working scheduling to timetable changes; Umlauf an Jahresfahrplan anpassen The importing system holds timetable and vehicle working data2 KB (209 words) - 18:11, 27 June 2022
- TT:platformEdgeRefs TT:previousActivities TT:referencePoint TT:reserve TT:reserves TT:routeRef TT:routeRefs TT:rule TT:startPoint TT:stop:activities TT:stop:announcements3 KB (756 words) - 14:47, 27 June 2022
- UC:TT:FGIInTrain (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)Infrastructure is referenced: from <ocpTT>.ocpRef to <ocp>.id (mandatory) Rolling stock is referenced: from <formationTT>.formationRef to <formation>.id (optional)9 KB (677 words) - 18:10, 27 June 2022
- UC:TT:ATimetableForACompetition (category Use case (TT))not recommended. <vehicle>s and <formation>s If the supply of vehicles is component of the competition, often there are neither vehicles nor formations given16 KB (1,903 words) - 13:27, 13 March 2023
- UC:TT:RunTimeCalculationInput (category Use case (TT))be a sequence of vehicles, at least one vehicle. Typically, vehicles of such formations are not specific vehicles but rather vehicles of a certain type6 KB (858 words) - 12:09, 25 March 2024
- UC:TT:ExchangeOfFormationData (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)the following data: the composition of <operationalTrainSectionPart>s of <vehicle>s (using <formation>s) <validity>s of <operationalTrainVariant>s commercial6 KB (688 words) - 13:26, 13 March 2023
- UC:TT:ImportCompleteTimetableForVehicleWorkingSchedulingAndVehicleWorkings (category Use case (TT)) (section vehicle working and rostering data)Concatenation of vehicle workings to multi-day sequences of trains served by the same (abstract) vehicle depot runs vehicle standbys vehicle accounting for3 KB (355 words) - 18:11, 27 June 2022
- UC:TT:LongTermCirculationPlanning (category Use case (TT))specific vehicles to journeys is to be exchanged. Instead, an assignment based on vehicle types is to be described, whereby abstract vehicle types are6 KB (926 words) - 17:00, 4 December 2023
- Autoexport from the XML-Schema for element TT:activityTrainReverse of railML® version 3.2 UML-visualization of TT Documentation Allows to specify that the5 KB (5 words) - 21:55, 25 April 2022
- Autoexport from the XML-Schema for element TT:activityOther of railML® version 3.2 UML-visualization of TT Documentation Represents activities that cannot5 KB (5 words) - 12:43, 8 February 2024
- Autoexport from the XML-Schema for element TT:activityLoad of railML® version 3.2 UML-visualization of TT Documentation Represents (commercial) loading5 KB (5 words) - 12:43, 8 February 2024
- Autoexport from the XML-Schema for element TT:activityRollingStock of railML® version 3.2 UML-visualization of TT Documentation Allows to describe that at5 KB (5 words) - 21:55, 25 April 2022
- Autoexport from the XML-Schema for element TT:activityTripDependency of railML® version 3.2 UML-visualization of TT Documentation Allows to specify a dependency6 KB (5 words) - 12:43, 8 February 2024
- Autoexport from the XML-Schema for element TT:activityCrewDependency of railML® version 3.2 UML-visualization of TT Documentation Allows to specify a dependency7 KB (5 words) - 12:43, 8 February 2024
- Dev:TrainProtectionSystems (section On Vehicle)<vehicleSystem>ATB</vehicleSystem> <vehicleSystem>ATBEG</vehicleSystem> </validFor> </trainProtectionSystem> <trainProtectionSystemsOnVehicle>: Container for train protection11 KB (422 words) - 15:50, 16 November 2022
- UC:TT:SlotOrdering (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)Infrastructure <ocpTT> Ordered stops Rolling stock <formationTT> Loco types Weight Length Maximum speed Infrastructure restrictions As a minimum the <ocpTT> elements2 KB (273 words) - 13:26, 13 March 2023
- UC:TT:LongTermStrategicTimetabling (category Use case (TT))system-> consumers of study information (i.e. authorities) VLTP system-> VLTP vehicle rostering The frequency of this data flow is not defined by any process4 KB (523 words) - 11:14, 18 July 2022
- (orderNumber, vehicleRef, vehicleCount) vehicle (ID, name, length, speed, bruttoWeight, tareWeight/nettoWeight, bruttoAdhesion), engine (propulsion-ID, rotationMassFactor1 KB (146 words) - 13:29, 13 March 2023
- elements for motored vehicles: propulsion (voltage, frequency, power, tractiveCurrent[valueTable], totalTractEfficiency/tractiveVehicleEfficiency[valueTable]2 KB (236 words) - 13:43, 13 March 2023
- UC:TT:IntegratedTMS (category Use case (TT))<trainPartSequence> <trainPartRef> <trainPart> <formationTT> <operatingPeriodRef> <ocpsTT> <time> <sectionTT> <runTimes> <connections> <stopDescription> <stopTimes>16 KB (1,744 words) - 18:21, 13 May 2024
- REDIRECT UC:TT:ImportCompleteTimetableForVehicleWorkingSchedulingAndVehicleWorkings10 bytes (2 words) - 17:38, 24 November 2019
- REDIRECT UC:TT:AdoptVehicleWorkingSchedulingToTimetableChanges10 bytes (2 words) - 17:38, 24 November 2019
- locations and speed restrictions; and various parameters relating to the vehicle itself. Data inputs Track attributes (Infrastructure): Track Centre Line3 KB (306 words) - 13:48, 13 March 2023
- 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 to7 KB (771 words) - 13:39, 13 March 2023