WEBVTT 00:00:00.133 --> 00:00:01.766 What are the advantages that we have? 00:00:01.766 --> 00:00:03.766 But most importantly, and I actually place 00:00:03.766 --> 00:00:07.933 this first, for our customers and for our partners? 00:00:07.999 --> 00:00:09.733 These can be divided into three areas. 00:00:09.733 --> 00:00:14.033 Firstly, what does ANTEROS do at Motul? What makes it special? 00:00:14.033 --> 00:00:15.933 What are the benefits that result from it? 00:00:15.933 --> 00:00:19.533 And finally, what in the market at the interface to the customer 00:00:20.066 --> 00:00:21.733 is particularly special? 00:00:21.766 --> 00:00:24.433 To focus on ANTEROS: We have the topic of 00:00:24.499 --> 00:00:27.466 international care, as just mentioned. 00:00:27.466 --> 00:00:29.266 This can be quite complex. 00:00:29.266 --> 00:00:31.866 There are many different people involved, 00:00:32.499 --> 00:00:35.233 who all have their own individual work to do, so to speak. 00:00:35.233 --> 00:00:38.866 And from this, meaningful, valid overall work 00:00:38.866 --> 00:00:41.766 is created, which can be communicated to the market. 00:00:42.666 --> 00:00:46.399 The major advantage is that the whole thing is just very easy to use. 00:00:46.399 --> 00:00:49.499 That means creating the structures internally, that's not difficult, 00:00:49.933 --> 00:00:53.733 because the effort, however many people may be involved in it, 00:00:53.933 --> 00:00:56.033 the whole thing is distributed in small chunks 00:00:56.033 --> 00:00:57.733 on different shoulders 00:00:57.733 --> 00:01:00.399 and the responsibilities are also clearly regulated accordingly. 00:01:01.566 --> 00:01:04.033 We have the benefit of standardized data, 00:01:04.366 --> 00:01:07.666 meaning that we don't have to tell one customer one thing and tell another customer another thing, 00:01:07.866 --> 00:01:10.966 depending on who is located where in the world at any given time. 00:01:11.066 --> 00:01:13.733 Based on this data from the PIM, 00:01:13.999 --> 00:01:17.466 we have one truth that we communicate to the outside world, 00:01:18.033 --> 00:01:19.333 and we can be sure 00:01:19.333 --> 00:01:21.733 that the information that reaches the customer is correct. 00:01:22.099 --> 00:01:25.032 And the customer can be just as sure of this and is grateful for it, 00:01:25.266 --> 00:01:28.832 because they definitely don't have that security with every provider, 00:01:28.832 --> 00:01:32.332 not with every supplier, and certainly not 00:01:32.332 --> 00:01:33.732 with the data involved. 00:01:35.332 --> 00:01:37.799 We mentioned the topic of workflows, roles and rights 00:01:38.566 --> 00:01:41.566 with the processes that result from them, 00:01:42.366 --> 00:01:44.432 which then lead to the high data quality. 00:01:45.066 --> 00:01:45.966 And finally, 00:01:45.966 --> 00:01:47.432 I mentioned very briefly 00:01:47.432 --> 00:01:50.699 the distribution of these tasks across various people, 00:01:50.766 --> 00:01:53.466 and if this is done efficiently, 00:01:53.699 --> 00:01:56.299 then we can speak of a significant time saving 00:01:56.566 --> 00:01:59.499 compared to the situation in which 00:01:59.499 --> 00:02:02.299 the data would otherwise be maintained in the conventional way. 00:02:04.132 --> 00:02:05.766 Thanks to the good data quality, 00:02:05.766 --> 00:02:09.432 we hardly have anything in terms of complaints coming our way. 00:02:09.732 --> 00:02:12.999 And if they do, simple algorithms, 00:02:13.199 --> 00:02:15.366 simple plausibility checks 00:02:15.999 --> 00:02:19.132 can be used to determine the quality of the data in the important areas. 00:02:19.966 --> 00:02:23.166 Data gaps are automatically detected by ANTEROS 00:02:23.532 --> 00:02:26.266 and plausible values can be easily found out 00:02:26.266 --> 00:02:28.932 based on the experience we have in handling the data, 00:02:29.532 --> 00:02:32.799 so we are able to offer a very high quality 00:02:33.066 --> 00:02:35.099 and thus satisfy the customer. 00:02:35.399 --> 00:02:38.532 And a customer who is satisfied is happy to stay with us 00:02:38.732 --> 00:02:41.666 and we are happy to work with them on a long-term basis. 00:02:41.966 --> 00:02:42.732 At that point, 00:02:42.732 --> 00:02:46.199 the result is a win-win situation for both sides. 00:02:46.299 --> 00:02:49.232 The interfaces that ANTEROS offers, those are a big plus 00:02:49.232 --> 00:02:53.399 at Motul, whether it's because of the safety data sheets, 00:02:53.465 --> 00:02:56.932 whether it's also because of forward direction of the various publications 00:02:56.932 --> 00:02:58.199 that we run. 00:02:59.132 --> 00:03:02.599 Everything works smoothly, these interfaces are standardized, 00:03:02.599 --> 00:03:05.865 the data only has to be maintained once, 00:03:06.465 --> 00:03:10.199 and we can return to the extremely important point 00:03:10.199 --> 00:03:11.265 of high data quality. 00:03:11.665 --> 00:03:13.465 Because if the data quality is not right, 00:03:13.565 --> 00:03:16.799 then the whole thing comes back to us as a company two and three times over. 00:03:17.399 --> 00:03:20.999 We have to do more because of this, and at the end of the day 00:03:21.199 --> 00:03:25.399 we have to deal with the issue that, at some point, customers might want to jump ship. 00:03:25.799 --> 00:03:28.665 If every piece of information that we deliver to the customer 00:03:28.665 --> 00:03:31.632 first has to be scrutinized, sorted and processed 00:03:31.632 --> 00:03:35.232 at the customer's premises, then in this day and age, 00:03:35.865 --> 00:03:39.065 when data is the basis for business, that is not something 00:03:39.065 --> 00:03:41.932 the customer is particularly interested in. 00:03:42.065 --> 00:03:43.399 The diversity of usage 00:03:43.399 --> 00:03:46.332 that results is especially important in this day and age, 00:03:46.432 --> 00:03:47.732 everything is becoming more digital. 00:03:47.732 --> 00:03:51.865 We are working on many ideas regarding new portals and so on and so forth. 00:03:51.865 --> 00:03:55.765 Where this data is applied is that the very basis 00:03:55.765 --> 00:03:57.965 that offers us a very, very big advantage, 00:03:58.265 --> 00:04:02.732 because to a certain extent with a new portal, new store, 00:04:02.732 --> 00:04:06.299 whatever, which we would now launch, 00:04:06.299 --> 00:04:09.932 it would actually only need a one-time interface configuration, 00:04:09.932 --> 00:04:13.032 but that can actually be adopted half-finished from somewhere else. 00:04:13.298 --> 00:04:15.865 And now, the whole thing runs fully automatically. 00:04:16.265 --> 00:04:20.332 At most, we are talking about a very few work days. 00:04:20.332 --> 00:04:23.432 In some cases we are talking about only a few hours of work, in which it is necessary 00:04:24.065 --> 00:04:26.598 to bring about some form of configuration. 00:04:26.865 --> 00:04:27.932 And then the solution is written. 00:04:27.932 --> 00:04:29.832 Then the solution can be rolled out. 00:04:29.832 --> 00:04:32.598 Then there is no need for time-consuming testing. 00:04:33.632 --> 00:04:37.198 There is no need for lengthy staging before a solution can be published. 00:04:37.432 --> 00:04:40.798 Rather, because we know that the quality of ANTEROS is good, 00:04:41.065 --> 00:04:43.232 that the interfaces operate reliably, 00:04:43.565 --> 00:04:46.365 we can also be sure that any new publication 00:04:46.365 --> 00:04:50.065 that we tackle can be realized within the shortest possible time. 00:04:50.432 --> 00:04:53.832 And short time means short time to market for us. 00:04:54.198 --> 00:04:55.332 This means that new ideas, 00:04:55.332 --> 00:04:58.832 which we would like to implement in connection with perhaps new products, 00:04:59.665 --> 00:05:01.898 make it to the market quickly. 00:05:02.698 --> 00:05:05.965 We don't have any obstacles that we have to overcome, but we 00:05:05.965 --> 00:05:08.998 manage to take the momentum that we have from product development 00:05:08.998 --> 00:05:11.732 to the customer, to the market. 00:05:12.865 --> 00:05:15.265 And ultimately, the faster we are, 00:05:15.265 --> 00:05:16.998 the more we might have the opportunity 00:05:16.998 --> 00:05:20.598 to conquer the market with our new product idea, with our 00:05:21.132 --> 00:05:24.298 new concept that we are rolling out, and not leave so much pie for the 00:05:24.532 --> 00:05:28.198 other competitors in the market. 00:05:29.998 --> 00:05:30.932 Time savings are there, 00:05:30.932 --> 00:05:33.132 as I said, and the main keyword that we have to mention 00:05:34.398 --> 00:05:36.331 and that I would like to address lastly, 00:05:36.331 --> 00:05:39.965 which makes the customers happy, is the retrievability of the data. 00:05:40.698 --> 00:05:42.965 Because that is a major concern that is becoming more and more prevalent. 00:05:42.965 --> 00:05:46.798 The customers themselves are all very eager 00:05:46.798 --> 00:05:48.931 to have high quality data. 00:05:48.931 --> 00:05:53.231 In many industries, customers have risen to such professional levels 00:05:53.231 --> 00:05:58.165 that they virtually no longer need to be considered as part of a specific industry, 00:05:58.165 --> 00:06:00.665 but can be seen as IT or logistics companies 00:06:00.665 --> 00:06:02.965 within the industry. 00:06:03.365 --> 00:06:04.365 We see this with us 00:06:04.365 --> 00:06:07.731 in the automotive aftermarket industry, for example, with many wholesalers. 00:06:08.098 --> 00:06:12.865 And the more opportunities you offer them to proactively obtain data, 00:06:13.131 --> 00:06:16.765 the more they will use this opportunity to obtain data for themselves 00:06:16.765 --> 00:06:19.865 and will be grateful for every change that is communicated. 00:06:20.231 --> 00:06:24.331 And as long as the whole thing is done at a high, automated level, 00:06:24.631 --> 00:06:29.665 this requires no additional work for our company, for Motul. 00:06:29.665 --> 00:06:32.265 And in this case, this is actually a standard function 00:06:32.465 --> 00:06:35.531 that we now have with the help of ANTEROS. 00:06:40.131 --> 00:06:43.231 Motul stands for international lubricant expertise. 00:06:43.465 --> 00:06:47.265 Motul has been in business since 1853. 00:06:47.565 --> 00:06:50.465 The company headquarters are located near Paris. 00:06:51.165 --> 00:06:53.831 I am part of the branch here in Cologne 00:06:53.831 --> 00:06:57.031 that looks after Central and Eastern Europe. 00:06:58.064 --> 00:06:59.098 Motul lubricants 00:06:59.098 --> 00:07:03.664 are available in more than 160 countries. 00:07:04.298 --> 00:07:06.331 We have two main product categories. 00:07:06.531 --> 00:07:09.831 On the one hand, there are the Consumer Goods. 00:07:09.864 --> 00:07:14.598 These include, for example, engine oils, transmission oils, brake fluids. 00:07:14.664 --> 00:07:17.731 And on the other hand we have Industry Goods. 00:07:17.831 --> 00:07:21.164 These are, to a certain extent, specialty industrial applications, 00:07:21.798 --> 00:07:24.631 release agents, other auxiliaries and auxiliary materials 00:07:24.898 --> 00:07:29.731 that are used in industrial production processes. 00:07:30.764 --> 00:07:34.764 Due to the wide range of applications that we have in terms of products, 00:07:35.064 --> 00:07:38.564 there are also quite a few challenges 00:07:38.564 --> 00:07:43.864 in terms of how we transfer everything into our data structure and into our data world. 00:07:43.864 --> 00:07:47.031 How do we use ANTEROS at Motul? 00:07:47.098 --> 00:07:48.198 How is it structured? 00:07:48.198 --> 00:07:50.698 What is the basic idea behind it? 00:07:50.698 --> 00:07:55.064 And ANTEROS as a PIM, or product information management system, 00:07:55.131 --> 00:07:58.031 clearly serves as our central product maintenance. 00:07:58.098 --> 00:08:00.498 We need the product data for various purposes. 00:08:01.198 --> 00:08:05.364 These can be store applications, meaning front-end solutions 00:08:05.364 --> 00:08:08.531 that we offer our customers, for example in the B2C sector. 00:08:08.964 --> 00:08:12.464 They can be websites that are fed from the data. 00:08:13.064 --> 00:08:17.164 We're talking about numerous print publications that we create worldwide 00:08:17.164 --> 00:08:21.797 for the different markets with the different product portfolios. 00:08:21.897 --> 00:08:25.764 And finally, in terms of the connection to our customers, 00:08:25.864 --> 00:08:29.131 we are talking about many different exports that we generate from PIM, 00:08:29.397 --> 00:08:32.664 which are based on a very high level of automation, 00:08:32.964 --> 00:08:37.497 so that the data that we have can also flow into the customers' systems 00:08:37.497 --> 00:08:41.797 and be processed there accordingly and 00:08:41.797 --> 00:08:42.597 contribute to sales. 00:08:43.097 --> 00:08:46.431 With ANTEROS being the technological leader, we have 00:08:46.431 --> 00:08:50.497 the possibility of simple and efficient data maintenance. 00:08:50.564 --> 00:08:55.631 And for us as a supplier of lubricant products 00:08:55.631 --> 00:08:59.197 for vehicles, for example, we also have the very important option 00:08:59.397 --> 00:09:01.931 of being able to easily and flexibly control 00:09:02.031 --> 00:09:05.764 and assign vehicle compatibility in accordance with 00:09:05.831 --> 00:09:09.164 the many different manufacturer specifications. 00:09:10.531 --> 00:09:12.631 Interfaces to other systems 00:09:12.631 --> 00:09:16.631 are a very big concern, because no company has a single system. 00:09:17.131 --> 00:09:19.697 And especially if you then look out into the customer landscape 00:09:19.697 --> 00:09:24.231 or into the end user landscape, there are systems galore. 00:09:24.964 --> 00:09:26.131 It is important to us 00:09:26.131 --> 00:09:29.397 that we understand PIM as a central hub, so to speak, 00:09:30.331 --> 00:09:33.931 that the interfaces are available, which make data transfers possible, 00:09:34.531 --> 00:09:37.264 but also enable a simple, standardized export 00:09:37.497 --> 00:09:42.264 to other environments such as webshops, websites, etc. 00:09:43.697 --> 00:09:45.197 Through ANTEROS we have that capability 00:09:45.197 --> 00:09:49.064 with many different interface formats being supported. 00:09:49.364 --> 00:09:53.730 We do not by any means use all of those that ANTEROS generally offers. 00:09:53.730 --> 00:09:58.130 We concentrate on the interfaces that are currently important to us 00:09:58.130 --> 00:10:02.697 and also requested by our customers and the associated data formats. 00:10:02.797 --> 00:10:05.764 How is ANTEROS integrated into our IT landscape? 00:10:05.830 --> 00:10:09.164 We start, of course, with the master data, 00:10:09.164 --> 00:10:11.930 which is also generated in-house. 00:10:12.697 --> 00:10:15.430 This data is stored in our main ERP system. 00:10:15.430 --> 00:10:17.397 In this case, that is SAP. 00:10:17.497 --> 00:10:20.130 We have a small appendage 00:10:20.430 --> 00:10:24.130 due to the security-related data elements that we have. 00:10:25.064 --> 00:10:29.930 We use an industry provider called Quick FDS, in which safety data 00:10:29.930 --> 00:10:33.530 and relevant content is made available. 00:10:34.164 --> 00:10:45.830 Both then enter ANTEROS accordingly via standardized interfaces, which is the central hub, as we just mentioned, from which everything else basically comes. 00:10:45.997 --> 00:10:48.897 That means we have fed the data usage 00:10:48.897 --> 00:10:51.364 into the CMS systems of our websites. 00:10:51.764 --> 00:10:57.030 We have an automatic data transfer to the content for various webshops. 00:10:57.497 --> 00:11:00.930 And we also have dealer exports, 00:11:00.997 --> 00:11:05.330 whether in Excel format based on master data or 00:11:05.364 --> 00:11:08.897 in accordance with the special industry standard TecDoc. 00:11:08.997 --> 00:11:13.763 And last but not least, ANTEROS can easily give us printed catalogs, 00:11:13.763 --> 00:11:18.197 data sheets, and similar publications based on data 00:11:18.197 --> 00:11:21.730 stored in ANTEROS, both application specific 00:11:21.830 --> 00:11:24.463 and within a short period of time. 00:11:24.563 --> 00:11:27.430 At Motul, as we have just mentioned, 00:11:27.497 --> 00:11:32.563 we are talking about 160 countries in which the products are sold. 00:11:32.597 --> 00:11:34.563 This means that we have maintenance 00:11:34.563 --> 00:11:38.430 for global products that are sold all over the world. 00:11:38.463 --> 00:11:42.997 But we also have more locally specific products, which are sold very regionally, 00:11:42.997 --> 00:11:47.230 nationally, sometimes locally limited. 00:11:47.897 --> 00:11:51.863 We have various brands, that's how you could describe it in general terms. 00:11:51.863 --> 00:11:55.363 As I mentioned, we have Consumer Goods on the one hand. 00:11:55.697 --> 00:11:58.563 But on the other hand, we have the Industry Goods, 00:11:58.630 --> 00:12:01.597 and in a sense these are two brands that we distinguish, 00:12:02.363 --> 00:12:05.797 both from the attribution that we give to the products in each case, 00:12:05.797 --> 00:12:10.163 but also from the way in which we release the data and publications 00:12:10.163 --> 00:12:12.197 to the respective customer accordingly. 00:12:13.330 --> 00:12:17.030 When we think internationally and want to act internationally, 00:12:17.030 --> 00:12:21.563 we also talk about the fact that we need several languages and that 00:12:21.563 --> 00:12:26.963 even individual languages may differ from region to region. 00:12:27.597 --> 00:12:31.096 So we don't just work with all the languages that are internationally 00:12:31.096 --> 00:12:34.496 relevant for us, be it German, English, French, Italian, 00:12:34.496 --> 00:12:37.596 Spanish, Russian and so on and so forth, but in some cases we also talk 00:12:37.596 --> 00:12:41.830 about language packages that are different within themselves. 00:12:41.896 --> 00:12:45.796 For example, we have three different English-language packages 00:12:45.863 --> 00:12:48.730 so that we can target the content appropriately for each region and 00:12:48.996 --> 00:12:52.696 also cater to more region-specific language requirements. 00:12:53.030 --> 00:12:54.530 As you know, British English 00:12:54.530 --> 00:12:56.763 is a bit different from American English. 00:12:57.096 --> 00:13:01.496 And if we want to publish in international English, so to speak, 00:13:01.696 --> 00:13:05.130 we also have a different requirement for the provision of language, 00:13:05.130 --> 00:13:08.663 so that something like this can be understood correctly by the customer in the end. 00:13:08.663 --> 00:13:13.396 What is also added internationally is the technical aspect 00:13:13.763 --> 00:13:18.396 of the assignment of manufacturer approvals and thus possible uses. 00:13:19.130 --> 00:13:22.630 These are also issues that differ in part locally and regionally 00:13:22.630 --> 00:13:25.896 or can be maintained at a global level. 00:13:26.196 --> 00:13:27.363 And these are basically 00:13:27.363 --> 00:13:29.496 the challenges that arise from the fact that we 00:13:30.230 --> 00:13:34.063 cannot basically lump everything together, but have to deal with our data 00:13:34.063 --> 00:13:35.063 in a very region-specific 00:13:35.063 --> 00:13:38.696 way in some cases, and have to enrich it accordingly. 00:13:38.896 --> 00:13:42.530 And last but not least, we have to make this data available in downstream systems 00:13:42.530 --> 00:13:44.296 or to our customers. 00:13:45.063 --> 00:13:46.963 If we look at what is maintained where, 00:13:46.963 --> 00:13:51.163 then we have the issue of global data. 00:13:51.163 --> 00:13:53.663 These are what we call corporate products. 00:13:54.029 --> 00:13:58.263 These are the products that are offered worldwide and are normally 00:13:58.329 --> 00:14:02.429 maintained centrally from our headquarters in Paris. 00:14:02.796 --> 00:14:08.063 We also have the local products, where data maintenance 00:14:08.063 --> 00:14:11.329 takes place partly in the individual branches in our business units, 00:14:11.329 --> 00:14:13.663 or example here in Cologne. 00:14:14.063 --> 00:14:16.396 And we also have the two brands, 00:14:16.496 --> 00:14:18.529 which you can almost imagine as a matrix 00:14:18.529 --> 00:14:21.029 in another dimension. 00:14:21.029 --> 00:14:25.163 In other words, the global management of one brand, Consumer Goods, 00:14:25.263 --> 00:14:27.396 is done differently in some places in France 00:14:27.663 --> 00:14:29.663 than is the case with Industry Goods. 00:14:29.963 --> 00:14:34.329 It is similar for us in our local office in Cologne, where the issue 00:14:34.329 --> 00:14:39.696 of Consumer and Industry Goods is handled differently in terms of data management. 00:14:39.696 --> 00:14:42.829 Due to other requirements that are placed on the respective 00:14:42.829 --> 00:14:44.263 quasi brand at that moment. 00:14:44.796 --> 00:14:46.296 In general, data maintenance 00:14:46.296 --> 00:14:49.729 can be divided into three main steps. 00:14:49.829 --> 00:14:54.796 At the headquarters near Paris, the new data is created in our ERP, 00:14:54.796 --> 00:14:59.729 i.e. in SAP, so that we have initially enriched the global master data there. 00:14:59.963 --> 00:15:04.896 This global master data is then transferred to us accordingly. 00:15:04.896 --> 00:15:08.863 Not only to us here in Cologne, but also made available worldwide. 00:15:09.629 --> 00:15:11.096 Here, the data is supplemented 00:15:11.096 --> 00:15:14.363 and enriched, and in some cases this is still done in SAP. 00:15:14.363 --> 00:15:18.696 To deal with country-specific features, 00:15:18.696 --> 00:15:20.729 this can also include dangerous goods data. 00:15:20.729 --> 00:15:23.796 This could be logistical aspects, such as customs tariff numbers 00:15:23.796 --> 00:15:25.062 and the like. 00:15:25.062 --> 00:15:28.929 From there, in the next step, 00:15:28.929 --> 00:15:32.662 when the enrichment of the master data has been completed, 00:15:33.229 --> 00:15:37.596 the whole thing is transferred to the PIM system in ANTEROS, where it is possible 00:15:37.862 --> 00:15:43.196 to enrich both the marketing-relevant content and the technically-relevant content 00:15:43.196 --> 00:15:47.796 and, in particular, to deal with the 00:15:47.796 --> 00:15:50.629 manufacturer and product approvals 00:15:50.629 --> 00:15:52.229 and allocate them accordingly. 00:15:53.262 --> 00:15:58.996 In the PIM usage step, the PIM data enrichment, 00:15:59.062 --> 00:16:04.129 we then also have a workflow that ensures text translation, 00:16:04.196 --> 00:16:08.462 so that for products that are used in certain areas, 00:16:08.462 --> 00:16:12.229 there is in principle also a translation task, 00:16:12.296 --> 00:16:16.596 so that the translation can then also be added quickly 00:16:17.429 --> 00:16:20.929 in accordance with a relatively standardized principle. 00:16:21.996 --> 00:16:24.996 The work that is presented here in three main steps is, 00:16:25.296 --> 00:16:28.229 all in all, distributed among 00:16:29.196 --> 00:16:32.196 a number of colleagues that can be seen in the 00:16:32.196 --> 00:16:33.662 lower two-digit range. 00:16:33.662 --> 00:16:37.096 So you can see how complex something like this can be, 00:16:37.296 --> 00:16:40.529 that not just one person is responsible for one area, 00:16:40.795 --> 00:16:43.929 but that we are talking about several colleagues 00:16:43.929 --> 00:16:45.095 being involved. 00:16:45.095 --> 00:16:49.429 And it is all the more important that we have an application basis through ANTEROS 00:16:49.762 --> 00:16:54.329 and also a process basis, so that in principle every colleague 00:16:54.329 --> 00:16:58.395 knows what is required of them accordingly. 00:16:58.895 --> 00:17:01.462 We therefore have different user roles 00:17:01.462 --> 00:17:04.195 that we use for international data maintenance. 00:17:04.395 --> 00:17:09.129 We have the topic of marketing at both corporate and business unit 00:17:09.129 --> 00:17:13.395 level, i.e. at the branch level of corporate marketing. 00:17:13.662 --> 00:17:16.495 In principle, this defines more fundamental data, 00:17:17.629 --> 00:17:19.629 such as basic categorizations 00:17:19.629 --> 00:17:22.662 that correspond to the global product hierarchy. 00:17:22.662 --> 00:17:26.162 Whereas the marketing department of the business unit, for example, 00:17:26.462 --> 00:17:29.962 goes and defines the country assortments, sometimes in different ways, 00:17:30.362 --> 00:17:34.929 and can then add country-specific data, images, 00:17:34.929 --> 00:17:36.562 or other requirements. 00:17:37.195 --> 00:17:39.262 We have the Technical Data Managers. 00:17:39.262 --> 00:17:43.629 These are the colleagues who deal specifically 00:17:43.629 --> 00:17:48.462 with application allocation, manufacturer approvals, industry standards, 00:17:48.595 --> 00:17:50.229 etc. 00:17:50.362 --> 00:17:53.895 Subsequent systems often use this as a filter in the end. 00:17:54.229 --> 00:17:57.295 It is only by entering these attributes that our products 00:17:57.295 --> 00:17:59.162 become relevant for the customer, 00:17:59.162 --> 00:18:02.962 making this a very important task that is performed both globally 00:18:03.162 --> 00:18:06.662 and then also locally in a somewhat more specialized way. 00:18:07.762 --> 00:18:10.495 We have the issue of translators. 00:18:10.495 --> 00:18:15.195 The translators are not a completely independent position for us, they are divided up. 00:18:15.195 --> 00:18:18.462 Depending on the branch, the whole thing falls either into the area 00:18:18.462 --> 00:18:21.828 of product management, technology or trade marketing. 00:18:22.062 --> 00:18:25.162 However, it's its own role in that the very translation 00:18:25.162 --> 00:18:27.362 is a critical part of us 00:18:27.362 --> 00:18:30.028 being able to complete the data enrichment to that point. 00:18:30.728 --> 00:18:34.495 Last but not least, we have several users within the whole global 00:18:34.795 --> 00:18:38.795 organization who have a kind of administrator role. 00:18:38.795 --> 00:18:42.795 So they have access to certain, let's call it backend 00:18:42.795 --> 00:18:43.428 functions. 00:18:43.428 --> 00:18:48.028 They can, for example, define data structures, 00:18:48.028 --> 00:18:50.295 redefine category trees 00:18:50.295 --> 00:18:55.062 when, for example, new publications, a new web portal, etc. are added, 00:18:55.062 --> 00:18:59.028 but they can also define the parameter definition 00:18:59.395 --> 00:19:02.962 when it comes to grouping, 00:19:02.962 --> 00:19:06.862 managing, creating and finally outputting data in some other form. 00:19:07.462 --> 00:19:12.295 In this case, it is important to look at who is allowed to change what, 00:19:12.762 --> 00:19:16.595 who is responsible for what, and who, 00:19:16.795 --> 00:19:21.395 despite being highly motivated and having good intentions, should maybe not be involved in a particular area for the time being. 00:19:22.062 --> 00:19:24.195 Especially when it comes to the manufacturer releases that we maintain. 00:19:24.195 --> 00:19:28.795 This is a very sensitive area, and if, based on the assumption 00:19:29.095 --> 00:19:32.461 that some data value is missing, someone starts 00:19:32.461 --> 00:19:35.428 to maintain these values without authorization and to store them differently, 00:19:35.695 --> 00:19:37.761 this can ultimately lead to 00:19:37.761 --> 00:19:40.528 our products being used in the wrong way. 00:19:40.528 --> 00:19:42.995 Which means that damage can occur, 00:19:43.328 --> 00:19:46.061 making us liable to recourse in some form afterwards. 00:19:47.195 --> 00:19:48.428 That's the thing for us. 00:19:48.428 --> 00:19:49.628 For the user, it is of course 00:19:49.628 --> 00:19:51.128 quite unpleasant if they choose a product 00:19:51.128 --> 00:19:53.161 of ours and damage occurs later. 00:19:53.561 --> 00:19:57.295 That's why the damage to our image, which we definitely 00:19:57.295 --> 00:20:00.328 have to avoid, is much more important at that point, 00:20:00.561 --> 00:20:02.595 so we always want to ensure technical compatibility. 00:20:02.595 --> 00:20:04.761 Hence the various user roles. 00:20:05.161 --> 00:20:09.228 This means that, depending on who assumes which function, 00:20:10.095 --> 00:20:12.861 who is responsible for what data maintenance, 00:20:12.861 --> 00:20:17.128 there is a sometimes quite complex structure of user roles. 00:20:17.128 --> 00:20:18.228 But they also clearly 00:20:18.228 --> 00:20:22.095 show where the limits of one's own actions are defined. 00:20:22.095 --> 00:20:25.995 Both in terms of responsibility, where you do have to take care of it, 00:20:26.095 --> 00:20:28.861 and in terms of non-responsibility, 00:20:28.928 --> 00:20:32.428 where you are not allowed to maintain data. 00:20:34.195 --> 00:20:37.861 In some places, this is defined on the basis of assignments 00:20:37.861 --> 00:20:39.695 that originate from SAP. 00:20:39.695 --> 00:20:41.795 This refers to the sales organization. 00:20:42.028 --> 00:20:45.295 So that sales organization-specific data, 00:20:45.728 --> 00:20:49.061 because the sales organizations are assigned to our branches, 00:20:49.695 --> 00:20:52.061 meaning, there is a certain synchronicity, 00:20:52.161 --> 00:20:58.794 so that the local affiliation, which comes from SAP, 00:20:59.061 --> 00:21:02.628 can be transferred to PIM from the data structure, so to speak. 00:21:02.961 --> 00:21:06.228 And then there are still changes 00:21:06.861 --> 00:21:09.961 that require a special adjustment, which can be 00:21:09.961 --> 00:21:12.194 easily displayed via ANTEROS. 00:21:12.694 --> 00:21:14.928 If we specifically look at the data maintenance 00:21:14.928 --> 00:21:18.661 of our marketing data, then we are talking about categorization. 00:21:18.661 --> 00:21:20.328 We are talking about marketing texts. 00:21:20.328 --> 00:21:22.461 Of course, we are also talking about images. 00:21:22.461 --> 00:21:26.794 But we are talking specifically about the fact, and this is actually the main objective, 00:21:26.794 --> 00:21:28.761 that we are ideally in a position 00:21:28.994 --> 00:21:31.494 to communicate USPs with the help of ANTEROS. 00:21:31.861 --> 00:21:33.361 USPs, unique selling propositions, 00:21:33.361 --> 00:21:37.294 and thus we manage to differentiate ourselves from the competition 00:21:37.528 --> 00:21:41.228 and the competitive position that we have, for example, 00:21:41.228 --> 00:21:44.761 as the market leader for motorcycle lubricants in Germany 00:21:45.094 --> 00:21:48.061 can be consolidates and ideally also expanded. 00:21:48.628 --> 00:21:53.461 Finally, the whole thing is also market-specific. 00:21:53.561 --> 00:21:58.161 So this is a small insight into what a specific product, 00:21:58.161 --> 00:22:02.861 in this case a product family, looks like in our backend. 00:22:03.661 --> 00:22:07.094 So we see that we have different options 00:22:07.094 --> 00:22:11.661 for data entry, data storage via the different tabs. 00:22:12.828 --> 00:22:16.094 We are currently in the Marketing Data tab, 00:22:16.094 --> 00:22:19.727 where we see, for example, the English description text. 00:22:20.094 --> 00:22:21.894 This is the global English text. 00:22:21.894 --> 00:22:25.827 Based on this, an English text for America 00:22:25.827 --> 00:22:30.094 or, for example, for the United Kingdom could be derived differently. 00:22:30.527 --> 00:22:32.594 Even in the webshop, we have the option 00:22:32.894 --> 00:22:35.627 of language-specific output. 00:22:36.361 --> 00:22:39.327 The reason for this is that there are sometimes 00:22:39.994 --> 00:22:44.194 different legal requirements for product illustration per country 00:22:44.194 --> 00:22:49.261 or per language region than might be the case globally. 00:22:49.361 --> 00:22:53.561 The process continues with further attributes, for example 00:22:53.561 --> 00:22:57.661 in the technical area, which can then 00:22:57.661 --> 00:23:01.994 also be maintained locally for the requirements. 00:23:01.994 --> 00:23:06.694 What is also often an issue: depending on which business unit of ours 00:23:06.694 --> 00:23:11.061 works how intensively with the PIM system, it makes sense at that moment 00:23:11.061 --> 00:23:15.027 to add other assets per family. 00:23:15.361 --> 00:23:19.394 Some of these are manufacturer releases in the form of logos, 00:23:19.394 --> 00:23:23.361 others can be technical properties in the form of pictograms. 00:23:23.727 --> 00:23:26.061 We will get to the technical data here. 00:23:26.061 --> 00:23:29.961 That is, we distinguish two brands, namely Motul and Motul Tech. 00:23:30.861 --> 00:23:34.994 Since the whole thing, as mentioned earlier 00:23:34.994 --> 00:23:39.027 has its own care both at headquarters and locally. 00:23:39.060 --> 00:23:42.294 This means that there are separate brand-specific teams 00:23:42.694 --> 00:23:44.760 that belong to this division, 00:23:45.327 --> 00:23:49.694 so we have also subdivided the technical data accordingly. 00:23:50.027 --> 00:23:52.860 So we have the technical data for our Consumer Goods, 00:23:53.227 --> 00:23:57.127 which is located in the left tab, and we have the technical data 00:23:57.394 --> 00:24:01.727 for our Industrial Goods, which is located in the right tab. 00:24:01.727 --> 00:24:05.027 Industrial goods have completely different attributes 00:24:05.094 --> 00:24:07.160 than our Consumer Goods do. 00:24:07.160 --> 00:24:10.260 That's why it's only right that we strictly separate this 00:24:10.560 --> 00:24:14.260 and, once it's separated, we can also take it into account 00:24:14.627 --> 00:24:18.694 for any output in the form of Excel exports 00:24:18.927 --> 00:24:20.527 or forwarding to other media. 00:24:20.727 --> 00:24:23.727 The topic of manufacturers and approvals, which has already been mentioned 00:24:23.727 --> 00:24:27.927 many times, is of course extremely important for us 00:24:27.927 --> 00:24:31.894 and can also be easily maintained via ANTEROS. 00:24:32.227 --> 00:24:35.427 This means that, first and foremost, we have a pool 00:24:35.727 --> 00:24:40.460 of all possible elements that are available to us as manufacturer approvals. 00:24:40.760 --> 00:24:44.394 And we are then in a position to add the corresponding approval to the respective product family 00:24:44.627 --> 00:24:48.994 with virtually just one click 00:24:49.294 --> 00:24:52.227 according to the current status of the technical approval 00:24:52.794 --> 00:24:55.127 that we have acquired with our product. 00:24:55.794 --> 00:24:59.094 This is so important, by the way, because only via this 00:24:59.094 --> 00:25:04.327 manufacturer approval is it possible to sell very, very many of our products. 00:25:04.693 --> 00:25:09.593 While engine oil is not just about viscosity, 00:25:09.593 --> 00:25:12.627 it is also not just a quality feature in the sense of whether it is semi-synthetic or mineral. 00:25:13.027 --> 00:25:16.260 The most important thing about engine oil, or transmission oil, 00:25:16.460 --> 00:25:18.327 is actually the manufacturer's approval. 00:25:19.093 --> 00:25:21.527 Does it have the certain approval, 00:25:21.527 --> 00:25:25.593 i.e. the release, for example from Mercedes Benz, from Opel/Vauxhall/Buick, from Volkswagen, from whoever? 00:25:26.027 --> 00:25:28.060 This is what our customers are looking for, 00:25:28.293 --> 00:25:31.193 the basis on which our customers make the decision to buy, 00:25:31.427 --> 00:25:34.727 and how business is finally generated, so to speak. 00:25:35.127 --> 00:25:39.227 If the information is not accurately maintained, or if it is not available in the first place, 00:25:39.627 --> 00:25:42.927 our sales suffer to a certain extent, quite dramatically. 00:25:43.293 --> 00:25:46.960 In order to communicate these technical properties, 00:25:46.960 --> 00:25:50.393 we therefore have a technical data sheet 00:25:50.393 --> 00:25:54.160 TDB or in English TDS for Technical Data Sheet. 00:25:55.227 --> 00:25:56.093 We also have 00:25:56.093 --> 00:25:58.893 a certain part, perhaps even a very large part, 00:25:59.193 --> 00:26:01.293 of the master data that is already 00:26:01.293 --> 00:26:04.227 transferred to ANTEROS via the SAP interface. 00:26:04.860 --> 00:26:08.993 Marketing and the Technical Department then work together 00:26:09.327 --> 00:26:13.027 together to ensure that this technical data sheet, the technical attribution as it were, 00:26:13.127 --> 00:26:15.260 is extended accordingly. 00:26:15.327 --> 00:26:18.027 We are talking about techno-commercial 00:26:18.627 --> 00:26:20.793 argumentation in terms of content. 00:26:21.060 --> 00:26:25.426 On the one hand, we have to clearly present the hard technical facts, 00:26:25.660 --> 00:26:29.626 but on the other hand, we also want to use USPs 00:26:29.693 --> 00:26:33.326 to arouse interest beyond the actual technical data 00:26:33.593 --> 00:26:36.460 and give the customer more information about 00:26:36.460 --> 00:26:39.493 why the product is right for them. 00:26:40.560 --> 00:26:43.593 Finally, the Technical Data Manager is responsible for the release. 00:26:44.260 --> 00:26:46.793 They are therefore responsible for ensuring 00:26:46.793 --> 00:26:48.060 that the data is correct. 00:26:48.360 --> 00:26:49.893 Then something very exciting happens, 00:26:49.893 --> 00:26:53.360 namely the automatic generation of this data sheet. 00:26:53.426 --> 00:26:57.960 In the past, we used to do this manually. 00:26:58.026 --> 00:27:00.926 The keyword here is Microsoft Word. 00:27:00.926 --> 00:27:04.160 This is something we no longer have to do nowadays, 00:27:04.793 --> 00:27:09.426 which means that based on the data verified once in the PIM, 00:27:09.660 --> 00:27:11.360 entire product families 00:27:11.360 --> 00:27:14.960 and even for subsequent and related product families 00:27:15.593 --> 00:27:19.526 correct data sheets can be automatically generated, 00:27:19.526 --> 00:27:22.960 which can then also be passed on to subsequent media. 00:27:23.260 --> 00:27:26.593 For example, for our B2C store, 00:27:26.593 --> 00:27:29.993 B2B store, B2C store, but also 00:27:29.993 --> 00:27:35.093 for data exports, where something is then provided as a PDF download link. 00:27:35.360 --> 00:27:37.293 The important thing here is the automatic generation, 00:27:37.293 --> 00:27:40.993 which saves us a lot of time and also simplifies checking for errors 00:27:41.293 --> 00:27:43.993 or data gaps. 00:27:44.226 --> 00:27:46.959 This is what a print document can look like in the end. 00:27:47.226 --> 00:27:49.159 So we have different areas. 00:27:49.159 --> 00:27:53.026 We start at the top with a few basic details, the product name 00:27:53.026 --> 00:27:57.693 for example, and a basic qualitative classification. 00:27:57.926 --> 00:28:02.026 At the top on the left, we see the icons, 00:28:02.026 --> 00:28:05.359 or pictograms, which I just mentioned, to show a user 00:28:05.359 --> 00:28:08.126 with technical experience what the product is suitable for. 00:28:08.559 --> 00:28:10.726 We have various subcategories 00:28:10.726 --> 00:28:13.826 in which we provide information about the various technical properties, 00:28:14.226 --> 00:28:18.926 so that comprehensive technical insight can be provided here 00:28:18.993 --> 00:28:22.193 on just under two, in this case three A4 pages, 00:28:22.393 --> 00:28:26.659 and thus a decision can also be made about the compatibility of our product. 00:28:26.993 --> 00:28:30.026 If we continue to talk about automatic data output, 00:28:30.326 --> 00:28:34.959 we are ultimately also talking about the topic of print documents. 00:28:35.059 --> 00:28:38.459 We had previously looked at the topic of technical data sheets, 00:28:39.193 --> 00:28:43.793 which is more interesting for mechanics, for workshops, 00:28:43.793 --> 00:28:47.126 and therefore for technical users in general. 00:28:47.459 --> 00:28:50.759 The publication of the catalog is 00:28:50.759 --> 00:28:54.893 where we try to promote the marketing nature. 00:28:54.893 --> 00:28:58.393 In other words, finding a way to address our customers, 00:28:58.993 --> 00:29:02.593 how we can present our products in the right light, 00:29:02.593 --> 00:29:05.193 and how we can communicate our unique selling points accordingly. 00:29:05.459 --> 00:29:09.059 The product catalog is also generated 100% automatically 00:29:09.426 --> 00:29:12.692 through defined routines, assignments 00:29:13.326 --> 00:29:18.159 and the resulting data pools, the right articles, 00:29:18.159 --> 00:29:22.492 the right families, the right categories and, as a result, 00:29:22.492 --> 00:29:27.359 the right texts, images and other assets for each language are fetched, 00:29:27.592 --> 00:29:31.526 i.e. compiled, and output as part of the catalog. 00:29:31.726 --> 00:29:36.626 Even generating a catalog with just under 180 or 200 pages 00:29:37.226 --> 00:29:40.026 for inspection with ANTEROS 00:29:40.026 --> 00:29:43.226 takes no longer than 5 to 10 minutes. 00:29:43.559 --> 00:29:46.359 This means that even if you want to get an interim status 00:29:46.359 --> 00:29:49.059 - what is the current status of an assortment? 00:29:49.059 --> 00:29:51.726 Then it is not an operation that takes hours, but 00:29:51.726 --> 00:29:53.759 it is an action that really only takes minutes 00:29:53.992 --> 00:29:57.092 and that can be done with one, two, three, 00:29:57.092 --> 00:29:59.226 for us it is four clicks. 00:29:59.226 --> 00:30:03.359 And then we have a locally specific edition, 00:30:03.726 --> 00:30:04.992 either as a PDF 00:30:04.992 --> 00:30:08.426 or in another format, which we can then also make available. 00:30:08.659 --> 00:30:12.159 Finally, I would like to mention the media portal again. 00:30:12.392 --> 00:30:15.059 This is our latest achievement, so to speak, 00:30:16.359 --> 00:30:18.126 but we are proud of it 00:30:18.126 --> 00:30:21.159 because it is a very big step forward. 00:30:21.359 --> 00:30:23.992 A step forward in the direction of the customer, the market. 00:30:24.059 --> 00:30:28.226 A step forward in the direction of providing necessary 00:30:28.226 --> 00:30:31.392 information, data and files. 00:30:32.459 --> 00:30:36.559 That is, we have enriched the standard ANTEROS media portal 00:30:36.659 --> 00:30:40.592 with partly our own functions in our own layout. 00:30:41.192 --> 00:30:44.092 So we are talking about standard elements 00:30:44.092 --> 00:30:45.592 being made available to partners. 00:30:46.292 --> 00:30:50.125 The whole thing is governed by a simple login process. 00:30:50.425 --> 00:30:54.659 We have the uncomplicated user administration on our side, 00:30:55.292 --> 00:30:57.692 users can be from our company, i.e. 00:30:57.692 --> 00:31:00.725 internal to the company, as well as external to the company. 00:31:00.992 --> 00:31:03.392 Not every external customer wants to use a portal like this. 00:31:03.992 --> 00:31:07.292 However, most people are happy to have 00:31:07.559 --> 00:31:09.792 access to the data and to have insight in and 00:31:09.792 --> 00:31:12.292 access to the files accordingly. 00:31:12.725 --> 00:31:15.792 We have made the whole thing as convenient and 00:31:15.792 --> 00:31:17.492 uncomplicated as possible. 00:31:18.159 --> 00:31:20.125 By the way, this was also already a basic function 00:31:20.125 --> 00:31:22.592 that was specified by the ANTEROS media portal. 00:31:22.925 --> 00:31:24.659 This means that the logical structure 00:31:24.659 --> 00:31:27.459 we use in our publication, for example, 00:31:27.792 --> 00:31:30.225 can also be applied to the media portal, 00:31:30.392 --> 00:31:33.525 so that the customer remains in their familiar environment, so to speak. 00:31:33.825 --> 00:31:36.992 The structure they are familiar with from our catalog 00:31:36.992 --> 00:31:39.892 can be transferred to the media portal on a one-to-one basis. 00:31:40.359 --> 00:31:44.225 This makes it easier to find the information 00:31:44.359 --> 00:31:48.092 and the customer never feels confused, lost 00:31:48.359 --> 00:31:49.859 or loses interest in 00:31:49.859 --> 00:31:52.959 organizing and collecting the data themselves. 00:31:53.592 --> 00:31:55.692 Organizing and collecting the data by oneself 00:31:55.692 --> 00:31:58.658 has a great advantage especially for e-commerce, 00:31:59.525 --> 00:32:05.658 as the graphic files and image files can be output 00:32:05.658 --> 00:32:08.125 according to the quality requirements of the requesting party. 00:32:08.492 --> 00:32:12.092 Until now, we have often gone and manually 00:32:12.092 --> 00:32:15.292 provided the largest file format by default. 00:32:15.458 --> 00:32:18.692 In some cases, this was simply too large to be uploaded or sent anywhere. 00:32:18.992 --> 00:32:20.158 The feedback coming back was: 00:32:20.158 --> 00:32:23.092 "Why so big? Now we need to rework that.” 00:32:23.192 --> 00:32:25.658 The reworking takes time, that takes resources. 00:32:25.892 --> 00:32:28.458 So here we have the possibility that the customer can now decide 00:32:28.458 --> 00:32:30.758 for themselves: how do they want the files? 00:32:30.758 --> 00:32:33.958 How should they be issued so that they are 00:32:33.958 --> 00:32:36.692 directly compatible for customer use? 00:32:36.958 --> 00:32:39.592 In addition, there is also the integration 00:32:40.358 --> 00:32:43.558 i.e. the safety data sheets. 00:32:43.558 --> 00:32:46.958 This is what is managed in the external database, 00:32:46.958 --> 00:32:49.258 in addition to the technical data sheets, 00:32:49.258 --> 00:32:52.025 which we create within ANTEROS, 00:32:52.325 --> 00:32:54.758 but are also equally integrated. 00:32:54.858 --> 00:32:57.425 Safety data sheets play a decisive role 00:32:57.425 --> 00:33:00.158 for the topic of transport and storage, 00:33:00.792 --> 00:33:04.225 so it is essential that when we talk about the provision of data 00:33:04.225 --> 00:33:08.458 and information, that something like this is also integrated. 00:33:09.525 --> 00:33:13.492 It is not exactly self-evident that content from a foreign server, 00:33:13.492 --> 00:33:16.225 to which we are barely properly connected, 00:33:17.325 --> 00:33:19.892 can be integrated into ANTEROS. 00:33:19.892 --> 00:33:22.458 We are glad that this could be done. 00:33:22.458 --> 00:33:24.091 What does the customer gain from information? 00:33:24.091 --> 00:33:26.125 What does the customer gain from images? 00:33:26.125 --> 00:33:29.325 Most importantly, what does the existing customer gain from this? 00:33:29.691 --> 00:33:30.758 As a rule, 00:33:30.758 --> 00:33:34.758 the existing customer only wants to know: "What's new?" and "What's different?". 00:33:34.825 --> 00:33:37.325 And these questions "What is new?" and "What is different?" 00:33:37.558 --> 00:33:38.758 are precisely the questions 00:33:38.758 --> 00:33:41.991 that can be answered to a certain extent with the change service. 00:33:42.725 --> 00:33:46.425 The change service queries over 60 different attributes, 00:33:46.491 --> 00:33:48.658 starting with the article description. 00:33:48.658 --> 00:33:53.858 This goes on to ERN codes, this goes up to whether new image files, 00:33:53.858 --> 00:33:57.391 new data sheets, etc. are available 00:33:57.391 --> 00:34:01.425 and outputs this in a simple Excel overview, so that the customer can decide for themselves 00:34:01.958 --> 00:34:04.358 which changes are relevant for them? 00:34:04.725 --> 00:34:06.158 So they can easily filter. 00:34:06.158 --> 00:34:10.625 I want to see, where are new technical data sheets and safety data sheets? 00:34:10.691 --> 00:34:13.591 Pictures aren't of interest to me, texts aren't of interest to me. 00:34:13.591 --> 00:34:17.091 And then, in principle, they are well informed about the changes 00:34:17.258 --> 00:34:20.758 and can update their data accordingly based on the information 00:34:20.758 --> 00:34:24.725 embedded in the change service as an Excelexport. 00:34:25.058 --> 00:34:27.691 In this case, the whole thing happens on a monthly basis 00:34:27.858 --> 00:34:30.625 and is automatically provided by ANTEROS 00:34:30.825 --> 00:34:33.091 in the media portal. 00:34:33.658 --> 00:34:37.358 What this avoids is a large amount of manual time 00:34:37.358 --> 00:34:42.325 that was previously spread throughout our organization. 00:34:42.725 --> 00:34:45.458 Quite frankly, that's not a task that anyone 00:34:45.458 --> 00:34:47.491 really wanted to do. 00:34:47.491 --> 00:34:49.958 We have several thousand customers in Germany. 00:34:50.391 --> 00:34:50.924 If we then 00:34:50.924 --> 00:34:54.024 add the foreign markets, there's a bit more to it. 00:34:54.824 --> 00:34:59.591 I think it's understandable that with the frequency of inquiries and the like, 00:34:59.658 --> 00:35:03.291 a standard has also generated plenty of buzz internally. 00:35:03.524 --> 00:35:07.191 Because now it comes automatically and no one needs to bother 00:35:07.458 --> 00:35:10.824 contributing manually in any way. 00:35:10.958 --> 00:35:12.324 What is definitely worth mentioning 00:35:12.324 --> 00:35:15.758 in terms of usage is our dealer exports. 00:35:15.824 --> 00:35:19.458 On the one hand, we are talking about the industry standard format 00:35:19.458 --> 00:35:24.558 that TecDoc specifies, which is the TAF format. 00:35:24.624 --> 00:35:28.624 It feels like the whole industry is using the TecDoc data. 00:35:28.724 --> 00:35:30.991 And that's probably not just a feeling, rather, 00:35:30.991 --> 00:35:36.291 if you're talking about the automotive aftermarket, that's simply the instance 00:35:36.291 --> 00:35:40.124 in which you have to participate with your data, in order to be seen on the market. 00:35:40.291 --> 00:35:44.024 Anyone who does not do this as a supplier of vehicle spare parts 00:35:44.024 --> 00:35:47.658 will find it relatively difficult to play a significant role in the market. 00:35:48.958 --> 00:35:52.858 It is also important that changes are communicated as quickly as possible. 00:35:53.258 --> 00:35:57.558 Because our customers' catalogs, 00:35:57.558 --> 00:36:02.324 which in turn can be intermediaries, are based on this TecDoc data. 00:36:02.324 --> 00:36:05.558 The wholesalers we supply build their catalogs 00:36:05.558 --> 00:36:08.557 one-to-one from the TecDoc data. 00:36:08.891 --> 00:36:12.457 In house, they might add a bit of content 00:36:12.457 --> 00:36:15.291 in some form or make a few slight changes, 00:36:15.591 --> 00:36:18.391 but the basis of the whole thing comes from TecDoc. 00:36:18.491 --> 00:36:22.691 That's why it's important that the whole thing can be generated 00:36:22.691 --> 00:36:24.924 at the push of a button, so that changes can be implemented 00:36:24.924 --> 00:36:27.524 as quickly as possible and, 00:36:27.524 --> 00:36:30.757 on the other hand, that we also have standardization. 00:36:30.757 --> 00:36:35.891 Standardization that the customer knows what data format to expect and how. 00:36:35.891 --> 00:36:36.591 And that is precisely 00:36:36.591 --> 00:36:39.524 what we do by implementing it within the framework of the TecDoc standard. 00:36:39.891 --> 00:36:41.091 The record types, 00:36:41.091 --> 00:36:44.891 as they are called in TecDoc, are maintained and distributed there. 00:36:45.524 --> 00:36:49.657 This is a standard that also ensures a very high level of data quality. 00:36:49.791 --> 00:36:52.291 In addition to the TecDoc format, we are also 00:36:52.357 --> 00:36:56.691 talking about the various Excelexports 00:36:56.791 --> 00:37:01.491 On the one hand, of course for customers, so for dealers, be it 00:37:01.491 --> 00:37:04.857 retailers, be it workshops, be it pure eCommerce players, 00:37:05.624 --> 00:37:09.157 also wholesalers, intermediaries, who obtain the data accordingly from us 00:37:09.857 --> 00:37:14.757 and partly use their own systems for master data preparation. 00:37:15.724 --> 00:37:19.057 But we are also talking about exports for sales platforms. 00:37:19.857 --> 00:37:21.991 Sales platforms, such as Idealo, 00:37:22.291 --> 00:37:26.291 where you as a provider or as a quasi enricher of this data 00:37:26.291 --> 00:37:29.424 have the opportunity to influence your assortment, 00:37:30.124 --> 00:37:33.824 so that the assortment is presented according to your own requirements 00:37:34.624 --> 00:37:36.724 and your own idea, 00:37:37.390 --> 00:37:40.624 because otherwise there is a rather uncontrolled growth, especially on such platforms. 00:37:40.924 --> 00:37:45.024 in terms of keeping content up to date, this can affect 00:37:45.024 --> 00:37:48.057 product images and product texts. 00:37:48.057 --> 00:37:52.490 In our case, the issue is that product texts often contain 00:37:52.490 --> 00:37:57.190 references to approvals that may become obsolete at some point. 00:37:57.390 --> 00:37:59.057 And at that moment, we consider 00:37:59.057 --> 00:38:02.290 it dangerous for the suppliers of our products 00:38:03.024 --> 00:38:06.290 if old information is present there without better knowledge 00:38:06.290 --> 00:38:09.724 without wanting to accuse anyone of bad intentions, but just old information. 00:38:10.057 --> 00:38:13.324 So that's where we can proactively adjust the data quality 00:38:13.324 --> 00:38:18.724 on the World Wide Web accordingly via the Excel exports 00:38:18.724 --> 00:38:22.157 in terms of the sales platform and keep it at a high level. 00:38:22.857 --> 00:38:25.990 It is simply in our interest that the right products 00:38:26.224 --> 00:38:29.557 find the right application and that there is 00:38:29.857 --> 00:38:31.857 no form of disappointment with our products. 00:38:31.957 --> 00:38:35.124 To sum up: What are the advantages that we have? 00:38:35.124 --> 00:38:37.124 But most importantly, and I actually place 00:38:37.124 --> 00:38:41.290 this first, for our customers and for our partners? 00:38:41.357 --> 00:38:43.090 These can be divided into three areas. 00:38:43.090 --> 00:38:47.390 Firstly, what does ANTEROS do at Motul? What makes it special? 00:38:47.390 --> 00:38:49.290 What are the benefits that result from it? 00:38:49.290 --> 00:38:52.890 And finally, what in the market at the interface to the customer 00:38:53.423 --> 00:38:55.090 is particularly special? 00:38:55.123 --> 00:38:57.790 To focus on ANTEROS: We have the topic of 00:38:57.857 --> 00:39:00.823 international care, as just mentioned. 00:39:00.823 --> 00:39:02.623 This can be quite complex. 00:39:02.623 --> 00:39:05.223 There are many different people involved, 00:39:05.857 --> 00:39:08.590 who all have their own individual work to do, so to speak. 00:39:08.590 --> 00:39:12.223 And from this, meaningful, valid overall work 00:39:12.223 --> 00:39:15.123 is created, which can be communicated to the market. 00:39:16.023 --> 00:39:19.757 The major advantage is that the whole thing is just very easy to use. 00:39:19.757 --> 00:39:22.857 That means creating the structures internally, that's not difficult, 00:39:23.290 --> 00:39:27.090 because the effort, however many people may be involved in it, 00:39:27.290 --> 00:39:29.390 the whole thing is distributed in small chunks 00:39:29.390 --> 00:39:31.090 on different shoulders 00:39:31.090 --> 00:39:33.757 and the responsibilities are also clearly regulated accordingly. 00:39:34.923 --> 00:39:37.390 We have the benefit of standardized data, 00:39:37.723 --> 00:39:41.023 meaning that we don't have to tell one customer one thing and tell another customer another thing, 00:39:41.223 --> 00:39:44.323 depending on who is located where in the world at any given time. 00:39:44.423 --> 00:39:47.090 Based on this data from the PIM, 00:39:47.357 --> 00:39:50.823 we have one truth that we communicate to the outside world, 00:39:51.390 --> 00:39:52.690 and we can be sure 00:39:52.690 --> 00:39:55.090 that the information that reaches the customer is correct. 00:39:55.457 --> 00:39:58.390 And the customer can be just as sure of this and is grateful for it, 00:39:58.623 --> 00:40:02.190 because they definitely don't have that security with every provider, 00:40:02.190 --> 00:40:05.690 not with every supplier, and certainly not 00:40:05.690 --> 00:40:07.090 with the data involved. 00:40:08.690 --> 00:40:11.157 We mentioned the topic of workflows, roles and rights 00:40:11.923 --> 00:40:14.923 with the processes that result from them, 00:40:15.723 --> 00:40:17.790 which then lead to the high data quality. 00:40:18.423 --> 00:40:19.323 And finally, 00:40:19.323 --> 00:40:20.790 I mentioned very briefly 00:40:20.790 --> 00:40:24.056 the distribution of these tasks across various people, 00:40:24.123 --> 00:40:26.823 and if this is done efficiently, 00:40:27.056 --> 00:40:29.656 then we can speak of a significant time saving 00:40:29.923 --> 00:40:32.856 compared to the situation in which 00:40:32.856 --> 00:40:35.656 the data would otherwise be maintained in the conventional way. 00:40:37.490 --> 00:40:39.123 Thanks to the good data quality, 00:40:39.123 --> 00:40:42.790 we hardly have anything in terms of complaints coming our way. 00:40:43.090 --> 00:40:46.356 And if they do, simple algorithms, 00:40:46.556 --> 00:40:48.723 simple plausibility checks 00:40:49.356 --> 00:40:52.490 can be used to determine the quality of the data in the important areas. 00:40:53.323 --> 00:40:56.523 Data gaps are automatically detected by ANTEROS 00:40:56.890 --> 00:40:59.623 and plausible values can be easily found out 00:40:59.623 --> 00:41:02.290 based on the experience we have in handling the data, 00:41:02.890 --> 00:41:06.156 so we are able to offer a very high quality 00:41:06.423 --> 00:41:08.456 and thus satisfy the customer. 00:41:08.756 --> 00:41:11.890 And a customer who is satisfied is happy to stay with us 00:41:12.090 --> 00:41:15.023 and we are happy to work with them on a long-term basis. 00:41:15.323 --> 00:41:16.090 At that point, 00:41:16.090 --> 00:41:19.556 the result is a win-win situation for both sides. 00:41:19.656 --> 00:41:22.590 The interfaces that ANTEROS offers, those are a big plus 00:41:22.590 --> 00:41:26.756 at Motul, whether it's because of the safety data sheets, 00:41:26.823 --> 00:41:30.290 whether it's also because of forward direction of the various publications 00:41:30.290 --> 00:41:31.556 that we run. 00:41:32.490 --> 00:41:35.956 Everything works smoothly, these interfaces are standardized, 00:41:35.956 --> 00:41:39.223 the data only has to be maintained once, 00:41:39.823 --> 00:41:43.556 and we can return to the extremely important point 00:41:43.556 --> 00:41:44.623 of high data quality. 00:41:45.023 --> 00:41:46.823 Because if the data quality is not right, 00:41:46.923 --> 00:41:50.156 then the whole thing comes back to us as a company two and three times over. 00:41:50.756 --> 00:41:54.356 We have to do more because of this, and at the end of the day 00:41:54.556 --> 00:41:58.756 we have to deal with the issue that, at some point, customers might want to jump ship. 00:41:59.156 --> 00:42:02.023 If every piece of information that we deliver to the customer 00:42:02.023 --> 00:42:04.989 first has to be scrutinized, sorted and processed 00:42:04.989 --> 00:42:08.589 at the customer's premises, then in this day and age, 00:42:09.223 --> 00:42:12.423 when data is the basis for business, that is not something 00:42:12.423 --> 00:42:15.289 the customer is particularly interested in. 00:42:15.423 --> 00:42:16.756 The diversity of usage 00:42:16.756 --> 00:42:19.689 that results is especially important in this day and age, 00:42:19.789 --> 00:42:21.089 everything is becoming more digital. 00:42:21.089 --> 00:42:25.223 We are working on many ideas regarding new portals and so on and so forth. 00:42:25.223 --> 00:42:29.123 Where this data is applied is that the very basis 00:42:29.123 --> 00:42:31.323 that offers us a very, very big advantage, 00:42:31.623 --> 00:42:36.089 because to a certain extent with a new portal, new store, 00:42:36.089 --> 00:42:39.656 whatever, which we would now launch, 00:42:39.656 --> 00:42:43.289 it would actually only need a one-time interface configuration, 00:42:43.289 --> 00:42:46.389 but that can actually be adopted half-finished from somewhere else. 00:42:46.656 --> 00:42:49.223 And now, the whole thing runs fully automatically. 00:42:49.623 --> 00:42:53.689 At most, we are talking about a very few work days. 00:42:53.689 --> 00:42:56.789 In some cases we are talking about only a few hours of work, in which it is necessary 00:42:57.423 --> 00:42:59.956 to bring about some form of configuration. 00:43:00.223 --> 00:43:01.289 And then the solution is written. 00:43:01.289 --> 00:43:03.189 Then the solution can be rolled out. 00:43:03.189 --> 00:43:05.956 Then there is no need for time-consuming testing. 00:43:06.989 --> 00:43:10.556 There is no need for lengthy staging before a solution can be published. 00:43:10.789 --> 00:43:14.156 Rather, because we know that the quality of ANTEROS is good, 00:43:14.422 --> 00:43:16.589 that the interfaces operate reliably, 00:43:16.922 --> 00:43:19.722 we can also be sure that any new publication 00:43:19.722 --> 00:43:23.422 that we tackle can be realized within the shortest possible time. 00:43:23.789 --> 00:43:27.189 And short time means short time to market for us. 00:43:27.556 --> 00:43:28.689 This means that new ideas, 00:43:28.689 --> 00:43:32.189 which we would like to implement in connection with perhaps new products, 00:43:33.022 --> 00:43:35.256 make it to the market quickly. 00:43:36.056 --> 00:43:39.322 We don't have any obstacles that we have to overcome, but we 00:43:39.322 --> 00:43:42.356 manage to take the momentum that we have from product development 00:43:42.356 --> 00:43:45.089 to the customer, to the market. 00:43:46.222 --> 00:43:48.622 And ultimately, the faster we are, 00:43:48.622 --> 00:43:50.356 the more we might have the opportunity 00:43:50.356 --> 00:43:53.956 to conquer the market with our new product idea, with our 00:43:54.489 --> 00:43:57.656 new concept that we are rolling out, and not leave so much pie for the 00:43:57.889 --> 00:44:01.556 other competitors in the market. 00:44:03.356 --> 00:44:04.289 Time savings are there, 00:44:04.289 --> 00:44:06.489 as I said, and the main keyword that we have to mention 00:44:07.756 --> 00:44:09.689 and that I would like to address lastly, 00:44:09.689 --> 00:44:13.322 which makes the customers happy, is the retrievability of the data. 00:44:14.056 --> 00:44:16.322 Because that is a major concern that is becoming more and more prevalent. 00:44:16.322 --> 00:44:20.156 The customers themselves are all very eager 00:44:20.156 --> 00:44:22.289 to have high quality data. 00:44:22.289 --> 00:44:26.589 In many industries, customers have risen to such professional levels 00:44:26.589 --> 00:44:31.522 that they virtually no longer need to be considered as part of a specific industry, 00:44:31.522 --> 00:44:34.022 but can be seen as IT or logistics companies 00:44:34.022 --> 00:44:36.322 within the industry. 00:44:36.722 --> 00:44:37.722 We see this with us 00:44:37.722 --> 00:44:41.089 in the automotive aftermarket industry, for example, with many wholesalers. 00:44:41.455 --> 00:44:46.222 And the more opportunities you offer them to proactively obtain data, 00:44:46.489 --> 00:44:50.122 the more they will use this opportunity to obtain data for themselves 00:44:50.122 --> 00:44:53.222 and will be grateful for every change that is communicated. 00:44:53.589 --> 00:44:57.689 And as long as the whole thing is done at a high, automated level, 00:44:57.989 --> 00:45:03.022 this requires no additional work for our company, for Motul. 00:45:03.022 --> 00:45:05.622 And in this case, this is actually a standard function 00:45:05.822 --> 00:45:08.889 that we now have with the help of ANTEROS. 00:45:09.322 --> 00:45:12.489 Thanks to ANTEROS we are able to control data accordingly 00:45:13.155 --> 00:45:16.422 and quickly deliver it to our customers 00:45:16.422 --> 00:45:18.155 and satisfy the market with it. 00:45:18.155 --> 00:45:21.289 Thank you very much for the presentation, very interesting. 00:45:21.289 --> 00:45:24.355 I found it interesting how many markets you operate in, 00:45:24.355 --> 00:45:26.955 with how many people also work with ANTEROS. 00:45:27.189 --> 00:45:32.355 So what were the biggest challenges in maintaining 00:45:32.355 --> 00:45:36.655 the data in these different markets and how did ANTEROS help with that? 00:45:37.689 --> 00:45:40.322 So one challenge at the beginning 00:45:40.322 --> 00:45:42.689 was to create awareness of what data means. 00:45:43.122 --> 00:45:45.522 I mean, by now, colleagues are increasingly 00:45:45.522 --> 00:45:48.255 confronted with this in their private lives as well. 00:45:48.322 --> 00:45:52.522 When someone buys something online, maybe a shoe in size 43, 00:45:52.522 --> 00:45:56.255 and size 39 is delivered, you can see when something is wrong in the background. 00:45:56.555 --> 00:45:59.155 That is, creating the willingness for it was not easy in 00:45:59.788 --> 00:46:02.355 the beginning, but when it was demonstrated 00:46:03.288 --> 00:46:07.655 how little complexity is associated with the program, with the application, 00:46:07.655 --> 00:46:11.555 how easy it is to use, then many were convinced. 00:46:11.555 --> 00:46:14.488 Particularly since what is brought in there 00:46:15.455 --> 00:46:19.022 becomes visible as a result in the subsequent steps. 00:46:19.322 --> 00:46:20.022 If you look at the whole thing 00:46:20.022 --> 00:46:23.522 from an international perspective, which is also the point of your question, 00:46:24.255 --> 00:46:25.788 then that was where 00:46:25.788 --> 00:46:28.488 we were able to solve something like this using different language packages. 00:46:29.622 --> 00:46:30.888 Although that is also a matrix. 00:46:30.888 --> 00:46:34.322 We have on one dimension, we have the different language packages 00:46:34.388 --> 00:46:38.455 and on the other dimension, we have our sales organization, so to speak. 00:46:38.555 --> 00:46:42.388 In other words, it's a mix, so to speak, of our ERP master data, 00:46:42.455 --> 00:46:45.622 namely the assignment of the products to the sales organizations 00:46:45.722 --> 00:46:49.055 and the application in the various markets and regions. 00:46:49.055 --> 00:46:50.288 When we talk about regions, 00:46:50.288 --> 00:46:53.422 we are very often talking about continents or subcontinents 00:46:53.522 --> 00:46:55.322 that are affected by this, in which we 00:46:55.322 --> 00:46:59.188 can load the corresponding language packages very precisely. 00:46:59.555 --> 00:47:02.488 And that's why we have, as mentioned at the beginning, 00:47:02.488 --> 00:47:07.388 three different English language packages, to give every local office 00:47:07.388 --> 00:47:10.955 around the world the opportunity to design content individually. 00:47:11.388 --> 00:47:14.621 Because nothing is worse than frustration that may build up somewhere 00:47:14.721 --> 00:47:19.055 in the moment because things can't be changed or something like that. 00:47:19.121 --> 00:47:22.788 With that many employees using ANTEROS then 00:47:22.788 --> 00:47:26.221 how is that accepted in your day-to-day work? 00:47:27.388 --> 00:47:30.555 Acceptance is now actually very high, 00:47:30.555 --> 00:47:34.888 because it's quite clear that if not everyone makes their small contribution, 00:47:35.921 --> 00:47:37.955 the whole thing won't be right. 00:47:38.188 --> 00:47:41.288 You can see quite transparently where there are gaps 00:47:42.288 --> 00:47:46.721 due to certain quality gates and so on and so forth that we have built in. 00:47:47.655 --> 00:47:50.588 As a result, every colleague actually 00:47:50.588 --> 00:47:52.521 has a bit of an incentive to avoid being contacted 00:47:52.521 --> 00:47:55.388 by anyone, along the lines of: "Look here, 00:47:55.588 --> 00:48:00.088 there's still something missing, could you please do it now and we'd like to get on with it". 00:48:00.155 --> 00:48:03.021 The other thing is that 00:48:03.121 --> 00:48:06.588 if you integrate it into your regular work routine and workflow, 00:48:06.888 --> 00:48:09.321 then you invest a few minutes every day. 00:48:09.955 --> 00:48:14.555 But if you wait half a year, it will take a little longer, 00:48:14.555 --> 00:48:17.788 then once the willingness is there, you show your 00:48:17.788 --> 00:48:22.288 colleagues: "Look, this is a quality gate report, for example, 00:48:22.288 --> 00:48:25.055 and these are your tasks that result from it. 00:48:25.388 --> 00:48:28.621 It will take 5 minutes to deliver two translations here. 00:48:28.621 --> 00:48:31.055 Do that please, and the work is done. ” 00:48:31.055 --> 00:48:34.355 There is an increase in knowledge that must take place, 00:48:34.355 --> 00:48:37.721 from which, however, understanding is then also established very quickly. 00:48:37.721 --> 00:48:40.954 Is it one person who then coordinates these employees 00:48:40.954 --> 00:48:44.954 or is it a hierarchy or how do you coordinate 00:48:44.954 --> 00:48:46.054 the employees' work now? 00:48:47.021 --> 00:48:50.221 The fact that we are many independent sales organizations 00:48:50.221 --> 00:48:52.754 means that there is no rigid hierarchy in any direction. 00:48:53.488 --> 00:48:57.454 What we do know is who is responsible for what and where in the world. 00:48:57.754 --> 00:49:01.388 And this actually results in a quite flexible composition 00:49:01.821 --> 00:49:06.121 of teams when it comes to certain product rollouts and so on. 00:49:06.888 --> 00:49:10.488 However, there is not one person who would supervise all employees 00:49:10.488 --> 00:49:12.221 as a staff unit somewhere, 00:49:13.054 --> 00:49:16.054 but we have the knowledge of who does what. 00:49:16.888 --> 00:49:21.588 In principle, everyone understands that they have to make their contribution. 00:49:22.288 --> 00:49:25.654 And if certain extended arrangements need to be made, 00:49:25.654 --> 00:49:30.254 these spontaneously assembled teams get together 00:49:30.554 --> 00:49:34.388 as a small group and tackle a problem. 00:49:34.454 --> 00:49:35.254 Quite pragmatic. 00:49:35.354 --> 00:49:36.054 Quite pragmatic. 00:49:36.054 --> 00:49:40.054 In some cases, we approach INCONY via our IT department or via you 00:49:40.821 --> 00:49:44.188 and, to a certain extent, 00:49:44.188 --> 00:49:47.254 tell our user story, tell our idea, 00:49:47.254 --> 00:49:49.921 and present it as a kind of change request, 00:49:50.821 --> 00:49:53.988 so that, let's say, colleagues 00:49:53.988 --> 00:49:56.854 with similar ideas can come together in a very flexible way. 00:49:57.721 --> 00:50:00.221 Be it from South America, be it from, 00:50:00.221 --> 00:50:04.987 be it from North America, be it from Eastern Europe, be it here from Cologne, wherever. 00:50:05.854 --> 00:50:08.254 We exchange ideas 00:50:08.254 --> 00:50:11.687 and work together in teams for as long as it takes, 00:50:11.687 --> 00:50:15.987 as it suits us, in order to achieve this mini-milestone, so to speak. 00:50:16.154 --> 00:50:18.587 And a mini-milestone can mean 00:50:18.587 --> 00:50:20.687 that we want to make a small change. 00:50:20.687 --> 00:50:23.587 We exchange ideas, pass them on to you, and are 00:50:23.587 --> 00:50:26.287 then quickly offered the solution we need. 00:50:26.286 --> 00:50:26.720 Okay.