> 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-ion.md).
# Teamcenter to ION
## Getting started
Follow the instructions below to automatically sync data from [Teamcenter](/apps/t/teamcenter.md) to [ION](/apps/i/ion.md):
{% stepper %}
{% step %}
### Create a Teamcenter integration
First, create a Teamcenter integration following the instructions [here](/integrations/s-z/teamcenter.md). Configure your data fetch, specifying:
* The types of data you want to fetch (`parts`, `files`, `change orders`, etc).
* Fetch frequency, for example every 1 hour, 10 minutes, etc.
{% endstep %}
{% step %}
### Create an ION integration
Next, set up an ION integration, following the instructions [here](/apps/i/ion/generate-api-credentials-in-ion.md). Configure your data fetch, specifying:
* The types of data you want to fetch (`parts`, `runs`, `purchase orders`, etc).
* Fetch frequency - this is either scheduled, eg. every 1 hour, 10 minutes, etc., or event-driven via webhooks.
Violet will need to fetch whichever data you wish to be synced from Teamcenter (eg. `parts`).
{% endstep %}
{% step %}
### **Configure sync workflow**
Head to [Workflows](/features/workflows.md) to configure your sync, including desired trigger, property mappings, business logic, etc. \
\
For example, only sync **Released** parts, parts with a certain suffix or prefix, etc.
{% endstep %}
{% endstepper %}
### One-time data syncs
Alternatively, you can push parts to ION 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 ION.
### Revision Schemes
Violet will detect the part revision scheme(s) available in your ION integration. From there, you can update the selected scheme within ION.
## 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-ion.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.
Teamcenter integration
First, create a Teamcenter integration following the instructions [here](/integrations/s-z/teamcenter.md). Configure your data fetch, specifying:
* The types of data you want to fetch (`parts`, `files`, `change orders`, etc).
* Fetch frequency, for example every 1 hour, 10 minutes, etc.
{% endstep %}
{% step %}
### Create an 
ION integration
Next, set up an ION integration, following the instructions [here](/apps/i/ion/generate-api-credentials-in-ion.md). Configure your data fetch, specifying:
* The types of data you want to fetch (`parts`, `runs`, `purchase orders`, etc).
* Fetch frequency - this is either scheduled, eg. every 1 hour, 10 minutes, etc., or event-driven via webhooks.
Violet will need to fetch whichever data you wish to be synced from Teamcenter (eg. `parts`).
{% endstep %}
{% step %}
### **Configure sync workflow**
Head to [Workflows](/features/workflows.md) to configure your sync, including desired trigger, property mappings, business logic, etc. \
\
For example, only sync **Released** parts, parts with a certain suffix or prefix, etc.
{% endstep %}
{% endstepper %}
### One-time data syncs
Alternatively, you can push parts to ION 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.*