Buyer resource
Integrator vs OEM vs In-House: Who Should Do Your Automation Work?
Use the OEM when the work is inside their machine and their standards. Use your own engineers when the work is routine, recurring and within current capacity. Use an outside integrator when the work crosses machines or disciplines, needs skills you do not want to keep permanently, or when your team is busy running production. Most plants need all three, allocated deliberately.
Published · Last reviewed by Geek Engineering senior engineering review.
The three options compared
| Option | Best for | Strength | Risk |
|---|---|---|---|
| Machine OEM | Changes inside one machine, warranty work, OEM-standard upgrades | Knows the machine and its code best | Slow or expensive for small changes; little interest in line-level problems |
| In-house engineers | Routine changes, recurring support, plant standards | Knows the process and people; available every day | Capacity: projects compete with keeping production running |
| Outside integrator or engineering firm | Line integration, migrations, new equipment, multi-discipline projects | Brings specialist skills and capacity for a defined project | Knowledge leaves with them unless documentation and code ownership are contracted |
Fixed price or time and materials
Fixed price is appropriate when the scope can be defined: a drawing package, a defined migration, or a machine built to a settled specification. Time and materials is appropriate when the work is discovery-led, such as troubleshooting, project recovery or work on an undocumented system where the scope cannot honestly be known in advance.
A fixed price quoted against an unknown scope is not lower risk. It is the same risk with contingency added and less visibility into how it is spent. A common compromise is a paid discovery phase on time and materials, followed by a fixed price for the defined build.
Protecting yourself with any outside party
- Contract for unlocked source code and native drawings, delivered to you
- Require a functional specification you approve before programming
- Tie payment milestones to FAT and SAT results, not calendar dates
- Agree a support model for the first 90 days after acceptance
- Keep one internal owner who attends design reviews and keeps the documentation
Staff augmentation versus project delivery
Some plants need extra engineering hours under their own direction; others need a defined outcome delivered. Staff augmentation keeps control and risk with you. Project delivery moves responsibility for the result to the supplier. Be explicit about which one you are buying, because the contract, management effort and accountability differ.
Key takeaways
- Allocate work to the OEM, in-house team or integrator deliberately.
- Use fixed price for defined scope and time and materials for discovery.
- Contract for code and drawing ownership with any outside party.
- Decide whether you are buying hours or an outcome.
Related questions
Why does the OEM charge so much for small changes?
OEMs are organized to build and ship machines, not to make small site changes, and they carry warranty and liability for their design. Small changes interrupt that model. An integrator or in-house engineer is often faster for changes outside warranty, provided you have the unlocked code.
Will modifying an OEM machine void the warranty?
It can. Check the warranty and support terms before changing code or hardware, and ask the OEM to approve significant changes in writing. After warranty, the bigger risk is undocumented changes that make the next support call harder.
What is a paid discovery phase?
A short, separately priced phase where an engineer inspects the equipment, code and documentation and produces a defined scope, risk list and estimate. It turns an unknown scope into a quotable one and is usually cheaper than the contingency a blind fixed price would carry.
Prefer to talk this through?
Send a short brief — objective, equipment, timeline — and a senior engineer will respond with questions and an honest fit assessment.
Get a Quote