GSMP Community Announcements
Public Review: GDSN Trade Item Implementation Guide: Populating TI/HI
The GDSN Item Implementation Guide Work Group is presenting an update to one of its topics: "Populating TI/HI". The original Trade Item Implementation Guide was delivered in January of 2007. The guide's objective is to supplement the formal GS1 GDSN standards with advice on their implementation and operation. It is in no way normative or definitive and is not a standard. It seeks to increase consistency and ease of implementation by explaining the standards and providing real-world examples. This public review is only for an update to the already existing "Populating TI/HI" topic.
It has been confirmed that the source data pools do not receive any notification that the GTIN is 48 months after its Discontinue Date. To support this we have modified section 3.4.3 and 3.4.4.1 (#9) of the "Populating TI/HI" topic where it is stated that the source data pool will automatically delete GTIN's after 48 months with a discontinued date. The modifications are highlighted in "Yellow". Once approved, it will be updated in the existing The GDSN Item Implementation Guide, which is located on the GS1 website at: http://www.gs1.org/gsmp/kc/gdsn.
All comments are due by no later than 26-Feb-2010.
Link to Public Review Populating TI/HI
Public Review: CR 09-103 Round 9 GDSN Validation Rules
The Public Review for CR 09-103 Round 9 VRs 513, 515, 524 - 530 begins 21-Jan-2010 and ends 20-Feb-2010. These are recommendations that today are codified in the GDSN Operations Manual and they are now being made official GDSN validation rules.
General Note: CR 09-103 consolidates under a single work-order change requests numbers 08-230, 08-245 and 08-249 submitted by GS1 Australia, GS1 Netherlands and GS1 Sweden. This Public review contains a link to CR 09-103 in the CR system, the VR 513, 515, 524 - 530 summary spreadsheet and the Business Requirement Spreadsheet.
Please make your comments 4 PM ET on 20 Feb-2010 Close of Public Review. Simple Level of Impact 2:
Link to CR 09-103 Round 9 Public Review
09-264 Public Review, GDSN BRG
The Public Review for CR 09-264 begins 21-Jan-2010 and ends 20-Feb-2010. Proposal: There is a need to enable data recipients in GDSN to calculate comparative price for a daily dose. To achieve this data sources must be able to indicate the price comparison content expressed as number of daily doses. A proposed solution is to add the following code value to PriceComparisonContentTypeList: PER_DAILY_DOSE - Specified using PCE as unit of measure (price per daily dose). This Public review contains a link to CR 09-264 in the CR system and the Business Requirement Spreadsheet.
Please make your comments 4 PM ET on 20 Feb-2010 Close of Public Review. Simple Level of Impact 2:
Link to CR 09-264 Public Review
GSMP Community Announcement
GS1 General Specifications
The GS1 General Specifications are the core standards document describing how barcodes and identification keys should be used to comply with GS1 AIDC Standards. As AIDC matures, it is still the means of automated identification and is expanding into more and more sectors such as in Healthcare and leveraging new technologies including GS1 DataBar™ to meet the growing needs of a data hungry world. In fact, more data being carried by new data carriers in new applications and sectors represents the true future of GS1 AIDC. It isn't just new technology; it's the use of additional data to solve business problems. This new version of the GS1 General Specifications is a step in that direction. To access the updated version of the General Specifications, please contact your local Member Organisation. You can find your local GS1 Office via this link: http://www.gs1.org/contact.
The important updates/additions to the GS1 General Specifications V10 include:
Global Healthcare AIDC Application Standards: A range of global AIDC application standards for Healthcare using the GS1 System Standards have been approved to set a common direction for all product types and package levels. The main focus is patient safety while being aware that improvement of supply chain management and performance will be achieved at the same time. In order to improve patient safety, our goal is to enable AIDC marking of healthcare products to allow every healthcare professional with the ability to gather the necessary information on the products in hand using one device (reader/scanner) per work station and utilize a common data set to automatically identify healthcare products from every corner of the globe. An example of this common data set includes the newly added Application Identifier for "Active Potency".
Application Standards for Small Medical and Surgical instruments: The addition of a small medical / surgical instruments specific marking standard for Healthcare using the GS1 System Standards is intended to set a common direction for direct marking of small medical / surgical instruments. These additions define practical AIDC based identification and direct part marking of small medical / surgical instruments for tracking & traceability through the instruments reprocessing cycle. GTIN Indicator Digits Rules: In the area of the use of Indicator Digits, there currently exist various translations / interpretations of the GS1 General Specifications that has led to divergent implementations, ultimately causing supply chain confusion. Updates to the GTIN Indicator Digits Rules, promoting a uniform and globally harmonized position, will encourage adoption that ensures patient safety and not patient risk due to over-labeling. This uniform position includes the clearly stated need for non-POS databases to be enabled to manage a 14 digit Global Trade Item Number (GTIN).
Expanding GS1 Standards for GS1 DataBar™: Retailers are now globally implementing =and/or piloting product identification using GS1 DataBar™. The new GS1 Standards provide the tools that enable additional GS1 Application Identifiers (weight, price, sell-by date, etc.) to be encoded and captured anywhere in the supply chain. Implementing GS1 DataBar™ will provide the data needed to solve business problems such as consumer safety and traceability programs, quality control and Point-Of-Sale processing. Use of GS1 Keys as a World Customs Organisation (WCO) Unique Consignment Reference (UCR): The World Customs Organisation (WCO) has published guidelines for the Unique Consignment Reference (UCR) that requires the sender (consignor) of goods to identify physical grouping of several transport or logistic units to be identified with a single UCR. This UCR is used by customs authorities to identify these groupings of transport units during the import or export processes. This makes the UCR an integral part of the customs declaration process which can be enabled with the GS1 Key; Global Shipment Identification Number (GSIN).
Reducing cost and enabling requirements of European Regulation: European Regulation (European Regulation No 275/2007) and customer requirements have been addressed regarding the labeling of beef and beef products. These changes enable the implementation of simplified beef labeling for representing multiple processing halls in one batch. This will simplify the operational procedures and reduce costs arising by the separate handling that currently takes place.
Additional Updates:
Increased capacity for Euro denominated Coupons: GS1 manages coupon issuer identification numbers and provides a common data structure for automatic coupon identification. In order to meet the continued demand, additional capacity has been allocated for coupons denominated with the Euro currency.
Clarification: GS1 is consistently looking for opportunities to improve our Standards and have made updates to ensure that the GS1 General Specifications continue to be the place to go for AIDC Standards.
Approved GSMP Change Request
CR 09-232 - Change 2 Humidity Attributes data type to percent
In GDSN Trade Item, for the attributes
"storageHandlingHumidityMaximum"
and
"storageHandlingHumidityMinimum",
the data type should be changed to percentage. Until this change is implemented in the GDS Network a temporary validation rule checking the same thing is needed. There is also a need for a rule that checks that the values are between 0 and 100, if possible in the schema, else as a non-temporary validation rule.
Call for Participation
Preliminary Trade Item
Preliminary Trade item is one of the GDSN Board approved projects for 2009-2010. The first teleconference to develop the business needs is scheduled for Thursday, January 28, 2010 at 0900 EST/1500 CET.
How To Apply ? Existing members of the GS1 Community Room can request membership in the group by clicking here: http://community.gs1.org/apps/org/workgroup/gdsnptig/
If you are not a GS1 Community Room member please apply for membership here: http://community.gs1.org/kmembership_info/person_signup?step%3Aint=2
If you need assistance joining please contact: mailto:alan.hyler@gs1.org
Below is the Call for Participation document.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
GDSN CALL FOR PARTICIPATION PACKET
1.0 Objective of this Call For Participation packet
The main purpose of this packet is:
To disseminate its contents to a broader GDSN community
To recruit a number of experts, which can bring their expertise, commitment, and contribution to the GSMP and the GDSN BCD Team
To provide input for Business Case Document (BCD) development
The information herein gives a general description of what the GDSN BCD Team will accomplish as well as its operation within the procedural framework.
2.0 Objective/Scope of the Preliminary Trade Item Data
Problem Description:
Suppliers are frequently asked to send item data to retailers before all data is available
There is currently no indication for data recipients to know when of if the item data is preliminary or final. Suppliers currently have to fulfil the expectation where data exchanged through GDSN is thought to be final item data
Retailers spend a lot of time and effort validating data that they think is final, when it is not
Suppliers receive notice if a product will be listed (or not listed) too late
Anticipated Business Benefits:
Improved efficiency for introductions of new items (shorter lead times for introductions)
Less corrections of Item Data for active trade items (less time and effort spent on retailers and suppliers disagreeing whether data was final or not)
Allows early publication of basic data (all mandatory attributes populated) and possible later addition of additional information (variant, colour, deposit, catalogue price, extensions…
May allow earlier listing notice to suppliers
Defining Business requirements around "Preliminary Data":
Create functionality enabling information providers to indicate that the Item Data has its final attribute values or if the information provider intends to correct or add values later
Determine which existing attributes can be different between the stages of preliminary to final and therefore affected by the new functionality
Determine how for the existing attributes one can recognize a preliminary value
Determine until which date item data can be preliminary (eg. Before first shipment (startAvaliabilityDate / firstOrderDate / firstShipDate) Item must be updated to final version)
Create, if necessary/possible, a Work Order (GSMP) for validation rules to enforce correct usage
Deliver a Trade Item Implementation Guide Chapter how to use the new attribute plus the affected existing fields
The attributes GTIN, GLN, TM and GPC cannot be subjected to the new attribute. Determine how to update the item data, possible differences to current processes (CORRECT vs. CHANGE_BY_REFRESH)
Rules have to be defined for what happens if ‘preliminary’ data is sent to recipients that do not (want to) use this feature
3.0 Scope Constraints of the Preliminary Trade Item Data Group
GDSN BCD Teams must adhere to the GDSN User Group Methodology to assure their scope and deliverables, upon which the work of other GSMP groups depends.
Generally, the team must operate within the following context:
Develop a Business Case Document (BCD) that captures the business need in order to create a work order as well as incorporate additional considerations that were discussed during the team’s calls and physical meetings.
Project scope will be finalized during the BCD work group.
4.0 Expertise Required:
This is a call for business information and business information technology experts in the Data Synchronisation Process. The participants should represent manufacturers, material suppliers, third parties, and solution providers to have proper representation on the Project Team. The intent is to have balanced participation from the GDSN user community to define and establish proper global standards with the clear intention of implementation of these.
5.0 Distribution for Call for Participation:
Please distribute this Preliminary Trade Item Data ‘Call for Participation’ packet by forwarding it to your email distribution lists. GDSN Project Teams are open to broad participation from any industry group, company, or region.
It will also be distributed via a GDSN Community email announcement.
6.0 Timeline:
Kick off/introductory conference call to fully brief all participants of objectives and working team activities. The first call will be held on 28 January 2010 from 0900 – 1000 EST/ 1500 – 1600 CET. The approximate duration of this BCD team effort is expected to be approximately 4 months, the entire project, including deployment into the network could take over 12 months.
7.0 Known participants:
Preliminary Data GDSN Project Team BCD Manager: Alan Hyler, GDSN Inc.
Participants known by January 14th 2010:
Staffan Olsson, GS1 Sweden (chair)
Daniëlle Hoekstra, GS1 Netherlands (co-chair)
Martina Appehl, ICA
Gina Tomasi, Pepsi
Hanjoerg Lerch, Metro
Steve Robba, J&J
Jay Yanko, BigHammer
Milan Vacval, Gladson Interactive
Grant Kille, SA2 Worldsync
8.0 Responsibilities
The GDSN BCD Team will work co-operate with the GSMP/GDSN BRG, GDSN Advisory and User Groups.
The GDSN BCD Teams responsibilities are to ensure Preliminary Data business requirements can meet minimum requirements for a GSMP Change Request.
Other responsibilities are reusability, consistency and integrity of the standards.
9.0 Sessions
The GDSN BCD Team is responsible for scheduling meetings to accomplish their work. Sessions are defined as face-to-face or physical meetings, and teleconferences. All GSMP Sessions include the necessary Anti-Trust cautions as defined by GS1 legal counsel.
9.1 Face-to-Face Meetings
If necessary, the BCD Manager and Project Co-chairs schedule face-to-face meetings with reasonable advance notice to allow for proper planning. Face-to-face meetings will cover 1 to 3 days for one meeting in order to speed up the work as much as possible. Participants are expected to cover their own expenses related to travel, accommodation, and time for the physical meetings.
9.2 Teleconferences
Preliminary Data GDSN Project Team teleconferences will occur on the 2nd and 4th Thursday of every month. Please CALL FOR PARTICIPATION PACKET – Preliminary Trade Item Data GDSN Project Team 4 of 4
9.3 Agendas and Minutes
GS1 Community room facilities will be used to support the work of this GDSN Project Team. The BCD Manager and co-chairs prepare agendas.
Standing agendas should include:
Review of the Anti Trust Caution
Review of the agenda.
Approval of previous meeting or call notes.
Discussion of all pending issues and action items.
All meetings or teleconference notes should record:
The original agenda
Attendees
Requests for notation
Decisions/Resolutions taken
Action items
10. How To Apply ?
Existing members of the GS1 Community Room can request membership in the group by clicking here: http://community.gs1.org/apps/org/workgroup/gdsnptig/
If you are not a GS1 Community Room member please apply for membership here: http://community.gs1.org/kmembership_info/person_signup?step%3Aint=2
If you need assistance joining please contact: mailto:alan.hyler@gs1.org