In discussions with customers and interested parties, we are observing this more and more clearly: Interfaces – i.e. the ability to connect systems with each other – are no longer a “nice-to-have”, but a key criterion when choosing software solutions.
Whether managing directors or dispatchers – many are specifically looking for a solution that fits seamlessly into their existing IT landscape. This is less about individual functions or price differences and more about openness and compatibility.
What is an interface?
An interface (technically: API) is the connection between two systems. It ensures that data is exchanged automatically – for example between an ERP system and a construction machinery management system such as SAM or RAM.
Instead of transferring information manually (e.g. via Excel or double entry), it flows automatically to where it is needed.
A concrete example from practice
A construction company has been using an established ERP system for years, which is central to project controlling.
If now additionally SAM is also used as a digital solution for machine and project management, the full benefit is only realized when both systems communicate with each other.
A central advantage in SAM is, for example, the automatic cost center allocation via geofencing & telematics.
When a machine is on the construction site, the operating hours are automatically assigned to the relevant cost center.
Thanks to an interface to the ERP system, these hours can be automatically booked correctly, processed further or invoiced directly – without manual rework.
Why is this so important?
Numerous digital applications are used in everyday construction work, for example to manage machines and equipment or to map commercial processes in ERP.
If these systems are not connected to each other, media disruptions occur:
Data has to be maintained twice, errors creep in and processes become unnecessarily time-consuming.
The ability to integrate systems via APIs is now the decisive criterion for many companies when choosing software.
In part 2, we share our practical experience: Which systems are most frequently requested? And why do many providers fail at precisely this point?
