# Teamcenter to Boltline

## Overview

Sync data from Teamcenter >> Boltline to keep parts and BOMs synchronized across systems.

<figure><img src="/files/knpmUA1BulKTKPAPxH6W" alt=""><figcaption></figcaption></figure>

Violet provides full observability into data sync status, metrics and error logging, as well as tailored notifications via email or Slack.

<figure><img src="/files/qO4salSvVNqFsHrb9FB7" alt="" width="563"><figcaption><p>Fine-grained metrics are tracked for each integration and data sync</p></figcaption></figure>

<figure><img src="/files/Mz7LvIvbcWZmRCeL1fxW" alt="" width="563"><figcaption><p>View a high level summary of data sync progress or delve into the details</p></figcaption></figure>

With data centralized and structured into Violet's ontology, you can manage and track data from disparate sources seamlessly. For example, use [Reports](/features/reports.md) to track part, inventory, test and purchasing data in a single report, monitor Clear-to-Build status or highlight differences across your EBoM and MBoM.

<div align="center"><figure><img src="/files/EvtKvpvZNSADQyci7bX0" alt="" width="563"><figcaption><p>Multisource Reports structure data from disparate systems into an always-up-to-date report.</p></figcaption></figure></div>

<figure><img src="/files/zPG6VqMxgyRaLBZ67xDU" alt="" width="563"><figcaption><p>Create charts and visualizations in Multisource Reports.</p></figcaption></figure>

## Getting started

Follow the instructions below to set up a data sync from [Teamcenter](/apps/t/teamcenter.md) to [Boltline](/apps/b/boltline.md)

{% stepper %}
{% step %}

#### Connect <img src="/files/WTUOwkBgzASZaVIU7Qoj" alt="" data-size="line"> Boltline and create an integration

First, connect Boltline in Violet, making sure to fetch **Parts** (instructions [here](/apps/b/boltline.md))
{% endstep %}

{% step %}

#### Connect <img src="/files/Oxt4MGAV3BCAl7ZSVJQZ" alt="" data-size="line">Teamcenter and create an integration

Next, set up your Teamcenter integration, making sure to fetch **Parts** ( instructions [here](/apps/t/teamcenter.md)).
{% endstep %}

{% step %}

#### Configure Teamcenter data sync to Boltline

* From the Teamcenter integration panel, select Boltline as the target app from the dropdown menu for data syncs
* Configure any custom property mappings, your desired fetch frequency, and (optionally) a time window when data syncs are allowed (for example, you can set the data syncs to run overnight to avoid business hours).

<figure><img src="/files/UamB3LL5C9PHOlBTEQ4V" alt="" width="188"><figcaption></figcaption></figure>

* Configure any rules for your data sync, for example only pushing released parts and assemblies, or only syncing parts with certain suffixes or prefixes.

<div><figure><img src="/files/oPHnk8ojHZ0pNoLzeP41" alt="" width="375"><figcaption></figcaption></figure> <figure><img src="/files/svXH56BUZnyNrku8TWUV" alt="" width="188"><figcaption></figcaption></figure></div>

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

### One-time data syncs

Alternatively, you can sync parts to Manufacturo on a one-off basis.

1. Navigate to the desired Teamcenter part in Violet. Under **Automations**, select your target app and click Push.\
   \
   \&#xNAN;*Note, if this part is an assembly, the entire assembly will be pushed.*
2. Once successful, you will now see this part and its children in Teamcenter, Violet and Manufacturo.

## Observability

To learn more about monitoring performance and health & status of your data syncs, head to [Observability](/features/workflows/observability.md).


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

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

The question should be specific, self-contained, and written in natural language.
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.