image image
Bezoek het Blog van PLMConsult Discussieer met PLMConsult op het Blog
Laatste Blog:  The impact of Kraljic on your  Teamcenter Implementation  
Lees het hele verhaal
Het uitgangspunt van PLMConsult Het uitgangspunt van PLMConsult voor haar diensten is uw probleem en hoe dit in eerste instantie organisatorisch kan worden opgelost. Lees het hele verhaal

How to handle simple Configuration Management with Teamcenter.

Gebruikerswaardering: 2 / 5

Ster actiefSter actiefSter inactiefSter inactiefSter inactief


In many cases it is necessary to trace an exact configuration of a product. During development it can be that you want to store a configuration at a milestone. When you deliver a product, you want to know how the configuration was at the time it was delivered.



With complete Configuration Management you need to have a minimum of 3 structures of a product:

  • As-Designed
  •  As-Build
  • As-Maintained

From every structure you can keep track of the changes on a particular structure. It is also possible to make a comparison between the structures.

In the As-Build and As-Maintained structures the changes are End-Item, serial numbers driven.

Teamcenter can use these structures, but you need to buy modules like:

  • A-Build Manager
  • Service Manager


  • MRO Module

For a lot of companies this will be to complex, so they need to find another more simple solution.


How to manage configurations at a milestone?

During the development of a product design, you may want to share your working design with other users based on so called Milestones.  You need to keep track on all the milestones during this process. To do this, you can create a baseline of the work-in-progress. When you request a baseline, Teamcenter creates a new dataset and attaches a copy of the currently configured structure to it. It creates a new revision for each unreleased revision in the structure and releases it with a predefined status, for example, Milestone1. It then applies a baseline revision rule to configure the base configuration; it also includes any new revisions created by the baseline. This method configures a completely released structure and thereby guarantees that the models are the same as when the baseline was created. This approach may be expensive as many new revisions might be created and (with them) copies of the associated data and CAD models. 


Before we can create the first baseline, we need to define the workflows. With these workflows we can create a status to the baselines based on the Milestone.  As a basic you can use the OOTB WFL TC Default Baseline Process.  The only thing you have to change is the status.

 After you created the WFL’s you need to set the Preference for the Baseline Release Procedures.




Now we can start to create our structure:




In this case it is a simple structure with no datasets related to it.


To create the Baseline select the Top menu:

·         Tools

o   Baseline….



The system will open the Baseline.. input form.  The system will create a new revision A.0001. In the Baseline Template you can define the Workflow used for the Baseline. In our case this will be Baseline Milestone1.




Be aware that creating a Baseline means it will make a copy of all the data, including the related Datasets. All the ItemRevisions in this Structure will be copied from Revision A à A.001


Because of the Workflow we used in this case, the ItemRevision will have the Status Milestone1




After this we can make some changes to the original structure. For example we can add an Item to the top level.


To check the differences you can open the BomViewRevision 000231/A and 000231/A.001 and do a Compare.




If you want to keep track of all the milestones in the development process and compare the Structures based on these Milestones, Baseline is a strong functionality.

You have to be aware that for every baseline a copy is made of all the data. If you have big structures with a lot of NX Data, this will generate a lot of data.

Optionally, you can implement smart copy of baselines by setting the

ITEM_smart_baseline preference. In this mode, only item revisions that have changed since the last baseline are copied into the new baseline and unchanged item revisions are referenced. Use the smart copy mode if you create large numbers of baselines, as each baseline occupies a significant amount of storage space.


Baselines can only be used for ItemRevisions with no status.

Next blog I will talk about How to keep track on Released Data by using Snapshots.

I hope this blog can help you in using Teamcenter and if you have any questions, do not hesitate to leave a comment or send an email 


October 2013

Menk Slot



Plaats reactie


Hoofdcategorie: ROOT