1 / 25

GSMP Local Community Network Global Agenda

GSMP Local Community Network Global Agenda. 23 Apr 2009 Melanie Kudela. LCN Global Agenda / Enhanced Process. Welcome to the GSMP Local Community Network Global Agenda Meeting! Key Milestones for this GA Cycle Last Survey Response Summary New Links Optional:

hinto
Télécharger la présentation

GSMP Local Community Network Global Agenda

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. GSMP Local Community NetworkGlobal Agenda 23 Apr 2009 Melanie Kudela

  2. LCN Global Agenda / Enhanced Process Welcome to the GSMP Local Community Network Global Agenda Meeting! • Key Milestones for this GA Cycle • Last Survey Response Summary • New Links • Optional: • Enhanced Process Update to Process Group

  3. Key Milestones for this GA Cycle

  4. WO#08-181 – Question from BarCodes & Identification Work Group WO#08-181-  Indicator Rules     1.  Do you have any trade item with more than eight packaging levels above the lowest retail packaging level? Yes – 8%; No – 92% Responses: 1 we have protional product with the same GTIN which are sold in many logistics 'pallet or display-shipper) 2 GTIN-14 with indicator 1-8 is not used in Germany, instead a GTIN-13 is used for all hierarchy levels. Due to limitations of the current indicator concept a release of indicator 1-8 with no meaning would be supported in order increase GTIN capacity. 3 GTIN-14 with indicator 1-8 is not used in Germany, instead a GTIN-13 is used for all hierarchy levels. Due to limitations of the current indicator concept a release of indicator 1-8 with no meaning would be supported in order to increase GTIN capacity. 4 No we do not have that in our company. GTIN-14 with indicator 1-8 is not used in Germany, instead a GTIN-13 is used for all hierarchy levels. Due to limitations of the current indicator concept a release of indicator 1-8 with no meaning would be supported in order increase GTIN capacity. 5 Existing legacy applications should be taken into account. The business requirements need to be clearly specified.

  5. WO#08-181 – Question from BarCodes & Identification Work Group 2. If the answer is Yes, how many of your trade items have more than eight packaging levels above the lowest retail packaging level?  Response 1 40% of our catalog   3. What is the highest number of packaging levels above the lowest retail packaging for your trade items? Response 1 4 levels. This excludes any products that may be cut in stores (ie watermellon) 2 6 3 between 25 and 30 4 max. 5 5 4 6 Four different level. 7 4 8 5 (each-display-case-carton-layer-pallet) 9 2 10 the highest number is 4 11 I think six, I will check.  

  6. BarCodes Business User Group CR# 09-003 - GDTI Serialization 1. Do you support the proposed solution to change the serial component part of GDTI to include alphanumeric characters and to change AI 253 accordingly?   1 THis does not impact our business. You would need to ensure that any systems can cope with receiving an Alpha rather than numeric number. 2 However, we are not currently utilising the AI and hence weight bearing from this answer is not heavy. 3 test test test 4 Existing legacy applications should be taken into account. The business requirements need to be clearly specified 5 EXISTING LEGACY APPLICATIONS SHOULD BE TAKEN INTO CONSIDERATION: tHE BUSINESS REQUIREMENTS NEED TO BE CLEARLY SPECIFIED: 6 No. Existing legacyapplicationsn should be taken into account. The business requirements need to be clearly specified. 7 Existing legacy applications should be taken into account. The business requirements need to be clearly specified. 8 Existing legacy applications should be taken into account. The business requirements need to be clearly specified. 9 I do not understand this well enough to comment on. 10 Existing legacy applications should be taken into account. The business requirements need to be clearly specified.

  7. GDSN Code List Improvement Work Group WO#08-000013 Q1 PackagingMaterial and PackagingType Code Lists   1. Please indicate which of the following applications are given to packaging material /packaging type codes in your organisation: Responses • Filter the list of SKUs assigned by distribution centre   43% • Manage the reusable assets (plastic crates, pallets, plastic casks...) 57% • Understand the different tolerance for products   14% • Communicate the composition of the materials used in the packaging so proper waste management fees can be calculated   43% • Environmental product tax and returnable trade item information   71% • Other or Additional Comment   14% • it should really be the data recipients to answer

  8. GDSN Code List Improvement Work Group WO#08-000013 Q2-4 PackagingMaterial and PackagingType Code Lists 2. Are there any live (in production) processes based on this information in your organisation? Responses Yes   75% No   25% 3. If the response to Q2 is yes, please specify. Responses 1 -5 Based on master data of packaging material information actual amount of waste/recycling material (e.g. paper) is calculated within waste management process6 to check to which level EA / CS / PA the GTIN corresponds 4.  Is it necessary for your organization to receive this information through GDSN? Responses Yes   7 100% No   0 0% it should really be the data recipients to answer

  9. GDSN Trade Item Implementation Guide Work Group WO#08-000270 The team is currently working on this topic to be included in the GDSN Trade Item Implementation Guide. If you have any documented procedures for GDSN for working with tax information for your country or region, please provide us that information. [Additional documentation and information can be sent to your MO Liaison who will forward it to the GSMP Staff.] Responses 1 In Germany only the VAT rate is included in master data.2 In Germany the VAT rate only is included in tax.3 In Germany only the VAT rate is included in master data.4 In Germany only the VAT rate is included in master data.5 green dot tax6 In Germany only the VAT rate is included in master data.7 In Germany only the VAT rate is included in master data

  10. GDSN Level Below Each  CR#08-000285 Proposal: Identify and clearly define the level below the each and add to the standards for identification  for exchange of relevant product attribute information via GDSN. This request is about product hierarchy and data synchronization. • The issue with clearly defining the level below each has been that the one retailer requires these items to be communicated as an EA and an "Orderable" level. Do all retailers agree that they will  synchronize using this  hierarchy  - "an EA and an 'Orderable' level"?      Responses Agree   12% Disagree   75% Other or Additional Information   75% Response 1 (see comment in Box Question 10 below)2-4 The EA is not necessarily an orderable unit. Quest5 we use TradeItemAnOrderableUnit attribute6 Not a retailer

  11. GDSN Level Below Each  CR#08-000285 2. GDSN Level Below Each  CR#08-000285 (Question 2 of 4)  2. How do retailers and suppliers handle the level below the each currently? Response 1 Currently information on components below each are displayed within the level of this product.The EA is not necessarily an orderable unit. Question whether retailer can process any levels below the EACH not uniquely identified with a GTIN. There are some areas where an GTIN is an EACH and contains two physical products (hair colouring product combined with a spray). In this case the products would have different dangerous goods information. But these can be handled within the specified GTIN, as the attribute class of dangerous goods is repeatable. If there is a need to give more information of the different product there should be additional information / attributes to describe these information. But there should be no additional level below the EACH.The EA s not necessarily an orderable unit. It's questioned whether retailer can process any levels below the EACH not uniquely with a GTIN. Thee are some areas where a GTIN is an EACH and contains two physical products (e.g. hair colouring product combined with a spray).In this case the products would have different dangerous goods information. But theses can be handled within the specified GTIN, as th atribute class of dangerous goods is repeatable. If there is a need to give more information of the different product there should be additional information / attributes to describe these information.But there should be no additional level below the EACH.2 we do not send information below Each 3- 7 Currently information on components below each are displayed within the level of this product (see above).

  12. GDSN Level Below Each  CR#08-000285 3. Please provide examples or use cases of your response to Q2. Response 1 - 6 E.g. in case a product (each) consists of two components and for these components hazardous information needs to be provided, the relevant attribute is repeated (see above). 4. GDSN Level Below Each  CR#08-000285 (Question 4 of 4)    4. Use this example to answer the next question:  There is a case of 232 White Hamburger Bun Dough. How should the information about the product be sent? Responses A one level hierarchy as an EA (which would actually be describing the Case) and then the new "sub each" level describing the 232 dough pieces? There maybe some attributes for the dough pieces that could be somewhat challenging to capture.   12% A CA/EA hierarchy, identifying the EA as the dough pieces with a virtual GTIN assigned to the dough pieces?   0% A one level hierarchy as a CA and only describe the case and nothing inside the case?   0% Other or Additional Information   88% 1 C. A+B may cause problems at retailer.2 - 5 A onelevel hierarchy as described in "C", 5 1 level hier. as an EA or a 2 levels hier. PL-EA 7 The options A and B may cause problems in retailer

  13. LCN Global Agenda Cycle Links • Apr GA (23 Apr Calendar Event) http://community.gs1.org/apps/org/workgroup/gsmp_g_lcn/calendar.php • Feb Survey Results http://www.gs1.org/services/gsmp/lcn/lcn_members.html

  14. LCN Process Group Update

  15. Awareness / Take Away • Liaisons firmly committed to continued progress and success of LCN • Interaction with global groups • Raise LCN level of importance • Persuade MO decision makers and supporting staff of LCN’s relevance [ Capture and address MOs’ key concerns / interests • Concrete plan to realize goal

  16. Works As Documented • Adhering to LCN Principles • Easy access to tools and CRoom • Hindrance to smaller MOs joining is lack of single global collaborative communications infrastructure

  17. Works As Documented • Responsibilities • LCN Monthly Cycles [ Ensure closure on feedback • Confirm feedback clearly communicated back to BRG / WG • Communicate feedback impact and consequences back to LCN [ Institutionalize LCN standing agenda item across board

  18. Works as Documented • Key MO readiness criteria • Resolve representation dilemma • LCN designed to bring community to table • Multi-Industry

  19. Works As Documented • LCN Feedback and Validation Model

  20. Analysis of Questions

  21. Not Documented [ Procedures for [ Questions sourced from Business Units [ Reconnaissance type questions [ 2 way dialogue • ex. Questions sourced from • GS1 Australia • GS1 Denmark and GS1 Malaysia

  22. Works as Documented • Checklist 1 New Member Country Launch • Checklist 2 Establish MO LCN Team in your Country • Checklist 3 GA Responsibilities of LCN Liaisons

  23. Not Working as Documented • World Trade Organization Compliance (TBD) • Projected LCN User growth [ Not yet realized • New MOs participate but without registering community [ Designed to bring user community

  24. Summary: Key Opportunities • Participating MO Liaisons strongly committed to LCN • LCN Champions in participating and prospective MOs • Need our strong support [ Improve communication of feedback impact [Elevate importance of LCN to MO! • Define plan to capture MO’s key needs in 2 step model

  25. Contact Details Melanie Kudela GS1 Director, GDSN Technology D +1 609 620 4514 F +1 609 620-1200 E melanie.kudela@gs1.org

More Related