Time Change...Time For Change...EDI Modernization

Posted by Brad Loetz on Mar 6, 2015 1:41 PM


This weekend it is time to spring ahead for many of us...time change.  It also usually means spring is just around the corner, but with 6 inches of snow outside the window we in the upper mid-west have our doubts.

This change of time not only means spring is on the way and the approach of another season, but it also means at least a weeks worth of resetting our internal clock...dragging out of bed and into work, and out of work to home, and then to bed.  Each season we change time it requires that we change our routine a bit to get rid of the fog associated with the process since the status quo is disrupted somewhat. 

Similar to the "fog" you might experience with the time change, movement from the integration status quo timechangehas created some fog for many of those that have gone through EDI modernization.  Fog in the form of fear, anxiety, change, risk, and reputation often clouds EDI and integration modernization initiatives.  In some instances the fog prevents modernization attempts, for others the fog is just something to deal with on the road to increased EDI, B2Bi, and file exchange efficiencies.

Last week at InterConnect in Las Vegas we heard the story of a Remedi client that made the journey from GENTRAN Mainframe to IBM Sterling B2B Integrator...the highlights and lessons learned.

Why make the change?

  • General upgrade in technology
  • Reduce costs
  • improved functionality
  • Simplify support for users and IT

What specific product features impacted their software choice?

  • Handles all communication in addition to EDI- ESB
  • Maintains detailed transaction history
  • End-to-end visibility of all communication transactions and processes
  • Guaranteed delivery
  •  Configurable using built in BPM and objects
  • Allows re-sending of documents or re-running processes
  • Email capable
  • Versatile and easier to use mapping tool

The points above are just a few reasons firms have moved from the EDI and Integration Status Quo.  Some of these may resonate with you and there are likely other use cases, opportunities, or brokenness in your situation where such an initiative would be cost justified.