Tip:
Highlight text to annotate it
X
My name is Kadima Lonji. I'm the Technology Director at Oakley
and I work in the technology team that manages the e-commerce.
Oakley is a sports apparel company
and that we are based in Southern California.
My use case or why we needed
MDM was a project. We were running an e-commerce platform project,
and that project we have to bring our retail,
our web and our call center systems together,
and in order to do so one of the important elements
was to bring our data together, and as we got into the project
we understood that our legacy data was
all different in the sense that the product information
had over time changed, then
evolved, so we had multiple models
for describing product and we needed to
bring it to a unified model in the e-commerce platform project.
So in order to do that we needed a tool which was the MDM
product from Semarchy to unify these different models into a single
model that could serve the purposes of
the current product sets that we has as well as future ones.
As we discovered that we had this data consolidation
problem and cleansing problem we actually had not anticipate
spending a lot of time on that. So with that surprise we needed a system that
was very quick and adaptable and that could
basically achieve this consolidation very quickly in the middle of our project,
rather than making a new project that was gonna take many many months,
so by working with Semarchy,
I was pleasantly surprised that we were able to stand up
this platform very quickly, bring in
multiple data sources and different models together,
in Semarchy relatively quickly, literally in a week and a half,
and then iterate as we did our project
on that data that was coming from the multiple sources and cleanse it
many many times as we kept working
on the platform. So we did it really quickly
and the flexibility of the system,
the learning curve that it required, which was very short,
all contributed to a successful project.
We did not impact our existing systems
very heavily, so essentially when we
started the project, we are able to
not modify the existing systems that much, but extract data from them
and then in Semarchy we were able to merge the data very quickly, so
the benefit of that is that the existing operations were not impacted
in a broad way
and the big project that we were working on was able to move forward very
quickly. So that was a big plus.
And then the second powerful
element of Semarchy
is that as you work through your
project, you get surprises along the way,
new data that you need, or data that you thought you didn't need, but now need,
and so you quickly can augment the system
with this extra data, and
build it back into your pipeline relatively quickly.
So you iterate multiple times and are able to
work on the project while still
getting new information to join
the main master data relatively easily.
Another area that I enjoyed is working
with the Semarchy team in terms of their flexibility to respond to our needs,
to worked late or respond whenever we had questions,
whether it's about the tool or whether it's about how to do MDM,
following best practices or whether it's
just getting their thought partnership in our project, which was helpful.