After you have identified the Creo Parametric models to export: set the export preferences, set the conflict overriding preferences, and resolve any conflicts before exporting a package from the source PLM system.

Creo Parametric users can create packages on an ad-hoc basis by setting criteria within a recipe file.

For example, an engineer is tasked with creating a package to be shared with a supplier. The criterion required is “all dependents” and “latest within work.” Additionally, Creo Parametric drawings need to be included as part of the collected items. The criteria is created within the export recipe file by specifying the name of the seed objects in the command line and exporting the package. This scenario is referred to as a manual ad-hoc export.

System administrators can create packages on a regular periodic and recurring basis by setting specific rules within a recipe file and creating custom batch files to execute the package export.

For example, an administrator needs to set up a system where the contents in the folder of the source and the destination system are synchronized. To do so, the administrator sets up an export recipe file to specify the location of the folder and its subfolders, and schedules a package creation to occur daily at midnight. Furthermore, the package should not contain previously published content. The administrator specifies all these rules in a manual periodic export recipe file, and writes a script to automatically export the package into certain locations daily.

A typical use case is where a product is collaboratively designed in more than one PLM system. One PLM system might be responsible for a top Creo Parametric assembly, while a different PLM system might be responsible for one or more of the subassemblies. Read-only collaboration is established based on the assumption that only the owner PLM system makes updates to their own Creo Parametric data.

A collective decision is made where the original owner transfers the ownership of an object to another PLM system whom assumes full responsibility of ownership for that object.

Object ownership transfer allows for the transfer of an object from the original owner to a new owner using a complete package and then a master synchronization package to complete the ownership transfer.

For example, the original owner sends a complete package for ownership transfer to the prospective new owner. The prospective new owner imports this package in their PLM system. The new owner sends a master synchronization package to the original owner and other PLM systems that they exchange data with containing the object data. In turn, the original owner imports the master synchronization package in their PLM system and sends the master synchronization package to other PLM systems that they exchange data with that also contains the object data.

In general, transfer of object ownership should happen only once or at most twice in the life of an object. In many cases, it never happens. Ownership transfer should not be performed casually, and should never be used as an alternative to fulfill an object’s round tripping modification.

PTC customers who use Windchill ProjectLink in a bundled server environment with Windchill PDMLink also installed can export objects from projects for use with Creo Packages provided that they meet the following requirements:

Objects that cannot be exported out of projects are the following:

You can export packages from Creo Packages for import to Windchill ProjectLink by doing the following:

Creo Packages allows you to import packages from Windchill ProjectLink to a source PLM system by doing the following: