ATIS 0300006-2018 Implementation Guide for Package Labeling.pdf

1、 ATIS-0300006 ATIS Standard on - Implementation Guide for Package Labeling As a leading technology and solutions development organization, the Alliance for Telecommunications Industry Solutions (ATIS) brings together the top global ICT companies to advance the industrys most pressing business priori

2、ties. ATIS nearly 200 member companies are currently working to address the All-IP transition, 5G, network functions virtualization, big data analytics, cloud services, device solutions, emergency services, M2M, cyber security, network evolution, quality of service, billing support, operations, and

3、much more. These priorities follow a fast-track development lifecycle from design and innovation through standards, specifications, requirements, business use cases, software toolkits, open source solutions, and interoperability testing. ATIS is accredited by the American National Standards Institut

4、e (ANSI). The organization is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a founding Partner of the oneM2M global initiative, a member of the International Telecommunication Union (ITU), as well as a member of the Inter-American Telecommunication Comm

5、ission (CITEL). For more information, visit www.atis.org. Notice of Disclaimer Phone: +32 2.788.7800 Fax : +32 2.788.7899, E-mail: infogs1.org, Web Site: http:/www.gs1.org. ATIS-0300006 3 ISO/IEC 15459-2, Information Technology Automatic Identification and Data Capture Techniques Unique Identificati

6、on Part 2: Registration procedures1 ISO/IEC 15459-3, Information Technology Automatic Identification and Data Capture Techniques Unique Identification Part 3: Common rules1 ISO/IEC 15459-4, Information Technology Automatic Identification and Data Capture Techniques Unique Identification Part 4: Indi

7、vidual Products and Product Packages1 ISO/IEC 16023, Information technology - International symbology specification - MaxiCode1 ISO/IEC 16388, Information technology - Automatic identification and data capture techniques - Code 39 bar code symbology specification1 ISO/IEC 19762-2, Information techno

8、logy - Automatic identification and data capture (AIDC) techniques - Harmonized vocabulary - Part 2: Optically readable media (ORM)1 1.3 Related References GR-485-CORE, COMMON LANGUAGE Equipment Codes (CLEI Codes) -Generic Requirements for Processes and Guidelines11 1.4 Introduction to Labels 1.4.1

9、Product Package Label The purpose of the PRODUCT PACKAGE LABEL is to provide a standard format for describing the contents of a given unit pack with respect to product identification number, quantity, and any optional information as further identified in the following sections. The label can also se

10、rve as a system interface between trading partners by providing, in a machine readable format, the descriptive information required for system updating. This labeling is normally performed at the lowest level of packaging. Some examples of Product Package labels are shown in Figure 1. 11 Available f

11、rom Common Language Customer Service, 444 Hoes Lane, Piscataway, NJ 08854. Telephone: +1 732.699.5577, Web site: http:/. Email: . ATIS-0300006 4 Figure 1 Product Package Labels (Not to Scale) 1.4.2 Shipping/Receiving Transaction Label The SHIPPING/RECEIVING TRANSACTION LABEL is primarily a vehicle t

12、o automate the delivery of customer order information (purchase order number, quantity, product identification, package identification, etc.) from the supplier of a product to the receiver. Whereas the PRODUCT PACKAGE LABEL provides information about the contents of a package that is usually order i

13、ndependent, the SHIPPING/RECEIVING TRANSACTION LABEL provides information about the customers order. As with the PRODUCT PACKAGE LABEL, the SHIPPING/RECEIVING TRANSACTION LABEL can also serve as a system interface by providing the information in a standard machine readable format. Some examples of S

14、hipping/Receiving Transaction labels are shown in Figures 2, 3, 4 and 5. C OU NT R Y OF OR I GI N ( 4L ) (01) 50098756100018 QUAN T I T Y ( 7Q) 1 2 3 4 PC US E A N. UC C - 14 4 L US 0 1 5 0 0 9 8 7 5 6 1 0 0 0 1 8 7 Q1 2 3 4 P C ATIS-0300006 5 Figure 2 Shipping/Receiving Transaction Label with DIs A

15、TIS-0300006 6 Figure 3 Shipping/Receiving Transaction Label with DIs and 2D symbols encoding data on the label ATIS-0300006 7 Previous versions of this document required the use of five different types of SHIPPING/RECEIVING TRANSACTION LABELS, referred to as 3S, 4S, 5S, 6S, and 7S. These are describ

16、ed in Appendix A. This methodology has been replaced by the use of labels that utilize a unique package identification code (license plate) that complies with the ISO 15394 formats shown in this section. The data encoded in the PDF417 symbol is all the data in linear bar codes on the label. The segm

17、ent explanations are as follows: Header )RS Data Format “06” Format Header 06GS Ship From Name 3LGOOD SUPPLIER GS Ship From Street Address 3LANY STREET GS Ship From City, State, and Postal Code12 3LANY CITY, ANY STATE, POSTAL CODE GS Ship To Name 2LGOOD CUSTOMER GS Ship To Street Address 2LANY ROAD

18、GS Ship To City, State, and Postal Code13 2LANY CITY, ANY STATE, POSTAL CODE GS Shipment ID 2S480546160GS Transport unit ID (Container License Plate) JUN0433257110000001GS Carrier Shipment Number 3K9631415926535984147098GS Customer PO # and Line Item # 14K505054+001GS Supplier Product ID 1P0987656GS

19、 Quantity (Each) Q500GS Customer Product ID P098756100013GS Country of Origin 4LUSGS Lot / Batch Number 1TMJH110780GS Carton “n of x” 13Q1/3GS Shipment Weight 2Q263.2LBGS Shipment Volume 3Q1.65CY Trailer RSEOT 12If the postal code is required for specific business processes, add the appropriate data

20、 identifier per ANS MH10.8.2 (e.g. 51L, 52L, 54L, or 55L). 13 If the postal code is required for specific business processes, add the appropriate data identifier per ANS MH10.8.2 (e.g. 51L, 52L, 54L, or 55L). ATIS-0300006 8 Figure 4 Shipping label using 2D Symbol with EDI 856 Data The following Ship

21、 Notice manifest EDI transaction 856 contains data which is encoded in the PDF417 symbol. The actual data encoded in the PDF417 symbol is found below this EDI transaction 856 data: Transmission Header ISA*00*bbbbbbbbbb*00*bbbbbbbbbb*16*0433257110000bb*16*0118504840000bb*920926*1705*U*00302*000002327

22、*0*T CR Functional Group Header GS*SH*0433257110000bb*0118504840000bb*920926*1045*145*X*003020 CR Transaction Header ST*856*579333453 CR Beginning Segment BSN*00*MH80312*920223*1442*0001 CR Hierarchical Level HL*1*S CR Carrier Details (Qty/Wt) 1.4.2.1.1 TD1*PLT94*36*G*220*KG CR ATIS-0300006 9 Carrie

23、r Details (Routing) TD5*2*SCAC*AE*CC*WD*2 CR Carrier Details (Spc Hnd) TD4*AMM CR Carrier Tracking Number REF*AW*3115387693 CR Ship Date DTM*017*921012*0800*GM*19 CR Ship To Co. owner code, serial number, and reel size code. As cable is manufactured, it is wound onto reels, each of which has been id

24、entified with an ATIS CABLE REEL ID LABEL. The CABLE REEL ID LABEL is scanned and entered into the manufacturers computer system with the cable type and cable length. This Cable Reel ID provides the manufacturer a key to the computer data bases for tracking the cable inventory and tracking the cable

25、 reel itself. As cable picking requests are sent to the manufacturers cable storage area, the order picker can scan the CABLE REEL ID LABEL, using a scanner. The scanned information is used by the manufacturers computer system to match against the inventory files to ensure the correct cable type and

26、 length is being pulled from storage and shipped. This information can also be used for the mechanized preparation of shipping documents, EDI ASN, and/or the tracking of reels for asset control purposes. The Cable Reel ID can be utilized by the cable purchaser to track the cable reels from the time

27、they are received, and moved to various transfer points, including company or customer locations, until the empty cable reels are returned to the cable providers. Additionally, the scanned data can be entered into a database allowing a computer system to associate the type and amount of cable on a s

28、pecific reel. The reels may be owned by the cable provider or by the company purchasing the cable. This system can track the incoming cable reels and decrement the cable balance on a reel A B 1 2 3 4 5 6 X Y Z( 1B ) R E E L ID - D O N O T R E M O V E1 B A B 1 2 3 4 5 6 XY ZATIS-0300006 13 by reel ba

29、sis as cable cuts are made. If cable is removed from a cable providers reel and transferred to a company owned reel the computer system can be utilized to track these transfers. This system can greatly facilitate the return of empty cable reels to minimize charges imposed by the cable provider when

30、specific cable reels are not returned within a specified time frame. 1.4.4.4 Packing List A packing list document may accompany a shipment in order to provide a paper copy listing the ordered products, their quantity, serial numbers, country of origin, and how they are packaged within the shipment.

31、It may also include a two dimensional symbol that contains portions of the associated Ship Notice Manifest data (EDI transaction set 85614) that can be used to receive the shipment and further automate the receiving process. The paper packing list document could become unnecessary in the future as e

32、lectronic commerce between trading partners becomes dependent on the package identification data field of the shipping label. However, the paper packing list may continue to be required for customs usage.15 1.4.5 Benefits The following are some of the benefits that can be gained through the use of t

33、he PRODUCT PACKAGE LABEL, the SHIPPING/RECEIVING TRANSACTION LABEL, and the CABLE REEL ID LABEL. The degree to which each of these benefits is realized is dependent on the application and the commitment of the organization implementing the labeling process. 1.4.5.1 Producers of Labels Standard label

34、 dimensions help reduce inventories of label stock previously required for different customers. Standard label format makes computer programming easier. The ability to produce these labels can attract customers wanting to use them in their receiving applications. Greater mechanization and accuracy i

35、n a customers receiving process can result in a reduction in disputed shipment data and in accelerated payment. Producing standard labels for customers reduces training of packing/shipping employees and makes procedures easier to monitor and to maintain. Standard machine readable symbol labels can b

36、e used to mechanize the consolidation of shipment data for the computer system and the creation of bills of lading/packing slips/Ship Notice Manifest. The use of standard label formats can provide a platform for further partnering using EDI technology. 1.4.5.2 Recipients of Labels Using automatic da

37、ta capture methods to scan the data on standard label formats provides the opportunity for greater efficiency and accuracy through mechanization of the receiving and/or put-away process. The standard format of the label can help to reduce training of receiving and put-away personnel. The use of stan

38、dardized machine readable labels can eliminate the need to re-identify (re-label) material for storage. Standardized machine readable labels can be used to mechanize the inventory control (cycle counting) process by providing a machine readable identification of product and quantity. 14 See ANSI ASC

39、 X12 (available at www.X12.org) or UN/EDIFACT (see http:/repository.edifice.org/migs/desadv.aspx) for additional information on EDI transaction sets. 15 For the cable reel manifest, see ATIS-0300045. ATIS-0300006 14 The use of standardized machine readable labels can provide a platform for further p

40、artnering using EDI technology. 2 Implementation Procedures for Labeling The following describes the procedures involved in establishing a trading partner relationship using the PRODUCT PACKAGE LABEL, the SHIPPING/RECEIVING TRANSACTION LABEL, and/or the CABLE REEL ID LABEL. These procedures are not

41、intended to be absolute in either content or sequence. Specific situations and requirements may warrant changes to this process. 2.1 Determining The Need For Machine Readable Labeling Many times, the need to generate or to receive the machine readable symbol PRODUCT PACKAGE LABEL, the SHIPPING/RECEI

42、VING TRANSACTION LABEL, and/or the CABLE REEL ID LABEL originates from customer requirements or as a request from suppliers attempting to standardize their labeling process. In addressing either situation, all affected work processes need to be examined. Because of the inherent accuracy and efficien

43、cy of data collection using machine readable technology, most manual data collection and data entry processes can be greatly improved. Organizations that are NOT the initiators of labeling requests have gained as much, if not more, than the requester by re-engineering their work processes to accommo

44、date the labeling requirements. While the stimulus for machine readable labeling may come from external sources, an examination of internal business processes can also prompt action. In those cases where an internal decision has been made to implement a machine readable labeling process, the first s

45、tep will be to identify partners to either receive or generate the labels. Prospective candidates include those customers or vendors with which successful business relationships are currently maintained. In looking toward to the future, examine what types of Electronic Commerce (e.g. EDI) capabiliti

46、es or plans these potential partners have as the merging of bar coding and Electronic Commerce is a potentially powerful tool. 2.2 Defining Label Requirements Once the need for the PRODUCT PACKAGE LABEL and/or the SHIPPING/RECEIVING TRANSACTION LABEL has been determined, trading partners must mutual

47、ly agree as to what information will be required on the labels. The PRODUCT PACKAGE LABEL and the SHIPPING/RECEIVING TRANSACTION LABEL provide for variable label formats and information content including optional data fields. The CABLE REEL ID LABEL format and information is fixed. While there are g

48、uidelines for the content, some of the informational fields are optional or may contain data in variable formats. It is a good practice to involve all affected organizations in the requirements definition phase. This will help to ensure that everyones needs and procedural changes resulting from mech

49、anization have been identified. While performing this review process, be sure to examine both current and future informational needs. Sections 7.2.4, 7.3.3, and 7.4.5 of this document contain expanded information on label content. 2.3 Communicating Requirements Depending on the number of potential trading partners, consider one-on-one communications with each partner or a “seminar” environment where communications with m