Most of our facility works with imprecise assemblies. Our load options are such: Engineering uses "load latest", and the shop floor "latest with status". Also using Teamcenter 11, and NX11.
Now our aero department likes to maintain "baselines", of how the car was configured at a certain period in time, so I created a precise assembly for them, as the development car (which they experiment with), and then at various times they do a save as, and name it accordingly. These are basically archives, of how the car was configured at that point, incase they need to go back and review something.
Since this assembly has some live wave links in it, you can't just save the top level assembly, you have to save the top level, and the two main subassemblies as a set. It's confusing, since they aren't daily NX users, and things go haywire at times, and I get called back to fix it.
Also, I have noticed that some sub asssemblies being used by other departments are showing up as precise, when they shouldn't be. I suspect they are added to this aero assembly, and when the top level is saved, the subassemblies are being made precise.
I'm trying to come up with a methodology to resolve both issues, and thought of bookmarks. Will a book mark remember the revision, like a precise assembly does? If we did away with the precise assemblies, and used a bookmark, it may save some headache.
Thoughts?