To outsource PLC programming successfully as a machine builder, hand over a written scope (functional spec, I/O list and your coding standard), buy it as a fixed-scope package with a defined deliverable and date, require the software to be tested against a simulation of the machine before FAT, and settle source-code ownership and remote access in the contract. Distance is rarely what makes outsourced controls work fail. Vague scope and code that first runs on the real machine are.
When outsourcing makes sense
Most machine builders keep core controls in-house, and they should. Outsourcing pays off in specific situations: a peak where three machines ship in the same quarter, a customer who specifies a platform you do not staff (a Siemens line for a Rockwell shop, or the reverse), a legacy migration nobody has time for, or a long tail of HMI screens and documentation that keeps your best engineer away from new designs.
The common thread is that the work can be specified. If the machine concept is still changing every week, keep the software in-house until it settles.
What to send with the request
| Item | Why it matters | If you do not have it |
|---|---|---|
| Functional design spec or sequence narrative | Defines what correct means | Pay for an FDS phase first |
| I/O list and electrical drawings | Fixes tags, addresses and hardware | Agree a draft and freeze date |
| Coding standard and libraries | Code matches your other machines | Use the end customer's standard |
| 3D CAD or layout | Needed to build a simulation model | Simpler logic-level testing only |
| Customer specs and standards | Brings in NFPA 79 and site rules | Ask the end user before quoting |
How a fixed-scope package runs
- Discovery call and written scope, schedule and price. Everything not in the scope is a change order.
- Design review: program structure, state model, alarm list and HMI navigation agreed before coding.
- Development to your standard, with weekly progress you can open and read.
- Testing against an emulated controller and a model of the machine, including fault cases.
- Remote FAT: your team runs the test protocol against the simulation, witnessed online.
- Delivery of source code, documentation and test records. Site commissioning by your team or a local partner, with remote support.
Step four is what makes remote delivery work. Rockwell's FactoryTalk Logix Echo is its controller emulator for Logix projects (Rockwell Automation), and Siemens describes PLCSIM Advanced as the basis for software-in-the-loop virtual commissioning on S7-1500 (Siemens Tecnomatix blog). Either way, the program runs against the model exactly as it will run on the machine, and the test record proves it.
Remote FAT and the standards around it
IEC 62381:2024 defines requirements and checklists for FAT, SAT and integration testing of automation systems, and it is a good skeleton for the protocol (IEC 62381:2024). For machines going into U.S. plants, the electrical design still needs to meet NFPA 79, and the software has to support what the design requires, such as stop categories and reset behavior (NFPA 79). Our guide to the virtual factory acceptance test covers the remote part in detail.
How To Choose a System Integrator
Inductive Automation
This video is hosted on YouTube. Playing it loads content from Google, which may set cookies.
Watch on YouTubeContract questions to settle up front
- Who owns the source code? It should be you or your end customer, delivered unlocked, with no know-how protection you cannot open.
- Confidentiality. An NDA that covers your designs and your customer's process data.
- Remote access. How the provider connects, if at all, and who approves each session. Simulation-first delivery should need no access to your network.
- Warranty and support. What happens when a bug appears at site, how fast, and at what cost.
- Change orders. How changes are priced and approved before work starts.
- Who commissions on site. Be clear whether the provider travels or supports remotely.
Start with a small first package
Do not hand a new provider your most complex machine first. Pick a well-understood unit, such as the infeed conveyor and its HMI screens, or the migration of one older machine, and run it through the full process: scope, design review, simulation testing, remote FAT and delivery. You learn how the provider writes code, how they report progress and how they handle a change order. They learn your standard. The second package is always faster, because the hard part of outsourcing is agreeing how the work is done, not the work itself.
Red flags
Credentials help you shortlist. CSIA certification, for example, audits integrators against best practices in ten areas including project management and the system development life cycle (CSIA). Ask any provider for a sample of anonymized code and a sample test record. Those two documents tell you more than a capability deck.
How Wartens USA works
Wartens USA delivers Studio 5000 and TIA Portal programming as fixed-scope work packages or as an engineering capacity retainer, with engineering done at the group's India engineering center and a U.S. company in Dover, Delaware. Software is accepted remotely before your team or a local partner commissions on site. See our controls engineering service, our article on what drives PLC programming cost, and our virtual commissioning service. Send us a spec and an I/O list through contact and we will return a written scope.
