Long Wait Times When Switching Work Parts

[Andy512]

While working in the context of an assembly, when I change the work part from one item to the next, the computer seems to be spending a lot of time "Updating Objects"

Some times as much as 2-3 minutes even though every thing is fully opened and nothing has changed.

These assemblies have approx 20 subassemblies with 2-10 components each, assembly constraints, and a few wave links. Nothing I would call huge.

Is there a particular setting that could be changed?

I've gone thru the customer defaults and tried a few things like delay interpart update but no luck.

We are running NX5.0.3.2 (64bit) Teamcenter 2005 sr1/2007
Intel Xeon 3.2G, 6GB, XP64

Thanks,

Andy

 

[JohnRBaker]

I would look first at TeamCenter since changing Work Part, depending on how you have your system set up, may require a complex check-in/check-out procedure with perhaps even notifications.

The next issue is that changing an item to be the work part, if you're using partial loading, will then require that the system do a full load on the part just made the work part for the first time in that session.

Anyway, those are a couple of thoughts.

John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

 

[hudson888]

Andy,

On partial loading you have the explanation from John which is as always entirely correct. I'd add that the benefit of partial loading is greater than the cost, in that you may not need to make every part in your assembly the displayed part from session to session. Therefore you employ a trade off taking less time to open the assembly in exchange for more time to swap between parts. But this should only happen the first time, so on the second occasion things should be noticeably quicker. You could turn off partial loading to check, but you may be on the wrong track if you leave it off permanently.

Automatic updates of linked geometry are another source of slowing you down in making something the displayed part, usually just the first time and less frequently thereafter unless you make a change that requires it. If this were the case then you would see features counting down through the updating process in the status bar. Again whether or not you're using partial loading has bearing on whether this occurs, as do settings you can change as to how and when linked geometry is maintained.

The teamcenter connection will be checking in and out as John describes. Users of workflow within teamcenter may find this less intrusive once an owner is assigned to a file others won't be kept waiting in order that the server register that they are checking out the file whenever they open it, because if you don't own the signoff you can't check out the file.

Check with your IT department whether the server used for teamcenter is running other corporate applications. In general this would be a bad thing. Specifically we had difficulty with a conflict between port usage to do with how somebody had implemented some usage of SAP taking priority over the server communications for the teamcenter database.

best regards

Hudson