Very astute observation. In fact I see Internet VANs eventually becoming central repositories, not only for the passage of EC data for high volume users that handle their own generations and interpretations, but eventually, as we begin to provide more and more OLAP EC services, becoming a sort of timeshare type of environment. We already have requests from companies to not only provide generation and interpretation of EC data, but also storage, and replenishment. We may end up turning thre clock back about 4 decades, but now the high availability and performance of TCP/IP networks will make "timesharing" so to speak, a viable solution for low end users.
 
thanks for the insights.
Mark
-----Original Message-----
From: Ginny Crane <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Cc: richard <[EMAIL PROTECTED]>; XML/edi Group <[EMAIL PROTECTED]>
Date: Tuesday, July 25, 2000 4:13 PM
Subject: RE: VAN's on the run

Folks

Just my two cents worth:

I don't think the VAN scenario will stay around just because of fear or
stubbornness. I think it is because of services and business needs
and economics. There are many, many companies that just do not want to run
their own shops for lack or resources, lack of dollars and the need to focus
on core competencies. In addition, the VANs are implementing EDIINT gateways
that will allow traditional VAN tps to get to their Internet tps and theses
companies do not want to buy their own EDIINT software and/or manage the keys.
VANs are morphing themselves (albeit slowly) into Value Added Internet Service
Providers where a company can still get the level of service and value add
that they require, but now at varying cost models such as all you can eat
monthly subscription fees, ASP services, web forms etc. Don't think just
because XML and the Internet is here to stay that VANs will go away. They
change as do everything else. XML will easily cross VAN to VAN on behalf of
tps who want to pay for SLAs, customer service, outsourcing, mailboxing,
reports simply because they can not or will not do it themselves. Their
business models just don't support it.

These issues are not technical. They are business and economical. Heck,
remember when timesharing was the rage? Well did those timesharing companies
go out of business when the apps moved inhouse? NO!!! They became VANS... Now
that the Internet is giving us a wealth of new technologies, business needs
and economics will reinvent the VANs to provide Value Added Internet services
both from a transport and a chargable services perspective.

Just my input.

Regards,

Ginny Crane
AT&T Internet and EDI Business Manager

____________________ Begin Original Message ___________________________
Date: Sun Jul 23 08:10:46 -0400 2000
From: internet!datatechis.com!scott (Scott T. Meade)
Subject: RE: VAN's on the run
Importance: Normal
UA-Message-ID: <[EMAIL PROTECTED]">[EMAIL PROTECTED]>
To: internet!dial.pipex.com!gk92 (richard)
To: internet!disa.org!xmledi-group (XML/edi Group)
Content-Type: Generic-Text
Content-Length: 2197

I don't think the EDI Van scenario is dead or dieing. There will always be
some companies just out of fear or stubbornness that will refuse to let go
of what has been working for years. Look at the mainframe and COBOL. When I
was in the Air Force in 1985, I was told to stop wasting my time learning
COBOL no one will be using it a year from now. Well here it is 14 years
later and COBOL is still here. XML is a great technology, but people have to
put it to work.

Smeade

-----Original Message-----
From: richard [mailto:[EMAIL PROTECTED]]
Sent: Saturday, July 22, 2000 4:35 PM
To: XML/edi Group
Subject: VAN's on the run


With the XML/Internet messaging lowering the costs of B2B
whats going to happen to the VAN model of charging for service
and message space charges ?

In the UK Britsh Telecom a EDI Van has just scrapped its £10 a month
service charge and replaced it by a £60 month. Is this a message that
EDI is dead for all other than large established EDI traders.

Is it time to get into XML/Internet messaging now before VAN's go
dinosaur ?







------   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
HTML>

Reply via email to