Starting from release R2019x FD03,  Product Processor ​​​​​, the Data Preparation batch, accepts stored Filters as input.

Filters can be created with " ENOVIA Product Finder" by explicitly selecting items to keep or remove, or using volume search. Through the command "Store Filter"  they are saved in the 3DEXPERIENCE platform.

The user interface of Product Processor stays unchanged. Using the"3DEXPERIENCE Object Search" command one can select type "filter" (as an alternative to Physical Product) and retrieve a stored filter.

When processing this object, only selected items of the complete structure are opened, isolated and optimized. Consequently, processing time is highly reduced.

Filters prove to be useful with Product Processor in two use cases:

1. When searching for the right values to be used with a given DataPrep Operation:

• Create a filter selecting few representative shapes (e.g. from a car, one exterior shape like the hood, the brand logo, and a BIW element).
• Then run Product Processor on the filter with various combinations of parameters.
• When satisfied with the result, run Product Processor again on the complete assembly.
  

2. When aiming to prepare a sub-system composed of elements disseminated in the assembly structure. Filter enables to select them and keep their relative positioning.

Let's have a look at an example

In the case of this smart kitchen appliance, the objective is to create a simplified representation of a spare part, the blade system.

With ENOVIA Product Finder, the filter is created by selecting sub-elements of the spare part and stored as "Nestor_tools".

Then the stored filter is provided as an input to Product Processor, and simplified following a given DataPrep Operation.

The result is a simplified model of the spare part containing six times less triangle than the original one!