I looked at the link Leah provided, and unless I missed something, it seems
the Wal-Mart RFID article was centered on item level tagging and not
shipment level tagging.
In some informal discussions with some retailers and some suppliers to
retailers the usage of RFID tags on cartons and pallets was not that useful.
I will say the distinction was trading partners who order & ship pallets,
especially those who have assigned GTINs to pallets, do see some usefulness;
however in a pick & pack environment the ROI is more elusive. Since the
subject matter of this list is EDI I will limit these ramblings to EDI
To address Todd's questions:
* Any opinions on where this is heading?
I assume we are referring to including the RFID tag info in the ASN? If so,
then I would ask exactly what RFID tag # is being put in the MAN segment.
There was a question posed to the group some time ago as to what exactly is
put in the MAN for the RFID. I checked with EPCglobal and GS1-US ad was
told that some UCC employee requested the code be added to X12 because he
thought it would be needed; no user requested it. There was never any
guidance as to what data and in what format the id should be. The question
is does one put the entire 96 bits in the MAN segment, should it be in bit
format (0nes & zeros) or hexadecimal. Should the SSCC or GTIN be
reconstructed from the bit format (remember the check digit in not contained
in the EPC ID. Since there is no defined content and format for the EPC ID
in the MAN then there could be no wide spread use of it to match up with the
physical transport unit.
What is known is the format of the EPC ID, so if the SSCC is on the ASN a
receiving system could read either the 128 barcode or the EPC Tag and
convert it to a format to match with the SSCC contained in the ASN. I don't
see any reason to put the RFID tag # (what ever that may be) in the ASN.
* Will this become standard practice?
I think there are two controlling variables in any standard practice: cost
and ROI (OK just ROI) for all trading partners. One of the reasons that the
ASN coupled with the SSCC and the "standardize" carton label were successful
was the barcode could be used within the supplier's distribution process
with relatively minor cost. In addition the demand side trading partners
were able to develop more sophisticated receiving processes based on the
fact a critical mass of their suppliers were willing to participate because
they also realized benefit from the process (other than simply compliance).
Until it gets to the point where the costs of the tags comes way down and
there is a critical mass of suppliers participating I doubt it will become a
standard practice. Just look at CPFR and Data Synchronization; both good
ideas but made too hard and costly by the industry "standards".
* Will the ASN still be used to give the buyer advanced notice of the
shipment and it contents for planning and visibility?
Yes or the Dispatch Advice. I don't see any organization swapping out their
EDI for XML unless there is some serious ROI, but there are places where XML
des make sense; it's a tool like anything else.
* Can the combination of the ASN and RFID help in the "Secure Supply Chain"
concept?
Assuming your definition of Secure Supply Cain and mine are the same; No not
directly. Where I see RFID and security meeting is in the transportation
arena more from a container / trailer viewpoint. RFID tags on containers
and trailers can provide monitoring of environmental conditions within the
container and intrusion alerts, including shock, light (cutting a hole in
the container), and door movement. In addition sensors coupled wit active
tags can be read at speed and distances that will accommodate reading
containers on moving trains in the 100 mph range. So knowing the ASN
contained within the container will provide the details. I think you will
see more use of RFID in the cold chain area, but not related to the ASN.
James D. Sykes II
Argolis, Inc.
1740 Pine St.
Martinez, CA 94553
[EMAIL PROTECTED]
Cell: 01.510.502.3333
[Non-text portions of this message have been removed]
...
Please use the following Message Identifiers as your subject prefix: <SALES>,
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Job postings are welcome, but for job postings or requests for work: <JOBS> IS
REQUIRED in the subject line as a prefix.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/EDI-L/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/EDI-L/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
