# Teamcenter to ION
## Getting started
Follow the instructions below to automatically sync data from [teamcenter](https://docs.violetlabs.com/apps/t/teamcenter "mention") to [ion](https://docs.violetlabs.com/apps/i/ion "mention"):
{% stepper %}
{% step %}
### Create a Teamcenter integration
First, create a Teamcenter integration following the instructions [here](https://docs.violetlabs.com/integrations/s-z/teamcenter). 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](https://docs.violetlabs.com/apps/i/ion/generate-api-credentials-in-ion). 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 [..](https://docs.violetlabs.com/features/workflows "mention") 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.\
\
\&#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 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](https://docs.violetlabs.com/features/workflows/observability "mention").
Teamcenter integration
First, create a Teamcenter integration following the instructions [here](https://docs.violetlabs.com/integrations/s-z/teamcenter). 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](https://docs.violetlabs.com/apps/i/ion/generate-api-credentials-in-ion). 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 [..](https://docs.violetlabs.com/features/workflows "mention") 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.\
\
\&#xNAN;*Note, if this part is an assembly, the entire assembly will be pushed.*