Category Archives: EDI and B2B Integration

Partner Setups and an Internal Contact with Your Provider

This blog post is the fourth part of a series highlighting the best practices for EDI-as-a-Service in planning and evaluation.

As you go about the implementation of an EDI-as-a-Service solution, knowing partner setups and determining an internal contact with your provider at the start of the implementation can save you a lot of time effort and frustration in the long-run.

Understanding partner setups, changes and how long they take

When onboarding new partners and implementing new transactions, a common complaint is that the process takes too long. Sometimes changes that should take minutes, take days or weeks. How can the expectation be set that a change sometimes isn’t instantaneous, but may take longer? Continue reading

Choosing EDI-as-a-Service and TCO

This blog post is the third part of a series highlighting the best practices for EDI-as-a-Service in planning and evaluation.

As past entries in this series pointed out, determining if EDI-as-a-Service is right for your business, and which provider solution makes the most sense, requires some careful consideration. Two very important caveats are to be sure to choose a solution based on requirements instead of provider capabilities, and approach your selection with a broadened view of total cost of ownership (TCO).

Pick EDI-as-a-Service for Requirements, Not Provider Capabilities

When EDI-as-a-Service offerings initially became available, “on-network translation” were the provided capabilities which hosted on Value Added Networks (VANs). Data format flexibility was minimal due to limited EDI translation options, where direct integration with enterprise applications and data resources could be offered, but came with a large price tag for the customization. Continue reading

Work to Predict Future Needs and Lifecycle Framework

This blog post is the second part of a series highlighting the best practices for EDI-as-a-Service in planning and evaluation.

As we discussed in the first post of this series, there are more deployment options to consider to most effectively and efficiently manage your EDI. It’s important to fully understand these alternatives before making a decision.

Take Inventory of Current and Future Needs
If you’ve decided that EDI-as-a-Service is best for your business needs, it’s important to think about what your current needs are and future needs will be in order to most accurately assess what services you require.
Continue reading

EDI-as-a-Service and If It’s Right for Your Business

This blog post is the first part of a series highlighting the best practices for EDI-as-a-Service in planning and evaluation.

EDI-as-a-ServiceWith more and more options than before for EDI, it’s important to know options come with positives and negatives in order to evaluate before making a decision.

One offering on the market is called EDI-as-a-Service, also known as EDI outsourcing or EDI managed services. What this service does is enable delegation of Electronic Data Interchange (EDI) to an outside service provider for provisioning, implementation and management activities. By utilizing a third party, businesses are able to focus on other activities while the provider can produce results rapidly while avoiding common errors. Continue reading

Modernizing EDI: The Difference Between Classic EDI and Modern EDI

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:

Classic EDI Versus Modern EDI

Classic EDI Versus Modern EDI

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