> 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/apps/t/teamcenter.md).

# Teamcenter

Fetch, sync and report on part and assembly data from [Siemens Teamcenter PLM](https://plm.sw.siemens.com/en-US/teamcenter/).

<img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2FFQP5Mi8OSlNSGiu9gGqc%2FScreenshot%202024-05-28%20at%206.43.25%E2%80%AFPM.png?alt=media&amp;token=c3b7e031-27ee-45e3-a98b-3a4a0ee819ba" alt="A Teamcenter assembly in Violet" width="375">

Violet structures and stores Part metadata as well as associated files like 2D drawings or 3D models.

From there, you can sync data and files to downstream applications like [NetSuite](/apps/n/netsuite.md), [ION](/apps/i/ion/generate-api-credentials-in-ion.md), [Manufacturo](/apps/m/manufacturo.md), [Boltline](/apps/b/boltline.md), [Cofactr](/apps/c/cofactr.md) and more.

Data can be synced on an individual basis or for an entire integration - requiring no manual intervention. See our [Example syncs](/features/workflows/data-sync-workflows/example-syncs.md) for more info.

### Getting started

To get started, follow the instructions below:

* For **on-premises** implementations:
  * Connect [directly to your Teamcenter SQL database](/apps/t/teamcenter/connect-direct-to-database.md) (recommended for faster performance)
  * Connect [via the Teamcenter API](/apps/t/teamcenter/connect-via-api.md) (necessary for files)
* For **cloud** implementations, follow the instructions for [Teamcenter X](/apps/t/teamcenter/connect-teamcenter-x.md)

Or, continue reading to learn more about how it works:

* [Supported data types](/apps/t/teamcenter/supported-data-types.md)
* [Teamcenter property mapping](/apps/t/teamcenter/teamcenter-property-mapping.md)
* [Teamcenter FAQ](/apps/t/teamcenter/teamcenter-faq.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 dynamically 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/apps/t/teamcenter.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 `build a script that syncs our docs to a CMS` 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.