Robot integration projects: scope, acceptance and the ramp nobody budgets

Write a specification about your process, not their machine

Weak specifications describe equipment; strong ones describe the duty. State the part range with drawings and tolerances, the condition parts will arrive in, how they will be presented, the required rate including allowances for changeover and stoppages, the utilities available, the environment, the interfaces to upstream and downstream equipment, and what the cell must record. Include the awkward cases: the variant only ordered occasionally, the material that behaves differently in humidity, the rework part that comes back round. Anything omitted becomes a variation order later, priced without competition, at the point where you have no bargaining power.

Scope boundaries where projects actually fail

Draw an explicit line through the grey areas: services brought to the cell and their final connection, foundations and floor preparation, guarding and its safety assessment, integration with existing controls, network addresses and cabling, removal of what was there before, and the software interface to plant systems. Say who supplies parts for testing, how many stages of testing there are, and who pays for the material consumed. Also name the responsible party for the finished assembly under machinery safety law in your jurisdiction, because when a plant integrates equipment from several suppliers, that duty can land on the plant itself.

Acceptance at their works and acceptance on your floor

Testing at the builder's factory proves function on their bench with parts you supplied. It cannot prove rate on your material, in your environment, with your operators. Split acceptance accordingly: a functional test before shipment covering safety functions, sequences and fault handling, then a performance test on site over a continuous production period long enough to expose intermittent problems. Define the site test in advance — the parts, the duration, the measured quantities, what counts as a stoppage, what happens if it fails — and tie a meaningful payment stage to it. A test that runs for an afternoon on hand-selected parts proves nothing you need to know.

The ramp is real work and it goes on your plan

Between a cell that functions and a cell that produces sits a period of tuning: feeders adjusted, grippers modified, fault causes traced, programs refined, operators learning. That period consumes engineering time, production capacity and material, and it is where projects overrun because the plan showed handover as a single date. Schedule it, staff it, and keep the builder's engineer available during it rather than releasing them at handover. Also keep old capacity available until the cell proves itself; plants that dismantle the manual station on the day the robot arrives have no way back when the ramp takes longer than hoped.

Handover is a transfer of knowledge, not a folder

What you need at the end is the ability to run, fault-find, modify and maintain the cell without ringing the supplier for routine matters. That means program copies in an editable form with the licences to use them, electrical and pneumatic drawings matching what was actually built, a spares list with part numbers and sources, the safety assessment and validation records, and training delivered to named people while the builder's engineers are still on site. Ask for as-built rather than as-designed documentation and check it, because commissioning changes are routinely made on the machine and never drawn.

Frequently asked questions

What should be tied to the final payment stage?

A performance test on your own site, on production material, run continuously for long enough to reveal intermittent faults, against a rate and a quality standard agreed in the contract. Include documentation and training in the same milestone, because both slide once the machine is running. Retaining a portion of the price until that test passes keeps the builder engaged through the ramp, which is exactly the period when their attention naturally moves to the next customer.

Who is responsible for safety when we combine machines from several suppliers?

In many jurisdictions the party that assembles separate machines into a functioning installation takes on the duties of the manufacturer for that assembly, which can be the plant itself if you are doing the integration. That means a risk assessment covering the combined operation, verification of the safety functions across the boundary between machines, and the associated technical file. Establish this at the outset with your safety adviser, because discovering it during commissioning delays the start of production.

How long should we keep the manual method available?

Until the cell has demonstrated the required rate and quality over a sustained production period, not until it has been signed off. Keeping fixtures, tooling and a trained operator available is a modest cost against the alternative of having no way to supply a customer while a feeder problem is diagnosed. Set a defined decision point for dismantling, tied to demonstrated performance rather than to a calendar date, and record what the fallback method requires so it can actually be restarted.