scotty7
New member
- Jul 27, 2004
- 111
We are currently running NX2, and will probably upgrade to NX3 sometime later this year.
However, I've seen a few comments on refiling parts when an NX upgrade is taken (as UG would do this on the fly anyway). We are a fairly new customer to UG, but we are expecting to be generating large (20,000+ item) assemblies and geometrically complex components within them. What experience is there when running ug_refile_part of regeneration failures, partfile checking and any other QA issues? What account is taken of partfile version numbers in Teamcenter, and does this have a knock on effect on the assemblies? How long does the process take, and how much dedicated resource does it absorb? We currently have over 100,000 parts with 600,000 drawings on our legacy database (not being translated) and we expect the use of UG will generate a larger database than this.
Any experience, good or bad, would be appreciated so we can take the leap forward with our eyes open.
However, I've seen a few comments on refiling parts when an NX upgrade is taken (as UG would do this on the fly anyway). We are a fairly new customer to UG, but we are expecting to be generating large (20,000+ item) assemblies and geometrically complex components within them. What experience is there when running ug_refile_part of regeneration failures, partfile checking and any other QA issues? What account is taken of partfile version numbers in Teamcenter, and does this have a knock on effect on the assemblies? How long does the process take, and how much dedicated resource does it absorb? We currently have over 100,000 parts with 600,000 drawings on our legacy database (not being translated) and we expect the use of UG will generate a larger database than this.
Any experience, good or bad, would be appreciated so we can take the leap forward with our eyes open.