JEMS: Implementing a Data Management Solution Across PHE and Its Subsidiaries

What were the underlying reasons or business implications for the need to innovate and transform the business?

PHE is an international spare part distribution for cars. The group was looking to implement a data management solution for all its 21 subsidiaries.

One of the main stakes is to make information flow between the applications of the different information systems, and insert them in analytics and Data Science tools.

The goal was to decompartmentalize everything and create a global and universal architecture (EAI, ESB, ETL, ELT, streaming, etc.) which was very ambitious.

As a unifed Data Platform, built with a Data Centric approach, we had a CENTRAL historized data hub component to answer any typology of use Case.

The first use case deployed in production concerns the Body Shop catalog. Allowing all subsidiaries to have an exhaustive view of the availability of parts and pricing of bodywork elements, all legal entities included.

Which customer did you implement this on?

PHE : Parts Holding Europe.
• PHE is group specialized in the distribution of spare parts for light and heavy vehicles.
• Turnover of 2B€ ,EBITDA of 245M€ in 2021.
• PHE integrates logistic platforms (ACR, Cora automobile, Logisteo) specialized on a part, activities of distribution of parts in B2B and B2C (autodistribution, AD Bosch) and a support service (123 autoservices, idGarages, mondial pare brise…)

Describe your strategy and execution to solve the business challenge.

We had the following 3-step approach along with SNAPLOGIC :

  1. Framing: what are the main challenges and gap analysis with current IS architecture? What are the prior functions to implement to answer business challenges? What kind of data platform and Data organization do we have to put in place? What data governance strategy? What cloud strategy to replace their aging Genio tool? Benchmark on Data Storage as well.

  2. Infrastructure development: Installing tools, deploying environments, applying security management on platforms with SnapLogic’s managed service.

  3. Use Case implementation (iterative mode) implementation of the first pilot for the creation of a body catalog. management, deployment, authentication management, reporting with data visualization and rollout to all subsidiaries.

Who was and how were they involved in building out the solution?

In addition to the project management functions, we have hired:
Data practice managers, cloud architects and SnapLogic experts.
TOTAL 15 FTEs for the project

What were the business results after executing the strategy?

Real Time Analytics set up to improve business decisions
With the 2 data warehouses merged, a unified web site was created
We reshaped the way they sell and increase revenue – less phone interactions and faster business incomes

What was the ROI the customer gained from executing the strategy?

700 Genio ETL Pipelines
36 Heterogeneous Data Warehouses
1 single MS cloud expert – churn with data experts from external SI

Anything else you would like to add?

SnapLogic has a Cloud Data Warehouse Migration or End-of-Life Data Management Replacement offering that JEMS, as a technical expert, values highly.