Reconciling a Filtered Product Structure

In ENOVIA V5 VPM, you can reconcile data extracted from a filtered product structure using Expand Capture (PVS), an attribute, volume or configuration filter. The process for the reconciliation doesn't change except that after mapping your structure to ENOVIA V5 VPM you must apply the correct filter to the VPDM view.  Once the VPDM view is filtered, the reconciliator can accurately calculate the changes that need to be integrated into ENOVIA V5 VPM.  Using a filtered view of the product structure saves resources and time by sending only necessary parts of the structures to suppliers.  For security and/or privacy reasons, there may be instances when you must not send all parts of your structure to a particular supplier. 

The scenario in this document shows how to use a configuration filter to reconcile a configured product structure.

To simplify the Reconciliation process and extraction of a batch utility, you can support Expand Capture (PVS) and add attribute, volume or configuration criteria for your filter.
Click Filter on PRC in the Reconciliator toolbar, the Filter dialog box appears.

Follow these steps to define filter criteria in the Reconciliator:

1. Click the Expand capture search button to search for existing Expand Capture. The Expand Capture Search dialog box appears.
   

2. Select one of the Search Parameters and click the Search Expand Capture button. The Search Results displays the list of existing Expand Capture.
   Note: To clear the current search criterion, click Reset Search Criterion .

   The options of using Expand Capture or selecting attribute predicates, zones, and config Handler for defining a product filter are mutually exclusive. Thus, only one of these selections is valid at a time. If PVS is created on a filter which is not supported by Reconciliation (for example, Part in Volume filter), such filter is ignored for filter execution as the result would be different.

   

3. Click the Add button, to add Attribute criteria.
   

4. Choose the Attribute Name and Operator from the respective lists.  Type a search string in the Searched String box.
   Click OK.
   The search predicate is added to the attribute filter criteria.
   

5. To remove a predicate, select the row and click the Remove button.

6. To add volume criteria, select from the Available zones and enter the Mode and Clearance information.  Please see the VPM Navigator User Guide > Basic Tasks > VPM Navigator > Filtering > Filtering by Volume for more information on using volume filters.

7. To select the zones you want to filter with, select a zone name in the Available zones list.  Click >| to move that zone into the Selected zones list.  >>| will move all the zones into the Selected zones list.  Similarly, to remove zones from the Selected zones list, select a Zone Name and click |<.  Clicking |<< removes all zones from the Selected zones list.
   
   Please see the VPM Navigator User Guide > Basic Tasks > VPM Navigator > Filtering > Filtering by Zone for more information about volume filters.

8. To add configuration criteria, select from the list of configuration handlers that have been defined for the PRC.  Configuration criteria can only be defined using a configuration handler. Please see the VPM Navigator User Guide > Basic Tasks > VPM Navigator > Filtering > Filtering by Configuration for more information on configuration filtering and configuration handlers.
   

This scenario uses the data from Use Case 1: Reconciling a Product Structure.    To illustrate using a filtered view in the reconciliator process, we will add an additional part, a brake to the skateboard.  The basic skateboard will be represented by units 1-50 and will be composed of the board and two hub assemblies with an axle and two wheels each.  From units 51 to infinity the skateboard will also contain a brake. The basic skateboard (filtered by units 1 to 50, therefore with no brake) is sent to the supplier for modification.  When the supplier modifications are returned, we must apply the same filter, so the reconciliator knows that the brake was not deleted by the supplier.  Instead, the brake should never be considered in the comparison. 

To simulate the above scenario,

• Load the original skateboard, Skate-100-ABC-1001.CATProduct, from Use Case 1: Reconciling a Product Structure  into ENOVIA V5 VPM (in the Before you begin part of Use Case 1).  This is the data that corresponds to what has been sent to the supplier - in our case, the basic skateboard (a board and two hub assemblies that each contain an axle and two wheels). 

• Add effectivity to the product structure.  In VPM Navigator, open the skateboard and use the Configure Part command to configure the skateboard, hub, axle, wheel and board.  Note that you are configuring the actual references (components) so it is not necessary to configure each instance of each part.  Add R(1 to infinity) effectivity to each instance in the structure using the Assign Effectivity to Instance  button. 

• Insert an additional part into the structure, Brake-000.  It is not important to associate a CATPart to the brake because we will need to filter it out of the structure that is going to be reconciled anyway.  Since the data given to the supplier was only the basic skateboard, if we don't filter out the brake, when we reconcile the data returning from the supplier (that does not contain a brake), the reconciliator will want to delete the brake.  Save the brake to ENOVIA V5 VPM.  Open the skateboard in VPM Navigator and configure the brake and apply R(100 to infinity) effectivity to it. 

• Execute the Use Case 1: Reconciling a Product Structure scenario through step 5.

• In VPM Navigator, create a configuration handler for the skateboard using an effectivity of R(1 to 50).

1. Once the mapping has been established between Skate2-100-ABC-1002 and Skate-100-ABC-1001, the filter on PRC button becomes available in the top toolbar of the Reconciliator Window.

2. Select the VPDM View tab.

   The VPDM view should represent the basic skateboard that was sent to the supplier, but since it is not filtered we see all the parts, including the brake. 

3. Click the filter on PRC button.
   The Filter window appears.

4. Define a configuration handler containing R(1 to 50) as the filter criteria for the VPDM view.

5. Click OK on the Filter window.

   The VPDM view is now filtered for units 1 to 50 just as the data sent to the supplier was filtered.  The reconciliator can now accurately compare the structures.

6. Continue with steps 6-10 in Use Case 1: Reconciling a Product Structure to complete the reconciliation of this product structure. 
   Note:

   • when you are saving configured parts, the Create configured part references portal setting in ENOVIA Product Editor may need to be set to true if you need any new parts to be created as configured.

   • when saving your changes to ENOVIA V5 VPM you can use the Save Under Action option to resolve the effectivity of the supplier changes.  Please see the VPM Navigator User Guide > VPM Configured Product Design > Saving Objects > Saving Changes Under an Action for more information about using an action to resolve modifications.