Derived files, parameters, and features should appended source model state onto name.

[owendN6XAN]

Derived content—including model states—needs clearer identification. Specifically, the source model state should be appended to derived elements such as files, parameters, and feature names. This is especially important when working on large files with multiple configurations that must remain linked, where maintaining accurate references between files is critical for proper fitment and centralized fast design updates.

Currently, derived files have no meaningful identifiers, and derived features and parameters are labeled only with an incrementing “_#” suffix. These numbers are assigned based on the order of import rather than the order in which derives were created, which can result in seemingly random naming accidentally.

This lack of clarity makes it difficult to track derived content—particularly parameters, which are not visible in the feature tree. Over time, this also complicates maintenance and support, especially as production teams become more involved and original design intent is less well understood.