This has been a great series of discussions and shows the value of this
list server.
I would recommend reading the Computer World article described below:
B-to-B XML Harder Than Anticipated
The travails RosettaNet has experienced in launching its
XML-based business-to-business e-commerce standards
effort could serve as a bellwether for the thousands of
companies that have yet to hit the playing field. But IT
professionals hoping to learn from RosettaNet's example
will have to wait until the fall -- if not 18 months or
longer -- before they'll be able to take stock of one of
the earliest industry efforts.
http://www.computerworld.com/home/print.nsf/CWFlash/000515DF2A
The lessons being learned are the same ones learned 15 years ago when
companies started implemeinting EDI solutions. The obstacle isn't the
technology, its the business issues.
o management and trading partner buy in
o agreement between trading partners on data to exchange
o establishment of standards for transactions
Simply changing the technology doesn't eliminate the business issues.
You could replace "XML" with "EDI" and "RosettaNet" with "DISA" and this
article could have been written 10 years ago.
Keep up the good exchanges. Its valuable.
Doug
-----Original Message-----
From: Shan [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 01, 2000 4:12 PM
To: 'Brad Berendt'; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Software - Objectivity
XML or EDI. The writing on the wall is clear: CO-EXIST
EDI has not ever realized benefits far-reaching; nor has XML brought out
evidence till my writing this mail that it can deliver those benefits
that
EDI failed. Like a 100% process-integrated community. ( Does a need
exist
for one such value is another perspective to look at. In my good old
GEIS
days, I used to never have an answer for: Does a Christmas tree supplier
need to be on EDI at all...)
My point:
Equal thought and discussions need to be focused on the BUSINESS aspect
of
Information exchange within any business value chain. The policies and
business practices in the industries, along with the ROI for any effort,
will determine whether or not any technology can benefit business. The
completeness of a business framework is evolving and will take time to
mature and be attested as a business practice; now add the global nature
of
eBusinesses to that. How will anyone fix without knowing what to fix? Do
we
have an answer for a B2B marketplace that will conduct business by
bidding
in real-time to co-exist with existing EDI Supplier, who participates in
the
eMarketplace as well.
XML or EDI. The business practice to behold them will have to be UNIQUE.
That's the missing piece yet.
Best regards,
Shan
Director, eBusiness Strategy Group
Pinnacle Systems,Inc.
Call:732 981 1400 Press 16
Mail-e: [EMAIL PROTECTED]
Virtual Office: www.pinnacle-sys.com
-----Original Message-----
From: Brad Berendt [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 01, 2000 4:38 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Software - Objectivity
I agree. Has anyone heard the phrase, "if it ain't broke, don't fix
it"?
Many
companies have spent plenty
of money in their current EDI inftrastructure. And guess what? These
are
the
"guts" of many integrated processing
systems today. I believe XML has its strengths and applications but
don't
rule
out good old EDI.
Brad Berendt
Sterling Commerce
District Consulting Mgr - E-Commerce Solutions Microsoft
Managed Services Division
Office: 614-791-5782 Fax: 614-793-7045
Scott Shulman <[EMAIL PROTECTED]> on 06/01/2000 04:26:31 PM
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
cc: (bcc: Brad Berendt/Dublin-ISG)
Subject: RE: Software - Objectivity
People, RELAX. Everyone thinks this XML thing is going to replace this
thing
called EDI, Just because this is the newest buzz word. What happened to
CPFR, That was last year's buzz word. What happened to VMI, That was two
years ago buzz word. We are still several years out before this thing
called
XML takes over the world.
Scott Shulman
Director of E-Commerce
K-Swiss inc
818-706-5203
[EMAIL PROTECTED]
> -----Original Message-----
> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, June 01, 2000 12:31 PM
> To: [EMAIL PROTECTED]
> Subject: Software - Objectivity
>
> Having recently completed a 5 month evaluation process of XML - B2B
> Servers
> and vendors, I have some relevant experience in the process of
selection
> to
> share. We did the following:
>
> * Evaluated vendors according to their industry participation and
> experience (Rosettanet in our case)
> * Met with this subset of vendors
> * Participated in 3 vendors' proof-of-concepts
> * Scored each vendor according to a formal weighted scorecard
> * Considered development plans and schedules
> * Completed a subjective evaluation
>
> The last item, "subjective evaluation" is very important and I would
like
> to
> expand on this. In the fast evolving software industry, products can
> change
> on a daily basis. During our recent evaluations we continually needed
to
> see the "latest" version of a vendor's product. Our "objective"
scorecard
> was likely obsolete even before it was finished. This reality led me
to
> recognize that the "relationship" with a vendor was even more relevant
to
> our needs than the "daily" feature list.
>
> The ability to cooperate in product development, future feature
> development,
> and priorities are more important to our company's B2B e-commerce
success
> than a particular list of features in any given day. A relationship,
and
> channel of communications with a vendor's decision makers is vital.
The
> B2B
> / XML vendor relationship should not be that of buyer/seller, but that
of
> "partner". The B2B / XML solution vendor is a virtual extension of
our
> internal IT department. The vendor who recognizes this and delivers
based
> upon this relationship is worth serious consideration.
>
> 0============================0
> | Kevin Benedict
> | B2B E-Commerce Manager
> | micronpc.com
> | 208-893-1738
> | [EMAIL PROTECTED]
> | "The Process is the Product"
>
> 0============================0
>
>
>
>
> ------ 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 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 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 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 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 join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
