Change Standard Parts in Model Manager. Normteile im Model Manager ändern.

[radolph]

Standard parts, stored in class LIBRARY_3D, can not be changed. Also with admin rights Model Manager prevents changes.

There are reasons to prevent this changes. Because the standard parts are often used and changes have consequences.

However, there are many reasons for which standard parts need to be changed anyway. Wrong density, errors in geometry, unfortunate position when loading, missing attributes, color, cut protection ...

We have therefore created a workaround software that directly accesses the SQL database and the stored models in a semi-automatic approach. This allows the examination and modification of standard parts.

Normteile, die in der Klasse LIBRARY_3D gespeichert werden, können nicht mehr geändert werden. Der Model Manager verhindert dies auch bei Admin-Rechten.

Es gibt Gründe, diese Änderungen zu unterbinden. Denn die Normteile sind vielfach verbaut und Änderungen haben natürlich entsprechende Auswirkungen.

Es gibt gleichwohl viele Gründe, aus denen Normteile trotzdem geändert werden müssen. Falsche Dichte, Fehler in der Geometrie, unglückliche Position beim Laden, fehlende Attribute, Farbe, Schnittschutz...

Wir haben deshalb als Workaround eine Software erstellt, die direkt auf die SQL-Datenbank und die gespeicherten Modelle zugreift und in einer teilautomatischen Vorgehensweise die Prüfung und Änderung von Normteilen ermöglicht.

This is too expensive for many cases.Therefore the idea to improve the Model Manager, that with appropriate admin rights, the change of standard parts is allowed by default.

Das ist jedoch für viele Fälle zu aufwändig. Deshalb der Vorschlag zur Verbesserung des Model Manager, daß mit entsprechenden Admin-Rechten die Änderung von Normteilen standardmäßig zugelassen wird.

[GerardLeclercq]

Dear Ralph,

I hope that PTC will do something on that hurdle. Meanwhile, how to get this software as a workaround?

[sparca]

I'm interested in this software, too. where we can get it?

[MaxR.Kublin]

Model Manager blocks changes to Library Parts by "Business Object" - this is the reason why you cannot modify/overwrite a Library Part within

Model Manager, even if the underlying ACLs in the Database would allow this.

In a OOTB classic WM, Library Parts can be changed/overwritten by Administrators (just because the Standard ACLs are defined accordingly).

However, this is only a small part of the whole procedure mentioned by Ralph.

I have also developed such a procedure a while ago, but it consists of a lot of manual steps (=a recipe).

The ability to "edit" Library Parts has been a most wanted/needed funtionality over years, but it never made it into the OOTB Model Manager.

[thollerweger]

Since ModelManager 18 there is a standard class called "CORP_LIBRARY_3D" which can be enabled vie XML Entry:

  <Class extends="DMCorporateLibrary">

   <Name>CORP_LIBRARY_3D</Name>

  </Class>

If this class is enabled, you can change the class of a library part to this class ant then you are able to modify this part.

After modification change back the class to the standard LIBRARY_3D class.

[MaxR.Kublin]

YES. But be very cautious with modifications of library parts in general.

The only permitted (=makes sense) change of a library part is to FIX Errors, e.g.

wrong thread, wrong desity.

NEVER do other changes like:

- Moving/rotating faces

- Change length or other geometry

[S_Edgenear]

For parts that do not ever need to be modified, like screws, it makes sense to have them always read-only and not modifiable.

But there are standard parts that are sold, and that must be cut to length when used in a project, as an ejector pin in a mold.

What I think would be better, is not to make the original parts modifiable, but a quick way to read the original read-only library parts, and  instead of inserting them in a project, would internally make derived parts (using inheritance) that would be assembled in a project. This way we have the best of both worlds.

In the case of an ejector part used in a mold, if we define a library using a family table, and apply the part in a mold, tu cut the part would change the instance of the family table, which is not intended, since the family table should be read-only. Tu cut it in assembly mode, has it's disadvantages too. We can create a normal part, and inside the part, create an inheritance feature that would reference the library part, which would be an instance of the library family table. (Previous versions of Creo would not update the geometry when inserting an instance of a family table part, it would insert the geometry of the generic always, but this has been solved). The problem with this workaround, is the time it takes to execute this procedure manually. Creo should really provide the user an option when inserting instances of family table read-only parts, to automatically make a derived part, using inheritance, or "Merge" feature.