Commissioning or Routine Care: Which Robot Jobs Fool You?

Let us settle a friendly argument. In a robotics operations team, which kind of job do you misjudge most: setting up something new, or looking after something that already runs? Most people say the new thing, and they are partly right. But the details are more interesting than the headline, and they show how a simple habit of comparing guessed and real hours can steer a team’s planning. This is a conversational comparison of commissioning work and routine care, with the same yardstick applied to both: how far the estimate landed from the time actually spent.

The yardstick: guess, actual, ratio

For each job, write down your estimate before you start. When the job is finished, write down the hours it really took. Divide the second number by the first. A ratio of 1 means you nailed it. A ratio of 2 means the job took twice as long as you said. A ratio below 1 means you were too gloomy. We will use this single number to judge both kinds of work.

One caution before we begin. The comparison below is a general pattern described in words, not a set of measurements from a particular site. Your own sheet will tell you what is true for your robots.

Contender one: commissioning new equipment

Commissioning means bringing a new machine or system into working service: unpacking, installing, connecting, configuring, calibrating, testing and handing over. It is exciting work, and it is also the work where optimism does the most damage.

Why guesses run short: the work depends on things outside your control. A site may not be ready. A network may not behave as the drawings suggested. A sensor may need recalibrating twice. A setup guide that takes a morning to read can take a week to put into practice. And because each installation is somewhat different, you have fewer past examples to lean on.

What the ratio looks like: typically high and widely scattered. A job can land close to the guess one week and at three times the guess the next. The scatter is the real finding, because it means a single correction factor will help on average but still leave surprises.

What helps: splitting the job into stages and estimating each separately, giving a range, and adding explicit time for dependencies such as site access. If you are planning a larger warehouse set-up, a long read like a long read on how warehouses put driverless carts to work will show how many stages are involved, and each stage is a place where an estimate can go astray.

Contender two: routine care

Routine care is the regular work of keeping equipment healthy: inspections, cleaning, software updates, spare checks, small repairs. It does not make headlines, but it fills many weeks.

Why guesses are better: the tasks repeat. A team that has inspected the same type of unit fifty times has a good feel for how long it takes. Instructions exist, the tools are at hand and the steps are familiar.

Where they still slip: routine care hides a different kind of surprise, the discovery that something is wrong. An inspection that should take twenty minutes becomes two hours when a worn part turns up. The estimate was fine for the routine; it simply had no room for the exception.

What the ratio looks like: usually closer to 1 on average, but with a long tail. Most jobs land near the guess, and a few jump well beyond it. If you only look at the average you will miss those few, and they account for most of the pain.

Side by side

  • Typical ratio: commissioning sits well above 1; routine care sits near 1 with occasional spikes.
  • Spread: commissioning varies from job to job; routine care varies mostly through rare exceptions.
  • Main cause of error: commissioning suffers from unfamiliar dependencies; routine care suffers from unexpected findings.
  • Main remedy: for commissioning, a staged estimate with ranges; for routine care, a small allowance for the unexpected and a note of how often it was needed.
  • Value of history: commissioning needs a careful grouping by type of equipment; routine care benefits from plain averages over many jobs.

The part nobody puts in the plan

Both kinds of work share one blind spot: paperwork and handover. After a robot is commissioned, someone writes up what was done, updates the asset record and briefs the people who will run it. After a routine round, someone logs findings and orders any parts. These tasks rarely have a line in the estimate, yet in a busy week they account for a surprising share of the hours. When you record actuals, include them. The ratio will go up, and it will go up honestly.

There is a related trap with waiting. A robot that is parked until a spare part arrives costs no hands-on time, but it still stretches the calendar. Keep two actual columns if you can, one for effort and one for elapsed days, and do not mix them up when you compare with the guess.

So which one fools you more?

Our answer: commissioning fools you by a wider margin, but routine care fools you more often than people expect, because its surprises arrive unannounced. A team that tracks only commissioning will miss the slow bleed of unplanned time inside routine work. A team that tracks only routine work will be caught out by every new installation.

If you can only manage one column in your sheet, add a label for the type of work and keep both kinds in the same table. The grouping will show you the difference within a few weeks.

A small invented example

Imagine a team that logs three months of work. Eight commissioning tasks have ratios ranging from 1.1 to 3.0, with an average of 1.9. Forty routine inspections average 1.1, but three of them reach 4.0 because of faults discovered on the day. The team learns two things: commissioning plans should be doubled or given wide ranges, and routine rounds should carry a small allowance, perhaps ten percent, for the odd repair. The numbers are invented, yet the pattern is typical of mixed workloads.

Other platforms, same lesson

The pattern holds well beyond warehouse vehicles. For aerial platforms, for instance, a clear introduction such as an easy introduction to flying robot platforms for working crews shows how setup, licensing, battery routines and software all feed into the work to be done. Each element has a different ratio, and a team that records them separately will see which parts deserve extra time in future plans.

A glance at how organisations look back

Comparing plans with results is a habit that groups in many fields share. One illustration is the Cotocus Foundation site, which introduces a nonprofit organisation working on technology, innovation and education, with pages for programs, research, community activity and a blog. For a robotics team, the lesson is simple: write down what you expected, write down what happened and put it where colleagues can read it.

Taking it to your own floor

  1. Choose two kinds of job you do often, perhaps a new installation and a routine round.
  2. For a month, write the estimate before each job and the real hours after it.
  3. Compute the ratio and note any exceptions in a few words.
  4. Compare the averages and the spreads for the two kinds.
  5. Adjust your standard estimates: a range for the new work, a small allowance for the routine.
  6. Repeat the comparison a quarter later and see what has moved.

It is a small experiment, and it costs a few minutes a day. The reward is that the next time someone asks how long a job will take, you can answer with something sturdier than a feeling.

Related Posts

Robotics Operations Skills: A Start-Stop-Continue Review

How robotics operations technicians and engineers can review a deployment period with start, stop and continue lists, and turn the findings into career skills.

Read More

Commission the Stubborn Robot Fault First: A Diagnosis

A diagnosis of why robotics schedules slip at the end and how starting each commissioning day with the stubborn fault moves discovery earlier.

Read More

Robotics Operations Today: The Rise of the Waiting-For List

A look at how multi-party robot deployments stall on unanswered requests, and why operations teams are adopting waiting-for lists with owners and dates.

Read More

Robot Task Done Right: A Beginner Primer on Acceptance Criteria

A friendly primer on writing acceptance criteria for a robotic task, with a delivery-vehicle example and a mini-glossary of the terms beginners will meet.

Read More

Why Does the Robot Keep Stopping Here? A Five Whys FAQ

A cart halts at the same junction again and again. This friendly FAQ shows how five why questions turn a repeat robot stop into a fixable process gap.

Read More

The AGV That Kept Stopping at Aisle Seven: A Team Story

An invented warehouse team spends weeks on a robot that halts at a clear aisle, until narrating the whole journey aloud to a charging dock exposes the cause.

Read More

Leave a Reply