MO - Motorbike

MO Datamodel is dedicated to Michelin brand

MO Data model can be found on what we called the 'Rosetta table', accessible here: https://docs.google.com/spreadsheets/d/1-UQGdHEJ8unHAk79phP1hamCKlcgMzLF3LNGxSWoDdY/edit#gid=0 There are 4 types of objects in the 4W Data model:

• Common

• Tyre

• Dealer

• Vehicle

4W and MO data models are the same, it is true that some attribut are dedicated only for one business line, we just send the attribut empty

'Common' attributs

Those attributs are always attached to an object no matter what is the object behind. Indeed, a feed will always have: - _id = database ID of the object - createdAt = creation of an object in the feed - updatedAt = latest reception of an object in the feed - id = - globalId = Unique identifier of a product ( is not present for a dealer) - active = is the object active or inactive in the database - brand = For which brand does this object exist (enum) - productLineActivity = For which business line does this object exists (enum) - country = For which country does this object exists - lang = For which language does this object exists - createDate - updateDate - provider = who pushes the feed (Lizeo, Salsify, other?)

'Tyre' object

Tyre attribut can be divided in 2 sections:

• Product level

• Articles (CAI or SKU level)

1.Product Level

What we call 'Product level' is what is driving the product page creation. It is driven by a GlobalID. A product includes several Articles (CAI).

2. Article Level

What we call 'Article level' is a size of one of the product (= product range). It is driven by the CAI

Specificities

`isCircuitTyre` = concerns tyres without LI/SI, they are not road homologated

'catégories' and `usages` are in english and common to all countries for MO

'warranties', 'descriptions' and 'notes' are not in used and is an AMN heritage

'sortOrder' is only used for generic search. Otherwise there is a sortOrder per usage that is handled in the TSU

'Dealer' object

Specificities

'googlePlacesID' is used to display opening hours, street view etc from Google My Business. Hence they are slowly replacing other attributs such as the 'opening hours'

'Vehicle' object

'tyreSet' is only used for MO (or non TSO v3 countries) because the matching between a vehicle and an article is for now directly made on MO Lizeo PIM

Lizeo export the data when:

• it's active in Lizeo's database (Products are activated based on Articles start dates present in a product catalog if none is filled in the Product catalog);

• start date is < to current date or empty (same for tyres);

• end date is > to current date or empty (same for tyres);

• global id and season are not null (except for TK that don't have season information);

• a Product has at least one active tyre (following previous rules);