TRANSPORTATION SUBCOMMITTEE (X12-I) MOTOR TASK GROUP (TG03) January 25, 2016 Meeting Minutes

Transcription

1 TRANSPORTATION SUBCOMMITTEE (X12-I) MOTOR TASK GROUP (TG03) January 25, 2016 Meeting Minutes I. Introductions Meeting was called to order with 7 members in attendance. Attendance was taken using the X12 Inc. automated reporting system and recorded by the organization. II. Approval of minutes of last meeting Minutes of the September meeting were approved as submitted. III. Update on GS1 Activities Mr. Birkle provided an update on GS1 activities. A copy of the update is included as ATTACHMENT 1 to these minutes. IV. CICA Update Ms. Morton advised that TG1 will meet at 1:30 pm local time on 25 Jan 16. No database under the updated CICA design rules using the new data base structure is available for this meeting. Based on CICA development history being primarily driven by X12I-TG4 (Marine) a discussion will be held regarding passing all CICA development effort to that task group and disbanding X12I-TG1 (XML). V. Review of maintenance and new projects The task group reviewed 25 referred data maintenance items, the final disposition was: 18 deferred or referred to other task groups; 5 approved; 1 approved as modified; 0 disapproved; 1 withdrawn interest. A summary of the individual data maintenance disposition is included in ATTACHMENT 2 to the minutes. VI. Outstanding issues and new business No outstanding issues or new business was brought forward by the task group. VII. Future Task Group scheduling Next meeting: June 2016, virtual meeting, exact dates will be announced closer to the meeting date.

2 ATTACHMENT 1 GS1 Activities Report GS1 Standards Event - April 2016 in Jersey City Hosted by GS1 US, the event will be held in Jersey City, NJ, at the Hyatt Regency Jersey City on the Hudson River. The GS1 Global Standards Event is a 5-day event that provides work groups a face-to-face opportunity to accelerate development of the GS1 System of standards and guidelines, collaborate with industry partners and discover innovative business solutions. NEW Publication: GS1 General Specifications version 16 The 16th version of the GS1 General Specification is now live on the standards area of the GS1 website. The GS1 General Specifications is the foundational GS1 standard that defines how identification keys, data attributes and barcodes must be used in business applications. New in this edition are updates to address work requests from the user community, revised wording in association with new GLN Allocation Rules, introduction of the new GS1 branding, etc. elearn: Intro to GSMP Intro to GSMP elearn is available. This 15 minute elearn has greater emphasis on the entrance criteria and the other process improvements which help drive: GS1 work on standards relevant to industry An efficient process Broad industry participation Participation Access the working groups webpage for a list of all active groups in standards development. Group descriptions are provided with links to help you join them. If you would like assistance or just have questions about participation, contact Edward.Merrill@gs1.org. Core Business Vocabulary v1.2 Phase 1 Draft Standard for PUBLIC Review CBV 1.2 is fully backward compatible with CBV 1.1 and 1.0. CBV 1.2 includes these new or enhanced features: A new standard vocabulary for EPCIS error declaration reason identifiers is added. The URI structure for EPCIS event identifiers is specified. This is a public review DRAFT; see below. Public Review DRAFT Notice This version of the CBV1.2 standard is a DRAFT for public review. It is a draft document and may be updated, replaced or made obsolete by other documents at any time. It is inappropriate

3 to use GSMP working Drafts as reference material or to cite them as other than work in progress. This is work in progress and does not imply endorsement by the GS1 membership. EPCIS v1.2 Phase 1 Draft Standard for PUBLIC Review EPCIS 1.2 includes these new or enhanced features: A mechanism is introduced to declare that a prior EPCIS event is in error, for use when it is impossible to correct the historical trace by means of ordinary EPCIS events. This mechanism includes the errordeclaration structure in an EPCIS event and associated query parameters.an optional eventid is added to all EPCIS events. Its main intended use is to allow for an error declaration event to (optionally) refer to one or more corrective events. Public Review Link / 8 January - 8 February 2016 Public Review DRAFT Notice This version of the EPCIS 1.2 standard is a DRAFT for public review. It is a draft document and may be updated, replaced or made obsolete by other documents at any time. It is inappropriate to use GSMP working Drafts as reference material or to cite them as other than work in progress. This is work in progress and does not imply endorsement by the GS1 membership. Community Reviews EDI : EDI SMG XML Business Requirement Extend existing standard code list of CopyElementsTypes with a few additional domain-specific types. Extend application domain of the message standard to applications in pharmaceutical packaging : EDI SMG XML Business Requirement Make GS1 Identification Keys optional in GS1 EDI XML. Misalignment on mandatory GS1 keys between GS1 EDI XML (mandatory except GLN) and GS1 EANCOM (not mandatory), EPC IS (not mandatory) makes it very difficult for companies that use multiple standards (which is the case for most international companies). It also makes it difficult to switch from older technology to newer XML based messages. GS1 identification keys originate from the retailer (downstream) supply chain where it took years to implement these. In relative new areas of the supply chain for GS1 like upstream (material suppliers) and transport (Logistics Services Providers) it takes time and at the moment unnecessary delay of implementation speed to have these keys used with these partners. Companies can have a mix of commercial and non-commercial products where non-commercial products will not be identified by a GTIN (typically spare parts and tools). To not mandate these identification keys makes the GS1 message more attractive to use for new companies in electronic messaging and will help them on their journey to introduce GS1 keys. If companies see the benefits of using these key that will come over time anyway and anyhow : EDI SMG XML Business Requirement Add a code to identify the 2-men-delivery. The transportation of big and heavy articles, e. g. washing machines, need special logistic service information. For this reason it is important to identify the 2-men-delivery in a transportinstructionmessage.

4 GLN Allocation Rules Update : GLN Allocation Rule Updates MSWG - Guideline The work group has developed scenario-based implementation guidelines, which will complement the updated GLN Allocation Rules. These scenarios are based on real-world challenges encountered by GS1 member companies participating in this work group or represented by one or more GS1 member organisations. We encourage all community members to review the proposed guideline materials and participate in this community review. Global Master Data (GMD) : Change definition of BASE_UNIT_OR_EACH & Harmonize the table for the Trade Item Unit Descriptor documentation in BMS and TIIG. Remove the incorrect table from the BMS. Risk: Different implementation in data pools and solution provider systems : There is a need to provide a measurement precision for the content of a trade item's ingredient. See within Community Review for more details : Issue on the Major Release 3.1 data migration of PackagingTypeCode as proposed by GS1 Global Office. See within Community Review for more details : Incorrect definition causing people to try and create validation. See within Community Review for more details : We would like to add following codes into PackagingMarkedLabelAccreditationCode: BIO_CZECH_LABEL, KLASA, REGIONAL_FOOD_CZECH,ECO_LABEL_CZECH. Details on those codes including definitions are available in attached Excel template : Add the UN Rec. 20 code "MTS" to the GDSN code list MeasurementUnitCode. MTS is metre per second : Add a code for the attribute referencedfiletypecode to represent "QR" codes. See within Community Review for more details. New : There is a need to update the packaging recycling scheme codes to be more inclusive of the codes which can be found on the packaging. See within Community Review for more details : There needs to be the ability to specify a descriptive term to represent the deposit information for a piece of packaging when an actual amount is not required. Global Master Data (GMD) SMG Product Image Specification

5 15-305: GMD SMG Add a statement in Product Image Specification to provide a naming convention for documents, video, and audio files. See within eballot for more details. Proposed solution: see pg. 11 in Product_Image_Specification_i2 8_r_ _DC.docx Global Product Classification (GPC) : Chocolate-Sugar Combinations Additions/modifications of GPC Bricks to support Chocolate-Sugar Combinations : Intended Use of Sauces Additions/modifications of GPC Bricks to support Intended Use of Sauces Community eballots Global Master Data New Add: Ø-mærket <- The red Ø-mærke with the text "Statskontrolleret økologisk", tells that the Danish authorities have been controlling the farm or the company which have processed, packed or marked an organic product. See within eballot for more details. New Minor definition change consumersalesconditioncode A code depicting restrictions imposed on the Trade Item regarding how it can be sold to the consumer for example Prescription Required. Change to A code depicting restrictions imposed on the Trade Item regarding how it can be sold to the consumer for example Age restrictions, selling restrictions. See within eballot for more details. New Change definition of ingredientsequence attribute was changed from integer to String and definition does not match any longer. See within eballot for more details. Events Board Committee for Standards Meeting (BCS) at the Global Forum February 2016 (08:45 am - 11:45 am) Brussels, Belgium GS1 Global Standards Event Spring April 2016 Jersey City, NJ, USA GS1 Industry and Standards Event October 2016 Brussels, Belgium

6 ATTACHMENT 2 Referred DM Disposition SEGMENT Previous TG3 TG3 DM # OR D.E. SETS DESCRIPTION OF CHANGES C, F, G, I, M, N Place holder for discussion of codes and versioning requirements Defer Defer C, F, G, I, N Creates new CICA template and documents LOGISTICS SERVICE REQUEST and LOGISTICS SERVICE RESPONSE C, I, J, N Add loop ID uniqueness to X12.6 and Design Rules and Guidelines C, I, N Update X12.7 to provide a mechanism to allow an instance document to specify default values for Supplementary Components. If a construct has its Supplementary Component set, this value will be used rather than the document's default value for that Supplementary Component C, F, I, M, N Changes to X12.5 to add new features -Ability to specify character coding -Ability to specify a release character Additional Additional -Other changes like new interchange envelope Project Proposal: Create new guideline: IMIF Implementation Metadata Interchange Format

7 SEGMENT Previous TG3 TG3 DM # OR D.E. SETS DESCRIPTION OF CHANGES Project Proposal: Create new guideline: RMIF Record Metadata Interchange Format Project Proposal: Create new guideline: MMIF Mapping Metadata Interchange Format Ability to send sender and receiver IDs, as well as qualifiers, as part of XML data stream Mult 418 Changes to 418 to allow delivering interchange carrier to provide train inspection information Defer Defer Revise Transportation Status - General Use document to meet the X12.7 rules Revise Transportation Status -General use Request document to meet the X12.7 rules Revise Transportation Status - Small Package Use Document the X12.7 rules Create a standard Implementation Guide (IG) for client implementations for 820s on version Changes X12.6 design rules regarding leading zeroes

8 SEGMENT Previous TG3 TG3 DM # OR D.E. SETS DESCRIPTION OF CHANGES MS1 838 Add segment MS1 to the N1 loop between the N4 at position 0900 and the N9 at position 1000, optional, max use 1. Add transaction set note at assigned position: The MS1 segment is used to pass the latitude and longitude of the party identified in the N1 loop. Also add another MS1 segment to the LCD loop between the N4 at position 1750 and the DMG at position 1770, optional, max use 1. Add transaction set note at the assigned position: The MS1 segment is used to pass the latitude and longitude of the place/location identified in the LCD loop. C Request of Mexican Customs to identify Mexican taxpayer code for consignee Refer to TG9 Refer to TG MS1 PPA Adds data element(s) to segments MS1 and PPA. Adds note(s) to segments MS1 and PPA. Changes note(s) in segments MS1 and PPA. Creates simple data elements 1794 and Changes purpose of simple data elements 1654 and Changes maximum of simple data elements 1654 and Changes "source" of code source 559. Adds reference(s) to code source Changes X12.5 and X12.6 for use of code values across standard versions Approve as modified removing the work accepts Approve as modified removing the work accepts Changes to Acknowledgement Reference Model

9 SEGMENT Previous TG3 TG3 DM # OR D.E. SETS DESCRIPTION OF CHANGES Changes to X12.6 for terms (Shall, Must) clarification of what is the document clarification of what is the document Removes references to the term DISA from X12 documentation , 999 Add a new code to data element 716 Code value: 33 - Invalid Version/Release/Industry Identifier Code Add a new code to data element I18 Code value: Invalid Version/Release/Industry Identifier Code New transaction to support greatly enhanced product information that support master product data and data synchronization processes Code Source 17, 21 Update CS17 (SCAC) and CS21 (SPLC) with current information provided by the National Motor Freight Tariff Association (NMFTA) Withdraw Interest