VATI Plant-Type Analysis §

Concept: Vocabulary that names a phenomenon.

TOC’s classification of manufacturing systems by the logical shape of material flow: V for repeated divergence, A for convergence into assemblies, T for common components assembled into many end items, and I for mostly linear flow.

Also known as: V-A-T-I analysis; VATI flow classification.

When a plant’s “constraint” seems to move every week, the first question is often not which machine is overloaded. It is what shape the material flow has. VATI analysis keeps Drum-Buffer-Rope from being applied as if every plant were a straight line. A factory’s physical layout can mislead the eye; the useful question is how material branches, converges, waits, and competes for shared resources as it moves from raw material to sold product.

The letters name four dominant shapes. A V-plant starts narrow and diverges into many products. An A-plant starts wide and converges into fewer assemblies. A T-plant runs through common components, then explodes into many end items at final assembly. An I-plant is close to a line. Each shape fails differently under local efficiency measures, so each asks DBR, S-DBR, Buffer Management, and constraint identification to watch different control points.

Context §

VATI analysis sits between the general Five Focusing Steps and the scheduling mechanisms that implement them. Step 1 says to identify the constraint. In a manufacturing system, that instruction isn’t enough. A planner has to know whether the visible queue, assembly shortage, setup campaign, or missing component is the constraint itself or a symptom produced by the plant’s topology.

Srikanth’s TOC Handbook chapter frames the classification as a change from a resource-centered view to a product-flow view. Resource-centered analysis asks which work center is overloaded. Product-flow analysis asks how materials depend on earlier materials, how resources are shared across routes, and where convergence or divergence makes a local decision damage the whole flow. That shift is why VATI analysis is not a taxonomy for its own sake. It is a diagnostic surface for the DBR design.

The classification is especially important before choosing between DBR and Simplified Drum-Buffer-Rope. Full DBR is appropriate when an internal capacity constraint must be scheduled and protected. S-DBR is often the better fit when the market is the strategic constraint and the internal capacity-constrained resource can be monitored through planned load. Plant type shapes that judgment. A V-plant with sequence-dependent setups, an A-plant with chronic missing parts, and a T-plant with common-component stealing can all appear to have “wandering bottlenecks” if the topology hasn’t been named first.

What It Is §

VATI analysis classifies a production environment by the logical flow of materials, not by industry label, building shape, department chart, or ERP routing list alone. The practitioner sketches the product-flow diagram from raw materials through fabrication and assembly, then asks which structural feature dominates.

V-plants are dominated by divergence. A small number of raw materials or intermediate forms can become a large number of finished products through a shared sequence of operations. Steel rolling, plastic extrusion, textile dyeing, and oil processing are common examples in the TOC literature. The signature failure is robbing: a divergence point consumes shared material or capacity for one downstream product while another due product waits. Finished-goods inventory can be high while the exact item the customer ordered is missing.

A-plants are dominated by convergence. Many fabricated and purchased components come together into a smaller number of assemblies. Aircraft, helicopters, kitchen cabinets, and footwear are typical examples. The signature failure is synchronization loss: one missing component blocks an assembly even when most of the plant looks busy and much of the necessary work is complete. The plant experiences feast-or-famine flow, overtime bursts, and bottlenecks that seem to move.

T-plants combine common components with final divergence. A relatively small set of common fabricated or purchased parts can be assembled into many finished products. Personal computers, cars, and faucets are standard examples. The signature failure is common-part stealing: assembly consumes a shared component for one end item and leaves the next due order unable to ship. The T shape magnifies the V-plant robbing problem because the stolen item is often a component used by several finished products.

I-plants are mostly linear. Materials pass through a direct sequence of operations with little convergence or divergence. Transfer lines and simple assembly lines are common examples. I-plants are the easiest topology to manage because the flow is legible, but they can still accumulate work-in-process and miss due dates when batch sizes are set for local utilization rather than flow.

No real factory is pure. The TOCICO Dictionary is explicit that one plant can combine more than one type. The classification is useful because one shape usually dominates the scheduling problem. If the dominant failure is divergence-point robbing, treat the plant as V-shaped for the DBR design. If the dominant failure is missing components at assembly, treat it as A-shaped. If common components are repeatedly stolen across end items, treat it as T-shaped until assembly control makes the plant behave more like an A-plant.

Some practitioner training shortens the name to VAT and treats the I case as a simple line. The certification-grade vocabulary keeps I explicit because a mostly linear flow has different control needs from divergence, convergence, and common-component assembly.

How It Is Measured or Recognized §

Start by drawing the product-flow diagram from the material’s point of view. Each box is a processing or assembly step. Each arrow is a material dependency: the box at the arrow’s tip can’t run until the material at the arrow’s base exists. Mark resource dependencies separately: if two steps need the same resource, they compete even when their material flows are different.

Then mark convergence and divergence points. A convergence point is an operation where multiple materials must come together before work can proceed. An assembly step is the ordinary example. A divergence point is an operation where one material can become several different outputs. A dye house that can turn the same yarn into many colors is the standard example. These points are control points because an unmanaged local choice there can reduce due-date performance even when the apparent resource load looks acceptable.

The recognition signals differ by type:

The CCR recognition rule also changes by topology. In a V-plant, the constraint is often visible as the resource with the largest in-process queue measured in hours of that resource’s work. In an A-plant, the better clue is the resource that repeatedly uses overtime and processes parts from the assembly shortage list. In a T-plant, the first task is often not finding a capacity constraint at all; it is stopping assembly from stealing common components so the plant can reveal what constraint remains. In an I-plant, the constraint is usually the obvious line-rate resource and the WIP buildup confirms it.

Why It Matters §

VATI analysis prevents the scheduler from treating a topology symptom as a capacity fact. A-plant shortages look like resource overload until the convergence structure is visible. T-plant late orders look like poor expediting until common-component stealing is visible. V-plant finished-goods piles look like market volatility until divergence-point decisions are visible. In each case, the wrong diagnosis sends the Five Focusing Steps to the wrong target.

The classification also determines where detailed control is necessary. Srikanth’s DBR treatment is clear on the point: simple FIFO can work in simple linear flows, but divergence points and assembly points need priority lists. A V-plant needs control at divergence points so shared material is not converted into the wrong downstream product. An A-plant needs a disciplined assembly schedule and smaller batches so component waves don’t arrive too late or too early. A T-plant needs tight assembly control before it can behave like a manageable A-plant. An I-plant may need little beyond material release, the constraint schedule, and Buffer Management.

For certification-track readers, the concept is also a vocabulary guardrail. “The constraint moved” is often the wrong sentence. Sometimes the plant’s topology is producing waves that make different resources look overloaded on different days. Sometimes a common component has been stolen. Sometimes the batch-size policy has created a queue that looks like a constraint but is only a local-efficiency artifact. VATI analysis gives the practitioner a way to state the difference without hand-waving.

The classification also protects the cost-world boundary. Large batches, setup minimization, and local utilization can all be locally rational inside one department while damaging the plant’s due-date performance. VATI analysis names exactly where that damage appears, so Cost-World Thinking can be corrected at the control point rather than argued about in the abstract.

Common Misunderstanding §

“VATI is an industry classification.” It isn’t. The same industry can contain multiple plant types, and the same plant can contain more than one topology. Classify the product flow, not the NAICS code, the building, or the department names.

“The biggest queue is always the constraint.” That can be true in a V-plant, where the highest hour-queue often points to the CCR. It is less reliable in an A-plant, where the visible queue may be a wave caused by missing components elsewhere. It can be actively misleading in a T-plant, where the common-component decision at assembly may be the real control failure.

“T-plants need more expediting.” They usually need less stealing. If assembly keeps making the end item whose components happen to be available, it consumes common parts needed by the next due order. More expediting cannot repair that policy. The assembly-control rule has to change first.

“I-plants don’t need TOC.” I-plants are simpler, not immune. They still suffer from large batches, local-utilization measures, and poor release discipline. The simpler topology means the DBR design has fewer control points, not that constraint management is optional.

“VAT and VATI are different methods.” They are usually different names for the same flow-classification move. Some public training material compresses I-plants into the VAT frame; the TOCICO Dictionary and Srikanth’s Handbook chapter keep VATI explicit. Use the term that fits the source you are reading, but do not lose the operational distinction: a mostly linear flow needs fewer control points than a V-, A-, or T-shaped flow.

“VATI replaces constraint identification.” VATI analysis supports Step 1; it does not replace it. After the topology is named, the practitioner still has to identify the system constraint, exploit it, subordinate the rest of the plant, and test whether elevation is warranted.

Related Articles §

Sources §