Business applications
Web or desktop, built around your process.
Services
We write applications built around how you actually work. For 30 years, always in house: no part of the work is subcontracted.
Web or desktop, built around your process.
SCADA, HMI, PLCs and sensors connected to the ERP.
Data moves by itself, without copy and paste.
The missing piece, without replacing what you have.
Six examples, across different industries. The names are absent because not every client wants to appear; the work is what it is.
Vehicle dismantling
The dismantler’s system talks to the parts database, to the warehouse and to the sales channels. Every part removed gets its label and is tracked from then on: which vehicle it came from, where it is, who bought it.
Manufacturing
Production management connected to the company ERP: what happens on the floor reaches the ERP with no manual step, and orders come down to production the same way.
Medical
A portal holding management and production together: the 3D geometry is uploaded, a scan of a limb or a face, and the order is followed through every stage, and the shipment is tracked. Whoever ordered knows where it stands without picking up the phone.
Enterprise systems
Sales enquiries go through a web portal that reads and writes directly on the IBM systems: AS/400 and DB2 on IBM Z mainframe. The legacy system stays where it is and carries on doing its job: only the way you reach it changes.
Industry
Data goes from the ERP to the machines and back: recipes go down to the HMIs and PLCs, Siemens and Allen-Bradley, and production comes up in real time. You always know where each part is, and rejects and faults are recorded as they happen rather than reconstructed afterwards.
Telemetry
Press telemetry and electricity readings collected on the floor and sent to cloud systems. The data arrives on its own, continuously: you see how the plant is working and what it costs while it works, not at the end of the month.
We come to you and watch how you work. Often less is needed than it first seemed.
Architecture, technology and timing. You know what arrives and when, before any code.
In stages, with checkpoints along the way. You see the work as it grows.
Testing, deployment, training. And support continues after handover.
We build on .NET, available today on Windows, Linux and macOS: the same application can sit on a server of yours or on cloud infrastructure, without being rewritten. We build APIs and services, web applications and desktop applications.
We connect to the databases you already run: SQL Server, PostgreSQL, MySQL, MongoDB, Oracle and DB2, and to shop-floor machines through their own protocols: OPC UA, Modbus, MQTT.
You do not wait until the end to see something. It is delivered in pieces: the first one goes into use while the rest carries on, and from there the aim is corrected against what is actually needed. A project you only see on delivery day is one where mistakes surface too late.
It starts with the analysis, which gives you the cost before a line of code is written: you know what you are committing to when you decide, not halfway through. And it is often less than it seemed: the problem as described is nearly always bigger than the real one.
The opposite: the software is built around the process you have. If using a program means changing how you work, it is usually the wrong program. We come and see how you do things before proposing anything.
Yes, and it is the common case. When the system you have does almost everything, we add the missing piece or make it talk to the rest, instead of replacing it. Throwing away something that works is a cost, not a solution.
Yes, and it is the work that pays off most. Repetitive operations, such as retyping data from one system into another, filling in the same documents or collecting figures from machines: are where time is lost and mistakes are made. They are also the easiest to take away.
There is no fixed rule: it can run on infrastructure of ours or on your own servers, if you would rather keep everything in house. It depends on what you need, not on what suits us: and since we work on infrastructure too, we can tell you which of the two makes sense in your case.
Tell us what you need. We will look at how it can be done, with no commitment.