Robotics & Automation worked example

Robot Path Efficiency at 81% target path efficiency: a worked example

This scenario runs the robot path efficiency calculation on the strong side: 81% target path efficiency, with every other input held at its documented default. Use it during cycle time reduction or runoff so productive motion versus waste in the robot program is visible before reprogramming.

The inputs for this scenario

  • Productive TCP motion time per cycle: 6.5 sec (unchanged)
  • Total program time per cycle: 10 sec (unchanged)
  • Target path efficiency: 81 % (raised for this scenario; the documented default is 70)

Working through the calculation

  • Applying the documented formula (Robot path efficiency = productive TCP motion time per cycle / total program time per cycle) to the inputs above produces each figure below.
  • At this operating point the engine returns 65 % path efficient for robot path efficiency, the number this scenario is built around.
  • At this operating point the engine returns 16 points for path efficiency gap.
  • At this operating point the engine returns 6.5 value for productive tcp motion time.
  • At this operating point the engine returns 10 value for total program time.

How this compares with the baseline

  • Against the tool's baseline example, where target path efficiency sits at 70% and the headline result is 65 % path efficient, this scenario lands almost exactly on the baseline at 65 % path efficient.
  • Use it when optimizing a teach program or benchmarking cells, to see how much of the cycle is actual value-adding motion. Treat this as a target state: the delta against the baseline quantifies what the improvement is worth before you commit to chasing it.

Results at a glance

  • Robot path efficiency: 65 % path efficient (headline result)
  • Path efficiency gap: 16 points
  • Productive TCP motion time: 6.5 value
  • Total program time: 10 value

Run it with your numbers

  • Every input above is editable in the live Robot Path Efficiency calculator, which recalculates instantly and can be shared with the inputs intact.

Last reviewed 2026-05-12.