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

re late path offer is applicable) in PCS o Publish the RC at X-2 in PCS - Allocation phase: annual timetable (annual timetable process) o Collect, check and review all requests for PaPs including error fixing when possible o Create a register of the applications and keep it up-to-date (see 2.4.1) o Manage the resolution of conflicting requests through consultation where applicable o In case of conflicting requests, take a decision on the basis of priority rules adopted by the Executive Board along the Corridor (see 3.1 Framework for Capacity Allocation (FCA) o Propose alternative PaPs, if available, to the applicants whose applications have a lower priority value (K value) due to a conflict between several path requests o Transmit path requests that cannot be treated to the IM/AB concerned, in order for them to elaborate tailor-made offers o Pre-book capacity and inform applicants about the results at X-7.5 o Allocate capacity (PaPs) in conformity with the relevant international timetabling deadlines (see 3.12) and processes as defined by RailNetEurope (RNE) and according to the allocation rules described in the FCA o Monitor the construction of feeder and/or outflow paths by sending these requests to the IMs/ABs concerned and obtain their responses/offers. In case of nonconsistent offers (e.g. non-harmonised border times), ask for correction o Send the responses/offers (draft offer and final offer including feeder and outflow) to the applicants on behalf of the IMs/ABs concerned o Keep the PaP catalogue updated - Allocation phase: late path requests (annual timetable process) o Collect, check and review all requests for the late path request phase including error fixing when possible o Allocate capacity for the late path request phase where applicable o Monitor the construction of feeder and/or outflow paths by sending these requests to the IMs/ABs concerned and obtain their responses/offers. In case of nonconsistent offers (e.g. non-harmonised border times), ask for correction o Send the responses/offers to the applicants on behalf of the IMs/ABs concerned o Keep the catalogue concerned updated - Allocation phase: ad-hoc requests (RC) (running timetable process) o Collect, check and review all requests for RC including error fixing when possible o Create a register of the applications and keep it up-to-date o Allocate capacity for RC o Monitor the construction of feeder and/or outflow paths by sending these requests to the IMs/ABs concerned and obtain their responses/offers. In case of nonconsistent offers (e.g. non-harmonised border times), ask for correction o Send the responses/offers to the applicants on behalf of the IMs/ABs concerned - Keep the RC catalogue updated Network Statement - 2026 ANNEX 4.b Version: 15.0.0 Update: 15.12.2024 Pag: 5 / 21  Compania Naţională de Căi Ferate “CFR” S.A. România 2.4.1 Path register The C-OSS manages and keeps a path register up-to-date for all incoming requests, containing the dates of the requests, the names of the applicants, details of the documentation supplied and of incidents that have occurred. A path register shall be made freely available to all applicants concerned without disclosing the identity of other applicants, unless the applicants concerned have agreed to such a disclosure. The contents of the register will only be communicated to them on request. 2.5 Tool PCS is the single tool for publishing the binding PaP and RC offer of the Corridor and for placing and managing international path requests on the Corridor. Applications for PaPs/RC can only be made via PCS to the involved C-OSS. If the application is made directly to the IMs/ABs concerned, they inform the applicant that they have to place a correct PaP/RC request in PCS via the C-OSS according to the applicable deadlines. PaP/RC capacity requested only through national tools will not be allocated. In other words, PaP/RC applications cannot be placed through any other tool than PCS. 3. CAPACITY ALLOCATION The decision on the allocation of PaPs and RC on the Corridor is taken by the C-OSS on behalf of the IMs/ABs concerned. As regards feeder and/or outflow paths, the allocation decision is made by the relevant IMs/ABs and communicated to the applicant by the C-OSS. Consistent path construction containing the feeder and/or outflow sections and the corridor-related path section has to be ensured. All necessary contractual relations regarding network access have to be dealt with bilaterally between the applicant and each individual IM/AB. 3.1 Framework for capacity allocation The decision on the allocation of PaPs and RC on the Corridor is taken by the C-OSS on behalf of the IMs/ABs concerned. As regards feeder and/or outflow paths, the allocation decision is made by the relevant IMs/ABs and communicated to the applicant by the C-OSS. Consistent path construction containing the feeder and/or outflow sections and the corridor-related path section has to be ensured. All necessary contractual relations regarding network access have to be dealt with bilaterally between the applicant and each individual IM/AB. 3.2 Applicants Applicants shall accept the general terms and conditions of the Corridor in PCS before placing their requests. Without accepting the general terms and conditions, the applicant will not be able to send the request. In case a request is placed by several applicants, every applicant requesting PaP sections has to accept the general terms and conditions for each corridor on which the applicant is requesting a PaP section. In case one of the applicants only requests a feeder or outflow section, the acceptance of the general terms and conditions is not needed. The acceptance shall be done only once per applicant and per corridor and is valid for one timetable period. With the acceptance the applicant declares that it:  has read, understood and accepted the Corridor’s CID and, in particular, the Section 4 of it,  complies with all conditions set by applicable legislation and by the IMs/ABs involved in the paths it has requested, including all administrative and financial requirements,  shall provide all data required for the path requests, Network Statement - 2026 ANNEX 4.b Version: 15.0.0 Update: 15.12.2024 Pag: 6 / 21  Compania Naţională de Căi Ferate “CFR” S.A. România  accepts the provisions of the national Network Statements applicable to the path(s) requested. In case of a non-RU applicant, it shall appoint the RU that will be responsible for train operation and inform the C-OSS and IMs/ABs about this RU as early as possible, but at the latest 30 days before the running day. If the appointment is not provided by this date, the PaP/RC is considered as cancelled, and national rules for path cancellation are applicable. In case the applicant is a non-RU applicant, and applies for feeder / outflow paths, the national rules for nomination of the executing RU will be applied. 3.3 Requirements for requesting capacity The Corridor applies the international timetabling deadlines defined by RNE for placing path requests as well as for allocating paths (for the Corridor calendar, see http://www.rne.eu/salestimetabling/timetabling- calender/ or Chapter 3.12). All applications have to be submitted via PCS, which is the single tool for requesting and managing capacity on all corridors. The C-OSS is not entitled to create PCS dossiers on behalf of the applicant. If requested, the C-OSS can support applicants in creating the dossiers in order to prevent inconsistencies and guide the applicants’ expectations (maximum 1 week prior to the request deadline). The IMs/ABs may support applicants by providing a technical check of the requests. A request for international freight capacity via the C-OSS has to fulfil the following requirements:  it must be submitted to a C-OSS by using PCS, including at least one PaP/RC section. Details are explained in the PCS User Manual http://cms.rne.eu/pcs/pcsdocumentation/pcs-basics),  it must cross at least one border on a corridor,  it must comprise a train run from origin to destination, including PaP/RC sections on one or more corridors as well as, where applicable, feeder and/or outflow paths, on all of its running days. In certain cases, which are due to technical limitations of PCS, a request may have to be submitted in the form of more than one dossier. These specific cases are the following: o Different origin and/or destination depending on running day (But using identical PaP/RC capacity for at least one of the IMs for which capacity was requested). o Transshipment from one train onto different trains (or vice versa) because of infrastructure restrictions. o The IM/AB specifically asks the applicant to split the request into two or more dossiers. To be able for the C-OSS to identify such dossiers as one request, and to allow a correct calculation of the priority value (K value) in case a request has to be submitted in more than one dossier, the applicant should indicate the link among these dossiers in PCS. Furthermore, the applicant should mention the reason for using more than one dossier in the comment field.  the technical parameters of the path request have to be within the range of the parameters – as originally published – of the requested PaP sections (exceptions are possible if allowed by the IM/AB concerned, e.g. when the timetable of the PaP can be respected)  as regards sections with flexible times, the applicant may adjust/insert times, stops and parameters according to its individual needs within the given range. In case of some Corridors further specific requirements for additional cases may be applied. For the description of such requirements refer to the CIDs of individual Corridors. 3.4 Annual Timetable phase 3.4.1 PaPs PaPs are a joint offer of coordinated cross-border paths for the annual timetable produced by IMs/ABs involved in the Corridor. The C-OSS acts as a single point of contact for the publication and allocation of PaPs. Network Statement - 2026 ANNEX 4.b Version: 15.0.0 Update: 15.12.2024 Pag: 7 / 21  Compania Naţională de Căi Ferate “CFR” S.A. România PaPs constitute an off-the-shelf capacity product for international rail freight services. In order to meet the applicants' need for flexibility and the market demand on the Corridor, PaPs are split up in several sections, instead of being supplied as entire PaPs, as for example from ‘Start Point(s)’ to ‘End Point(s)’. Therefore, the offer might also include some purely national PaP sections – to be requested from the C-OSS for freight trains crossing at least one border on a corridor in the context of international path applications. A catalogue of PaPs is published by the C-OSS in preparation of each timetable period. It is published in PCS. PaPs are published in PCS at X-11. Between X-11 and X-10.5 the C-OSS is allowed to perform, in PCS, all needed corrections of errors regarding the published PaPs detected by any of the involved parties. In this phase, the published PaPs have ‘read only’ status for applicants, who may also provide input to the C-OSS regarding the correction of errors. 3.4.2 Schematic Corridor Map A schematic map of each Corridor can be found as an annex to its CID. 3.4.3 Features of PaPs A PaP timetable is published containing one of the following features:  Sections with fixed times (data cannot be modified in the path request by an applicant). o Capacity with fixed origin, intermediate and destination times within one IM/AB. o Intermediate Points and Operational Points with fixed times. Requests for changes to the published PaP have to be examined by the IMs/ABs concerned and can only be accepted if they are feasible and if this does not change the calculation of the priority rule in case of conflicting requests at X-8.  Sections with flexible times (data may be modified in the path request by an applicant according to individual needs, but without exceeding the given range of standard running times, stopping times and train parameters. Where applicable, the maximum number of stops and total stopping time per section have to be respected). o Applicants are free to include their own requirements in their PaP request within the parameters mentioned in the PaP catalogue. o Where applicable, the indication of standard journey times for each corridor section has to be respected. o Optional: Intermediate Points without fixed times. Other points on the Corridor may be requested. o Optional: Operational Points without fixed times. Requests for changes outside of the above-mentioned flexibility have to be examined by the IMs/ABs concerned if they accept the requests. The changes can only be accepted if they are feasible. The C-OSS promotes the PaPs by presenting them to existing and potential applicants. For the description of further specificities refer to the CIDs of individual Corridors. In case of some Corridors the capacity bandwidth approach may be applied. For the description of the characteristics of specific capacity bandwidth approaches refer to the CIDs of individual Corridors. 3.4.4 Multiple corridor path It is possible for capacity requests to cover more than one corridor. A PaP offer harmonised by different corridors may be published and indicated as such. The applicant may request PaP sections on different corridors within one request. Each C-OSS remains responsible for allocating its own PaP sections, but the applicant may address its questions to only one of the involved COSSs, who will coordinate with the other concerned C-OSSs whenever needed. Network Statement - 2026 ANNEX 4.b Version: 15.0.0 Update: 15.12.2024 Pag: 8 / 21  Compania Naţională de Căi Ferate “CFR” S.A. România Multiple corridor paths on the Corridor are to be displayed on a map in Annex 4C to the CID of each Corridor. 3.4.5 PaPs on overlapping sections The layout of the corridor lines leads to situations where some corridor lines overlap with others. The aim of the corridors, in this case, is to prepare the best possible offer, taking into account the different traffic flows and to show the possible solutions to link the overlapping sections concerned with the rest of the corridors in question. In case of overlapping sections, corridors may develop a common offer, visible via all corridors concerned. These involved corridors will decide which C-OSS is responsible for the final allocation decision on the published capacity. In case of conflict, the responsible C-OSS will deal w