A practical guide for end users, integrators and robot makers on how service pricing models allocate risk, where SLA definitions go wrong, and what safety, insurance, data and exit terms to settle before anyone touches the robot.

Writing a Robot Field Service Contract: Pricing Models, SLA Traps and the Clauses That Matter

Qi Shi, Founder, | KeepRobots

Most robot projects spend months on the purchase agreement and a few days on the service agreement. That is backwards. The purchase is a one-time event. The service contract governs every fault, every site visit and every argument about downtime for the next five to ten years.

This article is for the people who end up living with that contract: plant and facility managers, integrators who subcontract field work, and robot makers who need someone on site in a region where they have no staff. It covers the four common pricing models and what each one really buys, how SLA terms get defined in ways that quietly shift risk, and the safety, insurance, data and exit clauses that tend to be missing until something goes wrong. A clause checklist is at the end.

Nothing here is legal advice. Treat it as a list of questions to bring to your own counsel and insurance broker.

 

Four pricing models, four different risk transfers

Every service pricing model answers the same question: who carries the cost of uncertainty? Failure rates, travel time, parts lead times and technician idle time are all uncertain. The model decides who pays when they go badly.

Model

What you pay for

Who carries failure-rate risk

Who carries idle-time risk

Fits best when

Time and materials (hourly)

Hours worked, travel, parts

Buyer

Provider (unpaid between jobs)

Small fleets, early deployments, unknown failure patterns

Per-call (fixed fee per dispatch)

Each visit, usually with a time cap

Shared: buyer pays per event, provider absorbs long jobs up to the cap

Provider

Predictable, repeatable fault types

Annual SLA package

Guaranteed response or availability, often with included PM visits and labor

Provider

Provider

Mature fleets with failure history, production-critical assets

Resident technician

A person on site for agreed shifts

Mostly provider for labor; parts often separate

Buyer (you pay whether or not anything breaks)

Large sites, high robot counts, 24/7 operation

 

 

Time and materials is the most transparent model and the easiest to start with. Its weakness is that it gives the provider no financial reason to fix things the first time, and gives the buyer no cost ceiling. Two terms matter more than the hourly rate: the minimum billable increment (a one-hour minimum and a four-hour minimum produce very different bills for a ten-minute reset), and what counts as billable time (travel, waiting for site access, safety induction, waiting for parts, writing the report).

Per-call pricing works when faults are routine. The detail to negotiate is the cap. If the fee covers "up to four hours on site," decide in writing what happens at hour five, and whether a return visit for the same fault within a set period is a new call or a continuation.

Annual SLA packages move failure-rate risk to the provider, and the provider prices that risk in. A provider with no failure data on your robot model will price it conservatively, or will write the SLA so narrowly that little risk actually transfers. A common approach is to run time and materials for the first six to twelve months, log every fault, and then negotiate an SLA package using that log as the shared baseline.

Resident technicians buy presence, not outcomes. The contract should say what the technician does during quiet hours (preventive maintenance, operator training, spares audits, data collection) and who covers absences, vacations and the technician's own training time.

A simple way to compare models is to estimate annual service hours and visits, then price each model against three scenarios: a good year, an expected year and a bad year. The model that looks cheapest in the expected year is often not the one that protects you in the bad year.

 

SLA definitions: where the real negotiation happens

A response-time number on its own tells you very little. Most SLA disputes trace back to definitions, not to the numbers.

"Response" versus "on site" versus "restored." A four-hour response can mean a callback, a remote session, or a technician physically at the robot. These are three different promises. Write separate targets for each one you care about, typically:

  • Acknowledgment time: a qualified person confirms the ticket and starts triage.
  • Remote engagement time: someone is connected to the robot's logs or controller.
  • On-site arrival time: a technician is at the equipment, through site security.
  • Restoration time: the robot is back in production, possibly with a workaround.
  • Permanent fix time: root cause resolved, which may require parts.

When the clock starts and stops. Typical traps include a clock that starts only when the provider "accepts" the ticket, a clock that pauses outside business hours, and a clock that stops while waiting for parts or customer access. Some pauses are fair. The provider should not be penalized while your site refuses entry. But each pause should be listed explicitly, and parts waiting time should be capped if the provider is responsible for stocking parts.

Business hours, time zones and holidays. "Next business day" depends on whose business days. If the provider, the robot maker's remote support team and the site are in different time zones or countries, define the clock in the site's local time and attach the holiday calendar that applies.

Severity levels. Define severity by business impact, not by the provider's opinion. A workable pattern: Severity 1 means production is stopped or a safety function is impaired; Severity 2 means degraded throughput or loss of redundancy; Severity 3 means cosmetic or non-urgent. Agree in advance who assigns severity and how to escalate a disagreement.

Availability percentages. Availability is the most misleading SLA metric because the denominator is rarely defined. Consider 99 percent availability:

  • Measured against a 720-hour calendar month, it allows 7.2 hours of downtime.
  • Measured against scheduled production time of two 8-hour shifts, 22 days a month (352 hours), it allows about 3.5 hours.

Same percentage, roughly twice the tolerance. Also settle whether planned maintenance counts as downtime, whether a robot running at reduced speed is "available," whether availability is measured per robot or across the fleet (fleet averages can hide one robot that is down for a week), and whose data counts: the robot's own logs, the fleet management system or the site's production records.

Remedies. An SLA without a consequence is a target. Service credits are the usual remedy. Check whether credits are the buyer's *sole* remedy (common, and it limits your other options), whether they are capped (often at a percentage of the monthly or annual fee), and whether repeated misses give you a right to terminate.

 

Safety: the contract must connect two lockout programs

When an outside technician services a robot, two employers' safety programs meet at the same energy isolation point. The contract should say how they fit together.

In the United States, OSHA's hazardous energy standard, 29 CFR 1910.147, applies to the servicing and maintenance of machines and equipment. Paragraph (f)(2) addresses outside personnel directly: the on-site employer and the outside employer must inform each other of their lockout or tagout procedures, and the on-site employer must ensure its own employees understand and comply with the restrictions of the outside employer's program. Where a crew works on the same equipment, paragraph (f)(3) requires group lockout protection equivalent to a personal lock for each authorized employee.

In British Columbia, Part 10 of the WorkSafeBC Occupational Health and Safety Regulation covers de-energization and lockout, including written lockout procedures. Other provinces have their own regulations, and CSA Z460 is the Canadian standard for control of hazardous energy. For industrial robot cells, ISO 10218-2:2025 addresses integration, commissioning, operation and maintenance of robot applications.

Contract terms that make this work in practice:

  • Exchange written lockout procedures before the first visit, not at the gate.
  • Name who supplies locks and who holds the key list for group lockout.
  • State which robot-specific energy sources need isolation beyond electrical: stored pneumatic or hydraulic pressure, gravity-loaded axes, springs, and batteries in mobile robots.
  • Require site induction to be scheduled and, if you want, make induction time non-billable after the first visit.
  • Give the technician explicit stop-work authority without penalty.

 

Insurance and workers' compensation

Ask for a certificate of insurance for general liability and, where relevant, professional liability and automobile coverage. Two points are often missed. First, the standard ACORD 25 certificate form typically states that it is issued for information only and confers no rights on the certificate holder. If you need additional insured status, ask for the policy endorsement, not just the certificate. Second, check that the coverage territory includes the province or state where the robot sits, especially with cross-border providers.

Workers' compensation is separate from liability insurance, and in Canada the hiring party can carry real exposure. WorkSafeBC warns that if you hire a registered contractor who is not paying required premiums, you could be liable for premiums related to the work they did for you; its clearance letter, addressed to you, is how you protect yourself, and it recommends getting one before and after the work. In Ontario, WSIB policy says that without a clearance certificate a principal may be liable for a contractor's unpaid amounts up to the value of the labour portion of the contract, and that clearances are valid for up to 90 days and must be renewed. Put an obligation in the contract for the provider to supply current clearances for every province where work occurs.

 

Data, privacy and remote access

Service robots record a lot: camera feeds, maps of the building, logs with timestamps, and sometimes images of people. The service contract should cover:

  • Who owns operational data (logs, maps, fault records) and who may use it, including whether the provider can share it with the robot maker.
  • Remote access rules: which accounts, which network path, whether every session is logged, and whether the site must approve each session.
  • Personal information: in Canada, private-sector privacy is governed by PIPEDA or, in British Columbia, Alberta and Quebec, by provincial laws the federal government has deemed substantially similar. If robot data includes images of employees or the public, decide who is responsible for notice, retention and access requests.
  • Data return and deletion at the end of the contract.

 

Spare parts: ownership and the cost of waiting

Parts often decide restoration time more than labor does. Settle who owns the spares stock (buyer, robot maker or provider), who insures it, who decides minimum stock levels, how used and returned parts are handled, and what happens to unused stock at termination. If the SLA clock pauses while waiting for parts, tie that pause to whoever owns the stocking decision.

 

Exit clauses

Assume the relationship will end, and make it orderly. Useful terms include termination for convenience with a reasonable notice period, termination for repeated SLA misses, a transition-assistance period, handover of service records, as-maintained configuration and spares inventory, return of site badges and credentials, and a clear statement of which software licenses and diagnostic tools stay with the site.

 

Clause checklist

Commercial

  • Pricing model, minimum billable increment, definition of billable time
  • Travel, after-hours and holiday terms
  • Return-visit rule for repeat faults
  • Price adjustment mechanism and notice period

Service levels

  • Separate targets for acknowledgment, remote engagement, on-site arrival, restoration, permanent fix
  • Clock start, stop and pause events listed explicitly
  • Time zone and holiday calendar defined
  • Severity definitions and escalation path
  • Availability denominator, exclusions and data source
  • Service credits, caps, sole-remedy language, termination trigger

Safety

  • Exchange of lockout procedures before first visit
  • Group lockout arrangements and lock supply
  • Robot-specific stored energy sources identified
  • Site induction and stop-work authority

Insurance and compensation

  • Certificates of insurance with territory confirmed
  • Additional insured endorsements where required
  • Workers' compensation clearances for each jurisdiction, renewed as required

Data

  • Data ownership and permitted use
  • Remote access controls and session logging
  • Privacy responsibilities for camera and personal data
  • Data return and deletion at exit

Parts

  • Ownership, insurance and stocking decisions for spares
  • Handling of returned and failed parts

Exit

  • Termination rights and notice periods
  • Transition assistance and record handover
  • Return of credentials, tools and licenses

The best service contracts are boring to read and easy to enforce. If both sides can look at a fault log and agree, within a few minutes, whether the SLA was met, the contract is doing its job.

 

Qi Shi is the founder of KeepRobots, a robot field service company in Vancouver, British Columbia, that provides on-site deployment, maintenance and repair for service, logistics and industrial robots in Canada and the US. keeprobots.com

 

The content & opinions in this article are the author’s and do not necessarily represent the views of RoboticsTomorrow

Featured Product

KNF - Automation Technology Requires Reliable and Durable Pumps

KNF - Automation Technology Requires Reliable and Durable Pumps

KNF vacuum pumps for automation applications are designed for a long service life, with micro gas pumps used as cobot pumps achieving more than 20,000 hours. The latest generation of KNF brushless DC motors has an innovative bearing design that withstands high mechanical loads. This technical strength protects the vacuum pump's longevity, especially with fast switching cycles.