- All parts get updated
- Consistent version level of database
- Reduced loading time
- Conversion of standard features
- Automatic changeover to new basic features (e.g. joint conditions)
- Less effort for the user
- Consistent approach to conversion
- New technics can be used earlier (in consultation)
- The refile shows, if the NX database can be opened and saved with the newer version
Optimizing NX refile processes and NX refile times:
- Processing sequence of NX part files
- Single parts – newest parts first, oldest parts last
- Assemblies – bottom up method
- Processing sequences can be controlled for example by volume groups
- Refile of several clients at the same time
- Analyzing the refile logfiles according to status, error messages, etc.
- Central repository of NX refile logfiles
- Central control of refile processes in multisite environments
- Central control of refile options
- Splitting the refile on several computers
- Organization of several refile processes on one computer (time factor)
- Organisation von mehreren Refile-Prozessen auf einem Rechner (Zeitfaktor)
- Avoiding „double refile“
- Supporting tool for the preparation of upgrades (data quality)
- Simplifying the change to a newer NX version
- Teamcenter single and multisite are fully supported
- Native refile is supported