What Is a Sub-Assembly in Manufacturing? Definition and Example

A sub-assembly is a component that is itself manufactured through its own routing and then fed into a larger parent product, so it is a build within a build. A gearbox made from its own machining and assembly steps, then fitted into the pump that consumes it, is a sub-assembly. In scheduling terms it is a routing step that pulls in a whole nested routing, which means the parent job cannot complete the step that consumes the sub-assembly until the sub-assembly's own operations are finished.

This entry is part of the EDGEBIC by User Solutions glossary series; for the broader vocabulary of production planning, see the manufacturing glossary.

How a Sub-Assembly Works

A bill of routing usually describes making one product from raw materials. A sub-assembly adds a level: one of the things the routing needs is not bought or drawn from stock, it is built, through its own sequence of operations.

That distinction changes the schedule. A raw material is consumed at a point, and a material step marks the draw. A sub-assembly is produced, so its operations take work center capacity and time, and they must finish before the parent step that fits the component can proceed. The sub-assembly introduces a dependency chain that a simple material never does.

The engine handles this by sorting every step, parent and sub-assembly, into one dependency order. It does not schedule the sub-assembly as a separate job in isolation; it weaves the sub-assembly's operations into the overall plan so they land ahead of the operation that consumes them. Crucially, the ordering comes from each step's dependency links, not from the machines the steps use, so a sub-assembly and its parent can share a work center and still schedule in the correct order rather than colliding.

A Concrete Example

A pump is built from a housing and a gearbox, and the gearbox is a sub-assembly with its own two operations. The parent routing consumes the gearbox at final assembly:

Step 40 consumes the finished gearbox, so the engine places steps 10 and 20 ahead of step 40. Notice that gear cutting and housing machining both want Mill-1. The engine sequences them on the shared machine and keeps the gearbox complete before final assembly, because the dependency, not the machine name, decides the order. If the gearbox build runs long, final assembly and anything after it wait on its real end.

How EDGEBIC Uses It

In EDGEBIC a sub-assembly is a component step in a routing that nests the component's own routing, and the engine schedules the whole structure as one dependency-ordered plan.

• The nested routing is scheduled ahead of its consumer. The sub-assembly's operations take real capacity and are placed before the parent step that fits the component.
• Order comes from dependency, not machines. A real topological sort keyed on step identity keeps a sub-assembly and its parent in the right order even when they share a work center.
• A slip is visible early. Because the dependency is modeled, a sub-assembly that runs long or waits on capacity pushes its consuming step and the rest of the parent job, so the delay surfaces on the schedule instead of surprising the floor.
• Actuals and reschedule follow the same rules. Completed sub-assembly operations are frozen by their actual dates on reschedule, exactly like any other finished step.

Sub-assemblies are what let a routing describe a multi-level product rather than a single flat sequence. To add one on a real routing, see how to add a sub-assembly to a routing in EDGEBIC, and job shop scheduling challenges covers why dependency ordering across shared machines is hard to get right by hand.