Bring Attention to Affected Data

[jer3d1]

Working inside of PDMLink...
When modifying CAD data, it is possible to change the 3D model without updating the drawings that refer to it. (The same thing holds true for parts to assemblies.) Hypothetically, if unchecked, changes like this may allow inaccurate data to creep into production. I don't know of any checks in PDMLink or Pro-E to prevent this from happening. Is this responsibility entirely governed by humans? Are there any config settings or Windchill options that help with these requirements?

[avillanueva]

I do not think this is an issue for PDMLink, its just fundamentally how
Pro/E works. We rely on the as-stored baseline of the drawing which
when compared to the latest iterations is an indication that "something"
could have changed. A change in the model file could be anything or
nothing at all. There is no way to tell. I guess you could assume that
any change is significant and check the drawing.

At the end of the day, the drawing relies on the model. You can always
create this situation in a workspace. Download the latest drawing and an
older version of the model. The drawing will be affected by that even if
released. I tell my users to never rely on print outs generated from a
ProE workspace, only to use ones generated from Product View via the
publisher. Its about providing consistent output, however you define
that to be.

[MikeLockwood]

This is why states exist in PDMLink and New Revisions.

When a drawing (which shows data in a 3d model) gets to the point where you need it to be static, you change it's state (thru Set State, or Promotion or Change Notice, or other). You have to set up permissions such that no one can Modify at the current state, requiring Revise instead.

[jer3d1]

We also use states to govern our access. This is a very effective control measure for us. It's the fact that changes may or may not be initiated by a group who is familiar with the data impact and having some sort of attention brought to the surface would be a valuable resource. The information is already held in the system, it just doesn't seem to be brought to the surface in the change processes.




From: Lockwood,Mike,IRVINE,R&D [