Path Modification process message sequence

About

Version History
Use cases of the path modification process
Download sequence_diagram_for_pcs_communication_path_modification_version_2.1.pdf

1. Version history

Version	Release date	Author	Highlights
2	27.06.2022	Nicolas Jasinski	Alignment between use cases descriptions and sequence diagram
3	23.09.2022	Nicolas Jasinski	Overall remark: improved alignment with the existing implementation, the implementation across the different process types/use cases and the Sector Handbook.”Start PM“: updated implementation status”Withdraw PM ” notifications: PTID and RPTID updated development status”Submit PM request“ notifications: updated development status”Withdraw PM request” notifications: PTID and RPTID updated development status”Submit PM offer”: implementation/development update”Accept PM offer” notifications: PTID and RPTID updated development status”Reject PM offer” notifications: PDRM implementation, PTID and RPTID updated development status”Ask for offer adaption” notifications: PTID and RPTID updated implementation statusClarification between “new” and “old” IDs
4	10.03.2023	Nicolas Jasinski	Start and withdraw PM: PCoM to affected applicants onlyImplementation completed: Withdraw PM, Submit PM request, Submit PM offer, Accept PM offer, Reject PM offer

2. Use cases of the path modification process

New PR ID: refers to a PR ID created after the start of the path modification
New PA ID: refers to a PR ID created after the start of the path modification
Old PA ID: refers to a PA ID belonging to an already booked path (dossier in Active Timetable phase)

2.1 Start PM

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.

2.1.1 Sent information – Under development: pending PCS schema update planned in October 2023

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

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

2.1.3 Notifications

PCS will send a Receipt Confirmation message only to the LA with the following content:

Message header:
- Sender: 3178 (RNE)
- Recipient: company code of the LA
Related reference

PCS will send a Path Coordination Message to all affected applicants 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, new PR ID

2.2 Withdraw Path Modification

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

2.2.1 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

2.2.2 Result

In case of a successful request, the dossier is withdrawn by the LA and goes back to the 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.

2.2.3 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 agency
TOR: 3 – Modification
TOI: 31 – Close dossier
Planned Transport Identifiers: TR ID, CR ID, new PR ID
Related Planned Transport Identifiers: PR IDs belonging to the same territory as the PR ID listed in Planned Transport Identifiers element, PA ID of the booked path
Free text field on the message level (mandatory): the reason for the withdrawal

2.3 Submit Path Modification request

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

2.3.1 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

2.3.2 Result

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

2.3.3 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 (current bug with TOI 1 – under analysis)
Planned Transport Identifiers: TR ID, CR ID, new PR ID, old PA ID
Related Planned Transport Identifiers: PR IDs belonging to the same territory as the PR ID listed in the Planned Transport Identifiers element, PA ID corresponding to the PR ID in PTID

PCS will send a Path Request Message to all affected agencies with the following content:

Message header:
- Sender: 3178 (RNE)
- Recipient: company code of affected agencies
TOR: 3 – Modification
TOI: 4 – Harmonization completed
Planned Transport Identifiers: TR ID, CR ID, new PR ID, old PA ID
Related Planned Transport Identifiers: PR IDs belonging to the same territory as the PR ID listed in the Planned Transport Identifiers element, PA ID corresponding to the PR ID in PTID
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, new PR ID, old PA ID
Related Planned Transport Identifiers: PR IDs belonging to the same territory as the PR ID listed in the Planned Transport Identifiers element, PA ID corresponding to the PR ID in PTID

2.4 Withdraw Path Modification request

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.

2.4.1 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

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

2.4.3 Notifications

PCS will send a Receipt Confirmation only to the LA and a Path Coordination Message to all affected applicants (to all affected IMs: under analysis) 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, new PR ID (under analysis)
Related Planned Transport Identifiers: PR IDs belonging to the same territory as the PR ID listed in Planned Transport Identifiers element
Free text field on the message level (mandatory): the reason for the withdrawal

2.5 Reject Path Modification request

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.

2.5.1 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

2.5.2 Result

In case of a successful request, the path modification request is rejected by the LIM 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.

2.5.3 Notifications

PCS will send a Receipt Confirmation only to the LIM 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
PTID: TR ID, CR ID, new PA ID
RPTID:
- Realted PR ID
Free text field on the message level: the reason for the rejection

2.6 Submit Path Modification offer

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

2.6.1 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

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

2.6.3 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 any affected IM
TOR: 3 – Modification
TOI: 16 – Final offer
Planned Transport Identifiers: TR ID, CR ID, new PA ID
Related Planned Transport Identifiers:
- Old PA ID
- all PR IDs of the territory to which the PA ID in Planned Transport Identifiers element belongs to

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

Message header:
- Sender: 3178 (RNE)
- Recipient: company code of affected agencies
TOR: 3 – Modification
TOI: 16 – Final Offer
Planned Transport Identifiers: TR ID, CR ID, new PA ID
Related Planned Transport Identifiers:
- Old PA ID
- all PR IDs of the territory to which the PA ID in Planned Transport Identifiers element belongs to

2.7 Accept Path Modification offer

2.7.1 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

2.7.2 Result

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

2.7.3 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
PTID: TR ID, CR ID, new PA ID
RPTID: PA IDs and PR IDs belonging to the same territory as the PA ID listed in the Planned Transport Identifiers element

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
TOR: 3 – Modification
TOI: 18 – Alternative offer accepted
PTID: TR ID, CR ID, new PA ID
RPTID: PA IDs and PR IDs belonging to the same territory as the PA ID listed in the Planned Transport Identifiers element

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
PTID: TR ID, CR ID, new PA ID
RPTID: PA IDs and PR IDs belonging to the same territory as the PA ID listed in the Planned Transport Identifiers element

2.8 Reject Path Modification offer

2.8.1 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

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

2.8.3 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)
PTID: TR ID, CR ID, new PA ID
RPTID: PA IDs and PR IDs belonging to the same territory as the PA ID listed in Planned Transport Identifiers element
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)
PTID: TR ID, CR ID, new PA ID
RPTID: PA IDs and PR IDs belonging to the same territory as the PA ID listed in Planned Transport Identifiers element

2.9 Ask for offer adaptation

2.9.1 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

2.9.2 Result

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

2.9.3 Notifications

PCS will send a Receipt Confirmation only to the LA and a Path Coordination Message to all affected applicants (potential improvement being assessed: to all affected agencies)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, new PA ID
Related Planned Transport Identifiers: all new PA IDs and new PR IDs belonging to the same territory as the PA ID listed in Planned Transport Identifiers element
Free text field for the mandatory comment

PCS will send a Path Details Refused 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: 28 – Alternative offer rejected (revision required)
Planned Transport Identifiers: TR ID, CR ID, new PA ID
Related Planned Transport Identifiers: all new PA IDs and new PR IDs belonging to the same territory as the PA ID listed in the Planned Transport Identifiers element

2.10 Edit sub-path in Path Modification conference

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

2.10.1 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

2.10.2 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)

2.10.3 Notifications

PCS will send a Receipt Confirmation only to the updater 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
Train Information Extended:
- PlannedTransportIdentifiers (PTID): TR ID
- RelatedPlannedTransportIdentifiers (RPTID): all objects ID of the dossier
- PathInformationExtended (PIE):
  - PTID: all PR ID only for the changed sub-paths.
  - Path Information: for each PR or PA ID listed in PTID
  - Every subpath gets its own PathInformationExtended element

2.11 Add sub-path in Path Modification conference

2.11.1 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 updater to provide it. If not provided, PCS will generate it.

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

2.11.3 Notifications

PCS will send a Receipt Confirmation only to the updater 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
Train Information Extended:
- PlannedTransportIdentifiers (PTID): TR ID
- RelatedPlannedTransportIdentifiers (RPTID): all objects ID of the dossier
- PathInformationExtended (PIE):
  - PTID: all PR ID only for the changed sub-paths.
  - Path Information: for each PR or PA ID listed in PTID
  - Every subpath gets its own PathInformationExtended element

2.12 Delete sub-path in Path Modification conference

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.

2.12.1 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

2.12.2 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).

2.12.3 Notifications

Automatic downgrade of the acceptance indicators: release for alignment with the behaviour in the Path Request process planned on 14.07.2022

PCS will send a Receipt Confirmation only to the updater and a 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: 32 – Path cancelled full
Planned Transport Identifiers: TR ID, CR ID, PR ID

2.13 Edit sub-path in Path Modification elaboration

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

2.13.1 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

2.13.2 Result

2.13.3 Notifications

Automatic downgrade of the acceptance indicators: release for alignment with the behaviour in the Path Request process planned on 14.07.2022

PCS will send a Receipt Confirmation only to the updater and an Object Info Message to all affected agencies 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
Train Information Extended:
- PlannedTransportIdentifiers (PTID): TR ID
- RelatedPlannedTransportIdentifiers (RPTID): all objects ID of the dossier
- PathInformationExtended (PIE):
  - PTID: all PA ID only for the changed sub-paths.
  - Path Information: for each PR or PA ID listed in PTID
  - Every subpath gets its own PathInformationExtended element

2.14 Add sub-path in Path Modification elaboration

2.14.1 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 updater to provide it. If not provided, PCS will generate it.

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

2.14.3 Notifications

Automatic downgrade of the acceptance indicators: release for alignment with the behaviour in the Path Request process planned on 14.07.2022

PCS will send a Receipt Confirmation only to the updater 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
Train Information Extended:
- PlannedTransportIdentifiers (PTID): TR ID
- RelatedPlannedTransportIdentifiers (RPTID): all objects ID of the dossier
- PathInformationExtended (PIE):
  - PTID: all PA ID only for the changed sub-paths.
  - Path Information: for each PR or PA ID listed in PTID
  - Every subpath gets its own PathInformationExtended element

2.15 Delete sub-path in Path Modification elaboration

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.

2.15.1 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

2.15.2 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).

2.15.3 Notifications

Automatic downgrade of the acceptance indicators: release for alignment with the behaviour in the Path Request process planned on 14.07.2022

PCS will send a Receipt Confirmation only to the updater and a Object Info Message to all affected agencies 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

2.16 Set acceptance indicator to green (as RA)

2.16.1 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
Planned Transport Identifiers: TR ID, CR ID

2.16.2 Result

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

2.16.3 Notifications

PCS will send a Receipt Confirmation only to the updater and a Path Coordination Message to the involved applicants with the following content:

Message header:
- Sender: 3178 (RNE)
- Recipient: company code of any involved agency
TOR: 3
TOI: 2
Planned Transport Identifiers: TR ID, CR ID, PR ID

2.17 Set acceptance indicator to yellow (as RA)

2.17.1 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
Planned Transport Identifiers: TR ID, CR ID

2.17.2 Result

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

2.17.3 Notifications

PCS will send a Receipt Confirmation only to the updater and a Path Coordination Message to the involved applicants with the following content:

Message header:
- Sender: 3178 (RNE)
- Recipient: company code of any involved applicant
TOR: 3
TOI: 1
Planned Transport Identifiers: TR ID, CR ID, PR ID

2.18 Set acceptance indicator to red (as RA)

2.18.1 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
Planned Transport Identifiers: TR ID, CR ID
Free text field for the mandatory comment

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

2.18.3 Notifications

PCS will send a Receipt Confirmation only to the updater and a Path Coordination Message to the involved applicants with the following content:

Message header:
- Sender: 3178 (RNE)
- Recipient: company code of any involved applicants.
TOR: 3
TOI: 3
Planned Transport Identifiers: TR ID, CR ID, PR ID

2.19 Set acceptance indicator to green (as IM)

2.19.1 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

2.19.2 Result

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

2.19.3 Notifications

PCS will send a Receipt Confirmation only to the updater and a Path Coordination Message to the involved IMs with the following content:

Message header:
- Sender: 3178 (RNE)
- Recipient: company code of any involved IMs.
TOR: 3
TOI: 14
Planned Transport Identifiers: TR ID, CR ID, PA ID

2.20 Set acceptance indicator to yellow (as IM)

2.20.1 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

2.20.2 Result

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

2.20.3 Notifications

PCS will send a Receipt Confirmation only to the updater and a Path Coordination Message to the involved IMs with the following content:

Message header:
- Sender: 3178 (RNE)
- Recipient: company code of any involved IMs.
TOR: 3
TOI: 13
Planned Transport Identifiers: TR ID, CR ID, PA ID

2.21 Set acceptance indicator to red (as IM)

2.21.1 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

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

2.21.3 Notifications

PCS will send a Receipt Confirmation only to the updater and a Path Coordination Message to the involved IMs with the following content:

Message header:
- Sender: 3178 (RNE)
- Recipient: company code of any involved IMs.
TOR: 3
TOI: 15
Planned Transport Identifiers: TR ID, CR ID, PA ID

3. Download sequence_diagram_for_pcs_communication_path_modification_version_2.1.pdf

Users can download or print the PDF document. Click the arrow to download or the printer icon to print.

Click the printer icon to select the printing option and find your home printer in the “see more” settings

sequence_diagram_for_pcs_communication_path_modification_version_2.1 Download

Do you have a question or want to give us feedback?

Contact & Service Desk
Monday - Thursday: 09:00 - 16:00
Fridays: 09:00 - 15:00

RailNetEurope

Joint Office
Jakov-Lind-Straße 5, Austria Campus 3
1020 Vienna
AUSTRIA

Support

E-Mail: support.ecmt@rne.eu