RFID Guide.PDF

Item-Level Passive RFID Technology Manufacturer’s Information Guide

Revision 2—December 2011

Revision 2—December 2011 iii

Contents

ITEM-LEVEL PRFID PROCESS

Step 1—Download Contract Data

Step 2—Encode/Print pRFID Item Tags

Step 3—Attach pRFID Item Tags

Step 4—Encode/Print pRFID Case Labels

Step 5—Attach pRFID Case Labels

Step 6—Pack Items in Case

Step 7—Read pRFID Item Tags and pRFID Case Label

Step 8—Case Validation/Item-to-Case Link

Step 9—Encode/Print pRFID Pallet Labels

Step 10—Build Pallet

Step 11—Attach pRFID Pallet Labels

Step 12—Link Case Labels to Pallet Labels

Step 13—Manufacturer: Upload Pack/pRFID Data to VIM-ASAP

Step 14—Generate Partial DD250 & MSL

Step 15—Manufacturer: View and Complete DD250

Step 16—Manufacturer: Review and Complete MSL

Step 17—Upload to WAWF

PROJECT IMPLEMENTATION

Identify Implementation Project Team

Manufacturer Preparation

Create and Distribute an RFP to potential pRFID Solution Providers

Conduct Solution Provider Selection Meeting

Installation and Operations

APPENDIX A. VIM-ASAP

APPENDIX B. FIELDS REQUIRED BY VIM-ASAP FOR FILE UPLOAD

APPENDIX C. RFP OUTLINE FOR AN ITEM-LEVEL TECHNOLOGY IMPLEMENTATION

APPENDIX D. RFP EVALUATION SCORECARD

APPENDIX E. EXAMPLE COSTS SUMMARY

APPENDIX F. ABBREVIATIONS

Revision 2—December 2011 iv

Figures

Figure 1. Typical Item-Level pRFID Process at the Manufacturer

Figure 2. Front and Back Side of an Item-Level pRFID Tag

Figure 3. pRFID Item-Level Tags Encoded and Printed

Figure 4. Attachment of pRFID Item Tag to ABU Trousers

Figure 5. Attachment of pRFID Item Tag to ABU Coats

Figure 6. Tag Gun with Fastener

Figure 7. Attachment of pRFID Item Tag to Boots

Figure 8. Attachment of pRFID Item Tag to Caps

Figure 9. Attachment of pRFID Item Tag to Duffel Bags

Figure 10. Example of Printed Information on pRFID Case Label

Figure 11. pRFID Case Label ID and Back of pRFID Case Label

Figure 12. ABUs Awaiting Packing

Figure 13. Items Being Packed in Case

Figure 14. Item-to-Case Pack Station/Table

Figure 15. Conveyor with Fixed pRFID Readers

Figure 16. Case Acceptance during Validation Process

Figure 17. Quantity Overage Error Message during Validation Process

Figure 18. Exception Case Label with Incorrect NSN Error

Figure 19. Front of pRFID Pallet Label

Figure 20. Pallet Label Attached to Pallet and Back of Pallet Label Showing Inlay

Figure 21. Linking Cases to Pallet—Handheld Reader

Figure 22. Linking Cases to Pallet—RFID-Enabled Palletizer

Figure 23. First Page after Login Menu

Figure 24. Drop Down Menu of Manufacturing Folder Tab

Figure 25. View/Edit Existing DD250s Web Page

Figure 26. View/Edit Existing Shipment Labels

Figure 27. Complete and Printed MSL

Revision 2—December 2011 1

Item-Level Passive RFID Technology

The Defense Logistics Agency (DLA) Customer Driven Uniform Manufacture

(CDUM) Program has conducted research and development (R&D) efforts to identify, test, and evaluate how emerging passive radio frequency identification

(pRFID) technology solutions at the item-level will affect fabric suppliers, combat uniform manufacturers, distribution warehouses, and the warfighter issuing points. The CDUM program confirmed that pRFID technology offers improved asset tracking and operational efficiencies throughout the military clothing and textile supply chain. Information gathered using pRFID technology also provides distinct advantages to the manufacturing community in terms of monitoring pro-duction and improving the precision of packing and shipping processes.

This guide provides manufacturers with important information and lessons learned by manufacturers involved in DLA’s CDUM program item-level pRFID technology pilots and Industrial Base Innovation Fund (IBIF) item-level pRFID implementation projects. This guide describes, step-by-step, a typical process for implementing item-level pRFID technology in a uniform-manufacturing environment.

ITEM-LEVEL PRFID PROCESS

The processes and implementation steps described in this guide are somewhat flexible; manufacturers can tailor their item-level pRFID solution to a particular item, production process, or manufacturing environment. Figure 1 shows a typical item-level pRFID manufacturing process. Most successful pRFID item-level technology implementations will follow this basic approach, with only minor modifications to accommodate unique manufacturing processes and environments.

As shown in Figure 1, the item-level pRFID process affects three areas of current military uniform production:

New and modified steps associated with pRFID item-level technology

(in red)

Existing and modified steps associated with the current case and pallet pRFID labeling (in blue)

Existing and modified steps associated with the Virtual Item Manager–

Apparel Research Network (ARN) Supply Chain Automated Processing

(VIM-ASAP) shipping process (in purple).

Revision 2—December 2011 2

Figure 1. Typical Item-Level pRFID Process at the Manufacturer

Existing/modified steps In VIM-ASAP shipping process

WAWF

ARN

Step 16 Manufacturer: Review and complete MSL

Step 15 Manufacturer:

View and complete DD250

Step 17 Upload to WAWF

New/modified steps in manufacturer process

Step 2 Encode/print pRFID item tags

Step 6 Pack items in case

Step 4 Encode/print pRFID case labels

Step 11 Attach pRFID pallet labels

Step 10 Build pallet

Step 3 Attach pRFID item tags

Step 5 Attach pRFID case labels

Step 9 Encode/print pRFID pallet labels

Step 8 Case validation/ item-to-case link

Step 14 Generate partial

DD250 & MSL

Existing/modified steps in manufacturer process

Local database

Step 1 Download contract data

Step 13 Manufacturer:

Upload pack/ pRFID data to

VIM-ASAP

Step 12 Link pRFID case labels to pRFID pallet labels

Step 7 Read pRFID item tags and pRFID case label

Note: MSL = military shipping label; WAWF = Wide Area Work Flow.

Note: Not shown in Figure 1 is an informal feedback loop consisting of email error messages sent to the manufacturer by VIM-ASAP after Step 13. VIM-ASAP generates these e-mail messages when it detects a prob-lem, such as duplicate RFID tags and quantities in excess of order quantity (including variance excesses). The email error messages are not part of the manufacturer process but rather are a result of deviations to the pro-cess.

A description of each step involved with the item-level pRFID manufacturer’s process follows below. Each step description provides an explanation of the pro-cess step, the pRFID equipment required to perform that step, and some pitfalls to avoid.

Revision 2—December 2011 3

Step 1—Download Contract Data

ARN

Local database

Step 1 Download contract data

Equipment and software required for Step 1:

Reliable high-speed internet connection

PC workstation and display

Microsoft Internet Explorer version 6.0 browser (or later)

The timely and accurate download of contract data associated with each item is critical for successfully applying item-level pRFID technology to each item. It is imperative that this source contract data is accurate, as it will be uploaded later in the process and made available to activities downstream as the items travel through the supply chain to the warfighter.

To accomplish the download process, manufacturers must set up a database (typi-cally on a local server, but remote servers have also been used) and use VIM-

ASAP to populate it with current contract information gathered from the ARN database and additional information associated with the items being produced.

VIM-ASAP is a collection of web applications used by apparel manufacturers to track production status, prepare invoices, ship items, and create all required docu-ments and electronic transactions from a single source of data, the ARN database.

Each day manufacturers receive information from VIM-ASAP, including contract number and delivery order number;

the prime contractor’s commercial and government entity code (CAGE);

a Department of Defense Activity Address Code (DoDAAC) for the ship-to site;

a contract line item number (CLIN);and all related CLIN data.

To access VIM-ASAP, manufacturers must acquire VIM-ASAP credentials, des-ignate a local program administrator, and establish system connectivity. VIM-

ASAP creates a home directory for each credentialed manufacturer; the manufac-turer automatically downloads, from its designated VIM-ASAP home directory, a file containing the current contract information listed above. It is the manufac-turer’s responsibility to transfer this data to its internal information systems in a

A ship-from CAGE code (if different from prime contractor’s CAGE code) is not provided in the downloaded data; it must be provided by the manufacturer.

Revision 2—December 2011 4 format that is compatible with the software it uses to create pRFID item-level tags and case- and pallet-level labels.

Manufacturers can download their contract data onto either a local or remote server. There are advantages and disadvantages for both server types. Local ser-vers tend to be faster, function better in high-volume manufacturing operations, and are not internet-dependent; but local servers also require a higher initial in-vestment and may increase overall system maintenance costs. Remote servers will have lower initial and operating costs, if operating in a shared environment; but a remote server may include monthly operations and maintenance fees, may be in-ternet-dependent, and may have scalability difficulties for high-volume manufac-turing operations.

Appendix A contains a more detailed discussion of how to upload and download contract data using VIM-ASAP.

Lesson learned for Step 1:

Manufacturers need to know their VIM-ASAP credentials (logon and password) for accessing the system. In some cases, VIM-ASAP credentials were established years ago to implement case and pallet level pRFID automated applications but have been forgotten or lost.

Revision 2—December 2011 5

Step 2—Encode/Print pRFID Item Tags

Step 2 Encode/print pRFID item tags

Equipment and software required for Step 2:

PC workstation and display pRFID enabled printer pRFID printer software

The encoding and printing of a tag consists of three sub-processes.

Printing the tag. The necessary information is printed on the front of the item-level tag (see Figure 2). This information includes two elements:

The information that is currently on a manufacturer’s non-RFID hang tag (in both human readable and bar code formats) and required by the contract

The unique RFID tag identification (ID) number—a unique hexadeci-mal serial number—in both human readable and bar code formats.

Encoding the tag ID. The unique RFID tag ID number is encoded by the printer on the RFID inlay embedded in the tag.

Linking information. The PC workstation and software links each unique tag ID to the contract information downloaded from VIM-ASAP in Step 1 and any other required item level information.

The manufacturer uses the contract data downloaded from VIM-ASAP and popu-lated into its database to encode and print pRFID item-level tags. The manufac-turer is responsible for creating this tag, much as they are responsible for creating the barcode hang tag specified in the contract.

Item-level tag size usually follows the current (non-RFID) hang tag dimensions.

Typical sizing of the tag ranges from 3 in. × 1.75 in. to 4 in. × 2.125 in. An ex-ample of the front side and back side of the type of pRFID item-level tag current-ly in use is depicted in Figure 2; however, these tags may change in the future as technology improves, information on the tag is modified, and costs fluctuate.

Revision 2—December 2011 6

Figure 2. Front and Back Side of an Item-Level pRFID Tag

The pRFID inlay is embedded in the tag, and is visible in the top back half of the tag. The pRFID chip sits in the middle of the inlay, and the antenna spans nearly the full length of the tag. It is important to note that the only data element encoded in the RFID chip is the unique hexadecimal RFID tag ID number; none of the in-formation printed on the front of the pRFID tag is encoded in the chip other than the pRFID tag ID number. The pRFID item tags and case and pallet labels use the same or similar pRFID inlays.

Figure 3 shows pRFID item-level tags being encoded and printed.

Figure 3. pRFID Item-Level Tags Encoded and Printed

Since 1 March 2007, DoD has exclusively accepted Ultra High Frequency (UHF)

Generation 2 Electronic Product Code (EPC) standard tags. The frequency range

Revision 2—December 2011 7 for these tags is 860 to 960 MHz, with a minimum read range of 3 meters. It is the responsibility of the manufacturer to ensure that every pRFID tag shipped to the government is encoded with a globally unique identifier (unique tag ID). The unique tag ID can only be used once in order to conform to the “one tag, one ID” rule.

DoD accepts two item-level tag constructs, the EPCglobal and the DoD-96. Only suppliers that are EPCglobal subscribers can use the EPCglobal tag construct.

To date, all manufacturers have used the DoD-96 construct for item-level technology.

The combination of a header/filter code, CAGE code, and serial number, as pro-vided by the construct, make the tag ID unique.

Pallet, case and item level tags and labels use the same DoD-96 construct. The difference is the first three digits of the unique ID number encoded in the inlay.

Each tag, case, and pallet ID number begins with “2F.” The next digit denotes whether the number refers to a pallet (0), a case (1) or a tag (2):

2F0… identifies a pallet

2F1… identifies a case

2F2… identifies an item.

Lesson learned for Step 2:

Strict controls over archived and active item tag, case, and pallet label print files should be maintained to ensure a print file is used only once. Access to archived print files should be limited to only required per-sonnel. This will prevent the duplication of printed tags and labels.

The same process should be used to generate and encode the pRFID tag ID and print the tag ID in both barcode and human-readable formats. Using separate processes has led to tag mismatches.

Care must be taken to place strict controls over naming and generating pRFID item tag encode/print files. Valid print files have been incorrectly overwritten, causing erroneous labels to be printed.

Manufacturers need to understand the operation of the tag printers, especially the printing of tags during

“power up,” a restart after power loss, reloading the printer with blank tags, and changing the print ribbon.

Some printers may start by purging tags in the printer when the power was turned off. These tags may need to be discarded.

If using a remote print service to generate tag print files, ensure the printer software has the latest soft-ware changes. Printers with outdated software may encounter errors when print files are received.

Automated printer software updates should be developed to guarantee successful printing operations.

For more information, please refer to the tag data standards document at http://www.epcglobalinc.org/standards.

http://www.epcglobalinc.org/standards

Revision 2—December 2011 8

Step 3—Attach pRFID Item Tags

Step 3 Attach pRFID item tags

Equipment and software required for Step 3:

Plastic/nylon tag fasteners

Tag gun

The manufacturer must attach the item-level pRFID tag printed and encoded in

Step 2 to each item so all items can be counted when the case is packed and ulti-mately tracked through the supply chain. From past implementations, we know the item-level pRFID hang tags can often be placed at the same attachment point and in the same manner as the non-pRFID hang tag; however, in some instances, it was necessary to attach the pRFID hang tag using a different method or attach-ment point to achieve acceptable read rates when packed in a case.

Various factors can affect the ability to successfully read a pRFID tag. For exam-ple, tags should not be folded, bent, or in contact with each other, or they may not be readable. Also, the materials used in uniform items, such as metallic fibers, may inhibit the successful read of item-level pRFID tags. Trial and error for the tag attachment method and tag attachment point will help identify an acceptable tag attachment approach.

Tag attachment points and methods may vary by item and manufacturer. The following offer some examples:

ABUs. pRFID item tags are attached to airman battle uniform (ABU) trou-sers using a nylon fastener that is normally looped through the hole in the tag and then looped through the flap of the side pocket on the thigh (see

Figure 4). pRFID item tags are attached to ABU coats using a nylon fas-tener that is normally looped through the hole in the tag and then looped through the flap of the right breast pocket (see Figure 5). In both cases the nylon fastener is closed using the attachment gun (see Figure 6).

Boots. pRFID item tags are attached to boots using a nylon fastener that is looped through the hole in the tag and then looped through the second speedloop from the top of the boot (see Figure 7).

Caps. pRFID item tags are attached to caps using a nylon fastener that is looped through the hole in the tag and then looped through the band where the top of the cap is sewn to the bill (see Figure 8).

Duffel bags. pRFID item tags are attached to duffel bags using a nylon fastener that is looped through the hole in the tag and then looped through the vertical seam in the duffel bag at a point near the top of the bag (see Figure 9).

Revision 2—December 2011 9

Figure 4. Attachment of pRFID Item Tag to ABU Trousers

Figure 5. Attachment of pRFID Item Tag to ABU Coats

Revision 2—December 2011 10

Figure 6. Tag Gun with Fastener

Revision 2—December 2011 11

Figure 7. Attachment of pRFID Item Tag to Boots

Revision 2—December 2011 12

Figure 8. Attachment of pRFID Item Tag to Caps

Revision 2—December 2011 13

Figure 9. Attachment of pRFID Item Tag to Duffel Bags

Revision 2—December 2011 14

Step 4—Encode/Print pRFID Case Labels

Step 4 Encode/print pRFID case labels

Equipment and software required for Step 4:

pRFID printer pRFID printer software

Many vendors currently place case and pallet pRFID labels on their shipments.

Information for pRFID case and pallet labels can be found in the United States

Department of Defense Suppliers’ Passive RFID Information Guide and MIL-

STD-129P (Change 4), Military Marking for Shipment and Storage.

The printing and encoding of the case pRFID label can occur before or after the packing of the case. Like item-level pRFID tag constructs, the manufacturer has the option of using the DoD-96 bit tag construct for case labels or the EPCglobal

(if the manufacturer is an EPCglobal subscriber) tag construct. The unique ID encoded in the pRFID chip used at the case level begins with 2F1.

To encode/print pRFID case labels, manufacturers use pRFID printer software to generate the case label with the required case information printed and the unique case pRFID label ID encoded.

Some manufacturers place additional labels on cases. These labels may support warehousing and shipment activities within their organization or they may fulfill additional contractual requirements. Manufacturers can take advantage of imple-menting the item-level pRFID process implementation to investigate the options for consolidating additional case labeling into one integrated case pRFID label, which could reduce material and labor costs.

Figure 10 shows a pRFID case label with the case information required by the contract printed on it. Figure 11 shows the case label’s unique ID number in bar code and human readable form. Typically, case pRFID labels, like the label shown in Figure 10 and Figure 11, are 4 in. × 6 in Figure 21.

Revision 2—December 2011 15

The inset for Figure 11 shows the pRFID chip inlay on the back of the case label.

The case label (see Figure 10 and Figure 11) uses the same inlay as that on the pRFID item tag in Figure 2 and pRFID pallet label in.

Figure 10. Example of Printed Information on pRFID Case Label

Figure 11. pRFID Case Label ID and Back of pRFID Case Label

Revision 2—December 2011 16

Step 5—Attach pRFID Case Labels

Step 5 Attach pRFID case

Equipment and software required for Step 5: None

The manufacturer must attach the pRFID case label so the particular case (and its contents) is accounted for when the pallet is built. The pRFID case labels are placed on each case to allow the markings to be easily read and to prevent the case labels from being destroyed when the pack or container is opened for inspection or until its contents have been used.

The markings should be placed so they are not obscured by any strapping or clo-sure tape. More details can be found in MIL-STD-129P (Change 4), Military

Marking for Shipment and Storage.

Revision 2—December 2011 17

Step 6—Pack Items in Case

Step 6 Pack items in case

Equipment and software required for Step 6: None

After the item-level pRFID hang tags have been attached to the finished item, cases must be packed with the correct type and quantity of items. The case can be packed prior to attaching the case labels (described in Step 5) or they can be packed in a case that already has the case pRFID label attached. The sequence of steps depends on the manufacturer’s production process.

The ABUs shown in Figure 12 have been tagged and are awaiting packing.

Figure 12. ABUs Awaiting Packing

To pack items in a case, the manufacturer needs the case and the requisite num-ber of items (per case pack quantity) with encoded pRFID item tags attached.

Figure 13 shows items with pRFID item tags being packed in a case.

Revision 2—December 2011 18

Figure 13. Items Being Packed in Case

In most cases, the method for packing cases will not change with the implementa-tion of the item-level pRFID process; however, we did observe modification to the item packing process was necessary in some implementations to increase the read-ability of item tags in a case. The method used for case packing should prevent the bending or folding of item-level pRFID hang tags and item-level pRFID hang tags from touching each other.

One manufacturer of battle uniform trousers had to modify its hang tag attach-ment point and place the item-level pRFID tag in the trouser pocket to prevent the tags from folding and to eliminate tag-to-tag contact.

Lesson learned for Step 6:

After packing, item tags may not be completely and accurately read during the first “read”. Different items may require different tag attachment points (for example, placed in a pocket) or other tag ad-justments to achieve an acceptable read rate.

Revision 2—December 2011 19

Step 7—Read pRFID Item Tags and pRFID Case Label

Step 7 Read pRFID item tags and pRFID case label

Local database

Equipment and software required for Step 7:

PC workstation and display (or case label printer) pRFID antennas and reader pRFID reader software

During this step, each item-level pRFID hang tag and its case pRFID label are read. The output of the item and case level read is provided on a computer screen and reviewed by the station operator. The information collected in the read will be used to validate the case contents and to establish the item-to-case link in Step 8.

Past implementations used two basic configurations:

A pack station or table with fixed pRFID readers (see Figure 14)

A conveyor with fixed pRFID readers (see Figure 15).

A third possible configuration is the use of handheld readers. Handheld readers are only practical in low-volume, low-pack-quantity manufacturing operations. They are more labor inten-sive and slower in comparison to the other configurations. There has been no implementation where it was feasible to employ the use of handheld readers for item tag to case label linking.

Revision 2—December 2011 20

Figure 14. Item-to-Case Pack Station/Table

Figure 15. Conveyor with Fixed pRFID Readers

Revision 2—December 2011 21

The equipment configuration is driven primarily by business considerations, such as the production process, location of facility (multiple-location; single-location; pro-duction and packing in one facility, with shipping and storage in another facility), equipment re-usability (print in one facility for use in another facility), ability to handle multiple customers’ shipments using the same national stock numbers

(NSN) and part numbers from separate suppliers (lot and part segregation and tracking by original part manufacturer), production volume (including surge), space availability, type of items, case pack quantity, and size of the case.

The following provide real-world examples:

A packing vendor may pack a size 32L pant from two different manufac-turers with different contract awards. The packing vendor must differenti-ate each manufacturer’s items and ensure the contents of each case are all from the same vendor. This is critical for correct billing and shipment of the correct manufacturer’s garments by contract.

A vendor may have multiple manufacturing facilities that must share item, case, and pallet detail among all facilities to allow a product to move from location to location.

A vendor may produce pRFID tags in one location, and then send them to another location for on-demand packing or palletizing. This allows the ven-dor to pre-encode pRFID tags using a single printer and have multiple re-mote locations packing and assigning products to the correct case or pallet as they are needed. This is known as “late binding.” It allows a pRFID tag to be assigned to a particular case or pallet long after it has been produced.

Lesson learned for Step 7:

The process to read tags and labels should be designed to isolate and eliminate reads of stray, un-desirable tags and labels. Power settings should be adjusted or the immediate areas should be kept clear of other pRFID tags so only the pRFID tags of interest are captured.

Some manufacturers may produce items that require item-level pRFID technology and other items that only require case and pallet pRFID labels. An item may follow a separate manufacturing process if item level technology is required. Strict controls must be put in place to insure that items requiring item level technology follow the manufacturer’s item level pRFID process established.

Revision 2—December 2011 22

Step 8—Case Validation/Item-to-Case Link

Step 8 Case validation/ item-to-case link

Equipment and software required for Step 8:

pRFID validation and linking software

Before the implementation of item-level pRFID, case validation was a manual process that could require several quality checks to determine whether the correct items (by size, CAGE code, and contract) and quantities were packed in the case.

The item-level pRFID process automates this step. During item-to-case valida-tion, data collected during the item tag and case label read process (Step 7) are used to confirm the contents of each case are correct. The pRFID hardware and software is capable of checking for the following case-pack conditions:

The number of items in the case matches the correct case-pack quantity.

The items in the case are all of the same type and size or NSN.

The items in the case share the same CAGE code.

Other validation checks may be necessary; it depends on the manufacturer’s circumstances and contract requirements.

The pRFID software uses the item-level tag reads and associated item information from the manufacturer’s database to perform the validation. If the system detects an error, it immediately notifies the operator responsible for resolving the error by displaying an error message on the PC workstation display or print out. The oper-ator can correct or override the error. Figure 16 shows an example of a PC work-station display during a successful validation (when the items and quantity are all correct). Figure 17 shows an example of an unsuccessful validation, where the number of item tags read was greater than the desired case pack quantity.

In some instances, cases may be packed in quantities under or over the stated case pack quantity when stipulated in the contract.

Revision 2—December 2011 23

Figure 16. Case Acceptance during Validation Process

Figure 17. Quantity Overage Error Message during Validation Process

An exception label for the case can be printed as an alternative to using a screen display for case validation errors. The exception label in Figure 18 indicates an

NSN error.

Revision 2—December 2011 24

Figure 18. Exception Case Label with Incorrect NSN Error

Lesson learned for Step 8:

Equipment must be protected against power fluctuations (power surges and “dirty” power).

Components within printers and readers are vulnerable to unstable power supplies.

Linking item tags to case labels and case labels to pallet labels requires local network connectivity, at a minimum, to exchange information. Redundant network capabilities should be available to pre-vent production delays.

To prevent the introduction of duplicate tags, the processes and equipment used for item-level pRFID technology should be designed with tag verification checks performed at multiple points in the process. At a minimum, tag verification should be conducted at printing, validation, and ship-ping.

If items are pulled out of cases for quality audit, rework or other reasons, the item must be disasso-ciated with the case. If the item-level tag is removed or disassociated from the item for any reason, the manufacturer must have controlled processes in place to insure the item is properly tagged and associated with the correct item data.

Revision 2—December 2011 25

Step 9—Encode/Print pRFID Pallet Labels

Step 9 Encode/print pRFID pallet

Equipment and software required for Step 9:

pRFID printer pRFID software

The manufacturer must perform this step to create the pallet’s unique ID number, which can be linked to the cases and tracked through the supply chain. Pallet labels include, in both human readable and bar code formats, the unique pallet label ID number and other information required by the contract. Figure 19 illus-trates the front of a pRFID pallet label. Figure 20 shows a pallet label attached to a pallet and the back of a pRFID pallet label, including the label’s inlay. The inlay is the same or similar to the inlays used in the pRFID item tag (Figure 2) and pRFID case label (Figure 10 and Figure 11).

Figure 19. Front of pRFID Pallet Label

Note: Some small shipments are made without pallet-level RFID tags. Even when only a few cases are shipped separately, each case requires its own MSL.

Revision 2—December 2011 26

Figure 20. Pallet Label Attached to Pallet and Back of Pallet Label Showing Inlay

Manufacturers that currently use a “slap-and-ship” process to link the case to the pallet and print the pallet label during their shipping process will likely need to modify their processes. To perform the case label read, validation, and linking processes, the case labels will need to be made available and placed on the cases earlier than required in a “slap-and-ship” operation.

Revision 2—December 2011 27

Step 10—Build Pallet

Step 10 Build pallet

Equipment and software required for Step 10: None

After the case has been packed, validated, and sealed, and each item-level pRFID tag has been linked to its case pRFID label, the cases are put on pallets in prepar-ation for storage, staging or shipment. As cases are placed on the pallet, it is pref-erable that outside cases be positioned so the case labels are visible and can be read; however, some manufacturers’ contracts dictate case markings not be visible on the outside of the pallet cube and must have their case labeling face inward.

Manufacturers with this requirement may need to use trial and error to identify the best placement of case labels and case orientation to achieve an acceptable case pRFID label read rate when palletized.

Additional information on case and pallet-level pRFID labels can be found in the

United States Department of Defense Suppliers’ Passive RFID Information Guide and MIL-STD-129P (Change 4), Military Marking for Shipment and Storage.

Revision 2—December 2011 28

Step 11—Attach pRFID Pallet Labels

Step 11 Attach pRFID pallet

Equipment and software required for Step 11: None

The pallet pRFID label may be integrated with the military or commercial ship-ping label (pRFID-enabled address label) or it may be placed in a separate loca-tion on the pallet. Pallet pRFID labels should be affixed at a suitable location where there is minimum risk of damage and the highest potential for successful pRFID label read.

Manufacturers have used different pRFID label configurations and attachment methods for their pallet pRFID labels. For example, when a palletized load was covered with stretch-wrap film, a pressure-sensitive pRFID label was placed on the outermost layer of wrap (see Figure 20).

The pallet pRFID label should not be placed over a seam nor should sealing tape or bands be placed over the label in a manner that interferes with the scanning of the label bar codes or the reading of pRFID labels. Also, it should not be placed in a manner that overlaps any other existing pRFID label.

Additional information on case- and pallet-level pRFID labels can be found in

United States Department of Defense Suppliers’ Passive RFID Information Guide and MIL-STD-129P (Change 4), Military Marking for Shipment and Storage.

Revision 2—December 2011 29

Step 12—Link Case Labels to Pallet Labels

Local database

Step 12 Link pRFID case labels to pRFID pallet labels

Equipment and software required for Step 12:

pRFID reading equipment pRFID software

Before shipment, each case pRFID label on the pallet needs to be linked to its pal-let pRFID label. The case-to-pallet linking process also must electronically link each pRFID pallet label to the contract, delivery order, and shipment numbers.

Several solutions are possible for the case-to-pallet linking process, including us-ing fixed readers, using a pRFID reader placed next to a palletizer/shrink wrap stand, or using a handheld pRFID reader/bar code scanner.

Figure 21 shows the handheld reader used to read and link cases to pallets; and

Figure 22 shows a pRFID reader next to a palletizer/shrink wrap stand. As a pre-cautionary note, power settings should be adjusted or the immediate areas should be kept clear of other pRFID tags so only the pRFID tags of interest are captured.

Figure 21. Linking Cases to Pallet—Handheld Reader

Palletizers/shrink wrap machines may be modified with RFID reader devices to accomplish the case-to-pallet link. It is important to note that palletizer equipment is not required for the item-level RFID process. Although the spinning action of the palletizer/shrink-wrap machine often im-proves the speed of the RFID reads, a manufacturer can use other fixed reader and handheld RFID reader/bar code scanners solutions to accomplish case-to-pallet association.

Revision 2—December 2011 30

Figure 22. Linking Cases to Pallet—RFID-Enabled Palletizer

Once the pallet pRFID label and case pRFID labels are captured by the pRFID read equipment, the operator confirms the pallet has the correct number of cases.

That confirmation also triggers the pRFID read software to send the case-to-pallet link information to the manufacturer’s information system.

Revision 2—December 2011 31

Step 13—Manufacturer: Upload Pack/pRFID Data to VIM-ASAP

Step 13 Manufacturer:

Upload pack/ pRFID data to

VIM-ASAP

ARN

Local database

Equipment and software required for Step 13:

Reliable high-speed Internet connection

PC workstation and display

Microsoft Internet Explorer version 6.0 browser, or later

The manufacturer must send its pRFID data (item, case, and pallet IDs and their associations) along with contract-related data and to VIM-ASAP. Information in-cluded in the uploads to VIM-ASAP includes data that will be used in Step 14 to generate the shipment’s DD Form 250 (DD250) and military shipping labels

(MSLs). The contract data the manufacturer will exchange with VIM-ASAP in-cludes the following:

Contract number and delivery order number

Prime contractor CAGE code

Ship-from CAGE code, if different from prime contractor CAGE code

DoDAAC

CLIN

NSN

Quantity shipped for the CLIN

Pallet-level pRFID packing data

Case-level pRFID packing data

Item-level pRFID packing data.

As described in Step 1, VIM-ASAP sends manufacturer contract data (contract number, CAGE code, and CLIN, as described in Step 1) for open contracts. During this upload process, the manufacturer returns shipment data (quantity per CLIN;

NSN; and pallet-, case-, and item-level pRFID data) for the items produced and shipped. VIM-ASAP stores this item-, case-, and pallet-level pRFID data and makes it available so manufacturers and receivers can trace shipments and particu-lar items through the supply chain.

Revision 2—December 2011 32

The file format for item-case-pallet pack and shipment pRFID data upload to

VIM-ASAP can be found at https://wawf.eb.mil/. The frequency of contract data upload is tied to the manufacturer’s production and delivery schedule. When manufacturers transmit their data to VIM-ASAP, the transmission must adhere to the file layout that VIM-ASAP expects. Additional information on VIM-ASAP upload and download procedures can be found in Appendices A and B. For fur-ther assistance, contact the VIM-ASAP Help Desk at 1-888-940-7348.

Lesson learned for Step 13:

The transition to add item-level technology to manufacturing operations currently applying only case and pallet needs to be well planned to insure proper linkages are established and uploaded. If op-erations continue to only upload case and pallet level information to VIM-ASAP without item-level information, downstream supply chain processes will encounter significant problems with unassoci-ated tags and lack of item level data.

https://wawf.eb.mil/

Revision 2—December 2011 33

Step 14—Generate Partial DD250 & MSL

ARN

Step 14 Generate partial

DD250 & MSL

Equipment and software required for Step 14:

PC workstation and display

Microsoft Internet Explorer version 6.0 browser, or later

VIM-ASAP uses the ARN Asset Visibility System (AAVS) to validate the ship-ment and pack data received from manufacturers. AAVS automatically generates a partial DD250 and MSL from that uploaded data. AAVS validates the infor-mation by comparing the uploaded information to existing contract data and pRFID files the manufacturer has already transmitted through VIM-ASAP. If

VIM-ASAP detects an error in the transmission, it sends an email about the error to the manufacturer within 15 minutes.

The following are possible transmission errors:

Unassociated item, case, and pallet pRFID tags

Duplicate pRFID tag/label ID numbers

Incorrectly coded tags

Total shipped quantity exceeds the contract delivery order quantity plus the variance percentage.

An example of an emailed error message for a duplicate case tag reads:

Duplicate Case RFID Tag: 2F120305A54463700000768D has already been imported from file 0ZTF7_0ZTF7_20110726.ftp.

Note that this message identifies the case pRFID tag that is a duplicate and identifies the uploaded file in which the original tag was sent.

If an error occurs with the uploaded file, VIM-ASAP does not generate a partial

DD250. The manufacturer has to correct the error and retransmit. If the transmis-sion is error free, VIM-ASAP will populate a DD250 document and the manufac-turer can finalize the DD250 and prepare the shipping labels as described in the next step.

Revision 2—December 2011 34

Step 15—Manufacturer: View and Complete DD250

ARN

Step 15 Manufacturer:

View and complete DD250

Equipment and software required for Step 15:

PC workstation and display

Microsoft Internet Explorer version 6.0 browser, or later

Ink-jet or laser printer

To access the partial DD250s created by VIM-ASAP in Step 14, the user logs in to VIM-ASAP and selects the “Manufacturing” folder located on the left side of the screen, above the Exit link, as shown in Figure 23.

Figure 23. First Page after Login Menu

Selecting the “Manufacturing” folder will display the submenu options shown in

Figure 24.

Figure 24. Drop Down Menu of Manufacturing Folder Tab

The user selects “View/Edit Existing DD250s” to access the screen shown in

Figure 25 and complete the DD250 processing.

Revision 2—December 2011 35

Figure 25. View/Edit Existing DD250s Web Page

Unfinished DD250s can be edited, deleted, or simply recalled and finished. Once the desired DD250 is displayed, the manufacturer must enter the manufacturer’s invoice and shipment numbers to complete it. The manufacturer’s invoice number must be a unique number; VIM-ASAP will not allow invoice numbers that al-ready exist in the system for that manufacturer.

Completed DD250s can be viewed by selecting the desired contract and delivery order and then clicking the appropriate button for the desired DD250. To modify a completed DD250, the user clicks the “unfinish” button associated with that doc-ument. This action restores the “edit” and “delete” options.

“VOID” appears in red on the DD250 until it is finished. This signifies to users that the DD250 has not been finalized. Once the manufacturer clicks the “Finish” button, the “VOID” disappears; the DD250’s shipped date field is updated with the current date, but it is not transmitted to the Wide Area Work Flow (WAWF) until the MSL is finished in Step 16. Once the DD250 has been sent to WAWF, the date transmitted is displayed and the DD250 is no longer available for editing or deletion. A copy of this form will be included in the shipment that corresponds to the completed DD250.

If the manufacturer needs to make a change to a completed DD250, it is much easier to do so if it has not been sent to the wide area work flow, or WAWF; however, there are times when

DD250s can be recalled from WAWF and DFAS. The VIM-ASAP help desk can help users with these special types of recalls.

Revision 2—December 2011 36

Step 16—Manufacturer: Review and Complete MSL

ARN

Step 16 Manufacturer: Review and complete MSL

Equipment and software required for Step 16:

PC workstation and display

Microsoft Internet Explorer version 6.0 browser, or later

Ink-jet or laser printer

VIM-ASAP places every new DD250 into one of the lists of shipments that are organized by ship-from location and destination. The shipping labels (DD Form

1387, Military Shipment Label) are accessed for one or more shipments by select-ing the desired ship-from location and destination.

To access and edit the shipment data, the user returns to the drop-down menu as-sociated with the Manufacturing folder on the VIM screen (see Figure 25). When

“Prepare Shipment Labels” is selected, the screen in Figure 26 will appear.

Figure 26. View/Edit Existing Shipment Labels

The shipping label will have “VOID” stamp in red, indicating it is incomplete.

Once the shipment record associated with the DD250 (which the manufacturer completed) is selected, the user enters the following data to complete the MSL:

Weight. Enter the weight of all containers for an individual shipment label.

Volume. Enter the length, width, and height of all containers associated with an individual shipment label.

Revision 2—December 2011 37

Tracking Number. Enter the tracking number, as identified by the selected shipper.

Postage. Enter the cost of the postage if the package is sent by the U.S.

Postal Service.

Mode of Shipment. Use the pull-down tab to enter the required DLA troop support code.

Shipper. Use the pull-down list to select the appropriate shipper.

After entering all required information, the user clicks the “Generate Label” but-ton to produce the shipping label. This action opens a new window that displays the shipping label for the manufacturer to view. Note it will have “VOID” printed in red across it. If the label is correct, the user clicks the “Finish” button. Doing so will remove the “VOID” and indicate the date printed. The label can no longer be edited once it has been finished. The manufacturer may now print the label to in-clude with the shipment.

The printed MSL is displayed in Figure 27.

Figure 27. Complete and Printed MSL

Revision 2—December 2011 38

Step 17—Upload to WAWF

WAWF

ARN

Step 17 Upload to WAWF

Equipment and software required for Step 17:

PC workstation and display

Microsoft Internet Explorer version 6.0 browser, or later

Ink-jet or laser printer

Once the manufacturer has entered the required data into the VIM-ASAP system, the DD250 and MSL are available for printing so they can be included in the shipment. VIM-ASAP transmits the DD250 data to WAWF at the top of each hour. Once in WAWF, the appropriate Defense Contract Management Agency

QAR electronically signs the DD250 and processes the data to the Defense Fi-nance and Accounting Service for payment authorization. In addition, VIM-

ASAP transmits DD250 data to the appropriate DLA warehouses and the affected recruit training center.

Revision 2—December 2011 39

PROJECT IMPLEMENTATION

In all CDUM R&D and IBIF implementations to date, each manufacturer pro-cured a solution from an outside RFID provider. The implementation described in this section follows that common methodology; however, the manufacturer al-ways has the option of fully implementing an acceptable item-level pRFID tech-nology solution with internal resources.

The sample schedule of key implementation activities is based on lessons learned from past implementations.

The implementation schedule is based on a target “go-live” date, which is the manufacturer’s desired date for when the new item-level pRFID system will be fully operational. The targeted go-live date includes such considerations as pro-duction schedule, contractual requirements, funding availability for capital ex-penditures, scope and complexity of the implementation, conflicts with and impacts on other internal information technology (IT) projects, personnel availa-bility, and other operational factors.

The sample schedule provides the major project implementation tasks with an ass-ociated “no later than” (NLT) date to provide an estimate of when that task should be performed relative to the targeted go-live date:

Identify implementation project team (NLT go-live − 85 days)

Manufacturer preparation (NLT go-live − 85 days)

Create and distribute a request for proposal (RFP) to potential pRFID solution providers (NLT go-live − 50 days)

Conduct RFID solution provider selection (NLT go-live − 42 days)

Finalize and sign contract agreement (NLT go-live − 40 days)

Finalize required equipment (NLT go-live − 38 days)

Order equipment (NLT go-live − 37 days)

Receive equipment (NLT go-live − 7 days)

Install and test equipment and software (NLT go-live − 5 days)

For example, NLT go-live − x days refers to the minimum number of days the task should be completed before the go-live date. NLT go-live + x days refers to the minimum number of days the task should be completed after the go-live date. A NLT time of go-live − 30 days means the task should be completed a minimum of 30 days before the scheduled go-live date; and a NLT time of go-live + 30 days means the task should be completed no later than 30 days after the scheduled go-live date.

Note: Some equipment may have a longer lead time to acquire.

Revision 2—December 2011 40

Initial user training (NLT go-live − 3 days)

Begin item tagging (go-live)

Begin data gathering—collect tag performance, cost, and lead-time data from the new implementation to measure progress and identify areas for improvement (go-live)

Begin resolution of issues as they arise and provide additional training, as necessary (go-live)

Follow-up (NLT go-live + 20 days)

Continue to resolve issues and provide additional training, as necessary

(NLT go-live + 20 days).

The following describes selected key steps in further detail.

Identify Implementation Project Team

The manufacturer should establish a project team that includes personnel from IT, manufacturing, quality, and shipping operations. Many manufacturers do not have the pRFID expertise on their staff to handle the technical issues associated with an item-level pRFID technology implementation. After reading the information pre-sented in this guide, the project team may consider hiring outside resources exper-ienced in item-level pRFID technology to assist in planning and execution of the implementation; however, the use of such services in past implementations has been costly.

Manufacturer Preparation

In preparing for implementation, the manufacturer should collect, prepare, and review the following information:

Contract requirements for non-pRFID item-level technology, and pRFID case and pallet marking and labeling. Data collected should include the in-formation that must be printed in human readable and barcode formats.

Non-pRFID item-level technology process.

Tag and label size and placement and requirements. Placement of

RFID tags and labels may need to be modified from current non-pRFID tag placement to achieve acceptable tag and label read rates.

Tag attachment method. Attachment method of the current hang tag may need to be modified to ensure the item-level pRFID tag is at-tached in such a way as to ensure the tag stays on the item until issue.

Revision 2—December 2011 41

The current production volumes and surge requirements for the items pro-duced and tagged.

Documentation of the manufacturing process that would be affected by item-level pRFID technology, which should include both material flow and interfaces with supporting information systems.

Any key metrics and measures of performance that are important to the manufacturer.

Use of current pRFID technology at the manufacturer (i.e., case and pallet pRFID labeling) including the current contractual requirements for case and pallet labeling and volume and surge requirement of cases and pallets.

Any exception handling procedures or requirements that may affect the item-level process. These exception handling procedures may be the result of quality audits, QAR inspections, etc., and they may require the manu-facturer to remove an item from a case or a case from a pallet after the item-to-case or case-to-pallet association has occurred.

The information technology systems that support production, inventory management, quality, shipping, etc., most notably the function of each system and its interface with other systems and processes;

the software platform on which the system resides (SQL, Microsoft

Excel, COTS software package, etc.);

and data elements and formats used for file transfers between systems and report files.

Manufacturer information technology system capabilities and any planned future corporate updates or changes…