AI, robotics and crypto, in context Deutsch

Automation

A Custom Automation System Makes You Its Only Customer

A system built for one company fits its process exactly. It also leaves that company alone with every future fix, update and spare part. When custom is worth it, and how to buy it without getting trapped.

A Custom Automation System Makes You Its Only Customer

A mid-sized food producer commissions a custom line that weighs, packs and labels products in formats no standard machine handles. A logistics company has a specialist firm build its own routing software because no package fits its mix of contracts. Both systems work well for years. Then the engineer who wrote the control logic leaves, or the builder is sold, and a small change turns into a project nobody can quote.

This is the hidden side of custom automation. A system built for one company fits that company's process exactly, which is its whole point. But it also means the company is the system's only customer. Every bug fix, security update and compatibility change has exactly one party to pay for it.

None of this argues against custom systems. It argues for buying them with that position in mind, from the first decision to the last spare part.

When custom is the right call

Standard products have large advantages. They are tested by many users, updated by the vendor and supported by a market of people who know them. A custom system has to beat that on fit. It usually does so in three situations: the process is unusual, the process is a real competitive edge, or the volumes and speeds involved go beyond what standard products manage.

There is also a middle path that is often overlooked. Many needs can be met by configuring a standard product and adding a small custom piece at the edge. A standard warehouse system with one custom interface is far easier to keep alive than a warehouse system written from scratch. Before commissioning a full build, it is worth asking which part of the requirement is truly unique.

What being the only customer means

With a commercial product, a bug found by one customer is fixed for all of them. With a custom system, a bug is found and paid for once, by you. The same applies to changes forced from outside: a new operating system version, a discontinued component, a new regulation or a changed interface at a supplier or customer.

Knowledge is the other weak point. In a commercial product, many engineers understand the code and many technicians know the machine. In a custom system, that knowledge may sit with two or three people at the builder's firm. If they move on, the company owns a system that works but cannot be changed with confidence.

Security is part of the same problem. Industrial controllers and custom software connected to the company network need patches like any other system. With a commercial product, the vendor watches for weaknesses and ships fixes. With a custom system, someone has to be paid to do that watching, or nobody does it.

A custom system fits your process perfectly on the day it is delivered, and from then on its upkeep is yours alone.

Build it from standard parts

The best protection is to keep the custom part as thin as possible. On the hardware side, that means common controllers, drives and sensors from established manufacturers, rather than exotic or self-built electronics. Spare parts can then be bought from more than one source, and many technicians already know how to work with them.

On the software side, it means mainstream programming languages, widely used frameworks and databases, and documented interfaces between components. A system written in a rare language or tied to one developer's private toolkit is hard to hand over. Asking the builder which parts are standard and which are their own invention is a fair and revealing question.

Standard parts also make a later change of builder possible. If the control logic runs on a common controller, another integrator can read it, adjust it or move it to newer hardware. A one-off circuit board designed by the original builder leaves no such options.

What to secure in the contract

Most of the protection against lock-in has to be agreed before the build starts. Afterward, the buyer has little bargaining power. A sound contract for a custom automation system usually covers:

  • A written specification of what the system must do, agreed before development and updated with every change.
  • Acceptance tests, both at the builder's site and after installation, with criteria fixed in advance.
  • The source code, control programs and the tools needed to build and load them, delivered with every version.
  • Documentation that a third party can work with: wiring diagrams, lists of inputs and outputs, interface descriptions and operating manuals.
  • A list of spare and wear parts with sources and expected lifetimes.
  • The right to have the system maintained or modified by others, including another firm, if the builder cannot or will not do it.
  • Training for the company's own staff that goes beyond basic operation.

Some buyers also use escrow, where the source code is deposited with a neutral party and released if the builder fails. That helps, but only if the deposit is kept current and someone has checked that it actually builds.

Acceptance tests deserve particular care. A test at the builder's site shows that the system meets the specification under controlled conditions. A second test after installation shows that it works with real products, real data and the company's own staff. Tying payments to both tests gives the builder a clear reason to finish the details that are easy to postpone.

Budget for the years after

The purchase price of a custom system is often the smaller part of its cost. Over its life come maintenance contracts, changes to follow the business, operating system updates and security patches, and the replacement of parts that are no longer made. Controllers and industrial computers in particular often stay in service longer than their manufacturers support them.

A realistic plan sets aside an annual budget for upkeep and names an internal person who understands the system well enough to judge quotes for changes. It also reviews, every few years, which components are approaching the end of their support. Replacing one module on schedule is far cheaper than an emergency rebuild after a failure.

Designing the system in modules with clear interfaces helps here as well. A modular system can be renewed piece by piece over many years, while a single tightly connected block often has to be replaced all at once.

Questions and answers

Is a custom automation system more expensive than a standard product?

Usually at purchase, and often over its lifetime, because the owner carries all maintenance and updates alone. It can still be the cheaper choice if a standard product would force costly workarounds or cannot reach the needed speed. The comparison should cover the full life of the system, not only the quote.

How long does it take to build a custom automation system?

It varies widely with size and complexity. A small custom station or software module may take a few months, while a full production line or a large business system can take a year or more. Time spent on the specification at the start usually shortens the project overall.

Can a custom system be connected to our existing machines and software?

Usually yes, provided the existing systems offer documented interfaces or standard industrial communication. Older equipment may need adapters or gateway devices. The connections should be part of the specification and the acceptance tests, because they are a frequent source of delays.

What happens if the company that built our system goes out of business?

That depends on what was secured in the contract. With source code, tools, documentation and the right to have others work on the system, another firm can take over, although it will need time to learn it. Without them, the company may be left with a system it can run but not change.

Who should maintain a custom system on our side?

At least one internal person should understand the system well enough to handle routine issues and to judge proposals from outside firms. In larger companies this is often a small team in engineering or IT. Relying entirely on the builder works only as long as the builder stays available and fairly priced.