Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

How to Speedily and Efficiently Review Planograms

1.689 visualizaciones

Publicado el

How to Speedily and Efficiently Review Planograms

  1. 1. By: Yonas Beyene Planogram Review Process using JDA Space Planning
  2. 2. Liquor Category Revision process • This presentation is customised for the Liquor Category • Similar process with some tweak to the Planogram Explorer Hierarchy, Labels, Highlights and Tables may be applied to fit specific Category
  3. 3. JDA Space Planning  Project: A file that serves as a container for planogram information.  Planogram: object that represents a group of merchandise on a fixture or collection of fixture elements.  Fixture: object that represents a physical structure on a planogram. – Type of fixtures: • Shelf • Chest • Bin • Polygonal Shelf • Rod • Lateral Rod • Bar • Pegboard • Multi-row Pegboard • Curved Rod • Obstruction • Sign • Gravity Feed  Product: An object that represents merchandise that can be placed on a planogram.  Position: The physical representation of a merchandised product on a fixture in a planogram.  Performance: Fields that allow you to store planogram- specific data for a product. Project Planogram Fixture Product Position Performance Note: The lower level hierarchy supersedes the higher level hierarchy. For example if Shelf under “Merchandising (X)” was set to “Fill Available Space” and product “Merchandising (x)” was set to “Default” and Position level “Merchandising (x)” was set to “Only 1” then only 1 facing will show of that position. “Performance” only stores information which is Planogram specific data where a products is known to have or have had a placement on a shelf. Objects Hierarchy
  4. 4. Objectives Standardise business process Improved efficiency Improved accuracy Increased productivity Improved delivery time Clarity
  5. 5. Business Process Space Planner (SP) • Reviews Planograms Space Planner (SP) • Provides draft to Stores Stores • Accept or propose changes Supply Chain to provide: • “In & Out List” • Promotion List • New Product List • Updated Product Ranking List • Upload MDQ on Business Object Buying Manager • Reviews category Space Planner (SP) • Updates POS data •Reviews Store communications And Publishes changes Space Planner (SP) • Provides MDQ Marketing Team • Delivers POS codes to SP • Provides POS images to SP • Distributes POS to stores
  6. 6. How to display Planogram details on “title bar” and “tabs” • When populating the “Planogram name for title bar and tabs” with “Desc 1”, “Desc 2” and “Desc 3” then one will be able to see the “Store Number” (e.g. “110”), “Name” (e.g. Terminal 1) and “type of store” (e.g. “Main”)
  7. 7. Planogram Explorer Configuration  Group by: IF(Facings>0, "On Shelf", "Not On Shelf")  then by: IF(Desc 45!="", Desc 45"-", "")IF(Desc 50!="",Desc 50"-", IF(Desc 10(Product)!="", "Promo - " Desc 10(Product),"Core - " (IF(Subcategory!="Wines", Desc 1"-" Desc 2"-"Desc 7"-"Brand, Subcategory"-"Desc 2"-"Brand))))  Product description: IF(Desc 45!="", Desc 45"-", "")Desc 49"-"IF(Desc 16(Product)!="", "Rank:"Desc 16(Product) "-","") IF(Desc 9!="", "£"Desc 9,"") IF(Subcategory="Wines",Desc 1,"") IF(Desc 1(Product)="Whisky", GROUP_BY(Desc 2 IF(Desc 45!="", Desc 45"-", "")Desc 7 Brand)Desc 16(Product), GROUP_BY(Subcategory"-"Desc 2"-"Desc 1"-"Brand))"-" ID(Product)"-" Name(Product) Products Tab
  8. 8. Planogram Explorer Configuration  Planogram description: Desc 3 "-" Desc 1 Desc 2 "-"LAST(25,File name)  Group by: IF(Facings>0, "On Shelf", "Not On Shelf")  then by: IF( Desc 46(Product) ="ALEX LIST", Desc 46(Product)Desc 7(Product), "") IF(Desc 47!="", Desc 47, "")IF(Desc 15(Product)="WoW" AND Desc 10(Product)="", Desc 3(Planogram)"-"Desc 15(Product), "") IF(Desc 10(Product)="" AND Desc 50(Product)=""AND Desc 9(Product)!="" AND Desc 9(Product)>=100, "HIGH VALUE", "")IF(Category(Product)! ="Liquor",Category(Product), "") IF(Desc 10(Product)="" AND Desc 50(Product)="","core", (IF(Category(Product)! ="Liquor",Category(Product), "") IF(Desc 10(Product)!="", "Promo - " Desc 10(Product), Desc 50(Product) Desc 49(Product))))IF(Desc 10(Product)="" AND Desc 50(Product)="" AND Desc 16(Product)!= "","Ranked core", "Unranked Core")  Performance description: IF( Desc 46(Product) ="ALEX LIST", Desc 46(Product)Desc 7(Product)Brand(Product)Desc 9(Product), "")IF(Subcategory(Product)!=" ", Desc 1(Product) Desc 16(Product) ID(Product) Name(Product), Desc 1(Product)Desc 16(Product)ID(Product) Name(Product)) IF(Desc 10(Product)="",Desc 1(Product) "-"GROUP_BY(Subcategory(Product)IF(Facings(Product)>"0" AND Desc 16(Product)!= "", Desc 16(Product) "-", "")) Desc 7(Product), Desc 1(Product)) IF(Subcategory(Product)="Wines"AND Facings(Product)>"0", Desc 16(Product), (Subcategory(Product)IF(Subcategory(Product)!="Wines"AND Facings(Product)="0", Desc 16(Product), "")))IF(Desc 1(Product)="Whisky", GROUP_BY(Desc 7(Product)Desc 1(Product)Desc 2(Product))Desc 16(Product), "") Performance Tab Note: “Performance Tab” displays “only” planogram-specific data for a product.
  9. 9. Planogram Explorer Configuration  Planogram description: File name"-"Desc 1 Desc 3  Fixture description: Number(Segment)IF(Name(Segment)!=""," - "Name(Segment)" - ", "")IF(Y(Segment)=0,"", Y(Segment))Name(Fixture)  Position description: IF(Desc 1(Product)!="",Desc 1(Product)"-","") IF(Desc 2(Product)! ="",Desc 2(Product)"-","") IF(Desc 3(Product)!="",Desc 3(Product)"-","") IF(Desc 7(Product)! ="",Desc 7(Product)"-","") IF(Desc 8(Product)!="",Desc 8(Product)"-","")IF(Desc 10(Product)!="", "Promo - ", "")ID(Product) Name(Product) Fixture Tab
  10. 10. Planogram Explorer Configuration • Group by: IF(Facings>0, "On Shelf", "Not On Shelf") Desc 50 Desc 49 Note: The details under “Desc 49” and “Desc 50” are only valid for a specific “Event”. Thus when making a copy of e.g. Event 3a to Event 3b one needs to ensure that after making the copy of planograms onto Event 3b one removes the data by resetting the Description fields e.g. under Desc 49 and Desc 50 and import particular changes (IN’s & Out’s and Promos) that require applying for the New Event. One also needs to consider that other data that is stored under other fields which is not relevant to the following Event may require considering resetting those fields as well.
  11. 11. Planogram Explorer Configuration • In the same network location one would also find some highlights starting with “WDF” which one could easily apply in conjunction with the customisation of the Planogram Explorer hierarchy that has been applied as in above sample configuration screenshot. • Planograms Explorer has been customised to easily allow one to select all positions by their “Status” e.g. “A”, “M”, “S”, “O” and “D” to remove them instantly from all Bays (Planogram Segments) and if one goes to the lower folder (subfolder) then one could easily select only a single Product ID which one perhaps might want to swap with another Product ID. Note: When one has multiple planograms and one wants to identify products that exists in active planogram then one needs to click on the “Performance Tab” in the Planogram Explorer to see “only” planogram specific products. Bear in mind that the Performance Tab requires also similar configuration as Product Tab.
  12. 12. Tables and Highlights • ARUK-HCY-L018.alpha-group.comTable • For clarifications on highlights used on tables click on the column field where Highlight has been applied and one should be able to see the meaning on the “Highlight Legend”. • Note: In the WDF tables it has been included the following: “Status”, “Promo”, “Rank”, “Avg Daily Unit Movement”, “Current MDQ”, “Line Type”, “Calc Demand”, “DC Pick QTY”, “Order Trigger QTY”, “Comb Line Type”.
  13. 13. Note: The New Space Planning Project serves “only” as a temporary storage (which does not require to be saved at the end of the process). The project only serves to allow one to eventually update Product Library with updated information (e.g. New Promo Lines, IN & OUT lists, Comments, New Lines etc...). Planogram Review Process 1. Update/Add Product Library 1. Create a “New” Space Planning Project without creating a new Planogram 2. Open Product Library 3. Import “all” products from the Product Library 4. “Reset Description fields” “where required” e.g. Desc 10 (Product), Desc 16 (Product), Desc 49 (Product), Desc 50 (Product) 4. Import “New Promo List” under “Desc 10 (Product)” and “In & Out list” under “Desc 50 (Product)” & “Comments” under “Desc 49 (Product)” 5. Add “New Products” (if there are any) 7. Open “New Event” Planograms 8. Update Products from Product Library 9. Review Planograms Note: Based on updated info e.g. “Promo” (Desc 10), “In & Outs” (Desc 50) and “Comments” (Desc 49) then group product placement by Region, Brand and Price (“Desc 7, Brand and Desc 9”) for a specific event 10. Publish First Draft 11. Publish Final Planograms
  14. 14. How to Create a New Project File > New > Project > check “Primary Key” >OK > “Create a New Planogram?” > “No”
  15. 15. Create Product Library using MS Access • Create a new Product Library based on MS Access and use “X:WDFEBuying and MerchandisingMICRO SPACE PLANOGRAMSOzJDAIntactixSpace PlanningLibraryProduct Library.mdb” as backend database. Note: The “new” product library that one will be creating will “only” be used as a “staging database” and NOT as “main product library”. Unless of course one migrates from an Excel based Product Library to an MS Access Product library. Also one does not require having MS Access installed on one’s machine to enable one to create a Product library based on MS Access. All one requires is that one’s machine (laptop/desktop) has access to the MS Access driver.
  16. 16. Updating from Product Library into Space Planning Project • If the project is the active window, select Tools > Product Library > Update From Library. If the product library is the active window, select Tools > Update From Library. The Load/Update from Product Library dialog box is displayed Note: Prior to updating Product Library ensure first that the Space Planning Project and Product Library are using “ID” as “Primary Key”. If “Primary Key” is not the same on both and one proceeds with updating the product library then one would end up duplicating existing products.
  17. 17. How to import Supply Chain “Updated Product List” in Space Planning • Tools > Import from Text/Clipboard Note: Ensure that during each import “ID” is selected as “Primary Key” and then select “Ignore this column” where fields in the column do not require to be imported/updated in Space Planning. E.g. where you know product already exists in Project and you only require to update products with “New Promotion” then you would select “ID (Product)”, and “Desc 10 (Product)” ignoring any other columns and keeping the column order consistent as in updated list. Note: Since one would be importing updated information into Space Planning on a regular basis (at least at each Event Interval), it is therefore strongly recommended to save the “Import Configuration” so that each time the import of updated product information can be performed speedily, efficiently and accurately as long as the information in the provided updated list by the Supply Chain Team/Buying Manager is always consistent in the way update list of data is presented to the Space Planner e.g. same “column order”, “column fields” and same naming conventions.
  18. 18. Updating Product Library from Space Planning Project • If the project is the active window, select Tools > Product Library > Update From Library. If the product library is the active window, select Tools > Update From Library. The Load/Update from Product Library dialog box is displayed Note: Prior to updating from Product Library ensure first that the Space Planning Project and Product Library are using “ID” as “Primary Key”. If “Primary Key” is not the same on both and one proceeds with updating the product library then one would end up duplicating existing products. Also ensure that when one selects “Update existing products” by first applying a filter to e.g. “only” update “ID”, “Desc 10”, “Desc 49” and “Desc 50”. If New Product Lines are to be added into the Product Library then add those separately by following above steps but select instead “Add new products only” option without any filter being applied. “Add new products only” option ensures that existing products specific data would be left untouched; thus avoiding loss of data if instead “Update/Add” were to be selected.
  19. 19. How to Speedily Update all Planograms 1. File >Open > select “all” Planograms >select “Open as Single Project” 2. Open Product Library Note: Confirm first that Product Library’s and Space Planning Project “Primary Key” are set to “ID”. 3. Tools > Update from Product Library 4. Update > “filter by the fields that you want to update” > OK > OK Note: above step can only performed when using MS Access as backend database. 5. File > Save As > Multiple Files > select “OK” override existing planograms.
  20. 20. Simplified Review Process A combination of the right Planogram Explorer configuration coupled with the right Highlight and Label will allow one to speedily review planograms and ensure accuracy and on time delivery.
  21. 21. How to compare changes between “old” and “new” planogram 1. Open old planogram 2. Open “Projects comparison highlight.PSH” Note: “Projects comparison highlight.PSH” helps in comparing entire planogram against another or only a section of the planogram against another if for example only the core products are expected to be the same in the “old” and “new” planogram. Thus only changes in the promo bays are expected to be seen if promo is different between old and new. 3. Open new planogram 4. Open “Projects comparison highlight.PSH” 5. at the top click on Window > Tile Horizontal Note: When comparing planograms one needs to take into account that the promos may differ due to the “event” each planogram falls on.
  22. 22. Proposed Improvements  Data stored under “Desc 9 (Product)” to be instead stored under “Value 9 (Product)” – Proposed change will ensure that one can sort by “Highest” or “Lowest” Price as in Space Planning “numeric values” are treated differently when stored under a “description field” such as “Desc 9” instead of a “value field” such as “Value 9” which will prevent numeric values stored in description fields being sorted correctly. The above is true specifically in “Product Library” when one attempts to sort by e.g. Desc 9 Descending.  Each “New Product Line” to be imported with complete info – such as ID, Name, Height, Depth, Width, Brand, Category, Subcategory, Desc 1, Desc 2, Desc, 7, Price, “Status”, “Promo”, Desc 16 (Rank), “Line Type” etc…  Supply Chain/Buying Manager to provide two separate lists for each “Event Review”. – One list should have the complete “IN & OUT” and “New Promos” product list – Second list for “New Product Lines” with complete set of product information such as ID, Name, Height, Depth, Width, Brand, Category, Subcategory, Price, “Status”, Desc 1, Desc 2 (Country), Desc7(Region), Value 9 (Price) etc….. Data Structure Business Process Caution: when migrating “Price” from “Desc 9(Product)” to e.g. “Value 9(Product)” ensure that these changes reflect also in the used formula such as “IF(Desc 9!="", "£"Desc 9,"")” under Planogram Explorer. Thus new formula should be “IF(Value 9!="", "£“Value 9,"")”.
  23. 23. POS Codes & Images • Marketing Team to deliver POS codes and images • Each Event folder will have it’s own POS data stored under each respective folder – For example “Event 4” will have it’s POS data stored under “X:WDFEBuying and MerchandisingMICRO SPACE PLANOGRAMSPlanogramsLiveLiquorLiquor2012Event 4 - 27 June 2012 - 21 Aug 2012POS” – Each event will be using “generic” POS Code  This means that the code for each POS used in each event will be the same generic code as in any other event except the details would be different e.g. which products fall under the same “promo”. This means after the first setup all Space Planners are expected to do is ensure that the path for the “POS” is updated to reflect the event one is working on.  Proposed solution ensures that POS files will not be overridden as files will be stored under each respective event folder.  POS data will be updated efficiently and speedily.
  24. 24. Updating POS data in Planograms Each Event folder will have it’s own POS data stored under each respective folder – For example “Event 4” will have it’s POS data stored under “X:WDFEBuying and MerchandisingMICRO SPACE PLANOGRAMSPlanogramsLiveLiquorLiquor2012Event 4 - 27 June 2012 - 21 Aug 2012POS” – Each event will be using “generic” POS Code • This means that the code for each POS used in each event will be the same generic code as in any other event except the details would be different e.g. which products fall under the same “promo”. This means after the first setup all Space Planners are expected to do is ensure that the path for the “POS” is updated to reflect the event one is working on. • Proposed solution ensures that POS files will not be overridden as files will be stored under each respective event folder. • POS data will be updated efficiently and speedily. 1. Open Planogram 2. Open “WDF_Load Gondola POS Data.PST” table 3. Windows > Tile Horizontal 4. Zoom to see the promo sections 5. Select a product that is nearer to the sign 6. Copy the code under the corresponding “Graphic Strip” onto “POS Code” field a) Repeat process for each sign that exists in the planogram 7. Select “COPY DATA” column > Copy > under “PASTE DATA” column select “only” the first field > paste 8. If the corresponding images are available under the corresponding “POS” folder then the sign images will appear. Note: The table default the POS path is “"X:WDFEBuying and MerchandisingMICRO SPACE PLANOGRAMSPlanogramsLiveLiquorLiquor2012Event 4 - 27 June 2012 - 21 Aug 2012POS" & Desc 2 & ".jpg“. Should you be working on a different “event” than “Event 4” then ensure that the POS path is amended before copying and pasting POS codes under the relevant fields by first right clicking on the “COPY DATA” column > Design > Column Properties > F > amend only the path in RED and leave the rest (in BLUE) intact as it is.

×