A quotation that looks good on paper can still disappoint on the shop floor. The purchase price of electrical control system development usually covers the panel build, the PLC and HMI programs, and the first commissioning trip. What it does not always cover is the next three years: who answers when a machine stops at 2 a.m., who can still open the original project files in 2030, and who pays for the re-engineering work when a line has to be moved or upgraded. Before you sign, the following questions will tell you whether you are buying a control system or an ongoing liability.
1. Who physically supports the machine after handover?
Ask for the maintenance model in writing, not as a promise. A control integrator may offer fully remote support, on-site engineer dispatch, a hybrid of the two, or nothing beyond the warranty window. Each model has a real cost profile. Remote support is fast and cheap when the fault is a logic or parameter issue, but it cannot replace a failed drive, a damaged sensor, or a re-dressed cable harness. On-site dispatch solves the physical failure, yet response time depends on where the engineers sit relative to your plant and whether your country is inside their service radius.
Practical version of the question: "Which of my fault types will be handled remotely, which require a site visit, how fast, at what hourly rate after warranty, and what is the travel cost?" If the answer is vague, assume the worst-case numbers and price the project again.
2. Which hardware platform, and can I buy it from my local distributor?
Control panels are built around PLCs, drives, HMIs, safety relays, and industrial PCs. If the vendor selects a brand with no distribution or service centre in your region, every failed module becomes an import with customs delay. For a manufacturing automation line that runs shifts, a two-week lead time on a discontinued servo drive is not a spare-parts problem, it is a capacity problem.
Ask three concrete things: the exact part numbers for every purchased component; whether those part numbers are in the current product lifecycle (active, last-time-buy, or obsolete); and which regional distributor stocks them. A vendor who can name the distributor is a vendor who has thought about your maintenance reality.
3. What documentation package do I actually receive?
"Documentation included" means different things across suppliers. A usable package for electrical control system development normally contains: electrical schematics and terminal schedules in an editable CAD format, panel layout and bill of materials, the native PLC and HMI project files (not only compiled downloads), a parameter list for drives and motion axes, an I/O list with tag names, a written description of the machine state machine and interlocks, alarm definitions with plain-language remedies, and a factory acceptance test protocol with results.
Two clauses protect you. First, the native editable project files, not just a backup archive, are delivered at acceptance. Second, any program change made during commissioning is written back into those files before final payment. A compiled-only backup can be re-uploaded to the same machine, but it cannot be maintained by anyone else.
4. What are the training and remote-access terms?
Ask who gets trained, on what, and how many times. Your maintenance technicians need a different session than your machine operators: technicians need alarm diagnosis, module replacement, and safe lockout procedure; operators need mode changes, recipe handling, and when to stop the machine. Confirm whether training happens at the vendor site, at your plant, or by video, whether it is recorded, and whether refresher training for new staff is charged.
On remote access, settle the terms before the equipment energises: which VPN or remote desktop path is used, who holds the access credentials, what your own IT policy allows, and whether remote support is billable per incident or under a retainer. Also ask for a local access method — a service port on the panel — so that a plant internet outage does not also disable vendor support.
5. What is the spare-parts and consumable list?
Request a recommended critical-spares list with part numbers, expected service intervals, and unit prices, then buy the short-lead-time, high-failure items on day one. Typical wear items in control work are sensors and cabling, HMI touch membranes, cooling fans and panel filters, relays, fuses, drive batteries, and seals on pneumatic or fluid subsystems. The list tells you what to hold; the price list lets you convert maintenance from an emergency purchase order into planned inventory.
For a customized or single-purpose machine, ask the additional question: which parts are genuinely non-standard and machined for this machine only? Those items have no distributor fallback, so drawings and a spare quantity are mandatory, not optional.
6. How are firmware and software updates handled?
Automation platforms get firmware updates for security patches and hardware compatibility. Ask who decides when to apply them, who performs them, and what rollback plan exists. An untested firmware update on a running line is one of the most common causes of unexplained downtime. Good practice is a documented change procedure: change note, backup taken before work, update applied outside production, function check against the acceptance list, and a known restore point if the update fails.
7. What change-control and upgrade support exists for the machine's life?
Machines rarely stay as delivered. Products change, sensors get replaced, capacity targets rise, and safety requirements tighten. Ask how the vendor prices change requests, whether they support third-party integrators making modifications, and whether the machine was delivered with enough spare I/O, panel space, and program structure to absorb growth. A control design with no spare capacity turns a small product change into a panel rebuild.
If you do not have in-house automation staff, this is also where integrated engineering team services matter. Clarify whether the supplier can stay engaged after delivery for upgrades and troubleshooting, and in what capacity — retainer, per-project, or on-call.
8. What response-time and escalation terms are contractual?
Verbal responsiveness is not a service level. Get numbers in the contract: acknowledgement time, remote response time, on-site arrival time, and the escalation path if the first line cannot solve the fault. Also check the definition of the response clock — business hours or 24/7, your time zone or theirs — and what happens if the vendor is short-staffed.
9. Who owns spare drawings and the right to modify?
Ask plainly: if this vendor is unavailable in four years, can another integrator legally and technically service this machine? The answer depends on file ownership, whether schematics are in a neutral or editable format, whether the vendor holds proprietary blocks inside the PLC program, and whether they charge a licence fee for third-party access. A vendor who refuses all third-party access is selling you dependence; a vendor who documents ownership up front is selling you a system.
10. What does commissioning and acceptance actually prove?
Maintenance quality starts at acceptance. Ask what tests will be run and what records will be produced: interlock and safety-function tests, alarm-trigger verification for each defined alarm, continuous-run and abnormal-condition testing, and a signed issue list showing what remains open at handover. If you receive no test report, you receive no baseline — future troubleshooting becomes guesswork about whether a behaviour was ever correct.
A simple checklist for your next supplier call
- Support model: remote, on-site, or both — with response times and post-warranty rates in writing
- Hardware brand, lifecycle status, and the name of your regional distributor
- Editable native project files for PLC, HMI, and schematics delivered at acceptance
- Training scope for operators and for maintenance technicians, including refresher terms
- Critical spares list with part numbers, intervals, prices, and drawings for non-standard parts
- Firmware and software change procedure, with backup and rollback steps
- Change-control pricing and spare I/O and panel capacity for future upgrades
- Contractual response times, escalation path, and who holds remote-access credentials
- Written test reports and a closed issue list before final payment
Judge electrical control system development by what happens after the machine is accepted, not by the panel photograph in the proposal. The supplier who can answer these ten questions with documents and numbers is the supplier who plans to be reachable when the line stops.
