Data deployment
Here you can find all the details of AG data deployment process.
Product data integration schema
Kleber and Taurus Agri products integration is simple and based on two files:
general product template (identical for all locales),
Covered.

Product template is being updated by the LB and provided together with Covered in the Jira ticket. Covered database is the same as for B2B Michelin project.
Covered does not have any data information. All articles within Covered are considered active. The column used to determine whether the article should be displayed on the website or not is column AC: "HasDatabookVisibility". The value of this column should be 1 in order to be displayed in the SKU on the website.
Products and articles
Products and articles information is fully data-driven and it's being exported from Covered database.
In order to create a data feed three different Covered files and a Product template are being used:
Covered-Tire - contains all the basic information about articles - designation, mspn, size details, etc.
Covered-Tire rims - complements the Covered-Tire file with rims information,
Covered-Tire accessories - complements the Covered-Tire file with tube information.
As AG project is using the B2B data model we were obliged to add the usages and vehicles information, that's why the Product template was a necessity.
Pressure tables
At present, AG project is not fully data driven. All the pressure tables are created and updated via csv files that are being loaded directly on the website.
Note! The data and the dev teams are working on the data driven mode for pressure tables (https://gitlab-dcadcx.michelin.net/lab/tier-3/-/issues/457).
Last updated
Was this helpful?