Search results
Jump to navigation
Jump to search
- Modelling Language (UML). Examples are solutions to use cases. CO Use Cases – IL Use Cases – IS Use Cases – RS Use Cases – TT Use Cases View/edit list on the10 bytes (287 words) - 16:31, 3 February 2020
- name>/<version number>. E.g. for element interlocking there exist the pages IL:interlocking/3.1 and IL:interlocking/3.2. Allways use Template:ElementDocu10 bytes (1,735 words) - 18:13, 5 March 2021
- UC:IL:EulynxDataPreparationInterlocking (category Use case (IL))information with signalling industry (link to IS:UC:InterlockingEngineering) The planning of the interlocking and signalling systems for individual yards is10 bytes (450 words) - 16:12, 3 February 2020
- UC:IL:InterlockingEngineering (category Use case (IL))functional behaviour of an interlocking now reflects the IM’s rulebook for interlocking. Customise, i.e. engineer, the interlocking to match individual stations10 bytes (828 words) - 16:12, 3 February 2020
- UC:IL:InterlockEngineeringForSignallingWithinJBV (category Use case (IL))Interlock engineering for signalling within JBV; Stellwerkstechnik für die Signalisierung innerhalb von JBV JBV intend to use this RailML interlocking10 bytes (558 words) - 16:12, 3 February 2020
- UC:IL:SitePreparationDataForSignalControlledWarningSystems (category Use case (IL)) (section Which specific IL data do you expect to receive/send (elements)?)data preparation of a SCWS are the topology data from the interlocking system. These interlocking data (IxL-data) describe the track-topology track-elements10 bytes (571 words) - 16:12, 3 February 2020
- UC:IL:HardwareAndCablePlan (category Use case (IL)) (section Which specific IL data do you expect to receive/send (elements)?)page is mirrored from page UC:IL:HardwareAndCablePlan in The railML® 3 wiki.10 bytes (119 words) - 16:12, 3 February 2020
- UC:IL:Simulation (category Use case (IL))internal generic interlocking (table) model. Thus this use case does not require a interlocking table. This distinguishes this IL UC from other IL UC. A route10 bytes (969 words) - 16:12, 3 February 2020
- UC:IL:OperationAndControl (category Use case (IL))the interlockings within the network are of different type and very often from different suppliers. Thus the configuration from these interlockings has10 bytes (209 words) - 16:12, 3 February 2020
- data, handing-over to the supplier (by using a database). interlocking (see also: Interlocking Engineering) This section serves to specify the required10 bytes (367 words) - 16:12, 3 February 2020
- Geometry Energy Safety system / interlocking Topology, Geometry (Location points, node-centre, node-ports), interlocking, 10 – 15 RINF parameter types for10 bytes (343 words) - 16:12, 3 February 2020
- modified data into the infrastructure manager data bases. IL This interference to interlocking relates to the visualization of routes and their attributes10 bytes (198 words) - 16:12, 3 February 2020
- Schienenanlagen railML data will be used for engineering signalling and interlocking systems. Engineers are used to working with paper plans that schematically10 bytes (383 words) - 16:12, 3 February 2020
- signalling discipline: track import, signalling import. Infrastructure + interlocking export. Generic topology information (e.g. electrification, track classification10 bytes (127 words) - 16:12, 3 February 2020
- Local operation Areas Shunting Areas Interlockings (if available in this project status) Balise groups Routes Interlockings RBCs Track layout description Points10 bytes (441 words) - 16:12, 3 February 2020
- timetable tool (Treno) and the simulation tool (Opentrack). The rest (mostly interlocking) is added manually from technical drawings. Jernbaneverket is planning10 bytes (687 words) - 16:12, 3 February 2020
- into the simulation system (currently manual) infrastructure timetable interlocking This section serves to specify the required data regarding certain aspects10 bytes (146 words) - 16:12, 3 February 2020
- Typically this is low frequency: once per study, several times per year, etc. Interlocking: -- Infrastructure: <operationalPoint> (macroscopic) Rolling stock: <formation>10 bytes (523 words) - 16:12, 3 February 2020