In short, you have separate change branches for a given item revision that are split. Then you start developing two different versions of one item in parallel.
This satisfies your needs and gives you numerous possibilities. You can create separate changes for separate needs, simply use it as you want!
At some point, you may want to merge these two parallel versions of the product together. What would you do with changes that affect the same products but are resolved differently?
Don’t worry. With Teamcenter Active Workspace 6.2, we’ve introduced change merge function to help you to put your separate changes together. You can now merge an unincorporated released change in the current in-progress product design. While doing so, you can review the differences between two assembly versions side-by-side. You can merge one or all of the changes from source change to target change.