Search results

Jump to navigation Jump to search
  • 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))
    its scope is macroscopic. Timetable period Typically there is no <timetablePeriod> for timetables of this use case. The timetable is valid not for a certain
    16 KB (1,903 words) - 13:27, 13 March 2023
  • productive use: Infrastructure (IS) and Interlocking (IL). The Timetable and Rostering (TT) and Rollingstock (RS) subschemas are in active development and
    10 KB (1,041 words) - 10:56, 2 May 2024
  • Infrastructure <ocpTT> Ordered stops Rolling stock <formationTT> Loco types Weight Length Maximum speed Infrastructure restrictions As a minimum the <ocpTT> elements
    2 KB (273 words) - 13:26, 13 March 2023
  • TT:text TT:textFragment TT:textFragments TT:textToSpeechTemplate TT:timeBasedRule TT:times TT:timetable:announcements TT:timetable:passengerTextInfos TT:timetableScenario
    3 KB (756 words) - 14:47, 27 June 2022
  • tool for short term formation planning to a timetable database, which contains data of the whole timetable period. The software for short term planning
    6 KB (688 words) - 13:26, 13 March 2023
  • UC:TT:LongTermCirculationPlanning (category Use case (TT))
    the necessary data. The basis for planning would be a timetable, or possibly even a rough timetable concept. As part of this use case, data that has been
    6 KB (926 words) - 17:00, 4 December 2023
  • UC:TT:IntegratedTMS (category Use case (TT)) (section Timetable)
    scenario the TMS will receive data from a timetable planning system. This timetable shall include all timetable objects (train missions) for a defined period
    16 KB (1,744 words) - 18:21, 13 May 2024