WEBVTT

00:00:00.160 --> 00:00:05.120
Klickparts, the construction machinery
parts shop, only works with a PIM.

00:00:06.320 --> 00:00:09.200
What also only works with a PIM is Big Data.

00:00:09.200 --> 00:00:12.880
Don't try to experiment with Excel,
it will fail.

00:00:12.880 --> 00:00:14.400
Access is not any better.

00:00:14.680 --> 00:00:18.800
With ANTEROS, even complex data
can be efficiently maintained.

00:00:19.440 --> 00:00:20.760
It is simple to use.

00:00:20.760 --> 00:00:23.200
It offers a mature set of functionalities.

00:00:23.320 --> 00:00:27.280
You always have multiple ways
to solve a problem.

00:00:27.720 --> 00:00:30.360
The data can be very well systematized.

00:00:30.360 --> 00:00:33.360
This saves a lot of maintenance effort.

00:00:33.440 --> 00:00:37.040
Even complex relationships can be
represented efficiently and easily.

00:00:37.200 --> 00:00:41.280
With ANTEROS, much more is possible
than originally expected,

00:00:41.280 --> 00:00:45.240
not only in the shop but also in our
knowledge database we are working on.

00:00:46.600 --> 00:00:50.640
ANTEROS can be customized to a
large extent with our own IT.

00:00:50.640 --> 00:00:54.120
It's really great, and there's no need
to be afraid of it.

00:00:54.120 --> 00:00:56.720
Even if you have no prior experience,

00:00:56.720 --> 00:00:57.760
you can learn it quickly.

00:00:58.400 --> 00:01:00.160
ANTEROS is highly flexible.

00:01:00.160 --> 00:01:03.360
The INCONY team,
the ones I have met,

00:01:03.360 --> 00:01:06.760
are very competent,
helpful, and quick.

00:01:07.840 --> 00:01:09.080
The implementation

00:01:09.080 --> 00:01:13.720
of our PIM in just six months,
with zero prior knowledge in the PIM

00:01:13.720 --> 00:01:17.760
field and a small team consisting
of two individuals,

00:01:18.600 --> 00:01:22.080
each working half-time,
would not have been possible

00:01:22.080 --> 00:01:25.920
without this support.
It would not have been

00:01:25.920 --> 00:01:28.680
achievable without the standards
provided by ANTEROS.

00:01:29.840 --> 00:01:34.080
We have achieved an extreme efficiency
gain in data maintenance.

00:01:34.160 --> 00:01:38.120
We have achieved
consistent data for the shop

00:01:38.440 --> 00:01:41.680
and can build a knowledge repository.

00:01:46.800 --> 00:01:48.800
My name is Marko Wötzel.

00:01:48.800 --> 00:01:53.040
At Klickparts I am responsible
for data structuring

00:01:53.040 --> 00:01:56.000
and data preparation
for our online shop,

00:01:56.000 --> 00:01:59.760
and therefore, responsible for
the implementation of a PIM system.

00:02:00.360 --> 00:02:04.480
Now, let's move on to the question of
why a PIM system is necessary at Klickparts.

00:02:05.240 --> 00:02:08.400
After the establishment of Klickparts,
we had a very tight schedule.

00:02:08.400 --> 00:02:12.080
With the introduction of our ERP system,
the development of the shop,

00:02:12.080 --> 00:02:15.960
and the preparation for the major
construction machinery trade fair Bauma 2019,

00:02:16.560 --> 00:02:20.240
we managed well thanks to
agile working methods.

00:02:20.400 --> 00:02:23.400
However, there wasn't enough time
and resources available

00:02:23.400 --> 00:02:25.960
to build a PIM as well.

00:02:26.320 --> 00:02:32.760
Therefore, we made the decision to launch
with only 10,000 articles at Bauma.

00:02:32.960 --> 00:02:35.240
And we built these articles in Excel.

00:02:35.240 --> 00:02:39.600
Our experience is for around 50 megabytes-

00:02:40.840 --> 00:02:44.240
try opening it and see how long it takes!

00:02:44.480 --> 00:02:45.160
Good luck.

00:02:45.360 --> 00:02:46.760
Yes, well, it crashes.

00:02:46.760 --> 00:02:48.480
All sorts of things happen.

00:02:49.840 --> 00:02:53.640
That's why it was clear to us from the beginning
that we definitely needed a PIM.

00:02:54.080 --> 00:02:57.080
Another reason is that
we work with Big Data.

00:02:57.800 --> 00:03:00.520
Currently, we have around 500,000 articles.

00:03:01.240 --> 00:03:05.360
We plan to build around 2 million
articles in the medium-term future.

00:03:05.720 --> 00:03:08.960
We hope to surpass the
one million article mark

00:03:08.960 --> 00:03:12.040
in the shop by the end of the year.

00:03:12.400 --> 00:03:16.560
The data we process is not only master data,
which includes the name

00:03:16.560 --> 00:03:20.520
or description of the product,
price, and weight.

00:03:20.720 --> 00:03:25.160
No, there are also many, many texts,
SEO-friendly texts.

00:03:25.480 --> 00:03:27.080
There are parameters.

00:03:27.080 --> 00:03:29.200
There are documents and images.

00:03:29.200 --> 00:03:34.160
There are cross-references
and machine application data

00:03:34.640 --> 00:03:38.280
that need to be compiled
to a significant extent

00:03:38.360 --> 00:03:41.360
in order to use them effectively
for a shop and its applications.

00:03:41.720 --> 00:03:47.680
Additionally, we have an extremely
complex knowledge of relationships.

00:03:47.960 --> 00:03:50.160
Which part fits into which machine?

00:03:50.360 --> 00:03:51.880
That's the cross-reference.

00:03:52.080 --> 00:03:54.120
Which machine does a particular part fit into?

00:03:54.120 --> 00:03:55.680
That's the "suitable for" aspect.

00:03:55.680 --> 00:03:57.320
So, if you enter in the shop

00:03:57.320 --> 00:04:00.320
that you need a spare part
for your wheel loader,

00:04:00.320 --> 00:04:03.040
you will find that part with us.

00:04:03.640 --> 00:04:06.600
Additionally,
which parts belong together?

00:04:06.600 --> 00:04:11.040
That's the question of bill of materials,
which includes spare parts and accessories.

00:04:13.160 --> 00:04:15.160
Furthermore, we face an extreme

00:04:15.160 --> 00:04:19.880
challenge in the so-called ETL process,
which stands for Extract-Transform-Load.

00:04:20.120 --> 00:04:24.560
This means that we receive data from
our suppliers in various formats.

00:04:24.720 --> 00:04:32.520
There is really everything from copied faxes
to completed Excel spreadsheets.

00:04:33.000 --> 00:04:35.920
The data comes in different formats,

00:04:36.480 --> 00:04:41.160
usually unstructured, faulty,
incomplete, or with gaps.

00:04:41.840 --> 00:04:43.600
There is always a price list included,

00:04:44.040 --> 00:04:49.760
sometimes images and parameters, but
SEO-friendly texts have never been included so far.

00:04:51.960 --> 00:04:57.080
So, we need to merge, process,
and clean up the data here.

00:04:57.600 --> 00:04:59.280
And try doing that with Excel.

00:05:00.480 --> 00:05:01.600
Excel is great.

00:05:01.600 --> 00:05:04.640
I am myself a passionate Excel user,

00:05:04.720 --> 00:05:07.360
but for this task, it is truly unsuitable.

00:05:08.040 --> 00:05:13.440
I always say that you can't drink
enough coffee while waiting for Excel.

00:05:14.000 --> 00:05:17.880
So why did we choose the ANTEROS
PIM system from INCONY?

00:05:19.080 --> 00:05:21.800
To be honest, by the end of 2018,

00:05:21.800 --> 00:05:24.800
I had to Google what a
PIM is supposed to do.

00:05:25.600 --> 00:05:29.680
We had no prior experience
with a PIM system.

00:05:30.080 --> 00:05:32.040
We conducted our own research.

00:05:32.040 --> 00:05:38.400
We also enlisted the help of a consultant
who evaluated various PIM systems for us.

00:05:38.960 --> 00:05:43.800
We looked at different segments
within the company.

00:05:44.000 --> 00:05:47.800
Including open-source solutions,
SMEs small to medium-sized enterprises,

00:05:47.880 --> 00:05:49.800
and enterprise solutions.

00:05:50.360 --> 00:05:56.080
We didn't want a purely marketing-focused system
that excelled only in print and web layout,

00:05:56.160 --> 00:05:58.760
instead, we needed a technical system

00:05:58.760 --> 00:06:01.120
with a strong emphasis on
master data management,

00:06:01.560 --> 00:06:04.120
to effectively synchronize

00:06:04.120 --> 00:06:06.160
the data I mentioned earlier.

00:06:06.160 --> 00:06:09.960
We needed an integrated data validation
and mass data processing.

00:06:10.080 --> 00:06:13.920
We needed to work with tables
instead of individual entries.

00:06:14.120 --> 00:06:18.440
We wanted to rely on standard features,
not custom developments

00:06:18.440 --> 00:06:22.920
or specific customizations,
at most allowing for configurability.

00:06:23.000 --> 00:06:27.080
We made this decision to ensure
that we remain updateable in the future.

00:06:27.160 --> 00:06:30.240
You can quickly find yourself
in a dead end with custom developments.

00:06:30.440 --> 00:06:37.040
We had a parallel ANTEROS project within
the corporation where we received very positive

00:06:37.520 --> 00:06:40.520
feedback and gained a positive experience.

00:06:40.640 --> 00:06:42.120
It served as an excellent reference for us.

00:06:42.280 --> 00:06:47.240
Most importantly, we found the
suitable data model in ANTEROS 5,

00:06:47.240 --> 00:06:52.480
which is based on the automotive sector's
TecDoc, the TecDoc standard.

00:06:52.800 --> 00:06:56.520
We found extensive functionalities
already included in the standard,

00:06:56.520 --> 00:07:00.200
the nature and scope of the data relationships
within the data model impressed us.

00:07:00.760 --> 00:07:03.720
The configurability is fantastic.

00:07:04.920 --> 00:07:08.120
We were able to do a lot ourselves,
which suits us well.

00:07:08.480 --> 00:07:10.000
I'll get back to that in a moment.

00:07:10.320 --> 00:07:15.080
The expandability, or scalability,
is present in ANTEROS 5.

00:07:15.280 --> 00:07:17.920
We also needed multilingual capabilities.

00:07:17.920 --> 00:07:20.800
Other systems offer that too.

00:07:20.920 --> 00:07:23.640
there are several systems
that can do similar things.

00:07:23.840 --> 00:07:29.040
However, a significant difference lies
in the team behind it.

00:07:29.680 --> 00:07:36.240
The INCONY team showed that they
had experience with complex data models.

00:07:36.640 --> 00:07:40.600
We found a very good understanding
of our specific requirements,

00:07:40.600 --> 00:07:43.320
our specific industry requirements.

00:07:43.640 --> 00:07:46.280
They responded quickly
and very competently.

00:07:46.280 --> 00:07:50.680
The whole thing was very flexible and,
what was very pleasant,

00:07:50.680 --> 00:07:54.440
it was not a software sale,

00:07:54.440 --> 00:07:57.880
but rather a solution and consultation
that was offered to us.

00:07:58.440 --> 00:08:02.200
So, we didn't find the
typical system house

00:08:02.200 --> 00:08:05.720
that would send us a junior consultant
and charge us for many invoices,

00:08:05.840 --> 00:08:10.280
instead, we found honest and
impartial consultation here.

00:08:12.440 --> 00:08:13.960
What convinced us, above all,

00:08:13.960 --> 00:08:19.440
was that our test or demo
was set up within a single day.

00:08:19.440 --> 00:08:22.640
That means I sent the data,
and the next day

00:08:22.640 --> 00:08:24.800
ANTEROS was completely set up
with everything included.

00:08:24.800 --> 00:08:29.000
We didn't expect something like this,
and it convinced us that the system

00:08:29.000 --> 00:08:32.800
may not be so complicated
that we couldn't use it ourselves.

00:08:33.600 --> 00:08:36.320
And an important aspect for us was

00:08:36.320 --> 00:08:40.760
that we could carry out the implementation
without external consultants.

00:08:40.880 --> 00:08:42.760
We were able to do a lot ourselves.

00:08:43.800 --> 00:08:46.440
In our experience, hiring a consultant

00:08:46.440 --> 00:08:48.000
can sometimes result in paying them
three times if you're unlucky.

00:08:48.000 --> 00:08:52.040
The first time when they solve the problem
or set up the system for you.

00:08:52.520 --> 00:08:55.040
The second time when they explain it to you.

00:08:55.040 --> 00:08:57.440
And the third time when they may offer

00:08:57.440 --> 00:09:00.480
to always solve the problem
for you as a service.

00:09:00.680 --> 00:09:05.400
We wanted to be independent or wanted
to be independent and be able to

00:09:05.400 --> 00:09:07.800
deal with our PIM ourselves.

00:09:07.800 --> 00:09:11.600
Because it's not just about having a standalone PIM,
but it also needs to work in conjunction

00:09:11.600 --> 00:09:14.280
with the ERP system and the shop.

00:09:14.600 --> 00:09:19.160
The import function is a highly efficient
tool in ANTEROS.

00:09:20.240 --> 00:09:25.040
Due to the difficulties or challenges
with supplier data,

00:09:25.040 --> 00:09:28.280
we decided to use two
instances of ANTEROS.

00:09:28.560 --> 00:09:31.280
We have a testing environment
where we initially load

00:09:31.280 --> 00:09:35.360
the raw data from the suppliers,

00:09:35.680 --> 00:09:40.040
including various types of data,
and then assess

00:09:40.120 --> 00:09:45.240
whether they are suitable for inclusion
in a PIM system.

00:09:45.600 --> 00:09:49.000
We clean up the data and also utilize
the quality dashboard

00:09:49.000 --> 00:09:52.800
provided by ANTEROS and once the
data is cleansed,

00:09:52.800 --> 00:09:55.200
we transfer it to the ANTEROS
productive system.

00:09:55.440 --> 00:09:59.440
Data maintenance for products is
very clear, simple, and fast

00:09:59.440 --> 00:10:03.720
thanks to the various editors, lists,
collections, and import-export functions.

00:10:03.880 --> 00:10:09.400
For every requirement you have,
there is more than one solution in ANTEROS.

00:10:09.400 --> 00:10:14.280
Overall, it is a truly excellent toolbox
that you can find with ANTEROS.

00:10:15.040 --> 00:10:17.960
We can also configure things ourselves.

00:10:17.960 --> 00:10:19.240
I already mentioned that.

00:10:19.240 --> 00:10:20.720
Here's an example.

00:10:20.720 --> 00:10:24.120
We have configured the SAP tab,

00:10:24.200 --> 00:10:28.560
our ERP system, within ANTEROS,
including all the fields

00:10:28.560 --> 00:10:29.720
and everything that is contained in it.

00:10:29.720 --> 00:10:30.520
and we found

00:10:30.520 --> 00:10:34.040
that it is much easier to load and write data

00:10:34.040 --> 00:10:38.640
into ANTEROS and then export it to SAP.

00:10:39.120 --> 00:10:42.360
Another example of configuration
is our INTERNAL tab.

00:10:42.360 --> 00:10:46.160
We had some internal data that we
didn't want to publish but

00:10:46.160 --> 00:10:50.760
wanted to display and record somewhere
within the product.

00:10:51.080 --> 00:10:54.000
So, we created our own tab with custom fields

00:10:54.000 --> 00:10:56.800
and actively use it for product descriptions.

00:10:57.560 --> 00:10:58.560
The product families.

00:10:58.760 --> 00:11:02.080
In our data model,
we placed the product family

00:11:02.200 --> 00:11:04.760
between the category and the product.

00:11:05.720 --> 00:11:10.560
We received a recommendation
from another PIM user

00:11:10.560 --> 00:11:15.480
who didn't have this feature and later had to
invest significant effort into maintaining it.

00:11:15.960 --> 00:11:18.720
We have found that using the product family

00:11:18.720 --> 00:11:22.280
significantly simplifies and speeds up
the data management process for our products.

00:11:22.280 --> 00:11:27.640
It serves as an excellent summary
for data cleansing purposes.

00:11:28.040 --> 00:11:34.280
Relationships are also maintained within the
product data itself, specifically under the product.

00:11:34.960 --> 00:11:39.320
For example,
we manage the association of spare parts

00:11:39.320 --> 00:11:42.800
to the construction machinery through
the vehicle application relation.

00:11:42.800 --> 00:11:45.600
This relates to the model series
in the master data.

00:11:46.720 --> 00:11:49.200
That is why customers can find their parts

00:11:49.200 --> 00:11:52.840
in the online shop under the "suitable for"
their construction machine category.

00:11:53.400 --> 00:11:56.560
The relationships also exist for accessories,

00:11:56.600 --> 00:12:00.640
This includes related products
and spare parts, known as bill of materials.

00:12:00.880 --> 00:12:04.440
With this, we can also incorporate
complex exploded drawings

00:12:04.440 --> 00:12:09.080
into the PIM and break down
the individual parts.

00:12:10.280 --> 00:12:13.720
Through these multiple relationships
that we can establish in ANTEROS,

00:12:13.800 --> 00:12:16.040
many more possibilities arise.

00:12:16.800 --> 00:12:20.200
Another interesting aspect is that
there is a reverse direction available,

00:12:20.200 --> 00:12:26.480
this means that if I establish a relationship
from the product to the construction machine,

00:12:26.480 --> 00:12:28.520
I can find the corresponding spare parts

00:12:28.520 --> 00:12:31.520
under that construction machine.

00:12:31.520 --> 00:12:34.360
This is particularly useful when
someone wants to know:

00:12:34.360 --> 00:12:37.360
“which parts for my machine
can be found in the shop?”

00:12:37.360 --> 00:12:42.720
The cross-reference relationship,
also present within the product data, works

00:12:42.720 --> 00:12:47.720
in a similar way, it is simply established
and provides a quick way

00:12:47.720 --> 00:12:52.600
to assign parts to specific
original spare part numbers.

00:12:52.600 --> 00:12:57.720
We typically handle this through the import,
the import process.

00:12:58.000 --> 00:13:00.120
Here again, we have
the reverse direction.

00:13:00.120 --> 00:13:04.400
With each cross-reference,
we can see which parts we have

00:13:04.400 --> 00:13:07.400
that are identical or
comparable to that specific part.

00:13:07.760 --> 00:13:12.360
Cross-references are often delivered by
various machine manufacturers

00:13:12.400 --> 00:13:15.040
or different spare part suppliers

00:13:15.040 --> 00:13:20.320
in different formats, and they are
usually not particularly readable.

00:13:20.320 --> 00:13:22.320
Therefore, we always need
to process and work on them.

00:13:23.160 --> 00:13:25.520
It is usually the case
that cross-references

00:13:25.520 --> 00:13:27.520
and model designations

00:13:27.520 --> 00:13:30.520
are manually entered in
products in many shops.

00:13:30.560 --> 00:13:34.240
This ultimately leads to data graveyards

00:13:34.240 --> 00:13:37.840
that are filled with data that
is no longer readable by humans.

00:13:38.280 --> 00:13:42.560
An extreme example we have seen
was 60 single-spaced A4 pages

00:13:42.800 --> 00:13:47.120
with 10pt font size for a single item,

00:13:47.360 --> 00:13:51.760
containing cross-references
and machine applications.

00:13:52.440 --> 00:13:54.440
No one reads that - it is unreadable

00:13:54.440 --> 00:13:57.520
and provides little information
for the customer.

00:13:57.840 --> 00:13:58.840
Parameters.

00:13:59.280 --> 00:14:03.080
Parameters are a challenge in the

00:14:04.880 --> 00:14:07.360
data we receive from suppliers.

00:14:07.640 --> 00:14:11.000
However, it is a crucial feature to control

00:14:11.000 --> 00:14:13.000
the search function in the shop.

00:14:13.120 --> 00:14:15.960
We currently have around 7000 parameters

00:14:15.960 --> 00:14:21.120
and thanks to ANTEROS,
we were able to upgrade and enhance this area,

00:14:21.240 --> 00:14:24.160
allowing us to describe our products today

00:14:24.160 --> 00:14:27.640
with parameters that we previously
only had in texts.

00:14:28.040 --> 00:14:32.720
We use an interface,
the REST interface.

00:14:32.720 --> 00:14:38.680
That isn’t what is left over, it stands for

00:14:39.280 --> 00:14:42.080
Representational State Transfer.

00:14:42.400 --> 00:14:43.800
You’ll forget that right away.

00:14:43.800 --> 00:14:46.640
So REST is the interface in ANTEROS,

00:14:46.960 --> 00:14:49.280
which is a programming interface

00:14:49.280 --> 00:14:53.600
that we use to transfer all the
PIM data into our store.

00:14:54.000 --> 00:14:57.800
So we transfer the products,
the manufacturers, the model lines,

00:14:57.800 --> 00:15:02.120
the parameters, the media assets,
everything, images, videos and so on.

00:15:02.560 --> 00:15:06.160
With this REST interface,
which ANTEROS provides,

00:15:06.160 --> 00:15:09.520
we were able to build our own importer
for the OXID store

00:15:10.000 --> 00:15:12.520
and thus transfer the data,
into the PIM.

00:15:12.600 --> 00:15:14.760
And we do the whole thing once a minute.

00:15:14.760 --> 00:15:18.640
So we have a very quick update
from the PIM into the store

00:15:18.880 --> 00:15:22.360
and can quickly add
new items to the store.

00:15:22.600 --> 00:15:27.080
We can make changes,
we can change the pictures and so on.

00:15:27.280 --> 00:15:29.120
Yes, I'm reaching the end.

00:15:30.080 --> 00:15:33.880
We have successfully implemented
ANTEROS as our PIM.

00:15:34.640 --> 00:15:36.800
Now you know who Klickparts is

00:15:36.800 --> 00:15:39.960
and what we do, how we
work with ANTEROS.

00:15:40.400 --> 00:15:44.000
And, if you ever need a spare part
for a construction machine,

00:15:44.240 --> 00:15:49.520
something for your construction site,
a spare part for a lawn mower.

00:15:49.800 --> 00:15:52.360
you can find that at Klickparts as well.

00:15:54.360 --> 00:16:00.400
We used ANTEROS because
we are a professional store.

00:16:00.400 --> 00:16:02.760
And you can't become a
pro store without PIM.

00:16:02.760 --> 00:16:06.120
Klickparts, the construction
machinery parts shop,

00:16:06.200 --> 00:16:07.920
only works with a PIM.

00:16:09.440 --> 00:16:12.320
What also only works with
a PIM is Big Data.

00:16:12.320 --> 00:16:16.000
Don't try to experiment with Excel,
it will fail.

00:16:16.000 --> 00:16:17.680
Access is not any better.

00:16:17.760 --> 00:16:22.080
With ANTEROS, even complex data
can be efficiently maintained.

00:16:22.520 --> 00:16:23.840
It is simple to use.

00:16:23.840 --> 00:16:26.280
It offers a mature set of functionalities.

00:16:26.600 --> 00:16:30.360
You always have multiple options
to solve a problem.

00:16:30.800 --> 00:16:33.480
The data can be very well systematized.

00:16:33.480 --> 00:16:36.280
This saves a lot of maintenance effort.

00:16:36.560 --> 00:16:40.320
Even complex relationships can be
represented efficiently and easily.

00:16:40.320 --> 00:16:44.360
With ANTEROS, much more is possible
than originally expected,

00:16:44.360 --> 00:16:48.320
not only in the shop but also in
our knowledge database we are working on.

00:16:49.840 --> 00:16:53.840
ANTEROS can be customized to
a large extent with our own IT.

00:16:53.840 --> 00:16:57.080
It's really great,
and there's no need to be afraid of it.

00:16:57.080 --> 00:16:59.840
Even if you have no prior experience,

00:16:59.840 --> 00:17:01.040
you can learn it quickly.

00:17:01.560 --> 00:17:03.240
ANTEROS is highly flexible.

00:17:03.240 --> 00:17:06.480
The INCONY team,
the ones I have met,

00:17:06.480 --> 00:17:10.360
are very competent,
helpful, and quick.

00:17:10.960 --> 00:17:16.840
The implementation of our PIM in just six months,
with zero prior knowledge in the PIM

00:17:16.840 --> 00:17:21.160
field and a small team consisting of
two individuals, each working

00:17:21.720 --> 00:17:25.160
half-time, would not have been possible

00:17:25.160 --> 00:17:29.000
without this support and
it would not have been achievable without

00:17:29.000 --> 00:17:31.560
the standards provided by ANTEROS.

00:17:32.960 --> 00:17:37.280
We have achieved an extreme efficiency
gain in data maintenance.

00:17:37.280 --> 00:17:41.080
We have achieved consistent
data for the shop

00:17:41.560 --> 00:17:45.000
and can build a knowledge repository.

00:17:46.000 --> 00:17:48.600
This is a outlook for the future.

00:17:48.960 --> 00:17:53.800
And with ANTEROS, we aim to become the TecDoc
of construction equipment spare parts.

00:17:54.280 --> 00:17:56.040
We will continue working towards this goal,

00:17:56.160 --> 00:17:59.200
and I hope that we will meet again.

00:17:59.200 --> 00:18:02.200
Thank you for your attention,
and I look forward to your questions.

00:18:06.320 --> 00:18:10.960
Then I’ll start the Q&A session.

00:18:11.040 --> 00:18:13.640
You have experienced quite
a lot with our ANTEROS,

00:18:13.640 --> 00:18:17.120
and it seems that there was a significant

00:18:17.840 --> 00:18:20.000
learning curve involved.

00:18:20.000 --> 00:18:22.600
What were the biggest challenges
you faced during this process?

00:18:22.880 --> 00:18:26.800
The biggest challenge was actually
preparing the data

00:18:26.960 --> 00:18:29.000
in a structured manner to be imported
into the database.

00:18:29.000 --> 00:18:32.760
It was less about working with ANTEROS itself
and more about working with the data.

00:18:33.320 --> 00:18:38.120
We realized the possibilities offered
by the data model and then

00:18:38.120 --> 00:18:41.840
tried to provide the data
in line with that model.

00:18:42.320 --> 00:18:45.520
One slide showed product data,

00:18:45.760 --> 00:18:51.080
and we focused on that in Excel,
as well as the surrounding elements such as

00:18:51.080 --> 00:18:54.080
model series, cross-references,
manufacturers,

00:18:54.840 --> 00:18:58.120
categories, and the various
classifications that

00:18:58.200 --> 00:18:59.960
ANTEROS allows.

00:18:59.960 --> 00:19:02.400
That was not available
in the Excel world at all.

00:19:02.400 --> 00:19:05.960
And that was the biggest challenge for us:
to provide the data.

00:19:06.080 --> 00:19:09.400
Suddenly going from tables
into real structures.

00:19:09.400 --> 00:19:09.960
Right, right.

00:19:09.960 --> 00:19:12.200
Now I'm looking at my little cheat sheet.

00:19:12.200 --> 00:19:14.360
I've jotted down a few more questions.

00:19:15.440 --> 00:19:19.240
Yes, in this learning curve that
you then made accordingly,

00:19:19.480 --> 00:19:22.120
were there points where you said: Hm,

00:19:23.240 --> 00:19:26.240
now you can use ANTEROS for even more

00:19:26.240 --> 00:19:28.560
things than I would have thought before?

00:19:29.520 --> 00:19:30.320
Yes, definitely.

00:19:30.320 --> 00:19:32.960
So after we understood

00:19:32.960 --> 00:19:37.040
how cross-references
can actually be used,

00:19:37.040 --> 00:19:40.880
that was a consultation from INCONY,

00:19:41.960 --> 00:19:44.720
we saw that you can make much,
much more out of it.

00:19:45.000 --> 00:19:47.000
And that makes it very,
very interesting.

00:19:47.000 --> 00:19:51.320
Because we already collected quite a lot
of cross references,

00:19:51.440 --> 00:19:54.240
but we didn't know how to assign them
to the products.

00:19:55.360 --> 00:19:58.840
The customers appreciate that,
have you noticed that you thereby -

00:19:58.880 --> 00:20:01.880
In any case,
we naturally transfer this to the store

00:20:01.880 --> 00:20:06.600
and thus actually lead the customer
to the spare part.

00:20:06.600 --> 00:20:11.040
Very few customers actually know
what the spare part is called or what it is.

00:20:11.240 --> 00:20:13.240
They come in and say:
"I have a red excavator"

00:20:13.480 --> 00:20:16.400
and then they start searching
and then we say well,

00:20:16.400 --> 00:20:19.640
red excavator is a good term,
type that into the search,

00:20:19.640 --> 00:20:22.760
and then we can narrow down more
and more and get closer and closer

00:20:22.760 --> 00:20:24.200
to what they are actually looking for.

00:20:24.200 --> 00:20:26.840
And that can only be done with
the help of structured data.

00:20:26.840 --> 00:20:30.680
We can only do that with the help
of search filters

00:20:30.680 --> 00:20:34.000
that we offer based on the parameters
that we've built and the cross-references and the usage.

00:20:35.000 --> 00:20:40.880
Have you noticed that now that
you have better data,

00:20:40.880 --> 00:20:44.640
you also got higher, better rankings for the store,
you got more customers as well?

00:20:44.640 --> 00:20:48.080
Yes, when you're involved in SEO,

00:20:48.920 --> 00:20:54.040
it's especially important
to provide clean descriptions.

00:20:54.560 --> 00:20:58.000
And it's not so much about the customer
necessarily reading it.

00:20:58.280 --> 00:21:00.800
What's important is
that search engines can read it

00:21:00.800 --> 00:21:01.760
that the search engines

00:21:01.760 --> 00:21:04.120
don't get the impression
it was programmed by a robot.

00:21:04.840 --> 00:21:08.400
These are the things that definitely
fill our shop

00:21:08.480 --> 00:21:12.680
and increase traffic in the shop.

00:21:14.600 --> 00:21:17.160
So perhaps at the very end, one final question,

00:21:17.160 --> 00:21:20.640
you talked about,
you drank a lot of coffee with Excel.

00:21:20.640 --> 00:21:22.720
Has your coffee consumption changed now?

00:21:22.720 --> 00:21:24.080
Yes, now I can enjoy it more.

00:21:25.600 --> 00:21:30.080
It's just that we still like to drink coffee,
but now

00:21:30.080 --> 00:21:32.880
we don't have to drink it, we can drink it.

00:21:33.520 --> 00:21:34.080
Thank you very much.