RINF XML Data Validation Guide
|
|
- Jonas Hunt
- 5 years ago
- Views:
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
Guide for the application of the CR NOI TSI
European Railway Agency According to Framework Mandate C(2007)3371 final of 13/07/2007 Reference in ERA: ERA/GUI/07-2011/INT Version in ERA: 1.01 Date: 03 December 2013 Document prepared by Document type:
More informationCOMMISSION DECISION. of
EUROPEAN COMMISSION Brussels, 6.11.2012 C(2012) 7325 final COMMISSION DECISION of 6.11.2012 amending Commission Decision 2012/88/EU on the technical specifications for interoperability relating to the
More informationGuide on the application of the common specification of the register of Infrastructure
Guide on the application of the common specification of the register of Infrastructure According to art 3 of Commission Implementing Decision 2014/880/UE of 26 ovember 2014 on the common specifications
More informationDevelopment of Optimum Assessment Technique for Railway Infrastructure Clearances
Development of Optimum Assessment Technique for Railway Infrastructure Clearances F. Moghadasnejad 1 and M. Fathali 2 1- Assistant Professor, moghadas@aut.ac.ir 2- PhD. Student, m_fathali@aut.ac.ir Amirkabir
More informationUser Manual. Document Information RDD-NLF. Date: Wed, 2017 May 17. Release Number: Version: Intrasoft International SA
RDD-NLF Document Information Date: Wed, 2017 May 17 Release Number: 3.5.1 Version: 0.13 Author(s): Reference: Intrasoft International SA ERA-031592-EN European Railway Agency, 120, rue Marc Lefrancq, F
More informationRECOMMENDATION FOR USE
Page 1 of 6 TITLE CONTENT OF THE TECHNICAL FILE ORIGINATOR NB-RAIL STRATEGY SG SUBJECT RELATED TO Directives 2008/57/EC, 2009/131/EC, 2011/18/EU, Recommendation 2011/217/EU, Decision 2010/713/EU and all
More informationQUESTION / CLARIFICATION
QUESTION / CLARIFICATION CO-ORDINATION BETWEEN NOTIFIED BODIES DIRECTIVE 2008/57/EC AND SUBSEQUENT AMENDMENTS ON THE INTEROPERABILITY OF THE RAIL SYSTEM WITHIN THE UNION QC-INF-015 Issue 01 Date: 25/02/2015
More informationFFFIS Juridical Recorder-Downloading tool
ERTMS/ETCS Class 1 FFFIS Juridical Recorder-Downloading tool REF : ISSUE : DATE : 2009-04-22 Company Technical Approval Management approval ALSTOM ANSALDO BOMBARDIER INVENSYS SIEMENS THALES FFFIS JR-Downloading
More informationImpact assessment for change to a Railway Group Standard, new Rail Industry Standard and withdrawal of associated RACOPs and Guidance Note
Impact assessment for change to a Railway Group Standard, new Rail Industry Standard and withdrawal of associated RACOPs and Guidance Note Version: Publication Date: 05 September 2017 Relevant Railway
More informationSicat CMS. siemens.com/mobility. Catenary monitoring system for overhead contact line systems
The contactless catenary monitoring system Sicat CMS continuously monitors the tensile forces in the contact wire and catenary wire and also acquires and evaluates the information. The filtered information
More informationRNE Common Components System (CCS)
RNE Common Components System (CCS) CSS & TAF/TAP regulations The requirements for the Common Components System (CCS) have been set by European Union legislation, namely: Commission Regulation (EC) No 62/2006
More informationThe Az S 350 U microcomputer axle counting system. Vacancy and occupancy detection of track sections.
The microcomputer axle counting system Vacancy and occupancy detection of track sections www.siemens.com/mobility The microcomputer axle counting system The safety of many individual components are vital
More informationEuropean Railway Agency. Electromagnetic Compatibility Requirements. Denmark
European Railway Agency Electromagnetic Compatibility Requirements Denmark Extract of the study on EMC Requirements Lloyd s Register - November 2010 1. Processes Compatibility demonstration in Denmark
More informationHow to fill out and submit off-line occurrence reports for. General Aviation. on my personal behalf
How to fill out and submit off-line occurrence reports for General Aviation as on my personal behalf Version 1.2, September 2017 Page 1 of 5 Scope The term on my personal behalf defines submission of a
More informationCLIMATE BONDS STANDARD VERIFICATION LETTER
CLIMATE BONDS STANDARD VERIFICATION LETTER Issuing Entity: The Metropolitan Transportation Authority Kind of engagement: Assurance Engagement Period engagement was carried out: December 21 st 2015 to January
More informationRST Standards Committee Chairman s presentation. Presented by Hugh O Neill 17 November 2016
RST Standards Committee Chairman s presentation Presented by Hugh O Neill 17 November 2016 1. Key issues from the last six months 1. Sanders Standard GMRT2461 issue 2 was published Jun 2016: 3 months early
More informationSpecification Voltage Limiting Device
Engineering Specification Electrical Networks L1-CHE-SPE-152 Specification Voltage Limiting Device Version: 1 Issued: 20 th April 2018 Owner: Chief Engineer Approved By: Andrew Russack Head of Engineering,
More informationUser Guide for VA Applicants
OSS User Guide for VA Applicants v0.52 Making the railway system work better for society. User Guide for VA Applicants Name Drafted by Validated by Approved by Intrasoft International S.A. Spilios Vergopoulos
More informationECAS. Conversion Specification. Provided to ECAS. Issue 4.1. Document No.
ECAS Mobile Conversion Specification Location Provided to ECAS Issue 4.1 Document No. Document Information Document Title Mobile Location Conversion Specification Filename Mobile Location Conversion Specification
More informationTsutomu Morimura Central Japan Railway Company
1 Introduction of the N700-I Bullet Train The World s Safest and Most Efficient High Speed Rail System January 13, 2012 Tsutomu Morimura Central Japan Railway Company 2 Contents of Presentation - Overview
More informationThis document is a preview generated by EVS
INTERNATIONAL STANDARD ISO 13141 First edition 2015-12-01 Electronic fee collection Localisation augmentation communication for autonomous systems Perception de télépéage Communications d augmentation
More informationMemorandum of Understanding
Memorandum of Understanding between the European Commission, the European Union Agency for Railways and the European rail sector associations (CER, EIM, EPTTOLA, ERFA, the ERTMS Users Group, GSM-R Industry
More informationETSI EN V1.2.1 ( )
EN 302 999 V1.2.1 (2013-03) European Standard Safety; Remote Power Feeding Installations; Safety requirements for the erection and operation of information technology installations with remote power feeding
More informationSTBEHC3020KC counter kit STB - 1 CH Hz - 2 I
Characteristics counter kit STB - 1 CH - 0..40000 Hz - 2 I Main Range of product Product or component type Number of channels 1 Complementary Kit composition Counting input number 2 Counting frequency
More informationGPRS-T1. Monitoring Converter. SATEL sp. z o.o. ul. Schuberta Gdańsk POLAND tel
Monitoring Converter GPRS-T1 Program version 1.01 gprs-t1_en 04/09 SATEL sp. z o.o. ul. Schuberta 79 80-172 Gdańsk POLAND tel. + 48 58 320 94 00 info@satel.pl www.satel.pl WARNINGS The module should only
More informationData sheet. Constant current DALI LED control gear 80 W Output power ma Output current Intelligent temperature protection.
Data sheet Constant current DALI LED control gear 8 W Output power 5 7 ma Output current Intelligent temperature protection Linear VI LED Linear VI LED control gear More than 25 years of experience in
More informationSafety module - PSR-SCP- 24DC/TS/S
Please be informed that the data shown in this PDF Document is generated from our Online Catalog. Please find the complete data in the user's documentation. Our General Terms of Use for Downloads are valid
More informationProduct Information. Door closing force measurement Type:HGE-DC700N DataManager Software. According to: EN 14752:2015
Product Information Door closing force measurement Type:HGE-DC700N DataManager Software According to: EN 14752:2015 Your advantage: Meets all requirements of the standard EN 14752:2015 Compact force sensor
More informationSAX.. ACVATIX Electromotive actuators for valves. with a 20 mm stroke
s 4 501 ACVATIX Electromotive actuators for valves SAX.. with a 20 mm stroke SAX31.. Operating voltage AC 230 V, 3-position control signal SAX61.. Operating voltage AC/DC 24 V, control signal DC 0 10 V,
More informationRECOMMENDATION FOR USE
Page 1 of 23 TITLE CONTENT OF EC CERTIFICATE/ QMS-APPROVAL/ ISV ORIGINATOR NB-RAIL SUB-GROUP STRATEGY SUBJECT RELATED TO DIRECTIVE 2008/57/EC (AS AMENDED BY 2009/131/EC, 2011/18/EU, 2010/713/EU, 2013/9/EU,
More informationGI/GN7633. Guidance on Lineside Signs. Rail Industry Guidance Note for GI/RT7033. Issue One: June 2015
GN This document contains one or more pages which contain colour. Published by: Copyright 2015 Rail Safety and Standards Board Limited GI/GN7633 Issue One: June 2015 Rail Industry Guidance Note for GI/RT7033
More informationThe Rolling Stock Innovation Centre
The Rolling Stock Innovation Centre Universities and Industry working together to deliver the next generation of railway vehicles Part of the UK Rail Research and Innovation Network (UKRRIN) The University
More informationLine Impedance Stabilization Network (LISN)
Model 3816/2 Line Impedance Stabilization Network (LISN) User Manual ETS-Lindgren Inc. reserves the right to make changes to any product described herein in order to improve function, design, or for any
More informationUC th Users Conference on BiAxial Fatigue Testing November 11 th, 2015
UC 12 12 th Users Conference on BiAxial Fatigue Testing November 11 th, 2015 UC 12-2015-11-11 Robert Keplin M.Sc. Fraunhofer-Institut für Betriebsfestigkeit und Systemzuverlässigkeit LBF www.lbf.fraunhofer.de
More informationSicat CMS. Features. Catenary monitoring system for overhead contact line systems. siemens.com/rail-electrification
Sicat CMS Catenary monitoring system for overhead contact line systems siemens.com/rail-electrification The contactless catenary monitoring system Sicat CMS continuously monitors the tensile forces in
More informationIRMA MATRIX Release 2 Data sheet
Automatic passenger counting IRMA Infrared Motion Analyzer 5th generation IRMA MATRIX Release 2 Data sheet Sensor versions DIST500-A DIST500-F iris-gmbh Ostendstrasse 1 14 12459 Berlin Germany www.irisgmbh.de
More informationThe UK Rail research and Innovation Network
Capacity for Rail The UK Rail research and Innovation Network Professor Simon Iwnicki, University of Huddersfield UK University Railway Research Since the development of Railway Research UK in 2003 which
More informationNERC Transmission Availability Data System (TADS): Element Identifier Data Submission Addendum
Transmission Availability Data System (TADS) Element Identifier Data Submission Addendum May 28, 2013 3353 Peachtree Road NE NERC Transmission Availability Data System (TADS): Element Identifier Data Submission
More informationElectronic File Location. CCMS ref: Version History
Electronic File Location CCMS ref: 64153205 Version History Issue Date Comments 1.0 14/06/13 Initial draft for internal review and comment 1.1 24/09/13 Updated for further internal review 1.2 21/11/13
More informationISO/IEC INTERNATIONAL STANDARD
INTERNATIONAL STANDARD ISO/IEC 15420 First edition 2000-12-15 Information technology Automatic identification and data capture techniques Bar code symbology specification EAN/UPC Technologies de l'information
More informationDraft Amendments to the Fuel Economy Test Method for Motorcycles
Attachment Draft Amendments to the Fuel Economy est Method for Motorcycles 1. est items 1.1 Fuel economy of motorcycles tested by using simulated urban driving cycle. 1.2 Fuel economy of motorcycles tested
More informationPower supply module, bus connection module
s 8 183 8183p01, p02 TX-I/O Power supply module, bus connection module TXS1.12F10 TXS1.EF10 Each I/O row begins with one of these devices TXS1.12F10 power supply module Up to 4 power supply modules can
More informationABL8RPS24030 regulated SMPS - 1 or 2-phase V - 24 V - 3 A
Characteristics regulated SMPS - 1 or 2-phase - 100..500 V - 24 V - 3 A Product availability : Stock - Normally stocked in distribution facility Price* : 270.00 USD Main Range of product Product or component
More informationATV12P037F1 variable speed drive ATV kW hp V - 1ph - on base plate
Characteristics variable speed drive ATV12-0.37kW - 0.55hp - 100..120V - 1ph - on base plate Complementary Main Range of product Altivar 12 Product or component type Product destination Product specific
More informationABL8WPS24200 regulated SMPS - 3-phase V AC - 24 V - 20 A
Characteristics regulated SMPS - 3-phase - 380..500 V AC - 24 V - 20 A Product availability : Stock - Normally stocked in distribution facility Price* : 735.00 USD Main Range of product Product or component
More informationCHAPTER 6. Computer Model
CHAPTER 6 Computer Model 6.1 Introduction In the previous chapters, the underlying principles that a designer of photovoltaic systems needs to understand before beginning the design process have been addressed.
More informationUL TEST REPORT AND PROCEDURE
Issue Date: 2013-04-10 Page 1 of 16 Report Reference # E135803-A73-UL UL TEST REPORT AND PROCEDURE Standard: Certification Type: CCN: Product: Model: Rating: UL 60950-1, 2nd Edition, 2011-12-19 (Information
More informationABL8RPS24100 regulated SMPS - 1 or 2-phase V - 24 V - 10 A
Characteristics regulated SMPS - 1 or 2-phase - 100..500 V - 24 V - 10 A Product availability : Stock - Normally stocked in distribution facility Price* : 525.00 USD Main Range of product Product or component
More informationNDT Certification for Railway Maintenance Personnel in France; 10 Years of the CFCM
5th International Conference on Certification and Standardization in NDT - Lecture 29 NDT Certification for Railway Maintenance Personnel in France; 10 Years of the CFCM Jacques BOUVY, Comité Ferroviaire
More informationAutomotive Electronics Council Component Technical Committee
ATTACHMENT 11 CHARGED DEVICE MODEL (CDM) ELECTROSTATIC DISCHARGE TEST Acknowledgment Any document involving a complex technology brings together experience and skills from many sources. The Automotive
More informationDX 3 MCB A / 16 ka 80 A to 125 A (1,5 module per pole)
87045 LIMOGES Cedex Telephone: +33 5 55 06 87 87 FAX: +33 5 55 06 88 88 DX 3 MCB 10000 A / 16 ka CONTENTS PAGES 1. Description - Use... 1 2. Range... 1 3. Overall dimensions... 1 4. Preparation - Connection...
More informationATV12H018M2 variable speed drive ATV kW hp V - 1ph
Characteristics variable speed drive ATV12-0.18kW - 0.25hp - 200..240V - 1ph Complementary Main Range of product Altivar 12 Product or component type Product destination Product specific application Assembly
More informationLION SAFE Remote I/O System. LÜTZE TRANSPORTATION GMBH Dimitrios Koutrouvis V00
Page 1 LÜTZE TRANSPORTATION GMBH Dimitrios Koutrouvis V00 Actual Market Situation New Safety Requirements from Standards and Authorities Governance European Union (EU) ==> European Railway Agency (ERA)
More informationISO/TS TECHNICAL SPECIFICATION. Transport information and control systems Traffic Impediment Warning Systems (TIWS) System requirements
TECHNICAL SPECIFICATION ISO/TS 15624 First edition 2001-01-15 Transport information and control systems Traffic Impediment Warning Systems (TIWS) System requirements Systèmes de commande et d'information
More information: EUROCONTROL Specification. for Surveillance Data Exchange ASTERIX Part 26 Category 025 CNS/ATM Ground System Status Reports
EUROCONTROL Specification for Surveillance Data Exchange ASTERIX Part 26 Category 025 CNS/ATM Ground System Status Reports DOCUMENT IDENTIFIER : Edition Number : 1.2 Edition Date : 17/04/2018 Status :
More informationNetwork Certification Body
Network Certification Body Scheme rules for assessment of Entities in Charge of Maintenance in accordance with requirements of ECM Regulation EU 445/2011 ECM certification scheme 1 NCB_MS_106_ECM Introduction
More informationITU-T G.979. Characteristics of monitoring systems for optical submarine cable systems
I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T G.979 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (11/2016) SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND
More informationWP5 Demonstrator - Functional Specifications. Patrick Deutsch, Nicolas Van Landeghem, Didier Weckmann, Alexis Julin
openetcs OETCS/WP5/D5.1 Work-Package 5: Demonstrator WP5 Demonstrator - Functional Specifications Patrick Deutsch, Nicolas Van Landeghem, Didier Weckmann, Alexis Julin This work is licensed under the "openetcs
More informationATV310H075N4E variable speed drive ATV kw - 1 hp V - 3 phase
Characteristics variable speed drive ATV310-0.75 kw - 1 hp - 380...460 V - 3 phase Main Range of product Altivar Easy 310 Product or component type Product specific application Assembly style Device short
More informationMyOwnDeliveries. a Magento module. User manual
MyOwnDeliveries a Magento module User manual Summary Installation 3 On the front office 4 When ordering 4 When subscribing 6 Booking system 7 Delivery sub areas 7 time slots occupation 7 Reservation windows
More informationABB component drive ACS50, 0.18 to 2.2 kw Technical catalogue PRODUCTS
ABB component drive ACS50, 0.18 to 2.2 kw Technical catalogue PRODUCTS ABB component drive What is an ABB component drive? The ABB component drives meet the requirements of OEMs, installation companies
More informationSERIES X: DATA NETWORKS, OPEN SYSTEM COMMUNICATIONS AND SECURITY. ITU-T X.660 Guidelines for using object identifiers for the Internet of things
I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Series X Supplement 31 (09/2017) SERIES X: DATA NETWORKS, OPEN SYSTEM COMMUNICATIONS
More informationQUINT-PS/ 1AC/24DC/ 5
Extract from the online catalog QUINT-PS/ 1AC/24DC/ 5 Order No.: 2866750 DIN rail power supply unit 24 V DC/5 A, primary switched-mode, 1- phase. The SFB technology (Selective Fuse Breaking Technology)
More informationG.SHDSL NTU with Fixed Serial Interfaces
DECEMBER 2006 ME231A ME232A ME233A G.SHDSL NTU with Fixed Serial Interfaces CUSTOMER Order toll-free in the U.S. 24 hours, 7 A.M. Monday to midnight Friday: 877-877-BBOX SUPPORT FREE technical support,
More informationMESP TECHNICAL SPECIFICATION FOR A RECTIFIER UNIT CONTROL & PROTECTION SYSTEM FOR USE IN THE 1500V DC TRACTION SYSTEM
Engineering Specification Electrical Networks TECHNICAL SPECIFICATION FOR A RECTIFIER UNIT CONTROL & PROTECTION SYSTEM FOR USE IN THE 1500V Version: 1 Issued: March 2014 Owner: Electrical Networks Asset
More informationSpark gap surge arrester for direct current OLE line
Spark gap surge arrester for direct current OLE line System suitable to ensure surge protection to equipment and devices connected to (Overhead Line Electrification) OLE lines operating under direct current.
More informationMiCOM P122C Time-Overcurrent Protection
Protection Relays 01 MiCOM P122C Time-Overcurrent Protection Customer Benefits 1A/5A software setting 4 function keys Compact unit for flush and wall-surface mounting Comprehensive measurements Disturbance
More informationMiniature Circuit Breakers for Railway Applications
Siemens AG 00 for Railway Applications BETA Low-Voltage Circuit Protection The miniature circuit breakers are used in fixed railway systems and rolling stock for protecting system components against overcurrent
More informationRTSS User s Manual. For RTSS Version DR RYO TAKAGI
RTSS User s Manual For RTSS Version 2.6.4 DR RYO TAKAGI 2011. 1. 12 Table of Contents XML Data File Lists... iv 1 Overview... 1 1.1 What is RTSS?... 1 1.2 What is the history of RTSS?... 1 1.3 What is
More informationERWA UNIFE Railway Wheels Committee
ERWA UNIFE Railway Wheels Committee Jean-Pierre Auger Chairman of ERWA UNIFE General Assembly 19 June 2008 ERWA, the association of European producers of railway wheels and wheelsets was established in
More informationConnect - Contact - Control. Connectors according to UIC VE EP Series. F 121.en
Connect - Contact - Control Connectors according to UIC 541-5 VE 123 F 121.en 2 Connector to UIC standard 541-5 VE, The connector is designed in accordance with the specifications of the international
More informationTransportation Solutions LÜTZE Rail Technology. Product overview Control Technology
Transportation Solutions LÜTZE Rail Technology Product overview Control Technology Control Technology Remote I/O Module Ethernet/IP DIOLINE 20 Passenger Information System DIOSWITCH IP 67 Remote I/O Module
More informationTrack Side On Board Mobile Communications. Dennis Schut UIC Research Manager
Track Side On Board Mobile Communications Dennis Schut UIC Research Manager Track Side On Board Operational Communication In Europe, the radio system supporting track side-on - board communications is
More informationABL8RPS24100 regulated SMPS - 1 or 2-phase V - 24 V - 10 A
Characteristics regulated SMPS - 1 or 2-phase - 100..500 V - 24 V - 10 A Main Range of product Product or component type Power supply type Input voltage Output voltage Rated power in W Jun 27, 2018 Phaseo
More informationStatement of compliance no 40/2011
-1- ST-65 module GSM v1.0.7 Statement of compliance no 40/2011 We, the company TECH, headquartered in Wieprz 1047A, 34122 Wieprz, declare with full liability, that the controller ST 65 GSM, produced by
More informationINTEROPERABILITY UNIT TRANS-EUROPEAN CONVENTIONAL RAIL SYSTEM SUBSYSTEM TELEMATICS APPLICATIONS FOR FREIGTH
EUROPEAN RAILWAY AGENCY INTEROPERABILITY UNIT TRANS-EUROPEAN CONVENTIONAL RAIL SYSTEM SUBSYSTEM TELEMATICS APPLICATIONS FOR FREIGTH Reference: Document Type: User acceptance test of the common interface
More informationSoftware Requirements Specification. for WAVED. Version 3.0. Prepared By:
Software Requirements Specification for WAVED Version 3.0 Prepared By: Sean Bluestein, Kristian Calhoun, Keith Horrocks, Steven Nguyen, Hannah Pinkos Advisor: Kurt Schmidt Stakeholder: Climate Central
More informationSELF SERVICE INTERFACE CODE OF CONNECTION
SELF SERVICE INTERFACE CODE OF CONNECTION Definitions SSI Administration User Identity Management System Identity Provider Service Policy Enforcement Point (or PEP) SAML Security Patch Smart Card Token
More informationCatalog. Arc Guard System TM TVOC-2
Catalog Arc Guard System TM TVOC-2 Introduction An even better Arc Guard System TVOC-2, ABB s latest Arc Monitor, builds on the well known TVOC design. Its new functions and features improve an already
More informationMobile Communications for the Transport Sector
White paper Oct 2012 Mobile Communications for the Transport Sector Public transport, as basic means of providing mobility for the general population, is a key factor in the development of our society.
More informationABL8WPS24400 regulated SMPS - 3-phase V - 24 V - 40 A
Characteristics regulated SMPS - 3-phase - 380..500 V - 24 V - 40 A Main Range of product Product or component type Power supply type Input voltage Output voltage Rated power in W Jan 11, 2018 Phaseo Power
More informationIdentification cards Recording technique. Part 1: Embossing. Cartes d identification Technique d enregistrement Partie 1: Estampage
Provläsningsexemplar / Preview INTERNATIONAL STANDARD ISO/IEC 7811-1 Fourth edition 2014-09-01 Identification cards Recording technique Part 1: Embossing Cartes d identification Technique d enregistrement
More information25th of October EuroMedRail project National Safety Authority Belgium
25th of October 2017 - EuroMedRail project National Safety Authority Belgium 2 Content 1. Legal basis and history 2. The Belgian rail system 3. Railway safety in Belgium 2016 4. The Belgian NSA : DRSI
More informationGUIDELINES ON FEATURES AND TECHNICAL SPECIFICATIONS FOR MOBILE CELLULAR DEVICES IMPORTED INTO AND DISTRIBUTED IN KENYA
GUIDELINES ON FEATURES AND TECHNICAL SPECIFICATIONS FOR MOBILE CELLULAR DEVICES IMPORTED INTO AND DISTRIBUTED IN KENYA June 2018 Table of Contents 1. Scope... 3 2. References... 4 3. Abbreviations and
More informationTM3AI4 module TM3-4 analog inputs
Characteristics module TM3-4 analog inputs Main Range of product Product or component type Range compatibility Analogue input number 4 Analogue input type Complementary Analogue input resolution Permissible
More information300W 1.5kW, QUBE Fiber Lasers
Technical Specification 300W 1.5kW, QUBE Fiber Lasers CONTENTS 1.1 SCOPE 2 1.2 OPTICAL SPECIFICATION 2 1.3 BEAM DELIVERY FIBER SPECIFICATION 3 1.4 ALIGNMENT LASER 3 1.5 POWER DISTRIBUTION 3 1.6 WATER COOLING
More informationAir data test indicator Model CPA2501
Calibration technology Air data test indicator Model CPA2501 WIKA data sheet CT 29.02 Applications Aviation calibration laboratories Aviation repair stations Manufacturers of avionics equipment Manufacturers
More informationDMT PERFORMING UNDER PRESSURE DMT. Applications. Special features. Description 1/9
Applications Aviation calibration laboratories Aviation repair stations Manufacturers of avionics equipment Manufacturers of aerospace equipment Wind tunnels Special features, model CPA2501 Accuracy up
More informationDANGER indicates that death or severe personal injury will result if proper precautions are not taken.
SIMATIC ET 200S distributed I/O SIMATIC ET 200S distributed I/O Digital electronic module 4DI DC24V HF (6ES7131-4BD01-0AB0) Manual Preface Properties 1 Parameters 2 Diagnostics 3 04/2007 A5E01077141-01
More informationABL8MEM24006 regulated SMPS - 1 or 2-phase V AC - 24 V A
Characteristics regulated SMPS - 1 or 2-phase - 100..240 V AC - 24 V - 0.6 A Complementary Input voltage limits Network frequency Inrush current Main Range of product Product or component type Power supply
More informationThis manual is for financial service provider (FSP) members of CIO in using the CIO self-service Portal.
CIO FSP Portal Manual 2017 Who is this manual intended for This manual is for financial service provider (FSP) members of CIO in using the CIO self-service Portal. Logging In The Portal can be accessed
More informationATV12H075M3 variable speed drive ATV kW - 1hp V - 3ph - with heat sink
Product datasheet Characteristics ATV12H075M3 variable speed drive ATV12-0.75kW - 1hp - 200..240V - 3ph - with heat sink Complementary Main Range of product Altivar 12 Product or component type Product
More informationDesign and Installation Guide
Design and Installation Guide Avigilon License Plate Recognition System Version 1.3 920-0028A-Rev3 Copyright 1/19/12 Avigilon. All rights reserved. No copying, distribution, publication, modification,
More informationInstaller manual. Eikon Arké Plana BUS EnOcean interface - 2 modules
Installer manual Eikon 20508 Arké 19508 Plana 14508 BUS EnOcean interface - 2 modules Instructions This manual is necessary in order to configure the radio-frequency devices when used with the By-me automation
More informationInstaller manual. Eikon Arké Plana BUS EnOcean interface - 2 modules
Installer manual Eikon 20508 Arké 19508 Plana 14508 BUS EnOcean interface - 2 modules Instructions This manual is necessary in order to configure the radio-frequency devices when used with the By-me automation
More informationPSI-MODEM-SHDSL/SERIAL Copper Extender
PSI-MODEM-SHDSL/SERIAL Copper Extender perle.com /products/serial-extenders/psi-modem-shdsl-serial-extender.shtml RS232/422/485 over copper wire Transmit serial data up to 20km [12.4 mi] Two SHDSL ports
More informationComponents Power Supplies and Converters TALIS48 AC/DC Converter Generic Product Catalog
Components Power Supplies and Converters TALIS48 AC/DC Converter Generic Product Catalog Power Supplies and Converters - TALIS48 AC/DC Converter Table of Contents Introduction TALIS power supply module...
More informationSecureETag TM Dealer Module User s Guide
TM Dealer Module User s Guide Version 1.0 July 2018 User s Guide Dealer Module Version 1.0 This document contains information belonging to OpSec Security Inc.; its use is provided under a license agreement
More informationATV310HU30N4E variable speed drive ATV310-3 kw - 4 hp V - 3 phase
Characteristics variable speed drive ATV310-3 kw - 4 hp - 380...460 V - 3 phase Complementary Product destination Main Range of product Altivar Easy 310 Product or component type Product specific application
More informationto 48V DC Power Supply
Telecommunications Group Section 855-080-201 Equipment Issue 1 Second Printing, July 2007 8550-80 24 to 48V DC Power Supply Compliant with UL Standard 60950, Second Edition* CONTENTS PAGE Part 1. GENERAL.............................................................................
More information