Product Database Structure, Workflow & Responsibilities
Executive summary • The advantages with a common Product Database in brief - effective information handling - short time to market, easy to roll out new product ranges - cooperation and information sharing among companies and countries with different languages - all information is used for different purposes (web, print etc) • The Local Catalogues are in English and local language • Each company and the local user (probably a PM) is responsible for input and maintenance of the Local Catalogues • The English Master is the complete total of the local catalogues in English
Product Range
SE
Brands in total 245 Brands that are shared today 87 Brands that are unique 158
NO
FI
DK
UK
PL
CZ
Brands/company and unique brands for that company
Large potential in using each others unique brands!
Structure for sharing information - Automatic, Motor and Telfa Sweden – Local Catalogues
Norway – Local Catalogues Finland – Local Catalogues
Czech – Local Catalogues
Denmark – Local Catalogues English Master
Poland – Local Catalogues
UK – Local Catalogue
Structure for sharing information - Automatic, Motor and Telfa Project plan – English Master of Local Catalogues 1.Translate the complete Swedish Local Catalogue into English.
Q4 2009
2.Copy the specific range to each company in English.
Q2 2010
3a. Each company translate the information to their local language.
Q2 2010 -
3b. Each company complete the Local Catalogues with their local documents. Q2 2010 4. Translation of the local documents into English.
Q2 2011
5. Results in a complete English Master and complete Local Catalogues.
Q3 2011
Structure for documents From articles in Movex we build documents in the Product Database.
Web Printed material
?
Structure – Documents & Publications All the documents in the Product Database are stored and sorted in Brand folders. (Create-environment = where the document lives) Then we build the tree we want to publish in the printed catalogue or on the web. (Publish-environment = where the documents are shown)
Create-environment
Publish-environment Publication one
Brand BrandAA Product Product Product Product1 1 Product2 2 Product3 3 Of course we present our product Product Product Product tree in Publish-environment Product4 4 Product5 5 in Product the6 6 most convenient way for our Brand BrandBB customers need. Sorted in type, Product Product 8 8 Product Product7 7 Product9 9 colour, function or Product application. Product Product Product Product Product1212 Exported to1010webProduct and1111print.
Sortiment WeSortiment are fromAAnow structuring all the Product Product Product Product7 7 Product2 2 Product1212 documents in Create-environment Product 1717 need Product Product Product Product Product1010 in order of brands. We to9 9have the same structure for all companies Sortiment BBthe only unique point Sortiment and brand is 1313 Product Product Product1414 Product1515 for us toProduct build at.Product Product Product7 7
Brand BrandCC Product Product1313
Product Product1414
Product Product1515
Product Product1616
Product Product1717
Product Product1818
Product Product8 8
Product Product9 9
Responsibilities – Product Database & the Business Product Database
The Business
Master Admin (Markus Hyltbring) Responsible for: •System (development, economy etc) •Education & support •English Master
Local Admin (Marketing Coordinator)
MD / Business Area Manager Responsible for: •Product range •Resources •Priorities
Responsible for: •Education & support for the local users •Pictures and media •Approving documents
Local User (Probably PM)
Responsible for: •Documents in both local-English and local language •Maintaining their documents
Keep Product Database updated – New document English Master
Master Admin
1. 2. 3. 4. 5.
User creates a new document in the local English catalogue. User makes a new language layer of the document and translates to the local language. Local Admin approve them. Master Admin put them in the English Master. All the users that are affected are noticed about the new documents. They then choose if they want to update their Local Catalogue.
Danish market
Local Admin
Local User
Keep Product Database updated – Update document English Master
Master Admin
1. 2. 3. 4. 5.
User makes a change in one or both of the Local Catalogues. Local Admin approve them. If the change will affect the English Master the user makes the change there as well. Master Admin finds the changed documents in the English Master and approve them. All the users that are affected are noticed about the changed documents. They then choose if they want to update their Local Catalogues.
?
Danish market
Local Admin
Local User