Search results

(sofern der Art entsprechend) Erforderliche Qualifikationen Der Use Case baut auf dem Use Case Fahrplanauskunft auf, das heißt für Dienste, die auf einer Fahrt

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

subschemas: IS RS CO Reported by: IVU For general information on use cases see UC:Use cases

This use case covers the ordering of slots by Railway Undertakings from Infrastructure Manager(s) and other managers of capacity. A related use case will

subschemas: IS RS  Reported by: PSI For general information on use cases see UC:Use cases

the infrastructure and state their validity. The infrastructure used in this use case is not based on the current infrastructure but an agreed future infrastructure

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

is envisioned for this use case is a microscopic description of the timetable. The use case is divided into three sub-use cases based on the relevant properties’

elements.) A better modelling for this aspect is, in the author’s opinion, to use the concept of commercial trains in a different way than currently described

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

data Typically, the import is done manually using a file based interface. Common Infrastructure: the import uses elements from mesoscopic and macroscopic

this use case even without reference to the timetable. This would be the case in a very early stage of planning. For the purposes of this use case, vehicle

proposal for a railML® use case: A timetable for a competition (call for proposals) Ausschreibungsfahrplan The use case describes a timetable which is

about restrictions concerning the infrastructure shall not be part of this use case ITMS. On the other hand a restriction of the infrastructure can be the

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 your inactive use case

(rolling stock schedules). A list of use cases for the railML® timetable schema can be found on page Category:Use case (TT). →Main Article: Common The Common

station, train number field, timetable element) to the next. For example, one use case is a TMS that provides the current (dispatching) timetable and train positions

status=approved. Implement a seperate semantic constraint for every rule. Use the template with all mandatory arguments according to Template:SemanticConstraint

Infrastructure   Related subschemas: IL TT RS  Reported by: ProRail For general information on use cases see UC:Use cases

Subschema: Rollingstock   Related subschemas: IS IL TT  For general information on use cases see UC:Use cases