WEBVTT 00:00:00.320 --> 00:00:05.400 From a larger selection, we first made a long list 00:00:05.400 --> 00:00:07.400 and then a short list from this long list. 00:00:08.040 --> 00:00:10.480 The participants who were still on the shortlist 00:00:10.920 --> 00:00:14.440 were then chosen for a proof-of-concept project. 00:00:14.640 --> 00:00:20.720 That means that over a period of 2 to 3 months, we set up a test system. 00:00:21.360 --> 00:00:24.520 We put it through its paces, testing everything 00:00:24.520 --> 00:00:29.040 that was relevant to our needs, everything that was important 00:00:29.920 --> 00:00:31.680 to us and that the system 00:00:31.680 --> 00:00:34.400 should be able to do, 00:00:34.400 --> 00:00:38.560 including data imports from TecDoc in TecDoc format, 00:00:39.840 --> 00:00:44.080 from Excel files from CSV files, and manual data maintenance in the PIM. 00:00:44.080 --> 00:00:46.320 How does it work? How can it be handled? 00:00:46.760 --> 00:00:48.880 Is it user-friendly? 00:00:48.880 --> 00:00:50.560 Is it complex? 00:00:51.160 --> 00:00:53.560 What are the settings in the background of the PIM? 00:00:53.880 --> 00:00:56.200 We were able to test all of this in detail 00:00:56.800 --> 00:00:59.560 and the result for us was 00:00:59.560 --> 00:01:02.680 that ANTEROS by INCONY 00:01:03.760 --> 00:01:06.760 is definitely the best system for our group. 00:01:07.120 --> 00:01:08.960 Perhaps briefly the reasons for this. 00:01:09.240 --> 00:01:11.600 On the one hand, of course, the experience that INCONY has. 00:01:11.840 --> 00:01:16.920 INCONY has many customers who are also active in the automotive sector. 00:01:18.440 --> 00:01:24.200 INCONY also has many years of experience with TecAllianz. 00:01:24.200 --> 00:01:28.600 TecDoc data, imports, exports, the whole thing in TAF format 00:01:29.440 --> 00:01:32.560 and of course the great references 00:01:32.560 --> 00:01:35.840 and also the feedback we got from others 00:01:35.840 --> 00:01:38.600 made us choose ANTEROS. 00:01:39.160 --> 00:01:42.160 Of course, you choose a system not only because you 00:01:42.160 --> 00:01:45.160 like the people behind it, but also the system itself. 00:01:45.520 --> 00:01:49.200 In this proof-of-concept, I have to say it was very flexible. 00:01:49.800 --> 00:01:53.040 There is a flexible data model. 00:01:53.080 --> 00:01:58.240 You can not only load TecDoc data and have 00:01:58.240 --> 00:02:01.240 this data in the system one-to-one, but you also have the option 00:02:01.840 --> 00:02:05.080 of adding your own data and enriching this data once again, 00:02:05.280 --> 00:02:10.080 creating your own brands and then maintaining them here. 00:02:10.840 --> 00:02:13.720 The user interface is very user-friendly, 00:02:13.720 --> 00:02:15.320 it is modern, it is intuitive. 00:02:16.760 --> 00:02:19.080 The standard alone that ANTEROS provides 00:02:19.920 --> 00:02:24.080 has extensive functions for data maintenance, also for imports and exports. 00:02:25.400 --> 00:02:29.080 The configurability that ANTEROS provides 00:02:29.320 --> 00:02:33.200 was also an important factor, and especially the multi-client capability. 00:02:33.360 --> 00:02:36.880 We'll come back to that later and what exactly that means. 00:02:38.160 --> 00:02:40.000 Those were the crucial points. 00:02:40.000 --> 00:02:44.120 And perhaps I should also briefly tell you again that the employees 00:02:44.720 --> 00:02:47.560 who accompanied us in the project were really 00:02:49.200 --> 00:02:51.800 approachable at all times. 00:02:51.800 --> 00:02:54.360 So it was really superb. 00:02:54.360 --> 00:02:55.640 There's no other way to put it. 00:03:02.120 --> 00:03:04.600 Let's start with myself, my name is Ralf Schroll. 00:03:04.600 --> 00:03:07.560 I am responsible for 00:03:07.560 --> 00:03:12.960 Master Data and the online store, a team with ten employees, in which we 00:03:12.960 --> 00:03:16.600 support the master data, the product master data for our subsidiaries 00:03:16.960 --> 00:03:19.760 and of course also the various online stores. 00:03:19.760 --> 00:03:23.520 This means that we also make further developments for the online stores 00:03:23.520 --> 00:03:26.560 further features that our B2B customers want. 00:03:27.040 --> 00:03:30.000 But now the focus here is on the topic of master data, 00:03:30.000 --> 00:03:34.120 i.e. on the PIM, our ANTEROS tool by INCONY. 00:03:34.480 --> 00:03:37.440 And from my team I have Andreas Santner with me. 00:03:37.440 --> 00:03:40.120 He is our absolute specialist for the PIM. 00:03:40.120 --> 00:03:43.720 Yes, and Andreas, I would like to pass the floor to you now. 00:03:44.120 --> 00:03:45.320 Yes, thank you. 00:03:45.640 --> 00:03:48.280 Yes, briefly about myself. Andreas Santner. 00:03:48.600 --> 00:03:53.720 I work in the master data team, at BPW Aftermarket Group 00:03:53.800 --> 00:03:56.800 and I will take you now in the following 00:03:56.920 --> 00:03:59.920 or with the following slides a little bit into 00:04:00.280 --> 00:04:05.800 our project, how we use ANTEROS in our Aftermarket Group later AMG, - 00:04:06.720 --> 00:04:08.520 we like to use the abbreviation. 00:04:08.960 --> 00:04:11.520 You forget that the people listening don't know that. 00:04:11.600 --> 00:04:14.240 So when I say AMG, that's the aftermarket group. 00:04:15.160 --> 00:04:17.760 Right, then I'll move on at this point. 00:04:18.080 --> 00:04:22.120 We have written "Efficient maintenance and multiple use of complex data" on the first slide. 00:04:22.720 --> 00:04:25.880 As I said, Andreas will show this in detail in the PIM itself. 00:04:26.320 --> 00:04:29.440 But perhaps a little more detail on the first slide: 00:04:29.440 --> 00:04:32.200 Who are we at BPW AMG anyway? 00:04:32.200 --> 00:04:33.680 As Andreas just said, 00:04:33.840 --> 00:04:35.920 AMG is short for none other than Aftermarket Group, 00:04:35.920 --> 00:04:39.600 which logically means everything that involves the trade in spare parts, accessories 00:04:39.600 --> 00:04:43.680 and service articles after the actual initial sale. 00:04:44.120 --> 00:04:45.400 So what that means 00:04:45.400 --> 00:04:49.280 is that we bring all kinds of parts via our online stores to B2B 00:04:49.360 --> 00:04:50.640 customers who are allowed - 00:04:50.640 --> 00:04:55.880 service workshops, for example, rental service providers and so on - 00:04:55.920 --> 00:04:58.400 who are allowed to keep their trucks and their trailers, 00:04:58.400 --> 00:05:01.400 their trucks rolling on the roads. 00:05:01.560 --> 00:05:04.560 So that's a CV parts trading network, 00:05:04.600 --> 00:05:07.600 so commercial vehicle, we're back to an acronym. 00:05:07.720 --> 00:05:09.240 We are positioned throughout Europe. 00:05:09.240 --> 00:05:12.360 We have 170 branches in 19 countries across Europe. 00:05:12.360 --> 00:05:15.640 Actually, that's no longer the case, I just remembered. 00:05:15.640 --> 00:05:18.840 We now have another company in New Zealand, which will be added. 00:05:19.320 --> 00:05:23.120 And in terms of our product portfolio, on the one 00:05:23.120 --> 00:05:27.080 hand we have original spare parts, OE items, as we call them - 00:05:27.080 --> 00:05:30.880 original equipment - from all relevant commercial vehicle manufacturers. 00:05:30.880 --> 00:05:32.600 I'm not going to list the brands now, 00:05:32.920 --> 00:05:35.680 so we can offer solutions for repairing even older vehicles 00:05:35.680 --> 00:05:38.720 that are in line with their current value. 00:05:39.080 --> 00:05:42.600 That is the rough picture of AMG. 00:05:42.680 --> 00:05:47.320 We are a subsidiary of the BPW Group as a whole, 00:05:47.680 --> 00:05:50.440 the old "Bergische Achsen", perhaps some of you have 00:05:50.440 --> 00:05:54.440 heard of it, from 1898, a very traditional 00:05:55.000 --> 00:05:56.840 medium-sized family business. 00:05:57.040 --> 00:06:00.000 Yes, this is roughly the overview of our company. 00:06:01.040 --> 00:06:04.920 The incentive for a PIM system here at AMG: 00:06:05.120 --> 00:06:09.280 As you can imagine, 170 subsidiaries, 19 countries, 00:06:09.960 --> 00:06:11.760 there is a lot of data traffic. 00:06:12.600 --> 00:06:16.680 In the past, everyone had their own ERP. 00:06:17.360 --> 00:06:19.960 Everyone maintained the data as they saw fit. 00:06:20.360 --> 00:06:22.280 This meant that we were not able to 00:06:22.280 --> 00:06:26.040 communicate with each other at all on the product level. 00:06:26.640 --> 00:06:31.520 Therefore, the first goal for us was uniform central data maintenance, 00:06:32.840 --> 00:06:35.400 meaning time savings. 00:06:35.760 --> 00:06:39.000 The data is maintained once in a central location 00:06:39.000 --> 00:06:40.960 and then passed on to all the others. 00:06:42.160 --> 00:06:44.200 We have better data quality 00:06:44.200 --> 00:06:48.760 because we have defined criteria and guidelines in advance 00:06:49.080 --> 00:06:51.440 in consultation with the company 00:06:52.040 --> 00:06:54.440 as to what data should be maintained. 00:06:54.920 --> 00:06:58.680 Another advantage, of course, is that the ETGs can also use this data. 00:06:59.120 --> 00:07:00.920 The data is also translated. 00:07:00.920 --> 00:07:02.320 So we don't 00:07:02.320 --> 00:07:05.440 just keep it in German, but in the future also 00:07:06.360 --> 00:07:09.880 in English and then also in the language of the country 00:07:10.120 --> 00:07:11.520 where the ETG is located. 00:07:11.520 --> 00:07:14.120 What else did the PIM have to be able to do? 00:07:14.120 --> 00:07:16.680 Of course, we don't just want to have the data in the PIM; 00:07:16.680 --> 00:07:19.600 we also want to transfer the data to other systems. 00:07:20.640 --> 00:07:22.640 For example, 00:07:22.640 --> 00:07:25.400 there is our new online store, which has 00:07:26.040 --> 00:07:28.200 now been created. 00:07:28.760 --> 00:07:31.120 Then, of course, we also have subsidiaries 00:07:31.120 --> 00:07:33.640 that act as manufacturers 00:07:34.400 --> 00:07:36.360 on the market and want to share their data 00:07:36.360 --> 00:07:39.080 with TecDoc or Topmotive. 00:07:40.200 --> 00:07:43.560 Furthermore, there is of course also an ERP system, 00:07:43.560 --> 00:07:46.560 which will also be standardized in the countries 00:07:47.040 --> 00:07:49.520 over time and the data will also be used there. 00:07:50.480 --> 00:07:54.920 Roughly summarized, maintain data once, but use it multiple times. 00:07:55.440 --> 00:08:01.040 How did we come to the decision to use ANTEROS, or rather, why ANTEROS? 00:08:02.080 --> 00:08:04.800 First of all, of course, we made an invitation to tender, 00:08:06.040 --> 00:08:09.160 because there are of course many different systems 00:08:09.160 --> 00:08:10.560 and providers on the market. 00:08:12.360 --> 00:08:14.920 The tender took place 00:08:15.760 --> 00:08:19.760 with lists of questions, as well as presentations from several providers, 00:08:20.520 --> 00:08:25.920 and we first made a long list from a larger selection, 00:08:25.920 --> 00:08:27.920 and then a short list from this long list. 00:08:28.560 --> 00:08:31.000 The participants who were still on the shortlist 00:08:31.440 --> 00:08:34.960 were then chosen for a proof-of-concept project. 00:08:35.160 --> 00:08:41.240 That means that over a period of 2 to 3 months, we set up a test system. 00:08:41.880 --> 00:08:45.040 We put it through its paces, testing everything 00:08:45.040 --> 00:08:49.560 that was relevant to our needs, everything that was important 00:08:50.440 --> 00:08:52.200 to us and that the system 00:08:52.200 --> 00:08:54.920 should be able to do, 00:08:54.920 --> 00:08:59.080 including data imports from TecDoc in TecDoc format, 00:09:00.360 --> 00:09:04.600 from Excel files from CSV files, and manual data maintenance in the PIM. 00:09:04.600 --> 00:09:06.840 How does it work? How can it be handled? 00:09:07.280 --> 00:09:09.400 Is it user-friendly? 00:09:09.400 --> 00:09:11.080 Is it complex? 00:09:11.680 --> 00:09:14.080 What are the settings in the background of the PIM? 00:09:14.400 --> 00:09:16.720 We were able to test all of this in detail 00:09:17.320 --> 00:09:20.080 and the result for us was 00:09:20.080 --> 00:09:23.200 that ANTEROS by INCONY 00:09:24.280 --> 00:09:27.280 is definitely the best system for our group. 00:09:27.640 --> 00:09:29.480 Perhaps briefly the reasons for this. 00:09:29.760 --> 00:09:32.120 On the one hand, of course, the experience that INCONY has. 00:09:32.360 --> 00:09:37.440 INCONY has many customers who are also active in the automotive sector. 00:09:38.960 --> 00:09:44.720 INCONY also has many years of experience with TecAllianz. 00:09:44.720 --> 00:09:49.120 TecDoc data, imports, exports, the whole thing in TAF format 00:09:49.960 --> 00:09:53.080 and of course the great references 00:09:53.080 --> 00:09:56.360 and also the feedback we got from others 00:09:56.360 --> 00:09:59.120 made us choose ANTEROS. 00:09:59.680 --> 00:10:02.680 Of course, you choose a system not only because you 00:10:02.680 --> 00:10:05.680 like the people behind it, but also the system itself. 00:10:06.040 --> 00:10:09.720 In this proof-of-concept, I have to say it was very flexible. 00:10:10.320 --> 00:10:13.560 There is a flexible data model. 00:10:13.600 --> 00:10:18.760 You can not only load TecDoc data and have 00:10:18.760 --> 00:10:21.760 this data in the system one-to-one, but you also have the option 00:10:22.360 --> 00:10:25.600 of adding your own data and enriching this data once again, 00:10:25.800 --> 00:10:30.600 creating your own brands and then maintaining them here. 00:10:31.360 --> 00:10:34.240 The user interface is very user-friendly, 00:10:34.240 --> 00:10:35.840 it is modern, it is intuitive. 00:10:37.280 --> 00:10:39.600 The standard alone that ANTEROS provides 00:10:40.440 --> 00:10:44.600 has extensive functions for data maintenance, also for imports and exports. 00:10:45.920 --> 00:10:49.600 The configurability that ANTEROS provides 00:10:49.840 --> 00:10:53.720 was also an important factor, and especially the multi-client capability. 00:10:53.880 --> 00:10:57.400 We'll come back to that later and what exactly that means. 00:10:58.680 --> 00:11:00.520 Those were the crucial points. 00:11:00.520 --> 00:11:04.640 And perhaps I should also briefly tell you again that the employees 00:11:05.240 --> 00:11:08.080 who accompanied us in the project were really 00:11:09.720 --> 00:11:12.320 approachable at all times. 00:11:12.320 --> 00:11:14.880 So it was really superb. 00:11:14.880 --> 00:11:16.160 There's no other way to put it. 00:11:16.840 --> 00:11:20.920 Yes, how is the PIM system, so ANTEROS, used in our company? 00:11:21.280 --> 00:11:25.000 For us, it was clear from the outset that this would be our leading system. 00:11:25.000 --> 00:11:29.800 So all products or all articles are first created in the PIM 00:11:30.520 --> 00:11:34.040 and are then exported from the PIM to other systems. 00:11:34.760 --> 00:11:37.040 You can see that here on the PIM slide, 00:11:37.080 --> 00:11:40.040 ANTEROS is the focus for us. 00:11:41.520 --> 00:11:43.480 The product data that we have is then 00:11:44.400 --> 00:11:46.960 imported into the PIM, enriched, created, 00:11:46.960 --> 00:11:50.480 in whatever form and then transferred 00:11:50.800 --> 00:11:55.400 to our ERP. 00:11:55.600 --> 00:11:58.960 Of course, as already mentioned, we also want 00:11:58.960 --> 00:12:02.960 to have the data in our new web store, which is a proprietary development on our part. 00:12:03.320 --> 00:12:07.960 We also mentioned earlier that we have subsidiaries of BPW KG 00:12:07.960 --> 00:12:10.000 that act as manufacturers on the market 00:12:10.000 --> 00:12:15.280 and naturally also want to present their products in the dealer portals 00:12:15.280 --> 00:12:19.600 such as TecAllianz, TecDoc or Topmotive. 00:12:19.920 --> 00:12:23.920 ANTEROS also offers the option 00:12:23.920 --> 00:12:26.560 of not only using the data from TecDoc, 00:12:26.560 --> 00:12:32.520 but also importing the data from Topmotive. 00:12:32.640 --> 00:12:36.640 The advantage of this is that Topmotive has a few more 00:12:36.640 --> 00:12:41.080 generic articles and also has a few more criteria available, 00:12:41.280 --> 00:12:46.280 which of course makes it a bit easier for us to divide the variety of products 00:12:46.680 --> 00:12:50.840 into a category tree in a sensible way. 00:12:51.320 --> 00:12:54.720 Yes, as I said, PIM as a measure for product data maintenance, 00:12:55.320 --> 00:12:58.360 product creation takes place exclusively in ANTEROS. 00:12:58.760 --> 00:13:04.080 For this, ANTEROS has a standard unique ID called a code, which 00:13:04.080 --> 00:13:06.400 is generated from seconds and minutes. 00:13:07.040 --> 00:13:09.320 We decided to use a different variant, 00:13:09.320 --> 00:13:14.240 simply for the reason: There are very many suppliers 00:13:15.640 --> 00:13:18.280 that we have in the portfolio and it can of course 00:13:18.280 --> 00:13:22.280 happen that a supplier article number, if you only take this number for itself, 00:13:23.080 --> 00:13:25.240 can be assigned to multiple suppliers. 00:13:25.440 --> 00:13:26.600 That is, the number itself, 00:13:26.600 --> 00:13:30.880 you do not know, is it MAN, is it MAHLE is it febi? 00:13:31.240 --> 00:13:34.000 Without a unique ID, 00:13:34.520 --> 00:13:37.280 you simply can't clearly identify the item. 00:13:37.280 --> 00:13:38.400 For this reason, 00:13:39.240 --> 00:13:43.560 we decided to have a ten-digit unique 00:13:43.560 --> 00:13:47.400 ID generated, which INCONY was able to 00:13:47.640 --> 00:13:51.680 implement relatively quickly and without any problems. 00:13:51.720 --> 00:13:56.160 We used various product data to create the new system. 00:13:56.200 --> 00:13:57.720 On the one hand, as already mentioned, 00:13:57.720 --> 00:14:01.960 we have imported these supplier articles, which are provided by TecDoc 00:14:01.960 --> 00:14:05.840 or Topmotive, in TAF format. 00:14:06.000 --> 00:14:09.440 We supplement this data once again 00:14:09.640 --> 00:14:13.480 with data that we need for our ERP, of course. 00:14:13.480 --> 00:14:15.240 For the merchandise management system as well. 00:14:15.240 --> 00:14:19.200 The second product type is private label products. 00:14:20.600 --> 00:14:25.560 As I said before, you can or you have the option, of course, 00:14:26.280 --> 00:14:30.680 creating your own brands in ANTEROS 00:14:30.680 --> 00:14:33.680 and then maintaining product data for them accordingly. 00:14:34.640 --> 00:14:40.840 At the start of the project, or rather in the middle of the project, 00:14:40.840 --> 00:14:46.080 we had to import all the products from the old product database 00:14:46.080 --> 00:14:48.800 into ANTEROS as a one-off. 00:14:50.240 --> 00:14:51.880 The cleansing, I call it, 00:14:51.880 --> 00:14:55.360 or the duplicate check of ANTEROS 00:14:55.440 --> 00:14:58.680 also helped us a lot to clean up the whole thing a bit. 00:15:00.280 --> 00:15:02.360 In total, we currently have 00:15:03.400 --> 00:15:05.680 almost 700,000 products in the PIM. 00:15:06.360 --> 00:15:10.600 It has to be said that not all ETGs are connected yet. 00:15:11.000 --> 00:15:14.440 That will only happen now in the following years. 00:15:14.440 --> 00:15:18.240 We expect to have somewhere around 1 million products 00:15:18.680 --> 00:15:21.000 to maintain in ANTEROS. 00:15:21.400 --> 00:15:23.440 ANTEROS in action at our company. 00:15:23.880 --> 00:15:26.080 How does access work? How do 00:15:27.040 --> 00:15:28.720 you get to or into ANTEROS? 00:15:29.440 --> 00:15:31.120 ANTEROS is completely web-based. 00:15:31.120 --> 00:15:35.720 This means that you can access the system in your car, at home, on the bus, 00:15:35.920 --> 00:15:39.160 on the train, wherever you want, and maintain data 00:15:39.160 --> 00:15:41.440 diligently if you want to. 00:15:41.840 --> 00:15:45.880 Every user gets a login with their own password. 00:15:46.120 --> 00:15:47.080 Of course 00:15:48.320 --> 00:15:53.120 not everyone is allowed to do everything in ANTEROS, as is the case with all other systems. 00:15:53.120 --> 00:15:55.320 There are extensive user roles. 00:15:55.800 --> 00:15:58.520 You can classify it very precisely in ANTEROS. 00:15:58.520 --> 00:16:01.520 Who is allowed to a) see and b) edit what? 00:16:02.360 --> 00:16:04.840 Who is only allowed to see and not to edit anything? 00:16:05.240 --> 00:16:08.360 So all this is possible in ANTEROS without any problems. 00:16:08.360 --> 00:16:12.040 And last but not least the data is encrypted. 00:16:12.720 --> 00:16:15.480 What does product data maintenance in ANTEROS look like for us? 00:16:16.320 --> 00:16:17.720 For example, you can see 00:16:18.360 --> 00:16:22.880 here on the left side of the screen - we have now selected a product, 00:16:23.920 --> 00:16:28.640 on the right half of the screen you can see all the tabs 00:16:29.360 --> 00:16:32.480 where we can practically maintain the product data, 00:16:32.480 --> 00:16:35.120 properties for the product. 00:16:35.920 --> 00:16:39.240 This was also a decisive point for us. 00:16:39.240 --> 00:16:41.080 The clarity that you have here, 00:16:41.640 --> 00:16:44.480 as you can see, you can click through the tabs at the top. 00:16:45.040 --> 00:16:48.520 The tabs contain different topics, so you can directly see 00:16:48.520 --> 00:16:51.840 "Okay, I have dangerous goods data, so I go to the dangerous goods tab. 00:16:51.840 --> 00:16:53.160 That's where I can maintain the data." 00:16:53.440 --> 00:16:58.280 In the General tab, there is some data 00:16:58.440 --> 00:17:04.000 that is necessary for the ERP - article numbers, article descriptions. 00:17:04.200 --> 00:17:06.440 Then, of course, there is a TecDoc tab, where all the data 00:17:06.440 --> 00:17:09.960 that we import from TecDoc is stored. 00:17:09.960 --> 00:17:14.000 Not all, but I say the basics, the basic data from TecDoc. 00:17:14.400 --> 00:17:18.840 ERP tab for ERP data, dangerous goods for dangerous goods as mentioned, etc. 00:17:18.840 --> 00:17:23.200 Further to the right, there are cross references that you can also 00:17:23.840 --> 00:17:28.280 add yourself, in addition to what you get from the dealer portals. 00:17:28.320 --> 00:17:31.920 Just like vehicle links, parameter values. 00:17:31.920 --> 00:17:34.280 Relations are also very important for us. 00:17:34.280 --> 00:17:37.920 Relations means, who is the supplier of the article? 00:17:38.360 --> 00:17:40.360 Is the item a deposit item? 00:17:40.800 --> 00:17:43.120 Are there substitute items for the deposit item? 00:17:43.720 --> 00:17:45.200 And so on and so forth. 00:17:45.360 --> 00:17:49.560 Of course, not to be sneezed at - anyone who has an online store; Online stores need images. 00:17:49.640 --> 00:17:54.120 For this there is also a Media tab, where it is relatively easy to store 00:17:54.120 --> 00:17:57.680 pictures, drawings, documents or even videos. 00:17:58.000 --> 00:18:00.800 All in all, it is easy and efficient 00:18:00.800 --> 00:18:04.520 to maintain the whole collection of data in ANTEROS. 00:18:04.960 --> 00:18:10.960 It is clearly arranged and it is user-friendly. 00:18:11.160 --> 00:18:13.240 In addition, as I mentioned at the beginning, 00:18:14.480 --> 00:18:17.920 we not only add data that we get from the dealer portals, 00:18:18.320 --> 00:18:22.320 but we also have the possibility to maintain data for the private brands. 00:18:23.480 --> 00:18:27.640 For this purpose, the corresponding brand is created in ANTEROS, 00:18:27.640 --> 00:18:31.920 with a corresponding ID so that this brand can 00:18:32.640 --> 00:18:34.720 also be used for further systems. 00:18:35.200 --> 00:18:36.400 The maintenance itself 00:18:37.480 --> 00:18:42.200 is then the same as that of the TecDoc data that we receive. 00:18:42.720 --> 00:18:45.040 You also have the possibility to flexibly 00:18:46.320 --> 00:18:48.800 store or upload all sorts of data 00:18:49.560 --> 00:18:51.640 that is relevant for you, 00:18:51.720 --> 00:18:55.600 and to configure ANTEROS in such a way, 00:18:55.600 --> 00:18:57.960 so that everything you might not need 00:18:59.080 --> 00:19:01.880 is hidden and does not disturb you at work. 00:19:02.120 --> 00:19:06.240 Furthermore, the specific 00:19:06.240 --> 00:19:09.520 or the specific country assortment is still listed here. 00:19:10.160 --> 00:19:12.720 We'll get into that in a bit more detail later. 00:19:13.400 --> 00:19:16.920 would say that the market in Germany or Spain is a different market 00:19:16.920 --> 00:19:17.880 than the one in Sweden. 00:19:18.800 --> 00:19:20.960 From that point of view, we also have the possibility, 00:19:22.080 --> 00:19:29.000 thanks to the flexibility and setting options in ANTEROS, to say which ETG, 00:19:29.000 --> 00:19:32.960 which national company gets which assortment. 00:19:34.000 --> 00:19:35.680 But more about that in a moment. 00:19:36.320 --> 00:19:39.960 Efficient data maintenance thanks to ANTEROS calculation rules. 00:19:40.400 --> 00:19:44.800 Here perhaps with a small example - it is, of course, usually more extensive, 00:19:44.800 --> 00:19:48.080 all that you can do with these calculation rules. 00:19:48.520 --> 00:19:50.800 Here I wanted to show a small example 00:19:51.680 --> 00:19:54.080 of how to automatically calculate parameters. 00:19:54.600 --> 00:20:00.800 You have the possibility here to use texts or values 00:20:00.800 --> 00:20:04.640 or also text elements to automatically calculate 00:20:04.640 --> 00:20:06.440 a coherent sentence. 00:20:06.440 --> 00:20:09.640 Of course within your own conditions or defaults, 00:20:09.640 --> 00:20:11.720 which of course you have to set in ANTEROS. 00:20:12.840 --> 00:20:13.720 The advantage is: 00:20:13.720 --> 00:20:18.800 You get good data with less work, but of course it doesn't happen without any work at all. 00:20:18.800 --> 00:20:21.800 But by, let's say, 00:20:22.320 --> 00:20:29.960 automatically assembling one of two different usage sets 00:20:29.960 --> 00:20:33.720 and using that in another system, we naturally save 00:20:33.720 --> 00:20:35.320 ourselves the maintenance in the other system, 00:20:35.440 --> 00:20:38.520 where we need something different than we would for the online store, for example. 00:20:38.720 --> 00:20:40.280 Specifically, perhaps the example 00:20:41.760 --> 00:20:42.640 of a water pump 00:20:43.440 --> 00:20:47.080 for the car or for a truck is also a generic article 00:20:47.240 --> 00:20:50.920 at Topmotive or at TecDoc, but stands on its own. 00:20:52.040 --> 00:20:54.920 But there are also packages, for example, a water pump 00:20:54.920 --> 00:20:57.080 with seals or with a seal. 00:20:57.320 --> 00:21:00.280 Accordingly, we have the generic article water pump. 00:21:00.280 --> 00:21:04.160 We have the additional text "with seals" and for the ERP 00:21:04.160 --> 00:21:07.040 we have this automatically assembled by ANTEROS 00:21:07.040 --> 00:21:10.160 so that the text "water pump with seal" appears in the ERP. 00:21:10.440 --> 00:21:12.240 So that the person who receives the delivery bill 00:21:12.240 --> 00:21:15.520 can perhaps also better identify "Okay, in this package 00:21:15.640 --> 00:21:17.760 there must be a water pump with seals". 00:21:17.760 --> 00:21:19.080 This is the background 00:21:20.040 --> 00:21:23.680 and you can of course run this on several examples. 00:21:23.680 --> 00:21:28.040 There are no limits as far as this automated calculation is concerned. 00:21:28.440 --> 00:21:31.800 Yes, what does that look like when you do that in ANTEROS? 00:21:32.920 --> 00:21:38.240 In the calculation rules - a submenu that you can open - 00:21:38.480 --> 00:21:43.040 you have the option to select the corresponding data fields. 00:21:43.440 --> 00:21:46.800 You can see this field here, where the pencil is. 00:21:46.800 --> 00:21:49.640 You can then click on it, select 00:21:50.360 --> 00:21:53.640 the corresponding field and, using the Free Marker format language, 00:21:53.640 --> 00:21:58.240 you can create the corresponding rule, refer to the individual fields, 00:21:58.680 --> 00:22:02.440 so that you get the water pump with seal as the end result. 00:22:03.080 --> 00:22:06.160 Master data, article data, data in general. 00:22:06.160 --> 00:22:11.040 Yes, there is of course more than "just" what comes from TecDoc. 00:22:12.720 --> 00:22:16.760 As mentioned before, we also imported data from Topmotive. 00:22:16.920 --> 00:22:20.040 Topmotive is a little bit more flexible 00:22:20.040 --> 00:22:23.240 in terms of generic articles, allows a little bit more there. 00:22:24.120 --> 00:22:27.520 This helps us to structure our products 00:22:27.840 --> 00:22:32.000 more finely in our category tree, 00:22:33.600 --> 00:22:35.920 which is of course advantageous for maintenance in the PIM 00:22:35.920 --> 00:22:38.640 and later for searching in the online store. 00:22:38.880 --> 00:22:43.560 Furthermore, of course, we need some parameters or 00:22:44.640 --> 00:22:47.160 criteria in terms of "Who are our ETGs?". 00:22:47.160 --> 00:22:48.240 We don't have just one. 00:22:48.240 --> 00:22:51.120 These must also be maintained in the system for the subsequent ones, 00:22:51.120 --> 00:22:52.800 so that the subsequent systems 00:22:53.000 --> 00:22:56.880 naturally know, "Okay, which product now belongs to which ETG". 00:22:56.880 --> 00:22:59.560 It all has to be numbered, given IDs. 00:22:59.960 --> 00:23:01.720 We can do all that in the PIM. 00:23:02.280 --> 00:23:06.240 The suppliers of each ETG, certainly overlap 00:23:06.560 --> 00:23:09.840 as far as suppliers are concerned, but each also has its own. 00:23:10.080 --> 00:23:14.440 We can also maintain these in the PIM in ANTEROS and then assign them 00:23:14.440 --> 00:23:15.320 to the corresponding ETG. 00:23:15.760 --> 00:23:18.640 For example, but also - as far as the store is concerned - 00:23:19.880 --> 00:23:22.080 the topic of priority lists. 00:23:23.120 --> 00:23:24.200 The ETG in Germany says 00:23:24.200 --> 00:23:27.840 "My priorities are brands one, two, three, four, five". 00:23:28.520 --> 00:23:32.080 The colleague in Italy, however, would like to have six, seven and eight in first place. 00:23:32.600 --> 00:23:36.880 And we can also set this in relation to the web store in ANTEROS. 00:23:37.280 --> 00:23:41.160 Yes, where there is data, data quality is always an issue. 00:23:43.200 --> 00:23:47.160 As you can imagine, it’s hard with just an ERP, 00:23:47.280 --> 00:23:50.840 well I wouldn’t know an ERP that could do this by itself. 00:23:51.680 --> 00:23:53.120 Everyone just says or 00:23:55.120 --> 00:23:58.120 brings it up: "We have poor data quality". 00:23:58.120 --> 00:23:59.920 Yes, where? What is it? 00:23:59.920 --> 00:24:00.760 You don't know. 00:24:00.760 --> 00:24:05.400 Only using ERP it is very difficult to find this out or 00:24:05.400 --> 00:24:06.520 to filter it out. 00:24:06.640 --> 00:24:08.200 With ANTEROS it is simple 00:24:08.920 --> 00:24:10.640 in the end result. 00:24:11.000 --> 00:24:15.440 Of course, you have to know what you're doing, but there are all kinds of settings 00:24:15.760 --> 00:24:18.480 that have no limits and you can 00:24:18.920 --> 00:24:22.400 put together the data check, the quality check, according to your needs. 00:24:22.800 --> 00:24:25.480 That means you don't get something standardized, 00:24:25.480 --> 00:24:27.080 "These are our data checks. 00:24:27.200 --> 00:24:31.000 Make sure that you can handle it," but something that is 00:24:31.480 --> 00:24:33.480 really tailored to your personal needs. 00:24:33.760 --> 00:24:36.520 Data testing once with the quality reports 00:24:36.520 --> 00:24:38.320 that you can create for yourself. 00:24:38.320 --> 00:24:42.600 And those quality reports are then displayed in a dashboard. 00:24:43.240 --> 00:24:46.720 So that you can see at a glance 00:24:46.720 --> 00:24:49.440 "okay, where's it stuck, what issues do I need to work on?". 00:24:49.440 --> 00:24:52.920 All of that can then be easily seen on a dashboard. 00:24:53.640 --> 00:24:58.200 Yes, here we have an example of an ANTEROS dashboard. 00:24:59.560 --> 00:25:03.440 The advantage of a dashboard is that 00:25:03.640 --> 00:25:07.560 you can see the topics that you defined yourself. 00:25:07.960 --> 00:25:12.640 What do you want to work on and the quality deficits 00:25:13.960 --> 00:25:19.640 are very clear due to the color coding, which we can see very well here. 00:25:19.640 --> 00:25:22.360 You have green for okay, red for not okay, 00:25:22.360 --> 00:25:25.960 and you immediately see okay, you have to do something about it. 00:25:26.240 --> 00:25:30.240 Every user has the possibility to create quality reports for themselves, 00:25:30.680 --> 00:25:32.840 depending on how this is divided up in the company. 00:25:32.840 --> 00:25:34.560 One of them has to work on axles, 00:25:34.560 --> 00:25:38.480 while the other focuses more on engines. 00:25:38.480 --> 00:25:40.000 So everyone can say for themselves: 00:25:40.000 --> 00:25:43.760 "Okay, I'm going to create a quality report specifically for this topic. 00:25:44.200 --> 00:25:48.040 What data is important for engine parts or for axle parts? 00:25:48.680 --> 00:25:52.600 And based on this, I create my own personal quality report. 00:25:53.000 --> 00:25:57.040 But you also have the option of creating a global quality report 00:25:57.160 --> 00:26:00.000 if you think, okay, this is interesting 00:26:00.600 --> 00:26:02.920 for everyone who has access to ANTEROS. 00:26:02.920 --> 00:26:05.600 So it is kept relatively flexible. 00:26:05.680 --> 00:26:08.160 How do you do these quality checks and 00:26:08.160 --> 00:26:10.360 what are the possibilities? 00:26:10.880 --> 00:26:15.800 On the one hand, there is the issue of search queries, for example "article without picture". 00:26:16.040 --> 00:26:18.320 I would like to see all the articles without a picture, 00:26:18.320 --> 00:26:20.720 because having no picture doesn't sell or sells poorly, 00:26:22.240 --> 00:26:23.840 or "article without dimensions". 00:26:23.840 --> 00:26:26.840 This is also 00:26:27.000 --> 00:26:29.600 not received well in the online store, if there is just a picture, 00:26:29.600 --> 00:26:32.320 but you don't have any other data. 00:26:32.840 --> 00:26:36.400 That's why this would be an easy way to filter out 00:26:36.400 --> 00:26:40.480 articles or to highlight them in the dashboard. 00:26:40.720 --> 00:26:44.440 Furthermore, of course, the possibility of linking 00:26:44.880 --> 00:26:46.200 these search queries with each other. 00:26:46.400 --> 00:26:50.600 For example: "Show me all articles without a picture, but only the active ones", 00:26:50.600 --> 00:26:54.520 i.e. the ones that are exported, because the ones that have expired 00:26:56.480 --> 00:26:58.960 or disappeared from the market, those I don't have to work on, 00:26:58.960 --> 00:27:00.200 hence only active ones. 00:27:00.200 --> 00:27:03.280 Or you can go one step further and link that 00:27:03.960 --> 00:27:06.400 to another quality level and say "I want all 00:27:06.400 --> 00:27:10.440 active items but only those without a picture and also without dimensions". 00:27:10.520 --> 00:27:13.120 So where both apply, that is also possible. 00:27:13.360 --> 00:27:17.240 So just like the rest of ANTEROS very flexible. 00:27:18.560 --> 00:27:21.320 Then the checking via quality levels. 00:27:21.320 --> 00:27:24.720 What we had just mentioned, the data fields 00:27:24.840 --> 00:27:27.840 can be checked via these quality levels. 00:27:28.720 --> 00:27:32.240 Here at a small example "Online store-ready". 00:27:32.480 --> 00:27:38.200 Here perhaps a more concrete example: The data conditions or quality level 00:27:38.200 --> 00:27:39.880 "Correct service article". 00:27:40.240 --> 00:27:43.280 Here, too, you can see the pencils, 00:27:43.280 --> 00:27:46.280 meaning you can compile these data conditions yourself. 00:27:46.280 --> 00:27:47.480 So you don’t 00:27:48.320 --> 00:27:52.160 have to depend on any standards, but it’s really flexible again. 00:27:53.320 --> 00:27:55.480 You determine for yourself 00:27:56.080 --> 00:27:59.360 "what constitutes a correct service item in my eyes". 00:27:59.760 --> 00:28:00.720 It's now of course 00:28:01.240 --> 00:28:03.520 an internal designation, a service article, 00:28:04.400 --> 00:28:08.280 not for the general public, but for us the service article was, 00:28:08.280 --> 00:28:11.360 or the service article had to have the following conditions: 00:28:11.840 --> 00:28:15.880 Firstly, the code of the article type – a one had to be set. 00:28:17.080 --> 00:28:23.080 Furthermore, it has to, is not allowed to have a parameter in the Storage Dimensions area. 00:28:24.760 --> 00:28:26.400 It had to have an amount, 00:28:26.400 --> 00:28:30.320 that is a Euro amount and it had to have at least the name 00:28:30.320 --> 00:28:32.360 in German, so an item description. 00:28:32.360 --> 00:28:36.360 Then this was a service article and only if these conditions were fulfilled, 00:28:36.360 --> 00:28:38.280 this article is also extracted for 00:28:38.280 --> 00:28:41.680 the export and passed on to the system, 00:28:42.480 --> 00:28:44.080 which is the purpose 00:28:45.680 --> 00:28:48.360 of data quality, so that no 00:28:49.000 --> 00:28:51.920 bad data gets into other systems. 00:28:52.560 --> 00:28:55.840 Yes, as mentioned, via Edit-Icon you can refer 00:28:55.840 --> 00:28:58.720 to these corresponding data fields. 00:28:59.280 --> 00:29:01.800 Also these are not fixed, they are freely expandable. 00:29:01.800 --> 00:29:06.640 So every data field you use in ANTEROS for properties, 00:29:07.160 --> 00:29:11.560 you can also use here again to create a quality level. 00:29:13.440 --> 00:29:14.720 Perhaps worth mentioning, 00:29:15.400 --> 00:29:18.920 there are different operations on the quality levels. 00:29:19.640 --> 00:29:21.600 That is, we have here: 00:29:21.600 --> 00:29:26.760 "is equal to", "is present", "is not present", "is greater than", "is less than". 00:29:26.880 --> 00:29:29.400 So here too, high flexibility. 00:29:30.280 --> 00:29:34.360 Cascading, multiple citation or 00:29:34.360 --> 00:29:36.920 linking of quality levels is also possible here. 00:29:37.400 --> 00:29:41.280 We previously had the example "Online store-ready". 00:29:41.280 --> 00:29:46.240 There, only the quality level VPE was available as a condition. 00:29:46.480 --> 00:29:49.920 Of course, this is not sufficient to present an article in an online store. 00:29:51.480 --> 00:29:54.320 Therefore, we link further 00:29:55.840 --> 00:29:58.600 data conditions or quality levels 00:30:00.200 --> 00:30:03.680 by saying "Online store-ready" means 00:30:03.680 --> 00:30:06.520 that a packaging unit must be available. 00:30:06.760 --> 00:30:09.880 There must be at least one name or generic item 00:30:09.880 --> 00:30:11.760 to have an item name 00:30:12.120 --> 00:30:14.280 and of course it must be an active item. 00:30:14.600 --> 00:30:16.480 Items that are dropped without replacement 00:30:16.920 --> 00:30:19.920 are not something we want to present in the online store anymore, unless 00:30:20.520 --> 00:30:22.280 they still have considerable stock, of course. 00:30:23.040 --> 00:30:24.880 Which in the best case is not the case. 00:30:25.160 --> 00:30:29.040 In the bottom area, here in the bottom area, you can see 00:30:29.040 --> 00:30:33.920 the individual quality levels, which are just linked 00:30:34.880 --> 00:30:38.160 in the Relations tab, at the quality level 00:30:38.320 --> 00:30:40.800 and this can also be flexibly expanded, 00:30:41.960 --> 00:30:44.200 as in the previous examples. 00:30:44.520 --> 00:30:45.600 As mentioned at the beginning, 00:30:46.480 --> 00:30:49.280 the PIM data is used for various purposes. 00:30:49.280 --> 00:30:51.760 So we don't just maintain the data in ANTEROS 00:30:51.760 --> 00:30:54.640 for the sake of having it maintained in ANTEROS, but the data is used 00:30:54.640 --> 00:30:57.000 in various systems, 00:30:57.640 --> 00:31:01.000 including our ERP system, the web store 00:31:01.480 --> 00:31:04.560 and the TecDoc and Topmotive dealer portals. 00:31:05.560 --> 00:31:07.120 Perhaps briefly on 00:31:07.200 --> 00:31:13.040 the ERP system - at AMG, it's Dynamics 365 from Microsoft. 00:31:13.920 --> 00:31:17.440 This system was set up for us via the Azure Cloud 00:31:17.480 --> 00:31:20.520 and the interface from the PIM 00:31:20.520 --> 00:31:23.680 to the ERP runs via the Azure services. 00:31:24.200 --> 00:31:26.240 This is where the data is then transferred. 00:31:26.720 --> 00:31:28.520 We always run the transfer of data 00:31:30.000 --> 00:31:34.240 at night for all newly created items 00:31:34.480 --> 00:31:38.480 or changed products. 00:31:38.480 --> 00:31:40.680 So we have a night run. 00:31:41.760 --> 00:31:46.080 This is started every evening at 8:00 p.m. and all changes 00:31:46.800 --> 00:31:50.200 to product data are then transferred to the ERP. 00:31:50.200 --> 00:31:52.440 So it's more or less a delta update. 00:31:52.480 --> 00:31:55.720 Of course, you also have to set up the interface, 00:31:56.000 --> 00:31:57.360 it's not just there. 00:31:57.520 --> 00:32:02.560 ANTEROS also has a configuration menu or 00:32:03.800 --> 00:32:07.160 a configurator to configure the interface accordingly. 00:32:07.360 --> 00:32:12.160 The whole thing in XML format is of course then specified by MS Dynamics. 00:32:12.360 --> 00:32:17.400 Also here Mr. Bernad of INCONY supported us very well. 00:32:17.760 --> 00:32:19.200 Of course, for people 00:32:19.200 --> 00:32:22.880 who have to deal with this on a daily basis, this is no big deal. 00:32:23.240 --> 00:32:26.880 For people who were more in the master data area and have nothing 00:32:27.080 --> 00:32:28.800 or very little to do with it, 00:32:29.680 --> 00:32:32.120 of course we had to give them a hand. 00:32:32.400 --> 00:32:33.240 Nevertheless, 00:32:34.680 --> 00:32:36.560 in retrospect, 00:32:36.560 --> 00:32:40.040 it was quite easy to set up this interface. 00:32:40.280 --> 00:32:42.760 You can specify here which files or 00:32:42.760 --> 00:32:46.200 which fields per file you need, which tags per field, 00:32:46.440 --> 00:32:51.120 so that we were also able to design this ourselves after instructions 00:32:51.120 --> 00:32:55.160 or after one-time instructions from Mr. Bernad. 00:32:55.360 --> 00:32:58.080 Then we have the interface to our online store. 00:32:58.600 --> 00:33:01.200 The online store is one of our own developments. 00:33:02.080 --> 00:33:04.240 The interface from the PIM to the online store 00:33:05.960 --> 00:33:11.200 is based on a TXT format, similar to the format of TecDoc or Topmotive, 00:33:11.800 --> 00:33:14.000 so the TAF format. 00:33:14.280 --> 00:33:18.640 We have fixed field lengths here and also here we could flexibly define 00:33:19.920 --> 00:33:23.000 which data, which properties, 00:33:23.680 --> 00:33:28.480 which additional information do we want to present in the online store? 00:33:28.960 --> 00:33:32.600 Here, too, the interface could then be created flexibly. 00:33:32.880 --> 00:33:36.720 Then, of course, we have the export to the dealer portals. 00:33:36.720 --> 00:33:38.320 One of them is TecAlliance. 00:33:38.680 --> 00:33:42.000 For all those who are perhaps not active in the automotive sector: 00:33:43.640 --> 00:33:47.640 TecDoc or TecAlliance is an association of 00:33:48.240 --> 00:33:51.880 multiple manufacturers and dealers in the automotive industry. 00:33:53.400 --> 00:33:55.080 The whole thing goes back 25 00:33:55.080 --> 00:33:59.040 to 30 years; is now, 00:33:59.880 --> 00:34:04.640 I'll say, one of the industry leaders or the industry leader. 00:34:05.080 --> 00:34:06.600 Depending on who you ask, of course. 00:34:06.720 --> 00:34:12.720 Here, manufacturers and suppliers basically feed in their data on the products. 00:34:13.080 --> 00:34:16.280 TecDoc uses this data to create a catalog 00:34:16.600 --> 00:34:21.000 that workshops can use to identify 00:34:21.720 --> 00:34:25.840 products and then order them directly from this catalog. 00:34:26.320 --> 00:34:28.400 Here, too, we will set up an interface. 00:34:29.120 --> 00:34:31.800 As I said, we have a subsidiary 00:34:31.800 --> 00:34:35.880 that acts as a manufacturer and will therefore also 00:34:36.600 --> 00:34:40.480 transmit data to TecDoc in the corresponding TAF format, 00:34:40.880 --> 00:34:43.320 and we will also set up the interface here, 00:34:43.320 --> 00:34:45.680 which is actually part of the ANTEROS standard. 00:34:45.800 --> 00:34:50.320 So import, export, TAF format is part of the ANTEROS standard. 00:34:50.840 --> 00:34:55.080 Yes, the DVSE dealer portal is very similar. 00:34:55.440 --> 00:35:01.240 TecDoc data is also used there, but you have the option 00:35:01.240 --> 00:35:05.680 of feeding in additional data as a supplier or manufacturer. 00:35:06.160 --> 00:35:08.960 But the whole thing also happens in TAF format, 00:35:09.520 --> 00:35:14.040 which is also part of the ANTEROS standard, 00:35:14.440 --> 00:35:18.800 as mentioned before, and we will definitely set up an interface in this direction as well. 00:35:19.680 --> 00:35:21.600 Yes, to sum up, 00:35:22.000 --> 00:35:25.240 the introduction of the PIM system was very successful. 00:35:26.000 --> 00:35:29.360 When I think back on the time, it was a lot of fun. 00:35:29.360 --> 00:35:31.800 The enthusiasm was very high on both sides. 00:35:32.600 --> 00:35:34.200 There is simply no other way to put it. 00:35:34.400 --> 00:35:37.840 Efficient data maintenance with ANTEROS or in ANTEROS: 00:35:38.440 --> 00:35:43.000 We currently have almost 700,000 products that we can maintain. 00:35:44.560 --> 00:35:47.160 Supplier data is easy to import, 00:35:47.160 --> 00:35:50.600 due to the fact that the TAF format is standard in ANTEROS. 00:35:51.360 --> 00:35:54.800 You can create your own brands, maintain your own products, 00:35:55.240 --> 00:35:58.680 very intuitive user-friendly interface. 00:35:59.680 --> 00:36:04.320 And you are not limited to data from third party suppliers, 00:36:04.320 --> 00:36:06.280 that you only use and keep 00:36:08.120 --> 00:36:13.000 this one standard format, but you can expand it flexibly with ANTEROS. 00:36:13.440 --> 00:36:16.040 We have seen the data quality in the dashboards. 00:36:16.040 --> 00:36:18.840 We can improve them in a targeted way, not scattergun - 00:36:18.840 --> 00:36:22.880 just do a little bit of something everywhere, but instead, 00:36:22.880 --> 00:36:26.280 thanks to previous settings, you can see specifically "Okay, where is it stuck at the moment, 00:36:27.120 --> 00:36:30.680 where is data missing, where are images missing, what can be done better?" 00:36:30.840 --> 00:36:34.040 You can assign the corresponding product groups to employees 00:36:34.040 --> 00:36:36.640 or teams, who then work on them. 00:36:36.760 --> 00:36:41.120 All this is also possible with the workflow in ANTEROS. 00:36:41.240 --> 00:36:43.560 Interfaces, as we have just seen, 00:36:44.560 --> 00:36:45.920 are easy to set up. 00:36:46.520 --> 00:36:48.440 You have different options. 00:36:49.000 --> 00:36:51.480 ANTEORS is so flexible that it can 00:36:51.560 --> 00:36:55.040 also jump onto different ERP systems. 00:36:55.320 --> 00:36:59.000 In our case, it was Microsoft 365, 00:36:59.640 --> 00:37:02.040 and all in all, you really have to say 00:37:02.040 --> 00:37:06.000 that this agile project approach that we had enabled us 00:37:06.000 --> 00:37:09.600 to achieve results very quickly, to make progress very quickly. 00:37:10.440 --> 00:37:14.320 When I think about the team size, at least from our side, 00:37:15.000 --> 00:37:18.640 we were able to complete the project faster than originally planned, 00:37:18.960 --> 00:37:22.680 which is of course also thanks to the competence and motivation 00:37:22.720 --> 00:37:24.280 of the INCONY team. 00:37:24.720 --> 00:37:27.040 Again, a big thank you. 00:37:27.040 --> 00:37:32.000 I had a great time and yes, that's all from me. 00:37:32.000 --> 00:37:34.720 Yes, then I'll start with the first questions. 00:37:34.720 --> 00:37:38.280 I have made a few notes and the first question would be: 00:37:38.520 --> 00:37:42.200 Now you have successfully introduced ANTEROS, you have some products in there 00:37:42.800 --> 00:37:46.840 and there are several users - 00:37:46.840 --> 00:37:51.240 do they all use the same articles with you? 00:37:53.720 --> 00:37:54.360 Yes, and no. 00:37:54.360 --> 00:37:57.360 We have split it up a bit. 00:37:57.520 --> 00:38:01.960 We have a central product range, which is maintained here in Wuppertal, 00:38:01.960 --> 00:38:05.880 and this is made available to all ETGs 00:38:05.880 --> 00:38:08.160 and national companies. 00:38:08.560 --> 00:38:14.400 They can only look at it, but they are not allowed to change anything in it, which is possible 00:38:14.840 --> 00:38:18.320 thanks to the flexible role administration that ANTEROS offers. 00:38:18.960 --> 00:38:22.400 In addition, each national company can add 00:38:22.400 --> 00:38:27.160 the assortment that is relevant for its country or its market. 00:38:27.520 --> 00:38:31.040 However, the colleagues are then also responsible for their own data. 00:38:31.520 --> 00:38:35.360 This means that the data is maintained by them, but not by us. 00:38:35.360 --> 00:38:39.200 We can see the data, and we also provide a framework 00:38:39.200 --> 00:38:43.360 of what we would like to have so that the quality is consistent, 00:38:44.200 --> 00:38:48.840 but the maintenance is then the responsibility of the colleagues in the respective company. 00:38:48.880 --> 00:38:53.480 Okay, that probably also means that if there are country assortments 00:38:54.080 --> 00:38:56.920 and you are now setting up stores, then they are probably 00:38:56.920 --> 00:39:00.600 country-specific, which means that this is also taken into account 00:39:00.920 --> 00:39:04.240 in the PIM evaluation for the store, or what does that look like in concrete terms? 00:39:04.840 --> 00:39:07.840 Yes, there too, of course, that is taken into account. 00:39:08.440 --> 00:39:11.560 Fortunately, this is also possible with ANTEROS. 00:39:11.920 --> 00:39:16.080 Here, too, we have various setting options so that we can say 00:39:16.920 --> 00:39:18.080 per country or 00:39:18.080 --> 00:39:21.440 per national company: " A central assortment 00:39:21.440 --> 00:39:23.880 you get in any case, whether you want it or not. 00:39:23.880 --> 00:39:27.720 That's just the way it is." Plus their own assortment, 00:39:27.720 --> 00:39:31.400 which they have created for the market. 00:39:31.640 --> 00:39:35.120 This is then designed on the basis of IDs, of the brands 00:39:35.600 --> 00:39:38.840 in connection with ETGs, which I explained earlier, which we 00:39:38.840 --> 00:39:43.280 can create cleanly in ANTEROS, so that 00:39:43.280 --> 00:39:48.080 each country has the articles it needs in its store. 00:39:48.680 --> 00:39:49.840 Okay, perfect. 00:39:50.320 --> 00:39:52.160 Then another question. 00:39:52.160 --> 00:39:55.160 It is about the future prospects 00:39:55.600 --> 00:39:58.600 of ANTEROS at BPW Aftermarket. 00:39:58.920 --> 00:40:01.040 What do you see there? 00:40:01.040 --> 00:40:03.480 What are your future plans for ANTEROS? 00:40:03.480 --> 00:40:05.280 Yes, quite a lot. Quite a lot. 00:40:05.280 --> 00:40:06.880 At the beginning, we already 00:40:06.880 --> 00:40:10.240 told you about our complete transformation of our IT landscape. 00:40:10.480 --> 00:40:13.320 That included rolling out ERP and web stores, and so on. 00:40:13.800 --> 00:40:17.880 The same applies to our PIM as the leading system. 00:40:18.440 --> 00:40:23.760 We have a roadmap that says until 2026, at least for the time being, 00:40:24.560 --> 00:40:27.320 that we will probably launch 14 to 16 00:40:27.320 --> 00:40:30.800 more spare parts companies 00:40:30.800 --> 00:40:34.840 with our IT landscape and will 00:40:36.240 --> 00:40:39.080 also introduce and use the PIM there. 00:40:39.080 --> 00:40:40.560 And why are we doing this? 00:40:41.960 --> 00:40:44.880 As a master data person, you always like to have a bit of an urge to 00:40:44.880 --> 00:40:46.240 standardize and harmonize. 00:40:46.520 --> 00:40:47.320 That is to say, 00:40:47.320 --> 00:40:50.520 as we have already described, PIM is the leading system 00:40:51.080 --> 00:40:54.680 and perhaps as a nice little phrase this SISO principle, 00:40:54.680 --> 00:40:58.280 you may know, "Shit In Shit Out", if we invite 00:40:58.280 --> 00:41:01.840 bad, defective and incomplete data from the outset, 00:41:02.240 --> 00:41:05.080 this of course also hinders our ERP in the next moment, 00:41:06.520 --> 00:41:09.920 where logically the processes in the supply chain from goods receipt 00:41:09.920 --> 00:41:12.680 to goods issue would not run as smoothly as if, 00:41:12.960 --> 00:41:16.280 on the other hand, we had complete and hopefully 00:41:16.280 --> 00:41:19.720 also qualitatively reasonable master data in our PIM. 00:41:19.840 --> 00:41:22.840 And that, of course, company by company, 00:41:24.200 --> 00:41:25.400 so that we ultimately 00:41:25.880 --> 00:41:30.320 have a really rounded data flow, which should 00:41:30.320 --> 00:41:33.320 ultimately support the processes, right up to the online store, 00:41:33.720 --> 00:41:37.520 so that the customer, our B2B customer, can then really see everything 00:41:37.800 --> 00:41:40.800 in the online store at a glance, everything they expect from the product. 00:41:41.000 --> 00:41:41.480 Okay. 00:41:42.040 --> 00:41:42.960 Yes, that is the plan. 00:41:43.000 --> 00:41:44.920 Well then you have a lot left to do. 00:41:44.920 --> 00:41:46.440 That's good, we'll gladly join in.