controllability

Controllability asks a deceptively simple yes-or-no question: using only the knobs and levers you are allowed to touch, can you steer a system into any state you might want? A state here means the full set of inner conditions that describe what the system is doing — positions, speeds, temperatures, and so on. A system is controllable if, given enough time, your available inputs can drive every one of those inner conditions to any chosen value. If some corner of the system can never be reached or changed no matter how you work the controls, it is not fully controllable.

A homely picture helps. Suppose a model train sits on a figure-eight track and your only control is the throttle. You can put the train anywhere along that track, fast or slow — but you can never make it leave the rails and sit in the middle of the room, because no throttle setting reaches that state. The rails limit which states your single input can produce. Real machines have the same issue: a quadcopter that lost one motor may be unable to reach certain tilt-and-spin combinations; a heating system with a single furnace cannot independently set the temperature of every room. The missing reach is a lack of controllability.

Engineers care because controllability is a precondition for control itself: you cannot design a regulator to hold or move a state that your inputs physically cannot influence. It is checked mathematically from the model of the system, before any controller is built, and it often guides hardware choices — where to place a thruster, how many actuators to add, which valve to install — so that the states that matter are all reachable. A system that is uncontrollable in some part usually needs more or better-placed inputs, not a cleverer algorithm.