EDI is, by just about any definition, a “mature” information technology. It has a long history, with origins in the planning in the Berlin Airlift, and was used in civilian businesses since as early as 1971, when London’s Heathrow airport started to use it for cargo management.
Most major sets of EDI standards, encompassing different industries (automobile manufacturing, health care, etc.) date back to the 1980s. Because EDI is so well-established, it’s not uncommon for an IT department, tasked to implement and, perhaps more important, maintain a company’s EDI system, to mistakenly believe that the job is almost completely about installing software, maintaining the internal network, and troubleshooting technical issues regarding data exchange with partners.
Because those tasks are, in fact, always time-consuming and often urgent, it’s up company leaders, including the CIO (or the company’s de facto equivalent), to make sure that the bigger picture is understood. And this bigger picture is that EDI is in service to the company’s business, and more specifically, one-to-one partnerships. Figuring out the IT department’s role and responsibilities for building and cultivating business relationships can be daunting, especially because working with many companies and individuals can be much more difficult to manage than code and data.