[EDI-L Mailing List Archive Home] [Message List] [Reply To This Message]

Re: TDCC and EDI X12

From: "R.T.Crowley" <rcrowley@...>
Date: Fri Nov 14, 2003  1:34 pm
Subject: Re: TDCC and EDI X12
It appears the listserv cut my post in half. The rest of it is shown below:

> TDCC is an international freight standard, with documents specific to each
> mode of moving freight: Rail, Motor, Air and Ship.

No, this one is wrong. The Transportation Data Coordinating Committee (TDCC)
standard is actually the original publicly published EDI standard. It was the
first. It was international only in the sense it could be used by
international freight carriers, but was primarily developed, starting with the
US railroads, as a domestic US EDI standard long before X12 ever existed. The
TDCC itself was founded in 1968, and published the first EDI standard in 1975.
As was mentioned by Mike Rawlins in another message, however, the TDCC
standards were merged into X12 in the late 1980s. The organization itself then
changed its name to the EDI Association (EDIA), struggled for a purpose for a
few years, and then went out of business. The so called "TDCC Standards"
actually no longer exist, but the term is often used to refer to the
transportation transaction sets maintained under X12.

> I have never fully understood the reasoning for UCS "a competing US standard
> to X12", at the core it is basically identical in structure to X12 and can be
easy
> confused for it if you don't know what to look for. I don't see it much
anymore
> which leads me to believe it's slowly going the way of the Edsel.

The Uniform Communication Standard (UCS) is quite alive a well, although one
tends not to see it unless one works in the retail or grocery industries. It
is a part of the Uniform Code Council (UCC) work. As the EDI part of the
products we get from UCC, the things found in UCS are more an implementation of
X12 standards than standards in and of themselves. The UCC is also the
official body for the barcodes we see on retail products throughout the United
States.

> Rather than getting into a long drawn out class, I will take a few moments to
> describe X12 in more detail. In the X12 world "as is the same in most others"
> we keep track of the changes to documents by version and a best example of
> this was the year 2000 and the introduction of the 8 digit date CCYYMMDD.
> Version 003071 had a date format that was YYMMDD, this was modified to
> reflect the new date format CCYYMMDD and version 003072 was born.

Close, but not quite. The version release numbers are simple. Let us look at
004010 and 004032 for examples. ANSI requires us to do a new version every
five to seven years. We have been working in version four, so the first part
of the number is 004, allowing the leading zeros for the future when we get to
version 121 or something. Then we make a new release each year, so the second
part of the number is 01, again allowing a leading zero in case we ever have to
issue a release 13 or something. We make three sub-releases each year after
each meeting; after the October meeting we do the primary release for the
following year with a 0 designation, after the February meeting we do
sub-release 1, and after the June meeting we do sub-release 2. Therefore
version release 004010 is actually version Four, release One, sub-releases
Zero; and 004032 is version Four, release Three, sub-release Two. When
speaking the name of the version/release, we often omit the first two zeros,
calling it something like "forty-twenty" for 004020.

> Now you asked about specifically about VICS, there are numerous industries
> and business that have created their own versions based on the original X12
> documents and standards to meet their specific needs. So it is not that
unusual
> to see versions like 002001FORD, 002003CHRY, 002003GM and 004010
> VICS. I'm still waiting for 005010WALMART to come out. I'm not sure what
> VICS stands for but this document is heavily modified for the grocery
industry.

The acronym stands for Voluntary Interindustry Commerce Standards (VICS), and
its secretariat is the Uniform Code Council (UCC). In its own words, VICS
"establishes cross-industry standards that simplify the flow of product and
information in the general merchandise retail industry for retailers and
suppliers alike." In practice, VICS is the convergence point for work on EDI
implementations for the retail industry when cross-industry communication is
involved.

George wrote:
> I am confused about the relationship between X12 and other EDI standard
> associations for example, TDCC, CIDX, PIDX, or VICS.

Just to finish this out, the other two organizations in the original post are
the Chemical Industry Data eXchange (CIDX) and Petroleum Industry Data eXchange
(PIDEX). These are industry groups developing implementation guides for their
respective industries based upon X12 standards.

As I said at the beginning of this, there are a LOT of EDI organizations of a
lot of different types out there, and it can be a VERY confusing world, even
for those of us with multiple decades of experience with it. I hope this
helps.

Best Regards,
Bob

R.T.Crowley - Senior Vice President

Research Triangle Software, Inc.
Suite 200
1135 Kildaire Farm Road
Cary, NC 27511

Tel: +1-919-657-0505
Cell: +1-919-349-3557
Fax: +1-919-657-0589
Web: www.rtseducation.com
www.ediassistant.com
www.cryptobuddy.com
www.rtsz.com

-- KBO --


[Non-text portions of this message have been removed]




 
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools Simplify EDI Data Integration with Stylus Studio XML Enterprise Suite - Free Download!
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2007 All Rights Reserved.