Today’s EDI is very different from what it was 10 or 15 years ago. When many companies made their last EDI technology investments, they were not facing the challenges they face today as they fill a supplier or intermediary role in the B2B value chain. They must support new shared processes, transactions, document types, and communication methods, all while meeting more stringent service levels.
Partner-driven and IT-driven integration changes are also propelling a wave of modernization. “Classic EDI” translators are being replaced by “Modern EDI” integration solutions, due to radical changes in internal business processes, on-premise and cloud (SaaS) applications, and new platforms.
Classic EDI refers to the exchange of standard electronic document types, with syntax and semantics defined by standards organizations, principally X12 and EDIFACT. Like Classic EDI, Modern EDI also embraces standard EDI document interchanges, but in addition, supports the interchange of non-standard, proprietary documents, mostly based on flat file, XML, and spreadsheet syntaxes.
But the differences between Classic and Modern EDI go beyond support for new document types:
Modern EDI reflects the increased diversity of partner, application, and service interfaces present in business environments today. That diversity imposes new requirements on EDI systems, including support for connections that combine applications, services, and data resources in powerful end-to-end business processes. Continue reading