WEBVTT 00:00:00.120 --> 00:00:02.240 A well-rounded tool, 00:00:02.240 --> 00:00:05.800 which leads to the conclusion that ANTEROS 00:00:05.880 --> 00:00:09.240 today can indeed be seen as a process optimizer. 00:00:09.400 --> 00:00:14.520 We have been able to massively reduce time and personnel costs 00:00:15.080 --> 00:00:17.880 when using ANTEROS. 00:00:18.480 --> 00:00:21.040 We have noticeably improved the quality of the final product, especially when 00:00:21.040 --> 00:00:25.400 we look at the print catalog, we have 00:00:25.840 --> 00:00:29.800 the quality has improved and we have dramatically reduced the error rate, and in addition 00:00:31.200 --> 00:00:34.920 to this process-optimizing function, we have 00:00:35.600 --> 00:00:39.880 also been able to create another structural instrument 00:00:40.240 --> 00:00:43.760 by channeling data and data flows. 00:00:43.960 --> 00:00:48.160 We are looking at really simple intuitive maintenance, 00:00:48.720 --> 00:00:50.120 which is why we 00:00:51.920 --> 00:00:53.880 were able to confidently return the maintenance of our data 00:00:55.880 --> 00:00:58.320 to the hands of product management, 00:00:58.320 --> 00:01:05.480 and we have a very clear risk minimization through the distribution of tasks. 00:01:05.480 --> 00:01:09.160 Whereas in the past 00:01:09.200 --> 00:01:13.040 everything was focused on the marketing department's work, on this graphically based work, 00:01:13.360 --> 00:01:16.120 today we have a much more equitable distribution 00:01:16.120 --> 00:01:20.000 and this in places where the knowledge is actually generated, 00:01:20.000 --> 00:01:24.640 which means that it is simply in good hands in product management. 00:01:28.840 --> 00:01:32.760 We are an electrical wholesaler, a classic wholesale business. 00:01:32.760 --> 00:01:36.720 We have recorded growth here, in some cases in the double-digit percentage range. 00:01:37.640 --> 00:01:40.560 Accordingly, we are naturally also active on several channels 00:01:40.760 --> 00:01:43.040 when it comes to communication and, 00:01:43.760 --> 00:01:46.640 like many other companies, we rely 00:01:46.640 --> 00:01:48.360 on a multi-channel approach. 00:01:49.040 --> 00:01:54.000 But the whole thing is still flanked by print. 00:01:54.400 --> 00:01:55.880 That is also our topic today. 00:01:56.080 --> 00:01:59.080 Print in the form of our stock range catalog. 00:01:59.680 --> 00:02:04.000 The catalog, as the name suggests, shows our entire stock range 00:02:04.000 --> 00:02:07.000 at a glance and is therefore 00:02:07.240 --> 00:02:10.240 more or less regarded as the leading medium in our company. 00:02:10.400 --> 00:02:16.040 It is also still demanded by our clientele. 00:02:16.680 --> 00:02:20.320 We really see it as a work tool, and so do our customers, 00:02:20.640 --> 00:02:22.400 which is why we 00:02:23.480 --> 00:02:26.480 are also faced with the great challenge of producing it. 00:02:26.480 --> 00:02:29.440 So as I mentioned before we and our clientele 00:02:29.440 --> 00:02:32.600 actually see this catalog as a working tool. 00:02:32.760 --> 00:02:36.880 So that means it can't be bigger, it can't be thicker. 00:02:36.920 --> 00:02:39.080 It must be suitable for everyday use. 00:02:39.080 --> 00:02:40.400 It has to fit into glove compartments 00:02:40.880 --> 00:02:44.760 or be pulled out quickly on the construction site. 00:02:45.280 --> 00:02:47.600 We are looking at 850 pages, 00:02:48.440 --> 00:02:51.440 30,000 articles, as I said, subdivided 00:02:51.440 --> 00:02:56.200 into 23 categories, which are then 00:02:56.800 --> 00:02:59.080 also reflected in the tabs on the side, 00:02:59.080 --> 00:03:02.800 that is, in these tabs. 00:03:03.880 --> 00:03:06.560 The big challenge we have is 00:03:07.200 --> 00:03:10.240 that the product range is of course always in motion and growing. 00:03:11.200 --> 00:03:15.080 But we have set ourselves the premise 00:03:15.240 --> 00:03:18.840 that the catalog cannot get any longer 00:03:18.840 --> 00:03:21.360 than the 850 pages we have set. 00:03:21.360 --> 00:03:22.680 We have a very fixed scope. 00:03:23.200 --> 00:03:27.720 Yesterday, if we just take a look at yesterday: 00:03:28.120 --> 00:03:30.920 We were using a template-based approach. 00:03:30.920 --> 00:03:33.920 We initiated template-based print generation. 00:03:33.920 --> 00:03:34.680 It was mostly 00:03:36.200 --> 00:03:37.600 done with InDesign. 00:03:37.600 --> 00:03:42.040 This limited the range of users, because InDesign is really 00:03:43.120 --> 00:03:44.560 a program for graphic artists. 00:03:45.440 --> 00:03:48.840 You have to have an affinity for it and a certain amount of prior knowledge. 00:03:52.960 --> 00:03:58.680 Within this framework, we were looking at a processing or post-processing time 00:03:58.680 --> 00:04:00.920 of a good six months, 00:04:01.200 --> 00:04:01.960 which is of course 00:04:03.880 --> 00:04:05.520 an immense amount of time, 00:04:05.520 --> 00:04:07.480 it took an immense amount of time 00:04:07.480 --> 00:04:12.240 and also the personnel effort in the creation of the catalog. 00:04:12.640 --> 00:04:13.960 That has changed today. 00:04:13.960 --> 00:04:15.400 Thank goodness. 00:04:15.920 --> 00:04:19.320 More or less, with the use of ANTEROS, 00:04:19.320 --> 00:04:20.840 we have taken a big step forward. 00:04:21.040 --> 00:04:24.520 Today, we use ANTEROS as a PIM 00:04:24.520 --> 00:04:26.960 for both print and digital. 00:04:27.880 --> 00:04:30.040 We no longer see catalog 00:04:30.040 --> 00:04:31.880 creation as a one-off process, 00:04:31.880 --> 00:04:36.640 but as a continuous process. 00:04:37.240 --> 00:04:40.640 We also have the great advantage 00:04:40.880 --> 00:04:44.240 of being able to centralize data maintenance. 00:04:44.240 --> 00:04:48.520 That means we have this one place where catalog-relevant data really accumulates. 00:04:48.520 --> 00:04:50.480 In this case, it's called ANTEROS. 00:04:50.920 --> 00:04:56.400 And in addition, the workload is distributed much more fairly 00:04:56.400 --> 00:04:58.280 and takes place 00:04:58.280 --> 00:05:01.960 where it should, that is, to a large extent in product management. 00:05:01.960 --> 00:05:03.040 ANTEROS has given us 00:05:03.040 --> 00:05:06.200 the opportunity to significantly expand our user base. 00:05:06.560 --> 00:05:11.360 While that was still very, very limited when InDesign was used, 00:05:11.440 --> 00:05:14.440 today we can ensure via ANTEROS accesses 00:05:14.520 --> 00:05:17.200 that the data is processed in the place 00:05:17.200 --> 00:05:21.320 where it makes the most sense, where the information is also generated. 00:05:21.600 --> 00:05:24.480 So much for today and yesterday, 00:05:24.480 --> 00:05:28.920 how it looks exactly in detail in the implementation - Mr. Demmer. 00:05:29.600 --> 00:05:33.280 Well, what we're seeing here now is a look at 00:05:34.280 --> 00:05:37.280 the data flow, so what's happening. 00:05:37.360 --> 00:05:39.920 Every day there are new articles, 00:05:40.520 --> 00:05:43.240 some of which are then also included in the warehouse assortment, 00:05:43.240 --> 00:05:47.240 and this product maintenance first takes place 00:05:47.240 --> 00:05:52.480 in our ERP, where the master data for the articles is stored, 00:05:52.960 --> 00:05:57.120 and every night there is an update in the direction of ANTEROS, so that 00:05:58.200 --> 00:06:02.040 we have this central location with all the articles that are to be included in the catalog. 00:06:02.040 --> 00:06:07.080 That means our product managers can look at it and see "Okay, what are my articles, 00:06:07.360 --> 00:06:10.960 which one do I still have to edit here?" and then 00:06:10.960 --> 00:06:12.440 precisely this work is done. 00:06:12.440 --> 00:06:19.120 The articles are assigned, the articles are assigned to product families, 00:06:19.120 --> 00:06:20.560 they get pictures 00:06:20.560 --> 00:06:25.080 the assignment of the logos happens automatically. 00:06:25.200 --> 00:06:29.840 The information that we have in the PIM - that is where we have the manufacturers with logos. 00:06:30.160 --> 00:06:32.960 From the ERP, of course, the article also states 00:06:33.040 --> 00:06:37.120 "Who is the manufacturer here?", so you don't have to worry about that either. 00:06:38.640 --> 00:06:41.960 Of course, we use this data, this treasure trove of data that is being built up 00:06:42.680 --> 00:06:45.160 for or our catalog, but not only that, 00:06:45.160 --> 00:06:48.360 we also transfer the data to our online store. 00:06:48.560 --> 00:06:51.120 We also transfer the data to all other print products 00:06:51.120 --> 00:06:56.400 that we also use from ANTEROS, so that it is not only done 00:06:57.440 --> 00:07:01.520 for this one medium, but also for all others. 00:07:03.400 --> 00:07:05.360 That's why it makes sense to maintain 00:07:05.360 --> 00:07:06.560 the catalog throughout the year 00:07:06.560 --> 00:07:10.880 that means that I, as a product manager, have a new article and of course I want 00:07:10.880 --> 00:07:14.800 all the information to be in the online store immediately 00:07:14.920 --> 00:07:18.520 and therefore have the motivation to maintain the data immediately. 00:07:19.600 --> 00:07:20.400 I have - 00:07:21.200 --> 00:07:26.280 In addition, this also gives us the opportunity to make data immediately visible. 00:07:26.560 --> 00:07:30.400 And that's always a good key to just say, "Okay, 00:07:30.480 --> 00:07:34.040 you can see the data immediately, so it makes sense to maintain it immediately." 00:07:34.240 --> 00:07:38.720 And of course we also have much more time to notice errors. 00:07:38.800 --> 00:07:42.720 That means when we go via our online store here, which is looked at by thousands of customers 00:07:42.720 --> 00:07:45.880 every day, errors naturally stand out. 00:07:45.880 --> 00:07:48.880 There are ways to report them. 00:07:48.880 --> 00:07:51.960 So that you also get a feedback loop here all by itself. 00:07:52.120 --> 00:07:55.480 So you no longer have to say, "Okay, we're going to create the catalog 00:07:55.800 --> 00:07:57.760 and we'll all take a look at it together 00:07:57.760 --> 00:08:01.840 to see if we notice anything," as you did in the past; 00:08:02.080 --> 00:08:08.120 instead, the data is immediately available for productive use and thus naturally reaches a certain level of maturity. 00:08:08.120 --> 00:08:10.600 Conversely, this also means 00:08:10.720 --> 00:08:14.400 that when I correct an error, it is immediately visible. 00:08:14.520 --> 00:08:17.560 In the past, we often had this situation where we 00:08:18.200 --> 00:08:21.400 had an error, very obvious, and in the end 00:08:21.400 --> 00:08:25.320 either a lot of people reported it, there are cases of that, just when 00:08:25.320 --> 00:08:29.080 the catalog is freshly published, but sometimes no one did. 00:08:29.120 --> 00:08:32.040 Which could be explained by the fact 00:08:32.040 --> 00:08:34.560 that everyone thought: "It's such an obvious mistake, 00:08:34.560 --> 00:08:36.920 it will already have been noticed and corrected. 00:08:36.920 --> 00:08:40.680 And I shouldn’t be the 3000th person to report this error". 00:08:40.680 --> 00:08:43.720 And now there are quite different possibilities. 00:08:43.920 --> 00:08:47.520 Now you can say: "Okay, I see the error in the catalog", 00:08:47.520 --> 00:08:52.480 look in our online store and see "okay, the error is corrected". 00:08:52.800 --> 00:08:53.880 I can relax again, 00:08:53.880 --> 00:08:57.680 everything is fine, or I just notice "Yes, okay, the error is still there". 00:08:57.680 --> 00:09:01.200 So it makes total sense to say now: "Okay, I'll go to 00:09:01.200 --> 00:09:03.440 our product management and say "okay, I've noticed 00:09:03.440 --> 00:09:06.400 something here, maybe you can look at it again". 00:09:06.520 --> 00:09:09.600 So that's what's happening in the background now. 00:09:10.240 --> 00:09:12.960 How does the data flow, what is it used for? 00:09:12.960 --> 00:09:14.000 Where does it go? 00:09:14.560 --> 00:09:17.160 Which is also important, of course, when you take this step and say, 00:09:17.160 --> 00:09:21.200 "Okay, I would now like us to no longer do this task in marketing, 00:09:21.200 --> 00:09:24.760 where we actually do very graphically oriented work, 00:09:24.960 --> 00:09:26.560 but in the specialist departments." 00:09:26.920 --> 00:09:28.880 Then it's just important 00:09:28.880 --> 00:09:32.680 that it's simple, that it's easy, that I understand it immediately 00:09:33.000 --> 00:09:36.360 and that I can see the inputs that I make immediately. 00:09:36.440 --> 00:09:39.440 This knowledge about the product is really with 00:09:40.240 --> 00:09:45.280 our product management, with the colleagues who decide 00:09:45.280 --> 00:09:48.400 which article to put in the warehouse, where should it be in the catalog? 00:09:48.400 --> 00:09:49.760 So all these considerations 00:09:49.760 --> 00:09:54.680 that you actually have to make when you place a product in the catalog 00:09:55.920 --> 00:09:59.960 and the actual implementation - that now happens with one person. 00:10:01.040 --> 00:10:03.560 From one category to another, it's someone else, 00:10:03.560 --> 00:10:07.400 but the many arrangements that had to take place in the past 00:10:07.400 --> 00:10:09.080 are no longer necessary. 00:10:09.920 --> 00:10:12.960 And in order to take a step like that, to say, okay, 00:10:12.960 --> 00:10:15.080 the task is no longer here, but here 00:10:15.280 --> 00:10:19.600 because we see these and those benefits, it is incredibly important 00:10:19.600 --> 00:10:22.520 that the operation and handling is relatively 00:10:22.520 --> 00:10:26.920 simple and that no large and long training processes are necessary. 00:10:27.000 --> 00:10:30.280 Especially because we say, okay, we don't want to 00:10:30.280 --> 00:10:33.640 maintain this data only once a year, but we want it to be done continuously 00:10:33.640 --> 00:10:37.800 - the whole year, of course there cannot be any big barriers 00:10:37.800 --> 00:10:41.840 that you have to think about for a long time again, how was that done, 00:10:41.920 --> 00:10:46.600 but the goal was to say okay, I'm going to do it now, 00:10:46.600 --> 00:10:49.600 I've done it before and I can work right now. 00:10:49.720 --> 00:10:51.560 We now have this interface. 00:10:51.800 --> 00:10:57.600 We have the great advantage that in ANTEROS it is possible, 00:10:57.880 --> 00:11:04.080 depending on the task, to adapt the web interface and the data entry masks 00:11:04.080 --> 00:11:06.640 in a way that best suits the specific task. 00:11:07.600 --> 00:11:11.880 It would even be possible to set this per employee, to say okay, 00:11:11.880 --> 00:11:13.960 one works like this, the other works like this. 00:11:13.960 --> 00:11:15.840 You can do that, but you don't have to. 00:11:15.840 --> 00:11:20.320 We have decided to do this per task, 00:11:20.320 --> 00:11:24.840 so that we now have a mask that we have set up to the point 00:11:24.840 --> 00:11:27.880 where you can really do the entire investment process 00:11:27.880 --> 00:11:29.400 within one mask. 00:11:29.880 --> 00:11:33.440 The work that is then necessary is to say, not only okay, 00:11:33.440 --> 00:11:37.160 the product should be in the catalog, but you have to think about this: 00:11:37.160 --> 00:11:42.440 "Okay, I now have a product family that must be placed in the catalog. 00:11:42.440 --> 00:11:43.880 What category does this fit into? 00:11:44.120 --> 00:11:46.600 Do subcategories perhaps need to be created?" 00:11:47.560 --> 00:11:53.160 And then to say at the end, okay, the article must now be included in this product family 00:11:53.760 --> 00:11:57.480 and the order of the products should now perhaps be adjusted 00:11:57.480 --> 00:12:01.200 so that it makes as much sense as possible 00:12:01.640 --> 00:12:04.720 and navigation in the catalog is very simple. 00:12:04.840 --> 00:12:09.640 So now we don't have to leave the mask and the best thing is 00:12:10.600 --> 00:12:15.400 that we have a very theoretical task here for the time being, i.e. 00:12:15.400 --> 00:12:19.600 assigning, arranging, labeling, changing an order. 00:12:20.400 --> 00:12:23.920 The great thing is that one click on print generation 00:12:23.920 --> 00:12:28.440 and our product managers immediately see: "Okay, that has now worked. 00:12:28.440 --> 00:12:30.920 That's exactly how I imagined it". 00:12:31.160 --> 00:12:35.200 Or, conversely: "Okay, that's not yet how I imagined it. 00:12:35.200 --> 00:12:37.040 I have to do it again; I want to change something again". 00:12:37.320 --> 00:12:40.960 That, too, is something that ultimately affects the quality of the product. 00:12:41.560 --> 00:12:46.440 Finally, I would like to say that 00:12:46.440 --> 00:12:47.960 when we are on the home stretch 00:12:47.960 --> 00:12:51.160 of generating the print catalog and the print shop is starting 00:12:51.480 --> 00:12:55.320 to get nervous, we can then see on the home stretch: 00:12:55.320 --> 00:12:56.320 "Where do we stand? 00:12:56.320 --> 00:12:59.120 Where do we have - where is there possibly still a need for work?". 00:12:59.320 --> 00:13:02.120 So we with marketing, who are then ultimately 00:13:02.120 --> 00:13:04.760 - who are responsible for the print product itself. 00:13:05.400 --> 00:13:08.160 We can immediately see where we stand. 00:13:08.240 --> 00:13:13.040 Generating the catalog overnight or generating individual chapters on an ad hoc basis 00:13:13.040 --> 00:13:17.160 saves us an incredible amount of time. And 00:13:18.520 --> 00:13:21.440 it makes us happy in the end, thank God, 00:13:22.160 --> 00:13:24.520 when we see that we are on the right track. 00:13:24.880 --> 00:13:27.160 The next slide - it's about image maintenance. 00:13:27.480 --> 00:13:30.840 Of course, in a good catalog there should be pictures, pictures of the product. 00:13:31.680 --> 00:13:34.280 We maintain our images, because we have this space issue, 00:13:34.280 --> 00:13:37.280 at the product family level, or maybe even one level higher. 00:13:39.360 --> 00:13:44.640 One thing to highlight is, okay, we do it all through ANTEROS, we upload the images. 00:13:45.840 --> 00:13:49.880 We get very much from the process, that is, the images are provided by our product managers, 00:13:49.880 --> 00:13:52.640 who might get those from suppliers. 00:13:52.880 --> 00:13:58.560 And what makes it particularly pleasant and effective is that we have a step in the upload process 00:13:59.000 --> 00:14:03.800 where we don't say, "I have a product family, 00:14:03.800 --> 00:14:06.440 I want to assign an image to this product family, I upload 00:14:06.480 --> 00:14:10.920 this image," but what we were able to implement together with INCONY 00:14:10.920 --> 00:14:13.680 for ANTEROS is that we say, "Okay, 00:14:13.680 --> 00:14:17.560 we avoid large ZIP files with 100 to 200 images that have been 00:14:17.560 --> 00:14:18.880 processed by our marketing 00:14:18.880 --> 00:14:23.080 We now provide those here, ANTEROS imports 00:14:23.080 --> 00:14:26.600 those and then automatically assigns the images to the product family 00:14:27.680 --> 00:14:30.120 based on the name of the image." 00:14:30.960 --> 00:14:32.640 This small change alone 00:14:33.760 --> 00:14:37.600 has saved so much work, because - if you think about it, 00:14:37.600 --> 00:14:40.960 if you now have 100 images, put in the product family 100 times, 00:14:40.960 --> 00:14:45.800 upload the image 100 times, confirm 100 times, watch it upload 100 times 00:14:46.120 --> 00:14:48.800 and then check again if that really worked. 00:14:49.120 --> 00:14:52.000 What it has become is, we take the file, upload it, 00:14:52.000 --> 00:14:54.520 and the work is ultimately done. 00:14:55.760 --> 00:14:58.120 We also get a full log afterwards. 00:14:58.120 --> 00:15:00.520 Where did it work? Where did it not work? 00:15:00.520 --> 00:15:03.080 If there is information there that maybe it didn't - 00:15:03.080 --> 00:15:05.400 that it didn't work, that we have a warning or an error, 00:15:05.400 --> 00:15:09.320 then you look at these cases again very specifically and also don't 00:15:09.320 --> 00:15:12.320 have the danger of pictures getting lost or being forgotten. 00:15:12.480 --> 00:15:15.720 What makes me very happy as a person with an affinity for design 00:15:15.720 --> 00:15:20.280 is the fact that we are also really 00:15:21.320 --> 00:15:24.920 very flexible in the visualization of the product itself. 00:15:25.080 --> 00:15:27.000 To go into detail, we have now 00:15:27.000 --> 00:15:31.640 divided the catalog into 23 main categories, 00:15:32.120 --> 00:15:36.480 which in turn are reflected in the tabs on the page. 00:15:36.880 --> 00:15:41.640 We were able to assign a color to each category, 00:15:41.640 --> 00:15:47.880 and we were able to store icons via the image assets, 00:15:47.880 --> 00:15:50.880 which then all come into play in this - in the context of this tab punching. 00:15:51.000 --> 00:15:54.480 Within the categories, i.e. within the special chapters, 00:15:54.760 --> 00:15:59.120 we can select different color shades, which simply 00:16:00.160 --> 00:16:03.320 guarantees a sophisticated, professional appearance. 00:16:03.840 --> 00:16:07.440 This then went so far that we also said: Well, 00:16:07.480 --> 00:16:11.160 we have clear corporate design guidelines, 00:16:11.600 --> 00:16:16.200 but we also break them to a certain extent by simply 00:16:16.480 --> 00:16:20.440 transferring these catalog categories to other areas of the company 00:16:20.720 --> 00:16:25.320 and, within this framework, we have adapted the colors 00:16:25.600 --> 00:16:28.600 and adopted the icons, which are then used in other areas. 00:16:28.600 --> 00:16:31.960 Whether it is in a local store, for example, on the store floor, 00:16:32.320 --> 00:16:38.880 or in digital channels, such as an app, for example, where the exact colors 00:16:39.760 --> 00:16:41.200 can be used, 00:16:41.320 --> 00:16:44.120 meaning you can always, - that we – 00:16:44.120 --> 00:16:49.320 it is important to us, for marketing strategy reasons, to always be recognizable. 00:16:49.560 --> 00:16:53.720 We have them - they are actually based more or less on ANTEROS, 00:16:53.720 --> 00:16:57.920 in that we have adapted them to other areas of the company. 00:16:58.160 --> 00:16:59.920 That was very important to me personally. 00:16:59.920 --> 00:17:04.480 What we - what's also important to emphasize about the process is: 00:17:05.440 --> 00:17:08.320 We come from the print world and then maybe we realize, 00:17:08.320 --> 00:17:11.240 the one color that's very, very nice in print, 00:17:11.680 --> 00:17:15.360 maybe it doesn't work so well on a phone 00:17:15.640 --> 00:17:18.760 or we realize that we want to change the colors. 00:17:18.760 --> 00:17:22.240 Then these are all things that we can do ourselves in ANTEROS. 00:17:22.240 --> 00:17:25.400 That means we just try it out, we change the color, 00:17:25.400 --> 00:17:28.840 we generate the PDF, maybe print it out again, 00:17:29.000 --> 00:17:32.640 and then immediately have feedback and know, 00:17:32.640 --> 00:17:35.640 "Okay, is this going in the direction we thought it was going 00:17:35.680 --> 00:17:37.320 or are we going to undo this?" 00:17:38.000 --> 00:17:39.160 We can just try that out. 00:17:40.960 --> 00:17:46.080 As my colleague Mr. Pfender mentioned at the beginning, space is a huge problem. 00:17:46.400 --> 00:17:47.800 We have the fixed number of pages 00:17:48.760 --> 00:17:50.960 and for that we need solutions. 00:17:50.960 --> 00:17:54.080 A big part of the solutions comes from ANTEROS. 00:17:54.080 --> 00:17:56.000 So we have done different things. 00:17:56.200 --> 00:18:00.520 For example, what we do is that within chapters - 00:18:00.520 --> 00:18:04.680 you see now an example page - what we do for example is 00:18:04.680 --> 00:18:06.200 that we change from two-column design 00:18:06.200 --> 00:18:09.960 to three-column design within a chapter. 00:18:11.560 --> 00:18:13.680 This has the following advantage, for example, 00:18:13.680 --> 00:18:16.800 that if we have a lot of text, it's more space-saving 00:18:16.920 --> 00:18:20.520 if we use the width, because then we don't have to pay attention to the breaks. 00:18:20.520 --> 00:18:22.240 If we have very little text, 00:18:22.240 --> 00:18:25.520 then it makes sense to use a three-column design, 00:18:25.720 --> 00:18:28.320 so that in the phase where we say, "Okay, 00:18:28.320 --> 00:18:30.440 it's now moving towards the final product," we can here - 00:18:31.440 --> 00:18:33.760 do we have something in the bag again to say okay, 00:18:33.760 --> 00:18:36.920 can we get another half a page or a full page in 00:18:37.000 --> 00:18:41.080 and we can also generate benefits for the customer here, 00:18:41.320 --> 00:18:44.680 because it's a little bit easier to read in the two-column design 00:18:44.680 --> 00:18:45.920 if you have longer texts. 00:18:46.200 --> 00:18:53.960 That means in chapters where explanations are needed and we have a lot of text, we use two columns. 00:18:53.960 --> 00:18:58.480 Where we have a lot of products, we tend to use three columns. 00:18:58.840 --> 00:19:03.000 In addition, we have another function that saves us a lot of space. 00:19:03.000 --> 00:19:07.680 What we do in catalog generation is that we say, okay, there are 00:19:08.120 --> 00:19:11.640 thoughts that say, okay, it now makes sense to have this product 00:19:11.720 --> 00:19:16.360 on the next page, or you don't necessarily want 00:19:16.360 --> 00:19:21.880 such a product family to be broken in an unfavorable way, and then we work with breaks. 00:19:22.480 --> 00:19:26.840 What we don't want then is for the catalog to look, well, disjointed. 00:19:26.840 --> 00:19:30.200 That is, at the bottom you can always see exactly where 00:19:30.200 --> 00:19:31.440 there would have been three centimeters of space, 00:19:31.440 --> 00:19:35.320 where there would have been two centimeters of space, and where it just fit. 00:19:35.640 --> 00:19:40.600 Our requirement was to say, okay, the line at the bottom should always be the same. 00:19:41.000 --> 00:19:45.640 That's why we do two print generations for this product. 00:19:45.640 --> 00:19:48.920 That is first the products set on the page 00:19:48.960 --> 00:19:52.560 and then the distance between the product families varies, 00:19:52.960 --> 00:19:56.600 so that it - the appearance of the page - always looks the same 00:19:56.920 --> 00:19:59.040 and we have the stability that we want to have. 00:20:00.040 --> 00:20:02.200 We want to avoid that, 00:20:02.200 --> 00:20:05.560 although we try to show as many articles as possible 00:20:05.880 --> 00:20:07.640 on one page, 00:20:08.560 --> 00:20:12.240 it should still look stable 00:20:12.560 --> 00:20:14.520 and it should be easy to find one's way around 00:20:14.520 --> 00:20:17.600 on the page and we have managed that very well. 00:20:18.200 --> 00:20:22.520 This way we ensure - with this stable presentation of the catalog page 00:20:22.600 --> 00:20:25.680 a certain reading flow 00:20:26.320 --> 00:20:28.480 without it flopping to the bottom. 00:20:28.760 --> 00:20:31.320 Perhaps another issue that should be highlighted 00:20:31.320 --> 00:20:34.320 is that in the past, 00:20:34.480 --> 00:20:37.560 when we were still template-based, 00:20:39.760 --> 00:20:41.440 we were always faced with a problematic creation 00:20:41.440 --> 00:20:44.440 of the keyword and manufacturer index. 00:20:44.680 --> 00:20:48.680 That was nerve-wracking, people got in each other's hair at times. 00:20:49.240 --> 00:20:50.560 Today, and this is 00:20:50.560 --> 00:20:55.240 not necessarily an exaggeration, we can create a 00:20:55.240 --> 00:20:59.040 keyword and manufacturer directory at the push of a button. 00:21:00.000 --> 00:21:02.880 The synonyms are maintained, the logos are maintained, 00:21:02.880 --> 00:21:05.960 and then both things are created practically 00:21:06.760 --> 00:21:09.480 at the push of a button, which of course 00:21:09.480 --> 00:21:12.200 saves us an incredible amount of time and work. 00:21:12.680 --> 00:21:15.400 On the slide all about the data, we've already shown that. 00:21:15.520 --> 00:21:17.440 We don't just do this one catalog. 00:21:18.040 --> 00:21:20.320 There is the one big catalog 00:21:20.320 --> 00:21:25.120 that comes out once a year, that's of course the most exciting thing. 00:21:25.120 --> 00:21:27.560 But what we also do, and we can do this thanks to 00:21:27.560 --> 00:21:34.920 ANTEROS, is that we say, okay, we'll make individual excerpt catalogs for customers. 00:21:35.280 --> 00:21:39.000 For example, we say, okay, there is a larger project here, there are 00:21:40.440 --> 00:21:42.880 articles that are needed for it, 00:21:43.120 --> 00:21:46.800 and we provide them to the customer so that they can easily 00:21:47.200 --> 00:21:51.200 find their way around, which articles are needed here. 00:21:51.440 --> 00:21:55.720 What we also do with that is this omni channel idea. 00:21:55.720 --> 00:21:57.240 We always try to say, okay, 00:21:57.240 --> 00:22:00.880 we have the print and we have our online store and we have our app. 00:22:00.880 --> 00:22:03.520 So what we do there is, we provide the customer 00:22:03.520 --> 00:22:07.360 with their individual catalog with barcodes 00:22:07.800 --> 00:22:11.200 and then with our app they can say again, "Okay, I want to 00:22:12.160 --> 00:22:17.280 buy this, this and this item." It does that with the barcode scanner function. 00:22:18.040 --> 00:22:20.680 The big advantage is the process. 00:22:20.680 --> 00:22:22.960 So we support the process of our customers. 00:22:24.800 --> 00:22:28.160 Our customer only wants to use certain items 00:22:28.160 --> 00:22:34.760 on a construction site, and we make them available via the customer-specific catalog. 00:22:35.240 --> 00:22:39.680 Through our app, the ordering process is supported in the best possible way, as far as - 00:22:40.880 --> 00:22:44.160 imagine this: Our customer's mechanic is 00:22:44.160 --> 00:22:46.880 on the construction site, has to make another order, thinking "Which consumables 00:22:46.880 --> 00:22:50.120 do I need on this construction site?" they scan them with the app. 00:22:50.560 --> 00:22:54.080 Our customers’ buyer 00:22:54.520 --> 00:22:56.600 gets the message on their computer, 00:22:56.800 --> 00:23:01.600 confirms the input made by their mechanic and the goods are on the construction site the next day. 00:23:01.640 --> 00:23:08.200 This completes the process and creating these catalogs, it just very, very simple. 00:23:08.200 --> 00:23:12.840 We have an Excel upload function in ANTEROS. 00:23:12.920 --> 00:23:15.840 So we say - which articles should it be? 00:23:15.840 --> 00:23:18.680 We can even include which prices are to be shown, 00:23:19.400 --> 00:23:21.400 and then the catalog is there. 00:23:22.240 --> 00:23:24.360 We even go so far as to create catalogs for our customers, 00:23:24.360 --> 00:23:27.000 which they then pass on to the end customer. 00:23:28.440 --> 00:23:32.920 And the effort on our side is kept to a minimum. 00:23:33.400 --> 00:23:35.600 The catalog is there; the data is maintained. 00:23:35.600 --> 00:23:39.560 All we have to do is say which articles are available at which prices, and that's it. 00:23:39.960 --> 00:23:42.080 A well-rounded tool, 00:23:42.080 --> 00:23:45.640 which leads to the conclusion that ANTEROS 00:23:45.720 --> 00:23:49.080 today can indeed be seen as a process optimizer. 00:23:49.240 --> 00:23:54.360 We have been able to massively reduce time and personnel costs 00:23:54.920 --> 00:23:57.720 when using ANTEROS. 00:23:58.320 --> 00:24:00.880 We have noticeably improved the quality of the final product, especially when 00:24:00.880 --> 00:24:05.240 we look at the print catalog, we have 00:24:05.680 --> 00:24:09.640 the quality has improved and we have dramatically reduced the error rate, and in addition 00:24:11.040 --> 00:24:14.760 to this process-optimizing function, we have 00:24:15.440 --> 00:24:19.720 also been able to create another structural instrument 00:24:20.080 --> 00:24:23.600 by channeling data and data flows. 00:24:23.800 --> 00:24:28.000 We are looking at really simple intuitive maintenance, 00:24:28.560 --> 00:24:29.960 which is why we 00:24:31.760 --> 00:24:33.720 were able to confidently return the maintenance of our data 00:24:35.720 --> 00:24:38.160 to the hands of product management, 00:24:38.160 --> 00:24:45.320 and we have a very clear risk minimization through the distribution of tasks. 00:24:45.320 --> 00:24:49.000 Whereas in the past 00:24:49.040 --> 00:24:52.880 everything was focused on the marketing department's work, on this graphically based work, 00:24:53.200 --> 00:24:55.960 today we have a much more equitable distribution 00:24:55.960 --> 00:24:59.840 and this in places where the knowledge is actually generated, 00:24:59.840 --> 00:25:04.480 which means that it is simply in good hands in product management. 00:25:05.320 --> 00:25:10.200 Once again the outlook: What are we actually doing right now? 00:25:10.640 --> 00:25:14.160 As a company, we are currently in the middle of the implementing SAP. 00:25:15.680 --> 00:25:18.760 A project that of course also affects the PIM. 00:25:19.680 --> 00:25:22.080 Our article numbers are changing 00:25:22.600 --> 00:25:24.600 and all interfaces have to be redone. 00:25:24.600 --> 00:25:25.560 We have 00:25:26.080 --> 00:25:28.480 seen the slide about where the interfaces are 00:25:28.880 --> 00:25:33.120 and there we are in the process of setting up a staging system. 00:25:33.120 --> 00:25:35.000 We are in the process of connecting SAP. 00:25:37.120 --> 00:25:40.120 We have the interfaces, iDocs can be worked with 00:25:40.520 --> 00:25:44.040 and so we are really looking forward here 00:25:45.480 --> 00:25:49.480 to take ANTEROS into the future and use it as our tool 00:25:50.600 --> 00:25:54.320 for product data, product data with print generation. 00:25:55.480 --> 00:25:57.880 Yes, thank you very much for the presentation, a very good one. 00:25:57.880 --> 00:26:00.640 Now I'm going to start the first round of questions 00:26:00.640 --> 00:26:05.600 and I'd like to start with this: Mr. Pfender, you mentioned at the beginning 00:26:05.800 --> 00:26:10.520 that you had previously worked with the template-based approach, which was almost ten years ago, 00:26:10.640 --> 00:26:11.120 Exactly. 00:26:11.600 --> 00:26:14.480 that it took you six months 00:26:14.480 --> 00:26:18.120 to generate a catalog at all, a single catalog. 00:26:18.120 --> 00:26:18.640 Absolutely. 00:26:19.840 --> 00:26:21.880 How long does it take now with ANTEROS? 00:26:23.240 --> 00:26:25.400 I hardly dare to say it, but in 00:26:25.400 --> 00:26:28.760 the last few years we've been able to - well, of course we've 00:26:29.200 --> 00:26:32.400 also tightened up the processes a bit, 00:26:32.400 --> 00:26:36.760 but today we're looking at a really concentrated workload 00:26:36.880 --> 00:26:41.080 in the catalog process of maybe a month - at the most. 00:26:41.080 --> 00:26:46.200 So if there are other projects going on at the same time, then we can definitely tighten things up. 00:26:46.400 --> 00:26:50.080 And this month that means data maintenance for you, that you look 00:26:50.240 --> 00:26:53.800 at which chapters have which colors or what kind of work needs to be done? 00:26:53.800 --> 00:26:56.040 No, data maintenance actually takes place 00:26:57.080 --> 00:27:01.280 continuously throughout the year because we also feed other systems. 00:27:01.480 --> 00:27:04.600 We then really take care of it: Where might something still be missing? 00:27:04.600 --> 00:27:07.720 We sift through the data more intensively, 00:27:07.720 --> 00:27:11.800 we go even deeper into this already continuous process. 00:27:12.040 --> 00:27:12.800 Yeah, okay. 00:27:13.680 --> 00:27:16.400 Now there is a function 00:27:16.480 --> 00:27:20.040 that some of our other customers use, which is the correction mode. 00:27:20.040 --> 00:27:22.760 This means that you can generate a print catalog 00:27:22.760 --> 00:27:26.200 and click on it directly when you proofread it. 00:27:26.560 --> 00:27:31.120 Do your employees also use this intensively, or how do you 00:27:31.400 --> 00:27:33.520 go about actually proofreading 00:27:34.800 --> 00:27:40.200 and adding or correcting incorrect data? 00:27:40.200 --> 00:27:42.400 The correction mode is, of course, well known. 00:27:42.400 --> 00:27:48.520 I have to say, it's not really widely used yet, because we're 00:27:48.520 --> 00:27:52.240 putting the experts directly on it, who are ultimately responsible 00:27:52.240 --> 00:27:55.040 for the content and ensure it accordingly. 00:27:55.040 --> 00:27:57.680 That's why it's not being discussed very intensively at the moment. 00:27:57.680 --> 00:28:01.800 But if we are in an exchange, if there are interdepartmental things, 00:28:02.000 --> 00:28:05.320 then of course we use it, but until then 00:28:05.720 --> 00:28:09.120 each individual product manager, who is also responsible 00:28:09.120 --> 00:28:13.080 for certain categories and subject areas, ensures it anyway. 00:28:13.080 --> 00:28:16.360 Of course, we use it for interdepartmental matters. 00:28:16.760 --> 00:28:19.480 Last question and then we'll ask the audience. 00:28:19.480 --> 00:28:23.080 Namely, you had already mentioned the topic of excerpt catalogs. 00:28:23.120 --> 00:28:25.720 That is of course an exciting thing, how you use it. 00:28:26.520 --> 00:28:29.840 And I understood that in some cases 00:28:29.840 --> 00:28:33.920 your sales people upload something in Excel files and 00:28:34.520 --> 00:28:38.400 determine which articles they need right now as an excerpt catalog, 00:28:38.400 --> 00:28:41.480 and you can also select the prices and then generate the catalog. 00:28:41.800 --> 00:28:44.080 Who is the target group? Who are they doing it for? 00:28:44.080 --> 00:28:47.480 Are they large projects at large construction sites? 00:28:49.480 --> 00:28:52.240 So those are, - 00:28:53.200 --> 00:28:56.680 it's very easy to do, that's why our colleagues in sales do it. 00:28:56.680 --> 00:28:58.800 That means that the additional work takes place in sales. 00:28:58.800 --> 00:29:01.960 In the end, we just get this Excel file 00:29:03.040 --> 00:29:07.240 and we do it for customers where we think it's 00:29:07.240 --> 00:29:08.920 really a useful addition 00:29:09.360 --> 00:29:11.000 and the decision 00:29:11.000 --> 00:29:14.160 for whom we do it is, of course, up to our colleagues in sales. 00:29:14.360 --> 00:29:17.880 They really do it all by themselves, without you in marketing / IT? 00:29:18.040 --> 00:29:21.080 Well, we generate the catalog. 00:29:21.480 --> 00:29:25.160 It then has to be put on paper and bound. 00:29:25.160 --> 00:29:28.080 That is something that naturally takes place in the relevant departments. 00:29:29.400 --> 00:29:30.880 But what we do - 00:29:31.520 --> 00:29:36.040 the target group is of course either customers, where it makes sense. 00:29:36.040 --> 00:29:41.440 So a nice example is really the installer who goes to the customer 00:29:41.440 --> 00:29:45.080 to repair things and then has a price list with them. 00:29:45.320 --> 00:29:48.720 And the electrical installation company, 00:29:48.720 --> 00:29:52.920 let's say three people, of course they don't have a catalog department 00:29:54.200 --> 00:29:55.200 and for them it's helpful. 00:29:55.320 --> 00:29:56.520 For them, it's very helpful to say: 00:29:56.520 --> 00:30:01.720 "Okay, I'll get a catalog here now and I can influence which article I want" - 00:30:02.720 --> 00:30:06.120 which should ultimately lead to us selling more, of course. 00:30:07.080 --> 00:30:13.680 Then perhaps it should also be said that with 30,000 stock items shown, give or take a few, 00:30:13.680 --> 00:30:17.440 there is of course always movement in there. 00:30:17.640 --> 00:30:21.800 Sales are - we look at certain product cycles, some are 00:30:22.800 --> 00:30:25.000 discontinued, some simply expire. 00:30:25.000 --> 00:30:29.080 And of course, a print catalog 00:30:29.080 --> 00:30:33.880 that we publish once a year becomes outdated relatively quickly. 00:30:34.000 --> 00:30:36.360 It is then only there for orientation purposes, 00:30:36.600 --> 00:30:41.560 which is why we also publish dedicated catalogs from time to time. 00:30:41.560 --> 00:30:44.800 Especially in areas where there are particularly fast - 00:30:44.800 --> 00:30:47.840 particularly fast product cycles, such as in the lighting sector, 00:30:47.840 --> 00:30:51.600 where we can then just say ad hoc, today 00:30:51.760 --> 00:30:54.560 or the requirement of the customer exists or the requirements 00:30:54.560 --> 00:30:57.880 of the target group exists: We now need a lighting catalog. 00:30:58.320 --> 00:31:03.400 Then we make it relatively quickly, give it a cover 00:31:04.320 --> 00:31:05.200 and then we're done. 00:31:05.200 --> 00:31:06.840 And then do you still print a lot 00:31:06.840 --> 00:31:08.800 or do you also do it as a PDF and send that out? 00:31:08.960 --> 00:31:11.880 Of course, we also work digitally, but 00:31:12.640 --> 00:31:18.240 we have noticed that our target group responds to print and requests it.