CR 09-103 - Round 8 GDSN Data Validation Rules 510-512 514 519-522 Public Review, GDSN BRG

The Public Review for CR 09-103 Round 8 GDSN data validation rules 510-512 514 519-522  begins 3-Dec-2009 and ends 14-Jan-2010. 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 GDSN data validation rules 510-512 514 519-522 summary spreadsheet, and the Business Requirement Spreadsheet. Please make your comments by 4 PM ET on 14-Jan--2010 Close of Public Review. Simple Level of Impact 2.

Link to CR 09-103 Round 8 Public Review

CR 09-263 Public Review, GDSN BRG

The Public Review for CR 09-263 begins 3-Dec-2009 and ends 14-Jan-2010. Proposal: Change definition of "organismMaximumValue" attribute in the Food and Beverage extension: From: "Maximum allowable value of the microbiological organism." To: "Maximum allowable Colony Forming Units (CFU) of the microbiological organism per weight or volume."  This Public review contains a link to CR 09-263 in the CR system and the Business Requirement Spreadsheet. Please make your comments 4 PM ET on 14 Jan-2010 Close of Public Review. Simple Level of Impact 1.

Link to CR 09-263 Public Review

CR 09-060 GLN in Healthcare Implementation Guide Public Review

The GSMP Healthcare GLN Work Group has posted the GLN In Healthcare Implementation Guide for a 30 day public review. The review starts on December 1, 2009 and ends on December 30, 2009. This document serves as a general guide for the implementation of the Global Location Number (GLN) in healthcare.

Link to CR 09-060 Public Review

For GSMP/GDSN Business Requirements Group (BRG) members who are eligible to vote, the following eBallot has been posted in the GS1 Community Room:
 
09-178 eBallot, GDSN BRG

The eBallot for CR 09-178 begins Dec-2-2009 and ends Dec-16-2009. CR 09-178 Proposal:  CR 09-178 Add a repeatable attribute with a code list to indicate application identifier types within barcode on a trade item specifically for AI10, AI15 and AI17. This will be used to indicate that a trade item is marked with batch number in bar code format (AI10), that a trade item is marked with best-before date in bar code format (AI15) or expiration date in bar code format (AI17). To achieve efficient and safe automated goods receiving processes during distribution and to obtain high precision for traceability and recalls, best-before dates and batch numbers that are printed as bar codes on trade items are scanned and stored by retailer DCs. This information is used by warehouse and logistics management systems to monitor first-in/first-out principles and to enable recalls at batch or best-before date level. The different processes (manual vs automated) are used in different facilities  . Items requiring the manual process are received at different locations from those that do not. In order to distinguish between trade items that support an automated receiving process from trade items that do not, the nformation required in CR 09-178 is necessary.

This eBallot contains a link to CR 09-178 in the CR system and the Business Requirement Spreadsheet. Please cast your eBallot by 4 PM ET on 16 December 2009 Close of eBallot). Simple Level of Impact 2

Clarification Note from the submitter: Batch numbers are user for traceability and best-before-dates are used to manage FIFO (first-in first-out) in the retailers  distribution process. Some Swedish retailers have a high level of automation in the goods receiving process, and are constantly finding new ways to improve fficiency. To enable an automated goods receiving process that supports the level of traceability required and FIFO, machine readable data is necessary. (In some cases best-before dates and batch number linked to an SSCC and available from Despatch Advise messages). In cases when best-before-dates and bath numbers are not available in machine readable format or from Despatch Advise messages, a manual process is required to support the requirements for traceability and FIFO. The different processes (manual vs. automated) are used in different facilities. Items requiring the manual process are received at different locations from those that do not. In order to distinguish between trade items that supp  ort an automated receiving process from trade items that do not, the information required in CR 09-178 is necessary.

To vote on this ballot, go here:

http://community.gs1.org/apps/org/workgroup/gsmp_g_gdsn_brg/ballot.php?id=541

CR 09-242 Public Review, GDSN BRG

The Public review for CR 09-242 begins Nov-30-2009 and ends Jan-4-2010. Proposal: The trade item needs to have an optional measurement attribute to denote the cube of the trade item. Expected benefits: Current business practice utilizes this value to make determinations about items both from a purchase and transportation stand point. Definition- The dimensions of an imaginary cube which can be drawn around the trade item as defined in the formula of H X W X D (The linear dimensions multiplied to get a cubic result). This only applies to In-box dimensions. Applied to all levels of hierarchy

Example- Bag of Cabbage, Bag of Flour, Broom, Ham, Case of Beer. Rationale- A single point of calculation populated by the manufacturer which trading partners can use as a valid value throughout the supply chain.  Without a single value, trading partners might encounter issues with various ways of rounding on each side of the relationship.  Trading partners may round differently and thereby determine different values for cube and reduce data quality.  Best practices for data quality call for a single source of truth for all calculations. Irregular shaped items are measured as if they are in an imaginary "cube". 

Please make your comments by Jan-4-2009 (Close of Public Review) Simple Level of Impact = 2

Link to CR 09-242 Public Review

Save the date for the next GS1 Standards Development Event Spring 2010

The next GS1 Standards Development Event Spring 2010 is scheduled 19-23 April 2010 in Orlando, Florida, USA at the Marriott World Center Hotel. Watch for more details to be announced soon.

CR 08-219 Physical Location Identification and Visibility Master Data Attributes

BMS and General Specification Section 2.4 Revision Public Review, Physical Location Identification and Visibility Work Group, BarCodes and Identification BRG
 
The Public Review for 2 documents developed under CR 08-219  begins 19-Nov-2009 and ends 22-Dec-2009. The 2 documents make up draft standards for identification of physical location and visibility. The CR/WO was submitted under a request by the Architecture Group and is related to EPCglobal, BarCodes and Identification BRG, GDSN Enhanced Party Synchronisation and other GSMP groups. WO 08-219 is a Complex Work Order.

This Public Review contains a link to CR 08-219 in the Change Request System, the 2 documents that are draft standards and are for public review and a link to an in-progress document that the Work Group is drafting. This in-progress document may be used as background information, Please make your comments directly in the Community Room starting at 16:00 19 November 2009 ET (Princeton NJ) and ending on 16:00 ET (Princeton NJ) 22 December 2009 Close of Public Review.

Please use this link to the Public Review: Public review CR 08-219

CR 09-103 Round 7 GDSN Validation Rules 474 505 - 516 Public Review, GDSN BRG

The Public Review for CR 09-103 Round 7 VRs 474 505 - 509, 513 & 516  begins 19-Nov-2009 and ends 22-Dec-2009. 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 474 & 505 - 509, 513 & 516 summary spreadsheet  and the Business Requirement Spreadsheet. Please make your comments 4 PM ET on 22-December 2009 Close of Public Review. Simple Level of Impact 2:

Link to CR 09-103 Round 7 Public Review

GS1 Call-to-Action

This is a GS1 Call-to-Action to recruit users from all industries and from everywhere in the world to bring their expertise, commitment, and contribution to a new GS1 work area.   The effort is a GS1 project  set up in the context of GS1's efforts to improve collaboration and efficiency for trading partners; the results of this work are not considered a 'standard' (and therefore not a GSMP group) but rather will result in a series of recommendations and best practices for the benefit of the industry.

Objective/Scope of the GS1 Data Quality Work Group (DQ WG):

1.  Based on the feedback from the 'Data Quality Challenge' pilot of 2008-2009, this group will develop an updated set of data quality tools including:
     a) The Data Quality Framework version 3
     b) KPI and self-assessment scorecards (update scorecards)
     c) DQ Framework implementation guides (update guides)
2.  Validate and QC the following data quality materials developed by GS1:
     a) DQ e-learning training
     b) DQ Workshop

To learn more about this group and info on how to join it click the link provided to the Call to Action: GS1 Data Quality Work Group Call to Action

CR 09-232 Public Review, GDSN BRG

The Public review for CR 09-232 begins Nov-12-2009 and ends Dec-14-2009. Proposal: In GDSN Trade Item, for attributes storageHandlingHumidityMaximum and storageHandlingHumidityMinimum, the datatype 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. This Public Review contains a link to CR 09-232 in the CR system, and the Business Requirement Spreadsheet. Please make your comment by 4 PM ET on 14-December-2009 Close of Public Review. Simple LOI 3 for field change to percent; VR LOI TBD:

Link to CR 09-232 Public Review

GDSN Weekly Communication

The GDSN Validation Rules Sub-Team has received several proposals for new validation rules around dates. The sub-team agreed that a work group is needed around a complex CR for dates. The CR is needed to clarify each date attribute and its use. The reason is that the intended usage of the date attributes has been subject to interpretation.  The GDSN VR Sub-team discussed this with the GDSN BRG on 06 October and the BRG agreed on the need for clarification. Only after the CR is successfully resolved, the sub-team will resume crafting of the date validation rules and putting them into deployment. The date validation rules are now in the parking lot of the VR sub-team and will not be worked until the clarification is completed. Any community member interested in submitting a complex CR on this date topic should contact Melanie.kudela@gs1.org at GS1  for further information.