Skip to main content
GullySystem
A practical guide

Site commissioning plan for a robotic cell, step by step

Ganesh HSStrategy and Technology, GullySystem
Practical advice · 5 min read

In this guide 6 sections
The short answer

Commission a robot cell in a fixed order: site acceptance, safety validation, teach points, cycle-time proving, then punch list closure. Each stage ends with a signed record before the next begins. Keep the safety file, program backups and open defects together, so the handover pack builds itself.

Begin with site acceptance, not the robot

Before anyone powers the arm, check what the site actually delivered. Compare the anchor bolt layout with the base drawing. Then confirm the air supply, the incoming power, the earth bond and the fence line against the layout approved at design review.

Mismatches found now cost an afternoon. Found during teaching, they stall the whole crew while the customer watches the clock. Photograph each item and attach it to the cell record, and ask the customer’s representative to sign the site acceptance sheet before you unpack the controller. Also check the main isolator position, the teach pendant holder height and the pendant cable length, since operators reach for these first and complain about them last.

It is a short step. Do not skip it. Measure twice.

  • Floor flatness and anchor positions
  • Compressed air pressure at the drop
  • Incoming supply, earth continuity and cable routes
  • Guard posts, light curtain mounts and gate positions
  • Network drops for the controller and any camera

Validate safety before motion at speed

Safety validation comes ahead of production speed. Test every emergency stop, each guard door interlock, the light curtain muting and the reduced-speed mode. Record the result per device, with the tester’s name and date.

The risk assessment must describe the cell as built, not as drawn. If a gripper changed or a guard moved during installation, the assessment changes too, and many commissioning delays trace back to a safety file that describes a different cell.

Keep the safety controller checksum with the record. Later, anyone can tell whether the safety program was altered after validation, and a surprised auditor becomes a calm one. No checksum, no proof.

  • Emergency stop and reset test per station
  • Interlock and gate switch test
  • Light curtain stopping distance check
  • Safety controller program checksum
  • Signed validation certificate

Teach points and name them properly

Teaching is where the cell takes shape. Set the tool centre point and the user frames first, because every taught position depends on them. Only then teach the pick, place, approach and retreat points.

A point called P37 means nothing to the night-shift technician six months later. A point called PalletA_Layer2_Approach does. Store the program, the frame data and the tool data together, and copy them to external media after each teaching session.

Note who changed what. When a point drifts, the history shows whether the change was deliberate, whether a collision nudged a flange, or whether a technician touched up a pick position.

Prove the cycle time with real parts

Run the cell with production parts, not dummies. The customer cares about the cycle time they were promised. Measure it across a long run, not one lucky cycle, and note the average, the slowest cycle and every stop cause.

Vision lighting, gripper wear and conveyor speed all show up here. If the target is missed, decide whether to retune the path, shorten the dwell times or change the process itself, and record who agreed to the decision.

Watch the first hour closely, because a servo gripper that overheats or a vacuum cup that loses seal tends to show itself late in the shift. A proving run with no unplanned stops closes this stage.

  • Run length and number of parts handled
  • Average and slowest cycle
  • Stops by cause: grip, vision, conveyor, operator
  • Reject count and reason
  • Customer witness signature

Close the punch list and hand over

Every open item goes on one punch list, each with a named owner, a status and a deadline. Separate safety items from cosmetic ones. Safety items block handover, while a paint chip on a guard post does not.

The handover pack holds the final program backup, the safety file, the electrical drawings, the spares list and the operator training record. Assemble it as you go, not in the last week.

Before leaving, agree the first service visit date with the customer. Put it in the calendar today. Chase the spares list too, since a customer who waits three weeks for a replacement cup remembers the wait longer than the install.

Robot cell commissioning tracker

Five blocks in order make up this single-sheet tracker: site acceptance, safety validation, teaching, cycle proving and punch list. Each block has columns for check item, result, tester, date and attached photo. The last block adds owner, due date and a safety-or-cosmetic flag for every open item.

Open a blank worksheet to print

Questions owners ask

Who signs off each commissioning stage?

The integrator’s commissioning engineer signs the technical result. The customer’s representative witnesses the site acceptance and the proving run. Safety validation is signed by the person competent to assess it.

What should be backed up after teaching?

The robot program, the tool and user frame data, the safety controller program and any PLC or vision files. Label each backup with the date, the cell and the person who took it.

What if the cycle time target is missed?

Find the cause first: path, dwell, gripper or feed. Then agree with the customer whether to retune, change the process or revise the target, and write the decision into the record.

When is a cell ready for handover?

When safety validation is signed, the proving run is accepted and no safety item remains open. Cosmetic items can continue on a dated list after handover.

Browse all guidesBack to top ↑
Next step

Have a specific situation to work through?

This article covers the general case. Tell us what you’re actually dealing with and we’ll respond directly.

Share Your Requirements