Stupid and very sad EDI story:
Few years ago a small Canadian company in grocery importing business was
forced to implement EDI with their major retail customer. The company
decided at the same time to also modernize their computer systems to better
meet the demands of EDI. In a year (after paying some penalties) everything
was in place: New computer, new ERP system, new EDI software, Orders, ASN's,
Invoices and Shipping Labels flawlessly integrated. They went live, but EDI
orders stopped coming. Apparently retailer's system send all the orders to
the primary vendor of each product. The new EDI system was sitting idle. A
year later the company also found out that their new ERP system (from a
vendor, which is now filed bankruptcy) was not Y2K compatible. Cost of
upgrading the software was high, and because the company was already badly
in red, they decided to file bankruptcy. A happy note to the story: the
retail chain is now also out of business.
Vesa Lindell
Group West Systems
E-mail: [EMAIL PROTECTED]
-----Original Message-----
From: William J. Kammerer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 07, 2000 1:55 PM
To: [EMAIL PROTECTED]
Subject: Stupid EDI Stories
I am collecting Stupid EDI Stories for my magnum opus on electronic
commerce. Or if I never get around to writing it, then at least I can
spread the stories around the office for a few laughs. As an example,
here is a contribution from an EDISIM fan at a trucking company:
The human element still rules. One of our major customers, who
shall remain nameless, is a heavy user of EDI. We receive Load
Tenders (204s) from them and are supposed to accept or reject
hauling the load via a 990. The idea is that they can track
accepted and rejected loads as one measure of performance. But
to avoid an unfavorable rating, their customer service reps
instruct our people to never reject any loads via EDI. Instead,
we call them and the rep withdraws the tenders for any loads we
don't want. Thus we (and our rep there) always come out perfect
on the loads accepted report.
I'm sure it wouldn't be hard to find many similar examples of people
circumventing the intentions of EDI. Would you mind sharing your
favorite stories of egregious EDI practices? Though I would appreciate
knowing the companies involved, you can rest assured that I will keep
their real identities secret.
Does anyone really think that XML will solve these sort of problems?
William J. Kammerer
FORESIGHT Corp.
4950 Blazer Memorial Pkwy.
Dublin, OH USA 43017-3305
+1 614 791-1600
Visit FORESIGHT Corp. at http://www.foresightcorp.com/
"Commerce for a New World"
=======================================================================
To signoff the EDI-L list, mailto:[EMAIL PROTECTED]
To subscribe, mailto:[EMAIL PROTECTED]
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
=======================================================================
To signoff the EDI-L list, mailto:[EMAIL PROTECTED]
To subscribe, mailto:[EMAIL PROTECTED]
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
