A STEP assembly can open with every solid in the right place and still lose the hierarchy you expected. Instead of Frame > Motor > Rotor, the receiving CAD system may show a flat list of bodies, generic names, or one compound shape.
That is different from missing geometry. A flattened assembly can be geometrically complete while its product structure, component identity or names were not preserved by the export/import path.
STEP is capable of representing assemblies and product structure. NIST describes STEP as a product-model exchange format used for parts, assemblies and manufacturing information. NIST STEP File Analyzer. Whether that structure survives a specific transfer is an implementation question.
First decide what was actually lost
Use separate checks for geometry and structure:
| Observation | Likely issue |
|---|---|
| All solids are visible, but the tree is flat | Assembly hierarchy or instance structure was flattened |
Solids are present but names became Body1, Body2 |
Naming metadata was not exported, mapped or imported |
| Repeated parts became separate anonymous solids | Instance identity may have been expanded into geometry |
| Components are physically absent | This is a missing-geometry or unresolved-reference problem |
| Parts moved to wrong positions | Placement/transform transfer needs investigation |
Do not report “parts missing” when the real problem is only lost names. Conversely, a tidy-looking tree is not proof that every component arrived.
Why a STEP reader may flatten an assembly
Some import pipelines read only the geometric shape and ignore the document-level product structure. Open CASCADE, for example, has both shape-oriented STEP reading and XCAF document workflows for preserving labels, assemblies, names, colors and other attributes. The difference illustrates a broader point: the same STEP file can expose more or less structure depending on the importer.
Export settings matter too. A sender may intentionally save an assembly as a single part, simplify it, merge bodies, or export only visible components. Once that has happened, the receiver cannot reconstruct the original product tree from geometry with certainty.
Native CAD mates and constraints are another layer. STEP can transfer assembly placements and product relationships, but it does not recreate the source application's editable mate system or feature history.
Names are useful, but they are not stable IDs by default
Component names help humans review a model, but names can change during export or import. A manufacturing handoff should not rely on a visible label alone to establish revision or part number.
If identity matters, carry a controlled part number/revision in the BOM or agreed metadata workflow. Modern AP242 workflows can include richer properties, but the sender and receiver still have to agree on what is exported and imported.
For repeated components, verify quantity separately. Ten anonymous bolts in the geometry may have come from one repeated instance definition, ten expanded solids, or a partial export. The visual result alone does not tell you which.
Check the assembly before converting it again
When an imported STEP tree looks wrong:
- Keep the original STEP unchanged.
- Open it in another reader that displays product structure, such as the STEP viewer.
- Compare component/body counts with the source BOM or sender's expected structure.
- Check whether geometry is actually missing or only names/hierarchy are different.
- Verify one known placement or interface dimension.
- Ask the sender which export mode was used: assembly, single part, merged bodies, simplified representation, or visible components only.
- If structure is required downstream, request a new export with that requirement stated explicitly.
Converting a flattened STEP to another STEP usually preserves the flattened result. A second conversion cannot infer a trustworthy original assembly tree.
Geometry review and BOM review are different jobs
A STEP model is useful for checking fit, dimensions and solid geometry. A BOM is the controlled list of what the product is supposed to contain. Use both when the assembly matters.
For example, a motor assembly may visually look complete while one internal spacer is absent. The overall dimensions and even total volume can stay plausible. A BOM/component-count check exposes the omission much more reliably than a shaded view.
The same principle applies to supplier RFQs: send the released geometry plus the revision, quantity and component scope. The supplier CAD handoff guide covers the package.
When to accept a flat STEP
Flattening is not always a defect. It can be intentional when the recipient only needs an envelope model, collision reference, CAM stock geometry or IP-protected supplier model.
A flat file is acceptable when everyone agrees that:
- component identity is not needed;
- the geometric scope is complete for the task;
- the receiving software can measure or machine the required bodies;
- revision and material requirements are carried elsewhere.
It is not acceptable when downstream work depends on part numbers, quantities, separate components or replacement of individual items.
Do not confuse structure loss with feature-tree loss
Even a STEP that preserves a beautiful assembly hierarchy normally does not reproduce the source CAD application's sketches, feature history, mates and configuration logic as native editable history. Product structure and parametric authoring history are different kinds of information.
If future design edits matter, keep the native files. Use STEP as the agreed exchange derivative and validate the parts of the product model that the next workflow actually needs.
Multibody part and assembly are not the same thing
One important case sits between “assembly preserved” and “assembly flattened”: the source or importer may intentionally represent several solids as a multibody part.
A body is geometry. A component is product structure.
Autodesk Inventor's import documentation makes the distinction explicit. Its conversion options include Assembly, which preserves source structure, and Multi-body part, which imports assembly geometry as solid bodies inside a single part. Autodesk Inventor import documentation.
That means a file containing twelve solids does not automatically represent twelve controlled components. The same visible geometry can be useful in different forms:
| Downstream task | Structure that may be acceptable |
|---|---|
| BOM and part quantities | Preserved components and instances |
| Envelope or packaging study | Multibody or flattened reference may be enough |
| CAM reference geometry | Multibody representation may be convenient |
| Supplier IP protection | Simplified structure may be intentional |
| Service and spare parts | Component identity is usually important |
Before trying to rebuild a hierarchy, ask whether the source CAD actually contained that hierarchy.
Why repeated bodies do not prove repeated part numbers
Autodesk Support documents a Fusion case where an imported STEP showed multiple bodies for what the user considered one repeated part. Autodesk attributes the behavior to a STEP exported as a part with bodies rather than an assembly and suggests creating components when a parts list is needed. Autodesk Support.
Geometry alone cannot establish every BOM relationship. Ten identical-looking solids might be ten instances of one component, ten independent bodies, or an expanded pattern. If quantity and identity matter, compare the STEP structure with the controlled BOM instead of inferring part numbers from shape.
For quoting, record body count, component count and unique part count separately when those distinctions matter. They answer different questions.
Keep geometry and identity acceptance separate
A useful receiving record has one result for geometric scope and another for product identity. An envelope study may accept all expected solids in correct positions even when names are flattened. A spare-parts workflow still needs controlled identifiers and quantity mapping.
Check one repeated component and one nested subassembly before declaring the structure preserved. If the recipient needs stable part identities, request the intended product structure from the source rather than renaming anonymous bodies by appearance. A second export from the already flattened derivative cannot establish the missing source relationships. Preserve the original delivery so the two import paths can be compared.
Original article: CADProps · https://www.cadprops.com/guides/step-assembly-flattened-after-import/