> 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-boltline.md). # Teamcenter to Boltline ## Overview Sync data from Teamcenter >> Boltline to keep parts and BOMs synchronized across systems.
Violet provides full observability into data sync status, metrics and error logging, as well as tailored notifications via email or Slack.

Fine-grained metrics are tracked for each integration and data sync

View a high level summary of data sync progress or delve into the details

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.

Multisource Reports structure data from disparate systems into an always-up-to-date report.

Create charts and visualizations in Multisource Reports.

## 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 Boltline and create an integration First, connect Boltline in Violet, making sure to fetch **Parts** (instructions [here](/apps/b/boltline.md)) {% endstep %} {% step %} #### Connect 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).
* Configure any rules for your data sync, for example only pushing released parts and assemblies, or only syncing parts with certain suffixes or prefixes.
* When you have finished configuring the sync, click **SAVE.** {% 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.\ \ *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 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-boltline.md?ask=&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.