WEBVTT 00:00:00.000 --> 00:00:03.960 I have to say it was a successful PIM implementation 00:00:04.480 --> 00:00:09.280 and now our data maintenance is very efficient 00:00:09.880 --> 00:00:13.640 thanks to the good features in ANTEROS and 00:00:14.080 --> 00:00:17.240 the new object type systems with the two sided 00:00:17.240 --> 00:00:21.280 relationship is perfect for our complex fire protection system. 00:00:22.520 --> 00:00:26.200 Furthermore, the grouping of our many parameters 00:00:26.200 --> 00:00:29.720 helps us to determine who can see and change which data. 00:00:30.720 --> 00:00:35.080 Last but not least, we use the dashboard and the quality reports 00:00:35.080 --> 00:00:39.880 for targeted data and quality improvements. 00:00:40.360 --> 00:00:43.560 And yes, thanks to ANTEROS 00:00:43.560 --> 00:00:48.720 we are now able to offer improved service with our new download portal, 00:00:48.920 --> 00:00:53.600 where images, documents and videos are easily accessible. 00:00:54.000 --> 00:01:00.240 In the portal, the user can quickly search across product categories without further 00:01:00.920 --> 00:01:02.800 association necessary. 00:01:03.160 --> 00:01:06.560 The last point I'd like to mention 00:01:06.760 --> 00:01:11.400 here is the automated generation of our complex data sheets. 00:01:11.640 --> 00:01:15.240 We offer our data sheets in a lot of different languages. 00:01:15.240 --> 00:01:18.760 And, in the past, we created each of them by hand. 00:01:19.360 --> 00:01:23.960 Now it's just a touch of a button which ensures up to date data 00:01:23.960 --> 00:01:28.840 and a standardization layout, which saves us a lot of time. 00:01:29.800 --> 00:01:31.000 So yes. 00:01:31.720 --> 00:01:35.440 I like our PIM and I think all my colleagues do also. 00:01:40.120 --> 00:01:43.680 I'm Tobias Bächle, head of IT application management 00:01:43.880 --> 00:01:48.360 at svt since three years and I was 00:01:48.600 --> 00:01:53.600 in charge of the project for the PIM implementation. 00:01:54.080 --> 00:01:59.160 svt is a all-round carefree provider of services and products 00:01:59.480 --> 00:02:03.960 for passive fire protection, damage restoration 00:02:04.000 --> 00:02:08.200 and planning and organization fire protection. 00:02:08.680 --> 00:02:12.560 svt was founded in 1969. 00:02:13.640 --> 00:02:18.560 We have above 1800 employees 00:02:18.840 --> 00:02:22.920 and we are settled in about over 60 locations. 00:02:23.800 --> 00:02:30.160 Yes, we have foreign subsidiaries, about 15. 00:02:30.600 --> 00:02:34.760 We have many fields of activities, so we have passive fire protection 00:02:34.760 --> 00:02:42.600 products and systems, fire protection services, we have industrial applications, 00:02:44.200 --> 00:02:50.120 damage restoration and we have organizational and planning fire protection. 00:02:50.440 --> 00:02:55.120 Our applications and products have - 00:02:55.240 --> 00:02:58.440 are registered in many trademarks. 00:02:58.720 --> 00:03:02.480 We have FLAMMADUR, FLAMRO, 00:03:03.240 --> 00:03:06.280 PYROGUARD and many more. 00:03:06.280 --> 00:03:08.960 But we want to merge them 00:03:08.960 --> 00:03:12.520 in the next time for better market standing. 00:03:12.760 --> 00:03:15.240 Let us come to the PIM project. 00:03:15.520 --> 00:03:19.040 Our project goals and requirements for the PIM system. 00:03:20.080 --> 00:03:26.040 We want a central hub for our data in the company. 00:03:26.280 --> 00:03:34.120 So we want storage input and import and modification of data in one system 00:03:34.840 --> 00:03:39.600 and making product data available for various purposes. 00:03:40.480 --> 00:03:45.120 We don't want data islands anymore, 00:03:45.120 --> 00:03:48.200 so we want to integrate the PIM system 00:03:48.560 --> 00:03:51.040 with existing systems. 00:03:51.400 --> 00:03:54.520 We have a clear storage of product data. 00:03:54.760 --> 00:03:58.960 So simple cross distribution and access to the data 00:03:59.800 --> 00:04:04.680 by using the PIM and standardization of data and increase 00:04:04.680 --> 00:04:08.680 in data quality to ensure consistent 00:04:08.880 --> 00:04:12.120 quality of data and texts. 00:04:12.760 --> 00:04:14.960 The quality assurance via 00:04:14.960 --> 00:04:20.400 dashboard was one of our goals and we want to define 00:04:20.400 --> 00:04:24.640 responsibilities and competencies regarding product data. 00:04:25.600 --> 00:04:28.600 Automation and simplification of processes 00:04:28.600 --> 00:04:32.240 saves considerable time and data maintenance. 00:04:32.680 --> 00:04:36.360 And at least we want to provide customers with faster 00:04:36.360 --> 00:04:39.120 and more targeted product information. 00:04:40.400 --> 00:04:43.720 So we need a fast and automatic generation 00:04:43.920 --> 00:04:47.240 of standardized print documents. 00:04:47.440 --> 00:04:50.320 The process of selecting a PIM system, 00:04:50.320 --> 00:04:54.240 or how we found to INCONY and ANTEROS: 00:04:55.840 --> 00:04:58.560 On March 21, 00:04:58.560 --> 00:05:01.840 we invited to tender to INCONY 00:05:01.840 --> 00:05:04.560 and other PIM providers with 00:05:05.160 --> 00:05:10.400 the requirements for PIM in a Excel file. 00:05:10.520 --> 00:05:14.760 So we had a catalog of wishes that 00:05:15.480 --> 00:05:19.360 we wrote down and sent to the vendors. 00:05:19.720 --> 00:05:22.280 On summer 21 00:05:22.280 --> 00:05:27.480 we had chosen a new CRM software, 00:05:27.760 --> 00:05:30.880 so we had not enough 00:05:32.160 --> 00:05:37.240 resources for the implementation of the PIM. 00:05:37.240 --> 00:05:39.240 So we postponed it. 00:05:39.560 --> 00:05:42.280 But finally, in June 22, 00:05:43.840 --> 00:05:47.440 we had the time in my team and we 00:05:48.520 --> 00:05:52.960 did a shortlist of presentations and yes. 00:05:52.960 --> 00:05:57.040 Finally INCONY made it and was the favorite. 00:05:57.920 --> 00:06:02.400 August 22, we finally signed it, and we signed it 00:06:02.400 --> 00:06:06.640 because INCONY was leading 00:06:06.640 --> 00:06:10.120 in the data maintenance and technical data 00:06:10.520 --> 00:06:13.880 in our evaluation and INCONY 00:06:15.000 --> 00:06:18.000 is experienced in industry. 00:06:19.000 --> 00:06:20.440 That was a good fit. 00:06:21.080 --> 00:06:25.560 INCONY had also flexible interfaces, 00:06:26.040 --> 00:06:29.040 imports and exports. 00:06:29.040 --> 00:06:33.760 And you can easily integrate it with other systems. 00:06:34.480 --> 00:06:42.360 We found 100% automatic print generation of data sheets and catalogs, 00:06:42.360 --> 00:06:45.560 that was a really big benefit for us 00:06:45.960 --> 00:06:50.200 and at least the product data maintenance, media management, 00:06:50.200 --> 00:06:56.000 media portal and print documents, it was all in one system. 00:06:56.480 --> 00:07:00.520 So the acceptance in our user 00:07:00.520 --> 00:07:04.800 rounds was very big for INCONY and ANTEROS. 00:07:05.320 --> 00:07:10.640 Integrating ANTEROS into the system architecture at svt 00:07:10.840 --> 00:07:16.280 we have a few ERP systems in our environment, 00:07:16.720 --> 00:07:20.880 but one of our biggest ERPs is proAlpha 00:07:21.640 --> 00:07:24.960 in the construction department. 00:07:25.800 --> 00:07:30.120 We connected proAlpha to ANTEROS 00:07:30.440 --> 00:07:34.600 by using a simple CSV file 00:07:34.600 --> 00:07:37.520 for the first data transfer. 00:07:37.920 --> 00:07:40.840 So the products 00:07:41.800 --> 00:07:43.800 were created in proAlpha 00:07:43.800 --> 00:07:47.720 and then transfered to the PIM system. 00:07:47.720 --> 00:07:51.840 And in the PIM system they were enriched 00:07:51.840 --> 00:07:57.880 with all necessary further data and media assets and 00:07:58.640 --> 00:08:03.440 so the PIM is in the center of the architecture. 00:08:03.880 --> 00:08:08.600 Next around the PIM there are websites, 00:08:08.920 --> 00:08:15.280 for example where the data is from the market department also 00:08:15.280 --> 00:08:18.760 and goes live and then to the website 00:08:19.240 --> 00:08:22.160 and so the products are online. 00:08:22.640 --> 00:08:26.720 We as svt had some special 00:08:27.640 --> 00:08:30.760 features and needs for ANTEROS. 00:08:31.200 --> 00:08:37.320 So we need a new object type 00:08:38.480 --> 00:08:43.080 in addition to the categories and product families and products. 00:08:43.400 --> 00:08:49.840 We need systems in the PIM system because we - 00:08:50.680 --> 00:08:55.840 our systems are created by multiple articles. 00:08:56.200 --> 00:08:59.440 So you have to connect them in the system 00:08:59.440 --> 00:09:04.200 and we need responsibilities between the systems. 00:09:05.000 --> 00:09:07.600 So the next point. 00:09:07.600 --> 00:09:11.520 Yes, I said responsibilities. I mean a relationship. 00:09:12.280 --> 00:09:14.480 The systems and the products 00:09:15.400 --> 00:09:18.600 have relationships between them. 00:09:18.840 --> 00:09:25.400 So now you can view it in the PIM from two sides, 00:09:25.400 --> 00:09:28.960 you can look at the system or you can look at the product 00:09:29.400 --> 00:09:33.080 and the other way around, you can see 00:09:33.080 --> 00:09:36.880 then the product or the system that belongs to it. 00:09:37.600 --> 00:09:42.880 And finally we need another feature that is - 00:09:43.760 --> 00:09:45.800 that are parameter groups. 00:09:46.960 --> 00:09:51.320 We had a bunch of parameters 00:09:51.320 --> 00:09:54.360 to all different articles. 00:09:54.720 --> 00:10:00.240 So we have to group it for the different departments. 00:10:00.760 --> 00:10:08.120 And so INCONY created an extra group 00:10:08.120 --> 00:10:11.760 for our parameters where we can categorize 00:10:11.800 --> 00:10:18.640 it and make restrictions on these categories. 00:10:18.920 --> 00:10:21.920 Let us take a look in the system. 00:10:22.920 --> 00:10:28.200 So here is our ANTEROS PIM system configured. 00:10:28.600 --> 00:10:31.800 You can see here there's a 00:10:32.160 --> 00:10:35.640 system point in the menu. 00:10:36.080 --> 00:10:38.760 To the left you can see the 00:10:38.760 --> 00:10:41.160 single application products. 00:10:41.160 --> 00:10:45.480 And to the right you can see relationships 00:10:46.480 --> 00:10:50.040 for the complete systems in 00:10:50.960 --> 00:10:53.360 in the PIM with their relation. 00:10:53.720 --> 00:10:59.400 So every product, complex product, 00:11:00.040 --> 00:11:03.400 we say application to it or system, 00:11:05.680 --> 00:11:11.280 is build from single products. 00:11:11.960 --> 00:11:15.600 I said we have of few of over 00:11:16.000 --> 00:11:18.160 nearly a thousand parameters. 00:11:18.320 --> 00:11:21.680 So and not every user needs to see 00:11:22.080 --> 00:11:25.200 or is able to edit all of them. 00:11:25.440 --> 00:11:30.000 So we decided to group the parameter 00:11:30.600 --> 00:11:37.400 in product system ERP and marketing parameter. 00:11:37.720 --> 00:11:40.600 If you step into it, 00:11:40.600 --> 00:11:44.520 you can see there's another category 00:11:44.520 --> 00:11:49.720 or we call it group where it's also 00:11:50.760 --> 00:11:52.880 categorized. 00:11:53.320 --> 00:11:55.400 And you have here 00:11:55.800 --> 00:11:59.040 special subtabs in the editor. 00:11:59.320 --> 00:12:03.920 So in this case marketing can find 00:12:04.320 --> 00:12:07.800 their parameters in the marketing tab. 00:12:07.800 --> 00:12:08.440 And 00:12:10.240 --> 00:12:15.680 we can also restrict the access for the different user types. 00:12:16.360 --> 00:12:19.120 About the user groups 00:12:19.120 --> 00:12:22.480 here are different user groups 00:12:22.480 --> 00:12:27.080 we created for our users. 00:12:27.080 --> 00:12:32.800 So you can see marketing has its own group with restrictions 00:12:33.120 --> 00:12:36.120 for delete, change, access, 00:12:36.440 --> 00:12:40.920 only maintain certain parameters as the assets. 00:12:41.080 --> 00:12:44.520 So you can restrict 00:12:44.920 --> 00:12:47.800 every user group for your needs. 00:12:48.200 --> 00:12:56.200 This example shows how a marketing employee would see the editor. 00:12:56.480 --> 00:13:00.760 So the marketing member 00:13:00.760 --> 00:13:04.480 can't change the brand name or language 00:13:04.960 --> 00:13:07.600 or validate the article, 00:13:07.600 --> 00:13:10.600 they can only access the fields 00:13:11.360 --> 00:13:13.480 that they are allowed to. 00:13:14.880 --> 00:13:18.680 Here it is the SEO text for example. 00:13:19.520 --> 00:13:21.440 So marketing could only 00:13:22.400 --> 00:13:25.200 fill in their necessary 00:13:26.200 --> 00:13:31.400 fields for placing the products for the website. 00:13:31.760 --> 00:13:35.000 You don't have to send 00:13:35.200 --> 00:13:39.680 Excel files from one department to another department. 00:13:39.680 --> 00:13:43.560 And we can build up here a workflow 00:13:44.080 --> 00:13:47.280 to collaborate through the departments. 00:13:47.280 --> 00:13:48.680 And that was really a 00:13:50.080 --> 00:13:52.840 big advantage in the system. 00:13:53.040 --> 00:13:56.840 We have the media asset maintenance 00:13:57.800 --> 00:14:00.280 portal where we can 00:14:02.520 --> 00:14:06.680 upload files and we can 00:14:08.080 --> 00:14:12.680 make rules for the quality of the uploads. 00:14:13.000 --> 00:14:14.360 So it's 00:14:15.280 --> 00:14:23.720 it’s a really good feature to keep the PIM data in high quality. 00:14:24.040 --> 00:14:31.360 You can specify a solution for the upload of media assets and - 00:14:31.720 --> 00:14:35.440 so it's a really convenient file upload. 00:14:35.680 --> 00:14:40.280 If you use it there are many 00:14:41.680 --> 00:14:46.440 sub pics generated automatically by upload. 00:14:47.440 --> 00:14:50.320 That saves us a lot of time too. 00:14:50.440 --> 00:14:56.960 Where you can upload meta data and you can assign the - 00:14:58.240 --> 00:15:02.640 end date for validity for example. 00:15:03.080 --> 00:15:08.200 On the other side from the media portal, you have the download portal. 00:15:08.520 --> 00:15:15.040 That's a really great benefit for our company because 00:15:15.800 --> 00:15:24.280 internal colleagues can easily search for images or documents, videos 00:15:25.320 --> 00:15:26.760 within the portal. 00:15:27.120 --> 00:15:31.840 You have a easy download button. 00:15:31.840 --> 00:15:35.640 You can easily access to all the assets 00:15:36.040 --> 00:15:38.920 and you have a right 00:15:38.920 --> 00:15:41.920 restriction for external colleagues. 00:15:41.920 --> 00:15:48.120 So external colleagues can't see all of your assets. 00:15:48.120 --> 00:15:51.960 You can restrict it by rights. 00:15:52.240 --> 00:15:57.440 So here you can see the maintenance of media assets. 00:15:57.560 --> 00:16:01.400 If you want to create a new asset, you can - 00:16:01.640 --> 00:16:05.960 you have to fill in for example the brand names, the language 00:16:06.440 --> 00:16:10.920 and the valid from and until date. 00:16:11.280 --> 00:16:15.080 Or you can automatically fill in the until date. 00:16:15.280 --> 00:16:17.520 You can fill in the approval, 00:16:19.040 --> 00:16:24.120 so you can maintain them for each media object 00:16:24.960 --> 00:16:26.120 or parameters. 00:16:26.440 --> 00:16:28.640 The download portal is 00:16:32.080 --> 00:16:39.240 good, searchable because you don't have to add manually 00:16:39.600 --> 00:16:42.600 all texts for the images. 00:16:43.000 --> 00:16:49.680 They're added automatically by the category. So 00:16:50.840 --> 00:16:55.960 you can easily search for product name, 00:16:55.960 --> 00:17:00.880 or you can search also by tag through the full range, 00:17:00.880 --> 00:17:03.640 they are generated from the PIM. 00:17:03.880 --> 00:17:07.280 Here you can see the difference between the internal 00:17:07.280 --> 00:17:11.080 and external download portal. 00:17:11.400 --> 00:17:16.160 So internal users have much more rights 00:17:16.840 --> 00:17:22.320 to access PDF files and declarations to download. 00:17:22.600 --> 00:17:27.280 And if you are logged in as an external user, 00:17:27.320 --> 00:17:30.320 you can for example only the access 00:17:31.000 --> 00:17:32.240 some pics and 00:17:33.440 --> 00:17:39.480 download promotion videos or declarations 00:17:40.200 --> 00:17:43.240 that are not for internal use. 00:17:43.880 --> 00:17:48.160 This is one of our DOP data sheets. 00:17:48.160 --> 00:17:50.760 DOP is declaration of performance. 00:17:50.760 --> 00:17:57.200 We have to create it for all of our articles. 00:17:57.560 --> 00:18:00.360 So it's a layout 00:18:00.760 --> 00:18:06.760 that is used very often and a big benefit of 00:18:07.600 --> 00:18:10.960 ANTEROS is we print that 00:18:11.320 --> 00:18:14.800 or we generate it first in the workshop 00:18:15.280 --> 00:18:18.720 with the colleagues from INCONY. 00:18:18.720 --> 00:18:22.280 And so if they - 00:18:22.280 --> 00:18:28.920 if we want to print it we just have to do one click and it's complete, 00:18:28.920 --> 00:18:34.400 generated through the data from our PIM automatically. 00:18:34.400 --> 00:18:39.040 So there’s a print rule and 00:18:39.840 --> 00:18:45.200 so we have a clear layout through all our data sheets. 00:18:45.360 --> 00:18:47.520 That's really a great benefit. 00:18:47.720 --> 00:18:52.920 In the past we created that by Photoshop 00:18:52.920 --> 00:18:58.720 and paint it one by one and we have really - 00:18:58.720 --> 00:19:03.640 or we are in over 20 countries worldwide, 00:19:03.960 --> 00:19:07.520 so we have to do it in many languages and 00:19:08.040 --> 00:19:12.920 we have now the single point of truth in our PIM 00:19:13.120 --> 00:19:19.560 and we can generate that in different languages just by one click 00:19:19.680 --> 00:19:21.360 with actual data. 00:19:21.640 --> 00:19:26.160 Here you can also see the data sheet 00:19:26.800 --> 00:19:34.040 on the left side, where you can find the data within the PIM system 00:19:34.040 --> 00:19:37.040 and on the right side you can see it 00:19:37.240 --> 00:19:42.680 how it's in the print layout, converted. So 00:19:43.640 --> 00:19:49.560 ANTEROS can create complicated or complex 00:19:50.800 --> 00:19:53.400 data models too. 00:19:54.240 --> 00:20:03.040 Yes, it can bring it to a standard layout where you can connect the fields to the layout 00:20:03.040 --> 00:20:06.320 and that's also really - 00:20:07.160 --> 00:20:09.680 you have to do it only one time 00:20:10.080 --> 00:20:14.040 to create this layout, and then it's finished. 00:20:14.440 --> 00:20:18.240 I wasn't able to think that that's possible 00:20:18.240 --> 00:20:23.600 but we did it and that's really a big benefit for our company. 00:20:23.600 --> 00:20:25.400 So we save a lot of time. 00:20:25.680 --> 00:20:30.160 In the next data sheet you can see we have our corporate design 00:20:30.160 --> 00:20:33.920 also implemented in the layout. 00:20:34.040 --> 00:20:40.200 So the customer journey is also better now. 00:20:40.400 --> 00:20:43.480 And we have a layout 00:20:44.240 --> 00:20:47.480 that fits with all our data sheets. 00:20:47.760 --> 00:20:53.080 Yes. We also have here the reference to the PIM fields 00:20:53.080 --> 00:20:57.280 and we have the latest data. 00:20:57.280 --> 00:21:01.600 So they are always actual. 00:21:01.600 --> 00:21:04.320 And you don't have to worry that 00:21:04.840 --> 00:21:08.200 you have old product data sheets. 00:21:08.440 --> 00:21:13.200 In conclusion, I have to say it was a successful PIM implementation 00:21:13.720 --> 00:21:18.520 and now our data maintenance is very efficient 00:21:19.120 --> 00:21:22.880 thanks to the good features in ANTEROS and 00:21:23.320 --> 00:21:26.480 the new object type systems with the two sided 00:21:26.480 --> 00:21:30.520 relationship is perfect for our complex fire protection system. 00:21:31.760 --> 00:21:35.440 Furthermore, the grouping of our many parameters 00:21:35.440 --> 00:21:38.960 helps us to determine who can see and change which data. 00:21:39.960 --> 00:21:44.320 Last but not least, we use the dashboard and the quality reports 00:21:44.320 --> 00:21:49.120 for targeted data and quality improvements. 00:21:49.600 --> 00:21:52.800 And yes, thanks to ANTEROS 00:21:52.800 --> 00:21:57.960 we are now able to offer improved service with our new download portal, 00:21:58.160 --> 00:22:02.840 where images, documents and videos are easily accessible. 00:22:03.240 --> 00:22:09.480 In the portal, the user can quickly search across product categories without further 00:22:10.160 --> 00:22:12.040 association necessary. 00:22:12.400 --> 00:22:15.800 The last point I like to mention 00:22:16.000 --> 00:22:20.640 here is the automated generation of our complex data sheets. 00:22:20.880 --> 00:22:24.480 We offer our data sheets in a lot of different languages. 00:22:24.480 --> 00:22:28.000 And, in the past, we created each of them by hand. 00:22:28.600 --> 00:22:33.200 Now it's just a touch of a button which ensures up to date data 00:22:33.200 --> 00:22:38.080 and a standardization layout, which saves us a lot of time. 00:22:39.040 --> 00:22:40.240 So yes. 00:22:40.960 --> 00:22:44.680 I like our PIM and I think all my colleagues do also. 00:22:46.120 --> 00:22:47.960 Okay, thank you very much Tobias. 00:22:47.960 --> 00:22:49.520 So for the speech. 00:22:50.080 --> 00:22:52.760 I'd like to start with first questions. 00:22:52.960 --> 00:22:55.680 The first one is: in your opinion, 00:22:55.680 --> 00:22:59.080 what was the biggest technical challenge in the project? 00:22:59.080 --> 00:23:02.480 I think one of our biggest challenges 00:23:02.480 --> 00:23:07.720 was to define the data model because in the past 00:23:07.720 --> 00:23:13.160 we did all our product management by Excel sheets. 00:23:13.600 --> 00:23:17.240 And we have very big and long Excel sheets 00:23:17.240 --> 00:23:22.640 in all different colors and variations. 00:23:23.040 --> 00:23:27.400 And now we had to define 00:23:27.400 --> 00:23:32.560 one data model for products and systems and 00:23:34.840 --> 00:23:37.800 we couldn't imagine how it 00:23:37.800 --> 00:23:42.600 can fit together because they are completely different. 00:23:42.600 --> 00:23:47.080 One is a application or a system and one is a product. 00:23:47.440 --> 00:23:50.440 But your software 00:23:51.840 --> 00:23:53.560 can solve that. 00:23:53.560 --> 00:23:55.840 So we are - 00:23:55.840 --> 00:23:57.400 That was a 00:23:58.520 --> 00:24:01.000 big way to find that out. 00:24:01.000 --> 00:24:05.320 We can make that this way but yes, we did. 00:24:05.600 --> 00:24:06.640 Okay. 00:24:06.640 --> 00:24:10.760 And my second question is: what were the biggest organizational 00:24:10.760 --> 00:24:14.560 challenges of the PIM project in your organization? 00:24:15.120 --> 00:24:21.600 We had to make a big part in change management 00:24:21.640 --> 00:24:24.280 because with PIM, 00:24:25.480 --> 00:24:29.320 we had a new kind of work together 00:24:29.320 --> 00:24:33.680 because we have different responsibilities. 00:24:33.880 --> 00:24:39.360 In the past we send Excel sheets from one station to another station 00:24:39.360 --> 00:24:42.680 to enrich the Excel files. 00:24:42.880 --> 00:24:45.600 And now we have 00:24:47.080 --> 00:24:53.480 straight ways through the PIM system with workflows and - 00:24:54.280 --> 00:24:57.520 So every department has 00:24:57.520 --> 00:25:00.720 their own tab with fields and 00:25:01.720 --> 00:25:05.120 responsibilities and restrictions. 00:25:05.240 --> 00:25:08.760 So if they - 00:25:09.080 --> 00:25:10.400 If the marketing 00:25:11.480 --> 00:25:14.880 doesn't fill in their SEO fields, 00:25:16.120 --> 00:25:20.520 the website would never or would not get the data 00:25:21.160 --> 00:25:25.760 because the workflow would stop at the marketing department. 00:25:27.120 --> 00:25:30.120 Yes, that was really a new 00:25:31.320 --> 00:25:33.080 kind of working together 00:25:33.080 --> 00:25:36.360 because they have their own 00:25:38.920 --> 00:25:41.720 responsibility for their processes. 00:25:41.880 --> 00:25:42.360 Okay. 00:25:42.360 --> 00:25:46.000 So a clear process for all different persons 00:25:46.000 --> 00:25:49.640 working with the system and all data in one system together. 00:25:49.800 --> 00:25:53.520 Yes. We always have the single point of truth in the system 00:25:53.520 --> 00:25:56.600 and that is really a big benefit for all of us.