IS:energyRollingstock

Introduction

When building trans-European high-speed railways the design of the overhead contact line shall comply with EN 50119:2001. The design and operation of overhead contact lines presumes that pantographs are equipped with an automatic dropping device (ADD) (see High Speed Rolling Stock TSI clauses). ADD is a device that automatically lowers the pantograph on electric trains to prevent additional damages in case of obstructions or emergencies. It is also known as pantograph dropping device .

Documentation

Syntax

3.33.23.1

Autoexport from the XML-Schema for element IS:energyRollingstock of railML® version 3.3      UML-visualization of IS
Description	child element summarizing the rollingstock energy parameters
Subschema	infrastructure
Parents*	electrificationSection
Children	None
Attributes: permittedMaxContactForce: value of the permitted maximum (dynamic) contact force of the pantograph, in [N] (optional: tForceN : xs:decimal), permittedStaticContactForce: value of the permitted static contact force of the pantograph, in [N] (optional: tForceN : xs:decimal), requiredFireCategory: information on the required fire category of the rolling stock. version 2019 Guide for the application of the Technical Specification for Interoperability on Safety in Railway Tunnels adopted by Commission Regulation (EU) No 1303/2014 of 18 November 2014 amended by Commission Implementing Regulation (EU) 2019/776 of 16 May 2019. Version 2023 Guide for the application of the LOC&PAS TSI Technical Specification for Interoperability for the “rolling stock subsystem - Locomotives and passenger rolling stock. (optional: tRSFireCategoryType : xs:string) Possible values: A: e.g. for passenger rolling stock side evacuation possible, Train will continue to drive to a safe area etc B: e.g. for passenger rolling stock fire barriers are provided to facilitate the protection of passengers and staff from the effects of heat and smoke on board a burning train for 15 minutes etc. none, requiresAutomaticDroppingDevice: flag, whether an automatic dropping device at the pantographs is required (optional: xs:boolean : xs:boolean), requiresPowerLimitation: flag, whether a current or power limitation on board is required (optional: xs:boolean : xs:boolean)
*Notice: Elements may have different parent elements. As a consequence they may be used in different contexts. Please, consider this as well as a user of this Wiki as when developing this documentation further. Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.

Autoexport from the XML-Schema for element IS:energyRollingstock of railML® version 3.2      UML-visualization of IS
Description	child element summarizing the rollingstock energy parameters
Subschema	infrastructure
Parents*	electrificationSection
Children	None
Attributes: permittedMaxContactForce: value of the permitted maximum (dynamic) contact force of the pantograph, in [N] (optional: tForceN : xs:decimal), permittedStaticContactForce: value of the permitted static contact force of the pantograph, in [N] (optional: tForceN : xs:decimal), requiredFireCategory: information on the required fire category of the rolling stock. version 2019 Guide for the application of the Technical Specification for Interoperability on Safety in Railway Tunnels adopted by Commission Regulation (EU) No 1303/2014 of 18 November 2014 amended by Commission Implementing Regulation (EU) 2019/776 of 16 May 2019. Version 2023 Guide for the application of the LOC&PAS TSI Technical Specification for Interoperability for the “rolling stock subsystem - Locomotives and passenger rolling stock. (optional: tRSFireCategoryType : xs:string) Possible values: A: e.g. for passenger rolling stock side evacuation possible, Train will continue to drive to a safe area etc B: e.g. for passenger rolling stock fire barriers are provided to facilitate the protection of passengers and staff from the effects of heat and smoke on board a burning train for 15 minutes etc. none, requiresAutomaticDroppingDevice: flag, whether an automatic dropping device at the pantographs is required (optional: xs:boolean : xs:boolean), requiresPowerLimitation: flag, whether a current or power limitation on board is required (optional: xs:boolean : xs:boolean)
*Notice: Elements may have different parent elements. As a consequence they may be used in different contexts. Please, consider this as well as a user of this Wiki as when developing this documentation further. Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.

Autoexport from the XML-Schema for element IS:energyRollingstock of railML® version 3.1      UML-visualization of IS
Description	child element summarizing the rollingstock energy parameters
Subschema	infrastructure
Parents*	electrificationSection
Children	None
Attributes: requiresPowerLimitation: flag, whether a current or power limitation on board is required (optional: xs:boolean : xs:boolean), permittedStaticContactForce: value of the permitted static contact force of the pantograph, in [N] (optional: tForceN : xs:decimal), permittedMaxContactForce: value of the permitted maximum (dynamic) contact force of the pantograph, in [N] (optional: tForceN : xs:decimal), requiresAutomaticDroppingDevice: flag, whether an automatic dropping device at the pantographs is required (optional: xs:boolean : xs:boolean), requiredFireCategory: information on the required fire category of the rolling stock (optional: tRSFireCategoryType : xs:string) Possible values: none B A
*Notice: Elements may have different parent elements. As a consequence they may be used in different contexts. Please, consider this as well as a user of this Wiki as when developing this documentation further. Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.

Changes 3.1→3.2

There exists an overview of all changes between railML^® 3.1 and railML^® 3.2 on page Dev:Changes/3.2.

The attributes have been changed.

Best Practice / Examples

This example is based on ERA knowledge graph (external link).

<infrastructure id="is_01">
  <topology>
    <netElements>
      <netElement id="ne_a11">
        <elementCollectionUnordered id="ne_a11_ecu01">
          <elementPart ref="ne_a01"/>
        </elementCollectionUnordered>
      </netElement>
    </netElements>
  </topology>
  <functionalInfrastructure>
    <electrificationSections>
      <electrificationSection id="es01">
        <energyRollingStock requiresAutomaticDroppingDevice="false"/>
        <linearLocation id="es01_lloc01" applicationDirection="both">
          <associatedNetElement netElementRef="ne_a01" keepsOrientation="true"/>
        </linearLocation>
      </electrificationSection>
    </electrificationSections>
    <lines>
      <line id="lineSection1" >
        <name name="Budapest-Déli-Budapest-Kelenföld" language="hu"/>
        <linearLocation id="lin01_lloc01" applicationDirection="both">
          <associatedNetElement netElementRef="ne_a11" keepsOrientation="true"/>
        </linearLocation>
        <beginsInOP ref="opp01"/>
        <endsInOP ref="opp02"/>
      </line>
    </lines>
    <operationalPoints>
      <operationalPoint id="opp01">
        <name name="Budapest-Déli" language="hu"/>
        <connectedToLine ref="lineSection1"/>
      </operationalPoint>
      <operationalPoint id="opp02">
        <name name="Budapest-Kelenföld" language="hu"/>
        <connectedToLine ref="lineSection1"/>
      </operationalPoint>
    </operationalPoints>
    <tracks>
      <track id="tr01" type="mainTrack">
        <linearLocation id="tr01_lloc01" applicationDirection="both">
          <associatedNetElement netElementRef="ne_a01" keepsOrientation="true"/>
        </linearLocation>
      </track>
    </tracks>
  </functionalInfrastructure>
</infrastructure>

Additional Information

🗒️ This segment provides background information that is not relevant for the certification process.

Example was reviewed by the coordinator (link to the railML^® website) of the Infrastructure subschema on 2025-11-11.