Industry — Multi-Level Assembly & Sub-Assembly

Assembly tracked at every tier — not just the top.

Your product is a structural BOM: a finished assembly built from sub-assemblies built from parts. Fast Production Software gives each level its own work order, kit issue, WIP and transfer — so the busbar sub-assembly and the panel it feeds are one connected tree, and you can see exactly which tier a delay is at.

FG → SFG → RM
structural BOM, explode & where-used
Kit issue
reserve then issue to the line
Every tier
own WO, issue, WIP and transfer
WO-2026-0142 · Control Panel — BOM Tree
🔩 Level 2 · Components / RM ISS/IWO
Terminal block ×24 · reserved & issued as kit
Copper strip, fasteners · kit to line
🛠 Level 1 · Sub-assembly (SFG) SWO-0143
Busbar sub-assembly · WIP good 60 / 60
SFG transfer up the tree ✓
📦 Level 0 · Finished assembly FGP/FG
Control panel · FG transfer to stock
⚠ Line rejection · child part 2 pc
2 terminal blocks failed at fit · to rework
Roll-up Events
Kit issued · ISS/IWO to WO-0142 · 12 lines
SFG transfer · busbar assembly → panel WO
FG transfer pending · 2 child parts in rework
Part of the Fast Suite — 12 products on one platform, built in Pune by Improsys
Fast Complaint
Fast Quality
Fast Audit
Fast CRM
Fast Billing
Fast ERP
Fast Maintenance
Fast WMS
Fast Inventory
Fast Production
Fast Planning
Fast Project Management
Fast Complaint
Fast Quality
Fast Audit
Fast CRM
Fast Billing
Fast ERP
Fast Maintenance
Fast WMS
Fast Inventory
Fast Production
Fast Planning
Fast Project Management
Why assembly plants choose Fast Production Software

When only the top assembly is managed,
the sub-assemblies go dark

Only the top-level BOM is managed

The finished product has a bill of materials, but the sub-assemblies inside it are just line items. Nobody plans, kits or tracks the SFG that the whole assembly waits on.

Kits reach the line short

The line starts, then stops — one fastener or one bracket was never issued. Without a BOM-exploded kit and a reserve step, the shortage is found on the bench, not on the requisition.

SFG stock is not really tracked

Sub-assemblies pile up in trays or vanish into the next job. There is no on-hand figure for a semi-finished good, so you over-build some and starve the line of others.

You can't tell which tier the delay is at

The final assembly is late, but is it waiting on a sub-assembly, a bought-out part or a rework? With one flat status, the tier that is actually stuck stays invisible.

How Fast Production Software answers each one
The whole structure is one released treeA multi-level structural BOM holds every tier — FG, SFG and RM — with revision control and a release (status 4). It explodes as an indented tree, and where-used runs the other way.
Kits are exploded, reserved, then issuedA production requisition (PRMR) explodes the BOM for the work order, earmarks stock (RES/WO), then issues the full kit to the line (ISS/IWO). Short lines are flagged before the kit goes out.
Sub-assemblies are real, on-hand SFG stockEach SFG is built on its own work order and transferred into stock — the SFG transfer works exactly like an FG transfer — so it carries a proper on-hand balance the higher assembly draws against.
Every tier reports its own progressOwn work order, own issue, own good/reject WIP and own transfer at each level — so a delay or rejection is pinned to the exact tier, in plants like Solidus Hi-Tech, Nikhtish Engineering and Micro India.
Multi-level build flow

How a structural BOM becomes a
finished assembly, tier by tier

Every stage of a multi-level assembly in Fast Production Software is a real document on the shared stock engine. Sub-assemblies are built first and roll up to feed the higher-level assembly — the same reserve, issue, WIP and transfer discipline at each tier.

Release BOM
Structural BOM tree released for production · status 4
Explode
Kit & Issue
PRMR explodes BOM · reserve RES/WO, issue ISS/IWO
Build SFG
Sub-assembly
Lower-level WO · WIP good/reject on its route
SFG transfer
Roll Up
SFG feeds the higher assembly WO as a component
Assemble
FG Transfer
Finished assembly to stock · FGM/FGM + FGP/FG
Rework
Line & Rework
Child-part rejection at any tier · rework loop
On the floor

What a multi-level assembly job
looks like on screen

A multi-level assembly follows a predictable shape — explode the tree, build the sub-assemblies, roll them up, finish the top. Each question a planner asks is answered by a record that already exists at the right tier.

"Show me the whole structure"
The structural BOM — an indented tree, FG to SFG to RM, with where-used the other way
"How did the kit reach the line?"
The PRMR exploded the BOM; the kit was reserved (RES/WO) then issued (ISS/IWO), short lines flagged
"Where's the sub-assembly at?"
The SFG work order — its own good/reject WIP, then the SFG transfer that rolls it up the tree
"Which tier is holding it up?"
Each level's WO status, so a delay is pinned to the exact sub-assembly, part or rework — not the whole job
01 — Structural BOM · the whole tree

A multi-level BOM that explodes and rolls up

A manufactured assembly is not a flat parts list — it is a tree. Fast Production Software holds the full structural BOM: material positions and resource lines against a header, revision-controlled and released for production. It explodes downward from the finished good to every sub-assembly and raw material, and where-used runs the other way so you can see every parent a shared bracket or fastener sits in. See BOM & Bill of Resources for the full model.

Indented multi-level tree — FG → SFG → RM
Where-used explosion — every parent of a component
Release control before production can use it · status 4
BOM costing rolls material + resource cost up each level
Structural BOM — Control Panel
Released
Item
Level
Type
Control panel assemblyparent · finished good
L0
FG
Busbar sub-assemblybuilt on its own WO
L1
SFG
Terminal block ×24bought-out component
L2
RM
Copper strip, fastenersissued as kit
L2
RM
02 — Sub-assembly (SFG) · build then roll up

Sub-assemblies are manufactured, not assumed

A sub-assembly is built exactly like any other item — a lower-level work order reserves and issues its material, runs its route, and books good and reject WIP at each operation. When it is complete it is transferred into stock as a semi-finished good, using the same mechanism as an FG transfer. That SFG then feeds the higher-level assembly work order as one of its issued components, so the tree rolls up level by level.

Each SFG has its own work order and route sheet
SFG transfer to stock — a real on-hand balance
Sub-assembly issued up into the higher-level assembly WO
Lot-tracked where the SFG needs traceability
Busbar SFG — SWO-0143
Sub-assembly work order
Material issued · ISS/IWO
Kit ✓
Punch & form · op 1–2
Good 60 ✓
Assemble & test · op 3
WIP/OKPLUS ✓
SFG transfer up the tree
Posting ...
Feeds panel WO-0142
Level 0
SFG on-hand: 60 pc
Available to issue into the higher assembly
03 — Kit issue to the line

The line gets a complete kit, or a flagged shortage

An assembly line stops for the one part that never arrived. Fast Production Software explodes the released BOM for the work order into its child components and sub-assemblies through a production requisition, earmarks each line against the order (RES/WO), then issues the full kit to the line (ISS/IWO — the real stock deduction). Short or missing lines are visible on the requisition before the kit leaves stores. See material issue & WIP.

PRMR explodes the BOM into a full component kit
Reserve (RES/WO) then issue (ISS/IWO) — two controlled steps
Short lines flagged before the kit goes out
Stock commits at issue — reserve only earmarks it
Issue Kit to WO-2026-0142
BOM-exploded component kit
Kit lines exploded12 components
ReservedRES/WO · 12/12
IssuedISS/IWO · 11/12
Short lineBracket M6 · 40 pc
Sub-assemblyBusbar SFG ✓
StatusKit held — 1 short
The shortage is caught on the requisition, not the bench
04 — Every tier tracked

Progress you can read at each level

Because every tier of the tree has its own work order, its own material issue, its own good and reject WIP and its own transfer, you see the state of the whole structure at once — not just the top assembly. When the finished product is late, the tier that is actually stuck is obvious: a sub-assembly still in WIP, a bought-out part short, or a child part in rework. See how operations and route sheets drive each level.

Own WO, issue, WIP and transfer at every tier
Good vs reject booked per operation · WIP/OKPLUS · WIP/OKNOTOKMINUS
Delay pinned to the exact tier, not the whole job
Live via Fast Planning / MRP — WO and reservation from the plan
Tier Status — Panel WO-0142
Live
Tier
WO
WIP
State
L0 · Panel assemblytop-level FG
0142
Wait
L1 · Busbar SFGsub-assembly
0143
60
Xfer
L2 · Terminal blockbought-out
ISS
24
Kit
L2 · Bracket M6short line
PR
40
Short
05 — Finish, reject & rework

Close the top tier — and salvage the rest

When the assembly route is complete the finished product is transferred into stock (FGM/FGM then FGP/FG), lot-tracked where it matters, and is immediately on-hand for dispatch. Parts that fail on the line are captured at part or child-part level against the work order, and a rework decision opens a self-contained loop — a rework route, tracked good/reject, then salvage back to FG or into the main flow. See FG, rejection & rework, and how it hands to Fast Inventory & Quality.

FG transfer to stock — FGM/FGM + FGP/FG, lot-tracked
Line rejection at part or child-part level, against the WO
Rework loop — salvage to FG or return to the main flow
Shared stock ledger with Fast Inventory
What you see on the job
Across every tier of the tree
Structural BOM · FG → SFG → RM tree
Kit issued · reserve then ISS/IWO
SFG built · WIP good/reject, transfer up
Higher assembly · SFG rolled up as a component
FG transfer to stock · FGP/FG, lot-tracked
Line rejection · child part to rework
Rework loop · salvage to FG or main flow
Full capability set

Everything Fast Production Software covers
for multi-level assembly

Multi-level structural BOM

An indented FG → SFG → RM tree with where-used, revision control, release (status 4) and level-by-level BOM costing that rolls material and resource cost upward.

Sub-assembly work orders

Each SFG built on its own work order — its own material, route and WIP — then transferred into stock and issued up into the higher-level assembly.

Kit issue to the line

A BOM-exploded component kit reserved (RES/WO) then issued (ISS/IWO) to the work order, with short lines flagged before the line starts.

Per-tier WIP & routing

Route sheets, work centers and operation times per level — good and reject WIP booked at every operation, so each tier reports its own progress.

SFG & FG transfer

Semi-finished goods roll up to feed the next tier; finished assemblies land in stock as FGM/FGM + FGP/FG, lot-tracked, on-hand for dispatch.

Line rejection & rework

Child-part rejection captured against the work order at any tier, with a self-contained rework loop that salvages parts to FG or back into the main flow.

FAQ

Multi-level assembly —
what planners ask us

Does it handle multi-level / structural BOMs?

Yes. A manufactured item carries a structural BOM that explodes as an indented tree — FG to SFG to RM — revision-controlled and released for production before the floor can use it.

How are sub-assemblies (SFG) transferred up?

A lower-level work order builds the SFG, which is transferred into stock the same way an FG is, then issued up into the higher-level assembly work order as a component.

Can we issue a kit of components to the line?

Yes. A PRMR explodes the BOM for the work order, the lines are reserved (RES/WO) and then issued as a kit (ISS/IWO), with short lines flagged before the kit goes out.

Is each BOM level tracked separately?

Every tier has its own work order, material issue, good/reject WIP and transfer — so you see progress and rejections at each level, not only at the top assembly.

How is where-used shown?

The BOM explodes downward from the assembly to every child; where-used runs back up, showing every parent that consumes a component — useful before an engineering change.

Does it cost a multi-level BOM?

Yes. BOM costing rolls material plus resource and process cost up each level, so a sub-assembly's cost becomes an input to the assembly above it and to a full unit cost.

Other industries

Fast Production Software is also built for

See your toughest assembly go through the tree.

A 30-minute demo — we take one of your real multi-level products through BOM explosion, sub-assembly build, kit issue, roll-up and FG transfer, tier by tier.

Get a demo View pricing
Multi-level structural BOM Kit issue to the line SFG roll-up to FG Every tier tracked