Enovia - Why complicate something "simple"..?

I know how it works, but why do we need an instance lock..? 

Can anyone give me a good example..?

Why is one lock not enough..? I mean, if you want to make changes to a part you lock it, the same with a product.. if you make changes you lock it... Keep it simple. 

Second, why Documents and Part References...? 

The user does not need to know this... Users think Assemblies, Parts, Drawings, Catalogs, ect...? Again.. why not keep it simple...? (I know, Enovia might need the Part Reference and document Revision... But the user don't)

Not that i'm complaining... because Enovia V6 is a huge step in the right direction...But... :-)

Thx. Michael Laursen 

Just a guess, but at some companies, some assemblies are so large that multiple people work on the same assembly at the same time.  Allowing the users to lock their instances, while leaving the product unlocked, keeps people from accidentally changing the wrong instances. 

Jim Strawn
IT Specialist, Lead
COE Board of Directors, Treasurer
Cessna Aircraft Company

In Reply to Jim Strawn:

Just a guess, but at some companies, some assemblies are so large that multiple people work on the same assembly at the same time.  Allowing the users to lock their instances, while leaving the product unlocked, keeps people from accidentally changing the wrong instances. 

Jim Strawn
IT Specialist, Lead
COE Board of Directors, Treasurer
Cessna Aircraft Company

Thx Jim, 

Don't you need both locks(Usage and reference) on the assembly in order to save changes to it... ? 

In Reply to Michael Laursen:

Thx Jim, 

Don't you need both locks(Usage and reference) on the assembly in order to save changes to it... ? 

Not out of the box.  Your system admins may have changed the policies to require this.   In V6, the locks are there to ensure you are the only one that can change something.  No lock means anyone can change it (within the policy of organization and context permissions - i.e. Manufacturing Roles usually can't change Engineering data). 

If I remember right, in ENOVIA V5 (also known as LCA, aka VPLM, aka VPM V5) it was the opposite - you had to have the locks to save. 

Jim Strawn
IT Specialist, Lead
COE Board of Directors, Treasurer
Cessna Aircraft Company

In Reply to Jim Strawn:

In Reply to Michael Laursen:

Thx Jim, 

Don't you need both locks(Usage and reference) on the assembly in order to save changes to it... ? 

Not out of the box.  Your system admins may have changed the policies to require this.   In V6, the locks are there to ensure you are the only one that can change something.  No lock means anyone can change it (within the policy of organization and context permissions - i.e. Manufacturing Roles usually can't change Engineering data). 

If I remember right, in ENOVIA V5 (also known as LCA, aka VPLM, aka VPM V5) it was the opposite - you had to have the locks to save. 

Jim Strawn
IT Specialist, Lead
COE Board of Directors, Treasurer
Cessna Aircraft Company

Thx again Jim, 

We are currently running Enovia V5 and we need both lock to make changes to an assembly. But it makes sense if you in V6 can leave the assembly onlocked and only lock the components you are working on. 

Thank you for your help.. 

B.R. Michael 

Yeah, i'm not sure why LCA worked that way.   VPM V4 (aka 1.6) didn't.  It works more like V6.  

Jim Strawn
IT Specialist, Lead
COE Board of Directors, Treasurer
Cessna Aircraft Company

Late answer but I feel this is a common misunderstanding of ENOVIA V5 VPLM Navigator.

Depends on what you are modifying ; Instance controls the use (or position) of a geometry, and Reference controls the geometry/content.

Example of the wheels of a car : Let's say you have four CAR_Rim.CATPart inside CAR.CATProduct.

If you update the shape of the CAR_Rim (size, numbe of spokes, etc), you'll need to save the Reference of CAR_Rim (geometry of CAR_Rim).

If you want to change the wheelbase, you'll need to change the Reference of CAR_Rim (move the CAR_rim instances)

If you want to model only the left half of the car, you'll need the Reference of CAR (you're changing the content of CAR.CATProduct)

Now remember, you can have more than one CAR.CATProduct in something like FACTORY.CATProduct ; if you add a CAR.CATProduct you'll need to save the FACTORY.CATProduct reference and CAR.CATProduct instance.

And like Jim mentionned, admins can change what's required to save ; when working with ENOVIA I found that checking "Partial Save authorized" was a very, very good thing. Tools > Options > Compatibility > ENOVIA V5 VPM > first box up top

Simon

In Reply to Michael Laursen:

In Reply to Jim Strawn:

In Reply to Michael Laursen:

Thx Jim, 

Don't you need both locks(Usage and reference) on the assembly in order to save changes to it... ? 

Not out of the box.  Your system admins may have changed the policies to require this.   In V6, the locks are there to ensure you are the only one that can change something.  No lock means anyone can change it (within the policy of organization and context permissions - i.e. Manufacturing Roles usually can't change Engineering data). 

If I remember right, in ENOVIA V5 (also known as LCA, aka VPLM, aka VPM V5) it was the opposite - you had to have the locks to save. 

Jim Strawn
IT Specialist, Lead
COE Board of Directors, Treasurer
Cessna Aircraft Company

Thx again Jim, 

We are currently running Enovia V5 and we need both lock to make changes to an assembly. But it makes sense if you in V6 can leave the assembly onlocked and only lock the components you are working on. 

Thank you for your help.. 

B.R. Michael 

The image in attachement is a good one slider that explain all possible cases of locks on Part Reference and Part Instances with ENOVIA LCA / VPM Nav.  This is whats required to enable team work while someone work on the geometry while someelse could work on the positioning of the part within one or multiple assembly in different products.  It enable to quickly understand what need to be lock depending on what change is to be performed.