PCS TAF-TSI Communication Guide

Content

Versions

Version number

Date

Author

Highlights

0.1

02-07-2020

Máté Bak

Creation of the document

0.226-01-2021Máté BakSequence diagram
0.301-03-2021Máté BakUpdated sequence diagram, loco type structure in PCS, Object Info Message, handling the ErrorMessage for PRM from IMs
0.401-07-2021Máté BakProcess diagrams, FS process

Introduction

The aim of this document to provide a guide for Infrastructure Managers (IMs), Allocation Bodies (ABs) and Applicants (RAs) who would like to synchronize their timetables with PCS from the national systems.

There are specific use cases prepared and described for practical, real-life issues dedicated either to IMs/ABs or RAs.

Apart from the messages and their content, we tried to also describe the particularities of PCS and its TAF-TSI implementation, such as the way it handles the identifiers and how a company shall communicate with a central tool.

Working with the national particularities is also essential and PCS is fulfilled with a lot of national specific data. The guide will explain also how to work with these Network-Specific parameters and with the loco types.

The document will be permanently updated with further use cases. Currently, the focus is on the particularities and the traditional (tailor-made) path request procedures for a different kind of process type. However, in the future, the document will be extended with use cases for Path Alteration and Path Modification and it needs to be updated once working with Pre-arranged Paths will be possible via the PCS Shared Metadata.

Further helper materials, such as example messages for the different use cases can be found in this Filedepot folder.

Abbreviations

Abbreviation

Explanation

MS

Message Status. Assigned by the Sender 1 = creation, 2 = modification, 3 = deletion

TOI

Type of information. Enumeration, indicating to which process step or process type in the planning the message belongs

TOR

Type of request. Enumeration for the types of processes. Study (1), Request (2) - used in PCS as Ad-hoc process type, Modification (3), (4) Annual TT New Request, (5) Annual TT Late Path Request, (6) Rolling Planning, (7) Pre-accepted Offer Request

NSP

Network Specific Parameter, also known as NIMP (National IM Parameter)

NIMP

National IM Parameter, also known as NSP (Network Specific Parameter)

PR

Path Request object, prepared by the RA

PA

Path object, prepared by the IM/AB

RA

Responsible Applicant

IM

Infrastructure Manager

AB

Allocation Body

Messages

For communication with PCS, the usual Planning related messages shall be implemented. However, you will see that most of the time, you can rely on the Path Coordination Message and the rest will be solved by PCS itself. Of course, the messages generated and sent from PCS will be always in line with the specification of TAF-TSI.

  • Path Request Message, because PCS will deliver the path requests to the IMs/ABs with Path Request messages
  • Path Details Message, because PCS will deliver the offer to the RAs with Path Details messages
  • Path Coordination Message, because for updates in PCS, dossier promotions you shall send Path Coordination messages, and PCS will use this for most of the notifications
  • Error Message, because if there is any mistake regarding your update, PCS will send back Error messages with PCS specific error codes inside
  • Path Confirmed Message, because PCS will deliver the information about the acceptance of the Final Offer to IMs with this message
  • Path Details Refused Message because PCS will deliver the information about the acceptance of the Final Offer to IMs with this message
  • Path Not Available Message, because IMs need an option to delete an existing path in PCS. They can do it with this message
  • Object Info Message, because PCS will deliver the notifications for every timetable related updates with Object Info Message. The reason is that all the sub-paths of the dossier can be entered to one Object Info Message and there is no need to send Path Coordination Messages for each and every sub-path separately

Message Status

According to the TAF-TSI XSD each message has a message status and it can be one of the following values:

  • 1 – Creation
  • 2 – Modification
  • 3 – Delete

However, it’s important to note that PCS is a synchronous system, hence, it processes the received messages immediately and there is no chance for either modifying or deleting a formerly sent message. In case of a mistake, we expect another message fixing the issue also with an MS = 1 – creation.

So, the conclusion is that for PCS, only MS = 1 – creation values can be used.

RNE as sender and recipient

PCS behaves as a message broker in the communication of RA-RA, RA-IM, IM-IM. Normally, the sender and the recipient fields of the messages are fulfilled with the company code of either the RA or the IM. However, there is no place for RNE company code, meaning for PCS in this case. Thus, for the future, it's planned to extend the message header with an additional field, called Broker, like it's shown in the picture below.

As the solution is not even close to being implemented, we have applied a simplification for PCS communication. The actors can send their messages directly to PCS, and PCS will forward them, based on the advanced notification service of the system. So, for each message:

  • Sender: RA/IM Company Code
  • Recipient: RNE Company Code

Then, immediately with the update in the PCS dossier:

  • Sender: RNE Company Code
  • Recipient: RA/IM Company Code

As the RA - IM pairs are stored properly in the system, Path Request Messages, Path Details Messages will be delivered always to the proper partner. As the sender won't contain the company code of the applicant, the IM can get the Applicant information from the message content, as for PCS, each location of a path will belong to the same responsible applicant.

Please note also the economical and other types of benefits of this solution, because the mapping and configuration efforts are reduced to a single channel between PCS and the national system, without having a configuration for all possible communication streams (e.g. for each RA active in a country).

In line with the implementation and the above-written structure, the use cases below are described in this manner.

Identifiers

PCS is prepared to handle TAF-TSI identifiers and even more, they are mandatory in the dossiers. However, as most of the agencies are not ready yet to work with these identifiers, the system is able to generate them automatically. The logic is simple; when the user wants, it’s possible to include the ID, if not, the system takes care of it. Let’s see the logic in practice for the different identifiers.

Train ID

During the dossier creation and in the Open phase, the dossier creator agency is allowed to select the company whose company code will be part of the Train ID. Then it’s also possible to define the core element. The timetable period is coming automatically from the timetable period of the dossier (also known as Case Reference). The variant is set to 00 by default.

Currently, there are ongoing discussions and projects for the proper definition of the Train Information. In that regard, PCS works now only with PRs and PAs. The user has the chance to link those PRs to different Train variants. When the user creates the PRs in the dossier (called sub-paths in the Applicant timetable) and their origin/border/destination varies, then the user must link them to different Train ID variants. This logic is in line current description of the JS Handbook.

What happens if a user cannot provide the Train ID?

It might happen that either a company is not so advanced with its TSI implementation that it can generate its own Train ID, or the user is simply a GUI end-user and not even aware of the meaning of the Train ID. In that case, PCS will generate a Train ID. If the creator agency has a UIC ID, then it will be added as company code, if not, then PCS will add 3178 as RailNetEurope. For the core element, the dossier ID will be used, and the variants are automatically increased as a sequence if there is a change in the origin/border/destination. Example: TR - 3178 - ******215987 - 00 - 2020, where 215987 is the dossier ID.

Path Request ID & Path ID

There is a slight difference compared to the Train ID. Companies can still define their own PR ID/PA ID, but only if it’s a machine to machine communication, meaning via an interface. PCS has its fields in the schema, called tsi_path_id. This field keeps the PR ID in the Applicant timetable, and the PA ID in the IM timetable. Please find below a subset of the Trasse model of PCS, where you can see how the PR/PA IDs are stored on the sub-path level and that they are always linked to a Train ID.

<t----- id="...">

  <dossier_id>...</dossier_id>

  <train_id>

    <companyCode>...</companyCode>

    <objectType>...</objectType>

    <coreElement>...</coreElement>

    <variant>...</variant>

    <timetableYear>...</timetableYear>

    <startDate>...</startDate>

  </train_id>

  <traffic_period_text>...</traffic_period_text>

  <agency_type_id>...</agency_type_id>

  <title>...</title>

  <validity_period>...</validity_period>

  <tsi_path_id>

    <companyCode>...</companyCode>

    <objectType>...</objectType>

    <coreElement>...</coreElement>

    <variant>...</variant>

    <timetableYear>...</timetableYear>

    <startDate>...</startDate>

  </tsi_path_id>

Identifiers in PCS right after the Path Request

When the leading Applicant submits the path request, PCS creates immediately an IM timetable in the dossier and copies there the content of the Applicant timetable. Then, IMs can start working on the offers in Path Elaboration. However, these PCS paths in the IM timetable get also unique PCS IDs. And the tsi_path_id is still mandatory, however, there is no chance of any input from an IM to set this value. Those shall happen at the same time as the path request. Therefore, PCS generates again the tsi_path_id using RNE's company code. The problem starts here. PCS sends PathCoordination message to the involved IM with the path information from the IM timetable and there they get the generated, PCS made TSI PA ID.

There are two options to apply:

  • The IM doesn't care, and stores the received PCS based identifier, just like any other integrated IM does for the regular PCS interface. They continue working with this identifier
  • The IM doesn't like this ID. He has an option to delete the path and create a new one with his own national ID. PCS will store it in the tsi_path_id element

Network-Specific Parameters

PCS and TAF TSI have this option in common, that apart from the common train parameters each IM has the possibility to define his national IM parameters for covering the national particularities.

In PCS, the parameters can be defined on the dossier level for an RA – IM pair and on the path section level. This can be represented in the TAF-TSI messages as message level and planned journey location level parameters. Please find here an example of the PCS and the TAF-TSI structure.

National IM Parameter in PCS

<processtype_id>H</processtype_id>

<national_im_parameter id="78118">

         <name>D01 - Vertriebskanal</name>

         <value>PCS</value>

</national_im_parameter>

Network Specific Parameter in TAF-TSI

</ns1:PathInformation>

         <ns1:NetworkSpecificParameter>

                 <ns1:Name> D01 - Vertriebskanal </ns1:Name>

                 <ns1:Value> PCS </ns1:Value>

         </ns1:NetworkSpecificParameter>

</ns1:PathCoordinationMessage>

Both are working with a name/value pair. However, in addition to the TAF TSI options, in PCS the IMs can define the required format of the parameter and the application checks their entry format. That is why please always respect the defined format of the parameter, otherwise, PCS will send back an error message.

Please find here a summary of the possible formatting options in PCS:

  • String
    • Min numbers of characters >=1
    • Max number of characters <=256
  • Single choice list: values are defined in the system
  • Multiple choice list: values are defined in the system
  • Number
    • Min number of digits >=1
    • Max number of digits <=12
  • Date
    • dd.mm.yyyy
    • yyyy-mm-dd
  • Time
    • hh:mm:ss
    • hh:mm
  • Datetime
    • dd.mm.yyyy hh:mm:ss
    • dd.mm.yyyy hh:mm

Also, the IMs have the possibility in PCS to set-up parent-child relations among the parameters with an impact on their visibility or mandatory status.

Please note that dossier level parameters can be entered only after the dossier creation when the RA - IM pairs are already available in the system. It means, they cannot be entered in the first step (dossier creation). Agency can update the dossier level parameters with message-level NSPs using an edit sub-path type of Path Coordination. Then add the message-level parameters after the Path Information and the parameters will be updated. Also, please note that an agency can edit the NSPs only for its partner IM. Editing of the dossier level parameters is limited to the Harmonization phase and available only for Applicants. Even IMs can't edit those parameters later in Path Elaboration or Post-processing phase.

Loco types

Since version 2.2.3 loco types are handled with a composite identifier in TAF TSI. In PCS, it’s also possible for the IMs to publish that are allowed to run on their network (it was developed a couple of years before the TAF TSI XSD change). There have been slight differences between the two structures, but since 2020 November, PCS also supports the TAF fields.

  • Type Code 1: it’s always 9
  • Type Code 2: general vehicle type
    • 0 Miscellaneous
    • 1 Electric locomotive
    • 2 Diesel locomotive
    • 3 Electric multiple-unit set (high speed) [power car or trailer]
    • 4 Electric multiple-unit set (except high speed) [power car or trailer]
    • 5 Diesel multiple-unit set [power car or trailer]
    • 6 Specialised trailer,
    • 7 Electric shunting engine
    • 8 Diesel shunting engine
    • 9 Special vehicle
  • Country code: numerical country code
  • Series number: 4 digits representing the type according to the country rules and based on the national vehicle register of the country indicated with the CountryCode
  • Serial number: Three digits representing the serial number of the traction of the series. Optionally used in Planning to identify the subseries. This field is available in PCS from October 2021 and if it's not fulfilled by the IM, the system will apply a default "000" value.

Apart from the above-written values, PCS also stores the following information for each loco type that are published by the IMs/ABs:

  • Engine type: diesel, electric, hybrid, steam (required)
  • Top speed (required)
  • Length (required)
  • Weight (required)
  • Train control system
  • Related performance

In practice, the series number is not always kept in 4 digits because not every IM was able to publish their loco types with UIC numbering. If you are planning to use TAF TSI communication, please check first your loco types in PCS.

Object Info Message in the PCS shared metadata

The Object Info Message has a very good structure that makes it possible to pack almost the whole dossier content in one message. We found it extremely useful because with this we can spare a lot of redundant messages, and in addition, all involved agency will get the whole content of the dossier. It means that all the foreign path requests and paths are shared among the involved agencies.

To be fully able to map the whole dossier content to an Object Info Message, we had to add there additional, optional fields that will deliver relevant information from the dossier.

IDs and timetable data from PCS

The identifiers, the timetable data (sub-paths) and their relation to each other are packed in the following structure.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved Applicant
  • Identifier: CR ID
  • Path Information Extended as part of the Train Information Extended: an array of all the created sub-paths in the dossier in the following structure
    • Planned Transport Identifiers of the Train Information Extended: TR ID
    • Planned Transport Identifiers of the Path Information Extended as part of the Train Information Extended: PR ID or PA ID
    • Path Information = sub-path

Process related attributes

There are certain fields in PCS (and also in TAF-TSI messages) that deliver important information about the process type or the process step. On top of that, it's also important to store who are the leading or coordinating agencies in the dossier. That is why, we extended the Object Info Message with the following optional fields:

  • TypeOfRequest to deliver the process type of the dossier
  • TypeOfInformation to deliver the process step that has just happened
  • CoordinatingIM to deliver the leading IM of the dossier
  • LeadRU to deliver the leading Applicant of the dossier

Network-specific parameters

As was written above, PCS supports dossier level and path section level parameters. It's very important to communicate those values with the dossier content, thus, we pack them too in the Object Info Message.

  • Parameters level to deliver the dossier level IM parameters
  • NetworkSpecificParameters to deliver the path section level IM parameters

Earliest, latest and public times in PCS

PCS supports the definition of earliest, latest and public times in the dossier (ELA, ELD, ALA, ALD, PLA, PLD time qualifiers in TAF TSI) as it is shown on the following image.

The information is stored in the PCS database and it's presented also in the PCS schema. However, please note that only the time information is stored there, but there is no dedicated calendar for the earliest, latest and public times. In PCS all calendar and offset are saved and calculated from the actual arrival and actual departure time. That is why, if there is an earliest, latest or public time, PCS will put "0" in the generated message as the offset is a mandatory element regardless of the value of the time qualifier code. Thus, the offsets are fulfilled properly only for ALA and ALD values.

ErrorMessage

From PCS (in development)

There are pre-defined error codes in TAF-TSI, but PCS also has its own error codes (please refer to them inside the application or at this link). The mapping between the two data sets would be theoretically possible up to a certain limit, but with a lot of compromises, which would lower the quality of the error information. To bypass this problem, in the shared metadata communication, PCS delivers its error codes to the agencies in TAF format, using the PCS error code with a "5" prefix.

To PCS (in development)

It might happen that PCS accepts a request from the Applicants, but one of the IMs has a problem with that and normally they would react with an ErrorMessage. As the dossier is Path Elaboration phase, the proposed behaviour in such case would be the following. When an IM cannot accept a path request, it shall send an ErrorMessage to PCS. With that PCS will set the light (acceptance indicator) of the IM to red and place the error to the reason for the red light. It's then up to the Applicants how they would like to proceed. They can either place a brand new request or they can withdraw the existing dossier.

TypeOfInformation and PCS actions for path request processes

Before going into the detailed use cases, please find here a general overview that shows a mapping among the TOIs and their pair PCS actions. There are some actions, statuses or lights, where we didn't find an identical pair, that is why you can see that a fallback value was selected. For the future, RNE is planning to prepare a change request for the extension of the TOI list. Please note that this list doesn't contain yet the TOI mapping for path alteration, path modification and feasibility study processes.

CodeTypeOfInformationPCS actionProcess typeFallback
01Harmonisation - in processHarmonisation, yellowNPR, LPR, RP, Ad-hoc 
02Harmonisation - acceptedHarmonisation, greenNPR, LPR, RP, Ad-hoc 
03Harmonisation - rejectedHarmonisation, redNPR, LPR, RP, Ad-hoc 
04Harmonisation - completePath request submitted by LANPR, LPR, RP, Ad-hoc 
08Coordination UpdatePath Elaboration, yellowNPR, LPR, RP, Ad-hoc 
42Preparation of draft offer - acceptedPath Elaboration, greenNPR, LPR, RP, Ad-hoc 
43Preparation of draft offer - rejectedPath Elaboration, redNPR, LPR, RP, Ad-hoc 
09Draft offerDraft offer submitted by LIMNPR, LPR, RP 
11Observation - in processObservation, yellowNPR, RP 
02Harmonisation - acceptedObservation, greenNPR, RPYes
03Harmonisation - rejectedObservation, redNPR, RPYes
12Observation - completeReleased to Post-processingNPR, LPR, RP 
13Preparation of final offer - in processPost-processing, yellowNPR, LPR, RP 
14Preparation of final offer - acceptedPost-processing, greenNPR, LPR, RP 
15Preparation of final offer - rejectedPost-processing, redNPR, LPR, RP 
16Final offerFinal offer submitted by LIMNPR, LPR, RP, Ad-hoc 
02Harmonisation - acceptedFinal offer, greenNPR, LPR, RP, Ad-hocYes
03Harmonisation - rejectedFinal offer, redNPR, LPR, RP, Ad-hocYes
17Final offer - acceptedDossier goes to Active TimetableNPR, LPR, RP, Ad-hoc 
20Final offer - rejectedDossier goes to Closed NPR, LPR, RP 
25Offer/final offer rejected (without revision)Dossier goes to ClosedAd-hoc 
27Offer/final offer rejected (revision required)Dossier goes to Path ElaborationAd-hoc 
07Create offerDossier is released to Path ElaborationNPR, LPR, RP, Ad-hoc 
30Create dossierDossier is created in HarmonizationNPR, LPR, RP, Ad-hoc 
20BookedDossier entered to Active TimetableNPR, LPR, RP, Ad-hoc 
29WithdrawalLA withdraws the dossier from Path Elaboration to HarmonizationNPR, LPR, RP, Ad-hoc 
29WithdrawalLIM rejects the dossier in Path Elaboration and puts it back to HarmonizationNPR, LPR, RP, Ad-hoc 
32Path cancelled fullSub-path is deletedNPR, LPR, RP, Ad-hoc 

Diagrams of path request processes

New Path Request and Rolling Planning Path Request (single TTP)

New Path Request (NPR) and Rolling Planning Path Request (RP) process types are both applicable for the annual timetable period. The RP was added to PCS as the first outcome of the TTR project, so Applicants and IMs can test it on their pilot lines. The process is the same as for the NPR, but the deadlines are different.

Since November 2020, the Path Request phase became a milestone in PCS, and after the leading Applicant submits the path request, the dossier goes immediately to Path Elaboration. Similar behaviour is applied for the Draft Offer when the dossier goes immediately to the Observations phase.

Late Path Request

The Late Path Request (LPR) process type is applicable for the annual timetable period. The LPR differs from the NPR in the following:

  • The request and allocation deadlines are different
  • Instead of the Observations phase, LPR has the Acceptance phase in which the LA can accept the Late Path Request Offer and move the dossier immediately to Active Timetable.

Ad-hoc Path Request

Ad-Hoc Path Request (AHPR) process type is applicable for the running timetable period. In PCS, the AHPR is the process type corresponding to the TAF-TSI short-term path request.

Ad-hoc Path Request with pre-accepted offer

Ad-Hoc Path Request (AHPR*) process type is applicable for the running timetable period. In TAF-TSI, the Applicants have a chance to indicate in their path request that they would like to ask for a pre-accepted offer, using the element Type Of Information (TOI 19). PCS doesn’t allow the users to change process type after the dossier was created. That is why a dedicated process type was created to allow users to indicate from the beginning of the dossier creation that they would like to ask for a pre-accepted offer. This process type selection is enabled only when placing an ad-hoc (short-term) path request.

Use Cases of path request processes

Please find here all the use cases related either to IMs/ABs or to RAs. Please note that some of them are commonly applicable for each party, e.g. an acceptance indicator change works the same for any agency in a PCS dossier.

Create dossier (implemented)

Sent information

The dossier is created by the leading Applicant. To do that, it shall send a Path Coordination Message with TrainInformation element to PCS with the following information, so that the system can build up an international dossier with the respective Applicant-IM pairs.

  • Message header:
    • Sender: company code of the leading Applicant
    • Recipient: 3178 (RNE)
  • TOR: the proper code, depending on the selected process type
  • TOI: 30 – create dossier
  • Planned Transport Identifiers: TR ID.

Result

If everything went fine, the dossier is created in PCS. If not, an Error Message is sent back with the root cause. For the codes, please check the chapter with the Error Message.

Path Coordination message can contain Train Information and/or Path Information element. For dossier creation, PCS considers the information from the Train Information element. Based on that, PCS prepares the dossier with the following content:

  • Territories, based on the RA  - IM pairs in the Train Information.
  • Sub-paths, based on the Planned Journey Location information in the Train Information element. Be sure, that each pair has at least two locations in the Train Information. In PCS, the timetables are stored in so-called sub-paths (~PR or PA, depending on which timetable you are checking)
  • Dossier ID is generated, which will be used further as the CR ID
  • Train ID is stored
  • PR IDs are generated for each sub-paths based on the PCS path IDs in the system

Notifications (in development)

The involved agencies (other Applicants and including the creator agency) shall be informed that a dossier was created and now it’s in Harmonization. For that, PCS will send an Object Info Message.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved Applicant
  • Identifier: CR ID
  • Path Information Extended as part of the Train Information Extended: an array of all the created sub-paths in the dossier in the following structure
    • Planned Transport Identifiers of the Train Information Extended: TR ID
    • Planned Transport Identifiers of the Path Information Extended as part of the Train Information Extended: PR ID
    • Path Information

Change acceptance indicator to green (Implemented)

This is a common use case and shall be applied in the same way by RAs, IMs/ABs. The aim of the use case is to set the acceptance indicators of the agency to green in PCS, which is resolved with the harmonization status in the TAF-TSI.

Sent Information

Any involved agency who would like to set the acceptance indicator to green shall send Path Coordination Message without any Train Information or Path Information having there the following information.

  • Message header:
    • Sender: company code of the involved agency (either Applicant or IM/AB)
    • Recipient: 3178 (RNE)
  • TOR: the proper code, depending on the process type
  • TOI: according to the TOI mapping above. Applicants and IMs can use those TOIs to change their acceptance indicators to the proper colour in the different dossier statuses.
  • Planned Transport Identifiers: TR ID, CR ID

Result

If all the mandatory information is fulfilled in the dossier, the acceptance indicators belonging to the involved agency are changed to green. If not, then PCS will send an Error Message.

Notifications (in development)

In case of a successful update, the agency that set the light shall receive a Receipt Confirmation message as the following.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved RA or IM/AB depending on the phase
  • TOR: the proper code, depending on the process type
  • TOI: according to the TOI mapping above. Applicants and IMs can use those TOIs to change their acceptance indicators to the proper colour in the different dossier statuses.
  • Planned Transport Identifiers: TR ID, CR ID

Change acceptance indicator to red (in development)

This is a common use case and shall be applied in the same way by RAs, IMs/ABs. The aim of the use case is to set the acceptance indicators of the agency to red in PCS. It works almost the same as setting the green light, but in addition, the sender agency must place a mandatory comment in PCS declaring the reason of the red light.

Sent information

Any involved agency who would like to set the acceptance indicator to red, shall send Path Coordination Message without any Train Information or Path Information having there the following information.

  • Message header:
    • Sender: company code of the involved agency
    • Recipient: 3178 (RNE)
  • TOR: the proper code, depending on the process type
  • TOI: according to the TOI mapping above. Applicants and IMs can use those TOIs to change their acceptance indicators to the proper colour in the different dossier statuses.
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field on the message level: reason of the red light

It works the same as changing the light to green or yellow, the only difference is that the sender agency shall put a mandatory comment in the free text field of the message.

Result

The involved agency set its acceptance indicators to red and the reason is saved in the comment area of the dossier.

Notifications

In case of a successful update, the agency that set the light shall receive a Receipt Confirmation message as the following.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved RA or IM/AB depending on the phase
  • TOR: the proper code, depending on the process type
  • TOI: according to the TOI mapping above. Applicants and IMs can use those TOIs to change their acceptance indicators to the proper colour in the different dossier statuses.
  • Planned Transport Identifiers: TR ID, CR ID

An automatic downgrade of an acceptance indicator (in development)

This is a common use case and shall be applied in the same way by RAs, IMs/ABs. It might happen that you have already set your acceptance indicator to green, but your neighbour makes a change in the dossier having an impact on the border. PCS detects this action and it will automatically downgrade your light from green to yellow. It’s valid for RAs (Harmonization) and IMs/ABs (Path Elaboration, Post-processing) too. PCS checks the following elements on the borders (handover and/or interchange point):

  • Timetable
  • Dwell time
  • Calendar
  • Location

Sent information

There is nothing to send here because this is an action by PCS.

Result

The acceptance indicator of the affected agency is changed to yellow.

Notifications

The affected agency shall receive a Path Coordination Message as the following.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved RA or IM/AB depending on the phase
  • TOR: the proper code, depending on the process type
  • TOI: 01 – harmonization in process, 08 - coordination update or 13 - preparation of final offer in process (depending on the dossier status and the agency type)
  • Planned Transport Identifiers: TR ID, CR ID, PR ID and or PA ID of the agency that made the change resulted in the downgrade.

General timetable update (Implemented)

This is a common use case and shall be applied in the same way by RAs, IMs/ABs. The aim of the use case is to make any kind of update in the PCS dossier for the timetables. Either changes times, edit the calendar, add new points, delete points, edit train parameters. If a location is not mentioned in the path that was part before, PCS will interpret as a delete. For calendar changes, the agency shall send only a new calendar bitfield with the message. It can be also used for adding new sub-paths (PR/PA) to a dossier. If the ID of the sub-path is not known by PCS, it will interpret as a deletion.

Sent information

Any involved agency who would like to make an update on the timetable in a PCS dossier shall send a Path Coordination Message with Path Information element having there the following information.

  • Message header:
    • Sender: company code of the involved Applicant
    • Recipient: 3178 (RNE)
  • TOR: the proper code, depending on the process type
  • TOI: 01 - harmonization in process, 08 - coordination update or 13 - preparation of final offer in process (depending on the dossier status and the agency type)
  • Planned Transport Identifiers: TR ID, CR ID, PR ID or PA ID (depending on the agency type)
  • Path Information element

Result

If everything went fine, the dossier is updated in PCS. If not, an Error Message is sent back with the root cause.

Notifications (in development)

In case of a successful update, all affected agencies (including the original sender) shall receive an Object Info Message with the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved Applicant
  • Identifier: CR ID
  • TOI: 01 - harmonization in process, 08 - coordination update or 13 - preparation of final offer in process (depending on the dossier status and the agency type)
  • Path Information Extended as part of the Train Information Extended: an array of all the created sub-paths in the dossier in the following structure
    • Planned Transport Identifiers of the Train Information Extended: TR ID
    • Planned Transport Identifiers of the Path Information Extended as part of the Train Information Extended: PR ID or PA ID
    • Path Information

Send path request as leading Applicant (Implemented)

The aim of this use case to promote the dossier from Harmonization to Path Request as a leading Applicant. As PCS stores everything in one dossier, it’s not necessary to send Path Request messages for each and every sub-paths, but the leading Applicant can simply promote the whole dossier, also on behalf of the other involved Applicants. This can happen by an automatic promotion of PCS on a timetable deadline too. In that case, everything works the same way, but there is no need for the sent information by the leading Applicant.

Sent information

The leading Applicant who would like to promote the dossier to Path Request shall send a Path Coordination Message without Train Information and Path Information to PCS having there the following information.

  • Message header:
    • Sender: company code of the leading Applicant
    • Recipient: 3178 (RNE)
  • TOR: the proper code, depending on the process type
  • TOI: 04 – harmonization completed
  • Planned Transport Identifiers: TR ID, CR ID

Result

If all the mandatory information is fulfilled in the dossier and all the acceptance indicators of the Applicants are set to green, the dossier will be promoted. If not, then PCS will send an Error Message.

Notifications

All involved Applicant shall be informed about the phase promotion; thus, PCS will send one Path Coordination Message to them with the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved Applicant
  • TOR: the proper code, depending on the process type
  • TOI: 04 – harmonization completed
  • Planned Transport Identifiers: TR ID, CR ID

Information about the dossier in Path Request phase

On the other side, all IMs/ABs shall be informed about the path requests; thus, PCS will send Path Request Messages for their territory.

The content of the Path Request Messages

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved IM/AB
  • TOR: the proper code, depending on the process type
  • TOI: 04 – harmonization completed
  • Planned Transport Identifiers: TR ID, CR ID, PR ID
  • Related Planned Transport Identifiers: all other PR IDs that are belonging to the dossier
  • Train Information
  • Path Information

Information about the dossier in the Path Elaboration phase

Please note the Path Request is only a milestone in PCS, that is why, the dossiers are automatically promoted to the next phase, called Path Elaboration. As this step is recorded in the dossier with a separated dossier version and all new dossier versions shall trigger a notification, the IMs/ABs will receive another notification immediately after the Path Request promotion. All IMs/ABs will receive a Path Coordination Message without Train Information and Path Information. As it’s only a “simple” phase promotion, there is no Object Info Message in this case.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved IM/AB
  • TOR: the proper code, depending on the process type
  • TOI: 07 – create offer
  • Planned Transport Identifiers: TR ID, CR ID

Delete a sub-path from a dossier

This is a common use case from the business point of view for the applicants and IMs/ABs.

Sent information

Any involved agency, who would like to delete a sub-path from a dossier, shall send a Path Coordination Message with the following content.

  • Message header:
    • Sender: company code of the involved Applicant
    • Recipient: 3178 (RNE)
  • TOR: the proper code, depending on the process type
  • TOI: 32 – path cancelled full
  • Planned Transport Identifiers: TR ID, CR ID, PR ID or PA ID (depending on the agency type)

Result

The sub-path either with the PR ID from the Applicant timetable or with the PA ID from the IM timetable is successfully deleted.

Notifications

As this update affects the whole dossier content, all affected agencies will receive one Object Info Message from PCS with the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved Applicant
  • Identifier: CR ID
  • Path Information Extended as part of the Train Information Extended: an array of all the created sub-paths in the dossier in the following structure
    • Planned Transport Identifiers of the Train Information Extended: TR ID
    • Planned Transport Identifiers of the Path Information Extended as part of the Train Information Extended: PR ID or PA ID
    • Path Information

Send Offer (draft or final) as leading IM/AB  (Implemented)

The aim of this use case is to show, how the leading IM/AB can send an offer. The same approach can be used for Draft Offer or Final Offer. This can happen by an automatic promotion of PCS on a timetable deadline too. In that case, everything works the same way, but there is no need for the sent information by the leading IM.

Sent information

The leading IM who would like to submit an offer for a PCS dossier shall send a Path Coordination Message without Train Information and Path Information having there the following information.

  • Message header:
    • Sender: company code of the leading IM/AB
    • Recipient: 3178 (RNE)
  • TOR: the proper code, depending on the process type
  • TOI: 09 - draft offer (for promotions from Path Elaboration during New Path Request, Late Path Request and Rolling Planning process types), 16 - final offer (for promotions from Post-processing during New Path Request, Late Path Request and Rolling Planning process types, from Path Elaboration during Ad-hoc Path Request process type)
  • Planned Transport Identifiers: TR ID, CR ID

Result

If all the mandatory information is fulfilled in the dossier and all the acceptance indicators of the IMs/ABs are set to green, the dossier will be promoted. If not, then PCS will send an Error Message.

Notifications

All involved IMs/ABs shall be informed about the phase promotion; thus, PCS will send one Path Coordination Message to them with the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved IM/AB
  • TOR: the proper code, depending on the process type
  • TOI: 09 – draft offer, 16 – final offer
  • Planned Transport Identifiers: TR ID, CR ID

On the other side, all Applicants shall be informed about the offers; thus, PCS will send Path Details Messages.

The content of the Path Details Messages

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved Applicant
  • TOR: the proper code, depending on the process type
  • TOI: 09 – draft offer, 16 – final offer
  • Planned Transport Identifiers: TR ID, CR ID, PA ID
  • Related Planned Transport Identifiers: all other PR IDs & PA IDs that are belonging to the dossier
  • Path Information

Reject dossier as leading IM (in development)

The aim of this use case to show, how a leading IM can reject a dossier. It’s possible for them only in the Path Elaboration phase.

Sent information

The leading IM who would like to reject a dossier in PCS shall send a Path Coordination Message without Train Information and Path Information having there the following information.

  • Message header:
    • Sender: company code of the leading IM/AB
    • Recipient: 3178 (RNE)
  • TOR: the proper code, depending on the process type
  • TOI: 29 - withdrawal
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field on the message level: the reason for the rejection

Result

The dossier is rejected by the leading IM and it goes back to Harmonization status. Also, the reason for the rejection is saved to the comment area of the dossier.

Notifications

All agencies shall be informed about the rejection; thus, PCS will send a Path Coordination Message without Train Information and Path Information having there the following information.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved agencies
  • TOR: the proper code, depending on the process type
  • TOI: 29 - withdrawal
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field on the message level: the reason for the rejection

Accept the offer as leading Applicant (Implemented)

The aim of this use case to show, how a leading Applicant can accept the dossier and promote it to Active Timetable. Here we have differences among the process types, because for New Path Request and Rolling Planning this acceptance happens in the Final Offer phase, after a Post-processing phase, but for Late Path Request and Ad-hoc Path Request, it happens immediately after the offer following the Path Elaboration.

Sent information

The leading Applicant who would like to accept the dossier and move it to Active Timetable shall send a Path Coordination Message without Train Information and Path Information having there the following content. This is valid for all process types.

  • Message header:
    • Sender: company code of the leading Applicant
    • Recipient: 3178 (RNE)
  • TOR: the proper code, depending on the process type
  • TOI: 17 – final offer accepted
  • Planned Transport Identifiers: TR ID, CR ID

Result

If all the mandatory information is fulfilled in the dossier and all the acceptance indicators of the applicants are set to green, the dossier will be promoted, and it arrives at the Active Timetable phase.

Notifications

Leading Applicants shall be informed about the promotion; thus, PCS will send a Receipt Confirmation Message having there the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved Applicant
  • TOR: the proper code, depending on the process type
  • TOI: 17 – final offer accepted
  • Planned Transport Identifiers: TR ID, CR ID

All IMs/ABs shall be informed about the acceptance; thus, PCS will send Path Confirmed Messages to them with the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved IM/AB
  • TOI: 17 – final offer accepted
  • Planned Transport Identifiers: TR ID, CR ID, PA ID
  • Related Planned Transport Identifiers: all other PR IDs & PA IDs that are belonging to the dossier

Reaching Active Timetable with the dossier

As the dossier arrived at Active Timetable, it reached its final destination in the path request process. To keep everyone up to date, PCS will send Path Details Messages with the booked paths to all involved agencies.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved Applicant
  • TOR: the proper code, depending on the process type
  • TOI: 22 - booked
  • Planned Transport Identifiers: TR ID, CR ID, PA ID
  • Related Planned Transport Identifiers: all other PR IDs & PA IDs that are belonging to the dossier
  • Path Information

The same shall happen for Pre-accepted offer dossier, when the leading IM sends the Offer, because then, it goes automatically to Active Timetable.

Refuse the Final Offer as leading Applicant (in development)

The aim of this use case is to show, how a leading Applicant can refuse the final offer. There are two options available to them. For the Ad-hoc path request, this decision can be made right after the Path Elaboration phase, for the others, it can happen after the Post-processing phase.

  1. Refuse it without revision
  2. Refuse it, asking for revision (it’s available only for Ad-hoc path request)

Sent information

The leading Applicant who would like to refuse the offer shall send a Path Coordination Message to PCS without Train Information and Path Information having there the following content.

  • Message header:
    • Sender: company code of the leading Applicant
    • Recipient: 3178 (RNE)
  • TOR: the proper code, depending on the process type
  • TOI: 25 – offer/final offer rejected (without revision) or 27 – offer/final offer rejected (revision required)
  • Planned Transport Identifiers: TR ID, CR ID

Result

The result depends on the selected refusal option. If it’s done without revision, the dossier will go to the Closed phase, but if it’s with revision (available only for Ad-hoc), it will go back to Path Elaboration.

Notifications

All involved Applicants shall be informed about the rejection; thus, PCS will send a Path Coordination Message without Train Information and Path Information having there the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved Applicant
  • TOR: the proper code, depending on the process type
  • TOI: 25 – offer/final offer rejected (without revision) or 27 – offer/final offer rejected (revision required)
  • Planned Transport Identifiers: TR ID, CR ID

All involved IMs/ABs shall be informed about the rejection too; thus, PCS will send Path Details Refused Messages.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved IM/AB
  • TOI: 25 – offer/final offer rejected (without revision) or 27 – offer/final offer rejected (revision required)
  • Planned Transport Identifiers: TR ID, CR ID, PA ID
  • Related Planned Transport Identifiers: all other PR IDs & PA IDs that are belonging to the dossier

Make Observation (in development)

The aim of this use case to show, how an Applicant can place an Observation in a dossier.

Sent information

The involved Applicant who would like to place an Observation shall send a Path Coordination Message without Train Information and Path Information having there the following content. Please note that this use case is valid only for New Path Request and Rolling Planning process types because the Consultation phase is not part of the other process types.

  • Message header:
    • Sender: company code of any involved Applicant
    • Recipient: 3178 (RNE)
  • TOR: the proper code, depending on the process type
  • TOI: 11 – observation in process
  • Planned Transport Identifiers: TR ID, CR ID, PA ID
  • Free text field: the text of the Observation

Result

The Observation is saved in PCS in the comment area.

Notifications

The applicant that made the observation shall be informed that it was made successfully; thus, PCS will send a Receipt Confirmation Message like the following.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved Applicant
  • TOR: the proper code, depending on the process type
  • TOI: 11 – observation in process
  • Planned Transport Identifiers: TR ID, CR ID

The IM/AB shall be informed that an Observation was made to one of the sub-paths; thus, PCS will send a Path Coordination Message without Train Information and Path Information having there the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved agency
  • TOR: the proper code, depending on the process type
  • TOI: 11 – observation in process
  • Planned Transport Identifiers: TR ID, CR ID, PA ID
  • Free text field: the text of the Observation

Release Post-processing as leading Applicant (Implemented)

The aim of this use case is to show, how the leading Applicant can promote the dossier to Post-processing. This can happen by an automatic promotion of PCS on a timetable deadline too. In that case, everything works the same way, but there is no need for the sent information by the leading Applicant.

Sent information

The leading Applicant who would like to promote the dossier to Post-processing shall send a Path Coordination Message without Train Information and Path Information having there the following content.

  • Message header:
    • Sender: company code of any leading Applicant
    • Recipient: 3178 (RNE)
  • TOR: the proper code, depending on the process type
  • TOI: 12 – observation complete
  • Planned Transport Identifiers: TR ID, CR ID

Result

The dossier is promoted to Post-processing.

Notifications

All involved agencies shall be informed about the dossier promotion; thus, PCS will send a Path Coordination Message without Train Information and Path Information having there the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved agency
  • TOR: the proper code, depending on the process type
  • TOI: 12 – observation complete
  • Planned Transport Identifiers: TR ID, CR ID

Withdraw dossier as leading Applicant (in development)

The aim of this use case to show, how a leading Applicant can withdraw a dossier. It’s possible for them only in Path Request and Path Elaboration phases.

Sent information

The leading Applicant who would like to withdraw a dossier in PCS shall send a Path Coordination Message without Train Information and Path Information having there the following information.

  • Message header:
    • Sender: company code of the leading Applicant
    • Recipient: 3178 (RNE)
  • TOR: the proper code, depending on the process type
  • TOI: 29 - withdrawal
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field on the message level: the reason for the withdrawal

Result

The dossier is withdrawn by the leading Applicant and it goes back to Harmonization status. Also, the reason for the withdrawal is saved to the comment area of the dossier.

Notifications

All agencies shall be informed about the withdrawal; thus, PCS will send a Path Coordination Message without Train Information and Path Information having there the following information.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved agencies
  • TOR: the proper code, depending on the process type
  • TOI: 29 - withdrawal
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field on the message level: reason for the rejection

getDossier (in development)

Any involved agency of the dossier has a chance to download the dosser from PCS at any time. To do so, they only need to send an Object Info Message and PCS will send back the dossier also packed to an Object Info Message.

Sent information

The involved agency who would like to download a dossier in PCS shall send an Object Info Message having there the following information.

  • Message header:
    • Sender: company code of the involved agency
    • Recipient: 3178 (RNE)
  • ObjectInfoType: I - Information
  • Identifier: CR ID

Result

As it is not an update in PCS, there is no result in the system, apart from the registered web-service request.

Notifications

PCS will send an Object Info Message to the requester agency with the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved Applicant
  • Identifier: CR ID
  • Path Information Extended as part of the Train Information Extended: an array of all the created sub-paths in the dossier in the following structure
    • Planned Transport Identifiers of the Train Information Extended: TR ID
    • Planned Transport Identifiers of the Path Information Extended as part of the Train Information Extended: PR ID or PA ID
    • Path Information

Feasibility Study process

The Feasibility Study (FS) process type is available to Applicants and applicable for all path request process types. They can initiate this process from the Harmonization phase. It’s mostly used for passenger trains in NPR, but available for freight trains, too. Applicants and IMs share access to the dossier on their timetables (RAs in the Applicant timetable, IMs in the IM timetable) in Harmonization Conference and Feasibility Elaboration Conference phases.

TOI overview

CodeTypeOfInformationFallbackPhaseActorTarget phaseAction
30create dossier HarmonizationLAHarmonization ConferenceStart Feasibility Study
31close dossier Harmonization ConferenceLA/LIMHarmonizationBack to Harmonization
05path study request Harmonization ConferenceLAFeasibility Study RequestSubmit FS request
07create offer Feasibility Study RequestLIM/PCSFeasibility Study ElaborationRelease FS Elaboration
02harmonization - accepted Harmonization ConferenceIM Set green light as IM
03harmonization - rejected Harmonization ConferenceIM Set red light as IM
01harmonization - in process Harmonization ConferenceIM Set yellow light as IM
02harmonization - accepted Harmonization ConferenceRA Set green light as RA
03harmonization - rejected Harmonization ConferenceRA Set red light as RA
01harmonization - in progress Harmonization ConferenceRA Set yellow light as RA
29withdrawal Feasibility Study ElaborationLAHarmonizationWithdraw FS
42preparation of draft offer - accepted Feasibility Study ElaborationIM Set green light as IM
43preparation of draft offer - rejected Feasibility Study ElaborationIM Set red light as IM
08coordination updateYesFeasibility Study ElaborationIM Set yellow light as IM
09draft offer Feasibility Study ElaborationLIMFeasibility Elaboration ConferenceRelease FS Conference
07create offer Feasibility Elaboration ConferenceLIMFeasibility Elaboration ConferenceReturn to FS Elaboration
02harmonization - acceptedYesFeasibility Elaboration ConferenceRA Set green light as RA
03harmonization - rejectedYesFeasibility Elaboration ConferenceRA Set red light as RA
11observation in process Feasibility Elaboration ConferenceRA Set yellow light as RA
14preparation of final offer - accepted Feasibility Elaboration ConferenceIM Set green light as IM
15preparation of final offer - rejected Feasibility Elaboration ConferenceIM Set red light as IM
13preparation of final offer - in process Feasibility Elaboration ConferenceIM Set yellow light as IM
16final offer Feasibility Study ElaborationLIMFeasibility Study ResultSubmit FS result
07create offer Feasibility Study ResultLIMFeasibility Study ElaborationWithdraw FS result
17final offer accepted Feasibility Study ResultLAHarmonizationAcknowledge FS Result
02harmonization - acceptedYesFeasibility Study ResultRA Set green light as RA
03harmonization - rejectedYesFeasibility Study ResultRA Set red light as RA

Use cases of the FS process

Start FS

The leading applicant of the dossier has the chance to start the feasibility process. As it's a dossier transition, it shall be done with a Path Coordination Message without any Train and Path Information. Please note that with this action the dossier enters to Harmonization Conference, but the path study request is not sent yet. That is why we utilized the create dossier type of information for this action, as the leading applicant created a new feasibility study.

Sent information

The leading applicant who would like to submit feasibility study request shall send a Path Coordination Message without Train and Path Information having there the following information.

  • Message header:
    • Sender: company code of the leading applicant
    • Recipient: 3178 (RNE)
  • TOR: 1 - study
  • TOI: 30 - create dossier
  • Identifier: CR ID, TR ID
Result

In case of a successful request, the dossier enters to Harmonization Conference phase.

Notifications

PCS will send a Receipt Confirmation message to the leading applicant and a Path Coordination Message to all involved applicants with the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved Applicant
  • TOR: 1 - study
  • TOI: 30 - create dossier
  • Identifier: CR ID, TR ID

Back to Harmonization

The leading applicant of the dossier has the chance to withdraw the dossier from the feasibility process. As it's a dossier transition, it shall be done with a Path Coordination Message without any Train and Path Information. With this action, the leading applicant closes the feasibility study before it's requested.

Sent information

The leading applicant who would like to withdraw the dossier from the feasibility study shall send a Path Coordination Message without Train and Path Information having there the following information.

  • Message header:
    • Sender: company code of the leading applicant
    • Recipient: 3178 (RNE)
  • TOR: 1 - study
  • TOI: 31 - close dossier
  • Identifier: CR ID, TR ID
Result

In case of a successful request, the dossier enters to Harmonization phase.

Notifications

PCS will send a Receipt Confirmation message to the leading applicant and a Path Coordination Message to all involved applicants with the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved Applicant
  • TOR: 1 - study
  • TOI: 31 - close dossier
  • Identifier: CR ID, TR ID

Submit FS Request

After Harmonization Conference, the leading applicant has the chance to submit the feasibility study request.

Sent information

The leading applicant who would like to submit the feasibility study request shall send a Path Coordination Message without Train and Path Information having there the following information.

  • Message header:
    • Sender: company code of the leading applicant
    • Recipient: 3178 (RNE)
  • TOR: 1 - study
  • TOI: 05 - path study request
  • Identifier: CR ID, TR ID
Result

In case of a successful request, the dossier enters to Feasibility Study Elaboration phase. Please note that in the case of LPR, the dossier remains in the Feasibility Study Request phase and the leading IM has to release the elaboration.

Notifications

PCS will send a Receipt Confirmation message to the leading applicant and a Path Coordination Message to all involved applicants with the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved Applicant
  • TOR: 1 - study
  • TOI: 05 - path study request
  • Identifier: CR ID, TR ID

The involved IMs will get Path Request Message(s) with the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved IM
  • TOR: 1 - study
  • TOI: 05 - path study request
  • Identifier:
    • Planned Transport Identifiers: CR ID, TR ID, PR ID
    • Related Planned Transport Identifier: PA ID (corresponding to the PR ID of the sub-path in the applicant timetable)

Withdraw FS request

Sent information

The leading applicant who would like to withdraw the feasibility study request shall send a Path Coordination Message without Train and Path Information having there the following information.

  • Message header:
    • Sender: company code of the leading Applicant
    • Recipient: 3178 (RNE)
  • TOR: 1 - study
  • TOI: 29 - withdrawal
  • Identifier: CR ID, TR ID
Result

In case of a successful request, the dossier returns to the Harmonization phase.

Notifications

PCS will send a Receipt Confirmation message to the leading applicant and a Path Coordination Message to all involved agencies with the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved agency
  • TOR: 1 - study
  • TOI: 29 - withdrawal
  • Identifier: CR ID, TR ID

Release FS Elaboration

As it was written previously, except for LPR, PCS releases automatically the dossier to FS Elaboration. Otherwise, it shall be done by the leading IM.

Sent information

The leading IM who would like to release the dossier to FS Elaboration shall send a Path Coordination Message without Train and Path Information having there the following information. For non-LPR dossiers, PCS will do this and the IMs will be informed as it's written in the notification part.

  • Message header:
    • Sender: company code of the leading IM
    • Recipient: 3178 (RNE)
  • TOR: 1 - study
  • TOI: 07- create offer
  • Identifier: CR ID, TR ID
Result

In case of a successful request, the dossier enters to Feasibility Study Elaboration phase.

Notifications

PCS will send a Receipt Confirmation message to the leading IM (in case of LPR) and a Path Coordination Message to all involved IMs with the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved IM
  • TOR: 1 - study
  • TOI: 07- create offer
  • Identifier: CR ID, TR ID

Release FS Elaboration Conference

During the FS process, the IMs can share their interim result with the applicants in the Feasibility Elaboration Conference phase.

Sent information

The leading IM who would like to release the dossier to Feasibility Elaboration Conference shall send a Path Coordination Message without Train and Path Information having there the following information. For non-LPR dossiers, PCS will do this and the IMs will be informed as it's written in the notification part.

  • Message header:
    • Sender: company code of the leading IM
    • Recipient: 3178 (RNE)
  • TOR: 1 - study
  • TOI: 09 - draft offer
  • Identifier: CR ID, TR ID
Result

In case of a successful request, the dossier enters to Feasibility Elaboration Conference phase.

Notifications

PCS will send a Receipt Confirmation message to the leading IM (in case of LPR) and a Path Coordination Message to all involved IMs with the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved IM
  • TOR: 1 - study
  • TOI: 09 - draft offer
  • Identifier: CR ID, TR ID

And Path Details Message to all involved applicants with the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved applicant
  • TOR: 1 - study
  • TOI: 09 - draft offer
  • Identifier:
    • Planned Transport Identifiers: CR ID, TR ID, PR ID, PA ID

Return to FS Elaboration

After the Feasibility Elaboration Conference, the dossier returns to FS Elaboration again.

Sent information

The leading IM who would like to bring the dossier to FS Elaboration shall send a Path Coordination Message without Train and Path Information having there the following information. 

  • Message header:
    • Sender: company code of the leading IM
    • Recipient: 3178 (RNE)
  • TOR: 1 - study
  • TOI: 07- create offer
  • Identifier: CR ID, TR ID
Result

In case of a successful request, the dossier enters to Feasibility Study Elaboration phase.

Notifications

PCS will send a Receipt Confirmation message to the leading IM and a Path Coordination Message to all involved IMs with the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved IM
  • TOR: 1 - study
  • TOI: 07- create offer
  • Identifier: CR ID, TR ID

Submit FS Result

Sent information

The leading IM who would like to submit Feasibility Results hall send a Path Coordination Message without Train and Path Information having there the following information. 

  • Message header:
    • Sender: company code of the leading IM
    • Recipient: 3178 (RNE)
  • TOR: 1 - study
  • TOI: 16 - final offer
  • Identifier: CR ID, TR ID
Result

In case of a successful request, the dossier enters to Feasibility Elaboration Conference phase.

Notifications

PCS will send a Receipt Confirmation message to the leading IM  and a Path Coordination Message to all involved IMs with the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved IM
  • TOR: 1 - study
  • TOI: 16 - final offer
  • Identifier: CR ID, TR ID

And Path Details Message to all involved applicants with the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved applicant
  • TOR: 1 - study
  • TOI: 16 - final offer
  • Identifier:
    • Planned Transport Identifiers: CR ID, TR ID, PR ID, PA ID

Withdraw FS Result

The leading has the chance the withdraw the FS Result and return again to FS Elaboration phase. As for all actions when the dossier enters FS Elaboration phase, the same, 07 - create offer TOI is used.

Sent information

The leading IM who would like to bring the dossier back to FS Elaboration shall send a Path Coordination Message without Train and Path Information having there the following information. 

  • Message header:
    • Sender: company code of the leading IM
    • Recipient: 3178 (RNE)
  • TOR: 1 - study
  • TOI: 07- create offer
  • Identifier: CR ID, TR ID
Result

In case of a successful request, the dossier enters to Feasibility Study Elaboration phase.

Notifications

PCS will send a Receipt Confirmation message to the leading IM  and a Path Coordination Message to all involved IMs with the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved IM
  • TOR: 1 - study
  • TOI: 07- create offer
  • Identifier: CR ID, TR ID

Acknowledge FS Result

The leading applicant can acknowledge the FS Result, so that the dossier can return to Harmonization phase.

Sent information

The leading applicant who would like to acknowledge the FS Result shall send a Path Coordination Message without Train and Path Information having there the following information. 

  • Message header:
    • Sender: company code of the leading applicant
    • Recipient: 3178 (RNE)
  • TOR: 1 - study
  • TOI: 17 - final offer accepted
  • Identifier: CR ID, TR ID
Result

In case of a successful request, the dossier enters to Harmonization phase.

Notifications

PCS will send a Receipt Confirmation message to the leading applicant and a Path Coordination Message to all involved applicants with the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved applicants
  • TOR: 1 - study
  • TOI: 17 - final offer accepted
  • Identifier: CR ID, TR ID

And the involved IMs will get the Path Confirmed Message with the following content.

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved IMs
  • TOR: 1 - study
  • TOI: 17 - final offer accepted
  • Identifier: CR ID, TR ID

Set acceptance indicator

Involved IMs and involved applicants shall set their acceptance indicators in the different phases. The procedure is the same, only the TOIs might be different.

Sent information

The involved agency who would like to set acceptance indicator shall send a Path Coordination Message without Train and Path Information having there the following information. 

  • Message header:
    • Sender: company code of the involved agency
    • Recipient: 3178 (RNE)
  • TOR: 1 - study
  • TOI: X
  • Identifier: CR ID, TR ID

The proper TOIs are shown in the TOI overview.

Notification

PCS will send a Receipt Confirmation message to the original sender.

 

Path Modification process

The Path Modification (PM) process type is available for dossiers in Active Timetable phase, for all path request process types and can be initiated by any RA.

TOI OVERVIEW

TOR

TOI

FALLBACK

PHASE

TYPE

ACTOR

TARGET PHASE

ACTION

3

30 - Create dossier

 

Active Timetable

Promotion

LA

PM Conference

Start Path Modification

3

31 - Close dossier

 

PM Conference

Promotion

LA

Active Timetable

Withdraw Path Modification

3

4 - Harmonisation complete

 

PM Conference

Promotion

LA

PM Elaboration

Submit Path Modification Request

3

2 - Harmonisation - accepted

 

PM Conference

Light

RA

Set green light in PM Conference

 

3

3 - Harmonisation - rejected

 

PM Conference

Light

RA

Set red light in PM Conference

 

3

1 - Harmonisation - in progress

 

PM Conference

Light

RA

Set yellow light in PM Conference

 

3

7 - Create offer

 

PM Request

Promotion

PCS

PM Elaboration

Release PM Elaboration

3

29 - Withdrawal

 

PM Elaboration

Promotion

LA

Active Timetable

Withdraw Path Modification Request (return to Active Timetable, keeping original IDs)

3

21 - No alternative available

 

PM Elaboration

Promotion

LIM

Active Timetable

Reject Path Modification Request (return to Active Timetable, keeping original IDs)

3

16 - Final offer

 

PM Elaboration

Promotion

LIM

PM Offer

Submit Path Modification Offer

3

14 - Preparation of final offer - accepted

2

PM Elaboration

Light

IM

 

Set green light in PM Elaboration as IM

3

15 - Preparation of final offer - rejected

3

PM Elaboration

Light

IM

 

Set red light in PM Elaboration as IM

3

13 - Preparation of final offer - in process

1

PM Elaboration

Light

IM

 

Set yellow light in PM Elaboration as IM

3

18 - Alternative offer accepted

 

PM Offer

Promotion

LA

Active Timetable

Accept Path Modification offer

3

28 - Alternative offer rejected (Revision required)

 

PM Offer

Promotion

LA

PM Elaboration

Ask for Offer adaptation

3

26 - alternative offer rejected (without revision)

 

PM Offer

Promotion

LA

Active Timetable

Reject Path Modification offer

3

XX - Offer/final offer - accepted

2

PM Offer

Light

RA

 

Set green light as RA

3

XX - Offer/final offer - rejected

3

PM Offer

Light

RA

 

Set red light as RA

USE CASES OF THE PATH MODIFICATION PROCESS

START PM (RA)

The PM process can be started by any RA and only when the dossier is in Active Timetable phase. The RA initiating the process is marked as “initiator” in PCS, becomes responsible for the dossier transition and is considered as leading applicant in the PM process. The leading applicant at dossier level, if different than the PM process leading applicant, is participating in the process as an involved or affected applicant. It is a dossier transition; therefore, it shall be completed with a Path Coordination Message without Train Information and Path Information and the dossier enters the Path Modification Conference. As the initiator RA creates a new path modification, the “create dossier” type of information is used.

In this process:

  • Leading applicant refers to the leading applicant only for the path modification process.
  • Leading IM refers to the IM of the pair from the applicant initiating the PM process. It can be the same or a different one than the dossier leading IM.
SENT INFORMATION

The applicant who would like to start the Path Modification process shall send a Path Coordination Message without Train Information and Path Information and with the following information regardless of the path modification type selected by the initiator applicant:

  • Message header:
    • Sender: company code of the initiator applicant
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 30 - Create dossier
  • Planned Transport Identifiers: TR ID, CR ID
RESULT

In case of a successful request, the dossier enters the Path Modification Conference phase and PCS saves the path modification process start, its type and initiator in the “comment” area of the dossier.

NOTIFICATIONS

PCS will send a Receipt Confirmation message only to the LA and a Path Coordination Message to all affected agencies (including the LA) with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected agency
  • TOR: 3 - Modification
  • TOI: 30 - Create dossier
  • Planned Transport Identifiers: TR ID, CR ID

 

WITHDRAW PATH MODIFICATION (RA)

For some reasons, the LA may need to withdraw the dossier from the path modification conference.

SENT INFORMATION

The LA who would like to withdraw the dossier from the Path Modification Conference shall send a Path Coordination Message without Train Information and Path Information and with the following content:

  • Message header:

    • Sender: company code of the LA
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 31 - Close dossier
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field on the message level (mandatory): the reason for the withdrawal
RESULT

In case of a successful request, the dossier is withdrawn by the LA and goes back to Active Timetable stage to its former state, keeps its original identifiers and the reason for the withdrawal is saved in the “comment” area of the dossier.

NOTIFICATIONS

PCS will send a Receipt Confirmation message only to the LA and a Path Coordination Message to all affected agencies (including the LA) with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected agency
  • TOR: 3 - Modification
  • TOI: 31 - Close dossier
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field on the message level (mandatory): the reason for the withdrawal

 

SUBMIT PATH MODIFICATION REQUEST (RA)

After the Path Modification Conference, the LA has the possibility to submit a path modification request.

SENT INFORMATION

The LA who would like to submit a path modification request shall send a Path Coordination Message without Train Information and Path Information and with the following content:

  • Message header:

    • Sender: company code of the LA
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 4 - Harmonization completed
  • Planned Transport Identifiers: TR ID, CR ID
RESULT

In case of a successful request, the dossier enters the Path Modification Elaboration phase.

NOTIFICATIONS

PCS will send a Receipt Confirmation message only to the LA and a Path Coordination Message to all affected applicants with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected applicant
  • TOR: 3 - Modification
  • TOI: 4 - Harmonization completed
  • Planned Transport Identifiers: TR ID, CR ID

 

PCS will send a Path Request Message to all affected IMs/ABs with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved IM
  • TOR: 3 - Modification
  • TOI: 4 - Harmonization completed  
  • Planned Transport Identifiers: TR ID, CR ID, PR ID
  • Related Planned Transport Identifiers: PA ID corresponding to the PR ID
  • Train Information
  • Path Information

 

The Path Modification Request phase is a milestone; therefore, all affected IMs will also receive a Path Coordination Message (for the transition to the Path Modification Elaboration phase) with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected IM
  • TOR: 3 - Modification
  • TOI: 7 - Create offer
  • Planned Transport Identifiers: TR ID, CR ID

 

WITHDRAW PATH MODIFICATION REQUEST (RA)

The LA has the possibility to withdraw the path modification request. With this action, the dossier returns to Active Timetable phase to its former state and keeps its original identifiers.

SENT INFORMATION

The LA who would like to withdraw the Path Modification request shall send a Path Coordination Message without Train Information and Path Information and with the following content:

  • Message header:

    • Sender: company code of the LA
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 29 - Withdrawal
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field on the message level (mandatory): the reason for the withdrawal
RESULT

In case of a successful request, the path modification request is withdrawn by the LA and the dossier returns to Active Timetable phase to its former state, keeps its original identifiers and the reason for the withdrawal is saved in the “comment” area of the dossier.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the LA and a Path Coordination Message to all affected agencies with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected agency
  • TOR: 3 - Modification
  • TOI: 29 - Withdrawal
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field on the message level (mandatory): the reason for the withdrawal

 

REJECT PATH MODIFICATION REQUEST (IM)

The LIM/LAB has the possibility to reject the path modification request. With this action, the dossier returns to Active Timetable to its former state and keeps its original identifiers.

SENT INFORMATION

The LIM who would like to reject a path modification request shall send a Path Coordination Message without Train Information and Path Information and with the following content:

  • Message header:

    • Sender: company code of the LIM
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 21 - No alternative available
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field on the message level (mandatory): the reason for the rejection
RESULT

In case of a successful request, the path modification request is rejected by the LIM/LAB and the dossier goes back to Active Timetable phase to its former state, keeps its original identifiers and the reason for the rejection is saved in the “comment” area of the dossier.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the LIM/LAB and a Path Coordination Message to all affected agencies with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected agency
  • TOR: 3 - Modification
  • TOI: 21 - No alternative available
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field on the message level: the reason for the rejection

 

SUBMIT PATH MODIFICATION OFFER (IM)

After the Path Modification Elaboration phase, the LIM/LAB has the possibility to submit a path modification offer.

SENT INFORMATION

The LIM who would like to submit an offer to the path modification request, shall send a Path Coordination Message without Train Information and Path Information and with the following content:

  • Message header:

    • Sender: company code of the LIM
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 16 - Final offer
  • Planned Transport Identifiers: TR ID, CR ID
RESULT

In case of a successful request and if all the mandatory information is fulfilled in the dossier and all the IMs acceptance indicators are set to green, the dossier enters the Path Modification Offer phase.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the LIM/LAB and a Path Coordination Message to all affected IMs with the following content:

  • Message header:

    • Sender: 3178 (RNE)
    • Recipient: company code any affected IM
  • TOR: 3 - Modification
  • TOI: 16 - Final offer
  • Planned Transport Identifiers: TR ID, CR ID

 

PCS will send a Path Details Message to all affected applicants with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected applicant
  • TOR: 3 - Modification
  • TOI: 16 - Final Offer
  • Planned Transport Identifiers: TR ID, CR ID, PR ID, PA ID
  • Related planned transport identifier: PA ID (original one before the modification)

 

ACCEPT PATH MODIFICATION OFFER (RA)

SENT INFORMATION

The LA who would like to accept the path modification offer and move the dossier to Active Timetable shall send a Path Coordination Message without Train Information and Path Information and with the following content:

  • Message header:
    • Sender: company code of the LA
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 18 - Alternative offer accepted
  • Planned Transport Identifiers: TR ID, CR ID
RESULT

In case of a successful request, the dossier is moved to Active Timetable phase with new identifiers and the IM timetable remains as it was offered in the path modification offer.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the LA and a Path Coordination Message to all affected applicants with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected applicant
  • TOR: 3 - Modification
  • TOI: 18 - Alternative offer accepted
  • Planned Transport Identifiers: TR ID, CR ID, PA ID

 

PCS will send a Path Confirmed Message to all affected IM/ABs with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected IM
  • TOR: 3 - Modification
  • TOI: 18 - Alternative offer accepted
  • Planned Transport Identifiers: TR ID, CR ID, PA ID

 

When the dossier enters to Active Timetable, PCS will send a Path Details Message to all affected agencies with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected agencies
  • TOR: 3 - Modification
  • TOI: 22 - Booked
  • Planned Transport Identifiers: TR ID, CR ID, PA ID

 

REJECT PATH MODIFICATION OFFER

SENT INFORMATION

The LA who would like to reject the path modification offer shall send a Path Coordination Message without Train Information and Path Information and with the following content:

  • Message header:
    • Sender: company code of the LA
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 26 - Alternative offer rejected (without revision)
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field for the mandatory comment: the reason for the rejection
RESULT

In case of a successful request, the path modification offer is rejected by the LA, the dossier goes back to Active Timetable phase and keeps its former state and original identifiers.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the LA and a Path Coordination Message to all affected applicants with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected applicants
  • TOR: 3 - Modification
  • TOI: 26 - Alternative offer rejected (without revision)
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field for the mandatory comment: the reason for the rejection

 

PCS will send a Path Details Refused to all affected IMs with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected IM
  • TOR: 3 - Modification
  • TOI: 26 - Alternative offer rejected (without revision)
  • Planned Transport Identifiers: TR ID, CR ID, PA ID

 

ASK FOR OFFER ADAPTATION

SENT INFORMATION

The LA who would like to request an offer adaptation shall send a Path Coordination Message without Train Information and Path Information and with the following content:

  • Message header:
    • Sender: company code of the LA
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 28 - Alternative offer rejected (revision required)
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field for the mandatory comment
RESULT

In case of a successful request, the dossier is moved to Path Modification Elaboration phase and the IMs/ABs get edit access rights on the IM timetable.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the LA and a Path Coordination Message to all affected applicants with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected applicant
  • TOR: 3 - Modification
  • TOI: 28 - Alternative offer rejected (revision required)
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field for the mandatory comment

 

PCS will send a Path Details Refused to all affected IMs with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected IM
  • TOR: 3 - Modification
  • TOI: 28 - Alternative offer rejected (revision required)
  • Planned Transport Identifiers: TR ID, CR ID, PA ID

 

EDIT SUB-PATH IN PATH MODIFICATION CONFERENCE (RA)

The LA can only edit the running days which are in the future. The sub-path itself is not editable. Moreover, to avoid that the applied changes run into the past due to the potential long duration of the Path Modification Conference, the LA can select the “adjust validity period” option.

SENT INFORMATION
 

The affected applicant who would like to edit a sub-path in a path modification conference shall send a Path Coordination Message with Path Information and the following content:

  • Message header:
    • Sender: company code of the applicant
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 1 - Harmonization in process
  • Planned Transport Identifiers: TR ID, CR ID, PR ID
  • Path Information
RESULT

In case of a successful update, the sub-path is updated according to the sent Path Information content. If the sub-path has days in the past and the user would like to proceed further with this update, the system will return an error code (673: only future days can be changed for sub-paths in PA/PM)

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the original sender and an Object Info Message to all affected applicants with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected applicant
  • TOR: 3 - Modification
  • TOI: 1 - Harmonization in process
  • Identifier: CR ID
  • Path Information Extended - An array of all the sub-paths in the dossier in the following structure:
    • Planned Transport Identifiers: TR ID, CR ID, PR ID, PA ID
    • Path Information

 

ADD NEW SUB-PATH IN PATH MODIFICATION CONFERENCE (RA)

SENT INFORMATION

The affected applicant who would like to edit a sub-path in a path modification conference shall send a Path Coordination Message with Path Information and with the following content:

  • Message header:
    • Sender: company code of the applicant
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 1 - Harmonization in process
  • Planned Transport Identifiers: TR ID, CR ID, PR ID*
  • Path Information
*Optional for the original sender to provide it. If not provided, PCS will generate it.
RESULT

The new sub-path will be added to the dossier. In case of overlapping running days with other sub-paths, they will be automatically deselected by PCS.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the original sender and an Object Info Message to all affected applicants with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected applicant
  • TOR: 3 - Modification
  • TOI: 1 - Harmonization in process
  • Identifier: CR ID
  • Path Information Extended: an array of all the sub-paths in the dossier in the following structure
    • Planned Transport Identifiers: TR ID, CR ID, PR ID, PA ID
    • Path Information

 

DELETE SUB-PATH IN PATH MODIFICATION CONFERENCE (RA)

The sub-path to be deleted must have a validity period and running days in the future. More than one sub-path can be deleted in one request if they all belong to the same territory.

SENT INFORMATION

The affected applicant who would like to delete a sub-path in a path modification conference shall send a Path Coordination Message with the following content:

  • Message header:
    • Sender: company code of the applicant
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 32 - Path cancelled full
  • Planned Transport Identifiers: TR ID, CR ID, PR ID
RESULT

In case of a successful update, the sub-path is deleted from the dossier. If the sub-path has days in the past and the user tries to proceed further with this update, the system will return an error code (673: only future days can be changed for sub-paths in PA/PM; or 674: the selected sub-paths do not belong to the added RU-IM Pair ID).

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the original sender and a Object Info Message to all affected applicants (including the original sender) with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected applicant
  • TOR: 3 - Modification
  • TOI: 32 - Path cancelled full
  • Planned Transport Identifiers: TR ID, CR ID, PR ID

 

EDIT SUB-PATH IN PATH MODIFICATION ELABORATION (IM)

Running days in the future and the sub-path(s) with a validity period in the future are editable. 

SENT INFORMATION

The affected IM who would like to edit a sub-path in the PM Elaboration phase shall send a Path Coordination Message with Path Information and the following content:

  • Message header:
    • Sender: company code of the IM
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 13 - Preparation of final offer - In process
  • Planned Transport Identifiers: TR ID, CR ID, PA ID
  • Path Information
RESULT

In case of a successful update, the sub-path is updated according to the sent Path Information content. If the sub-path has days in the past and the user would like to proceed further with this update, the system will return an error code (673: only future days can be changed for sub-paths in PA/PM)

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the original sender and an Object Info Message to all affected IMs with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected IM
  • TOR: 3 - Modification
  • TOI: 13 - Preparation of final offer - In process
  • Identifier: CR ID
  • Path Information Extended - An array of all the sub-paths in the dossier in the following structure:
    • Planned Transport Identifiers: TR ID, CR ID, PR ID, PA ID
    • Path Information

 

ADD NEW SUB-PATH IN PATH MODIFICATION ELABORATION (IM)

SENT INFORMATION

The affected IM who would like to add a new sub-path in the PM Elaboration phase shall send a Path Coordination Message with Path Information and with the following content:

  • Message header:
    • Sender: company code of the IM
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 13 - Preparation of final offer - In process
  • Planned Transport Identifiers: TR ID, CR ID, PA ID*
  • Path Information
*Optional for the original sender to provide it. If not provided, PCS will generate it.
RESULT

In case of a successful update, the new sub-path will be added to the dossier. In case of overlapping running days with other sub-paths, they will be automatically deselected by PCS.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the original sender and an Object Info Message to all affected agencies with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected agency
  • TOR: 3 - Modification
  • TOI: 13 - Preparation of final offer - In process
  • Identifier: CR ID
  • Path Information Extended: an array of all the sub-paths in the dossier in the following structure
    • Planned Transport Identifiers: TR ID, CR ID, PR ID, PA ID
    • Path Information

 

DELETE SUB-PATH IN PATH MODIFICATION ELABORATION (IM)

The sub-path to be deleted must have a validity period and running days in the future. More than one sub-path can be deleted in one request if they all belong to the same territory.

SENT INFORMATION

The affected IM who would like to delete a sub-path in the PA Conference shall send a Path Coordination Message with the following content:

  • Message header:
    • Sender: company code of the IM
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 32 - Path cancelled full
  • Planned Transport Identifiers: TR ID, CR ID, PA ID
RESULT

In case of a successful update, the sub-path is deleted from the dossier. If the sub-path has days in the past and the user tries to proceed further this update, the system will return an error code (673: only future days can be changed for sub-paths in PA/PM; or 674: the selected sub-paths do not belong to the added RU-IM Pair ID).

NOTIFICATION

PCS will send a Receipt Confirmation only to the original sender and a Object Info Message to all affected agencies (including the original sender) with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved agency
  • TOR: 3 - Modification
  • TOI: 32 - Path cancelled full
  • Planned Transport Identifiers: TR ID, CR ID, PA ID

 

SET GREEN LIGHT AS RA

SENT INFORMATION

The affected applicant who would like to set the acceptance indicator to green shall send a Path Coordination Message without Train Information and Path Information and with the following content:

  • Message header:
    • Sender: company code of the applicant
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI:
    • PM Conference: 2 - Harmonization accepted
    • PM Offer: 2 - Harmonization accepted (NOTE: future change request for another code)
  • Planned Transport Identifiers: TR ID, CR ID
RESULT

In case of a successful update, the acceptance indicator of the applicant changes to green.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the original sender with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the original sender
  • TOR: 3 - Modification
  • TOI:
    • PM Conference: 2 - Harmonization accepted
    • PM Offer: 2 - Harmonization accepted (NOTE: future change request for another code)
  • Planned Transport Identifiers: TR ID, CR ID

 

SET YELLOW LIGHT AS RA

SENT INFORMATION

The affected applicant who would like to set the acceptance indicator to yellow shall send a Path Coordination Message without Train Information and Path Information and with the following content:

  • Message header:
    • Sender: company code of the applicant 
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI:
    • PM Conference: 1 - Harmonization in progress
    • PM Offer: 1 - Harmonization in process (NOTE: future change request for another code)
  • Planned Transport Identifiers: TR ID, CR ID
RESULT

In case of a successful update, the acceptance indicator of the applicant changes to yellow.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the original sender and a Path Coordination Message to all affected applicants with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved applicant
  • TOR: 3 - Modification
  • TOI:
    • PM Conference: 1 – Harmonization in progress
    • PM Offer: 1 - Harmonization in process (NOTE: future change request for another code)
  • Planned Transport Identifiers: TR ID, CR ID

 

SET GREEN LIGHT AS IM

SENT INFORMATION

The affected IM who would like to set the acceptance indicator to green shall send a Path Coordination Message without Train Information and Path Information and with the following content:

  • Message header:
    • Sender: company code of the IM
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 14 - Preparation of final offer - Accepted
  • Planned Transport Identifiers: TR ID, CR ID
RESULT

In case of a successful update, the acceptance indicator(s) of the IM changes to green.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the original sender and a Path Coordination Message to all affected IM with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the involved IM
  • TOR: 3 - Modification
  • TOI: 14 - Preparation of final offer - Accepted
  • Planned Transport Identifiers: TR ID, CR ID

 

SET YELLOW LIGHT AS IM

SENT INFORMATION

The affected IM who would like to set the acceptance indicator to green shall send Path Coordination Message without Train Information and Path Information and with the following content:

  • Message header:
    • Sender: company code of the IM
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 13 - Preparation of final offer – In process
  • Planned Transport Identifiers: TR ID, CR ID
RESULT

In case of a successful update, the acceptance indicator of the IM changes to yellow.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the original sender and a Path Coordination Message to all affected IM with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved IM
  • TOR: 3 - Modification
  • TOI: 13 - preparation of final offer – In process
  • Planned Transport Identifiers: TR ID, CR ID

 

SET RED LIGHT AS RA

SENT INFORMATION

The affected applicant who would like to set the acceptance indicator to red shall send Path Coordination Message without Train Information and Path Information and with the following content:

  • Message header:
    • Sender: company code of the applicant
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI:
    • PM Conference: 3 - Harmonisation - Rejected
    • PM Offer: 3 - Harmonisation - Rejected (NOTE: future change request for another code)
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field for the mandatory comment
RESULT

In case of a successful update, the acceptance indicator(s) of the Applicant changes to red, and the comment is saved in the “comment” area of the dossier.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the original sender and a Path Coordination Message to all affected applicants with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved applicants
  • TOR: 3 - Modification
  • TOI:
    • PM Conference: 3 - Harmonisation - Rejected
    • PM Offer: 3 - Harmonisation - Rejected (NOTE: future change request for another code)
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field for the mandatory comment

 

SET RED LIGHT AS IM

SENT INFORMATION

The affected IM who would like to set the acceptance indicator to red shall send a Path Coordination Message without Train Information and Path Information and with the following content:

  • Message header:
    • Sender: company code of the IM
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 15 - Preparation of final offer - Rejected
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field for the mandatory comment
RESULT

In case of a successful update, the acceptance indicator of the IM changes to red and the comment is saved in the “comment” area of the dossier.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the original sender and a Path Coordination Message to all affected IMs/ABs with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved IM
  • TOR: 3 - Modification
  • TOI: 15 - Preparation of final offer - Rejected
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field for the mandatory comment

 

 

Path Alteration process

The Path Alteration (PA) process type is available for dossiers in Active Timetable phase, for all path request process types and can be initiated by any IM.

TOI overview

TOR

TOI

FALLBACK

PHASE

ACTOR

TARGET PHASE

ACTION

3

21 - No alternative available

 

Active Timetable

LIM

PA Conference

Start PA as Cancellation

3

23 - Preparation of alternative offer in progress

 

Active Timetable

LIM

PA Conference

Start PA with alternative offer

3

29 - Withdrawal

 

PA Conference

LIM

Active Timetable

Withdraw Path Alteration (return to Active Timetable, keeping original IDs)

3

24 – Alternative offer triggered by IM

 

PA Conference

LIM

PM Offer

Submit Path Alteration offer

3

23 - Preparation of draft alternative offer is in progress

1

PA Conference

IM

 

General timetable update

3

23 - Preparation of draft alternative offer is in progress

1

PA Conference

IM

 

Set yellow light in PA Conference as IM

3

XX - Preparation of draft alternative offer is accepted

2

PA Conference

IM

 

Set green light in PA Conference as IM

3

XX - Preparation of draft alternative offer is rejected

3

PA Conference

IM

 

Set red light in PA Conference as IM

3

18 - Alternative offer accepted

 

PA Offer

LA

Active Timetable

Accept Path Alteration offer

3

26 - Alternative offer rejected (without revision)

 

PA Offer

LA

Active Timetable

Reject Path Alteration offer

3

28 - Alternative offer rejected (revision required)

 

PA Offer

LA

Path Elaboration

Ask for Offer adaptation

3

XX - Offer/final offer - accepted

2

PA Offer

RA

 

Set green light in PA Offer as RA

3

XX - Offer/final offer - rejected

3

PA Offer

RA

 

Set red light in PA Offer as RA

USE CASES PF PATH ALTERATION PROCESS 

START PA (IM)

The PA process can be started by any IM and only when the dossier is in Active Timetable phase. The IM initiating the process is marked as “initiator” in PCS, becomes responsible for the dossier transition and is considered as leading IM in the PA process. The leading IM at dossier level, if different than the PA process leading IM, is participating in the process as an involved or affected IM. It is a dossier transition; therefore, it shall be completed with a Path Coordination Message without Train Information and Path Information and the dossier enters the Path Alteration Conference.

In this process:

  • Leading IM refers to the leading IM only for the path alteration process.
  • Leading applicant refers to the applicant of the pair from the IM initiating the PA process. It can be the same or a different one than the dossier leading applicant.

 

SENT INFORMATION

The IM who would like to start the path alteration process shall send a Path Coordination Message without Train Information and Path Information and with the following content:

No alternative path available:

  • Message header:
    • Sender: company code of the initiator IM
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 21 - No alternative available (PCS PA Type 2)
  • Planned Transport Identifiers: TR ID, CR ID

 

Alternative path available:

  • Message header:
    • Sender: company code of the initiator IM
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 23 - Preparation of alternative offer in progress (PCS PA Type 7)
  • Planned Transport Identifiers: TR ID, CR ID
RESULT

In case of a successful request, the dossier enters the Path Alteration Conference phase and PCS saves the path alteration process start, its type and initiator agency in the “comment” area of the dossier.

NOTIFICATIONS

PCS will send a Receipt Confirmation message only to the LIM and a Path Coordination Message to all affected IMs with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected IM
  • TOR: 3 - Modification
  • TOI: 21 (no alternative available) or 23 (alternative path available)  
  • Planned Transport Identifiers: TR ID, CR ID

 

WITHDRAW PATH ALTERATION (IM)

For some reasons, the LIM may need to withdraw the dossier from the path alteration conference.

SENT INFORMATION

The LIM who would like to withdraw the dossier from the path alteration conference shall send a Path Coordination Message without Train information and Path Information and with the following content:

  • Message header:
    • Sender: company code of the LIM
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 29 - Withdrawal
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field on the message level: the reason of the withdrawal
RESULT

In case of a successful update, the dossier is withdrawn by the LIM and goes back to Active Timetable phase to its former state, keeps its original identifiers and the reason for the withdrawal is saved in the “comment” area of the dossier.

NOTIFICATIONS

PCS will send a Receipt Confirmation message only to the LIM and a Path Coordination Message to all affected IMs with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected agency
  • TOR: 3 - Modification
  • TOI: 31 - Close dossier
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field on the message level (mandatory: the reason for the withdrawal)

 

SUBMIT PATH ALTERATION OFFER (IM)

SENT INFORMATION

The LIM who would like to submit a path alteration offer, shall send a Path Coordination Message without Train Information and Path Information with the following content:

  • Message header:
    • Sender: company code of the LIM
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 24 - Alternative offer triggered by IM
  • Planned Transport Identifiers: TR ID, CR ID
RESULT

In case of a successful request, the dossier enters the Path Alteration Offer phase.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the LIM and a Path Coordination Message to all affected IMs with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected IM
  • TOR: 3 - Modification
  • TOI: 24 - Alternative offer triggered by IM
  • Planned Transport Identifiers: TR ID, CR ID

 

PCS will send the following messages to all affected applicants with the following content:

  1. Path Not Available Messages

Depending on the previous messages and the selected Path Alteration type in the dossier, the applicant shall receive one of these messages:

No alternative path available:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved applicant
  • TOR: 3 - Modification
  • TOI: 21 - No alternative available
  • Planned Transport Identifiers: TR ID, CR ID, PA ID

 

Alternative path available:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved applicant
  • TOR: 3 - Modification
  • TOI: 23 - Preparation of alternative offer in progress
  • Planned Transport Identifiers: TR ID, CR ID, PA ID

 

  1. Path Details Messages

Alternative path available

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved applicant
  • TOR: 3 - Modification
  • TOI: 24 - Alternative offer triggered by IM
  • Planned Transport Identifiers: TR ID, CR ID, PA ID

 

ACCEPT PATH ALTERATION OFFER (RA)

SENT INFORMATION

The LA who would like to accept the Path Alteration offer and move it to Active Timetable phase shall send a Path Coordination Message without Train Information and Path Information with the following content:

  • Message header:
    • Sender: company code of the LA
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 18 - Alternative offer accepted
  • Planned Transport Identifiers: TR ID, CR ID
RESULT

In case of a successful request, the dossier is moved to Active Timetable phase with new identifiers and the IM timetable remains as it was offered in the path alteration offer.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the LA and a Path Coordination Message to all affected applicants with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected applicant
  • TOR: 3 - Modification
  • TOI: 18 - Alternative offer accepted
  • Planned Transport Identifiers: TR ID, CR ID, PA ID

 

PCS will send a Path Confirmed Message to all affected IMs with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected IM
  • MS: 1 - Creation
  • TOR: 3 - Modification
  • TOI: 18 - Alternative offer accepted
  • Planned Transport Identifiers: TR ID, CR ID, PA ID

 

When the dossier enters to Active Timetable, PCS will send a Path Details Message to all affected agencies with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected agencies
  • TOR: 3 - Modification
  • TOI: 22 - Booked
  • Planned Transport Identifiers: TR ID, CR ID, PA ID

 

REJECT PATH ALTERATION OFFER (RA)

SENT INFORMATION

The LA who would like to reject the path alteration offer shall send a Path Coordination Message without Train Information and Path Information with the following content:

  • Message header:
    • Sender: company code of the LA
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 26 - Alternative offer rejected (without revision)
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text for the mandatory comment: the reason for the rejection
RESULT

In case of a successful request, the path alteration offer is rejected by the LA, the dossier goes back to Active Timetable phase and keeps its former state and original identifiers.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the LA and a Path Coordination Message to all affected applicants with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected applicant
  • TOR: 3 - Modification
  • TOI: 26 - Alternative offer rejected (without revision)
  • Planned Transport Identifiers: TR ID, CR ID, PA ID

 

PCS will send a Path Details Refused to all affected IMs with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected IM
  • TOR: 3 - Modification
  • TOI: 26 - Alternative offer rejected (without revision)
  • Planned Transport Identifiers: TR ID, CR ID, PA ID

 

ASK FOR OFFER ADAPTATION (RA)

SENT INFORMATION

The LA who would like to request a path alteration offer adaptation shall send a Path Coordination Message without Train Information and Path Information with the following content:

  • Message header:
    • Sender: company code of the LA
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 28 - Alternative offer rejected (revision required)
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text for the mandatory comment
RESULT

In case of a successful request, the dossier is moved to Path Alteration Conference Elaboration phase and the IMs get edit access rights on the IM timetable.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the LA and a Path Coordination Message to all affected applicants with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected applicant
  • TOR: 3 - Modification
  • TOI: 28 - Alternative offer rejected (revision required)
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text for the mandatory comment

 

PCS will send a Path Details Refused to all affected IMs with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected IM
  • TOR: 3 - Modification
  • TOI: 28 - Alternative offer rejected (revision required)
  • Planned Transport Identifiers: TR ID, CR ID, PA ID

 

EDIT SUB-PATH IN PA CONFERENCE (IM)

Running days in the future and the sub-paths with a validity period in the future are editable. 

SENT INFORMATION

The affected IM who would like to edit a sub-path in the Path Alteration Conference phase shall send a Path Coordination Message with Path Information and the following content:

  • Message header:
    • Sender: company code of the IM
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 23 - Preparation of draft alternative offer is in progress
  • Planned Transport Identifiers: TR ID, CR ID, PA ID
  • Path Information
RESULT

In case of a successful update, the sub-path is updated according to the sent Path Information content. If the sub-path has days in the past, the system will return an error code (673: only future days can be changed for sub-paths in PA/PM).

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the original sender and an Object Info Message to all affected agencies with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected agency
  • TOR: 3 - Modification
  • TOI: 23 - Preparation of draft alternative offer is in progress
  • Identifier: CR ID
  • Path Information Extended: an array of all the sub-paths in the dossier in the following structure
    • Planned Transport Identifiers: TR ID, CR ID, PR ID, PA ID
    • Path Information

 

ADD NEW SUB-PATH IN PA CONFERENCE (IM)

The added new sub-path must have a validity period and running days in the future.

SENT INFORMATION

The affected IM who would like to edit a sub-path in the Path Alteration Conference shall send a Path Coordination Message with Path Information and with the following content:

  • Message header:
    • Sender: company code of the IM
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 23 - Preparation of draft alternative offer is in progress
  • Planned Transport Identifiers: TR ID, CR ID, PA ID*
  • Path Information
*Optional for the original sender to provide it. If not provided, PCS will generate it.
RESULT

In case of a successful update, the new sub-path will be added to the dossier. In case of overlapping running days with other sub-paths, they will be automatically deselected by PCS.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the original sender and a Path Coordination Message to all affected agencies with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected agency
  • TOR: 3 - Modification
  • TOI: 23 - preparation of draft alternative offer is in progress
  • Identifier: CR ID
  • Path Information Extended: an array of all the sub-paths in the dossier in the following structure
    • Planned Transport Identifiers: TR ID, CR ID, PR ID, PA ID
    • Path Information

 

DELETE SUB-PATH IN PA CONFERENCE (IM) 

The sub-path to be deleted must have a validity period and running days in the future. More than one sub-path can be deleted in one request if they all belong to the same territory.

SENT INFORMATION

The affected IM who would like to delete a sub-path in the Path Alteration Conference shall send a Path Coordination Message with the following content:

  • Message header:
    • Sender: company code of the IM
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 32 - Path cancelled full
  • Planned Transport Identifiers: TR ID, CR ID, PA ID

Result

In case of a successful update, the sub-path is deleted from the dossier. If the sub-path has days in the past, the system will return an error code (673: only future days can be changed for sub-paths in PA/PM; or 674: the selected sub-paths do not belong to the added RU-IM Pair ID).

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the original sender and a Object Info Message to all affected agencies (including the original sender) with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any involved agency
  • TOR: 3 - Modification
  • TOI: 32 - Path cancelled full
  • Planned Transport Identifiers: TR ID, CR ID, PA ID

 

SET GREEN LIGHT AS IM IN PA CONFERENCE

SENT INFORMATION

The affected IM who would like to set the acceptance indicator to green shall send a Path Coordination Message without Train Information and Path Information, with the following content:

  • Message header:
    • Sender: company code of the affected IM
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 2 - Harmonization accepted (NOTE: later change request for another code)
  • Planned Transport Identifiers: TR ID, CR ID
RESULT

In case of a successful update, the acceptance indicator of the IM changes to green.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the original sender with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the original sender
  • TOR: 3 - Modification
  • TOI: 2 - Harmonization accepted
  • Planned Transport Identifiers: TR ID, CR ID

 

SET GREEN LIGHT AS RA IN PA OFFER

SENT INFORMATION

The affected applicant who would like to set the acceptance indicator to green shall send a Path Coordination Message without Train Information and Path Information and with the following content:

  • Message header:
    • Sender: company code of the affected applicant
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 2 - Harmonization accepted (NOTE: later change request for another code)
  • Planned Transport Identifiers: TR ID, CR ID
RESULT

In case of a successful update, the acceptance indicator(s) of the applicant changes to green.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the original sender and a Path Coordination Message to all affected applicants with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected applicant
  • TOR: 3 - Modification
  • TOI: 2 - Harmonization accepted (NOTE: later change request for another code)
  • Planned Transport Identifiers: TR ID, CR ID

 

SET YELLOW LIGHT AS IM IN PA CONFERENCE

SENT INFORMATION

The affected IM who would like to set the acceptance indicator to yellow shall send Path Coordination Message without Train Information and Path Information and with the following content:

  • Message header:
    • Sender: company code of the affected IM
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 23 - Harmonization in progress (NOTE: later change request for another code)
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text for the mandatory comment
RESULT

In case of a successful update, the acceptance indicator of the IM changes to yellow.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the original sender and a Path Coordination Message to all affected IM with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected IM
  • TOR: 3 - Modification
  • TOI: 23 - Harmonization in progress (NOTE: later change request for another code)
  • Planned Transport Identifiers: TR ID, CR ID

 

SET RED LIGHT AS RA IN PA OFFER

SENT INFORMATION

The affected applicant who would like to set the acceptance indicator to red shall send Path Coordination Message without Train Information and Path Information, with the following content:

  • Message header:
    • Sender: company code of the affected Applicant
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 3 - Harmonization rejected (NOTE: later change request for another code)
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field for the mandatory comment
RESULT

In case of a successful update, the acceptance indicator of the applicant changes to red, and the comment is saved in the “comment” area of the dossier.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the original sender and a Path Coordination Message to all affected applicants with the following content:

  • Message header:
    • Sender: company code of the affected applicant
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 3 - Harmonization rejected (NOTE: later change request for another code)
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text for the mandatory comment

 

SET RED LIGHT AS IM IN PA CONFERENCE

SENT INFORMATION

The affected IM who would like to set the acceptance indicator to red shall send a Path Coordination Message without Train Information and Path Information, with the following content:

  • Message header:
    • Sender: company code of the affected IM
    • Recipient: 3178 (RNE)
  • TOR: 3 - Modification
  • TOI: 3 - Harmonization rejected (NOTE: later change request for another code)
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text field for the mandatory comment
RESULT

In case of a successful update, the acceptance indicator of the IM changes to red and the comment is saved in the “comment” area of the dossier.

NOTIFICATIONS

PCS will send a Receipt Confirmation only to the original sender and a Path Coordination Message to all affected IMs with the following content:

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of the affected IM
  • TOR: 3 - Modification
  • TOI: 3 - Harmonization rejected (NOTE: later change request for another code)
  • Planned Transport Identifiers: TR ID, CR ID
  • Free text for the mandatory comment

 

File