Stefan Jugelt (ERA) TAP TSI CCM – baseline version th RISC Committee – January 2014

Topics of processed change requests The CRs handled in the TAP TSI CCM can be grouped in the following topics: 1.Corrections of errors detected in TAP TSI phase one 2.Enhancements of code lists 3.Correction of errors for the technical document B.10 4.Alignment of the technical document B.6 with new business requirements 5.Other CRs 6.Changes of RU/IM communication January th RISC CommitteeN° 2

Corrections of errors detected in TAP TSI phase one January th RISC CommitteeN° 3 “Corrections of errors”-CRs were driven by the TAP TSI phase one Rail sector has discovered during this phase some errors in the TAP TSI technical documents resulting from the history of these documents Furthermore the rail sector has discovered ambiguities in the text of the ERA technical documents, the clarity of the text of the technical documents has to be improved  Both questions were solved through CRs discussed in the CCM working party

Enhancements of code lists and TD B.10 January th RISC CommitteeN° 4 TAP TSI code lists : CRs covering the changes of code lists used in the TAP TSI technical documents changes were triggered by new business requirements (e.g. new accommodation classes, new brand names). Technical document B.10: code lists were not aligned with the usage in the rail sector alignments of the message catalogue with the TAP TSI core text and the passenger rights regulation the mandatory issuing of a confirmation number for PRM reservation requests including ticket vendors as requesting party

Alignment of the technical document B.6 with new business requirements January th RISC CommitteeN° 1 TAP TSI TD B.6 – “Electronic seat/berth reservation and electronic production of transport documents (RCT standard)” - was changed because of new business requirements from the rail sector to: improve the readability group the used ticket layouts according to their usage as transport tickets or other transport documents (e.g. voucher)

Changes of RU/IM communication January th RISC CommitteeN° 6 CRs mainly driven by TAF requirements The most important TAP TSI related CRs are: remove the data content from the technical document B.30 and use a single TAF/TAP TSI data catalogue for RU/IM- communication New messages “ChangeOfTrackMessage” “TrainJourneyModificationMessage” to support the information exchange between the infrastructure manager/railway undertaking and the station manager Introduction of optional elements for commercial data (e.g. brand name, train type, facility descriptions) mainly driven by the obligation for IMs to publish timetable information for customers at stations

TAP CCM Economic Evaluation - Conclusions January th RISC Committee N° 7 Overall, the CRs put forward for the baseline release version 1.2 in the TAP TSI CCM WP are likely to result in net-benefits for the sector. As such the CRs should support applicability and acceptance as well as improved alignment between the TAF TSI and TAP TSI while not leading to any significant costs. The rest of the CRs above set out are related to corrections of errors. Each of these CRs does not involve an extension of the TAP TSI system only an improvement of its relevance and applicability to users. Therefore, these CRs should result in net-benefits for the sector without leading to any additional costs. Thus, their inclusion in the baseline 1.2 would not require a detailed cost-benefit analysis

Lille 11/09/2013 TAF TSI CCM Board N° 8 Questions ?

11/09/2013N° 9 Thank you for your kind attention: ERA Telematics Team Project officers for Telematics at Applications European Railway Agency th RISC Committee