UC:IL:EulynxDataPreparationInterlocking
|
Description: Infrastructure Managers wish to represent their railway system in terms of standardised data types. Eulynx collects and analyses the types and attributes of objects, or track assets, that are found on Europe’s railways. The result of this analysis is a data dictionary that must fit the railML IL schema. Eulynx distinguishes conventional and ERTMS interlocking whilst recognising that there is overlap. The reason for standardising data types is 1. Exchange of asset information, e.g. with the Registry of Infrastructure (link to RINF Use Case) 2. Exchange of asset information with signalling industry (link to http://wiki.railml.org/index.php?title=IS:UC:InterlockingEngineering) The planning of the interlocking and signalling systems for individual yards is and remains within the scope of the railways. Extracts of the data set describing the yard flows to the suppliers who a) customises their signalling system to that particular yard. This is the To Build data subset. The supplier enriches or modifies the data subset according to the As Built situation. This As Build dataset then flows back to the IM who incorporates the data in his asset information system.
Rationale: ruggedize the Information Life Cycle The asset manager prepares data in a standardized format, this data is transferred to the supplier for use in the production process and delivered back in standardized format to the asset manager with enriched detail asset information Please refer to the linked use cases that cover the Eulynx use case.