Case Studies

Avoiding MEGO (My Eyes Glaze Over)

Todd Herman

MEGO. You've experienced it — we all have. It sneaks up on you. You're talking with a technology-savvy colleague, who breaks into geek talk, and you think, "I am not understanding a word he says! Maybe I'll just fake it and nod knowingly." But you can't really fake it — your eyes betray you. That's a common reaction — My Eyes Glaze Over, or MEGO.

This month's e-update features a case study involving a lot of great technology! But I don't want MEGO to happen to you. So, I've tried to construct this case study to feature only enough "behind the scenes" technical stuff to help tell the story.

Distilling the Essence of a Project 


And the story is really about how our consultants jumped in the foxhole (see: In the Foxhole — THA e-update November 2009 ) with our client when no one else would. Not their system vendor, not their value added network provider, no one.

Once a project is completed and presented in a case study format, it all seems so tidy and simple — that's only because someone worked very hard to distill its essence. To really appreciate just how hard this project was, take a look at the lettered graphics. Imagine trying to write the rules and translations to create Item B, having only a few instances of Item A and Item C. Looking at all the bits and bytes is tedious. Developing the logic and program code to reliably and consistently generate them is even more so.

So when the case study says "The final specifications documents were iteratively developed by trial-and-error", understand that at least 5 iterations were required to develop each specifications document — and over 74 specifications documents were created during this project.

Never Forget the Purpose

While our consultants are comfortable immersing themselves in a project's technical details, they never forget our purpose — to get business results by using technology and improving processes, as practiced for over 20 years. Our consultants work hard to avoid inflicting MEGO on client personnel, by minimizing geek speak and technical jargon.

Oh — the technology we developed to automatically receive, parse, translate, and interface inbound EDI transactions (and similarly handle the outbound transactions) is really cool, too. Explaining that would most definitely cause MEGO, so I'll spare you.


Todd L. Herman

Todd L. Herman

Read more on the benefits of an EDI (Electronic Data Interchange) project

Case Study: Incorporating EDI Documents and Automated Processing into an ERP System


This not-for-profit organization provides contract warehouse and distribution services for a large agency of the Federal government. While this organization was implementing a new ERP system, the agency informed our client it was changing its method of sending information electronically, from an outdated proprietary method to an XML-based EDI method.


This change was a requirement for our client to keep this contract, and the deadline imposed was extremely short. Neither the ERP software vendor nor the Value Added Network (VAN) provider for the EDI service was willing or able to work with our client to develop the required software, interfaces, and EDI definition documents. Furthermore, the agency was responsible for developing its own EDI specifications, and these specifications were still in development at the deadline specified for our client.


The biggest challenge to be overcome in meeting the agency's deadline were the constantly changing EDI specifications — and having up to 33 parties involved on behalf of the agency only compounded the challenge. Nonetheless, we worked with our client to:

  • Obtain the best available specifications from the agency,
  • Develop the XML-based specifications documents to support these,
  • Repeatedly receive and process test EDI transaction, and
  • Compare these results against source documents provided by the agency.

In short, the final specifications documents were iteratively developed by trial-and-error.

We also developed the software to automatically receive, parse, translate, and interface inbound EDI transactions into the main ERP system. This software also works in a similar manner to package outbound transactions from the ERP system into the agency's appropriate EDI document format.

Diagram with rows labeled Agency, VAN, and Organization has boxes describing EDI routing processes with arrows showing routing processes order.

The flowchart, above, shows the process, document, and systems flow among the organization (our client), their VAN provider, and the agency (their customer). Everything begins with a transaction begun in the agency's business system, which then translates it into an EDI document, routed through the VAN, and received and interfaced through the INBOUND processing. Once the transaction has been interfaced into our client's business system, their personnel process the transaction, which then triggers the OUTBOUND processing.

One of the key outbound transactions is a "Warehouse Shipping Advice" and the transformation of it from screen-based document (Item A) to XML document (Item B) to EDI document (Item C) is shown, below. Colors are used to cross-reference information during the transformation.

Item A graphic, which illustrates the screen rendering of the waehouse shipping advice shows the transaction details displayed in four modules - trading partner, warehouse shipment ID, party ID, and date/time - each identified by a unique color hand.

Item B graphic showing the xml code for the warehouse shipping device.

Item C graphic illustrating the electronic data exchange coding the organization sends to the value added network provider.

Results & Benefits...

Beyond the most important benefit of meeting changed requirements for its largest customer, our client achieved many advantages from implementing EDI for this Federal agency, including:

  • Automatic receipt and processing of inbound documents — This eliminates human errors and procrastination from the process.
  • Immediate visibility of orders to process — Real-time knowledge of items to handle enables better scheduling and improves on-time shipment performance.
  • Enhanced transparency and accountability — Information is now available to routinely evaluate performance against contract requirements and work to become "best in class" among peer vendors.

The organization's Executive Director noted this was a large and important project, and its benefits certainly justified the time and effort put into it.


Our client achieved many benefits from implementing EDI with a Federal agency, and they are now planning to extend this to their commercial customers to gain the same efficiency and effectiveness from inbound and outbound EDI documents.


Take the Poll
What was the level of "geek speak" in this month's e-update?

Too much — MEGO set in.
Just right — thank you!
Not enough — I want more!
Current Results


For More Information...

To discuss how technology usage and business process improvements could be applied to the issues facing your business, call us at 336.297.4200 to schedule a no-obligation consultation, or click here to contact us online.

Popular Case Studies

Applying Technology to Reduce Unbilled Charges

Accession Inventory graphSometimes, brute force gets a job done. Sometimes, a little finesse is all it takes. Other times, you need to combine the two to accomplish your goal!

Investing vs Spending

AvaCare-screen-shot-v4What's the difference "investing" and "spending"? From the perspective of current cash outlays, nothing is different - yet, taking the long view, there's a great deal of difference.

Deliver Major Cost Savings by Using Technology and Improving Process

Read how this fast growing company partnered with Todd Herman Associates, and found short-term and long-term cost savings through technology and process.

Making Reports Useful: A Case Study

Read how a CIO found a profitable innovation idea in the way the business delivers lab reports.

Activity Versus Achievement

Establish Accountability and Evalutate Results

The Wall of Knowledge

Clarifying Business Needs

Ending the Spreadsheet

Managing Job Costs and Timelines

Tip of the Iceberg

Delivering Meaningful Information to Executives

"Culture" is a Verb

Redefining "The Hottest Topic in Business Today"

Category:Leadership Relationships

Start transforming your business and yourself by signing up here:


Business Book Reviews

Need more resources for growing your business? Get great business book suggestions from Todd.

Leadership Lessons to Take to the Pool

Image It Doesnt Have to be Crazy at Work(June 2019) Do you believe books on leadership have to be heavy, in both tone and weight? If so, these three books should convince you otherwise.


Good Things Come in Small Packages

Putting Your Employees First(June 2018) You've likely heard the phrase "Good things come in small packages." You might also wonder "How does that apply to books?"


A Picture Is Worth a Thousand Words - 2017 Summer Book Reviews

thebackofthenap (June 2017) Is a picture truly worth a thousand words? Todd's annual summer book reviews cover four books that have helped either hone thinking skills by using doodles and simple drawings, or spark ideas for improving doodles or other visuals.


Nothing Changes Until Somebody Feels Something

Whoever Tells The Best Story Wins(June 2016) Hugh MacLeod of Gapingvoid Art gave Todd inspiration for this summer's book reviews when he said "Attach emotion to logic and anything is possible" — A common thread in the four books Todd reviews.


Free Range Staff — 2015 Summer Book Reviews

Leadership and the One Minute Manager book cover(June 2015) Todd describes his idea of how to develop "Free Range Staff" — Employees who can take an idea, develop and run with it with little or no supervision — as he reviews four books he uses to teach and develop his staff.

Interested in reading past case studies? Visit the Case Study Archive.

Todd Herman Associates


620 Green Valley Road
Suite 104
Greensboro, NC 27408

About Todd Herman Associates

Todd Herman Associates is a business technology consulting firm focused on non-routine technology issues such as replacing QuickBooks, getting two systems to "talk" to each other, shrinking process cycle time, and taming large volumes of data.