I was tasked to check out the feasibility of doing inhouse EDI, as the 3rd party costs are getting out of hand.
In doing web searches on the subject, there is a lot of info about the various documents types and formats and creating them from XML or database files. This looks pretty straightforward. However, I don't see much on the subject of the server to server communication.
The question is, what does it take to set up such as server? I am looking for a 3rd party component that I can run on a Windows server as a server (I see it like as IIS server which just sits there and waits for incoming connections and then does the handshake and accepts the file.) The only thing I have found so far is that MS BizTalk server includes EDI capability.
I have also found Edidev.com which has an AS2 server which looks like it might fit the bill.
I am completely new to this area, and don't want to miss anything important.
Answer
There are many different options available when talking about EDI.
The primary components involved in an Full EDI Setup include, a Translation Tool, a Job Scheduler, a Managed File Transfer (MFT) Solution, and a Server.
Now, what most EDI professionals, primarily EDI Oustourcing Companies want the public to believe is that is setting up your own In House EDI solution is extremely difficult and will cost an arm and a leg.
Granted, some outsource options out there really do cost an arm and a leg like Gentran, GXS Open Text, IBM Sterling, and the other mainstream EDI Service providers out there. Others like Liaison, 1EDI Source, and the like are quite a bit more cost effective and have various different support packages out there including cloud based solutions.
The overall truth of the matter though, and getting back to the original point on setting up your own In-House Solution, is that everything that these EDI Service Providers provide can be done In-House at a fraction of the cost. There are open source solutions, free cloud services options, or off the shelf software that can be installed, implemented, and integrated for use with your business systems.
The cost in this scenario is the In-House EDI Specialist to run, maintain, and implement new relationships with your newly built EDI Solution.
One example solution: Open Source Solution
(Free to download, install,& use)
Translation Tool - MFT Solution - AS2 Server
[ Bots EDI Translator - Waarp MFT - OpenAS2 Server ]
bots.sourceforge.net/en/index.shtml
sourceforge.net/projects/waarp/
sourceforge.net/p/openas2/wiki/Home/
There are many other options out there that can be pieced together and customized to fit your specific business needs.
EDI simply defined is the translation and transmission of electronic business documents from one company to another.
The Translation tool is simply taking one data field from one file and putting in the predefined field on the other file.
The Managed File Transfer is the GUI you want to use in order to view transactions, resend transactions, manually download previous transactions, etc.
The File Transfer portion is simply setting up the communication settings between your company and the company you want to send/receive the file. Can be configured as FTP, SFTP, AS2, or even email distribution lists.
I am the former Business Manager of one of those 3rd Party EDI Service Providers, and was amazed at how the industry was able to trick the users into thinking that EDI was so complex and hard to implement, maintain, or even understand.
I am still in the EDI Industry, and currently work as the Business Analyst for a Manufacturing Company doing, you guessed it, In-House EDI.