Tyre updates

This describes the process for updating the tyres (product) within the GlobalDB tool (internal data tool).

FILES DESCRIPTIONS

• Product Template File helping to create the 'Product' level with basic marketing information How to get it: Download on https://globaldb.michelin.net/ Warning: It is mandatory to download the latest version of the Product Template before making modifications

• Commercial Catalog File containing all the CAI/MSPN/Articles/Sizes list and technical details How to get it: Owned by the countries/regions/LBs. Warning:

  • We do not work in a differential mode, we need to receive the full catalog of sizes for each update

  • Do not change your catalog format, no additional columns without our awarness and no column name changes.

  • 2W (Françoise Pascarel), 4W EUR (Christophe Charbonneau), and BICYCLE (Cecile Ribeyre) catalogs are handled centrally/regionally. In those cases, countries are not in charge of updating commercial catalog (CAI list) and should contact the owner in case of use.

• Prices files For some countries that display their MSRP on the website (simple 2 columns file: CAI/Price) How to get it: Owned by the countries Warning: We do not work in a differential mode, we need to receive the full price list for each update

• Sort order file (for Season marketing priorities) How to get it: Owned by the countries. Use your latest version of the file Warning:

  • We have an automatic treatment behind the processing, do not change the format

  • For B2B usages sort order, please precise on the ticket which usage has been changed

UPLOAD PROCESS

1. Create a JIRA ticket on https://michelingdic.atlassian.net/jira/your-work on the dedicated project

2. Upload the files you want to update => If you have a new product (range), remember to upload both your product template and your commercial catalog and potentially the sort order and price list (if in your country scope)

3. Make sure this is a format we are used to receive with column names unchanged. Otherwise the file will be rejected.

4. Give a quick summary of the changes/additions you request (e.g: new product launch, new CAIs, category change etc.)

5. Keep the assignee as 'Automatic' => The live services team will make sure it is assigned to the appropriate person

Each country/region/LB is owning its data, we observe sometimes issues with data quality and errors. Those won't be spotted, so please make sure your data quality is satisfying.

SLAs

For tyres updates: 15 days of delay for updates => If the files can be taken before, they will of course.

This delay doesn't apply if: - The following process is not respected - Format has changed or columns have been added/renamed => In that case, the file will be rejected and we'll take into account the file only when the expected format is being sent (with a 15 days treatment delay).

FORMAT CHANGES

Changes in format or additional information/attributes can of course be considered provided that the team is informed in advance and validates them.

How to handle a format change? 1. Create a JIRA ticket inhttps://michelingdic.atlassian.net/jira/your-work 2. Precise within the ticket the changes you are expecting to make 3. Precise the date by when we should receive this new format => We'll tell you on the ticket if that change can be handled or not

Please aware us at least 1.5 month in advance for those changes. => It involves development and we need to plan with the team according to our bandwidth.

Warning: it is only for data side, if your changes implies development on Apostrophe platform, this will need to be analysed and prioritized by your project's Product Owner.