This is a SolidWorks Technical Tip that SolidWorks had on their website in the middle of June for public consumption. I believe that during the overhaul of their website this document was deleted or misplaced. I wanted to take the opportunity to repost it because I think that it has very important information for upgrading to the latest version of SolidWorks (new release or service pack). I take no responsibility for what this document says and likewise I take no credit for it either. Thanks and I hope you enjoy!

___________________________

SolidWorks Technical Tip

Creating and validating a dataset

Solution ID: S-023889

Applies to: SolidWorks

Version: All Versions

Category: Administration, Installation, Best Practice, Tech Tip

Created: 06/10/2008

Last revised: 06/10/2008

When moving to a new version of service pack of SolidWorks software, you should have a test dataset that can be used to insure a smooth transition to the new version or service pack.

There are infinite ways to create and edit SolidWorks documents, and some of these elements can be unique to your company. When preparing for any software update, you should do some level of validation testing in your environment to insure the upgrade goes smoothly.

One way to prepare for any software migration is to create a sample of representative data (dataset) and processes to insure the new software works the way you intend to use it. The process side takes into consideration the way your designs are created and edited.

Creating a dataset

When it comes to validating your data and methodologies, more is not better. What you are looking for is different types of design processes, file types, and input that would make a dataset unique:

• Different design processes and methodologies examples of this include:
  • In-context design
  • Configurations and design tables
  • Use of Hole tables
  • Drawings and annotations
  • Sheet metal design
  • Exploded assembly views
  • Use of different feature types
  • Complexity of design
  • All document types used should be included (parts, assemblies, drawings, formats, design library parts)
• Different organizations within your company
• Different design groups
• Use of imported data
• Different SolidWorks setting, formats, and templates
• Previous problems or issues
• Use of different languages
• New SolidWorks features or functions

As the organization of your data or the way you use SolidWorks changes, so should your validation test methods and datasets change as part of an ongoing process.

The size of your dataset should be kept reasonable in size (~2-3GB) so the files can be tested and transferred, if necessary, easily. It is prohibitive to maintain and test all of your SolidWorks data. Choose wisely and keep it up to date.

Documents added to the dataset should be clean and not contain (after a forced rebuild using Ctrl-Q) FeatureManager design tree warning or errors for part and assembly features, mate groups, and drawing views. If there are issues with a design, clean the problem up before adding the document to the validation dataset.

Validating the dataset and process

Once your datasets and design validation methodologies are created, you will need a way to test this information.

To validate your representative dataset:

• Convert Files – This will open the documents and convert them to the new version of the SolidWorks. This Task Scheduler (Convert Files) will report any issues with the document. This only will find the simple problems and does not provide a forced rebuild or anything outside of the ability to open the document.
• Macros – Creating a macro to test documents can be effective but are harder to create and maintain. These macros also offer only limited coverage to the different features, functions, and processes used.

To validate design methodologies:

A pilot group is one way to validate your processes and methodologies is to have a small test group pilot the new version or service pack doing real work. This is the best way to insure the way your organization uses SolidWorks is acceptable in the next version/service pack.

This is easier to do in a service pack as the data is compatible to the older service pack, while a new version is not backward compatible. Also, it is not recommended to perform production work in a beta version as the possibility exists that the files may not be compatible with the final version. While this is rare, it is a possibility.

The pilot group should validate:

• Design processes and methodologies
• Any add-in applications
• Data management tools, workflow, etc.
• Printing and plotting
• Any other custom macros or programs that are used by SolidWorks
• Test cases – Create simple checklists to run through design scenarios, common practices, etc. These checklists are simple to create and can be used by the pilot or beta test group to insure consistency in your validation testing.
• Macros – Some processes can be repeated by creating macros. This will require some level of understanding of VB (Visual Basic). A good start to these macros is to record a macro and use that as a basis for the test. One thing you will find is the macro recorder does not record all the functions to automatically re-run the test. Some editing of the macro will be required to make it run.

Conclusion

Creating a good, representative dataset is useful for insuring a smooth transition between new versions and service packs. Remember it is quality not quantity when creating the dataset.

The processes and methodology validation is also important to insure all applications and tools work as intended. Also remember to update your datasets and design process validation as new processes, design groups, new SolidWorks functionality, or other application changes occur.