Roger, the reason why I said the VAN appeared to be the bottleneck was in
the description of the problem provided by Steve, to wit:
"Currently our EDI (via VAN) takes about 5 minutes (could possibly be
trimmed) to deliver to the VAN and about 5 minutes for the VAN to deliver to
the trading partner. Problem is that the VAN only guarantees one hour
delivery. This makes the time to TP a possible 1 hour 10 min instead of the
usual 10 minutes. This ruins the 1 hour support and cuts too deeply into
the 2 and 4 hour service. Even 10 minutes cuts deeply into a 1 hour
delivery promise."
I know that some VANS can provide realtime or near-realtime delivery without
mailboxing, but that is not how the problem was described.
Rachel
-----Original Message-----
From: Roger Trout [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 19, 2000 8:46 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: The need for speed: XML vs. Internet EDI
Rachel: I am not certain I understand why you believe the van is the
bottleneck.
We have not experienced this problem in our XML-based work. If there is a
problem that you have identified I would certainly be interested in
investigating (dont know who the van is so this is immaterial to Sterling
per
se). Hope all is well with you. Roger
"Rachel Foerster" <[EMAIL PROTECTED]> on 07/17/2000 04:30:35 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: (bcc: Roger Trout/Sterling Commerce)
Subject: RE: The need for speed: XML vs. Internet EDI
Steve,
I don't think the formatting of the data is relevant in your example.
Whether it's EDI or XML doesn't make a difference. It seems to be the real
bottleneck is your VAN. Why not just use the Internet to send EDI rather
than going through the VAN?
Rachel
-----Original Message-----
From: Steve Bollinger [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 17, 2000 1:20 PM
To: [EMAIL PROTECTED]
Subject: The need for speed: XML vs. Internet EDI
Hi All:
I would like to know if anyone has done any actual benchmarks in this area
of comparing the speed of XML to EDI on the Internet. Is there anything
inherently faster/slower about XML?. I am not talking just transmission
speed, but point to point (DB to DB).
We are working on sending messages to satisfy service requests, some of
which are very fast turn around: 4hrs, 2hrs and soon to come 1hr. That is
from the time the request is committed to our database until the time the
replacement part arrives at the customer's site (scope: worldwide). As you
can see from this, time is of the essence. We would like to see a 60 second
or less turn around in message delivery. 20 - 30 seconds would be great.
That is the time from our DB commit to the time the message arrives at the
remote shipping depot - which is run by a third party carrier that
warehouses our parts. Protocol: HTTPS.
Time includes: triggering the send, extracting the data, mapping the data,
encryption, sending, receiving into the DB at the other end.
Currently our EDI (via VAN) takes about 5 minutes (could possibly be
trimmed) to deliver to the VAN and about 5 minutes for the VAN to deliver to
the trading partner. Problem is that the VAN only guarantees one hour
delivery. This makes the time to TP a possible 1 hour 10 min instead of the
usual 10 minutes. This ruins the 1 hour support and cuts too deeply into
the 2 and 4 hour service. Even 10 minutes cuts deeply into a 1 hour
delivery promise.
I don't expect transaction size to be an issue. Typical EDI transactions
are around 1K. Even with a 50-to-1 verbosity ratio sending 50K is not a big
deal. Current benchmarks on our file transfers is 11 seconds per meg.
Thanks for any real world data you can send me or ideas you may have on
this.
Steve Bollinger.
Steve Bollinger 408-853-8478
Cisco Systems B2B Service Logistics Pjt
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
