WEBVTT

00:00:00.160 --> 00:00:03.240
Why did we choose INCONY or

00:00:03.240 --> 00:00:07.280
what is our summary of the implementation
of the PIM system in our company?

00:00:07.480 --> 00:00:12.480
Data maintenance has become much more efficient;
we have significant time savings.

00:00:12.800 --> 00:00:16.280
We can find all the information in one place,

00:00:16.680 --> 00:00:20.360
which was not possible before;
many had their own filing system,

00:00:20.360 --> 00:00:21.800
thanks to PIM we have simply

00:00:21.800 --> 00:00:25.760
made it possible to have all the information
about the product in one system.

00:00:25.760 --> 00:00:28.480
ANTEROS convinced us because

00:00:28.480 --> 00:00:32.680
it specializes in complex data and
also covered most of the points

00:00:32.680 --> 00:00:36.520
in our requirements catalog
in its standard version.

00:00:36.920 --> 00:00:41.080
We have managed to automate things
that were previously manual

00:00:41.560 --> 00:00:46.360
and the service and consultation
and project management

00:00:46.360 --> 00:00:54.000
have enabled us to have a truly excellent
implementation of our PIM system in our company.

00:00:54.440 --> 00:00:57.560
The experience with complex data
and technical industries

00:00:57.560 --> 00:01:00.080
provided by the INCONY consultants
was very valuable for us,

00:01:00.800 --> 00:01:04.320
and the reliable support and
short response times were not only applicable

00:01:04.320 --> 00:01:08.160
to the proof-of-concept,
but also continue to apply to the project.

00:01:13.320 --> 00:01:16.560
Allow me to say a few words
about us, MC-Bauchemie.

00:01:16.560 --> 00:01:20.680
We are a family-owned company
with over 60 years of experience

00:01:20.680 --> 00:01:24.720
in the field of construction chemicals,
and we have two main areas of focus.

00:01:24.720 --> 00:01:26.800
One is in the area of new construction

00:01:27.160 --> 00:01:30.200
and there we are active in the
field of concrete admixtures,

00:01:30.280 --> 00:01:34.240
i.e. accelerators, retarders, such topics,

00:01:34.240 --> 00:01:37.480
and also in the field of injection
within new construction.

00:01:37.840 --> 00:01:42.040
Our second main pillar is in the field of repair.

00:01:42.400 --> 00:01:45.080
Of course, the focus is clearly on the topic

00:01:45.080 --> 00:01:50.600
of concrete repair, i.e. concrete replacement
systems, coating systems

00:01:50.600 --> 00:01:54.000
within repair and also the

00:01:54.000 --> 00:01:56.440
topic of injection of cracked concrete.

00:01:56.640 --> 00:01:59.160
We have around 3,000 employees

00:01:59.160 --> 00:02:02.560
working for us and are active in over 40 countries

00:02:03.000 --> 00:02:06.640
and have 20 production sites worldwide.

00:02:06.920 --> 00:02:09.400
That is, of course, also one of the reasons

00:02:09.400 --> 00:02:13.960
why we have said that we must,
obviously, do a better job of

00:02:14.440 --> 00:02:18.280
updating our product data
and keeping it up to date.

00:02:19.000 --> 00:02:23.120
The challenge is maintaining two
and a half thousand products

00:02:23.120 --> 00:02:27.760
with more than 25,000 articles
and keeping them up to date.

00:02:28.120 --> 00:02:32.520
Of course, we also have to translate content
into other languages,

00:02:32.800 --> 00:02:37.880
taking into account requirements and
legislation in the individual countries.

00:02:38.840 --> 00:02:40.920
The individual stand-alone solutions

00:02:41.320 --> 00:02:43.760
implemented in the different
countries, which is of course

00:02:44.520 --> 00:02:48.040
due to the fact that we are
still working with other systems

00:02:48.040 --> 00:02:52.360
abroad, make it even more difficult

00:02:52.360 --> 00:02:55.080
to keep our documents up to date.

00:02:56.280 --> 00:03:00.480
And to communicate them
internally to our colleagues,

00:03:00.800 --> 00:03:02.920
but also externally to our customers.

00:03:03.040 --> 00:03:06.880
Until now, we had always created
our data sheets manually,

00:03:06.880 --> 00:03:10.440
which took an enormous amount of time,

00:03:10.920 --> 00:03:14.080
and we had also always manually

00:03:14.080 --> 00:03:19.680
uploaded them to our websites,
as well as to our CRM system.

00:03:20.280 --> 00:03:25.480
Of course, I would like to explain the reasons
why we decided to use

00:03:25.480 --> 00:03:28.280
the ANTEROS system from INCONY.

00:03:28.960 --> 00:03:31.640
We have created a requirements catalog

00:03:31.640 --> 00:03:34.120
and conducted initial market research.

00:03:34.120 --> 00:03:37.320
For this purpose, we also held
talks with various companies.

00:03:37.920 --> 00:03:40.640
ANTEROS convinced us because

00:03:40.640 --> 00:03:44.840
it specializes in complex data and
also covered most of the points

00:03:44.840 --> 00:03:48.680
in our requirements catalog
in its standard version.

00:03:49.240 --> 00:03:53.520
We then carried out a
three-month proof-of-concept

00:03:53.600 --> 00:03:57.320
with INCONY and 15 employees
from various departments

00:03:57.520 --> 00:04:02.560
in our company and tested the system

00:04:02.840 --> 00:04:06.080
and revised it again to suit our concept.

00:04:06.760 --> 00:04:09.880
The experience with complex data
and technical industries

00:04:09.880 --> 00:04:12.400
provided by the INCONY consultants
was very valuable for us,

00:04:13.120 --> 00:04:16.640
and the reliable support and
short response times were not only applicable

00:04:16.640 --> 00:04:20.480
to the proof-of-concept,
but also continue to apply to the project.

00:04:20.960 --> 00:04:23.520
Now to the topic of how is the ANTEROS system

00:04:23.520 --> 00:04:26.040
integrated in our company MC-Bauchemie?

00:04:27.320 --> 00:04:31.000
Currently, we are still using
various ERP systems,

00:04:31.000 --> 00:04:33.360
which is the result of our global activities.

00:04:33.800 --> 00:04:38.600
But our main system is called Oxaion,
which covers a good 15 countries worldwide.

00:04:39.520 --> 00:04:42.120
The master data is updated once a night

00:04:42.840 --> 00:04:47.160
and the data is then transferred
to the PIM system.

00:04:47.720 --> 00:04:49.480
Here it is then refined

00:04:49.480 --> 00:04:52.080
or supplemented with further information

00:04:52.080 --> 00:04:54.960
that is not contained in our ERP system.

00:04:55.320 --> 00:04:59.840
Currently, we have five different types of
data sheets that we use.

00:05:00.080 --> 00:05:04.240
One of them is our technical data sheet
with all the technical information.

00:05:04.960 --> 00:05:07.480
We have a declaration of performance

00:05:07.560 --> 00:05:11.600
for our products;
we have a sustainability data sheet,

00:05:11.880 --> 00:05:16.160
a processing note for
our commercial customers

00:05:16.720 --> 00:05:20.280
and an environmental product declaration.

00:05:21.120 --> 00:05:28.440
These are created using fully automated print generation
and uploaded to our websites nightly.

00:05:28.600 --> 00:05:32.880
Further product information is also uploaded
to the product subpages

00:05:32.880 --> 00:05:38.920
on the websites from the ANTEROS
system fully automatically.

00:05:39.680 --> 00:05:42.000
For example areas of application,

00:05:42.000 --> 00:05:45.440
short descriptions of our
product items, etc.

00:05:45.640 --> 00:05:48.680
In addition, certain product contents
are transferred to our in-house

00:05:48.800 --> 00:05:51.080
workflow system Phoenix,

00:05:51.760 --> 00:05:55.160
which includes, for example,
label contents that

00:05:55.160 --> 00:05:59.760
pass through the Phoenix
system in a control run.

00:06:00.200 --> 00:06:03.680
Let's continue with efficient structured
data maintenance with ANTEROS.

00:06:04.360 --> 00:06:07.480
For this, we have brought you a
screenshot from our PIM system.

00:06:07.800 --> 00:06:10.360
On the left side, you can
select the product family.

00:06:10.600 --> 00:06:13.400
Here you can also perform a
search function and filtering.

00:06:13.560 --> 00:06:15.600
On the right you can see
the product information.

00:06:15.840 --> 00:06:19.040
For the sake of overview,
we have created a separate tab for each area.

00:06:19.400 --> 00:06:23.720
So in one tab we have our
imported ERP data listed.

00:06:23.760 --> 00:06:24.960
But we also have general

00:06:24.960 --> 00:06:29.400
information, product names, subtitles etc.,
but also each document,

00:06:29.400 --> 00:06:32.480
data sheet, declaration of
performance have their own tab.

00:06:32.880 --> 00:06:35.640
Our principle is not to maintain
any information twice.

00:06:35.920 --> 00:06:40.200
The required information
is therefore imported

00:06:40.680 --> 00:06:44.240
from the existing tabs into the
required fields or documents,

00:06:45.120 --> 00:06:48.040
for example the product name
or the subtitle of the product.

00:06:48.200 --> 00:06:51.200
But we can also extract
individual characteristic values

00:06:51.520 --> 00:06:54.360
and transfer them to our
website, for example.

00:06:54.480 --> 00:06:58.200
With structured data maintenance,
the focus is on set default values.

00:06:58.360 --> 00:07:01.000
This improves the CI-compliant notation,

00:07:01.200 --> 00:07:03.520
as can be seen here in the example
"Standard Climate" (Normklima).

00:07:04.000 --> 00:07:07.000
The spacing between the
degrees, the plus-minus sign,

00:07:07.000 --> 00:07:10.160
and also the abbreviation
of the relative humidity

00:07:10.760 --> 00:07:13.480
are thus always identical
across all documents.

00:07:14.000 --> 00:07:17.760
This minimizes the errors and makes
the translation much easier.

00:07:17.960 --> 00:07:21.640
We use different types of parameters
according to requirements and trading.

00:07:21.640 --> 00:07:26.680
On the one hand, we have the preset values,
as shown in the example of the "Standard Climate".

00:07:26.920 --> 00:07:30.040
Here you can use the radio button,

00:07:30.040 --> 00:07:33.600
the small button in front, to choose which information
you want to have displayed in the document.

00:07:33.960 --> 00:07:37.240
There is also a single selection
via a drop-down menu,

00:07:37.240 --> 00:07:40.560
where the default values can
be selected by colleagues.

00:07:41.080 --> 00:07:45.000
Multiple selection is identical
to single selection.

00:07:45.240 --> 00:07:49.360
It only differs by the small plus sign
at the front of the parameter,

00:07:49.920 --> 00:07:54.120
which allows you to duplicate the parameter
and make another selection.

00:07:54.560 --> 00:07:57.960
The majority of our parameters, however,
are multi-structured types,

00:07:57.960 --> 00:08:00.240
i.e. nested parameters.

00:08:00.440 --> 00:08:04.400
The rationale behind this is on the
one hand the minimized database,

00:08:04.960 --> 00:08:08.680
because all our divisions
and also subsidiaries

00:08:09.080 --> 00:08:13.840
access one parameter pool despite
having different requirements,

00:08:13.840 --> 00:08:17.160
i.e. in the B2B sector
or direct approach

00:08:17.160 --> 00:08:18.960
to consumers in the B2C sector.

00:08:19.080 --> 00:08:21.080
We want to minimize data maintenance.

00:08:21.280 --> 00:08:24.360
This means that the characteristic values
only exist once in the system

00:08:24.960 --> 00:08:27.880
and will be easier to maintain
despite having different specifications,

00:08:28.240 --> 00:08:32.280
such as maximum and
minimum temperatures.

00:08:32.480 --> 00:08:35.320
A quick example: In the past,
we had a parameter

00:08:35.320 --> 00:08:38.600
called "minimum temperature"
and one called "maximum temperature".

00:08:38.720 --> 00:08:43.240
Today this parameter is called "temperature"
with the respective addition of minimum or maximum.

00:08:45.080 --> 00:08:48.040
This has already saved
us another parameter.

00:08:48.240 --> 00:08:50.880
But we also need to
have maximum flexibility

00:08:52.080 --> 00:08:53.960
despite our fixed default values.

00:08:53.960 --> 00:08:58.440
We can achieve this by
working with additions

00:08:58.440 --> 00:09:02.800
like greater than or equal to,
less than or equal to, approximate, etc.

00:09:02.880 --> 00:09:06.800
But we also have the option
to enter range of values.

00:09:07.200 --> 00:09:11.960
Multiple values as just explained,
can be selected and also additions

00:09:12.200 --> 00:09:16.480
per parameter unit can
be chosen exactly.

00:09:16.880 --> 00:09:20.120
On the left you can see the
overview of the data maintainer,

00:09:20.120 --> 00:09:23.440
that is, live, in the PIM system
and on the right

00:09:23.440 --> 00:09:26.480
you can see the corresponding
data sheet as a PDF.

00:09:26.480 --> 00:09:30.760
We need these nested data because we
have to present our information

00:09:30.760 --> 00:09:33.520
in such detail in our documents.

00:09:33.640 --> 00:09:37.800
On the one hand, this is because
we want to make this information

00:09:37.800 --> 00:09:42.280
available to our user,
i.e. customer, as best we can,

00:09:42.720 --> 00:09:45.720
but we also need legal
certainty for the company.

00:09:45.720 --> 00:09:48.080
We therefore need clear,

00:09:48.080 --> 00:09:51.840
unambiguous and comprehensive
information in our data sheets.

00:09:52.120 --> 00:09:55.800
Through clearly defined print rules,
the person maintaining the data

00:09:56.240 --> 00:09:58.480
already knows when inputting

00:09:58.480 --> 00:10:01.720
the information in the PIM system where this information
will later be displayed in the data sheet.

00:10:01.960 --> 00:10:06.440
Only the parameters that are filled are
transferred to our print documents.

00:10:06.440 --> 00:10:11.080
As you can see here on the left,
the parameters that are not filled are

00:10:11.200 --> 00:10:14.480
not displayed at all in
the PDF on the right.

00:10:15.000 --> 00:10:18.160
I would like to highlight the
parameter "Storage" (Lagerung),

00:10:18.160 --> 00:10:21.280
because it works with a
so-called calculation formula.

00:10:22.080 --> 00:10:25.280
We have a variety of products,
so we have liquid products,

00:10:25.280 --> 00:10:28.480
solid products, powdery
and in some cases,

00:10:28.480 --> 00:10:30.760
products that also use
multiple components.

00:10:31.560 --> 00:10:35.960
In addition, there is a wide range of containers
that we use: Bags, buckets, hobbocks,

00:10:35.960 --> 00:10:40.320
tin containers, IBCs,
and these in different sizes.

00:10:41.200 --> 00:10:43.440
Depending on the constellation,

00:10:43.440 --> 00:10:46.160
storage of the products
can therefore also vary.

00:10:47.320 --> 00:10:51.280
For normal powder products,
the storage period is in months.

00:10:51.440 --> 00:10:54.480
How long can the product be stored
in its original packaging?

00:10:55.160 --> 00:10:58.720
Liquid products have the
addition of "frost-free" storage.

00:10:58.960 --> 00:11:03.720
But there are also products that can only be stored
within a certain temperature range,

00:11:03.720 --> 00:11:06.680
that is, from and up to
however many degrees.

00:11:06.840 --> 00:11:10.640
The calculation rule is based
on a formula that assigns a

00:11:10.640 --> 00:11:14.880
default value to each combination of time,
minimum and maximum temperature.

00:11:16.080 --> 00:11:18.680
In other words, it specifies

00:11:19.200 --> 00:11:22.360
how long and where
the material is to be stored.

00:11:22.840 --> 00:11:24.960
The product itself is then calculated

00:11:24.960 --> 00:11:28.280
by filling the corresponding
fields in the rule.

00:11:29.160 --> 00:11:35.040
Directly in the PIM system, you can then
also see the default value in the product

00:11:35.160 --> 00:11:41.280
and that the information required for this
has already been entered in this record.

00:11:41.520 --> 00:11:43.320
So, for example,

00:11:43.320 --> 00:11:50.320
“the product can be stored for twelve months
and must be stored in a range of 5 to 20 degrees”.

00:11:50.640 --> 00:11:53.320
Let's move on to the publication

00:11:53.320 --> 00:11:56.480
We are currently building
country-specific publications

00:11:56.920 --> 00:11:59.480
to only reflect the
local product portfolio.

00:12:00.840 --> 00:12:03.240
This also ensures that the system

00:12:03.600 --> 00:12:07.480
remains clearer for
colleagues, as only

00:12:07.480 --> 00:12:11.640
those products that
are available in the

00:12:11.640 --> 00:12:12.680
respective county are displayed.

00:12:13.200 --> 00:12:15.760
By feeding the data
from the ERP system,

00:12:15.920 --> 00:12:20.720
the products including PIM content are then
mirrored in the country publication.

00:12:21.720 --> 00:12:26.000
Irrelevant categories or products are
blocked in the respective publications,

00:12:26.000 --> 00:12:30.120
as you can see here on the right
marked by the many red x's.

00:12:30.200 --> 00:12:34.240
These products or categories
are not even

00:12:34.240 --> 00:12:35.240
available in the country.

00:12:35.240 --> 00:12:38.880
The master data is always maintained
by the production site.

00:12:38.960 --> 00:12:44.120
The countries therefore only need to
translate the documents into the national language.

00:12:44.360 --> 00:12:47.880
If there are national
production developments

00:12:48.400 --> 00:12:51.920
or product developments,
these must be included separately in the PIM

00:12:52.280 --> 00:12:54.360
and maintained in the
respective language.

00:12:54.400 --> 00:12:57.280
Let's move on to the automatic
maintenance of our data sheets.

00:12:59.160 --> 00:13:01.200
For this purpose, I have
brought you an example

00:13:02.160 --> 00:13:05.800
on the topic of the declaration of performance,
i.e. from the "DOP" tab.

00:13:06.120 --> 00:13:09.240
Most of the data is maintained
here via default values.

00:13:09.240 --> 00:13:13.200
So in the system, the manufacturer is
simply selected via the drop-down,

00:13:13.480 --> 00:13:19.280
which promotes a uniform notation and
also minimizes the error rate.

00:13:20.440 --> 00:13:23.840
The product name is automatically
transferred into the document.

00:13:25.120 --> 00:13:27.920
The only input fields left
are the reference number

00:13:27.920 --> 00:13:29.000
and the reason for use.

00:13:29.000 --> 00:13:32.440
But there will certainly be some need

00:13:32.440 --> 00:13:34.160
for optimization over time.

00:13:35.560 --> 00:13:37.600
The standard in question is

00:13:37.600 --> 00:13:40.280
linked via the
"standard object" relation,

00:13:41.320 --> 00:13:44.320
whereby the corresponding standard,

00:13:44.520 --> 00:13:48.160
is simply selected via the drop-down
menu in the relation below

00:13:48.160 --> 00:13:53.880
and linked to the corresponding product,
in this case 1504-7.

00:13:54.120 --> 00:13:57.200
I would like to explain to you
how such a standard object

00:13:57.200 --> 00:13:58.520
is structured in this slide.

00:13:58.840 --> 00:14:02.440
All required standards within
the "DOP" classification

00:14:02.440 --> 00:14:04.680
are linked with the
corresponding parameters.

00:14:04.720 --> 00:14:07.480
In the Data Maintenance tab,
the standard parameters

00:14:07.480 --> 00:14:10.480
are filled with default values
for the standard object.

00:14:10.600 --> 00:14:13.200
In the product family itself
in the DOP tab,

00:14:13.600 --> 00:14:16.560
the standard object is then linked
to the product as described

00:14:16.760 --> 00:14:19.600
and, if required, the default values
can then also be

00:14:19.800 --> 00:14:23.440
either overwritten or deleted because
they are not always mandatory

00:14:23.440 --> 00:14:25.320
for all products.

00:14:25.320 --> 00:14:28.520
Or are not identical.

00:14:28.680 --> 00:14:29.680
For easy review,

00:14:29.680 --> 00:14:33.640
we can also generate all documents
as PDF in draft preview.

00:14:34.600 --> 00:14:36.560
To do this, all you need to do

00:14:36.560 --> 00:14:39.360
is select the document type

00:14:39.360 --> 00:14:43.600
Data Sheet, Declaration of Performance
or EPD in the Print Rule section

00:14:44.080 --> 00:14:47.680
and choose the associated
language you want to view.

00:14:47.720 --> 00:14:51.080
The draft version as PDF is
intended for internal use only.

00:14:51.320 --> 00:14:54.680
It is used here as a print preview
for the colleague

00:14:54.680 --> 00:14:58.240
who fills the document,
but also for reviewing

00:14:58.240 --> 00:15:01.680
by means of our internal workflow
system, which my colleague

00:15:01.760 --> 00:15:04.760
Mr. Sven Steppa will tell you
about in detail in a moment.

00:15:05.080 --> 00:15:07.840
This draft document is also clearly

00:15:07.840 --> 00:15:09.920
labeled "Draft" and has also not yet

00:15:09.920 --> 00:15:13.360
been created with our final
draft or version number.

00:15:14.320 --> 00:15:17.560
Therefore, it is not intended
for external distribution.

00:15:17.960 --> 00:15:22.520
Generally, we can say about
the document creation via PIM

00:15:22.960 --> 00:15:27.000
that the fixed input fields as well
as the stored print rules

00:15:27.080 --> 00:15:30.280
save us at least 50% of time,

00:15:30.880 --> 00:15:33.400
in comparison to our
previous manual input.

00:15:33.760 --> 00:15:38.040
In addition, the automatic upload
always ensures that our documents

00:15:38.520 --> 00:15:43.320
are updated simultaneously across all systems,
on the website, in the CRM system.

00:15:46.360 --> 00:15:47.640
Finally, on the subject

00:15:47.640 --> 00:15:51.560
of document generation,
here is an example of released documents.

00:15:51.600 --> 00:15:53.360
Here is the example of our data sheet.

00:15:53.600 --> 00:15:56.000
The print version for the website is

00:15:56.000 --> 00:16:00.520
here, of course, without the draft
notation and with the corresponding

00:16:00.520 --> 00:16:04.800
version number or unique
sequential identification number.

00:16:05.120 --> 00:16:09.720
At this point, I would like to hand over
to my colleague Mr. Sven Steppa,

00:16:09.720 --> 00:16:14.520
who will now give you more
information about the workflows

00:16:14.520 --> 00:16:19.240
that we implement here in the field of
data maintenance and print generation with INCONY.

00:16:20.120 --> 00:16:22.000
Yes, good day from me as well.

00:16:22.000 --> 00:16:23.520
My name is Sven Steppa.

00:16:23.520 --> 00:16:27.040
Today I would like to use
the example of the DOPs

00:16:27.040 --> 00:16:30.720
to explain how we have
designed this workflow

00:16:31.040 --> 00:16:34.480
and how we run the whole
thing through our system.

00:16:34.920 --> 00:16:37.440
Let's take a look at the declaration
of performance as an example

00:16:37.840 --> 00:16:41.280
of how the DOP is created in our company
and what the workflow behind it is.

00:16:42.120 --> 00:16:44.600
On the one hand, the product manager
maintains the product

00:16:44.600 --> 00:16:48.480
in the local language
of the producing country.

00:16:48.600 --> 00:16:51.040
In our case in Germany,
for example.

00:16:51.360 --> 00:16:54.760
Moreover, they also maintain
the respective English data sheet.

00:16:54.960 --> 00:16:57.720
The reason for this is that
the English data sheet,

00:16:57.800 --> 00:17:00.760
or the English DOP,
is the document

00:17:00.760 --> 00:17:03.040
that is distributed to all countries

00:17:03.040 --> 00:17:07.320
in order to hand it to the translators
or the people on site.

00:17:08.000 --> 00:17:13.480
The DOP in German, for example,
is filled in, changed, adapted.

00:17:13.480 --> 00:17:16.760
It is then released by
the respective releaser

00:17:16.760 --> 00:17:18.200
and it then goes to the laboratory.

00:17:18.200 --> 00:17:22.320
The laboratory staff look at
the DOPs, check them

00:17:22.480 --> 00:17:24.320
and then approve them.

00:17:24.320 --> 00:17:26.120
After this approval process

00:17:26.120 --> 00:17:29.920
is completed, fully automatic
print generation takes place

00:17:30.000 --> 00:17:33.680
in the background and the output
is sent to our various platforms.

00:17:33.920 --> 00:17:36.360
The whole thing was
implemented with Camunda,

00:17:36.440 --> 00:17:40.840
INCONY's internal workflow,
and looks like this.

00:17:40.920 --> 00:17:45.720
On the one side we have the
initial product data adaptation.

00:17:45.800 --> 00:17:52.720
We have the release of the workflow
and possibly adjustments

00:17:52.720 --> 00:17:54.840
if it has not been released.

00:17:54.920 --> 00:17:58.360
All this is, or also has this
charm that we can

00:17:58.360 --> 00:18:02.880
export the designed
workflow in Camunda

00:18:02.880 --> 00:18:05.720
and have it in the bag
for an ISO audit.

00:18:05.800 --> 00:18:08.000
This workflow is now supplemented

00:18:08.200 --> 00:18:11.960
by a country version
in the example of the DOP.

00:18:11.960 --> 00:18:12.600
In this example:

00:18:12.600 --> 00:18:17.720
On the left side of the graphic
we see the German workflow,

00:18:17.840 --> 00:18:21.400
next to it the English workflow
and the output in the respective

00:18:21.760 --> 00:18:24.200
national language attached
to the English workflow.

00:18:24.200 --> 00:18:26.920
This can then be individually
adjusted, extended.

00:18:27.200 --> 00:18:30.920
If more languages were now
to be added, another output in

00:18:30.920 --> 00:18:36.200
French, Dutch, Italian, etc.
would occur on the basis of the English output.

00:18:36.400 --> 00:18:38.280
In Camunda itself,
we have the option

00:18:38.600 --> 00:18:44.520
to attach events and actions
to the respective tasks.

00:18:44.600 --> 00:18:49.400
We can enter permissions
there and we can say:

00:18:49.480 --> 00:18:53.080
should individual users release it,
should a group release it.

00:18:53.600 --> 00:18:59.560
And these approvals are
transmitted through the PIM.

00:18:59.640 --> 00:19:01.320
Let's take a look at this in detail.

00:19:01.320 --> 00:19:07.760
We have the options on the
right-hand side that allow

00:19:07.760 --> 00:19:15.680
interactions to be retrieved from the PIM side
and processed in the workflow, and from that,

00:19:16.080 --> 00:19:19.040
documents can be forwarded.

00:19:19.160 --> 00:19:21.080
What does this look like
in the PIM itself?

00:19:21.080 --> 00:19:25.480
We have on one side the product manager
who maintains the product,

00:19:25.480 --> 00:19:28.760
who maintains the data sheets,
who maintains the parameters.

00:19:29.040 --> 00:19:33.440
The release, which is then done by
the product manager,

00:19:33.440 --> 00:19:35.680
means that the data
has been completed

00:19:35.680 --> 00:19:39.840
and then the checks are carried out
by the respective laboratory employee.

00:19:39.840 --> 00:19:43.840
The control area is then locked
for the product manager at that moment.

00:19:46.120 --> 00:19:49.040
The lab employee
themselves can see

00:19:49.040 --> 00:19:53.440
their open tasks on the dashboard
and can then click directly on them

00:19:53.440 --> 00:19:56.560
and release these adjusted DOPs.

00:19:58.800 --> 00:20:01.560
Release and review then
happens in the lab.

00:20:02.160 --> 00:20:04.560
The lab releases this DOP

00:20:04.840 --> 00:20:08.880
and in the background this DOP
is printed automatically,

00:20:08.960 --> 00:20:13.840
which we then forward to
the various output media.

00:20:14.120 --> 00:20:17.680
In the nightly print,
the draft is also removed.

00:20:17.760 --> 00:20:21.480
A version number is assigned
and a signature is printed in it.

00:20:21.600 --> 00:20:25.360
This document is saved to our website,
our CRM system

00:20:25.360 --> 00:20:29.280
as well as to our
audit-proof archive

00:20:29.280 --> 00:20:33.000
in order to retrieve it
for future years.

00:20:33.320 --> 00:20:35.960
Furthermore, an example here,
the documents

00:20:35.960 --> 00:20:39.320
are automatically exported at night
and are for our website.

00:20:39.440 --> 00:20:43.160
The data sheets can
be viewed there

00:20:43.880 --> 00:20:45.240
and are available.

00:20:45.400 --> 00:20:48.480
Why did we choose INCONY or

00:20:48.480 --> 00:20:52.520
what is our summary of the implementation
of the PIM system in our company?

00:20:52.720 --> 00:20:57.720
Data maintenance has become much more efficient;
we have significant time savings.

00:20:58.040 --> 00:21:01.520
We can find all the
information in one place,

00:21:01.920 --> 00:21:05.600
which was not possible before;
many had their own filing system,

00:21:05.600 --> 00:21:07.040
thanks to PIM we have simply

00:21:07.040 --> 00:21:11.000
made it possible to have all the information
about the product in one system.

00:21:11.720 --> 00:21:15.880
We have managed to automate things
that were previously manual

00:21:16.360 --> 00:21:21.160
and the service and consultation
and project management

00:21:21.160 --> 00:21:28.800
have enabled us to have a truly excellent
implementation of our PIM system in our company.

00:21:29.120 --> 00:21:31.560
What are the next steps
we have planned?

00:21:31.640 --> 00:21:35.520
We want to venture a rollout
in the next 15 countries.

00:21:36.040 --> 00:21:39.320
We want to build a
media portal in two steps.

00:21:39.760 --> 00:21:43.320
For one thing, for media
that we have created

00:21:43.840 --> 00:21:49.280
and added ourselves:
Images, videos, etc.

00:21:49.520 --> 00:21:54.280
And we want to create a web catalog
to search the information

00:21:54.280 --> 00:21:58.480
and provide it to the sales force
or external partners.

00:21:59.360 --> 00:22:01.560
Furthermore, we want to
design a label workflow

00:22:02.280 --> 00:22:06.960
or an output of the labels
into another workflow

00:22:06.960 --> 00:22:09.720
to become even more
efficient there.

00:22:09.960 --> 00:22:12.520
Yes, then I would like
to start the first round

00:22:12.520 --> 00:22:15.080
of questions here
on the stage and

00:22:15.760 --> 00:22:20.120
I would like to start by asking
what the acceptance of the employees is like?

00:22:20.120 --> 00:22:23.520
You started this proof-of-concept
with 15 people,

00:22:23.520 --> 00:22:27.000
which was already quite a lot
for us in terms of projects.

00:22:27.280 --> 00:22:31.120
I think at least those 15 have continued,
what is the acceptance of the employees like?

00:22:31.120 --> 00:22:32.520
It is definitely positive.

00:22:32.520 --> 00:22:34.240
When the employees realize

00:22:34.240 --> 00:22:38.520
that you have to make a big investment
to maintain the data,

00:22:38.520 --> 00:22:41.080
but the output you get afterwards
is just tremendous.

00:22:41.080 --> 00:22:42.600
You save a lot of time.

00:22:42.760 --> 00:22:45.040
The employees have time
to do other things

00:22:45.200 --> 00:22:48.160
and they can easily see that they
can find all the information in one place.

00:22:48.240 --> 00:22:52.160
The next question would be:
What is the main benefit

00:22:52.160 --> 00:22:55.200
from the perspective of the employees,
perhaps also of the national companies?

00:22:55.560 --> 00:22:58.200
What do you really see
as your benefit there?

00:22:58.200 --> 00:23:00.440
So one benefit or
the biggest benefit

00:23:00.440 --> 00:23:05.280
that we simply see in the PIM system
is the single point of truth.

00:23:05.280 --> 00:23:08.480
A platform where we have all the information
from all the countries.

00:23:08.760 --> 00:23:09.560
In the past, it was

00:23:09.560 --> 00:23:12.800
often the case that the national companies
created their own documents,

00:23:12.960 --> 00:23:15.840
but we at the head office did not
necessarily notice that changes

00:23:15.840 --> 00:23:19.360
were made to these documents
or only noticed them later.

00:23:19.640 --> 00:23:21.360
Thanks to the PIM system,
we have simply managed

00:23:21.360 --> 00:23:25.200
to maintain this information
in one place and to send it out.

00:23:25.560 --> 00:23:28.920
If someone does something manually,
that is not in the standard and also not wanted there.

00:23:29.280 --> 00:23:33.760
And we have managed in this way to simply
collect all the information.

00:23:33.760 --> 00:23:36.800
And if you need it, you can pull it
from the PIM system.

00:23:37.320 --> 00:23:39.600
Okay, maybe the final question.

00:23:40.240 --> 00:23:44.440
If you take a look, beforehand
you created all the documents

00:23:44.440 --> 00:23:47.520
manually, you also translated
the languages manually.

00:23:48.480 --> 00:23:51.280
How much time have you saved?

00:23:51.360 --> 00:23:55.440
So in total, you can roughly say
that we save 50% of the time

00:23:55.800 --> 00:23:59.680
thanks to the automatic generation of the documents
and the maintenance in the system.