Skip page content

Security Model example in Vault Collaboration

generic viagra generic viagra viagra viagra cheap levitra online vardenafil cheap levitra online vardenafil cialis online cialis online levitra online levitra online levitra online levitra online viagra viagra generic cialis generic cialis levitra online levitra online india cialis india cialis viagra viagra cialis online cialis online

I have recently posted a bit about folder level security in Vault and how that can restrict people from changing data in locations they shouldn’t have access to. Potentially more important is the ability to use the folder security in conjunction with Lifecycle based security.

Take a look at the two vault interfaces in figures 1 and 2 below.

This first is a look at what an engineer or designer might see when logging into Vault:

This second image shows how a shop floor user or other viewer might see using the Vault Collaboration light weight web client:

Notice that the viewer has been configured to only display data that is a “Released” or equivalent state. This ensures that they are viewing only the correct data and at the right time in the files process lifecycle.

Contributed by Ben of the Tata Technologies CAD Geeks

Breaking Down the "L" in PLM

I have seen and heard all kinds of different descriptions of what PLM (Process Lifecycle Management) is. They usually end up way too complex with lifecycle being the primary hangup. Lets make it simple:

Process – A series of steps that need to occur

Lifecycle – A time based measure of the process (What steps can occur when)

Management – A way to control something

So by my way of thinking, Lifecycles are nothing more than a way to define what should happen at a specific point in time in a process.

Autodesk’s Vault Workgroup and Collaboration fit into this category of engineering tools, and the Lifecycle part is a key to the latest Autodesk data management offerings. The Vault solutions allow you to configure as many lifecycle schemes as necessary for your different processes. Each lifecycle scheme can then have as many lifecycle states as you need to define a process. The great thing about a lifecycle state is that it controls exactly who can access a document and what they can do with it.

I have also heard it described as “allowing the right people to access the right documents at the right time” in reference to the latest Vault products.

Contributed by Ben of the CAD Geeks

Define your own process

All the companies I deal with typically have their own process intricacies with different numbers of process states. I usually discuss design processes in terms of “work in progress”, “released” and “obsolete”. Sometimes companies will have their own terminology or additional process states. With Vault 2010 (Workgroup and above), you can create as many process states with their own names as required. These are referred to as lifecycle states in Vault.
Here is an example of a couple extra lifecycle states used in a file list.
Each lifecycle state can have its own security for file access as well as for transitioning between states. The security model can be created with endless possibilities as shown in the image below.
Contributed by Ben of the Tata Technologies CAD Geeks

Vault Workgroup – Lifecycle based permissions

One of the great features in the new Vault Workgroup 2010 is the ability to control access permissions based on the lifecycle state of the file in question. This means that only the appropriate personnel have access to a file when it is Work in Progress, Released, or Obsolete.

As an example take a look at the folder contents in this image. The administrator has access to all files regardless of lifecycle state.

But if we look at this image showing the same folder, there is only one released file shown due to the access permissions assigned to the “manufacturing” user.

This opens up the door for a whole new simplified release management structure. No moving files between WIP and Released folders that can be next to impossible to do correct consistently in Inventor… Just access to the right data, at the right time, by the right people.

Contributed by Ben of the CAD Geeks

Change State and Revise right in my Inventor tools?

Well lookee there. The new data management tools in the Vault 2010 products are sure making it easier to manage the release of drawings for production. This is definitely the case with the Change State and Revise tools that are now built right into both the Inventor and AutoCAD environments with Vault Workgroup.
The Change State command allows us to manage the lifecycle of the file directly from the CAD window, and will even automate the Revision assignment process if Vault Workgroup is configured to do so. The Revise command will let us manually define the Revision with more control such as might be required for tertiary revisions.
Contributed by Ben of the INCAT CAD Geeks

CAD Geek Speak! Autodesk CAD Geek Speak! Dassault Systêmes</i> CAD Geek Speak! Siemens