For those members of the Business Requirements Group who are eligible to vote, the following 3 eBallots are available:

CR 08-276 eBallot Add Calories & Kilocalories to UOM Code List

The eBallot for CR 08-276 begins Mar-4-2009 and endsMar-18-2009. Proposal: In the Food and Beverage Extension there is a UN_INFOODS code list and an existing attribute "nutrientTypeCode" to state calories and quantityContained for the value. We need to add Calories and Kilocalories to Unit of Measure Code List. Add values to the Unit of Measure Code List.

E14   kilocalorie (IT)

R4    calorie

Value for nutrientTypeCode would be: ENERC  energy, total metabolizable; calculated from the energy-producing food components  Unit: kJ.  The value may be expressed in kilocalories instead  of the default unit of kilojoules.  However, if expressed in kilocalories, kcal must be explicitly stated with the secondary tagname. Synonyms: kilojoules; kilocalories; Calories; food energy. Full Infoods code list is as follows:

http://www.fao.org/infoods/tags/part1.txt

This eBallot contains a Link to CR 08-276 in the CR system and the Business Requirement (See tab CR 08-276). Please cast your eBallot  4 PM ET Mar-18-2009 (Close of eBallot)  Simple Level 1

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

CR 08-281 eBallot Improve Food & Beverage Extension ways to ID Kosher organizations

The eBallot for CR 08-281 begins Mar-4-2009 and ends Mar-18-2009. Proposal:  The Food and Beverage extension limits the way certified Kosher organization can be identified.  Recommending that no code list  be used  (remove code list) and the field is open to identify the agency. DietTypesubcode would remain an open string with values governed by the chosen Diet Certification Agency. DietType will still remain a code list housed in the schema which will allow the user to say that the product is Kosher. So for example to express a type of Kosher you would say:

DietCertificationAgency = Organized Kashruth Laboratories DietType = KOSHER

DietTypeSubCode: Circle K

 ERIC Assessment NOTE: Simple level 3 since it is a data type change. Secondly, there is an existing requirement that is applicable to the same attribute from CR 07-406. I think Ritas approach is more flexible but there is no need to enter a new attribute for Agency as there is already dietCertificationAgency. We should change the dietTypeSubCodelist to be an open string. This way Dairy Pareve could be placed there according to Requirement 72028290 but it is open to provide the various kosher types that are available. This eBallot contains a Link to CR 08-281 in the CR system and the Business Requirement (See tab CR 08-281). Please cast your eballot by 4 PM ET Mar-18-2009 (Close of eballot)  Simple Level 3

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

CR 08-288 Add Weight Density to Food & Beverage Ext

The eBallot for CR 08-288 begins Mar-4-2009 and ends Mar-18-2009. Proposal: CR 08-288 Proposal Add weight Density to the PhysiochemicalCharacteristicCodeList  in the Food And Beverage Extension, Weight density:  Weight Density Equals the volume of 1 LB of Water divided by the Volume of 1 LB of the product. This Ratio allows conversion of a unit of volume or a unit of volume into a unit of weight. This eballot contains a Link to CR 08-288 in the CR system and the Business Requirement (See tab CR 08-288). Please cast your eballot by 4 PM ET Mar-18-2009 (Close of Public review)  Simple Level 1

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

GDSN Trade Item Implementation Guide (issue 9) The GDSN Trade Item Implementation Guide Work Group has released issue 9 of the GDSN Trade Item Implementation Guide - the definitive source on how to implement GDSN data. This new issue now contains the following revisions:  - Updated section 3.9 Item Futurisation  - Updated section 4.2. Fresh Foods  - Updated section 3.3.3.2 Populating TI/HI  

The GDSN Trade Item Implementation Guide is located on the GS1 website at:http://www.gs1.org/services/gsmp/kc/gdsn/index.html 

  Call-To-Action: Traceability in Healthcare II Work GroupThe Objective/Scope of the Traceability in Healthcare II Work Group is to develop a suite of Global Standards that enable Traceability in Healthcare (Process standard(s) and technical standards). The team will also develop supporting products such as guidance on enabling technologies and migration plans for all stakeholders.  

The Call-To-Action is available at: http://www.gs1.org/docs/gsmp/call_to_action/2009/CTA_Traceability_Healthcare_2_Feb_2009.pdf

  Call-To-Action: GDSN BRG Membership to work on Household Office Furnishings To help the Hardlines and Electronics Industries better achieve data synchronization, the Hardlines and Electronics Attribute Initiative (HEAI) was formed, and has made steady progress since its initial conference call on 7-Dec-06. This group was formed to look at product specific attributes that are not currently transmitted through the GDS Network, and to determine how we can define these attributes into a standard to enable passing of this data via the GDSN. This will enable more complete product data to be sent electronically without utilizing proprietary, non-standard methods of communication between trading partners, which ultimately will result in cost savings for all trading partners. Successful implementation will also increase adoption of the GDSN within the Hardlines and Consumer Electronics verticals. Attribute submissions have been received for the GPC bricks in the Household\Office Furniture family of GPC product codes. They have been harmonized and are ready for review. It is now our intention to begin reviewing, completing, and preparing for further processing these attributes at a physical meeting on 23-Mar-09 at the GSMP/JAG Meeting in Los Angeles, California. 

The Call-To-Action is available at: http://www.gs1.org/docs/gsmp/call_to_action/2009/CTA_Household_Office_Furnishings_Feb_2009.pdf

  Public Review: Global Traceability Standard for Healthcare (GTSH) Implementation GuideThe 30 Day Public Review for the Implementation Guideline related to the Global Traceability Standard for Healthcare (GTSH) starts 00:01 Central European Time (CET), Tuesday 24-Feb-2009 and ends 23:59 CET 24-Mar-2009 . The purpose of the Implementation Guideline "...is to assist any/all stakeholders in the global healthcare supply chain to implement a traceability system in line with the GS1 Global Traceability Standard for Healthcare (GTSH) utilising the GS1 System of standards." Please review this document and provide your comments. If you are a GS1 Member Organisation (MO) it is anticipated that, through your local Healthcare User Group, you will engage your local community in this public review.  

Please provide your comment via this link: http://community.gs1.org/apps/org/workgroup/gsmp_g_pr/documents.php?folder_id=4997#folder_4997

     Public Review:  Global Fruit & Vegetable Traceability Implementation Guide The 30 Day Public Review for the Implementation Guide related to work effort WO 08-20 starts 00:01 Eastern Standard Time (EST), Tuesday 24-Feb-09 and ends 23:59 EST 24-Mar-09. The Implementation Guide serves as a best practice guide to implementing traceability in the Fresh Fruit & Vegetable (Produce) Industry.  The best practices recommended are based on GS1 global standards for supply chain management and product identification.  These standards were developed by industry to optimize business practices across supply chains world-wide.   

Please provide your comment via this link. http://community.gs1.org/apps/org/workgroup/gsmp_g_pr/documents.php?folder_id=4998#folder_4998

  Public Review Extension: WO 09-031, GDSN BRGThe Public review for WO 09-031 begins 26-Feb-09 and ends 3-Apr-09, extended due to GSMP March LA CA USA physical meeting. Proposal: Add and alter the definition of the attached values to the Trade item External Information Code list. This Public review contains a Link to CR 09-031 in the CR system, a spreadsheet of attributes associated with CR 09-031, the Business Requirement (See tab CR 09-031). Please make your comments in the Business Requirement spreadsheet using the cRoom comment feature by 4 PM ET 3-Apr-09 (Close of Public review) - Simple Level 1  Please provide your comment via this link: Link to WO 09-031 Public Review

This Call to Action is for the "Traceability in Healthcare II Project" (TH-II).

The Work Team's Mission is "To develop a suite of GS1 Global Standards that enable Traceability in Healthcare.
A suite that comprises of the process and technical standards necessary to achieve end to end (raw materials
to patient care) global supply chain traceability (that is: track forward/downstream and trace backward/upstream).
The suite of process and technical standards will be the foundation for:
- ultimately achieving the GS1 Vision for Traceability in Healthcare
- through the incremental implementation of traceability systems that enable Patient Safety, Regulatory Compliance,

    Supply chain safety and integrity"

This Call-To-Action is located on the GSMP Website at: HC Traceability in Healthcare 

08-275 - Brand Name Language Requirement

Adds 2 new attributes to accommodate the brand name requirement for language. The existing Brand and Sub-brand attributes will remain strings in this proposal. This is to say that you cannot specify any language for the primary brand and sub-brands and that the assumption is that these are in the same language as all of the other single language data in the trade item. It is intended to implement these new attributes with the Multi-Description data type, with which a Language Code is always sent together with the text.

A.  Brand Name - Language Specific

        a.   Field Length = 70 characters

        b.   Allow multiple language iterations = >1

B.   Sub Brand Name - Language Specific

        a.   Field Length = 70 characters

        b.   Allow multiple language iterations = >1

NOTE:  Where a Brand name does not need to be multi-lingual, the existing Brand and Sub-brand attributes are to be used.

The GPC governance group is asking for information from trading partners that have either sucess stories to share or can provide insight into how they use the GPC classification in their internal systems.

Tpoics can include:

• How or if you use GPC in your internal systems

• As a supplier have you implemented GPC

• As a retailer, do you subscribe using GLN. If not,why

• As a retailer, do you use the GPC to route incoming messages

• What challenges do you have using or implementing GPC

They would like to have this input to use in presentations to be made during the GSMP event in Los Angeles, California next month.

If any of you can share one or two slides for me to provide the GPC group, it will be greatly appreciated. Better yet, if any of you will be attending the event and would like to present your own slides, that will be more impactful.

Thank you for your assistance and input!