Search results
Jump to navigation
Jump to search
- UC:TT:FGIInTrain (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)least this use case needs the following elements: the elements <train> and <trainPart> to supply information about line, direction and relevant information9 KB (677 words) - 18:10, 27 June 2022
- UC:TT:ExchangeOfFormationData (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)day, the <trainPart> must be divided among several commercial trains. Practically, this means that each <trainPartSequence> of a commercial train may only6 KB (688 words) - 13:26, 13 March 2023
- UC:TT:ATimetableForACompetition (category Use case (TT))days. Each <trainPart> can refer to a different seating capacity. All these <trainPart>s have to be joined in the corresponding <trainPartSequence>s. (This16 KB (1,903 words) - 13:27, 13 March 2023
- Main Page (section Timetable and Rostering (TT))formation and operating period. The train part includes the actual information regarding the path of the train as a sequence of operation or control points10 KB (1,041 words) - 10:56, 2 May 2024
- UC:TT:TimetableInformation (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)following changes: full cancellation of a train partial cancellation - i.e. of a trainPart extra train or trainPart cancelled stop extra stop etc. Terms and5 KB (751 words) - 13:28, 13 March 2023
- TT:commercialSchedulings TT:commercialTrain TT:commercialTrainReference TT:commercialTrainSection TT:commercialTrainVariant TT:commercialTrains TT:connectionTransferTime3 KB (756 words) - 14:47, 27 June 2022
- UC:TT:RunTimeCalculationInput (category Use case (TT))& route clearance operational rules*** electrification train protection system restrictions part of railML® 3.3 (and railML® 2.5) for systems that require6 KB (858 words) - 12:09, 25 March 2024
- UC:TT:TAF/TAP TSI (category Use case (TT)) (section Which specific TT data do you expect to receive/send (elements)?)elements (e.g. trains) To be specified As a bare minimum the commercial view of a <train> can be reduced to one <trainPart> with a sequence of <ocpTT> elements4 KB (592 words) - 18:06, 7 December 2023
- UC:TT:LongTermCirculationPlanning (category Use case (TT))completed Operational train journey or part of train journey, if applicable The blocks described in this way are compiled into sequences within the framework6 KB (926 words) - 17:00, 4 December 2023
- UC:TT:IntegratedTMS (category Use case (TT))Passenger information <train> <trainPartSequence> <trainPartRef> <trainPart> <formationTT> <operatingPeriodRef> <ocpsTT> <time> <sectionTT> <runTimes> <connections>16 KB (1,744 words) - 18:21, 13 May 2024