Menu Content/Inhalt
Home
Why is our EDI not standardized? PDF Print E-mail
Written by Mike Kelly   
Wednesday, 16 April 2008

As someone who earns a living in EDI and as an avid blogger, I am excited to begin what I hope to be a long line of interesting and helpful posts within the realm of Electronic Data.  Like yourselves, I have logged several years of "doing EDI" in one capacity or other, and have both the scars and success stories to show for it.  Like most of the EDI relationships I've set up, my posts will probably be "non-standard".   :)

My background is in manufacturing, shipping, logistics and retail;  for the last dozen years, I been consulting in EDI integration or directing others in the same for various clients.  Currently, I'm hanging my hat at a major retailer, in the supply chain group.

Not long ago, I was asked by a client "why isn't our EDI standardized?"  At first I thought this was a rhetorical question, but decided to respond gently as I could see the manager asking me this question was quite serious.  "Well, it is;  at least the maps are built using published EDI standards."

He went on to inquire why it takes so long for the EDI folks to create a relationship with a customer if all of  the maps are standardized (by the way, this manager inherited EDI and had little background in it).  My reply was the standard EDI person's response:

  • EDI maps are standardized, but everyone has their own version of them
  • Customers tend to be less flexible than suppliers in an EDI relationship
  • Setup and mapping can be quick; testing with another party can be excruciatingly slow
  • Setup can be slow if a lot of programming is involved on the backend
  • The larger the organization, the longer the implementation will take

I allowed this to sink in as an eerie silence fell over the room; somewhere in the distance, a dog barked.

To break the silence, I said optimistically "However, once the customers are up and running, they rarely have to be touched again unless one of the trading partners wants to make a change."

Informing me to put together an estimate for customers X, Y and Z, the manager shooed me away.  Customers X and Y were up in a few days.  I think customer Z is still a work in progress...

Many happy 997s,
Mike Kelly, EDI Advocate at www.GotEDI.com


Mike Kelly
About the author:
James M. (Mike) Kelly is President of Global Data Integrators, Inc. (GDI) which specializes in Electronic Data Interchange and Electronic Commerce on the IBM System-i Server. He is an EDI Project Manager and Consultant for SMB to Fortune 100 sized clients. His company has been in business for 12 years, and is a VAR for various EDI and EAI packages. Currently, Mike is working primarily with The Home Depot Store Support Center in Atlanta.

Prior to forming GDI, Mike worked as a Programmer Analyst for a mixture of companies including Mannington Carpets and WORLDSPAN, the information services partner of Delta Airlines also in Atlanta.

In 1996, Mike founded Global Data Integrators for the purpose of providing programming, consulting, and systems integration solutions for Electronic Commerce and EDI. In 2003, he and other partners formed LiquiFile Services, LLC to provide services focused specifically on the petroleum sector for Federal Excise Tax reporting. LiquiFile is one of only four companies certified by the IRS to provide this service.

As a self described “serial entrepreneur”, Mike’s interests extend beyond EDI into blogging, publishing and real estate. He also serves on the boards of various industry organizations and technology user groups. He can be reach through his websites at www.GlobalDataIntegrators.com or www.theITentrepreneur.com

Comments
Add NewSearchRSS
Only registered users can write comments!
 

What's New

Member Login