Let's talk about interfaces

Industry 4.0, digitalization and the networking of things - these terms currently dominate the business world and suggest a paradisiacal future scenario of comprehensive data exchange between all economic players with a myriad of autonomously interacting systems. But the road ahead is long and rocky. Up to now, there has been a lack of communication standards in the interaction between the systems. This is evident in the interface management of software systems. This is where the question of "debt to be discharged" comes into play.

Networked supply chain requires networked systems

In our increasingly complex business world, companies within the supply chain are merging more and more with the structures of their suppliers and customers. As a result, internal and cross-company processes must be planned and operationally controlled at the software level. The value contribution that IT makes to companies is therefore higher than ever: business processes are based on a complex system of interconnected and interdependent software applications, and their smooth operation is an important factor for sustainable market success.

Smart logistics needs IT

In other words, we are talking about systems that communicate via interfaces. These form the transition between different programs and thus enable the exchange of data - the output of A is the input for B. For this exchange to take place synchronously, the interfaces and data structures of the programs must fit together, they must be compatible. Communication problems are virtually pre-programmed. But which customer hoping for smarter logistics processes for their company by purchasing software wants to open up additional construction sites that are also associated with additional financial outlay?

Interfaces are a sensitive topic

According to a recent study by GMP Munich, the topic of "interfaces" in the context of logistics software is therefore one of the most sensitive of all. When selecting a provider, particular attention is therefore paid to the ability to manage interfaces effectively. The questions to be answered are: "What does this management actually look like?" and: "Who actually has to manage what?" The task of the software provider in this context is to install a functional solution that congruently reflects the customer's wishes. The task of the future user is to be able to deliver data that is workable and resilient in the first place. This is not a matter of course. Very few people think about the fact that the customer himself has to "co-manage" interfaces when implementing new logistics software before making a purchase decision.

The customer must "co-manage"

It is therefore important for customers to know what their own ERP system can do. The required interfaces are sometimes not even planned in the systems. This means that quite a few of them are outdated or not designed for interaction with other systems. A lot of data no longer comes via standard interfaces. Additional segments often have to be built in or even completely new interfaces generated. The customer must therefore prepare himself for the use of the new software. What he intends to do with it in the future is one thing. But the current status is important in order to get started at all.