Study smarter with Fiveable
Get study guides, practice questions, and cheatsheets for all your subjects. Join 500,000+ students with a 96% pass rate.
Controllability is one of the most fundamental questions you can ask about any dynamic system: can you actually steer it where you want it to go? Before you design a controller, before you pick gains, before you simulate anything, you need to know whether the system is even capable of being controlled. This concept connects directly to state-space analysis, eigenvalue placement, and feedback design. If a system isn't controllable, no amount of clever control design will save you.
You're being tested on your ability to verify controllability using multiple methods (the controllability matrix, Kalman's rank condition, the PBH test, and the Gramian) and to interpret what controllability means for system design. Don't just memorize the formulas. Understand what each test reveals about the system's structure and when you'd choose one method over another.
Before testing for controllability, you need to understand what it means and how systems are mathematically described. State-space representation provides the framework; controllability tells you what's possible within that framework.
A system is controllable if you can drive it from any initial state to any desired final state in finite time using admissible inputs. The key word is any: the control input must exist for every possible state transition, not just convenient ones.
If a system is uncontrollable, some portion of the state space is effectively "locked." No input signal, no matter how large or cleverly shaped, can influence those states. Think of it this way: if one state variable has no path connecting it to the input (even indirectly through coupling with other states), you simply can't move it.
Four matrices define a linear system:
The state equation captures how states evolve under input influence. This is your starting point for all controllability analysis. Without state-space form, systematic controllability testing would be impractical for anything beyond trivial systems.
Compare: Definition of Controllability vs. State-Space Representation: the definition tells you what you're checking for, while state-space gives you how to check it mathematically. Exam problems often ask you to first write the state-space form, then verify controllability.
The most common exam questions involve constructing matrices and checking their properties. These tests convert the abstract question "is this controllable?" into concrete linear algebra.
The controllability matrix is built by repeatedly multiplying into :
where is the number of state variables (the dimension of ).
Each column block represents how the input's influence propagates through the system over successive time steps. captures the immediate effect of the input on the states. captures where that effect migrates after one time step through the dynamics. is two steps out, and so on. By the Cayley-Hamilton theorem, and higher powers can be expressed as linear combinations of , so you never need more than blocks.
Full rank means controllable. If , every state direction is reachable. If the rank falls short, some states are inaccessible from the input.
This is the formal name for the test you just saw: a system is controllable if and only if . When a problem says "use Kalman's condition," it's asking you to build the controllability matrix and compute its rank.
This condition works identically for both continuous-time and discrete-time systems. The matrices and come from whichever domain you're working in, but the rank check is the same.
A system in controllable canonical form has a specific structure: takes companion matrix form (characteristic polynomial coefficients along the last row, ones on the superdiagonal, zeros elsewhere) and is a unit vector (typically ).
This structure is useful for two reasons:
Compare: Controllability Matrix vs. Controllable Canonical Form: the matrix test tells you whether a system is controllable, while canonical form gives you a representation that makes controllability structurally obvious. If a problem asks about pole placement, canonical form is often the fastest path.
When the controllability matrix is large or when you need physical insight into which modes are problematic, alternative tests offer computational or conceptual advantages. These methods connect controllability to the system's modal structure and energy requirements.
The Popov-Belevitch-Hautus (PBH) test checks controllability one eigenvalue at a time. For every eigenvalue of , verify that:
If this rank condition holds for all eigenvalues, the system is controllable. If it fails for a specific , that eigenvalue's associated mode cannot be influenced by the input.
This test is particularly useful when you already know the eigenvalues of (or when is diagonal/block-diagonal), because you can pinpoint exactly which mode is uncontrollable rather than just getting a single rank number from . For repeated eigenvalues, you need to check each one carefully since repeated modes are a common source of lost controllability.
The controllability Gramian provides an energy-based perspective. For continuous-time LTI systems:
For stable systems, you can let , and converges to the unique solution of the Lyapunov equation:
Positive definite (all eigenvalues strictly positive) means the system is controllable. A singular indicates uncontrollable modes.
The Gramian goes beyond a binary yes/no. The eigenvalues of quantify how much energy is needed to reach different state directions. Small eigenvalues correspond to directions that require enormous input energy to reach. So a system can be technically controllable but practically very difficult to control along certain directions.
Compare: PBH Test vs. Controllability Gramian: PBH gives a binary yes/no for each mode, while the Gramian provides quantitative information about how controllable each direction is. For numerical systems, the Gramian reveals practical limitations even when technical controllability holds.
Controllability analysis adapts to different system classes, and understanding its relationship to stabilizability helps you handle imperfect situations. Real-world systems aren't always fully controllable, so knowing what's still possible matters.
For LTI systems, and are constant matrices. This means a single controllability matrix characterizes the system for all time. All standard tests (Kalman's condition, PBH, Gramian) apply directly without modification.
Most control design techniques assume LTI structure. When you linearize a nonlinear system around an operating point, you get an LTI approximation, and controllability of that linearization tells you whether local control is feasible near that equilibrium.
For discrete-time systems , controllability means reaching any state in at most steps. The controllability matrix has the identical form:
using the discrete and matrices. Kalman's rank condition and the PBH test apply unchanged.
The Gramian adapts by replacing the integral with a sum:
The interpretation is the same: positive definite means controllable, and eigenvalue magnitudes reflect control effort requirements.
Controllability implies stabilizability, but not the other way around. Stabilizability is a weaker condition: a system is stabilizable if only its unstable modes are controllable. Stable uncontrollable modes are acceptable because they decay on their own.
Formally, a system is stabilizable if for every eigenvalue of with (continuous-time) or (discrete-time), the PBH rank condition holds.
This distinction matters in practice. Many real systems have stable modes that inputs can't reach, but that's fine for keeping the system bounded. If an exam problem presents uncontrollable but stable modes, argue that stabilizability is what matters for practical control design.
Compare: Controllability vs. Stabilizability: controllability requires reaching every state, while stabilizability only requires controlling the unstable part. If uncontrollable modes are all stable, the system is stabilizable and you can still design a stabilizing feedback controller.
| Concept | Best Use Case |
|---|---|
| Controllability Matrix / Kalman's Rank Condition | Standard algebraic test; first thing to try on most problems |
| PBH Test | Identifying which specific modes are uncontrollable |
| Controllability Gramian | Quantifying control effort; assessing practical controllability |
| Controllable Canonical Form | Simplifying pole placement and controller design |
| LTI / Discrete-Time Variants | Applying the same tests to different system classes |
| Stabilizability | Handling systems that aren't fully controllable but can still be stabilized |
Given a system with as a matrix and as , what dimensions does the controllability matrix have, and what rank indicates full controllability?
Compare the PBH test and the controllability matrix method. When would you prefer one over the other, and what additional information does each provide?
A system has three eigenvalues: one unstable and two stable. The controllability matrix has rank 1. Is the system controllable? Is it stabilizable? Explain your reasoning.
How does the controllability Gramian differ from the controllability matrix in terms of what it tells you about a system, and why might a system be "technically controllable" but practically difficult to control?
If you're asked to design a state feedback controller using pole placement, why must you first verify controllability, and which representation would make the design process easiest?