You
make some very good points, but is an SME really going to make that kind of
investment?
He
should to be entirely safe. I was trying to bare bones this analysis in that
as a minimum,
the
components needed were highlighted. In deference to Paul, I think that the
"numbers" especially
in
the area of interface development are low. Fifty dollars per hour is about the
cost of a
mid
level and experienced programmer. An analyst or consultant is going to be more
expensive that
that.
I also assumed that the programmer would probably be a part time resource in
that other
projects
would cross his/her plate.
I
think that "high availability" is an issue in anyone's system that is doing EDI
today if they
want
to be effective. You are right in that B2B just makes it an even higher
priority.
Mark
-----Original
Message-----
From:
Catlin, Phil [mailto:[EMAIL PROTECTED]]
Sent:
Wednesday, October 25, 2000 9:50 AM
To:
[EMAIL PROTECTED]
Subject:
Re: XML for EDI book: Any comments?
Paul...
I
have to disagree...
If
anything Mark has left out some VERY significant expenses. Initiating
B2B
commerce
over the internet also assumes that you have established "high
availability"
in your environment. I define high availability as being
7x24x365
up
time on ALL components of your system. You also need to be staffed
to
support
"high
availability", someone on site or with dial in capability on call
24x7x365.
This
usually involves redundant components such as servers, network
access
points,
routers and disk arrays. Don't forget to include your legacy
systems
here
too! An enlightening question to ask your systems people is "How long
do
we
take for backups each night, and can users be in the (pick your
application)
system
during the backup?"
You
can also be assured that most software is not capable of "high
availability"
in
it's off the shelf configuration, and that making it highly available
will
be
expensive.
This
isn't all bad, but I find it amusing every time I read how this will
lower
the
cost barriers for SME's. That red herring should be permanently
retired!
Phil
C
-----Original
Message-----
From:
"Wakelam Paul (RBAU/LOG)
Sent:
Tuesday, October 24, 2000 8:07 PM
To:
"EDI-L"
Subject:
RE: XML for EDI book: Any comments?
Greetings,
Mark's
costs seem high.
<<SNIP>>
=======================================================================
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/
- Re: XML for EDI book: Any comments? Richard Druckenmiller
- Re: XML for EDI book: Any comments? Catlin, Phil
- Re: XML for EDI book: Any comments? Paul Krikke
- Re: XML for EDI book: Any comments? Andy Sicignano
- Re: XML for EDI book: Any comments? Hurd, Richard A (Rich)
- Re: XML for EDI book: Any comments? J. Glenn Thompson
- Re: XML for EDI book: Any comments? Williams, Ian
- Re: XML for EDI book: Any comments? Rachel Foerster
- Re: XML for EDI book: Any comments? Richard Druckenmiller
- Re: XML for EDI book: Any comments? Richard Druckenmiller
- Re: XML for EDI book: Any comments? Mark Kusiak
- Re: XML for EDI book: Any comments? Rachel Foerster
- Re: XML for EDI book: Any comments? Mike Lemon
- FW: XML for EDI book: Any comments? Eric Moeller
- Re: XML for EDI book: Any comments? Mark Kusiak
- Re: XML for EDI book: Any comments? Wakelam Paul (RBAU/LOG)
- Re: XML for EDI book: Any comments? Rachel Foerster
- Re: XML for EDI book: Any comments? Michael Mattias