A typical use case is where Site A collaborates with Site B (collaborating for Product B) and Site C (collaborating for Product C). Each target PLM system site (Site B and Site C) receives a different incremental package from Site A (source PLM system site).

Site A creates different export preferences in the wpc_preferences.txt file for Site B and Site C by configuring the output baseline names to be target PLM system site specific. For example, the output baseline name is site_b_export_baseline_name for Site B, while the output baseline name is site_c_export_baseline_name for Site C.

Additionally, Site A creates different recipe files for Site B and Site C by configuring the different pattern of baseline names to be used for the incremental package being created. For example, rules to subtract any baseline with “site_b” prefix, or “site_c” prefix. This rule is chosen because a component in the Creo Parametric assembly has already been sent to Site B previously, but has not yet sent to Site C. Site A must include this additional component in the incremental package being created for Site C. However, if the same set of package components is being sent to Site B and Site C, one recipe file can be used for the package export.

Also see Collaboration Using Creo Packages.