# Arena to ION

## Getting started

Follow the instructions below to automatically sync data from [arena](https://docs.violetlabs.com/apps/a/arena "mention") to [ion](https://docs.violetlabs.com/apps/i/ion "mention"):

{% stepper %}
{% step %}

### Create an <img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2FjEUUf71xOyb4XakXE8Lw%2Fion.png?alt=media&#x26;token=b2154d3d-d7c2-49fe-b327-405feddc422e" alt="" data-size="line">ION integration

First, set up your Ion or Ion Gov integration, following the instructions [here](https://docs.violetlabs.com/apps/i/ion/generate-api-credentials-in-ion).
{% endstep %}

{% step %}

### Connect  <img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2Fv5CS755cKfDfwmztijnt%2Farena.png?alt=media&#x26;token=5f285858-289a-4d7c-9100-f1b4b3bf9e8c" alt="" data-size="line"> Arena

Next, connect [arena](https://docs.violetlabs.com/apps/a/arena "mention").
{% endstep %}

{% step %}

### Configure Arena integration and ION sync

Once you are connected to Arena, configure your data fetch, including:

* the types of data you want to fetch (parts, files, change orders)
* specific projects to include or exclude
* how often data should be fetched (scheduled vs. event-driven)

Last, configure your sync to ION, including:

* how often you want data to be synced
* any preferred windows of time (for example, only sync outside of business hours)
* any specific rules for what should be synced (for example, by release status)
* any custom fields or attributes
  {% endstep %}
  {% endstepper %}

<div align="center"><figure><img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2FmTAujFYabPjQCba06tw9%2FScreenshot%202025-07-11%20at%208.00.29%E2%80%AFAM.png?alt=media&#x26;token=8f63187f-5606-43d4-b00f-952bf6e58225" alt="" width="563"><figcaption><p>Arena to ION sync configuration</p></figcaption></figure></div>

### One-off syncs

Alternatively, you can push parts to ION on a one-off basis.

1. Navigate to the desired Arena 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 Arena, Violet and ION.

### Revision Schemes

Violet will detect the part revision scheme(s) available in your ION integration. You can update the selected scheme within ION at any time.

### 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").

## How does it work?

Violet retrieves BOMs, files, assembly relationships, release status, and more from Arena on an event-driven, scheduled or ad-hoc basis. Violet structures information into our purpose-built schema that enables data to be mapped and synced to any downstream tool, such as an MES, ERP or modeling & simulation environment.

Data orchestration is fully user configurable in Violet. The Violet platform syncs relevant data to ION according to any desired criteria (for example, released parts only), allows users to create matching assembly relationships, and syncs CAD files and drawings. Violet provides full observability into data sync status, metrics and error logging, and can provide tailored notifications to users via email or Slack.

<figure><img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2FYmrkIPedfbKdHEDd70Ji%2FSync%20Metrics.png?alt=media&#x26;token=7f63afd6-77b5-469e-9df5-a6c9faa66193" alt="" width="563"><figcaption><p>Monitor every integration and data sync with live metrics.</p></figcaption></figure>