RINF XML Data Validation Guide - European Union Agency … XML Data... · The RINF Validation...

European Railway Agency, 120, rue Marc Lefrancq, F–59300 Valenciennes, FranceTelephone: +33–(0)327–09 65 00 ▪ Fax: +33–(0)327–09 66 37

Website: http://www.era.europa.eu ▪ E-mail: [email protected]

RINF XML Data Validation GuideRINF

Document InformationDate: Thu, 2015 Feb 26

Release Number: 1.1

Version: 0.6

Author(s): European Dynamics

Reference: [Ref Identifier]

Document History

2 version 0.6 – 2015-02-26

Document HistoryDate Author Version Comment Modified

SectionsMon, 2013 Nov 4 European Dynamics 0.1 Document creation AllFri, 2014 Feb 7 European Dynamics 0.2 Updates for validity end date AllWed, 2014 May 28 European Dynamics 0.3 Updates for Release 1.0 AllTue, 2014 Aug 26 European Dynamics 0.4 Updated for Release 1.1 AllFri, 2014 Dec 19 European Dynamics 0.5 Updated for Release 1.1 AllThu, 2015 Feb 26 European Dynamics 0.6 Groups of parameters All

Document Distribution ListDate Name Position OrganisationClick here toenter a date.Click here toenter a date.Click here toenter a date.

Table of Contents

version 0.5 – 2015-02-26 3

Table of ContentsDocument Information............................................................................................................................. 1

Document History.................................................................................................................................... 2

Document Distribution List....................................................................................................................... 2

Table of Contents..................................................................................................................................... 3

1 Introduction ..................................................................................................................................... 4

1.1 Explanation of an XML line for a RINF parameter.................................................................................. 4

2 Validity Dates for Future Railway Infrastructure Modifications Planning ............................................ 5

3 General Validation Rules................................................................................................................... 7

3.1 ID ............................................................................................................................................................ 7

3.2 APPLICABLE............................................................................................................................................. 8

3.3 MANDATORY .......................................................................................................................................... 8

3.4 CAN BE REPEATED .................................................................................................................................. 8

3.5 FORMAT.................................................................................................................................................. 8

4 Parameter-Specific Validation Rules................................................................................................ 10

Introduction

4 version 0.6 – 2015-02-26

1 IntroductionThis document comprises an XML Data Validation Guide for the RINF Application explaining the validationrules for XML data files with specific examples per parameter.

1.1 Explanation of an XML line for a RINF parameterA typical line of an XML RINF data file like the following : <SOLTrackParameter ID="CTD_DetectionSystem"IsApplicable="Y" Value="10" OptionalValue=”Track circuit” Set="trackcircuit" /> consists of the followingelements:

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 (seeLookUpValuesDictionaries.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 thevalue is the code (in this example 50) of the selected item from the list of values, in addition to the requiredtext (in this example 994).

Another example:

<SOLTrackParameter ID="EPA_StripMaterial" IsApplicable="Y" Value=”50 27”/>

OptionalValue: This optional attribute is used only for readability of the XML file and more specifically in lookupvalues where the “Value” attribute stores the code of the parameter value and not the value itself. Thisattribute can store the full actual value of the parameter.

Set: This attribute is used to map a set of parameters as a group.

For example, the set of parameters 1.1.1.3.7.2 – 1.1.1.3.7.23 are children of the parameter 1.1.1.3.7.1 andmust have the “Set” attribute the same as their parent.

<SOLTrackParameter ID="CTD_DetectionSystem" IsApplicable="Y" Value="10" Set="trackcircuit"/>

<SOLTrackParameter ID="CTD_TSIMaxDistConsecutiveAxles" IsApplicable="Y" Value="20"Set="trackcircuit"/>

<SOLTrackParameter ID="CTD_MaxDistConsecutiveAxles" IsApplicable="Y" Value="123" Set="trackcircuit"/>

…

Validity Dates for Future Railway Infrastructure Modifications

Planning

version 0.5 – 2015-02-26 5

2 Validity Dates for Future Railway Infrastructure Modifications Planning

For future planning purposes two additional dates are included: one indicating the beginning of the validityfor a specific subset of data of RINF items collected from the Member States (see section 1.3 of the RINFTechnical Specifications – Complementary Document) and one for the expiration of the validity for a specificsubset 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 thenew/updated infrastructure will come into service and to specify when the existing infrastructure is plannedto be out of service, i.e. to provide information about changes or additions to the railway network that areplanned 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 needto include 2 sub-sets of data for the particular RINF item within the uploaded RINF data set: one sub-set ofdata will describe the currently existing infrastructure and the other sub-set of data will describe the futurechanges 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, ando 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 importo The validity end date is in the future.

- The implementation of the validation mechanism will be based on the following assumptions:o Any object with no validity start date or with validity start date set in the past will be accepted.

Validity Dates for Future Railway Infrastructure Modifications Planning

6 version 0.6 – 2015-02-26

o If an object has both validity start date and validity end date, then the validity start date mustbe before the validity end date.

o Objects with validity end date set in the past are not accepted.

General Validation Rules

version 0.5 – 2015-02-26 7

3 General Validation Rules

In this chapter, the validation rules that apply for all RINF parameters are presented. Furthermore, examplesare 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

YES NYAMUST_BE_PRESENT

VALUE_ATTRIBUTE_NOT_REQUIRED

NO Y OPTIONAL VALID_VALUE_IF_PRESENT

NO N OPTIONALVALUE_ATTRIBUTE_NOT_REQUIRED

IF_PRESENT

NO NYAOPTIONAL 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). Usingthis ID, the Validation and Import modules map the data of the XML element to the respective RINF Items anddata tables.

Example of an element without the ID attribute:

<OPTrack ValidityDateStart="2012-12-13" ValidityDateEnd="2020-12-17">

In the above example, the OPTrack element does not have the ID attribute because it is the name of theelement (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 ParameterILL_MultiNatGauge”).


8 version 0.6 – 2015-02-26

3.2 APPLICABLE

When an XML data file is submitted for validation and a not applicable parameter is included, the RINFapplication 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 nextexamples. “NYA” is used when the applicability is not yet available and the application Validation moduleshould 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: <OPTrackTunnelParameterID="ITU_NatFireCatReq" IsApplicable="N" />

Example of not yet available applicability definition in an XML data file: <OPTrackParameterID="ILL_InteropGauge" IsApplicable="NYA" />

In case the Application Guide does not include the “Applicable” section for a parameter, the parameter isconsidered 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 RINFapplication 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 RINFapplication will detect the missing mandatory parameter and log the error which will also be displayed in thevalidation 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 morethan once, the RINF application will detect the multiple parameters and specify them in the validation errorpopup 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 onespecified in the Application Guide, the RINF application will detect it and specify it in the validation error popupdialog.

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 ofintegral digits that can be provided, e.g. ‘NNN’ represents a number in the range of [0, 999].


version 0.5 – 2015-02-26 9

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].

o Note: The opening and closing brackets ‘[‘ and ‘]’ are only provided for readability reasons inthe 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 lengthof the string is not restricted by the Application Guide, the maximum permitted length in the XSD is450 characters.

Single selection from the predefined list: A list of values is provided in the Application Guide. TheRINF Validation will only accept the values of that list.

More specific examples for format validation rules are following in the next chapter.

Parameter-Specific Validation Rules

10 version 0.6 – 2015-02-26

4 Parameter-Specific Validation Rules

A detailed list of the RINF parameters is presented below, accompanied with examples and explanations ofspecific 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 whouploaded the file.

1.1 SECTION OF LINE

Format Example: <SectionOfLine ValidityDateStart="2013-01-20" ValidityDateEnd="2015-12-13">

Validation: If ValidityDateStart is greater than the date of the validation, the Section of Line will beconsidered a FUTURE planning; otherwise, it is considered a CURRENT item.

1.1.0.0.0.1 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 donenationally.

1.1.0.0.0.2 National line identification

Format Example: <SOLLineIdentification Value="ELLine0001" />

Validation: No special validation rules apply. Check shall be done nationally.

1.1.0.0.0.3 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 from1.1.0.0.0.4. No validation will be performed by CUI regarding which is the start and which the end OP. Checkshall be done nationally.

1.1.0.0.0.4 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 from1.1.0.0.0.3. No validation will be performed by CUI regarding which is the start and which the end OP. Checkshall be done nationally.

1.1.0.0.0.5 Length of section of line

Format Example: <SOLLength Value="123.456" />


version 0.5 – 2015-02-26 11

Validation: Regarding the correctness of the length of SoL, no validation will be performed by CUI. Check shallbe done nationally. However, any number outside the boundaries defined in the Application Guide will resultin the corresponding error message in the RINF validation.

1.1.0.0.0.6 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 ofthe following groups of parameters will not be applicable:

1.1.1.1 Infrastructure subsystem 1.1.1.2 Energy subsystem 1.1.1.3 Control-command and signalling subsystem

1.1.1 RUNNING TRACK

Format Example: <SOLTrack ValidityDateEnd="2015-12-13">

Validation: If ValidityDateStart is greater than the date of the validation, the SOL Track will be considered aFUTURE planning; otherwise, it is considered a CURRENT item.

Mandatory: Y

1.1.1.0.0.1 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.

1.1.1.0.0.2 Normal running direction

Format Example: <SOLTrackDirection Value="10" />

Validation: Any value that is not defined in the pre-defined list of the Application Guide will result in thecorresponding error message in the RINF validation.

1.1.1.1.1.1 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/436195241ASDVG/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 1900-2100. The NNNNNN characters must be digits.

1.1.1.1.1.2 EI declaration of demonstration for track (INF)

Format Example: <SOLTrackParameter ID="IDE_EIDemonstration" IsApplicable="Y"Value="EL/436195241ASDVG/2012/003001"/>



12 version 0.6 – 2015-02-26



1.1.1.1.2.1 TEN classification of track

Format Example: <SOLTrackParameter ID="IPP_TENClass" IsApplicable="Y" Value="10"/>


1.1.1.1.2.2 Category of Line

Format Example: <SOLTrackParameter ID="IPP_LineCat" IsApplicable="Y" Value="10"/>


1.1.1.1.2.3 Part of a Railway Freight Corridor

Format Example: <SOLTrackParameter ID="IPP_FreightCorridor" IsApplicable="Y" Value="10"/>


1.1.1.1.2.4 Load capability

Format Example: <SOLTrackParameter ID="IPP_LoadCap" IsApplicable="Y" Value="40 12"OptionalValue="C2 12"/>


1.1.1.1.2.5 Maximum permitted speed

Format Example: <SOLTrackParameter ID="IPP_MaxSpeed" IsApplicable="Y" Value="351">

Validation: Any number outside the boundaries defined in the Application Guide will result in thecorresponding error message in the RINF validation.

1.1.1.1.2.6 Temperature range

Format Example: <SOLTrackParameter ID="IPP_TempRange" IsApplicable="Y" Value="30"OptionalValue="T3 (-25 to +45)"/>


1.1.1.1.2.7 Maximum altitude

Format Example: <SOLTrackParameter ID="IPP_MaxAltitude" IsApplicable="Y" Value="+0123"/>


1.1.1.1.2.8 Existence of severe climatic conditions


version 0.5 – 2015-02-26 13

Format Example: <SOLTrackParameter ID="IPP_SevereClimateCon" IsApplicable="Y" Value="Y"/>


1.1.1.1.3.1 Interoperable gauge

Format Example: <SOLTrackParameter ID="ILL_InteropGauge" IsApplicable="Y" Value="10"/>


1.1.1.1.3.2 Multinational gauges

Applicability: Only if “none” is selected in parameter 1.1.1.1.3.1.

Format Example: <SOLTrackParameter ID="ILL_MultiNatGauge" IsApplicable="N" />


1.1.1.1.3.3 National gauges

Applicability: Only if “none” is selected in parameter 1.1.1.1.3.2.

Format Example: <SOLTrackParameter ID="ILL_NatGauge" IsApplicable="N"/>


1.1.1.1.3.4 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" />


1.1.1.1.3.5 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"/>


1.1.1.1.3.6 Gradient profile

Format Example: <SOLTrackParameter ID="ILL_GradProfile" IsApplicable="Y" Value="+11.2"/>

Validation: Any number outside the boundaries defined in the Application Guide will result in thecorresponding error message in the RINF validation (maximum number of digits up to 1000).

1.1.1.1.3.7 Minimum radius of horizontal curve


14 version 0.6 – 2015-02-26

Format Example: <SOLTrackParameter ID="ILL_MinRadHorzCurve" IsApplicable="Y" Value="426"/>


1.1.1.1.4.1 Nominal track gauge

Format Example: <SOLTrackParameter ID="ITP_NomGauge" IsApplicable="Y" Value="20"/>


1.1.1.1.4.2 Cant deficiency

Format Example: <SOLTrackParameter ID="ITP_CantDeficiency" IsApplicable="Y" Value="+153"/>


1.1.1.1.4.3 Rail inclination

Format Example: <SOLTrackParameter ID="ITP_RailInclination" IsApplicable="Y" Value="20"/>


1.1.1.1.4.4 Existence of ballast

Applicability: Only for tracks with permitted speed (parameter 1.1.1.1.2.5) of more than 200 km/h.

Format Example: <SOLTrackParameter ID="ITP_Ballast" IsApplicable="Y" Value="Y"/>


1.1.1.1.5.1 TSI compliance of in service values for switches and crossings

Format Example: <SOLTrackParameter ID="ISC_TSISwitchCrossing" IsApplicable="Y" Value="N"/>


1.1.1.1.5.2 Minimum wheel diameter for fixed obtuse crossings

Format Example: <SOLTrackParameter ID="ISC_MinWheelDiaFixObtuseCrossings" IsApplicable="Y"Value="443"/>


1.1.1.1.6.1 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"/>



version 0.5 – 2015-02-26 15

1.1.1.1.6.2 Use of eddy current brakes

Format Example: <SOLTrackParameter ID="ILR_EddyCurrentBrakes" IsApplicable="Y" Value="10"/>


1.1.1.1.6.3 Use of magnetic brakes

Format Example: <SOLTrackParameter ID="ILR_MagneticBrakes" IsApplicable="Y" Value="10"/>


1.1.1.1.7.1 Use of flange lubrication forbidden

Format Example: <SOLTrackParameter ID="IHS_FlangeLubeForbidden" IsApplicable="Y" Value="Y"/>


1.1.1.1.7.2 Existence of level crossings

Format Example: <SOLTrackParameter ID="IHS_LevelCrossing" IsApplicable="Y" Value="Y"/>


1.1.1.1.7.3 Acceleration allowed at level crossing

Applicability: Applicable only when selected value of parameter 1.1.1.1.7.2 is ‘Y’

Format Example: <SOLTrackParameter ID="IHS_AccelerationLevelCrossing" IsApplicable="Y" Value="0.1"/>


1.1.1.1.8. Tunnel

Format Example: <SOLTunnel ValidityDateStart="2012-12-13" ValidityDateEnd="2015-12-13">

Validation: If ValidityDateStart is greater than the date of the validation, the SOL Tunnel will be considered aFUTURE planning; otherwise, it is considered a CURRENT item.

1.1.1.1.8.1 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 bedone nationally.

1.1.1.1.8.2 Tunnel identification

Format Example: <SOLTunnelIdentification Value="000001" />


16 version 0.6 – 2015-02-26


1.1.1.1.8.3 Start of tunnel

Format Example: <SOLTunnelStart Latitude="43.1232" Longitude="+10.4545" Kilometer="123.475" />


1.1.1.1.8.4 End of tunnel

Format Example: <SOLTunnelEnd Latitude="43.4445" Longitude="+12.2145" Kilometer="123.459" />


1.1.1.1.8.5 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/436195241ASDVG/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 1900-2100. The NNNNNN characters must be digits.

1.1.1.1.8.6 EI declaration of demonstration for tunnel (SRT)

Applicability: “Y” shall be selected in case when the demonstration was executed and EI declaration wasissued

Format Example: <SOLTunnelParameter ID="ITU_EIDemonstration" IsApplicable="Y"Value="EL/4361FRWS1ASDVG/2013/000002" />




1.1.1.1.8.7 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" />


1.1.1.1.8.8 Cross section area


version 0.5 – 2015-02-26 17

Format Example: <SOLTunnelParameter ID="ITU_CrossSectionArea" IsApplicable="Y" Value="27" />


1.1.1.1.8.9 Existence of emergency plan

Format Example: <SOLTunnelParameter ID="ITU_EmergencyPlan" IsApplicable="Y" Value="N" />


1.1.1.1.8.10 Fire category of rolling stock required

Applicability: Not applicable shall be selected for short tunnels of less than 1 km, as for them the firecategory according SRT TSI does not exist.

Format Example: <SOLTunnelParameter ID="ITU_FireCatReq" IsApplicable="Y" Value="10" />


1.1.1.1.8.11 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 1.1.1.1.8.10 the option ‘none’ was selected.

Format Example: <SOLTunnelParameter ID="ITU_NatFireCatReq" IsApplicable="N" />


1.1.1.2.1.1 EC declaration of verification for track (ENE)


Format Example: <SOLTrackParameter ID="EDE_ECVerification" IsApplicable="Y"Value="EL/436195241ASDVG/2012/000004"/>



1.1.1.2.1.2 EI declaration of demonstration for track (ENE)


Format Example: <SOLTrackParameter ID="EDE_EIDemonstration" IsApplicable="Y"Value="EL/4361FRWS1ASDVG/2013/000002"/>



18 version 0.6 – 2015-02-26



1.1.1.2.2.1.1 Type of contact line system

Format Example: <SOLTrackParameter ID="ECS_SystemType" IsApplicable="Y" Value="20"Set="ThirdRail" />


1.1.1.2.2.1.2 Energy supply system (Voltage and frequency)

Applicability: When "not electrified" is chosen in parameter 1.1.1.2.2.1.1, then this parameter is notapplicable.

Format Example: <SOLTrackParameter ID="ECS_VoltFreq" IsApplicable="Y" Value="30"Set="ThirdRail" />


1.1.1.2.2.2 Maximum train current

Applicability: When "not electrified" is chosen in parameter 1.1.1.2.2.1.1, then this parameter is notapplicable.

Format Example: <SOLTrackParameter ID="ECS_MaxTrainCurrent" IsApplicable="N" Set="ThirdRail"/>


1.1.1.2.2.3 Maximum current at standstill per pantograph

Applicability: This parameter is applicable (“Y”) only if “Overhead contact line (OCL)” is selected forparameter 1.1.1.2.2.1.1 and if DC system is selected in 1.1.1.2.2.1.2

Format Example: <SOLTrackParameter ID="ECS_MaxStandstillCurrent" IsApplicable="Y" Value="175"Set=”OCL”/>


1.1.1.2.2.4 Permission for regenerative braking

Applicability: When "not electrified" is chosen in parameter 1.1.1.2.2.1.1, then this parameter is notapplicable

Format Example: <SOLTrackParameter ID="ECS_RegenerativeBraking" IsApplicable="Y" Value="N"Set="ThirdRail" />


version 0.5 – 2015-02-26 19


1.1.1.2.2.5 Maximum contact wire height

Applicability: This parameter is applicable (“Y”) only if “Overhead contact line (OCL)” is selected in1.1.1.2.2.1.1

Format Example: <SOLTrackParameter ID="ECS_MaxWireHeight" IsApplicable="N" />


1.1.1.2.2.6 Minimum contact wire height


Format Example: <SOLTrackParameter ID="ECS_MinWireHeight" IsApplicable="N" />


1.1.1.2.3.1 Accepted TSI compliant pantograph heads

Applicability: This parameter is applicable (“Y”) only if “Overhead contact line (OCL)” is selected for1.1.1.2.2.1.1. It is not applicable (“N") if there is no contact line.

Format Example: <SOLTrackParameter ID="EPA_TSIHeads" IsApplicable="N" />


1.1.1.2.3.2 Accepted other pantograph heads


Format Example: <SOLTrackParameter ID="EPA_OtherHeads" IsApplicable="N"/>


1.1.1.2.3.3 Requirements for number of raised pantographs and spacing between them, at the given speed


<SOLTrackParameter ID="EPA_NumRaisedSpeed" IsApplicable="N" />


1.1.1.2.3.4 Permitted contact strip material


20 version 0.6 – 2015-02-26


Format Example: <SOLTrackParameter ID="EPA_StripMaterial" IsApplicable="Y" Value=”50 27”/>

Validation: Any value that is not defined in the pre-defined list of the Application Guide will result in thecorresponding error message in the RINF validation. Note that for the “impregnated carbon ([NN] % of metalliccontent)” option, any number outside the boundaries defined in the Application Guide will result in thecorresponding error message in the RINF validation.

1.1.1.2.4.1.1 Phase separation


Format Example: <SOLTrackParameter ID="EOS_Phase" IsApplicable="N" />


1.1.1.2.4.1.2 Information on phase separation

Applicability: Applicable when in parameter 1.1.1.2.4.1.1 selected option is ‘Y’

Format Example: <SOLTrackParameter ID="EOS_InfoPhase" IsApplicable="Y" Value="length 144 + switch offbreaker Y + lower pantograph Y"/>

Validation: Invalid input will mean a value for “Length” outside the boundaries defined in the ApplicationGuide or any value that is not defined in the pre-defined list in the Application Guide for "Switch off breaker”or “Lower pantograph”.

1.1.1.2.4.2.1 System separation

Applicability: This parameter is applicable (“Y”) only if the value “Overhead contact line (OCL)” is selected for1.1.1.2.2.1.1

Format Example: <SOLTrackParameter ID="EOS_System" IsApplicable="N" />


1.1.1.2.4.2.2 Information on system separation

Applicability: Selection ‘Y’=yes when in parameter 1.1.1.2.4.2.1 selected option is ‘Y’.

Format Example: <SOLTrackParameter ID="EOS_InfoSystem" IsApplicable="Y" Value="length 123 + switchoff breaker Y + lower pantograph Y + change supply system N"/>

Validation: Invalid input will mean a value for “Length” outside the boundaries defined in the ApplicationGuide 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”.

1.1.1.2.5.1 Current or power limitation on board required


version 0.5 – 2015-02-26 21

Applicability: When "not electrified" is chosen in parameter 1.1.1.2.2.1.1, then this parameter is notapplicable selection ‘N’.

Format Example: <SOLTrackParameter ID="ERS_PowerLimitOnBoard" IsApplicable="Y" Value="N"Set="ThirdRail" />


1.1.1.2.5.2. Contact force permitted


Format Example: <SOLTrackParameter ID="ERS_ContactForce" IsApplicable="N" />


1.1.1.2.5.3 Automatic dropping device required


Format Example: <SOLTrackParameter ID="ERS_AutoDropRequired" IsApplicable="N" />


1.1.1.3.1.1 EC declaration of verification for track (CCS)


Format Example: <SOLTrackParameter ID="CDE_ECVerification" IsApplicable="N" />



1.1.1.3.2.1 ETCS level

Format Example: <SOLTrackParameter ID="CPE_Level" IsApplicable="Y" Value="30" Set="2" />


1.1.1.3.2.2 ETCS baseline

Applicability: Not applicable (‘N’) when selected value for 1.1.1.3.2.1 is ‘N’.

Format Example: <SOLTrackParameter ID="CPE_Baseline" IsApplicable="Y" Value="20" Set="2" />


22 version 0.6 – 2015-02-26


1.1.1.3.2.3 ETCS infill necessary for line access

Applicability: Only applicable when selected value for 1.1.1.3.2.1 is ‘1’.

Format Example: <SOLTrackParameter ID="CPE_Infill" IsApplicable="Y" Value="N"/>


1.1.1.3.2.4 ETCS infill installed lineside

Applicability: Only applicable when selected value for 1.1.1.3.2.1 is ‘1’.

Format Example: <SOLTrackParameter ID="CPE_InfillLineSide" IsApplicable="Y" Value="10"/>


1.1.1.3.2.5 ETCS national application implemented

Applicability: Not applicable ‘N’ when selected value for 1.1.1.3.2.1 is ‘N’.

Format Example: <SOLTrackParameter ID="CPE_NatApplication" IsApplicable="Y" Value="N"/>


1.1.1.3.2.6 Existence of operating restrictions or conditions


Format Example: <SOLTrackParameter ID="CPE_RestrictionsConditions" IsApplicable="Y" Value="N"/>


1.1.1.3.2.7 Optional ETCS functions


Format Example: <SOLTrackParameter ID="CPE_OptionalFunctions" IsApplicable="Y" Value="test"/>


1.1.1.3.3.1 GSM-R version

Format Example: <SOLTrackParameter ID="CRG_Version" IsApplicable="Y" Value="40"/>



version 0.5 – 2015-02-26 23

1.1.1.3.3.2 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 1.1.1.3.3.1

Format Example: <SOLTrackParameter ID="CRG_NumActiveMob" IsApplicable="Y" Value="20"/>


1.1.1.3.3.3 Optional GSM-R functions

Applicability: Not applicable (‘N’) when “none” is selected in parameter 1.1.1.3.3.1.

Format Example: <SOLTrackParameter ID="CRG_OptionalFunctions" IsApplicable="Y" Value="10"/>


1.1.1.3.4.1 Existence of train detection system fully compliant with the TSI

Format Example: <SOLTrackParameter ID="CCD_TSITrainDetection" IsApplicable="Y" Value="N"/>


1.1.1.3.5.1 Existence of other train protection, control and warning systems installed

Applicability: Y in case when for 1.1.1.3.2.1 the selected option is ‘N’.

Format Example: < <SOLTrackParameter ID="CPO_Installed" IsApplicable="Y" Value="N"/>


1.1.1.3.5.2 Need for more than one train protection, control and warning system required on-board

Applicability: Y in case when for 1.1.1.3.2.1 the selected option is ‘N’

Format Example: <SOLTrackParameter ID="CPO_MultipleRequired" IsApplicable="Y" Value="N"/>


1.1.1.3.6.1 Other radio systems installed

Applicability: Y when for the parameter 1.1.1.3.3.1 it was selected ‘none’.

Format Example: <SOLTrackParameter ID="CRS_Installed" IsApplicable="N" />


1.1.1.3.7.1 Type of train detection system


24 version 0.6 – 2015-02-26

Format Example: <SOLTrackParameter ID="CTD_DetectionSystem" IsApplicable="Y" Value="10"Set="trackcircuit" />


1.1.1.3.7.2.1 TSI compliance of maximum permitted distance between two consecutive axles

Format Example: <SOLTrackParameter ID="CTD_TSIMaxDistConsecutiveAxles" IsApplicable="Y" Value="20"Set="trackcircuit" />


1.1.1.3.7.2.2 Maximum permitted distance between two consecutive axles in case of TSI non-compliance

Applicability: Applicable (‘Y’) when in 1.1.1.3.7.2.1 selected option is ‘TSI not compliant’

Format Example: <SOLTrackParameter ID="CTD_MaxDistConsecutiveAxles" IsApplicable="Y" Value="123"Set="trackcircuit" />


1.1.1.3.7.3 Minimum permitted distance between two consecutive axles

Applicability: Applicable (‘Y’) when parameter 1.1.1.3.7.1 the selected option is ‘wheel detector’

Format Example: <SOLTrackParameter ID="CTD_MinDistConsecutiveAxles" IsApplicable="Y" Value="3325"Set="trackcircuit" />


1.1.1.3.7.4 Minimum permitted distance between first and last axle

Applicability: Applicable (‘Y’) only when for parameter 1.1.1.3.7.1 the selected option is ‘track circuits’.

Format Example: <SOLTrackParameter ID="CTD_MinDistFirstLastAxles" IsApplicable="Y" Value="12"Set="trackcircuit" />


1.1.1.3.7.5 Maximum distance between end of train and first axle

Applicability: Applicable (‘Y’) only when for parameter 1.1.1.3.7.1 the selected option is ‘track circuits’ or‘wheel detector’.

Format Example: <SOLTrackParameter ID="CTD_MaxDistEndTrainFirstAxle" IsApplicable="Y" Value="321"Set="trackcircuit" />


version 0.5 – 2015-02-26 25


1.1.1.3.7.6 Minimum permitted width of the rim

Applicability: Applicable (‘Y’) only when for parameter 1.1.1.3.7.1 the selected option is ‘wheel detector’.

Format Example: <SOLTrackParameter ID="CTD_MinRimWidth" IsApplicable="Y" Value="11"Set="trackcircuit" />


1.1.1.3.7.7 Minimum permitted wheel diameter


Format Example: <SOLTrackParameter ID="CTD_MinWheelDiameter" IsApplicable="Y" Value="96"Set="trackcircuit" />


1.1.1.3.7.8 Minimum permitted thickness of the flange


Format Example: <SOLTrackParameter ID="CTD_MinFlangeThickness" IsApplicable="Y" Value="56.2"Set="trackcircuit" />


1.1.1.3.7.9 Minimum permitted height of the flange


Format Example: <SOLTrackParameter ID="CTD_MinFlangeHeight" IsApplicable="Y" Value="33.8"Set="trackcircuit" />


1.1.1.3.7.10 Maximum permitted height of the flange


Format Example: <SOLTrackParameter ID="CTD_MaxFlangeHeight" IsApplicable="Y" Value="73.7"Set="trackcircuit" />


1.1.1.3.7.11 Minimum permitted axle load


26 version 0.6 – 2015-02-26

Applicability: Applicable (‘Y’) only when for parameter 1.1.1.3.7.1 the selected option is ‘track circuit’ or‘wheel detector’.

Format Example: <SOLTrackParameter ID="CTD_MinAxleLoad" IsApplicable="Y" Value="5.9"Set="trackcircuit" />


1.1.1.3.7.12 TSI compliance of rules for metal-free space around wheels


Format Example: <SOLTrackParameter ID="CTD_TSIMetalFree" IsApplicable="Y" Value="10"Set="trackcircuit" />


1.1.1.3.7.13 TSI compliance of rules for vehicle metal construction

Applicability: Applicable (‘Y’) only when for parameter 1.1.1.3.7.1 the selected option is ‘loop’.

Format Example: <SOLTrackParameter ID="CTD_TSIMetalConstruction" IsApplicable="Y" Value="10"Set="trackcircuit" />


1.1.1.3.7.14 TSI compliance of Ferromagnetic characteristics of wheel material required


Format Example: <SOLTrackParameter ID="CTD_TSIFerroWheelMat" IsApplicable="Y" Value="20"Set="trackcircuit" />


1.1.1.3.7.15.1 TSI compliance of maximum permitted impedance between opposite wheels of a wheelset

Applicability: Applicable (‘Y’) only when for parameter 1.1.1.3.7.1 the selected option is ‘track circuit’.

Format Example: <SOLTrackParameter ID="CTD_TSIMaxImpedanceWheelset" IsApplicable="Y" Value="20"Set="trackcircuit" />


1.1.1.3.7.15.2 Maximum permitted impedance between opposite wheels of a wheelset when not TSIcompliant

Applicability: Applicable (‘Y’) only when for parameter 1.1.1.3.7.15.1 the selected option is ‘TSI notcompliant’


version 0.5 – 2015-02-26 27

Format Example: <SOLTrackParameter ID="CTD_MaxImpedanceWheelset" IsApplicable="Y" Value="1.598"Set="trackcircuit" />


1.1.1.3.7.16 TSI compliance of sanding

Applicability: Applicable (‘Y’) only when for parameter 1.1.1.3.7.1 the selected option is ‘track circuit’ andwhen selection for parameter 1.1.1.3.7.18 is “Y”.

Format Example: <SOLTrackParameter ID="CTD_TSISand" IsApplicable="Y" Value="20" Set="trackcircuit" />


1.1.1.3.7.17 Maximum sanding output

Applicability: Applicable (‘Y’) when for parameter 1.1.1.3.7.16 selected option is ‘TSI not compliant’

Format Example: <SOLTrackParameter ID="CTD_MaxSandOutput" IsApplicable="Y" Value="834"Set="trackcircuit" />


1.1.1.3.7.18 Sanding override by driver required


Format Example: <SOLTrackParameter ID="CTD_SandDriverOverride" IsApplicable="Y" Value="Y"Set="trackcircuit" />


1.1.1.3.7.19 TSI Compliance of rules on sand characteristics


Format Example: <SOLTrackParameter ID="CTD_TSISandCharacteristics" IsApplicable="Y" Value="20"Set="trackcircuit" />


1.1.1.3.7.20 Existence of rules on on-board flange lubrication


Format Example: <SOLTrackParameter ID="CTD_FlangeLubeRules" IsApplicable="Y" Value="N"Set="trackcircuit" />


28 version 0.6 – 2015-02-26


1.1.1.3.7.21 TSI compliance of rules on the use of composite brake blocks


Format Example: <SOLTrackParameter ID="CTD_TSICompositeBrakeBlocks" IsApplicable="Y" Value="20"Set="trackcircuit" Set="trackcircuit" />


1.1.1.3.7.22 TSI compliance of rules on shunt assisting devices


Format Example: <SOLTrackParameter ID="CTD_TSIShuntDevices" IsApplicable="Y" Value="20"Set="trackcircuit" />


1.1.1.3.7.23 TSI compliance of rules on combination of RST characteristics influencing shunting impedance


Format Example: < <SOLTrackParameter ID="CTD_TSIRSTShuntImpedance" IsApplicable="Y" Value="20"Set="trackcircuit" />


1.1.1.3.8.1 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"/>


1.1.1.3.8.2 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"/>


1.1.1.3.9.1 Existence and TSI compliance of rules for magnetic fields emitted by a vehicle



version 0.5 – 2015-02-26 29

Format Example: <SOLTrackParameter ID="CEI_TSIMagneticFields" IsApplicable="Y" Value="20"/>


1.1.1.3.9.2 Existence and TSI compliance of limits in harmonics in the traction current of vehicles

Applicability: Applicable (‘Y’) only when for parameter 1.1.1.3.7.1 the selected option is ‘wheel detector’ or‘track circuit’.

Format Example: <SOLTrackParameter ID="CEI_TSITractionHarmonics" IsApplicable="Y" Value="20"/>


1.1.1.3.10.1 ETCS level for degraded situation

Applicability: ‘N’=not applicable shall be selected when ETCS is not installed (selection of parameter1.1.1.3.2.1 is ‘no’).

Format Example: <SOLTrackParameter ID="CLD_ETCSSituation" IsApplicable="Y" Value="30"/>


1.1.1.3.10.2 Other train protection, control and warning systems for degraded situation

Applicability: Y in case when for parameter 1.1.1.3.10.1 was selected ‘none’.

Format Example: <SOLTrackParameter ID="CLD_OtherProtectControlWarn" IsApplicable="N" />


1.1.1.3.11.1 Maximum braking distance requested

Format Example: <SOLTrackParameter ID="CBP_MaxBrakeDist" IsApplicable="Y" Value="4326"/>


1.1.1.3.12.1 Tilting supported

Applicability: ‘N’=not applicable shall be selected when ETCS is not installed (selection in parameter1.1.1.3.2.1 is ‘no’).

Format Example: <SOLTrackParameter ID="COP_Tilting" IsApplicable="Y" Value="N"/>


1.2 OPERATIONAL POINT

Format Example: <OperationalPoint ValidityDateStart="2012-12-13" ValidityDateEnd="2015-12-13">


30 version 0.6 – 2015-02-26

Validation: If ValidityDateStart is greater than the date of the validation, the Operational Point will beconsidered a FUTURE planning; otherwise, it is considered a CURRENT item.

1.2.0.0.0.1 Name of Operational Point

Format Example: <OPName Value="ELOP1" />


1.2.0.0.0.2 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 countrycode and an alphanumeric OP code [AA+AAAAA]. The first part ‘AA’ is the country code in two-letter systemof ISO; this must match the country indicated by parameter 1 (Member State). The second part ‘AAAAA’ isalphanumeric OP code within the MS.

1.2.0.0.0.3 OP TAF TAP primary code

Applicability: Y in case when OP TAF TAP primary code exists, otherwise N

Format Example: <OPTafTapCode IsApplicable="Y" Value="XX00002" />


1.2.0.0.0.4 Type of Operational Point

Format Example: <OPType Value="120" OptionalValue="switch"/>


1.2.0.0.0.5 Geographical location of Operational Point

Format Example: <OPGeographicLocation Longitude="+31.4155" Latitude="51.4245" />


1.2.0.0.0.6 Railway location of Operational Point

Format Example: <OPRailwayLocation Kilometer="1234.445" NationalIdentNum="ELLine0001" />


1.2.1 RUNNING TRACK

Format Example: <OPTrack ValidityDateStart="2012-12-13" ValidityDateEnd="2015-12-13">

Validation: If ValidityDateStart is greater than the date of the validation, the OP Track will be considered aFUTURE planning; otherwise, it is considered a CURRENT item.


version 0.5 – 2015-02-26 31

Mandatory: N

1.2.1.0.0.1 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 donenationally.

1.2.1.0.0.2 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.

1.2.1.0.1.1 EC declaration of verification for track (INF)


Format Example: <OPTrackParameter ID="IDE_ECVerification" IsApplicable="Y"Value="EL/436195241ASDVG/2012/000090" />



1.2.1.0.1.2 EI declaration of demonstration for track (INF)


Format Example: <OPTrackParameter ID="IDE_EIDemonstration" IsApplicable="Y"Value="EL/4361FRWS1ASDVG/2013/000002" />



1.2.1.0.2.1 TEN classification of track

Format Example: <OPTrackParameter ID="IPP_TENClass" IsApplicable="Y" Value="10" OptionalValue="Partof the TEN-T Comprehensive Network"/>


1.2.1.0.2.2 Category of Line


32 version 0.6 – 2015-02-26

Applicability: Technical scope of the INF TSI now includes all the networks (TEN and off-TEN) for nominaltrack 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"/>


1.2.1.0.2.3 Part of a Railway Freight Corridor

Format Example: <OPTrackParameter ID="IPP_FreightCorridor" IsApplicable="Y" Value="10" />


1.2.1.0.3.1 Interoperable gauge

Format Example: <OPTrackParameter ID="ILL_InteropGauge" IsApplicable="NYA" />


1.2.1.0.3.2 Multinational gauges

Applicability: Y only if “none” is selected in 1.2.1.0.3.1

Format Example: <OPTrackParameter ID="ILL_MultiNatGauge" IsApplicable="Y" Value="30" />


1.2.1.0.3.3 National gauges

Applicability: Y only if “none” is selected in 1.2.1.0.3.2

Format Example: <OPTrackParameter ID="ILL_NatGauge" IsApplicable="Y" Value="10" />


1.2.1.0.4.1 Nominal track gauge

Format Example: <OPTrackParameter ID="ITP_NomGauge" IsApplicable="Y" Value="20" />


1.2.1.0.5 Tunnel

Format Example: <OPTrackTunnel ValidityDateStart="2012-12-13" ValidityDateEnd="2015-12-13">


version 0.5 – 2015-02-26 33

Validation: If ValidityDateStart is greater than the date of the validation, the OP Track Tunnel will beconsidered a FUTURE planning; otherwise, it is considered a CURRENT item.

1.2.1.0.5.1 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.


Format Example: <OPTrackTunnelIdentification Value="000002" />

Validation: No verification will be done by CUI. The check must be done nationally.



Format Example: <OPTrackTunnelParameter ID="ITU_ECVerification" IsApplicable="Y"Value="EL/436195241ASDVG/2012/000091" />




Applicability: “Y” shall be selected in case when the demonstration was executed and EI declaration wasissued.

Format Example: <OPTrackTunnelParameter ID="ITU_EIDemonstration" IsApplicable="Y"Value="EL/4361FRWS1ASDVG/2013/000002" />




Applicability: Y only for a tunnel with length of 100 metres or more.

Format Example: <OPTrackTunnelParameter ID="ITU_Length" IsApplicable="Y" Value="1212" />



Format Example: <OPTrackTunnelParameter ID="ITU_EmergencyPlan" IsApplicable="Y" Value="N" />


34 version 0.6 – 2015-02-26



Applicability: ‘N’=not applicable shall be selected for short tunnels of less than 1 km, as for them the firecategory according SRT TSI does not exist.

Format Example: <OPTrackTunnelParameter ID="ITU_FireCatReq" IsApplicable="Y" Value="10" />



Applicability: ‘N’=not applicable shall be selected when respective national rules do not exist

Y only for tunnels when for the parameter 1.2.1.0.5.7 the option ‘none’ was selected.

Format Example: <OPTrackTunnelParameter ID="ITU_NatFireCatReq" IsApplicable="N" />


1.2.1.0.6 Platform

Format Example: <OPTrackPlatform ValidityDateStart="2012-12-13" ValidityDateEnd="2015-12-13">

Validation:If ValidityDateStart is greater than the date of the validation, the OP Track Platform will beconsidered a FUTURE planning; otherwise, it is considered a CURRENT item.

1.2.1.0.6.1 IM’s Code

Applicability: Y/N (if platform does not exist on the OP)

Format Example: <OPTrackPlatformIMCode Value="1234" />


1.2.1.0.6.2 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.

1.2.1.0.6.3 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"/>


version 0.5 – 2015-02-26 35


1.2.1.0.6.4 Usable length of platform


Format Example: <OPTrackPlatformParameter ID="IPL_Length" IsApplicable="Y" Value="1234" />


1.2.1.0.6.5 Height of platform


Format Example: <OPTrackPlatformParameter ID="IPL_Height" IsApplicable="Y" Value="10" />


1.2.1.0.6.6 Existence of platform assistance for starting train


Format Example: <OPTrackPlatformParameter ID="IPL_AssistanceStartingTrain" IsApplicable="Y" Value="Y"/>

Validation: Any value that is not defined in the pre-defined list of the Application Guide will result in thecorresponding error message in the RINF validation.1.2.1.0.6.7 Usable length of platform

1.2.1.0.6.7 Range of use of the platform boarding aid


Format Example: <OPTrackPlatformParameter ID="IPL_AreaBoardingAid" IsApplicable="Y" Value="2000" />


1.2.2 SIDING

Format Example: <OPSiding ValidityDateStart="2012-12-13" ValidityDateEnd="2015-12-13">

Validation: If ValidityDateStart is greater than the date of the validation, the Siding will be considered aFUTURE planning; otherwise, it is considered a CURRENT item.

1.2.2.0.0.1 IM’s Code

Format Example: <OPSidingIMCode Value="1234" />


1.2.2.0.0.2 Identification of siding


36 version 0.6 – 2015-02-26

Format Example: <OPSidingIdentification Value="TRXDD19" />

Validation: No validation will be performed by CUI. The uniqueness of siding ID shall be checked nationally.

1.2.2.0.0.3 TEN classification of siding

Format Example: <OPSidingParameter ID="IPP_TENClass" IsApplicable="Y" Value="10" />


1.2.2.0.1.1 EC declaration of verification for siding (INF)


Format Example: <OPSidingParameter ID="IDE_ECVerification" IsApplicable="Y"Value="EL/436195241ASDVG/2012/000090" />



1.2.2.0.1.2 EI declaration of demonstration for siding (INF)

Applicability: “Y” shall be selected in case when the demonstration was executed and EI declaration wasissued.

Format Example: <OPSidingParameter ID="IDE_EIDemonstration" IsApplicable="Y"Value="EL/4361FRWS1ASDVG/2013/000002" />



1.2.2.0.2.1 Usable length of siding

Format Example: <OPSidingParameter ID="IPP_Length" IsApplicable="Y" Value="4343" />


1.2.2.0.3.1 Gradient for stabling tracks

Applicability: Y only if it is above TSI value.

Format Example: <OPSidingParameter ID="ILL_Gradient" IsApplicable="NYA" />



version 0.5 – 2015-02-26 37

1.2.2.0.3.2 Minimum radius of horizontal curve expressed in meters


Format Example: <OPSidingParameter ID="ILL_MinRadHorzCurve" IsApplicable="Y" Value="265" />


1.2.2.0.3.3 Minimum radius of vertical curve


Format Example: <OPSidingParameter ID="ILL_MinRadVertCurve" IsApplicable="Y" Value="600+600" />


1.2.2.0.4.1 Existence of toilet discharge

Format Example: <OPSidingParameter ID="ITS_ToiletDischarge" IsApplicable="Y" Value="N" />


1.2.2.0.4.2 Existence of external cleaning facilities

Format Example: <OPSidingParameter ID="ITS_ExternalCleaning" IsApplicable="Y" Value="N" />


1.2.2.0.4.3 Existence of water restocking

Format Example: <OPSidingParameter ID="ITS_WaterRestocking" IsApplicable="Y" Value="N" />


1.2.2.0.4.4 Existence of refueling

Format Example: <OPSidingParameter ID="ITS_Refuelling" IsApplicable="Y" Value="N" />


1.2.2.0.4.5 Existence of sand restocking

Format Example: <OPSidingParameter ID="ITS_SandRestocking" IsApplicable="Y" Value="Y" />


1.2.2.0.4.6 Existence of electric shore supply


38 version 0.6 – 2015-02-26

Format Example: <OPSidingParameter ID="ITS_ElectricShoreSupply" IsApplicable="Y" Value="Y" />


1.2.2.0.5 Tunnel

Format Example: <OPSidingTunnel ValidityDateStart="2012-12-13">

Validation: If ValidityDateStart is greater than the date of the validation, the Siding Tunnel will be considereda FUTURE planning; otherwise, it is considered a CURRENT item.

1.2.2.0.5.1 IM’s Code

Format Example: <OPSidingTunnelIMCode Value="1234" />



Format Example: <OPSidingTunnelIdentification Value="TRXDD39" />

Validation: No validation will be performed by CUI. Check shall be done nationally.



Format Example: <OPSidingTunnelParameter ID="ITU_ECVerification" IsApplicable="Y"Value="EL/436195241ASDVG/2012/000090" />





Format Example: <OPSidingTunnelParameter ID="ITU_EIDemonstration" IsApplicable="Y"Value="EL/4361FRWS1ASDVG/2013/000002" />





version 0.5 – 2015-02-26 39

Applicability: Y only for a tunnel with length of 100 metres or more.

Format Example: <OPSidingTunnelParameter ID="ITU_Length" IsApplicable="N" />



Applicability: Y/N (if tunnel does not exist)/NYA

Format Example: <OPSidingTunnelParameter ID="ITU_EmergencyPlan" IsApplicable="Y" Value="N" />



Applicability: ‘N’=not applicable shall be selected for short tunnels of less than 1 km, as for them the firecategory according SRT TSI does not exist.

Format Example: <OPSidingTunnelParameter ID="ITU_FireCatReq" IsApplicable="Y" Value="10" />



Applicability: ‘N’=not applicable shall be selected when respective national rules do not exist

Y only for tunnels when for the parameter 1.2.2.0.5.7 the option ‘none’ was selected.

Format Example: <OPSidingTunnelParameter ID="ITU_NatFireCatReq" IsApplicable="N" />


RINF XML Data Validation Guide - European Union Agency … XML Data... · The RINF Validation...

Documents

Transcript of RINF XML Data Validation Guide - European Union Agency … XML Data... · The RINF Validation...