A single failure of your Delphi or Access software can turn into the most expensive production downtime of the year in a matter of minutes.
Many production systems have been running on Delphi or Access applications for years, reliably controlling machines and delivering data to ERP or MES. But this stability is deceptive: in many cases, these are systems that have grown over decades.
Risks remain invisible until it is too late. A failure of production software does not just mean IT problems. It directly jeopardizes delivery capability, product quality, and the entire value chain. It is therefore crucial for production managers to be aware of these risks and actively manage them.
According to the ABB study «Value of Reliability,» unplanned downtime costs German industrial companies an average of EUR 147,000 per hour. A two-hour outage can quickly result in costs in the hundreds of thousands or even millions, depending on the machinery, production value, and product line. If your production is down for 10 hours, the cost would be approximately EUR 1.47 million. That’s just for the outage itself, without follow-up costs such as scrap or delays.
Robert Schmuck, CTO soxes AG
Delphi and Access applications were often developed for stable processes, not for dynamic production environments. As soon as interfaces to ERP or MES become unstable or a faulty update is installed, the entire line can come to a standstill.
Such downtime causes high production downtime. Depending on the industry and production volume, each hour can mean losses in the five- to six-figure range.
A production stoppage is expensive, but the follow-up costs are often even higher. If an Access application that transfers production data to the ERP fails, incorrect or missing entries occur. This leads to manual corrections, special transports, and overtime.
In modern production systems, automated testing and monitoring ensure that incorrect data or process deviations are detected immediately. This level of security is lacking in old Delphi or Access systems.
An incorrect parameter, an incomplete data record, or an interface error can render entire production batches unusable. This not only means high material and disposal costs, but also direct damage to the trust of customers and auditors.
Today’s production systems are closely linked to the supply chain. If data from a Delphi or Access application is not reliably transferred to the ERP or MES, the entire delivery planning process is thrown into disarray.
This can result in delayed deliveries, contractual penalties, or even the loss of important customers.
Further development is often only possible with great effort, if at all. This creates a competitive disadvantage: while other companies are digitizing and optimizing their production, your own system remains static. Competitiveness declines and costs rise.
The number of experts who are proficient in Delphi or Access is dwindling. Every adjustment takes longer, costs more, and depends on a few individuals.
When a developer leaves the company, valuable know-how is left unsecured. Without targeted knowledge and documentation, there is a risk of complete standstill as soon as a small adjustment is necessary.
soxes is your partner for legacy software support and combines Delphi expertise with .NET, Python, PostgreSQL, and cloud solutions for companies from various industries.
Production downtime can lead to direct losses in the six-figure range.
A lack of further development blocks innovation. While competitors use data to optimize processes, your systems remain static.
Outdated software jeopardizes certifications such as ISO 27001 or industry-specific standards (e.g., GMP in the pharmaceutical industry).
Young developers don't want to work with outdated technologies. If there is a shortage of skilled workers, your company will remain dependent on a small number of experts.
Instead of ignoring these risks, we recommend a structured risk check. This will give you a clear analysis of your production software and a plan of action for the coming years.
You reduce risks, ensure the stability of your production, and gain time to implement a planned modernization based on .NET, Python, cloud, or modern ERP/MES interfaces.
Lucerne-based Striebig AG has been a global market and technology leader in vertical panel saws for decades. Its sawing software, directly connected to the machine, has run on Striebig saws for 12 years and was built on code maintained mainly by a single developer.
Critical business software needed guaranteed support for around 15 years. Striebig faced typical legacy risks: knowledge concentrated in one person, poorly documented components, an exactly reproducible Delphi environment, and tests dependent on physical machines near the PLC.
Rather than a rewrite, soxes carried out a clean handover. It rebuilt the complete development and build environment and recovered the source code until it compiled and launched reliably. Every module and dependency was documented, and everything moved into a version-controlled repository.
Striebig can now rely on a functional development environment, a documented list of build dependencies and traceable compilation steps. An initial risk assessment means the application is technically traceable and controllable for years to come.
How can I avoid downtime in production?
Can an Access database be integrated into a modern ERP or MES?
How long can a Delphi or Access application still be operated?
How much does it cost to modernize production software?
Which modules should be modernized first to reduce downtime?
What security vulnerabilities are typical in old Delphi applications?
When does switching from Access to SQL Server pay off?
Who provides maintenance and support for old Delphi applications in Switzerland?
Identify hidden vulnerabilities before they cause costly production downtime.
Sofia Steninger
Solution Sales Manager
We are ISO 27001 certified:
