Search results

Jump to navigation Jump to search
  • subschemas: IS RS  Reported by: PSI For general information on use cases see UC:Use cases
    10 bytes (691 words) - 16:12, 3 February 2020
  • UC:IS:Schematic Track Plan (category AllUseCases) (section Use case / Anwendungsfall)
    Schematic Track Plan Infrastructure managers use maps for the visualization of their railway infrastructure. These maps comprise: Geographic maps Geoschematic
    10 bytes (198 words) - 16:12, 3 February 2020
  • Standortvorbereitung für signalkontrollierte Warnsysteme An SCWS is a system used to warn working gangs on used tracks that a train is arriving and that they have to stop
    10 bytes (571 words) - 16:12, 3 February 2020
  • technologies of global optimization (ATO, ATP, timetabling…) for further possible use in practice. Our Railway laboratory has been equipped with model railway lines
    10 bytes (427 words) - 16:12, 3 February 2020
  • together especially when gathering information regarding topology. Future use case should handle integration towards 3D modelling for evaluation of e.g. sight
    10 bytes (558 words) - 16:12, 3 February 2020
  • UC:TT:TAF/TAP TSI (category AllUseCases) (section Use case / Anwendungsfall)
    this use case is the process description and the minimum data content for the timetable data exchange. The used data format is EDIFACT. The use case shall
    10 bytes (592 words) - 16:12, 3 February 2020
  • TT:connection (category AllSemcons)
    train is provided in this use case. To determine whether an attribute must be specified or can be omitted, the respective use case must be taken into account
    25 KB (3,398 words) - 20:30, 22 January 2024
  • UC:TT:TimetableInformation (category AllUseCases) (section Use case / Anwendungsfall)
    and print material as well as ticketing and real-time information. This use case will focus on the definition of the minimum requirements for passenger
    10 bytes (751 words) - 16:12, 3 February 2020
  • trainPart is in the best case redundant, if it is used as a shortcut to the commercial train number. The recommended practice is to use trainNumber only on
    12 KB (1,930 words) - 15:44, 13 May 2024
  • UC:TT:FGIInTrain (category AllUseCases) (section Use case / Anwendungsfall)
    master data for the use case "passenger information inside the train". The information from the <timetable> are data which will be used individually for every
    10 bytes (677 words) - 16:12, 3 February 2020
  • exchange format. This use case concerns the exchange of engineering data for tailoring an interlocking to fit a station. This use case focuses on "legacy"
    10 bytes (828 words) - 16:12, 3 February 2020
  • IS:speedChange (category AllSemcons)
    other standards (external link). This defines the language used for name and description. Use <additionalName> to provide a name and/or description in other
    10 KB (1,890 words) - 15:25, 25 March 2024
  • TT:blockPart (category AllSemcons)
    language used for name and description. Use <additionalName> to provide a name and/or description in other languages. begin: This is usually used only if
    12 KB (1,612 words) - 12:52, 14 May 2024
  • proposal for a railML® use case: A timetable for a competition (call for proposals) Ausschreibungsfahrplan The use case describes a timetable which is
    10 bytes (1,903 words) - 16:12, 3 February 2020
  • signalling; CAD für Zugsignalisierung Engineers of the railway signaling discipline use a Computer-Aided Design (CAD) tool to model a railway construction project
    10 bytes (127 words) - 16:12, 3 February 2020
  • UC:IS:MaintenancePlanning (category AllUseCases) (section Use case / Anwendungsfall)
    Infrastructure   Related subschemas: RS  For general information on use cases see UC:Use cases
    10 bytes (133 words) - 16:12, 3 February 2020
  • UC:IL:OperationAndControl (category AllUseCases) (section Use case / Anwendungsfall)
    interlockings has to be incorporated into the operation and control systems. They uses the interlocking to operate elements get element status schedule and manage
    10 bytes (209 words) - 16:12, 3 February 2020
  • information system. There are two types of data flows: Scenario 1: Bulk transfer of all (updated) timetable, traction and topology data: 5-6 times per year. Scenario
    10 bytes (157 words) - 16:12, 3 February 2020
  • UC:IS:NetworkStatement (category AllUseCases) (section Use case / Anwendungsfall)
    the requirements for access and use of the rail network (route network) of the infrastructure manager. It provides all the technical and operational information
    10 bytes (169 words) - 16:12, 3 February 2020
  • UC:RS:OperationalSimulation (category AllUseCases) (section Use case / Anwendungsfall)
    Rollingstock   Related subschemas: IS IL TT  For general information on use cases see UC:Use cases
    10 bytes (146 words) - 16:12, 3 February 2020
View ( | ) (20 | 50 | 100 | 250 | 500)