EDI

Over the past few years, we have seen more and more projects where there has been a requirement to exchange information about goods/products between several different systems.

We experience this especially in connection with projects for our international customers, where the ability to exchange information about the status of an item/product in a secure and standardized way between supplier, customer and carrier has long since been adopted.

A setup around AS2 (Applicabillity Statement 2) is the preferred setup, probably because our customers often have roots in the US, while you often see X.400 for customers in Europe.

Whether it’s AS2, EDIFACT or a completely different standard is basically irrelevant. What is interesting is the ability to exchange information between different parties in an automatic, standardized and secure way.

We are currently working on a project for a customer that involves the exchange of EDIs between many different parties, and with almost as many different EDI formats. But what they all have in common is that they want to get information about a product or service that another “supplier” has – as quickly and securely as possible.

Using standardized EDI formats ensures that information is exchanged both securely and quickly, and that it is relatively easy to implement in the running systems of the individual participants.