Rachel raises a good point that I personally believe is frequently
overlooked, not just in the EDI arena, but anywhere technology is
applied. Deploying a given technology doesn't necessarily mean that
measureable improvements will even be realized.
It has been my experience that flawed business processes often make
technology deployment more of a challenge than it needs to be. It is
typically more of a challenge to get people to take a step back and
look at their business processes in an objective manner, often harder
yet to convince them of the necessity and validity of doing so before
deploying any technology.
Brian Richardson
Highlander Technologies, Inc.
> -----Original Message-----
> From: Electronic Data Interchange Issues
> [mailto:[EMAIL PROTECTED]]On Behalf Of Rachel Foerster
> Sent: Wednesday, June 14, 2000 8:33 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Request for Cost Justification Studies To Support The
> Adoption of EDI
>
>
> William,
>
> Notwithstanding the rosy picture painted in the article you referenced
> below....nor other cost/benefit projections that have been published over
> the years, one cannot cost justify EDI. The benefits are achieved
> ONLY when
> you integrate data interchanges at every step of the supply chain COUPLED
> with business process improvements. My personal opinion is that what
> oftentimes are pointed to as benefits of EDI are actually
> benefits realized
> as a result of business process improvements.
>
> This topic has been discussed ad nauseum over the past several
> years with no
> hard, documented, substantive data being brought forth.
> Everything is based
> on projections, estimates, and "what we plan to achieve."
>
> Rachel
>
> > Adoption of EDI
> > --------------------------------------------------------------
> > -----------------
> >
> > Matt Jillings, of PaperFree, is preparing "a cost
> > justification document
> > detailing the cost savings to be realized from the adoption
> > of X12 EDI."
> > He wants "some actual case studies, including the statistics on cost
> > savings, and which factor in and detail the associated costs of
> > hardware, EDI translation software, consulting, VAN charges,
> > etc, etc.."
> > He wants more detail than the typical "Executive Summary" provides.
> >
> > Dear Matt:
> >
> > By coincidence, Dave Darnell, of Systrends, Inc., asked
> > pretty much the
> > same question last month. But I've seen no answers on EDI-L. Are
> > cost-justification studies something that people always talk about but
> > never do?
> >
> > You might be able to find meaty detail on EDI cost justification by
> > looking at past issues of the Journal of Electronic Commerce (formerly
> > EDI Forum), at http://www.faulknergray.com/ecommerc/jec.htm. Every
> > self-respecting EDI professional should have at least one or
> > two issues
> > of this journal on their desk, even if they've never cracked it open.
> > It demonstrates seriousness and depth. You can find article
> > samples at
> > http://www.faulknergray.com/ecommerc/re2000.htm, and a
> > complete list of
> > all Journal articles at http://www.faulknergray.com/ecommerc/ebks.xls.
> >
> > Also, the article "Business-to-Business EC Activity in Small
> > Manufacturers," by Jonathan A. Morell, Ph.D. and Mark E. Brown, Ph.D.
> > reprinted from The Journal of Electronic Commerce Volume 12, Number 2,
> > 1999, is available at http://jamorell.com/ECOTS_article/article.html.
> > Of special interest will be the section entitled "Cost
> > justification for
> > integrated EDI."
> >
> > But cost justifying EDI involves a lot of work, what with
> > estimating the
> > costs of business process integration and VANS and translators and
> > staffing and training, balanced against the expected benefits
> > of on-time
> > delivery and greater customer satisfaction. Why not take
> > the easy way
> > out? Get the CEO on a plane. He (and I say "he" only because men are
> > more gullible than women) is sure to read the in-house
> > airplane magazine
> > which has all the answers to EC. It will certainly hype XML.
> > Then when
> > he comes back from his trip, he'll demand that XML be implemented
> > because it is free over the Internet, doesn't require
> > translators and is
> > easy to read and understand. And do this now, costs be damned.
> >
> > CEOs suspend their usual bean-counting conservatism and
> > skepticism when
> > it comes to XML. These are the same folks who'll toil countless hours
> > poring over spreadsheets working out how many working men and
> > women need
> > to be laid off in order to justify the next round of
> > management bonuses.
> > Regardless how this offends your notion of how the world should work,
> > get over it: you should use XML hysteria to your advantage. Agree to
> > move the company to XML and put any price tag you want on the
> > project -
> > it will be approved in any case.
> >
> > Then do what you needed to do in the first place: buy a
> > translator (but
> > call it a "B2B exchange system"), productivity tools, negotiate with
> > trading partners, map documents, reengineer processes, contract with a
> > VAN (but remember - it's now called an "eBusiness Hub"), etc. etc. I
> > know this sounds like hard work and is a money sink, but remember: you
> > have an unlimited budget.
> >
> > The only thing left is to gussy up this real business solution in XML:
> > take the EDI that we all know and love, and place it in something like
> > XEDI wrappers, described at http://www.xedi.org/, and voil�,
> > you're XML
> > enabled! If you don't like XEDI, there are other wrapper
> > proposals - it
> > doesn't really matter which one you use. If you think this is a silly
> > and roundabout way of implementing EC automation, remember that it
> > worked for RosettaNet on their first go-round.
> >
> > William J. Kammerer
> > FORESIGHT Corp.
> > 4950 Blazer Memorial Pkwy.
> > Dublin, OH USA 43017-3305
> > (614) 791-1600
> >
> > Visit FORESIGHT Corp. at http://www.foresightcorp.com/
> > "Commerce for a New World"
> >
> > ==============================================================
> > =========
> > 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/
>
> =======================================================================
> 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/
>
=======================================================================
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/
