WEBVTT 00:00.000 --> 00:12.680 Good afternoon, everybody can yam yam yam well, I guess, yeah, that's cool. 00:12.680 --> 00:17.440 It's a bit unfortunate that the commission is making now presentation after hearing 00:17.440 --> 00:23.440 a call for you from, so I'm not here to fund any project, just to make everybody comfortable. 00:23.440 --> 00:28.400 I'm saying, I'm walking at the open commission in a unique dealing with technical matters 00:28.400 --> 00:34.200 specifically for RAV, and that's my pleasure actually to tell you a story about mobility 00:34.200 --> 00:39.600 data architecture and whole, we need disruptions there too, as we could hear from the study 00:39.600 --> 00:42.600 of the previous colleagues. 00:42.600 --> 00:47.240 There is actually a vision of what we want to do, what we would like to do from a political 00:47.240 --> 00:55.400 perspective with data, relevant for ticketing, John Eplaner and so on. 00:55.400 --> 01:03.760 This is finding in one single place, digital tickets for RAV, John E and Volving, 01:03.760 --> 01:12.520 multi-operators, so from Lisbon to Tallinn in one single ticket in one single place. 01:12.520 --> 01:18.720 It's a vision, so from the vision to the technical implementations there is obviously a gap 01:18.720 --> 01:25.080 and this is the story I would like to tell you today in a bit more detail. 01:25.080 --> 01:31.640 So to do that, working for the commission, this being the good start or not, the starting 01:31.640 --> 01:37.840 point for us is to look at legislation, right, so just a little snapshot on what else 01:37.840 --> 01:40.040 the legislation at stake here. 01:40.040 --> 01:47.400 First, I would like you to forget for some, the market pillar, which does not exist yet. 01:47.400 --> 01:52.680 So we have the technical pillar because obviously there is a common understanding that 01:52.680 --> 02:00.920 every body in the market is have a good intention to serve citizens in the best way possible 02:00.920 --> 02:07.080 or passengers that's generally speaking the case, but in a competitive market, of course, 02:07.080 --> 02:11.400 at a certain point you need to put some market rules on the table, so that everybody 02:11.400 --> 02:14.560 behave in the most appropriate way in an early quarter term. 02:14.560 --> 02:18.440 So that the market pillar does not exist yet. 02:18.520 --> 02:24.040 The first part is market rules related to platforms and other parts is market rule related 02:24.040 --> 02:25.840 to hardware operators. 02:25.840 --> 02:30.840 When I say platforms, this is platform independently of the type of transport mode. 02:30.840 --> 02:34.680 So let's put aside for a moment, there will be future discussion on that. 02:34.680 --> 02:40.280 Would like to give you today a focus on the technical pillar, without forget things that, 02:40.280 --> 02:45.360 of course, when we are on this transport, there is also a social pillar. 02:45.360 --> 02:52.080 We need also rights to enjoy when taking transport and this is also addressed by the regulation. 02:52.080 --> 02:57.680 So let's focus today on this technical pillar, there is two aspects out of it, one which 02:57.680 --> 03:03.440 is searching horizontal principle for all mode of transport and one specifically, this is the 03:03.440 --> 03:12.560 one we came to talk to you about, about rail specification for interoperability in relation 03:12.560 --> 03:15.080 to data, of course. 03:15.080 --> 03:22.080 So for that, there is the reflection, okay, what is the technical enable to make this vision 03:22.080 --> 03:23.480 happen? 03:23.480 --> 03:28.800 And basically there was three words that we could summarize it. 03:28.800 --> 03:36.280 The first one is we need data, we need data which is interoperable, but we also need data 03:36.280 --> 03:40.440 which is available because that's good to have rules for data to be interoperable, but 03:40.440 --> 03:47.240 if it is a nobody, makes all that data available, does not exist, I mean that does not work. 03:47.240 --> 03:54.240 So what is interoperable, what we have defined it, so data which is serialized with a harmonized 03:54.240 --> 03:58.200 ontology, so if everybody speaks the same vocabulary or at least there is compatibility 03:58.200 --> 04:03.240 between the different way to express things digitally in a structured manner, and this 04:03.240 --> 04:10.240 data is available, or if you are common or federated systems and then we need data space. 04:10.240 --> 04:16.480 And this is all, this is all on those principles that the regulation is built to make that 04:16.480 --> 04:20.920 data available, and we look at what is the data at stake here. 04:20.920 --> 04:29.120 The first piece of this technical pillar is the so-called MMTIS regulation, European Union 04:29.120 --> 04:37.960 wide multimodal travel information services, MMTIS, 2017 regulation almost a decade now, 04:37.960 --> 04:40.120 is there any progress in terms of implementation? 04:40.120 --> 04:44.800 I will give you some words at the very end of this presentation on this, and this is where 04:44.800 --> 04:49.840 your community can actually play, and big role, and this is why it was very important for 04:49.840 --> 04:55.800 me personally to be there today to have some disruption also from the open community. 04:55.800 --> 05:01.600 So this is about travel and traffic data, this is about establishing a single point of 05:01.600 --> 05:08.040 success for data users, you are the data users among us as, and whole this single point 05:08.040 --> 05:11.680 of success is created by establishing national access points. 05:11.680 --> 05:17.440 So each member state has, I will not say, east too, because now these are established, 05:17.440 --> 05:23.160 this is a data is inside of it, another story, but national access point must be and 05:23.160 --> 05:27.560 I've been set up by member state. 05:27.560 --> 05:32.720 Now on rail, and why I'm here today is because actually this regulation is so recent 05:32.720 --> 05:38.880 that I invite you to follow DGMove on, so DGMove is a director of a general for transport 05:38.880 --> 05:43.200 as the European Commission on social media to be aware of the publication of the text on 05:43.200 --> 05:51.600 the tense of February, so that you will be able to read actually its content about which 05:51.600 --> 05:55.720 I'm going to give you an overview now. 05:55.720 --> 05:59.840 So what this regulation is about, and here I will talk only about what is interesting 05:59.840 --> 06:06.440 for the topic of this session and this devroom, this is not only about this, but a part 06:06.440 --> 06:09.880 of what's regulation is about the results aspect. 06:09.880 --> 06:18.760 So I mentioned there is an issue about availability of data, so let's say, the single 06:18.760 --> 06:27.000 place for that data to be available exist, but are not yet really populated or the regulation 06:27.000 --> 06:36.120 is not really applied, I would say, I think I'm not recorded or maybe I am, I don't know. 06:36.120 --> 06:42.760 So it's not only about mandating things to be done or requiring things to be done by 06:42.760 --> 06:48.640 law, it's of course also about disseminating these regulations, this is why I'm also 06:48.640 --> 06:54.960 here today, this is about supporting financial easy implementation of the regulation and also 06:54.960 --> 06:59.720 enforcing it, and this is of course the last step, the last result step, but before this 06:59.720 --> 07:05.880 enforcement step, I also believe there is kind of disruption attitude that got come to 07:05.880 --> 07:13.640 actually put to the light, that there is things which are not functioning well, public 07:13.640 --> 07:18.560 and free of charge that are made available or legally required to be made available by 07:18.560 --> 07:25.960 the operators, this is about, this is about reference data, this is about timetable, this 07:25.960 --> 07:31.360 is about connection time, connection time is the time which only did between two different 07:31.360 --> 07:35.960 trains to be connected so that you can actually in the future enjoy passenger rights, when 07:35.960 --> 07:40.640 also taking two different trains from two different operators, this is about condition of 07:40.640 --> 07:44.960 carriage, so what are the condition in the different transport to transport your bike, to 07:44.960 --> 07:51.640 transport your luggage, your plan and so on and so forth, this is about accessibility, in 07:51.640 --> 07:59.400 the sense of a person with reduced mobility, both for trains and stations, this is about 07:59.400 --> 08:04.480 real time and forecast information about where the train are and where the train will be, 08:04.480 --> 08:10.480 this is about the composition of the train, this is about also the historical record of all 08:10.480 --> 08:15.920 this, to make sure that when something goes wrong, it's not only only your on-word against 08:15.920 --> 08:21.920 the word, but there is also a historical record, all this publicly and free of charge available 08:21.920 --> 08:27.800 via national access point established by member states, based on European standards 08:27.880 --> 08:37.360 and common profiles via common IPI as well for data consumption and based on standard open licenses. 08:37.360 --> 08:43.120 In addition to that, this is a battle we have lost, it's a service, it will be subject 08:43.120 --> 08:48.480 to contractual provision, so to make tariff available, not publicly available, not free 08:48.480 --> 08:53.960 of charge, but subject to contractual provision, the justification behind that is that tariff 08:54.040 --> 09:00.200 are to be used for commercial purposes to actually sell those tickets, not only for passenger 09:00.200 --> 09:05.560 information, therefore the conclusion of the political discussion was that it's justified, 09:05.560 --> 09:10.760 that tariff are only available, subject to contractual provision and not publicly and free 09:10.760 --> 09:17.400 of charge, we could debate it outside of this room, but this is the outcome of the political 09:17.480 --> 09:25.160 conclusion, so my last word for today, before I hand over to my colleague Stefan Fugel 09:25.160 --> 09:30.440 for deep diving to a technical aspect from the European Union Agency for Railways, is 09:30.440 --> 09:37.560 go search, find the data and reuse it, it is not available, even though legally required, 09:37.560 --> 09:44.120 go to the national authority, be disruptive and complain, without complain, the data will not 09:44.200 --> 09:49.720 be available, so goes there, find it, not available, go there and complain, there is deadline 09:49.720 --> 09:56.280 in that regulation, with very short period of time for this data to be finally available, 09:56.280 --> 10:01.080 public and free of charge, the European Commission with the support of the agency will 10:01.080 --> 10:06.600 monitor the progress, will take enforcement action, but for this enforcement action to be taken, 10:06.600 --> 10:12.200 we need a disruptive attitude of the open source community, consuming that data making 10:12.200 --> 10:20.280 creative use of it and pushing it to the next level, so I understood there is a date which 10:20.280 --> 10:25.160 is taken in Switzerland, well I don't know what is the level of implementation of SBB visas 10:25.160 --> 10:31.800 would be a good question I guess, but go there, ask them and consumes and they are data and 10:31.800 --> 10:37.160 let's see where we can push that first, many thanks, I will now give the floor to my colleague 10:37.160 --> 10:48.680 for a deep dive on a technical aspect, sorry, the deadline for implementation, the 10:53.640 --> 10:59.080 there is deadline for each different data type, so my advice is that they tune, 10:59.080 --> 11:04.040 look at another tensor for rearrangement legislation, I cannot quote them all by heart, 11:04.040 --> 11:09.400 it says that the earlier deadline is in March this year for veterans data, 11:09.400 --> 11:18.200 that is also in the one year, the latest deadline for which the regulation also cover free 11:18.280 --> 11:31.560 and the latest deadline, so when I spoke passenger, which is 28, I believe. 11:37.560 --> 11:44.600 So can you help me? Okay, very well, okay, I take over now from my colleague Jan's, let's say 11:44.600 --> 11:48.680 more technical part, of course, I will not bother you with all bits and bits of tickets, I think 11:48.680 --> 11:54.920 there are people in the room who have elaborated this in much more detail and I will talk a bit 11:54.920 --> 12:01.240 about some technical details of the telematics applications, because this is a regulation that 12:01.240 --> 12:07.640 will give you a hard decision, but first of all I would like to tell you what is the European 12:07.640 --> 12:13.640 Union agency for always because most of you have maybe a very good understanding what the European 12:13.640 --> 12:20.920 Commission does, but what is the European Union agency for railways? We are one of these, 12:20.920 --> 12:26.360 so, context-interalyzed agencies dealing with specific tasks for the European Commission and 12:26.360 --> 12:32.440 our task as the name says is dealing with questions related to railways and here more on the 12:32.440 --> 12:40.440 technical side, not on the market pillar. We have found a term already a long time ago in 2004 12:41.400 --> 12:47.880 based on two regulations, one regulation from 2004, which has been updated 10 years ago 12:48.840 --> 12:57.960 in the so-called force-ravy package, which gave us more tasks and we have a bit more than 200 12:57.960 --> 13:04.040 employees and are based in a nice north-on-flange town called Wollungsjende, not far away from 13:04.040 --> 13:13.800 Brussels, but on the other side of the border. And we have some topics which are our core topics 13:13.800 --> 13:20.360 we are dealing with, it's railway interoperability, it's so-called technical specifications for 13:20.360 --> 13:26.600 interoperability for rail, dealing with all technical details for rail and as well as the rail 13:26.600 --> 13:35.480 they saved. And with a new regulation from 2016, we are as well responsible for the authorization 13:35.480 --> 13:42.440 of running stock of railway vehicles in Europe and as well of the undertakings. It means if a 13:42.440 --> 13:48.360 railway undertaking wants to operate in Europe and wants to operate cross-border trains, they 13:48.360 --> 13:55.560 have to come to us and asking us, would you autorise that I operate them and after the check 13:55.560 --> 14:03.320 off-served documents, then we autorise and so-called vehicles can one. So maybe you are 14:03.320 --> 14:08.200 you were, if you were coming by rail to Brussels, you have already used trains which were 14:08.200 --> 14:16.760 autorised by all actions. Continuing with the topic, what is interoperability, what we have to 14:16.760 --> 14:23.400 regulate because sometimes there's an action scene, an authority have to regulate everything. 14:24.360 --> 14:31.880 For interoperability, it is not the case. We have to regulate some things to specify those 14:31.880 --> 14:40.840 technical details which are necessary which are specifying only so-called essential requirements 14:40.840 --> 14:49.560 and so-s requirements which are necessary to ensure that different parties can speak with each 14:49.560 --> 14:56.040 other different parties can operate also in networks with different infrastructures, operators 14:56.040 --> 15:02.360 with different railways operators and these essential requirements are mentioned in European 15:02.360 --> 15:09.560 regulations or the railways safety, the railia ability and availability, health environment protection, 15:10.680 --> 15:18.840 technical compatibility and as well accessibility. And we have teased lies related to structural 15:18.920 --> 15:24.520 subsystems means for instance rolling stock and infrastructure and here we come to the 15:24.520 --> 15:30.920 telemetics here so-called functionalist subsystems. Where we have different functions which have to 15:30.920 --> 15:37.320 be fulfilled in an interoperable way by all parties addressed by these regulations. 15:40.680 --> 15:48.040 Going down to the telemetics here's I and to the tiers I which is regulating the data exchange 15:48.840 --> 15:56.440 for trade transport for the operation of rail but as well for any aspect dealing with passenger 15:56.440 --> 16:03.640 information and ticketing because this is also three pillars of this tiers I and this is a tier 16:03.640 --> 16:13.000 side which will be published on 10th of February as you have heard now and we are regulating now 16:13.080 --> 16:19.640 these topics here including a common government for things which should be shared between those parties. 16:20.520 --> 16:27.080 This is for instance a so-called river and state I mean that if you address a railways station 16:27.080 --> 16:32.280 then even the railways station has sometimes the same name in Europe you should be sure if the 16:32.280 --> 16:39.080 railways station is located in Italy or in Germany even if the name Rome is the same of the 16:39.400 --> 16:46.360 most stations for instance and then we have a part called planning and operations this means 16:46.360 --> 16:53.160 this is a data exchange how the undertakings itself can reserve an access pass a slot for 16:53.160 --> 17:00.200 the railway network and follow up sends a slot if the train is running. Then freight specific 17:00.840 --> 17:07.160 data exchange for instance the exchange between freight companies if a wagon has reached a certain point 17:07.240 --> 17:13.800 to behind it over to another undertaking or all topics which are related to passenger information 17:13.800 --> 17:20.520 and ticketing starting from time-level information until the final ticketing at the end. 17:22.680 --> 17:28.600 And here I picked up some so-called basic parameters defining what kind of data have to be made 17:28.600 --> 17:35.240 a railway label and made a railway means as well not always only to rave a undertaking spot as well 17:35.880 --> 17:42.600 other parties and here I picked up one of the topics which is maybe the most interesting one for most 17:42.600 --> 17:50.120 of you it's the passenger information and it is a timetable data and here the purpose is to provide 17:50.120 --> 17:55.400 harmonize timetable data which can be understood in all member states which are harmonized 17:55.400 --> 18:01.080 in a way that if I read such a data set I have a clear understanding what is within that the 18:01.080 --> 18:06.840 partial time is clearly indicated and not enhanced by some information that you have to be earlier 18:06.840 --> 18:15.960 at the platform for instance it's intended to enable a facilitated journey planning and 18:15.960 --> 18:22.040 cover all the railway undertakings in Europe. There is no exception as long as the railway 18:22.040 --> 18:27.240 undertaking belongs to the interoperability directive. This is the overarching regulation. 18:27.320 --> 18:32.120 They have to follow this basic parameters and provide safe timetable data. 18:33.400 --> 18:39.880 The data format if you have just changed this a new TSI and the past we have used a format 18:39.880 --> 18:45.480 which has been developed decades ago by the rail sector and is still in use based on an 18:45.480 --> 18:51.000 artifact format and we just changed to a European standard called a netx which has been 18:51.000 --> 18:55.240 developed some years ago by the European standardization organization site. 18:56.200 --> 19:05.160 And to be published has also any alternative data have to be published. Updates must be published 19:05.160 --> 19:11.800 on time means we have as well requirements concerning the data quality and also historical data 19:11.800 --> 19:18.440 have to be available for instance to follow up the past or complaints in case of a delay. 19:18.840 --> 19:28.120 And the task is split between two and about a between two. Rolls here on the one hand side 19:28.120 --> 19:34.040 we have the railway undertakings which have to provide your time tether data but now as well 19:34.040 --> 19:40.920 the station manager, the entities managing the stations comes into force, they have as well 19:40.920 --> 19:44.840 to exchange data for instance about connecting times between trains. 19:45.480 --> 19:50.200 And so the data have to be published by the national access points. 19:51.800 --> 19:57.720 And the second topic I would like to address is the data just mentioned by my colleague 19:58.280 --> 20:02.680 and here we are talking about the railway undertakings which have to publish as well 20:02.680 --> 20:10.280 via the national access points that have a data but as I said restricted to service data which 20:11.160 --> 20:16.040 intended to be exchanged under a contractual agreement means before you can receive 20:16.040 --> 20:22.840 so a data kind of contractual agreement has to be agreed with in the parties and we are using 20:22.840 --> 20:29.640 as well here in this case a European standard as well a change of the standardization from let's say 20:29.640 --> 20:35.400 a bit outdated protocols based on CSV data which are to a certain extent still in use 20:36.280 --> 20:43.720 to an an example based format based on a European standard model and called SLL networks. 20:47.320 --> 20:54.200 And the last topic I would like to address because we are not only providing a technical 20:54.200 --> 20:59.160 expertise to provide those data and to support the European legislation with technical 20:59.160 --> 21:05.320 expertise we are also profiting from the work which is done in the open source community and I would 21:05.320 --> 21:11.960 like to show you one showcase we have here on the table because we have as well an obligation 21:11.960 --> 21:19.560 as European Union agency for avis to publish accessibility data for avis stations and here we build 21:19.560 --> 21:27.800 our system based on open source system a database which has been developed some decades some years 21:27.800 --> 21:38.040 ago by colleagues from Antio to provide information about accessibility of railway station and here 21:38.040 --> 21:45.720 the customized and open source tool in a way which is we'll be soon published as well on a 21:45.720 --> 21:53.720 production system on our side we are still on the customization phase on our systems to provide 21:53.720 --> 21:59.800 your accessibility data for all European stations which have to be feeded into the system 21:59.800 --> 22:05.880 by entities on the member state level means all member states have to feed the system which should 22:06.680 --> 22:13.640 allow you in the future to determine if the station in Europe is accessible for a wheelchair user 22:13.640 --> 22:19.400 for instance if you can come from any stop in the neighborhood from the public transport to 22:19.400 --> 22:26.920 the station without any obstacle and you can use the public transport even if you have if you 22:26.920 --> 22:33.720 are a wheelchair user for instance and so you see as well we try to profit from the work which is 22:33.720 --> 22:40.760 done in this community here and would like to extend this in the future if we see similar 22:40.760 --> 22:47.080 log projects which could help us to fulfill all tasks and now we are available for your questions 22:56.120 --> 23:02.440 so here and here so is there any work done by era or by the commission on ensuring that the 23:02.440 --> 23:07.080 data that is published by the national by the railway undertaking or the national infrastructure 23:07.080 --> 23:14.280 operators are actually correct in a sense that like frequently maybe there is some data that is 23:14.280 --> 23:20.120 published but there is duplicate data that is published by like in multiple different 23:20.120 --> 23:24.920 next files we'll see the same bit of data where there will be different station ideas use across 23:24.920 --> 23:30.040 different files like is there any work in progress to sort of unify this so that you can 23:30.680 --> 23:42.280 write down what all the data is. Short answer yes long answer we have with the new TSI as error 23:42.280 --> 23:49.480 as a task to manage this reference data means the station ideas centrally and we are starting to work 23:49.480 --> 23:54.920 on this topic even ideas are way labors nothing we have stopped from scratch but now we have to 23:55.000 --> 24:03.240 migrate this to this new work and yes quality parameters are foreseen in the TSI and are defined 24:03.240 --> 24:12.520 as legal requirements yeah they can be enforced by the commission we don't need to I mean we can 24:12.520 --> 24:19.880 take an extra question but let me answer so if you prefer not answer I can do both so of course 24:19.880 --> 24:25.720 the commission is enforcing your legislation what you need to be aware as I mentioned you 24:25.720 --> 24:33.960 endorsement is based on a complaint or assumption of non-compliance this TSI or this legislation 24:33.960 --> 24:41.960 also include a requirements on compliance meaning that and these are the following so the one on 24:42.040 --> 24:51.160 which the requirements are have to demonstrate compliance and then on the base of non-compliance 24:51.160 --> 24:57.560 or presumption of non-compliance or complaint the agency as system authority as actually authority 24:57.560 --> 25:04.520 to do a formal compliance check if this compliance check is negative as a sense of the alleged 25:04.520 --> 25:09.720 compliance is not only alleged but it's an actual non-compliance then the commission can take 25:09.720 --> 25:13.800 enforcement aid action against the member state and the member state are taking 25:14.600 --> 25:21.000 enforcement action against the company themselves we find and so on I think we can 25:39.720 --> 25:52.200 approach the commission they's putting not that deep in pressure 25:52.200 --> 25:53.200 or something like that. 25:53.200 --> 25:58.560 So how strong is the involvement of an enforcement 25:58.560 --> 26:00.360 for seeing its regulation is? 26:00.360 --> 26:03.560 You might really definitely wait to get it to community time. 26:03.560 --> 26:05.560 So the commission is putting nobody in prison. 26:09.800 --> 26:11.200 Be disruptive. 26:11.200 --> 26:14.120 Raise awareness on the non-compliance. 26:14.120 --> 26:17.320 And blame and shame exercise is actually quite well 26:17.320 --> 26:19.440 walking from my personal experience. 26:19.440 --> 26:20.560 Thank you very much. 26:20.560 --> 26:22.560 Thank you very much.