《ATIS-0300006-2008.pdf》由会员分享，可在线阅读，更多相关《ATIS-0300006-2008.pdf（107页珍藏版）》请在三一文库上搜索。
1、 ATIS-0300006 (Formerly TCIF-93-002, Issue 5) Implementation Guide for Package Labeling -,-,- The Alliance for Telecommunication Industry Solutions (ATIS) is a technical planning and standards development organization that is committed to rapidly developing and promoting technical and operations sta
2、ndards for the communications and related information technologies industry worldwide using a pragmatic, flexible and open approach. Over 1,100 participants from more than 350 communications companies are active in ATIS 23 industry committees and its Incubator Solutions Program. COMMON LANGUAGE is a
3、 registered trademark and CLEI is a trademark of Telcordia Technologies. This document, “Implementation Guide to Package Labeling,” has been written to augment the more technical information supplied in the Electronic Industries Alliance EIA/CEA-624-A PRODUCT PACKAGE BAR CODE LABEL STANDARD, Electro
4、nic Industries Alliance CEA- 556-B OUTER SHIPPING CONTAINER BAR CODE LABEL STANDARD, and GUIDELINES FOR THE IDENTIFICATION AND BAR CODE LABELING OF CABLE REELS by providing a practical approach to the subject of bar code labeling. Notice of Disclaimer and Limitation of Liability The information prov
5、ided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering or other professional standards and applicable regulations. No recommendation as to products or vendors i
6、s made or should be implied. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AG
7、AINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. ATIS SHALL NOT BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY ATIS FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL ATIS BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. ATIS EXPRESSLY ADVI
8、SES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. NOTE - The users attention is called to the possibility that compliance with this standard may require use of an invention covered by patent rights. By publication of this standard, no posi
9、tion is taken with respect to whether use of an invention covered by patent rights will be required, and if any such use is required no position is taken regarding the validity of this claim or any patent rights in connection therewith. ATIS-0300006, Implementation Guide for Package Labeling Impleme
10、ntation Guide for Package Labeling is an ATIS standard developed by the Bar Code/Standard Coding (BCSC) under the ATIS OAM owner code, serial number, and reel size code. As cable is manufactured, it is wound onto reels, each of which has been identified with a TCIF CABLE REEL ID LABEL. The CABLE REE
11、L ID LABEL is scanned and entered into the 18 -,-,- 19 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 reel itself. As cable picking requests are
12、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 length is being pulled from storage and shi
13、pped. 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 they are received, and moved to various tran
14、sfer 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 specific reel. The reels may be owned by the
15、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 by reel basis 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 uti
16、lized to track these transfers. This system can greatly facilitate the return of empty cable reels to minimize charges imposed by the cable provider when specific cable reels are not returned within a specified time frame. 1.3.4.3.1 Packing List A packing list document may accompany the cable reel s
17、hipment in order to provide a paper copy listing ordered products, their quantity and how they are packaged within the shipment. It may also include a two dimensional symbol that contains portions of the associated Ship Notice Manifest data (TCIF transaction set 856) that can be used to receive the
18、shipment and further automate the receiving process. The packing list document should become unnecessary in the future as electronic commerce between trading partners becomes dependent on the package identification data field of the shipping label. 1.3.5 Benefits The following are some of the benefi
19、ts that can be gained through the use of the 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.
20、1.3.5.1 Producers of Labels Standard label 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 applicat
21、ions. Greater mechanization and accuracy in 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. Sta
22、ndard bar code symbol labels can be 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. -,-,- 20 1.3.
23、5.2 Recipients Of Labels Using automatic data 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 receiv
24、ing and put-away personnel. The use of standard bar code symbol labels can eliminate the need to re-identify (re-label) material for storage. Standard bar code symbol labels can be used to mechanize the inventory control (cycle counting) process by providing a bar code symbol identification of produ
25、ct and quantity. The use of standard bar code symbol labels can provide a platform for further partnering using EDI technology. -,-,- 21 2 Implementation Procedures for Labeling The following describes the procedures involved in establishing a trading partner relationship using the PRODUCT PACKAGE L
26、ABEL, the SHIPPING/RECEIVING TRANSACTION LABEL, and/or the CABLE REEL ID LABEL. These procedures are not 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 Bar Code Labeling Many times, the nee
27、d to generate or to receive the bar code symbol PRODUCT PACKAGE LABEL, the SHIPPING/RECEIVING 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 a
28、ffected work processes need to be examined. Because of the inherent accuracy and efficiency of data collection using bar code 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,
29、if not more, than the requester by re-engineering their work processes to accommodate the labeling requirements. While the stimulus for bar code labeling may come from external sources, an examination of internal business processes can also prompt action. In those cases where an internal decision ha
30、s been made to implement a bar code labeling process, the first step 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
31、, examine what types of Electronic Commerce (e.g. EDI) capabilities 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 TR
32、ANSACTION LABEL has been determined, trading partners must mutually 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
33、 REEL ID LABEL format and information is fixed. While there are guidelines 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 ensur
34、e that everyones needs and procedural changes resulting from mechanization have been identified. While performing this review process, be sure to examine both current and future informational needs. Sections 3.2.4., 3.3.4. and 3.4.5. of this document contains expanded information on label content. 2
35、.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 many partners can be accomplished. In either situation, the following items should be covered in the discussi
36、ons. 2.3.1 TCIF Label Information Exchange Form The TCIF LABEL INFORMATION EXCHANGE FORM (See Attachments) contained in this document has been developed to assist the “initiator“ of the labeling requirements in communicating labeling requirements to the other partner in the relationship. This form s
37、hould be completed as part of the requirements definition process. Instructions for completing the form are included in this document (See Attachments). -,-,- 22 The form can then serve as the primary requirements record between partners and should represent the exact content of the labels. (The dat
38、a content of the CABLE REEL ID LABEL is fixed, therefore the LABEL INFORMATION EXCHANGE FORM is not applicable.) 2.3.2 Differences There will be occasions when requirements cannot be easily met by both trading partners and a negotiated solution will be required. It would not be unusual to be partner
39、ing with hundreds of different companies, each having some unique requirements. Designing systems and procedures with as much flexibility as practical will help handle these differences. See the TCIF LABEL INFORMATION EXCHANGE FORM. 2.3.3 Label Samples Normally the “supplier“ in the partnership will
40、 be required to produce sample labels prior to implementation. These samples should be reviewed by the “receiver“ to ensure that data is encoded properly and that the required print quality levels are met on an initial and continuing basis. 2.3.4 Schedules Mutually agreeable time frames must be esta
41、blished for the implementation. Milestones should include (but not necessarily be limited to): Creation of initial label samples Review and verify samples, providing feedback Creation of final label samples Final review of samples and approval Implementation Post-implementation review 2.4 Process An
42、alysis Both partners should analyze their business processes to ensure that the changes imposed by bar code labeling have been reviewed with all affected organizations and that all necessary system and procedural changes have been identified. Again, both partners should also examine their existing p
43、ractices to ensure that they are maximizing the potential of the bar code technology. 2.5 Communicating System And Procedural Changes Many companies follow a structured methodology for introducing system and/or procedural changes into their business processes. Whether or not a formal methodology exi
44、sts, it is critical to convey any changes and time frames for those changes to those organizations that have responsibility for making the modifications. It is important that these organizations (typically Management Information Systems MIS, Engineering, Methods, Sales and Marketing, Shipping, Recei
45、ving) have a clear understanding of the goal. 2.6 Software Selection/Development Normally the introduction of bar code labeling into an organizations business processes requires some computer system modification. There are several approaches and resources that can be utilized, the three most common
46、being: 23 the internal company MIS department, contractor who has experience with bar code integration, off-the-shelf software that is compatible with the host computer. 2.7 Hardware Selection The hardware involved in the bar code process typically includes bar code printers, scanners, and verifiers
47、. Bar code printers can also require ribbons/inks and label stock. Because there are a myriad of products and manufacturers, the critical factor in the selection of any hardware is that it is suitable to the bar code printing application or process in which it will be used. More specifically, the ha
48、rdware should be capable of printing, scanning, and verifying bar code labels of the size, symbology, and quality specified by the TCIF for this application. If the scanning of labels affixed directly to products requires using the same scanners as those used for scanning the package labels, then sc
49、anners must include additional symbologies and scanner resolution capabilities in accordance with section 8 of the TCIF-00- 003 Product Marking Implementation Guideline. In addition, the hardware components should be compatible with each other, as well as with the software that drives them. Assistance in h