Sovelia Vault

How can you automate Autodesk Vault without being a coder?

Why do we use lifecycle states in Autodesk Vault? Because we want to track where in the process our design is, in line with our business process, and allow others access to those designs at the right time.

Typically our state change indicates that other functions need to happen, such as translations, notifications, and general information distribution to all required stakeholders. Often an admin overhead that impacts our time available for innovation, Autodesk Vault can be customised to automatically trigger and take care of these mundane tasks for you.

The only problem is, you have to be a coder to put these in place and, once in place, further code change may be needed when your processes need to change.

Sovelia Vault offers the best of both worlds; A configurable add in to Autodesk Vault that any competent administrator can adjust and use. It offers the automation to recover that design time, but without the shackles of holding you back when your processes evolve.

See Symetri consultant Graham Harrison walk through Sovelia Vault and how it can really benefit you - no coder skills needed to automate and configure your Autodesk Vault.

How do you guarantee transformation of the correct data from your design environment to PLM?

08 September 2021

When you look at all PLM systems one of the fundamental issues they face is getting the correct, good quality data into the PLM system in the first place. “Crap in, Crap out” is a phrase that has been used to describe this problem whenever talking about transferring information from one system to another. How do you guarantee the correct information is transferred from your design environment to PLM?