Path Alteration process message sequence

About

Back to Path Alteration process

Table of contents

1. Version History

VersionRelease dateAuthorHighlights
227.06.2022Nicolas Jasinski– Alignment between use cases description and sequence diagram- Missing use case identified: not alternative path available. Need alignment with PCS CCB and Process Group before implementation in the interface
323.09.2022Nicolas JasinskiOverall remark: improved alignment with the existing implementation, the implementation across the different process types/use cases and the Sector Handbook.- “Start PA”: implementation/development update- “Ask for offer adaptation” notifications: updated PTID and RPTID (not/partially described in the previous version)- “Withdraw path alteration“: updated PTID and RPTID (not/partially described in the previous version) and development status- “Accept path alteration offer” notifications: updated PTID and RPTID (not/partially described in the previous version) and development status- ‘Reject path alteration offer”: updated PTID and RPTID (not/partially described in the previous version)- Clarification between “new” and “old” IDs
410.03.2023Nicolas Jasinski– Implementation completed: Start PA, Submit PA offer, Accept PA offer, Reject PA offer,
In progressIn progressNicolas Jasinski– “Withdraw path alteration“: also applicable for withdrawal from PA offer

Back to top

2. Use cases of the path alteration process

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

Back to top

2.1 Start PA

The PA process can be started by any IM and only when the dossier is in the Active Timetable phase. The IM initiating the process is marked as an “initiator” in PCS, becomes responsible for the dossier transition and is considered as leading IM in the PA process. The leading IM at the 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.

2.1.1 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:

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

No alternative path available:

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

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

2.1.3 Notifications

PCS will send a Receipt Confirmation message only to the LIM 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 IMs with the following content:

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

If the process is triggered in PCS GUI, the following applies for the type of information doe:

  • If “Cancellation of days (no alternative path available)” or Path not available (offering of alternative path) is selected with other PA types: it takes precedence over the other types.
  • If “Cancellation of days (no alternative path available)” nor Path not available (offering of alternative path) are selected: “Cancellation of days (no alternative path available)” (TOI 21) takes precedence
  • If both “Cancellation of days (no alternative path available)” and “Path not available (offering of alternative path)” are not selected in the dossier (let’s say some or all of the remaining ones are selected): TOI 23 is the default TOI

Back to top

2.2 Withdraw Path Alteration

For some reason, the LIM may need to withdraw the dossier from the path alteration conference or PA offer.

2.2.1 Sent information

The LIM who would like to withdraw the dossier from the path alteration conference or PA 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 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 for the withdrawal 

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

2.2.3 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: 29 – Close dossier
  • Planned Transport Identifiers: TR ID, CR ID, old PA (implementation in March 2023)
  • Other PA IDs and PR IDs belonging to the same territory as the PA ID listed in Planned Transport Identifiers element 
  • Free text field on the message level: mandatory reason for the withdrawal 

Back to top

2.3 Submit Path Alteration offer

2.3.1 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

2.3.2 Result

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

2.3.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 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: 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:

2.3.3.1 Path Not Available Message 

Alternative 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, old PA ID 
  • Related Planned Transport Identifiers: new PA ID  

No alternative 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, old PA ID 
  • Related Planned Transport Identifiers: new PA ID  

2.3.3.2 Path Details Message

  • 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, new PA ID
  • Related Planned Transport Identifiers:
    • Old PA ID 

Back to top

2.4 Accept Path Alteration Offer

2.4.1 Sent information

The LA who would like to accept the Path Alteration offer and move it to the 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

2.4.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 alteration offer.

2.4.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
  • Planned Transport Identifiers: TR ID, CR ID, new 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
  • PTID: TR ID, CR ID, new PA ID
  • RPTID: PA belonging to the same territory as the PA ID listed in the Planned Transport Identifiers element (under development)

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:
    • Old PA ID 

Back to top

2.5 Reject Path Alteration Offer

2.5.1 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

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

2.5.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: 26 – Alternative offer rejected (without revision)
  • PTID: TR ID, CR ID, new PA ID
  • RPITD: other 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 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
  • RPITD: other PA IDs and PR IDs belonging to the same territory as the PA ID listed in the Planned Transport Identifiers element

Back to top

2.6 Ask for offer adaption

2.6.1 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

2.6.2 Result

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

2.6.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: 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 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 Planned Transport Identifiers element

Back to top

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

2.7.1 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

2.7.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, the system will return an error code (673: only future days can be changed for sub-paths in PA/PM).

2.7.3 Notifications

PCS will send a Receipt Confirmation only to the updater and an Object Info Message to all affected IMs (to affected applicants: under analysis) 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
  • 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

Back to top

2.8 Add sub-path PA Conference (IM)

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

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

2.8.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.8.3 Notifications

PCS will send a Receipt Confirmation only to the updater and an Object Info Message to all affected IMs (to affected applicants: under analysis) 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
  • 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

Back to top

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

2.9.1 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 Path Information 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.9.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, 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.9.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 IMs (to affected applicants: under analysis)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

Back to top

2.10 Set acceptance indicator to green as IM in PA conference

2.10.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, 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

2.10.2 Result

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

2.10.3 Notifications

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

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected IMs
  • TOR: 3
  • TOI: 2
  • Planned Transport Identifiers: TR ID, CR ID,  PA ID

Back to top

2.11 Set acceptance indicator to yellow as IM in PA conference

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

2.11.2 Result

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

2.11.3 Notifications

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

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected IMs
  • TOR: 3 – Modification
  • TOI: 23 – Harmonization in progress 
  • Planned Transport Identifiers: TR ID, CR ID, PA ID

Back to top

2.12 Set acceptance indicator to red as IM in PA conference

2.12.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, with the following content:

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

2.12.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.12.3 Notifications

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

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

Back to top

2.13 Set acceptance indicator to green as RA in PA offer

2.13.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 affected applicant
    • Recipient: 3178 (RNE)
  • TOR: 3 – Modification
  • TOI: 2 – Harmonization accepted
  • Planned Transport Identifiers: TR ID, CR ID

2.13.2 Result

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

2.13.3 Notifications

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

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected applicants
  • TOR: 3 – Modification
  • TOI: 2 – Harmonization accepted
  • Planned Transport Identifiers: TR ID, CR ID, PR ID

Back to top

2.14 Set acceptance indicator to red as RA in PA Offer

2.14.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, with the following content:

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

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

2.14.3 Notifications

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

  • Message header:
    • Sender: 3178 (RNE)
    • Recipient: company code of any affected applicants
  • TOR: 3 – Modification
  • TOI: 3 – Harmonization rejected 
  • Planned Transport Identifiers: TR ID, CR ID, PR ID

Back to top

3. Download sequence_diagram_for_pcs_communication_path_alteration_version_2.1

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_alteration_version_2.1-1DOWNLOAD
Back to top

© RailNetEurope. All Rights Reserved.