Steve,

The Natural Gas Industry has been E-Commerce through Internet EDI since 1997
and their requirements are even more strict (15 minute turnaround from PO to
response) that you've indicated.  The Gas Industry Standards Board (GISB)
created the Electronic Delivery Mechanism (EDM), a secure, reliable standard
for transporting EDI (and other files) over the Internet using http file
upload (ref: RFC 1867), PGP for encryption and digital signatures and
positive acknowledgements with transaction ID's. Enron publicly announced
that it did $26 Billion dollars in E-Commerce last year using the GISB EDM
standard.

The GISB EDM standard is one of the foundation standards for IETF EDIINT AS2
and has been used in other industries including Automotive (AIAG adopted
GISB EDM in 1998) and Healthcare.

There was a recent article in an Energy industry publication that talks
about Internet EDI versus the VAN's, it's located at:
http://www.8760.com/ecsr.pdf


Regards,

Dick Brooks
http://www.8760.com/

-----Original Message-----
From: Steve Bollinger [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 17, 2000 4:33 PM
To: [EMAIL PROTECTED]
Subject: RE: The need for speed: XML vs. Internet EDI


Can you recommend some good software for doing this?  What are your
experiences with Internet EDI?

I am a little familiar with Templar from Harbinger.  Who are the
competitors?  Any good reviews comparing the options?  I am open to
reviewing ideas here.

Thanks, Rachel,
Steve

At 03:30 PM 7/17/00 -0500, you wrote:
>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

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


Reply via email to