Data deployment

Here you can find all the details of B2B data deployment process.

Data integration schema

B2B data import is a complicated system based on several files combined together and it changes within regions.

Europe

European Tyre data integration schema

European data integration process consists of 3 steps:

• integration of a RAG file - RAG file contains all the CAIs,

• integration of Product Template - B2B product template activates chosen products and indicates which universe file should be used (thanks to Template TDP column)

• integration of Covered and AUG file - these files complete the information missing from RAG and active the CAIs.

These actions are performed by Lizeo and once done the proper feed is sent to Datastream.

AMN

AMN tyre/retread data integration

B2B databases mapping

Covered database

data model attribut	covered column name	databook usual name
tyre.name	A - TireRange
common.brand	B - TireManufacturer
tyre.articles.cai	C - CAI	CAI
tyre.articles.mspn	D - MSPN	MSPN
tyre.articles.tyreDimension.displaySize	F - DynamicDesignation
tyre.articles.tyreDimension.geobox	J - DimensionalGroup
tyre.articles.tyreDimension.dimensionalEquivalence	K - DimensionalEquivalence1
tyre.articles.RCI	M - RollingCircleIndex
tyre.articles.active	AC - HasDatabookVisibility = 1
tyre.articles.tyreDimension.tkph	AE - Tkph
tyre.articles.tyreDimension.tmph	AF - Tmph
tyre.articles.tyreDimension.seatDiameter	AJ - SeatDiameter	Φ
tyre.articles.tyreDimension.loadIndex	AM - LoadIndex
tyre.articles.tyreDimension.speedIndex	AN - SpeedIndex
tyre.articles.tyreDimension.loadIndex2	AO - LoadIndex2
tyre.articles.tyreDimension.speedIndex2	AP - SpeedIndex2
tyre.articles.compound	AU - Compound
tyre.articles.tyreDimension.sectionWidth	BK - UnloadedSidewallWidth	S
tyre.articles.overallDiameter	BN - OverallDiameter	D
tyre.articles.minDualSpacing	BQ - MinimalDualSpacing
tyre.articles.treadDepth	BS - TreadDepth	Prof Scul Mm
tyre.articles.fillingVolume75	BU - InternalVolume75	Volume 75%
tyre.articles.fillingVolume100	BV - InternalVolume100	Volume 100%
tyre.articles.weight	BW - RagWeight
tyre.articles.loadedRadius	CB - StaticLoadedRadius	SLR or R'
tyre.articles.rollingCircumference	CC - RollingCircumference	Cdr.

Access database

USA tyres feed

Import: to import only the tyres that meet the following criteria: 1.MFG should be = MXin 'NEWTIRE_MASTER' tab 2.MARKET should be = USC, MNA, USA or USM in the 'TRUCK' tab (article level)

Then for Apostrophe export, to consider a tyre as active = yes here are the rules: 3. CODE should be = A in 'TRUCK' tab (article level) 4. Tire_release should have a date in the past or no date in 'NEWTIRE_MASTER' tab

Then for Apostrophe export, to consider a tyre as active = no but to still send it in the export: 5. CODE should be = T in 'TRUCK' tab (article level)

Other rules: 6.if coming soon attribut is on, then we should export the softlaunchdate (column to be added soon on Access database) 7. if at least one of the articles of a product has Tyre.articles.hasDirectionalTread = True then the product should be tagged with Tyre.hasDirectionalTread = True as well

USA Retread feed

Import: to import only the tyres that meet the following criteria: 1.Market_CM should be = USCor USA in 'RETREAD_MASTER' tab 2.Brand_Website should be = MRT or MRTOin 'RETREAD_MASTER' tab 3.Brand_Website should be = PMRT or MMRT in MCPL tab

Then for Apostrophe export, to consider a tyre as active = yes here are the rules: 4. stock_status = A in 'RETREAD_MASTER' tab (product level) 5. stock_status = A, or T in 'MCPL' tab (article level), where T is exported as active=false 6. Tire_release should have a date in the past or no date in 'RETREAD_MASTER' tab

Then for Apostrophe export, to consider a tyre as active = no but to still send it in the export: 7. stock_status should be = T in 'RETREAD_MASTER' tab (product level) 9. stock_status should be = T in 'MCPL' tab (article level)

Other rule: 10. if coming soon attribut is on, then we should export the softlaunchdate (column to be added soon on Access database)

Plug data/locales creation

As mentioned in the General chapter B2B project has it's tab in the Plug data:creation locales Apostrophe file.

The B2B tab is divided into 5 parts:

1. The general information - these fields are mandatory and contains the information about the local to be created, creation priority, date of the feed deliverance and the number of git ticket.

2. Lizeo to Back Office - this part is done once the data available in Lizeo BO. For instance B2B information is not available in the BO.

3. Lizeo to Datastream - these fields help to track the information sent to Datastream, once Lizeo pushed the data to our data base this step can be considered as accomplished.

4. Tyredating - helps to track the development of Tyre Selector by Tyredating (time of TSU delivery can vary from 15 days to a month, depending on the request).

5. DCAD - Authoring team - helps to survey the Authoring team work.

Each part needs to be followed by B2B Project Owners.

Git ticket

As mentioned in Data deployment - git ticket chapter to get the correct and proper feed from Lizeo, the Git ticket must be created. It needs to contain:

1. Product catalog or information which existing product catalog should be used (all the details as well as exemples of product catalogs can be found here).

2. Product template - a list of active products (all the details as well as exemples of product templates can be found here).

3. Dealers file - if Dealer Locator is available on the website.

The first two will give Lizeo the possibility to create a Tyre feed and are mandatory, the three is optional.

Tyre Selector Universal

As mentioned in TSU deployment chapter once the proper feed is available and integrated in the Datastream, in order to include TSU on the new website, Tyredating must be informed via e-mail send to: [e-mail].

The e-mail must contain:

• the locale details,

• the type of TSU to be implemented (master, seasonal, usage, retread selector),

• the feed Id of the data to be used,

• needed date.