Cell Family and Equipment Selection
In one sentence
A product family joins a cell not because the parts look alike, but because of shared operations, a compatible route and verified equipment conditions.
By the end of this lesson
- Calculate 75% commonality by counting 18 shared relations out of 24 required operation relations in a product–equipment matrix.
- Show that operation commonality and time-weighted load give different results.
- Screen equipment candidates by capacity, product suitability and safe access conditions.
- Decide which products enter the cell and justify the operations that stay outside.
Why it matters
Cell design starts by deciding which products can flow together, before any machines are moved closer. Parts of a similar color, or shipped in the same box, may need different processing. Conversely, two parts that look different may share the same operation sequence, the same fixturing arrangement and similar inspection conditions. A product family is built on these relationships. The purpose of a cell is not only to shrink floor space; it is to create a sustainable link between human work, equipment and part movement. For this reason family selection comes before the list of machines to buy. Choosing the wrong family produces parts that keep leaving and returning inside a layout that looks good.
A product–equipment matrix shows products in the rows and the required operations, or the resources that can perform them, in the columns. But the meaning of the columns must be fixed at the start. Counting two alternative machines that do the same operation as two separate required operations distorts the commonality rate. Likewise, when a product uses the same resource at different stages and the matrix shows only that the resource exists, the route information is lost. The matrix is a screening tool; sequence, time and technical conditions need a complementary record. The cell boundary is drawn by reading these records together. State clearly whether an empty cell means that no operation is needed or that information is missing.
The commonality percentage depends on what is counted. In this lesson the denominator is all required product–operation relations of the selected products. The numerator is the relations that belong to operations shared by all candidate products. This way the same percentage is not compared wrongly with another matrix definition. Even when the number is high, one rare long operation can set the capacity. Short, frequent operations create many shared relations, while a long special operation looks small in the table. Commonality is not a workload ratio. Once time and demand are added, the family that enters the cell can change; using the percentage alone as an acceptance threshold erases this distinction.
Equipment selection is not limited to moving what already exists into the cell. Part size, fixturing method, operating range, inspection access, maintenance space and material presentation are considered together. A machine may be able to perform the required operation and still be unsuitable for all products. Using a shared resource can reduce or increase setup loss; the result is measured, not assumed. The selection record must show which condition was verified and which is still open. An uncertain technical suitability is not hidden inside an optimistic capacity calculation. The output of this lesson is not a final investment approval but a reasoned family and equipment proposal that explains which products can be tried in the same cell under which conditions.
Formula
Operation commonality (%) = Number of relations belonging to operations shared by all products ÷ Total required product–operation relations × 100
Operation load (s/day) = Demand (units/day) × Operation time (s/unit)
Resource load (s/day) = Sum of product loads + Setup load
Load ratio (%) = Resource load ÷ Available resource time × 100
Unlock the rest of this lesson with an Academy account
Create a free Academy account with your work email address; it can be used once it is approved.
- Step-by-step instructions
- Worked example with real numbers
- Where the method misleads
- Common mistakes