Re: is edi translator software difficult to write? was: edi vendor complaining

["jde iSeries" <jde.iseries@xxxxxxxxx>]

Steve Richter,
Why write your own EDI X12 translator?  My gentle recommendation is that you
and your organization should focus on being the best widget builder that you
can be (or whatever it is that you sell to your customers), not get
side-tracked.

Don't get sidetracked into thinking you should build your own EDI
translator, or build your own telephone switch, or build your own
automobiles, or build your own water supply system, or build your own
electrical grid, or your own computer hardware, etc.
With the IBM Power6 and the IBM i OS, your total I.T. budget will likely be
less than 1 percent of your annual revenues, even with Inovis EDI and the
other expensive software licenses.   Let's all focus on the reality that the
reality that an organization's I.T. budget is a very small expense when
compared to annual company revenues.

After all, none of us work for Google that builds all of its software
systems on commodity hardware, realizing that no supplier exists that could
provide what Google needs in software anyway, so they have to build their
own stuff.


On Thu, Jun 5, 2008 at 10:40 AM, Steve Richter <stephenrichter@xxxxxxxxx>
wrote:

> is it difficult to write an EDI translator? or port code from Linux?  I
> dont
> follow why so many are locked into the Innovis package.