Search results
Jump to navigation
Jump to search
- UC:TT:ExchangeOfFormationData (category UC reported by iRFP) (section Which views are represented by the data (focus)?)(maximum speed, length and weight, driving and braking characteristics, etc.), i.e. a change of the formation data does not affect the running times nor the6 KB (688 words) - 13:26, 13 March 2023
- UC:TT:ATimetableForACompetition (category UC reported by iRFP) (section Which views are represented by the data (focus)?)corresponding infrastructure manager. This can be done by a unique attribute of the <track> elements (like code) or by a direction of the track in conjunction with16 KB (1,903 words) - 13:27, 13 March 2023
- UC:Use cases (section By category)follow our UC guideline. Generally speaking, contributions to railML® and this wiki are appreciated. For contributing use cases, please follow our UC guideline7 KB (287 words) - 15:43, 8 April 2024
- Category:UC reported by iRFP (category Use cases by company)2 members (0 subcategories, 0 files) - 17:59, 20 March 2024
- UC:TT:TrafficManagementPlan (category UC reported by Thales Germany) (section Which views are represented by the data (focus)?)stock data, used by RU and IM, usually before a train run; e.g. TPS from HaCon (external link), Viriato from SMA (external link), FBS from iRFP (external link)3 KB (270 words) - 15:11, 27 June 2022
- writer: Interautomation (17. 01. 17); reviewer: PSI Transcom and iRFP draft June 27th 2022 by User:RailML Coord Documentation TT IS, RS A timetable for a competition18 KB (0 words) - 15:53, 8 April 2024