Teamcenter Setup

[187lockdown]

Hi All,

Our site has recently installed TC Engineering 9.1.3.3 with NX4. We would like to configure some revision rules as currently when revising a part to say revision B users can still open revision A do changes an save revision A.

I remember from my training that this action was performed using Admin > Business modeler but im unclear of the steps after that.

Also is it possible to force changes to a part into a new item revision? Our existing setup allows users to checkout a revision perform modifications and then save them. We could like the action that when a user opens an NX dataset and applies a mod it auto prompts on save for a new revision.

If anyone has the steps for applying this modification we would be very happy.

Thanks.

John

 

[looslib]

When the user is finished with a revison, it needs to have its state set to Released. If your rules are set correctly, then a Released object cannot be modified.
In order to modify a Released object, the use will have to revise it which should force it to the next revision level.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli
Sr IS Technologist
L-3 Communications

 

[fgbrender]

You cannot modify a released item revision which leads me to believe you are not releasing item revisions. This is what forces changes into a new IR.

What you are asking is very complex as far a s setup is concerned. You not only have to define your business rules but you need to create workflow in order to apply release status.

Unfortunately, what you need cannot be communicated in this forum.

See the earlier thread regarding Tc migration.

 

[joshua0977]

I agree with "fgbrender". Do you release your revisions?
I'm unclear about the need to revise Rev "A" while modifying Rev "B"? If you revised Rev "A" while working on Rev "B" how would you flow down those changes?
Anyway...In the Business Modeler you can set a rule for the Number of Working Revisions you would like but more than 1 "Latest Working Revision" of a part would be hard to manage unless your were using the PSE to manage your use of Variant Configurations, Incremental change etc.

As for forcing an auto prompt to do a Save As to a new Revision when a modification occurs could be cumbersome. When would that rule apply? On every save of a dataset?
I would think that using the Business Modeler to set a "1" working revision rule for all Revisions would give you what you want provided you do put a Release Status on all previous revisions. If nothing else a Pre-Release would suffice. You probably need to discuss this in more detail than this forum will provide.
Jay

 

[Mattimuss]

Revision rules have nothing to do with having write access to multiple working datasets. They control which revision of an item is loaded as a component of an assembly in the PSE or CAD tool. Revision rules are not part of Business Modeller, they are created or modified with the PSE application.

In order to prevent users from modifying previous revisions, you need to apply a status to the revisions that you would like to be locked. TcEng comes with a few simple release procedures and it should be fairly easy to modify one of these or create a new one to suit your needs. (this is assuming that the class that you took was the admin class and you still have the book to use as reference.)

I would guess that it is possible to customize NX to enable you to suggest saving as a new revision upon save, but it would require quite a bit of programming to do so.

What are you hoping to accomplish by having NX prompt for a new revision at every save anyway? The users should be saving their work in the CAD tool several times per day and saving each into a new revision would create a huge amount of garbage data in your system. TcEng already stores the last 3 saves as dataset versions in the background by default and you could specify a higher version limit if you want more. The dataset versions are then purged down to the latest when a status is applied so that the older "garbage" versions aren't stored forever.