TeamcenterKnowledge

Modeling systems > Managing branches with collaborative modeling

What are branches?

Branches are part of a system model project that allow for parallel development of individual aspects of the overall project. For example, a system model for a car's drivetrain can have a main branch and multiple child branches:

  • The main drivetrain branch for the system modeling project.
  • A child branch created from the main branch to track work on the engine component.
  • Child branches created from the Engine branch to track work for the engine components of the Chassis and Piston.
  • A tag created for the main branch for the BETA release milestone.
  • Visual indicators for the branch that show if it has a parent branch and key events, such as branch-outs and merges.

Managing branches in Teamcenter

When work on a child branch is complete, it can be merged into its parent branch from the system modeling application. There may also be experimental branches that you do not want merged into the main branch — these can just be removed from the project.

Note: Teamcenter can only manage the system modeling properties and the related branches. Changes to the actual design must be done within the integrated system modeling application and then saved to Teamcenter by committing the changes.

Source: https://docs.sw.siemens.com/en-US/doc/282219420/PL20251212545240207.MBSE/bjg8517138143873 · retrieved 2026-07-10