1.

L-Anness I għandu jiġi emendat kif ġej: (a) It-Taqsima 4.2.1 għandha tinbidel b’li ġej: “4.2.1. Exchange of timetable data This basic parameter lays down how the railway undertaking shall perform the exchange of timetable data. This basic parameter shall ensure that timetables comprising the data elements defined below shall be made available. This basic parameter shall further ensure that each railway undertaking shall provide accurate and up-to-date timetable data. The provisions of this basic parameter shall apply to the passenger services of the railway undertaking. This basic parameter shall have the following process:” (b) It-Taqsima 4.2.2 għandha tinbidel b’li ġej: “4.2.2. Exchange of tariff data This basic parameter lays down how the railway undertaking shall perform the exchange of tariff data. This basic parameter shall ensure that tariff data in the format defined below shall be made available. The provisions of this basic parameter shall apply in respect of all passenger tariffs of the railway undertaking for domestic, international and foreign sales. This basic parameter shall have following process:” (c) It-Taqsima 4.2.2.1 għandha tinbidel b’li ġej: “4.2.2.1. The railway undertaking makes available its own tariffs to other railway undertakings, authorised public bodies and third parties Without prejudice to passenger rights and in accordance with distribution agreements, each railway undertaking shall make available its tariffs (including fare tables) by guaranteeing access to railway undertakings to which it grants authorisation to sell, third parties to which it grants authorisation to sell, and to authorised public bodies. The railway undertaking shall ensure that the tariff data are accurate and up-to-date. Where a railway undertaking operates a transport service for which it is one of the joint carriers, the railway undertaking shall ensure, together with all the other joint carriers, that the tariff data are accurate and up-to-date. The main content of tariff data intended for international or foreign sales shall be as defined in Annex IV. Tariff data intended for international or foreign sales shall be made available at least as far in advance as provided for in Annex IV. The above process and the information used for it shall be compliant for tariff data intended for international or foreign sales with the technical document(s): — B.1 (see Annex III), — B.2 (see Annex III), — B.3 (see Annex III). The above process and the information used for it in respect of tariff data intended for domestic sales shall comply with the technical documents to be developed by the Agency (see Annex II).” (d) Fit-taqsima 4.2.6 għandha titħassar is-sentenza li ġejja: “The provision of this basic parameter regarding electronic request/confirmation shall be applied if there is an agreement between the requesting and the addressed parties.” (e) Fit-Taqsima 4.2.6.1 is-sentenza: “This website shall comply with web content accessibility guidelines which take into account the needs of people with auditory and/or visual impairment.” għandha tinbidel b’dan li ġej: “This website shall be accessible to persons with disabilities”. (f) It-Taqsima 4.2.6.2 għandha tinbidel b’li ġej: “4.2.6.2. If the railway undertaking or ticket vendor uses IT communication for the purposes of sending an availability/reservation request for PRM assistance, such request must comply with the relevant provisions The requesting distribution system shall send to the system requests for the relevant train availability/reservation in respect of the specified type of assistance. The main types of requests shall be: — Availability request, — Reservation request, — Partial cancellation request, — Full cancellation request. This process shall be performed following a request from a customer transmitted to the system of the railway undertaking or ticket vendor. The data elements and the information content of the message used to meet the obligations shall comply: — either with elements defined in technical document B.10 (see Annex III), in which case all addressed systems must be able to understand the request and to respond, — or with otherwise defined standards, in which case the addressed system must be able to understand the request and to reply.” (g) It-Taqsima 7.2.3 tal-Anness I għandha tinbidel bit-test li ġej: “7.2.3. Deliverables The phase 1 deliverables include the following: (1) Application guides describing functional, technical and performance specifications, the associated data, the interface requirements, the security and the quality requirements. (2) The outline of the global architecture of the system. (3) The master plan including: — The identification of the activities necessary to achieve the implementation of the system. — A migration plan which includes a set of phases that is conducive to intermediate and verifiable tangible results, from the current framework of stakeholders’ information and communication systems to the system itself. — A detailed milestone plan. — A risk assessment of the crucial phases of the master plan. — An assessment of the total lifecycle costs (LCC) associated with the deployment and operation of the system, together with a subsequent investment plan and the relevant cost-benefit analysis. (4) The governance deliverable which includes the identification of the appropriate governance structures, methods and procedures to support the development and validation of the system and subsequently its deployment and its field operation and management throughout its lifetime (including dispute management between the parties involved under the provisions of this TSI).” (h) Il-kapitolu 7.3 tal-Anness 1 għandu jinbidel bit-test li ġej: “7.3. Phase 2 — Development All actors concerned shall develop the system following the provisions of the phase 1 deliverables as follows: (a) Project governance In order to guarantee the appropriate development of the system the governance structure as described in technical document B.61 (see Annex V) shall be progressively implemented by the actors. Roles and responsibilities of all actors shall evolve with the implementation of the new governance structure as described in technical document B.61. The steering committee set up under phase 1 will be maintained in phase 2 until the governance structure described in technical document B.61 is fully operational. Its rules of procedure will be updated also to take into account its new role which is to monitor progress of implementation of the new governance structure, the architecture developed in phase 1 and the development of the system by individual companies taking particularly into account the adherence to the application guides published and maintained by ERA. Before recognising the end of phase 2 the Steering Committee will issue an opinion on the legal status and ownership of the Application Guides. Full compliance with technical document B.61 will be considered as a presumption of conformity of the new governance structure with the requirements of this Regulation. However due to the nature of the document and the continuous need for alignment of the governance structure to the real needs of the market, any deviation from its provisions should be immediately reported to the Steering Committee which will assess the deviation and decide if the technical document and/or its legal status needs to evolve at the end of phase 2. (b) Master Plan In order to guarantee the appropriate development of the system all actors concerned shall cooperate and implement the system in full adherence to the master plan as specified in ERA technical document B.62 (see Annex V). (c) Development of the system All actors concerned shall cooperate and develop the retail architecture of the system according to the architecture provisions as described in ERA technical document B.60 (see Annex V). All concerned actors shall cooperate and develop the system and its parts as to be as much as possible compliant with the Application Guides as described in the technical documents: B.50 (see Annex III) B.51 (see Annex III) B.52 (see Annex III) B.53 (see Annex III) B.54 (see Annex III) B.55 (see Annex III) B.56 (see Annex III). Full compliance with these technical documents will be considered as a presumption of conformity of the system with the technical requirements of this Regulation. Any deviation from the Application Guides shall be reported to the Steering Committee which will assess it in the context of its role described under item (a). As the Application Guides B.50 to B.56 referred to in Annex III are not mandatory specifications, they are not subject to the Change Control Management.”