About Change Level of Development

The Change level of Development function refers to the continuous level of development (LOD) process with a code number evolving with the maturity of the design from 100 to 500. For more information, see (http://bimforum.org/lod/).

In Building and Civil Assemblies, the change level of development converts a feature-based model to a product-based model. Once fully converted, a model can be edited concurrently and further detailed.

Change level of development enables to automatically instantiate and synchronize user features using the specification features as inputs. These parametric components can be developed over time to contain increasing levels of detail and complexity. At a certain point in the evolution of a project, a reference or a template can be instantiated to give more details to the project and make it PLM. You can create an engineering template (with the appropriate license for Knowledge Engineering Specification) that shares the same inputs as the user features. This model development process is very powerful and will allow users to adopt a streamlined workflow, facilitating automation and the instantiation of parametric templates. Decreasing the time necessary to pass from a conceptual model to a fully detailed model.

Change level of development processes specialized specifications that must be published by their containing representations.

Processing specifications involves determining the instance destination and creating links (engineering connections) between the specification and the resulting instance. The specification is based on an object type that includes mandatory and optional elements, as well as an instantiation method. The instantiation method of an object type determines mandatory elements and the type of engineering connections to be created.

Reference or Adaptative Object Type-based Specification

As an example, when specifying an object type with a reference or adaptive instantiation method, you must specify a positioning axis system (that is a hook) for the product-based design. You must publish this positioned axis system to a Base Axis System by using the Define Components command. During the process, a coincidence constraint is created between the hook element and the related specification.

Note: This definition plays a prominent role when working with multiple ranges as it ensures the geometry is close to the original product origin and can then be defined in normal range

Distribution Object Type-based Specification

When a specification is defined by an object type with a distribution instantiation method, a fix together constraint is created between the created instance and the related specification. The instance is also fixed in position (fixed instance position). If the engineering connection is deleted, the link between the instantiated product and the specification is also deleted. Change level of development considers the specification as not exposed and will propose to expose it again.