Your EDI Resource

On-Premise, Hosted or Web-Based EDI – Which is the Right Fit?

Thu, Jul 02, 2015 @ 12:16 PM / by Shandra Locken

EDI ChoicesPhoto appears courtesy of Dean Hochman.  This week's blog was written by Art Douglas.  Millenia ago, Og went into his cave looking for his deer-antler hatchet.  But alas, he was unable to find it, for he had many belongings, and a very small cave.  After hours of searching, the hatchet was discovered.  Later, Og pondered how he could store the hatchet where it would be easier to find.  At that moment, Og remembered his friend, Kow, who had a very large cave with many chambers.  The two friends struck a deal.  Kow would store Og’s weapons in one of his many chambers, so when Og needed them, he didn’t have to search for them in his own cluttered cave, he knew he could find them in Kow’s cave.  Moreover, should Og wish to share his weapons with others in the community, he only had to notify Kow of the fact, and Kow would share Og’s stuff with whomever Og has allowed.

In this way, cloud storage was born.

We have known The Cloud by different names.  When I was first in the industry, we called it Time Sharing.  More recently we have used the term, Hosted.  Regardless, The Cloud is pretty much a euphemism for Somebody Else’s Computer.

The purpose of this blog is to help you decide if EDI in the cloud is the best choice for your operation, or is there some other configuration that will serve you better.

Let’s begin by looking at the various configurations:

  • On-premise EDI.  Your company owns the hardware and software used to run EDI in-house.

  • Hosted EDI Solution.  Another company has the EDI system running on hardware at their own site, and the platform may be shared with other clients of the host, each client’s data kept separate from the others.

  • Web-based EDI.  Another company has a web site that allows you to read and create EDI documents, which are translated to and from EDI, and received from or sent to your Trading Partners.

Let’s look at three key aspects of each, to determine which model is best for us, or our clients.

  • Cost – both initial and on-going.

  • Expertise & Support

  • Volume

The cost of acquisition of the hardware and software to support in in-house EDI system can vary widely, from a few thousand dollars, to hundreds of thousands, depending on the decisions you make.  Cost is not always a predictor of success, in this case.  And big names don’t always perform best.  When calculating the cost, make sure you include the cost of the database software, networking, the hardware platform, and ongoing support in addition to the initial and continuing cost of the EDI software.  Also, make sure you understand what the initial cost includes, in terms of licenses, scalability, etc., and what expansion might cost you in the future.

For a hosted solution, there should be virtually no acquisition costs.  But expect to pay consultant’s rates for map development.

For Web-based EDI, you will probably not directly interface your application with the EDI system.  Instead, you will re-key all inbound and outbound data into the application, or the Web EDI system.  You may be charged for each data transaction, and for map development for each trading partner.

To implement and effectively utilize your EDI system, someone will have to configure it and create and maintain the mapping and business processes that are required in every EDI system.  For an in-house system, you will need to either hire somebody, or contract with an expert to take care of these tasks. You will also want on-going support on staff, or quickly available.  For a hosted system, or a Web-based system, the host should provide expert help with mapping, and configuration, plus support at a contracted rate.  The hosted cloud solution undoubtedly has staff skilled in many areas, but they may also be engaged helping other clients.

When selecting between the hosted or in-house solution, volume should be considered in terms of the capacity of each site to process the peak number of transactions in a timely manner.  Does the hosted solution have the throughput and storage capacity to handle your traffic level, as well as all the other customers the host services?  Does your own operation wish to invest the money to put together a big enough system to handle your volume?  On the other end of the spectrum, how many transactions do you handle in a day?  A week?  A month?  Are there few enough that the savings of using a web-based service will outweigh the cost of implementing a fully integrated EDI solution?

Og’s solution won’t work for everybody.  And today’s cloud has many features that Kow could never supply.  Carefully consider these, as well as other questions before committing to purchase EDI software, trust your data to somebody else, or step back from a full system for the advantage of the lower entry cost of Web EDI.

Art Douglas has been an independent consultant since 1983, and has been implementing EDI solutions around the world for over 15 years.

Click below to read a case study on how we helped a company with no prior EDI experience become EDI compliant with a complete, integrated on-premise EDI solution.

Click for Print Media Case Study

Topics: EDI integration, EDI Technology, EDI considerations, EDI software, data integration, benefits of EDI, EDI Implementation, EDI basics, EDI compliant, cloud, EDI expense, EDI document, ERP integration, electronic data interchange

Shandra Locken

Written by Shandra Locken

Shandra is the Director of Business Development for GraceBlood LLC.

Subscribe to Email Updates

Lists by Topic

see all

Posts by Topic

see all

Recent Posts