Parents, children, transforms
In glTF the elements are called nodes. They form a parent-child hierarchy without cycles; each node has at most one parent [1]. A node's global transform is its parent's global transform multiplied by its own local one [1]. Move the group "lid" and the screws and hinges beneath it move too.
Libraries such as three.js work the same way internally: every object in the scene can have children whose placement is relative to the parent [2].
Why it matters for configurators
A configurator addresses parts through the scene graph. For that to work, the model needs:
- meaningful names: "side-panel-left" rather than "Body047";
- sensible groups: everything that is swapped or moved together sits under one node;
- correct pivots: a door turns on its hinge, a gear on its shaft.
Without this structure every variant, every exploded view and every part swap becomes manual work.
Typical faults in CAD exports
- Flat structure: thousands of parts hang directly under the root, with no groups.
- Pivots at the origin: every part turns around the scene origin instead of its hinge.
- Duplicate or cryptic names: scripts cannot address parts unambiguously.
All of these can be fixed during preparation, but they cost time that clean CAD data saves.
Example
The model of the planetary gearhead (example configurator, fictional product) contains more than 200 nodes with names such as "carrier" or "planet-pin". Each part has its own explode direction and a place in the assembly order, which is what makes the exploded view, cut-away and item numbers controllable.
The guide CAD to web 3D explains how to prepare this structure in CAD.