Vehicle updates
This describe the process for updating the Tyres (product) within the GlobalDB tool (internal data tool)
FILES DESCRIPTIONS:
Fitments/mount files or 'Tire Selector' files => Only for countries working in inclusion mode
UPLOAD PROCESS
Log a JIRA ticket on https://michelingdic.atlassian.net/jira/core/projects/MIB2CX/board on the correct project
Upload the files you want to update.
Make sure this is a format we are used to receive with column names unchanged. Otherwise the file will be rejected.
Give a quick summary of the changes/additions you have there on the ticket (e.g: new vehicles, new product/vehicles association etc...)
Keep the assignee as 'Automatic'
=> The live services team will make sure it is assigned to the appropriate person
SLAs
We'll have the same SLAs with the internal tool as the ones we had with Lizeo.
For Tyres updates: 15 days of delay for updates => If the files can be taken before, it 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 15days treatment delay).
FORMAT CHANGES
Format changes or additional informations/attributs can of course be added if the data team is aware in advance.
How to handle a format change? 1. Log a JIRA ticket in https://michelingdic.atlassian.net/jira/core/projects/MIB2CX/board 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.5month in advance for those changes. => It involves devlopement and we need to plan with the team according to our bandwidth.
Warning: it is only for data side, if your changes implies devloppement on Apostrophe platform, this will need to be analysed and prioritized by your project's Product Owner.
Last updated
Was this helpful?