| « Approved GSMP Change Requests | New e-Ballots for GSMP Change Requests » |
GSMP Community Announcements
Public Review: WO 08-000073, BarCodes & ID BRG
The GSCN for WO 08-000073 "AI(401) and AI(402)" is posted for public review. The BRAD for WO 08-000073 is posted as a reference for reviewers. The Public Review Period opens 18-Nov-2008 and closes 16-Dec-2008. Background: In the latest version of the General Specifications AI 401 and AI 402 are classified as GS1 keys, however this fact is not reflected in all parts of the General Specifications. A name change is request to align these keys with the GS1 naming convention. The world customs organisation (WCO) has published guidelines for the unique consignment reference (UCR) in 2004. These guidelines require 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 when undergoing import or export processes. The UCR is an integral part of the customs declaration messages. AI 402 can fulfill the requirement of the WCO, however the definition needs slightly been enhanced.
Please use the following link for this Public Review: Link to WO 08-000073 Public Review
Public Review: WO 08-000258, GDSN BRG
The Public review for WO 08-000258 begins 20-Nov-2008 and ends 22-Dec-2008 extended due to two USA Holidays in Nov. Proposal: Add a value to the Additional Classification Agency name attribute for the product classification system maintained by GS1 Italy. Inclusion of the GS1 Italy classification is needed to support the implementation of retailers and suppliers and their migration into the Global Data Synchronization Network. Retailers will be unable to perform machine to machine item setup if the GS1 Italy product classification is not communicated within the network. GS1 Italy maintains a product classification system that is required within their country for item setup by retailers. This classification system is a current need within the country. This Public review contains a Link to WO 08-000258 in the WO system and the Business Requirement (See tab WO 08-000258). Please make your comments in the Business Requirement spreadsheet using the Community Room comment feature by 22-Dec-2008 at 4 PM ET (Close of Public Review).
Please use the following link for this Public Review: Link to WO 08-000258 Public Review
Public Review: WO 07-000332, GDSN Enhanced Party Synchronisation Work Group
The 30 Day Public Review for WO 07-000332 has begun. The Business Requirements Analysis Document (BRAD) for phase 1 of synchronization of party information in GDSN is now in review. This Public Review contains the link to WO 07-000332 and the BRAD under review. Please review and make any comments by 4 PM ET on 22-Dec-2008 (Close of Public Review). Please use the following link for this Public Review: Link WO 07-000332 Public Review
Call-To-Action: GS1 Physical Location Identification and Definition for Visibility Data Work Group
This workgroup will define business requirements around standardizing Physical Location Identification and Definition for Visibility Data. Please use the following link to access the Call-to-Action: access here
Call-To-Action: GDSN Enhanced Party Synchronisation Implementation Work Group
This workgroup will define business implementation guidelines for GDSN Enhanced Party Synchronisation.
Please use the following link to access the Call-to-Action: access here
1 comment
Gina,
The Business Requirements Document (BRD) ohase of the project is out for public review at this time. The next phase will be to review the draft Business Message Solution, tentatively planned to be available early February. The BRD documentation represents only the changes to be made to a previously approved, but never implemented, standard published 3 or 4 years ago.
Suffice it to say the proposed solution will make Party Synchronization look and act basically like item Synchronization. It will have a pub/sub functionality, however the confoirmation message will be deferred until a future phase. That also means the sycnhronization list processing will be simpler for data pools, at least intially.
Implementation is not likely to occur before 2010. This functionality will be mandatory for all data pools in the GDSN, but of course optional for Trading Partners. Mandatory functionality also requires a certificatiion event. Currently, GDSN funding only allows for one implementaion of standards updates per year. For this fiscal year that implementation will be the Maintenance Release in March, 2009. in addition, no funding has been made available for any kind of major certificatio nevent for the network.
Discussions are underway with GDSN Inc., the GDSN Architecture Committee, and ultimately the GDSN Inc. Board to make a final determination about the deployment of Party Synch. Other factors include potential Maintenance Release 4 in early 2010 (which may really be a major BMS 3.0 release) and consideration given to the initial implementation of Modular Item. As these events unfold, i will keep you posted via the BLOG.
Comment feed for this post