About Shrinkwrap Models
A Shrinkwrap model is a part composed of a collection of surfaces that represents the exterior shape of a source model. You can use a part or an assembly as the source model for a Shrinkwrap.
Shrinkwrap models usually reduce disk and memory usage by more than 90 percent. This varies according to the complexity of the source model and the quality setting used to generate the Shrinkwrap model. Memory saving is considerable in assemblies with many hidden components. When a low to mid range quality setting is used, the Shrinkwrap model collects a smaller number of surfaces and the resulting file is smaller. The recommended method for creating a Shrinkwrap model is to try various combinations of settings for different models to obtain a firsthand account of the differences in file size. Create Shrinkwrap models to perform the following tasks:
• Represent complex design assemblies with one lightweight part.
• Improve system performance with large assemblies (Shrinkwrap models load faster than complex models).
• Provide an accurate external representation of the model for use by other design teams, suppliers, or customers, without disclosing the model's internal design. Others can visualize the product and conduct space claim studies, form and fit studies, interference checking, and so forth, while you protect trade secrets, patented designs, and other proprietary information.
• Control and handle the amount of information included in the model:
◦ Close holes and gaps.
◦ Control the level of detail.
◦ Assign exact mass properties from the original model.
◦ Include additional datum geometry referenced from the original model.
◦ Export to standard formats, such as IGES, STEP, and VRML.
◦ Use as standard assembly components.
◦ Produce a visualization of complex assemblies using tools such as Windchill and the Web.
Shrinkwrap models can be created automatically or manually by specifying surfaces to be included in the model. The Shrinkwrap model is stored as a separate part file.
|
|
 Shrinkwrap models are not associative. They do not update when the source model is modified. |