GDS MR Business Value - GS1 · 2014. 11. 28. · GDS Major Release Business Value 3 Date of Change...

GDS Major Release Business Value

1

GDS Major Release Business Value Team Analysis Document


8 May, 2013


2

Document Summary

Document Item Current Value

Document Number 1

Document Title GDS Major Release Business Value Team Analysis

Date Last Modified

Status Final

Owner Kerry Angelo

Change Request Reference

Date of CR Submission to GSMP: CR Submitter(s): Refer to Change Request (CR) Number(s):

N/A

Document Change History

Date of Change

Version Changed By Reason for

Change / Summary of Change

April 25, 2012

0.01 Kerry Angelo Added straw-man content in Executive Summary

April 30, 2012

0.02 Kerry Angelo Added straw-man content in Executive Summary

May 4, 2012 0.02 Kerry Angelo Added straw-man content in Executive Summary to clarify scope of effort

May 8, 2012 0.04 Kerry Angelo Added straw-man content in Executive Summary to clarify Benefits

May 9, 2012 0.05 Kerry Angelo Conference call notations

August 8, 2012

0.06 Kerry Angelo Updates from July 10 physical IUG meeting and from August 8 Conference Call

August 29, 2012

0.07 Kerry Angelo Updates from August 29 conference call

September 19, 2012

0.08 Kerry Angelo Updates from September 19 conference call

November 5, 2012

0.09 Kerry Angelo Updates from October 17 conference call

November 12, 2012

0.10 Kerry Angelo Updates from November 7 conference call

November 28, 2012

0.11 Ewa Iwicka Updates from November 28 conference call

January 30, 2012

0.12 Kerry Angelo Updates from January 9 and 30 conference calls

April 3, 2013

0.13 Kerry Angelo Update to XML Module replacing Modular Item

April 24, 2013

0.14 Kerry Angelo Updates resulting from sub-team review


3

Date of Change

Version Changed By Reason for

Change / Summary of Change

May 8, 2013 0.15 Kerry Angelo Saved as final version per group motion

Disclaimer

Whilst every effort has been made to ensure that the guidelines to use the GS1 standards contained in the document are correct, GS1 and any other party involved in the creation of the document HEREBY STATE that the document is provided without warranty, either expressed or implied, of accuracy or fitness for purpose, AND HEREBY DISCLAIM any liability, direct or indirect, for damages or loss relating to the use of the document. The document may be modified, subject to developments in technology, changes to the standards, or new legal requirements. Several products and company names mentioned herein may be trademarks and/or registered trademarks of their respective companies.


4

Table of Contents

1. Executive Overview ............................................................................................................ 5

1.1. Introduction......................................................................................................................................... 5

1.2. Major Release Benefits ...................................................................................................................... 5

1.3. Solutions in the Major Release .......................................................................................................... 6

2. Document Purpose ............................................................................................................. 6

3. Document Scope ................................................................................................................ 7

3.1. In Scope ............................................................................................................................................. 7

3.2. Out of Scope ...................................................................................................................................... 7

4. Major Release Background ................................................................................................ 7

5. Business Value Analysis.................................................................................................... 8

5.1. Key Business Functionalities Introduced ........................................................................................... 8

5.2. Business Value for Data Source, Data Recipient, Data Pools, GS1, GDS Network ......................... 9

5.3. Business Value for Data Recipient .................................................................................................... 9

5.4. Business Value for Data Source ...................................................................................................... 10

5.5. Business Value for Data Pools & Solution Providers ....................................................................... 11

5.6. New XML Module Structure ............................................................................................................. 11

5.7. Risk of Not Deploying the Major Release ........................................................................................ 12

5.8. Risks of Deploying Modular Item & Context in Major Release ........................................................ 13

6. XML Module & Context ..................................................................................................... 13

7. Reference Documents ...................................................................................................... 14

8. Acknowledgements .......................................................................................................... 14

APPENDIX A: KEY TERM DEFINITIONS ............................................................................................................ 15


5

1. Executive Overview

1.1. Introduction

In October 2004 when GS1 launched its Global Data Synchronisation Network (GS1 GDSN®), there

were only 74,000 GTINs shared among trading partners in 13 countries in the Global Registry. Today, over 25,000 companies have made the GS1 GDSN a cornerstone of their supply chain initiatives in more than 150 countries across multiple industry sectors. More than 10,000,000 GTINs are now shared among trading partners.

At the core of the Network is the GS1 Global Registry that is a “yellow pages” directory operated by GS1, allowing companies to locate critical source/supplier or recipient/buyer information to exchange standardised data with trading partners worldwide. This Registry is one of the most essential tools within the GS1 GDSN which is a powerful environment for secure and continuous synchronisation of accurate data for products shipped through international supply chains.

GDSN was originally implemented in the Consumer Packaged Goods [CPG] Retail sector but is applicable to many other sectors in the Global Supply Chain. The changes in this Major Release are expected to greatly improve the implementation time for new sectors beyond this core GDSN sector. This will be accomplished by easing the CPG restrictions developed to meet legacy business requirements needed for CPG Retail to support the flexibility needed for other sectors. It utilises the concept of ‘Context’ to drive what information is appropriate and necessary for each industry sector to describe a Trade Item. Information may be optional to be exchanged in one sector, while for one another sector it may be mandatory to be exchanged. This flexibility is at the core of the value of ‘Context’.

1.2. Major Release Benefits

The GDSN Major Release will improve the GDSN standards by removing the complexities noted

above. It will support adoption of non-CPG sectors more elegantly; not forcing neither the exchange of

CPG attributes nor the use of CPG business rules and data validations. Both new and existing sectors

will realize this benefit; new inherently and existing when mergers and acquisitions introduce new

[sector] products into existing product catalogues.

It will promptly support any requests for new data attributes. For example a sector can respond to

government regulatory mandates by quickly adding the needed exchange of data into GDSN; as well,

any sector can request the addition of new attributes needed to support new product categories as a

result of acquisitions, growth or adapt to general or specific market changes for their sector.

The new releases will no longer impact all user companies, but only those affected by the changes

and additions, therefore alleviating costs of unnecessary upgrades. Removing complexity eliminates

the barrier to adoption, which has discouraged new participants and new sectors.

There is also the opportunity to eliminate non-GDS channels of communication, when GDS is truly

comprehensive and able to pass all relevant information in a timely way.

This GDSN Major Release also introduces functionality to support multiple prices for a trade item

meeting the needs of the supply chain for actual methods of pricing utilized by some sectors. This

enhancement to ‘Price Synchronization’ will bring great value to those supply chain companies that

use this more complex pricing model.

In total, this release delivers the ability to support the on-boarding of all sectors and industries into

GDSN in a more efficient, cost effective and timely manner.


6

1.3. Solutions in the Major Release

Improved XML Structure: The current design of the trade item data model is CPG centric based on legacy participation in the development of Global Data Synchronization [GDS] where CPG sector was an early adopter and driver of GDSN. This design is not flexible enough to meet the needs of other industry sectors that want to adopt GDSN and gain from its many benefits. This has presented challenges for new sectors and overall makes it more difficult to attract other sectors to global data synchronization. This resulting complexity for non-CPG sectors resulted in longer timelines for their adoption of GDSN. For example in some cases non CPG sectors had to exchange CPG attributes that were not applicable to their business model. Additionally they had to validate this data with business rules and validations that were not pertinent to that sector. Additionally the current CPG implementers have issues with long implementation timeline and implementation of new standards (long time in current model). One set of inflexible business rules for all sectors and organization of validation rules add complexity for some trading partners. The size of the current model makes it very difficult to understand and implement to meet particular trading needs. Business Process Enhanced By:

Corrective restructure of Hazardous Information Dangerous Goods and Substances

Full Hierarchical Withdrawal o Ability to restructure hierarchy prior to ship or corrections

Preliminary Trade Item o Ability to send estimated information

New tax structure o increase the usability of this data

2. Document Purpose

This document will capture the business value for the GDS Major Release; including Data Pools, Data Sources, Data Recipients and the Global Registry. It will focus on XML Module and Context as structures of the GDS item message exchanged for the purpose of synchronization. It will also define the business process values introduced and enhanced as components of the release.

In 2010, all open GDSN Work Requests were studied and compared to the current XML structure. This study applied the concept of Context [based on the Global Product Classification [GCP] of the Trade Item] to the proposed structure changes of the GDSN synchronization message, using Context as the source for validations rules.

In summary the structural approach would be:

A small set of attributes as the ‘core’ of the Trade Item message [where these attributes are the minimum required to define that item uniquely in the global supply chain]

A Global Product Classification assignment for the Trade Item carried in the ‘core’ attribute set

XML Modules that are ‘appropriate’ to the GCP

With ‘validations’ to check the population of data in attributes [standard for ‘core’ + validations appropriate to the assigned GCP

The results of that study indicated that the proposed changes to GDSN could serve to introduce Network changes on a timelier basis and with less complexity.


7

Additionally this document will explore the business value for Data Source and Data Recipients in the network noting however that their value is greatly dependent upon their Data Pools implementation of this release. How a data pool interacts with its members is not in the purview of GDSN. Each Data Pool works to establish value added interactions with their member base and GS1 is not engaged in that business relationship.

Data Source and Data Recipient members of GDSN are greatly encouraged to work with their Data Pools in the various work efforts underway to plan and educate on the release.

Data Pools are greatly encouraged to engage in Operational and Technical Advisory Group [OTAG] to understand all aspects of the Major Release as part of their overall understanding of the changes in the GDS Major Release.

3. Document Scope

3.1. In Scope

Scope for this document is limited to GDS Major Release with a focus on XML Module & Context. The new and enhanced Business Process supported will also be discussed.

3.2. Out of Scope

Any detailed review of 3.0 Change Requests. Also out of scope is the development of Return of Investment calculators for Data Pools or Business Partners.

4. Major Release Background

As GDSN had expanded into new sectors it became apparent there are many inefficiencies of how the current data sync model limits speed to market for critical changes for new industries. It was realized that some of the following capabilities needed improvement:

The need to support regulatory compliance requirements (e.g., allergen information, material safety information), which many times have unique requirements or different implementations across different sectors and different geographies

Product marketing information which includes business to consumer (B2C) information for retail or other promotional processes. This may also include the ability to send and retrieve information using new and upcoming technologies in the mobile communication areas.

Enhanced functionality in ‘speed to market’ offers further support for business applications such as product recall, hazardous materials and/or sustainability.

The proposed solution for XML Modules eliminates some of these challenges and creates opportunities from improvement by taking a more context-sensitive approach to information sharing.

HOW WILL THIS WORK?

This approach reduces the size of the “core” item attributes to solely those applicable to any trade item or service independent of the sector. Attributes that are not used within all business scenarios (e.g. different sectors or geopolitical regions) would be arranged and communicated in context sets (includes validations). This allows:

Easier entry into new sectors or adjacent sectors, and geographies

Reduction of the time required to introduce new attributes or code values into the GDS network


8

Expansion of data content for regulatory compliance, product marketing info and to support additional business applications such as product recall, hazardous materials or sustainability.

Additionally the intent of the XML Module design is to remedy the following issues with the trade item and related data that defines an item:

Unnecessary constraints on attribute usage

Rigidity of attribute characteristics

“One size fits all” nature of the current model constrains ability to meet the needs of varying industry sector, target markets and regulatory requirements

Healthcare sector does not have Length, Width and Depth information for Pharmaceuticals.

o Current Trade Item message requires that this information is included

o Resolution to this currently is to have Healthcare enter ‘fake data’ for these three mandatory fields

o With Context these fields would be checked for population if context is ‘FMCG’ and would not be validated for population if context is ‘Healthcare’; both are Industry Contexts

Difficulty in updating code lists that are part of the message; embedded in the message

Global Product Classification (GPC) attributes are not maintained in the Global Data Dictionary (GDD) creating confusion in the user community.

5. Business Value Analysis

5.1. Key Business Functionalities Introduced

Beyond XML Module & Context, the GDSN Major Release also introduces other new functionalities that are ‘pivotal’ for some of the network community members. Several of these bring long awaited support for business process to the Network members who plan to utilize them. These benefits are defined in the Business Requirements Analysis Document [BRAD] insert link here.

Release Features:

o New validations to ensure data quality

o Trade Item Components Restructure: Identify ingredients and nutrients for multi-item variety pack Support ingredients and nutrition for each component level of a Trade Item the ability to relate sub-ingredients to an ingredient

o Support for exchange of Packaging Sustainability Program information o Similarly support exchange of the attributes for:

Hazardous Information Dangerous Goods and Substances

o A new structure for tax information will increase the usability of this data when exchanged in the GDS Network.

o Full Hierarchical Withdrawal

o Preliminary Trade Item

o Multiple Expressions of Price


9

5.2. Business Value for Data Source, Data Recipient, Data Pools, GS1, GDS Network

The GDS Major Release will reduce risk and eliminate barriers to adoption for the trading partner community by:

Introducing greater backward compatibility, eliminating the “big bang” changes that are required to occur today when new functions and attributes are added

Permitting new Trading Partners to gradually adopt GDSN by synchronizing a small set of attributes in a small core and adding extensions as business needs arise and Return On Investment [ROI] is proven

Allowing Trading Partners to pick and choose what works for them in their industry and not having to follow the bulk of adopters in the CPG area

Allowing Trading Partners to implement local requirements without impacting the whole users base in other geographies

Permitting Data Pools to create more flexible validation rules depending on the specific trading partner requirements

Facilitating the certification processes for the Data Pools without compromising the integrity of the network

5.3. Business Value for Data Recipient

Affected Data Recipients can be divided into 2 groups:

1. Those recipients that have implemented GDSN

2. Those recipients that have not yet implemented GDSN

For recipients that have not yet implemented GDSN, the advantages of the major release exceed the drawbacks, allowing a phased or gradual adoption as stated in section 4.2, by synchronizing a small set of attributes in a small core and adding extensions as business needs arise and ROI is proven.

For those recipients that heavily contributed to and invested in GDSN, the migration effort will be large. This both from a time and cost perspective. The added value of the major release will be limited on the short run although it will increase over time. These recipients will have to be supported in the transition period. This support can be provided by GDSN or by the Data Pools. Support by GDSN could be e.g. through developing a good transition scenario. Depending on options analysed and determinations made by the GDSN Board on the analysis, support by the Data Pools could be provisioned by transformation services of messages coming in the new format back to the old format while still enabling new features. While based on the decision of the Board this extenuating support will not be necessary, it was a consideration.

In summary the chosen model and approach chosen for the Major Release will provide:

Improved “time to market” for retail specific business needs

Improved “time to market” for adaptation to regulatory requirements

New structure of AVP will improve data quality; can insert AVP’s in more locations within the XML Standards vs. current approach of two extension points that do not support association to other attributes

Enabled ability to choose context to receive information about

Possibility to target information based on context to different departments and/or legacy systems

Support for protection against irrelevant information

Enabled possibility to synchronize information for new items that are not yet listed

Enhanced and more efficient error handling for trade item information


10

Enhanced data quality assured by improved and configurable validation of trade item information

Validations will be easier to manage and configure both in retail system and at the recipient data pool.

o Different levels of validations can be used for different contexts and within contexts; it will be faster and easier to turn validations on and off.

o It will be easier to set constraints on attribute level, A constraint for the number of times a specific attribute should be repeated for example offers protection against problems for one recipient that do not support more than one. Meanwhile allowance for an unlimited repeat of the same attribute at another recipient offers them valuable business benefits.

o It will be easier to configure rules based on comparisons between attributes

5.4. Business Value for Data Source

Approved ability to adopt Global Data Synchronization is greatly improved with flexible framework; small core + schema snippets + Attribute Value Pair [AVP] / Trade Item Validation [TIV]

o Improvement in ability to implement additional countries, industries, product categories and customers; improves implementation of SME organizations

Strategically MjR is a framework that allows faster implementation of future business needs in areas of Business To Business To Customer [B2B2C], Sustainability and Regulatory Compliance –

New XML validation process is more structured; validations will be ‘targeted’ against the attribute in a specific context & will be presented in a validation rule language

o Data Source will better understand the Data Recipient data requirements; use of a ‘validation rule language’ is that the presentation will be consistent; this will help to alleviate ambiguity for better understanding of these important validations

Acquiring data from back-end systems will be more efficient in support of new business relationships / on-boarding

Decrease timeframe for new item introduction

Will be able to meet more data requirements of Data Recipients:

o Reduction of time for AVP [Fast Track] to migrate to an actual standard attribute

o Reduction of use of AVP due to use of modules

o New ‘context driven’ XML will decrease on-boarding time for new industries for their specific attribute needs; new attributes for these sectors and modifications to validation of attributes

o Reduce Item Portal requirements for ‘top off’ since it’s easier to add attributes into GDSN; reduction in cost for portals and entry time

Support varying product requirements across Industry Sectors and Product Types

For example: no packaging dimensions required for Health Care

Fewer non-applicable GDS mandatory attribute requirements will reduce entry of ‘dummy’ data for better quality of data for Data Recipient


11

5.5. Business Value for Data Pools & Solution Providers

Moving beyond the compliance requirement that all Data Pools & Solution Providers must meet…

Data Pools and Solution Providers as technology providers to GDSN, the Business Values for the GDS MjR are:

o Ability to onboard new segments, markets, sectors faster, it can increase opportunities for DP’s in the area of market penetration

Ease of adoption of GDSN Roadmap – more flexible technical structure with XML Modules & Context

o Contextual validation as part of new GDS message architecture

Clarity around validation rules vs. business rules; beginning with this release business rules will moved into the Implementation Considerations section of the Trade Item BSD for better identification and explanation

o In the past this has caused confusion among Data Pools where some implemented a business rule as a validation rule and vice versa

Healthcare hits barrier of retail basis of current XML where mandatory fields do not apply

o Context and XML Module will remove this barrier

In the past Data Pools have adapt some aspects of releases based on community need [not all aspects of ‘optional’ functionality are adapted by all data pools]

o The flexibility of the new model will allow Data Pools to limit non-interoperability by providing easier, more flexible and faster to market adaptation to new customer and Data Pool interoperability needs

o More cost effective and efficient for Data Pools to participate in the Network

o Some functionalities in GDSN are not mandatory for Data Pools to support and Data Pools are not required to ‘certify’ on these features; this ‘selection’ based on Data Pool’s community needs impacts the ability for Data Pools to interoperate

Better organization of attributes and validations within contextual relationships

Documentation realignment and quality

o Reduction in the number of Standards documents for the GDSN Trade Item Standard

o Provides for reports by Context [business scenarios] for validation and business rules and required modules

Global Data Dictionary

o Context supports improved query of validation rules and XML Modules

The GDSN Test Data Pool KATO is available for use by any Data Pool for quick uptime to this release as well as for Data Pool Certification

5.6. New XML Module Structure

Due to the parallel activities underway that are supporting this release development, some decisions remain to be made around the technical implementation of the release and provide the following value:

• Allows time for continuous improvement of the model during this period of several parallel activities and for the future


12

• Can adapt or shift technical approach to meet community needs; new sectors can be implemented with minimal to no impact to existing sectors

The new XML module structure does raise certain questions.

• For the initial implementation, while an attribute can exist in multiple contexts the attribute exists in the XML structure only once

• Education for the GDSN Community on this and other factors of context will be required

5.7. Risk of Not Deploying the Major Release

The impact of not introducing XML Module & Context is explored in this section. If not included, several key work efforts that are either completed or underway would need to be repeated and would impact the GDSN budget as well as the time of the participants and the GDSN Board of Governors. This includes but is not limited to:

Drummond Group Test Case Development – additional costs required to re-work test cases and plans

Community Management to re-reset expectations will be significant

Major Release and Certification event will still be required but will be delayed appropriate to the rework referenced above

Community will continue to wait the current 18 – 24 months to get a simple CR implemented into the network

Slowing adoption of GDSN in new sectors

Continue having wrong data flowing through the network just to fulfil the mandatory fields

The longer the deployment is delayed, the bigger the gap and the bigger the migration effort and the more users will be impacted as the community grows

GDSN has not deployed a Major Release since 2006. This release represents over 140 work requests that have been queued waiting deployment to the network. These requests are inclusive of:

Backwards Compatible changes

o 200 New attributes

o 630 Code values (new attributes + adds)

o 30 New validations

Non- Backwards Compatible changes

o 14 classes restructured

o 10 attribute length format changed

o 4 Cardinality of attributes changed

o 6 attributes removed

o 30 schema embedded codes added

These changes are necessary to support:

Regulatory requirements to represent sub-ingredients to an ingredient – GDS Item cannot support in current production

Exchange of Packaging Sustainability Program information

o Restructure of packaging to state primary, secondary, tertiary package types and materials


13

Trade Item Components Restructure:

o Identify ingredients and nutrients for multi-item variety pack

o Support ingredients and nutrition for each component level of a Trade Item

Additionally if this release was not deployed alignment with the XML architecture in the B2C initiative for GS1 Source [of trusted data] would be infringed as the technical solution is using XML Module.

5.8. Risks of Deploying Modular Item & Context in Major Release

The known risks of deployment are represented by the significant changes in the GDSN Major Release. For details on risks and change management readiness, please refer the GDSN Major Release Risk Analysis document. This document is a readiness assessment tool that identifies what is changing and identified resolution options to mitigate the risks an organization may discover as it prepares to implement this release with their supply chain partners or on their own.

A GDSN Pilot Specification document is another document that may provide insight into the changes of this release. This document is purposed to detail the approach and scope of the pilot activities that will be used to test the draft standards prior to the Data Pool Certification activity. The Simulation Pilot will test the expectations of new and modified business process as supported by the Business Requirements and translated into the technical modifications of new and changed XML.

6. XML Module & Context

As GDSN expanded into new sectors many inefficiencies and limitations of the current data sync model became apparent. It was realized that the following capabilities needed improvement:

Support requirements of varying industry sectors and target markets (e.g. product marketing or promotional information)

Support regulatory compliance requirements (e.g., allergen information, material safety information)

Support requirements to send and retrieve information for the mobile communication area

Enable code list updates that are embedded in the message

Enable a high speed to market for critical changes. With the Trade Item and models for MR3 these capabilities are improved significantly:

The new item message will be very small, containing the basic information necessary to introduce an item into the supply chain. Additional information about the item can accompany this basic information.

Appropriate validations on these additions will be applied to ensure proper population and transmission of applicable information.

Nwe sectors can be implemented with minimal to no impact to existing sectors that are already implemented. Also, existing sectors will have the ability to more quickly adapt to changes such as new regulations and implementation improvements.

HOW THIS WILL WORK This approach reduces the size of the “basic” item attributes to solely those applicable to all trade item or services across all sectors. Additional attributes beyond basic to support the product classification assignment will also be communicated and appropriate validations will be applied to ensure proper population and transmission of applicable information.

For example: As new GS1 industry sector, Healthcare currently does not use or want to exchange Length, Width and Depth information for some of their products.

In the future there could be other industry sectors that have similar if the same requirement


14

Current GDSN Trade Item message requires that this information is included [origin of GDSN in FMCG/CPG]

o Without ‘context’ the path forward currently would be to have Healthcare enter ‘fake data’ for these three mandatory fields

With XML Module & Context these fields would be checked or validated for population if context is ‘FMCG’ and would not be validated for population if context is related to the Healthcare sector

ANALYSIS An analysis of the Major Release by GDSN staff was undertaken at the request of the GDSN Board. This was governed by the desire to mitigate as much as possible, the cost of data pools and users to implement the new standard. Other considerations such as disruption of current production systems were also taken into account as well as the GDSN Board’s direction to ensure that the expectation of change would not slow nor deter GDSN expansion. The baseline for this effort was all open GDSN Work Requests as of May 2011; represented by approximately 140 individual work requests. Although the XML Module solution is anticipated to have an impact on all stakeholders, design measures have been taken to limit the impact on the current installed base. Data Pools will try to reduce the impact to their customers, to the extent possible, based on their implementation of the Major Release. This impact is not limited to XML Module but comes also from other components of the Major Release such as tax restructure and ingredients sub-structure. These are important functional changes requested for the Network to improve data quality and regulatory requirements in some markets. The GDSN Board reviewed the pros and cons of several approaches for delivery of the Major Release. These options were reviewed against customary methodologies and the Board reaffirmed their support of the Major Release as defined with the inclusion of XML Module & Context. Additional detail on the analysis is available from GDSN Inc. on request. Ongoing evaluation of the business impact and risks as the implementation work is underway, will serve to provide the Community with detail for their consideration as they prepare for this release. The Community will deliver their feedback to GS1 against the ‘draft’ technical solution. Feedback will be based upon review of documentation, pilot and Data Pool Certification activities. This information will result in modification to the draft standards for the final technical solution for ratification.

7. Reference Documents

BMS Modular Trade Item_01Feb2010

GS1 Modular Item Community Announcement 2010

GSMP Major Release Consolidated BRAD_May 2012

8. Acknowledgements

Team members can be found in the Roster of the GDSN User Group.


15

APPENDIX A: KEY TERM DEFINITIONS Attribute Value Pairs [AVP’s]:

An AVP is a simple flexible data structure allowing for the passing of an attribute name and corresponding value in an existing XML message.

XML Module Item:

Original intent was thin core set of attributes + all other attributes as Attribute Value Pairs [AVPs ] in class structures = flexible and highly modular trade item when put together based on ‘context’. This allowed for Trade Item data passed in the CIN that share a business association.

XML Modules:

Use same thin core item with XML Modules schemas. The XML Modules are a set of similar attributes that share a business purpose and can be assigned one or many GPCs (for example Ingredient Information for cheese). AVP’s can still be passed in the ‘core’ and in several selected XML Modules and classes.

This method employs XML Modules (Mini Extensions) that are selected for inclusion with the Core based on the GCP assigned to the GTIN.

Trade Item Validations:

Validations that are common across all products

Validations that are specific to the GPC of the trade item

Context Set (for current implementation)

A set of Modules (mandatory, optional & conditional), and/or validation rules based upon a specific process and product context.

Product Context

A grouping of GPC’s (segment, family, class or brick) that have similar properties (ingredients, nutrition, special labeling requirements). Examples of Product Contexts include Food, Beverage & Tobacco and Pet Food; Pharmaceuticals, Medical Device, Apparel and Accessories.

GDS MR Business Value - GS1 · 2014. 11. 28. · GDS Major Release Business Value 3 Date of Change...

Documents

Transcript of GDS MR Business Value - GS1 · 2014. 11. 28. · GDS Major Release Business Value 3 Date of Change...