Search results

Jump to navigation Jump to search

  • UC:Use cases
    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
    7 KB (287 words) - 15:43, 8 April 2024
  • TT:activityRollingStock
    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
    523 bytes (38 words) - 21:55, 25 April 2022
  • TT:activityLoad
    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
    515 bytes (38 words) - 21:55, 25 April 2022
  • TT:activityOther
    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
    516 bytes (38 words) - 21:55, 25 April 2022
  • TT:activityTrainReverse
    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
    523 bytes (38 words) - 21:55, 25 April 2022
  • TT:activityTripDependency
    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
    525 bytes (38 words) - 21:55, 25 April 2022
  • TT:activityCrewDependency
    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
    525 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 features
    10 KB (1,042 words) - 15:08, 3 April 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 data
    2 KB (209 words) - 18:11, 27 June 2022
  • Dev:Changes/3.2
    TT:platformEdgeRefs TT:previousActivities TT:referencePoint TT:reserve TT:reserves TT:routeRef TT:routeRefs TT:rule TT:startPoint TT:stop:activities TT:stop:announcements
    3 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 given
    16 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 type
    6 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 commercial
    6 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 for
    3 KB (355 words) - 18:11, 27 June 2022
  • UC:TT:TrafficManagementPlan (category Use case (TT))
    <trainPartSequence> <trainPartRef> <trainPart> <formationTT> <operatingPeriodRef> <ocpsTT> <sectionTT> <runTimes> <connections> <stopDescription> <stopTimes>
    3 KB (270 words) - 15: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 are
    6 KB (926 words) - 17:00, 4 December 2023
  • TT:activityTrainReverse/3.2
    Autoexport from the XML-Schema for element TT:activityTrainReverse of railML® version 3.2 UML-visualization of TT Documentation Allows to specify that the
    5 KB (5 words) - 21:55, 25 April 2022
  • TT:activityOther/3.2
    Autoexport from the XML-Schema for element TT:activityOther of railML® version 3.2 UML-visualization of TT Documentation Represents activities that cannot
    5 KB (5 words) - 12:43, 8 February 2024
  • TT:activityLoad/3.2
    Autoexport from the XML-Schema for element TT:activityLoad of railML® version 3.2 UML-visualization of TT Documentation Represents (commercial) loading
    5 KB (5 words) - 12:43, 8 February 2024
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)
Retrieved from "https://wiki3.railml.org/wiki/Special:Search"