Table of contents
- Version History
- Use cases of the feasibility Study process
- Download sequence_diagram_for_fs_2021-07-01_0.pdf
1. Version History
| Version | Release date | Author | Highlights |
| 2 | 27.06.2022 | Nicolas Jasinski | – Use cases description and sequence diagram transferred to this new CMS location |
2. Use cases of the Feasibility Study process
2.1 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.
2.1.1 Sent information
The leading applicant who would like to submit a 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
2.1.2 Result
In case of a successful request, the dossier enters to Harmonization Conference phase.
2.1.3 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
2.2 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.
2.2.1 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
2.2.2 Result
In case of a successful request, the dossier enters to Harmonization phase.
2.2.3 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
2.3 Submit FS Request
After the Harmonization Conference, the leading applicant has the chance to submit the feasibility study request.
2.3.1 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
2.3.2 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.
2.3.3 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
All involved agencies will get Path Request Message(s) with the following content.
- Message header:
- Sender: 3178 (RNE)
- Recipient: company code of the involved agencies
- 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)
2.4 Withdraw FS request
2.4.1 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
2.4.2 Result
In case of a successful request, the dossier returns to the Harmonization phase.
2.4.3 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
2.5 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.
2.5.1 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
2.5.2 Result
In case of a successful request, the dossier enters to Feasibility Study Elaboration phase.
2.5.3 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
2.6 Release FS Elaboration Conference
During the FS process, the IMs can share their interim result with the applicants in the Feasibility Elaboration Conference phase.
2.6.1 Sent information
The leading IM who would like to release the dossier to the 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
2.6.2 Result
In case of a successful request, the dossier enters to the feasibility elaboration conference phase.
2.6.3 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 agencies with the following content.
- Message header:
- Sender: 3178 (RNE)
- Recipient: company code of the involved agencies
- TOR: 1 – study
- TOI: 09 – draft offer
- Identifier:
- Planned Transport Identifiers: CR ID, TR ID, PR ID, PA ID
2.7 Return to FS Elaboration
After the Feasibility Elaboration Conference, the dossier returns to FS Elaboration again.
2.7.1 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
2.7.2 Result
In case of a successful request, the dossier enters to Feasibility Study Elaboration phase.
2.7.3 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
2.8 Submit FS Result
2.8.1 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
2.8.2 Result
In case of a successful request, the dossier enters to Feasibility Elaboration Conference phase.
2.8.3 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 agencies with the following content.
- Message header:
- Sender: 3178 (RNE)
- Recipient: company code of the involved agencies
- TOR: 1 – study
- TOI: 16 – final offer
- Identifier:
- Planned Transport Identifiers: CR ID, TR ID, PR ID, PA ID
2.9 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.
2.9.1 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
2.9.2 Result
In case of a successful request, the dossier enters to Feasibility Study Elaboration phase.
2.9.3 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
2.10 Acknowledge FS Result
The leading applicant can acknowledge the FS Result so that the dossier can return to the Harmonization phase.
2.10.1 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
2.10.2 Result
In case of a successful request, the dossier enters to Harmonization phase.
2.10.3 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
2.11 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.
2.11.1 Sent information
The involved agency who would like to set an 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.
2.11.2 Notifications
PCS will send a Receipt Confirmation message to the updater and a Path Coordination Message without Train and Path Information with the following content:
- Message header:
- Sender: 3178 (RNE)
- Recipient: company code of any involved agency
- TOR: 1
- TOI: according to the TOI mapping
- Planned Transport Identifiers: TR ID, CR ID, PR or PA ID
3. Download sequence_diagram_for_fs_2021-07-01_0.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
