The principles of allocation infrastructure capacities on the European Rail Freight Corridors (RFC)

B) The MB takes a decision regarding the capacity to be republished after X-7.5. This decision depends on the “booking situation” at that moment. More precisely, at least the following three criteria must be fulfilled in the following order of importance): 1. There must be enough capacity for late requests, if applicable, and RC. 2. Take into account the demand for international paths for freight trains placed by other means than PCS. 3. Take into account the need for modification of the capacity offer due to possible changes in the planning of TCRs. Information on the way in which the non-requested PaPs are being handled is provided in the CID of each Corridor. 3.4.19 Draft over After receiving the pre-booking decision by the C-OSS, the IMs/ABs concerned will elaborate the flexible parts of the requests:  Feeder, outflow or intermediate sections  Pre-booked sections for which the published timetable is not available anymore due to external influences, e.g. temporary capacity restrictions  In case of modifications to the published timetable requested by the applicant  In case of an alternative offer that was rejected by the applicant or is not available In case IMs/ABs cannot create the draft offer due to specific wishes of the applicant not being feasible, the C-OSS has to reject the request. The C-OSSs shall be informed about the progress, especially regarding the parts of the requests that cannot be fulfilled, as well as conflicts and problems in harmonising the path offers. At the RNE draft timetable deadline (X-5) the C-OSS communicates the draft timetable offer for every handled request concerning pre-booked PaPs including feeder and/or outflow, tailor-made sections and tailor-made offers in case of conflicting requests to the applicant via PCS on behalf of the IM/AB concerned. Corridor Specificities The IMs/ABs can mark areas in which the flexibility will be available even after the final offer (in case the IMs/ABs create the actual timetable only shortly before operations) as ‘Flexible after allocation’. [To be checked by each IM/AB, whether this applies.] 3.4.20 Observations Applicants can place observations on the draft timetable offer in PCS one month from the date stated in 3.12, which are monitored by the C-OSS. The C-OSS can support the applicants regarding their observations. This procedure only concerns observations related to the original path request — whereas modifications to the original path requests are treated as described in 3.7.1 (without further involvement of the C-OSS). Network Statement - 2026 ANNEX 4.b Version: 15.0.0 Update: 15.12.2024 Pag: 14 / 21  Compania Naţională de Căi Ferate “CFR” S.A. România 3.4.21 Post-prelucrare Based on the above-mentioned observations the IMs/ABs have the opportunity to revise offers between X-4 and X-3.5. The updated offer is provided to the C-OSS, which – after a consistency check – submits the final offer to the applicant in PCS. 3.4.22 Final order At the final offer deadline (X-3.5), the C-OSS communicates the final timetable offer for every valid PaP request including feeder and/or outflow, tailor-made sections and tailor-made offers in case of conflicting requests to the applicants via PCS on behalf of the IM/AB concerned. If, for operational reasons, publication via national tools is still necessary (e.g. to produce documents for train drivers), the IMs/ABs have to ensure that there are no discrepancies between PCS and the national tool. Corridor Specificities The IMs/ABs can mark areas in which flexibility will be available even after the final offer (in case the IMs/ABs create the actual timetable only shortly before operations) as ‘Flexible after allocation’. [To be checked by each IM/AB, whether this applies.] Solicitanții implicați acceptă sau resping oferta finală în decurs de 5 zile calendaristice în SCT.  Acceptance > leads to allocation  Rejection > leads to withdrawal and closing of the request  No answer > The C-OSS will actively try to get an answer. In case there is no answer from the applicants, the C-OSS will end the process (no allocation). If not all applicants agree on the final offer, the request will be considered as unanswered. 3.5 Late path request phase Late path requests refer to capacity requests concerning the annual timetable sent to the C-OSS within the timeframe from X-7.5 until X-2. It is stated in the CID of each Corridor whether it offers the possibility to place late path requests or not. 3.5.1 Product Capacity for late path requests can be offered in the following ways: A) In the same way, as for PaPs, either specially constructed paths for late path requests or PaPs which were not used for the annual timetable. B) On the basis of capacity slots. Slots are displayed per corridor section and the standard running time is indicated. To order capacity for late path requests, corridor sections without any time indications are available in PCS. The applicant may indicate his individually required departure and/or arrival times, and feeder and outflow path(s), as well as construction starting point. The indications should respect the indicated standard running times. Capacity for late path request has to be requested via PCS either in the same way as for PaPs or by using capacity slots in PCS. If the Corridor offers the possibility to place late path requests, it is stated in the CID of that Corridor which of the above variants would be used. 3.5.2 Multiple corridor paths It is possible for capacity requests to cover more than one corridor if capacity is offered. See 3.4.4. Network Statement - 2026 ANNEX 4.b Version: 15.0.0 Update: 15.12.2024 Pag: 15 / 21  Compania Naţională de Căi Ferate “CFR” S.A. România 3.5.3 Late path on overlapping sections See 3.4.5 Description of common offers on overlapping sections can be found on a map in Annex 4C to the CID of each Corridor. 3.5.4 Handling of request The C-OSS receives and collects all path requests that are placed via PCS. 3.5.5 Leading tool for late path request Applicants sending late path requests to the C-OSS shall use PCS. Within the construction process, the national tool may show additional information to the applicant. The following matrix shows for each step of the process which tool is considered as the leading tool. Phase Application Withdrawal Offer (x-1) Acceptance Modification Cancellation (until la x- (x-7,5 până la (x-8 până la 0,75) x-2) x-2) National National Leading tool PCS PCS PCS PCS tool/PCS* tool/PCS* To be checked by each IM, whether requests for modification or cancellation via PCS are accepted. If applicable, the following sentence shall be added: Modifications/Cancellations have to be placed in the [IMs name/tool]. 3.5.6 Check of the applications The C-OSS checks all requests as described in 3.4.9. 3.5.7 Pre-booking The C-OSS coordinates the offer with the IMs/ABs concerned or other C-OSS if needed by following the rule of “first come – first served”. 3.5.8 Path elaboration During the path elaboration phase, the IMs/ABs concerned will prepare the Late Path offer under coordination of the C-OSS. 3.5.9 Late request offer All applicants involved shall accept, ask for adaptations or reject the late request offer within 5 calendar days in PCS. By triggering the ‘ask for adaptation’ function, applicants can place comments on the late request offer, which will be monitored by the C-OSS. This procedure only concerns comments related to the original path request – whereas modifications to the original path requests are treated as described in 3.7.1 (without further involvement of the C-OSS).  Acceptance > leads to allocation  Ask for adaptations > late offer can be returned to path elaboration with comments; IM/AB will make an alternative proposal; however, if no alternatives are possible, the applicant will have to prepare a new request  Rejection > leads to withdrawal and closing of the request  No answer > The C-OSS will actively try to get an answer. In case there is still no answer from the applicants, the C-OSS will end the process (no allocation) Network Statement - 2026 ANNEX 4.b Version: 15.0.0 Update: 15.12.2024 Pag: 16 / 21  Compania Naţională de Căi Ferate “CFR” S.A. România If not all applicants agree on the final offer, the request will be considered as unanswered. 3.6 Ad-hoc path request phase 3.6.1 Reserve capacity (RC) During the ad-hoc path request phase, the C-OSS offers RC based on PaPs or capacity slots to allow for a quick and optimal answer to ad-hoc path requests: A. RC based on PaPs will be a collection of several sections along the Corridor, either of non-requested PaPs and/or PaPs constructed out of remaining capacity by the IMs/ABs after the allocation of overall capacity for the annual timetable as well as in the late path request phase. B. In case RC is offered on the basis of capacity slots, slots are displayed per corridor section and the standard running time is indicated. The involved IMs/ABs jointly determine the amount of RC for the next timetable year between X-3 and X-2. The determined slots may not be decreased by the IMs/ABs during the last three months before real time. To order reserve capacity slots, corridor sections without any time indication are available in PCS. The applicant may indicate his individually required departure and/or arrival times, feeder and outflow path(s) as well as construction starting point. The indications should respect the indicated standard running times as far as possible. It is stated in the CID of each Corridor through which variant that Corridor offers RC. In case a Corridor offers the RC through variant B, the relevant time frames are also specified in the CID of that Corridor. RC is published by the C-OSS at X-2 in PCS. The IMs can modify or withdraw RC for a certain period in case of unavailability of capacity due to force majeure. Applicants can book RC via the C-OSS until 30 days before the running day. To make ad-hoc requests less than 30 days before the running day, they have to contact the IMs/ABs directly. 3.6.2 Multiple corridor path It is possible for capacity requests to cover more than one corridor. See 3.4.4. 3.6.3 Reserve capacity on overlapping sections See 3.4.5. Description of common offers on overlapping sections is to be displayed on a map in Annex 4C to the CID of each Corridor. 3.6.4 Feeder, outflow and tailor-made path See 3.4.6. For RC the same concept applies as for PaPs in the annual timetable. 3.6.5 Handling of request The C-OSS receives and collects all path requests for RC placed via PCS until 30 days before the running day. If requested, the C-OSS can support applicants in creating the dossiers to prevent inconsistencies and guide the applicants’ expectations. The IMs/ABs may support the applicants by providing a technical check of the requests. Network Statement - 2026 ANNEX 4.b Version: 15.0.0 Update: 15.12.2024 Pag: 17 / 21  Compania Naţională de Căi Ferate “CFR” S.A. România 3.6.6 Landing tool for ad-hoc requests Applicants sending requests for RC to the C-OSS shall use PCS. Within the construction process, the national tool may show additional information to the applicant. The following matrix shows for each step of the process which tool is considered as the leading tool. Phase Application Withdrawal Offer calendar Answer within 5 Modification Cancellation and Allocation ( 10 days days after offer) (x-2 until before train x+12) runs) National National Leading toll PCS PCS PCS PCS tools/PCS* tools/PCS* To be checked by each IM, whether requests for modification or cancellation via PCS are accepted. If applicable, the following sentence shall be added: Modifications/Cancellations have to be placed in the [IMs name/tool]. 3.6.7 Check of the applications The C-OSS checks all requests as described in 3.4.9. 3.6.8 Pre-booking The C-OSS applies the ‘first come – first served’ rule. 3.6.9 Path elaboration During the path elaboration phase, the IMs/ABs concerned will prepare the offer under coordination of the C- OSS. 3.6.10 Ad-hoc request offer Applicants shall receive the ad-hoc offer no later than 10 calendar days before the train run. All applicants involved shall accept, ask for adaptations or reject the ad-hoc offer within 5 calendar days in PCS. By triggering the ‘ask for adaptation’ function, applicants can place comments on the ad-hoc request offer, which will be monitored by the C-OSS. This procedure only concerns comments related to the original path request – whereas modifications to the original path requests are tre