Hire a freelance automation integrator

Post the job and read proposals from engineers who make separate machines work as one line. Ingenium is the marketplace and holds the contract; the engineer you hire does the integration work.

Post an integration job
The work

What automation integration involves

Integration is the work of making equipment that was bought separately behave as one system — and then proving on site that it does.

Individual machines usually arrive working. A line does not. Each unit comes with its own controller, its own HMI, its own idea of what “ready” means and its own fault handling, and somebody has to decide how they hand product to each other, what stops what, how a jam on the labeller affects the filler two stations upstream, and which single screen an operator looks at. That is line integration: the handshakes, the shared state, the alarms, the mode logic, and the hundreds of small agreements between vendors who have never spoken to each other.

A large share of this work is not new lines but retrofits and migrations. A retrofit keeps the mechanics and replaces the control system: obsolete PLCs whose spares are gone, drives nobody can source, an HMI running on an operating system that has not had a patch in a decade. A migration moves a working program to a current platform — SLC or PLC-5 to ControlLogix, S7-300 to S7-1500 — which is never a straight conversion, because the conversion tools produce code that runs but that nobody wants to own. Both start with reverse-engineering: reading a program with no comments, written by someone who left, to work out what the machine actually requires before anything is allowed to change.

And both are done under a constraint that has nothing to do with engineering: the plant has to keep producing. Work happens during a shutdown window measured in days or hours, often at night, with a tested rollback plan, and with the knowledge that overrunning the window costs more than the whole project. An integrator who asks about the shutdown window and the rollback plan in the first conversation has done this before.

The acceptance sequence is what the engagement is actually judged on. A factory acceptance test, or FAT, runs the system at the builder’s or integrator’s premises against a written test specification, with the client present, before anything ships — ideally with simulated I/O so fault paths can be exercised rather than hoped for. A site acceptance test, or SAT, repeats it on real equipment after installation, which is the first time real sensors, real material and real timing get a say. Commissioning is the stretch in between and after: point-to-point checks, loop testing, dry cycles, product trials, tuning, and then handover with documentation, backups and operator training. Insist that the test specification is written and agreed before the work starts; a FAT without one is a demonstration, not a test.

One thing to be clear about, because the word “integrator” normally means a company. A system integration firm takes contractual responsibility for a working line, carries insurance, holds the safety sign-off and sends a crew. A freelance engineer hired through Ingenium is one engineer on a project you are still managing — frequently the right one, and frequently the most experienced person in the room, but the project management, the safety assessment and the responsibility for the finished line stay with you unless you have agreed otherwise in writing. Ingenium holds the contract and the money. It does not take on the engineering.

Scope

What an integration job usually covers

These are the parts worth naming in a job post, in roughly the order they happen.

Survey and reverse engineering

Reading the existing program, drawings and panels, finding out what is actually installed versus what the documentation claims, and producing a scope that someone can price with confidence.

Functional specification

What the line does, in writing: modes, sequences, interlocks, handshakes between machines, alarm behaviour, and the acceptance criteria. The single document that prevents the argument at the end.

Line integration

Machine-to-machine handshakes, upstream and downstream stops, shared recipes and changeover, a line-level overview screen, and the data the plant needs out of it — downtime reasons, counts, OEE.

Retrofit and migration

Replacing obsolete controllers, drives and terminals, or moving a program to a current platform, with the code rewritten to be maintainable rather than left as a conversion-tool output.

FAT and SAT

A written test specification, a factory acceptance test against it before anything ships — simulated I/O where possible — and a site acceptance test after installation on real equipment.

Commissioning and handover

Point-to-point checks, loop testing, dry cycles, product trials and tuning, then documentation, program backups, as-built drawings and operator and maintenance training.

Tools

Platforms, protocols and documents

Integration experience is specific to what is already installed. Listing the equipment in the job post is what makes a proposal worth reading.

Control platforms

  • Allen-Bradley ControlLogix and CompactLogix
  • Studio 5000
  • Siemens S7-1500 and TIA Portal
  • Legacy SLC and PLC-5
  • S7-300 and STEP 7
  • Schneider
  • Omron
  • Mitsubishi
  • Beckhoff TwinCAT

Supervisory and data

  • Ignition
  • FactoryTalk View
  • WinCC
  • AVEVA InTouch
  • Historians
  • MES interfaces
  • ERP interfaces
  • Downtime and OEE reporting

Networks and devices

  • EtherNet/IP
  • Profinet
  • Profibus
  • Modbus TCP and RTU
  • OPC UA
  • VFDs and servo drives
  • Robots and cobots
  • Vision systems
  • Barcode and RFID

Project documents

  • URS and functional specification
  • FAT and SAT protocols
  • I/O schedules
  • Cause-and-effect matrices
  • Risk assessment inputs
  • As-built drawings
  • Handover packs

Regulated environments

  • GAMP 5 / CSV
  • IQ, OQ and PQ
  • 21 CFR Part 11 audit trails
  • Validated change control

Platform names are what is installed on a client’s site. An engineer’s experience with them is a fact about their history, not a partnership with or endorsement by any vendor. Ingenium does not perform integration, FAT, SAT, commissioning or validation, and holds no certification to do so.

Both sides

Hiring it, and doing it

The same page serves two readers. One is deciding who to trust with a running machine; the other is deciding whether the job is worth a proposal.

What to look for in an integrator

The bar here is not technical fluency. It is whether the person has stood in a plant at two in the morning with a shutdown window closing and made the right call.

  • Experience with the equipment you already have, not only with the platform you are moving to
  • A habit of writing the functional specification and the test protocol before touching code
  • Questions about the shutdown window, the rollback plan and who signs off the safety assessment
  • A migration approach that produces maintainable code, not a conversion-tool dump
  • Honesty about what one freelance engineer can carry and where you need a second pair of hands
  • Clarity on travel, site access, inductions, and whose insurance covers the work
Post a job

If integration and commissioning is your work

Clients read your profile before they message you, and Ingenium requires it to be complete before you can send a proposal or accept an offer.

  • Name the platforms you have migrated between, in both directions
  • Use job history for the industries and the line types — packaging, dairy, pharma, water, automotive
  • Say whether you write specifications and test protocols, or work to the client’s
  • Be explicit about travel, notice, passport and visa situation, and site certifications you hold
  • Skills, resume, job history, education, hourly rate and work schedule are all required before you can apply
  • A client has to open the conversation — an invite to a job, a message, or an offer
Create a freelancer profile
Hiring on Ingenium

How you hire an automation integrator here

Ingenium is a marketplace, not an engineering firm. It does not do the work — it is where the job is described, proposals are compared, and the contract and the money are held once terms are agreed.

Post the job

Describe the scope, the equipment involved and the site, and post it under Systems Engineering. Posting is free. You can also invite a specific engineer to the job, or message one from their profile.

Read the proposals

Engineers who do this work reply with their rate and how they would approach it. Messaging is open from the moment a client starts the conversation, so the scope can be argued out before anyone commits.

Send an offer

An offer sets the payment model and the terms. Fixed price is split into milestones; hourly is invoiced weekly from logged time. The model is chosen when the job is posted and cannot be swapped later. A saved card is needed before an offer can go out.

Run the contract

An accepted offer becomes a contract with a shared work diary, tasks, time entries, comments, invoices and expense claims. Funds are held by Stripe and released when the client accepts the work.

Which payment model fits

Integration is the clearest case for hourly work on this whole site: site time belongs to the plant, a shutdown window moves, and nobody can honestly fix a price on debugging a line they have not yet seen running. Fixed price fits the document-shaped parts — a survey, a functional specification, a migration of a defined program, a written FAT protocol — and those make good first milestones precisely because they are what make the rest estimable. Since the payment model is chosen when the job is posted and cannot be changed afterwards, the usual shape is a fixed-price survey and specification job, then a separate hourly job for commissioning.

The full flow from posting a job to getting paid covers both models and where the money sits in between. Everything a contract carries — time tracking, milestones, messaging, invoices, payouts — is listed on the features page. Or create an account and post the job.

Your next engineer is one click away

Connect with the best freelance engineers and streamline your projects with our integrated management tools.