GDSN Major Release 3.1 Training Course for High Level Changes

Transcription

1 Welcome to the Global Data Synchronisation Network Major Release 3.1 Training Course for. This 30 minutes e-learning targets any GS1 Member Organization, Data Pool or Trading partner that needs to implement or support the GDSN Major Release.

2 By the end of this course, you will be able to: Explain how the Major Release 3.1 will enable quicker and more frequent updates to the GDSN, Learn how to prepare for some changes in GDSN Major Release 3.1, and Understand projected timelines associated with the GDSN Major Release 3.1 Navigation controls at the bottom of each screen will help you interact with the course. Clicking the Menu button will open the course menu. Clicking the Script button displays the audio transcript and audio can be turned either on or off using the Audio On/Off button. Clicking the Play/Pause button will pause or play the screen. Clicking the Previous and Next buttons will take you one screen backward and forward respectively.

3 You can always click the Help button to help you with the navigation controls. Clicking the Exit button will close the course. Clicking the Handout button will open a PDF containing screenshots of all the slides in the course along with the slide notes. First, let s look at what led to the major release.

4 It s been 10 years since the last GDSN major release. Currently, updating the attributes and codes available in GDSN is a slow and long process, which is not adapted to the different industries it serves. It does not move at the speed of today s fast paced business, it is like a paper airplane. GDSN Major Release allows the system to be molded to industry needs and the speed of business (like a rocket), using a new module structure based on product type. The Major Release 3.1 will speed up subsequent maintenance releases and future Major Releases, enabling system updates at the actual level of impact.

5 GDSN deploys changes based on the impact to the network. There are 3 levels of impact. Level of Impact 1 has minimal impact. It includes errata fixes such as spelling errors in definitions and are backward compatible. Level of Impact 2 has medium Impact. Examples include addition of new optionals and attributes, relaxation of mandatory attributes to be optional, and are backward compatible. Level of Impact 3 has Significant impact. It includes the deletion of attributes, promotion to mandatory from optional, restructuring of the message formats, etc. and are non-backward compatible. Global Data Synchronization Network Release Types, are as follows: Efficient Code List Level Of Impact 1 adding new code values which are not hard coded, GPC or Global Product Classification Updates - Updating the GPC Bricks used based on GPC Publications,

6 Maintenance Release - Level Of Impact 1 and 2 changes and finally Major Release - Level Of Impact 1, 2, and 3 changes. The code list are managed outside of the schema, in other words they are not hard coded, into a system. You don t have to change the schema or version number of the software just to update those code list. So what is the GDSN Major Release 3.1? It is an update to the GDSN Standard which takes place on May sixth, It includes modifications of the standard requested by trading partners between 2005 and 2012, a reduction in the number of core attributes, whilst keeping those applicable for all products and sectors, and it enables sector-specific attributes to be added to the core attributes at anytime, increasing flexibility.

7 This means that future modifications will be driven by the needs of the sectors. GDSN Major Release 3.1 uses a module structure. Sectors will be able to establish their own specifications, without impacting other sectors. This enables smaller, more frequent releases.

8 The Global Data Synchronization Network (GDSN) is a single version system, which uses the most current version of the system. There is no backward system compatibility to a previous version of the system. All participants of the network will use the most current version of the system. Deployment of GDSN Major Release 3.1 will take place on May sixth, 2016.

9 What happens if a Trading Partner does Nothing? If a Trading Partner does not make any changes, GDSN messages could fail to be published or received.

10 Let s take a look at the Key Changes in the major release 3.1.

11 Here is an overview of the areas which will change due to the Major Release 3.1. If you wish to have more information, click the arrows, and then the home button to return to this page. If you wish to proceed further in the course, please click Next.

12 A validation checks uploaded content against a set of rules. Validations will be executed by context, which is a high level product type. For instance, validations for Food & Beverage, Medical Devices, or Do It Yourself. All new attributes will be built as optional, and then validation rules can be executed to make them mandatory or dependent, based on product type. For example, for Consumer Products (such as Food & Beverage, Health & Beauty, Do It Yourself, etc.) height, width, and depth are mandatory; but for Medical Devices and Services they are optional. Whether an attribute is Mandatory or Dependent (or conditional) will now be in the validation rules as opposed to part of the data type.

13 New attributes will be added to support first, nutrient serving size basis, such as per 100 grams and secondly, the Daily Value Intake Percent Precision. In the example, the nutrients are Carbohydrates, Potassium, and Niacin. The measurement precision is exact, and quantity is 23 grams and 15 grams for Carbohydrates and Potassium respectively. The Daily Value Intake measurement precision is approximately for Carbohydrates and Niacin; it is less than for potassium. The Daily Value Intake are eight, one, and thirty five percent respectively.

14 New attributes will also be added to support Flexible Nutritional Claims such as Free From, Contains, Enriched With, High In, Increased, Low, Natural Source Of, No added, etc. They can be combined with more than 50 elements such as Energy, Fat, Corn Syrup, Fructose, Preservatives, etc. resulting in Nutritional claims such as FREE FROM FAT, CONTAINS PEANUTS, HIGH ENERGY, etc.

15 Packaging Structure will change to provide Packaging Material details for each Packaging Type, both on the primary and secondary level.

16 Packaging Type Codes have been reduced from hundreds to about 60 and attributes have been added to replace existing codes including Packaging Function Code, Packaging Feature Code, Packaging Shape Code, and Packaging Material Type Code.

17 For Trade Item Unit Descriptors, the list of valid values is changing. Assortment Pack is not included in Inner Pack. New attributes are added to define displays. For more details regarding changes in Trade Item Unit Descriptors, please download the PDF.

18 Attributes are now shared across industry verticals. For example, allergens are available for non-food products. Field lengths change have expanded. For Example, Trade Item Feature Benefit expanded from a length of 70 to 250 characters. There is Language enablement for attributes. You can provide the same information in multiple languages (such as on the back of a cereal box) by using the description fields which contain language code and content.

19 Today, functionality is limited. The AVP schema is a simple text field. It cannot be associated with other information, or use language or a unit of measure functionality. It can only be specified in a large group at trade item core level. In the major release 3.1, there is an alignment between temporary and final attribute areas. Multiple AVP points are present throughout the message, and it can use language, qualifiers, & units of measure. Existing temporary GDSN attributes may be migrated and retired based on the timing of the release.

20 Components are distinct items contained within a Product. In this example, yogurt comes in 3 different flavors peach, blueberry, and strawberry. Sometimes you need to send Ingredients, nutritional information, or regulatory information by components.

21 Components can also be identified in chemical ingredients, hazardous wastes, or regulatory information by components.

22 There are also variable attributes across components.

23 Additional Ingredient information is available for Farming & Processing (such as GMO, Growing Method, Irradiated, Maturation Method, Preservation Technique, Source, Animal, etc.), and Organic Information (such as Organic percent claim, Organic Farming, etc.). This information can be transmitted at the ingredient level, as well as at the trade item level.

24 Additional Ingredient information is also available to indicate the place of activity, such as Birth, Rearing and Slaughter, Catch Zone, Country Of Origin, etc.

25 Sub-Ingredients are the ingredients that make up an ingredient in a structured format. For example, the sub-ingredients of Vegetable Oil are Soybean and Canola.

26 Ability to state that Trade Item information is preliminary Any information may change based on the actual production. A Trade Item can only be PRELIMINARY up to the First Ship Date and must be set to FINAL by the First Ship Date. This ensures Data quality in GDSN.

27 Implementation and support of Global Packaging Sustainability Packaging Sustainability is achieved through Life Cycle Indicators, Sustainability Economic Indicators, and GPP Sustainability Information.

28 The major release enables variations of the same GTIN in the supply chain at the same time. This supports data accuracy and production facility multi-source variations.

29 Enablement of production variants: this applies to Different variations of the same GTIN that occur in the supply chain at the same time. A production variant can be a small change in the recipe of the item, such as 0.1 % less fat with accordingly changed nutrition facts. In Brick and Mortar retails, the Consumer can read package texts before buying the product and thus knows what the product contains. In distance selling, because of EU regulation 1169 which says that for products sold through the internet the same label information must be provided to consumers as that of the brick & mortar retail, we will need to send data for the 2 variations of the same GTIN at the same time, thus providing two sets of product labels.

30 A product hierarchy withdrawal of a publication from recipients and data pool is used to reset a hierarchy or just remove it completely. Hierarchy withdrawals no longer have to pass through validations. This results in shorter lead times, reduction of complexity, better Data Quality and a quicker product update process.

31 GTIN REUSE clock will be disabled. The Data Source is responsible for determining GTIN reuse. The Global Registry will generate a report for data pools. Previously set Discontinue Dates can be removed. Discontinued products will not be deleted from the Global Registry automatically. The Data Source initiates a manual process to delete from the Global Registry and Data Pool when a GTIN is to be reused. The Discontinue Date can be set up to 6 months into the past. Currently, it is limited to today s date or into the future by 1 day.

32 Unit of Measure codes have been changed to align with UN/ECE REC 20 standard.

33 For Packaging materials, some additional mapping will be necessary. Some target markets have their own codes. In addition to this, GDSN introduced a new way of coding packaging material.

34 Shown here is the mapping between T M rules and GDSN, and the mapping between GDSN versions 2.8 and 3.1

35 How should data be migrated to prepare for the major release 3.1?

36 What is the impact of this major release? Let s look at the differences between Web interface users, excel users and machine-to-machine users.

37 How should data be migrated to prepare for the major release 3.1?

38 There is Minimal impact on web interface users. Automatic data migration is supported whenever possible (for codes and attributes which have equivalents). Manual data transfer is still required in some areas; you will have to change certain information (we will show an example shortly). Some attributes change location in the interface and Data Pools will provide a mapping of the attributes.

39 Test Environment displays the Data Pool interface as it will be after the GDSN Major Release 3.1. Check with your Data Pool for availability. You will be able to identify what changes should be made and the actions to be taken.

40 Shown onscreen are some useful support materials for web interface users.

41

42 After May sixth, 2016: Any changes in the data model (such as new attributes, transfers, new codes, etc.) will be reflected in a new Excel template. Download your products via the Data Pool in the new Excel template. Do your modifications as usual and upload the Excel file as usual.

43 Shown onscreen are some useful support materials for Excel users.

44

45 There will be a Medium to High level impact on machine to machine users. There will be New schemas. All messages have to be reformatted for integration. Technical support documentation is available from your Data Pool.

46 Shown onscreen are some useful support materials for Machine-to- Machine users.

47 Finally, let s take a look at the next steps to be taken.

48 So what should you now do to get ready for the major release 3.1? First, inform yourself, then evaluate the situation, and finally, implement the change.

49 Regularly stay up to date with the GS1 Global website. Contact and follow your data pool.

50 Documentation provided to you by GS1 Global Office will help you evaluate the situation.

51 To implement the change, perform a gap analysis for data migration, develop an implementation plan, develop an internal communications plan, and develop a problem solving process.

52 Here are some documents to help you prepare for the Major Release 3.1.

53 The documents relevant to preparation are shown onscreen. Click the links on the right side to be redirected to the relevant webpage.

54 The documents relevant to GDSN standard 3.1 are shown onscreen. Click the links on the right side to be redirected to the relevant webpage.

55 The documents relating to data migration are shown onscreen. Click the links on the right side to be redirected to the relevant webpage.

56 Click the links on the right side to be redirected to the relevant webpage.

57 We have come to the end of the course. Let s summarise.

58 Click each tab for a quick recap.

59

60