About collaborative modeling

Collaborative modeling in System Modeler allows you to collaborate with other teams when working on a project model. Each team can work on their own branch of the main product to work in parallel and complete the overall work faster.

The benefits of collaborative modeling

With collaborative modeling in Teamcenter, you can:

• Navigate project branches and commits in a timeline to enhance project clarity.
• Create, edit, and remove branches as necessary during the lifecycle of the project.
• Track key modeling events, such as branch merges, for better project traceability.
• Enable the creation of parallel branches for testing ideas without impacting the main branch.
• View commit details, such as the author, date, and description, to understand the full context of the project.
• Assign tags to product versions to keep track of release milestones across the various branches.
• Search existing tags to quickly find the branches assigned to the tags.

Example

In the workflow: a car project system model is published to Teamcenter and the master branch (A) is created. This is the main work branch for the car project. The team performs iterations of the product on this branch, and commits changes leading to release 1.1 and 1.2. During release 1.2, a new branch is created for another team to work on the audio (B) aspect of the product.

The master branch (A) and audio branch (B) are now being worked in parallel. With release 1.3 of the main product and 1.2 of the audio product, a new branch is created from these releases to make the MP3 support (C) branch. Now there are three teams working in parallel on the car project.

The main branch team assigns a tag to release 1.4 of the product to track a milestone of the first release candidate version. As work continues on all three branches, the audio branch work is complete with release 1.2 and is merged into release 1.4 of the audio system branch. When work on the audio system branch completes in release 1.5, it is merged with the main branch release of 1.7.

A new tag is then assigned to the main branch for the second release candidate milestone that now includes the completed work on the audio system with MP3 support.