RINF XML Data Validation Guide

Transcription

1 RINF XML Data Validation Guide RINF Document Information Date: Fri, 2014 Dec 19 Release Number: 1.1 Version: 0.5 Author(s): Reference: European Dynamics [Ref Identifier] European Railway Agency, 120, rue Marc Lefrancq, F Valenciennes, France Telephone: +33 (0) Fax: +33 (0) Website: servicedesk@era.europa.eu

2 Document History Document History Date Author Version Comment Modified Sections Mon, 2013 Nov 4 European Dynamics 0.1 Document creation All Fri, 2014 Feb 7 European Dynamics 0.2 Updates for validity end date All Wed, 2014 May 28 European Dynamics 0.3 Updates for Release 1.0 All Tue, 2014 Aug 26 European Dynamics 0.4 Updated for Release 1.1 All Fri, 2014 Dec 19 European Dynamics 0.5 Updated for Release 1.1 All Document Distribution List Date Name Position Organisation Click here to enter a date. Click here to enter a date. Click here to enter a date. 2 version

3 Table of Contents Table of Contents Document Information... 1 Document History... 2 Document Distribution List... 2 Table of Contents Introduction Explanation of an XML line for a RINF parameter Validity Dates for Future Railway Infrastructure Modifications Planning General Validation Rules ID APPLICABLE MANDATORY CAN BE REPEATED FORMAT Parameter-Specific Validation Rules version

4 Introduction 1 Introduction This document comprises an XML Data Validation Guide for the RINF Application explaining the validation rules for XML data files with specific examples per parameter. 1.1 Explanation of an XML line for a RINF parameter A typical line of an XML RINF data file like the following <SOLTrackParameter ID="IPP_SevereClimateCon" IsApplicable="Y" Value="Y" OptionalValue="Yes" /> consists of the following elements: SOLTrackParameter: This is the declaration element, i.e. the type of the RINF parameter ID: This is the XML name of the Parameter, as found in the Application Guide. IsApplicable: This is an attribute denoting the applicability of the RINF parameter Value: This is an attribute containing the value of the RINF parameter in a specified format. If the value is a lookup value, then the value is the code of the selected item from the list of values (see LookUpValuesDictionaries.xlsx). If the value is a lookup value and requires extra text such as the following parameter <SOLTrackParameter ID="IPP_LoadCap" IsApplicable="Y" Value="50 994" OptionalValue="C3 994"/>, then the value is the code (in this example 50) of the selected item from the list of values, in addition to the required text (in this example 994). Another example: <SOLTrackParameter ID="EPA_StripMaterial" IsApplicable="Y" Value= /> OptionalValue: This optional attribute is used only for readability of the XML file and more specifically in lookup values where the Value attribute stores the code of the parameter value and not the value itself. This attribute can store the full actual value of the parameter. 4 version

5 Validity Dates for Future Railway Infrastructure Modifications Planning 2 Validity Dates for Future Railway Infrastructure Modifications Planning For future planning purposes two additional dates are included: one indicating the beginning of the validity for a specific subset of data of RINF items collected from the Member States (see section 1.3 of the RINF Technical Specifications Complementary Document) and one for the expiration of the validity for a specific subset of data of RINF items. Reasons for this modification These validity dates provide the option to Member States (i.e. Infrastructure Managers) to signify when the new/updated infrastructure will come into service and to specify when the existing infrastructure is planned to be out of service, i.e. to provide information about changes or additions to the railway network that are planned for the future or to indicate planned out of service situations for maintenance etc. Proposed modification The validity dates are two optional fields available at the level of objects, i.e. for each - Operational Point - Section of Line - Track - Siding - Platform - Tunnel The validity dates can be used for announcing : - New items of railway infrastructure, e.g. a new line that will come into service, or - Updates to existing railway infrastructure, e.g. new equipment to be installed on a track or new value of the technical parameter of the line to be provided or - Planned expiration of availability. When a Member State will want to announce future changes using the Validity start date field, it will need to include 2 sub-sets of data for the particular RINF item within the uploaded RINF data set: one sub-set of data will describe the currently existing infrastructure and the other sub-set of data will describe the future changes that are planned to come into operation on the validity date. Validity date implementation - Duplicate objects with the same unique IDs but with different validity dates should be allowed in the XML and they should be processed by SSIS. - The search results grid includes two columns for Start validity date Validity start date and for End validity date Validity end date. - The search result details display the same dates above under the respective object (e.g. OP, SoL, etc.). - If for 2 or more duplicate items, no validity date exists or validity date is in the past, the validation will fail. - The map display will not display the future planning, i.e. it will not display OPs and SoLs for which o Validity start date exists, and o Validity start date was in the future at the time of the import. - The map will display items that: o Were active at the time of the import o The validity end date is in the future. - The implementation of the validation mechanism will be based on the following assumptions: version

6 Validity Dates for Future Railway Infrastructure Modifications Planning o o o Any object with no validity start date or with validity start date set in the past will be accepted. If an object has both validity start date and validity end date, then the validity start date must be before the validity end date. Objects with validity end date set in the past are not accepted. 6 version

7 General Validation Rules 3 General Validation Rules In this chapter, the validation rules that apply for all RINF parameters are presented. Furthermore, examples are provided that show how RINF parameters should be expressed in an XML data file. The following table shows whether a value must be provided for a parameter in the xml file. More details are described below. MANDATORY APPLICABLE PRESENT IN XML VALUE YES N MUST_BE_PRESENT VALUE_ATTRIBUTE_NOT_REQUIRED YES Y MUST_BE_PRESENT VALID_VALUE MUST_BE_PRESENT YES NYA VALUE_ATTRIBUTE_NOT_REQUIRED NO Y OPTIONAL VALID_VALUE_IF_PRESENT NO N OPTIONAL VALUE_ATTRIBUTE_NOT_REQUIRED IF_PRESENT NO NYA OPTIONAL VALUE_ATTRIBUTE_NOT_REQUIRED IF_PRESENT 3.1 ID XML elements contain a required ID attribute (except for the key elements like OPs, SoLs, and Tracks). Using this ID, the Validation and Import modules map the data of the XML element to the respective RINF Items and data tables. Example of an element without the ID attribute: <OPTrack ValidityDateStart=" " ValidityDateEnd=" "> In the above example, the OPTrack element does not have the ID attribute because it is the name of the element (OPTrack). Elements like this do not require the ID attribute. Example of an element with the ID attribute: <OPTrackParameter ID="ILL_InteropGauge" IsApplicable="Y" Value="10" OptionalValue="GA" /> <OPTrackParameter ID="ILL_MultiNatGauge" IsApplicable="Y" Value="30" OptionalValue="GB2" /> In this case, the provided OPTrackParameter elements have different IDs. A two-step validation is performed: The XSD validation ensures that OPTrackParameter elements can only be defined inside an OPTrack element. The RINF Validation module will only use the OPTrackParameter elements which contain IDs that are expected (IDs like SOL Track Parameter ILL_InteropGauge, SOL Track Parameter ILL_MultiNatGauge ). version

8 General Validation Rules 3.2 APPLICABLE When an XML data file is submitted for validation and a not applicable parameter is included, the RINF application will detect the redundant parameter and specify it in the validation error popup dialog. In order to define the applicability of a parameter, Y, N or NYA values are used, as shown in the next examples. NYA is used when the applicability is not yet available and the application Validation module should accept this parameter without validation. In case of N and NYA the value attribute is not required. Example of applicability definition in an XML data file: <OPTrackParameter ID="IPP_LineCat" IsApplicable="Y" Value="60" OptionalValue="P6"/> Example of non-applicability definition in an XML data file: <OPTrackTunnelParameter ID="ITU_NatFireCatReq" IsApplicable="N" /> Example of not yet available applicability definition in an XML data file: <OPTrackParameter ID="ILL_InteropGauge" IsApplicable="NYA" /> In case the Application Guide does not include the Applicable section for a parameter, the parameter is considered Applicable and should always be provided with IsApplicable= Y. 3.3 MANDATORY When an XML data file is submitted for validation and a mandatory parameter is not included, the RINF application will detect the missing parameter and specify it in the validation error popup dialog. If a parameter is mandatory, it should be contained in the XML data file. If it is not contained, the RINF application will detect the missing mandatory parameter and log the error which will also be displayed in the validation error popup dialog. 3.4 CAN BE REPEATED When an XML data file is submitted for validation and a parameter that cannot be repeated is included more than once, the RINF application will detect the multiple parameters and specify them in the validation error popup dialog. If a parameter can be repeated, it will exist in the XML data file as follows: Example of parameter that can be repeated in an XML data file: <OPTrackParameter ID="ITP_NomGauge" IsApplicable="Y" Value="10" /> <OPTrackParameter ID="ITP_NomGauge" IsApplicable="Y" Value="20" /> 3.5 FORMAT When an XML data file is submitted for validation and the format of a parameter is different than the one specified in the Application Guide, the RINF application will detect it and specify it in the validation error popup dialog. The most common validation formats in the Application are: Numeric: The definition of numeric formats is: o One or more N characters. The number of N characters indicates the maximum number of integral digits that can be provided, e.g. NNN represents a number in the range of [0, 999]. 8 version

9 General Validation Rules o o (Optional) The decimal separator., followed by one or more N characters: The number of N characters indicate the maximum number of decimal digits that can be provided, e.g..nnn will allow up to 3 decimal digits (from [0 to.999]. Note: The opening and closing brackets [ and ] are only provided for readability reasons in the Application Guide and should NOT be included in the actual XML values. Character string: No restriction is defined on the input value by the Application Guide. If the length of the string is not restricted by the Application Guide, the maximum permitted length in the XSD is 450 characters. Single selection from the predefined list: A list of values is provided in the Application Guide. The RINF Validation will only accept the values of that list. More specific examples for format validation rules are following in the next chapter. version

10 4 Parameter-Specific Validation Rules A detailed list of the RINF parameters is presented below, accompanied with examples and explanations of specific validation mechanisms. 1 MEMBER STATE Format Example: <MemberStateCode Code="EL" Version="1.12" /> Validation: The Code field of the Member State must be equal to the Member State Code of the NRE who uploaded the file. 1.1 SECTION OF LINE Format Example: <SectionOfLine ValidityDateStart=" " ValidityDateEnd=" "> Validation: If ValidityDateStart is greater than the date of the validation, the Section of Line will be considered a FUTURE planning; otherwise, it is considered a CURRENT item IM Code Format Example: <SOLIMCode Value="1234" /> Validation: No verification will be done by CUI. The check of the link between MS and IM s Code must be done nationally National line identification Format Example: <SOLLineIdentification Value="ELLine0001" /> Validation: No special validation rules apply. Check shall be done nationally Operational Point at start of Section of Line Format Example: <SOLOPStart Value="EL00001" /> Validation: OP ID must exist in the MS file of RINF. The value of this parameter must be different from No validation will be performed by CUI regarding which is the start and which the end OP. Check shall be done nationally Operational Point at end of Section of Line Format Example: <SOLOPEnd Value="EL00002" /> Validation: OP ID must exist in the MS file of RINF. The value of this parameter must be different from No validation will be performed by CUI regarding which is the start and which the end OP. Check shall be done nationally Length of section of line Format Example: <SOLLength Value=" " /> 10 version

11 Validation: Regarding the correctness of the length of SoL, no validation will be performed by CUI. Check shall be done nationally. However, any number outside the boundaries defined in the Application Guide will result in the Nature of Section of Line Format Example: <SOLNature Value="10" OptionalValue="Regular SoL" /> Validation: If the user selects the Link value, then for all tracks belonging to this SoL, all the parameters of the following groups of parameters will not be applicable: Infrastructure subsystem Energy subsystem Control-command and signalling subsystem RUNNING TRACK Format Example: <SOLTrack ValidityDateEnd=" "> Validation: If ValidityDateStart is greater than the date of the validation, the SOL Track will be considered a FUTURE planning; otherwise, it is considered a CURRENT item. Mandatory: Y Identification of track Format Example: <SOLTrackIdentification Value="TRXDD11" /> Validation: No validation will be performed by CUI. The uniqueness of track ID shall be checked nationally Normal running direction Format Example: <SOLTrackDirection Value="10" /> EC declaration of verification for track (INF) Applicability: Not applicable when track is not included in geographical scope of the TSI Format Example: <SOLTrackParameter ID="IDE_ECVerification" IsApplicable="Y" Value="EL/ ASDVG/2012/000001"/> Validation: The following validations will be performed by the system: The number of characters and the slashes must be provided in the following manner: [CC/RRRRRRRRRRRRRR/YYYY/NNNNNN] The YYYY characters must be a number in between The NNNNNN characters must be digits EI declaration of demonstration for track (INF) Format Example: <SOLTrackParameter ID="IDE_EIDemonstration" IsApplicable="Y" Value="EL/ ASDVG/2012/003001"/> Validation: The following validations will be performed by the system: version

12 The number of characters and the slashes must be provided in the following manner: [CC/RRRRRRRRRRRRRR/YYYY/NNNNNN] The YYYY characters must be a number in between The NNNNNN characters must be digits TEN classification of track Format Example: <SOLTrackParameter ID="IPP_TENClass" IsApplicable="Y" Value="10"/> Category of Line Format Example: <SOLTrackParameter ID="IPP_LineCat" IsApplicable="Y" Value="10"/> Part of a Railway Freight Corridor Format Example: <SOLTrackParameter ID="IPP_FreightCorridor" IsApplicable="Y" Value="10"/> Load capability Format Example: <SOLTrackParameter ID="IPP_LoadCap" IsApplicable="Y" Value="40 12" OptionalValue="C2 12"/> Maximum permitted speed Format Example: <SOLTrackParameter ID="IPP_MaxSpeed" IsApplicable="Y" Value="351"> Temperature range Format Example: <SOLTrackParameter ID="IPP_TempRange" IsApplicable="Y" Value="30" OptionalValue="T3 (-25 to +45)"/> Maximum altitude Format Example: <SOLTrackParameter ID="IPP_MaxAltitude" IsApplicable="Y" Value="+0123"/> Existence of severe climatic conditions 12 version

13 Format Example: <SOLTrackParameter ID="IPP_SevereClimateCon" IsApplicable="Y" Value="Y"/> Interoperable gauge Format Example: <SOLTrackParameter ID="ILL_InteropGauge" IsApplicable="Y" Value="10"/> Multinational gauges Applicability: Only if none is selected in parameter Format Example: <SOLTrackParameter ID="ILL_MultiNatGauge" IsApplicable="N" /> National gauges Applicability: Only if none is selected in parameter Format Example: <SOLTrackParameter ID="ILL_NatGauge" IsApplicable="N"/> Standard combined transport profile number for swap bodies Applicability: Only when the track belongs to route for combined transport Format Example: <SOLTrackParameter ID="ILL_ProfileNumSwapBodies" IsApplicable="Y" Value="10" OptionalValue="C 22" /> Standard combined transport profile number for semi-trailers Applicability: Only when the track belongs to route for combined transport Format Example: <SOLTrackParameter ID="ILL_ProfileNumSemiTrailers" IsApplicable="Y" Value="130" OptionalValue="P 341"/> Gradient profile Format Example: <SOLTrackParameter ID="ILL_GradProfile" IsApplicable="Y" Value="+11.2"/> corresponding error message in the RINF validation (maximum number of digits up to 1000) Minimum radius of horizontal curve version

14 Format Example: <SOLTrackParameter ID="ILL_MinRadHorzCurve" IsApplicable="Y" Value="426"/> Nominal track gauge Format Example: <SOLTrackParameter ID="ITP_NomGauge" IsApplicable="Y" Value="20"/> Cant deficiency Format Example: <SOLTrackParameter ID="ITP_CantDeficiency" IsApplicable="Y" Value="+153"/> Rail inclination Format Example: <SOLTrackParameter ID="ITP_RailInclination" IsApplicable="Y" Value="20"/> Existence of ballast Applicability: Only for tracks with permitted speed (parameter ) of more than 200 km/h. Format Example: <SOLTrackParameter ID="ITP_Ballast" IsApplicable="Y" Value="Y"/> TSI compliance of in service values for switches and crossings Format Example: <SOLTrackParameter ID="ISC_TSISwitchCrossing" IsApplicable="Y" Value="N"/> Minimum wheel diameter for fixed obtuse crossings Format Example: <SOLTrackParameter ID="ISC_MinWheelDiaFixObtuseCrossings" IsApplicable="Y" Value="443"/> Maximum train deceleration Applicability: Not applicable when specific track is the part of the line which is not in the scope of the TSI Format Example: < <SOLTrackParameter ID="ILR_MaxDeceleration" IsApplicable="Y" Value="2.5"/> 14 version

15 Use of eddy current brakes Format Example: <SOLTrackParameter ID="ILR_EddyCurrentBrakes" IsApplicable="Y" Value="10"/> Use of magnetic brakes Format Example: <SOLTrackParameter ID="ILR_MagneticBrakes" IsApplicable="Y" Value="10"/> Use of flange lubrication forbidden Format Example: <SOLTrackParameter ID="IHS_FlangeLubeForbidden" IsApplicable="Y" Value="Y"/> Existence of level crossings Format Example: <SOLTrackParameter ID="IHS_LevelCrossing" IsApplicable="Y" Value="Y"/> Acceleration allowed at level crossing Applicability: Applicable only when selected value of parameter is Y Format Example: <SOLTrackParameter ID="IHS_AccelerationLevelCrossing" IsApplicable="Y" Value="0.1"/> Tunnel Format Example: <SOLTunnel ValidityDateStart=" " ValidityDateEnd=" "> Validation: If ValidityDateStart is greater than the date of the validation, the SOL Tunnel will be considered a FUTURE planning; otherwise, it is considered a CURRENT item IM s Code Applicability: N (if tunnel does not exist) Format Example: <SOLTunnelIMCode Value="1234" /> Validation: No verification will be done by CUI. The check of the link between MS and IM s Code must be done nationally Tunnel identification Format Example: <SOLTunnelIdentification Value="000001" /> version

16 Validation: No special validation rules apply. Check shall be done nationally Start of tunnel Format Example: <SOLTunnelStart Latitude=" " Longitude=" " Kilometer=" " /> End of tunnel Format Example: <SOLTunnelEnd Latitude=" " Longitude=" " Kilometer=" " /> EC declaration of verification for tunnel (SRT) Applicability: Y shall be selected in case when EC declaration was issued Format Example: <SOLTunnelParameter ID="ITU_ECVerification" IsApplicable="Y" Value="EL/ ASDVG/2012/000003" /> Validation: The following validations will be performed by the system: The number of characters and the slashes must be provided in the following manner: [CC/RRRRRRRRRRRRRR/YYYY/NNNNNN] The YYYY characters must be a number in between The NNNNNN characters must be digits EI declaration of demonstration for tunnel (SRT) Applicability: Y shall be selected in case when the demonstration was executed and EI declaration was issued Format Example: <SOLTunnelParameter ID="ITU_EIDemonstration" IsApplicable="Y" Value="EL/4361FRWS1ASDVG/2013/000002" /> Validation: The following validations will be performed by the system: The number of characters and the slashes must be provided in the following manner: [CC/RRRRRRRRRRRRRR/YYYY/NNNNNN] The YYYY characters must be a number in between The NNNNNN characters must be digits Length of tunnel Applicability: Only for a tunnel with length of 100 meters or more, otherwise it is optional. Format Example: <SOLTunnelParameter ID="ITU_Length" IsApplicable="Y" Value="1230" /> Cross section area 16 version

17 Format Example: <SOLTunnelParameter ID="ITU_CrossSectionArea" IsApplicable="Y" Value="27" /> Existence of emergency plan Format Example: <SOLTunnelParameter ID="ITU_EmergencyPlan" IsApplicable="Y" Value="N" /> Fire category of rolling stock required Applicability: Not applicable shall be selected for short tunnels of less than 1 km, as for them the fire category according SRT TSI does not exist. Format Example: <SOLTunnelParameter ID="ITU_FireCatReq" IsApplicable="Y" Value="10" /> National fire category of rolling stock required Applicability: N =not applicable shall be selected when respective national rules do not exist Y only for tunnels when for the parameter the option none was selected. Format Example: <SOLTunnelParameter ID="ITU_NatFireCatReq" IsApplicable="N" /> Validation: No special validation rules apply. Check shall be done nationally EC declaration of verification for track (ENE) Applicability: Y shall be selected in case when EC declaration was issued Format Example: <SOLTrackParameter ID="EDE_ECVerification" IsApplicable="Y" Value="EL/ ASDVG/2012/000004"/> Validation: The following validations will be performed by the system: The number of characters and the slashes must be provided in the following manner: [CC/RRRRRRRRRRRRRR/YYYY/NNNNNN] The YYYY characters must be a number in between The NNNNNN characters must be digits EI declaration of demonstration for track (ENE) Applicability: Y shall be selected in case when the demonstration was executed and EI declaration was issued Format Example: <SOLTrackParameter ID="EDE_EIDemonstration" IsApplicable="Y" Value="EL/4361FRWS1ASDVG/2013/000002"/> Validation: The following validations will be performed by the system: version

18 The number of characters and the slashes must be provided in the following manner: [CC/RRRRRRRRRRRRRR/YYYY/NNNNNN] The YYYY characters must be a number in between The NNNNNN characters must be digits Type of contact line system Format Example: <SOLTrackParameter ID="ECS_SystemType" IsApplicable="Y" Value="20"/> Energy supply system (Voltage and frequency) Applicability: When "not electrified" is chosen in parameter , then this parameter is not applicable. Format Example: <SOLTrackParameter ID="ECS_VoltFreq" IsApplicable="Y" Value="30"/> Maximum train current Applicability: When "not electrified" is chosen in parameter , then this parameter is not applicable. Format Example: <SOLTrackParameter ID="ECS_MaxTrainCurrent" IsApplicable="N" /> Maximum current at standstill per pantograph Applicability: This parameter is applicable ( Y ) only if Overhead contact line (OCL) is selected for parameter and if DC system is selected in Format Example: <SOLTrackParameter ID="ECS_MaxStandstillCurrent" IsApplicable="Y" Value="175"/> Permission for regenerative braking Applicability: When "not electrified" is chosen in parameter , then this parameter is not applicable Format Example: <SOLTrackParameter ID="ECS_RegenerativeBraking" IsApplicable="Y" Value="N"/> Maximum contact wire height 18 version

19 Applicability: This parameter is applicable ( Y ) only if Overhead contact line (OCL) is selected in Format Example: <SOLTrackParameter ID="ECS_MaxWireHeight" IsApplicable="N" /> Minimum contact wire height Applicability: This parameter is applicable ( Y ) only if Overhead contact line (OCL) is selected in Format Example: <SOLTrackParameter ID="ECS_MinWireHeight" IsApplicable="N" /> Accepted TSI compliant pantograph heads Applicability: This parameter is applicable ( Y ) only if Overhead contact line (OCL) is selected for It is not applicable ( N") if there is no contact line. Format Example: <SOLTrackParameter ID="EPA_TSIHeads" IsApplicable="N" /> Accepted other pantograph heads Applicability: This parameter is applicable ( Y ) only if Overhead contact line (OCL) is selected in Format Example: <SOLTrackParameter ID="EPA_OtherHeads" IsApplicable="N"/> Requirements for number of raised pantographs and spacing between them, at the given speed Applicability: This parameter is applicable ( Y ) only if Overhead contact line (OCL) is selected in <SOLTrackParameter ID="EPA_NumRaisedSpeed" IsApplicable="N" /> Permitted contact strip material Applicability: This parameter is applicable ( Y ) only if Overhead contact line (OCL) is selected in Format Example: <SOLTrackParameter ID="EPA_StripMaterial" IsApplicable="Y" Value= /> version

20 Note that for the impregnated carbon ([NN] % of metallic content) option, any number outside the boundaries defined in the Application Guide will result in the Phase separation Applicability: This parameter is applicable ( Y ) only if Overhead contact line (OCL) is selected in Format Example: <SOLTrackParameter ID="EOS_Phase" IsApplicable="N" /> Information on phase separation Applicability: Applicable when in parameter selected option is Y Format Example: <SOLTrackParameter ID="EOS_InfoPhase" IsApplicable="Y" Value="length switch off breaker Y + lower pantograph Y"/> Validation: Invalid input will mean a value for Length outside the boundaries defined in the Application Guide or any value that is not defined in the pre-defined list in the Application Guide for "Switch off breaker or Lower pantograph System separation Applicability: This parameter is applicable ( Y ) only if the value Overhead contact line (OCL) is selected for Format Example: <SOLTrackParameter ID="EOS_System" IsApplicable="N" /> Information on system separation Applicability: Selection Y =yes when in parameter selected option is Y. Format Example: <SOLTrackParameter ID="EOS_InfoSystem" IsApplicable="Y" Value="length switch off breaker Y + lower pantograph Y + change supply system N"/> Validation: Invalid input will mean a value for Length outside the boundaries defined in the Application Guide or any value that is not defined in the pre-defined list of the Application Guide for "Switch off breaker or Lower pantograph or Change supply system Current or power limitation on board required Applicability: When "not electrified" is chosen in parameter , then this parameter is not applicable selection N. Format Example: <SOLTrackParameter ID="ERS_PowerLimitOnBoard" IsApplicable="Y" Value="N"/> 20 version

21 Contact force permitted Applicability: This parameter is applicable ( Y ) only if the value Overhead contact line (OCL) is selected for Format Example: <SOLTrackParameter ID="ERS_ContactForce" IsApplicable="N" /> Validation: No special validation rules apply. Check shall be done nationally Automatic dropping device required Applicability: This parameter is applicable ( Y ) only if the value Overhead contact line (OCL) is selected for Format Example: <SOLTrackParameter ID="ERS_AutoDropRequired" IsApplicable="N" /> EC declaration of verification for track (CCS) Applicability: Y shall be selected in case when EC declaration was issued Format Example: <SOLTrackParameter ID="CDE_ECVerification" IsApplicable="N" /> Validation: The following validations will be performed by the system: The number of characters and the slashes must be provided in the following manner: [CC/RRRRRRRRRRRRRR/YYYY/NNNNNN] The YYYY characters must be a number in between The NNNNNN characters must be digits ETCS level Format Example: <SOLTrackParameter ID="CPE_Level" IsApplicable="Y" Value="30"/> ETCS baseline Applicability: Not applicable ( N ) when selected value for is N. Format Example: <SOLTrackParameter ID="CPE_Baseline" IsApplicable="Y" Value="20"/> ETCS infill necessary for line access Applicability: Only applicable when selected value for is 1. version

22 Format Example: <SOLTrackParameter ID="CPE_Infill" IsApplicable="Y" Value="N"/> ETCS infill installed lineside Applicability: Only applicable when selected value for is 1. Format Example: <SOLTrackParameter ID="CPE_InfillLineSide" IsApplicable="Y" Value="10"/> ETCS national application implemented Applicability: Not applicable N when selected value for is N. Format Example: <SOLTrackParameter ID="CPE_NatApplication" IsApplicable="Y" Value="N"/> Existence of operating restrictions or conditions Applicability: Not applicable N when selected value for is N. Format Example: <SOLTrackParameter ID="CPE_RestrictionsConditions" IsApplicable="Y" Value="N"/> Optional ETCS functions Applicability: Not applicable N when selected value for is N. Format Example: <SOLTrackParameter ID="CPE_OptionalFunctions" IsApplicable="Y" Value="test"/> Validation: No special validation rules apply. Check shall be done nationally GSM-R version Format Example: <SOLTrackParameter ID="CRG_Version" IsApplicable="Y" Value="40"/> Advised number of active GSM-R mobiles (EDOR) on-board for ETCS Level 2 (or level 3) Applicability: Applicable only when level 2 or 3 is selected for parameter Format Example: <SOLTrackParameter ID="CRG_NumActiveMob" IsApplicable="Y" Value="20"/> 22 version

23 Optional GSM-R functions Applicability: Not applicable ( N ) when none is selected in parameter Format Example: <SOLTrackParameter ID="CRG_OptionalFunctions" IsApplicable="Y" Value="10"/> Existence of train detection system fully compliant with the TSI Format Example: <SOLTrackParameter ID="CCD_TSITrainDetection" IsApplicable="Y" Value="N"/> Existence of other train protection, control and warning systems installed Applicability: Y in case when for the selected option is N. Format Example: < <SOLTrackParameter ID="CPO_Installed" IsApplicable="Y" Value="N"/> Need for more than one train protection, control and warning system required on-board Applicability: Y in case when for the selected option is N Format Example: <SOLTrackParameter ID="CPO_MultipleRequired" IsApplicable="Y" Value="N"/> Other radio systems installed Applicability: Y when for the parameter it was selected none. Format Example: <SOLTrackParameter ID="CRS_Installed" IsApplicable="N" /> Type of train detection system Format Example: <SOLTrackParameter ID="CTD_DetectionSystem" IsApplicable="Y" Value="10"/> TSI compliance of maximum permitted distance between two consecutive axles version

24 Format Example: <SOLTrackParameter ID="CTD_TSIMaxDistConsecutiveAxles" IsApplicable="Y" Value="20"/> Maximum permitted distance between two consecutive axles in case of TSI non-compliance Applicability: Applicable ( Y ) when in selected option is TSI not compliant Format Example: <SOLTrackParameter ID="CTD_MaxDistConsecutiveAxles" IsApplicable="Y" Value="123"/> Minimum permitted distance between two consecutive axles Applicability: Applicable ( Y ) when parameter the selected option is wheel detector Format Example: <SOLTrackParameter ID="CTD_MinDistConsecutiveAxles" IsApplicable="Y" Value="3325"/> Minimum permitted distance between first and last axle Applicability: Applicable ( Y ) only when for parameter the selected option is track circuits. Format Example: <SOLTrackParameter ID="CTD_MinDistFirstLastAxles" IsApplicable="Y" Value="12"/> Maximum distance between end of train and first axle Applicability: Applicable ( Y ) only when for parameter the selected option is track circuits or wheel detector. Format Example: <SOLTrackParameter ID="CTD_MaxDistEndTrainFirstAxle" IsApplicable="Y" Value="321"/> Minimum permitted width of the rim Applicability: Applicable ( Y ) only when for parameter the selected option is wheel detector. Format Example: <SOLTrackParameter ID="CTD_MinRimWidth" IsApplicable="Y" Value="11"/> 24 version

25 Minimum permitted wheel diameter Applicability: Applicable ( Y ) only when for parameter the selected option is wheel detector. Format Example: <SOLTrackParameter ID="CTD_MinWheelDiameter" IsApplicable="Y" Value="96"/> Minimum permitted thickness of the flange Applicability: Applicable ( Y ) only when for parameter the selected option is wheel detector. Format Example: <SOLTrackParameter ID="CTD_MinFlangeThickness" IsApplicable="Y" Value="56.2"/> Minimum permitted height of the flange Applicability: Applicable ( Y ) only when for parameter the selected option is wheel detector. Format Example: <SOLTrackParameter ID="CTD_MinFlangeHeight" IsApplicable="Y" Value="33.8"/> Maximum permitted height of the flange Applicability: Applicable ( Y ) only when for parameter the selected option is wheel detector. Format Example: <SOLTrackParameter ID="CTD_MaxFlangeHeight" IsApplicable="Y" Value="73.7"/> Minimum permitted axle load Applicability: Applicable ( Y ) only when for parameter the selected option is track circuit or wheel detector. Format Example: <SOLTrackParameter ID="CTD_MinAxleLoad" IsApplicable="Y" Value="5.9"/> TSI compliance of rules for metal-free space around wheels Applicability: Applicable ( Y ) only when for parameter the selected option is wheel detector. Format Example: <SOLTrackParameter ID="CTD_TSIMetalFree" IsApplicable="Y" Value="10"/> version

26 TSI compliance of rules for vehicle metal construction Applicability: Applicable ( Y ) only when for parameter the selected option is loop. Format Example: <SOLTrackParameter ID="CTD_TSIMetalConstruction" IsApplicable="Y" Value="10"/> TSI compliance of Ferromagnetic characteristics of wheel material required Applicability: Applicable ( Y ) only when for parameter the selected option is wheel detector. Format Example: <SOLTrackParameter ID="CTD_TSIFerroWheelMat" IsApplicable="Y" Value="20"/> TSI compliance of maximum permitted impedance between opposite wheels of a wheelset Applicability: Applicable ( Y ) only when for parameter the selected option is track circuit. Format Example: <SOLTrackParameter ID="CTD_TSIMaxImpedanceWheelset" IsApplicable="Y" Value="20"/> Maximum permitted impedance between opposite wheels of a wheelset when not TSI compliant Applicability: Applicable ( Y ) only when for parameter the selected option is TSI not compliant Format Example: <SOLTrackParameter ID="CTD_MaxImpedanceWheelset" IsApplicable="Y" Value="1.598"/> TSI compliance of sanding Applicability: Applicable ( Y ) only when for parameter the selected option is track circuit and when selection for parameter is Y. Format Example: <SOLTrackParameter ID="CTD_TSISand" IsApplicable="Y" Value="20"/> Maximum sanding output Applicability: Applicable ( Y ) when for parameter selected option is TSI not compliant 26 version

27 Format Example: <SOLTrackParameter ID="CTD_MaxSandOutput" IsApplicable="Y" Value="834"/> Sanding override by driver required Applicability: Applicable ( Y ) only when for parameter the selected option is track circuit. Format Example: <SOLTrackParameter ID="CTD_SandDriverOverride" IsApplicable="Y" Value="Y"/> TSI Compliance of rules on sand characteristics Applicability: Applicable ( Y ) only when for parameter the selected option is track circuit. Format Example: <SOLTrackParameter ID="CTD_TSISandCharacteristics" IsApplicable="Y" Value="20"/> Existence of rules on on-board flange lubrication Applicability: Applicable ( Y ) only when for parameter the selected option is track circuit. Format Example: <SOLTrackParameter ID="CTD_FlangeLubeRules" IsApplicable="Y" Value="N"/> TSI compliance of rules on the use of composite brake blocks Applicability: Applicable ( Y ) only when for parameter the selected option is track circuit. Format Example: <SOLTrackParameter ID="CTD_TSICompositeBrakeBlocks" IsApplicable="Y" Value="20"/> TSI compliance of rules on shunt assisting devices Applicability: Applicable ( Y ) only when for parameter the selected option is track circuit. Format Example: <SOLTrackParameter ID="CTD_TSIShuntDevices" IsApplicable="Y" Value="20"/> TSI compliance of rules on combination of RST characteristics influencing shunting impedance Applicability: Applicable ( Y ) only when for parameter the selected option is track circuit. version

28 Format Example: < <SOLTrackParameter ID="CTD_TSIRSTShuntImpedance" IsApplicable="Y" Value="20"/> Existence of switch over between different protection, control and warning systems Applicability: Applicable ( Y ) when at least two different protection, control and warning systems exist Format Example: SOLTrackParameter ID="CTS_SwitchProtectControlWarn" IsApplicable="Y" Value="Y"/> Existence of switch over between different radio systems Applicability: Applicable ( Y ) when at least two different radio systems exist Format Example: <SOLTrackParameter ID="CTS_SwitchRadioSystem" IsApplicable="Y" Value="Y"/> Existence and TSI compliance of rules for magnetic fields emitted by a vehicle Applicability: Applicable ( Y ) only when for parameter the selected option is wheel detector. Format Example: <SOLTrackParameter ID="CEI_TSIMagneticFields" IsApplicable="Y" Value="20"/> Existence and TSI compliance of limits in harmonics in the traction current of vehicles Applicability: Applicable ( Y ) only when for parameter the selected option is wheel detector or track circuit. Format Example: <SOLTrackParameter ID="CEI_TSITractionHarmonics" IsApplicable="Y" Value="20"/> ETCS level for degraded situation Applicability: N =not applicable shall be selected when ETCS is not installed (selection of parameter is no ). Format Example: <SOLTrackParameter ID="CLD_ETCSSituation" IsApplicable="Y" Value="30"/> Other train protection, control and warning systems for degraded situation 28 version

29 Applicability: Y in case when for parameter was selected none. Format Example: <SOLTrackParameter ID="CLD_OtherProtectControlWarn" IsApplicable="N" /> Maximum braking distance requested Format Example: <SOLTrackParameter ID="CBP_MaxBrakeDist" IsApplicable="Y" Value="4326"/> Tilting supported Applicability: N =not applicable shall be selected when ETCS is not installed (selection in parameter is no ). Format Example: <SOLTrackParameter ID="COP_Tilting" IsApplicable="Y" Value="N"/> 1.2 OPERATIONAL POINT Format Example: <OperationalPoint ValidityDateStart=" " ValidityDateEnd=" "> Validation: If ValidityDateStart is greater than the date of the validation, the Operational Point will be considered a FUTURE planning; otherwise, it is considered a CURRENT item Name of Operational Point Format Example: <OPName Value="ELOP1" /> Validation: No special validation rules apply. Check shall be done nationally Unique OP ID Format Example: <UniqueOPID Value="EL00001" /> Validation: The provided OP ID must be unique within each Member State. This ID is composed of the country code and an alphanumeric OP code [AA+AAAAA]. The first part AA is the country code in two-letter system of ISO; this must match the country indicated by parameter 1 (Member State). The second part AAAAA is alphanumeric OP code within the MS OP TAF TAP primary code Applicability: Y in case when OP TAF TAP primary code exists, otherwise N Format Example: <OPTafTapCode IsApplicable="Y" Value="XX0002" /> Validation: No special validation rules apply. Check shall be done nationally. version

30 Type of Operational Point Format Example: <OPType Value="120" OptionalValue="switch"/> Geographical location of Operational Point Format Example: <OPGeographicLocation Longitude=" " Latitude=" " /> Railway location of Operational Point Format Example: <OPRailwayLocation Kilometer=" " NationalIdentNum="ELLine0001" /> RUNNING TRACK Format Example: <OPTrack ValidityDateStart=" " ValidityDateEnd=" "> Validation: If ValidityDateStart is greater than the date of the validation, the OP Track will be considered a FUTURE planning; otherwise, it is considered a CURRENT item. Mandatory: N IM s Code Format Example: <OPTrackIMCode Value="1234" /> Validation: No verification is done by CUI. Check of the link between MS and IM s Code must be done nationally Identification of track Format Example: <OPTrackIdentification Value="TRXDD12" /> Validation: No validation will be performed by CUI. The uniqueness of track ID shall be checked nationally EC declaration of verification for track (INF) Applicability: Y shall be selected in case when EC declaration was issued Format Example: <OPTrackParameter ID="IDE_ECVerification" IsApplicable="Y" Value="EL/ ASDVG/2012/000090" /> Validation: The following validations will be performed by the system: The number of characters and the slashes must be provided in the following manner: [CC/RRRRRRRRRRRRRR/YYYY/NNNNNN] The YYYY characters must be a number in between version

31 The NNNNNN characters must be digits EI declaration of demonstration for track (INF) Applicability: Y shall be selected in case when the demonstration was executed and EI declaration was issued Format Example: <OPTrackParameter ID="IDE_EIDemonstration" IsApplicable="Y" Value="EL/4361FRWS1ASDVG/2013/000002" /> Validation: The following validations will be performed by the system: The number of characters and the slashes must be provided in the following manner: [CC/RRRRRRRRRRRRRR/YYYY/NNNNNN] The YYYY characters must be a number in between The NNNNNN characters must be digits TEN classification of track Format Example: <OPTrackParameter ID="IPP_TENClass" IsApplicable="Y" Value="10" OptionalValue="Part of the TEN-T Comprehensive Network"/> Category of Line Applicability: Technical scope of the INF TSI now includes all the networks (TEN and off-ten) for nominal track gauges 1435, 1520, 1524, 1600 and 1668 mm Applicable if track is included in technical scope of the TSI Format Example: <OPTrackParameter ID="IPP_LineCat" IsApplicable="Y" Value="60" OptionalValue="P6"/> Part of a Railway Freight Corridor Format Example: <OPTrackParameter ID="IPP_FreightCorridor" IsApplicable="Y" Value="10" /> Interoperable gauge Format Example: <OPTrackParameter ID="ILL_InteropGauge" IsApplicable="NYA" /> Multinational gauges Applicability: Y only if none is selected in version

32 Format Example: <OPTrackParameter ID="ILL_MultiNatGauge" IsApplicable="Y" Value="30" /> National gauges Applicability: Y only if none is selected in Format Example: <OPTrackParameter ID="ILL_NatGauge" IsApplicable="Y" Value="10" /> Nominal track gauge Format Example: <OPTrackParameter ID="ITP_NomGauge" IsApplicable="Y" Value="20" /> Tunnel Format Example: <OPTrackTunnel ValidityDateStart=" " ValidityDateEnd=" "> Validation: If ValidityDateStart is greater than the date of the validation, the OP Track Tunnel will be considered a FUTURE planning; otherwise, it is considered a CURRENT item IM s Code Format Example: <OPTrackTunnelIMCode Value="1234" /> Validation: No verification by CUI. Check of the link between MS and IM s Code must be done nationally Tunnel identification Format Example: <OPTrackTunnelIdentification Value="000002" /> Validation: No verification will be done by CUI. The check must be done nationally EC declaration of verification for tunnel (SRT) Applicability: Y shall be selected in case when EC declaration was issued Format Example: <OPTrackTunnelParameter ID="ITU_ECVerification" IsApplicable="Y" Value="EL/ ASDVG/2012/000091" /> Validation: The following validations will be performed by the system: The number of characters and the slashes must be provided in the following manner: [CC/RRRRRRRRRRRRRR/YYYY/NNNNNN] The YYYY characters must be a number in between The NNNNNN characters must be digits EI declaration of demonstration for tunnel (SRT) 32 version

33 Applicability: Y shall be selected in case when the demonstration was executed and EI declaration was issued. Format Example: <OPTrackTunnelParameter ID="ITU_EIDemonstration" IsApplicable="Y" Value="EL/4361FRWS1ASDVG/2013/000002" /> Validation: The following validations will be performed by the system: The number of characters and the slashes must be provided in the following manner: [CC/RRRRRRRRRRRRRR/YYYY/NNNNNN] The YYYY characters must be a number in between The NNNNNN characters must be digits Length of tunnel Applicability: Y only for a tunnel with length of 100 metres or more. Format Example: <OPTrackTunnelParameter ID="ITU_Length" IsApplicable="Y" Value="1212" /> Existence of emergency plan Format Example: <OPTrackTunnelParameter ID="ITU_EmergencyPlan" IsApplicable="Y" Value="N" /> Fire category of rolling stock required Applicability: N =not applicable shall be selected for short tunnels of less than 1 km, as for them the fire category according SRT TSI does not exist. Format Example: <OPTrackTunnelParameter ID="ITU_FireCatReq" IsApplicable="Y" Value="10" /> National fire category of rolling stock required Applicability: N =not applicable shall be selected when respective national rules do not exist Y only for tunnels when for the parameter the option none was selected. Format Example: <OPTrackTunnelParameter ID="ITU_NatFireCatReq" IsApplicable="N" /> Validation: No special validation rules apply. Check shall be done nationally Platform Format Example: <OPTrackPlatform ValidityDateStart=" " ValidityDateEnd=" "> Validation:If ValidityDateStart is greater than the date of the validation, the OP Track Platform will be considered a FUTURE planning; otherwise, it is considered a CURRENT item. version

34 IM s Code Applicability: Y/N (if platform does not exist on the OP) Format Example: <OPTrackPlatformIMCode Value="1234" /> Validation: No verification will be done by CUI. The check of the link between MS and IM s Code must be done nationally Identification of platform Applicability: Y/N (if platform does not exist on the OP) Format Example: <OPTrackPlatformIdentification Value="000001" /> Validation: No validation will be performed by CUI. This shall be checked nationally TEN Classification of platform Applicability: Y/N (if platform does not exist on the OP)/NYA Format Example: <OPTrackPlatformParameter ID="IPL_TENClass" IsApplicable="Y" Value="10" OptionalValue="Part of the TEN-T Comprehensive Network"/> Usable length of platform Applicability: Y/N (if platform does not exist on the OP)/NYA Format Example: <OPTrackPlatformParameter ID="IPL_Length" IsApplicable="Y" Value="1234" /> Height of platform Applicability: Y/N (if platform does not exist on the OP)/NYA Format Example: <OPTrackPlatformParameter ID="IPL_Height" IsApplicable="Y" Value="10" /> Existence of platform assistance for starting train Applicability: Y/N (if platform does not exist on the OP)/NYA Format Example: <OPTrackPlatformParameter ID="IPL_AssistanceStartingTrain" IsApplicable="Y" Value="Y" /> 34 version