> For the complete documentation index, see [llms.txt](https://docs.violetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violetlabs.com/features/workflows/data-sync-workflows/example-syncs/teamcenter-to-cofactr.md).

# Teamcenter to Cofactr

## Getting started

Follow the instructions below to automatically sync data from [Teamcenter](/apps/t/teamcenter.md) to [Cofactr](/apps/c/cofactr.md):

{% stepper %}
{% step %}

### Connect <img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2FeBbOK3l5R3853HsDmFdW%2Fcofactr.png?alt=media&amp;token=2d5388cb-b82c-4eaa-ac80-c3b6b629fceb" alt="" data-size="line">Cofactr and create an integration

First, set up and configure your Cofactr integration, following the instructions [here](/apps/b/boltline.md). \
\
Ensure that you are fetching the data types that you wish to sync. For the Teamcenter to Cofactr sync, you must at least select **Parts** and **BOMs**.
{% endstep %}

{% step %}

### Connect <img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2FbGCfobaGlsNcIsh6aA04%2Fimage.png?alt=media&amp;token=3e4643c1-815e-4feb-a163-e9fec1776dce" alt="" data-size="line"> Teamcenter and create an integration

Next, connect Teamcenter and create your integration (instructions [here](/apps/t/teamcenter.md)).
{% endstep %}

{% step %}

### Configure data sync

Last, select Cofactr as the destination for automated syncs.

<figure><img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2FQ9CmDn4STBmXXplWDZOc%2FTC-Cofactr-sync.png?alt=media&amp;token=d6fd22e0-44a8-4ed9-b654-e5650b977b4f" alt="" width="375"><figcaption></figcaption></figure>

\
Here is where you will also configure any rules for your sync, for example only pushing parts or BOMs based on **Release** status.

<figure><img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2F6DJMNDfqeMXhWsbAwOfP%2FTC-Cofactr-sync-config.png?alt=media&amp;token=26ad23c3-3441-4364-a655-9f29ac46f316" alt="" width="375"><figcaption></figcaption></figure>

When you have finished configuring the sync, click <mark style="color:purple;">**SAVE**</mark>**.**
{% endstep %}
{% endstepper %}

#### One-time data syncs

Alternatively, you can push parts and BOMs to Cofactr on a one-off basis.

1. Navigate to the desired Teamcenter part in Violet. Under **Automations**, select your target app and click Push. If you choose an assembly, the entire assembly will be pushed.
2. Once successful, you will now see this part or assembly in both Violet and Cofactr. Any future pushes will update existing parts and/or create new parts intelligently (it will not duplicate data).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.violetlabs.com/features/workflows/data-sync-workflows/example-syncs/teamcenter-to-cofactr.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.