Violet’s Automations feature allows you to automate data transfer from one app to another. For example, set up an automatic sync of Teamcenter parts to your ION library.
This powerful feature works by ingesting and mirroring data from a source app into Violet, then pushing it to a downstream tool that has a known, mapped data structure. Once an automation is created, Violet will continue to push new revisions to the target app when they occur.
Read more below for the current automations we support.
Teamcenter to ION
Save your engineering team valuable time by automating a previously manual task: pushing assemblies from Teamcenter into your ION parts library.
This automation is configurable in a number of ways:
Push parts on an individual basis, or by default for your entire Teamcenter instance
Configure rules for which parts you want to push, for example pushing only released parts
Update revision scheme post-push to ensure consistency in ION
Curious how it works or ready to get started? Follow the instructions below.
Instructions
Connect ION. First, you will need to have ION integrated in Violet. Connect and configure your integration by following the instructions here. Make sure the integration is fetching Parts.
Connect Teamcenter. Next, you will set up your Teamcenter integration. Connect and configure your integration via the instructions here.
Configure your automation. Once connected, there are two ways to sync data from Teamcenter:
Part-by-part
In this method, you can push parts to ION on a one-off basis.
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!
Once successful, you will now see this part and its children in Teamcenter, Violet and ION.
Entire integration by default
In this method, you can configure a Teamcenter integration to automatically push all parts to ION, including new revisions.
Configure this automation when you create the Teamcenter integration. See Step 3 above, Fetching data from Teamcenter.
You will have the option to only push released data from Teamcenter:
Confirm and update revision scheme. Violet will be able to detect the part revision scheme(s) available in your ION integration. From there, you can update the selected scheme within ION.
What’s needed from your team
We’ll need to set up a couple things first:
Violet will need access to your Teamcenter server, which is either via simple whitelisting or VPN. Detailed info here.
Let us know if you have any Custom Item Types or Custom Properties in Teamcenter
We’ll need a read-only Violet user account for your Teamcenter instance, and access to Active Workspace if you have it
This automation pushes assemblies from Teamcenter to NetSuite to populate Inventory items.
This automation is configurable in a number of ways:
Push parts on an individual basis, or by default for your entire Teamcenter instance
Configure rules for which parts you want to push, for example pushing only released parts
Curious how it works or ready to get started? Follow the instructions below.
Instructions
Connect NetSuite. First, you will need to have NetSuite integrated in Violet. Connect and configure your integration by following the instructions here. Make sure the integration is fetching Items.
Connect Teamcenter. Next, you will set up your Teamcenter integration. Connect and configure your integration via the instructions here.
Configure your automation. Once connected, there are two ways to sync data from Teamcenter:
Part-by-part
In this method, you can push parts to NetSuite on a one-off basis.
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!
Once successful, you will now see this part and its children in Teamcenter, Violet and NetSuite.
Entire integration by default
In this method, you can configure a Teamcenter integration to automatically push all Bills of Material (BOMs), sub-assemblies and parts to NetSuite, including new revisions.
Configure this automation when you create the Teamcenter integration - see Step 3 above, Fetching data from Teamcenter.
You will have the option to only sync released data from Teamcenter:
What’s needed from your team
We’ll need to set up a couple things first:
Violet will need access to your Teamcenter server, which is either via simple whitelisting or VPN. Detailed info here.
Let us know if you have any Custom Item Types or Custom Properties in Teamcenter
We’ll need a read-only Violet user account for your Teamcenter instance, and access to Active Workspace if you have it
When configuring your Teamcenter integration, select Datum in the dropdown menu to push part information to Datum’s part library.
👆Click to zoom
Solidworks PDM to Fusion
Automate the sync of assemblies from SolidWorks PDM into your MES or ERP.
Currently, this automation supports Solidworks PDM via .csv import. A Solidworks plugin is on our feature roadmap and launching soon.
Curious how it works or ready to get started? Follow the instructions below.
Instructions
Connect your MES, for example Fusion. First, you will need to have your MES integration set up. For Fusion, connect and configure your integration by following the instructions here. Make sure the integration is fetching Parts.
Import a BOM from Solidworks PDM. Next, import a BOM from Solidworks PDM by following the instructions here. To push all parts to Fusion, select it in the dropdown menu:
👆Click to zoom
[Optional] Push released parts only. To push only released parts, check the box beneath the dropdown.
If you are interested in this automation (or any others), please reach out to help@violetlabs.com.
FAQ
What data is pushed in a Teamcenter PLM automation?
Currently, Violet pushes the following properties as well as files (this is configurable):
Part Number
Revisions
Release Date
Owner
Last Modified Date
Last Modified By
Center of Mass
BOM Qty
[NEW] STEP Files
[NEW] PDF documents
For a PLM —> ION automation, Violet also detects the revision scheme(s) available in the user’s ION instance. The user can then update the selected scheme in ION.
The Violet integration is highly configurable - if your team needs to fetch and push other properties, including custom properties, please reach out to us.
