Set up Teamcenter integration

Once Violet and Teamcenter are connected, you can configure your integration and any desired automations (i.e., pushing Teamcenter data to other tools)

Note: Setting up a Teamcenter integration can be a little involved depending on how your Teamcenter environment is configured. If you have any questions, don't hesitate to reach out to us!

Configuring your Teamcenter Fetch

Basic Fetch Configuration Options

  • Fetch Frequency: Options range from 10 minutes to 1 week

  • Types of Data to Fetch: You can choose to fetch Parts (will fetch part metadata, as described here) and/or Files.

If you choose to fetch Files, you will also need to configure a few more fields:

  • Method for and information for File requests: either Active Workspace URL or Group Name and FSC ID

  • [OPTIONAL] Import format for 3rd party files if zip exports are detected: Most users can leave this blank, but if you expect zip files in Teamcenter to be in a specific format you can choose it here.

Advanced Fetch Configuration Options

There are several additional options in the "Advanced Fetch Configuration" section. These help to ensure that you are fetching only the Teamcenter Projects that you want to pull into Violet, and that we are correctly mapping the Item Revision, ID, Part Name, and Part Description information from Teamcenter into Violet. If you're not sure which Teamcenter objects or fields you use, contact your Teamcenter adminstrator or us, and we can help you figure it out.

Configuring your Teamcenter Pushes

Basic Push Configuration Options

Choose any apps that you would like to push Teamcenter data to from the drop-down menu. This menu will show all of the connected apps that can accept data pushed from Teamcenter. You must connect the apps that you wish to push to first, or they will not appear here.

Once you have selected the app(s) that you wish to push Teamcenter data to, you can configure the push options.

  • Required Release Status: You must choose which combination of released or un-released parts you want to push

There are several additional options regarding what to include or exclude when pushing from Teamcenter to another app. You may leave these in their default configuration, or update them depending on how you plan to use the data that you are pushing.

mBOM Management in ION

If no mBOM exists for an assembly that you push to ION, Violet will generate a v1 mBOM when that assembly is pushed. If an assembly does have an existing mBOM, Violet will update the latest version mBOM if that version is not locked (i.e., in DRAFT mode or IN_REVIEW with no reviewers). If the latest version of the mBOM is locked, Violet will not update the mBOM or create a new mBOM version when the push occurs.

With the "Set status to Released in Ion" option checked, Violet will immediately release the v1 mBOM that it created on the first push of a new assembly. That mBOM is then locked until someone manually creates a new mBOM version, or transitions the v1 mBOM back to DRAFT. This allows users to treat the originally pushed assembly BOM as an eBOM, and then create new mBOM versions that will not be affected by subsequent pushes from the PLM.

Advanced Push Configuration Options

You also have the option to allow or exclude sets of parts with a certain prefix or suffix if you do not want to push these parts. For example, you may use a particular suffix for design-only parts that do not need to be pushed to your inventory management system.

If you have questions about setting up your configuration or want to discuss best practices, please get in touch with us and we can talk it through with you.

More Resources

Check out our Automations guide for more information on data syncing.

Last updated

Was this helpful?