Removal of national particularities Introduction Became team member Next presenter Removal of national particularities PCS-TTR Day 2018, Vienna

Previously about National IM Parameters Why do we have to talk about it? I would like to give you a quick overwiev and highlight the importance of it! Since PCS introduced the number of National parameters grew dramatically in the past few years. We all know what are these parameters are for! We all know that PCS contains common parameters, but what happens when these parameter are not suitable enough? Guess what? Then each IM/AB has to create their own network specific parameters (NS). Everybody who is regular PCS user started to create these parameters and the number of these parameters are highly increased! This is the point where the problem have started….

National Parameters (Network Specific Parameters) Our target is to reduce the number of National Parameters together with IMs/ABs as much as possible. However, if some exist, why do we need them in PCS? National System PCS 1 2 3 Without National Parameters in PCS Common parameter National parameter National System PCS 1 2 With National Parameters in PCS Common and national parameter What would like to achive? To reduce the number of National Parameters. (We can delete all of them from the system that is not a problem! ) However, if some exist, but still why do we need them in PCS? The reason is why you need to enter into your National System! See PCS how works without National Parameters together with the National Systems, You need to use another communication chanel, to send email or text to notify others and after Manually has to enter these parameters. And see when PCS is working with National Parameters, how easy it is, you enter the information ones and goes into the National system!

Steps with the parameters STANDARDIZE In case of partial interest, National Parameters should be harmonized among the creator IMs/ABs (name, format, validation, etc.) DISCUSS First National Parameter workshop, organized by PCS Team. Target is the removal/harmonization of National Parameters for TT2020 REMOVE National Parameters that are already part of the existing TAF/TAP-TSI or PCS schema should be removed by the IMs/ABs Mid-term ADOPT In case of common interest, National Parameters should be added to the general TAF/TAP-TSI schema Long-term How di we get there? Basicly analyzed the last years parameters which have already defined in the system. What to do with these parameters? Stadardize the validation, format and name! Why? It happenes that the same parameter have been defined by IMs on a different name or on slightly different name. When there is clearly a common demand, it shall be checked by the sector, whether it makes sense to include to the common schema. Discuss: Outr work continued with various discussions and first National IM Parameter and Loco Preparation for TT2020 meeting held in October, where we checked the parameters and proposed some optimization. Ex. Öbb and VPE started to use same parameters. This what we have done in short term actions and our work continues with Mid and Long-term actions. Mid –term remove: degrees the number of those parameters which are already part of TAF/TSI and PCS schema. And for long-term adopt: In case of common interest National Parameters should be added to the TAF/TSI schema. Short-term Short-term

Checking the results of the short-term actions

Participation in the workshop 30th October 2018, a workshop (WS) was organized for IMs/Abs to review their national IM parameters (NIMP) and loco types. Participated on the WS Absent from the WS, but sent data Absent from the WS, pending information No NIMP in PCS As I mentioned earlier the first workshop organized in October. PCS Team would like to show how efficient we were and how many IMs we have been working together with to optimize these parameters.

Comparison 2019 and 2020 345 216 Parameters in total ADIF Contact information is available in PCS, no need for parameters. See the comparison a bit detailed and on the chart and see how many total number of parameters we had in the system! See what we achived now! Degreesed the number of it from 345 to 216. Lets see some examples: We received valuable inputs under the analysis, let me present 3 examples. It could have the numbers are chanced since last month. CFR PCS common technical planned data is suitable enough, no need for parameters VPE Re-conceptualize the way of ordering services, need for less parameters

Looking deeper behind the figures Are all the parameters for the RUs? No, some parameters, e.g. at SZDC network are for the IM to provide additional information to the offer Are all the parameters mandatory? No, most of them are optional Parameters in total 82 Lets looking behind the figures. Are all the parameters for the RUs? No, some parameters, e.g. at SZDC network are for the IM to provide additional information to the offer Are all the parameters mandatory? No, most of them are optional See what we achieved so far! How many mandatory parameters do we have in the system! Get examples But there is a long way to go as we still have all together 82 clustered ! *Number of mandatory parameters are lower, if there is national (TPN, M-AMA) request

Clustering The 82 mandatory parameters can be clustered by motivation index, local index and schema index. Motivation index Operational Organizational Double requests Timetabling Invoicing, charging Network statements Safety reasons Local index The need is only local The need is available European wide Schema index We have qlassified the parameters: Motivation – what is the purpose? Local Schema index: exaples: Dangeourus goods Contact informations Tilting And according to the role of responsibility, role of responsible applicant and role of responsible RU – not always the same person who orders and manages the train! Missing in TAF, but it’s mandatory nationally Part of PCS, but in slightly different format Part of PCS, but not included in TAF Part of TAF, but not yet in PCS

Thank you! Introduction Became team member Next presenter