Skip to content

FAT, SAT, Runoff, and Acceptance Criteria for Robot Cells

FAT, SAT, Runoff, and Acceptance Criteria for Robot Cells

Section titled “FAT, SAT, Runoff, and Acceptance Criteria for Robot Cells”

Many robot projects start slipping long before anyone says the word “delay.” The real problem is often that FAT, SAT, and runoff are proving different things in different people’s heads. Engineering thinks the cell has already succeeded because the core motion works. Operations thinks the cell is still unproven because recovery and staffing are not stable. Management hears both messages and assumes the last mile is minor. It rarely is.

This page exists to separate those phases clearly. A healthy project proves the right things at the factory, the right things on site, and the right things only under real production runoff.

The clean split usually looks like this:

PhaseWhat it should prove
FATCore sequence, safety logic, major interfaces, and the basic designed behavior
SATSite integration, utilities, line interfaces, access, and installation-specific interactions
RunoffProduction reality: staffing, recovery, uptime drift, material behavior, and shift-level consistency

Projects get into trouble when they try to declare victory too early by asking FAT to stand in for everything else.

FAT is usually the wrong place to make final claims about:

  • real shift throughput on unstable upstream flow;
  • operator recovery in a crowded production area;
  • maintenance response under live scheduling pressure;
  • packaging or part behavior after full-site environmental variation shows up.

Those things may be previewed at FAT, but they are not fully proven there.

Strong FAT criteria usually include:

  • stable execution of the agreed sequence set;
  • correct safety-state transitions;
  • interface checks with simulated or available equipment signals;
  • evidence that common faults are detected and handled as designed;
  • enough visibility that the plant understands what remains unproven until site and runoff.

Good FAT is honest. It proves what can be proven in a controlled environment and refuses to pretend that factory conditions equal production conditions.

SAT should focus on what changed because the cell is now on the real floor:

  • utilities and network reality;
  • line-side access and material approach paths;
  • timing with actual upstream and downstream assets;
  • what maintenance and operators can do without the integrator standing beside them.

The point is not to rerun FAT. The point is to expose site-specific friction while the project can still react deliberately.

Runoff is where the project stops being a machine and starts becoming a production system. This is where teams finally see:

  • whether off-shift behavior is materially different from day shift;
  • whether recovery rules hold when schedule pressure rises;
  • which “rare” conditions actually happen several times per week;
  • whether the support model is real or only project-team heroics.

If the cell cannot survive runoff honestly, the earlier acceptance stages were not wrong. They were incomplete.

Weak acceptance criteria usually share the same flaw

Section titled “Weak acceptance criteria usually share the same flaw”

Weak criteria often:

  • overfocus on nominal cycle behavior;
  • ignore who performs recovery and under what conditions;
  • avoid defining acceptable drift during the first production weeks;
  • leave too much room for one side to claim success while the other side is still absorbing pain.

That is why acceptance criteria should be written around operating reality, not around whichever phase is easiest to pass.

A better stack usually says:

  1. FAT proves the designed system works as built.
  2. SAT proves the system still works when connected to the real plant.
  3. Runoff proves the system can survive production conditions with the actual people who will own it.

That structure is harder to oversell and much easier to govern.