@Dave_K sounds like a problematic behavior. "structure only" and "partial load-lightweight" ought to be quick without the opening and saving, etc. of all of the BOM.
Are you using Wave links to routing object geometry (or some other wave link to what Windchill doesn't yet support as a reference) in your assemblies?
We observe a similar behavior with Wave links created using Routing Objects... especially when part families are involved. What I have my users do is ensure that they "Add to workspace" ENTIRE part families so that NX has in the local cache access to all instances it may need to update a model even if Windchill isn't capable to recognize which ones it may require.
The other thing to consider as well - if the syslog is complaining about Teamcenter or Windchill issues - is that there could be some sort of behavior in NX that is causing excessive calculations on the Windchill end and that is ultimately what's giving rise to this excessive time to open/load. We ran into this with reporting NX_Mass when there were modeling "issues" so to say. NX didn't recognize anything as wrong, but however the model was trying to calculate mass caused Windchill to just sit there for as long as 30 minutes on opens or saves until it would sort out the issue. The resolution was to turn off mass reporting from NX to Windchill.
In NX, it might be worthwhile running:
- Examine Geometry
- Feature Reply
- Part Cleanup
All that with the model FULLY LOADED. This ought to point out any model consistency errors. What you're looking for is that Data Structures, Consistency, Face-face intersections and Self-intersections are passing. If not, that could be part of the issue as well that NX can work through but Windchill cannot.
