Enterprise Administration > Windchill Export and Import > PTC Windchill PLM Connector - Creo Packages Administrator's and User's Guide > Creo Packages > Getting Started with Creo Packages > Collaboration Using Creo Packages
  
Collaboration Using Creo Packages
Creo Packages supports a read-only collaboration methodology for sharing any Creo Parametric data in two or more PLM systems. This enables the exchange of Creo Parametric designs data between source and target PLM systems without compromising your PLM content management system.
Collaboration also occurs when the owner of the original object wants to relinquish ownership of that object to a new owner. This collaboration can occur between PLM systems or within the same PLM system. During the ownership transfer process, the original owner relinquishes ownership of Creo Parametric data to the new owner, which becomes recognized as the new owner PLM system for that data.
* 
Presence of Private Checkout copy does not impact Creo packages import. If the user wants to use Privately modified CAD content copy into the Collaboration, user should have ownership of the same to proceed with Regular Checkout and merge the content.
A Product is Collaboratively Designed in More Than One PLM System
A typical use case is where a product is collaboratively designed in more than one PLM system. One PLM system may be responsible for a top assembly, while a different PLM system may be responsible for one 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.
For example, a company is developing a bicycle with an external design partner who manufactures drivetrains for bicycles (the gears and gear changes etc.).
The bicycle company and the drivetrain manufacturer might follow the following process to collaborate the design project using Creo Packages:
Steps
Bicycle Company
Drivetrain Partner
Step 1—Select data for collaboration
Creates a basic bicycle assembly which could include a skeleton providing all the interface points in the bicycle and stores in their PLM system.
Creates one or more drivetrain subassemblies with basic geometry, with the key interface points and stores in their PLM system.
Step 2—Initial exchange of data to establish collaboration
Uses Creo Packages to export the drivetrain subassemblies and sends the exported package to the bicycle company.
Step 3
Uses Creo Packages to import the drivetrain subassemblies into the bicycle company PLM system.
* 
The imported drivetrain subassemblies are read-only in the bicycle company PLM system.
Step 4
Adds the drivetrain subassemblies to the bicycle assembly.
* 
The imported drivetrain subassemblies are not modified when they are added to the bicycle assembly.
Step 5
Uses Creo Packages to export the drivetrain subassemblies and the bicycle assembly with references to the imported drivetrain subassemblies and sends to drivetrain partner.
Step 6
Uses Creo Packages to import the bicycle assembly with references to the drivetrain subassemblies.
* 
Since the drivetrain subassemblies are already in the drivetrain partner’s PLM system, they are not imported.
Step 7—Work in process stage
Continues development of the bicycle assembly making changes and adding new subcomponents.
Continues development of the drivetrain subassemblies making changes and adding new subcomponents.
Step 8—Periodically exchange updates
Periodically sends updates (incremental packages) of the bicycle assembly.
Periodically sends updates (incremental packages) of the drivetrain subassemblies.
A Product is Collaboratively Designed in More Than One PLM System with Eventual Object Ownership Transfer
A typical use case is where a product is collaboratively designed in more than one PLM system. One PLM system may be responsible for a top assembly, while a different PLM system (the ODM) may 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 PLM system owner transfers the ownership of the design or product to a PLM system design partner or supplier whom assumes full responsibility of ownership for that design or product.
For example, a company is developing a bicycle with an external design partner who manufactures drivetrains for bicycles (the gears and gear changes etc.). During the course of the bicycle design the external design partner provides updates of the drivetrain subassemblies to the bicycle company.
The bicycle company and the drivetrain manufacturer might follow the following process to initiate and complete the design of the drivetrain subassemblies and for the drivetrain partner to eventually transfer ownership of the drivetrain subassemblies to the bicycle company.
Steps
Bicycle Company (OEM)
Drivetrain Partner (ODM)
Step 1—Select data for collaboration
Creates a basic bicycle assembly which could include a skeleton providing all the interface points in the bicycle and stores in their PLM system.
Creates one or more drivetrain subassemblies with basic geometry, with the key interface points and stores in their PLM system.
Step 2—Initial exchange of data to establish collaboration
Uses Creo Packages to export the drivetrain subassemblies and sends the exported package to the bicycle company (OEM).
Step 3
Uses Creo Packages to import the drivetrain subassemblies into their source PLM system.
* 
The imported drivetrain subassemblies are read-only in the bicycle company source PLM system.
Step 4
Uses Creo Packages to add the drivetrain subassemblies to the bicycle assembly.
* 
The imported drivetrain subassemblies are not modified when they are added to the bicycle assembly.
Step 5
Uses Creo Packages to export the bicycle assembly with references to the imported drivetrain subassemblies and sends the exported package to the drivetrain partner (ODM).
Step 6
Uses Creo Packages to import the bicycle assembly with references to the drivetrain subassemblies.
* 
Since the drivetrain subassemblies are already in the drivetrain partner’s PLM system, they are not imported.
Step 7—Work in process stage
Continues development of the bicycle assembly by making changes and adding new subcomponents.
Continues development of the drivetrain subassemblies by making changes and adding new subcomponents.
Step 8—Periodically exchange updates
Uses Creo Packages to periodically send updates (incremental packages) of the bicycle assembly to the drivetrain partner (ODM).
Uses Creo Packages to periodically send updates (incremental packages) of the drivetrain subassemblies to bicycle company (OEM).
Step 9—Collaboration to transfer ownership from ODM to OEM
Collaborates with drivetrain partner (ODM) to acquire ownership rights of the drivetrain subassemblies.
Collaborates with the bicycle company (OEM) to relinquish ownership rights of the drivetrain subassemblies.
Step 10—ODM partner initiates ownership transfer
Uses Creo Packages to send ownership transfer package to the bicycle company (OEM).
Step 11—OEM accepts and imports ownership transfer package
Uses Creo Packages to receive and import the ownership transfer package in their source PLM system.
Step 12—OEM sends acceptance of receipt to ODM
Uses Creo Packages to send receipt package (master synchronization package) to the drivetrain partner (ODM).
Step 13—ODM receives and imports acceptance of receipt
Uses Creo Packages to accept and import receipt package (master synchronization package) from the bicycle company (OEM)
Step 14—OEM and ODM sends acceptance of receipt of ownership package (master synchronization package)
The new owner (bicycle company) sends the master synchronization package to any other PLM systems in receipt of the bicycle assembly.
The original owner (drivetrain partner) sends the master synchronization package to any other PLM systems in receipt of the drivetrain subassemblies.