Two different purchases wearing the same name
A standard PLC and HMI integration is a control package assembled from choices someone else already made. The controller family is fixed, the input and output mix is fixed, the screen layout follows a house template, and the program logic follows patterns that have run before on machines of that class. You are buying proven work: the sequences, the interlocks and the screen behaviour have been exercised somewhere, and the quotation is firm because very little is still open.
A customized PLC and HMI integration starts from your process instead of their catalogue. The input and output count follows your sensors and actuators, the safety chain follows your guarding, the screen follows the language and the sequence your operators work in, and the program follows the cycle you actually intend to run. Quoting it means quoting design hours, not just hardware, and the price moves with how much of your process is unusual. That is not a sign of a worse supplier. It is the price of the engineering being done for the first time, for you.
The trap in the comparison is reading both as "control system included". Same line in the quotation, same photograph in the brochure, entirely different allocation of work, risk and future option.
What each route puts on the table
In a standard package the engineering content is already paid for and closed. The supplier decides what the control can do; you decide whether that is enough. The enquiry therefore centres on fit: does the published input and output count cover the machine you are actually installing, does the safety chain match the way your guarding is arranged, does the screen show the values your shift needs to see, and can the machine talk to the station upstream and downstream without a translation layer nobody priced.
In a customized package the engineering content is the deliverable. On the engineering-services route the enquiry starts with requirement analysis, then scheme design, mechanical structure and electrical control, then prototype manufacturing, testing and verification before the line is handed over. The control design is not an attachment to that chain; electrical schematic design, the PLC and HMI program, motion control, sensor integration, cabinet design and the safety control system are named as part of the work, and the program is written for the machine you specified rather than adapted to one that already exists.
That is where the comparison turns. The standard route asks whether your duty fits a design that exists. The customized route asks what your duty requires of a design that does not exist yet, and puts engineering hours against the answer.
Where a ready-built control package earns its price
Choose the standard package when your machine sits inside the envelope that package was built for. The honest signals are simple: the standard input and output set covers your sensors with margin to spare, the standard motion arrangement drives your axes in the way they need to move, the standard safety arrangement matches how your guards and access points are placed, and the standard screen shows what your shift needs without a rework.
Where it pays back is in everything that is not on the invoice. Because the logic has run before, the failure modes are known and the supplier can answer a fault question from experience. Because the hardware mix is repeatable, the spare parts you will need in year three are already catalogued. Because the program is stable, the training material already exists. A standard package on a machine that fits it genuinely is a lower-risk, lower-cost purchase, and there is no virtue in commissioning bespoke control for a duty the standard one handles.
The obligation you take on is fit-testing. Nobody at the supplier will prove that your process sits inside their envelope. You have to do that, on your product and your materials, before the order.
When the machine is outside that envelope
The standard route stops working at a recognisable list of points. Your sensor set is wider than any standard input card covers. Your axes have to move in relation to one another in a way the standard motion arrangement does not coordinate. Your guarding, access and wash-down arrangement force a safety chain that the standard one cannot reproduce. Your station has to handshake with an upstream or downstream machine on signals that do not exist in the standard interface. Your product changes between runs and the changeover needs recipes, per-cycle records and named faults that a template screen does not carry.
Then the customized route is not a preference, it is the only route that reaches your duty. In a whole-line or non-standard build the control is designed alongside the mechanics rather than bolted onto a finished frame, and that is also the case where one team carries mechanical, electrical, automation, test and project work instead of the buyer stitching three contractors together.
The obligation you take on here is specification. A customized program can only be as correct as the description you supplied, and the description has to be written down while there is still time to change the machine.
The comparison line by line
| What you are comparing | Standard, ready-built package | Customized package |
|---|---|---|
| Who decided the control architecture | The supplier, on a previous project, already closed | A designer, working to your requirement, still open at enquiry |
| What the enquiry has to contain from you | Enough detail to confirm your machine fits the published envelope | The process itself: sequence, interlocks, product variants, acceptance |
| How firm the price is | Firm, because the design work is finished | Firm only after the requirement is fixed; earlier it is an estimate |
| What changes at your request | Screen labels, parameters within the exposed range, option modules on the list | The sequence, the safety chain, the recipe structure, the record set |
| Who can change the program later | Usually the supplier, because they hold the only working copy | Negotiable, and it should be agreed in writing before build |
| What proves it works | Reference machines and a factory run on their arrangement | A test and verification stage written into the delivery chain |
| What you own afterwards | A working machine and a supplier dependency | A documented design, if the documentation was bought |
The last row is the one buyers under-weight. A standard package can still be the right buy, but it leaves you owning a machine whose behaviour you cannot change without the supplier. A customized package can leave you owning that same dependency, or owning the drawings and program instead, depending entirely on what was written into the order.
Ownership of the program, and what you do with it
The question that separates a good control purchase from a bad one is rarely technical: who holds the program, and who is allowed to change it after acceptance. Ask both routes the same set of questions. Does the delivered set include the electrical schematic and the panel layout, or only the terminal schedule. Does it include the program itself, in an editable form, or only a machine that runs it. Which faults are named on the screen, and can your engineers add to that list. Who may change a recipe, and does the change get logged. If a controller fails at two in the morning, can a replacement be commissioned from drawings you hold, or must the original supplier attend.
On a standard package the answer is often that the design is closed and support runs through the supplier. That is a legitimate commercial position, but it has to be visible to you before you sign, because it sets the cost of every future change. On a customized package the answer is yours to shape: the engineering is being created anyway, and buying the record of it is a small addition compared with commissioning an undocumented machine.
Whichever route you take, ask for the change boundary in writing: what you may edit yourself, what voids support, and how the program version is recorded when something is altered. A machine with no version record is a machine nobody can troubleshoot reliably.
What you have to supply before either quote is real
Both quotations depend on input that only you have, and the quality of that input decides which route you can actually buy. Write down the cycle in words, station by station, including what may fail and what the machine should do when it does. List every input and output with its signal type, because the input and output count is the single most common place a standard package quietly falls short. State the guarding and access arrangement, since the safety chain is what you cannot retrofit cheaply. Name the neighbours on the line and the signals each one needs to send and receive. Describe the product variants and how a changeover is supposed to happen, since changeover is where control work concentrates.
Then state how a machine is judged fit. A factory run on your own material, watched by a named person from your side, against an acceptance criterion agreed before the build rather than after, is worth more than any clause in the specification. A customized package makes that test straightforward, because the test and verification stage is part of the delivery chain. A standard package makes it awkward, because you are testing fit against somebody else's design intent and you need to know in advance what the machine was ever meant to do.
Questions to have answered before you sign
- Does the published input and output set cover my machine with spare capacity, and what does an added point cost?
- Which of my sequences, interlocks and recipes already exist in the program, and which would be new work?
- Is my safety arrangement inside the supplier's standard safety chain, or does it need a designed safety circuit?
- What signals pass between my machine and its neighbours, and who designs and tests that handshake?
- Do I receive the electrical schematic, panel layout, terminal schedule and program in editable form?
- What am I permitted to change myself, and what ends the support arrangement?
- Who tests the machine, on what material, against what acceptance criterion, and is that stage inside the price?
- Which parts are expected to wear or fail, and can a replacement controller be commissioned from documents I hold?
Where the answers to those questions come back thin, you are not comparing two prices; you are comparing two kinds of exposure. Send the cycle description, the input and output list and the acceptance criterion through one route and make the answers answerable: the non-standard automation equipment route is where a designed control package is quoted, and the integrated engineering team services route is where mechanical, electrical and automation design sit with the same team instead of with three contractors. If your machine is a cleaning or wash unit, the customized steam cleaning equipment enquiry route reaches the same engineering desk. Read what comes back against the list above. A supplier who returns a requirement analysis and a scheme design is quoting the customized route; a supplier who returns a catalogue page is quoting the standard one. Both can be honest. Only one of them is a comparison of the same purchase.
