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.
This blog post is tackling the most common barriers with Vault - ERP integration projects, like duplicate files, properties spread around, unresolved models, uncategorized files, poor planning and lack of Vault knowledge, and describes some examples how you can prepare for success using the right tools, expertise and knowledge
Watermarking can signify whether the document is a preliminary version, not ready for production or just a document for pre-review of a design. A watermark stamp is hard to miss and will most likely eliminate the risk that production is done from non-released documents.
Before we at Symetri can begin to offer a solution, it is our responsibility to always collaborate and try to find the best option for a specific company and their business goals, and always communicate what challenges a solution we recommend will solve.