Documentation | TTR ECMT

Introduction

The European Capacity Management Tool (ECMT) is an online application providing a centralised capacity supply and capacity model overview of railway lines and routes. The tool consolidates capacity needs and capacity restrictions on the railway infrastructure based on the information provided by Infrastructure Managers and Allocation Bodies. It offers capacity supply and capacity model visualisations and other related functionalities.

ECMT was first launched as part of the Timetable Redesign (TTR) Pilots, and in the future, it will also intend to play the role of the capacity hub in Digital Capacity Management (DCM).

The following document aims to give an overview of ECMT structure, functionalities and constraints.

1. Access to ECMT

1.1 ECMT account, log in and password reset.

New account request, log in and password resets are available on the ECMT home page.

New Account

1.1.1 Request a new ECMT account

The request for the creation of an ECMT account can be sent via the “Request new account” formular on the ECMT homepage or by sending an email to the ECMT support team: support.ecmt@rne.eu.

The requested accounts are reviewed and approved by the ECMT support team. Once the request is approved, the requester will receive the login credentials via email.

Request New Account

1.1.2 Password reset

The user provides his/her email address. The email with the instructions for the password reset will be shortly received.

1.1.3 Login

The email address provided in the new account request and the password after the account creation, need to be entered on the ECMT home page.

1.2 Access rights

Based on the user’s company (selected in the registration step), and the company’s attributes defined in CRD (The Central Reference File Database), the user would be defined as either “IM” or as “Applicant”.

If the user belongs to IM, he would be able to define Capacity Model data objects for PLCs which do belong to his network (and no other IM, unless additionally defined in Access Right Module).

In case if user belongs to the Applicant company, the user would be able to define the Capacity Need Announcement.

The following menus, functions and information are publicly available with an anonymous profile and do not require an ECMT account:

Chart menu
Search menu (including overlapping objects detection function)

Only objects with a “published” status are visible on: charts, in search results and their object page.

The following user roles are available and provide the following additional features:

Read-only role: custom save search
Editor role: all objects are visible and objects in the preparation phase are editable.

With an editor role, the editing rights on an object are available if the user is an editor on all the lines that are used by the route of the object. If the user is not an editor on at least one part of the route, the object will be read-only.

1.3 Access rights module

In this menu, IM users with the before mentioned Editor role can give members of other companies permission to view and/or edit objects of their company. These rights can either be given permanently or for a limited amount of time and can be revoked at any point. Additionally, users can give these permissions to all users of a company at once, in case two companies share a physical network and its responsibilities. Access can be given for Rights for other companies cannot be requested in the tool, they can only be given to others.

Users from company which gave rights to 3rd party can see what user/companies have access to their data.

Add new access right

Access Right

2. ECMT menus

ECMT navigation is organized around two menus for the anonymous users, three menus for the users with a read-only role and five menus for the users with an editor role.

2.1 +Add CNA

2.2 Overview

This menu lists all objects, which have been created or edited by the user. A detailed view of these objects can be accessed using the links provided in the same rows as them. The Overview page can also be found under “My profile”.

2.3 ECMT Tabfolder

This menu contains all the items from Capacity Model and Capacity Supply:

ECMT Tabfolder

The Capacity Model contains three overviews:

Section Overview: Capacity situation between two PLCs (e.g. to gather information on the planned volumes for a border section). Mostly used by Applicants.
Line Overview: Capacity situation on a selected line to facilitate the cross-border harmonisation and creation of variants (e.g. during TCR periods). Mostly used by IMs, Applicants
Network Overview: General overview on capacity on a very high level (e.g. capacity situation of a selected country). Mostly used by higher management levels, Ministry of Transport, etc.

The CapacitySupply shows so called “train graph” on international level, including TCRs.

2.3.1 Capacity Model

2.3.1.1Section Overview

Section Overview1

2.3.1.2 Line Overview

Line Overview

2.3.1.3 Network Overview

Network1

2.3.2 Capacity Supply Chart

2.3.2.1. Structure of the chart

The space-time chart presents the objects positioned on a line or route according to the chart filters. The timeline is on the x-axis and the line/route locations are listed on the y-axis with a spacing considering the actual distance between the locations.

Chart features:

Route filter: the chart can be based on a line or a route. In case of a route, the “From location” and “To location” shall be informed by the user and the tool calculates shortest route between these two locations considering the waypoint (optional field). The tool generates the chart with objects that are either fully or partially positioned on the generated route. As soon as there is one common location between two lines, the tool assumes the transfer of the train from one to another is possible.
Zoom sliders: a zoom on a specific line, route or timeline section is possible with the zoom slider bars (thick grey lines above and on the right side of the chart)

Link to the object page: a click with the mouse on the object positioned on the chart triggers the opening of the object page in a new tab.
Tooltip: a mouse hover on the object positioned on the chart triggers the display of a text box containing basic information about the object.

Chart 1

Object representations:

Path and Catalogue Path: line
Capacity Band and TCRs: shape depending on the timetable

2.3.2.2 How to read the chart?

Objects are positioned on the chart based on their timetable.

Practical example:

Case:

First a path, a TCR and a capacity band have been created on a route starting from J, passing by locations L and M and ending at N.
Secondly an ECM chart has been generated by for a route from A to N via J. The locations sequence calculated by the tool for this route is A-B-I-J-L-M-N.
It is relevant to note that the three created objects are located on the route from A to N via J.

Interpretations:

The zoom sliders have been adjusted to focus on the J-L-M-N route section between 01:00 and 16:00.
The legend at the bottom of the chart refers to all objects included on the chart for route A-B-I-J-L-M-N.
Path - Solid green line: the train arrives at location J at 8:00 and departs at 8:30. Between 11:45 and 12:00 it stays at location M and arrives at location N at 16:00.
TCR - Blue line: TCR between 11:00 and 11:50 between locations J and M.
Capacity Band – Yellow band: capacity planned with a 30minute timeframe from location J to N.

4.3. Object positioning over different lines and routes

Objects are defined with a timetable on the entire length or on a partial section of a line or route, but the object information is stored per location. Therefore, objects may appear either fully, or partially on other line / route charts and in the search results depending on the selected line and route and their potential timetable overlap.

2.3. Search

This menu contains the search function and the overlapping objects detection feature. Please refer to section 4 for more information.

2.4. Data (available with editor role)

This menu contains the object creation, editing and import functions. Please refer to section 7 for more information.

2.5. My profile (available with read-only and editor roles)

This menu contains the basic information about the user’s account (name, e-mail address etc)

3. Objects

3.1. Object types

Path (PA): capacity planned for one train.
Capacity Band (CB): capacity planned for more than one path within a specific timeframe and with a predefined number of capacity slots.
Catalogue Path (CP): pre-constructed capacity paths prepared by the infrastructure managers and offered to applicants.
Temporary Capacity Restriction (TC): capacity restriction planned as necessary to maintain the infrastructure and allow development in accordance with market needs. ECMT is not master of TC objects since those are created and maintained in RNE’s TCR Tool.
Capacity Model data object (CM): volumes created by infrastructure managers to cover expected capacity consumption.
Capacity Need Announcement (CN): early information on applicants` planned traffic to infrastructure managers.

3.2. Object allocation

Objects are created on the level of Primary Location Codes (PLCs). IM users can allocate(create) all objects except Capacity Need Announcements which are exclusively reserved for Applicants and TCRs which cannot be created in ECMT (but in TCR Tool).

4. The search function

4.1. Search function

To refine the search, search filters are available. Search results will list all objects according to the search filters. Each object is accessible by clicking on its title and a new tab with the page object will open.

The “From location” and “To location” shall be informed by the user and the tool calculates shortest route between these two locations considering the waypoint (optional field). The tool generates the results list with the objects either fully or partially positioned on the route. As soon as there is one common location between two lines, the tool assumes the transfer of the train from one to another is possible.

4.2. Export function

Users with a read-only and editor role can export the search results in excel (feature located at the bottom of the results page).

4.3. Overlapping objects detection

The overlapping objects detection feature is relevant only fort Capacity Supply module and is accessible at the bottom of each object page and lists in a new window the objects overlapping with the base object. Objects are listed in the results as soon as they have one common location with the selected rail line or route.

This feature is supposed to be a "conflict detection" feature, but as the tool has limited information about the infrastructure, it has been named “overlapping detection”. To provide some indication about potential conflict risk, each overlapping object is listed with a priority level. For example, an overlapping with a total closure TCR has a high priority, while two paths overlapping each other at a station has low priority. Crossing a total closure TCR is very likely to be a critical conflict while overtaking between two stations can happen even as planned.

Overlapping objects detection results:

5. Object creation, editing and import

In the data menu’s drop-down list, the user selects the object type to be created / edited and a webpage with the import, add/edit an object, object bulk operation ( and search functions appears.

5.1 Object creation and editing

5.1.1. Search function and general guidelines

· Search function

The search function contains the same filters and has the same layout as the search function in the search menu. The user can search for some objects and edit or choose one of the other operation available in the operations column drop-down list.

The search can be filtered with the route filter. The “From location” and “To location” shall be informed by the user and the tool calculates shortest route between these two locations considering the waypoint (optional field). The tool generates the results list with the objects either fully or partially positioned on the route. As soon as there is one common location between two lines, the tool assumes the transfer of the train from one to another is possible.

· General guidelines

In order to create an object, the user should click on the add new object button (“add new catalogue” in the above screenshot example”) and a new webpage opens.

The general guidelines when creating and editing objects are listed below.

· Mandatory fields are marked with an * and must be informed to create the object

· Circulation days and calendar: selection of the applicable weekday(s) and/or selection of the exact dates in the calendar. Note that if weekday(s) are selected, the calendar remains editable if specific dates need to be added/removed to/from the selection.

· Timetable period: timetable period, for which the object is published.

· Line or route selection:

o If needed, the line / route section can be shortened with “From location” and “To location”.

o The locations sort order is important as it indicates the running sequence of the object (start location on top). The sort order can be reverse with the reverse order feature (double arrows with opposite directions).

o For route-based objects: the “From location” and “To location” shall be informed by the user and the tool calculates the shortest route between these two locations considering the waypoint(s) (optional field) and generates the timetable. As soon as there is one common location between two lines, the tool assumes the transfer of the train from one to another is possible.

· Timetable:

o Timetable refresh: when an object needs to be created on a shortened line or route, the timetable needs to be refreshed after entering the customised locations.

o Times at first and last location are mandatory.

o Offset: automatically set if the tool detects a midnight crossing, but the user can also apply manual offsets, in case of a long dwell time at a station.

Relevant object-specific additional information is listed below.

5.1.2. Add / edit paths and catalogue paths

Paths and catalogues paths are two distinct objects in the ECMT however, the editing of these objects is identical.

Train parameters: applicable for the entire line/route (if informed).

5.1.4. Add / edit Capacity Bands

· Slots:

o Number of slots available within the band (the number of paths included in the band).

o If required, different number of slots can be provided depending on the calendar. When editing the object after its creation, if the slot default number is updated, the tool will request confirmation on whether all dates need to be updated with the new default slot value or only those who were using the previous default value.

5.1.5. Object bulk operation

The bulk operation function is available when at least one object from the search results is select. After the objects to be edited are selected, a new webpage opens.

The concerned objects are listed. The operation and the update shall be selected by the user.

5.2. Object import function

The import function is accessible via the search menu.

5.2.1. General guidelines

· Supported format: xlsx

· Each object type shall be imported in a separated file.

· Export file and import file have the same structure. Exporting an objects list containing at least one object per object type provides the required structure for the import file.

· The columns’ order in the import file is irrelevant. Missed out columns only triggers warning and additional columns are ignored.

· Columns in the import file must have the same name as in the tool.

· The import file is not case sensitive.

· Time format: hh:mm

· Date format: dd.mm.yyy

· If applicable, an error message with the errors list appears after uploading the file.

5.2.2. Catalogues and Paths

Paths and catalogues paths are two distinct objects in the ECMT however, they have the same following import constraints:

· ID (mandatory): numbering common to rows belonging to the same object. Minimun two locations (so two rows) shall belong to an object.

· Title (mandatory): object title

· Colour (mandatory): 1 = red, 2 = green, 3 = black, 4 = blue, 5 = yellow, 6 = purple, 7 = brown

· Harmonization status (mandatory): rows belonging to the same object must have the same input.

· Traffic type (mandatory): rows belonging to the same object must have the same input.

· Line type: rows belonging to the same object must have the same input.

· TTP: number format, e.g. 2022. rows belonging to the same object must have the same input.

· Valid from (mandatory with “Valid to” if no input in “Calendar”): to be in line with the TTP, if given. Rows belonging to the same object must have the same input.

· Valid to (mandatory with “Valid from” if no input in “Calendar”): to be in line with the TTP, if given. Rows belonging to the same object must have the same input.

· Line (mandatory if line-based object): rows belonging to the same object must have the same input.

· OP (mandatory): location for the corresponding timetable shall in ECMT belong to the selected line.

· Arr: arrival time

· Arr offset: if applicable.

· Dep: departure time

· Dep offset: if applicable.

· For the following columns, number format and rows belonging to the same object must have the same input: Weight, Length, Speed, P1, P2, C1, C2

· For the following columns, 1 = the object circulates on that; 0 = the object does not circulate: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday.

· Calendar (mandatory if no input in “Valid from” and “Valid to”)

· Object type

· Company

· Core element

· Variant

5.2.4. Capacity bands

· ID (mandatory): numbering common to all rows belonging to the same object. Minimun two locations (so two rows) shall belong to an object.

· Title (mandatory): object title

· Colour (mandatory): 1 = red, 2 = green, 3 = black, 4 = blue, 5 = yellow, 6 = purple, 7 = brown

· Slots (mandatory): number format. Rows belonging to the same object must have the same input.

· Harmonization status (mandatory): rows belonging to the same object must have the same input.

· TTP: number format, e.g. 2022. Rows belonging to the same object must have the same input.

· Valid from (mandatory with “Valid to” if no input in “Calendar”): to be in line with the TTP, if given. Rows belonging to the same object must have the same input.

· Valid to (mandatory with “Valid from” if no input in “Calendar”): to be in line with the TTP, if given. Rows belonging to the same object must have the same input.

· Line (mandatory if line-based object): rows belonging to the same object must have the same input.

· OP (mandatory): location for the corresponding timetable shall in ECMT belong to the selected line.

· From time (mandatory at origin and destination)

· From time offset

· To time (mandatory at origin and destination)

· To time offset

· For the following columns, number format and rows belonging to the same object must have the same input: Weight, Length, Speed, P1, P2, C1, C2

· For the following columns, 1 = the object circulates on that; 0 = the object does not circulate, Rows belonging to the same object must have the same input: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday.

· Object type

· Company: company creating the object

· Core element

· Variant

5.2.5 Capacity Need Announcements

· ID ID that combines all operational points/locations on different rows into a single object. By this you can enter several CNAs into the same excel sheet. Use one numerical ID of your selection for all rows of the same object. Do not worry to use 1,2,3 or other small numbers - this ID will be changed by ECMT after the upload, to avoid conflict with other using also the same numbers.

· ObjectType Alphanumerical field (2 characters). The relevant types: CN = CNA and for IMs it is for instance CP = Catalogue Path, CM = Capacity Model.

· Company Alphanumerical field (4 characters) for the company code of the entity which created the object, the codes can be searched here: https://teleref.era.europa.eu/

· Core Alphanumerical field (12 characters) for the core element of the planned transport identifier.

· Variant Alphanumerical field (2 characters). For CNA only 00 shall be used.

· TimeTableYear The timetable period where the business will be carried out. Example: for timetable period from December 2024 to December 2025: enter 2025.

· RPTI_ObjectType Alphanumerical field (2 characters). The relevant type is only TR.

· RPTI_Company Alphanumerical field (4 characters) for the company code of the entity which created the object, the codes can be searched here: https://teleref.era.europa.eu/

· RPTI_Core Alphanumerical field (12 characters) for the core element of the planned transport identifier.

· RPTI_Variant Alphanumerical field (2 characters).

· RPTI_TimetableYear The timetable period where the business will be carried out. Example: for timetable period from December 2024 to December 2025: enter 2025.

· Reason of Reference Filed with predefined values, explaining reason why particular object is given as reference for given CAN

· OTN The "train number" or any national identifier that either the Applicant or the IM would like to assign to the CNA or CM object. It is only a desired number, no number allocation is part of the CNA process.

· Title An optional field to provide a user-friendly naming of the object, so you can recognise it easier. It does not need to be unique.

· LeadRU It shall be used only for the CNA to state who is the leading applicant for the CNA. Enter the company code of the applicant, it can be searched here: https://teleref.era.europa.eu/

· TrainType Enter the train type (Passenger, Freight). Please note that TAF code list has more values (see the sheet Code list)

· TrafficType Related to the train type. Only valid traffic types can be selected: Passenger (high speed/long distance/express regional/regional), Freight (wagonload/blocktrain/combined transport)

· CapacityProductType This field is related to the capacity partitioning. For CNA, you indicate what capacity product would be suitable for the CNA (see the sheet Code list).

· Category Write if the traffic is either national or international

· StatusQuo This field is specific for CNAs and first years of TTR in case the applicant wishes to notify IMs also about the status quo. If the CNA is for a new or modified traffic skip it. For StatusQuo cases, write down the year from which the status quo is to be considered (e.g.2022). The applicant is given the chance to provide an OTN (see field OTN) of already allocated paths and and in this way notify the IM that wishes to keep the status quo also for the timetable period for which the CNA is submitted.

· TrafficContracted "For passenger: write ""1"" in case the traffic is already contracted (e.g. PSO) or the traffic is planned as market (commercial) driven operation (e.g. open access). Write ""0"" if you are not fully sure that your company will be selected to execute the carriage (e.g. ongoing PSO tender).

· For freight: write ""1"" in case the traffic is already contracted or supply-driven. Write ""0"" if you are not fully sure that your company will be selected to execute the carriage. "

· TypeOfContract "In case you wrote ""1"" in the field TrafficContracted, provide information on the type of contract (e.g. PSO/commercial-driven-operation/supply-driven-operation/demand-driven operation).

· In case you wrote ""0"" in the field TrafficContracted, write down description for IMs for which customer and or what kind of transport will you apply for. This is to allow IMs identify double CNAs for the same transport."

· MaxJourneyTime It shall be used only for the CNA to indicate the limit of the journey time from origin to the destination (hh:mm), wished by the applicant. The idea is that exceeding the maximum time journey would make the transport not economically viable anymore.

· CountryCodeISO 2 character ISO code of the country of the location on the particular row. They can be found here: https://www.iso.org/obp/ui/#search

· LocationPrimaryCode Max. 5 digit field for the Primary location code (PLC) of the location on the particular row. You can find them here: https://teleref.era.europa.eu/, enter them without the country ISO code.

· PrimaryLocationName The location name (https://teleref.era.europa.eu/), note that only Location Primary Code is imported, so actually you can use any text for the location name here.

· TrainActivity This field is used to indicate the train activity at the particular location. The overview of activities is in the sheet Code list. The values shall be provided with their 4-digit codes and comma-separated if more activities are executed in the same location, for instance; 0001,0013 (=commercial stop, attach wagon).

· ELA Earliest arrival time (hh:mm)

· ELD Earliest departure time (hh:mm)

· ALA Actual arrival time (hh:mm)

· ALD Actual departure time (hh:mm)

· LLA Latest arrival time (hh:mm)

· LLD Latest departure time (hh:mm)

· DwellTime For the min. dwell time on the location in minutes (mm)

· MaxJourneyTimeSection It shall be used only for the CNAs to indicate the limit of the journey time from a location to the next location, wished by the applicant (hh:mm)

· ResponsibleApplicant Alphanumerical field (4 characters): company code of the applicant resposible for/from the location on this row. The codes can be searched here: https://teleref.era.europa.eu/

· TrainWeight The weight of the train excluding locos in tons

· TrainLength The length of the train excluding locos in metres

· TrainMaxSpeed The maximum possible speed of the train in km/h, provided by the Applicant

· Acceleration The acceleration information in m/s^2. Note that comma is used, not dot, to separate the decimal part (correct: 1,2 incorrect: 1.2)

· BrakeType Only valid brake types can be selected, see the sheet Code list.

· BrakingRatio The braking ratio for the selected brake type.

· NumberOfLocos A number that indicates the number of traction units to be used for the future train indicated in the CNA.

· PushPullTrain Write either 1 or 0. A boolean field that indicates if the train can change direction without shunting the loco around the train.

· RollingStockType Indicate the rolling stock type (see sheet Code list).

· ETCSOnBoard Write either 1 or 0. A boolean field that indicates whether the train is equipped with any kind of ETCS option.

· P1 Belongs to the combined transport profile. It shall be fulfilled only for combined transport trains.

· C1 Belongs to the combined transport profile. It shall be fulfilled only for combined transport trains.

· P2 Belongs to the combined transport profile. It shall be fulfilled only for combined transport trains.

· C2 Belongs to the combined transport profile. It shall be fulfilled only for combined transport trains.

· DangerousGoodsInidication Write either 1 or 0. It's a boolean field that indicates whether the train includes any kind of dangerous goods.

· ExceptionalTransport Write either 1 or 0. It's a boolean field that indicates whether the train is an exceptional transport.

· TiltingFunction Write either 1 or 0. It's a boolean field, only for passenger trains, that indicates whether train is capable of tilting.

· ValidFrom The start of the validity period of the object. YYYY-MM-DD

· ValidTo The end of the validity period of the object. YYYY-MM-DD

· Monday Part of the circulation days pattern, if the user does not want to provide daily bitmap for the calendar. Write either 1 or 0. For future train journeys longer than one calendar day, select the day of the train departure from the origin.

· Tuesday Part of the circulation days pattern, if the user does not want to provide daily bitmap for the calendar. Write either 1 or 0. For future train journeys longer than one calendar day, select the day of the train departure from the origin.

· Wednesday Part of the circulation days pattern, if the user does not want to provide daily bitmap for the calendar. Write either 1 or 0. For future train journeys longer than one calendar day, select the day of the train departure from the origin.

· Thursday Part of the circulation days pattern, if the user does not want to provide daily bitmap for the calendar. Write either 1 or 0. For future train journeys longer than one calendar day, select the day of the train departure from the origin.

· Friday Part of the circulation days pattern, if the user does not want to provide daily bitmap for the calendar. Write either 1 or 0. For future train journeys longer than one calendar day, select the day of the train departure from the origin.

· Saturday Part of the circulation days pattern, if the user does not want to provide daily bitmap for the calendar. Write either 1 or 0. For future train journeys longer than one calendar day, select the day of the train departure from the origin.

· Sunday Part of the circulation days pattern, if the user does not want to provide daily bitmap for the calendar. Write either 1 or 0. For future train journeys longer than one calendar day, select the day of the train departure from the origin.

· TimeUnit Only valid values can be selected (see sheet Code list). Then the applicant can provide a frequency for the selected time unit in the defined validity period.

· Frequency This field is connected with the TimeUnit filed for the defined TimeTableYear. If you select TimeUnit=weekly and write Frequency=1, it would mean 1 train run per week.

· BitmapDays The length shall be in line with the selected validity period and it indicates a daily calendar of the object. You can use the BitMapDays convertor sheet to create the BitMapDays, but note that the converter work only if you select the validity period for the whole annual timetable: 2024-12-15 to 2025-12-13

· Comment Free text field

5.2.6 Capacity Model objects